SIMATIC WinCC Basic V13.0 System overview of STEP 7 and WinCC 1 Readme 2 Installation 3 Migrating projects and programs 4 First steps 5 Introduction to the TIA Portal 6 Editing projects 7 Editing devices and networks 8 Programming the PLC 9 System Manual Printout of the online help 02/2014 Visualize processes 10 Using technology functions 11 Using Team Engineering 12 Using online and diagnostics functions 13 Hardware documentation 14 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 indicates that minor personal injury can result if proper precautions are not taken. NOTICE indicates that property damage can result if proper precautions are not taken. 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 (R) 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 NURNBERG GERMANY 04/2014 Subject to change Copyright (c) Siemens AG 2014. All rights reserved Table of contents 1 2 System overview of STEP 7 and WinCC....................................................................................................25 1.1 Scaling of STEP 7 and WinCC in the TIA Portal.........................................................................25 1.2 Options for STEP 7 Engineering System....................................................................................26 1.3 Options for WinCC Engineering and Runtime systems...............................................................26 Readme......................................................................................................................................................29 2.1 General notes..............................................................................................................................29 2.2 2.2.1 2.2.2 2.2.3 2.2.4 2.2.4.1 2.2.4.2 2.2.4.3 2.2.4.4 2.2.4.5 2.2.4.6 2.2.5 2.2.5.1 2.2.5.2 2.2.5.3 2.2.6 2.2.6.1 2.2.7 2.2.7.1 STEP 7 Basic..............................................................................................................................33 Security information.....................................................................................................................33 News...........................................................................................................................................35 Notes on use...............................................................................................................................35 Editing devices and networks......................................................................................................36 General information on devices and networks............................................................................36 Use of modules on the S7-1200..................................................................................................37 Replacing ET 200S positioning modules.....................................................................................38 CP 343-2 on SIMATIC S7 Embedded Controller EC31-RTX......................................................38 Notes on online and diagnostics.................................................................................................38 Network components...................................................................................................................39 Programming a PLC....................................................................................................................40 General notes on PLC programming...........................................................................................40 Instructions..................................................................................................................................42 Testing the user program............................................................................................................44 Inter Project Engineering (IPE)....................................................................................................45 Notes on IPE...............................................................................................................................45 Technological functions...............................................................................................................45 Notes on technological functions.................................................................................................45 2.3 2.3.1 2.3.2 2.3.3 2.3.4 2.3.5 2.3.5.1 2.3.5.2 2.3.5.3 2.3.5.4 2.3.5.5 2.3.5.6 2.3.5.7 2.3.6 2.3.7 2.3.8 2.3.8.1 2.3.8.2 WinCC Basic...............................................................................................................................45 Security information.....................................................................................................................45 News...........................................................................................................................................47 Notes on use...............................................................................................................................47 Migration......................................................................................................................................50 Engineering System....................................................................................................................53 Screens and Screen Objects.......................................................................................................53 Tags and connections.................................................................................................................57 Alarm system and alarm displays................................................................................................59 System functions.........................................................................................................................60 Recipes.......................................................................................................................................60 User administration.....................................................................................................................60 Communication...........................................................................................................................60 System-wide functions................................................................................................................63 Compiling and loading.................................................................................................................63 Runtime.......................................................................................................................................66 Notes on operation in Runtime....................................................................................................66 Notes on operation of panels in Runtime....................................................................................68 WinCC Basic V13.0 System Manual, 02/2014 3 Table of contents 2.3.9 2.3.9.1 3 4 Installation..................................................................................................................................................73 3.1 Notes on the installation..............................................................................................................73 3.2 3.2.1 3.2.2 3.2.3 3.2.3.1 3.2.3.2 3.2.3.3 3.2.4 3.2.4.1 3.2.4.2 3.2.4.3 System requirements for installation...........................................................................................74 Notes on licenses........................................................................................................................74 Notes on the system requirements..............................................................................................75 System requirements STEP 7 Basic...........................................................................................76 Licensing of STEP 7....................................................................................................................76 Handling licenses and license keys.............................................................................................78 Software and hardware requirements STEP 7............................................................................80 System requirement for WinCC Basic.........................................................................................83 Software and hardware requirements.........................................................................................83 Parallel installation......................................................................................................................87 Licenses and Powerpacks...........................................................................................................88 3.3 Installation log.............................................................................................................................92 3.4 Starting installation......................................................................................................................93 3.5 Checking availability of updates and support packages and installing them..............................95 3.6 Displaying the installed software.................................................................................................97 3.7 Modifying or updating installed products.....................................................................................98 3.8 Repairing installed products........................................................................................................99 3.9 Starting to uninstall....................................................................................................................101 3.10 3.10.1 3.10.2 3.10.3 Installing and uninstalling the migration tool..............................................................................103 System requirements................................................................................................................103 Installing the migration tool........................................................................................................103 Uninstalling the migration tool...................................................................................................104 Migrating projects and programs..............................................................................................................105 4.1 4.1.1 4.1.2 4.1.2.1 4.1.2.2 4.1.2.3 4.1.3 4.1.4 4.1.5 4.1.6 4.1.6.1 4.1.6.2 4.1.6.3 4.1.6.4 4.1.6.5 4.1.7 4.1.7.1 4.1.7.2 4.1.7.3 4 HMI devices.................................................................................................................................69 Notes on HMI devices.................................................................................................................69 Migrating projects in a TIA portal project...................................................................................105 Migration of projects with the TIA Portal....................................................................................105 Preparing projects with the migration tool.................................................................................106 Migrating projects with the migration tool..................................................................................106 Calling the migration tool...........................................................................................................108 Creating a migration file............................................................................................................108 Migrating projects......................................................................................................................109 Displaying the history of the migration......................................................................................111 Display migration log.................................................................................................................111 Migrating WinCC flexible projects (Basic).................................................................................112 Basics (WinCC flexible).............................................................................................................112 Migrating engineering data (WinCC flexible)............................................................................117 Migrating runtime data (WinCC flexible)....................................................................................128 Migrating integrated projects (WinCC flexible)..........................................................................130 Reference (WinCC flexible).......................................................................................................134 Migrating integrated projects.....................................................................................................142 Migrating an integrated project..................................................................................................142 Post-editing integrated projects.................................................................................................144 Converting unspecified CPUs into specified CPUs...................................................................145 WinCC Basic V13.0 System Manual, 02/2014 Table of contents 5 4.1.7.4 4.1.7.5 4.1.7.6 Creating an integrated HMI connection.....................................................................................147 Re-linking HMI tags...................................................................................................................149 Deleting an unspecified connection...........................................................................................150 4.2 4.2.1 4.2.2 4.2.3 Migrating S7-1200 to firmware as of V4....................................................................................150 Basic information on upgrading to V4.......................................................................................150 Migrating to V4..........................................................................................................................153 Special considerations after migrating to V4.............................................................................154 4.3 4.3.1 4.3.2 4.3.3 4.3.4 4.3.5 4.3.6 4.3.7 4.3.8 4.3.9 Programming recommendations...............................................................................................156 The new S7-1500 CPU functions at a glance...........................................................................156 Symbolic addressing.................................................................................................................160 Using IEC timers and counters..................................................................................................161 Flexibly using enable output ENO.............................................................................................163 Using MOVE instructions in STL...............................................................................................164 Implementing array access with a variable index......................................................................166 Using PLC data types (UDT).....................................................................................................168 Querying and fixing errors in the program code........................................................................170 Using VARIANT instructions.....................................................................................................174 First steps.................................................................................................................................................181 5.1 6 Getting Started Documentation.................................................................................................181 Introduction to the TIA Portal....................................................................................................................183 6.1 6.1.1 6.1.1.1 6.1.1.2 6.1.1.3 6.1.1.4 6.1.1.5 6.1.2 6.1.2.1 6.1.2.2 6.1.2.3 6.1.2.4 6.1.2.5 6.1.2.6 6.1.2.7 6.1.2.8 6.1.2.9 6.1.2.10 6.1.2.11 6.1.2.12 6.1.3 6.1.3.1 6.1.3.2 6.1.3.3 6.1.3.4 6.1.3.5 6.1.3.6 6.1.3.7 6.1.3.8 User interface and operation.....................................................................................................183 Starting, setting and exiting the TIA Portal...............................................................................183 Starting and exiting the TIA Portal.............................................................................................183 Overview of the program settings..............................................................................................183 Overview of the script and text editor settings...........................................................................185 Overview of the print settings....................................................................................................186 Changing the settings................................................................................................................186 Layout of the user interface.......................................................................................................187 Views.........................................................................................................................................187 Portal view.................................................................................................................................187 Project view...............................................................................................................................189 Library view...............................................................................................................................191 Project tree................................................................................................................................192 Work area..................................................................................................................................195 Inspector window.......................................................................................................................203 Task cards.................................................................................................................................205 Reference projects....................................................................................................................207 Details view...............................................................................................................................209 Overview window......................................................................................................................210 User interface layout.................................................................................................................214 Keyboard operation in the TIA Portal........................................................................................218 Operating the TIA Portal with the keyboard..............................................................................218 Displaying an overview of all keyboard shortcuts......................................................................218 Basic functions of the TIA Portal...............................................................................................218 Using project-related functions..................................................................................................220 Arranging windows....................................................................................................................220 Navigating through the program interface.................................................................................221 Customizing editors...................................................................................................................222 Editing objects...........................................................................................................................224 WinCC Basic V13.0 System Manual, 02/2014 5 Table of contents 7 6 6.1.3.9 6.1.3.10 6.1.3.11 6.1.3.12 6.1.4 6.1.4.1 6.1.4.2 Text editing................................................................................................................................225 Editing tables.............................................................................................................................226 Using online functions...............................................................................................................227 Using the on-screen keyboard..................................................................................................228 Special features specific to the operating system.....................................................................228 Influence of user rights..............................................................................................................228 Expanding user rights................................................................................................................229 6.2 6.2.1 6.2.2 6.2.3 6.2.4 6.2.5 6.2.6 6.2.7 6.2.8 6.2.9 Help on the information system.................................................................................................230 General remarks on the information system.............................................................................230 Opening the supplied Help system............................................................................................233 Searching the Help system for keywords..................................................................................234 Full-text searches......................................................................................................................234 Using favorites...........................................................................................................................235 Printing help topics....................................................................................................................236 Configuring the display of tooltips and tooltip cascades............................................................237 Safety Guidelines......................................................................................................................237 Assembling customized documentation....................................................................................239 Editing projects.........................................................................................................................................241 7.1 The basics of projects...............................................................................................................241 7.2 Using logs..................................................................................................................................241 7.3 7.3.1 7.3.2 7.3.3 7.3.4 7.3.5 7.3.6 7.3.7 7.3.8 7.3.9 7.3.9.1 7.3.9.2 7.3.9.3 7.3.9.4 7.3.9.5 7.3.9.6 7.3.9.7 7.3.9.8 7.3.10 7.3.10.1 7.3.10.2 7.3.10.3 Creating and managing projects...............................................................................................242 Creating a new project..............................................................................................................242 Compatibility of projects............................................................................................................243 Opening projects.......................................................................................................................244 Upgrading projects....................................................................................................................245 Displaying properties of the project...........................................................................................247 Saving projects..........................................................................................................................248 Closing projects.........................................................................................................................249 Deleting projects........................................................................................................................249 Working with multi-language projects........................................................................................250 Project text basics.....................................................................................................................250 Select project languages...........................................................................................................252 Setting the editing language......................................................................................................252 Translating all project texts in tabular form................................................................................253 Translating text associated with individual objects....................................................................254 Translating texts using reference texts......................................................................................254 Exporting and importing project texts........................................................................................255 Application examples for multilanguage projects......................................................................257 Archiving and retrieving projects...............................................................................................258 Working with project archives....................................................................................................258 Archiving projects......................................................................................................................259 Retrieving projects.....................................................................................................................260 7.4 7.4.1 7.4.2 7.4.3 Using reference projects...........................................................................................................261 Basics of reference projects......................................................................................................261 Opening and closing a reference project...................................................................................261 Comparing reference projects...................................................................................................262 7.5 7.5.1 7.5.1.1 Editing project data....................................................................................................................263 Compiling and loading project data...........................................................................................263 Compiling project data...............................................................................................................263 WinCC Basic V13.0 System Manual, 02/2014 Table of contents 7.5.1.2 7.5.2 7.5.2.1 7.5.2.2 7.5.2.3 7.5.2.4 7.5.3 7.5.3.1 7.5.3.2 7.5.4 7.5.4.1 7.5.4.2 Loading project data..................................................................................................................265 Comparing project data.............................................................................................................273 Basics of project data comparison............................................................................................273 Carrying out an online/offline comparison.................................................................................274 Carrying out offline/offline comparisons....................................................................................274 Using the compare editor .........................................................................................................275 Protecting project data..............................................................................................................288 Protection concept for project data............................................................................................288 Revoking access rights for devices...........................................................................................289 Printing project contents............................................................................................................290 Printing project documentation..................................................................................................290 Printing module labels...............................................................................................................309 7.6 7.6.1 7.6.2 7.6.3 Undoing and redoing actions.....................................................................................................312 Basics of undoing and redoing actions......................................................................................312 Undoing an action.....................................................................................................................314 Redoing an action.....................................................................................................................315 7.7 7.7.1 7.7.2 Finding and replacing in projects...............................................................................................316 Information on the search function............................................................................................316 Search and replace...................................................................................................................317 7.8 7.8.1 7.8.2 7.8.3 7.8.4 Working with text lists................................................................................................................319 Text lists....................................................................................................................................319 Creating user-defined text lists..................................................................................................320 Editing user-defined text lists....................................................................................................321 Editing system-defined text lists................................................................................................321 7.9 7.9.1 7.9.2 7.9.3 7.9.4 Using memory cards.................................................................................................................322 Basics about memory cards......................................................................................................322 Adding a user-defined card reader............................................................................................323 Accessing memory cards..........................................................................................................324 Displaying properties of memory cards.....................................................................................324 7.10 7.10.1 7.10.2 7.10.2.1 7.10.2.2 7.10.3 7.10.3.1 7.10.3.2 7.10.4 7.10.4.1 7.10.4.2 7.10.4.3 7.10.4.4 7.10.4.5 7.10.4.6 7.10.5 7.10.5.1 7.10.5.2 7.10.5.3 7.10.5.4 7.10.5.5 Using libraries............................................................................................................................325 Library basics............................................................................................................................325 Using the "Libraries" task card..................................................................................................327 Overview of the "Libraries" task card........................................................................................327 Using the element view.............................................................................................................329 Using the library view................................................................................................................330 Overview of the library view......................................................................................................330 Opening and closing the library view.........................................................................................332 Using library management........................................................................................................333 Overview of the library management.........................................................................................333 Opening library management....................................................................................................335 Filtering the display of types......................................................................................................336 Displaying instances in the project............................................................................................336 Displaying cross references of an instance...............................................................................337 Displaying relations to other library objects...............................................................................337 Using global libraries.................................................................................................................338 Creating a global library............................................................................................................338 Compatibility of global libraries..................................................................................................339 Opening a global library............................................................................................................340 Upgrading global libraries..........................................................................................................341 Displaying properties of global libraries.....................................................................................343 WinCC Basic V13.0 System Manual, 02/2014 7 Table of contents 7.10.5.6 Displaying logs of global libraries..............................................................................................343 7.10.5.7 Saving a global library...............................................................................................................344 7.10.5.8 Closing a global library..............................................................................................................345 7.10.5.9 Deleting a global library.............................................................................................................346 7.10.5.10 Archiving and disabling global libraries................................................................................346 7.10.5.11 Using global corporate libraries............................................................................................349 7.10.6 Creating folders in a library.......................................................................................................351 7.10.7 Using master copies..................................................................................................................351 7.10.7.1 Basics on master copies...........................................................................................................351 7.10.7.2 Adding master copies................................................................................................................352 7.10.7.3 Filtering master copies..............................................................................................................353 7.10.7.4 Using master copies..................................................................................................................354 7.10.8 Using types and their versions..................................................................................................354 7.10.8.1 Basics on types.........................................................................................................................354 7.10.8.2 State of type versions................................................................................................................356 7.10.8.3 Displaying a released type version............................................................................................357 7.10.8.4 Displaying properties of a type or version.................................................................................358 7.10.8.5 Working with types in the project library....................................................................................359 7.10.8.6 Working with types in global libraries........................................................................................370 7.10.8.7 Assigning a version...................................................................................................................373 7.10.9 Editing library elements.............................................................................................................375 7.10.10 Updating a library with the contents of another library..............................................................377 7.10.11 Harmonizing names and path structure....................................................................................379 7.10.12 Clean up library.........................................................................................................................380 7.10.13 Comparing library elements......................................................................................................381 8 7.11 7.11.1 Using cross-references.............................................................................................................382 Using cross-references.............................................................................................................382 7.12 7.12.1 7.12.2 Simulating devices....................................................................................................................382 Simulation of devices................................................................................................................382 Starting the simulation...............................................................................................................383 Editing devices and networks...................................................................................................................385 8.1 8.1.1 8.1.1.1 8.1.1.2 8.1.1.3 8.1.1.4 8.1.1.5 8.1.1.6 8.1.1.7 8.1.1.8 8.1.1.9 8.1.1.10 8.1.1.11 8.1.1.12 8.1.1.13 8.1.1.14 8.1.2 8.1.2.1 8.1.2.2 8 Configuring devices and networks............................................................................................385 Hardware and network editor....................................................................................................385 Overview of hardware and network editor.................................................................................385 Network view.............................................................................................................................387 Device view...............................................................................................................................389 Topology view...........................................................................................................................392 Overview of settings for hardware configuration.......................................................................393 Printing hardware and network configurations..........................................................................394 Activating the page break preview for printout..........................................................................396 Changing the print options........................................................................................................396 Inspector window ......................................................................................................................397 Hardware catalog......................................................................................................................398 Enabling product support..........................................................................................................400 Displaying product support for hardware components..............................................................401 Keyboard operation: Navigation in the editor............................................................................402 Keyboard operation: Editing objects..........................................................................................403 Configuring devices...................................................................................................................404 Basics........................................................................................................................................404 Configuring individual devices...................................................................................................413 WinCC Basic V13.0 System Manual, 02/2014 Table of contents 9 8.1.2.3 8.1.3 8.1.3.1 8.1.3.2 8.1.3.3 8.1.3.4 8.1.4 8.1.4.1 8.1.4.2 8.1.4.3 8.1.4.4 8.1.4.5 8.1.4.6 8.1.4.7 8.1.4.8 8.1.4.9 8.1.4.10 8.1.5 8.1.5.1 8.1.5.2 8.1.5.3 8.1.5.4 8.1.5.5 8.1.5.6 8.1.5.7 8.1.5.8 8.1.5.9 8.1.5.10 8.1.5.11 8.1.5.12 8.1.6 8.1.6.1 8.1.6.2 8.1.6.3 8.1.6.4 Comparing devices....................................................................................................................427 Configure networks...................................................................................................................429 Networking devices...................................................................................................................429 Communication via connections................................................................................................451 Displaying and configuring topology..........................................................................................510 Industrial Ethernet Security.......................................................................................................526 Creating configurations.............................................................................................................663 Information about the web server..............................................................................................663 Things you should know about PROFIBUS DP operating modes.............................................664 Configuring automation systems...............................................................................................665 S7-1200 CM/CP........................................................................................................................701 SCALANCE X, W and M...........................................................................................................717 Configuring PROFIBUS DP.......................................................................................................877 Configurations for PROFINET IO..............................................................................................901 Bus coupling with PN/PN coupler..............................................................................................930 Integrating external tools...........................................................................................................931 Loading a configuration.............................................................................................................933 Displaying alarms......................................................................................................................944 Overview of the alarm display...................................................................................................944 Archive view..............................................................................................................................944 Layout of the alarms in the archive view...................................................................................945 Receiving alarms.......................................................................................................................945 Export archive...........................................................................................................................946 Clear archive.............................................................................................................................946 "Active alarms" view..................................................................................................................946 Layout of the alarms in the "Active alarms" view.......................................................................946 Status of the alarms..................................................................................................................947 Acknowledging alarms..............................................................................................................947 Ignoring alarms..........................................................................................................................948 Keyboard commands in the alarm display................................................................................948 Additional information on configurations...................................................................................949 Functional description of S7-1200 CPUs..................................................................................949 Identification systems..............................................................................................................1023 Distributed I/O.........................................................................................................................1029 IPv6 configuration....................................................................................................................1083 8.2 8.2.1 8.2.1.1 8.2.1.2 8.2.1.3 8.2.1.4 8.2.1.5 8.2.1.6 8.2.1.7 8.2.1.8 8.2.2 8.2.2.1 8.2.2.2 8.2.2.3 Device and network diagnostics..............................................................................................1085 Hardware diagnostics..............................................................................................................1085 Overview of hardware diagnostics..........................................................................................1085 Showing non-editable and current values of configurable module properties.........................1095 Showing the current values of dynamic modules properties...................................................1102 Checking a module for defects................................................................................................1106 Changing the properties of a module or the programming device/PC....................................1113 Diagnostics in STOP mode.....................................................................................................1129 Online accesses in the Online and Diagnostics view..............................................................1131 Checking PROFIBUS DP subnets for faults............................................................................1134 Connection diagnostics...........................................................................................................1137 Overview of connection diagnostics........................................................................................1137 Displaying the connection status using icons..........................................................................1138 Detailed connection diagnostics..............................................................................................1139 Programming the PLC............................................................................................................................1143 9.1 Creating the user program......................................................................................................1143 WinCC Basic V13.0 System Manual, 02/2014 9 Table of contents 10 9.1.1 9.1.1.1 9.1.1.2 9.1.1.3 9.1.1.4 9.1.1.5 9.1.1.6 9.1.2 9.1.2.1 9.1.2.2 9.1.2.3 9.1.2.4 9.1.2.5 9.1.2.6 9.1.2.7 9.1.2.8 9.1.2.9 9.1.2.10 9.1.3 9.1.3.1 9.1.3.2 9.1.3.3 9.1.4 9.1.4.1 9.1.4.2 9.1.4.3 9.1.4.4 9.1.4.5 9.1.5 9.1.5.1 9.1.5.2 9.1.5.3 9.1.5.4 9.1.6 9.1.6.1 9.1.6.2 9.1.7 9.1.7.1 9.1.7.2 9.1.7.3 9.1.7.4 9.1.7.5 9.1.7.6 9.1.7.7 Programming basics................................................................................................................1143 Operating system and user program.......................................................................................1143 Blocks in the user program......................................................................................................1144 Block calls...............................................................................................................................1156 Using and addressing operands..............................................................................................1173 Data types...............................................................................................................................1204 Program flow control...............................................................................................................1299 Declaring PLC tags.................................................................................................................1305 Overview of PLC tag tables.....................................................................................................1305 Structure of the PLC tag tables...............................................................................................1306 Rules for PLC tags..................................................................................................................1307 Creating and managing PLC tag tables..................................................................................1311 Declaring PLC tags.................................................................................................................1313 Grouping PLC tags for inputs and outputs in structures..........................................................1316 Declaring global constants......................................................................................................1319 Editing properties....................................................................................................................1321 Monitoring of PLC tags............................................................................................................1324 Editing PLC tag tables.............................................................................................................1324 Creating and managing blocks................................................................................................1331 Creating blocks........................................................................................................................1331 Specifying block properties.....................................................................................................1343 Managing blocks.....................................................................................................................1349 Programming blocks................................................................................................................1354 Program editor.........................................................................................................................1354 Programming code blocks.......................................................................................................1375 Programming data blocks........................................................................................................1523 Programming PLC data types.................................................................................................1551 Using external source files......................................................................................................1560 Comparing PLC programs.......................................................................................................1565 Basic information on comparing PLC programs......................................................................1565 Comparing blocks....................................................................................................................1569 Comparing PLC tags...............................................................................................................1591 Comparing PLC data types.....................................................................................................1592 Compiling and downloading blocks.........................................................................................1594 Compiling blocks.....................................................................................................................1594 Downloading blocks................................................................................................................1599 Protecting blocks.....................................................................................................................1610 Protecting blocks.....................................................................................................................1610 Setting up and removing block copy protection.......................................................................1612 Setting up block know-how protection.....................................................................................1613 Opening know-how protected blocks......................................................................................1614 Printing know-how protected blocks........................................................................................1615 Changing a password..............................................................................................................1616 Removing block know-how protection.....................................................................................1616 9.2 9.2.1 9.2.2 9.2.2.1 9.2.2.2 9.2.2.3 9.2.2.4 9.2.2.5 Displaying program information...............................................................................................1617 Overview of available program information.............................................................................1617 Displaying an assignment list..................................................................................................1618 Introduction to the assignment list...........................................................................................1618 Layout of the assignment list...................................................................................................1619 Symbols in the assignment list................................................................................................1620 Displaying an assignment list..................................................................................................1621 Setting the view options for the assignment list......................................................................1622 WinCC Basic V13.0 System Manual, 02/2014 Table of contents 9.2.2.6 9.2.2.7 9.2.2.8 9.2.2.9 9.2.2.10 9.2.3 9.2.3.1 9.2.3.2 9.2.3.3 9.2.3.4 9.2.3.5 9.2.3.6 9.2.3.7 9.2.4 9.2.4.1 9.2.4.2 9.2.4.3 9.2.4.4 9.2.4.5 9.2.4.6 9.2.4.7 9.2.5 9.2.5.1 9.2.5.2 9.2.5.3 9.2.5.4 Filter options in the assignment list.........................................................................................1623 Defining filters for assignment list............................................................................................1623 Filtering an assignment list......................................................................................................1624 Defining retentive memory areas for bit memories..................................................................1625 Enabling the display of retentive bit memories........................................................................1626 Displaying the call structure....................................................................................................1626 Introduction to the call structure..............................................................................................1626 Symbols in the call structure...................................................................................................1628 Layout of the call structure......................................................................................................1629 Displaying the call structure....................................................................................................1630 Setting the view options for the call structure..........................................................................1631 Introducing the consistency check in the call structure...........................................................1631 Checking block consistency in the call structure.....................................................................1632 Displaying the dependency structure......................................................................................1633 Introduction to the dependency structure................................................................................1633 Layout of the dependency structure........................................................................................1634 Symbols in the dependency structure.....................................................................................1635 Displaying the dependency structure......................................................................................1635 Setting the view options for the dependency structure............................................................1636 Introducing the consistency check in the dependency structure.............................................1637 Checking block consistency in the dependency structure.......................................................1637 Displaying CPU resources......................................................................................................1638 Introducing resources..............................................................................................................1638 Layout of the "Resources" tab.................................................................................................1640 Displaying resources...............................................................................................................1641 Selecting the maximum load memory available......................................................................1642 9.3 9.3.1 9.3.2 9.3.3 9.3.4 Displaying cross-references....................................................................................................1642 General information about cross references...........................................................................1642 Structure of the cross-reference list........................................................................................1643 Displaying the cross-reference list..........................................................................................1644 Displaying cross-references in the Inspector window.............................................................1646 9.4 9.4.1 9.4.2 9.4.2.1 9.4.2.2 9.4.2.3 9.4.2.4 9.4.2.5 9.4.2.6 9.4.3 9.4.3.1 9.4.3.2 9.4.3.3 9.4.3.4 9.4.3.5 9.4.3.6 9.4.3.7 9.4.3.8 9.4.4 9.4.4.1 Testing the user program........................................................................................................1647 Basics of testing the user program..........................................................................................1647 Testing with program status....................................................................................................1648 Introduction to testing with program status..............................................................................1648 Switching test with program status on/off................................................................................1649 Editing blocks during the program test....................................................................................1650 Modifying tags in the program status......................................................................................1651 Switching display formats in the program status.....................................................................1652 Examples of program status display.......................................................................................1652 Testing with the watch table....................................................................................................1655 Introduction to testing with the watch table.............................................................................1655 Layout of the watch table........................................................................................................1656 Basic mode and expanded mode in the watch table...............................................................1657 Icons in the watch table...........................................................................................................1658 Creating and editing watch tables...........................................................................................1659 Entering tags in the watch table..............................................................................................1661 Monitoring tags in the watch table...........................................................................................1669 Modifying tags in the watch table............................................................................................1674 Testing with the force table.....................................................................................................1682 Introduction for testing with the force table..............................................................................1682 WinCC Basic V13.0 System Manual, 02/2014 11 Table of contents 12 9.4.4.2 9.4.4.3 9.4.4.4 9.4.4.5 9.4.4.6 9.4.4.7 9.4.4.8 9.4.4.9 9.4.4.10 Safety precautions when forcing tags.....................................................................................1684 Layout of the force table..........................................................................................................1684 Basic mode and expanded mode in the force table................................................................1685 Icons in the force table............................................................................................................1686 Open and edit force table........................................................................................................1687 Entering tags in the force table................................................................................................1688 Monitoring tags in the force table............................................................................................1695 Forcing tags in the force table.................................................................................................1699 Stop forcing tags.....................................................................................................................1706 9.5 9.5.1 9.5.1.1 9.5.1.2 9.5.1.3 9.5.1.4 9.5.1.5 9.5.1.6 9.5.1.7 Using Team Engineering.........................................................................................................1708 Exchanging data with Inter Project Engineering (IPE)............................................................1708 Basics of Inter Project Engineering (IPE)................................................................................1708 Requirements for Inter Project Engineering (IPE)...................................................................1710 Procedure for working with Inter Project Engineering (IPE)....................................................1711 Creating device proxy data......................................................................................................1713 Opening device proxy data......................................................................................................1714 Exchange of controller data via IPE file...................................................................................1714 Exchange of controller data via project file..............................................................................1715 9.6 9.6.1 9.6.1.1 9.6.1.2 9.6.1.3 9.6.1.4 9.6.2 9.6.2.1 9.6.2.2 9.6.2.3 9.6.2.4 9.6.3 9.6.3.1 9.6.3.2 9.6.3.3 Programming examples..........................................................................................................1716 LAD programming examples...................................................................................................1716 Example of controlling a conveyor belt ...................................................................................1716 Example of detecting the direction of a conveyor belt.............................................................1718 Example of detecting the fill level of a storage area ...............................................................1719 Example of controlling room temperature...............................................................................1722 FBD programming examples...................................................................................................1724 Example of controlling a conveyor belt ...................................................................................1724 Example of detecting the direction of a conveyor belt.............................................................1725 Example of detecting the fill level of a storage area ...............................................................1726 Example of controlling room temperature...............................................................................1729 SCL programming examples...................................................................................................1731 Example: Bit logic instructions.................................................................................................1731 Example of detecting the direction of a conveyor belt.............................................................1733 Example of detecting the fill level of a storage area ...............................................................1734 9.7 9.7.1 9.7.1.1 9.7.1.2 9.7.2 9.7.2.1 9.7.2.2 9.7.2.3 9.7.3 9.7.3.1 9.7.3.2 9.7.3.3 9.7.3.4 9.7.3.5 9.7.3.6 9.7.3.7 9.7.3.8 9.7.3.9 References..............................................................................................................................1736 General parameters of the instructions...................................................................................1736 Meaning of the parameters REQ, RET_VAL and BUSY with asynchronous instructions.......1736 Evaluating errors with output parameter RET_VAL.................................................................1738 Basic instructions....................................................................................................................1742 LAD.........................................................................................................................................1742 FBD.........................................................................................................................................2015 SCL.........................................................................................................................................2300 Extended instructions..............................................................................................................2506 Date and time-of-day...............................................................................................................2506 String + Char...........................................................................................................................2521 Process image.........................................................................................................................2551 Distributed I/O.........................................................................................................................2558 PROFIenergy..........................................................................................................................2629 Module parameter assignment................................................................................................2682 Interrupts.................................................................................................................................2692 Alarms.....................................................................................................................................2722 Diagnostics..............................................................................................................................2729 WinCC Basic V13.0 System Manual, 02/2014 Table of contents 9.7.3.10 9.7.3.11 9.7.3.12 9.7.3.13 9.7.4 9.7.4.1 9.7.4.2 9.7.4.3 9.7.5 9.7.5.1 9.7.5.2 9.7.5.3 9.7.5.4 9.7.5.5 10 Pulse.......................................................................................................................................2764 Recipes and data logging........................................................................................................2766 Data block functions................................................................................................................2796 Addressing..............................................................................................................................2805 Technology..............................................................................................................................2820 S7-1200 Motion Control..........................................................................................................2820 High-speed counters...............................................................................................................2882 PID Control..............................................................................................................................2885 Communication.......................................................................................................................2992 Communications processor.....................................................................................................2992 S7 communication...................................................................................................................3074 Open User Communication.....................................................................................................3091 Web server..............................................................................................................................3172 TeleService.............................................................................................................................3174 Visualize processes................................................................................................................................3183 10.1 Creating screens.....................................................................................................................3183 10.1.1 Basics......................................................................................................................................3183 10.1.1.1 Screen basics .........................................................................................................................3183 10.1.1.2 Device-specific functional scope of screens............................................................................3184 10.1.1.3 Basics......................................................................................................................................3186 10.1.1.4 Working with screens..............................................................................................................3189 10.1.1.5 Working with Templates..........................................................................................................3192 10.1.1.6 Working with styles..................................................................................................................3198 10.1.2 Working with objects...............................................................................................................3200 10.1.2.1 Overview of objects.................................................................................................................3200 10.1.2.2 Options for Editing Objects......................................................................................................3203 10.1.2.3 Inserting an object...................................................................................................................3204 10.1.2.4 Deleting an Object ..................................................................................................................3206 10.1.2.5 Positioning an object...............................................................................................................3207 10.1.2.6 Resizing an object...................................................................................................................3208 10.1.2.7 Selecting multiple objects........................................................................................................3210 10.1.2.8 Aligning objects.......................................................................................................................3212 10.1.2.9 Moving an object forward or backward....................................................................................3213 10.1.2.10 Show objects outside the screen area...............................................................................3214 10.1.2.11 Rotating objects.................................................................................................................3215 10.1.2.12 Flipping objects..................................................................................................................3217 10.1.2.13 Designing an object............................................................................................................3217 10.1.2.14 Designing the fill pattern.....................................................................................................3218 10.1.2.15 Formatting graphics in an object........................................................................................3221 10.1.2.16 Formatting text in an object................................................................................................3222 10.1.2.17 Designing table-based objects...........................................................................................3223 10.1.2.18 Designing a border.............................................................................................................3224 10.1.2.19 Defining color gradients.....................................................................................................3226 10.1.2.20 Applying predefined styles.................................................................................................3227 10.1.2.21 Inserting multiple objects of the same type (stamping tool)...............................................3228 10.1.2.22 Repositioning and resizing multiple objects.......................................................................3230 10.1.2.23 External graphics...............................................................................................................3230 10.1.2.24 Managing external graphics...............................................................................................3231 10.1.2.25 Storing an external image in the graphics library...............................................................3233 10.1.2.26 Working with object groups................................................................................................3235 10.1.2.27 Configuring the keyboard access.......................................................................................3242 WinCC Basic V13.0 System Manual, 02/2014 13 Table of contents 10.1.2.28 Examples...........................................................................................................................3244 10.1.3 Working with text lists and graphics lists.................................................................................3248 10.1.3.1 Working with text lists..............................................................................................................3248 10.1.3.2 Working with graphics lists......................................................................................................3255 10.1.4 Dynamizing screens................................................................................................................3264 10.1.4.1 Basics on dynamization...........................................................................................................3264 10.1.4.2 Dynamization in the inspector window....................................................................................3265 10.1.4.3 Dynamization with animations.................................................................................................3267 10.1.4.4 Dynamize with system functions.............................................................................................3276 10.1.5 Working with function keys......................................................................................................3278 10.1.5.1 Working with function keys .....................................................................................................3278 10.1.5.2 Assigning function keys globally..............................................................................................3280 10.1.5.3 Local assignment of function keys..........................................................................................3282 10.1.5.4 Assigning a function key to a function.....................................................................................3283 10.1.5.5 Assigning operator authorization for a function key................................................................3284 10.1.5.6 Assigning a function key to a graphic......................................................................................3286 10.1.5.7 Configuring LED tags..............................................................................................................3288 10.1.5.8 Example: Using function keys for screen navigation...............................................................3290 10.1.6 Working with layers.................................................................................................................3291 10.1.6.1 Basics on working with layers.................................................................................................3291 10.1.6.2 Moving objects between layers...............................................................................................3292 10.1.6.3 Setting the active layer............................................................................................................3293 10.1.6.4 Show and hide layers..............................................................................................................3294 10.1.6.5 Renaming layers.....................................................................................................................3295 10.1.7 Display and operating objects.................................................................................................3297 10.1.7.1 Device-Specific Nature of the Objects.....................................................................................3297 10.1.7.2 Objects....................................................................................................................................3298 10.1.8 Configuring screen navigation.................................................................................................3327 10.1.8.1 Basics for screen navigation...................................................................................................3327 10.1.8.2 Assign button with screen change...........................................................................................3328 10.1.8.3 Assign screen change to function key.....................................................................................3329 10.2 10.2.1 10.2.1.1 10.2.1.2 10.2.1.3 10.2.1.4 10.2.1.5 10.2.2 10.2.2.1 10.2.2.2 10.2.2.3 10.2.3 10.2.3.1 10.2.3.2 10.2.3.3 10.2.4 10.2.4.1 10.2.5 10.2.5.1 10.2.5.2 14 Working with Tags...................................................................................................................3330 Basics......................................................................................................................................3330 Basics of tags..........................................................................................................................3330 Overview of HMI tag tables.....................................................................................................3331 External tags...........................................................................................................................3332 Addressing external tags.........................................................................................................3334 Internal tags.............................................................................................................................3336 Working with tags....................................................................................................................3337 Creating tags...........................................................................................................................3337 Editing tags..............................................................................................................................3341 Configuring tags......................................................................................................................3347 Working with arrays.................................................................................................................3364 Basics on arrays......................................................................................................................3364 Creating array tags..................................................................................................................3366 Examples of arrays..................................................................................................................3367 Working with cycles.................................................................................................................3367 Cycle basics............................................................................................................................3367 Displaying tags........................................................................................................................3368 Outputting tag values in screens.............................................................................................3368 Configuring trend displays for values from the PLC................................................................3369 WinCC Basic V13.0 System Manual, 02/2014 Table of contents 10.3 10.3.1 10.3.1.1 10.3.1.2 10.3.1.3 10.3.1.4 10.3.1.5 10.3.1.6 10.3.1.7 10.3.2 10.3.2.1 10.3.2.2 10.3.2.3 10.3.2.4 10.3.3 10.3.3.1 10.3.3.2 10.3.3.3 10.3.3.4 10.3.4 10.3.4.1 10.3.4.2 10.3.5 10.3.5.1 10.3.5.2 10.3.5.3 Working with alarms................................................................................................................3370 Basics......................................................................................................................................3370 Alarm system in WinCC..........................................................................................................3370 Alarm types.............................................................................................................................3371 Alarm states ...........................................................................................................................3373 Alarm classes..........................................................................................................................3375 Acknowledgment.....................................................................................................................3376 Alarm groups...........................................................................................................................3378 Alarm number..........................................................................................................................3379 Working with alarms................................................................................................................3379 Alarm components and properties..........................................................................................3379 Configuring alarms..................................................................................................................3381 Configuring alarm output.........................................................................................................3393 Acknowledging alarms............................................................................................................3399 Operating alarms in Runtime...................................................................................................3402 Alarms in Runtime...................................................................................................................3402 Simple alarm view, simple alarm window in runtime ..............................................................3403 Alarm indicator in Runtime......................................................................................................3405 Acknowledging alarms............................................................................................................3406 Reference................................................................................................................................3407 System functions for alarms....................................................................................................3407 System events.........................................................................................................................3407 Configuring system diagnostics...............................................................................................3429 System diagnostics basics......................................................................................................3429 System diagnostics views.......................................................................................................3430 Configuring the system diagnostic view..................................................................................3432 10.4 10.4.1 10.4.1.1 10.4.1.2 10.4.1.3 10.4.1.4 10.4.1.5 10.4.1.6 10.4.2 10.4.2.1 10.4.3 10.4.3.1 10.4.3.2 10.4.4 10.4.4.1 10.4.4.2 10.4.4.3 10.4.5 10.4.5.1 10.4.6 10.4.6.1 Working with recipes...............................................................................................................3433 Basics......................................................................................................................................3433 Definition and applications......................................................................................................3433 Examples for using recipes.....................................................................................................3434 Structure of recipes.................................................................................................................3434 Displaying recipes...................................................................................................................3436 Flow of data for recipes...........................................................................................................3436 Synchronization of recipe data records with the PLC..............................................................3437 Elements and basic settings....................................................................................................3438 "Recipes" editor.......................................................................................................................3438 Displaying and editing recipes in Runtime..............................................................................3441 Simple recipe view..................................................................................................................3441 Behavior of the recipe view in Runtime...................................................................................3442 Configuring recipes.................................................................................................................3443 General configuration procedure ............................................................................................3443 Creating and Editing Recipes..................................................................................................3444 Configuring the display of recipes...........................................................................................3452 Using recipes in Runtime........................................................................................................3455 Using the simple recipe view...................................................................................................3455 Example..................................................................................................................................3461 Example of creating a recipe...................................................................................................3461 10.5 10.5.1 10.5.2 10.5.3 Configuring user administration...............................................................................................3463 Field of application of the user administration.........................................................................3463 Form of the user administration...............................................................................................3463 Basics......................................................................................................................................3464 WinCC Basic V13.0 System Manual, 02/2014 15 Table of contents 16 10.5.3.1 10.5.3.2 10.5.3.3 10.5.3.4 10.5.3.5 10.5.4 10.5.4.1 10.5.4.2 10.5.4.3 10.5.4.4 10.5.5 10.5.5.1 10.5.5.2 10.5.6 10.5.6.1 10.5.6.2 10.5.6.3 Users.......................................................................................................................................3464 Users work area......................................................................................................................3465 User groups.............................................................................................................................3466 User groups work area............................................................................................................3466 Settings for the user administration.........................................................................................3467 Setting up the user administration...........................................................................................3469 Basics on user administration.................................................................................................3469 Administering users for Runtime.............................................................................................3470 Managing users in Runtime.....................................................................................................3477 Configuring access protection.................................................................................................3485 Reference................................................................................................................................3486 Objects with access protection................................................................................................3486 Default user groups and authorizations...................................................................................3487 Examples.................................................................................................................................3487 Example: Configuring a button with logon dialog box.............................................................3487 Example: Logging the logon and logoff events.......................................................................3488 Example of user management................................................................................................3489 10.6 10.6.1 10.6.1.1 10.6.1.2 10.6.2 10.6.2.1 10.6.2.2 10.6.2.3 10.6.2.4 10.6.2.5 10.6.3 10.6.3.1 10.6.4 10.6.4.1 10.6.4.2 Working with system functions................................................................................................3496 Basics......................................................................................................................................3496 System functions.....................................................................................................................3496 Use of system functions .........................................................................................................3498 Working with function lists.......................................................................................................3498 Basic of the functions list.........................................................................................................3498 Properties of a function list......................................................................................................3499 Configuring a function list........................................................................................................3500 Editing a function list...............................................................................................................3502 Executing a function list in Runtime .......................................................................................3503 Example..................................................................................................................................3503 Changing the operating mode on the HMI device with the current display.............................3503 Reference................................................................................................................................3506 Function list.............................................................................................................................3506 Events.....................................................................................................................................3570 10.7 10.7.1 10.7.2 10.7.3 10.7.3.1 10.7.3.2 10.7.3.3 10.7.3.4 10.7.4 10.7.4.1 Planning tasks.........................................................................................................................3586 Field of application of the Scheduler.......................................................................................3586 Working with tasks and triggers..............................................................................................3588 Basics......................................................................................................................................3589 Work area of the "Scheduler" editor........................................................................................3589 Function list.............................................................................................................................3590 Triggers...................................................................................................................................3590 Planning tasks with event triggers...........................................................................................3591 Examples.................................................................................................................................3593 Example: Update user following change of user.....................................................................3593 10.8 10.8.1 10.8.1.1 10.8.1.2 10.8.1.3 10.8.1.4 10.8.1.5 10.8.2 10.8.2.1 Communicating with PLCs......................................................................................................3595 Basics of communication.........................................................................................................3595 Communication between devices............................................................................................3595 Devices and networks in the automation system....................................................................3596 Data exchange using tags.......................................................................................................3601 Data exchange using area pointers.........................................................................................3602 Communication drivers............................................................................................................3602 Editors for communication.......................................................................................................3603 "Devices & networks" editor....................................................................................................3603 WinCC Basic V13.0 System Manual, 02/2014 Table of contents 10.8.2.2 Network view...........................................................................................................................3604 10.8.2.3 Network data...........................................................................................................................3607 10.8.2.4 Diagnostics of online connections...........................................................................................3609 10.8.2.5 Device view.............................................................................................................................3610 10.8.2.6 Topology view.........................................................................................................................3612 10.8.2.7 Inspector window ....................................................................................................................3614 10.8.2.8 Hardware catalog ...................................................................................................................3616 10.8.2.9 Information on hardware components.....................................................................................3618 10.8.3 Networks and connections......................................................................................................3619 10.8.3.1 SIMATIC communication networks.........................................................................................3619 10.8.3.2 Configuring networks and connections...................................................................................3624 10.8.4 Data exchange........................................................................................................................3632 10.8.4.1 Data exchange using tags.......................................................................................................3632 10.8.4.2 Data exchange using area pointers.........................................................................................3639 10.8.5 Device dependency.................................................................................................................3645 10.8.5.1 Basic Panel.............................................................................................................................3645 10.8.6 Communicating with SIMATIC S7 1500..................................................................................3651 10.8.6.1 Communication with SIMATIC S7 1500..................................................................................3651 10.8.6.2 Communication via PROFINET...............................................................................................3652 10.8.6.3 Communication via PROFIBUS..............................................................................................3665 10.8.6.4 Data exchange........................................................................................................................3674 10.8.6.5 Performance features of communication.................................................................................3692 10.8.6.6 Configuring connections in the "Connections" editor..............................................................3694 10.8.7 Communicating with SIMATIC S7 1200..................................................................................3699 10.8.7.1 Communication with SIMATIC S7 1200..................................................................................3699 10.8.7.2 Communication via PROFINET...............................................................................................3700 10.8.7.3 Communication via PROFIBUS..............................................................................................3714 10.8.7.4 Data exchange .......................................................................................................................3723 10.8.7.5 Performance features of communication.................................................................................3742 10.8.7.6 Creating connections in the "Connections" editor...................................................................3744 10.8.8 Communicating with SIMATIC S7 300/400.............................................................................3753 10.8.8.1 Communication with SIMATIC S7 300/400.............................................................................3753 10.8.8.2 Communication via PROFINET...............................................................................................3754 10.8.8.3 Communication via PROFIBUS..............................................................................................3767 10.8.8.4 Communication via MPI..........................................................................................................3775 10.8.8.5 Data exchange........................................................................................................................3783 10.8.8.6 Performance features of communication.................................................................................3800 10.8.8.7 Creating connections in the "Connections" editor...................................................................3801 10.8.9 Communicating with SIMATIC S7 200....................................................................................3813 10.8.9.1 Communication with SIMATIC S7 200....................................................................................3813 10.8.9.2 Creating a connection to SIMATIC S7 200.............................................................................3813 10.8.9.3 Parameters for the connection................................................................................................3815 10.8.9.4 Data exchange .......................................................................................................................3822 10.8.9.5 Performance features of communication.................................................................................3840 10.8.10 Communicating with SIMATIC LOGO!....................................................................................3840 10.8.10.1 Communication with SIMATIC LOGO!...............................................................................3840 10.8.10.2 Creating a connection to SIMATIC LOGO!........................................................................3841 10.8.10.3 Connection parameters......................................................................................................3843 10.8.10.4 Data exchange...................................................................................................................3847 10.8.10.5 Performance features of communication...........................................................................3851 10.8.11 Communication with other PLCs.............................................................................................3852 10.8.11.1 Communication with other PLCs........................................................................................3852 WinCC Basic V13.0 System Manual, 02/2014 17 Table of contents 10.8.11.2 10.8.11.3 10.8.11.4 10.9 10.9.1 10.9.2 10.9.2.1 10.9.2.2 10.9.2.3 10.9.2.4 10.9.2.5 10.9.2.6 10.9.2.7 10.9.3 10.9.3.1 10.9.3.2 10.9.3.3 10.9.3.4 10.9.4 10.9.4.1 10.9.4.2 10.9.4.3 10.9.4.4 10.9.4.5 10.9.4.6 10.9.5 10.9.5.1 10.9.5.2 10.9.5.3 10.9.5.4 10.9.5.5 10.9.6 10.9.6.1 10.9.6.2 10.9.6.3 10.9.6.4 10.9.6.5 10.9.6.6 10.9.6.7 10.9.6.8 10.9.7 10.9.7.1 10.9.7.2 10.9.7.3 10.9.8 10.9.8.1 10.9.8.2 10.9.8.3 10.9.9 10.9.9.1 10.9.9.2 10.9.9.3 18 Distinctive features when configuring.................................................................................3853 Communication drivers......................................................................................................3853 Data exchange using area pointers...................................................................................3967 Using global functions.............................................................................................................3982 HMI device wizard basics........................................................................................................3982 Working with libraries..............................................................................................................3983 Basics on libraries...................................................................................................................3983 Overview of the library view....................................................................................................3985 Copy templates and types.......................................................................................................3987 Libraries in WinCC..................................................................................................................3988 Managing libraries...................................................................................................................3989 Managing objects in a library...................................................................................................3997 Using types and their versions................................................................................................4001 Using controller data from other projects................................................................................4005 Basics of Inter Project Engineering (IPE)................................................................................4005 Controller data.........................................................................................................................4006 Initializing a device proxy via an IPE file.................................................................................4006 Initializing a device proxy via a project file..............................................................................4012 Importing and exporting project data.......................................................................................4017 Importing and exporting project data.......................................................................................4017 Importing and exporting recipes..............................................................................................4018 Importing and exporting alarms...............................................................................................4022 Importing and exporting tags...................................................................................................4029 Importing and exporting text lists.............................................................................................4034 Importing and exporting project texts......................................................................................4039 Using cross-references...........................................................................................................4042 General information about cross references...........................................................................4042 Displaying the cross-reference list..........................................................................................4042 Structure of the cross-reference list........................................................................................4043 Displaying cross-references in the Inspector window.............................................................4044 Rewiring tags in the screens...................................................................................................4045 Managing languages...............................................................................................................4048 Languages in WinCC..............................................................................................................4048 Language settings in the operating system.............................................................................4049 Operating system settings for Asian languages......................................................................4050 Setting project languages........................................................................................................4051 Creating one project in multiple languages.............................................................................4054 Using language-specific graphics............................................................................................4062 Languages in runtime..............................................................................................................4066 Example of multilingual configuration......................................................................................4073 Replacing devices...................................................................................................................4076 Basics......................................................................................................................................4076 Device-specific functions.........................................................................................................4077 Adjusting screens to the new device.......................................................................................4080 Copying between devices and editors.....................................................................................4085 Basics......................................................................................................................................4085 Copying and pasting................................................................................................................4087 Copying between different RT and ES versions......................................................................4090 Using WinCC version compatibility.........................................................................................4092 Basics on version compatibility...............................................................................................4092 Editing projects of a previous WinCC version.........................................................................4094 Upgrading projects..................................................................................................................4095 WinCC Basic V13.0 System Manual, 02/2014 Table of contents 10.9.9.4 Upgrading a global library.......................................................................................................4096 10.9.9.5 Changing between device versions.........................................................................................4097 10.9.9.6 Changing the device version...................................................................................................4098 10.9.10 Viewing memory card data......................................................................................................4099 10.9.10.1 Basics.................................................................................................................................4099 10.9.10.2 Working with backups........................................................................................................4100 10.10 Compiling and loading.............................................................................................................4102 10.10.1 Compiling and loading projects...............................................................................................4102 10.10.1.1 Overview of compiling and loading projects.......................................................................4102 10.10.1.2 Compiling a project............................................................................................................4104 10.10.1.3 Loading projects.................................................................................................................4105 10.10.1.4 Runtime start......................................................................................................................4108 10.10.2 Simulating projects..................................................................................................................4109 10.10.2.1 Simulation basics...............................................................................................................4109 10.10.2.2 Simulating a project............................................................................................................4110 10.10.2.3 Working with the tag simulator...........................................................................................4112 10.10.2.4 Simulation restrictions........................................................................................................4114 10.10.3 Servicing the HMI device.........................................................................................................4114 10.10.3.1 Overview of HMI device maintenance (Basic Panels).......................................................4114 10.10.3.2 ProSave.............................................................................................................................4115 10.10.3.3 Backup of HMI data............................................................................................................4116 10.10.3.4 Backing up and restoring data of the HMI device..............................................................4117 10.10.3.5 Updating the operating system..........................................................................................4118 10.10.3.6 Updating the HMI device operating system.......................................................................4119 10.10.4 Reference................................................................................................................................4121 10.10.4.1 Error messages during loading of projects.........................................................................4121 10.10.4.2 Adapting the project for another HMI device......................................................................4122 10.10.4.3 Establishing a connection to the HMI device.....................................................................4123 10.11 Operating in Runtime..............................................................................................................4124 10.11.1 Basics......................................................................................................................................4124 10.11.1.1 Overview............................................................................................................................4124 10.11.1.2 Tags in Runtime.................................................................................................................4125 10.11.1.3 System functions in Runtime..............................................................................................4126 10.11.2 Commissioning projects..........................................................................................................4126 10.11.2.1 Settings in the Runtime software ......................................................................................4126 10.11.2.2 Loading projects.................................................................................................................4128 10.11.2.3 Starting Runtime on the Engineering Station.....................................................................4129 10.11.2.4 Starting Runtime on the HMI device..................................................................................4129 10.11.2.5 Testing a project.................................................................................................................4130 10.11.2.6 Closing a project................................................................................................................4131 10.11.2.7 Backing up and restoring data of the HMI device..............................................................4132 10.11.3 Languages in runtime..............................................................................................................4133 10.11.3.1 Languages in runtime.........................................................................................................4133 10.11.3.2 Setting a runtime language................................................................................................4133 10.11.3.3 Setting the font for a runtime language..............................................................................4134 10.11.3.4 Configuring language switching.........................................................................................4135 10.11.3.5 Specific features of Asian and Eastern languages in runtime............................................4136 10.11.4 Operating projects...................................................................................................................4137 10.11.4.1 Basics.................................................................................................................................4137 10.11.4.2 Operating objects...............................................................................................................4144 10.11.4.3 Project security...................................................................................................................4157 WinCC Basic V13.0 System Manual, 02/2014 19 Table of contents 10.11.4.4 10.11.4.5 Operating alarms................................................................................................................4164 Operating recipes...............................................................................................................4171 10.12 Performance features..............................................................................................................4181 10.12.1 Engineering system.................................................................................................................4181 10.12.2 Basic Panel.............................................................................................................................4183 10.12.3 Basic Panel 2nd Generation....................................................................................................4187 10.12.4 General technical data............................................................................................................4190 10.12.4.1 Permitted characters..........................................................................................................4190 10.12.4.2 Recommended printers......................................................................................................4191 10.12.4.3 Memory requirements of recipes for Basic Panels.............................................................4192 10.13 10.13.1 10.13.2 10.13.3 11 Migrating to WinCC in the TIA Portal......................................................................................4193 Overview of migration to WinCC V12......................................................................................4193 Libraries...................................................................................................................................4193 Screens and templates............................................................................................................4195 Using technology functions.....................................................................................................................4199 11.1 PID control...............................................................................................................................4199 11.1.1 Principles for control................................................................................................................4199 11.1.1.1 Controlled system and actuators.............................................................................................4199 11.1.1.2 Controlled systems..................................................................................................................4200 11.1.1.3 Characteristic values of the control section.............................................................................4202 11.1.1.4 Pulse controller........................................................................................................................4204 11.1.1.5 Response to setpoint changes and disturbances....................................................................4208 11.1.1.6 Control Response at Different Feedback Structures...............................................................4209 11.1.1.7 Selection of the controller structure for specified controlled systems......................................4217 11.1.1.8 PID parameter settings............................................................................................................4218 11.1.2 Configuring a software controller.............................................................................................4218 11.1.2.1 Overview of software controller...............................................................................................4218 11.1.2.2 Steps for the configuration of a software controller.................................................................4220 11.1.2.3 Add technology objects...........................................................................................................4220 11.1.2.4 Configure technology objects..................................................................................................4221 11.1.2.5 Call instruction in the user program.........................................................................................4222 11.1.2.6 Downloading technology objects to device.............................................................................4223 11.1.2.7 Commissioning software controller.........................................................................................4224 11.1.2.8 Save optimized PID parameter in the project..........................................................................4225 11.1.2.9 Comparing values...................................................................................................................4225 11.1.2.10 Parameter view..................................................................................................................4228 11.1.2.11 Display instance DB of a technology object.......................................................................4245 11.1.3 Using PID_Compact................................................................................................................4245 11.1.3.1 Technology object PID_Compact............................................................................................4245 11.1.3.2 PID_Compact V2.....................................................................................................................4246 11.1.3.3 PID_Compact V1.....................................................................................................................4262 11.1.4 Using PID_3Step.....................................................................................................................4276 11.1.4.1 Technology object PID_3Step.................................................................................................4276 11.1.4.2 PID_3Step V2..........................................................................................................................4277 11.1.4.3 PID_3Step V1..........................................................................................................................4294 11.2 11.2.1 11.2.1.1 11.2.1.2 11.2.2 20 Using S7-1200 Motion Control................................................................................................4309 Introduction..............................................................................................................................4309 Motion functionality of the CPU S7-1200................................................................................4309 Hardware components for motion control...............................................................................4310 Basics for working with S7-1200 Motion Control.....................................................................4312 WinCC Basic V13.0 System Manual, 02/2014 Table of contents 11.2.2.1 CPU outputs relevant for motion control (technology version V4)...........................................4312 11.2.2.2 How the pulse interface works................................................................................................4314 11.2.2.3 Relationship between the signal type and the direction of travel............................................4315 11.2.2.4 Hardware and software limit switches.....................................................................................4319 11.2.2.5 Jerk limit..................................................................................................................................4320 11.2.2.6 Homing....................................................................................................................................4321 11.2.3 Guidelines on use of motion control........................................................................................4322 11.2.4 Using versions.........................................................................................................................4322 11.2.4.1 Overview of versions...............................................................................................................4322 11.2.4.2 Changing a technology version...............................................................................................4324 11.2.4.3 Compatibility list of tags...........................................................................................................4325 11.2.4.4 Status of limit switch................................................................................................................4328 11.2.5 Positioning axis technology object..........................................................................................4330 11.2.5.1 Integration of the positioning axis technology object...............................................................4330 11.2.5.2 Tools of the positioning axis technology object.......................................................................4333 11.2.5.3 Adding a positioning axis technology object............................................................................4335 11.2.5.4 Configuring the positioning axis technology object.................................................................4335 11.2.6 Technology object command table..........................................................................................4359 11.2.6.1 Use of the command table technology object.........................................................................4359 11.2.6.2 Command table technology object tools.................................................................................4359 11.2.6.3 Adding the technological object command table.....................................................................4360 11.2.6.4 Configuring the command table technology object.................................................................4361 11.2.7 Download to CPU....................................................................................................................4378 11.2.8 Commissioning the axis - Axis control panel...........................................................................4379 11.2.9 Parameter view.......................................................................................................................4383 11.2.9.1 Introduction to the parameter view..........................................................................................4383 11.2.9.2 Structure of the parameter view..............................................................................................4385 11.2.9.3 Opening the parameter view...................................................................................................4388 11.2.9.4 Default setting of the parameter view......................................................................................4388 11.2.9.5 Working with the parameter view............................................................................................4390 11.2.10 Programming...........................................................................................................................4400 11.2.10.1 Overview of the Motion Control statements.......................................................................4400 11.2.10.2 Creating a user program....................................................................................................4401 11.2.10.3 Programming notes............................................................................................................4404 11.2.10.4 Behavior of the Motion Control commands after POWER OFF and restart.......................4406 11.2.10.5 Monitoring active commands.............................................................................................4406 11.2.10.6 Error displays of the Motion Control statements................................................................4417 11.2.11 Axis - Diagnostics....................................................................................................................4418 11.2.11.1 Status and error bits (technology objects as of V4) ..........................................................4418 11.2.11.2 Motion status......................................................................................................................4421 11.2.11.3 Dynamics settings..............................................................................................................4421 11.2.12 Appendix.................................................................................................................................4422 11.2.12.1 Using multiple axes with the same PTO............................................................................4422 11.2.12.2 Using multiple drives with the same PTO..........................................................................4426 11.2.12.3 Tracking jobs from higher priority classes (execution levels).............................................4427 11.2.12.4 Special cases for use of software limit switches................................................................4429 11.2.12.5 Reducing velocity for a short positioning duration..............................................................4436 11.2.12.6 Dynamic adjustment of start/stop velocity..........................................................................4436 11.2.12.7 List of ErrorIDs and ErrorInfos (technology objects as of V4)............................................4436 11.2.12.8 Tags of the positioning axis technology object as of V4....................................................4446 11.2.12.9 Tags of the command table technology object as of V4....................................................4465 11.2.12.10 Versions V1...3...................................................................................................................4466 WinCC Basic V13.0 System Manual, 02/2014 21 Table of contents 12 13 Using Team Engineering........................................................................................................................4513 12.1 12.1.1 12.1.2 12.1.3 12.1.4 Shared commissioning of projects..........................................................................................4513 Basics for shared commissioning............................................................................................4513 Requirements for shared commissioning................................................................................4515 Procedure for shared commissioning......................................................................................4516 Rules for shared commissioning.............................................................................................4519 12.2 12.2.1 12.2.2 12.2.3 Exchanging data with Inter Project Engineering (IPE)............................................................4524 Basics of Inter Project Engineering (IPE)................................................................................4524 Requirements for Inter Project Engineering (IPE)...................................................................4526 Procedure for working with Inter Project Engineering (IPE)....................................................4527 Using online and diagnostics functions..................................................................................................4531 13.1 Displaying accessible devices.................................................................................................4531 13.2 Changing the device configuration online...............................................................................4532 13.3 13.3.1 13.3.2 13.3.3 13.3.4 13.3.5 Connecting devices online......................................................................................................4533 General information about online mode..................................................................................4533 View in online mode................................................................................................................4535 Establishing and canceling an online connection....................................................................4536 Connecting online with several devices..................................................................................4538 Disconnecting online connections of multiple devices............................................................4538 13.4 13.4.1 13.4.2 13.4.3 Backing up the software and hardware configuration of a device...........................................4539 Creating a backup of a device.................................................................................................4539 Backing up a device configuration...........................................................................................4540 Restoring the software and hardware configuration of a device.............................................4541 13.5 13.5.1 13.5.2 13.5.3 13.5.4 13.5.5 13.5.6 13.5.6.1 13.5.6.2 13.5.6.3 13.5.6.4 13.5.6.5 13.5.6.6 13.5.6.7 13.5.7 13.5.7.1 13.5.7.2 13.5.7.3 13.5.7.4 13.5.7.5 13.5.7.6 Configuring the PG/PC interface.............................................................................................4542 Online access..........................................................................................................................4542 Basics of assigning parameters for the PG/PC interface........................................................4544 Showing or hiding interfaces...................................................................................................4545 Displaying and modifying interface properties.........................................................................4545 Adding interfaces.....................................................................................................................4546 Setting parameters for the Ethernet interface.........................................................................4547 Setting parameters for the Industrial Ethernet interface..........................................................4547 Displaying operating system parameters................................................................................4548 Connecting the PG/PC interface to a subnet..........................................................................4548 Setting parameters for the Ethernet interface.........................................................................4549 Assigning a temporary IP address..........................................................................................4550 Managing temporary IP addresses.........................................................................................4550 Resetting the TCP/IP configuration.........................................................................................4551 Setting parameters for the MPI and PROFIBUS interfaces....................................................4551 Setting parameters for the MPI and PROFIBUS interfaces....................................................4551 Setting MPI or PROFIBUS interface parameters automatically..............................................4552 Setting parameters for the MPI interface.................................................................................4553 Setting parameters for the PROFIBUS interface.....................................................................4555 Overview of the bus parameters for PROFIBUS.....................................................................4557 Resetting the MPI or PROFIBUS configuration.......................................................................4559 13.6 Using the trace and logic analyzer function.............................................................................4559 Preface....................................................................................................................................4559 Security information.................................................................................................................4560 13.6.1 22 WinCC Basic V13.0 System Manual, 02/2014 Table of contents 13.6.1 13.6.1.1 13.6.1.2 13.6.1.3 13.6.1.4 13.6.2 13.6.2.1 13.6.2.2 13.6.2.3 13.6.3 13.6.3.1 13.6.3.2 13.6.3.3 13.6.3.4 13.6.3.5 13.6.3.6 13.6.4 13.6.4.1 Description..............................................................................................................................4561 Supported hardware................................................................................................................4561 Recording of measured values with the trace function............................................................4561 Trace configuration, recording and measurement...................................................................4562 Data storage............................................................................................................................4563 Software user interface...........................................................................................................4564 Project navigator.....................................................................................................................4566 Working area...........................................................................................................................4566 Device-specific area................................................................................................................4574 Operation.................................................................................................................................4574 Quick start...............................................................................................................................4574 Using the trace function - overview.........................................................................................4579 Calling the trace editor............................................................................................................4580 Trace handling.........................................................................................................................4580 Signal table..............................................................................................................................4584 Curve diagram.........................................................................................................................4585 Devices....................................................................................................................................4586 S7-1200/1500 CPUs...............................................................................................................4586 13.7 13.7.1 13.7.1.1 13.7.1.2 13.7.1.3 13.7.2 13.7.2.1 13.7.2.2 13.7.2.3 13.7.2.4 13.7.3 13.7.3.1 13.7.3.2 13.7.3.3 13.7.3.4 13.7.3.5 13.7.3.6 13.7.4 13.7.4.1 13.7.4.2 13.7.4.3 13.7.4.4 13.7.4.5 13.7.4.6 13.7.5 13.7.5.1 13.7.5.2 13.7.5.3 13.7.5.4 13.7.5.5 13.7.6 13.7.6.1 13.7.6.2 13.7.6.3 Establishing a remote connection with TeleService................................................................4599 Basics of working with TeleService.........................................................................................4599 Introduction to TeleService......................................................................................................4599 TeleService functionality.........................................................................................................4600 Telephone book at TeleService...............................................................................................4601 Working with the phone book..................................................................................................4602 Basics on working with the phone book..................................................................................4602 Structure of the phone book....................................................................................................4602 Symbols in the phone book.....................................................................................................4603 Manage phone book................................................................................................................4604 Remote connections as dial-up connections...........................................................................4610 Basics for establishing a dial-up connection...........................................................................4610 Telephone networks and modems..........................................................................................4611 Access protection for dial-up connections...............................................................................4614 TS adapter MPI.......................................................................................................................4619 TS adapter IE..........................................................................................................................4626 Establishing a dial-up connection to a remote system............................................................4632 Remote VPN connections.......................................................................................................4634 Basics for establishing a VPN connection...............................................................................4634 Basics of CA certificates..........................................................................................................4635 Installing CA certificates for VPN connections........................................................................4637 Deleting CA certificates for VPN connections.........................................................................4640 Establishing a VPN connection to a remote system................................................................4640 TS Adapter IE Advanced.........................................................................................................4642 CPU controlled TeleService remote connections ...................................................................4647 Overview of CPU controlled remote connections....................................................................4647 Establishing a connection from and to remote systens (PG-AS-remote coupling)..................4648 Data exchange between remote systems (AS-AS-remote coupling)......................................4649 Send SMS from a system........................................................................................................4651 Send an email from a system..................................................................................................4652 Notes on troubleshooting........................................................................................................4655 General information on troubleshooting for modem problems................................................4655 Recording a log file for the modem.........................................................................................4655 Dial-up connection to the TS Adapter is not established.........................................................4656 WinCC Basic V13.0 System Manual, 02/2014 23 Table of contents 13.7.6.4 13.7.6.5 13.7.6.6 13.7.6.7 13.7.6.8 14 Dial-up connection from the TS Adapter is not established....................................................4657 Modem connection is interrupted............................................................................................4658 Checklist for troubleshooting the modem................................................................................4659 Modem alarms.........................................................................................................................4659 Possible error messages with VPN connections.....................................................................4660 Hardware documentation.......................................................................................................................4663 14.1 General information on the hardware documentation.............................................................4663 14.2 PLC.........................................................................................................................................4663 14.2.1 SIMATIC S7-1200...................................................................................................................4663 14.2.1.1 CPU.........................................................................................................................................4663 14.2.1.2 Signal boards..........................................................................................................................4667 14.2.1.3 Communication boards...........................................................................................................4668 14.2.1.4 Battery boards.........................................................................................................................4669 14.2.1.5 Digital input modules...............................................................................................................4669 14.2.1.6 Digital output modules.............................................................................................................4670 14.2.1.7 Digital input and digital output modules...................................................................................4671 14.2.1.8 Analog input modules..............................................................................................................4672 14.2.1.9 Analog output modules............................................................................................................4674 14.2.1.10 Analog input and analog output modules...........................................................................4674 14.2.1.11 Communications modules..................................................................................................4675 14.2.1.12 Technology modules..........................................................................................................4677 14.3 Distributed I/O.........................................................................................................................4678 14.3.1 ET 200MP...............................................................................................................................4678 14.3.1.1 Interface modules....................................................................................................................4678 14.3.1.2 Digital input modules...............................................................................................................4678 14.3.1.3 Digital output modules.............................................................................................................4679 14.3.1.4 Digital input and digital output modules...................................................................................4681 14.3.1.5 Analog input modules..............................................................................................................4681 14.3.1.6 Analog output modules............................................................................................................4682 14.3.1.7 Analog input and analog output modules................................................................................4682 14.3.1.8 Communications modules.......................................................................................................4683 14.3.1.9 Power supply module..............................................................................................................4684 14.3.1.10 Technology modules..........................................................................................................4685 14.3.2 ET 200SP................................................................................................................................4686 14.3.2.1 CPU.........................................................................................................................................4686 14.3.2.2 Interface modules....................................................................................................................4686 14.3.2.3 Digital input modules...............................................................................................................4687 14.3.2.4 Digital output modules.............................................................................................................4688 14.3.2.5 Analog input modules..............................................................................................................4690 14.3.2.6 Analog output modules............................................................................................................4691 14.3.2.7 Communication modules.........................................................................................................4692 14.3.2.8 Power modules........................................................................................................................4692 14.3.2.9 Special modules......................................................................................................................4692 14.3.2.10 Technology modules..........................................................................................................4693 Index.......................................................................................................................................................4695 24 WinCC Basic V13.0 System Manual, 02/2014 1 System overview of STEP 7 and WinCC 1.1 Scaling of STEP 7 and WinCC in the TIA Portal Scope of performance of the products The following graphic shows the scope of performance of the individual products of STEP 7 and WinCC: 6,0$7,&67(3 6,0$7,&:LQ&& 3URJUDPPLQJODQJXDJHV /$')%'6&/67/ 6*5$3+ 0DFKLQHOHYHORSHUDWRUFRQWURO DQGPRQLWRULQJ 2SWLRQDOSDFNDJH67(36DIHW\ 6&$'$DSSOLFDWLRQV :LQ$& LQFO)DLOVDIH 6&$'$ 6 LQFO)DLOVDIH 3URIHVVLRQDO $GYDQFHG &RPIRUW %DVLF 6 %DVLF 3URIHVVLRQDO 6 3&VLQJOHXVHUVWDWLRQ &RPIRUW3DQHOVDQG[ ZLWKRXW0LFUR 0RELOH %DVLF3DQHOV &RPPXQLFDWLRQ 352),%86352),1(7$6L,2/LQN(7QHWZRUNWRSRORJ\ 352),VDIHYLD352),%86DQG352),1(7 &RPPRQIXQFWLRQV 6\VWHPGLDJQRVWLFVLPSRUWH[SRUWWR([FHOUHXVHRIHOHPHQWVZLWKKHOSRIOLEUDULHVDQGPXFKPRUH * ** Only with STEP 7 Professional for S7-300/400/WinAC and S7-1500 With installed optional package "STEP 7 Safety Advanced" STEP 7 STEP 7 (TIA Portal) is the engineering software for configuring the SIMATIC S7-1200, S7-1500, S7-300/400 and WinAC controller families. STEP 7 (TIA Portal) is available in two editions, depending on the configurable controller families: STEP 7 Basic for configuring the S7-1200 STEP 7 Professional for configuring S7-1200, S7-1500, S7-300/400 and WinAC WinCC Basic V13.0 System Manual, 02/2014 25 System overview of STEP 7 and WinCC 1.3 Options for WinCC Engineering and Runtime systems 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 four 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 Professional is available in the following editions: WinCC Professional for 512 and 4096 PowerTags as well as "WinCC Professional max. PowerTags". 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, and 64k 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 supplemented with the STEP 7 Safety Advanced option. When using the STEP 7 Safety Advanced option, you can configure failsafe I/O and program safety programs for F-CPUs in LAD and FBD. 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. 26 WinCC Basic V13.0 System Manual, 02/2014 System overview of STEP 7 and WinCC 1.3 Options for WinCC Engineering and Runtime systems 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) WinCC ControlDevelopment (extension by means of customer-specific controls) 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) WinCC ControlDevelopment (extension by means of customer-specific controls) WinCC Basic V13.0 System Manual, 02/2014 27 System overview of STEP 7 and WinCC 1.3 Options for WinCC Engineering and Runtime systems 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. 28 WinCC Basic V13.0 System Manual, 02/2014 2 Readme 2.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. Notes on the information system The following function is already described in the information system, but is not available in TIA Portal V13: Hardware comparison of devices Functions for S7-1200 as of firmware version V4 In the information system for the TIA Portal V13, functions are documented for S7-1200 as of firmware version V4 which are not yet available in the software. The 64-bit data types will be available for an S7-1200 as of firmware version V4. User-defined documentation On the product DVD under "Documents\UserDocumentation", you will find instructions for creating and using user-defined documentation. Display of interfaces via online access If the Ethernet interfaces for online access are not displayed sporadically, install hotfix KB2588507 (for Microsoft Windows) from the Microsoft Support website. Internet link: http://support.microsoft.com/kb/2588507 (http://support.microsoft.com/kb/ 2588507/en-us) Display of Asian characters in the TIA Portal If the Chinese TIA Portal is installed on a different Asian Windows operating system (for example Korean) and texts are not displayed correctly in the TIA Portal, select English as the "Language for non-Unicode programs" in the Windows Control Panel. Instruction "GET_NAME: Read out name of a module" According to the online help, the read name depends on the IO device type. For an HMI Panel, however, it is not the name of the station that is output - as described in the online help - but the name of the interface module. WinCC Basic V13.0 System Manual, 02/2014 29 Readme 2.1 General notes Online operation in hibernate mode We recommend that you do not use the two options "Hibernate" and "Sleep" in online operation; if you do, communication problems could occur. If necessary, adapt the computer's energy options. 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 alarm "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. 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. 30 WinCC Basic V13.0 System Manual, 02/2014 Readme 2.1 General notes Notes on SIMATIC memory cards The SIMATIC memory cards have been formatted and set up by Siemens for use with S7-1200 and S7-1500 modules. This format must not be overwritten; otherwise, the card will no longer be accepted by the modules. Formatting with Windows tools is therefore not permitted. Behavior in case of open force job Note that an active force job is retained even after you have loaded a new project to the SIMATIC memory card. This means you should first delete the active force job before you remove a SIMATIC memory card from the CPU and before you overwrite the card in the PC with a new project. If you use a SIMATIC memory card with unknown content, you should format the SIMATIC memory card before the next download. 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. 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. 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. WinCC Basic V13.0 System Manual, 02/2014 31 Readme 2.1 General notes Entry of decimal places With certain Windows language settings, it may occur that the entry of values with a comma as decimal place is not recognized (entering "1,23" leads to an error). Instead, use the international format ("1.23"). Access protection for memory cards in USB card readers By improving the security mechanisms for online access and engineering of S7-1500 CPUs, the data storage on memory cards has been changed. For this reason, this version of STEP 7 cannot evaluate the passwords of the configured protection level when reading project data from memory cards that is accessed via a USB card reader. The changed behavior affects the memory cards for CPUs of the S7-1200/1500 series. Therefore, use physical safeguards to protect critical project data on memory cards for these devices. Note This restriction is not related to online access to devices or the know-how protection of program blocks. Information on the TIA Portal in online support Overview of the most important technical information and solutions for the TIA Portal in the Siemens Industry online support. Internet link: TIA Portal in Siemens Industry online support (www.siemens.com/industry/ onlinesupport/tiaportal) All information on service and support in the Siemens Industry online support: Internet link: Service and support in Siemens Industry online support (http:// support.automation.siemens.com) Here, you can also subscribe to the newsletter that provides you with latest information relating to your products. Starting the TIA Portal When you start the TIA Portal, Windows attempts to update the Certificate Revocation List (CRL) of "windowsupdate.com". If no Internet access is available and there are multiple DNS servers, a timeout may occur and delay the start of the TIA Portal. Compatibility with V12 SP1 An empty V12 SP1 project with the name "TIA_Portal_Project_V12.0.1.3.ap12" is installed in the installation directory under ..\Portal V13\SampleProjects to allow TIA Portal V13 to be opened in compatibility mode V12 SP1. This project must be copied to a local directory with full access before it can be used. For more information on this, refer to FAQ ID 835846. 32 WinCC Basic V13.0 System Manual, 02/2014 Readme 2.2 STEP 7 Basic FAQs on the TIA Portal FAQs on the TIA Portal are available at FAQs (http://support.automation.siemens.com/WW/ view/en/28919804/133000). 2.2 STEP 7 Basic 2.2.1 Security information Upgrades and updates Siemens provides products and solutions with industrial security functions that support the secure operation of plants, solutions, machines, equipment and/or networks. They are important components in a holistic industrial security concept. With this in mind, Siemens' products and solutions undergo continuous development. Siemens recommends strongly that you regularly check for product updates. For the secure operation of Siemens products and solutions, it is necessary to take suitable preventive action (e.g. cell protection concept) and integrate each component into a holistic, state-of-the-art industrial security concept. Third-party products that may be in use should also be considered. For more information about industrial security, visit http://www.siemens.com/industrialsecurity (http://www.industry.siemens.com/topics/global/ en/industrial-security/Pages/Default.aspx) To stay informed about product updates as they occur, sign up for a product-specific newsletter. For more information, visit http://support.automation.siemens.com (http://support.automation.siemens.com/WW/ llisapi.dll?aktprim=99&lang=en&referer=%2fWW %2f&func=cslib.csinfo2&siteid=csius&extranet=standard&viewreg=WW&groupid=4000002) Network settings The following tables show the network settings of each product you need to analyze the network security and to configure external firewalls: STEP 7 Basic Name Port number Transport protocol Direction Function Description ALM 4410* TCP Inbound/ outbound License service This service provides the complete functionality for software licenses and is used by both the Automation License Manager as well as all license-related software products. RFC 1006 102 TCP Outbound S7 communicatio n Communication to the S7 controller via Ethernet/PROFINET for programming and diagnostic purposes. WinCC Basic V13.0 System Manual, 02/2014 33 Readme 2.2 STEP 7 Basic STEP 7 Basic DCP --- Ethernet Outbound PROFINET The DCP protocol (Discovery and Basic Configuration Protocol) is used by PROFINET and provides the basic functionality for locating and configuring PROFINET devices. SNMP 161 UDP Outbound PROFINET The SNMP client functionality is used by STEP 7 to read status information from PROFINET devices. * Default port that can be changed by user configuration WinCC ES Basic (without simulation) Name Port number Transport protocol Direction Function Description ALM 4410* TCP Inbound/ outbound License service This service provides the complete functionality for software licenses and is used by both the Automation License Manager as well as all license-related software products. HMI Load 1033 TCP Outbound HMI Load (RT Basic) This service is used to transmit images and configuration data to Basic Panels. * Default port that can be changed by user configuration Simulation RT Basic Name Port number Transport protocol Direction Function Description HMI Load 1033 TCP Inbound HMI Load (RT Basic) This service is used to transmit images and configuration data to Basic Panels. Ethernet/ IP 44818 TCP Outbound Ethernet/IP channel The Ethernet/IP protocol is used for connections to Allen Bradley PLCs. 2222 UDP Inbound Ethernet/IP channel The Ethernet/IP protocol is used for connections to Allen Bradley PLCs. Modbus TCP 502 TCP Outbound Modbus TCP channel The Modbus TCP protocol is used for connections to Schneider PLCs. RFC 1006 102 TCP Outbound S7 channel Communication to the S7 controller via Ethernet/PROFINET Mitsubishi MC 5002 TCP Outbound Mitsubishi MC channel The Mitsubishi protocol is used for connections to Mitsubishi PLCs. 34 WinCC Basic V13.0 System Manual, 02/2014 Readme 2.2 STEP 7 Basic 2.2.2 News News in the TIA Portal To keep you up-to-date with the latest news, Siemens Industry Online Support now offers a website with the latest news on a variety of topics of the TIA Portal. All news on STEP 7 Basic are available at a glance at this link: http://support.automation.siemens.com//WW/view/84047138 (http:// support.automation.siemens.com/WW/view/en/84047138) 2.2.3 Notes on use Contents Information that could not be included in the online help and important information about product characteristics. Online operation The simultaneous online operation of STEP 7 V5.5 or earlier and STEP 7 Basic V13 has not been approved. Simultaneous online connections on an S7-1200 CPU It is not possible to establish an online connection from multiple TIA Portal instances simultaneously to the same S7-1200 CPU. Configuring and assigning module parameters You will find an overview of the modules that can be configured and assigned parameters with STEP 7 Basic V13 at http://support.automation.siemens.com (http:// support.automation.siemens.com/WW/view/en/28919804/133000). Removing/inserting the memory card After removing or inserting a memory card, always perform a memory reset on the CPU in order to restore the CPU to a functional condition. Removing and inserting Ethernet modules If Ethernet modules are removed and re-inserted during operation, you must boot the PC; otherwise, the "Accessible devices" functionality in STEP 7 or NCM PC will not display all devices. While the PC boots, Ethernet modules must be activated. WinCC Basic V13.0 System Manual, 02/2014 35 Readme 2.2 STEP 7 Basic Comparing project data The comparison functions (online/offline, offline/offline) currently do not take hardware into consideration. Loading project data with TIA Portal V12 and V13 (S7-1200) If you load the project data of an S7-1200 CPU with the TIA Portal V13, you can no longer use TIA Portal V12 to access this data. To do this, first restore the factory settings of the CPU. Read the additional information on this in the online help under "How to reset a CPU to factory settings". Using project data of distributed IO-Link master modules from TIA Portal V12 in V13 The following procedure applies if you are using distributed IO-Link master modules in TIA Portal V12 that are not GSD devices and were configured with PCT: To continue using your project data from TIA Portal V12.0 in TIA Portal V13.0, you have to export them in the PCT before you upgrade the project. After the upgrade, you must import the project data once again using the PCT. Compatibility The device configuration and program of an S7-1200 CPU must always be configured with the same STEP 7 version. Usually, the TIA Portal makes sure that no version conflicts occur by outputting appropriate notifications during loading to the device. This automatic verification is not possible with S7-1200 CPUs with firmware version V1.x. In this case, users themselves must ensure that no version conflicts occur. 2.2.4 Editing devices and networks 2.2.4.1 General information on devices and networks Contents General information on devices and networks. S7 PCT IO-Link The S7 Port Configuration Tool is available for free download at the following link. http://support.automation.siemens.com/WW/view/37936752 (http:// support.automation.siemens.com/WW/llisapi.dll?aktprim=0&lang=en&referer=%2fWW %2f&func=cslib.csinfo&siteid=csius&groupid=4000002&extranet=standard&viewreg=WW&n odeid0=33102519&objaction=csopen) 36 WinCC Basic V13.0 System Manual, 02/2014 Readme 2.2 STEP 7 Basic 2.2.4.2 Use of modules on the S7-1200 Contents Information that could not be included in the online help and important information about product characteristics. Use of modules on the S7-1200 The modules listed below are not supported on the S7-1200. Family Module Order number S7-300 FMs SM 338 6ES7 338-4BC01-0AB0 FM 350-1 6ES7 350-1AH03-0AE0 FM 350-2 6ES7 350-2AH00-0AE0, 6ES7 350-2AH01-0AE0 FM 351 6ES7 351-1AH01-0AE0, 6ES7 351-1AH02-0AE0 FM 352 6ES7 352-1AH02-0AE0 FM 355 S 6ES7 355-1VH10-0AE0 FM 355 C 6ES7 355-0VH10-0AE0 FM 355-2 C 6ES7 355-2CH00-0AE0 FM 355-2 S 6ES7 355-2SH00-0AE0 CP 340 6ES7 340-1AH02-0AE0, 6ES7 340-1BH02-0AE0, 6ES7 340-1CH02-0AE0 CP 341 6ES7 341-1AH01-0AE0, 6ES7 341-1AH02-0AE0, 6ES7 341-1BH01-0AE0, 6ES7 341-1BH02-0AE0, 6ES7 341-1CH01-0AE0, 6ES7 341-1CH02-0AE0 S7-300 PtP-CP Network component Diagnostics repeater 6ES7 972-0AB01-0XA0 ET 200S 1 Count 24 V 6ES7 138-4DA04-0AB0 1 Count 5 V 6ES7 138-4DE02-0AB0 1 Step 5 V 6ES7 138-4DC00-0AB0, 6ES7 138-4DC01-0AB0 2 pulses 6ES7 138-4DD00-0AB0, 6ES7 138-4DD01-0AB0 1 SI 6ES7 138-4DF01-0AB0 1 SI Modbus 6ES7 138-4DF11-0AB0 1 SSI 6ES7 138-4DB02-0AB0, 6ES7 138-4DB03-0AB0 1 Pos Universal 6ES7 138-4DL00-0AB0 SIWAREX 7MH4910-0AA01, 7MH4912-0AA01, 7MH4920-0AA01 SIWAREX 7MH4 900-2AA01, 7MH4 900-3AA01, 7MH4 950-1AA01, 7MH4 950-2AA01 ET 200M Loading S7-1200 module comments to the PG/PC In central configurations with S7-1200, comments of modules, submodules and signal boards are not loaded. With CPs/CMs, only the comments of the IE interface or DP interface are loaded. In distributed configurations with ET 200SP or ET 200MP, only the comment of the channels is loaded from the I/O modules. WinCC Basic V13.0 System Manual, 02/2014 37 Readme 2.2 STEP 7 Basic 2.2.4.3 Replacing ET 200S positioning modules Contents Information that could not be included in the online help and important information about product characteristics. Replacing ET 200S positioning modules This information relates to the positioning module "1 Step 5V" (6ES7 138-4DC00-0AB0) from a project which was created with TIA Portal V11.0. When replacing these modules from the TIA Portal V11.0 with a new version of these modules, the parameter settings are reset to the default values. This is the case with one of the following procedures: Replace the positioning module 6ES7 138-4DC00-0AB0 with its successor module 6ES7 138-4DC01-0AB0 by means of a device exchange. Updating the module version using the appropriate button in the device properties in the Inspector window. 2.2.4.4 CP 343-2 on SIMATIC S7 Embedded Controller EC31-RTX Contents Information that could not be included in the online help and important information about product characteristics. CP 343-2 on SIMATIC S7 Embedded Controller EC31-RTX The module AS-Interface CP 343-2 (order no.: 6GK7 343-2AH01) can be inserted in an expansion rack of the SIMATIC S7 Embedded Controller EC31-RTX (order no.: 6ES7 677-1DDxx-0BB0), but the CP 343-2 cannot be operated with the EC31-RTX. 2.2.4.5 Notes on online and diagnostics Contents Information that could not be included in the online help and important information about product characteristics. Hardware detection followed by online connection When the "Online > Hardware detection" command is performed for an unspecified CPU, the online configuration is not loaded from the CPU. If you do not load the configuration resulting from the hardware detection to the CPU, the device and network views will always show a difference between the offline and online configurations. It will appear that there are different 38 WinCC Basic V13.0 System Manual, 02/2014 Readme 2.2 STEP 7 Basic configurations in the online and diagnostic views, although the MLFBs are identical in the actual CPU and the offline CPU. 2.2.4.6 Network components Network components CP 1242-7 Copying the CP 1242-7 into another project If you copy a CP 1242-7 from one project into another project, the following parameters in the parameter group "CP identification" are changed on the target station: Project number of the CP Station number of the CP Download to device Only use the "Download to device" function with the CP 12427 via a TeleService connection as follows: 1. Select the CP in STEP 7. 2. Select the "Online" > "Download to device" menu. 3. In the "Extended download" dialog that appears, select the TeleService interface. 4. Download the project data from the "Extended download" dialog. Upload from device The function "Upload from device" is not supported by the CP 12427. PC CPs PC CPs for VMware vSphere Hypervisor ESXi The following communications processors have been released for operation with VMware vSphere 5.1 Hypervisor ESXi: CP 5622 CP 5711 VMware E1000 network adapter The following communications processors have not been released for operation with VMware vSphere 5.1 Hypervisor ESXi: WinCC Basic V13.0 System Manual, 02/2014 39 Readme 2.2 STEP 7 Basic CP 5611 CP 5612 CP 5621 CP 5512 Other communications processors such as the CP 1613, CP 1623, CP 5613, CP 5614, CP 5623, CP 5624 are released following installation of the SIMATIC NET PC software. You will find information on this in the readme file of the SIMATIC NET PC software. Media converters When you migrate a project, you need to reconfigure the media converters. 2.2.5 Programming a PLC 2.2.5.1 General notes on PLC programming Contents Information that could not be included in the online help and important information about product characteristics. Information about network security For communications access between the TIA Portal and CPU or between HMI (except for HMI access using "GET/PUT communication") and CPU, there are integrated security functions. The provide greater protection from manipulation and higher access protection. To protect against unauthorized network access to a CPU with standardized communications access such as "GET/PUT", "TSEND/TRCV", "Modbus", "FETCH/WRITE", you should also take suitable additional measures (e.g. cell protection concept). Renumbering PLC data types For better performance, the CPUs of the S7-1200 module process PLC data types with numbers. The user is not aware of these numbers, because the system processes the numbers independently. This means number conflicts are automatically resolved. When using knowhow protected blocks that use PLC data types, it may be useful to set up your own numbering system (recommended > 5000) because the automatic resolution of numbering conflicts may result in a password prompt (compilation required). To renumber the default number of a PLC data type, follow these steps: 1. Open the project library in the "Libraries" task card. 2. Drag the compilable PLC data type to the "Types" folder. The "Add type" dialog opens. 3. Enter the properties of the new type. 40 WinCC Basic V13.0 System Manual, 02/2014 Readme 2.2 STEP 7 Basic 4. Click "OK" to confirm. 5. Right-click the PLC data type. The shortcut menu opens. 6. Select "Edit type" in the shortcut menu. 7. Open the "PLC programming" task card once again. The extension "in testing" is now added to the name of the PLC data type. 8. Right-click the PLC data type. The shortcut menu opens. 9. Select "Properties" in the shortcut menu. 10.Change the number of the PLC data type in the "General" section. 11.Select "Release version" from the shortcut menu of the library. The PLC data type now has the new number and can be used. The assigned number is retained even if the type of the PLC data type is revoked. Generating external sources from blocks When generating external sources from blocks, the changes made directly in the block interface to the default values of PLC data types are not exported to the sources. This means these values are not available when the sources are imported once again. The default values are applied instead. To prevent this loss of data for the modified default values, the changes must be made directly in the PLC data type and not in the block interface. In this case, the changes are also exported when generating external sources. Indirect indexing of ARRAY components of data type bit string in SCL In TIA Portal V13, you can address the components of an ARRAY for a CPU of the S7-1200 series in SCL with a tag of the data type BYTE, WORD or DWORD as index in addition to a tag of the integer data type if the IEC check is not set. Explicit data type conversion in SCL As of TIA Portal V13, the string is displayed with a leading sign during explicit data type conversion of SINT/INT/DINT/LINT_TO_STRING or WSTRING in SCL and transferred aligned to the left. The result is an incompatibility with TIA Portal V12 SP1, in which the string was transferred aligned to the right during conversion. Start value behavior during "Upload from device" The start values that you have changed with the instruction "WRIT_DBL: Write to data block in the load memory" will be lost during execution of the action "Upload from device". WinCC Basic V13.0 System Manual, 02/2014 41 Readme 2.2 STEP 7 Basic Loading inconsistent programs to a device In TIA Portal, it is not possible to download inconsistent programs to a device without a consistency check. During the loading process, all blocks of the program are implicitly checked and are compiled again in the event of inconsistencies. If, however, there are programs on your CPU which were loaded with earlier versions of STEP 7, these programs could demonstrate inconsistencies. In this case, note the following: If you load an inconsistent program from a device, you will not be able to load the program unchanged to the device afterwards, because a consistency check always takes place during the loading process and existing inconsistencies are corrected. Process image of PTO/PWM outputs Do not use PTO/PWM outputs in the process image (for example, for access in the user program, for online functions or in HMI). The update rate of the process image is much slower than the rate of the signal changes. The display in the process image therefore does not reflect the signal flow. Monitoring blocks in LAD and FBD If the start of the current path is outside the visible range, it may not be possible to determine the input value. In this case, the current path is shown grayed out. Avoid using PLC data types generated by the system in libraries Some instructions generate their own PLC data types during instancing which are saved in the "PLC data types" project folder. However, you should not use these system-generated PLC data types in any library, because they may be recreated by the system at any time and may result in an unfavorable system behavior. Using global data blocks in assignments It is not possible to assign the contents of a global data block to a structurally identical data block, e.g. using a move box. 2.2.5.2 Instructions Contents Information that could not be included in the online help and important information about product characteristics. 42 WinCC Basic V13.0 System Manual, 02/2014 Readme 2.2 STEP 7 Basic Notes on the information system The following function is already described in the information system, but is not available in TIA Portal V13: "ASI_CTRL" instruction for CPUs of the S7-1200 module Instruction "TRCV_C: Receive data via Ethernet" Contrary to the information provided in the online help, the communication connection is terminated immediately, and not after sending data, when the CONT parameter is set to the value "0". Instruction "T_CONFIG: Configure interface" The CPU is restarted after you have executed the "Configure interface" instruction in order to change an IP parameter. The CPU goes to STOP mode, a warm restart is carried out and the CPU starts up again (RUN mode). Make sure that the control process is in a secure operating mode after the CPU has been restarted following execution of the "Configure interface" instruction. Uncontrolled operation can result in serious material damage or personal injury due to malfunctions or programming errors, for example. Non-retentive data could be lost. Parameters ERROR and STATUS ERROR STATUS (DW#16#..) ERR_LOC Explanation 0 00000000 0 After the instruction has been executed successfully, the STATUS parameter "00000000" does not return any value. Instruction "GET_DIAG: Read diagnostics information" MODE 3 at the MODE parameter is not supported by the S7-1200 CPU. Using instructions with parameters of type VARIANT in code blocks with different access types (S7-1200) Code blocks (FBs/FCs) and data blocks (DBs) can be created with different access types ("standard" and "optimized"). In code blocks, you can call any instructions. Certain instructions (for example, "WRIT_DBL" and "READ_DBL") use pointers of type VARIANT at input and output parameters to address data blocks. Ensure that you do not use these instructions in programs in which code blocks of different access types are called reciprocally. This could cause the following to occur: WinCC Basic V13.0 System Manual, 02/2014 43 Readme 2.2 STEP 7 Basic A structure from a standard data block is directly or indirectly passed to an optimized code block, which forwards this structure directly or indirectly to one of the blocks mentioned above. The reverse scenario, whereby a structure from an optimized code block is directly or indirectly passed to a standard data block, which forwards this structure directly or indirectly to one of the blocks mentioned above. 2.2.5.3 Testing the user program Testing with the watch table Contents Information that could not be included in the online help and important information about product characteristics. Multiple access to the same CPU Access to a CPU from a PG/PC is permitted only when a TIA Portal is open. Multiple access to the same CPU is not permitted and can lead to errors. Loading data blocks during an active control job Note Loading changed data blocks during an active control job can result in unforeseen operating states. The control job continues to control the specified address, although the address allocation may have changed in the data block. Complete active control jobs before loading data blocks. Testing programs converted from STEP 7 V10.5/V11.0 To monitor and test a program converted from STEP 7 V10.5, you have to first compile and load with STEP 7 V13.0. Testing with the force table Contents Information that could not be included in the online help and important information about product characteristics. 44 WinCC Basic V13.0 System Manual, 02/2014 Readme 2.3 WinCC Basic Example If I/O access to the address "IB0:P" takes place in the user program, it is not permitted to force the following I/O address areas: I0.0:P, IB0:P, IW0:P and ID0:P. 2.2.6 Inter Project Engineering (IPE) 2.2.6.1 Notes on IPE Contents Information that could not be included in the online help and important information about product characteristics. Comment box of the device proxy Contrary to the description in the information system for the TIA Portal V13, with the "Inter Project Engineering" functionality, the comment field for a device proxy cannot be edited. Restricted functionality In the TIA-Portal V13, the "S7 GRAPH overview" and "PLC code display" functionality cannot be used in conjunction with the IPE device proxy. 2.2.7 Technological functions 2.2.7.1 Notes on technological functions There are no notes about the technology functions. 2.3 WinCC Basic 2.3.1 Security information Security information Siemens provides products and solutions with industrial security functions that support the secure operation of plants, solutions, machines, equipment and/or networks. They are WinCC Basic V13.0 System Manual, 02/2014 45 Readme 2.3 WinCC Basic important components in a holistic industrial security concept. With this in mind, Siemens' products and solutions undergo continuous development. Siemens recommends strongly that you regularly check for product updates. For the secure operation of Siemens products and solutions, it is necessary to take suitable preventive action (e.g. cell protection concept) and integrate each component into a holistic, state-of-the-art industrial security concept. Any third-party products that may be in use must also be taken into account. For more information about industrial security, visit http://www.siemens.com/industrialsecurity (http://support.automation.siemens.com) To stay informed about product updates as they occur, sign up for a product-specific newsletter. For more information, visit http://support.automation.siemens.com (http://support.automation.siemens.com) Passwords Various passwords are set by default in WinCC. For security reasons, you should change these passwords. For the user "Administrator", the default password is "administrator". Communication via Ethernet In Ethernet-based communication, end users themselves are responsible for the security of their 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. Ending Runtime automatically If automatic transfer is enabled on the HMI device and a transfer is started on the configuration PC, the running project is automatically stopped on the HMI device. The HMI device then switches autonomously to "Transfer" mode. Transfer mode may cause undesired reactions in the system. After the commissioning phase, disable the automatic transfer function to prevent the HMI device from switching inadvertently to transfer mode. To block access to the transfer settings and thus avoid unauthorized changes, assign a password in the Control Panel. Network settings The following tables show the network settings of each product which you need in order to analyze the network security and for the configuration of external firewalls: WinCC Basic (without simulation) Name Port number Transport protocol Direction Function Description ALM 4410* TCP Inbound, Outbound License service This service provides the complete functionality for software licenses and is used by both the Automation License Manager as well as all license-related software products. 46 WinCC Basic V13.0 System Manual, 02/2014 Readme 2.3 WinCC Basic WinCC Basic (without simulation) HMI Load 1033 TCP Outbound HMI Load (RT Basic) This service is used to transmit images and configuration data to Basic Panels. * Default port that can be changed by user configuration WinCC Simulation for Basic Panels Name Port number Transport protocol Direction Function Description HMI Load 1033 TCP Inbound HMI Load (RT Basic) This service is used to transmit images and configuration data to Basic Panels. EtherNet/IP 44818 TCP Outbound Ethernet/IP channel The Ethernet/IP protocol is used for connections to Allen Bradley PLCs. 2222 UDP Inbound Ethernet/IP channel The Ethernet/IP protocol is used for connections to Allen Bradley PLCs. Modbus TCP 502 TCP Outbound Modbus TCP channel The Modbus TCP protocol is used for connections to Schneider PLCs. RFC 1006 102 TCP Outbound S7 channel Communication with the S7 controller via Ethernet/PROFINET Mitsubishi MC 5002 TCP Outbound Mitsubishi MC channel The Mitsubishi protocol is used for connections to Mitsubishi PLCs. See also http://www.siemens.com/industrialsecurity (http://www.industry.siemens.com/topics/global/ en/industrial-security/Pages/Default.aspx) 2.3.2 News News about the TIA Portal You can learn about the latest news about various topic areas of the TIA Portal in Siemens Industry Online Support. All news concerning WinCC can be found here: News (http://support.automation.siemens.com/ WW/view/en/88360672) 2.3.3 Notes on use Contents Information that could no longer be included in the online help and important information about product features. WinCC Basic V13.0 System Manual, 02/2014 47 Readme 2.3 WinCC Basic 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 is not automatically connected to an existing PLC with the same name. This 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 have to complete the configuration of the HMI connection immediately after copying. Proceed as follows: 1. Open the "Devices & Networks" editor. 2. Connect the new HMI device to 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 an additional HMI connection to the same PLC is created. This is especially true if you connect HMI tags with DB array elements. Device replacement After an HMI device has been replaced, you should check the appearance of the configured screens. Changing the size of the display may result in changes to the position and appearance of screen objects, e.g. recipe view and alarm view. Device replacement - communication If an HMI device is replaced, error messages of the type "... are not supported in the new configuration. and will therefore be removed" may be generated. These alarms refer to configured connections of the device and are triggered, for example, if the HMI devices have a different number of interfaces. These connections are marked red after a device replacement. If you would like to continue to use these connections, you have change the configuration of the connection. Proceed as follows: 1. Open the "Devices and Networks" editor. 2. Click "Network" in the toolbar of the network view. 3. Network the interface of the HMI device with the interface of the CPU. 4. Click in the table area of the network view on the "Connections" table. 5. Select the connection marked red. 6. Enter the new interface under "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. 48 WinCC Basic V13.0 System Manual, 02/2014 Readme 2.3 WinCC Basic 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. Installing East Asian project languages on a PC without Asian operating system If you select an East Asian project language on a PC that does not have an Asian operating system installed, the default font is marked as invalid in the "Runtime settings > Language & font" editor. To resolve this problem, open the "Regional and Language Options > Languages" dialog in the Control Panel and enable the "Install files for East Asian languages" option. Installation sequence for Startdrive When you install Startdrive on a PC, adhere to the following installation sequence: Install STEP 7 V13.0. Install Startdrive. Compatibility with V12 An empty V12.0.1.3 project with the name "TIA_Portal_Project_V12.0.1.3.ap12" is installed in the installation directory under ..\Portal V13\SampleProjects to allow TIA Portal V13 to be opened in compatibility mode V12. This project must be copied to a local directory with full access before it can be used. For more information on this, refer to FAQ ID 66027369. WinCC Basic V13.0 System Manual, 02/2014 49 Readme 2.3 WinCC Basic File browser on a Windows 8 PC with touch screen You can only operate the file browser dialog with a mouse, keyboard or on-screen keyboard (without using the touch function) on a Windows 8 PC with touch screen. We recommend using the file browser dialog of the Windows operating system with the help of a script on a touch screen PC with Windows 8. 2.3.4 Migration Contents Information that could no longer be included in the online help and important information about product features. Project languages in WinCC WinCC V13 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. Migrating an integrated project with ProTool objects The "PROTOOL option package(s) missing in STEP 7" error message output during migration of a WinCC flexible project that is integrated in STEP 7 indicates that WinCC flexible 2008 SP3 is installed on your system. Moreover, the project still contains objects that were configured using ProTool. Do not open the project with WinCC flexible 2008 SP3! Proceed as follows to migrate the project: 1. Copy the project to a computer on which WinCC flexible 2008 SP2 and STEP 7 are installed. 2. Open the project in the SIMATIC Manager. 3. Remove all ProTool objects from the project. 4. Execute the "Save as" command in the "File" menu. 5. Enable the option "With reorganization" in the "Save project as" dialog. 6. Click OK. 7. Copy the project back to the original computer. 8. Restart the migration. 50 WinCC Basic V13.0 System Manual, 02/2014 Readme 2.3 WinCC Basic Migrating a WinCC V7 project: Border line of rectangles In a WinCC V7 project, you have configured a rectangle with the settings "Line weight = 1" and "Draw insider border = yes". You then migrate the WinCC V7 project to WinCC V13. To have the rectangle displayed correctly, follow these steps. 1. Open the Inspector window of the rectangle. 2. Open the property list. 3. Disable "Widen border line inwards". Progress bar As long as the progress bar still shows a value of 100%, the software is still busy running remaining tasks such as the closing of references. The software will not respond to user input while this status is given. Open a project created with WinCC V11 When you open a V11 project with a WinCC V13 version, it is no longer be possible to open this project with an older version afterwards. Managing third-party ActiveX controls The migration also supports third-party ActiveX controls. However, the controls must be registered in the operating system. If an ActiveX control is not registered, migration is canceled. If you save a project with the migration tool and perform the migration yourself on another PC, the controls must also be registered on this PC. Migrating integrated projects with alarm views An alarm view is enabled with all alarm classes in an integrated project. The alarm classes are disabled during migration of the project. Once the migration of the project is completed, check the settings in the alarm view. Enable the require alarm classes in the Inspector window of the alarm view if needed under "Properties > General". Migrating more extensive projects from WinCC V7 We recommend the use of a 64-bit operating system for the migration of more extensive projects from WinCC V7. Migrating projects from WinCC V7 In TIA Portal V13, you can continue to use projects from WinCC V7.2 after migration. Projects from earlier WinCC versions cannot be migrated directly to WinCC TIA Portal version V13. If you wish to continue using such projects in TIA Portal V13, you must first migrate them to the WinCC V7.2 Classic page. To do so, use WinCC V7.2 with the latest update. WinCC Basic V13.0 System Manual, 02/2014 51 Readme 2.3 WinCC Basic Migration log As of TIA Portal V13.0 alarms are sorted into a tree structure in the migration log. This means all alarms that are part of a specific subsystem are stored in one folder. The result is an increase in the number of folders in the tree structure. Press the shortcut <NUM+ X> to expand the currently selected folder and all subfolders in one single step. Restrictions for user-specific project data 1. Folders and files you have created in the WinCC V7.2 project directory are not copied to the new project directory during the migration. You must adapt all scripts that access such directories and files after the migration. 2. C standard functions of WinCC V7 are not migrated. If you have made changes to the C standard functions in the WinCC V7 project, you must apply these changes manually to the TIA Portal after the migration. Migration of texts in Spanish (international sorting) and Spanish (traditional sorting) If the WinCC V7 project includes texts in Spanish (traditional sorting), these texts are migrated as Spanish (Spain) in WinCC V13. If the WinCC V7 project includes texts in Spanish (international sorting), these texts are migrated as Spanish (Spain) in WinCC V13. If the WinCC V7 project includes texts in Spanish (international sorting) as well as Spanish (traditional sorting), only the texts from Spanish (traditional sorting) are migrated as Spanish (Spain) in WinCC V13. The texts from Spanish (international sorting) are not taken into consideration. See also Object support during migration 52 WinCC Basic V13.0 System Manual, 02/2014 Readme 2.3 WinCC Basic 2.3.5 Engineering System 2.3.5.1 Screens and Screen Objects Contents Information that could no longer be included in the online help and important information about product features. Display objects after HMI device replacement If you upgrade a device to the new HMI device versions, you should check the screens contained in the project. Because of the new appearance and improved operability, texts of symbolic I/O fields may not be completely legible and may be concealed by operator controls. 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 Display of the cross-references in the Inspector window The Inspector window displays objects used by a screen object in the "About > Crossreference" 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, the locations of use of the interconnected PLC tag or DB tag are 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. WinCC Basic V13.0 System Manual, 02/2014 53 Readme 2.3 WinCC Basic Name in the "Properties" tab of the Inspector window Name in the "Info" tab of the Inspector window Cleared ClearScreen Loaded GenerateScreen Enable Activate Change Change When a dialog is opened ONMODALBEGIN When a dialog is closed ONMODALEND User change PASSWORD Screen change SCREEN Disable Deactivate Press Press Outgoing Going Incoming Coming Limit "high limit error" violated AboveUpperLimit Limit "low limit error" violated BelowLowerLimit Click Click Loop-in alarm LoopInAlarm Release Release Alarm buffer overflow OVERFLOW Acknowledge Acknowledgement Runtime stop Shutdown Press key KeyDown Release key KeyUp Toggle ON SwitchOn Toggle OFF SwitchOff Value change Change value Faceplates Faceplates cannot be rotated or mirrored. Tab sequence in screens with faceplates If you have configured a tab sequence in screens with faceplates in WinCC V12 or WinCC V12 SP1, you should check the tab sequence of these screens in WinCC V13. The tab sequence may have been changed in both the screen and the faceplate. Tag prefix of a screen window in WinCC Runtime Professional The objects of the "Controls" palette do not support the tag prefix that can be configured for a screen window. 54 WinCC Basic V13.0 System Manual, 02/2014 Readme 2.3 WinCC Basic I/O field with "decimal" display format and format pattern without "s" prefix You have linked a process tag to an I/O field. The I/O field is assigned the "decimal" display format. You may select a signed or an unsigned display format. A "Format pattern" setting without "s", e.g., "999" has the following effects: 1. You cannot set negative values using the I/O field in Runtime. 2. If the tag assumes a negative value, the I/O field generates a two's complement and a corrupted positive value is output. Trend view on Basic Panels The trend view buttons are not displayed on Basic Panels. You can operate the trend view using the function keys of the HMI device that are assigned corresponding system functions. Grouping of screen objects When you group screen objects in WinCC, performance problems can arise in WinCC in the case of large nesting depths. ActiveX and .NET controls ActiveX and .NET controls are always positioned in the foreground in runtime. The configuration of ActiveX and .NET controls on levels is not supported. Use of bitmaps as icons In Windows 8 and Windows 8.1, the use of bitmaps with a size of 48x48 pixels and a color depth of 32 bits as icons is not supported. Border line of rectangles In a WinCC V7 project, you have configured a rectangle with the settings "Line weight = 1" and "Draw insider border = yes". You then migrate the WinCC V7 project to WinCC V12. To have the rectangle displayed correctly, follow these steps. 1. Open the Inspector window of the rectangle. 2. Open the property list. 3. Disable "Widen border line inwards". Border line of "Graphic I/O field" object In WinCC V13, the dynamization of the border line of the "Graphic I/O field" object in "Two states" mode has no effect during runtime. WinCC Basic V13.0 System Manual, 02/2014 55 Readme 2.3 WinCC Basic Dynamization of instances of a faceplate type in a group You are using the instance of a faceplate type in an object group. The properties of the instance are also displayed as properties of the group. Any dynamization with tags, scripts or animations of the group is not displayed in Runtime. Preview in screen window You use your own designs with shadows for screen objects. The screen objects can be displayed in a screen window. The shadows of the screen objects are not displayed in the preview of the screen window. The response occurs only in the engineering system. It is displayed correctly in Runtime. Assigning graphics to a softkey A graphic can only be assigned to a softkey if the bottom edge of the permanent window does not conceal the area of the softkey graphic. Renaming a PLC in Runtime If a PLC is connected to the PLC code display in WinCC Professional and Runtime is running, changing the name of the PLC during runtime will trigger a error. Do not change the PLC name, the IP address, or other properties of the HMI connection during runtime. Panels and RT Advanced with device version V13: many visually different screen objects The use of screen objects with very many visually different properties (e.g., very many different styles) can reduce the performance of the user interface in Runtime and can increase the amount of available memory space used. Avoid using, for example, very many different corner radii: 0 pixel, 1 pixel, 2 pixels, 3 pixels, etc. The use of many differently sized "Gauge" objects can have the same effect. Avoid "Gauge" of height 48 pixels, 49 pixels, 51 pixels, etc. Instead, use sizes such as 50 pixels, 70 pixels, 100 pixels. Dynamization of grouped objects For groupings with multiple nestings (group in group, faceplate in group, group in faceplate, etc.), only the events of the outermost group and the innermost objects can be used for dynamization with system functions. System functions that are configured at events of the lower-level group or lower-level faceplate are not executed. Number of characters in text fields, lists and alarm texts The number of available characters in the text of a screen object is dynamic and depends on the HMI device and the memory format. Control instructions and formatting are taken into consideration when entering text data and the maximum number of characters is reduced accordingly. 56 WinCC Basic V13.0 System Manual, 02/2014 Readme 2.3 WinCC Basic Transparency in WinCC V13 Transparent screens can be displayed without any problems in Runtime. This is true for all Comfort Panels and WinCC Runtime Advanced with version 13.0.0.0. To use the transparency in a graphic view or in a graphic I/O field, the "Fill pattern" property must be set to "Transparent" and the property "Use transparent color" must be disabled. If the property "Use transparent color" is enabled in a device with version 13.0.0.0, the transparency of the screen is lost and the transparent screen areas are displayed in black. We recommend that you check the "Use transparent color" property at the points of use of transparent screens after upgrading existing projects to device version 13.0.0.0. If the screens are not displayed correctly, disable this property. 2.3.5.2 Tags and connections Contents Information that could no longer be included in the online help and important information about product features. Display of deleted array elements at location of use of HMI tags The locations of use of HMI tags, such as the process value of IO fields, are usually indicated by the tag name. If the element of an array tag is used, then the tag name will be extended by the index of the array element indicated in brackets. If a used tag is no longer included in the project, then the tag name will still be displayed at the location of use. The field will be displayed with a red background to indicate the missing tag. If a used array element or the array tag is no longer present, then only the index of the array element will be displayed in brackets. The tag name will not be displayed. The field is highlighted in red. You can no longer identify the name of the associated array tag based on the location of use in this instance. If you do not know which array tag was linked to this location of use, then it may be necessary to link the array element once again. If a tag or array tag was created based on a reference, then the selected reference will be closed automatically. If an HMI tag is connected with an array element of a PLC tag and the PLC tag does no longer exist in the project, then the same behavior will take place in the "HMI tags" editor. Array tags as list entry of multiplex tags You can use the array tags of the Char data type just like the tags of the String data type. The use of an array tag of the Char data type as list entry of a multiplex tag in the "HMI tags" editor is not supported. WinCC Basic V13.0 System Manual, 02/2014 57 Readme 2.3 WinCC Basic Multiplexing tags on a Basic Panel If you multiplex a tag with an external tag on a Basic Panel, the address is read from the PLC in runtime during the first read cycle. The value of the address read is not available until the second read cycle. Runtime Advanced and Panels: Importing array elements and structure elements Array tags and structure tags are always imported in full with all elements. The elements of the array tags and structure tags are not filled further during import. A new tag is created if the name of a tag corresponds to the name of an array or structure element in the import file. Example: The import file contains an array tag called "Otto" with 10 array elements. The array elements are then called Otto[1], Otto[2], for example. If the import file contains a tag named "Otto[1]", the first element of the array tag will not be filled. Instead, a new tag will be created in the engineering system. Local ID of HMI connections You cannot edit the "Local ID" value in the HMI connection properties. You need the local ID, for example, for communication by way of AR_SEND. To enable usage of the "Local ID" for communication, proceed as follows: 1. Open the network view in the "Devices & Networks" editor. 2. Click "Connections". 3. Select an S7 connection. 4. Select the "Add new connection" command in the shortcut menu of the PLC. 5. Click on the interface. 6. Specify the "Local ID (hex)". 7. Click "Add" and then "Close". 8. Select "Properties > General" from the partner area of the Inspector window and enter the IP address of the HMI device for the new connection. 9. Configure the necessary raw data tags for communication in the HMI device. Tags with the DTL data type Tags that use the "DTL" data type element by element, can only be used as read-only. Tag names in faceplates Use of the "." or "@" character in names of tags in faceplate types is not permitted. Do not use these special characters in the tag names in faceplates. 58 WinCC Basic V13.0 System Manual, 02/2014 Readme 2.3 WinCC Basic RT Professional: Tags with symbolic addressing and "Char Array" data type Tags with symbolic addressing and the "Char Array" data type are not released for communication of RT Professional and SIMATIC S7-1200 V3. Array elements in WinCC If you have connected an HMI tag with an array from a STEP 7 data block which does not start with a low limit of 0, the array elements are mapped in WinCC to the low limit of 0. To ensure that you do not have to rethink between the STEP 7 indices and the WinCC indices when accessing the individual array elements, the low limits of arrays should also start at 0 in STEP 7. 2.3.5.3 Alarm system and alarm displays Contents Information that could not be included in the online help and important information about product properties. 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 It is also possible to use multiplex tags in the output boxes of alarm texts in the engineering system. During runtime, this leads to an incorrect display of the alarm, because the use of multiplex tags is not supported by the basic panels. Parameters in user alarms Contrary to the information in the online help, it is not possible to configure parameters for user alarms. The menu command "Properties > Properties > Alarm parameters" is not available in the Inspector window. Tags in alarm texts of RT Advanced Tags of data type WChar or WString cannot be displayed in the alarm view in RT Advanced. WinCC Basic V13.0 System Manual, 02/2014 59 Readme 2.3 WinCC Basic 2.3.5.4 System functions Content Information that could not be included in the online help and important information about product properties. The "SimulateTag" system function on Basic Panels If you use the system function "SimulateTag" with a short cycle time on a Basic Panel, the HMI device may be overloaded. 2.3.5.5 Recipes Contents Information that could not be included in the online help and important information about product features. Arrays in recipe elements If you have configured both an array as well as the elements of this array for recipe elements of a recipe, the loading of data records aborts with the following error message: "290055: Import of data records aborted with error" Use either the array or just the array elements for recipe elements of a single recipe. 2.3.5.6 User administration Contents Information that could not be included in the online help and important information about product features. 2.3.5.7 Communication Contents Information that could no longer be included in the online help and important information about product features. 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. 60 WinCC Basic V13.0 System Manual, 02/2014 Readme 2.3 WinCC Basic It is recommended to check these connection resources in the PLC program of the PLC and also to enable them again. 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. Communication by means of routing with S7 300/400 Communication of connection partners in different subnets is possible via routing with the following connections: PROFINET, PROFIBUS, MPI. Use of 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 a PROFINET IO-capable S7-400 CPU is used with one of the HMI devices listed below: The offset for the start of the address area of the inputs must not be greater than the offset for the start of the address area of the outputs. The restriction applies to the following HMI devices: OP 177B OP 277 Mobile Panel 177 For the configuration of the address parameters, open the PLC with the S7-400 CPU 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. Enable 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 Mitsubishi MC and Mitsubishi FX communication drivers 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 WinCC Basic V13.0 System Manual, 02/2014 61 Readme 2.3 WinCC Basic 20-bit block 24-bit block 28-bit block Coordination area pointer in an OPC connection In principle, the coordination area pointer can be used eight times in an OPC connection. If you have configured an OPC connection and you automatically create another OPC connection using "Add", the coordination area pointer 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 coordination area pointer can again be used eight times. Changing IP settings and device name of a PLC in the Control Panel of the HMI device The Control Panel is open in the "Service and Commissoning > IP-Adaptation" menu on the HMI device. If you want to change the IP settings or the device name of a PLC, note the following: In the Engineering System, you need to have activated the following options in the Inspector window of the PLC under "Properties > General > PROFINET interface > Ethernet addresses" beforehand: - "Set IP address using a different method" and - "Set PROFINET device name using a different method". HMI connections in WinCC V13 HMI connections to SIMATIC S7-1200 PLCs with firmware versions earlier than V2.0 are not possible in WinCC V13. Connections via PROFIBUS DP When a connection between a PLC and an HMI device via PROFIBUS DP is interrupted and then re-established, sporadically all other PROFIBUS DP connections in the communication network are interrupted and re-established. De-energize the disconnected station before reconnecting it. "Set the IP suite (address) of the PLC in the Control Panel" with SIMATIC S7-1200 V1 The function "Set the IP suite (address) of the PLC in the Control Panel" has not been approved for the following PLCs: SIMATIC S7-1200 V1 Switching a connection A connection may be interrupted when it is switched from an HMI device to a SIMATIC S7-300/400, to a SIMATIC S7-1500 or to a SIMATIC S7-1200 PLC. 62 WinCC Basic V13.0 System Manual, 02/2014 Readme 2.3 WinCC Basic Note the following settings in the SIMATIC S7-1500 or SIMATIC S7-1200 controllers: Absolute addressing of tags The "Disable PUT-GET communication" option must be selected The "Complete protection" protection level may not be set Raw data communication in redundant projects Simatic.NET, Named Connections and various communication blocks, such as BSEND/BRCV, for example, can only be used to a limited extent in a redundantly configured PC station because the connection parameters for the redundant partner server cannot be configured. 2.3.6 System-wide functions Contents Information that could no longer be included in the online help and important information about product features. Inter Project Engineering: Displaying alarms of system diagnostics If you do not enable "PLC alarms" when you create device proxy data, system diagnostic alarms are not applied to the device proxy data. System diagnostic alarms of the device proxy are not displayed after initialization of device proxy data without "PLC alarms". 2.3.7 Compiling and loading Contents Information that could no longer be included in the online help and important information about product features. 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. WinCC Basic V13.0 System Manual, 02/2014 63 Readme 2.3 WinCC Basic Settings for update of operating system If you select the command "Online > HMI device maintenance > Update operating system" from WinCC, you cannot change the settings such as the type of PG/PC interface or baud rate. The settings used during the last download are always used. To make changes to the settings, open the "Extended download" dialog using the "Online > Extended download to device" command and change the settings. When you click the "Load" button the changed settings are saved. Alternatively, you can perform an update of the operating system with changed settings with ProSave. You start ProSave via the Windows Start menu "Siemens Automation > Options and Tools > HMI Tools > SIMATIC ProSave". Incorrect installation of ProSave If you receive an error message during installation of ProSave when loading data to a target device or maintenance of an HMI device, then you cannot remedy this error using the repair function of setup. Remove ProSave via the Control Panel. Then start setup and install the "ProSave" component again. Checking the address parameters During compilation of an HMI device in the project tree with the command "Compile > Software" in the shortcut menu, the address parameters of the HMI device, such as the IP address, will not be checked. If you want to ensure that the address parameters are checked as well, you will have to compile the HMI device using the "Compile" button 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 enable the option "Show all accessible devices", it may occur that the application stops responding. 64 WinCC Basic V13.0 System Manual, 02/2014 Readme 2.3 WinCC Basic OP77A, OP73, TP177A: Loading projects When loading a project to an HMI device, it can happen that Runtime is not automatically ended, even though "Remote Transfers" is activated in the Panel. If this happens, stop Runtime and manually set the transfer mode on the HMI device. Loading a SIMATIC HMI application to a PC station The following circumstances can lead to an error message during the first load of a SIMATIC PC station: A SIMATIC HMI application is configured in a PC station in the project - WinCC Runtime Advanced - WinCC Runtime Professional - WinCC Standby - or WinCC Client The property "S7RTM is installed" is activated. Before you load a SIMATIC PC station for the first time, select the configured device HMI_RT (WinCC...) in the project tree. 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. Project transfer via USB If you have connected more than one HMI device via USB to your configuration PC, project transfer is only possible to the last connected device. Opening project files When you run "HmiIRTm.exe", a dialog opens asking if you want to open the project file (.fwc). The following options are available to you: "Yes": A dialog opens allowing you to select a project file (.fwc). "No": The dialog closes. Tag simulator in WinCC Professional does not start If the tag simulator does not start in WinCC Professional, it may be because the fm20.dll file has not been installed in the system yet. The fm20.dll file cannot be distributed and must be installed as part of a Microsoft application: http://support.microsoft.com (http://support.microsoft.com/default.aspx?scid=kb;EN-US; 224305) You have the following two options for installing the fm20.dll file: WinCC Basic V13.0 System Manual, 02/2014 65 Readme 2.3 WinCC Basic Install an application, such as Microsoft Office 97, on the destination system. The installation routine also installs the fm20.dll file. You can also download and install the Microsoft ActiveX Control Pad free of charge. The fm20.dll file is also installed in this case. Additional information on the ActiveX Control Pad is available on the Microsoft Developer Network website: http://msdn.microsoft.com/en-us/library/ms968493.aspx (http://support.microsoft.com/ default.aspx?scid=kb;EN-US;224305) 2.3.8 Runtime 2.3.8.1 Notes on operation in Runtime Contents Information that could no longer be included in the online help and important information about product features. Focus in Runtime If you have configured a low-contrast combination of focus color and border color in a V12 project, the focus may no longer be identifiable after changing the HMI device version in Runtime. Change one of the two colors. Language behavior - Layout of on-screen keyboard The layout of the on-screen keyboard is not switched when the runtime language changes. Tag values exceed the maximum length You enter a character string in a string tag via an I/O field. If the character string exceeds the configured number of tags, the character string will be shortened to the configured length. Empty message texts Runtime is running with a project. The project is saved on a network drive. In the event of interruptions to the network drive connection, Runtime may attempt to load message texts from the network drive. In the event of disconnection, the alarm window or the alarm view remains empty. To avoid this, copy the project to a local drive before the starting the project in Runtime. Complete download in Service mode If you need to perform a "complete download" to the OS in Service mode from the engineering station, Runtime automatically stops and then starts again. 66 WinCC Basic V13.0 System Manual, 02/2014 Readme 2.3 WinCC Basic The project is then no longer in Service mode. In this state, the power supply is interrupted and WinCC Runtime no longer starts automatically on the OS. Remedy: 1. Switch the project manually to Service mode after you have performed the "complete download". 2. Close the project manually. 3. Enable Service mode. 4. Start Runtime again using the surrogate icon in the taskbar. 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: You can find 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. Note 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 the product DVD: Support\Windows7\CRL_Check or CD_RT\Support\Windows7\CRL_Check\ WinCC Basic V13.0 System Manual, 02/2014 67 Readme 2.3 WinCC Basic Starting Runtime Only WinCC Runtime V13 can be started in TIA Portal V13. WinCC Runtime V11.02, V12 or V13 can be simulated in TIA Portal V13. 2.3.8.2 Notes on operation of panels in Runtime Contents Information that could not be included in the online help and important information about product features. License transfer via S7USB You always need to run WinCC to transfer a license to a panel via S7USB. Transferring licenses to a panel on 64-bit operating systems If you are running a 64-bit operating system and the "Edit > Connect target systems > Connect HMI device" menu command is not available in Automation License Manager, open command line input and run the following command with administrator rights: "%WINDIR%\system32\RegSvr32.exe" "%CommonProgramFiles%\siemens\AlmPanelPlugin \ALMPanelParam.dll" Using the mouse wheel in Runtime The use of the mouse wheel in Runtime is not supported on all panels. 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 Basic Panels: Connections to S7-1200 and S7-1500 with Backup/Restore If you use the "Backup/Restore" function, a maximum of two connections from Basic Panels to the controllers are possible at any given time. SIMATIC S7-1200 SIMATIC S7-1500 68 WinCC Basic V13.0 System Manual, 02/2014 Readme 2.3 WinCC Basic Basic Panels: Backup on the memory card of the PLC Create the backup file "A.psb" on the memory card of the PLC. An error, for example a connection break, occurs when creating the backup. This will create a corrupt file on the memory card of the PLC. Such a file has "~$" as prefix. Delete the file with the prefix "~$" if you want to save a backup again under the same name "A.psb". Basic Panels: Panel Data Storage and S7-1500F The "Panel Data Storage" PDS function cannot be used on Basic Panels in conjunction with S7-1500F when the password for the protection level "Full access incl. fail-safe" is used. 2.3.9 HMI devices 2.3.9.1 Notes on HMI devices Contents Information that could no longer be included in the online help and important information about product features. 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. Multi-key operation Unintentional actions can be triggered by multi-key operation: When you are using a key device, you cannot press more than two function keys at the same time. When you are using a touch device, a standard PC or a panel PC, you can only press one function key or button at the same time. 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. WinCC Basic V13.0 System Manual, 02/2014 69 Readme 2.3 WinCC Basic 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. 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. Mobile Panels V2 If you use Mobile Panels V2 in a project, it is not possible to open the project with WinCC V11 SP1. This affects projects with the following devices: Mobile Panel 277F IWLAN (RFID Tag) Mobile Panel 277F IWLAN V2 Mobile Panel 277 IWLAN V2 "Zone ID/Connection point ID" tag of a Mobile Panel 277 IWLAN V2 The tag used for the "Zone ID/Connection point ID" must be of data type INT for Mobile Panel 277 IWLAN V2 devices. Adapt this data type if necessary when migrating a project. HMI devices with operating system Windows CE 5.0 or higher Owing to a modified client-server communication security setting, the time difference between the HMI device (client) and PC (server) must not exceed 1 day. If you back up recipe data from the HMI device on a network drive, for example, make sure that the time is set correctly on the PC (server) and the HMI device (client). 70 WinCC Basic V13.0 System Manual, 02/2014 Readme 2.3 WinCC Basic HMI devices with high communication load S7 Diagnostics should be enabled if a Panel is assigned many connections to PLCs or other HMI devices. Otherwise, you will risk overload on the Panel. Device replacement in the engineering system In the engineering system, you replace a device with configured LED keys with a device without LED keys. Runtime start fails after you have transferred the project data to the device. For this reason, delete the LED key configuration before you replace the device. Restrictions for the HMI device, MP 377 15" Touch daylight readable The following functions are not supported in WinCC V12 for the MP 377 15" Touch daylight readable HMI device: Option: Sm@rtServer System function: SetAndGetBrightness Direct keys Upgrading Basic Panels to WinCC V13 Before you upgrade Basic Panels from version V12 to version V13, transfer the image of the V12 SP2 Update 5 or higher to the devices. In the "SIMATIC ProSave [OS Update]" dialog, select the setting "Reset to factory settings". In this way, you always start a functional update of the image. Affected devices: KP300 Basic mono PN KP400 Basic color PN KTP400 Basic color PN Connection switch in the Control Panel with Basic Panels If you use the "Override protected connection information" function, the following restriction applies: You cannot perform a connection switch in the Control Panel of a Basic Panel from a PLC without a protection level to a PLC with a "Complete protection" level. Mobile Panels 277F 8'' IWLAN Mobile Panels 277F 8" IWLAN V2 and 277F 8" IWLAN (RFID Tag) cannot be configured with WinCC V13. Basic Panels 2nd Generation Basic Panel KTP1200 Basic can currently not be configured with WinCC V13. WinCC Basic V13.0 System Manual, 02/2014 71 Readme 2.3 WinCC Basic The following maximum values are in effect for Basic Panels 2nd Generation. Alarms Number of discrete alarms KTP400 Basic KTP700 Basic KTP900 Basic KTP1200 Basic 1000 1000 1000 1000 KTP400 Basic KTP700 Basic KTP900 Basic KTP1200 Basic Screens Number of complex objects per screen 1) This information is not relevant for Basic Panels 2nd Generation. Number of system diagnostic displays per screen 5 5 5 5 Number of array elements per screen 2) 100 100 100 100 1) Complex objects include: Bars, sliders, symbol library, clock, and all objects from the Controls area. 2) Array elements contained in recipes are included in the count. Logs KTP400 Basic KTP700 Basic KTP900 Basic KTP1200 Basic Number of entries per log (including all log segments) 1) 10000 10000 10000 10000 Number of log segments 400 400 400 400 Number of tags that can be logged per log 10 10 10 10 Cyclic trigger for tag logging 1s 1s 1s 1s 72 WinCC Basic V13.0 System Manual, 02/2014 Installation 3.1 3 Notes on the installation Contents Information that could not be included in the online help and important information about product characteristics. Automated Installation A description of automated installation is available on the product DVD in the directory "Documents\Readme\<Language directory>". Using the same versions of TIA Portal products The TIA Portal products STEP 7 (incl. PLCSIM), WinCC and Startdrive must be upgraded to the same version (V13). If the versions are different, you will no longer be able to start the TIA Portal. Even uninstalling a product will not restore an operational status. Please ensure that you have the service packs for these products to hand before you start the installation. You can download the service packs from the Internet under Siemens Industry online support (http:// support.automation.siemens.com/WW/llisapi.dll?aktprim=99&lang=en&referer=%2fWW %2f&func=cslib.csinfo2&siteid=csius&extranet=standard&viewreg=WW&groupid=4000002). Target directory of the installation Do not use any UNICODE characters (for example, Chinese characters) in the installation path. Use of antivirus programs During the installation, read and write access to already installed files is necessary. Some antivirus programs block this access. We therefore recommend that you disable antivirus programs during the installation of the TIA Portal and enable them again afterwards. WinCC Basic V13.0 System Manual, 02/2014 73 Installation 3.2 System requirements for installation 3.2 System requirements for installation 3.2.1 Notes on 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. Before you uninstall the TIA Portal, you must transfer and back up the licenses still required. Use the Automation License Manager for this purpose. Provision of the Automation License Manager The Automation License Manager is supplied on the installation data medium and is transferred automatically during the installation process. If you remove the TIA Portal, the Automation License Manager remains installed on your system. Working with the Automation License Manager The Automation License Manager is a product of Siemens AG, which is used for handling license keys (technical representatives of licenses). Software products that require license keys for operation, such as the TIA-Portal, register the required license key automatically with the Automation License Manager . If the Automation License Manager finds a valid license key for this software, the software can be used according to the license usage terms associated with this license key. Note For additional information on how to manage your licenses with the Automation License Manager , refer to the documentation supplied with the Automation License Manager . See also Notes on the system requirements (Page 75) Starting installation (Page 93) Displaying the installed software (Page 97) Modifying or updating installed products (Page 98) Repairing installed products (Page 99) 74 WinCC Basic V13.0 System Manual, 02/2014 Installation 3.2 System requirements for installation Starting to uninstall (Page 101) Installation log (Page 92) 3.2.2 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 Notes on licenses (Page 74) Starting installation (Page 93) Displaying the installed software (Page 97) Modifying or updating installed products (Page 98) Repairing installed products (Page 99) Starting to uninstall (Page 101) WinCC Basic V13.0 System Manual, 02/2014 75 Installation 3.2 System requirements for installation 3.2.3 System requirements STEP 7 Basic 3.2.3.1 Licensing of STEP 7 Introduction You require a License Key to license the following STEP 7 editions: STEP 7 Basic STEP 7 Professional You can install the corresponding License Key when you are installing STEP 7 or transfer it using the Automation License Manager after the installation has been completed. Licenses for STEP 7 The following licenses with the corresponding license keys are available: STEP 7 Basic STEP 7 Professional STEP 7 Professional Combo 76 WinCC Basic V13.0 System Manual, 02/2014 Installation 3.2 System requirements for installation Validity of license keys for older versions of STEP 7 With a valid License Key for V13.x of STEP 7 Professional and STEP 7 Professional Combo, you can also operate older versions of STEP 7 without restrictions. The following table provides more detailed information about this: Edition License Valid for STEP 7 Basic V13.x STEP 7 Basic STEP 7 Basic V13.x STEP 7 Basic V12.x STEP 7 Basic V11.x STEP 7 Basic V10.5 STEP 7 Professional V13.x STEP 7 Professional STEP 7 Professional V13.x STEP 7 Professional V12.x STEP 7 Professional V11.x STEP 7 Basic V13.x STEP 7 Basic V12.x STEP 7 Basic V11.x STEP 7 Basic V10.5 STEP 7 Professional V13.x STEP 7 Professional Combo STEP 7 Professional V13.x STEP 7 Professional V12.x STEP 7 Professional V11.x STEP 7 Basic V13.x STEP 7 Basic V12.x STEP 7 Basic V11.x STEP 7 Basic V10.5 STEP 7 V5.5 STEP 7 V5.4 STEP 7 Professional 2010 STEP 7 Professional 2006 Starting without a valid license key If you start an edition of STEP 7 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. However, this license is valid for a limited period only and expires after 21 days. When the Trial License expires, the following scenarios can occur: STEP 7 has never been licensed on the PC in question: - Operations requiring a license can no longer be performed in STEP 7. STEP 7 was already licensed on the PC in question: - A window requiring acknowledgment presents an alert for non-licensed mode every 10 minutes and for every action requiring a license. WinCC Basic V13.0 System Manual, 02/2014 77 Installation 3.2 System requirements for installation License requirements for simulation You do not require additional licenses when you use the menu command "Online > Simulation" to start the simulation in STEP 7. If the following conditions are met, the appropriate licenses for the edition of STEP 7 you have installed are also required for the simulation. The engineering station is connected to a PLC. The connection to the PLC is configured and active. See also Handling licenses and license keys (Page 78) 3.2.3.2 Handling licenses and license keys Introduction In each case, you require a valid License Key to use STEP 7 Basic and STEP 7 Professional. Installing license keys When you install STEP 7 Basic, the License Key is installed automatically during setup. When you install STEP 7 Professional you will be prompted at the end of the setup to transfer the license from the supplied storage medium to your PC. If you want to install additional License Keys, you have to use the Automation License Manager to do this. When you install a license, the associated license key is removed from the license key storage location. NOTICE Destruction of license keys by copying It is not possible to copy a License Key. The copy protection prevents the license keys from being copied. If you attempt to copy a License Key this will be destroyed. Uninstalling license keys License keys are always uninstalled using the Automation License Manager. You uninstall a License Key in the following cases: When backing up data. If you no longer require the license. You can then use a valid license on another PC or HMI device. 78 WinCC Basic V13.0 System Manual, 02/2014 Installation 3.2 System requirements for installation Data backup When backing up data on the HMI device or creating a backup during device replacement, remove the License Keys on the HMI device. To do this, open the Automation License Manager and back up the uninstalled license key to another storage location. NOTICE 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. Before you start an optimization program that moves fixed blocks. Before you install a new operating system. Read the description of Automation License Manager ("Start > Siemens Automation > Documentation"). Observe all warnings and notices. On PC-based HMI devices and on non-PC-based HMI devices where Automation License Manager is used, the license key storage location may contain multiple license keys. This capability means you can store multiple licenses of the same type at one location. Save all license keys of an HMI device to the same storage location. NOTICE 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 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 using the Automation License Manager under the time zone setting that was set when the license key was installed. 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 location. If the license key disappears during its transfer to the destination drive. You can use the Automation License Manager to repair the defective license. To do this, use the "Restore" function or the "Restore wizard" of the Automation License Manager. To perform this restore operation you must contact Customer Support. WinCC Basic V13.0 System Manual, 02/2014 79 Installation 3.2 System requirements for installation You can find more detailed information on the Internet: http://support.automation.siemens.com (http://support.automation.siemens.com/WW/llisapi.dll?aktprim=99&lang=en&referer= %2fWW %2f&func=cslib.csinfo2&siteid=csius&extranet=standard&viewreg=WW&groupid=4000002) See also Licensing of STEP 7 (Page 76) 3.2.3.3 Software and hardware requirements STEP 7 System requirements for installation The following table shows the minimum software and hardware requirements for installation of the "SIMATIC STEP 7 Basic" software package: Hardware/software Requirement Processor Intel(R) Celeron(R) Dual Core 2.2 GHz (Ivy/Sandy Bridge) RAM 4 GB Available hard disk space 5 GB Operating systems * Windows 7 (32-bit) Windows 7 Home Premium SP1 Windows 7 Professional SP1 Windows 7 Enterprise SP1 Windows 7 Ultimate SP1 Windows 7 (64-bit) Windows 7 Home Premium SP1 Windows 7 Professional SP1 Windows 7 Enterprise SP1 Windows 7 Ultimate SP1 Windows 8.1 (64-bit) Windows 8.1 Windows 8.1 Professional Windows 8.1 Enterprise Windows Server (64-bit) Windows Server 2012 R2 StdE (full installation) Screen resolution 1024 x 768 * For more detailed information on operating systems, refer to the help on Microsoft Windows or the Microsoft homepage. 80 WinCC Basic V13.0 System Manual, 02/2014 Installation 3.2 System requirements for installation Recommended software and hardware requirements The following table shows the recommended software and hardware for the operation of STEP 7. Hardware/software Requirement Computer From SIMATIC FIELD PG M4 PREMIUM (or similar PC) Processor From Intel(R) CoreTM i5-3320M 3.3 GHz RAM 8 GB or more Hard disk 300 GB SSD Monitor 15.6" Wide Screen Display (1920 x 1080) Operating systems * Windows 7 (64-bit) Windows 7 Home Premium SP1 Windows 7 Professional SP1 Windows 7 Enterprise SP1 Windows 7 Ultimate SP1 Windows 8.1 (64-bit) Windows 8.1 Windows 8.1 Professional Windows 8.1 Enterprise Windows Server (64-bit) Windows Server 2012 R2 StdE (full installation) * For more detailed information on operating systems, refer to the help on Microsoft Windows or the Microsoft homepage Supported virtualization platforms You can install the "SIMATIC STEP 7 Basic" software package on a virtual machine. For this purpose, use one of the following virtualization platforms in the specified version or a newer version: VMware vSphere Hypervisor (ESXi) 5.5 VMware Workstation 10 VMware Player 6.0 Microsoft Windows Server 2012 R2 Hyper-V These virtualization platforms can use the following operating systems as host operating system: Windows 7 Professional/Ultimate/Enterprise (64-bit) Windows Server 2008 R2 (64-bit) Windows Server 2012 R2 (64-bit) Windows 8.1 Professional/Enterprise (64-bit) You can use the following host operating systems to install "SIMATIC STEP 7 Basic" within the selected virtualization platform: WinCC Basic V13.0 System Manual, 02/2014 81 Installation 3.2 System requirements for installation Windows 7 Professional/Ultimate/Enterprise (64-bit) Windows 8.1 Professional/Enterprise (64-bit) Note The same hardware requirements apply to the host operating system as for the respective TIA products. The plant operator must ensure that sufficient system resources are available for the host operating systems. The hardware certified by the manufacturers is recommended for the use of HyperV server and ESXi. When you use Microsoft Hyper-V, accessible stations cannot be displayed. Supported security programs The following security programs are compatible with "SIMATIC STEP 7 Basic": Antivirus programs: - Symantec Endpoint Protection 12.1 - Trend Micro Office Scan Corporate Edition 10.6 - McAfee VirusScan Enterprise 8.8 - Kaspersky Anti-Virus 2014 - Windows Defender (as of Windows 8.1) Encryption software: - Microsoft Bitlocker Host-based Intrusion Detection System: - McAfee Application Control 6.0 82 WinCC Basic V13.0 System Manual, 02/2014 Installation 3.2 System requirements for installation 3.2.4 System requirement for WinCC Basic 3.2.4.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. If this happens, remove the computer from the domain prior to installing Microsoft Message Queuing, Microsoft SQL Server 2005 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 the installation of the "SIMATIC WinCC Basic" software package: Hardware/software WinCC Basic V13.0 System Manual, 02/2014 Requirement Processor type Intel(R) Celeron(R) Dual Core 2.2 GHz (Ivy/Sandy Bridge) RAM 4 GB Free hard disk space 5 GB 83 Installation 3.2 System requirements for installation Hardware/software Requirement Operating systems * Windows 7 (32 bit) Windows 7 Home Premium SP1 Windows 7 Professional SP1 Windows 7 Enterprise SP1 Windows 7 Ultimate SP1 Windows 7 (64 bit) Windows 7 Home Premium SP1 Windows 7 Professional SP1 Windows 7 Enterprise SP1 Windows 7 Ultimate SP1 Windows 8 (64 bit) Windows 8.1 Windows 8.1 Professional Windows 8.1 Enterprise Windows Server (64 bit) Windows Server 2012 R2 Standard Edition Screen resolution 1024x768 Network Ethernet 10 Mbps or faster Optical drive DVD-ROM Software Microsoft .Net Framework 4.5 * For additional information on the operating systems, refer to the Microsoft Windows help 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. 84 Hardware Requirement Computer SIMATIC FIELD PG M4 PREMIUM or higher (or comparable PC) Processor Intel(R) CoreTM i5-3320M 3.3 GHz or higher RAM 8 GB or more Hard disk 300 GB SSD WinCC Basic V13.0 System Manual, 02/2014 Installation 3.2 System requirements for installation Hardware Requirement Monitor 15.6" Wide Screen Display (1920 x 1080) Optical drive DL MULTISTANDARD DVD RW Supported virtualization platforms You can install the "SIMATIC WinCC Basic" software package on a virtual machine. To do this, use one of the following virtualization platforms: VMware vSphere Hypervisor (ESXi) 5.5 VMware Workstation 10 VMware Player 6.0 Microsoft Windows Server 2012 R2 Hyper-V The following operating systems can serve as a host operating system for these virtualization platforms: Windows 7 Professional/Ultimate/Enterprise (64-bit) Windows 8.1 Professional/Enterprise (64-bit) Windows Server 2008 R2 (64-bit) Windows Server 2012 R2 (64-bit) You can use the following guest operating systems to install "SIMATIC WinCC Basic" on the selected virtualization platform: Windows 7 Professional/Ultimate/Enterprise (64-bit) Windows 8.1 Professional/Enterprise (64-bit) Note The same hardware requirements apply to the guest operating system as to the respective TIA products. The plant operator must provide sufficient system resources for the guest operating systems. The hardware certified by the manufacturers is recommended for the use of HyperV server and ESXi. WinCC Basic V13.0 System Manual, 02/2014 85 Installation 3.2 System requirements for installation Supported security programs The following security programs are compatible with "SIMATIC WinCC Basic": Virus scanners: - Symantec Endpoint Protection 12.1 - Trend Micro Office Scan Corporate Edition 10.6 - McAfee VirusScan Enterprise 8.8 - Kaspersky Anti-Virus 2014 - Windows Defender (Windows 8.1 and higher) Encryption software: - Microsoft Bitlocker Host-based Intrusion Detection System: - McAfee Application Control 6.0 Installing Microsoft .Net Framework The software requires .Net Framework 4.5; it is automatically installed and activated. You will be prompted to install the required .Net Framework version if this cannot be performed by the software package installation. A restart may be necessary after installation of .Net Framework. Online help for Windows 7 / Windows Server 2008 Windows 7 and Windows Server 2008 no longer support all online help formats by default. These online help formats are used in WinCC in the following scenarios: Call-up of WinCC Direct Help Call-up of the WinCC Information System from the WinCC editors or via the Direct Help links In order to still call WinCC Direct Help, the following component is installed during the installation of WinCC: Microsoft Help Engine You can also call the WinCC Information System in 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) Security settings during installation When you install WinCC V13, security settings are changed in your operating system. The security settings in question are listed during the installation. 86 WinCC Basic V13.0 System Manual, 02/2014 Installation 3.2 System requirements for installation You must confirm the changes to the security settings. If you make changes to your operating system after the installation, the changes to the security settings made by the installation of the TIA Portal could be changed. You can restore the changes to the security settings made by the installation of the TIA Portal: "Start > All Programs > Siemens Automation > Security Controller > Restore settings". SQL instance of WinCC V13 If you have installed a WinCC V11 product and you wish to install WinCC V13, you must uninstall the WinCC instance of SQL Server 2005 before the installation. A new WinCC SQL 2008 instance is installed with the installation of WinCC V13. See also Licensing of WinCC Engineering System (Page 88) 3.2.4.2 Parallel installation Parallel installations in TIA Portal V13 You will be prevented from starting the TIA Portal if you perform a non-permitted parallel installation of STEP 7 and WinCC. The following parallel installations are permitted in the TIA portal: STEP 7 V13 and WinCC V13 A dialog opens during installation to inform you of any inconsistencies in your parallel installation. The following parallel installations are permitted: WinCC V13 and RT Advanced V13 WinCC V13 and RT Professional V13 The engineering system and Runtime must always be of the same version after an installation. Parallel installation of WinCC V13 and other SIMATIC HMI products Parallel installation of WinCC V13 and versions of WinCC flexible earlier than WinCC flexible 2008 SP1 is not allowed. Parallel installation of WinCC V13 with versions of WinCC earlier than WinCC V7.0 SP2 is not allowed. Parallel installation of WinCC V13 with WinCC V7.0 SP2 or WinCC V7.0 SP3 is only allowed for: WinCC V 13 Professional WinCC V 13 Professional WinCC Basic V13.0 System Manual, 02/2014 87 Installation 3.2 System requirements for installation Parallel use If the term "Combo" appears in the name or license key of the software after installation, the use of the following products/versions is permitted in accordance with paragraph 1.6 of the General Terms and Conditions (see also setup text): With license for "WinCC V13 Comfort Combo": WinCC flexible 2008 Standard With license for "WinCC V13 Advanced Combo": WinCC flexible 2008 Advanced 3.2.4.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 licenses for the 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 nonlicensed mode. You have the one-time option of activating a trial license. The trial license for Engineering editions WinCC Basic, Comfort/Advanced, and Professional expires after 21 days. When the trial license has expired, the following scenarios may occur: WinCC was never licensed on the PC in question. - Operations requiring a license can no longer be performed in WinCC. WinCC was already licensed on the PC in question. - Non-licensed mode is indicated every 10 minutes and at every action requiring a license by a window, which you must acknowledge. License requirements for simulation When you want to start simulation in WinCC using the "Online > Simulation> With tag simulator" menu command, you do not need licenses for WinCC Runtime or for add-ons that require a license. If the following conditions are met, you will need the appropriate licenses for WinCC Runtime and add-ons that require a license even for simulation: 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. 88 WinCC Basic V13.0 System Manual, 02/2014 Installation 3.2 System requirements for installation See also Software and hardware requirements (Page 83) Licensing of HMI devices (Page 89) Working with license keys (Page 90) Licensing of HMI devices Non-PC-based HMI devices are always equipped with "Runtime licenses". A license key is not required for runtime operation. A license may be required for an add-on for non-PC-based HMI devices. The license key of the respective license always activates one add-on for use. License key In order to license non-PC-based HMI devices with license keys, the "SIMATIC HMI License Manager Panel Plugin" add-on is needed. WinCC Setup installs this add-on by default. You open the License Manager Panel Plugin in the Automation License Manager with the "Edit > Connect Target System > Connect HMI Device" menu command. If WinCC is not installed, an installation of ProSave 7.2 or higher is required. Note Further information on license handling can be found in the Automation License Manager help. Note Verify that the current version of the operating system (or higher) is installed on the HMI device before you start licensing. If necessary, update the operating system using ProSave. Non-licensed mode Runtime add-ons can be used for a short time without restrictions without a valid license. Nonlicensed mode is indicated every 10 minutes by a window, which you must acknowledge. See also Licensing of WinCC Engineering System (Page 88) WinCC Basic V13.0 System Manual, 02/2014 89 Installation 3.2 System requirements for installation Working with license keys Introduction You transfer a license key to the HMI device in the following cases: To use 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 You transfer a license key from the HMI device in the following cases: When backing up data If you no longer require the license You can then use this license on another PC or HMI device. When you transfer a license to an HMI device, 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 You transfer the license keys from the HMI device for data backup on the HMI device or as a backup for device replacement. You use the Automation License Manager to back up license keys from an HMI device to the storage area of the license keys. NOTICE Destruction of license keys on non-PC-based HMI devices License keys transferred as a result of backup/restore operations are destroyed in the case of the following HMI devices. 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. Transfer the license keys present on the HMI device to a storage location. After restoring has been carried out, transfer the license keys back to the HMI device. 90 WinCC Basic V13.0 System Manual, 02/2014 Installation 3.2 System requirements for installation NOTICE Destruction of license keys on PCs Transfer all license keys to a storage location in the following cases: Before you format the hard disk Before you compress the hard disk Before you restore the hard disk Starting an optimization program that moves fixed blocks Installing a new operating system Read the description of Automation License Manager ("Start > Simatic Automation > Documentation"). Observe all warnings and notices. The license key storage location on PC-based HMI devices and on non-PC-based HMI devices where Automation License Manager is used may contain multiple license keys. This capability means you can store multiple licenses of the same type at one location. For the backup, use a single storage location for all license keys present on an HMI device. Note Always keep the original storage location of the license keys. Invalid license after time zone change The transferred 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 work around this, transfer the license key from the HMI device with a time zone setting that was set when the license key was transferred to the HMI device. Example: You transferred the license key to the HMI device with a time zone setting based on a full hour. Then, also transfer the license key from the HMI device 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. WinCC Basic V13.0 System Manual, 02/2014 91 Installation 3.3 Installation log Note Resetting of the system date to an earlier time causes all licenses to be become defective. 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. You must 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. Note If you start the 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 has expired, the following scenarios may 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 can be started. Non-licensed mode is indicated every 10 minutes by a window, which you must acknowledge. See also Licensing of WinCC Engineering System (Page 88) 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. 92 WinCC Basic V13.0 System Manual, 02/2014 Installation 3.4 Starting installation Installation logs storage location The log file is the most recent file with the file extension ".log" and the name of which that starts with "SIA". 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 Notes on licenses (Page 74) Starting installation (Page 93) Checking availability of updates and support packages and installing them (Page 95) Displaying the installed software (Page 97) Modifying or updating installed products (Page 98) Repairing installed products (Page 99) Starting to uninstall (Page 101) 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. WinCC Basic V13.0 System Manual, 02/2014 93 Installation 3.4 Starting installation 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". 94 WinCC Basic V13.0 System Manual, 02/2014 Installation 3.5 Checking availability of updates and support packages and installing them 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. Following installation, you will receive a message indicating whether the installation was successful. 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 92) Notes on the system requirements (Page 75) Notes on licenses (Page 74) Displaying the installed software (Page 97) Modifying or updating installed products (Page 98) Repairing installed products (Page 99) Starting to uninstall (Page 101) 3.5 Checking availability of updates and support packages and installing them In the TIA Portal, you have the option of checking whether new software updates or support packages are available, for example, Hardware Support Packages (HSPs). If this is the case, you can then install the software. Note Updates and support packages from TIA Portal V13 or higher are supported. WinCC Basic V13.0 System Manual, 02/2014 95 Installation 3.5 Checking availability of updates and support packages and installing them Procedure To check the availability of software updates and support packages and then install these, follow these steps: 1. Use one of the two following methods to start the installation process: - Click "Installed software" in the "Help" menu in the TIA Portal. The "Installed software" dialog opens. - Open the "Siemens TIA Updater" program using the program link on your computer. The "Siemens TIA Updater" dialog is opened and the available software packages are displayed. 2. Click "Check for updates". This step is optional if the "Siemens TIA Updater" dialog is already open. If you started the installation procedure in the TIA Portal, the "Siemens TIA Updater" dialog is opened and the available updates are displayed. 3. Click "Download" in the line of the update or support package that you want to install. The update or support package is downloaded. The associated "Install" button becomes active as soon as the download process has been completed. Note Please note the following: 1. You can initiate multiple download processes simultaneously. 2. You can log off or also shut down the computer while the download process is running. In such cases, the download process continues in the background as soon as you log on again. 4. Close the TIA Portal if it is still open. 5. In the "Siemens TIA Updater" dialog, click the "Install" button of the software package you want to install. The installation dialog appears. Note Please note the following: 1. It is not possible to install multiple updates simultaneously. 2. Do not log off during an installation and do not shut down the computer. This avoids inconsistent versions of the software on your computer. 6. Click "Next". The selected product is installed. 96 WinCC Basic V13.0 System Manual, 02/2014 Installation 3.6 Displaying the installed software Alternative procedures for the installation of support packages Another procedure is available for the installation of a support package. To do this, follow these steps: 1. Click "Support packages" in the "Options" menu in the TIA Portal. 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 92) 3.6 Displaying the installed software You can find out which software is installed at any time. In addition, you can display more information on the installed software. Procedure To display an overview of the software installed, follow these steps: 1. Click "Installed software" in the "Help" menu. The "Installed software" dialog opens. You will see the installed software products in the dialog. Expand the entries to see which version is installed in each case. 2. If you would like to display additional information on the installed automation software, click the link on the "Detailed information about installed software" dialog. The "Detailed information" dialog opens. 3. Chose the topic you want more information about in the area navigation. See also Notes on the system requirements (Page 75) Notes on licenses (Page 74) Starting installation (Page 93) WinCC Basic V13.0 System Manual, 02/2014 97 Installation 3.7 Modifying or updating installed products Modifying or updating installed products (Page 98) Repairing installed products (Page 99) Starting to uninstall (Page 101) Installation log (Page 92) 3.7 Modifying or updating installed products You have the option to modify installed products using the setup program or to update to a new version. Requirement Hardware and software of the programming device or PC meet the system requirements. You have administrator privileges on your computer. All running programs are closed. Procedure To modify or update installed products, follow these steps: 1. Insert the installation medium in the relevant drive. The setup program starts automatically unless you have disabled Autostart on the programming device or PC. 2. If the setup program does not start up automatically, start it manually by double-clicking the "Start.exe" file. The dialog for selecting the setup language opens. 3. Choose the language in which you want the setup program dialogs to be displayed. 4. To read the information on the product and installation, click the "Read Notes" or "Installation Notes" button. The help file containing the notes opens. 5. Once you have read the notes, close the help file and click the "Next" button. The dialog for selecting the installation variant opens. 6. Select the "Modify/Upgrade" option button and click the "Next" button. The dialog for selecting the product languages opens. 7. Select the check boxes of the product languages that you want to install. You can remove previously installed product languages by clearing the corresponding check boxes. Note Note that the product language "English" cannot be removed. 8. Click the "Next" button. The dialog for selecting the product configuration opens. 98 WinCC Basic V13.0 System Manual, 02/2014 Installation 3.8 Repairing installed products 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 Following installation, you will receive a message indicating whether the existing installation was successfully changed. 13.It may be necessary to restart the computer. If this is the case, select the "Yes, restart my computer now." option button. Then click "Restart". 14.If the computer does not reboot, click "Exit". Result The existing installation has been modified on your computer. See also Notes on the system requirements (Page 75) Notes on licenses (Page 74) Starting installation (Page 93) Displaying the installed software (Page 97) Repairing installed products (Page 99) Starting to uninstall (Page 101) Installation log (Page 92) 3.8 Repairing installed products You have the option to repair installed products by completely reinstalling them using the setup program. WinCC Basic V13.0 System Manual, 02/2014 99 Installation 3.8 Repairing installed products Requirement Hardware and software of the programming device or PC meet the system requirements. You have administrator privileges on your computer. All running programs are closed. Procedure To repair installed products, follow these steps: 1. Insert the installation medium in the relevant drive. The setup program starts automatically unless you have disabled Autostart on the programming device or PC. 2. If the setup program does not start up automatically, start it manually by double-clicking the "Start.exe" file. The dialog for selecting the setup language opens. 3. Choose the language in which you want the setup program dialogs to be displayed. 4. To read the information on the product and installation, click the "Read Notes" or "Installation Notes" button. The help file containing the notes opens. 5. Once you have read the notes, close the help file and click the "Next" button. The dialog for selecting the installation variant opens. 6. Select the "Repair" option button, and click the "Next" button. The next dialog displays an overview of the installation settings. 7. Click the "Repair" button. This starts the repair of the existing installation. Note Following installation, you will receive a message indicating whether the existing installation was successfully repaired. 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 75) Notes on licenses (Page 74) Starting installation (Page 93) Displaying the installed software (Page 97) 100 WinCC Basic V13.0 System Manual, 02/2014 Installation 3.9 Starting to uninstall Modifying or updating installed products (Page 98) Starting to uninstall (Page 101) Installation log (Page 92) 3.9 Starting to uninstall Introduction Software packages are removed automatically by the setup program. Once started, the setup program guides you step-by-step through the entire removal procedure. You have two options for removing: Removing selected components via the Control Panel Removing a product using the installation medium Note The Automation License Manager will not be removed automatically when you remove the software packages, because it is used for the administration of several license keys for products supplied by Siemens AG. Removing selected components via the Control Panel To remove selected software packages, follow these steps: 1. Open the Control Panel with "Start > Settings > Control Panel". 2. Double click on "Add or Remove Programs" in the control panel. The "Add or Remove Programs" dialog opens. 3. Select the software package to be removed in the dialog "Add or Remove Programs", and click "Remove". The dialog for selecting the setup language opens. 4. Select the language in which you want the dialogs of the setup program to be displayed and click "Next". 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 "Next". 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". WinCC Basic V13.0 System Manual, 02/2014 101 Installation 3.9 Starting to uninstall 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 "Read product information" or "Read installation notes". The help file containing the notes opens. 5. Once you have read the notes, close the help file and click the "Next" button. The dialog for selecting the installation variant opens. 6. Select the "Uninstall" option button and click the "Next" button. The next dialog displays an overview of the installation settings. 7. Click the "Uninstall" button. Removal begins. 8. It may be necessary to restart the computer. If this is the case, select the "Yes, restart my computer now." option button. Then click "Restart". 9. If the computer does not reboot, click "Exit". See also Installation log (Page 92) Notes on the system requirements (Page 75) Notes on licenses (Page 74) Starting installation (Page 93) Displaying the installed software (Page 97) Modifying or updating installed products (Page 98) Repairing installed products (Page 99) 102 WinCC Basic V13.0 System Manual, 02/2014 Installation 3.10 Installing and uninstalling the migration tool 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: - WinCC flexible 2008 SP2 and SP3 - WinCC V7.0 SP3 - STEP 7 V5.5 - Integrated projects from STEP 7 V5.5 and the WinCC products listed above - SINUMERIK - STARTER and Startdrives - SIMOTION SCOUT V4.4 You need the SCOUT Migration Tool PlugIn V4.4 to migrate SIMOTION SCOUT V4.4 projects. 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 You can find the migration tool in the "Support" directory on the installation DVD of the TIA Portal. Alternatively, it can be downloaded from the Service & Support area of the Siemens website. For some products, (such as SIMATIC Failsafe or SIMOTION) additional plug-ins are required for the migration tool. These plug-ins can also be downloaded from the Service & Support page or installed from the installation DVD of the specific products. 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. WinCC Basic V13.0 System Manual, 02/2014 103 Installation 3.10 Installing and uninstalling the migration tool Procedure To install the migration tool, proceed as follows: 1. Download the installation DVD from the Service & Support area of the Siemens website or use the installation file from the "Support" directory of the installation DVD of the TIA portal to perform the installation. 2. Run the installation 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 entry for the migration tool in the "Add or Remove Programs" dialog, and click the "Remove" button. A security prompt appears. 4. Click the "Uninstall" button to confirm this prompt. The migration tool will be removed. 104 WinCC Basic V13.0 System Manual, 02/2014 Migrating projects and programs 4.1 Migrating projects in a TIA portal project 4.1.1 Migration of projects with the TIA Portal 4 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 TIA Portal projects already open are closed first. The migration is then displayed in the table of the project history. From there, you have access to the migration log 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 Siemens Industry Online Support and the documentation of your software products. See also: Scaling of STEP 7 and WinCC in the TIA Portal (Page 25) Procedure during migration The migration process is divided into the following basic steps: 1. Preparing the initial project If the software for editing the initial project is not or not fully installed on the programming device/PC with the TIA Portal, or if the initial project is an integrated project, the initial project must first be converted into a migration file. To do this, install the migration tool on a programming device/PC on which the required software for editing the initial project 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, and if the initial project is not an integrated project. 2. Performing migration Perform the actual migration within the TIA Portal. For the migration, specify as source either the migration file which you created with the migration tool or the initial project when all required software has been installed. WinCC Basic V13.0 System Manual, 02/2014 105 Migrating projects and programs 4.1 Migrating projects in a TIA portal project 3. Checking the migration log A migration log is created for each migration. It contains information about modified project parts. You can call the log under "Common data > Logs" in the project tree or in the project history. After completion of the migration, the migration log will be displayed in the TIA Portal. Check the log following completion of the migration. If the migration failed, an XML file is created as a log under "\Logs" in the project directory. You can use any XML editor to open this log and view the reasons why the migration failed. 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. If you have not included the hardware configuration in the migration, you also have to convert the unspecified devices to the appropriate hardware. Including the hardware configuration in the migration By default, only the software parts of the project are included in the migration. An unspecified device is 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. If you are certain that the hardware used in the initial project has a corresponding equivalent in the TIA Portal, you can include the hardware configuration in the migration. In this case, both the hardware configuration and the software are migrated. See also Display migration log (Page 111) Scaling of STEP 7 and WinCC in the TIA Portal (Page 25) 4.1.2 Preparing projects with the migration tool 4.1.2.1 Migrating projects with the migration tool Preparation for migration In many cases, a project that you wish to migrate will not be located on the same programming device/PC on which the latest version of the TIA Portal is installed. Therefore, the initial project must first be converted to a compatible format for the migration. The same applies to integrated projects. After creation of the migration file, you copy the migration file to the programming device/PC on which the current version of the TIA Portal is installed. In the TIA Portal, enter the migration file as source for the migration. You can now create a project in the current file format of the TIA Portal. 106 WinCC Basic V13.0 System Manual, 02/2014 Migrating projects and programs 4.1 Migrating projects in a TIA portal project Procedure for migration with the migration tool The following steps are necessary to prepare a migration with the migration tool: 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 Siemens Industry Online Support or install the migration tool from the setup DVD of the TIA Portal. 2. Start the migration tool, and use it to convert the source project to the migration file format with file extension ".am13". 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 with the extension ".am13" as the source. 5. Once migration is complete, check the migration log and systematically work through the information provided there for the newly created project. Read the information in the Inspector window with special care after the first compilation of the configuration. Including the hardware configuration in the migration By default, only the software parts of the project are included in the migration. An unspecified device is 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. If you are certain that the hardware used in the initial project has a corresponding equivalent in the TIA Portal, you can include the hardware configuration in the migration. In this case, both the hardware configuration and the software are migrated. See also Migration of projects with the TIA Portal (Page 105) Migrating projects (Page 109) Calling the migration tool (Page 108) Creating a migration file (Page 108) WinCC Basic V13.0 System Manual, 02/2014 107 Migrating projects and programs 4.1 Migrating projects in a TIA portal project 4.1.2.2 Calling the migration tool Starting the migration tool During the installation, a "Migration to TIA Portal V13" shortcut is created as standard in the Start menu under "Siemens Automation > Migration Tool". Click this shortcut. Alternatively, you can call the migration tool directly in Windows Explorer. During the installation, the migration tool is saved by default in one of the following folders: On a 64-bit operating system: C:\Program Files (x86)\Siemens\Automation\MIGTOOL_V13\Bin On a 32-bit operating system: C:\Program Files\Siemens\Automation\MIGTOOL_V13\Bin To start the migration tool, click the "Siemens.Automation.MigrationApplication.exe" file in one of the directories. See also Creating a migration file (Page 108) 4.1.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. Requirements 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. 108 WinCC Basic V13.0 System Manual, 02/2014 Migrating projects and programs 4.1 Migrating projects in a TIA portal project Procedure To create the migration file, proceed as follows: 1. Choose the path of the source file for the migration in the "Storage Location (Path)" field. 2. Specify which project parts are to be migrated: - Select the "Include HW and Network data during the migration" check box to migrate not only the software but also the complete hardware parts and the network configuration of the project. - Select the "Copy SCADA runtime data" check box if you also want to migrate the runtime data, such as alarm archives, tag archives and user archives, in addition to the data of the engineering system. 3. Choose the path and the file name for the migration file in the "Intermediate file" field. 4. Click the "Migrate" button. Result: A migration file is created. Finally, copy this file to the target system and migrate this file in the TIA Portal. See also Migrating projects (Page 109) Calling the migration tool (Page 108) Migrating projects with the migration tool (Page 106) 4.1.3 Migrating projects Requirements A converted file in the format ".am13" is already available or the 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. 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. WinCC Basic V13.0 System Manual, 02/2014 109 Migrating projects and programs 4.1 Migrating projects in a TIA portal project 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 ".am12" migration format or in the format of the initial project. 3. To include the hardware configuration in the migration, select the "Include hardware configuration" check box. If you have selected a migration file that was created with the migration tool, the check box cannot be selected. In this case, you must specify if you wish to include the hardware configuration in the migration before the conversion with the migration tool . 4. Select the "Copy WinCC Runtime Professional data" check box, if you also want to migrate the runtime data, such as alarm archives, tag archives and user archives, in addition to the data of the engineering system. If you have selected a migration file that was created with the migration tool, the check box cannot be selected. In this case, you must specify if you wish to include the SCADA runtime data in the migration before the conversion with the migration tool . 5. Choose a name for the new project in the "Project name" box. 6. Choose a path in the "Target path" box where the new project will be created. 7. Enter your name or the name of another person responsible for the project in the "Author" field. 8. Enter a comment in the "Comment" box, if you require one. 9. Click "Migrate". Result The initial project is converted and a message appears after conversion is complete. The newly created project is then opened in the project view and the migration log is opened in the TIA Portal. Even if the migration failed, a project directory is created and a migration log in the form of an XML file is generated in this directory. The completion message that appears after the migration contains a link to this XML file. Click the link to open the XML file. Alternatively, you can find the XML file in the project directory under "\Logs". See also Post-editing integrated projects (Page 144) Display migration log (Page 111) Using logs (Page 241) Migrating projects with the migration tool (Page 106) Creating a migration file (Page 108) 110 WinCC Basic V13.0 System Manual, 02/2014 Migrating projects and programs 4.1 Migrating projects in a TIA portal project 4.1.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 247) 4.1.5 Display migration log A log is created for each successful migration. The log contains the following information: Migrated objects Modifications to objects made during migration Errors that occurred during migration In certain cases a link to more help with specific events. In this case, click the question mark to obtain more help. Procedure To display the log file of the migration, follow these steps: 1. Open the "Common data > Logs" folder in the project tree. 2. Double-click the desired log in the list. The contents of the log are displayed in the work area. See also Migration of projects with the TIA Portal (Page 105) Using logs (Page 241) WinCC Basic V13.0 System Manual, 02/2014 111 Migrating projects and programs 4.1 Migrating projects in a TIA portal project 4.1.6 Migrating WinCC flexible projects (Basic) 4.1.6.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 operating devices that are supported and the required conditions for a successful migration. Projects from ProTool and from earlier versions of WinCC flexible cannot be migrated directly to WinCC. If you wish to continue to use such projects in WinCC, you must first migrate them to a supported version of WinCC flexible. See also Object support during migration (WinCC flexible) (Page 118) Projects from Migrating WinCC flexible projects (WinCC flexible) (Page 114) Compiling and loading a migrated project (WinCC flexible) (Page 116) Migrating runtime data (WinCC flexible) (Page 128) Migrating integrated projects (WinCC flexible) (Page 130) Supported HMI devices (WinCC flexible) (Page 117) Migration of data types (WinCC flexible) (Page 134) Basics on migration (WinCC flexible) Introduction During migration, the project data from a WinCC flexible project are converted to the new 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. For more information on this topic, refer to the "Visualize Processes > Performance Features > Engineering System" chapter in the online help. 112 WinCC Basic V13.0 System Manual, 02/2014 Migrating projects and programs 4.1 Migrating projects in a TIA portal project Unique object names The objects are clearly identified by the folders in which they are contained in WinCC flexible. Screen elements 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 elements 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. Example: In WinCC flexible, tags located in different folders may have the same name. In WinCC, the tag name must be unique on the configured HMI device. This means tags with the same name from different folders will be renamed during migration. Tags are renamed as follows: Before migration After migration Folder_1/Tag_1 Folder_1/Tag_1 Folder_1/Tag_2 Folder_1/Tag_2 Folder_2/Tag_1 Folder_2/Tag_1#Mig1 Folder_2/Tag_2 Folder_2/Tag_2#Mig1 Folder_3/Tag_1 Folder_3/Tag_1#Mig2 Folder_3/Tag_2 Folder_3/Tag_2#Mig2 Affected objects The following objects are renamed if necessary: Screens Screen objects Recipes Tags 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 SQLServer. If the migration cannot address the project database due to missing user authorization. WinCC Basic V13.0 System Manual, 02/2014 113 Migrating projects and programs 4.1 Migrating projects in a TIA portal project If you select the "*.hmi" file for the migration in an integrated project. You must select the "*.s7" file for the migration in an integrated project. If the project was created with a version not supported by the migration. Saving the project in the migration format You do not have to execute the migration of a WinCC flexible project completely on the PC on which the project is available. You can prepare the migration by saving the project in the migration format. The migration tool is available for saving a WinCC flexible project in the migration format. The migration tool exports the engineering data from the WinCC flexible project and saves the data in the migration format "*.AM11". For the actual migration, copy the data in the migration format to a PC on which the TIA-Portal is installed. See the section "Auto-Hotspot" for more information on the migration tool. Projects from Migrating WinCC flexible projects (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 an integrated project can be found in the section Migrating integrated projects (WinCC flexible) (Page 130). If you only want to save the project in migration format, you can use the migration tool. See Basics on migration (WinCC flexible) for additional information. Requirement A project from WinCC flexible is available. The project is not open in WinCC flexible. 114 WinCC Basic V13.0 System Manual, 02/2014 Migrating projects and programs 4.1 Migrating projects in a TIA portal project 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. - The project is saved and a message displayed upon completion of the migration. The message contains a link that you can use to open the log. WinCC Basic V13.0 System Manual, 02/2014 115 Migrating projects and programs 4.1 Migrating projects in a TIA portal project When migration is complete, you will find a newly created device for each migrated HMI device in the project tree. These devices contain the migrated data, such as screens, alarms and tags. Opening the migration log at a later point in time The migration log is saved together with the migrated project. You can view the log at a later point in time. Open the log as follows: 1. Open the "Common data > Logs" folder in the project tree. It contains the logs of all previously performed migrations. 2. Double-click the required migration log. The log is opened. See also Migrating integrated projects (WinCC flexible) (Page 130) 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 errorfree 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 Configure the options as you want to use them in the project in the future. Subsequently, load the project to the HMI device. 116 WinCC Basic V13.0 System Manual, 02/2014 Migrating projects and programs 4.1 Migrating projects in a TIA portal project 4.1.6.2 Migrating engineering data (WinCC flexible) Supported HMI devices (WinCC flexible) Introduction Note that WinCC only supports the following HMI device types when migrating projects from WinCC flexible: KTP400 Basic mono PN KTP400 Basic mono PN Portrait KTP600 Basic DP KTP600 Basic DP Portrait KTP600 Basic PN KTP600 Basic PN Portrait KTP600 Basic mono PN KTP600 Basic mono PN Portrait KTP1000 Basic DP KTP1000 Basic PN TP1500 Basic PN WinCC only supports the functions provided by these HMI device types. If your WinCC flexible project contains an HMI device that is not supported by WinCC, then the migration process will abort. To migrate the project, you must change the HMI device in WinCC flexible to a HMI device type supported by WinCC. There may be some functions in a WinCC flexible project that are not supported by a Basic Panel, for example, because the device type has been switched. These unsupported functions are not migrated. Adaptations before migration If the HMI device has changed in the project being migrated, the project needs to be recompiled before migration. The compilation process will adjust the size of the screens and screen elements. See also Object support during migration (WinCC flexible) (Page 118) Migration (WinCC flexible) (Page 112) Migration of alarm classes and alarm groups (WinCC flexible) (Page 122) Migration of language-dependent contents (WinCC flexible) (Page 124) Migrating libraries (WinCC flexible) (Page 127) WinCC Basic V13.0 System Manual, 02/2014 117 Migrating projects and programs 4.1 Migrating projects in a TIA portal project Migration tags (WinCC flexible) (Page 121) Changes of values of object properties by the migration (WinCC flexible) (Page 120) Object support during migration (WinCC flexible) Introduction When migrating projects from WinCC flexible, all configuration data involving an HMI device supported by WinCC will be migrated. Basically, all object types and functions that are available and can be mapped to the new project environment will be fully migrated. Some global object types are not migrated, for example, dictionaries and global libraries. Supported object types The following object types are supported for migration: Animations Scheduler User administration Area pointer 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 Recipes Runtime languages Runtime scripting System functions Texts Text lists 118 WinCC Basic V13.0 System Manual, 02/2014 Migrating projects and programs 4.1 Migrating projects in a TIA portal project Tags Connections Unsupported object types The following object types are not supported by migration: Global libraries Dictionaries Project versions Change log 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 different templates of WinCC. The following objects are migrated to the "global screen" of WinCC: Alarm window Alarm indicator Function keys of HMI devices with function keys All other objects and properties are migrated to a template of WinCC. The connection of the objects and properties to the respective template is automatically adapted. Migration of system functions The names of some system functions have changed in WinCC. 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 See also Supported HMI devices (WinCC flexible) (Page 117) Changes of values of object properties by the migration (WinCC flexible) (Page 120) WinCC Basic V13.0 System Manual, 02/2014 119 Migrating projects and programs 4.1 Migrating projects in a TIA portal project 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 Supported HMI devices (WinCC flexible) (Page 117) Object support during migration (WinCC flexible) (Page 118) 120 WinCC Basic V13.0 System Manual, 02/2014 Migrating projects and programs 4.1 Migrating projects in a TIA portal project Migration 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 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. You can find additional details on this in the section "Migration of data types (WinCC flexible) (Page 134)". Migrating tags Tags are always fully migrated. Only the data type names and tag names may change due to 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 tags with the same name from different folders will be renamed during migration. You can find additional details on this in the section "Basics on migration (WinCC flexible) (Page 112)". See also Basics on migration (WinCC flexible) (Page 112) Migration of data types (WinCC flexible) (Page 134) Supported HMI devices (WinCC flexible) (Page 117) WinCC Basic V13.0 System Manual, 02/2014 121 Migrating projects and programs 4.1 Migrating projects in a TIA portal project 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. 122 WinCC Basic V13.0 System Manual, 02/2014 Migrating projects and programs 4.1 Migrating projects in a TIA portal project 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. WinCC Basic V13.0 System Manual, 02/2014 123 Migrating projects and programs 4.1 Migrating projects in a TIA portal project 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 Supported HMI devices (WinCC flexible) (Page 117) 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. 124 WinCC Basic V13.0 System Manual, 02/2014 Migrating projects and programs 4.1 Migrating projects in a TIA portal 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 WinCC Basic V13.0 System Manual, 02/2014 125 Migrating projects and programs 4.1 Migrating projects in a TIA portal project 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 126 WinCC Basic V13.0 System Manual, 02/2014 Migrating projects and programs 4.1 Migrating projects in a TIA portal project Tamil Telugu Urdu Punjabi Persian Syrian See also Supported HMI devices (WinCC flexible) (Page 117) Migrating 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 Supported HMI devices (WinCC flexible) (Page 117) WinCC Basic V13.0 System Manual, 02/2014 127 Migrating projects and programs 4.1 Migrating projects in a TIA portal project 4.1.6.3 Migrating runtime data (WinCC flexible) Migrating runtime data (WinCC flexible) Introduction When migrating a project, only the configuration data will be migrated. 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. Migrating runtime data You update the runtime project by compiling the project in WinCC again and loading it to the HMI device. 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. You can then load the migrated project to the HMI device. Finally, you load the saved recipe data and user administration back to the HMI device. You can find additional details on this in the section "Auto-Hotspot". See also Migration (WinCC flexible) (Page 112) Backing up recipe data and user administration (WinCC flexible) (Page 128) Restoring recipe data and user administration (WinCC flexible) (Page 129) 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. 128 WinCC Basic V13.0 System Manual, 02/2014 Migrating projects and programs 4.1 Migrating projects in a TIA portal project 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 128) Restoring recipe data and user administration (WinCC flexible) (Page 129) 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. WinCC Basic V13.0 System Manual, 02/2014 129 Migrating projects and programs 4.1 Migrating projects in a TIA portal project 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 128) Backing up recipe data and user administration (WinCC flexible) (Page 128) 4.1.6.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. 130 WinCC Basic V13.0 System Manual, 02/2014 Migrating projects and programs 4.1 Migrating projects in a TIA portal project Note It is advisable to compile and save an integrated project in WinCC flexible before you migrate it. You can be sure that the data in WinCC flexible and STEP 7 is synchronized if compilation was completed without errors. Migrating an integrated project When migrating an integrated project, the same requirements apply for the WinCC flexible component as those for the migration of a non-integrated WinCC flexible project. The objects and properties contained in the WinCC flexible component must be supported by WinCC, for example, the HMI device or the communication driver. The "Online" property must be activated on the configured connection. A connection with deactivated "Online" property is not migrated. In addition to the requirements for the WinCC flexible component, there are also requirements for the STEP 7 component of the integrated project. The objects and properties contained in the STEP 7 V5.4 SP5 or V5.5 component must be supported in STEP 7. For detailed information, refer to the documentation for STEP 7. To fully migrate an integrated project and then edit it, the following components must be installed on the PC performing the migration: STEP 7 V5.4 SP5 or STEP 7 V5.5 WinCC flexible 2008 SP2 or WinCC flexible 2008 SP3 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 112) 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 Basics on migration (WinCC flexible) (Page 112) Migrating an integrated project 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. WinCC Basic V13.0 System Manual, 02/2014 131 Migrating projects and programs 4.1 Migrating projects in a TIA portal 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. For more information, refer to basics of migration (WinCC flexible). 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. 132 WinCC Basic V13.0 System Manual, 02/2014 Migrating projects and programs 4.1 Migrating projects in a TIA portal project Procedure To migrate an integrated project in the portal view, follow these steps: 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. To migrate the project with hardware configuration, activate "Include hardware configuration". WinCC Basic V13.0 System Manual, 02/2014 133 Migrating projects and programs 4.1 Migrating projects in a TIA portal project 6. 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. 7. Once migration is completed, save the project. Once the migration is complete, you will find a newly created device for each migrated HMI device and controller in the project tree. These devices include the migrated data. Opening the migration log at a later point in time The migration log is saved together with the migrated project. You can view the log at a later point in time. Open the log as follows: 1. Open "Shared data > Logs" in the project navigation. 2. Double-click the log file. The migration log opens. See also Basics on migration (WinCC flexible) (Page 112) 4.1.6.5 Reference (WinCC flexible) Migration of data types (WinCC flexible) Introduction To harmonize the data types used by controllers and HMI systems, some types of 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 data types from WinCC flexible to the data types in WinCC. 134 WinCC Basic V13.0 System Manual, 02/2014 Migrating projects and programs 4.1 Migrating projects in a TIA portal project Migration of data types The internal data types are mapped as follows during migration: Internal data types WinCC flexible Internal data types WinCC Bool Bool Char SInt Byte USInt Int Int UInt UInt Long DInt ULong UDInt Float Real Double LReal String WString DateTime DateTime Migrating external data types See the following pages for how to map the available communication drivers. See also Migration (WinCC flexible) (Page 112) Migrating data types of Allen-Bradley DF1 (WinCC flexible) (Page 136) Migrating data types of Allen-Bradley Ethernet IP (WinCC flexible) (Page 136) Migrating data types of Mitsubishi FX (WinCC flexible) (Page 137) Migrating data types of Modicon Modbus (WinCC flexible) (Page 137) Migrating data types of Modicon Modbus TCP/IP (WinCC flexible) (Page 138) Migrating data types of Omron Hostlink/Multilink (WinCC flexible) (Page 138) Migrating data types of SIMATIC S7 200 (WinCC flexible) (Page 139) Migrating data types of SIMATIC S7 300/400 (WinCC flexible) (Page 139) WinCC Basic V13.0 System Manual, 02/2014 135 Migrating projects and programs 4.1 Migrating projects in a TIA portal project 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 Migration of data types (WinCC flexible) (Page 134) 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 Migration of data types (WinCC flexible) (Page 134) 136 WinCC Basic V13.0 System Manual, 02/2014 Migrating projects and programs 4.1 Migrating projects in a TIA portal project Migrating data types of Mitsubishi FX (WinCC flexible) Migrating data types Mitsubishi FX The data types of the Mitsubishi FX communication driver are mapped as follows in the migration to WinCC: Data type in WinCC flexible Data type in WinCC 12 Bit Block 12-Bit Block 16 Bit Block 16-Bit Block 20 Bit Block 20-Bit Block 24 Bit Block 24-Bit Block 28 Bit Block 28-Bit Block 32 Bit Block 32-Bit Block 4 Bit Block 4-Bit Block 8 Bit Block 8-Bit Block Bit Bool Double DWord IEEE-Float Real String String Word Word See also Migration of data types (WinCC flexible) (Page 134) 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: WinCC Basic V13.0 System Manual, 02/2014 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 137 Migrating projects and programs 4.1 Migrating projects in a TIA portal project See also Migration of data types (WinCC flexible) (Page 134) Migrating data types of Modicon Modbus TCP/IP (WinCC flexible) Migrating data types Modicon Modbus TCP/IP The data types of the Modicon Modbus TCP/IP communication driver are mapped as follows in the migration to WinCC: Data type in WinCC flexible Data type in WinCC +/-Double +/- Double +/-Int +/- Int 16 Bit Group 16 Bit Group ASCII ASCII Bit Bit Double Double Float Float Int Int See also Migration of data types (WinCC flexible) (Page 134) 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: 138 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 WinCC Basic V13.0 System Manual, 02/2014 Migrating projects and programs 4.1 Migrating projects in a TIA portal project See also Migration of data types (WinCC flexible) (Page 134) 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 Char DInt DInt DWord DWord Int Int Real Real StringChar StringChar Timer Timer Word Word See also Migration of data types (WinCC flexible) (Page 134) 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: WinCC Basic V13.0 System Manual, 02/2014 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 139 Migrating projects and programs 4.1 Migrating projects in a TIA portal project Data type in WinCC flexible Data type in WinCC Real Real String String StringChar see below Time Time Time of Day Time_Of_Day Timer see below Word Word Special considerations for some data types There are special considerations to be made when migrating external tags that contain data types of a SIMATIC S7-300/400 PLC. Mapping of the S7 data type "Char" The S7 data type "Char" is a data type for mapping characters according to the specification. However, since this data type is often used for reading and writing numerical values, it is mapped in WinCC to the S7 data type "Byte". If this should be the case during migration, an alarm will appear in the output window. If the S7 data type "Char" is used for numerical values and negative numbers were configured at the point of use, the result is an error in mapping to the S7 data type "Byte". The S7 data type "Byte" cannot map any negative numbers. You have to adapt the configuration accordingly to correct the error. Use a signed data type, such as the data type "Int", for processing positive and negative numerical values. If the S7 data type "Char" is used for mapping characters, you must change the configuration after migration. To represent characters, use the data type "String". When an integrated project is migrated, the data type "Char" in WinCC is also migrated to the data type "Byte". With a connected PLC tag, the data type "Char" remains "Char". As a result of changing the data type of the HMI tag, symbolic addressing of the tags in question is not migrated. After migration. the tags are interconnected by absolute addresses and continue to work. If you want to restore symbolic addressing, you have to change the configuration accordingly after the migration. Mapping an array of the S7 data type "Char" An array of the S7 data type "Char" is mapped to an array of the data type "Byte" during migration. If an array of the S7 data type "Char" is used for numerical values and negative numbers were configured at the point of use, the result is an error in mapping to an array of the S7 data type "Byte". The S7 data type "Byte" cannot map any negative numbers. You have to adapt the configuration accordingly to correct the error. Use a signed data type, such as the data type "Int", for processing positive and negative numerical values. 140 WinCC Basic V13.0 System Manual, 02/2014 Migrating projects and programs 4.1 Migrating projects in a TIA portal project 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". 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 Basic V13.0 System Manual, 02/2014 141 Migrating projects and programs 4.1 Migrating projects in a TIA portal project WinCC flexible 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 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 WinCC See also Migration of data types (WinCC flexible) (Page 134) 4.1.7 Migrating integrated projects 4.1.7.1 Migrating an integrated project Introduction In integrated projects, you use SIMATIC controllers and WinCC components together in a project. When an integrated project is migrated, the complete project will be migrated with components from WinCC 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 WinCC component must also be supported in WinCC (TIA Portal). For detailed information, refer to the documentation for WinCC. Also note that the initial project must be compiled before the migration. To fully migrate an integrated project, the following components must be installed on the PG/ PC performing the migration: STEP 7 V5.4 SP5 or STEP 7 V5.5 WinCC V7.0 SP3 or WinCC Flexible 2008 SP2 and SP3 To be able to fully post-edit an integrated project, the following components must be installed on the PC for post-editing: 142 WinCC Basic V13.0 System Manual, 02/2014 Migrating projects and programs 4.1 Migrating projects in a TIA portal project STEP 7 Professional V12 SP1 WinCC Basic, WinCC Comfort/Advanced or WinCC Professional, depending on the components used Using the migration tool It is necessary to use the migration tool under the following circumstances: The initial project is not located on the same PG/PC as the installation of the TIA Portal. SCADA devices are included in the initial project. These can only be migrated with the migration tool. WinCC Professional V12 and STEP 7 with WinCC V7.0 SP3 cannot be installed on the same PG / PC. Therefore, integrated projects with WinCC V7.0 SP3 parts must be prepared for migration with the migration tool. 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 SP5 or V5.5 without an installation of WinCC. Then, save the project again and select the "Reorganize" function during saving. The WinCC parts are then automatically removed when the copy is saved. You can then migrate the STEP 7 project without the WinCC project. Migration of an integrated project with the hardware configuration In integrated projects, HMI devices are migrated even if the hardware configuration is not included in the migration. The STEP 7 part of the hardware configuration, including network configurations, and connections and interrupts, is migrated only if you include the hardware configuration in the migration. Otherwise, unspecified modules will be created for the STEP 7 devices and you will need to convert them into suitable modules after the migration. HMI modules that are plugged into a PC station are converted to a separate Station during the migration. If you perform the migration without including the hardware configuration, the migrated project then 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. When the hardware configuration is included, the migrated project contains two separate stations: the HMI Station and the PC Station. Storage location of an integrated WinCC project If you migrate an integrated project, the HMI part of it must be on the same PG/PC as the STEP 7 part of the project. If the HMI part is on a different PG, then only the STEP 7 part will be migrated. WinCC Basic V13.0 System Manual, 02/2014 143 Migrating projects and programs 4.1 Migrating projects in a TIA portal project 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 144) 4.1.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: 1 2 144 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. WinCC Basic V13.0 System Manual, 02/2014 Migrating projects and programs 4.1 Migrating projects in a TIA portal project 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 145) Creating an integrated HMI connection (Page 147) Re-linking HMI tags (Page 149) Deleting an unspecified connection (Page 150) 4.1.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. WinCC Basic V13.0 System Manual, 02/2014 145 Migrating projects and programs 4.1 Migrating projects in a TIA portal project 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 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 147) 146 WinCC Basic V13.0 System Manual, 02/2014 Migrating projects and programs 4.1 Migrating projects in a TIA portal project 4.1.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. WinCC Basic V13.0 System Manual, 02/2014 147 Migrating projects and programs 4.1 Migrating projects in a TIA portal project 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 149) 148 WinCC Basic V13.0 System Manual, 02/2014 Migrating projects and programs 4.1 Migrating projects in a TIA portal project 4.1.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. WinCC Basic V13.0 System Manual, 02/2014 149 Migrating projects and programs 4.2 Migrating S7-1200 to firmware as of V4 See also Deleting an unspecified connection (Page 150) 4.1.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. 4.2 Migrating S7-1200 to firmware as of V4 4.2.1 Basic information on upgrading to V4 Introduction If you have used a CPU with firmware version V3 in your project and want to upgrade to a CPU with firmware V4.0 or later, you can easily replace the device. 150 WinCC Basic V13.0 System Manual, 02/2014 Migrating projects and programs 4.2 Migrating S7-1200 to firmware as of V4 The TIA Portal offers the "Change device" function for this purpose. The project remains unchanged when the device is replaced. You can continue using the programs that you created with firmware version V3. Rules The following basic rules apply when replacing a device: Device replacement is only possible if the CPU used to date has been operating with firmware version V3.0. S7-1200 CPUs with firmware version V1.0 or V2.0 must first be replaced with a V3.0 CPU. It is not possible to replace a V4 CPU with a V3 CPU. If you want to continue using the existing V3 CPU, create a copy of this CPU before replacing the device. The program cannot be transferred to the new CPU via a memory card. Instead, use the "Change device" function, which is described in the following sections. HMI panels Configured HMI panels are treated differently during device replacement, depending on the firmware version of the panel and the communication mode. The following table shows the HMI connections that are supported with the migration: Firmware version of the panel PUT/GET communication Migration to V4 V11 or later No S7-1200 does not support this configuration. Upgrade the firmware of the HMI panel to V12.0. Then compile and load the configuration. V11 or later Yes S7-1200 supports this configuration. The connection is established automatically while you compile and load the project after replacing the device. V12 or later No S7-1200 supports this configuration. The connection is established automatically while you compile and load the project after replacing the device. Note HMI TP 177B 4" The HMI TP 177B 4" with firmware version V11.0.2 cannot be operated with S7-1200 V4. Replace the panel with a new device, if necessary. WinCC Basic V13.0 System Manual, 02/2014 151 Migrating projects and programs 4.2 Migrating S7-1200 to firmware as of V4 S7-1200 expansion modules If you are already using the following centrally plugged S7-1200 modules in your system, you must perform a firmware update for these modules in order to guarantee operation with S7-1200 V4. ASi - Master - CM 1243 DP - Master - CM 1243-5 WAN CP - CP1243-1 Newly shipped S7-1200 modules have the latest firmware installed ex works. Protected blocks Blocks equipped with know-how protection or copy protection cannot be converted to V4. If the project contains protected blocks, you must remove the protection prior to migration. If these are supplied blocks and you do not know the password, ask your supplier either for the password or for a V4-compatible block. WARNING Preventing personal injury and material damage Changes are made to the program during device replacement in some cases. Therefore, thoroughly check the program in a test environment after replacing the device and before putting it in operation. Note Additional support You can find the latest FAQs about migrating to S7-1200 V4 (http:// support.automation.siemens.com/WW/view/en/82140966) in Siemens Industry Online Support. If you need further assistance with migrating to S7-1200 V4, please contact SIMATIC Customer Support. See also Migrating to V4 (Page 153) Special considerations after migrating to V4 (Page 154) 152 WinCC Basic V13.0 System Manual, 02/2014 Migrating projects and programs 4.2 Migrating S7-1200 to firmware as of V4 4.2.2 Migrating to V4 Requirement A CPU with firmware version V3 is available in the project. The project contains no protected blocks. Procedure Proceed as follows to replace a CPU: 1. Select the V3 CPU you want to replace. 2. Select the "Change device" command in the shortcut menu. The "Change device" dialog box appears. 3. Under "New device" in the tree structure, select the V4 CPU with which you want to replace your current V3 CPU. 4. Click "OK". The existing CPU is replaced by the new one. 5. Select the new CPU and select the "Compile > Hardware and software (only changes)" command in the shortcut menu. The device configuration and the user program are compiled again. 6. Optional: If necessary, apply know-how protection or copy protection to individual blocks in the program. 7. Select the new CPU and select the "Download to device > Hardware and software (only changes)" command in the shortcut menu. The device configuration and the user program are loaded into the new CPU. This completes the device replacement. WARNING Preventing personal injury and material damage Changes are made to the program during device replacement in some cases. Therefore, thoroughly check the program in a test environment after replacing the device and before putting it in operation. WinCC Basic V13.0 System Manual, 02/2014 153 Migrating projects and programs 4.2 Migrating S7-1200 to firmware as of V4 Note Additional support You can find the latest FAQs about migrating to S7-1200 V4 (http:// support.automation.siemens.com/WW/view/en/82140966) in Siemens Industry Online Support. If you need further assistance with migrating to S7-1200 V4, please contact SIMATIC Customer Support. See also Basic information on upgrading to V4 (Page 150) Special considerations after migrating to V4 (Page 154) 4.2.3 Special considerations after migrating to V4 Functional changes in V4 S7-1200 V4 offers significantly enhanced functionality. The most important functional changes that you need to consider after migrating from V3 are described briefly below. You can find more information on S7-1200 in the "SIMATIC S7-1200 Programmable controller" system manual. See also: TIA Portal in Siemens Industry Online Support (http://support.automation.siemens.com/WW/ view/en/65601780) Organization blocks With S7-1200 V4, you can specifically set the interruptibility of each organization block used. When a device is replaced, all the organization blocks are configured as non-interruptible, to ensure that the executability of your V3 program remains unchanged. The OB priorities from the V3 program also remain unchanged. After migration, you can change the settings for priority and interruptibility as needed. The behavior of diagnostic interrupts in V4 has changed as follows: In V3, the start information always contained information on the triggering module, including the channel number. In V4, this information is only generated for a pending diagnostics event. If no diagnostic event is pending, for example, because the fault has already been corrected, only the triggering module is indicated. 154 WinCC Basic V13.0 System Manual, 02/2014 Migrating projects and programs 4.2 Migrating S7-1200 to firmware as of V4 Access levels S7-1200 V4 offers an extended access level concept. The following table shows how the protection levels of the V3 firmware are indicated in V4: V3 protection level V4 access level No protection Full access (no protection) Read-only Read access Write/read protection HMI access The access level "No access (complete protection)" has been newly introduced with V4. It was not available in previous versions. Instruction libraries After migrating to S7-1200 V4, instructions from the libraries of the V3 firmware version are still available. This ensures that you can continue to use your program unchanged. In addition, S7-1200 V4 offers many new instructions which are also compatible with the instructions of the S7-1500. You can find more information on the instruction libraries of S7-1200 in the "SIMATIC S7-1200 Programmable controller" system manual. See also: TIA Portal in Siemens Industry Online Support (http://support.automation.siemens.com/WW/ view/en/65601780) Motion Control When a device is replaced, the Motion Control objects from the libraries of the firmware versions V1 and V2 are replaced with the corresponding objects from the V3 libraries. The objects from V3 libraries are compatible so that you can continue to use the programs unchanged. The libraries of the S7-1200 V4 offer many new Motion Control functions, which are compatible with the functions of the S7-1500. If you want to use V4 libraries, select them on the "Instructions" task card after replacing the device. You can find more information on the new Motion Control functions in the "SIMATIC S7-1200 Programmable controller" system manual. See also: TIA Portal in Siemens Industry Online Support (http://support.automation.siemens.com/WW/ view/en/65601780) Web server The following settings for operation via a web server are transferred from the V3 CPU to the V4 CPU during device replacement: Activate web server on this module Permit access only with HTTPS WinCC Basic V13.0 System Manual, 02/2014 155 Migrating projects and programs 4.3 Programming recommendations If you want to operate the V4 CPU via a web server, you need to set up user accounts with assigned user rights in the user management. Only the standard web pages are available to standard users without any additional rights. Note Additional support You can find the latest FAQs about migrating to S7-1200 V4 (http:// support.automation.siemens.com/WW/view/en/82140966) in Siemens Industry Online Support. If you need further assistance with migrating to S7-1200 V4, please contact SIMATIC Customer Support. Communication via PUT/GET Communication via PUT/GET is enabled after the device replacement. Note that the new integrated connection types offer a security standard higher than PUT/GET communication. If you do not use PUT/GET communication, you should disable it. See also Basic information on upgrading to V4 (Page 150) Migrating to V4 (Page 153) 4.3 Programming recommendations 4.3.1 The new S7-1500 CPU functions at a glance Higher performance The S7-1500 represents a CPU series that provides much higher performance than the CPUs of the S7-300/400 series. When programming with STEP 7 V5.x, you were probably used to working with programming methods such as absolute addressing to achieve higher performance from the CPU and leaner program code. Due to the high performance that the S7-1500 provides, these programming methods are made obsolete. In the paragraphs below we would like to introduce some new programming options of the S7-1500. 156 WinCC Basic V13.0 System Manual, 02/2014 Migrating projects and programs 4.3 Programming recommendations Universal symbolism The S7-1500 allows you to use the symbolism throughout the entire project. Using the autocomplete function, you are given context-dependent support for programming with symbols within the programming editors. The data elements, for example those in a data block, are assigned only a symbolic name in the declaration but no fixed address within the data block. This allows you to fully exploit the high performance of the S7-1500 when accessing these data elements. The absolute addresses of operands need not be known and access errors are avoided. Your program code will be clearer due to the symbolism and you have to comment less. All points of use are automatically updated when a correction is made to the symbolism. An example of the use of universal symbols is available at: Symbolic addressing (Page 160) Optimized block access With optimized block access, the declared data elements are arranged automatically in the available memory area of the block in a way that makes optimal use of its capacity. The data is structured and saved in way that is optimal for the CPU used. The storage is left to the system. The data elements are assigned only a symbolic name in the declaration by which the WinCC Basic V13.0 System Manual, 02/2014 157 Migrating projects and programs 4.3 Programming recommendations tag within the block can be addressed. This allows you to increase the performance of the CPU. Access errors, from the HMI, for example, are not possible. 6,(0(16 &RPSDULVRQRIEORFNDFFHVVHV 6WDQGDUG!2SWLPL]HG 'DWDPDQDJHPHQW 6WDQGDUGEORFNDFFHVV 6FRPSDWLEOH ZLWK6 2SWLPL]HGEORFNDFFHVV 6RQO\ <RXFDQDGGUHVVWDJVXVLQJERWKV\PEROLF PHPRU\RSWLPL]HG DQGDEVROXWH XVHUGHILQHG DGGUHVVHV 7KHV\VWHPPDQDJHVDQGRSWLPL]HVWKH GDWDVWRUDJH7KLVUHVXOWVLQRSWLPDOXVHRI WKHPHPRU\FDSDFLW\ 3HUIRUPDQFH 7KHDFFHVVWRD&38RIWKH 6VHULHVGRHVQRWDOZD\V RFFXUDVIDVWDVSRVVLEOHEHFDXVHWKH GDWDVWRUDJHFDQEHLQHIILFLHQWGXHWR DEVROXWHDGGUHVVLQJ 7KHDFFHVVDOZD\VRFFXUVDVIDVWDV SRVVLEOHEHFDXVHWKHGDWDVWRUDJHLV RSWLPL]HGE\WKHV\VWHPDQGQRIL[HG DGGUHVVHVDUHDVVLJQHG 6XVFHSWLELOLW\WRHUURUV $EVROXWHDGGUHVVLQJ HJIURP+0, RUZKHQLQGLUHFWDGGUHVVLQJLVXVHG FDQOHDGWRLQFRQVLVWHQFLHVDIWHUD FKDQJHWRWKHIL[HGDGGUHVV $FFHVVHUURUVHJIURP+0,RUZKHQ LQGLUHFWDGGUHVVLQJLVXVHGDUHQRW SRVVLEOHEHFDXVHWKHDFFHVVLV V\PEROLF 5HWHQWLYLW\ 9DOLGIRUDOOWDJVRIDGDWDEORFN 9DOLGIRULQGLYLGXDOWDJV 5HFRPPHQGDWLRQ 7RDFKLHYHWKHEHVWSRVVLEOHSHUIRUPDQFHWKHFRPELQLQJRIGLIIHUHQWEORFNDFFHVVW\SHVZLWKLQ\RXUSURJUDPLVQRW UHFRPPHQGHG You can find additional information on blocks with optimized access under "See also". New data types The new data types LWORD, LINT, ULINT, LTIME, LTOD, LDT and the array (32-bit limit) offer much higher calculation accuracy when using mathematical functions. In the area of implicit and explicit data type conversion, you have more options in comparison to the CPUs of the S7-300/400 series. You can find additional information on the new data types under "See also". PLC data types PLC data types (UDT) are data structures that you define and that can be used multiple times within the program. The structure of a PLC data type is made up of several components, each of which can contain different data types. You define the type of components in the declaration of the PLC data type. 158 WinCC Basic V13.0 System Manual, 02/2014 Migrating projects and programs 4.3 Programming recommendations You can use the PLC data type as a base data type for defining tags and as a template for creating global data blocks. If you later make changes to the PLC data type, the changes are automatically updated at all points of use. You can also symbolically access individual elements of an array within a PLC data type. You can find additional information on the new data types under "See also". You can find an example for using PLC data types under: Using PLC data types (UDT) (Page 168) Uniform instructions in all programming languages You are provided with a uniform set of instructions in all programming languages (LAD, FBD, STL, SCL, and GRAPH). Slice access Slice access gives you the option of specifically addressing areas within declared tags. You can implement symbolic access to a single bit up to the level of the tag. The single bit is then addressed absolutely. You can find additional information on slice access under "See also". Indirect addressing Indirect addressing offers you the option of addressing operands whose address is not calculated until runtime. All programming languages provide general methods for indirect addressing, for example, via POINTER. In the SCL programming language, you can also use PEEK and POKE instructions. You can find additional information on indirect addressing under "See also". Additional programming recommendations You can find more information about programming recommendations and a programming guide in the Siemens Industry online support under: FAQs: Programming recommendations (http://support.automation.siemens.com/WW/ llisapi.dll?aktprim=0&lang=en&referer=%2fWW %2f&func=cslib.csinfo&siteid=csius&Datakey=47071380&extranet=standard&groupid=40 00002&viewreg=WW&nodeid0=29156492&objaction=csopen) Background and system descriptions in the Programming Guideline (http:// support.automation.siemens.com/WW/llisapi.dll?aktprim=100&lang=en&referer=%2fWW %2f&func=cslib.cssearch&nodeid0=4000024&viewreg=WW&siteid=csius&extranet=stand ard&groupid=4000002&objaction=cssearch&content=adsearch%2Fadsearch%2Easpx) WinCC Basic V13.0 System Manual, 02/2014 159 Migrating projects and programs 4.3 Programming recommendations 4.3.2 Symbolic addressing Advantages of symbolic addressing The use of universally applied and meaningful symbols in the overall project makes the program code easier to read and understand. This gives you the following advantages: You do not have to write detailed comments. Data access is faster. No errors occur when accessing data. You no longer have to work with absolute addresses. The assignment of the symbol to the memory address is monitored by STEP 7, which means all points of use are automatically updated when the name or the address of a tag changes. Programming in STEP 7 V5.x STEP 7 V5.x already gave you the option to write a program that is easier to read by using descriptive names for operands and blocks. You did this by assigning the symbolic operands to memory addresses and blocks in the symbol table. In order for a change in the symbolism to also have an affect on the program code in the programming editor, you had to use the "Operand priority" property to specify whether the symbol or the absolute value had priority. The use of symbolic addressing allowed you to create a program with greater clarity. However, in some cases, such as when programming with user-defined data types (UDT), this could impair performance. You could increase the performance by ignoring the symbolism in the UDT and using absolute addressing. This made in necessary, however, to know the data storage. Changes to the UDT were not automatically updated. Using absolute addressing, you could also access parts of a tag and edit these. The only drawback of absolute addressing, however, was that after a certain level the program code was cluttered and you had to insert additional comments for better orientation. Procedure in STEP 7 TIA Portal The S7-1500 CPU offers much higher performance than the S7-300/400 CPUs. To fully use this high performance, we recommend you enable optimized block access for all blocks and use symbolic addressing in the program code. The programming editor helps you work with symbols through context-sensitive input help, for example, auto-complete. Using it, you can easily access existing tags or instructions during programming. 160 WinCC Basic V13.0 System Manual, 02/2014 Migrating projects and programs 4.3 Programming recommendations Programming example The following example shows you how to symbolically access individual elements: You can use the tag names that you have defined in the block interface directly at the parameters of the TON instruction without knowing the absolute address of the tag. See also Using VARIANT instructions (Page 174) 4.3.3 Using IEC timers and counters Advantages of IEC timers and counters The universal use of IEC timers and counters makes your program code more efficient. This gives you the following advantages: The blocks can be called multiple times with newly generated instance data blocks. The IEC counters have a large counting range. Compared to S5 timers, IEC timers have better performance and greater time accuracy. WinCC Basic V13.0 System Manual, 02/2014 161 Migrating projects and programs 4.3 Programming recommendations Programming in STEP 7 V5.x The S5 timers and counters in STEP 7 V5.x were addressed absolutely via a number. Due to this dependency on numbers, program blocks were not reusable with S5 timers and counters. The value range of a timer was limited to 9990 seconds and that of a counter limited to a maximum of 999. Procedure in STEP 7 TIA Portal You declare IEC timers and counters in the program block where they are called or needed. The IEC timer is a structure of data type IEC_TIMER, IEC_LTIMER, or TON_TIME and TON_LTIME, for example, which you can also declare as a local tag in a block. The IEC counter is a structure of data type IEC_SCOUNTER, IEC_USCOUNTER, etc. Programming example in the TIA Portal The following example shows you how to declare an IEC timer and IEC counter as a local tag: The data of the TON IEC timer and the CTU IEC counter is stored as a local tag (multi-instance) in the block interface. 162 WinCC Basic V13.0 System Manual, 02/2014 Migrating projects and programs 4.3 Programming recommendations 4.3.4 Flexibly using enable output ENO Advantages You can to detect runtime errors and avoid program termination using the EN/ENO mechanism for each instruction and block call. Overflow, for example, is reported via the ENO enable output for mathematical functions. In STEP 7 TIA Portal, the ENO enable output is disabled by default in the programming languages LAD and FBD. If needed, you can activate the enable output and thereby deliberately target the instructions for which you want to have error evaluation. This gives you the following advantages: The performance increases with ENO disabled. Runtime errors do not cause the CPU to go to STOP when ENO is enabled. Procedure in STEP 7 TIA Portal Proceed as follows to activate the EN/ENO mechanism of an instruction: 1. In your program, right-click the instruction at which you want to activate the EN/ENO mechanism. 2. Select the "Generate ENO" command from the shortcut menu. The ENO value is generated for the instruction. Other instructions are inserted with the enable output. The tables below list the instructions for which ENO enable output can be disabled: Basic instructions Math functions ADD, SUB, MUL, DIV, MOD, INC, DEC, ABS, NEG, SQR, SQRT, LN, EXP, SIN, COS, TAN, ASIN, ACOS, ATAN, FRAC, EXPT, MIN, MAX, LIMIT, CALCULATE Move operations MOVE, SWAP, MOVE_BLK, UMOVE_BLK, FILL_BLK, UFILL_BLK, MOVE_BLK_VARIANT Conversion operations CONVERT, ROUND, CEIL, TRUNC, FLOOR, NORM_X, SCALE_X Word logic operations AND, OR, XOR, INV, DECO, ENCO Shift and rotate SHR, SHL, ROR, ROL Extended instructions String + Char CONCAT, LEFT, RIGHT, MID, DELETE, INSERT, REPLACE, FIND, LEN, S_CONV Date and time T_CONV You can find additional information on the EN/ENO mechanism in each programming language under "See also". WinCC Basic V13.0 System Manual, 02/2014 163 Migrating projects and programs 4.3 Programming recommendations Programming example The following example shows you how to use instructions with the ENO enable output enabled and disabled: If you have activated the ENO enable output, for example with the SUB instruction, all subsequent instructions are also applied with an activated enable output. If an arithmetic error occurs during the execution of the SUB instruction, the ADD instruction is not executed. The ENO enable output is disabled for the DIV instruction in the second branch. If a runtime error occurs during execution, the MUL instruction is executed anyway. 4.3.5 Using MOVE instructions in STL Possible applications You can now program with MOVE instructions in STL on an S7-1500 CPU. This gives you the following advantages: The program structure is easier to create. The performance of the CPU increases. Programming in STEP 7 V5.x In STEP 7 V5.x, you used the "BLKMOV: Move block" and "UBLKMOV: Move block uninterruptible" system functions to implement the MOVE functionality. 164 WinCC Basic V13.0 System Manual, 02/2014 Migrating projects and programs 4.3 Programming recommendations Procedure in STEP 7 TIA Portal The following new MOVE instructions are available in STEP 7 TIA Portal: MOVE: Move value MOVE_BLK: Move block MOVE_BLK_VARIANT: Move block UMOVE_BLK: Move block uninterruptible You can find additional information on the new MOVE instructions under "See also". Programming example The following example shows you how the "MOVE_BLK instruction works: Move block". An array block is copied into another array block: WinCC Basic V13.0 System Manual, 02/2014 165 Migrating projects and programs 4.3 Programming recommendations Using the MOVE_BLK instruction, ten elements from "Array_1" of the "Data_DB" data block are copied into "Array_2" of the same data block. 4.3.6 Implementing array access with a variable index Advantages of the variable index For addressing the components of an array, you can specify tags of the integer data type as well as constants as the index. Integers with lengths up to 32 bits are allowed here. When tags are used, the index is calculated during runtime. You can, for example, use a different index for each cycle in program loops. You can also access an array within a PLC data type. This gives you the following advantages: No addressing with address registers or with self-assembled pointers, for example, an ANY pointer, is necessary. More flexibility within your program. The variable index is available in all STEP 7 programming languages. It uses the existing names of data blocks and array tags. This improves readability of the program code. The start address of the array does not have to be known. The program code is easier to write. The compiler generates optimized program code. Procedure in STEP 7 V5.x In STEP 7 V5.x, you had to use an address register with the help of a self-configured POINTER for indexed addressing of array elements. The SCL programming language already supported indirect addressing with variable index. 166 WinCC Basic V13.0 System Manual, 02/2014 Migrating projects and programs 4.3 Programming recommendations Programming example in STEP 7 V5.x The "Data_classic" data block is required for the following STL example. To address an element of the "Quantities" array, the following commands must be used: STL Explanation OPN "Data_classic" // The "Data_classic" data block is called. L #index // The value of the local tag #index is loading in accumulator 1. SLD 3 // Move bits 0 to 31 of accumulator 1 by 3 positions to the left. // Fill the now empty bit places with zeros. LAR1 // Load address register 1 with contents of accumulator 1. L DBW [AR1, P#10.0] // Load the array element addressed with #index into accumulator 1. // P#10.0 = Start address of the array You need to consider the following with this procedure, however: The array name is not used. This reduces the readability of the program code and makes it necessary to add a comment. The start address of the array (P#10.0) must be known to perform the addressing. The indexed addressing must involve the use of the address register. Programming example in STEP 7 TIA Portal The following syntax is used for indirect indexing of the "Quantities" array that was declared in the "Data_DB" data block: "Data_DB".Quantities["i"] // One-dimensional array "Data_DB".Quantities["i"].a // One-dimensional array of STRUCT "Data_DB".Quantities["i","j"] // Multi-dimensional array "Data_DB".Quantities["i","j"].a // Multi-dimensional array of STRUCT Part Description Data_DB Name of the data block in which the array is located Quantitie s Tag of the Array data type i, j PLC tags of the integer data type that are used as pointers a Additional partial tag of the structure The following example shows indirect indexing of an array component in STL. You need another program line for addressing an array element: WinCC Basic V13.0 System Manual, 02/2014 167 Migrating projects and programs 4.3 Programming recommendations Addressing in STL Explanation L "Data_DB".Quantities[#index] // The value of the array element #index is loaded directly from the data block into accumulator 1. Note the following to get the best performance: Declare tags that are used as an array index as an integer of less than or equal to 32 bits. Store intermediate results and array indexes in the temporary local data area. 4.3.7 Using PLC data types (UDT) Advantages of the PLC data types PLC data types (UDT) are data structures that you define and that can be used multiple times within the program. The structure of a PLC data type is made up of several components, each of which can contain different data types. You define the type of components in the declaration of the PLC data type. By using PLC data types, you can optimally exploit the high performance of the S7-1500 CPU. Many programs require contiguous data records that have to be processed by different locations in the program. They are optimized or replaced as the program runs. These are, for example: Data records for material tracking A parameter set for a motor setting Various recipes This gives you the following advantages: PLC data type elements can also be addressed indirectly, which means the address is variable and is first calculated in runtime. Tags based on a PLC data type inherit all properties of the PLC data type. Modifying the PLC data type results in automatic adjustment of all tags derived from it. Using universal symbolism makes the program easier to read, because the names of the individual elements of a PLC data type are displayed in the program. Increased performance because optimized program code is generated. The PLC data type can be passed as a complete structure for a block call. Simplified calling interface due to fewer parameters that have to be supplied. Procedure in STEP 7 V5.x STEP 7 V5.x already gave you the option to create a data record as a structured tag using the STRUCT data type or a PLC data type (UDT). However, the performance was adversely affected by the use of symbolic addressing. The declaration in the data blocks was mostly implemented as an anonymous structure. The blocks themselves were then programmed to pass the values of the structure as actual 168 WinCC Basic V13.0 System Manual, 02/2014 Migrating projects and programs 4.3 Programming recommendations parameters and the calculated values were copied back into the structure. This enabled you to also pass the data block number and use absolute addressing in the block. The number of parameters that you had to supply was often very large. The actual data was stored in the data blocks and the calculated values were passed to other blocks. But no symbolism was available when passing the data block tags. Procedure in STEP 7 TIA Portal If you work with PLC data types in your program, you can assign them to both a formal parameter and an actual parameter. This means you no longer have to declare each individual parameter. If a block has an input parameter that is based on a PLC data type, you must transfer a tag that has the same PLC data type as an actual parameter. To use a PLC data type, follow these steps: 1. Declare the data records as PLC data type with a suitable name, for example, "Material tracking". 2. Use this data type to declare a data block or a DB tag. 3. Define the formal parameter as VAR_IN_OUT / VAR_IN or VAR_OUT tag in the block interface. 4. Assign the PLC data type to the formal parameter in the "Data type" column. Programming example in the TIA portal The following example shows the call and the parameter assignment of a function block (FB) with two formal parameters. The data type of the DB tag (Array [1 .. 10] of BOOL) and the PLC data type (UDT) are identical to the data types of the FB parameters. WinCC Basic V13.0 System Manual, 02/2014 169 Migrating projects and programs 4.3 Programming recommendations Declare the "UserDataType" PLC data type in the project tree in the "PLC data types" folder. Then use it as a data type for the "UserData_Var" tag. You declare both tags "UserData_Var" and "Arr_Var" in the "Data_block_1" data block and use them to supply the parameters of the "FB_Module" block. 4.3.8 Querying and fixing errors in the program code Error handling in the TIA Portal Various error scenarios can occur within the program code during runtime. These can involve, for example, an access error or an overflow in mathematical operations. If you do not catch such a runtime error using a program code sequence within your program, the CPU reacts as follows in the event of an error, depending on the model: CPU S7-1200: - The CPU remains in RUN mode and writes an entry to the diagnostic buffer. CPU S7-1500: - When a programming error occurs, the CPU goes to STOP mode and writes an entry to the diagnostic buffer. - With an I/O access error, the CPU remains in RUN mode and writes an entry to the diagnostic buffer. To be able to respond appropriately to possible errors, in addition to global error handling (for example, the use of the organization blocks "Programming error OB" or "I/O access error OB"), we recommend that you implement local error handling in your program (for example, use an EN/ENO mechanism, the parameters RET_VAL, STATUS and ERROR, or the instructions "GET_ERROR"/"GET_ERR_ID"). Note STL programming language In STL, you use the BR bit of the status word instead of the EN/ENO mechanism. 170 WinCC Basic V13.0 System Manual, 02/2014 Migrating projects and programs 4.3 Programming recommendations Global error handling intervenes at the end of each program cycle, while local error handling is capable of intervening immediately after an error occurs. Note BR bit and EN/ENO mechanism as first indicator A first indicator for an error can be either the BR bit of the status word or the ENO enable output. If these return signal state "0", there is an error in the execution of the instruction. Signal state "1" indicates that there is no error and no further error analysis is necessary. Options for local error handling The following options for local error handling of programming and access errors are available: Error handling method Validity Explanation EN/ENO mechanism S7-1200/15 You can use the ENO enable output to detect and handle runtime errors. 00 Execution of subsequent instructions depends on the signal state of this parameter. You can avoid program crashes by using the EN/ENO mechanism. The block status is passed on in the form of a Boolean tag. Output parameter RET_VAL S7-1200/15 Using the RET_VAL parameter as the return value of system functions (SFCs). 00 you can display general error codes that may relate to any instruction or specific error codes that apply only to the instruction at hand. A maximum of one tag of the data type INT or WORD can be output. This error handling method is suitable for querying a communication error or incorrect data access, for example. Output parameters STATUS and ERROR S7-1200/15 Using the STATUS and ERROR parameters as return values of system 00 function blocks (SFBs), you can query device-specific error information. The error information is output in a pre-defined structure. Instructions "GET_ERROR" and "GET_ERR_ID" S7-1200/15 The instructions give you the opportunity to obtain an error ID or detailed error 00 information. You can use the error information for an access error, for example, to determine the parameter that caused the access error. In order for the instructions to output the required error information, they must be programmed in the user program for each individual block from which potential errors are to be evaluated. This option is ideal especially for custom libraries with error handling. If you work with the "GET_ERROR" or "GET_ERR_ID" instructions, no error OB is called and there is no entry in the diagnostic buffer. With this method of error handling, you actively intervene in the program sequence when an error occurs. BR bit of the status word S7-1200/15 Using the BR bit of the status word, you can determine whether an error 00 occurred when the instruction was executed. (BR bit = "0" => An error has occurred; BR bit = "1" => No error has occurred) WARNING Output parameter RET_VAL When errors occur in the supply of the input parameters during the execution of the instruction that contains the RET_VAL parameter, an invalid error code is output at the RET_VAL parameter and the output parameters of the instruction cannot be evaluated. WinCC Basic V13.0 System Manual, 02/2014 171 Migrating projects and programs 4.3 Programming recommendations Example The above-mentioned local error handling options can be programmed individually or in combination with one another. To ensure that each error scenario that can occur within your program is recognized, we recommend a combination of local error handling options, as shown in the example below. For a more precise error analysis, in addition to the RET_VAL output parameter you can also use the instructions "GET_ERROR" or "GET_ERR_ID". These options provide you with error codes, the detailed explanations of which are available in the descriptions of the respective instructions. There are also error scenarios in which the RET_VAL output parameter does not output a valid error code. If an access error occurs while reading an input parameter, for example, the outputs of the instruction are no longer written, because the execution of the instruction is interrupted. In this case, we recommend that you integrate the two instructions "GET_ERROR" and "GET_ERR_ID" in your program because they provide reliable error information even when this type of error occurs. WARNING Access error when reading an input parameter The RET_VAL parameter does not return a valid error code and no detailed error information is output to the diagnostic buffer. The following example shows you how you can recognize an access error when reading an input parameter: 172 WinCC Basic V13.0 System Manual, 02/2014 Migrating projects and programs 4.3 Programming recommendations WinCC Basic V13.0 System Manual, 02/2014 173 Migrating projects and programs 4.3 Programming recommendations In network 1, the instruction "MOVE_BLK_VARIANT": Move block" is called. The "SrcField" source area is accessed at the SRC parameter using a variable index. If no errors occur during the execution of the instruction, the ENO enable output returns signal state "1", and program execution jumps to network 4 and continues there. If an access error occurs during the execution of the instruction, for example, due to the variable index, the instruction "GET_ERR_ID: Get error ID locally" in network 2 returns an error ID. The comparison of the error ID for "NOT EQUAL" with the value "0" returns the result "Test2" = TRUE. The #TagRet_Val operand at the RET_VAL output parameter returns no valid error code in this case. See also Evaluating errors with output parameter RET_VAL (Page 1738) 4.3.9 Using VARIANT instructions The VARIANT data type The VARIANT data type can be used to create generic function blocks or functions. It is used to interconnect the parameters of the block to tags of any type when called. Parameters of the VARIANT data type can be declared in the sections VAR_IN, VAR_IN_OUT and VAR_TEMP. When the block is called, the type information of the tag is passed in addition to a pointer to the tag. The code of the block can then be executed according to its type with regard to the tags passed during runtime. If, for example, a block parameter of a function has the VARIANT data type, then a tag of the integer data type can be passed at one point in the program, and a tag of the PLC data type can be passed at another point in the program. With the help of the VARIANT instructions, the function is then in a position to react to the situation without errors. Procedure in the S7-300/400 The ANY data type can be used as follows for CPUs of the S7-300/400 series: In SCL and STL, memory of any kind can be passed at a block call when a pointer of the ANY data type has been programmed at a block parameter. However, important information about the structure of the memory is lost because the ANY pointer does not store the information that it points to a tag of the PLC data type, for example. The ANY pointer sees this as an ARRAY of BYTE. Parameters of the ANY data type can be passed to system function blocks (SFBs) or system functions (SFCs). In combination with the ANY data type, you can use the instruction "BLKMOV: Move block" to copy data of any data type in the program. The ANY data type has the following restrictions: 174 WinCC Basic V13.0 System Manual, 02/2014 Migrating projects and programs 4.3 Programming recommendations The ANY pointer has to manually constructed. No data with optimized block access can be passed. The ANY pointer cannot point to structures. Procedure in S7-1500 In the TIA Portal, we recommend that you use the VARIANT data type instead of the ANY pointer. Advantages of the VARIANT data type: Using the VARIANT data type, it is possible to write programs that perform dynamic type definition, i.e. integrated type checking during runtime of the program. The VARIANT data type loses the information about the data type of the tag to which it points. In other words, if the block parameter of a function of the VARIANT data type is supplied with a PLC data type, you can check within the function during runtime whether VARIANT points, for example, to "myUDTa" or "myUDTb". The VARIANT pointer can also be constructed symbolically. This improves the readability of your program code. You can find more information on the advantages of symbolic addressing here: Symbolic addressing (Page 160) Any data can be passed at a parameter of the VARIANT data type. The data type of the actual parameter to which the VARIANT points is determined during runtime. This gives you the possibility to program different responses in the program code depending on the data type of the actual parameter. You can find more information about working with the VARIANT data type in the Siemens Industry online support under: Indirect addressing with the VARIANT data type (http:// support.automation.siemens.com/WW/llisapi.dll?aktprim=0&lang=en&referer=%2fWW %2f&func=cslib.csinfo&siteid=csius&groupid=4000002&extranet=standard&viewreg=WW&n odeid0=29156492&objaction=csopen) The TIA Portal provides, among others, the following instructions of the VARIANT data type as parameters: Basic instructions Programming language Instruction Description LAD/FBD comparator operations EQ_Type Compare data type for EQUAL with the data type of a tag NE_Type Compare data type for UNEQUAL with the data type of a tag EQ_ElemType Compare element data type for EQUAL with the data type of a tag NE_ElemType Compare element data type for UNEQUAL with the data type of a tag IS_NULL Compare for EQUALS ZERO NOT_NULL Compare for UNEQUALS ZERO IS_ARRAY Check for ARRAY TypeOf Check data type of a VARIANT tag TypeOfElements Check element data type of a VARIANT tag IS_ARRAY Check for ARRAY VariantGet Read out VARIANT tag value VariantPut Write VARIANT tag value SCL comparator operations LAD/FBD/SCL/GRAPH move operations WinCC Basic V13.0 System Manual, 02/2014 175 Migrating projects and programs 4.3 Programming recommendations Basic instructions Programming language Instruction Description CountOfElements Get number of ARRAY elements LAD/FBD/STL/SCL/GRAPH move operations ReadFromArrayD Read from the array data block B WriteToArrayDB Write to the array data block ReadFromArrayD Read from the array data block in the load memory BL WriteToArrayDBL Write to array data block in the load memory BLKMOV Move block UBLKMOV Move block uninterruptible FILL Fill block Deserialize Move data type from ARRAY of BYTE (Deserialize) Serialize Move data type to ARRAY of BYTE (Serialize) MOVE_BLK_VAR Move block IANT SCL move operations LAD/FBD/STL/SCL conversion operations READ_LITTLE Read data in little endian format WRITE_LITTLE Write data in little endian format READ_BIG Read data in big endian format WRITE_BIG Write data in big endian format VARIANT_TO_D B_ANY Convert VARIANT to DB_ANY DB_ANY_TO_VA RIANT Convert DB_ANY to VARIANT You can find additional instructions with the VARIANT data type in the online help under "Extended instructions". Example The following example in the SCL programming language shows you a queue (FIFO, First In First Out), which works with elements of any data type. Programmed using the instructions described above. Declaration of the block interface of the "FIFOQueue" function block: Declaration Parameters Data type Comment Input request BOOL The instruction is executed when a positive signal edge is detected at the "request" parameter. mode BOOL 0 = The first entry in the ring buffer is returned. 1 = An entry is written at the last position in the ring buffer. Output 176 initialValue VARIANT Value with which the ARRAY of the ring buffer is initialized. error INT Error information WinCC Basic V13.0 System Manual, 02/2014 Migrating projects and programs 4.3 Programming recommendations Declaration Parameters Data type Comment InOut item VARIANT The entry that is either returned from the ring buffer or written to the ring buffer. buffer VARIANT An ARRAY that is used as a ring buffer. edgeupm BOOL Edge memory bit in which the RLO of the previous query is saved. firstItemIndex INT Index of the oldest entry in the ring buffer nextEmptyItemIndex INT Index of the next free entry in the ring buffer edgeup BOOL Result of edge evaluation internalError INT Error information newFirstItemIndex INT Variable index newNextEmptyItemInde x INT Variable index bufferSize UDINT Number of ARRAY elements in the ring buffer Static Temp Program code of the "FIFOQueue" function block: (* This program code section is only executed once after a positive signal edge. If there is no change in the signal state of the RLO, the program execution of the "FIFOQueue" FB ends. *) #edgeup := #request & NOT #edgeupm; #edgeupm := #request; IF NOT (#edgeup) THEN RETURN; END_IF; // ------Validation of whether all parameter inputs are valid.---(* This program code section checks whether the ring buffer is an ARRAY. If so, the number of the ARRAY elements is read out. If it is not an ARRAY, the program execution is terminated at this point and the error code "-10" is output. *) IF NOT (IS_ARRAY(#buffer)) THEN #error := -10; RETURN; ELSE #bufferSize := CountofElements(#buffer); END_IF; (* This program code section checks whether the data type of the ARRAY elements matches the data type of the entry (tag #item). If the data types do not match, the program execution is terminated at this point and the error code "-11" is output. *) WinCC Basic V13.0 System Manual, 02/2014 177 Migrating projects and programs 4.3 Programming recommendations IF NOT (TypeOf(#item) = TypeOfElements(#buffer)) THEN #error := -11; RETURN; END_IF; (* This program code section checks whether the initial value of the ring buffer matches the entry (tag #item). If the data types do not match, the program execution is terminated at this point and the error code "-12" is output. *) IF NOT (TypeOf(#item) = TypeOf(#initialValue)) THEN #error := -12; RETURN; END_IF; (* This program code section checks whether the variable indices are within the ARRAY limits. If they are not, the program execution is terminated at this point and either error code "-20" or "-21" is output depending on the index. *) IF (#nextEmptyItemIndex >= #bufferSize) THEN #error := -20; RETURN; END_IF; IF (#firstItemIndex >= #bufferSize) THEN #error := -21; RETURN; END_IF; //-----------Program code execution, depending on the Mode parameter------------// The execution of the instructions depends on the signal state of the Mode parameter. IF #mode = 0 THEN // If the Mode parameter has the signal state "0", the first entry from the passed ring buffer is returned. (* This program code section checks whether the ring buffer is empty. If this is the case, program execution is terminated at this point and the error code "-40" is output. *) IF (#firstItemIndex = -1) THEN #error := -40; RETURN; END_IF; // This program code section returns the first entry of the ring buffer. #internalError := MOVE_BLK_VARIANT(SRC := #buffer, COUNT := 1, SRC_INDEX := #firstItemIndex, DEST_INDEX := 0, DEST => #item); 178 WinCC Basic V13.0 System Manual, 02/2014 Migrating projects and programs 4.3 Programming recommendations IF (#internalError = 0) THEN (* This program code section checks whether the ring buffer contains ARRAY elements. If it does, the first entry is passed further on and the index is incremented by 1. *) #internalError := MOVE_BLK_VARIANT(SRC := #initialValue, COUNT := 1, SRC_INDEX := 0, DEST_INDEX := #firstItemIndex, DEST => #buffer); // This program code section calculates the new index of the first entry. #newFirstItemIndex := #firstItemIndex +1; #newFirstItemIndex := #newFirstItemIndex MOD #bufferSize; // This program section checks whether the ring buffer is empty. IF (#nextEmptyItemIndex = #newFirstItemIndex) THEN // If the ring buffer is empty, the index is set to 0. #firstItemIndex := -1; #nextEmptyItemIndex := 0; ELSE // The index of the first entry is changed. #firstItemIndex := #newFirstItemIndex; END_IF; END_IF; ELSE // If the Mode parameter has the signal state "1", the entry is written to the passed ring buffer. (* This program code section checks whether the ring buffer is full. If this is the case, program execution is terminated at this point and the error code "-50" is output. *) IF (#nextEmptyItemIndex = #firstItemIndex) THEN #error := -50; RETURN; END_IF; // This program code section writes the entry to the ring buffer. #internalError := MOVE_BLK_VARIANT(SRC := #item, COUNT := 1, SRC_INDEX := 0, DEST_INDEX := #nextEmptyItemIndex, DEST => #buffer); IF (#internalError = 0) THEN WinCC Basic V13.0 System Manual, 02/2014 179 Migrating projects and programs 4.3 Programming recommendations // This program code section increments the index by 1 and calculates the new empty entry index. #newNextEmptyItemIndex := #nextEmptyItemIndex +1; #newNextEmptyItemIndex := #newNextEmptyItemIndex MOD #bufferSize; #nextEmptyItemIndex := #newNextEmptyItemIndex; (* This program code section checks which index the "#firstItemIndex" tag has. If the number = -1, the ring buffer is initialized and the entry is written to the ring buffer. Therefore, "0" must be assigned to the tag. *) IF (#firstItemIndex = -1) THEN #firstItemIndex := 0; END_IF; END_IF; END_IF; //-------------------------Local error handling---------------------------(* This program code section checks whether a local error has occurred. If this is the case, program execution is terminated at this point and the error code "-100" is output. *) IF (#internalError > 0) THEN #error := -100; RETURN; END_IF; // If no error occurred during program execution, the error code "0" is output. #error := 0; 180 WinCC Basic V13.0 System Manual, 02/2014 5 First steps 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 for STEP 7 and WinCC 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 and WinCC Basic (V10.5) (http://support.automation.siemens.com/WW/ view/en/40263542/0/en) STEP 7 Professional and WinCC Advanced (V11) (http://support.automation.siemens.com/ WW/view/en/28919804/133300) STEP 7 Professional and WinCC Advanced (V12) (http://www.automation.siemens.com/ salesmaterial-as/interactive-manuals/getting-started_simatic-s7-1500/_content/EN/ content_en.html) WinCC Basic V13.0 System Manual, 02/2014 181 6 Introduction to the TIA Portal 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 V13". 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: 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 WinCC Basic V13.0 System Manual, 02/2014 183 Introduction to the TIA Portal 6.1 User interface and operation Group Setting Description 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 Load most recent project during startup The last opened project is opened automatically after the TIA Portal starts. Displaying truncated text in full Texts which are truncated due to their length are displayed in a tooltip. Show tooltips (contextTooltips are displayed and you get context-sensitive help. If this sensitive help is available) function is disabled, you can open the tooltip with <F1>. Reset to default Start view View for objects in overview Storage settings 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. All application settings All changes that you made in the TIA Portal after installation are reversed. Layout of the editors Resets the complete layout of the application to the factory state. Show all message windows All message windows whose appearance was manually suppressed are displayed again. Most recent view Starts the program in the last view that was used. This can 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. 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. 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 Configuration file for corporate libraries Data exchange 184 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. WinCC Basic V13.0 System Manual, 02/2014 Introduction to the TIA Portal 6.1 User interface and operation See also Starting and exiting the TIA Portal (Page 183) Resetting the user interface layout (Page 217) Changing the settings (Page 186) Configuring the display of tooltips and tooltip cascades (Page 237) 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 Operands Scripts Standard functions Instructions/system functions Constant strings Numeric constants Constant tags Tags Object models Formal parameters Reset to default Resets all font colors in editors to their factory settings. Tab width Sets the width of tabs. Use tabs Enables the use of tabs. Use spaces Specifies use of space characters instead of tabs. None Text entries are not automatically indented. Block The lines or the selected paragraph are automatically indented. Smart The lines or the selected paragraph are automatically indented. All unnecessary spaces are also removed. View 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) Show line numbers Shows the row numbers in SCL programs. Tabs Indent WinCC Basic V13.0 System Manual, 02/2014 185 Introduction to the TIA Portal 6.1 User interface and operation See also Changing the settings (Page 186) 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. 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. Motion & Technology Dialog display/graphic HMI screens The content of the editor is printed out as a graphic if the editor supports this. Table The parameters of the technology objects are printed out in the form of a table. 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 186) 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. 186 WinCC Basic V13.0 System Manual, 02/2014 Introduction to the TIA Portal 6.1 User interface and operation Result The change will be adopted immediately, there is no need to save it explicitly. See also Overview of the program settings (Page 183) Overview of the script and text editor settings (Page 185) Overview of the print settings (Page 186) 6.1.2 Layout of the user interface 6.1.2.1 Views Views Three 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. The library view (Page 191) shows the elements of the project library and the open global libraries. 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 189) for the selected task. WinCC Basic V13.0 System Manual, 02/2014 187 Introduction to the TIA Portal 6.1 User interface and operation 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. 188 WinCC Basic V13.0 System Manual, 02/2014 Introduction to the TIA Portal 6.1 User interface and operation 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 tree (Page 192) Basics of the work area (Page 195) Inspector window (Page 203) Basics on task cards (Page 205) Details view (Page 209) 6.1.2.3 Project view Purpose of the project view The project view is a structured view of all components of the project. WinCC Basic V13.0 System Manual, 02/2014 189 Introduction to the TIA Portal 6.1 User interface and operation Layout of the project view The following figure shows an example of the components of the project view: 190 Title bar Menu bar Toolbar Project tree (Page 192) Reference projects (Page 207) Details view (Page 209) Work area (Page 205) Dividers Inspector window (Page 203) Changing to the Portal view (Page 187) Editor bar Status bar with progress display Task cards (Page 205) WinCC Basic V13.0 System Manual, 02/2014 Introduction to the TIA Portal 6.1 User interface and operation 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. Dividers Dividers separate individual components of the program interface. The arrows on the dividers allow you to display and hide the adjacent sections of the user interface. 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. See also Basics of the work area (Page 195) 6.1.2.4 Library view Function of the library view The library view provides an overview of the elements in the project library and the open global libraries. You can switch to the library view using the "Libraries" task card. WinCC Basic V13.0 System Manual, 02/2014 191 Introduction to the TIA Portal 6.1 User interface and operation See also: Overview of the library view (Page 330) 6.1.2.5 Project tree 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 You can select the objects of the project tree either with the mouse or via the keyboard by typing the first letter of the desired object. If more than one object begins with the same letter, the next lower object is selected. The project tree must be the focused user interface element in order for you to select an object with its initial letter. 192 WinCC Basic V13.0 System Manual, 02/2014 Introduction to the TIA Portal 6.1 User interface and operation Layout of project tree The following figure shows an example of the project tree components: 1 2 3 4 5 6 7 8 9 WinCC Basic V13.0 System Manual, 02/2014 193 Introduction to the TIA Portal 6.1 User interface and operation Title bar Toolbar Project Devices Common data Documentation settings Languages & resources Online access Card Reader / USB memory 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 197) 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. 194 WinCC Basic V13.0 System Manual, 02/2014 Introduction to the TIA Portal 6.1 User interface and operation Common data This folder contains data that you can use across more than one device, such as common message classes, logs, scripts and text lists. Documentation settings 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. Card Reader / USB memory This folder is used to manage all card readers an other USB storage media connected to the programming device / PC. See also Portal view (Page 187) Project view (Page 189) Basics of the work area (Page 195) Inspector window (Page 203) Basics on task cards (Page 205) Details view (Page 209) 6.1.2.6 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 WinCC Basic V13.0 System Manual, 02/2014 195 Introduction to the TIA Portal 6.1 User interface and operation 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. Layout of the work area The following figure shows an example of a vertically split work area: 196 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 WinCC Basic V13.0 System Manual, 02/2014 Introduction to the TIA Portal 6.1 User interface and operation See also Maximizing and minimizing the work area (Page 197) Splitting the work area (Page 199) Floating the work area elements (Page 199) Using grouped elements of the work area (Page 200) Minimizing and maximizing elements of the work area (Page 202) Switching between the elements in the work area (Page 202) Saving a layout of editors and tables (Page 216) Save user interface layout (Page 214) 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: WinCC Basic V13.0 System Manual, 02/2014 197 Introduction to the TIA Portal 6.1 User interface and operation 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 195) Splitting the work area (Page 199) Floating the work area elements (Page 199) Using grouped elements of the work area (Page 200) Minimizing and maximizing elements of the work area (Page 202) Switching between the elements in the work area (Page 202) Saving a layout of editors and tables (Page 216) 198 WinCC Basic V13.0 System Manual, 02/2014 Introduction to the TIA Portal 6.1 User interface and operation 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 195) Maximizing and minimizing the work area (Page 197) Floating the work area elements (Page 199) Using grouped elements of the work area (Page 200) Minimizing and maximizing elements of the work area (Page 202) Switching between the elements in the work area (Page 202) Saving a layout of editors and tables (Page 216) 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. Note Properties of elements in a floating window The properties of elements that you have selected in a floating window are only displayed in the Inspector window if the Inspector window is floating as well. WinCC Basic V13.0 System Manual, 02/2014 199 Introduction to the TIA Portal 6.1 User interface and operation 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 195) Maximizing and minimizing the work area (Page 197) Splitting the work area (Page 199) Using grouped elements of the work area (Page 200) Minimizing and maximizing elements of the work area (Page 202) Switching between the elements in the work area (Page 202) Saving a layout of editors and tables (Page 216) 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. 200 WinCC Basic V13.0 System Manual, 02/2014 Introduction to the TIA Portal 6.1 User interface and operation 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 195) Maximizing and minimizing the work area (Page 197) Splitting the work area (Page 199) Floating the work area elements (Page 199) Minimizing and maximizing elements of the work area (Page 202) Switching between the elements in the work area (Page 202) Saving a layout of editors and tables (Page 216) WinCC Basic V13.0 System Manual, 02/2014 201 Introduction to the TIA Portal 6.1 User interface and operation 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 195) Maximizing and minimizing the work area (Page 197) Splitting the work area (Page 199) Floating the work area elements (Page 199) Using grouped elements of the work area (Page 200) Switching between the elements in the work area (Page 202) Saving a layout of editors and tables (Page 216) Switching between the elements in the work area You can switch between the elements in the work area at any time. 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 195) Maximizing and minimizing the work area (Page 197) 202 WinCC Basic V13.0 System Manual, 02/2014 Introduction to the TIA Portal 6.1 User interface and operation Splitting the work area (Page 199) Floating the work area elements (Page 199) Using grouped elements of the work area (Page 200) Minimizing and maximizing elements of the work area (Page 202) Saving a layout of editors and tables (Page 216) 6.1.2.7 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: WinCC Basic V13.0 System Manual, 02/2014 "Properties" tab "Info" tab "Diagnostics" tab Area navigation within the "Properties" tab Content of the "Properties" tab 203 Introduction to the TIA Portal 6.1 User interface and operation "Properties" tab "Info" tab "Diagnostics" tab Navigation within the tabs (only available in the "Info" and "Diagnostics" tabs) Content of the "Diagnostics" tab "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 tree (Page 192) Basics of the work area (Page 195) Portal view (Page 187) Project view (Page 189) 204 WinCC Basic V13.0 System Manual, 02/2014 Introduction to the TIA Portal 6.1 User interface and operation Basics on task cards (Page 205) Details view (Page 209) 6.1.2.8 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. WinCC Basic V13.0 System Manual, 02/2014 205 Introduction to the TIA Portal 6.1 User interface and operation Layout of task cards The following figure shows an example of the bar with the task cards: Task cards closed Task card open Opened palette of a task card Closed palette of a task card See also Changing the pane mode (Page 207) Project tree (Page 192) Basics of the work area (Page 195) Inspector window (Page 203) Portal view (Page 187) Project view (Page 189) Details view (Page 209) 206 WinCC Basic V13.0 System Manual, 02/2014 Introduction to the TIA Portal 6.1 User interface and operation Changing the pane mode You can choose between two pane modes: Single pane mode: Only one pane is open at any given time. If you open another pane, the previously opened pane is closed automatically. Multi-pane mode: You can open several panes at the same time. Procedure To change the pane mode, follow these steps: 1. Click the "Change pane mode" button above the panes inside a task card. See also Basics on task cards (Page 205) 6.1.2.9 Reference projects Function of reference projects In the "Reference projects" palette, you can open other projects in addition to the current project. These reference projects are write-protected and cannot be edited. However, you can drag the objects of a reference project into your current project and further edit them there. You can also compare the objects of a reference project to the objects of your current project. Layout of the "Reference projects" palette The following figure shows the layout of the "Reference projects" palette: WinCC Basic V13.0 System Manual, 02/2014 207 Introduction to the TIA Portal 6.1 User interface and operation 1 2 3 Title bar Toolbar Opened reference projects Title bar The arrow for closing the palette is located in the title bar of the "Reference projects" palette. Once it is closed, the direction in which the arrow is pointing changes from downwards to right. It can now be used to reopen the palette. Toolbar The toolbar contains buttons for opening and closing reference projects. Opened reference projects Opened reference projects are displayed as read-only with their objects and their hierarchical structure. See also Basics of reference projects (Page 261) Opening and closing a reference project (Page 261) 208 WinCC Basic V13.0 System Manual, 02/2014 Introduction to the TIA Portal 6.1 User interface and operation 6.1.2.10 Details view Purpose of the details view The detail view shows certain content of the selected object is in the overview window or in the project tree. This might include text lists or tags. The content of folders is not shown, however. To display the content of folders, use the project tree or the Inspector window. Layout of the details view The following figure shows an example of the details view: 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 tree (Page 192) Basics of the work area (Page 195) Inspector window (Page 203) Basics on task cards (Page 205) WinCC Basic V13.0 System Manual, 02/2014 209 Introduction to the TIA Portal 6.1 User interface and operation Portal view (Page 187) Project view (Page 189) 6.1.2.11 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-anddrop and moving, copying, pasting, and deleting objects 210 WinCC Basic V13.0 System Manual, 02/2014 Introduction to the TIA Portal 6.1 User interface and operation Layout of the Overview window The following figure shows the components of the Overview window: 1 5 6 6 7 2 3 4 8 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. All elements within a selected folder are displayed even if these are located in lower-level groups. This option is only available in details view. Contents of the object selected in the project tree. WinCC Basic V13.0 System Manual, 02/2014 211 Introduction to the TIA Portal 6.1 User interface and operation 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 according to category. See also Comparing objects in the overview window (Page 212) Sorting the details view of the overview window (Page 213) Overview of the library view (Page 330) Comparing objects in the overview window 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 210) 212 WinCC Basic V13.0 System Manual, 02/2014 Introduction to the TIA Portal 6.1 User interface and operation Sorting the details view of the overview window You have several options for adapting the display in the details view of the overview window: Adding additional columns Some columns are hidden by default to increase clarity. You can display hidden columns if needed. The columns available depend on the selected object. Display of folder contents in a flat hierarchy Folder contents can be displayed in a flat hierarchy. All the content is displayed at once even if it is located in different groups. Sorting the table columns You can sort individual columns of the table in ascending or descending order. Showing or hiding columns 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. Displaying folder contents in flat hierarchy To display the content of a folder in a flat hierarchy, follow these steps: 1. Select the required folder in the project tree or in the library navigation of the library view. 2. Click the "Show subordinate elements" icon in the toolbar. All elements are displayed at once in the table even if they are located in subfolders. Sorting a table in ascending or descending order To sort the table by a column in ascending or descending order, follow the steps below: 1. Click the table header of a column if you want to sort the column in ascending order. 2. Click again on the same column of the table header to sort the column in descending order. 3. Click a third time on the table header of the same column to cancel the sorting. See also Overview window (Page 210) WinCC Basic V13.0 System Manual, 02/2014 213 Introduction to the TIA Portal 6.1 User interface and operation 6.1.2.12 User interface layout Save user interface layout Options for saving the user interface layout When you make a change to the user interface, this is retained even after a restart of the TIA portal. A change to the user interface layout includes, for example, moving a window or adjusting the size of an editor. In addition to the automatic saving of the user interface layout, you have the option of saving certain layouts: Saving the window layout You can save the layouts of the windows and editors of the TIA portal manually and restore these at a later time. It is possible to call five window layouts using a key combination. Use this function, for example, if you are work with a notebook which you connect to an external monitor when necessary. You can create a window layout for mobile use on the notebook display and another layout for when you work at the office with an external monitor. Save the layout within editors With some editors, you can adjust the display. You can, for example, adjust the width of tables or show or hide individual table columns. See also Save window layout (Page 214) Load window layout (Page 215) Managing window layouts (Page 216) Saving a layout of editors and tables (Page 216) Resetting the user interface layout (Page 217) Basics of the work area (Page 195) Save window layout You can save the current window layout in order to call it again in the same form at a later time. Procedure To save a window layout, follow these steps: 1. Arrange all windows in the way in which you want to save them. 2. In the "Window" menu, select the "Save window layout as" command. The "Save window layout" dialog box appears. 3. Enter a name for the window layout in the "Name" field. 214 WinCC Basic V13.0 System Manual, 02/2014 Introduction to the TIA Portal 6.1 User interface and operation 4. Enter a description of the window layout in the "Description" field in order to be able to identify the window layout more easily later. 5. Click "Save". Result The new window layout is saved in the last position after the existing saved window layouts. The first five window layouts can be called using a key combination. See also Save user interface layout (Page 214) Load window layout If you have already saved a window layout, you can load this, allowing you to quickly adjust your work environment to the respective conditions. You can load the first five window layouts using quick access via the "Window" menu or via a key combination. If you load a window layout and then make changes to the arrangement of the window, you can restore the originally saved window layout. Using quick access to load window layouts 1 to 5 To load one of the first five saved window layouts, follow these steps: 1. In the "Window" menu, select a window layout or select the key combination <Alt+Shift+[1 ... 5]>. Loading additional window layouts To load a window layout that is not among the first five window layouts, follow these steps: 1. In the "Window" menu, select the "Additional window layouts" command. The "Manage window layouts" dialog box appears. 2. Select the desired window layout. 3. Click "OK". Restore window layout To go back to a saved window layout, follow these steps: 1. In the "Window" menu, select the "Restore window layout" command or select the key combination <Alt+Shift+0>. See also Save user interface layout (Page 214) WinCC Basic V13.0 System Manual, 02/2014 215 Introduction to the TIA Portal 6.1 User interface and operation Managing window layouts You can carry out the following actions with existing window layouts: Changing the order of window layouts The order of the window layouts is important, as the first five window layouts can be called directly via the "Window" menu and via a key combination. Select a window layout If a window layout is not one of the first five window layouts, you can call it using the "Manage window layouts" dialog box. Deleting window layouts Procedure To manage the existing window layouts, follow these steps: 1. In the "Window" menu, select the "Manage window layouts" command. The "Manage window layouts" dialog box appears. 2. Select the window layout which you want to modify. 3. Click the "Up" or "Down" symbol to move the window layout up or down. 4. Click the "Delete" symbol to delete the selected window layout. 5. Click "OK". The selected window layout is activated. See also Save user interface layout (Page 214) 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. 216 WinCC Basic V13.0 System Manual, 02/2014 Introduction to the TIA Portal 6.1 User interface and operation See also Basics of the work area (Page 195) Maximizing and minimizing the work area (Page 197) Splitting the work area (Page 199) Floating the work area elements (Page 199) Using grouped elements of the work area (Page 200) Minimizing and maximizing elements of the work area (Page 202) Switching between the elements in the work area (Page 202) Save user interface layout (Page 214) 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, if another user prefers a different arrangement of the user interface. Procedure To reset the user interface settings to the default, 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 "Reset to default > Editor layout". Result The default settings for the user interface are restored. See also Overview of the program settings (Page 183) Save user interface layout (Page 214) WinCC Basic V13.0 System Manual, 02/2014 217 Introduction to the TIA Portal 6.1 User interface and operation 6.1.3 Keyboard operation in the TIA Portal 6.1.3.1 Operating the TIA Portal with the keyboard You can navigate through the TIA Portal using the keyboard, for example if you do not have a mouse available at the given moment. Many functions are also accessible via keyboard shortcuts. You can find an overview of all keyboard shortcuts in the settings for the TIA Portal. In the following sections, you will learn how to navigate in the TIA Portal using the keyboard, edit objects and customize the TIA Portal to your needs. See also Displaying an overview of all keyboard shortcuts (Page 218) 6.1.3.2 Displaying an overview of all keyboard shortcuts You can display an overview of all keyboard shortcuts. Procedure To display an overview of all available keyboard shortcuts, follow these steps: 1. Select the "Settings" command in the "Options" menu. The settings of the TIA Portal are displayed. 2. Open the "Keyboard shortcuts" entry in the area navigation. You can see an overview of all keyboard shortcuts, which are valid for the currently installed products. 6.1.3.3 Basic functions of the TIA Portal Below, you will learn how you can use the basic functions of the TIA Portal using only your keyboard. Operating basic functions of the TIA Portal with a keyboard The following table shows how you can access basic functions of the TIA Portal with keyboard shortcuts: Function Keyboard shortcuts Switch between the project view and the portal view <Alt+F7> Open the Help system <F1> Menu command Help > Show help If you need help on the TIA Portal, press <F1>. Cancel the current action <Esc> Find <Ctrl+F> Replace an object <Ctrl+H> 218 WinCC Basic V13.0 System Manual, 02/2014 Introduction to the TIA Portal 6.1 User interface and operation Function Keyboard shortcuts Find next <F3> Menu command If you have started a search, you can jump to the next hit with <F3> Print object <Ctrl+P> Project > Print Operating menus The following table shows how you can navigate through menus using the keyboard: Function Keyboard shortcuts Start keyboard operation in the menu <Alt> You can access the menu using the <Alt> key and then continue to navigate with the arrow keys to scroll through the menu. Confirm your selection of the menu command with <Return>. Go directly to a specific menu You can go directly to an individual menu command by holding down the <Alt> key. There is an underlined letter for each menu command. Press the <Alt> key along with the underlined letter. <Alt+underlined letter in respective menu> Open shortcut menu of an object <Shortcut menu key> With the shortcut menu key (on Microsoft Windows compatible keyboards), you can open the shortcut menu of the selected object. Alternatively, you can use <Shift+F10> if you are not using a Microsoft Windows compatible keyboard. You can use the arrow keys to scroll through the shortcut menu and select a menu command with <Return>. Alternative: <Shift+F10> Operating expandable elements The following table shows how you can operate expandable elements using the keyboard: Function Keyboard shortcuts Expand a folder in a tree <Arrow right> With <Arrow right>, for example, you expand a folder in the project tree. Close a folder in a tree <Arrow left> With <Arrow left>, for example, you collapse a folder in the project tree. Open a drop-down list <F4> You can open drop-down lists with <F4> and then navigate with the arrow keys to scroll through the drop-down list. Finally, press the <Return> key to confirm your selection. Open autocompletion <Ctrl+Space> <Ctrl+I> Show object selection WinCC Basic V13.0 System Manual, 02/2014 <Ctrl+J> 219 Introduction to the TIA Portal 6.1 User interface and operation 6.1.3.4 Using project-related functions Editing a project Function Keyboard shortcuts 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 Delete a project <Ctrl+E> Project > Delete project Print project <Ctrl+P> Project > Print Undo last action <Ctrl+Z> Edit > Undo Redo last action <Ctrl+Y> Edit > Redo Calling up the help function Function Keyboard shortcuts Menu command Calling up the help function <F1> or <Shift+F1> Help > Show help 6.1.3.5 Arranging windows Below, you will learn how to open and close individual windows of the TIA Portal and save window layouts using the keyboard . Opening and closing windows The following table shows how you can open and close windows with keyboard shortcuts: Function Keyboard shortcuts 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 libraries <Ctrl+Shift+L> Open hardware catalog If you are in the device or network view, the hardware catalog opens. <Ctrl+Shift+C> Open/close inspector window <Ctrl+5> Open the "Properties" tab in the inspector window <Ctrl+6> Open the "Info" tab in the Inspector window <Ctrl+7> Open the "Diagnostics" tab in the Inspector window <Ctrl+8> Display or hide reference projects <Ctrl+9> 220 View > Inspector window WinCC Basic V13.0 System Manual, 02/2014 Introduction to the TIA Portal 6.1 User interface and operation Function Keyboard shortcuts Display the on-screen keyboard <Ctrl+Shift+K> Menu command You can display a keyboard on the screen, for example, to operate with a touch screen. Close all editors <Ctrl+Shift+F4> Window > Close all Using saved window layouts You can save individual window arrangements and restore them at a later point in time. The following table shows how you to access saved window layouts with keyboard shortcuts: Function Keyboard shortcuts Menu command Restore active window layout <Shift+Alt+0> Window > Restore window layout <Shift+Alt+[Number of the window layout]> Window > Window layout 1 to 5 If you use a saved window layout and have made changes to the program interface in the meantime, you can restore the original state of the active window layout with <Alt+Shift+0>. Load window layout You can use <Alt+Shift+[number of the window layout]> to activate the first of the five saved window layouts. 6.1.3.6 Navigating through the program interface The TIA Portal is divided into several interface areas, for example, individual windows, toolbars and editors. If you want to work with the keyboard within an interface area, you first have to place the focus on it. Below, you will learn how to place the focus on individual interface areas using the keyboard. You will also learn how to move within an interface area in the TIA Portal using the keyboard. Switching between interface areas and editors The following table shows how to move between individual interface areas of the TIA Portal: Function Keyboard shortcuts Move clockwise between the interface areas <F6> You can use the <F6> key to move clockwise between the various interface areas of the TIA Portal. The interface area currently in focus is highlighted with a blue title bar. If you are in the project tree, for example, and press the <F6> key, you jump to the currently open editor. If you press <F6> again, and the task cards are in focus. If you press <Shift+F6>, on the other hand, you move counterclockwise between the work areas. Move counter-clockwise between the interface areas <Shift+F6> With <Shift+F6> you move counter-clockwise between the interface areas of the TIA Portal. Go to the next open editor <Ctrl+Alt+Arrow right> With <Ctrl+Alt+Arrow right> you move to the next open editor. You can see the open editors Alternative: <Ctrl+F6> in the editor toolbar. WinCC Basic V13.0 System Manual, 02/2014 221 Introduction to the TIA Portal 6.1 User interface and operation Function Keyboard shortcuts Go to the previously open editor <Ctrl+Alt+Arrow left> With <Ctrl+Alt+Arrow left> you move to the most recently open editor. Alternative: <Ctrl+Shift+F6> Go to the next higher section of the interface area <Shift+Esc> With <Shift+Esc>, you move to the next higher section of the program interface. If, for example, you have selected a device in the project tree and you press <Shift+Esc>, the entire project navigation is put into focus. Alternative: <Alt+Arrow up> Go to the next lower section of the interface area <Return> With <Return>, you place the focus on the next lower section of the program interface. For example, if you have just opened the properties of a device in the Inspector window in order to assign parameters to the device, press <Return> to go one level deeper in the program interface. You can then navigate to the desired parameter using the Tab key. Alternative: <Alt+Arrow down> Navigation within interface areas and editors The following table shows how you can navigate within an interface area using the keyboard: Function Keyboard shortcuts Jump to the next element within an interface area <Tab> You can use the Tab key to jump from one element to the next within a work area. If, for example, you have opened the properties of a device and want to jump from one field to the next, press the Tab key. Any changes you have made to the current text box are applied in this case. Jump to the previous element within an interface area <Shift+Tab> With <Shift+Tab>, you can jump to the previous element in a work area, for example, a previous text box. Any changes you have made to the current text box are applied in this case. Move to the next tab within an interface area <Ctrl+Tab> If an interface area is divided into separate tabs, you can move between the tabs with the shortcut keys <Ctrl+Tab>. If, for example, you are in the "Properties" tab of the Inspector window and you want to jump to the "Info" tab, press the shortcut keys <Ctrl+Tab>. Go to the previous tab <Ctrl+Shift+Tab> With <Ctrl+Shift+Tab>, you move to the most recently open tab within an interface area. Jumping to the toolbar of an editor <Alt+F10> You can use the <Alt+F10> key to jump to the toolbar of an editor. For example, if you have opened the print preview and want to switch to the next page of the printout in the toolbar, press <Alt+F10>. Then, use the arrow keys to navigate to the appropriate icon in the toolbar and confirm the selection with <Return>. Use arrows on the divider to display or hide user interface components <Space> The table in the work area can be minimized and maximized. First, navigate to the work area and use the Tab key to place the focus on one of the little arrows on the separator line above the table. The arrows have the focus as soon as they are highlighted in blue. Then, press the space bar to minimize or maximize the table. 6.1.3.7 Customizing editors Below, you will learn how to arrange editors using the keyboard. You will also learn how to select the display size and the area within a graphical editor. 222 WinCC Basic V13.0 System Manual, 02/2014 Introduction to the TIA Portal 6.1 User interface and operation Arranging and customizing editors The following table shows how to arrange open editors above and below each other or sideby-side, and how to close an open editor: Function Keyboard shortcuts Close active editor <Ctrl+F4> Split editor space vertically <F12> Window > Split editor space vertically <Ctrl+F12> Window > Split editor space horizontally <Alt+Shift+F12> Window > Unsplit editor space If, for example, you have opened the overview window and the network view and want to display them side-by-side, press the <F12> key. Split editor space horizontally You can display two open editors in the work area above and below each other. Remove window split Menu command If you have displayed two editors in the work area horizontally or vertically in split mode, you can remove the split with <Alt+Shift +F12>. Customizing the display in an editor The following table shows how you how to zoom in and out in graphical editors and how to move the area selection in an editor: Function Keyboard shortcuts Zoom in step-by-step in an editor <Ctrl+Plus> With <Ctrl> and the <Plus> key on the numeric keypad of the keyboard, you can zoom in on the display of the editor. Alternative: <Ctrl+mousewheel up> Zoom out step-by-step in an editor <Ctrl+Minus> Use the <Ctrl> and the <Minus> key on the numeric keypad of the keyboard to zoom out of the display of the editor. Alternative: <Ctrl+mousewheel down> Set view in editor to 100% <Ctrl+0> You can zoom in or out of the display in a graphical editor to set the current view to 100% by pressing <Ctrl+0>. Moving the area selection of the editor <Space> If you hold down the spacebar, you can move the displayed section of an editor using the mouse. WinCC Basic V13.0 System Manual, 02/2014 223 Introduction to the TIA Portal 6.1 User interface and operation 6.1.3.8 Editing objects Selecting objects The following table shows how to select individual objects, for example, devices in the project tree: Function Keyboard shortcuts Select an object located at the left, right, above or below <Arrow keys> Jump to the first object within the current interface area <Home> Menu command The first object in the interface area currently in focus is selected. In the project tree, this would be the project node at the top, for example. Jump to the last object within the current interface area <End> The last object in the interface area currently in focus is selected, for example, the last item in the project tree. Select all objects in an area <Ctrl+A> Edit > Select all All objects in the work area currently in focus are selected. Select multiple objects If you want to select several objects that are not located directly next to each other, you first have to move the focus (gray outline of an object) to the next desired object using <Ctrl+Arrow keys>. The current selection is maintained. Then, press the space bar to select the new focused object as well. Repeat this process until all desired objects are selected. <Ctrl+Arrow keys> + <Space> Editing objects The following table provides an overview of all the keyboard shortcuts required for editing objects: Function Keyboard shortcuts Insert new object <Ctrl+N> Menu command A new object is inserted depending on your current context. If, for example, you are in the device view, the "Add Device" dialog opens for creating a new device. Open object <Return> Rename an object <F2> Edit > Rename Copy an object <Ctrl+C> Edit > Copy Alternative: <Ctrl+Ins> Cut an object <Ctrl+X> Edit > Cut Alternative: <Shift+Del> Paste an object <Ctrl+V> Edit > Paste Alternative: <Shift+Ins> Delete an object 224 <Del> Edit > Delete WinCC Basic V13.0 System Manual, 02/2014 Introduction to the TIA Portal 6.1 User interface and operation Function Keyboard shortcuts Menu command Compile an object <Ctrl+B> Edit > Compile Open properties of an object <Alt+Return> - Many objects in the TIA Portal have editable properties. Press the shortcut keys <Alt+Enter> to display the properties of an object. 6.1.3.9 Text editing Below, you will learn how to operate text editing functions using only the keyboard. Editing text The following table shows the basic editing functions for text: Function Keyboard shortcuts Switch to insert or overwrite mode <Insert> Exit edit mode <Esc> Delete <Del> Delete characters <Backspace> Confirm entry in a text box and leave the text box <Return> Line break in a multiline text box <Shift+Return> In a multiline text box, hold down the <Shift> button to create a line break. Reset input in a text box <Esc> If you are in an text box and press <Esc>, you exit the box and the changes are discarded. Navigating within a text area The following table shows how to navigate in a text area with the keyboard: Function Keyboard shortcuts Jump to start of line <Home> Jump to end of line <End> Jump to start of text <Ctrl+Home> Jump to end of text <Ctrl+End> Jump to the previous page <PgUp> Jump to the next page <PgDn> Confirm entry in a text box and leave the text box <Return> Line break in a multiline text box <Shift+Return> Reset input in a text box <Esc> If you are in an text box and press <Esc>, you exit the box and the changes are discarded. WinCC Basic V13.0 System Manual, 02/2014 225 Introduction to the TIA Portal 6.1 User interface and operation Selecting text The following table shows how to select text with the keyboard: Function Keyboard shortcuts Expand selection to the word at the left or right <Ctrl+Shift+Arrow left or Arrow right> The text or current text selection is marked up to the end of word. If you are at the beginning or end of a word, the previous or next word is selected. Expand selection to beginning of line <Shift+Home> Expand selection to end of line <Shift+End> Expand selection to beginning of text <Ctrl+Shift+Home> The text is selected up to the beginning or the end. Expand selection to end of text <Ctrl+Shift+End> The text is selected up to the beginning or the end. 6.1.3.10 Editing tables Below, you will learn how to navigate with the keyboard in tables, edit individual fields, and select parts of tables. General keyboard operation in tables The following table shows how you can edit tables using only the keyboard: Function Keyboard shortcuts Place a cell in edit mode <F2> or <Return> Confirm entry and exit edit mode <Return> Cancel editing and discard changes <Esc> Open drop-down list in a cell <F4> Open the drop-down list with <F4>. Use the arrow keys to select the desired entry and then confirm the selection with <Return>. Close drop-down list in a cell and discard changes <Esc> Navigate in tables The following table shows how you can navigate within a table using the keyboard: Function Keyboard shortcuts 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> Move a screen downwards <PgDn> Go to the first cell in the row <Home> 226 WinCC Basic V13.0 System Manual, 02/2014 Introduction to the TIA Portal 6.1 User interface and operation Function Keyboard shortcuts 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+Arrow up> Go to the bottom cell in the column <Ctrl+Arrow down> Selecting areas in tables The following table shows how you can select areas within a table using the keyboard: Function Keyboard shortcuts Select column <Ctrl+Space> Select line <Shift+Space> Select all cells <Ctrl+A> Expand selection by one cell <Shift+arrow keys> Extend selection up one page <Shift+PgUp> Extend selection down one page <Shift+PgDn> Expand selection up to the first row <Ctrl+Shift+Arrow up> Expand selection down to the last row <Ctrl+Shift+Arrow down> Expand selection to the first cell in the row <Ctrl+Shift+Arrow left> Expand selection to the last cell in the row <Ctrl+Shift+Arrow right> 6.1.3.11 Using online functions Controlling online functions with the keyboard The following table provides an overview of the shortcut keys that you can use for the online functions of the TIA Portal: Function Keyboard shortcuts Menu command Establish an online connection <Ctrl+K> Online > Go online Go offline <Ctrl+M> Online > Go offline Download project data to the device <Ctrl+L> Online > Download to device Show accessible devices <Ctrl+U> Online > Show accessible devices <Ctrl+Shift+E> Online > Start CPU This opens a dialog showing all devices that are connected to the PG/ PC interface of the PG/PC. Start CPU The CPU is set to "RUN" mode. The CPU must be online for this. WinCC Basic V13.0 System Manual, 02/2014 227 Introduction to the TIA Portal 6.1 User interface and operation Function Keyboard shortcuts Menu command Stop CPU <Ctrl+Shift+Q> Online > Stop CPU <Ctrl+Shift+X> Online > Simulation > Start The CPU is set to "STOP" mode. The CPU must be online for this. Start simulation The hardware and software of the project can be tested in a simulated online environment, without the modules actually being online. 6.1.3.12 Using the on-screen keyboard Introduction When working with the TIA portal, you also have the Microsoft on-screen keyboard available. 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. 228 WinCC Basic V13.0 System Manual, 02/2014 Introduction to the TIA Portal 6.1 User interface and operation 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. 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. WinCC Basic V13.0 System Manual, 02/2014 229 Introduction to the TIA Portal 6.2 Help on the information system 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. 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 supplied with the TIA Portal 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): 230 WinCC Basic V13.0 System Manual, 02/2014 Introduction to the TIA Portal 6.2 Help on the information system Help The supplied 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 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 to specific devices only. To be able to recognize such sections at first 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. WinCC Basic V13.0 System Manual, 02/2014 231 Introduction to the TIA Portal 6.2 Help on the information system 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 permitted 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: The roll-out is closed as soon as you exit the window or click on the "x" in the upper right-hand corner. Tooltip Interface elements offer you a tooltip for easier identification. 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 to the corresponding help topic appears in the cascade. If you click on the link, the corresponding topic opens in help. The following figure shows a tooltip with opened cascade: 232 WinCC Basic V13.0 System Manual, 02/2014 Introduction to the TIA Portal 6.2 Help on the information system See also Configuring the display of tooltips and tooltip cascades (Page 237) 6.2.2 Opening the supplied Help system You access the help via the menu, using links in the tooltip cascades, or with the <F1> key. Procedure To open the supplied help system, follow these steps: 1. In the "Help" menu, select the "Show help" command or press <F1> to display the help matching the current context. Or: WinCC Basic V13.0 System Manual, 02/2014 233 Introduction to the TIA Portal 6.2 Help on the information system 1. Click on the link in a tooltip cascade to go directly to a point in the help system that contains more detailed information. 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. 234 WinCC Basic V13.0 System Manual, 02/2014 Introduction to the TIA Portal 6.2 Help on the information system 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. WinCC Basic V13.0 System Manual, 02/2014 235 Introduction to the TIA Portal 6.2 Help on the information system 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. 236 WinCC Basic V13.0 System Manual, 02/2014 Introduction to the TIA Portal 6.2 Help on the information system 6.2.7 Configuring the display of tooltips and tooltip cascades Configuration options for tooltips and tooltip cascade You can customize the display of tooltips and tooltip cascades to suit your needs. You can make the following settings: Display or hide truncated text Sometimes texts may be too long for a text field. The texts are then fully displayed in a tooltip when you hover your mouse over the text field. You can enable or disable this function. Enable or disable tooltips Tooltips provide more detailed information about an element of the user interface. You can also have tooltips displayed in a cascade. If you disable the tooltips, the cascade with context-sensitive help is also no longer displayed. However, you have the option of manually displaying the tooltip for the currently active interface element by pressing <F1>. Enable or disable automatic opening of tooltip cascades By keeping the mouse pointer over a tooltip for a brief time, any available cascades are displayed automatically. You can enable or disable the automatic display of cascades. When automatic display is disabled, you must open the cascade manually if necessary. To do this, click on the arrow icon in the tooltip. Procedure To configure the display of tooltips and tooltip cascades, follow these steps: 1. Select the "Settings" command in the "Options" menu. 2. Select the "General" group in the area navigation. 3. Select or clear the individual check boxes in the "Tooltips" area to suit your needs. The "Open cascade automatically in tooltips" check box is only available if you have enabled the display of tooltips. See also General remarks on the information system (Page 230) 6.2.8 Safety Guidelines Safety guidelines This Help 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 WinCC Basic V13.0 System Manual, 02/2014 237 Introduction to the TIA Portal 6.2 Help on the information system 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. NOTICE without a safety alert symbol, indicates that property damage can result if proper precautions are not taken. Note indicates that an unintended result or situation can occur if the corresponding 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 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. 238 WinCC Basic V13.0 System Manual, 02/2014 Introduction to the TIA Portal 6.2 Help on the information system Trademarks All names identified by (R) 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. 6.2.9 Assembling customized documentation Customized documentation In the Siemens Industry Online Support, you can assemble customized documentation that is tailored to your needs. All configurable manuals and operating instructions of the Siemens Industry Online Support are available to you for this purpose. You can select the parts that are of interest to you and combine them into in a library to form personal documentation. You can organize the documentation using folders in the library. The folders will later become the individual chapters of your custom documentation. You can open your personal library here (https://www.automation.siemens.com/mdm/? guiLanguage=en). Requirements The manuals or operating instructions used must be configurable. You can recognize configurable manuals by the suffix "configurable" in their name. To use all the functions, you have to register in the Siemens Industry Online Support and log on. Documentation in different languages You can change the language of the assembled documentation to German, French, Spanish, Italian and Chinese. This gives you the possibility, for example, to gather relevant information for a specific project and make it available to colleagues who speak other languages. Export function in the documentation You can perform an export at any part of your library in various formats (PDF, XML, RTF). WinCC Basic V13.0 System Manual, 02/2014 239 Introduction to the TIA Portal 6.2 Help on the information system Help on creating documentation You can find more help on creating and using custom documentation in the Siemens Industry Online Support (https://www.automation.siemens.com/mdm/_help/en/ mdm_reference_manual_de-DE.htm). 240 WinCC Basic V13.0 System Manual, 02/2014 Editing projects 7.1 7 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 Logs for important events in the life cycle of the project 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 242) Opening projects (Page 244) Saving projects (Page 248) Deleting projects (Page 249) Using logs (Page 241) 7.2 Using logs For some operations within the TIA Portal, logs are created automatically in the background. These logs document changes in the project. Logs are created automatically, for example, when you migrate projects and programs or when you update instances from the library. Logs are displayed in the "Common data" folder in the project tree. They are stored together with the project in the project folder and can therefore be read independently of the programming device/PC used as soon as you have opened the project. In addition to displaying them in the TIA Portal, logs can also be printed. WinCC Basic V13.0 System Manual, 02/2014 241 Editing projects 7.3 Creating and managing projects Opening logs To open a log, follow these steps: 1. Open the "Common data > Logs" folder in the project tree. 2. Double-click the desired log in the list. The contents of the log are displayed in the work area. Deleting logs To delete a log, follow these steps: 1. Select the log in the project tree. 2. Press <Del>. The selected log is deleted from the project directory and removed from the project tree. 7.3 Creating and managing projects 7.3.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 241) Opening projects (Page 244) Saving projects (Page 248) Deleting projects (Page 249) 242 WinCC Basic V13.0 System Manual, 02/2014 Editing projects 7.3 Creating and managing projects 7.3.2 Compatibility of projects You can use the TIA Portal to open projects that were created with an older version of the TIA Portal or with a different installation package. In the following, you will learn what to consider in this case. Opening projects from older product versions The table below demonstrates the behavior of the TIA Portal when opening projects from older product versions: Product version of the TIA Portal Behavior when opening with TIA Portal V13 (file extension of the respective version) V10.5 (.ap10) The project is automatically upgraded to the latest product version when opened, following your confirmation. The upgraded project is a copy of the original project. The original project is retained unchanged. V11.x (.ap11) V12 (.ap12) The project is upgraded when you open it. You can select if you want to upgrade the project to product version V12 SP1 or V13. The upgraded project is a copy of the original project in both cases. The original project is retained unchanged. When you upgrade the project to product version V12 SP1, the project is opened in compatibility mode. V12 SP1 (.ap12) When you open the project, you can decide if you want to open it in compatibility mode or upgrade it to the current product version. A copy of the original project is created when you upgrade the project. The original project is retained unchanged. Compatibility mode When you open a project in the V12 SP1 project format and do not upgrade it, the project is in compatibility mode. The range of functions of the TIA Portal is limited to the range of functions of V12 SP1. The project remains backward compatible and can still be opened and edited with TIA Portal V12 SP1. To projects in compatibility mode, components can be added that were supplied at a later date for version V12 SP1 as part of a Hardware Support Package (HSP). The project is still backward compatible with TIA Portal V12 SP1. To continue working with the project in TIA Portal V12 SP1, you merely have to also install the Hardware Support Package. Global libraries are always created in the most recent format and are not backwards compatible, even if the project is opened in compatibility mode. You need to upgrade the project to use the full range of functions of the current version. By upgrading the project you convert it to the current project format. The full range of functions of the current version becomes available. Backward compatibility with the current product version Projects saved with the current version of the TIA Portal are not backward compatible with older versions due to their enhanced functionality. Projects saved with TIA Portal V13 can only be opened with TIA Portal V13 or later. WinCC Basic V13.0 System Manual, 02/2014 243 Editing projects 7.3 Creating and managing projects Opening projects created with add-on products The project you want to open may include data that were created with an optional software. The following cases may occur if you did not install these software components: Software components which are not absolutely required are missing: A dialog appears listing the missing software components. After the project is opened, its properties are displayed. You now have the opportunity to install missing components. All the devices contained in the project are available even if you do not install the missing components. However, you can only work with the devices that are supported by the currently installed software. Devices which are not supported because software components are missing are identified by the following symbol in the project tree: Essential software packages are missing: A dialog appears listing the missing software components. The essential software components are marked. The project can only be opened if you install the missing software components. See also Opening projects (Page 244) Upgrading projects (Page 245) Compatibility of global libraries (Page 339) 7.3.3 Opening projects You can open all projects from the current version and earlier versions in the TIA Portal. Projects from earlier versions of the TIA Portal may first have to be upgraded to a more recent project format. You are prompted to upgrade the project when you open it. You recognize projects of the TIA Portal by their file name extension ".ap[version number]". TIA Portal V13 projects have the file name extension ".ap13". Procedure To open an existing project, follow these steps: 1. Select the "Open" command in the "Project" menu. The "Open project" dialog box opens and the list of most recently used projects is displayed. 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 in the current project format are opened in the project view. The "Upgrade project" dialog box opens if you have selected a project from an older version of the TIA Portal. More information on upgrading the project can be found in chapter "Upgrading projects (Page 245)". 244 WinCC Basic V13.0 System Manual, 02/2014 Editing projects 7.3 Creating and managing projects See also Compatibility of projects (Page 243) Upgrading projects (Page 245) Compiling project data (Page 264) Opening a global library (Page 340) The basics of projects (Page 241) Creating a new project (Page 242) Saving projects (Page 248) Deleting projects (Page 249) 7.3.4 Upgrading projects Projects from older versions of the TIA Portal can be edited with the current version of the TIA Portal. Depending on the product version that was used to create the project, you either upgrade the project or open the project in compatibility mode. To find out which options you have depending on the product version of the project, go to chapter "Compatibility of projects (Page 243)". When you open projects from older product versions, you are prompted to upgrade the project. You can manually upgrade projects that are already open in compatibility mode. After upgrading the project to the current product version, it can no longer be opened in older versions of the TIA Portal. But the original project is still available. The upgraded project is saved as a copy. Upgrading projects from V11.x or lower Proceed as follows to upgrade a project from TIA Portal V11.x or lower: 1. Open the project. The "Upgrade project" dialog box opens. 2. Click "OK". A copy of the project is created and upgraded. The project copy receives the name extension "_V13". The project is opened. 3. Compile the hardware and software of all devices in the project. WinCC Basic V13.0 System Manual, 02/2014 245 Editing projects 7.3 Creating and managing projects Upgrading projects from V12 Proceed as follows to upgrade a project from TIA Portal V12: 1. Open the project. The "Upgrade project" dialog box opens. 2. Select the target version for the upgrade: - Click "Yes" to upgrade the project to product version V13. - Click "No" to upgrade the project to product version V12 SP1 and to work in compatibility mode. A copy of the project is created and upgraded. The project copy receives the name extension "_V13" or "_V12SP1". The project is opened. 3. Compile the hardware and software of all devices in the project. Upgrading V12 SP1 projects or using them in compatibility mode Proceed as follows to upgrade a project from TIA Portal V12 SP1 or to use it in compatibility mode: 1. Open the project. The "Upgrade project" dialog box opens. 2. Select how you want to proceed with the project: - Click "Yes" to upgrade the project to product version V13. - Click "No" to use the project in compatibility mode. 3. Optional: If you have upgraded the project to the current product version, compile the hardware and software of all devices in the project. Manually upgrading projects in compatibility mode to V13 To do this, the project must already be open in compatibility mode for the TIA Portal V12 SP1. To manually upgrade a project in compatibility mode, follow these steps: 1. Select the "Upgrade" command in the "Project" menu. A security prompt appears. 2. Click "Yes" to confirm. A copy of the project is created and upgraded. The project copy receives the name extension "_V13". The project is opened. 3. Compile the hardware and software of all devices in the project. 246 WinCC Basic V13.0 System Manual, 02/2014 Editing projects 7.3 Creating and managing projects Notes Pay attention to the following notes after upgrading a project: Note Upgrading global libraries Because global libraries are independent of projects, they are not upgraded automatically together with the project. If you want to continue using libraries from older versions of the TIA Portal, you need to upgrade these global libraries as well. More information on upgrading global libraries can be found in the chapter "Compatibility of global libraries (Page 339)". Note Upgrading know-how-protected blocks The block is only upgraded and loaded after it has been opened once with the password. This means you should open know-how-protected blocks once after upgrading the project to also upgrade the blocks. If you have protected numerous know-how-protected blocks with the same password, you can select and open all of them at once. See also Compatibility of projects (Page 243) Opening projects (Page 244) Upgrading global libraries (Page 341) Compiling project data (Page 264) Compatibility of global libraries (Page 339) 7.3.5 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 properties can be changed. Project history The project history contains an overview with important events in the project life cycle. Here, for example, you can see the version of the TIA Portal used to create a project and whether it has been converted into another version in the meantime. If a project was created during a migration, for example, this is also indicated in the project history table with the date and time of the migration. If a log was created for an event, you can also call the log directly. WinCC Basic V13.0 System Manual, 02/2014 247 Editing projects 7.3 Creating and managing projects Support packages in the project An overview of the add-on software needed to work with all devices in the project is displayed. In addition, installed GSD files are listed (device description files for other devices in the hardware catalog). 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.3.6 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. If you are editing a project from an earlier version of the TIA Portal, the file extension of the project is also retained and you can continue to edit the project in the earlier version of the TIA Portal. 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 241) Creating a new project (Page 242) Opening projects (Page 244) 248 WinCC Basic V13.0 System Manual, 02/2014 Editing projects 7.3 Creating and managing projects Deleting projects (Page 249) Upgrading projects (Page 245) Compatibility of projects (Page 243) 7.3.7 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.3.8 Deleting projects Note When you delete a project, the entire project data is removed from the storage medium. Requirement 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 desired project folder, and open the project file. 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. WinCC Basic V13.0 System Manual, 02/2014 249 Editing projects 7.3 Creating and managing projects See also The basics of projects (Page 241) Creating a new project (Page 242) Opening projects (Page 244) Saving projects (Page 248) 7.3.9 Working with multi-language projects 7.3.9.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". Reference language The reference language is used as a template for translation. The text is displayed in the reference language for each text box in the "Tasks > Languages and resources" task card. You therefore know which text that belongs in a text box, even when no text is entered in the currently selected editing language. 250 WinCC Basic V13.0 System Manual, 02/2014 Editing projects 7.3 Creating and managing projects 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 Comments in tables Alarm texts Operator-relevant texts Text lists Labels of buttons Display names of recipes Translating texts The following procedures are available to translate texts. Translate all texts used in the project in tabular form 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". Specify text assigned to individual objects in the Inspector window In the Inspector window, you can translate the texts that are assigned to the currently selected objects. Columns are displayed in a table for all available project languages. You can enter the translations for each text there. 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 in a conventional table calculation program. You then import the translated texts again into the TIA Portal. WinCC Basic V13.0 System Manual, 02/2014 251 Editing projects 7.3 Creating and managing projects 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 183) Changing the settings (Page 186) Application examples for multilanguage projects (Page 257) 7.3.9.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. 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.3.9.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. 252 WinCC Basic V13.0 System Manual, 02/2014 Editing projects 7.3 Creating and managing projects 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.3.9.4 Translating all project texts in tabular form You can display and edit all project text used in the currently open project in a list. User and system texts are separated into two different lists for clarity. Both lists contain a separate column for each project language in which you can enter the translations for text. Requirement You are in the project view. You have selected at least one further project language. Procedure To translate text in the project-wide list, 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. WinCC Basic V13.0 System Manual, 02/2014 253 Editing projects 7.3 Creating and managing projects 7.3.9.5 Translating text associated with individual objects If you want to edit the text of individual objects, it would be too difficult to locate the matching text in the table with all project texts. For this reason, there is a table in the Inspector window in which only the texts assigned to the currently selected objects are displayed. In the table, you can add missing translations for individual project languages or change existing texts. Requirement Text must be entered in at least one project language for the texts to be translated. Procedure To edit the text of the currently selected object, follow these steps: 1. Select the object whose text you want to edit. 2. Open the "Properties" tab in the Inspector window. 3. Open the lower-level "Texts" tab in the inspector window. A table with all the texts that belong to the selected objects is displayed. It contains one column for the currently selected editing language and the reference language, as well as additional columns for the other project languages. 4. Add or change the entries in the table for each project language. See also Application examples for multilanguage projects (Page 257) 7.3.9.6 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. 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. 254 WinCC Basic V13.0 System Manual, 02/2014 Editing projects 7.3 Creating and managing projects 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. 7.3.9.7 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 spreadsheet programs may be able to process only a certain number of rows. Microsoft Excel 2003 supports a maximum of 65536 rows, for example. Later versions of Microsoft Excel support significantly more rows. 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 "Export project texts" on the editor toolbar. The "Export" dialog box opens. WinCC Basic V13.0 System Manual, 02/2014 255 Editing projects 7.3 Creating and managing projects 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". 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 257) 256 WinCC Basic V13.0 System Manual, 02/2014 Editing projects 7.3 Creating and managing projects 7.3.9.8 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 Gerat" 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. 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. WinCC Basic V13.0 System Manual, 02/2014 257 Editing projects 7.3 Creating and managing projects See also Project text basics (Page 250) Exporting and importing project texts (Page 255) Translating text associated with individual objects (Page 254) 7.3.10 Archiving and retrieving projects 7.3.10.1 Working with project archives Archiving and transferring projects If you work for a long time with a project, large files may result, especially with extensive hardware configurations. Therefore, you may want to reduce the size of the project, for example, when you archive it to an external hard drive, or when you send it via e-mail and require a smaller file size. Options for reducing the size of the project There are two ways to reduce the size of the project: Creating a project archive TIA Portal project archives are compressed files, each containing an entire project, including the entire folder structure of the project. Before the project directory is compressed into the archive file, all files are reduced to their essential components to further decrease the size of the project. Project archives are therefore well suited for sending via e-mail. Project archives have the file extension ".zap[version number of the TIA Portal]". Projects created with TIA Portal V13 have the file extension ". zap13". To open a project archive, retrieve the project archive. By retrieving it, the archive file with the included project files is extracted to a previously selected location in the original project directory structure. Minimizing a project You can skip additional compression in an archive file, and instead create a copy of the project directory. The included files are reduced to the essential elements of the project. This minimizes the required storage space. The full functionality of the project is maintained and you can open the project as usual. A minimized project is especially well suited for archiving, for example, on an external medium. See also Retrieving projects (Page 260) Archiving projects (Page 259) 258 WinCC Basic V13.0 System Manual, 02/2014 Editing projects 7.3 Creating and managing projects 7.3.10.2 Archiving projects You can reduce the storage space required for the currently open project by compressing the project into a file, or by reducing the project files to their essential components. You can do both of these with the archiving function of the TIA Portal. Note The most recently saved state of the project is used for archiving. Therefore, save the project before using the archiving function. This will ensure that your most recent changes are included in the archived project. Procedure To archive a project, follow these steps: 1. Select the "Archive" command in the "Project" menu. The "Archive current project as..." dialog opens. 2. Select the directory where you want to save the archive file or the new project directory. 3. Select the file type from the "File type" drop-down list: - TIA Portal project archive, if you want to create a compressed file of the project. - Minimized TIA Portal project, if you only want to create a copy of the project directory with minimal storage space. 4. Enter a file name in the "File name" field if you are creating an archive file. If you are creating a minimized project directory instead, enter the name of the new project directory to be created in the "File name" box. 5. Click "Save". Result When you have created a project archive, a compressed file with the extension ".zap13" is generated. Project archives of projects in compatibility mode for product version V12 SP1 receive the file extension ".zap12" and are backward compatible with TIA Portal V12 SP1. The archive file contains the complete project directory. The individual files of the project are also reduced to the essential components in order to save space. If you have created a minimized TIA Portal project, only a copy of the original project directory is created at the desired location. The files contained within it are reduced to their essential components in order to save space. See also Working with project archives (Page 258) Retrieving projects (Page 260) WinCC Basic V13.0 System Manual, 02/2014 259 Editing projects 7.3 Creating and managing projects 7.3.10.3 Retrieving projects You extract project archives of the TIA Portal with the "Restore from archive" function. This restores the project directory structure including all project files. Requirement No project should be open. Procedure To unpack a project archive, follow these steps: 1. Select the "Restore from archive" command in the "Project" menu. The "Retrieve archived project" dialog opens. 2. Select the project archive. 3. Click "Open". 4. The "Find folder" dialog opens. 5. Select the target directory to which the archived project should be extracted. 6. Click "OK". Result The project is extracted to the selected directory and opened immediately. If you extract a project archive that includes a project from a product version lower than V12 SP1, you may have to upgrade the project. You will automatically receive the corresponding prompt as soon as you open the project. The same rules apply that are described in the chapter "Compatibility of projects (Page 243)". See also Working with project archives (Page 258) Opening projects (Page 244) Compatibility of projects (Page 243) Upgrading projects (Page 245) 260 WinCC Basic V13.0 System Manual, 02/2014 Editing projects 7.4 Using reference projects 7.4 Using reference projects 7.4.1 Basics of reference projects Introduction You can open other projects as a reference in addition to the current project. You can use these reference projects as follows: You can drag individual objects from a reference project into the current project and then edit them. You can open specific objects, for example, code blocks from a reference project as readonly. But this is not possible for all elements. You can use an offline/offline comparison to compare devices of the reference project to devices from the current project. Note that reference projects are read-only. You cannot change the objects of a reference project. Projects that were created with an older version of the TIA Portal or with a different installation package can also be opened as reference projects. The same compatibility rules as those for the normal opening of a project from an older version of the TIA Portal apply here. See also: Compatibility of projects (Page 243) See also Comparing reference projects (Page 262) Opening and closing a reference project (Page 261) Reference projects (Page 207) 7.4.2 Opening and closing a reference project Opening a reference project To open a reference project, follow these steps: 1. In the "Reference projects" palette of the project tree, click on "Open reference project" in the toolbar. The "Open reference project" dialog box opens. 2. Navigate to the desired project folder, and open the project file. TIA Portal V13.x projects have the extension ".ap13". Older projects of the TIA Portal have the extension ".ap[version number]". 3. Click "Open". The selected project is opened as a read-only reference project. WinCC Basic V13.0 System Manual, 02/2014 261 Editing projects 7.4 Using reference projects Closing a reference project To close a reference project, follow these steps: 1. In the "Reference projects" palette of the project tree, select the reference project you want to close. 2. Click on "Close reference project" in the toolbar. The selected reference project is closed. See also Basics of reference projects (Page 261) Comparing reference projects (Page 262) Reference projects (Page 207) 7.4.3 Comparing reference projects Introduction You can compare devices from reference projects with devices from both the current project as well as from the same or another reference project or from a library. Note Please note the following: You cannot specify actions for the comparison objects, since the reference projects are write-protected. You can perform a detailed comparison for the comparison objects, if the type of comparison object generally allows a detailed comparison. When comparing reference projects, you can always switch between automatic and manual comparison. Procedure To compare the objects of a reference project to the device data of the current project, follow these steps: 1. In the project tree, select the device whose data you want to compare to the data of a reference project and which allows offline/offline comparison. 2. Select "Compare > Offline/Offline" from the shortcut menu. The compare editor opens with the selected device displayed in the left area. 3. Open the "Reference projects" palette in the project tree. 262 WinCC Basic V13.0 System Manual, 02/2014 Editing projects 7.5 Editing project data 4. Select the device of a reference project that you want to compare to the device data from the current project. 5. Drag the device from the reference project into the right drop area of the compare editor. You can identify the status of the objects based on the symbols in the status and action area. When you select an object, the object's properties and the corresponding object of the associated device is clearly shown in the properties comparison. You can drag a library or other devices from a reference project from the current project into drop areas at any time and thus start a new comparison. It does not matter which device you drag into the drop area. See also Basics of reference projects (Page 261) Reference projects (Page 207) Opening and closing a reference project (Page 261) Carrying out offline/offline comparisons (Page 274) Using the compare editor (Page 275) 7.5 Editing project data 7.5.1 Compiling and loading project data 7.5.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 WinCC Basic V13.0 System Manual, 02/2014 263 Editing projects 7.5 Editing project data Note While a device is being compiled, no additional compiling process can be started. Note in this regard that you can not only perform a compiling process manually, but you can also trigger it automatically for HMI devices. Scope of the compilation When you compile project data, you have the following options depending on the device involved: Hardware and software (only changes) Hardware (only changes) Hardware (rebuild completely) Software (only changes) Software (rebuild all blocks) Software (reset memory reserve) See also Compiling project data (Page 264) 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, select the devices whose project data you want to compile. 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". See also General information on compiling project data (Page 263) 264 WinCC Basic V13.0 System Manual, 02/2014 Editing projects 7.5 Editing project data 7.5.1.2 Loading project data General information on loading Introduction In order to set up your automation system, you need to load the project data you generated offline on 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 devices and memory cards. Note While a device is being compiled, no additional download process can be started. Note in this regard that you can not only perform a compiling process manually, but you can also trigger it automatically for HMI devices. Possible options for downloading Depending on the object you want to download, you have the following options: Hardware and software (only changes) Both the hardware configuration and software are downloaded to the destination if differences exist between the online and offline versions. Hardware configuration Only the hardware configuration is downloaded to the destination. Software (only changes) Only the objects that differ online and offline are downloaded to the destination. Load PLC program to device and reset All the blocks are loaded to the destination and all values are reset to their initial state. Be aware that this also applies to retentive values. You can also upload project data already contained in a device back to your project. You have the following options: Upload entire device as new station The hardware configuration of the device and the software on the device is uploaded to the project. All relevant data of the device is uploaded to the project. Upload software of a device Only the blocks and parameters from the device are uploaded to an existing CPU in the project. In both cases, during loading all instances of library types are connected again with the corresponding version of the type in the project library. If no suitable type is yet available for WinCC Basic V13.0 System Manual, 02/2014 265 Editing projects 7.5 Editing project data a loaded instance or the correct version of the type does not exist in the project library, the type or the version is added to the project library. Downloading with synchronization In team engineering, it is possible for several users to work on one project with several engineering systems at the same time and to access one S7-1500 CPU. To ensure consistency within the shared project, it is necessary to synchronize the changed data prior to loading so that nothing gets overwritten unintentionally. If differences are detected between the online and offline data management within the shared project that were caused by a different engineering system, automatic synchronization of the data to be loaded is offered when loading. In this case, the "Synchronization" dialog displays the data to be synchronized with the current status (online-offline comparison) and the possible actions. Use case Recommendation Synchronization One or more blocks on the CPU (online) are more recent than in the engineering system (offline). These blocks should be uploaded from the CPU to the engineering system before downloading. Automatic synchronization is possible: One or more new blocks have been created and exist only on the CPU (online). These blocks should be uploaded from the CPU to the engineering system before downloading. Automatic synchronization is possible: One or more blocks on the CPU have been deleted. The blocks should also be deleted prior to the download in the engineering system. Automatic synchronization is not possible. 266 The blocks in the engineering system are updated prior to loading. The new blocks are added to the engineering system prior to the download. The blocks deleted on the CPU should be manually deleted in the offline project in the engineering system. WinCC Basic V13.0 System Manual, 02/2014 Editing projects 7.5 Editing project data Use case Recommendation Synchronization One or more blocks on the CPU and in the engineering system are different. These blocks with competing changes must be adapted manually. You decide in this case which changes you are going to accept. Automatic synchronization is not possible: This is the case when a different user has changed blocks to which you have also made corrections and has already downloaded them to the CPU. If the blocks on the CPU are to be retained, you should adopt these blocks from the CPU in your engineering system before downloading to the CPU. The affected blocks on the CPU or in the engineering system must be adapted manually. One of the existing block versions (online or offline) will be overwritten in the process. If the blocks that you have changed are to be applied, you can continue with the download without synchronization. There are differences in the hardware configuration on the CPU (online) and in the engineering system (offline). Differences in the hardware configuration must be adapted manually. You decide in this case which hardware configuration you are going to accept. If the existing hardware configuration on the CPU is to be retained, you should adopt this in your engineering system prior to downloading. Automatic synchronization is not possible: The hardware configuration must be adapted manually. One of the existing hardware configurations (online or offline) will be overwritten. If you want to apply the hardware configuration you changed, you can continue downloading without synchronization. If required, you can use the "Force download to device" command to download blocks without synchronization. See also Downloading project data to a device (Page 267) Downloading project data to a memory card (Page 269) Uploading project data from a device (Page 270) 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. WinCC Basic V13.0 System Manual, 02/2014 267 Editing projects 7.5 Editing project data 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. You have the option of showing all compatible devices by selecting the corresponding option and clicking the "Start search" command. See also: Auto-Hotspot 4. Check the messages in the "Load preview" dialog, and select the actions in the "Action" column, if necessary. WARNING Preventing personal injury and material damage 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. The loading operation is performed. If there is a need for synchronization, the system automatically displays the "Synchronization" dialog. This dialog displays messages and suggests actions that are required for the synchronization. You have the option of performing these actions or forcing the download without synchronization by clicking "Force download to device". If you have performed the suggested actions, you will be asked whether you want to continue with the download. 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. 6. Click the "Finish" button. Result The selected project data was downloaded to the devices. 268 WinCC Basic V13.0 System Manual, 02/2014 Editing projects 7.5 Editing project data See also General information on loading (Page 265) Downloading project data to a memory card (Page 269) Uploading project data from a device (Page 270) Downloading project data to a memory card You can drag-and-drop project data to load it to a memory card. For CPUs of the S7-300/400 series you can also explicitly download the user program to a memory card inserted in the CPU. Requirement A memory card is displayed. See also: Accessing memory cards (Page 324) Dragging project data to a memory card To download project data to a memory card, follow these steps: 1. In the project tree, drag the project data you want to load 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. Download the user program to a memory card in the CPU (S7-300/400 only) To download the user program to a memory card in a CPU of the S7-300/400 series, follow the steps below: 1. Select a CPU of the S7-300/400 series in the project tree. 2. Select the "Download user program to memory card" command in the "Online" menu. The "Load preview" dialog opens. This dialog displays messages and proposes actions necessary for downloading. 3. Check the messages, and select the actions in the "Action" column, if necessary. As soon as loading becomes possible, the "Load" button is enabled. 4. Click the "Load" button. The download is made and the "Load results" dialog is displayed. This dialog displays messages and suggests possible actions. WinCC Basic V13.0 System Manual, 02/2014 269 Editing projects 7.5 Editing project data 5. Check the messages, and select the actions in the "Action" column, if necessary. 6. Click the "Finish" button. See also General information on loading (Page 265) Downloading project data to a device (Page 267) Uploading project data from a device (Page 270) 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 options for uploading project data from a device to your project: Upload as new station With this option you upload existing project data of a device to your project as a new station. Uploading project data of a device With this option you upload project data from the device to an existing CPU in the project. You will find the project data that can be loaded in the online help of the product. In both cases, all instances of library types are connected again with the corresponding version of the type in the project library during loading. If no suitable type is yet available for a loaded instance or the correct version of the type does not exist in the project library, the type or the version is added to the project library. 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. Upload as new station To upload the complete device to your project, follow these steps: 1. Select the project name in the project tree. 2. Select "Upload device as new station (hardware and software)" in the "Online" menu. 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: Auto-Hotspot 270 WinCC Basic V13.0 System Manual, 02/2014 Editing projects 7.5 Editing project data 6. Display all compatible devices by selecting the relevant option and clicking the "Start search" command. 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. Uploading project data of a device To upload only project data from one 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: Auto-Hotspot 2. Select the device in the project tree. The "Upload from device (software)" command in the "Online" menu is enabled. 3. Select the "Upload from device (software)" 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 265) Downloading project data to a device (Page 267) Downloading project data to a memory card (Page 269) Loading project data from a memory card You have the following options for uploading project data from a memory card to your project: Upload project data of the memory card as a new station With this option you upload the project data of a memory card to your project as a new station. Upload project data of the memory card to an existing device With this option you upload project data of a memory card to an existing device in your project. You will find the project data that can be loaded in the online help of the product. In both cases, all instances of library types are connected again with the corresponding version of the type in the project library during loading. If no suitable type is yet available for a loaded instance or the correct version of the type does not exist in the project library, the type or the version is added to the project library. WinCC Basic V13.0 System Manual, 02/2014 271 Editing projects 7.5 Editing project data Requirement A project is open. The memory card is displayed. See also: Accessing memory cards (Page 324) The hardware configuration and software to be downloaded have to be compatible with the TIA Portal. If the data on the memory card was created with a previous program version or with different configuration software, please make sure they are compatible. Upload project data as a new station To upload project data from a memory card to your project, follow these steps: 1. In the project tree, select the project data you want to upload. 2. Select "Upload device as new station (hardware and software)" in the "Online" menu. Or: 1. In the project tree, drag the memory card folder to the project. Or: 1. Right-click on the memory card. 2. Select "Copy" in the shortcut menu. 3. Right-click on the project. 4. Select the "Paste" command in the shortcut menu. Uploading project data to an existing device To upload the project data of a memory card to an existing device, follow these steps: 1. In the project tree, drag the folder of the memory card to a device in the project or copy the memory card and paste the data into a device. The "Upload preview" dialog box opens. 2. 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. 3. Click the "Upload from device" button. The loading operation is performed. 272 WinCC Basic V13.0 System Manual, 02/2014 Editing projects 7.5 Editing project data 7.5.2 Comparing project data 7.5.2.1 Basics of project data comparison Function You can compare project data of the same type in order to determine possible differences. In principle, the following comparison methods are available: Online/offline comparison With this comparison method you can compare the software of objects of a device with the objects of a project. This is only possible when you establish an online connection to the device. Offline/offline comparison With this comparison method you can either compare the software or the hardware. When you compare the software, you can compare objects from projects or libraries. The hardware comparison is available for devices from the currently open project or from reference projects. You can decide for the software as well as the hardware comparison whether the comparison should be performed automatically for all objects or whether you want to compare individual objects manually. Detailed comparison For some objects, for example, blocks, you can also perform a detailed comparison in addition to the online/offline and offline/offline comparison. This involves opening the blocks to be compared beside each other and highlighting the differences. A simple online/offline comparison is performed as soon as 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. The normal online/offline and offline/offline comparison is performed in the compare editor. With the software comparison, you can also select actions for non-identical objects in the compare editor. Note Not all objects allow all types of comparison. Which comparison method you can use for which project data depends on the products installed. Compile your user program before you start a comparison or detailed comparison. After each change of the program during a comparison, repeat this step before you update the result of the comparison. This ensures that the comparison shows the current status. See also Carrying out an online/offline comparison (Page 274) Carrying out offline/offline comparisons (Page 274) Using the compare editor (Page 275) Running a detailed comparison (Page 283) WinCC Basic V13.0 System Manual, 02/2014 273 Editing projects 7.5 Editing project data 7.5.2.2 Carrying out an online/offline comparison The online/offline comparison lets you compare objects of a device with objects of a project. Requirement The project tree is open. Procedure To perform an online/offline comparison, follow these steps: 1. Select a device in the project tree that allows online/offline comparison. 2. Select the "Compare > Offline/online" command in the shortcut menu. 3. If you have not already established an online connection to this device, the "Go online" dialog opens. In this case, set all the necessary parameters for the connection and click "Connect". The online connection is established and compare editor opens. Result All objects that exist online and offline are displayed. The symbols in the compare editor and in the project tree show you the status of the objects. In the compare editor, you can now define certain actions for the objects, depending on their status. See also Basics of project data comparison (Page 273) Carrying out offline/offline comparisons (Page 274) Using the compare editor (Page 275) Running a detailed comparison (Page 283) 7.5.2.3 Carrying out offline/offline comparisons With offline/offline comparison you have the option to compare the project data of two devices. You can carry out a software as well as a hardware comparison. When you compare the software, you can compare objects from projects or libraries. The hardware comparison is available for devices from the currently open project or from reference projects. You can decide whether the comparison should be performed automatically for all objects or whether you want to compare individual objects manually. You can drag any other device to the drop area at any time to perform further comparisons. Requirement The project tree is open. 274 WinCC Basic V13.0 System Manual, 02/2014 Editing projects 7.5 Editing project data Procedure To perform an offline/offline comparison, follow these steps: 1. Select a device in the project tree that allows offline/offline comparison. 2. Select the "Compare > Offline/offline" command in the shortcut menu. The compare editor opens and the selected device is displayed in the left area. 3. Drag-and-drop an additional device to the drop area of the right pane. All existing objects of the selected devices are displayed depending on the settings of the compare editor in the "Software" tab and an automatic comparison is carried out. You can identify the status of the objects based on the symbols in the compare editor. You can define certain actions depending on the status of the objects. 4. If you want to carry out a manual comparison, click on the button for switching between automatic and manual comparison in the status and action area. Then select the objects that you want to compare. The properties comparison is displayed. You can identify the status of the objects based on the symbols. You can define certain actions depending on the status of the objects. 5. If you want to carry out a hardware comparison, open the "Hardware" tab. You can once again carry out a manual comparison, if necessary. But you cannot specify any action. See also Basics of project data comparison (Page 273) Carrying out an online/offline comparison (Page 274) Using the compare editor (Page 275) Running a detailed comparison (Page 283) 7.5.2.4 Using the compare editor Overview of the compare editor Function The compare editor gives an overview of the results of a comparison in a table. The appearance varies slightly depending on whether it is an online/offline comparison or a hardware/software comparison. WinCC Basic V13.0 System Manual, 02/2014 275 Editing projects 7.5 Editing project data Layout of the compare editor The following figure shows the layout of the compare editor for an online/offline comparison: Compare editor toolbar Left comparison table Status and action area Right comparison table Properties comparison The following figure shows the layout of the compare editor for an offline/offline comparison (software): 276 WinCC Basic V13.0 System Manual, 02/2014 Editing projects 7.5 Editing project data Compare editor toolbar Drop areas Button to toggle between automatic and manual comparison Left comparison table Status and action area Right comparison table Properties comparison The following figure shows the layout of the compare editor for an offline/offline comparison (hardware): WinCC Basic V13.0 System Manual, 02/2014 277 Editing projects 7.5 Editing project data Compare editor toolbar Drop areas Button to toggle between automatic and manual comparison Left comparison table Status area Right comparison table Properties comparison Compare editor toolbar With the toolbar, you can access the following compare editor functions: Only show different objects You can hide identical objects to make the comparison easier to follow. Show identical and different objects You can show identical objects if you want to view the comparison in full. Scope of the comparison (only online/offline comparison and offline/offline comparison for software) You can define which objects are to be compared. Select assignment criterion (only offline/offline comparison for hardware) You can specify the criterion according to which the modules are to be assigned to each other for the comparison. 278 WinCC Basic V13.0 System Manual, 02/2014 Editing projects 7.5 Editing project data Changing the view You can choose between a hierarchical and a flat view. In the hierarchical view, the devices are shown in their structure; in the flat view, the objects of the devices are listed without structure. Start detail comparison (only online/offline comparison and offline/offline comparison for software) You can start a detailed comparison for objects to show the individual differences. This function is, however, not available for every object. Updating comparison results After you have modified objects, you can update the comparison results using this function. Synchronize non-identical objects (only online/offline comparison and offline/offline comparison for software) You can synchronize non-identical objects using specific actions. Drop areas In the case of an offline/offline comparison, you can drag the devices you want to compare into the drop areas. In the case of a software comparison, the devices to be compared can originate from the opened project, from reference projects, from the project library or from global libraries. However, note that you can only drop complete libraries into the right drop area. In the case of a hardware comparison, you can compare devices from the opened project or from reference projects. Button to toggle between automatic and manual comparison With an offline/offline comparison, you can switch between automatic and manual comparison. In the case of automatic comparison, the objects to be compared are assigned automatically to each other. In the case of a manual comparison, you can select the objects that are to be compared. Comparison tables Comparison tables show the objects of the devices being compared to one another. The following table shows the meaning of the columns of the comparison table: WinCC Basic V13.0 System Manual, 02/2014 Column Description Name Name of the compare object Comment Comment on the compare object Title Title of the compare object Address Address of the compare object Numbering Type of numbering for the comparison object Type Type of compare object Language Programming language set for the compare object. Time stamp interface Time of the last modification to the block interface Time stamp code Time of the last modification to the source code Author Name of the author of the compare object 279 Editing projects 7.5 Editing project data Column Description Version Version of the compare object Family Name of the object family Load memory Memory usage of the load memory of the compare object Work memory Memory usage of the work memory of the compare object Modified on Time of last modification Signature Signature of the compare object (SIMATIC Safety) Interface signature Signature of the block interface of the compare object (SIMATIC Safety) Not all columns are shown in the default setting. However, as in all table editors, you can show or hide the columns as required and sort according to individual columns. In the case of a hardware comparison, the comparison tables only contain the "Name" column. Status and action area The status and action area offers the following options: You can view the results of automatic comparison. The results are displayed with symbols. In an online/offline comparison and an offline/offline comparison for software, you can specify actions for non-identical objects. Status and action symbol The following table shows the comparison results symbols for an online/offline comparison: Symbol Description Folder contains objects whose online and offline versions differ Comparison results are 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 The following table shows the comparison results symbols for an offline/offline comparison: Symbol Description Reference program Version compared Folder contains objects of which the versions compared differ Results of the offline/offline comparison are not known 280 WinCC Basic V13.0 System Manual, 02/2014 Editing projects 7.5 Editing project data Symbol Description The versions of the object compared are identical The versions of the object compared differ Object only exists in the reference program Object only exists in the version compared Hardware comparison only: Although the lower-level objects of the container are identical, there are differences between the containers themselves. Such a container may be a rack, for example. Hardware comparison only: The lower-level objects of the container are different. There are also differences between the containers. Such a container may be a rack, for example. The following table shows the symbols for possible actions in a software comparison: Symbol Description No action Overwrite the object of the compared version with the object from the reference program Overwrite the object of the output program with the object from the compared version Different actions for the compare objects in the folder Properties comparison The properties comparison compares the properties of the selected compare objects. The result is displayed with symbols. Only the properties comparison is made with a manual comparison so that the status and action area remains empty. With automatic comparison, you can perform the property comparison in addition to the comparison in the comparison tables. See also Basics of project data comparison (Page 273) Carrying out an online/offline comparison (Page 274) Carrying out offline/offline comparisons (Page 274) Changing the view (Page 287) Show and hide table columns (Page 282) Filtering the compare editor view (Page 282) Updating the comparison results (Page 284) Synchronizing non-identical objects (Page 285) WinCC Basic V13.0 System Manual, 02/2014 281 Editing projects 7.5 Editing project data Show and hide table columns In a software comparison, you can show or hide the columns of comparison tables as required. Procedure To show or hide table columns, follow these steps: 1. Click a column header. 2. Select the "Show/Hide" command in the shortcut menu. The selection of available columns is displayed. 3. To show a column, select the column's check box. 4. To hide a column, clear the column's check box. The change affects both the left and the right comparison table. Result The columns in both the left and the right comparison table are shown or hidden. See also Basics of project data comparison (Page 273) Carrying out an online/offline comparison (Page 274) Carrying out offline/offline comparisons (Page 274) Overview of the compare editor (Page 275) Filtering the compare editor view (Page 282) Running a detailed comparison (Page 283) Updating the comparison results (Page 284) Synchronizing non-identical objects (Page 285) Changing the view (Page 287) Filtering the compare editor view You can improve the clarity of the compare editor using the following filters: Hiding identical comparison objects You can hide comparison objects which have identical online/offline or offline/offline versions. Any such comparison objects you have hidden can also be shown again at any time. Displayed objects In an online/offline comparison or an offline/offline comparison for software, you can specify the objects for which the comparison results are to be shown. 282 WinCC Basic V13.0 System Manual, 02/2014 Editing projects 7.5 Editing project data Requirement The compare editor is open. Hiding identical comparison objects To hide identical objects, follow these steps: 1. Click on the "Show only objects with differences" button in the toolbar. Only the elements that differ online and offline are displayed. Showing identical comparison objects To show identical objects again, follow these steps: 1. Click on the "Show identical and different objects" button in the toolbar. All elements will be displayed. Selecting displayed objects To select the objects for which comparison results should be displayed, follow these steps: 1. Perform an online/offline or an offline/offline comparison for software. 2. Click the arrow of the button "Show additional available filters" in the toolbar. 3. Select the required filter. See also Basics of project data comparison (Page 273) Carrying out an online/offline comparison (Page 274) Carrying out offline/offline comparisons (Page 274) Overview of the compare editor (Page 275) Changing the view (Page 287) Show and hide table columns (Page 282) Running a detailed comparison (Page 283) Updating the comparison results (Page 284) Synchronizing non-identical objects (Page 285) Running a detailed comparison Note Not all objects allow a detailed comparison. The project data for which you can perform a detailed comparison depends on the products installed. A detailed comparison of the hardware components is not available for hardware comparison. WinCC Basic V13.0 System Manual, 02/2014 283 Editing projects 7.5 Editing project data Procedure Proceed as follows to perform a detailed comparison: 1. First, perform an online/offline or an offline/offline comparison for software. The compare editor opens. Note You can only perform a detailed comparison for objects that are listed in the left as well as the right comparison table. 2. In the compare editor, select the object for which you want to perform a detailed comparison. 3. Click the "Start detailed comparison" button in the toolbar. See also Basics of project data comparison (Page 273) Carrying out an online/offline comparison (Page 274) Carrying out offline/offline comparisons (Page 274) Overview of the compare editor (Page 275) Show and hide table columns (Page 282) Changing the view (Page 287) Filtering the compare editor view (Page 282) Updating the comparison results (Page 284) Synchronizing non-identical objects (Page 285) Updating the comparison results As soon as you change an object, the comparison results are no longer valid and must be updated. Note For online/offline comparisons, you should note that changes in the device may result in the system automatically updating the comparison editor if objects in the comparison are affected by the change. This can have the following results: Some of the actions you have defined may become invalid, for example if the device no longer contains the object in question. Objects with such invalid actions will be highlighted so you can define new, valid actions. The selection you made before the automatic update may also be cancelled. Requirement The comparison editor is open. 284 WinCC Basic V13.0 System Manual, 02/2014 Editing projects 7.5 Editing project data Procedure To update the comparison results, follow these steps: 1. Click the "Refresh view" button in the toolbar. The comparison results are updated. Note Please note that the "Refresh view" button will not be available while the comparison editor is loading or synchronizing content. See also Basics of project data comparison (Page 273) Carrying out an online/offline comparison (Page 274) Carrying out offline/offline comparisons (Page 274) Overview of the compare editor (Page 275) Show and hide table columns (Page 282) Changing the view (Page 287) Filtering the compare editor view (Page 282) Running a detailed comparison (Page 283) Synchronizing non-identical objects (Page 285) Synchronizing non-identical objects Specifying actions If you have performed a comparison, you can specify the actions to be performed for nonidentical objects in the compare editor. You cannot select any actions for identical objects. Note that you cannot execute any actions during hardware comparison. In the case of an online/offline comparison, only synchronization actions in one direction are permitted, in order to retain program consistency. Thus, for example, you can load multiple blocks to a device or from a device, but you cannot perform a combination of loading actions in one synchronization action. In this case, the first action you set in the compare editor determines the synchronization direction. For example, if you specify for a block that the offline block is to be loaded to the device, then the other objects can also only be loaded to the device via a synchronization action. To load objects from the device again, first select the "No action" WinCC Basic V13.0 System Manual, 02/2014 285 Editing projects 7.5 Editing project data option. You can then specify the action settings again as required. Or, you can perform a new comparison. Note Please note the following CPU-specific aspects when defining actions: S7-300/400: - You can define actions for the "Program blocks" folder, for folders you have created yourself or for individual blocks. - Neither SCL nor GRAPH blocks can be loaded from the device to the offline project. S7-1200/1500: - You can define actions for the "Program blocks" folder, for folders you have created yourself or for individual blocks. If you have performed an online/offline comparison and select download to the device as action, a consistent download is executed. If you upload the object from the device to the project, however, you can also upload individual blocks. - SCL blocks cannot be loaded from the device to the offline project. Requirement The compare editor is open. Procedure To select an action for a non-identical object, follow these steps: 1. In the status and action area, double-click in the "Action" column on the cell of the object for which you want to define an action. The cell changes to a drop-down list. 2. Click on the drop-down list. 3. Select the action you want. The action set will be carried out for the object in question the next time synchronization is performed. If you have accidentally changed the action you had selected, you can undo the change before the next synchronization. 4. To restore the previous action selected, right-click on the object or folder. 5. Select the "Restore previous selection" command in the shortcut menu. See also Basics of project data comparison (Page 273) Carrying out an online/offline comparison (Page 274) Carrying out offline/offline comparisons (Page 274) Overview of the compare editor (Page 275) Show and hide table columns (Page 282) 286 WinCC Basic V13.0 System Manual, 02/2014 Editing projects 7.5 Editing project data Filtering the compare editor view (Page 282) Updating the comparison results (Page 284) Synchronizing objects (Page 287) Synchronizing objects Synchronization executes the actions you have specified for non-identical objects. Note, however, that in the case of an online/offline comparison you can only perform actions in one direction in one synchronization action. Requirement The compare editor is open. The desired actions have been selected. Procedure To synchronize objects, follow these steps: 1. Click the "Execute actions" button in the toolbar. Result The actions you specified for the objects are performed. See also Basics of project data comparison (Page 273) Carrying out an online/offline comparison (Page 274) Carrying out offline/offline comparisons (Page 274) Overview of the compare editor (Page 275) Show and hide table columns (Page 282) Filtering the compare editor view (Page 282) Updating the comparison results (Page 284) Specifying actions (Page 285) Changing the view You can choose between a hierarchical and a flat view for the left comparison table. In the hierarchical view, the devices are shown in their structure; in the flat view, the objects of the devices are listed without structure. In the right comparison table, the objects are always displayed flat. WinCC Basic V13.0 System Manual, 02/2014 287 Editing projects 7.5 Editing project data Setting the hierarchical view To set the hierarchical view, follow these steps: 1. Click the "Display in hierarchical view" button in the toolbar of the compare editor. Setting the flat view To set the flat view, follow these steps: 1. Click the "Display in flat view" button in the toolbar of the compare editor. See also Basics of project data comparison (Page 273) Carrying out an online/offline comparison (Page 274) Carrying out offline/offline comparisons (Page 274) Overview of the compare editor (Page 275) Show and hide table columns (Page 282) Filtering the compare editor view (Page 282) Running a detailed comparison (Page 283) Updating the comparison results (Page 284) Synchronizing non-identical objects (Page 285) 7.5.3 Protecting project data 7.5.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 For objects with know-how protection, this protection is also retained after the object is pasted into a library. 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 288 WinCC Basic V13.0 System Manual, 02/2014 Editing projects 7.5 Editing project data execute the required function. You continue to have access rights on the device until you close the TIA Portal. If you want to reactivate password protection while the TIA Portal is open, you can explicitly revoke the access rights for a device. As a result, certain functions for the protected device cannot be executed until the correct password is entered again. You specify the functions for which a password must be entered when you assign the device protection level. See also Printing project data (Page 307) 7.5.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 288) WinCC Basic V13.0 System Manual, 02/2014 289 Editing projects 7.5 Editing project data 7.5.4 Printing project contents 7.5.4.1 Printing project documentation Documentation settings Introduction Once a project is created, the contents can be printed in an easy-to-read format. You may print the entire project or individual objects within the project. A well-structured printout is helpful when editing the project or performing service work. The printout can also be used for your customer presentations or as full system documentation. You can prepare the project in the form of standardized circuit manuals and print it in a uniform layout. You can limit the scope of the printout. You have the option to print to the entire project, individual objects along with their properties, or a compact overview of the project. In addition, you can print the contents of an open editor. Improving the printout with frames and cover pages You can design the appearance of the printed pages according to your own requirements, for example, to add your own company logo or the corporate design of your company in the project documentation. You can create any number of design variants as frames and cover pages. The frames and cover pages are stored in the project tree under the item "Documentation settings" and are part of the project. You can insert placeholders for data from previously entered document information within the frames and cover pages. 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. 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 frames (Page 296) Creating a cover page (Page 296) 290 WinCC Basic V13.0 System Manual, 02/2014 Editing projects 7.5 Editing project data Editing cover pages and frames (Page 298) Entering document information (Page 294) Print function for module labels (Page 309) Printout of project contents Availability of print function The following contents can be printed: An entire project in the project tree One or more project-related objects in the project tree Contents of an editor Tables Libraries Diagnostics view of the Inspector window It is not possible to print in the following areas: Portal view Detailed view Overview window Compare editor All tabs of the Inspector window, except the diagnostics view All task cards, except the libraries Most of the dialogs Properties and devices of the programming device/PC not related to the project, for example online portals and connected card readers. 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. If you select the entire project in the project tree for printing, all project contents are printed with the exception of the graphical views. These have to be printed separately. Items in the project tree that are not part of the project cannot be printed. For example, this includes online portals and connected card readers and USB memory devices. 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. WinCC Basic V13.0 System Manual, 02/2014 291 Editing projects 7.5 Editing project data 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 307) Changing the print settings Changing the print settings You can specify general print settings that are retained even after the TIA Portal is closed and re-opened. Some settings are dependent on the products installed. The following settings are possible in every case: Always print table data as pairs of values If this option is selected, tables are not printed in tabular format but rather as a pairs of key and value. Example: Object name Property 1 Property 2 Object A Value A1 Value A2 Object B Value B1 Value B2 In this case, the printout has the following appearance: Object A Property 1: Value A1 Property 2: Value A2 Object B Property 1: Value B1 Property 2: Value B2 292 WinCC Basic V13.0 System Manual, 02/2014 Editing projects 7.5 Editing project data 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 186) Specifying the print layout Specifying the print layout If you do not want to rely on ready-made print templates, you can specify your own cover page or your own layout for the individual pages. Your designs are saved together with the respective project. Your designs for the cover page and your templates for the page layout can be found in the project tree under the "Documentation information" group. You will also find metadata on the project there under the entry "Document information". For subsequent print operations, you can customize the appearance of the printout in the "Print" dialog using the saved cover pages and page layout templates and the available metadata. Designing the cover page The cover page can be customized. You can insert a background graphic and provide placeholders for text on the page. The placeholders are automatically filled with data from a documentation information during printing. Cover pages are located in the project tree under the "Documentation information > Cover pages" group. WinCC Basic V13.0 System Manual, 02/2014 293 Editing projects 7.5 Editing project data Designing the content page The regular pages of a printout can contain the following elements: Frame with static content, such as a company logo Placeholders 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. Entering document information You can enter metadata in the document information for every project. In addition, a print frame and a cover page are specified in the document information. You can create different information, if required, to enable you to quickly switch between different document information containing different information, frames, cover pages, page sizes, and page orientations when printing. For example, this is useful if you want to generate printouts in different languages and different document information is provided for each language. In the documentation editor, you can specify placeholders on the cover page or in the frame of the regular pages. These placeholders can be automatically replaced with metadata from the documentation information during printing. The various document information are therefore part of the printing function and specify the print layout and print content. Procedure To add metadata, follow these steps: 1. To create new document information, double-click "Add new document information" under "Documentation information > Document information" in the project tree. The new document information is created and opened immediately. 2. Enter a name for the set in the "Name" field. 3. Fill in the individual fields with the metadata for the project. 294 WinCC Basic V13.0 System Manual, 02/2014 Editing projects 7.5 Editing project data 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 readymade page frame and then store it again as a new frame. Like cover pages, frames can be saved in global libraries where they are available for use across projects. Frames are designed for use on right printed pages only. Cover pages and templates in the project tree Cover pages and frames associated with the project are stored in the project tree under the entry "Documentation information". There are separate folders here for frames and cover pages. The following actions are available in the project tree for cover pages and frames. Creating your own subfolders Copying and pasting Inserting cover pages and frames from the "Documentation templates" system library Copying cover pages and templates to a global library Cover pages and templates in libraries The "Documentation templates" system library contains a few cover pages and templates that are available in every project. The cover pages and templates can be moved from there to the project tree using a drag-and-drop operation. You can then adapt the cover pages and templates in the project tree according to the requirements of your project. Cover pages and templates can be moved from the project tree to a global library. Afterwards, these are available in every project. WinCC Basic V13.0 System Manual, 02/2014 295 Editing projects 7.5 Editing project data See also Library basics (Page 325) Overview of the "Libraries" task card (Page 327) Designing cover pages and frames (Page 298) Using ready-made frames and cover pages (Page 297) Creating frames 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 "Creating frames" 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 298) Creating a cover page (Page 296) 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. 296 WinCC Basic V13.0 System Manual, 02/2014 Editing projects 7.5 Editing project data 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 298) Creating frames (Page 296) Using ready-made frames and cover pages The TIA Portal comes with some ready-made frames and cover pages. These can change according to your wishes. Procedure To create and edit the ready-made frames and cover pages, follow these steps: 1. Open the "Global libraries" pane in the "Libraries" task card. 2. In the "Templates" folder, open the "Cover Pages" or "Frames" folder. 3. Drag a cover page or a frame from one of the folders into the project tree and drop it into one of the following folders: - For frames: "Document information > Frames" - For cover pages: "Document information > Cover pages". The ready-made frame or cover page can now be used in the project. 4. Double-click on the new entry in the project tree click to edit the frame or the cover page. See also Using cover pages and frames (Page 295) Editing cover pages and frames (Page 298) WinCC Basic V13.0 System Manual, 02/2014 297 Editing projects 7.5 Editing project data 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 296) Creating frames (Page 296) General operation of the documentation editor (Page 299) 298 WinCC Basic V13.0 System Manual, 02/2014 Editing projects 7.5 Editing project data General operation of the documentation editor Components of the documentation editor The following figure provides an overview of the components of the documentation editor: WinCC Basic V13.0 System Manual, 02/2014 299 Editing projects 7.5 Editing project data 300 Toolbar The toolbar provides the following tools (from left to right): 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. Zoom with selection Adapts the page size to a selected work area. 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. WinCC Basic V13.0 System Manual, 02/2014 Editing projects 7.5 Editing project data 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 "Zoom with selection" 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. WinCC Basic V13.0 System Manual, 02/2014 301 Editing projects 7.5 Editing project data 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 298) Specifying the print area (Page 302) Inserting placeholders for metadata (Page 302) 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. 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 frames (Page 296) General operation of the documentation editor (Page 299) 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. 302 WinCC Basic V13.0 System Manual, 02/2014 Editing projects 7.5 Editing project data 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. 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. WinCC Basic V13.0 System Manual, 02/2014 303 Editing projects 7.5 Editing project data See also General operation of the documentation editor (Page 299) 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 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. 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. 304 WinCC Basic V13.0 System Manual, 02/2014 Editing projects 7.5 Editing project data 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 306) WinCC Basic V13.0 System Manual, 02/2014 305 Editing projects 7.5 Editing project data 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, enable the "Zoom with selection" icon and use the mouse to drag an outline around the area you want to focus on. 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 "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. "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 to the first page - "Previous page" Goes to the previous page. - "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. 306 WinCC Basic V13.0 System Manual, 02/2014 Editing projects 7.5 Editing project data See also Creating a print preview (Page 304) 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. The print scope for protected objects is limited. Disable the know-how protection to print the objects in full. 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. WinCC Basic V13.0 System Manual, 02/2014 307 Editing projects 7.5 Editing project data 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. 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 blue cross 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 288) Revoking access rights for devices (Page 289) Printout of project contents (Page 291) Designing cover pages and frames (Page 298) 308 WinCC Basic V13.0 System Manual, 02/2014 Editing projects 7.5 Editing project data 7.5.4.2 Printing module labels Print function for module labels Printing of module labels for hardware modules You can print labels for the modules in your project with the help of the TIA Portal. The labels are custom-fit to each module and can contain the following printed information: Symbolic name of the input or output Absolute address of the input or output Symbolic name and additionally the absolute address of the input or output. The order of the information can be specified. The modules are displayed graphically in the device view. If you set the zoom level in the device view to at least 200%, the labels for the individual modules will be visible. The printout on the labels corresponds to the representation of the labeling in the device view. The following figure shows an example of two modules in the device view on which the labeling of the inputs and outputs is visible: Export and further editing as Microsoft Word file Before you can print them, the labels are first exported as a Microsoft Word file (.docx). This file can be further edited with commonly available word processing programs such as Microsoft WinCC Basic V13.0 System Manual, 02/2014 309 Editing projects 7.5 Editing project data Word 2010. The individual labels are represented as a table in the .docx file. You can format the text or the backgrounds of the individual cells as desired. The character spacing of the text within the table is adapted by default, so that texts are not truncated. If you want to prevent this from stretching or compressing the text too much, change the character spacing of the text in the table cell properties. Print media You can print the labels either on ready-made print sheets or on standard DIN A4 paper. You can separate the individual labels from the ready-made print sheets and insert them in the designated labeling areas of your modules. If you print on standard paper, the individual labels must be cut out. Cut marks are automatically included on the printout and serve as aids. Because the paper feeds of different printers differ slightly, the printout may be slightly offset on the paper. When the labels are printed on ready-made print sheets, printing that is accurate to the millimeter is important, because otherwise the text will not be custom-fit inside the stamped area. In addition, if the printing is imprecise, the labeling of an input or output may no longer be congruent with the channel status displays of the module. For this reason, you can enter an offset value for your printer in the TIA Portal to ensure precise printing. For information on how to determine the proper offset value for your printer, refer to Chapter "Determining the print area offset (Page 312)". See also Printing labels (Page 310) Determining the print area offset (Page 312) Documentation settings (Page 290) Printing labels You can print labels for the modules in your project if provision has been made for attaching labels to the utilized modules. The labels are first exported to a Microsoft Word file (.docx). A separate .docx file is created for each module family (for example, for all selected S7-1500 modules). You can then modify the labels according to your wishes. The labels are always printed from the word processing program. If no provision has been made for printing labels, the corresponding shortcut menu command is inactive. If you have selected multiple modules for printing of labels and at least one of the modules does not support this, a message is shown on the "Info > General" tab of the Inspector window. The message lists all unsupported modules, and the export of the print file is continued for the supported modules. Requirement The chosen modules must support the printing of labels. A word processing program that supports Microsoft Word .docx files must be installed, e.g., Microsoft Word 2010. You need the ready-made labels for your modules or commercially available DIN A4 paper. 310 WinCC Basic V13.0 System Manual, 02/2014 Editing projects 7.5 Editing project data Procedure To print labels for hardware modules, follow these steps: 1. In the project tree, select the modules for which you want to print labels. - You can select one or more stations in order to print out labels for all modules plugged into these stations. - Or, select the desired modules below the stations in the "Local modules" folder. 2. Right-click on one of the devices, and select the "Export labels" command from the shortcut menu. The "Export labels" dialog box opens. 3. In the "Content of label" area, select which data are to be printed on the label: - Choose "Symbolic name" in order to print the symbolic name of the input or output (corresponds to the contents of the "Name" column in the IO tag table). - Choose "Absolute address" in order to print the absolute address of the input or output (corresponds to the contents of the "Address" column in the IO tag table). - Choose "Absolute and symbolic address" or "Symbolic and absolute address" in order to print both addresses. The print order corresponds to the indicated order. 4. Select which paper you plan to print on in the "Paper type" area. - Choose "Print on SIEMENS label sheet" if you want to print on a ready-made label sheet for your modules. - Choose "Print on standard paper" if you want to print on standard DIN A4 paper. 5. In the "Offset print area" select correction values for your printer, if required, for proper orientation of the print area. This is only necessary if you are printing on ready-made labels. - Enter a correction value, in millimeters, in the "Vertical offset" field. A negative value shifts the print area upward. A positive value shifts the print area downward. - Enter a correction value, in millimeters, in the "Horizontal offset" field. A negative value shifts the print area to the left. A positive value shifts the print area to the right. 6. In the "Path" field, select the path to which the exported .docx files should be stored. 7. Click the "Export" button to start the export to a .docx file. The .docx files are created. 8. Open the .docx files with a conventional word processing program, such as Microsoft Word 2010, and change the design of the labels if necessary. 9. Print out the labels from your word processing program. To do so, use the paper that you specified in the Export dialog box. 10.If you are using ready-made sheets, separate the labels at the stamped lines provided for that purpose. When standard DIN A4 paper is used, you must cut out the labels. See also Determining the print area offset (Page 312) WinCC Basic V13.0 System Manual, 02/2014 311 Editing projects 7.6 Undoing and redoing actions Determining the print area offset If you are using a ready-made label sheet, the printing on it must be applied precisely so that the text is properly oriented on the prestamped labels and will have the proper fit relative to the channel status displays of the module. However, the paper feeds vary slightly from one printer to another. For this reason, you must enter a suitable correction value for your printer in the TIA Portal, if necessary. The print area is then shifted in the exported .docx file in such a way that the printing fits precisely on the ready-made label sheet. The settings for shifting the print area are stored for the specific Windows user. If you log on to Windows using a different user name, you have to enter the correction values again. The procedure for determining the correction value for your printer is described below. Requirement You require a ready-made label sheet. You must have access to the actual printer that you will use subsequently for the printout. The printer must be made ready for printing on standard DIN A4 paper. Procedure To determine the correction value for your printer, follow these steps: 1. Print out a label sheet on standard DIN A4 paper, as described in Chapter "Printing labels (Page 310)". 2. Compare the printout on the DIN A4 paper with the ready-made label sheet. 3. If the print area is offset, you must use correction values. - Using a ruler, measure the horizontal offset relative to the ready-made label sheet. This will be entered later in the "Horizontal offset" field of the Export dialog box for the printing. If the print area is offset to the right, a negative correction value must be entered. If the print area is offset to the left , a positive correction value must be entered. - Using a ruler, measure the vertical offset relative to the ready-made label sheet. This will be entered later in the "Vertical offset" field of the Export dialog box for the printing. If the print area is offset downward, a negative correction value must be entered. If the print area is offset upward, a positive correction value must be entered. 7.6 Undoing and redoing actions 7.6.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 312 WinCC Basic V13.0 System Manual, 02/2014 Editing projects 7.6 Undoing and redoing actions other words, if you undo an action that lies further down in the stack, all actions located above it in the stack will also be undone automatically. You can redo previously undone actions until you execute a new action. Once you execute a new action, it is no longer possible to redo previously undone actions. Particularities for undoing There are a few actions that empty the action stack. You cannot undo these actions or the actions performed before these actions. The following actions empty the action stack: Saving Project management (creating a new project, opening project, closing a project, deleting a project) Compiling Restoring blocks Establishing an online connection Loading Writing to memory cards Displaying the action stack The "Undo" button in the toolbar is enabled as soon as you perform an action that can be undone. This button is split; you can use the arrow down portion to open a drop-down list containing all actions of the action stack that you can undo. If you had performed actions in an editor other than the currently displayed editor, the corresponding editor is also displayed as a subheading. This allows you to always identify the point at which the undo operation will be applied. The subheadings are removed from the list when the editor responsible can no longer undo actions. Actions you have undone are entered in the action stack from where they can be redone. Here, you can redo actions you have undone. The display of actions you can redo it is analogous to the display of the actions that you can undo. WinCC Basic V13.0 System Manual, 02/2014 313 Editing projects 7.6 Undoing and redoing actions Example of undoing actions The figure below shows how actions performed in various editors and tables are undone: $FWLRQVWDFN +DUGZDUHDQG QHWZRUNHGLWRU 8QGRVHTXHQFH 7DVNSODQQHU 3URJUDPPLQJHGLWRU 0HVVDJHV 6DYHSURMHFW 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 314) Redoing an action (Page 315) 7.6.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. 314 WinCC Basic V13.0 System Manual, 02/2014 Editing projects 7.6 Undoing and redoing actions 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 312) Redoing an action (Page 315) 7.6.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. WinCC Basic V13.0 System Manual, 02/2014 315 Editing projects 7.7 Finding and replacing in projects 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 312) Undoing an action (Page 314) 7.7 Finding and replacing in projects 7.7.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 316 WinCC Basic V13.0 System Manual, 02/2014 Editing projects 7.7 Finding and replacing in projects 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 317) 7.7.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. 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. WinCC Basic V13.0 System Manual, 02/2014 317 Editing projects 7.7 Finding and replacing in projects 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. 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 316) 318 WinCC Basic V13.0 System Manual, 02/2014 Editing projects 7.8 Working with text lists 7.8 Working with text lists 7.8.1 Text lists Introduction You can manage texts to be referenced in alarms centrally. All the texts are stored in text lists. Each text list has a unique name with which you can call up its content. A range of values is assigned to each text in a text list. If a value from a range of values occurs, the corresponding text is called up. All the texts can be translated to all project languages. Here, you have two options available: You can enter the translation of the texts in a list. You will find the list in the project tree under "Languages & Resources > Project texts". You can export all texts to a file in Office Open XML format and enter the translation in a spreadsheet program. The translations can then be imported again. The texts are translated into the other project languages within the framework of the project texts. In the text lists editor, you only have to manage the assignment of individual texts to a text list. Each device in the project has its own text lists. For this reason, these lists are arranged under the devices in the project tree. In addition, there are text lists that apply to all devices. These can be found in the project tree under "Common data > Text lists". User-defined and system-defined text lists There are two types of text lists: User-defined text lists You can create user-defined text lists yourself and fill them with texts; in other words, you can specify value ranges and the corresponding texts yourself. With user-defined text lists, the name of the text list begins with "USER" as default. You can change this name to any suitable name. System-defined text lists System-defined text lists are created by the system. These always involve texts relating to devices. They are automatically created as soon as you insert a device in the project. With system alarms, the name of the text list begins with "SYSTEM". The name of the text list and the ranges of values it contains cannot be modified. You can only edit texts assigned to individual value ranges. WinCC Basic V13.0 System Manual, 02/2014 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. 319 Editing projects 7.8 Working with text lists User-defined text lists System-defined text lists You can add and delete value ranges in the text lists. You cannot add or delete value ranges in the text lists. You can specify both the value ranges as well as the associated texts. You can only edit the text associated with one value range. Device-specific and cross-device text lists Device-specific text lists relate to only one device in the project and are therefore only valid for this device. For this reason, they are arranged under a device in the project tree. Devicespecific 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 userdefined text lists under "Common data". See also Exporting and importing project texts (Page 255) 7.8.2 Creating user-defined text lists Creating text lists You can create user-defined text lists for individual devices. Requirement You are in the project view. A project is open. The project includes a least one device. Procedure To create user-defined text lists, follow these steps: 1. Click on the arrow to the left of a device in the project tree. The elements arranged below the device are displayed. 2. Double-click on "Text lists". All the text lists assigned to the device are displayed in the work area listed in a table. 3. Double-click on the first free row in the table. A new user-defined text list is created. 4. Enter a name for your new text list in the "Name" column. 320 WinCC Basic V13.0 System Manual, 02/2014 Editing projects 7.8 Working with text lists 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.8.3 Editing user-defined text lists Editing user-defined text lists You can enter value ranges and the corresponding texts in user-defined text lists. User-defined text lists are always located below a device in the project tree. Requirement You are in the project view. A project is open. The project includes a least one device. Adding to user-defined text lists with value ranges and texts To add to user-defined text lists with value ranges and texts, follow these steps: 1. Click on the arrow to the left of a device in the project tree. The elements arranged below are displayed. 2. Double-click on "Text lists". All the text lists assigned to the device are displayed in the work area listed in a table. 3. Select a text list in the table. The contents of the selected text list are displayed in the work area. There, you can enter a value range and assign texts to the individual value ranges. 4. Enter the value ranges you require in the "Range from" and " Range to" columns. The entry must be made in the numeric format selected for the text list. 5. Enter a text for each value range in the "Entry" column. 7.8.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". WinCC Basic V13.0 System Manual, 02/2014 321 Editing projects 7.9 Using memory cards 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. 7.9 Using memory cards 7.9.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 322 WinCC Basic V13.0 System Manual, 02/2014 Editing projects 7.9 Using memory cards information on handling memory cards in the TIA Portal, refer to the online help under keyword "Memory Card". NOTICE 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 323) Accessing memory cards (Page 324) Displaying properties of memory cards (Page 324) 7.9.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. Procedure To add a card reader, follow these steps: 1. Open the project tree. 2. Select the "Card Reader / USB memory > Add user-defined Card Reader" command 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 322) Accessing memory cards (Page 324) Displaying properties of memory cards (Page 324) WinCC Basic V13.0 System Manual, 02/2014 323 Editing projects 7.9 Using memory cards 7.9.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 the "Card Reader / USB memory > Card Reader / Show USB memory" command in the "Project" menu. The "Card reader / USB memory" folder is displayed in the project tree. 3. Open the "Card Reader / USB memory" folder. You can now access the memory card. Note If data from a non-installed product is stored on the memory card, the folders that contain these data are shown in gray. You receive an error message when you attempt to access such a folder. Install the corresponding product if needed. See also Basics about memory cards (Page 322) Adding a user-defined card reader (Page 323) Displaying properties of memory cards (Page 324) 7.9.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. Requirement A memory card is inserted in the card reader. The project view is open. 324 WinCC Basic V13.0 System Manual, 02/2014 Editing projects 7.10 Using libraries 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 322) Adding a user-defined card reader (Page 323) Accessing memory cards (Page 324) 7.10 Using libraries 7.10.1 Library basics Introduction You can store objects you want to reuse in libraries. For each project there is a project library that is connected to the project. In addition to the project library, you can create any number of global libraries that can be used over several projects. Since the libraries are compatible with each other, library elements can be copied and moved from one library to another. Libraries are used, for example, to create templates for blocks that you first paste into the project library and then further develop there. Finally, you copy the blocks from the project library to a global library. You make the global libraries available to other employees working on your project. They use the blocks and further adapt them to their individual requirements, where necessary. Both the project library and global libraries distinguish between two different types of objects: Master copies Almost every object can be saved as a master copy and pasted into the project again later. You can, for example, save entire devices with their contents or cover sheets for plant documentation as master copies. Types Elements that are required to run user programs, for example, blocks, PLC data types, userdefined data types or faceplates are suitable as types. Types can be versioned and therefore support professional further development. Projects using the types can be updated as soon as new versions of the types are available. WinCC Basic V13.0 System Manual, 02/2014 325 Editing projects 7.10 Using libraries Project library Each project has its own library, the project 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 In addition to the project library, you use global libraries if you want to use libraries over several projects. Global libraries exist in three versions: System libraries Siemens supplies global libraries for its own software products. These include off-the-peg functions and function blocks that you can use within your project. The supplied libraries cannot be changed. The supplied libraries are loaded automatically matching the project. If you are working in V12 SP1 compatibility mode, the matching libraries for product version V12 SP1 are loaded. For all other projects the supplied libraries of the latest TIA Portal version are loaded. Corporate libraries Corporate libraries are made available centrally by your organization, for example, in a central folder on a network drive. The TIA Portal manages the corporate libraries automatically. As soon as a more recent version of an existing corporate library becomes available, you receive a prompt to update the corresponding corporate library to the more recent version. User libraries Global user libraries are independent of a specific project and can therefore be passed on to other users. Shared access to global user libraries is also possible, for example on a network drive, if all users open the global user library with write protection. Global user libraries you have created yourself from older versions of the TIA Portal can still be used. To continue using global user libraries from older versions of the TIA Portal, they must first be upgraded. Comparing library objects You can compare blocks and PLC data types with the objects of a device. This allows you to determine, for example, whether certain blocks or PLC data types have been used in a project and whether they have been modified. See also Overview of the "Libraries" task card (Page 327) Overview of the library view (Page 330) Overview of the library management (Page 333) Basics on master copies (Page 351) Basics on types (Page 354) 326 WinCC Basic V13.0 System Manual, 02/2014 Editing projects 7.10 Using libraries 7.10.2 Using the "Libraries" task card 7.10.2.1 Overview of the "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. Layout of the "Libraries" task card The "Libraries" task card consists of the following components: WinCC Basic V13.0 System Manual, 02/2014 327 Editing projects 7.10 Using libraries "Library view" button "Project library" pane "Global libraries" pane "Elements" pane "Info" pane "Types" folder "Master copies" folder "Library view" button The "Library view" button is used to change to the library view. The "Libraries" task card and the project tree are hidden with this action. See also: Using the library view (Page 330) "Project library" pane In the "Project library" pane, you can store the objects that you want to use more than once in the project. "Global libraries" pane In the "Global libraries" pane, you manage the global libraries whose elements you want to reuse over several projects. The "Global libraries" pane also lists libraries that were shipped together with the products you purchased. These libraries provide you with ready-made functions and function blocks, for example. The supplied global libraries cannot be edited. "Elements" pane In this pane, you can display the contents of folders in the library. The "Elements" pane is not displayed by default. If you want to display the "Elements" pane, you have to enable it first. Three view modes are available in the "Elements" palette: Details mode The properties of folders, master copies and types are shown in table form in details mode. List mode In list mode, the contents of folders are listed. Overview mode In overview mode, the contents of folders are displayed with large symbols. See also: Using the element view (Page 329) "Info" pane You can display the contents of the library elements in the "Info" pane. The individual versions of types and the last revision date of the version are also displayed. 328 WinCC Basic V13.0 System Manual, 02/2014 Editing projects 7.10 Using libraries "Types" folder In the "Types" directories, you can manage types and type versions of objects that you use as instances in the project. See also: Using types (Page 354) "Master copies" folder In the "Master copies" directories, you can manage master copies of objects that you can use as copies in the project. See also: Using master copies (Page 351) See also Library basics (Page 325) Comparing library elements (Page 381) 7.10.2.2 Using the element view Introduction When you open the "Libraries" task card the first time, the "Project library" and "Global libraries" palettes are opened and the "Info" palette is closed. You can display the "Elements" palette if needed. The elements view shows the elements of the selected library. Three view modes are available in the elements view: Details The properties of folders, master copies and types are shown in table form in details mode. List In list mode, the contents of folders are listed. Overview In overview mode, the contents of folders are displayed with large symbols. The "Info" palette shows the contents of the selected library element. If you select a type in the elements view, for example, the type versions are displayed in the "Info" palette. Requirement The "Libraries" task card is displayed. WinCC Basic V13.0 System Manual, 02/2014 329 Editing projects 7.10 Using libraries Procedure To use the element view, follow these steps: 1. Click "Open or close the element view" in the "Project library" or "Global libraries" pane. 2. To change the view mode from the details view to the list mode or overview mode, click the corresponding icon on the toolbar. See also Library basics (Page 325) Overview of the "Libraries" task card (Page 327) Using global libraries (Page 338) Comparing library elements (Page 381) 7.10.3 Using the library view 7.10.3.1 Overview of the library view Function of the library view The library view combines the functionality of the "Libraries" task card and the overview window. In the library view, the elements of a library are displayed in various views. In the details view, for example, you see additional properties of the individual elements. You can also edit and version the types in the library view. 330 WinCC Basic V13.0 System Manual, 02/2014 Editing projects 7.10 Using libraries Layout of the library view The following figure shows the components of the library view: Library tree Library overview "Library view" button "Open or close library overview" button Library tree The library tree is similar to the "Libraries" task card, apart from a few minor differences. In contrast to the task card, there is no "Elements" palette, because the elements are displayed in the library overview. In addition, you can close the library view in the library tree, or open and close the library overview. See also: "Libraries" task card (Page 327) WinCC Basic V13.0 System Manual, 02/2014 331 Editing projects 7.10 Using libraries Library overview The library overview corresponds to the overview window and displays the elements of the currently selected object in the library tree. You can display the elements in three different views: 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 according to category. In addition, you can perform the following actions in the library overview: Renaming elements Deleting elements Copying elements Moving elements Editing type instances Versioning types WinCC only: Editing faceplates and HMI user data types See also: Overview window (Page 210) See also Basics on master copies (Page 351) Basics on types (Page 354) Opening and closing the library view (Page 332) Library basics (Page 325) Comparing library elements (Page 381) 7.10.3.2 Opening and closing the library view The library view is opened automatically in some cases, for example, when you edit the test instance of a type or when you edit faceplates and HMI user data types. You can also open the library view manually. 332 WinCC Basic V13.0 System Manual, 02/2014 Editing projects 7.10 Using libraries Opening the library view To open the library view manually, follow these steps: 1. Open the "Libraries" task card. 2. Click the "Open library view" button in the "Libraries" task card. The library tree opens. The "Library" task card and the project tree are closed. 3. If the library overview is not displayed, click "Open/close library overview" button in the library tree. The library overview opens. Exit library view To exit the library view, follow these steps: 1. Click the "Close library view" button in the library tree. The library tree closes. The "Libraries" task card and the project tree are opened. See also Overview of the library view (Page 330) Library basics (Page 325) Using the "Libraries" task card (Page 327) Using global libraries (Page 338) Comparing library elements (Page 381) 7.10.4 Using library management 7.10.4.1 Overview of the library management Function of the library management Master copies and types with dependencies to other library elements are subject to some functional restrictions. They can, for example, not be deleted as long as dependencies still exist. This prevents other library elements from becoming useless. The library management is used to identify the dependencies and to create an overview of the work progress. The library management offers the following functions: Display of the correlations of types and master copies If a type is referenced in other types or master copies, the correlations are displayed in the library management. You will also be able to see which library elements reference a type or a master copy. Display of points of use of types in the project Use of filters to narrow down the displayed types WinCC Basic V13.0 System Manual, 02/2014 333 Editing projects 7.10 Using libraries Layout of the library management The following figure shows the components of the library management: Toolbar of the library management "Types" area "Uses" area Toolbar of the library management You can perform the following tasks in the toolbar of the library management: Update view If the project was changed, you can update the view of the library management. Clean up library You can clean up the project library and global libraries. By cleaning up a library, you delete all types and type versions that are not linked to an instance in the project. Harmonize project By harmonizing a project, you adapt the names and the path structures of type uses in the project to the corresponding names and path structures of the types within a library. "Types" area The "Types" area displays the contents of the folder that you have selected in the library view. For each type, the types that it references are displayed. You can expand or collapse all type nodes by using the buttons in the toolbar of the "Types" area. You can also filter the view with the "Filter" drop-down list. 334 WinCC Basic V13.0 System Manual, 02/2014 Editing projects 7.10 Using libraries "Uses" area The "Uses" area gives you an overview of the points of use of the selected types and master copies. The "Uses" area is divided into two tabs: "Uses in the project" tab The "Uses in the project" tab is used to show the instances of type versions and their respective point of use in the project. When you select an instance, you can show the cross references of the instance in the project in the Inspector window. "Uses in the library" tab The "Uses in the library" tab is used to show all points within the library at which a type or a master copy is used. See also Opening library management (Page 335) Filtering the display of types (Page 336) Displaying cross references of an instance (Page 337) Displaying instances in the project (Page 336) Displaying relations to other library objects (Page 337) Library basics (Page 325) Basics on master copies (Page 351) Basics on types (Page 354) 7.10.4.2 Opening library management Procedure To open the library management, follow these steps: 1. Open the library view. 2. Select a type or any folder that contains types. 3. Select the "Library management" command from the shortcut menu. Result The library management opens and the types are displayed with their versions. See also Overview of the library management (Page 333) WinCC Basic V13.0 System Manual, 02/2014 335 Editing projects 7.10 Using libraries 7.10.4.3 Filtering the display of types Use filters to obtain a better overview of types in extensive libraries. A filter provides you with the option of limiting the displayed types. The following filters are available: Display all types that include a version with the "In test" or "In progress" status Display all released types Display all types that have no instances in the project Display all types that have more than one version Requirement The library management is open. Procedure To filter the displayed types, follow these steps: 1. In the "Types" area, select the folder whose contents you want to filter. 2. Select the required filter in the "Filter" drop-down list. In the "Types" area, types are displayed that correspond to the selected filter criteria. See also Overview of the library management (Page 333) State of type versions (Page 356) Creating a test version of a type (Page 361) Editing a test version of a type (Page 362) Creating an editing version of a type (Page 363) 7.10.4.4 Displaying instances in the project In the library management, you can have the instances of all versions of a type or an individual type version displayed. You can jump directly to each instance in the project. Requirement The library management is open. 336 WinCC Basic V13.0 System Manual, 02/2014 Editing projects 7.10 Using libraries Procedure To display the instances of a type or its versions, follow these steps: 1. Select a type or one of its versions in the "Types" area. 2. Open the "Uses in the project" tab in the "Uses" area. The instances in the project are displayed for each type version. The "Path" column shows the path at which the respective instance is located in the project. 3. Optional: Click the path to jump directly to the respective instance in the project tree. The library management is hidden and the instance is selected in the project tree. See also Displaying cross references of an instance (Page 337) Using types (Page 360) Overview of the library management (Page 333) Displaying relations to other library objects (Page 337) 7.10.4.5 Displaying cross references of an instance You can display the cross references of an instance without exiting the library management. Requirement The library management is open. Procedure To display the cross references of an instance in the project, follow these steps: 1. In the "Types" area, select a type version whose instances you want to display. 2. Select the instance of the required type version in the "Uses > Uses in the project" area. 3. Open the "Info > Cross-references" tab in the inspector window. The cross reference of the instance are displayed in the project. See also Using cross-references (Page 382) Overview of the library management (Page 333) Displaying instances in the project (Page 336) 7.10.4.6 Displaying relations to other library objects You can display relations between individual library objects in the library management. The references of the individual type versions to the other library objects are automatically WinCC Basic V13.0 System Manual, 02/2014 337 Editing projects 7.10 Using libraries displayed in the "Types" area. In the "Uses" area, you can also view the other library objects in which the respective type version is referenced. Requirement The library management is open. Procedure To display the other library objects from which a type version is referenced, follow these steps: 1. Select a folder, an individual type or an individual version in the "Types" area. 2. Open the "Uses in the library" tab in the "Uses" area. In the "Uses" area, you can now see which other library objects are referenced by the individual type versions. 3. Optional: To jump to the referenced library object, click on the respective path in the "Path" column. See also Displaying instances in the project (Page 336) Overview of the library management (Page 333) 7.10.5 Using global libraries 7.10.5.1 Creating a global library Requirement The "Libraries" task card is displayed or the library view is open. Procedure To create a new global library, follow these steps: 1. Click the "Create new global library" icon in the toolbar of the "Global libraries" palette or select the command "Global libraries > Create new library" in the "Options" menu. The "Create new global library" dialog opens. 2. Specify the name and the storage location for the new global library. 3. Confirm your entries with "Create". 338 WinCC Basic V13.0 System Manual, 02/2014 Editing projects 7.10 Using libraries Result The new global library is generated and pasted into the "Global libraries" palette. A folder with the name of the global library is created in the file system at the storage location of the global library. This actual library file is given the file name extension ".al12". See also Library basics (Page 325) Opening a global library (Page 340) Displaying properties of global libraries (Page 343) Saving a global library (Page 344) Closing a global library (Page 345) Deleting a global library (Page 346) 7.10.5.2 Compatibility of global libraries You can use the TIA Portal to open global libraries that were created with an older version of the TIA Portal. However, the product version of global libraries must correspond to the product version of the opened project if you want to use objects from the global library in the project. Consequently, you may need to upgrade the global libraries. Opening global libraries from older product versions The table below illustrates the behavior of the TIA Portal when global libraries from older product versions are opened: Product version of the TIA Portal Behavior when a global library is opened (file extension of the respective global library) V10.5 (.al10) The global library is automatically upgraded to the latest library version when opened, following your confirmation. The upgraded global library is a copy of the original library. The original global library is retained unchanged. V11.x (.al11) V12 (.al12) The global library is upgraded when opened. You can choose whether you want to upgrade the global library to the library version V12 SP1 or V13. In both cases, the upgraded library is a copy of the original global library. The original global library is retained unchanged. When you upgrade the global library to library version V12 SP1, the library is opened in compatibility mode. V12 SP1 (.al12) When you open the global library, you can decide whether you want to open it in compatibility mode or upgrade it to the current library version. If you upgrade the global library, a copy of the original global library is created. The original global library is retained unchanged. Compatibility mode If a project is open in compatibility mode for product version V12 SP1 of the TIA Portal, the global library must also be in compatibility mode. You can use objects from the global library WinCC Basic V13.0 System Manual, 02/2014 339 Editing projects 7.10 Using libraries in the project opened in compatibility mode. You can also save new objects in the global library if the objects originate from a project in compatibility mode. A global library in compatibility mode can still be opened and edited with TIA Portal V12 SP1. Backward compatibility of the current library version Global libraries saved with the library format of the TIA Portal V13 are not backward compatible with older versions due to their enhanced functionality. Global libraries in TIA Portal V13 library format can only be used in connection with TIA Portal V13 projects. See also Compatibility of projects (Page 243) Opening a global library (Page 340) Upgrading global libraries (Page 341) Upgrading projects (Page 245) 7.10.5.3 Opening a global library Global libraries can be further developed centrally and used over several projects. Several persons can open a global library simultaneously from a central storage location, provided all users open the global library in write-protected mode. Requirement The "Libraries" task card is displayed or the library view is open. Procedure To open a global library, follow these steps: 1. Click the "Open global library" icon in the toolbar of the "Global libraries" pane or select the command "Global libraries > Open library" in the "Options" menu. The "Open global library" dialog box is displayed. 2. Select the global library you want to open. Library files are identified by the file name extension ".al[version number]". This means global libraries that were saved with TIA Portal V13 have the file name extension ".al13". 3. Write protection is activated for the library. If you want to modify the global library, disable the "Open as read-only". 4. Click "Open". The global library is opened and pasted into the "Global libraries" pane if the library version matches the project version. The "Upgrade global library" dialog box opens if you have selected a global library from an older version of the TIA Portal. More information on upgrading the global library can be found in the chapter "Upgrading global libraries (Page 341)". 340 WinCC Basic V13.0 System Manual, 02/2014 Editing projects 7.10 Using libraries See also Retrieving global libraries (Page 348) Upgrading global libraries (Page 341) Opening projects (Page 244) Compatibility of global libraries (Page 339) Library basics (Page 325) Creating a global library (Page 338) Displaying properties of global libraries (Page 343) Saving a global library (Page 344) Closing a global library (Page 345) Deleting a global library (Page 346) 7.10.5.4 Upgrading global libraries If you want to use objects from a global library in a project, the library version must match the product version of the project. Global libraries must be present in the library version of the TIA Portal V12 SP1 if you want to edit a project in V12 SP1 compatibility mode. Global libraries must be present in the library version of the TIA Portal V13 if you want to edit a project of the product version V13. Depending on the library version, the following options are available: Upgrading the global library to the product version V13 You can upgrade each global library from an older product version to the current product version. You are prompted accordingly when you open the global library. You can manually upgrade global libraries projects that are already open in compatibility mode to product version V13. Upgrading the global library to the product version V12 SP1 (compatibility mode) If you open a global library from version V12 of the TIA Portal, you also have the option of upgrading the global library to the library version V12 SP1. In this case, however, the global library can only be used in connection with projects from the TIA Portal V12 SP1. Upgrading global libraries from V11.x or lower Proceed as follows to upgrade a global library from TIA Portal V11.x or lower: 1. Open the global library. The "Upgrade global library" dialog box opens. 2. Click "OK". A copy of the global library is created and upgraded. The copy of the global library receives the name extension "_V13". The global library is opened. WinCC Basic V13.0 System Manual, 02/2014 341 Editing projects 7.10 Using libraries Upgrading global libraries from V12 Proceed as follows to upgrade a global library from TIA Portal V12: 1. Open the global library. The "Upgrade global library" dialog box opens. 2. Select the target version for the upgrade: - Click "Yes" to upgrade the global library to product version V13. - Click "No" to upgrade the global library to product version V12 SP1 and to work in compatibility mode. A copy of the global library is created and upgraded. The copy of the global library receives the name extension "_V13" or "_V12SP1". The global library is opened. Upgrading V12 SP1 libraries or using them in compatibility mode Proceed as follows to upgrade a global library from TIA Portal V12 SP1 or to use it in compatibility mode: 1. Open the global library. The "Upgrade global library" dialog box opens. 2. Select how you want to proceed with the global library: - Click "Yes" to upgrade the global library to product version V13. - Click "No" to use the global library in compatibility mode. A copy of the global library is created and upgraded or the library is opened changed. The copy of the global library receives the name extension "_V13". Manually upgrading libraries in compatibility mode to V13 To do this, a global library must already be open in compatibility mode for the TIA Portal V12 SP1. Proceed as follows to manually upgrade global libraries to the library version V13: 1. Right-click on the global library you want to upgrade. 2. Select the "Upgrade library" command in the shortcut menu. The "Upgrade" dialog opens. 3. Confirm with "Yes". A copy of the global library is created and upgraded. The copy of the global library receives the name extension "_V13". The upgraded global library is opened. The original global library is closed. See also Opening a global library (Page 340) Compatibility of global libraries (Page 339) Upgrading projects (Page 245) 342 WinCC Basic V13.0 System Manual, 02/2014 Editing projects 7.10 Using libraries 7.10.5.5 Displaying properties of global libraries Global libraries contain properties for describing the respective library in more detail. Properties include the following: General information about the library This includes the following information: creation time, author, file path, file size, copyright, etc. Many of the attributes can be changed. Library history The library history contains an overview of the migrations performed. Here you can also call the log file for the migrations. The library history also contains information on updates of the global library. Support packages in the library You can display an overview of the additional software needed to work with all devices in the project. Software products in the library You can display an overview of all installed software products needed for the project. Requirement The "Libraries" task card is displayed or the library view is open. Procedure To display the properties of a global library, follow these steps: 1. Right-click the global library whose properties you want to display. 2. Select the "Properties" command in the shortcut menu. A dialog containing the properties of the global libraries opens. 3. Select the properties in the area navigation that you want to have displayed. See also Opening a global library (Page 340) Library basics (Page 325) Creating a global library (Page 338) Saving a global library (Page 344) Closing a global library (Page 345) Deleting a global library (Page 346) 7.10.5.6 Displaying logs of global libraries Logs are created when you update or clean up global libraries or assign a shared version to several types. The logs list all changes you have made to the global library. The logs are stored WinCC Basic V13.0 System Manual, 02/2014 343 Editing projects 7.10 Using libraries together with the global library and are always available once you have opened the global library. Procedure To open the logs of a global library, follow these steps: 1. Open the global library in the "Libraries" task card or in the library view. 2. Open "Common data > Logs" in the lower-level folder. 3. Double-click the required log. The log opens in the work area. See also Updating a library with the contents of another library (Page 377) 7.10.5.7 Saving a global library After you have changed a global library, you need to save it. You can save a global library under another name using the "Save library as" command. Note Backward compatibility to older versions of the TIA Portal Note that global libraries can no longer be opened in older versions of the TIA Portal once they have been saved in the newer version. Requirement The "Libraries" task card is displayed or the library view is open. Saving changes To save a global library, follow these steps: 1. Right-click on the global library you want to save. 2. Select the "Save library" command in the shortcut menu. Saving a global library under another name To save a global library under another name, follow these steps: 1. Right-click the global library that you want to save under a different name. 2. Select the "Save library as" command in the shortcut menu. The "Save global library as" dialog opens. 344 WinCC Basic V13.0 System Manual, 02/2014 Editing projects 7.10 Using libraries 3. Select the storage location and enter the file name. 4. Confirm your entries with "Save". The library is saved in the specified location under the new name. The original library is retained. See also Working with archives of global libraries (Page 346) Archiving global libraries (Page 347) Library basics (Page 325) Creating a global library (Page 338) Opening a global library (Page 340) Displaying properties of global libraries (Page 343) Closing a global library (Page 345) Deleting a global library (Page 346) 7.10.5.8 Closing a global library Global libraries are independent of projects. This means that global libraries are not closed together with your project. You must therefore close global libraries explicitly. Requirement The "Libraries" task card is displayed or the library view is open. Procedure To close a global library, follow these steps: 1. Right-click on the global library you want to close. 2. Select the "Close library" command in the shortcut menu. If you have made changes to the global library, select whether or not you want to save the changes. The global library is closed. See also Creating a global library (Page 338) Opening a global library (Page 340) Displaying properties of global libraries (Page 343) Saving a global library (Page 344) Library basics (Page 325) Deleting a global library (Page 346) WinCC Basic V13.0 System Manual, 02/2014 345 Editing projects 7.10 Using libraries 7.10.5.9 Deleting a global library If you no longer require a global library, you can delete it. Libraries supplied by Siemens cannot be deleted. Requirement The "Libraries" task card is displayed or the library view is open. Procedure To delete a global library, follow these steps: 1. Right-click the global library you want to delete. 2. Select the "Delete" command in the shortcut menu. 3. Click "Yes" to confirm. Result The global library is removed from the "Global libraries" palette. The entire library for the global library is deleted from the file system. See also Library basics (Page 325) Creating a global library (Page 338) Opening a global library (Page 340) Displaying properties of global libraries (Page 343) Saving a global library (Page 344) Closing a global library (Page 345) 7.10.5.10 Archiving and disabling global libraries Working with archives of global libraries If you want to back up global libraries on an external hard drive or send them via e-mail, for example, use the archiving function to reduce the storage space of the library. 346 WinCC Basic V13.0 System Manual, 02/2014 Editing projects 7.10 Using libraries Options for reducing the size of the project There are two ways to reduce the storage space of global libraries: Creating a compressed archive of global libraries Archives of global libraries are compressed files, each containing an entire global library, including the entire folder structure of the library. Before the directory with the global library is compressed into the archive file, all files are reduced to their essential components to further decrease the storage space. Compressed archives of global libraries are therefore well suited for sending via e-mail. Compressed archives of global libraries of TIA Portal V13 have the file extension ".zal13". Archives from TIA Portal V12.x have the file extension ".zal12". To open a compressed archive of a global library, retrieve the archive. The archive file is extracted to a location you have selected with the entire folder structure and all files. Minimizing global libraries You can skip additional compression in an archive file, and instead create a copy of the global library directory. The included files can be reduced to the essential elements. This minimizes the required storage space. The full functionality of the global library is retained and the global library can be loaded as usual. Minimized global libraries are especially well suited for archiving, for example, on an external medium. See also Archiving global libraries (Page 347) Retrieving global libraries (Page 348) Archiving global libraries You reduce the storage space of a global library by packing it into a compressed file. You can also reduce the storage space by saving the global library reduced to the essential elements. You can do both of these with the archiving function for global libraries. When you archive a library, the original library version is retained. This means libraries in compatibility mode for TIA Portal V12 SP1 are still compatible with TIA Portal V12 SP1. Requirement The global library is loaded. Procedure To archive a global library, follow these steps: 1. Select the global library that you want to archive. 2. Right-click the global library and select the "Archive" command from the shortcut menu. The "Archive global library as..." dialog opens. 3. Select the directory where you want to save the archive file or the new directory of the global library. The directory may not be located in a project directory or within the directory of a global library. WinCC Basic V13.0 System Manual, 02/2014 347 Editing projects 7.10 Using libraries 4. Select the file type from the "File type" drop-down list: - Global libraries archive, if you want to create a compressed file of the library. - Minimized global library, if you only want to create a copy of the library directory with minimal storage requirement. 5. Enter a file name in the "File name" field if you are creating an archive file. If you are creating a minimized global library, enter the name of the new library directory to be created in the "File name" box. 6. Click "Save". Result A compressed file with the extension ".zal13" or ".zal12" is generated. The file extension depends on whether you have archived a library in V12 SP1 compatibility mode or in the library format of TIA Portal V13 The file includes the complete directory of the global library. The individual files of the global library are also reduced to the essential components in order to save space. If you have minimized the global library, only a copy of the original directory of the global library is created at the required location. The files contained within it were reduced to their essential components in order to save space. See also Working with archives of global libraries (Page 346) Retrieving global libraries (Page 348) Retrieving global libraries Before you can use an archived global library, you have to retrieve it. The global library is extracted and then opened in the TIA Portal. Procedure To extract the archive of a global library, follow these steps: 1. Select the "Global libraries > Retrieve library" command in the "Options" menu. The "Retrieve archived global library" dialog opens. 2. Select the archive file. 3. Select the check box "Open read-only" if you want to load the global library write-protected. 4. Click "Open". 5. The "Find folder" dialog opens. 6. Select the target directory to which the archived global library should be extracted. 7. Click "OK". 348 WinCC Basic V13.0 System Manual, 02/2014 Editing projects 7.10 Using libraries Result The global library is extracted to the selected directory and opened immediately. If the archive file contained a global library from TIA Portal V12 SP1, the global library is opened in compatibility mode. Manually upgrade the library to the library version of TIA Portal V13, if necessary. See also Working with archives of global libraries (Page 346) Archiving global libraries (Page 347) Opening a global library (Page 340) Compatibility of global libraries (Page 339) Upgrading global libraries (Page 341) 7.10.5.11 Using global corporate libraries Basics of corporate libraries Introduction Corporate libraries are global libraries made available by an administrator and assigned to the TIA Portal. The administrator can assign new libraries or change libraries at any time. New libraries are automatically uploaded in the TIA Portal following your confirmation. As soon as more recent versions of corporate libraries are available, the existing corporate libraries are automatically updated to the more recent version, also following your confirmation. The corporate libraries are located just like normal global libraries in the "Global libraries" palette of the "Libraries" task card. Providing corporate libraries Corporate libraries can be saved in any directory on the hard drive of the computer or on a network drive. Use an XML file to assign corporate libraries to the TIA Portal. The XML file includes the directories and names of the assigned corporate libraries. The XML file must be saved in the following directory on the hard drive of the computer: C:\ProgramData\Siemens\Automation\Portal V13\CorporateSettings\ The XML file must be named "CorporateSettings.xml". You either copy the configuration file yourself to the corresponding directory or the configuration file is assigned to you through the company network. The valid configuration is automatically applied when the TIA Portal is started. When the TIA Portal is started, it continuously monitors the directory for configuration files. If the configuration file has changed, you receive a prompt to apply the new configuration. You can reject this prompt twice. You will always receive the next prompt three hours later. You must apply the new configuration at the third prompt. You receive a changed configuration file from the project administrator, for example, if corporate libraries have been added or deleted. WinCC Basic V13.0 System Manual, 02/2014 349 Editing projects 7.10 Using libraries Options as project administrator You can automatically assign the configuration file or the corporate libraries to the computers of the team members or distribute updates to the team members. This function is not part of the TIA Portal and requires a corresponding IT infrastructure in your company. If you want to administer the configuration file centrally, discuss this approach with the IT managers at your company. Creating a configuration file Use a configuration file in XML format to make the corporate libraries available in the TIA Portal. The configuration file includes the directories and file names of the libraries to be loaded. Below you will learn how you create the XML configuration file and where to save it. Procedure To provide a configuration file for corporate libraries, follow these steps: 1. Create an XML configuration file with the content listed below. Use the coding "UTF-8". 2. Save the XML file under the name "CorporateSettings.xml". 3. Save the file in the following directory on your computer: C:\ProgramData\Siemens\Automation\Portal V13\CorporateSettings\ Content of the XML configuration file The XML configuration file must have the following content: XML <?xml version="1.0" encoding="utf-8"?> <Document> <Settings.Settings ID="0"> <ObjectList> <Settings.General ID="1" AggregationName="General"> <AttributeList> <CorporateLibraryPaths> <!-- Example of an entry --> <Item>D:\CorporateLibraries\Corporate_Library_1.al13</Item> <!-- Here you enter additional global libraries, if any. --> </CorporateLibraryPaths> </AttributeList> </Settings.General> </ObjectList> </Settings.Settings> </Document> Result As soon as you have saved the XML configuration file in the respective directory, you will receive the prompt (in the TIA portal) to download the corporate libraries in the TIA Portal. 350 WinCC Basic V13.0 System Manual, 02/2014 Editing projects 7.10 Using libraries 7.10.6 Creating folders in a library The library elements are stored in the libraries according to their type in the "Types" and "Master copies" folders. Create additional folders below "Types" and "Master copies" to further organize master copies and types. Requirements The "Libraries" task card is displayed or the library view is open. If you want to create new folders within a global library, you have to open the global library with write permission. Procedure To create a new folder, follow these steps: 1. Right-click any folder within the library. 2. Select "Add folder" from the shortcut menu. A new folder is created. 3. Enter a name for the new folder. See also Working with types in the project library (Page 359) Filtering master copies (Page 353) 7.10.7 Using master copies 7.10.7.1 Basics on master copies Master copies are used to create standardized copies of frequently used elements. You can create as many elements as needed and insert them into the project based on a master copy. The elements inherit the properties of the master copy. You store master copies either in the project library or in a global library. Master copies in the project library can only be used within the project. When you create the master copy in a global library, it can be used in different projects. The following elements can be created as master copies in the library, for example: Devices with their device configuration Tag tables Instruction profiles Monitoring tables Elements from the documentation settings, for example, cover sheets and frames WinCC Basic V13.0 System Manual, 02/2014 351 Editing projects 7.10 Using libraries Blocks and groups containing multiple blocks PLC data types and groups containing multiple PLC data types Text lists Alarm classes Technology objects In many cases, the objects you add as master copy contain additional elements. A CPU, for example, can contain blocks. If the included elements are uses of a type version, the used versions of the types are automatically created in the library. The elements contained therein are then used as an instance and linked to the type. See also Adding master copies (Page 352) Using master copies (Page 354) Basics on types (Page 354) Filtering master copies (Page 353) 7.10.7.2 Adding master copies If you want to use objects multiple times, copy them as master copies in the project library or in a global library. You can choose from the following methods for creating master copies: You can select one or more elements and generate a master copy from it You can select multiple elements and generate a master copy from each element Requirement The "Libraries" task card is displayed. If you add a device as a master copy, this device meets the following requirements: - The device is compiled and consistent. - The device contains no test instance of a type. If you add the master copy to a global library, the global library is opened with write permission. Creating a master copy from one or more elements To create a master copy for one or more elements, follow these steps: 1. Open the library in the "Libraries" task card. 2. Drag one or more elements and drop them into the "Master copies" folder or any subfolder of "Master copies". Alternative: Copy the elements to the clipboard and paste them at the required location. The element is pasted into the library as a single master copy. 352 WinCC Basic V13.0 System Manual, 02/2014 Editing projects 7.10 Using libraries Creating a master copy for each element among multiple elements To create a master copy for each element among multiple elements, follow these steps: 1. Open the library in the "Libraries" task card. 2. Copy to the clipboard the elements that you want to create as master copies. 3. Right-click on the "Master copies" folder or any of its subfolders in the library. 4. In the shortcut menu, select "Paste as separate master copies". The elements are pasted into the library as separate master copies. In each case, a separate type is created automatically for any objects contained. See also Basics on master copies (Page 351) Using master copies (Page 354) Library basics (Page 325) Adding types to the project library (Page 359) 7.10.7.3 Filtering master copies To make it easier to keep track of a large number of master copies, you can filter the display according to the type of master copy. Requirement The "Libraries" task card is displayed or the library view is open. Procedure To filter the view, follow these steps: 1. Open the "Master copies" folder in the project library or a global library. 2. In the drop-down list of the toolbar, select the type of objects you want to display under "Master copies". Result Only the selected type of master copies is displayed. You can set the filter to "All" to return to an unfiltered view. See also Library basics (Page 325) Creating folders in a library (Page 351) Basics on master copies (Page 351) WinCC Basic V13.0 System Manual, 02/2014 353 Editing projects 7.10 Using libraries Using master copies (Page 354) Using the element view (Page 329) 7.10.7.4 Using master copies Master copies are contained either in the project library or in a global library. Requirement The "Libraries" task card is displayed. Procedure To paste a master copy into the project, follow these steps: 1. Open the "Master copies" folder or any subfolder of "Master copies" in a library. 2. Drag-and-drop one or more master copies to the desired point of use. A copy of the master copy is inserted. Or: 1. Open the element view. 2. Drag the master copy from the "Elements" palette and drop it at the location where you want to use it. A copy of the master copy is inserted. See also Basics on master copies (Page 351) Adding master copies (Page 352) Filtering master copies (Page 353) Library basics (Page 325) Using the element view (Page 329) 7.10.8 Using types and their versions 7.10.8.1 Basics on types Using types Types are elements that are required for the execution of user programs. Types can be versioned and further developed from a central location. The following elements can be stored as type in the project library or the global library: 354 WinCC Basic V13.0 System Manual, 02/2014 Editing projects 7.10 Using libraries Functions (FCs) Function blocks (FBs) PLC data types User data types Faceplates Figures User-defined functions Any number of instances can be derived from the versions of types in the project. The instances are then linked to the version of the type. If you are using types from a global library, the type is also created in the project library. If the type already exists in the project library, any missing type versions are added if necessary. The instance is then linked only to the respective type version in the project library. Types and their instances are marked with a black triangle. The following figure shows an instance, marked with a black triangle, and an ordinary program block: Basics on versioning types Type versioning provides you with the means to develop types centrally and then roll out the most recent version to the individual projects as an update. In this way, error corrections and added functions can be easily integrated into existing projects. If you have created a new version of a global library, you can update existing projects in an automatic process. This minimizes errors and reduces the amount of maintenance work for large automation solutions that contain numerous individual projects. Versioning allows you to trace the development process of individual types. Before you release a version, you can try it out in a test environment to determine whether changes made to a type integrate smoothly into an existing project. You only release a version for productive use after you have made sure that everything operates without errors. You can view the history of individual instances in the project at any time and determine the version from which the instance was derived. The TIA Portal also checks automatically if there are associated objects with individual versions of a type. Associated objects can be, for example, PLC data types or other blocks referenced in a block. All associated objects are already taken into consideration during the creation of a type or during copying between libraries. Before being released, versions of types are checked for their consistency to ensure that no inconsistencies arise in the project. Versions of types Versions are assigned to each type. The version number is displayed in both the "Libraries" task card as well as the library view next to the respective type. The version number is also displayed in the project tree next to instances of types. This allows you to see at all times which version of an instance is used in the project. WinCC Basic V13.0 System Manual, 02/2014 355 Editing projects 7.10 Using libraries The version number consists of three numbers separated by periods. You can randomly assign the first two digits. Numbers from 1 to 999 are permitted as the first two numbers. The third digit is the build number. It is automatically incremented by one when you edit an instance related to the version. The build number is reset to 1 when you release the version. The versions of types can have three states: In progress (faceplates and HMI user data types) In test (all sorts of types except faceplates and HMI user data types) Released The following figure shows a type with two versions. One version is "in test" and one version is released: See also State of type versions (Page 356) Basics on master copies (Page 351) Adding types to the project library (Page 359) Using types (Page 360) 7.10.8.2 State of type versions The versions of types can be in three different states. The states can be determined from the instance or in the library. "In progress" status Only versions of faceplates and HMI user data types have the "in progress" state. If a version is in progress, "in progress" appears next to the version in the library. When you create a new type or a new version of a released type, the type is assigned the status "in progress". Types with the status "in progress" can be edited in the library view. A reference to an instance in the project does not have to exist. Upon release, the compatibility of the type is tested by a consistency check. "In test" status All types except for faceplates and HMI user data types can have the "in test" status. If a version is in test, "in test" appears next to the instance and in the library. A version in the test state is linked to a test instance in the project. This allows you try out the effects of your changes in a test environment including all online functions before you release a type for use in actual operations. 356 WinCC Basic V13.0 System Manual, 02/2014 Editing projects 7.10 Using libraries "Released" status The "released" status is available for all types, regardless of the point of use. If a version has been released, the symbol of the version is marked with a seal in the library: Released versions can be opened with write protection in their instance. If you want to edit a released version, you must first create a new "in progress" or "in test" version. See also Basics on types (Page 354) Using types (Page 360) Creating a test version of a type (Page 361) Editing a test version of a type (Page 362) Creating an editing version of a type (Page 363) Performing a consistency check for a version (Page 363) Discarding versions (Page 364) Release versions (Page 365) Assigning a version (Page 373) Updating the project to the latest versions (Page 368) Remove the link between instance and type (Page 369) Filtering the display of types (Page 336) 7.10.8.3 Displaying a released type version If you display a released version but do not want to edit it, open the instance with write protection. All types except faceplates and HMI user data types can be opened directly at the instance. Faceplates and HMI user data types can only be opened in the "Libraries" task card or in the library view. Requirement The released version has an instance in the project; except with types, this is a faceplate or an HMI user data type. WinCC Basic V13.0 System Manual, 02/2014 357 Editing projects 7.10 Using libraries Opening a type version at an instance To open a released version of a type with write protection starting from an instance, follow these steps: 1. Select the released version at the instance in the project tree. 2. To do this, right-click the instance and select the "Open" command from the shortcut menu. The instance is opened with write protection. Opening a type version in the "Libraries" task card or library view To open a released version of a type in the "Libraries" task card or in the library view, follow these steps: 1. Select the version. 2. To do this, right-click the version and select the "Open" command from the shortcut menu. If it is a faceplate or HMI user data type, it is opened directly in the library view. In this case, skip the remaining steps. If it is any other type, the "Open type" dialog opens. 3. Select the instance with the version that you want to display from the list of instances. 4. Click "OK" to confirm. The instance is opened with write protection. 7.10.8.4 Displaying properties of a type or version The following properties can be viewed and changed in the properties of a type or its versions, if needed: Name of the type Version number (only visible in the case of a version) Data and time of the last change to the version (only visible in the case of a version) Author who created the version (only visible if there is a version) Comments on the type or the version of the type The comment on the type can be changed. Original library (only visible in the case of a version) Displayed is the project and the library from which the current version of the type was generated. This information is important, for example, for finding the original of the type after it has been copied from another library. ID of the type or the version of the type This ID is used to uniquely identify the type or the version of the type, even if, for example, there are types or versions with an identical name within the project library or the global library. The ID cannot be changed and is assigned automatically. 358 WinCC Basic V13.0 System Manual, 02/2014 Editing projects 7.10 Using libraries Procedure To display the properties of a type or a version and to enter a comment, follow these steps: 1. Select a type or the version of a type in the "Libraries" task card or in the library view. 2. To do this, right-click on the type or one of its versions and select the "Properties" command from the shortcut menu. The "Properties" dialog box opens. 3. If needed, enter a comment on the type in the "Comment" field or edit an existing comment. 7.10.8.5 Working with types in the project library Adding types to the project library Types for reuse in the project can be created in the project library for various elements. You can create the following elements as types, for example: Program blocks Faceplates PLC data types HMI user data type If you add an element as a type to the project library and this element has dependencies to other elements, the dependent elements are automatically created as a type as well. After a type has been added to the project library, the type is linked to the added element from the project. Requirement The "Libraries" task card is displayed. The elements that you want to add as type are compiled. The elements are consistent. Procedure To add an existing element to the project library as a type, follow these steps: 1. Open the project library in the "Libraries" task card. 2. Drag-and-drop one or more elements into the "Types" folder or any subfolder of "Types". Alternative: Copy the elements in the project tree to the clipboard and add the elements in the desired project library folder. The "Generate type" dialog opens. WinCC Basic V13.0 System Manual, 02/2014 359 Editing projects 7.10 Using libraries 3. Enter the properties of the new type: - Enter a name for the new type in the "Name of the type" field. - Enter a version number for the new type in the "Version" field. - Enter the name of the editor who is responsible for the type in the "Author" field. - Enter a comment on the type in the "Comment" field. 4. Click "OK" to confirm. The new type is generated with a released version. The version is linked to the element that has been added. See also Basics on types (Page 354) Library basics (Page 325) Adding master copies (Page 352) Using types To use the version of a type, create an instance of the version at a suitable location in the project tree. You can also position faceplates and HMI user data types directly in the editor. The instance is then linked to the version of the respective type. If the type contains dependent elements such as a PLC data types referenced in a block, these are also created as instance at a suitable location. You can only assign a version of the same type to a device. If necessary, you can create instances of several types at the same time. Requirement The "Libraries" task card is displayed. The desired versions have been released. A device which supports the sort of desired type is already available in the project The device is not yet assigned any further instance of the same type. Procedure To create instances of type versions, follow these steps: 1. In the project library, navigate to the versions of the types that you want to use. 2. Select the versions of which you want to create instances. 3. Drag the required type versions from the project library and drop them at the location where you want to use them. Alternative: To automatically use the most recent version, drag the types from the project library and drop them at the location where you want to use them. 360 WinCC Basic V13.0 System Manual, 02/2014 Editing projects 7.10 Using libraries Result Instances of the types and their dependent elements are generated and pasted at the location where you want to use them. The instances are connected to the respective version of the type in the project library. See also Basics on types (Page 354) State of type versions (Page 356) Library basics (Page 325) Using master copies (Page 354) Creating a test version of a type Before you release a type for productive use, you need to test the type within a project and on the automation system. The test is conducted in a specific test environment. This test environment can be a CPU, for example. Create a version with "in testing" status for the test. The creation of a version "in testing" is suitable for all sorts of types except for faceplates and HMI user data types. On the other hand, versions "in progress" can be created from faceplates and HMI user data types. There are two ways to create a test version of a type and define the test environment: In the "Libraries" task card or library view Generate the new version with "in testing" status in the "Libraries" task card or in the library view. You can generate the new version either directly from the type or from a specific version of the type. At an instance in the project tree You can also create the test version directly at the instance in the project tree. Since the instance is always used in a specific version in the project, a new version of the type is generated from the version used at the instance. You can also create test versions from several types at the same time. The following rules apply to a version "in testing": You can set only one version to "in testing" for each type at a given time. A version in testing may only be linked to a single instance in the project. Therefore, it is not possible to copy an instance to the clipboard, to duplicate it or to create an additional type from the instance as long as it has "in testing" status. Requirement There is at least one instance of the type within the project in a given version. If you want to create the new version from a particular version of the type, the instance must be used in this version in the project. WinCC Basic V13.0 System Manual, 02/2014 361 Editing projects 7.10 Using libraries Procedure To generate a new test version of a type or the version of a type, follow these steps: 1. Select the type, a version of the type, or the instance. When you create the test version directly at the instance, you can select several elements or folders with multiple selection. You can skip steps 3 and 4 because the test environment is already defined by the selected instance. 2. Right-click the selected element and select the "Edit type" command from the shortcut menu. If you have started the editing in the "Libraries" task card or in the library view, the "Edit type" dialog opens. If you have started the editing at the instance in the project tree, the test instance is immediately opened for editing in the library view. 3. Select an instance of the type from the list in the project. If you have started editing at the type itself, the following applies: - The location at which the instance is used (for example, the CPU) is also used as test environment for the subsequent editing of the type. - Selecting the test instance also defines the version to be edited. The following applies to editing a specific version: If your starting point is a specific version, you can only select from the list instances that are used in the same version. 4. Click "OK" to confirm. Result A new version of the type is created. The new version is "in testing" and is identified as such in the user interface. See also Basics on types (Page 354) State of type versions (Page 356) Library basics (Page 325) Editing a test version of a type When you edit a version "in testing", a new version is not created. You can start the editing of the test version at the instance in the project tree, in the "Libraries" task card" or in the library view. Note Deleting and renaming interface parameters You can add new parameters. However, if you rename or delete existing parameters, these parameters will not be supplied when the block is called. 362 WinCC Basic V13.0 System Manual, 02/2014 Editing projects 7.10 Using libraries Procedure To edit the test version of a type, follow these steps: 1. Right-click the test version or the instance. 2. Select the "Edit type" command from the shortcut menu. The test instance is opened in the library view and can be edited. See also Basics on types (Page 354) State of type versions (Page 356) Library basics (Page 325) Performing a consistency check for a version (Page 363) Discarding versions (Page 364) Release versions (Page 365) Creating an editing version of a type If you want to edit a type with faceplates or HMI user data types, create a new "in progress" version of the type. The new version is edited in the library view. To check the compatibility of the changes, a consistency check is automatically performed for the type prior to the release. Requirement The project library is opened in the "Libraries" task card or in the library view. Procedure To create a new version of a type in progress, follow these steps: 1. Right-click the type or the version of the type. 2. Select the "Edit type" command from the shortcut menu. A new "in progress" version is created and opened for editing in the library view. See also Basics on types (Page 354) State of type versions (Page 356) Library basics (Page 325) Performing a consistency check for a version A type version can unintentionally obtain an inconsistent state during editing. To notice errors in the development process in good time, you can regularly perform a consistency check. WinCC Basic V13.0 System Manual, 02/2014 363 Editing projects 7.10 Using libraries However, the consistency check always takes place automatically as soon as you release a version. Details of how to start the consistency check manually for the version of a type are provided below. Requirement The project library is opened in the "Libraries" task card or in the library view. The version is "in progress" or "in test". Procedure To perform a consistency check for the version of a type, follow these steps: 1. Right-click on the version that you want to check for consistency. 2. Select the "Consistency check" command in the shortcut menu. The consistency check is carried out. You receive a message with the result of the consistency check. See also Release versions (Page 365) Discarding versions (Page 364) Editing a test version of a type (Page 362) Basics on types (Page 354) State of type versions (Page 356) Library basics (Page 325) Discarding versions Discard versions of a type "in test" or "in progress" when you no longer need the version. You can also select several types or folders and discard all test or editing versions contained therein. All uses of the deleted versions are reset to the last released status. Requirement The versions that you want to discard are in the "In test" or "In progress" status. Your are in the library view of the "Libraries" task card is open. 364 WinCC Basic V13.0 System Manual, 02/2014 Editing projects 7.10 Using libraries Procedure To discard one version, follow these steps: 1. Right-click the version that you want to discard. 2. Select the "Discard changes and delete version" command from the shortcut menu. The version is deleted. Alternative: 1. Click the "Discard changes and delete version" button in the toolbar while a version is opened for editing. The version is deleted. See also Basics on types (Page 354) State of type versions (Page 356) Library basics (Page 325) Performing a consistency check for a version (Page 363) Discarding all versions within a folder You can discard all versions with the "In test" or "In progress" status at the same time within a folder. All uses of the deleted version are reset to the last released status. Requirement Your are in the library view of the "Libraries" task card is open. Discarding a version of a single type To discard all versions within a folder, follow these steps: 1. Right-click the folder. 2. Select the "Discard all" command from the shortcut menu. All "In test" or "In progress" versions are deleted. Release versions When you are finished editing a type version, release the version for productive use. Assign a version number for the release. You can also select to release several type versions at the same time. WinCC Basic V13.0 System Manual, 02/2014 365 Editing projects 7.10 Using libraries Requirement The "Libraries" task card is open or you are in the library view. The versions that you want to release are "in test" or "in progress" status. The versions are consistent. A consistency check is performed as soon as you start the release. If errors that prevent a release occur during the consistency check, a message is displayed indicating how you can correct the errors. Procedure To release type versions, follow these steps: 1. Select the versions you want to release. 2. Right-click your selection. 3. Select the "Release version" command from the shortcut menu. The "Release type version" dialog box opens. 4. If necessary, change the properties of the version: - Enter a name for the type in the "Name" field. If you have selected several versions for release, the "Name" field cannot be changed. - In the "Version" field, define a main and an intermediate version number for the version to be released. If you have selected several versions for release, the "Version" field cannot be changed and the last version number is used for the release. - In the "Author" field, enter the editor of the version to be released. - In the "Comment" field, enter a comment on the version to be released. 5. Optional: Select the "Delete all unused type versions from the library" check box to delete all versions from the library that are not connected to any instance in the project. Versions with dependencies on other types or master copies are not deleted. 6. Click "OK" to confirm. Alternative: 1. Click the "Release version" icon in the toolbar while a version is opened for editing. 2. Continue with steps 3 to 5 of the description above. Result The selected versions are released. The properties are applied for the types themselves, the versions to be released, and for all future versions. Versions already released remain unaffected by the changes. If needed, all instances with the same original version are updated to the most recent version and the unused versions of the type are deleted. 366 WinCC Basic V13.0 System Manual, 02/2014 Editing projects 7.10 Using libraries See also Releasing all versions within a folder (Page 367) Basics on types (Page 354) State of type versions (Page 356) Library basics (Page 325) Performing a consistency check for a version (Page 363) Assigning a version (Page 373) Adding types to a global library (Page 370) Updating the project to the latest versions (Page 368) Releasing all versions within a folder When you are finished editing all types within a folder, release all versions simultaneously. Requirement Your are in the "Libraries" task card or in the library view. The folder includes versions "in test" or "in progress" status. All versions "in test" or "in progress" are consistent. A consistency check is performed as soon as you start the release. If errors that prevent release occur during the consistency check, a message is displayed indicating how to correct the errors. Procedure To release all type versions within a folder, follow these steps: 1. Right-click the required folder. 2. Select the "Release all" command from the shortcut menu. The "Release type version" dialog box opens. 3. If necessary, change the properties of the version: - In the "Author" field, enter the editor of the versions to be released. - In the "Comment" field, enter a comment on the versions to be released. 4. Select the "Delete all unused type versions from the library" check box to delete all versions from the library that are not connected to any instance in the project. Versions with dependencies on other types or master copies are not deleted. 5. Click "OK" to confirm. Result All type versions "in test" or "in progress" status within the selected folder are released. WinCC Basic V13.0 System Manual, 02/2014 367 Editing projects 7.10 Using libraries The properties are applied for the versions to be released and for all future versions. Versions already released remain unaffected by the changes. Versions of types not used in the project may be deleted. See also Release versions (Page 365) Updating the project to the latest versions After you have updated several types in the project library, update all instances in the project to the most recent version of the types from the project library. If you do not want to apply the changes to the entire project, restrict the update to individual devices in the project. Each of the following elements can be selected as source for the update: The entire project library Individual folders within the project library Individual types You can select multiple types. Requirement Your are in the "Libraries" task card or in the library view. Procedure To update instances in a project with the contents from the project library, follow these steps: 1. Select the entire project library or elements from it. 2. Right-click the required elements and select the "Update > Project" command from the shortcut menu. The "Update project" dialog box opens. 3. Select either the entire project or individual devices for the update. 4. Select the options for the update process: - The "Update all instances of the affected types" check box is always selected during this process. - Select the "Delete all unused versions of affected types" check box to delete all older versions of the updated types from the project library. 5. Click "OK" to confirm. The update is performed. 368 WinCC Basic V13.0 System Manual, 02/2014 Editing projects 7.10 Using libraries Result The following changes were made to the project: All older versions were deleted from the project library as needed. All instances within the selected devices were updated to the most recent version of the linked types. You can find a log of the update process in the projection tree under "Common data". See also Updating the project to the latest type versions (Page 372) Using logs (Page 241) Updating a library with the contents of another library (Page 377) Basics on types (Page 354) Library basics (Page 325) State of type versions (Page 356) Remove the link between instance and type Instances of types are always connected to the version of the corresponding types. They cannot be edited like an ordinary object. If you edit the instance, a new version of the type is created automatically in the library and the changes therefore affect the entire project. If you remove the link between the instance and its type, you then edit the object like an ordinary object in the project tree. Requirement The instance may not be "in test". Procedure To remove the link between instances and their type versions, follow these steps: 1. Select one or more instances in the project tree. 2. Right-click the selection and select the "Terminate connection to type" command from the shortcut menu. 3. The link to the corresponding type versions is removed. See also Basics on types (Page 354) Library basics (Page 325) State of type versions (Page 356) WinCC Basic V13.0 System Manual, 02/2014 369 Editing projects 7.10 Using libraries 7.10.8.6 Working with types in global libraries Adding types to a global library Global libraries are used as a central resource when working on multiple projects. Among the types, only the types in the project library can be edited directly. Therefore, use the project library if you want to work on types. When you are finished editing a type in the project library, you can add the type to a global library. Adding types from the project library corresponds to a normal copy process from the project library. Requirement The "Libraries" task card is displayed or the library view is open. The global library to which you want to add types is opened and can be written to. Procedure To add types to a global library, follow these steps: 1. Open the required folder in the global library in the "Libraries" task card or in the library view. 2. Drag one or more types from the project library to the "Types" folder or any subfolder of the global library. Alternative: 1. Copy the required types from the project library to the clipboard. 2. Open the required global library in the "Global library" palette of the "Libraries" task card. 3. Right-click the "Types" folder or any of its subfolders. 4. Select the "Paste" command in the shortcut menu. Result The types are inserted in the global library. Dependent types, such as types of HMI user data types or tags, are also copied to the global library, provided they do not already exist there. This ensures that all necessary elements for generating an instance are present in the global library. If a type already exists in the global library, the described action corresponds to an update of the global library. In this case, the most recent released versions of the types are added to the global library. See also Basics on types (Page 354) Release versions (Page 365) Assigning a version (Page 373) 370 WinCC Basic V13.0 System Manual, 02/2014 Editing projects 7.10 Using libraries Updating the project to the latest type versions (Page 372) Library basics (Page 325) Using types To use the version of a type from the global library, create an instance of the version at a suitable location in the project tree. You can also position faceplates and HMI user data types directly in the editor. In the project, instances of types from a global library are not linked to the type in the global library. Instead, a copy of the type and its dependent elements is generated in the project library when an instance is pasted into the project. Dependent elements, for example, can be PLC data types that are referenced in a block. In each case, the copy of the type and the dependent elements in the project library contain the version that you link to the instance. If the type or a dependent element already exists in the project library, only the missing version is added when necessary to the type in the project library. The instance is linked to the type in the project library. You can only assign a type to a device once irrespective of the version. Requirement The "Libraries" task card is displayed. A device which supports the sort of desired type is available in the project. The device is not assigned to any further instances of the same type. Procedure To generate and use an instance from a type, follow these steps: 1. In the global library, navigate to the version of the type that you want to use. 2. Drag the required version of the type and drop it at the location where you want to use it. Alternative: To automatically use the most recent version, drag the type to the location where you want to use it. Result Missing elements are added to the project library. An instance is generated from the type and its dependent elements and pasted at the location where you want to use it. The instances are connected to the respective version of the type in the project library. See also Basics on types (Page 354) Updating the project to the latest type versions (Page 372) Library basics (Page 325) Using the element view (Page 329) WinCC Basic V13.0 System Manual, 02/2014 371 Editing projects 7.10 Using libraries Updating the project to the latest type versions In large enterprises with numerous automation projects. the global libraries are frequently edited from a central location. The updated global libraries of the individual projects are made available after the completion of a new version. If you have received a more recent version of a global library, replace the outdated instances in your project with the most recent version. If you do not want to apply the changes to the entire project, restrict the update to individual devices in the project. The project library is also updated with the new versions of the types in the global library during the updating of the project or individual devices. The following elements can be selected as source for the updating: A global library Individual folders within a global library Individual types You can select multiple types. Requirement Your are in the "Libraries" task card or in the library view. The updated global library is open. Procedure To update instances in a project with the contents from a global library, follow these steps: 1. Select the updated global library or the individual elements from it. 2. Right-click the global library or the required elements and select the "Update > Project" command from the shortcut menu. The "Update project" dialog box opens. 3. Select either the entire project or individual devices for the update. 4. Select the options for the update process: - The "Update all instances of the affected types" check box is always selected during this process. - Select the "Delete all unused versions of affected types" check box to delete all older versions of the updated types from the project library. 5. Click "OK" to confirm. The update is performed. 372 WinCC Basic V13.0 System Manual, 02/2014 Editing projects 7.10 Using libraries Result The following changes were made to the project: The most recent version of the select types is present in the project library. All older versions were deleted if necessary. All instances within the selected devices were updated to the most recent version of the linked types. You can find a log of the update process in the projection tree under "Common data". See also Updating the project to the latest versions (Page 368) Using logs (Page 241) Updating a library with the contents of another library (Page 377) Basics on types (Page 354) Library basics (Page 325) Adding types to a global library (Page 370) 7.10.8.7 Assigning a version A library is more clearly structured if types related by content have the same version number. The identical version number reflects the work progress. When you have completed the work on multiple associated types, you can assign the same version number to these types. You have the following options to assign a common version to types: The entire project library or a complete global library One or more folders in a library One or more types Requirement The "Libraries" task card or the library view is open. Your selection must not contain types with "in test" or "in progress" status. Procedure To assign several types the same version, follow these steps: 1. Select the types to which you want to assign a common version. 2. Select the "Assign version" command from the shortcut menu. The "Assign version" dialog box opens. WinCC Basic V13.0 System Manual, 02/2014 373 Editing projects 7.10 Using libraries 3. If necessary, change the properties of the version: - In the "Version" field, determine the new version number. The version number must be higher than the highest version number of all selected types. - In the "Author" field, enter the person responsible for the version to be released. - In the "Comment" field, enter a comment on the version to be released. 4. If you have started the operation within the project library, select the options for the release. The following options cannot be selected in a global library. - Select the "Update all instances" check box to update all instances in the project to the new version. Types used in master copies are not updated. - Select the "Delete all unused versions from the library" check box to delete all older versions of the types from the project library. The versions are only deleted if they are not assigned to an instance in the project and if they have no dependencies to other types. 5. Click "OK" to confirm. Result The selected type versions are changed as follows: A new version of all selected types is created with the specified version number. The properties are applied to all selected types, the new version and to all future versions. Lower versions remain unaffected by the changes. If you make no changes to the properties, the properties of the last released version of each type are applied. If needed, all instances are updated to the most recent version and the unused versions of all types are deleted from the project library. The build number of dependent types is incremented to the next free build number as long as the dependent types were not in your selection. If you had selected a dependent type as well, the version number you specified will be assigned. A log of the changes is created. If you have versioned the types in the project library, you find the log in the project tree under "Common data > Logs". If you have versioned types in a global library, you find the log in the "Common data > Logs" folder in the level below the global library. See also Basics on types (Page 354) State of type versions (Page 356) Library basics (Page 325) Release versions (Page 365) Adding types to a global library (Page 370) Using logs (Page 241) Displaying logs of global libraries (Page 343) 374 WinCC Basic V13.0 System Manual, 02/2014 Editing projects 7.10 Using libraries 7.10.9 Editing library elements Types, master copies and folder can be cut, copied, pasted, moved, renamed or deleted in the usual way within the "Libraries" task card or the library view. Global libraries must be opened with write permission for each of the above-described processes. Note User help for types and master copies User help is not affected by any of the operations within the library. When you move a master copy or a type to a different location, you are also moving the associated user help in the file system to the corresponding location. Additional help on using the user help can be found in the chapter "Conventions for creating user help". Copying types The following rules apply when you copy types to the clipboard: Types are always copied to the clipboard with all associated versions. However, only versions that have previously been released are copied. Types are always copied to the clipboard with all dependent elements. Master copies are always copied to the clipboard with all type versions used in them. Copying and pasting type versions When you copy type versions to another library, the types must already exist in the target library. Cutting elements You can only paste previously cut library elements into the same library. In so doing, you can only paste master copies into the "Master copies" folder or any of its subfolders. Likewise, you can only paste types into the "Types" folder or any of its subfolders. Pasting types Pasting types in a different library corresponds to updating the target library. The following rules apply when you have pasted a type into a different library: A type is always pasted with all its versions. If the type already exists in the target library, all versions that are more recent than the existing versions are added to the corresponding types in the target library. If there is already a version with released status in the target library, this version is not pasted again. WinCC Basic V13.0 System Manual, 02/2014 375 Editing projects 7.10 Using libraries If the same version exists with in test or in progress status in the target library, it is replaced by the released version. If a type needs other types, these are also added at the respective location. Pasting master copies When you paste master copies, all type versions contained in these copies are also pasted. If the corresponding types already exist in the library, only the missing versions are added to the individual types. If one of the types used does not yet exist, it is pasted at the highest level in the library. The type includes the type version that was used in the master copy. Moving elements When you move an element from one library to another, the element is copied and not moved. The same rules apply as described under "Pasting types" and "Pasting master copies". Deleting of types and type versions Note the following when you delete types or type versions: A type or a type version can only be deleted if there are no dependencies to other types. When you delete a type, all versions of the type are deleted. If you delete all versions of a type, the type is also deleted. If you delete a version that has instances in the project, the instances are also deleted from the project. If you delete a type that is also stored at the same time as a master copy, the master copy is also deleted. Deleting instances If you delete an instance that has dependencies to other instances, this instance is restored during the next compilation. The instance is then linked again to the original type version. This restores the consistency of the project. See also Library basics (Page 325) Remove the link between instance and type (Page 369) Updating a library with the contents of another library (Page 377) 376 WinCC Basic V13.0 System Manual, 02/2014 Editing projects 7.10 Using libraries 7.10.10 Updating a library with the contents of another library An existing library can be updated with the contents of another library. The following options are available for updating libraries: Updating a global library with types from another global library or from the project library Updating the project library with types from a global library Each of the following elements can be selected as source for the update: An entire library Individual folders within a library Individual types You can select multiple types. During the update, new versions are added to the types that already exist in the target library. Types that do not yet exist in the target library are copied together with all their versions to the target library. Note User help for copying types User help is not copied together with a type to another library. You need to copy the user help for types to the corresponding directory. Additional help on using the user help can be found in the chapter "Conventions for creating user help". Requirement If you want to update a global library, you have to open it with write permission. Procedure To update a library with the contents of a different library, follow these steps: 1. Select a library or individual elements from a library as source for the update. 2. Right-click the source and select the "Update > Library" command from the shortcut menu. The "Update library" dialog box opens. 3. Select the type of library you want to update: - Select "Update the project library" to update the project library with types from a global library. - Select "Update a global library" if you want to update a global library. 4. Optional: In the drop-down list, select the global library that you want to update, if you want to update a global library. WinCC Basic V13.0 System Manual, 02/2014 377 Editing projects 7.10 Using libraries 5. Select the options for the update: - The "Update all instances of the affected types" option is always disabled during this process. - Select the "Delete all unused versions of the affected types" check box to delete all older versions of types from the project library if these are not assigned to any instance in the project and if there are no dependencies to other types. This option cannot be selected for the update of a global library, since types of a global library never have a point of use in the project. 6. Click "OK" to confirm. The update is performed. Result The following changes were made to the target library: Types not yet available in the target library were copied together with all their versions. More recent versions were added to the types that already exist in the target library. If a more recent version of a type already existed in the target library, the latest version was nevertheless copied and automatically assigned a newer version number. If needed, all versions of types were deleted from the project library if these were not used in any instance in the project. A log listing all performed changes to the target library was created for the update process. If you have updated the project library, you can find the log in the project tree under "Common data > Logs". If you have updated a global library, you can find the log in the "Common data > Logs" folder in the level below the global library. See also Using logs (Page 241) Updating the project to the latest versions (Page 368) Updating the project to the latest type versions (Page 372) Displaying logs of global libraries (Page 343) Library basics (Page 325) 378 WinCC Basic V13.0 System Manual, 02/2014 Editing projects 7.10 Using libraries 7.10.11 Harmonizing names and path structure You can harmonize the project with a library. This helps you correct the following items: Names of the instances: Instances can be created during the development phase of a library, the names of which are appended by "_1", "_2", etc. due to an automatic correction. This extension is used to prevent duplicate names in the project. During harmonization, the instances once again receive the names of their associated types. Path structure: The original path structure can be lost due to parallel development or copying of dependent instances. This affects the clarity of the project. During harmonization, the path structure within the project is adapted to the path structure of the library. Procedure To harmonize the names and the path structure, follow these steps: 1. Open the library management. 2. Click "Harmonize project" in the toolbar. The "Harmonize project" dialog box opens. 3. Select the device with which you wish to harmonize the library. 4. Select the "Harmonize paths between project and library" check box if you want to restore the path structure. 5. Select the "Harmonize names between project and library" check box if you want to have the names corrected. 6. Confirm your entries with "OK". Result Depending on your settings, the names and the path structure in the project are harmonized with the library. The changes to the project are logged. The log is available under "Common data > Logs" in the project navigation. See also Library basics (Page 325) Overview of the library view (Page 330) Overview of the library management (Page 333) Using logs (Page 241) WinCC Basic V13.0 System Manual, 02/2014 379 Editing projects 7.10 Using libraries 7.10.12 Clean up library You can clean up the project library or global libraries to remove types or versions that are not connected to any instance in the project. This step provides more clarity within the libraries and decreases the size of the library. Cleaning up the project library To clean up the project library, follow these steps: 1. Open the library management. 2. Click on "Clean up library" in the toolbar. The "Clean up project library" dialog box opens. 3. Select the scope in which types or versions are to be deleted: - to retain the version with the highest version number, even if this has no instance, select the option "Delete old type versions and retain the newest type version". - Select the option "Delete complete types" to delete the complete type if no version is connected to an instance. 4. Confirm your entry with "OK". Depending on your selection, either unused type versions or types are removed from the project library. The changes are logged. The log is available under "Common data > Logs" in the project navigation. Clean up global library To clean up a global library, follow these steps: 1. Open the library management. 2. Click on "Clean up library" in the toolbar. The "Clean up global library" dialog box opens. 3. Click "Continue". Unused type versions are deleted. The latest version of a type is always retained. The changes are logged. The log is available in the "Common data > Logs" folder in the level below the global library. See also Library basics (Page 325) Overview of the library view (Page 330) Overview of the library management (Page 333) Using logs (Page 241) Displaying logs of global libraries (Page 343) 380 WinCC Basic V13.0 System Manual, 02/2014 Editing projects 7.10 Using libraries 7.10.13 Comparing library elements Introduction You can compare devices from libraries with devices from both the current project as well as from the same or another libraries or reference projects. Note, however, that reference projects are write-protected. You can also compare instances in a device with their type version in a library. Not all actions are available for the comparison with types. You cannot, for example, overwrite an instance of a newer version with an older type version from the library. When comparing library elements, you can always switch between automatic and manual comparison. Procedure To compare library elements with the device data of a project, follow these steps: 1. In the project tree, select the device whose data you want to compare to a library element and which allows offline/offline comparison. 2. Select the "Compare > Offline/offline" command in the shortcut menu. The compare editor opens and the selected device is displayed in the left area. 3. Open the "Libraries" task card. 4. Select the library element that you want to compare to the device data. 5. Drag the library element into the right drop area of the compare editor. You can identify the status of the objects based on the symbols in the status and action area. When you select an object, the object properties and the corresponding object of the assigned device are clearly shown in the property comparison. You can drag other devices into the drop areas from the current project, a library or from a reference point at any time to start a new comparison. It does not matter which device you drag into the drop area. See also Using the compare editor (Page 275) Carrying out offline/offline comparisons (Page 274) Using the library view (Page 330) Library basics (Page 325) Overview of the "Libraries" task card (Page 327) Overview of the library view (Page 330) Using the element view (Page 329) Using global libraries (Page 338) WinCC Basic V13.0 System Manual, 02/2014 381 Editing projects 7.12 Simulating devices 7.11 Using cross-references 7.11.1 Using cross-references Introduction to cross-references The cross-reference list provides an overview of the use of objects within the project. You can see which objects are interdependent and where the individual objects are located. Crossreferences are therefore part of the project documentation. You can also jump directly to the point of use of an object. Which objects you can display and localize in the cross-reference list depends on the installed products. See also Displaying cross references of an instance (Page 337) 7.12 Simulating devices 7.12.1 Simulation of devices Introduction You can use the TIA Portal to run and test the hardware and software of the project in a simulated environment. The simulation is performed directly on the programming device or PC. No additional hardware is required. The simulation software provides a graphical user interface for monitoring and changing the configuration. It differs according to the currently selected device. Integration in the TIA Portal The simulation software is fully integrated in the TIA Portal but is only supported by certain devices. Therefore, the button for calling the simulation software is only active if the selected device supports simulation. The simulation software for some devices requires its own virtual interface to communicate with the simulated devices. The virtual interface can be found in the project tree under the "Online access" entry next to the physical interfaces of the programming device/PC. Once you have opened the software, additional help on the simulation software is available via a separate link. 382 WinCC Basic V13.0 System Manual, 02/2014 Editing projects 7.12 Simulating devices See also Starting the simulation (Page 383) 7.12.2 Starting the simulation Some devices can be simulated with additional software. You therefore do not have to have the actual devices to perform comprehensive testing of your project. Procedure To start the simulation software, follow these steps: 1. Select the device you want to simulate, for example, in the project tree. 2. Select the "Simulation > Start" command in the "Online" menu. This calls the simulation software. See also Simulation of devices (Page 382) WinCC Basic V13.0 System Manual, 02/2014 383 Editing devices and networks 8.1 Configuring devices and networks 8.1.1 Hardware and network editor 8.1.1.1 Overview of hardware and network editor 8 Function of the hardware and network editor The hardware and network editor opens when you double-click on the "Devices and Networks" entry in the project tree. The hardware and network editor is the integrated development environment for configuring, networking and assigning parameters to devices and modules. It provides maximum support for the realization of the automation project. WinCC Basic V13.0 System Manual, 02/2014 385 Editing devices and networks 8.1 Configuring devices and networks Structure of the hardware and network editor The hardware and network editor consists of the following components: Device view (Page 389), Network view (Page 387), Topology view (Page 392): Graphic area Device view (Page 389), Network view (Page 387), Topology view (Page 392): Table area Hardware catalog (Page 398) Inspector window (Page 397) 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. Drag the devices and modules you need for your automation system from the hardware catalog to the network, device ot topology view. The inspector window contains information on the object currently marked. Here you can change the settings for the object marked. 386 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks 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: Changeover switch: device view / network view / topology view Toolbar of network view Graphic area of network view Overview navigation Table area of network view You can use your mouse to change the spacing between the graphic and table areas of the network view. To do this, click between the graphic and the table areas and change the spacing by moving the divider to the left or right while keeping the mouse button pressed. The Speedy Splitter (the two small arrow keys) allows you to use a single click to minimize the table view, maximize the table view or restore the last selected split. WinCC Basic V13.0 System Manual, 02/2014 387 Editing devices and networks 8.1 Configuring devices and networks Toolbar The toolbar provides the following functions: Icon Meaning Mode to network devices. Mode to create connections. You can use the adjacent drop-down list to set the connection type. Mode to create relations. Show interface addresses. Adjust the zoom setting. You can use the adjacent drop-down list to select or directly enter the zoom setting. You can also zoom in or zoom out the view in steps using the zoom symbol or draw a frame around an area to be zoomed in. Show page breaks Enables page break preview. Dotted lines are displayed at the positions where the pages break when printed. Remember layout Saves the current table view. The layout, width and visibility of columns in the table view is stored. Graphic area The graphic area of the network view displays any network-related devices, networks, connections and relations. In this area, you add devices from the hardware catalog, connect them with each other via their interfaces and configure the communication settings. Overview navigation Click in the overview navigation to obtain an overview of the created objects in the graphic area. By holding down the mouse button, you can quickly navigate to the desired objects and display them in the graphic area. Table area The table area of the network view includes various tables for the devices, connections and communication settings present: Network overview Connections Relations I/O communication VPN You can use the shortcut menu of the title bar of the table to adjust the tabular display. 388 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks See also Adding a device to the hardware configuration (Page 415) Layout of the user interface (Page 187) Displaying diagnostics status and comparison status using icons (Page 1087) Networking devices in the network view (Page 430) Tabular network overview (Page 433) 8.1.1.3 Device view Introduction The device view is one of three working areas of the hardware and network editor. You undertake the following tasks here: Configuring and assign device parameters Configuring and assign module parameters WinCC Basic V13.0 System Manual, 02/2014 389 Editing devices and networks 8.1 Configuring devices and networks Structure The following diagram shows the components of the device view: Changeover switch: device view / network view / topology view Toolbar of device view Graphic area of the device view Overview navigation Table area of device view You can use your mouse to change the spacing between the graphic and table areas of the device view. To do this, click between the graphic and the table areas and change the spacing by moving the divider to the left or right while keeping the mouse button pressed. The Speedy Splitter (the two small arrow keys) allows you to use a single click to minimize the table view, maximize the table view or restore the last selected split. Toolbar The toolbar provides the following functions: Icon Meaning Switches to the network view. Note: The device view can switch between the existing devices using the drop-down list. Show the area of unplugged modules. Show module labels. 390 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Icon Meaning Adjust the zoom setting. You can use the adjacent drop-down list to select or directly enter the zoom setting. You can use the Zoom icon to zoom in or out incrementally or to drag a frame around an area to be enlarged. With signal modules, you can recognize the address labels from a zoom level of 200% or higher. Show page breaks Enables page break preview. Dotted lines are displayed at the positions where the pages break when printed. Remember layout Saves the current table view. The layout, width and visibility of columns in the table view is stored. Graphic area The graphic area of the device view displays hardware components and if necessary the associated modules that are assigned to each other via one or more racks. In the case of devices with racks, you have the option of installing additional hardware objects from the hardware catalog into the slots on the racks. Overview navigation Click in the overview navigation to obtain an overview of the created objects in the graphic area. By holding down the mouse button, you can quickly navigate to the desired objects and display them in the graphic area. Table area The table area of the device view gives you an overview of the modules used and the most important technical and organizational data. You can use the shortcut menu of the title bar of the table to adjust the tabular display. See also Working with racks (Page 408) Network view (Page 387) Area for unplugged modules (Page 412) Inserting a module into a rack (Page 417) Objects in the device view (Page 410) Layout of the user interface (Page 187) Displaying diagnostics status and comparison status using icons (Page 1087) WinCC Basic V13.0 System Manual, 02/2014 391 Editing devices and networks 8.1 Configuring devices and networks 8.1.1.4 Topology view Introduction The topology view is one of three working areas of the hardware and network editor. You undertake the following tasks here: Displaying the Ethernet topology Configuring the Ethernet topology Identifying and minimizing differences between the desired and actual topology Structure The following figure provides an overview of the topology view. Changeover switch: device view / network view / topology view Topology view toolbar Graphic area of the topology view Overview navigation Table area of the topology view You can use your mouse to change the spacing between the graphic and table areas of the topology view. To do this, click between the graphic and the table areas and change the spacing by moving the divider to the left or right while keeping the mouse button pressed. The Speedy Splitter (the two small arrow keys) allows you to use a single click to minimize the table view, maximize the table view or restore the last selected split. 392 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Toolbar The toolbar provides the following functions: Icon Meaning Adjusting the zoom setting. You can use the adjacent drop-down list to select or directly enter the zoom setting. You can also zoom in or zoom out the view in steps using the zoom symbol or draw a frame around an area to be zoomed in. Show page breaks Enables page break preview. Dotted lines are displayed at the positions where the pages break when printed. Remember layout Saves the current table view. The layout, width and visibility of columns in the table view is stored. Graphic area The graphic area of the topology view displays Ethernet modules with their appropriate ports and port interconnections. Here you can add additional hardware objects with Ethernet interfaces. See: Adding a device to the hardware configuration (Page 415) Overview navigation Click in the overview navigation to obtain an overview of the created objects in the graphic area. By holding down the mouse button, you can quickly navigate to the desired objects and display them in the graphic area. Table area This displays the Ethernet or PROFINET modules with their appropriate ports and port interconnections in a table. This table corresponds to the network overview table in the network view. You can use the shortcut menu of the title bar of the table to adjust the tabular display. See also Layout of the user interface (Page 187) Displaying diagnostics status and comparison status using icons (Page 1087) 8.1.1.5 Overview of settings for hardware configuration You can make some settings for the hardware configuration in the settings of the TIA Portal. Overview The following table provides an overview of the settings for the hardware configuration: WinCC Basic V13.0 System Manual, 02/2014 393 Editing devices and networks 8.1 Configuring devices and networks Group Setting Description Information on product support Deactivated Prevents access to the Siemens Industry Online Support Via Internet Enables access to product information about individual devices in the hardware catalog via the Internet. Topological overview Temporarily assigning an IP address Assigns a temporary IP address for topology discovery if a device does not have a valid IP address. Topology information (LLDP) cannot be read from a device without valid IP address. Show a warning if the option is activated Shows a warning when a temporary IP address is assigned to a device during topology discovery. Download module comment Transfers any existing comments in addition to the hardware configuration when loading the hardware configuration to the device. The comment is available after the device is loaded to a programming device. Compiling See also Changing the settings (Page 186) 8.1.1.6 Printing hardware and network configurations Printout of hardware and network configurations You can print out the following elements of the hardware and network view as part of the project documentation: Graphic network view Network overview table Graphic device view The device overview table The parameters of the object currently selected in the editor Printout of editor content If you start a printout within an opened editor and no module is selected, the content of the editor is always printed. This includes a graphic representation of the editor as well as the table for the editor. You can adapt the scope of the printout. You can specify whether only the graphic view, the table or both together are to be printed. Read section "Changing the print options (Page 396)" for more on this. If the graphic is larger than the page layout you have selected, the printout is continued on the next page. No content is lost this way. Alternatively, you can change the zoom level of the graphic representation to fit the printout on one page. The printout is always made in the currently selected zoom setting. 394 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks To check that all content fits on one page, you can either use the print preview or activate the page break preview. When page break preview is activated, dashed lines are displayed within the graphic editor at the location where the page break is later made. Printing very large tables If a table is larger than the print area and therefore cannot be fully printed, the content of the table is not printed as a table, but instead as pairs between value and key. Example: Object name Property 1 Property 2 Object A Value A1 Value A2 Object B Value B1 Value B2 In this case, the printout has the following appearance: Object A Property 1: Value A1 Property 2: Value A2 Object B Property 1: Value B1 Property 2: Value B2 You can also preset this as a template so that tables are always printed as pairs between the key and the value. Read section "Changing the print settings (Page 292)" for more on this. Printing module parameters Parameters of selected modules are printed out along with the current value settings in text form. All parameters from corresponding modules are also printed. For example, if you have selected a CPU, the parameters of an inserted signal board, if present, are printed as well. You can determine the scope of the module parameters to be printed. In the "Print" dialog, select whether all properties and parameters of a module are to be printed or whether to use the compact printout. If you select the compact form, only the entries in the "General" area of the module properties are printed. Comments on modules, as well as the author and module description, are excluded. In compact mode, the following module parameters are therefore printed, for example: Module specifications Name, module slot, short description, order number, firmware version Name of the PROFINET interface Subnet specifications Name of the subnet, ID of the S7 subnet WinCC Basic V13.0 System Manual, 02/2014 395 Editing devices and networks 8.1 Configuring devices and networks See also Changing the print options (Page 396) Documentation settings (Page 290) Creating a print preview (Page 304) Printing project data (Page 307) Activating the page break preview for printout (Page 396) 8.1.1.7 Activating the page break preview for printout You can activate the page break preview for the printout in the graphic editor. If this option is activated, dashed lines are shown within the graphic editor at the locations where page breaks are later made during printout. Procedure Proceed as follows to activate the page break preview: 1. Select the graphic area of the corresponding view. 2. Click on the "Show page break" symbol in the toolbar of the graphic editor. Dashed lines are displayed within the graphic editor at the location a page break is later made. 3. To modify the frame layout, select the "Print" command in the "Project" menu. 4. To disable page break preview, click again on the "Show page break" symbol in the toolbar of the graphic editor. 8.1.1.8 Changing the print options Changing the scope of the printout When printing from an editor, you can specify whether both graphics and tables are to be printed or just one of the two. Both are printed by default. Procedure To change the scope of the printout, proceed as follows: 1. In the "Options" menu, select the "Settings" command. 2. In the area navigation, open the "Print settings" parameter group under "General". 3. Scroll to the "Hardware configuration" group. 4. Select or clear the "Active graphic view" check box, depending on whether you want to print the graphics of the network and device view as well. 5. Select or clear the "Active table" check box, depending on whether you want to print the table for the editor as well. 396 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks See also Printing hardware and network configurations (Page 394) 8.1.1.9 Inspector window The properties and parameters shown for the object selected can be edited in the Inspector window. Structure The Inspector window consists of the following components: Switch between various information and work areas Switch between various tabs of the information and work areas Navigation between various pieces of information and parameters Display showing the selected information and parameters Function The information and parameters in the Inspector window are split into different types of information: Properties Info Diagnostics WinCC Basic V13.0 System Manual, 02/2014 397 Editing devices and networks 8.1 Configuring devices and networks To display the corresponding information and parameters, click in the relevant area. The "Properties" area is the most important one for configuring an automation system. This area is displayed by default and contains various tabs: General: Display the properties and settings of the device or module. Here you can edit the settings and parameters. The left pane of the Inspector window is used for area navigation. Information and parameters are arranged there in groups. If you click on the arrow symbol to the left of the group name, you can expand the group if sub-groups are available. If you select a group or sub-group, the corresponding information and parameters are displayed in the right pane of the Inspector window and can be edited there too. IO tags: Display the IO tags of the PLC. You can assign names for the tags, assign the tags to the user-defined tag tables via a drop-down list, and enter comments for the tags. The IO tags are also shown in the PLC tag table. System constants: Display the constants required by the system with the HW IDs of the modules. The system constants are also shown in the PLC tag table. Texts: Display the reference language and specify the text source for the project texts. See also Editing properties and parameters (Page 423) Overview of hardware and network editor (Page 385) Translating text associated with individual objects (Page 254) Project text basics (Page 250) Addressing modules (Page 665) 8.1.1.10 Hardware catalog The "Hardware catalog" task card gives you easy access to a wide range of hardware components. 398 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Structure The "Hardware catalog" task card consists of the following panes: "Catalog" pane, search and filter function "Catalog" pane, component selection "Information" pane Search and filter function The search and filter functions of the "Catalog" pane make it easy to search for particular hardware components. You can limit the display of the hardware components to certain criteria using the filter function. For example, you can limit the display to objects that you can also place within the current context or which contain certain functions. Objects that can be used in the current context include, for example, interconnectable objects in the network view or only modules compatible with the device in the device view. WinCC Basic V13.0 System Manual, 02/2014 399 Editing devices and networks 8.1 Configuring devices and networks Component selection The component selection in the "Catalog" pane contains the installed hardware components in a tree structure. You can move the devices or modules you want from the catalog to the graphic work area of the device or network view. Installed hardware components without a license are grayed out. You cannot use non-licensed hardware components. Hardware components belonging to various components groups thematically are partially implemented as linked objects. When you click on such linked hardware components, a catalog tree opens in which you can find the appropriate hardware components. Information The "Information" pane contains detailed information on the object selected from the catalog: Schematic representation Name Order number Version number Description See also Browsing the hardware catalog (Page 407) Overview of hardware and network editor (Page 385) 8.1.1.11 Enabling product support For each device in the hardware catalog, you have the option of displaying additional information that is stored in the Siemens Industry Online Support. By default, the function is disabled. Instructions for enabling the function are given below. Requirement The TIA Portal has access to the Internet. Procedure To enable access to Siemens Industry Online Support, follow these steps: 1. In the "Options" menu, select the "Settings" command. 2. Open the "Hardware configuration" group in the area navigation. 3. Select the "Via Internet" check box. 400 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Result You can access product support, FAQs and manuals in the hardware catalog via the shortcut menu for the module. See also Displaying product support for hardware components (Page 401) 8.1.1.12 Displaying product support for hardware components In the hardware catalog, you have direct access to information that is stored for each module in Siemens Industry Online Support. You can jump directly to the following pages in Siemens Industry Online Support: Information on product support FAQs Manuals Requirement You have access to the Internet. Access to product support is enabled in the settings of the TIA Portal. For information on how to enable the function, refer to section "Enabling product support (Page 400)". Procedure To display the information for a particular module in Siemens Industry Online Support, follow these steps: 1. Navigate to the required module in the hardware catalog. 2. Right-click the module. 3. Select one of the following entries in the shortcut menu: - Information on product support - FAQs - Manuals Result The default browser set in the operating system is opened and the relevant page in the Siemens Industry Online Support is loaded. See also Enabling product support (Page 400) WinCC Basic V13.0 System Manual, 02/2014 401 Editing devices and networks 8.1 Configuring devices and networks 8.1.1.13 Keyboard operation: Navigation in the editor You can use shortcut keys in the network and device view to navigate between the components of the hardware and network editor and its objects. Navigating between elements and functions Function Shortcut keys Switch to the next lower selection level <Return> You can for example, use <Return> to switch from a selected rack to the lower selection level of the devices and modules that are snapped onto it. If a device is selected, you can use <Return> to switch to the lower selection level of the interfaces that are displayed on the device. Switch to the next higher selection level <Esc> You can use <Esc>, for example, to switch from a selected interface to the higher selection level of the devices and modules. If a device is selected, you can use <Esc> to switch to the higher selection level of the rack. Navigation between objects in the current selection level <Up arrow> You can use the arrow keys to switch between the objects within a current selection level. To change the selection level, use the <Return> or <Esc> keys. <Down arrow> <Right arrow> <Left arrow> Switches to the device view <Ctrl+Shift+D> Switches to the network view <Ctrl+Shift+N> Switches to the topology view <Ctrl+Shift+T> Switch between editor elements <Tab> Use the <Tab> key to switch from one editor element to the next element. Use <Shift +Tab> to switch to the previous element. You can switch, for example, between the graphical view, Speedy Splitter, table view or underlying tabs. <Shift+Tab> Switch between tabs <Ctrl+Tab> Use the <Ctrl+Tab> keys to switch from one tab to the next tab on the right. Use <Ctrl <Ctrl+Shift+Tab> +Shift+Tab> to switch to the next tab to the left. You can use these keys, for example, to switch between the device view, the network view and the topology view. Opening elements and functions Function Shortcut keys Opening the online and diagnostics view <Ctrl+D> When a device is selected, <Ctrl+D> opens the online and diagnostics view for the selected device. Opening the download to device dialog <Ctrl+L> When a device is selected, <Ctrl+L> opens the advanced download dialog. Add new device <Ctrl+N> <Ctrl+N> opens the dialog for adding a new device. Opens the "Hardware catalog" task card <Ctrl+Shift+C> Opens "Online Tools" task card <Ctrl+Shift+O> 402 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks See also Keyboard operation in the TIA Portal (Page 218) 8.1.1.14 Keyboard operation: Editing objects You can execute some of the functions of the network and device view directly with a combination of keyboard and mouse in the hardware and network editor. The keyboard operation in tables (Page 218) corresponds to standard characteristics. Here you find the keyboard operation for the graphic work area of the network and device view. General keyboard operation Function Shortcut keys Zoom in on view in frame <Ctrl+Space> + pressed mouse button Drag a frame in the graphical view in order to correspondingly change the size of the view. Move view <Space> + pressed mouse button Move the mouse pointer in order to move the view. Cancel current operation <Esc> Separate connection <Esc> or double-click Use <Esc> or a double-click to exit connection mode when dragging a connection. Zoom in graphic view <Ctrl> + turn mouse wheel The enlargement or reduction depends on the direction of rotation. Selected objects Function Shortcut keys Select object Mouse click Cut an object <Ctrl+X> The selected object is copied to the clipboard and deleted from the graphical view. Copy object <Ctrl+C> The selected object is copied to the clipboard. Paste object <Ctrl+V> The object from the clipboard is inserted into the selection. Delete selected object <Del> Select several objects 1 <Shift> + click You can add several objects to the selected objects by clicking on them individually. Alternatively, you can use <Shift> + pressed mouse key to drag a frame around the objects that are to be selected. Select several objects 2 <Ctrl> + click You can add several objects to the selected objects by clicking on them individually. Alternatively, you can use <Shift> + pressed mouse key to drag a frame around the objects that are to be selected. When holding down the <Ctrl> key, you can use a mouse click to deselect selected objects. WinCC Basic V13.0 System Manual, 02/2014 403 Editing devices and networks 8.1 Configuring devices and networks Function Shortcut keys Move selection Mouse button pressed When the mouse button is pressed, you can drag devices or modules to allowed slots on a rack. Copy selection <Ctrl> + pressed mouse button Using <Ctrl> + pressed mouse button you can drag devices and modules to allowed slots on a rack. This copies the devices or modules. 8.1.2 Configuring devices 8.1.2.1 Basics Introduction to configuring hardware To set up an automation system, you will need to configure, assign parameters and interlink the individual hardware components. The work needed for this is undertaken in the device and network view. Configuring "Configuring" is understood to mean arranging, positioning, and networking devices and modules within the device or network view. Racks are represented symbolically. Just like "real" racks, they allow you to plug in a defined number of modules. An address is automatically assigned to each module. The addresses can be subsequently modified. When the automation system is started, the CPU compares the configuration that is preset by the software with the actual configuration of the system. Possible errors can be detected and reported straight away. Assigning parameters "Assigning parameters" is understood to mean the setting of properties of the components used. Parameter assignment is carried out for hardware components and for data exchange settings: Properties of modules with assignable parameters Settings for data exchange between components The parameters are loaded to the CPU and transferred to the corresponding modules when the CPU starts up. Modules can be replaced with ease since the assigned parameters are automatically loaded into the new module during startup. 404 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Adjusting the hardware to the project requirements You need to configure hardware if you want to set up, expand or change an automation project. To do this, add hardware components to your configuration, connect them to existing components, and adapt the hardware properties to the tasks. The properties of the automation systems and modules are preset in such a way that in many cases there is no need for additional parameter assignment. Parameter assignment is however needed in the following cases: You want to change the default parameter settings of a module. You want to use special functions. You want to configure communication connections. See also Changing properties of the modules (Page 970) Using existing configurations Open existing projects When opening existing projects, an automatic check is made to determine if the appropriate software is installed for all modules used within the project. If you try to open a project with modules that are not supported by the current scope of the installation of the TIA portal, a message appears on opening the project informing you of the missing software components. If the software components are not absolutely required to open the project, the project can still be opened. WinCC Basic V13.0 System Manual, 02/2014 405 Editing devices and networks 8.1 Configuring devices and networks Reaction to missing software components Projects that contain modules not supported by the current scope of the installation react as follows: Display the modules on the GUI - The non-supported modules are displayed in the project navigation with all of their nested objects. However, the modules themselves cannot be processed in editors or in inspector windows. When possible, a replacement module is used that best matches the original module. Replacement modules are indicated by an exclamation mark. - Display of properties in tables is limited. This applies in particular to the display of network parameters, such as the IP address. Functional limitations - Non-supported modules cannot be printed out or compiled. - An online connection cannot be established to the module. It is therefore also impossible to download. - To change the device type, the device must first be deleted and then re-inserted. The "Change device type" function is not supported. - Copying and inserting nested objects, such as modules, is possible although the device itself cannot be copied and inserted. - The network configuration cannot be changed with replacement modules within the network view. - Cross-references can be displayed. However, the cross-references only reflect the state last saved within the project because on online comparison to the original module cannot be made. See also Opening projects (Page 244) General slot rules Introduction Specific slot rules apply to each automation system and module. If you select a module from the hardware catalog in the device view, all possible slots for the module selected are marked in the rack. You can only drag modules to marked slots. If you insert, move or swap a module, the slot rules are also applied. Consistency Some slot rules depend on how the environment is configured. This means that you can sometimes plug modules into the rack although this would result in inconsistencies at the current time. If you change the configuration, for example by selecting different modules or module parameter settings, you can make the configuration consistent again. 406 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks In cases where inserting a module results in an inconsistency that can be corrected, this will be permitted. A consistency check is run when the configuration is compiled. Inconsistencies are displayed as alarms in the Inspector window under "Info". Based on the result of the consistency check, you can revise your configuration and make it consistent again. Rules for arranging modules The following rules apply generally to modules in racks: You can only plug modules into a rack. You can only plug interface modules into a module. You can only use modules of the same product or system family in one rack. There are also other special rules for some modules: Can only be inserted in certain slots Insertion depends on other modules, CPUs or settings Limited number of uses in a rack Browsing the hardware catalog Introduction Use the "Hardware catalog" task card to select the hardware components you want for a hardware configuration. Use the hardware catalog to select the interconnectable hardware components in the network and topology view and to select the modules you want in the device view. Context filter You can use the "Filter" option of the hardware catalog to restrict the number of displayed hardware components and the number of hardware components that can be found by searching. If you select the filter, only those components are displayed that can be selected currently in the hardware catalog. If the do not select the filter, the entire hardware catalog is displayed. If you switch between the various views, the view of the filter objects is adapted to the current context. Search options You can use the search function to search for specific entries in the hardware catalog. Note the following rules when entering search terms: No distinction is made between upper and lower case text. Dashes and blanks are ignored during the search. The search function considers parts of a search term. Several search terms must be separated by a space WinCC Basic V13.0 System Manual, 02/2014 407 Editing devices and networks 8.1 Configuring devices and networks You start the search from an object highlighted in the hardware catalog and either search upwards or downwards. Symbol Meaning Downwards search Upwards search Browsing the hardware catalog If you want to browse the hardware catalog, proceed as follows: 1. Click in the entry field of the search function 2. Enter a search term. The search includes the following elements: - Name of device or module - Order number (MLFB) - Description in "Information" pane 3. Click on either the "Downwards search" or "Upwards search" buttons. Note To ensure the right search direction, note which point you have marked in the hardware catalog. To browse the entire catalog, click on the topmost object of the hardware catalog and start the search once you have entered the search term by clicking "Downwards search". The first match with the search term found is displayed as the result. For more search results, again click on the "Downwards search" or "Upwards search" button. Observe the context filter of the hardware catalog. If this is selected, the search in the hardware catalog is restricted to the displayed inserted hardware components. See also Hardware catalog (Page 398) Working with racks Introduction To assign modules to a device, you need a rack, for example a mounting rail. Secure the modules on the rack and connect these via the backplane bus with the CPU, a power supply or other modules. 408 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Creating a rack If you insert a device in the network view, a station and a rack suitable for the device selected are created automatically. The rack and slots available are displayed in the device view. The number of slots available again depends on the type of device used. Rack structure A rack always contains the device that has been inserted in the network view. The device is permanently assigned a slot which will depend on the type of device in question. There are additional slots on the right of the device and, if necessary, on left of the device; slot numbers are located above slots in which devices are plugged. A corresponding short description is displayed above the plugged devices and modules. You show or hide this short description via the toolbar under "View" with the command "Display module titles" or the corresponding symbol in the toolbar of the device view (Page 389). Symbol Meaning Show module titles When modules are selected in the hardware catalog, all the slots permitted for this module are marked. This allows you to see immediately the slot into which the selected module can be inserted. In the following screenshot, a signal module has been selected in the hardware catalog for a partially filled S7-1200 rack: Since slots 101-103 are reserved for communications modules, only the other free slots are shown as available slots. You can expand and collapse the front group of slots using an arrow symbol above the expandable slot. When the group of slots is collapsed, the first and last of the group's slot numbers are displayed. The following figure shows the expanded slot group: WinCC Basic V13.0 System Manual, 02/2014 409 Editing devices and networks 8.1 Configuring devices and networks Groups of slots into which modules have already been plugged cannot be collapsed. Multiple selection of modules and slots There are various ways of selecting several modules or slots: By pressing <Shift> or <Ctrl>, you can select several modules or slots at the same time. Click outside the rack and then hold the mouse button and drag a frame to include the modules or slots you want to select. Objects in the device view A graphic display of the rack and the devices plugged into it is shown in the left area of the device view. You can see the device overview in the right area of the device view. The device overview is a table showing you the most important information about the modules inserted in the rack. Both areas are displayed in a window. The size of both areas is adjusted using a divider. You can also use it to display one or the other area in full or to hide them. Structure and content of device view The offline configuration of the devices in the rack are displayed in the graphic device view. This is a symbolic representation of the configuration on the real rack. The rack configuration is displayed as a table in the device view. Each line in the table contains the information for assigning a slot. The following screenshot shows the device view with the configuration of a SIMATIC S7-1200 CPU. 410 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Graphic view of the allocation of the rack by the CPU and various modules in slots 1 to 4, as well as 101 and 102. You can use the divider to adjust the proportion of the device view between the left area (graphic view) and the right area (device overview). If you click on the arrows, you can quickly switch the division of the separate areas. Device overview with a tabular representation of the slots of the rack and the plugged components. Each line in the device overview represents one slot. The key information for each slot is displayed in the various columns: WinCC Basic V13.0 System Manual, 02/2014 Column Meaning Module Name of module, can be edited in any way Slot Slot number I address Input address area, can be edited in any way Q address Output address area, can be edited in any way 411 Editing devices and networks 8.1 Configuring devices and networks Column Meaning Type Catalog name of module Order no. Module order number Firmware Firmware version of module Comments Optional comments See also Device view (Page 389) Area for unplugged modules In some cases, the modules for a hardware configuration are not assigned a slot for short periods. Such unplugged modules are moved to the area of unplugged modules, a special area in the device view. Adding modules to the storage area The modules that, for example, should be assigned to a device using a copy action but for which the corresponding rack does not have a free compatible slot, are moved automatically into the area of unplugged modules. Under the following conditions, modules are automatically added to the area of unplugged modules: In the network view, a module is moved to a device but the rack does not have a compatible free slot. In the device view, a module is moved or copied from the rack, the hardware catalog or the project tree straight into the storage area. CPs and FMs that occupy a network resource can be moved into the area of unplugged modules but will lose the network resources they have been assigned. You can add modules to the area of unplugged modules by means of drag-and-drop, for example. To do this, the area must be opened. Using the area of unplugged modules Use the corresponding button to open the area of unplugged modules. You can find the area of unplugged modules in the device view. You open the area of unplugged modules with the respective icon in the toolbar of the device view (Page 389). 412 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Icon Meaning Open area of unplugged modules Note To free up slots, move modules from your configuration into the storage area and plug the modules you want from the storage area into the freed up slots. You can use this approach to temporarily move modules whose parameters have already been assigned out of the configuration without deleting them. Treatment of modules in the storage area The following rules apply to modules in the storage area: The modules appear in the project tree under the corresponding device in the "Local modules" folder. The modules retain all settings and parameters previously assigned. The modules are not taken into account during loading to a target system. This means that a consistency check is not undertaken for modules in the area of unplugged modules. Using the context menu, the modules can be copied, cut, or deleted, for example. 8.1.2.2 Configuring individual devices Selecting a CPU Introduction Select a CPU from the hardware catalog and place it, together with a rack, in the network view. On this device drag the desired modules from the hardware catalog; they are arranged automatically on the rack. Selecting the components in the hardware catalog Each hardware component is displayed as a folder in the hardware catalog. When you open this folder you will see the different versions of the selected hardware component with its respective order numbers. There will be an example of how to set up a CPU with a rack in network view. Requirement The hardware catalog is open. You must be in the network view. WinCC Basic V13.0 System Manual, 02/2014 413 Editing devices and networks 8.1 Configuring devices and networks Procedure To select a CPU from the hardware catalog, proceed as follows: 1. In the hardware catalog navigate to the folder with the desired CPUs. 2. Open the folder with the desired CPU type; you will see all order numbers for the selected CPU type. 3. Click on a CPU order number to get information about the selected CPU under "Information" pane. 4. Set up the CPU and a rack. You have the following options: - Use drag-and-drop to drag the CPU from the hardware catalog into network view. - Use Copy & Paste to copy the CPU to the network view. - Double-click the CPU entry in the hardware catalog. See also Browsing the hardware catalog (Page 407) Adding a device to the hardware configuration (Page 415) Inserting a module into a rack (Page 417) Working with racks (Page 408) Creating an unspecified CPU (Page 416) 414 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Adding a device to the hardware configuration Introduction There are various ways of adding a connectable device from the hardware configuration in the network view and the topology view: Command "Add new device" in the project tree Double-click device in hardware catalog Drag-and-drop from the hardware catalog in network view or in topology view: - Text entry from the "Catalog" pane - Preview graphic from the "Information" pane "Add > Device" command from menu bar in network view or topology view Shortcut menu of a device in the hardware catalog for copying and pasting A suitable rack is created along with the new device. The selected device is inserted at the first permitted slot of the rack. Regardless of the method selected, the added device is visible in the project tree and the network view of the hardware and network editor. Adding device using the project tree To use the project tree to add a device to the hardware configuration, proceed as follows: 1. Click on the command "Add new device" in the project tree. The "Add new device" dialog box opens. 2. Display the required device in the tree structure: - Go to required device in the tree structure. - Enter a device name in the entry field. 3. Select the required device from the tree. More information about the device presently selected is displayed on the right-side of the dialog box. 4. If necessary, set the firmware version using the drop-down list in the dialog box. 5. Select the "Open device view" check box if you want to change to the device view immediately after adding the device. There you can immediately continue with device configuration and equipping the rack. 6. Click on "OK" to add the device selected. The dialog box closes. Adding device from the hardware catalog To add a device to the hardware configuration using the hardware catalog, proceed as follows: 1. Open the network view or the topology view. 2. Open the hardware catalog. WinCC Basic V13.0 System Manual, 02/2014 415 Editing devices and networks 8.1 Configuring devices and networks 3. Go to the required device in the hardware catalog. 4. Click on the chosen device to select it. 5. If necessary, set the firmware version using the drop-down list in the hardware catalog. 6. Drag the device to the network view or the topology view. You have now placed the device in the network view or in the topology view. The displayed rectangle (in other words "Station") symbolizes the plugged device together with its rack and any lower-level modules. Double-click on the device or station to open the device view and view the new rack and inserted device. In the next steps, you can configure the device in the device view and equip the rack with modules. See also Network view (Page 387) Creating an unspecified CPU (Page 416) Topology view (Page 392) Creating an unspecified CPU Introduction If you have not yet selected a CPU but have already started programming or want to use an existing program, you have the option of using an unspecified CPU. You can also adjust some settings with unspecified CPUs. The setting options are restricted to parameters that all CPUs of the same CPU family have in common. Creating an unspecified CPU in the portal view To create an unspecified CPU in the portal view, follow these steps: 1. Now, click one of the following options: - "Devices & networks > Add new device" - "PLC programming" > "Device" button 2. For a device family, select an unspecified CPU from the tree structure of the "Add new device" dialog. 3. Click on "Add". An unspecified CPU is created and the device view for this CPU appears. 416 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Further options for creating unspecified CPUs In the project view, you can create unspecified CPUs like specified CPUs: Using the "Add new device" button in the project tree In the "Hardware catalog" task card You can also use these methods to create multiple unspecified CPUs. Specifying unspecified CPUs You have two options for specifying unspecified CPUs: Use drag-and-drop to assign an existing CPU from the hardware catalog to an unspecified CPU by means of module replacement (Page 423). Select a selected, unspecified CPU and then the menu command "Online > Hardware detection" and assign a CPU identified online. For this purpose, you assign an IP address using the "Add address for PG/PC" button. Note If you want to go online after the hardware detection, you have to first download the detected configuration to your project; otherwise, an error may occur due to inconsistent configurations. After hardware detection, the order numbers of the CPU in the project and the actually existing CPU are identical, but their parameters are not. The parameters of the CPU in the project have the default values; the parameters of the actually existing CPU have the values set by you. See also Selecting a CPU (Page 413) Adding a device to the hardware configuration (Page 415) Inserting a module into a rack Introduction Once you have added devices from the hardware catalog to your configuration in network view, you can add modules to the devices. There are various ways of adding a module to a rack in the device view: If there is an available valid slot, double-click a module in the hardware catalog. Use drag-and-drop to move the module from the hardware catalog to an available valid slot in the graphic or table area: - Text entry from the "Catalog" pane - Preview graphic from the "Information" pane Select "Copy" in the shortcut menu for a module in the hardware catalog and then select "Paste" in the shortcut menu on an available valid slot in the graphic or table area. WinCC Basic V13.0 System Manual, 02/2014 417 Editing devices and networks 8.1 Configuring devices and networks To access the device view from the network view, double-click a device or station in the network view or select the Device view tab. The device view contains an illustration of the device selected within a rack. The graphic illustration of the rack in the software corresponds to the real structure, i.e. you can see the same number of slots as exist in the real structure. Note You can also move a module to a rack in the network view. The filter function for the hardware catalog must be deactivated in this instance. The module is automatically plugged into a free and permitted slot. If there are no slots available, the module will be moved to the area of unplugged modules (Page 412). Equipping a rack Arrange the modules on a rack according to the applicable slot rules. After a module has been inserted in a rack with an already inserted CPU, the address areas are checked automatically so that addresses are not assigned twice. After it has been inserted, each module then has one valid address range. To do so, DP slaves and IO devices must be networked with a CPU via the corresponding DP master or IO system. Requirements You are in the device view. The hardware catalog is open. Adding module from the hardware catalog How to insert a module from the hardware catalog into a rack is illustrated based on the example of a signal module. To do this, follow these steps: 1. Go to the required module board in the hardware catalog. Note If you activate the filter function of the hardware catalog, only those modules which match the selected device type will be displayed. 2. Select the chosen module. 418 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks 3. If necessary, set the firmware version using the drop-down list in the hardware catalog. 4. Drag the signal module to a free slot in the rack. You have now inserted the digital signal module in a slot in the rack. Repeat these steps with the other modules. The name of the module is displayed above the inserted modules. You can activate or deactivate module labeling in the menu bar with "View > Show module labels". Inserting module You can also drag modules and drop them between modules that have already been inserted. To do this, drag a module above and between the two existing modules while holding down the mouse button. A mouse pointer appears. When you release the mouse button, all modules plugged to the right of the pointer are moved one slot to the right. Any redundant modules are moved to the area of unplugged modules. The new module is plugged at the point of the freed up slot. See also Device view (Page 389) Area for unplugged modules (Page 412) General slot rules (Page 406) Deleting a hardware component There are various ways of deleting hardware components. Deleted hardware components are removed from the system and assigned addresses made available again. WinCC Basic V13.0 System Manual, 02/2014 419 Editing devices and networks 8.1 Configuring devices and networks Rules CPUs or modules from the rack and from the area of unplugged modules can be deleted. When a rack is deleted in the device view, the plugged hardware components are moved to the area of unplugged modules. Procedure Proceed as follows to delete a hardware component: 1. Select the hardware components you want to delete. - Network view: Select devices or network relevant hardware components in the graphic view or in the network view. - Device view: In the graphic view or device overview, select racks or modules in racks or in the area of unplugged components. - Topology view: Select devices or hardware components with Ethernet interfaces in the graphic view or in the topology view. - Project tree: Select devices or individual hardware components from the tree structure. 2. Select "Delete" from the shortcut menu or press <Del>. If the "Delete" menu item is unavailable, your selection contains at least one component that cannot be deleted. The selected hardware components are deleted. Note Deleting hardware components may result in inconsistencies in the project, such as violation of slot rules. Inconsistencies are reported during the consistency check. Correct the inconsistencies by taking appropriate action, for example, ensuring compliance with the slot rules. See also Keyboard operation: Editing objects (Page 403) Copying a hardware component You can copy hardware components in the device or network view. Copied hardware components are stored on a clipboard and can be pasted at another point from this clipboard. Copied stations are pasted as new stations in the network view. Copied devices and modules can be pasted into existing racks in the network and device view. Rules Single objects as well as several objects can be copied at the same time. Modules inserted in the rack and in the area of unplugged modules can be copied. 420 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks You can only copy devices and modules to free and valid slots in keeping with the slot rules. Racks with a CPU inserted cannot be copied individually, but only as complete units along with all inserted hardware components. Procedure Proceed as follows to copy a hardware component: 1. Select the hardware components you want to copy. - Device view: Select the module in a rack or put it in the area of unplugged modules. - Network view: Select the station or the relevant hardware component from the network view. - Project tree: Select the station or module. 2. Select "Copy" from the shortcut menu or press <Ctrl+C>. If the "Copy" menu item is unavailable, your selection contains at least one component that cannot be copied. 3. Select the location at which the content of the clipboard is to be pasted. - Device view: Select a free slot in the rack or area of unplugged modules. - Network view: Select a station where you want to insert devices or modules or move the mouse pointer to a free location in the network view to paste a copied station or a hardware component relevant to the network view. 4. Select "Paste" from the shortcut menu or press <Ctrl+V>. If the "Paste" menu item is unavailable, the clipboard is empty or contains at least one component that cannot be pasted at this point. The selected object is pasted at the chosen point. Once you have selected a station where you want to insert a module in the network view, the module is inserted in the first free and valid slot. If no free, valid slots are available, the object is inserted in the area of unplugged modules. Note You can also copy a module from one device to another: To do so, copy a module in the hardware and network editor, select a different device in the network view or the drop down list of the device view and insert the module. You can insert the copied object directly in a slot or place it in the area of unplugged modules in the device view. If you add the copied object in the network view of a device or a station, it will be inserted in the first available slot. If there is no slot available for the object, it is automatically placed in the area of unplugged modules (Page 412). Note You can use <Ctrl> and drag-and-drop to directly copy a selected hardware component. WinCC Basic V13.0 System Manual, 02/2014 421 Editing devices and networks 8.1 Configuring devices and networks See also Keyboard operation: Editing objects (Page 403) Moving a hardware component You can move hardware components in the device or network view. Rules You can move devices and modules from the rack and the area for unplugged modules taking the slot rules into consideration. CPs can be moved in the network view. The CP is plugged in a free and valid slot in the target device. If there are no free slots available, the CP to be inserted is moved to the area for unplugged modules. In the network view, CPU and slave head modules can be moved between the devices; depending on CPU type also within the rack. Note Moved CPs are disconnected from their network but keep their network parameters and address. If you reconnect the CP to the network and its address has been assigned, use a dialog to assign a new unique address to the CP. Procedure Proceed as follows to move a hardware component: 1. Select the hardware component you want to move. - Device view: Select the module in a rack or put it in the area of unplugged modules. - Network view: Select the hardware component of relevance to the network view. 2. Select "Cut" from the shortcut menu or press <Ctrl+X>. If the "Cut" menu item is unavailable, your selection contains at least one component that cannot be cut. 3. Select the location to which the cut object is to be moved. - Device view: Select a free slot in the rack or area of unplugged modules. - Network view: Select a station where you want to insert devices or modules. 4. Select "Paste" from the shortcut menu or press <Ctrl+V>. If the "Paste" menu item is unavailable, the clipboard is empty or contains at least one component that cannot be pasted at this point. 422 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks The selected hardware component is moved to the target. If the hardware component being moved is a networked object, it is disconnected from the network. Note You can use drag-and-drop to directly move a selected hardware component. See also Keyboard operation: Editing objects (Page 403) Replacing a hardware component You can replace hardware components with others. This, for example, allows you to replace unspecified CPUs (Page 416) with available CPUs from the hardware catalog. Rules You can only replace hardware components if they support module replacement and if the two components are compatible. Procedure To replace one module with another, proceed as follows: 1. Select the module you want to replace. 2. Open the shortcut menu: - If the "Replace device" entry is enabled, the module can be replaced. - If the "Replace device" entry is disabled, a module cannot be replaced. 3. Click on "Replace device" in the shortcut menu. The "Replace device" dialog box appears. 4. Under "New device" in the tree structure, select the module with which you want to replace your current module. 5. Click "OK". The existing module is replaced by the new one. As an alternative, you can take a module by dragging it from the hardware catalog to the module you are replacing. If the module can be replaced by the selected module, this is indicated by the mouse pointer symbol. Editing properties and parameters Once you have inserted hardware components in your rack, you can edit their default properties, for example parameters or addresses in the network or device view. WinCC Basic V13.0 System Manual, 02/2014 423 Editing devices and networks 8.1 Configuring devices and networks Requirement You are in the device view. Note You can also edit properties and parameters in the network view. In the graphic network view, you have access to the network-related hardware components and the station. You can access modules and hardware components not displayed in the graphic network view using the table network view. Procedure To change the properties and parameters of the hardware components, proceed as follows: 1. In the graphic view, select the CPU, module, rack or interface you want to edit. 2. Edit the settings for the selected object: - Use the table view to edit addresses and names, for example. - In the Inspector window additional setting possibilities are available in "Properties". Note that modules can only be fully parameterized if they are assigned to a CPU. Therefore, PROFIBUS or PROFINET interfaces modules must first be networked with the CPU or a centrally inserted communication module so that they form a master system or IO system. Only then is it possible, for example, to edit the addresses of the distributed components that are inserted. 424 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Example of changing settings 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 397) Input and output addresses in the address overview Introduction The currently used input and output addresses can be displayed in the address overview in a table form. The address overview can be found in the Inspector window under "Properties" of the CPU. WinCC Basic V13.0 System Manual, 02/2014 425 Editing devices and networks 8.1 Configuring devices and networks Design of the address overview With the different check boxes, you can set which objects should be displayed in the address overview: Inputs: Display of the input addresses Outputs: Display of the output addresses Address gaps: Display of open address spaces Slot: Display of the slot number The following information is typically shown in the address overview: Table header Meaning Type Indicates whether the area is an input address area or an output address area. Addr. from Start address of the address range. Addr. to End address in the address range. Module Module using the address area. PIP Number of the process image partition. Shows whether the cyclic OB is within the process image partition. OB Organization block that is assigned to the process image. This column is not available for every CPU. DP Number of the master system. You can use the number to determine which slaves are assigned to a master. The value in brackets specifies the PROFIBUS address of the hardware component. PN Number of the IO system. The value in brackets stands for the device number of the hardware component. Rack Number of the rack on which the hardware component is inserted. Slot Number of the slot in the rack in which the hardware component is inserted. See also Specifying input and output addresses (Page 666) 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. Example: V11.0.0.0 Firmware version: The version of the firmware of the module whose parameters are assigned offline Example: V2.0 426 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Requirement 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 use 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 TIA Portal V12 to V13. In this case, all older module versions are automatically adapted. 8.1.2.3 Comparing devices Basics of device comparison Function You have the option of comparing the hardware components of two devices allowing you to identify any differences. You can perform an offline/offline comparison for this purpose. The devices to be compared can be from one project or different projects. You can compare the central as well as the distributed I/O. The devices to be compared can be assigned either automatically or manually. The automatic assignment of central I/O is based WinCC Basic V13.0 System Manual, 02/2014 427 Editing devices and networks 8.1 Configuring devices and networks on the slot number. With the distributed I/O, the automatic assignment can be made according to the following criteria: Assignment using the address/ID: The assignment is made using the addresses or IDs of the devices. This criterion is suitable for comparing devices within a project. Assignment using the name: The assignment is made based on the device names. This criterion is suitable for comparing devices in different projects. You can either specify the assignment yourself or let the system decide. In the latter case, the system selects the assignment itself depending on the context. See also Basics of project data comparison (Page 273) Overview of the compare editor (Page 275) Making a device comparison (Page 428) Making a device comparison Procedure Follow the steps below to compare devices: 1. Select a device in the project tree that allows offline/offline comparison. 2. Select the "Compare > Offline/offline" command in the shortcut menu. The comparison editor opens and the selected device is displayed in the left area. 3. Open the "Hardware" tab. 4. Drag an additional device to the drop area in the right-hand pane. All existing objects of the selected devices are displayed depending on the settings of the comparison editor in the "Hardware" tab and an automatic comparison is made. You can identify the status of the objects based on the symbols in the comparison editor. 5. If you want to change the matching criterion, click on the arrow of the "Available matching criteria" button in the toolbar. Then, select the matching criterion you want to use. 6. If you want to make a manual comparison, click the button for switching between automatic and manual comparison above the status area. Then select the objects you want to compare. The properties comparison is displayed. You can see the status of the objects based on the symbols. See also Basics of device comparison (Page 427) Overview of the compare editor (Page 275) 428 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks 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. WinCC Basic V13.0 System Manual, 02/2014 429 Editing devices and networks 8.1 Configuring devices and networks 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. 430 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks 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. WinCC Basic V13.0 System Manual, 02/2014 431 Editing devices and networks 8.1 Configuring devices and networks 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. 432 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks 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. WinCC Basic V13.0 System Manual, 02/2014 433 Editing devices and networks 8.1 Configuring devices and networks 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. 434 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks 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. WinCC Basic V13.0 System Manual, 02/2014 435 Editing devices and networks 8.1 Configuring devices and networks 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 430) 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. 436 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks 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. WinCC Basic V13.0 System Manual, 02/2014 437 Editing devices and networks 8.1 Configuring devices and networks 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 439) 438 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks 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, ... 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 ... Max. Tsdr - 1, 34 + 2*Tset + Tqui) WinCC Basic V13.0 System Manual, 02/2014 439 Editing devices and networks 8.1 Configuring devices and networks 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 438) Description of the bus parameters (Page 440) 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. 440 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks 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 439) 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 WinCC Basic V13.0 System Manual, 02/2014 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 441 Editing devices and networks 8.1 Configuring devices and networks 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. 442 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks 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. WinCC Basic V13.0 System Manual, 02/2014 443 Editing devices and networks 8.1 Configuring devices and networks 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 "Userdefined" 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. 444 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks 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 IP subnet Address of the device (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 device. 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 device, i.e. 0.2. It is generally true that: The network address results from AND logic operation of the IP address and subnet mask. The device address results from the AND NOT logic operation of 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: WinCC Basic V13.0 System Manual, 02/2014 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 445 Editing devices and networks 8.1 Configuring devices and networks 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 not recommended, however, because there is no address check for these values. Masking other subnets You can use the subnet mask to add further structures and form "private" subnets for a subnet that is assigned one of the address classes A, B or C. This is done by setting other lower points of the subnet mask to "1". For each bit set to "1", the number of "private" networks doubles and the number of devices 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 devices with addresses between 129.80.001.xxx and 129.80.127.xxx are on one IP subnet, all devices with addresses between 129.80.128.xxx and 129.80.255.xxx are on another IP subnet. Router The task of the routers is to connect the IP 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 device in the IP subnet. The IP address of a device in the subnet and the IP address of the router can only differ at the points at which there is a "0" in the subnet mask. See also Settings for interconnecting Ethernet devices (Page 446) Settings for interconnecting Ethernet devices The following paragraph describes the behavior of STEP 7 during interconnection of PROFINET devices and the effects of the port interconnection on the network view. 446 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Relation between port interconnection and network view Topology view: In the topology view, you specify the physical interconnection of Ethernet ports. You specifically determine which Ethernet port of a device is to be connected with a specific Ethernet port of another device by means of an Ethernet cable (preset topology). Example: You specify that port 1 of the PROFINET interface of the CPU is to be connected to port 2 of the PROFINET interface of device A by means of an Ethernet cable. You also specify the interface for devices with several PROFINET interfaces. Example: You specify that port 1 of PROFINET interface X2 of the CPU is to be connected to port 2 of the PROFINET interface of device A by means of an Ethernet cable. The Ethernet ports can be interconnected in a table or graphically. Network view: In the network view, you specify which devices are to be connected with each other via an Ethernet subnet. You do not specify the Ethernet ports by which the devices are interconnected with each other (that is the task of the port interconnection). The port interconnection has effects on the network view: When you interconnect Ethernet ports of devices with each other in the topology view, STEP 7 connects the interconnected PROFINET interfaces of the devices in the network view with an Ethernet subnet (green line). However, the course of the green line does not reflect the actual cable routing. You specify the actual wiring in the topology view. An Ethernet subnet always has a name and an S7 subnet ID. You can set these two values in the subnet properties. Which Ethernet subnet is used to link interconnected devices? STEP 7 distinguishes between the following cases: Ethernet subnet specified (default subnet). No Ethernet subnet specified (no default subnet). Ethernet subnet specified (default subnet) The option "Connect devices that are not linked with this subnet in case of port connection" is activated in the properties of an Ethernet subnet (default). This option can be activated for exactly one Ethernet subnet. Activate the option, if necessary, for the Ethernet subnet that is to be continued when interconnecting devices that are not linked. This subnet is referred to as "default subnet" below. WinCC Basic V13.0 System Manual, 02/2014 447 Editing devices and networks 8.1 Configuring devices and networks Response of STEP 7: When you interconnect the ports of two devices that are not linked in the topology view, STEP 7 links these devices with the default subnet. Example: Step 1: Create a subnet in the network view at PLC_4, "Connect devices that are not linked with this subnet in case of port connection" option is enabled. Step 2: Interconnect PLC_1 with PLC_2 (topology view). Result: All PLCs are now connected to the same default subnet (network view). No Ethernet subnet specified (no default subnet). This is the case when the following conditions are fulfilled: A subnet has been added to a PROFINET interface (this interface is referred to as "Interface A" below). The option "Connect devices that are not linked with this subnet in case of port connection" is deactivated in the properties of this subnet (no default subnet). There is no other Ethernet subnet for which this option is activated. Response of STEP 7: The Ethernet subnet of interface A is only continued when you interconnect a port of interface A with a port of another device. When you interconnect ports of other devices that are not linked with each other, STEP 7 creates a new Ethernet subnet. 448 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Example: Step 1: Create a subnet in the network view at PLC_4, "Connect devices that are not linked with this subnet in case of port connection" option is disabled. Step 2: Interconnect PLC_1 with PLC_2 (topology view). Result: PLC_1 and PLC_2 are connected to a new subnet (network view). Manual adaptation of the IP addresses It can occur that STEP 7 does not adapt the IP addresses of the interconnected devices in such a way that the resulting network can be correctly compiled, for example, for devices with multiple PROFINET interfaces. In these situations, you need to adapt the IP addresses of the devices manually. The following rules apply: Devices that are to communicate with each other without a router cannot belong to different IP subnets. For devices with multiple PROFINET interfaces, the interfaces must be in different IP subnets. To change the IP address of a PROFINET interface, perform the following steps: 1. Change to the network view (if not selected already). 2. Left-click on the icon of the PROFINET interface that is not to be part of the IP subnet. 3. Change the subnet part of the IP address in the properties of the PROFINET interface (in the "Ethernet addresses" area). WinCC Basic V13.0 System Manual, 02/2014 449 Editing devices and networks 8.1 Configuring devices and networks Example: Manual conversion of the IP subnet part for devices with multiple PROFINET interfaces in a subnet The IP address is: "192.168.0.1". The subnet mask is "255.255.255.0". The first three numbers "192.168.0" form the IP subnet part of the IP address "192.168.0.1". Change the IP subnet part, for example, to "192.168.1" See also Interconnecting ports in the graphic view (Page 519) Interconnecting ports in the table view (Page 520) Configuring Industrial Ethernet (Page 444) Network configuration of AS interface AS-Interface consists of an AS-i master and AS-i slaves connected to each other over an ASi 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. 450 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks 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. WinCC Basic V13.0 System Manual, 02/2014 451 Editing devices and networks 8.1 Configuring devices and networks 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" 452 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks 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 WinCC Basic V13.0 System Manual, 02/2014 453 Editing devices and networks 8.1 Configuring devices and networks 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. 454 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks 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. WinCC Basic V13.0 System Manual, 02/2014 455 Editing devices and networks 8.1 Configuring devices and networks 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 colorhighlighted 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. 456 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks 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. WinCC Basic V13.0 System Manual, 02/2014 457 Editing devices and networks 8.1 Configuring devices and networks 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. 458 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks 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 using the network view or the connection table. In the network view you can delete one highlighted connection per action. In the connection table you can delete one or several connections per action. Procedure To delete a connection, follow these steps: 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. Result The selected connection is removed completely. WinCC Basic V13.0 System Manual, 02/2014 459 Editing devices and networks 8.1 Configuring devices and networks 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, 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 460 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks 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. 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. WinCC Basic V13.0 System Manual, 02/2014 461 Editing devices and networks 8.1 Configuring devices and networks 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 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 462 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks S7 connections via CM/CP Introduction S7-1200 CPUs with a firmware version of V2.0 or higher support one-way and two-way S7 connections via CM/CP interfaces. This increases the number of Ethernet ports and networks that can be used for S7 connections. Even though the connection is then guided via the CM/ CP, the associated S7-1200 CPU is an end point of the connection. The other end point can be any other device in the case of two-way connections. This other device must also support S7 connections. Data volumes and configuration limit The number of communication connections which are supported by CM/CP can be found in the manual accompanying every CM/CP. The number of connections per device can be further increased by adding other CM/CPs. If several CM/CPs are fitted in a device, an automatic switch is made to the next CM/CP when this limit is exceeded. Specifically assign the connections using the path selection as required. Note Data transfer > 240 byte transfer is supported by the current CPs. CPs with an older product version support the transfer of data with a data length of up to 240 bytes. For more information, refer to the details provided in the Ethernet CP equipment manual. Tasks of the Ethernet CM/CP in online mode During data transfer via a connection, the Ethernet CM/CP takes on the following tasks: Receiving Receiving data from the Ethernet and forwarding to the user data area in the CPU Sending Transferring data from the user data area of the CPU and sending data via the Ethernet The connection is established automatically as soon as the partner can be reached. WinCC Basic V13.0 System Manual, 02/2014 463 Editing devices and networks 8.1 Configuring devices and networks 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). 464 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks 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 WinCC Basic V13.0 System Manual, 02/2014 465 Editing devices and networks 8.1 Configuring devices and networks 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. 466 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks 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. WinCC Basic V13.0 System Manual, 02/2014 467 Editing devices and networks 8.1 Configuring devices and networks 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 colorhighlighted 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. 468 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks 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. WinCC Basic V13.0 System Manual, 02/2014 469 Editing devices and networks 8.1 Configuring devices and networks See also Creating a new connection graphically (Page 467) 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. 470 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks 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 using the network view or the connection table. In the network view you can delete one highlighted connection per action. In the connection table you can delete one or several connections per action. Procedure To delete a connection, follow these steps: 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. Result The selected connection is removed completely. 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. WinCC Basic V13.0 System Manual, 02/2014 471 Editing devices and networks 8.1 Configuring devices and networks 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. 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 recreate 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. 472 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks 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 given to a program-controlled communication process for communicating via the integrated PN/IE interface of the S7-1200/1500 and S7-300/400 CPUs. Different connection types are available for this communication process. 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 CPUs with an integrated PN/IE interface, the TCP, UDP, and ISO-on-TCP connection types are available for Open User Communication. The communication partners can be two SIMATIC PLCs or a SIMATIC PLC and a suitable third-party device. WinCC Basic V13.0 System Manual, 02/2014 473 Editing devices and networks 8.1 Configuring devices and networks Instructions for Open User Communication To create the connections, you have various instructions available after opening in the program editor in the "Instructions > Communication > Open User Communication" task card: Compact instructions for sending or receiving data via the integrated functions for establishing and terminating the connection (S7-1200/1500 only): - 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 communication partners. One communication partner sends its data using TSEND, TUSEND or TSEND_C while the other communication partner receives the data using TRCV, TURCV or TRCV_C. One of the communication partners starts the connection establishment as the active partner. The other communication 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 configuration You can specify establishment of the connection via a connection description DB with the TCON_Param, TCON_IP_v4, or TCON_IP_RFC structure by means of parameter assignment as follows: Manually create, assign parameters and write directly to the instruction. Supported by connection configuration. Connection configuration supports the establishment of the connection and should, therefore, be given preference over the other methods. You specify the following in the connection configuration: Connection partner Connection type Connection ID 474 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Connection description DB Address details according to selected connection type 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 communication partner. See also Principle of operation of connection-oriented protocols (Page 487) Connection configuration Overview of connection configuration Introduction You can 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 configuration supports the flexible functionality of communication programming: The parameters entered for the connection configuration are stored in an automatically generated global DB derived from the TCON_Param, TCON_IP_v4 or TCON_IP_RFC structure. You can modify the connection parameters in this connection description DB. WinCC Basic V13.0 System Manual, 02/2014 475 Editing devices and networks 8.1 Configuring devices and networks Structure of the connection configuration The connection configuration is made up of the following components: 476 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks WinCC Basic V13.0 System Manual, 02/2014 477 Editing devices and networks 8.1 Configuring devices and networks Communication instruction for TCON, TSEND_C or TRCV_C "Configuration" tab in the "Properties" tab Area navigation of the "Configuration" tab General properties of the connection parameters Address details of the connection parameters (for selected connection DBs) "Configuration" tab Enter the desired connection parameters in the "Configuration" tab. The area navigation of the "Configuration" tab includes the "Connection parameters" group. This group contains the connection configuration. Here, you can enter the parameters for the connections and the address details with system support. Here, you also connect the CONNECT (TCON, TSEND_C, TRCV_C) or ID (TCON, TSEND, TRCV, TUSEND, TURCV) block parameters of the selected communication instructions. When all the required parameters are assigned, a check mark is set in front of the "Connection parameters" group in the area navigation. Note The connection parameter assignment does not check whether the connection IDs and port numbers (TCP, UDP) or TSAPs (ISO-on-TCP, ISO) are unique. When you configure Open User Communication, you should, therefore, make sure that the parameter settings are unique within a device. See also Connection parameters with structure according to TCON_Param (Page 489) Connection parameters with structure according to TCON_IP_v4 (Page 492) Connection parameters with structure according to TCON_IP_RFC (Page 493) 478 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Description of the connection parameters Overview The following table shows the general connection parameters: Parameter Description End point The names of the local end point and the partner end point are shown. The local end point is the CPU for which TCON, TSEND_C or TRCV_C is programmed. The local end point is, therefore, always known. The partner end point is selected from the drop-down list. The drop-down list shows all available possible connection partners including unspecified connection partners for devices whose data is unknown in the project. For S7-1500, broadcast can be selected as the partner end point (message to all subnet devices). For S7-1500 CPs/CMs, multicast can also be selected as the partner end point (message to a group within the subnet). The connection type is converted automatically to UDP in this case. As long as no connection partner is set, all other parameters in the mask are disabled. Interface The interface of the local end point is displayed. If multiple interfaces are available, e.g., by means of CPs or CMs, the interface can be selected from the drop-down list. To display or select the partner interface, a specified partner end point must first be selected. Subnet The subnet of the local end point is displayed, provided this exists. The partner subnet is displayed only after the partner end point has been selected. If at least one of the two connection partners is not connected with a subnet, the two connection partners are connected with each other. A connection between partners in different subnets is only possible with IP routing. The IP routing settings can be edited in the properties of the relevant Ethernet interfaces. Address The IP address of the local end point is displayed. The IP address of the partner is displayed only after the partner end point has been selected. If you have selected an unspecified connection partner, the input box is empty and has a red background. In this case, you need to specify a valid IP address. Broadcast (S7-1500 only): If "Broadcast" is set as the partner end point, a non-editable IP address with host address 255 is entered automatically for the connection partner. The network allocation corresponds to that of the sender. Example: Local IP address 192.168.0.1, partner IP address 192.168.0.255. Multicast (S7-1500 CPs/CMs only): If "Multicast" is set as the partner end point, the editable IP address 224.0.1.0 is entered automatically for the connection partner. Connection type Select the connection type you want to use from the "Connection type" drop-down list: TCP ISO-on-TCP UDP With the S7-1500, you can also select the ISO connection type at the configuration type of the configured connections for TSEND_C and TRCV_C or TCON. The connection types can only be used for partners that support the corresponding protocol. WinCC Basic V13.0 System Manual, 02/2014 479 Editing devices and networks 8.1 Configuring devices and networks Parameter Description Connection type (for S7-1500 only) With the S7-1500, two different configuration types can be set for TSEND_C and TRCV_C: Programmed connections use program blocks for the connection description. Configured connections are saved for the configuration and are only created after download to the device in runtime. You can also use the configured connection to select the connection type ISO. The specified configuration method depends on the selected connection type. If both configuration methods are possible, the programmed connection is preset. The same configuration method must be set for both connection partners. Connection ID Enter the connection ID in the input box. You can change the connection ID in the input boxes or enter it directly in TCON. Ensure that the connection ID assigned is unique within the device. Connection data The names of the connection description DBs for the connection description structured according to TCON_IP_v4, TCON_IP_RFC or TCON_Param are displayed in the drop-down lists. The drop-down list is still empty after selection of a connection partner. You can use the dropdown list to generate a new data block or to select an existing data block. This data block is filled automatically with the values from the connection configuration. The name of the selected data blocks is entered automatically in the CONNECT block parameter of the selected TSEND_C, TRCV_C or TCON instruction. From the drop-down list, you can also reference another valid data block. If a DB is referenced using the CONNECT input parameter of the TSEND_C, TRCV_C or TCON extended instructions and this does not correspond to the structure of a TCON_IP_v4, TCON_IP_RFC or TCON_Param, the drop-down list is shown with no content on a red background. Connection name (for S7-1500 only) If the connection type of the configured connections is set for TSEND_C and TRCV_C for the S7-1500, the "Connection data" parameter is replaced with the "Connection name" parameter. The name of the configured connection serves here as the connection data. The drop-down list is still empty after selection of a connection partner. You can use the dropdown list to generate a new connection or to select an existing connection. If needed, a data block is created and automatically filled with the values from the connection configuration. The name of the data block is entered automatically in the CONNECT block parameter of the TSEND_C or TRCV_C instruction. You can also reference an existing connection from the drop-down list. Active connection establishment Use the "Active connection establishment" check box to specify the active partner of the Open User Communication (only with TCP and ISO-on-TCP). Port Address component for a TCP or UDP connection. The default after creating a new TCP connection is 2000. (only with TCP and UDP) You can change the port numbers. The port numbers must be unique on the device! TSAP (ISO-on-TCP only) Address component for an ISO-on-TCP connection. The default value after creating a new ISO-on-TCP connection is E0.01.49.53.4F.6F.6E.54.43.50.2D.31 (S7-1200/1500) or E0.02.49.53.4F.6F.6E.54.43.50.2D.31 (S7-300/400). You can enter the TSAP-ID with an extension or as an ASCII TSAP. The TSAPs must be unique on the device! 480 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Note UDP connection for the "Broadcast" setting (S7-300/400/1200) The parameters of the UDP connection for the "Broadcast" setting for the partner end point are stored in a connection description DB TCON_IP_v4 : With respect to UDP communication with TCON and TUSEND/TURCV , the TCON_IP_v4 is not filled with any partner parameters (value=0). However, the partner address and the partner port are necessary for sending the data and must be entered by the user in the TADDR_Param . The TADDR_Param for UDP communication is referenced by the TUSEND-/TURCV block parameter ADDR . The values for both parameters can be taken from the connection configuration. The configuration must also be adapted for the other recipients of UDP communication. In order to receive broadcast frames, the partner port must be configured at the receiver end. For this purpose, the RemotePort parameter of the TADDR_Param must be filled at the ADDR block. Note Communication via TSEND_C and TRCV_C (S7-1500) When TSEND_C and TRCV_C are used, a separate TSEND_C and TRCV_C block pair with a configured connection is required for each communication. Multiple TSEND_C and TRCV_C block pairs cannot simultaneously use the same configured connection for communication. Additional connections for a TSEND_C or TRCV_C instruction can be created in the inspector window for the connection parameters using the appropriate button next to the connection data. The connections configured using TSEND_C and TRCV_C are displayed in a connection table in the inspector window under "Properties > Configuration > Overview of configured connections" when the TSEND_C or TRCV_C block is selected. See also Assignment of port numbers (Page 494) TSAP structure (Page 497) Examples of TSAP assignment (Page 499) Ability to read back connection description parameters (Page 495) Creating and assigning parameters to connections (Page 483) Connection parameters with structure according to TCON_Param (Page 489) Connection parameters with structure according to TCON_IP_v4 (Page 492) Connection parameters with structure according to TCON_IP_RFC (Page 493) WinCC Basic V13.0 System Manual, 02/2014 481 Editing devices and networks 8.1 Configuring devices and networks Starting connection parameter assignment The connection configuration for Open User Communication is enabled as soon as a TCON, TSEND_C or TRCV_C instruction for communication is selected in a program block. Requirement Your project must contain at least one S7-CPU. The program editor is open. A network is available. Procedure To insert the extended instructions for Open User Communication, proceed as follows: 1. Open the task card, pane and folder "Instructions > Communication > Open User Communication". 2. Drag one of the following instructions to a network: - TSEND_C - TRCV_C - TCON The "Call options" dialog opens. 3. Edit the properties of the instance DB in the "Call properties" dialog. You have the following options: - Change the default name. - Select the "Manual" check box to assign your own number. - You can also execute the DB as a multi-instance for function blocks. 4. Click "OK" to complete your entry. Result A corresponding instance DB is created at a single instance for the inserted instruction TSEND_C, TRCV_C or TCON. In the case of a multi-instance, the instance DB of the function block is used. With TSEND_C, TRCV_C or TCON selected, you will see the "Configuration" tab under "Properties" in the Inspector window. The "Connection parameters" group in area navigation contains the connection parameter assignment that you can now make. See also Creating and assigning parameters to connections (Page 483) 482 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Creating and assigning parameters to connections In the connection configuration for Open User Communication, you can create and configure connections of the TCP, UDP or ISO-on-TCP type. Requirement A CPU exists with a TCON, TSEND_C or TRCV_C communication instruction. Procedure To create a connection for Open User Communication, follow these steps: 1. Select a TCON, TSEND_C or TRCV_C block of Open User Communication in the program editor. 2. Open the "Properties > Configuration" tab in the inspector window. 3. Select the "Connection parameters" group. Until you select a connection partner, only the empty drop-down list for the partner end point is enabled. All other input options are disabled. The connection parameters already known are displayed: - Name of the local end point - Interface of the local end point - IP address of the local end point 4. In the drop-down list box of the partner end point, select a connection partner. You can select an unspecified device or a CPU in the project as the communication partner. Certain connection parameters are then entered automatically. The following parameters are set: - Name of the partner end point - Interface of the partner end point - IP address of the partner end point If the connection partners are networked, the name of the subnet is displayed. 5. With the S7-1500, in the "Configuration type" drop-down list, you choose between using program blocks or configured connections. WinCC Basic V13.0 System Manual, 02/2014 483 Editing devices and networks 8.1 Configuring devices and networks 6. Select an existing connection description DB in the "Connection data" drop-down list or for configured connections select an existing connection under "Connection name". You can also create a new connection description DB or a new configured connection. Later, you can still select other connection description DBs or configured connections or change the names of the connection description DBs in order to create new data blocks: - You can also see the selected data block at the interconnection of the CONNECT input parameter of the selected TCON, TSEND_C or TRCV_C instruction. - If you have already specified a connection description DB for the connection partner using the CONNECT parameter of the TCON, TSEND_C or TRCV_C instruction, you can either use this DB or create a new DB. - If you edit the name of the displayed data block in the drop-down list, a new data block with the changed name but with the same structure and content is generated and used for the connection. - Changed names of a data block must be unique in the context of the communication partner. - A connection description DB must have the structure TCON_Param, TCON_IP_v4 or TCON_IP_RFC, depending on CPU type and connection. - A data block cannot be selected for an unspecified partner. Additional values are determined and entered after the selection or creation of the connection description DB or configured connection. The following is valid for specified connection partners: - ISO-on-TCP connection type - Connection ID with default of 1 - Active connection establishment by local partner - TSAP ID for S7-1200/1500: E0.01.49.53.4F.6F.6E.54.43.50.2D.31 for S7-300/400: E0.02.49.53.4F.6F.6E.54.43.50.2D.31 The following is valid for unspecified connection partners: - TCP connection type - Partner port 2000 The following applies for a configured connection with a specified connection partner: - TCP connection type - Connection ID with default of 257 - Active connection establishment by local partner - Partner port 2000 The following applies for a configured connection with an unspecified connection partner: - TCP connection type - Local port 2000 484 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks 7. Enter a connection ID as needed for the connection partner. No connection ID can be assigned to an unspecified partner. Note You must enter a unique value for the connection ID at a known connection partner. The uniqueness of the connection ID is not be checked by the connection parameter settings and there is no default value entered for the connection ID when you create a new connection. 8. Select the desired connection type in the relevant drop-down list. Default values are set for the address details depending on the connection type. You can choose between the following: - TCP - ISO-on-TCP - UDP For configured connections with S7-1500, ISO applies in addition. 9. You can edit the input boxes in the address details. Depending on the selected protocol, you can edit the ports (for TCP and UDP) or the TSAPs (for ISO-on-TCP and ISO). 10.Use the "Active connection establishment" check box to set the connection establishment characteristics for TCP, ISO and ISO-on-TCP. You can decide which communication partner establishes the connection actively. Changed values are checked immediately for input errors by the connection configuration and entered in the data block for the connection description. Note Open User Communication between two communication partners can only work when the program section for the partner end point has been downloaded to the hardware. To achieve fully functional communication, make sure that you load not only the connection description of the local CPU on the device but also that of the partner CPU as well. See also Description of the connection parameters (Page 479) Starting connection parameter assignment (Page 482) TSAP structure (Page 497) Assignment of port numbers (Page 494) Connection parameters with structure according to TCON_Param (Page 489) Connection parameters with structure according to TCON_IP_v4 (Page 492) Connection parameters with structure according to TCON_IP_RFC (Page 493) WinCC Basic V13.0 System Manual, 02/2014 485 Editing devices and networks 8.1 Configuring devices and networks Deleting connections Introduction The data of a created connection for Open User Communication is stored in a connection description DB. You can delete the connection by deleting the data block containing the connection description. Requirement You have created an Open User Communication connection. Procedure To delete a connection, follow these steps: 1. Select a communication partner for Open User Communication in the project tree. 2. Open the "Program blocks > System blocks > Program resources" folder below the selected communication partner. 3. Select the "Delete" command from the shortcut menu of the data block with the connection parameter assignment. Note If you are not certain which block to delete, open the extended instruction TCON, TSEND_C or TRCV_C. You will find the name of the data block as the CONNECT input parameter or in the connection parameter assignment as the "Connection data" parameter. If you only delete the instance DBs of the extended instructions TCON, TSEND_C or TRCV_C, the assigned connections are not deleted as well. Note If the connection DB is still being used by other blocks of the extended instructions, then the corresponding calls, their instance DBs, and, if present, the combination blocks TSEND_C and TRCV_C must also be deleted from the block folder, provided they are not used elsewhere. This action prevents the program from being inconsistent. 486 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Result You have deleted the connection. Note Insert an extended instruction TCON, TSEND_C, or TRCV_C again in order to reference an existing connection description with the TCON_Param, TCON_IP_v4, or TCON_IP_RFC structure again via the "Connection data" parameter. How protocols work Principle of operation of connection-oriented protocols Introduction Connection-oriented protocols establish a logical connection to the communication partner before data transmission is started. After the data transmission is complete, they then terminate the connection, if necessary. Connection-oriented protocols are used especially when reliable data transmission is important. Several logical connections can exist over one physical line. Open User Communication supports the following connection types: TCP ISO-on-TCP ISO (S7-1500 only) UDP Both communication partners must support the same connection type for a connection. If a communication partner does not support a connection of the type ISO-on-TCP, for example, use the connection type TCP instead, if it is supported. For communication partners that cannot be configured in the TIA Portal, such as third-party devices or PCs, enter "unspecified" for the partner end point during connection parameter assignment. The required connection type for unspecified devices is listed in the respective documentation. Note Connections with ISO For S7-1500 CPUs, configured connections of the type ISO can be created using the TSEND_C and TRCV_C instructions. For additional information on these connection types, refer to the general connection descriptions. WinCC Basic V13.0 System Manual, 02/2014 487 Editing devices and networks 8.1 Configuring devices and networks Characteristics of TCP TCP is a streaming protocol in which the length of the data stream is transmitted to the receiver so that it can receive the data stream as individual TCP segments. This means no information about the start and end of a message is transmitted during data transmission via a TCP connection. The receiver cannot determine by the received segments of the data stream where one message in the data stream ends and the next one begins. It is therefore recommended that the number bytes to be received (parameter LEN, instruction TRCV/TRCV_C) be assigned the same value as the number of bytes to be sent (parameter LEN, instruction TSEND/ TSEND_C). If the length of the sent data and the length of the expected data do not match, the following occurs: Length of data to be received (parameter LEN, instruction TRCV/TRCV_C) greater than length of data to be sent (parameter LEN, instruction TSEND/TSEND_C): TRCV/TRCV_C copies the received data to the specified receive area (parameter DATA) only after the assigned length is reached. When the assigned length is reached, data of the subsequent job are already being received. As a result, the receive area contains data from two different send jobs. If you do not know the exact length of the first message, you are unable to recognize the end of the first message and the start of the second message. Length of data to be received (parameter LEN, instruction TRCV/TRCV_C) less than length of data to be sent (parameter LEN, instruction TSEND/TSEND_C): TRCV/TRCV_C copies the number of bytes you specified in the LEN parameter to the receive data area (parameter DATA). Then, it sets the NDR status parameter to TRUE (job completed successfully) and assigns RCVD_LEN (amount of data actually received) the value of LEN. With each subsequent call, you receive a further block of the sent data. A receive area with fixed data length can be specified in the TRCV/TRCV_C instructions with the protocol version of the Ad-hoc mode. Characteristics of ISO-on-TCP ISO-on-TCP is a message-oriented protocol which detects the end of the message at the receiver end and indicates the data that belongs to the message to the user. This does not depend on the specified reception length of the message. This means that information regarding the length and the end of a message is included during data transmission via an ISO-on-TCP connection. If the length of the sent data and the length of the expected data do not match, the following occurs: Length of data to be received (parameter LEN, instruction TRCV/TRCV_C) greater than length of data to be sent (parameter LEN, instruction TSEND/TSEND_C): TRCV/TRCV_C copies all the sent data to the receive data area (parameter DATA). Then, it sets the NDR status parameter to TRUE (job completed successfully) and assigns RCVD_LEN (amount of data actually received) the length of the data sent. Length of data to be received (parameter LEN, instruction TRCV/TRCV_C) less than length of data to be sent (parameter LEN, instruction TSEND/TSEND_C): TRCV/TRCV_C does not copy any data to the receive data area (parameter DATA), but instead supplies the following error information: ERROR=1, STATUS=W#16#8088 (destination buffer too small). 488 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Characteristics of UDP UDP is a message-oriented protocol which detects the end of the message at the receiver end and indicates the data that belongs to the message to the user. This does not depend on the specified reception length of the message. This means that information on the length and the end of a message is included during data transmission via a UDP connection. If the length of the sent data and the length of the expected data do not match, the following occurs: Length of data to be received (parameter LEN, instruction TRCV/TRCV_C) greater than length of data to be sent (parameter LEN, instruction TUSEND/TSEND_C): TURCV/TRCV_C copies all the sent data to the receive data area (DATA parameter). Then, it sets the NDR status parameter to TRUE (job completed successfully) and assigns RCVD_LEN (amount of data actually received) the length of the data sent. Length of data to be received (parameter LEN, instruction TRCV/TRCV_C) less than length of data to be sent (parameter LEN, instruction TUSEND/TSEND_C): TRCV/TRCV_C copies as much data to the receive data area (parameter DATA) as the LEN parameter requests. No further error message is generated. In this case, the user has to call a T_URCV again in order to receive the remaining bytes. See also Basics of Open User Communication (Page 473) Connection parameters with structure according to TCON_Param Data block for connection description A connection description DB with a structure according to TCON_Param is used for some S7-1200 CPUs when it comes to the assignment of parameters for TCP, UDP and ISO-onTCP communication connections. The fixed data structure of the TCON_Param contains all the parameters that are needed to establish the connection. The connection description DB is automatically created for a new connection by the connection configuration for Open User Communication when the TSEND_C, TRCV_C or TCON instruction is used. The CONNECT connection parameter of the instance DBs for TSEND_C, TRCV_C or TCON contains a reference to the data block used. Structure of the connection description according to TCON_Param Byte Data type Start value Description 0 ... 1 block_length Parameter UINT 64 Length: 64 bytes (fixed) 2 ... 3 id CONN_OUC 1 Reference to this connection (value range: 1 to 4095). You must specify the value of this parameter for the TSEND_C, TRCV_C or TCON instruction under ID. WinCC Basic V13.0 System Manual, 02/2014 489 Editing devices and networks 8.1 Configuring devices and networks Byte Parameter Data type Start value Description 4 connection_type USINT 17 Connection type: 17: TCP 18: ISO-on-TCP 19: UDP 5 active_est BOOL TRUE Identifier for the type of connection establishment: FALSE always applies to UDP, since data can be sent and received via local ID. The following is valid for TCP and ISO-on-TCP: FALSE: Passive connection establishment TRUE: Active connection establishment 6 local_device_id USINT 1 ID for the local PN/IE interface. 7 local_tsap_id_len USINT 0 Length of parameter local_tsap_id used, in bytes; possible values: 0 or 2, if connection type = 17 (TCP) Only the value 0 is permissible for the active side. 2 to 16, if connection type = 18 (ISO-on-TCP) 2, if connection type = 19 (UDP) 8 rem_subnet_id_len USINT 0 This parameter is not used. 9 rem_staddr_len USINT 4 Length of address of partner end point, in bytes: 0: unspecified, in other words, parameter rem_staddr is irrelevant. 4: valid IP address in the parameter rem_staddr (TCP and ISO-on-TCP only) 10 rem_tsap_id_len USINT 2 Length of parameter rem_tsap_id used, in bytes; possible values: 0 or 2, if connection type = 17 (TCP) Only the value 0 is permissible for the passive side. 2 to 16, if connection type = 18 (ISO-on-TCP) 0, if connection type = 19 (UDP) 11 next_staddr_len USINT 12 ... 27 local_tsap_id ARRAY [1..16] of BYTE 0 This parameter is not used. - Local address component of connection: TCP and UDP: local port no. (possible values: 1...49151; recommended values: 2000...5000); local_tsap_id[1] = high byte of port no. in hexadecimal notation; local_tsap_id[2] = low byte of port no. in hexadecimal notation; local_tsap_id[3-16] = irrelevant ISO-on-TCP: local TSAP-ID: local_tsap_id[1] = B#16#E0; local_tsap_id[2] = rack and slot of local end points (bits 0 to 4: Slot number, bits 5 to 7: rack number); local_tsap_id[3-16] = TSAP extension, optional Note: Make sure that every value of local_tsap_id is unique within the CPU. 490 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Byte Parameter Data type 28 ... 33 rem_subnet_id ARRAY [1..6] of USINT Start value - This parameter is not used. Description 34 ... 39 rem_staddr ARRAY [1..6] of USINT - TCP and ISO-on-TCP only: IP address of the partner end point, for example, for 192.168.002.003: rem_staddr[1] = 192 rem_staddr[2] = 168 rem_staddr[3] = 002 rem_staddr[4] = 003 rem_staddr[5-6]= irrelevant 40 ... 55 rem_tsap_id ARRAY [1..16] of BYTE - Partner address component of connection TCP: partner port no. (possible values: 1...49151; recommended values: 2000...5000); rem_tsap_id[1] = high byte of port no. in hexadecimal notation; rem_tsap_id[2] = low byte of port no. in hexadecimal notation; rem_tsap_id[3-16] = irrelevant ISO-on-TCP: partner TSAP-ID: rem_tsap_id[1] = B#16#E0; rem_tsap_id[2] = rack and slot of partner end point (bits 0 to 4: Slot number, bits 5 to 7: rack number); rem_tsap_id[3-16] = TSAP extension, optional UDP: This parameter is not used. 56 ... 61 next_staddr ARRAY [1..6] of BYTE 62 ... 63 spare WORD - W#16#0000 This parameter is not used. Reserved. Note TCON_Param for S7-1500 CPU The connection description DB with the structure according to TCON_Param is also supported by S7-1500 CPUs for migration reasons. However, we recommend that you use the new structures TCON_IP_v4 and TCON_IP_RFC. See also Principle of operation of connection-oriented protocols (Page 487) Description of the connection parameters (Page 479) Ability to read back connection description parameters (Page 495) Overview of connection configuration (Page 475) WinCC Basic V13.0 System Manual, 02/2014 491 Editing devices and networks 8.1 Configuring devices and networks TSAP structure (Page 497) Assignment of port numbers (Page 494) Connection parameters with structure according to TCON_IP_v4 Data block for connection description A connection description DB with a structure according to TCON_IP_v4 is used for CPUs of S7-1200 V4.0 and higher and S7-1500 to assign parameters for TCP and UDP communication connections. The fixed data structure of the TCON_IP_v4 contains all parameters that are required to establish the connection. The connection description DB is automatically created for a new connection by the connection configuration for Open User Communication when the TSEND_C, TRCV_C or TCON instruction is used. The CONNECT connection parameter of the instance DBs for TSEND_C, TRCV_C or TCON contains a reference to the data block used. Structure of the connection description according to TCON_IP_v4 Byte Data type Start value Description 0 ... 1 interface_id Parameter HW_ANY 64 Hardware identifier of the local interface (value range: 0 to 65535). 2 ... 3 id CONN_OUC 1 Reference to this connection (value range: 1 to 4095). You must specify the value of this parameter for the TSEND_C, TRCV_C or TCON instruction under ID. 4 connection_type BYTE 11 Connection type: 11: TCP 13: UDP 5 active_established BOOL TRUE Identifier for the type of connection establishment: FALSE: Passive connection establishment TRUE: Active connection establishment 6 ... 9 remote_address ARRAY [1..4] of BYTE - IP address of the partner end point, for example, for 192.168.0.1: addr[1] = 192 addr[2] = 168 addr[3] = 0 addr[4] = 1 10 ... 11 remote_port UINT 2000 Port address of the remote connection partner (value range: 1 to 49151). 12 ... 13 local_port UINT 2000 Port address of the local connection partner (value range: 1 to 49151). 492 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks See also Principle of operation of connection-oriented protocols (Page 487) Description of the connection parameters (Page 479) Ability to read back connection description parameters (Page 495) Overview of connection configuration (Page 475) Assignment of port numbers (Page 494) Connection parameters with structure according to TCON_IP_RFC Data block for connection description A connection description DB with a structure according to TCON_IP_RFC is used for CPUs of S7-1200 V4.0 and higher and S7-1500 to assign parameters to ISO-on-TCP communication connections. The fixed data structure of the TCON_IP_RFC contains all parameters that are required to establish the connection. The connection description DB is automatically created for a new connection by the connection configuration for Open User Communication when the TSEND_C, TRCV_C or TCON instruction is used. The CONNECT connection parameter of the instance DBs for TSEND_C, TRCV_C or TCON contains a reference to the data block used. Structure of the connection description according to TCON_IP_RFC Byte Data type Start value Description 0 ... 1 interface_id Parameter HW_ANY 64 Hardware identifier of the local interface (value range: 0 to 65535). 2 ... 3 id CONN_OUC 1 Reference to this connection (value range: 1 to 4095). You must specify the value of this parameter for the TSEND_C, TRCV_C or TCON instruction under ID. 4 connection_type BYTE 12 Connection type: ISO-on-TCP 5 active_established BOOL TRUE Identifier for the type of connection establishment: FALSE: Passive connection establishment TRUE: Active connection establishment 8... 11 remote_address ARRAY [1..4] of BYTE - IP address of the partner end point, for example, for 192.168.0.1: addr[1] = 192 addr[2] = 168 addr[3] = 0 addr[4] = 1 WinCC Basic V13.0 System Manual, 02/2014 493 Editing devices and networks 8.1 Configuring devices and networks Byte Parameter Data type Start value Description 12 ... 45 remote_tselector TSelector - TSelector of the remote connection partner: TSelLength = Value range 0 to 32 as UINT TSel[1-32] = Value range each 0 to 255 in bytes 46 ... 79 local_tselector TSelector - TSelector of the local connection partner: TSelLength = Value range 0 to 32 as UINT TSel[1-32] = Value range each 0 to 255 in bytes See also Principle of operation of connection-oriented protocols (Page 487) Description of the connection parameters (Page 479) Ability to read back connection description parameters (Page 495) Overview of connection configuration (Page 475) TSAP structure (Page 497) Assignment of port numbers Introduction When an Open User Communication is created, the value 2000 is automatically assigned as the port number. Permissible values for port numbers are 1 to 49151. You can assign any port number within this range. However, because some ports may already be used depending on the system, port numbers within the range from 2000 to 5000 are recommended. Note Port numbers must be unique. The connection configuration or a corresponding block call is rejected with an error if the port numbers are assigned twice. Overview of port numbers The following table summarizes the system reactions to various port numbers. Port no. Description System reaction 2000 ... 5000 Recommended range No warning, no error message on entry Port number is permitted and accepted 1 ... 1999, 5001 ... 49151 494 Can be used, but is outside the recommended range Warning message on entry Port number is permitted and accepted WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Port no. Description 0, 20, 21, 25, 80, 102, 135, 161, 34962 ... 34964 Can be used conditionally* 53, 80, 102, 135, 161, 162, 443, 520, 9001, 34962 ... 34964 Can be used conditionally** System reaction * Ports defined for specific functions: 0: ANY - Port number is automatically assigned by S7-1500 CPU as value (>49151) 20: FTP data transmission 21: FTP control 25: TMAIL_C (Simple Mail transfer protocol) 80: Web server 102: ISO-on-TCP (RFC1006) 135: DCE Endpoint Mapper for PROFINET 161: SNMP (Simple Network Management Protocol) 34962 ... 34964: PROFINET Note The user usually specifies the value 0 for the local port on the active connection end point for UDP/TCP. In this case, the CPU operating system selects the next available port above 49151. The partner port usually has the default 0 with the passive connection end point. The corresponding parameter is disabled in the connection configuration. ** These ports are disabled depending on the function scope of the CPU in use. The documentation of the respective CPUs provides the assignment of these ports. See also Description of the connection parameters (Page 479) Creating and assigning parameters to connections (Page 483) Ability to read back connection description parameters Changing parameter values in the connection description The connection description for exactly one connection of the Open User Communication is entered from the connection configuration in the connection description DB. You can change the parameter values of the connection description DB outside of the connection configuration in the user program. Connection description DBs containing values you changed subsequently can be read back from the connection configuration. Under WinCC Basic V13.0 System Manual, 02/2014 495 Editing devices and networks 8.1 Configuring devices and networks "Properties > Configuration > Connection parameters", the inspector window displays only the connection parameters stored in the connection description DB. Note You can only change the values in the running user program if the instructions TCON, TSEND_C or TRCV_C are not being processed and the referenced connection is not established. The connection configuration does not support nested entries of connection descriptions in DB types that can only be found via offset referencing (for example, Global-DB). The structure of the connection description cannot be changed. Ability to read back individual connection parameters For the "Address" parameter of the communication partner in a TCP or ISO-on-TCP connection, its IP address is displayed from the "rem_staddr" parameter of the connection description. The following values can also be reloaded from the connection description: Connection type Local connection ID Active/passive connection establishment (only with UDP) Local TSAP (ISO-on-TCP only) Partner TSAP (ISO-on-TCP only) Local port (only with TCP and UDP) Partner port (only with TCP) The values of the connection ID parameters of the communication partner, the connection data, as well as the connection establishment, are not included in the connection description in the local connection description DB. Consequently, these parameters cannot be displayed when the connection configuration is reopened. The connection establishment of the partner results from the local connection establishment and is therefore also displayed. A new communication partner can be selected at any time in the "Partners" drop-down list box. When a CPU recognized in the project is selected as a specified communication partner, the entry options for the connection ID and the connection data are shown again. See also Connection parameters with structure according to TCON_Param (Page 489) Description of the connection parameters (Page 479) 496 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks TSAP structure Introduction For an ISO-on-TCP connection, Transport Service Access Points (TSAPs) must be assigned for both communication partners. TSAP IDs are assigned automatically after an ISO-on-TCP connection is created. To ensure the uniqueness of TSAP IDs within a device, you can change the preassigned TSAPs in the connection parameter assignment. Structure of TSAPs You must comply with certain rules when assigning TSAPs. A TSAP must contain a certain number of bytes, which are able to be displayed and entered as hexadecimal values (TSAPID) or as ASCII characters (ASCII-TSAP): $6&,,76$3 76$3 $6&,, ,62RQ7&3 $6&,,FKDUDFWHUV 76$3,' ))(' +H[YDOXHV 76$3,' Entries or changes of the TSAP-ID or the ASCII-TSAP in the corresponding entry fields always take effect in the other display format as well. If a TSAP contains no valid ASCII characters, the TSAP is displayed only as TSAP-ID and not as ASCII-TSAP. This is the case after a connection is created. The first two hex characters as TSAP-ID identify the communication type and the rack/slot. Because these characters are not valid ASCII characters for a CPU, the ASCII-TSAP is not displayed in this case. $6&,,76$3QRWSUHVHQW 76$3,'FRQWDLQVLQYDOLG$6&,,FKDUDFWHUV $6&,,FKDUDFWHUV 76$3 $6&,, 76$3,' ())(' 76$3,' +H[YDOXHV 76$3H[WHQVLRQ FRPSOHWH76$3,' In addition to the rules for length and structure of TSAPs, you must also ensure the uniqueness of the TSAP-ID. The assigned TSAPs are not automatically unique. WinCC Basic V13.0 System Manual, 02/2014 497 Editing devices and networks 8.1 Configuring devices and networks Length and content of TSAPs A TSAP is structured as follows: TSAP-ID with TSAP extension Length = 2 to 16 bytes x_tsap_id[0] = 0xE0 (Open User Communication) x_tsap_id[1] (bits 0 to 4) = slot number of CPU x_tsap_id[1] (bits 5 to 7) = rack number of CPU x_tsap_id[2...15] = any characters (TSAP extension, optional) (x = loc (local) or x = rem (partner)) TSAP-ID as ASCII-TSAP Length = 3 to 16 bytes x_tsap_id[0 to 2] = 3 ASCII characters (0x20 to 0x7E) x_tsap_id[3...15] = any characters (optional) (x = loc (local) or x = rem (partner)) The following table shows the schematic structure of a TSAP-ID: TSAP-ID tsap_id_len tsap_id[0] tsap_id[1] tsap_id[2..15] tsap_id[3..15] ...with extension 2...16 bytes 0xE0 0x01 or 0x02 or 0x00* Extension (optional) Extension (optional) ...as ASCII-TSAP 3...16 bytes 0x20...0x7E 0x20...0x7E 0x20...0x7 Any (optional) *An S7-1200/1500 CPU is normally inserted on rack 0 and slot 1, and an S7-300/400 CPU on rack 0 and slot 2. For this reason, hex value 01 or 02 is valid for the second position of the TSAP-ID with extension. If the connection partner is an unspecified CPU, for example, a thirdparty device, the hex value 00 is also permissible for the slot address. Note For unspecified communication partners, the local TSAP-ID and the partner TSAP-ID can have a length of 0 to 16 bytes, in which all hex values from 00 to FF are permitted. ASCII code table for entry of ASCII TSAPs For entry of an ASCII-TSAP in the connection parameter assignment, only hexadecimal values from 20 to 7E are permitted: Code ..0 ..1 3.. 0 4.. @ 5.. P 6.. 7.. p 2.. 498 ..2 ..3 ..4 ..5 ..6 ..7 ..8 ..9 ..A ..B ! " # $ % & ' 1 2 3 4 5 6 7 A B C D E F G H Q R S T U V W X a b c d e f g h q r s t u v w x ..C ..D ..E ..F ( ) * + , - . / 8 9 : ; < = > ? I J K L M N O Y Z [ \ ] ^ _ i j k l m n o y z { | } ~ WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks See also Examples of TSAP assignment (Page 499) Description of the connection parameters (Page 479) Creating and assigning parameters to connections (Page 483) Examples of TSAP assignment The following examples show the processing of the TSAPs for CPUs of the S7-1200/1500 (CPU on slot 1) under various points of view: Example 1: Creating a new connection for PLC-PLC communication Example 2: Entry of a local ASCII-TSAP Example 3: Entry of a TSAP extension in the TSAP-ID Example 4: Incorrect editing of the TSAP-ID Example 5: Entry of an ASCII-TSAP via the "TSAP-ID" entry field Example 1: Creating a new connection for PLC-PLC communication Once you have created a new connection with two PLCs for the Open User Communication, the TSAP extension "ISOonTCP-1" is assigned automatically. This TSAP extension produces the TSAP-ID E0.01.49.53.4F.6F.6E.54.43.50.2D.31, which is entered automatically in the connection description DB and in the entry fields of the local and the partner TSAP. The entry fields of the ASCII-TSAPs remain empty: Local TSAP Partner TSAP E0.01.49.53.4F.6F.6E.54.43.50.2D.31 E0.01.49.53.4F.6F.6E.54.43.50.2D.31 TSAP (ASCII) TSAP-ID You can change the values in the entry fields of the TSAP-ID and the ASCII-TSAP at any time. The entry field of the TSAP-ID shows the complete TSAP stored in the data block of the connection description. The TSAP-ID with TSAP extension, which is limited to 16 characters, is not displayed in the "TSAP (ASCII)" entry field because the character E0 does not represent a valid character for the ASCII-TSAP. If the displayed TSAP-ID is a valid ASCII-TSAP, it is displayed in the "TSAP (ASCII)" entry field. Changes in the entry fields for TSAP-ID and ASCII-TSAP affect the other field. Example 2: Entry of a local ASCII-TSAP If you have created a new connection and assigned an ASCII value for the local TSAP in the "TSAP (ASCII)" entry field, for example, "ISOonTCP-1", the resulting TSAP-ID is created automatically. When you exit the "TSAP (ASCII)" entry field, the number of ASCII characters is checked automatically for compliance with the limit (3 to 16 characters) and the resulting TSAP-ID is entered into the corresponding entry field: WinCC Basic V13.0 System Manual, 02/2014 499 Editing devices and networks 8.1 Configuring devices and networks Local TSAP TSAP (ASCII) ISOonTCP-1 TSAP-ID 49.53.4F.6F.6E.54.43.50.2D.31 Partner TSAP E0.01.49.53.4F.6F.6E.54.43.50.2D.31 Example 3: Entry of a TSAP extension in the TSAP-ID If, following creation of a connection and entry of an ASCII-TSAP (see examples 1 and 2) in the entry field of the local TSAP-ID, you add the prefix "E0.01" to the TSAP value, the ASCIITSAP will no longer be displayed when the entry field is exited. Local TSAP Partner TSAP E0.01.49.53.4F.6F.6E.54.43.50.2D.31 E0.01.49.53.4F.6F.6E.54.43.50.2D.31 TSAP (ASCII) TSAP-ID Once you have exited the entry field of the TSAP-ID, a check is performed automatically to determine whether the first character of the TSAP-ID is a valid ASCII character. Since the character "E0" now present in the TSAP-ID is not a valid character for the ASCII-TSAP, the "TSAP (ASCII)" entry field no longer displays an ASCII-TSAP. If a valid ASCII character is used, the check for compliance with the length specification of 2 to 16 characters follows. Example 4: Incorrect editing of the TSAP-ID If you remove the hex value "E0" from a TSAP-ID beginning with "E0.01", the TSAP-ID now begins with "01" and therefore no longer complies with the rules and is invalid: Local TSAP Partner TSAP 01.49.53.4F.6F.6E.54.43.50.2D.31 E0.01.49.53.4F.6F.6E.54.43.50.2D.31 TSAP (ASCII) TSAP-ID After the entry field is exited, a message is output because the TSAP-ID is neither a valid ASCIITSAP (this would have to have a hex value in the range from 20 to 7E as the first value) or a valid TSAP-ID (this would have to have the identifier "E0" as the first value). Example 5: Entry of an ASCII-TSAP via the "TSAP-ID" entry field If you remove the value "01" in addition to the value "E0" from the incorrect TSAP-ID in example 4, the TSAP-ID begins with the hex value 49. This value is within the permissible range for ASCII-TSAPs: Local TSAP Partner TSAP 49.53.4F.6F.6E.54.43.50.2D.31 E0.01.49.53.4F.6F.6E.54.43.50.2D.31 TSAP (ASCII) TSAP-ID When you exit the entry field, the TSAP-ID is recognized as a valid ASCII-TSAP and the resulting ASCII-TSAP "ISOonTCP-1" is written to the "TSAP (ASCII)" entry field. 500 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks See also TSAP structure (Page 497) Description of the connection parameters (Page 479) Communication via PUT and GET instructions Basic information on communication via the PUT/GET instruction Basic information on PUT/GET instructions Use PUT and GET instructions to exchange data between two CPUs via an S7 connection. The GET instruction is used to read data from a partner CPU. The PUT instruction is used to control the writing of tags by the communication partner via the user program. Apart from the PUT and GET instructions, no additional communication functions are provided for reading and writing tags. To simplify the use of the two instructions, specify all required parameters for the connection and all block parameters in the Inspector window of the program editor. Requirement To be able to use the PUT and GET instructions, the following requirements must be satisfied: At least one S7-1200/1500 CPU or S7-300/400 CPU must be created in the project. Firmware 2.0 or higher must be installed on an S7-1200 CPU. If you have not yet created a second CPU in the project, you can initially establish the connection to an unspecified partner. An S7 connection must exist between the two CPUs. If you have not yet established a connection between two CPUs, a connection is automatically established during the configuration of the instructions. For both instructions, an instance data block is required in which all data used by the instruction is stored. The instance data block is created automatically as soon as you drag a PUT or GET instruction to a network in the program editor. For the correct execution of the program, it is essential that the instance data blocks are not changed; consequently, these data blocks are know-how protected. You only have read access to the instance data blocks. See also Overview of connection configuration (Page 502) Assigning parameters to start request (Page 507) PUT: Set parameters for write and send area (Page 508) GET: Set parameters for read and memory area (Page 509) WinCC Basic V13.0 System Manual, 02/2014 501 Editing devices and networks 8.1 Configuring devices and networks Connection configuration Overview of connection configuration Introduction The connection parameters for the PUT and GET instructions are assigned in the inspector window of the program editor. All parameters are saved in the corresponding instance data block. 502 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Structure of the connection configuration The connection configuration is made up of the following components: Communication instruction for PUT or GET Call of online and diagnostic functions "Configuration" tab in the "Properties" tab Area navigation of the "Configuration" tab General properties of the connection parameters Display of online and diagnostic functions If you click the icon for starting the online and diagnostic functions, the associated CPU goes online automatically. The connection table in the network view is opened. In addition, the "Diagnostics" tab and the connection information are displayed in the inspector window. WinCC Basic V13.0 System Manual, 02/2014 503 Editing devices and networks 8.1 Configuring devices and networks Entering the connection parameters Enter the desired connection parameters in the "Configuration" tab. The area navigation of the "Configuration" tab includes the "Connection parameters" group. This group contains the connection configuration. Here, you can enter the parameters for the connections using system functions. When all the required parameters are assigned, a check mark is set behind the "Connection parameters" group in the area navigation. See also Assigning parameters to start request (Page 507) PUT: Set parameters for write and send area (Page 508) GET: Set parameters for read and memory area (Page 509) Description of the connection parameters Overview The following table shows the general connection parameters: Parameter Description End point The names of the local end point and the partner end point are shown. Local end point The local end point is the CPU in which the PUT or GET instruction is programmed. Partner end point The partner end point is selected from the drop-down list. The drop-down list shows all available possible connection partners including unspecified connection partners for devices whose data is unknown in the project. As long as no connection partner is set, all other parameters in the mask are disabled. Interface The interface of the partner CPU is displayed. The partner interface is not displayed until a specified partner CPU has been selected. Interface type The type of interface via which communication is handled is displayed. Subnet name The subnet of the local end point is displayed, provided this exists. The partner subnet is displayed only after the partner end point has been selected. If at least one of the two connection partners is not connected with a subnet, the two connection partners are automatically connected with each other. The partner which is not connected to a network is hereby connected to the same subnet via which the other partner is already connected to a network. A connection of connection partners to different subnets is only possible with IP or S7 routing. The IP routing settings can be edited in the properties of the relevant Ethernet interfaces. Address The IP address of the local end point is displayed. The IP address of the partner is displayed only after the partner end point has been selected. If you have selected an unspecified connection partner, the input box is empty and has a red background. In this case, you will need to specify a valid IP address for the connection partner. Connection ID 504 The currently set connection ID is displayed. You can change the connection ID in the connection table in the network view. You can also directly access the connection table while you are setting the connection parameters. To do this, click the "Create new connection" icon. WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Parameter Description Connection name The name of the connection which was automatically created when the PUT/GET instruction was inserted is displayed. You can change the name of the connection by entered a different name in the field. You can also create a new connection or edit existing connections by clicking the "Create new connection" icon. Active connection establishment Use the "Active connection establishment" option button to specify which partner starts the communication. When the connection is created, the local partner is initially specified by default for the establishment of the connection. If a device does not support active connection establishment, you have to activate active connection establishment on the other partner. Configured at one end If this check box is selected, the connection partner is the server for this connection. It cannot actively send or receive. This corresponds to the behavior of the PUT/GET instructions. In this case, other instructions are not possible. If the check box is not selected, other instructions can also be used for the communication. Starting connection parameter assignment You can assign the connection parameters for PUT and GET in the inspector window as soon as you have inserted and selected a PUT or GET instruction in a program block. Procedure To insert PUT/GET instructions, follow these steps: 1. Open the "Instructions" task card in the "Communication > S7 Communication" folder. 2. Drag a PUT or GET instruction to a network. The "Call options" dialog opens. 3. Optional: Edit the properties of the instance DB in the "Call properties" dialog. You have the following options: - Change the default name. - Select the "Manual" check box to assign your own number. 4. Click "OK". Result A corresponding instance data block is created for the inserted PUT or GET instruction. For S7-300 CPUs, a function block is also created in the program resources. When PUT or GET instruction is selected, you will see the "Configuration" tab under "Properties" in the inspector window. The "Connection parameters" group in area navigation contains the connection parameter assignment that you can now make. See also Creating and assigning parameters to connections (Page 506) Deleting connections (Page 507) WinCC Basic V13.0 System Manual, 02/2014 505 Editing devices and networks 8.1 Configuring devices and networks Creating and assigning parameters to connections You can create S7 connections and assign the parameters for these in the connection parameter assignment of the PUT/GET instructions. Changed values are checked immediately by the connection parameter assignment for input errors. Requirement A CPU exists with a PUT or GET communication instruction. Procedure To configure an S7 connection using PUT/GET instructions, follow these steps: 1. In the program editor, select the call of the PUT or GET instruction. 2. Open the "Properties > Configuration" tab in the inspector window. 3. Select the "Connection parameters" group. Until you select a connection partner, only the empty drop-down list for the partner end point is enabled. All other input options are disabled. The connection parameters already known are displayed: - Name of the local end point - Interface of the local end point - IP address of the local end point 4. In the drop-down list box of the partner end point, select a connection partner. You can select an unspecified device or a CPU in the project as the communications partner. The following parameters are automatically entered as soon as you have selected the connection partner: - Interface of the partner end point - Interface of the partner end point. If several interfaces are available, you can change the interface as required. - Interface type of the partner end point - Subnet name of both end points - IP address of the partner end point - Name of the connection which is used for the communication. If no connection exists yet, it is automatically established. 5. If required, change the connection name in the "Connection name" input box. If you want to create a new connection or edit an existing connection, click on the "Create new connection" icon. Note The PUT and GET instructions between two communication partners can only run if both the hardware configuration and the program part for the partner end point have been loaded into the hardware. To achieve fully functional communication, make sure that you load not only the connection description of the local CPU on the device but also that of the partner CPU as well. 506 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Deleting connections A connection which was automatically created during the insertion of a PUT or GET instruction appears in the connection table of the network view like every standard connection. As a result, it can be deleted in the connection table. Procedure To delete a connection, follow these steps: 1. Open the connection table in the network view. 2. In the connection table, select the connection that you want to delete. 3. To do this, right-click the connection and select the "Delete" command from the shortcut menu. Result The connection is deleted. The PUT or GET instruction and the associated instance data blocks are retained and must be manually deleted if necessary. To continue using the PUT or GET instruction, you must configure the connection again in the inspector window of the program editor, since all connection parameters were also deleted when the connection was deleted. In this case, specify a new communication partner and a suitable connection. Block parameter assignment Assigning parameters to start request To start communication via the PUT or GET instruction, you have to specify an event which activates the instruction. This event is referred to as control parameter (REQ). The communication job is activated as soon as there is a positive edge at the control parameter REQ. Please note that the control parameter REQ is assigned the default FALSE at first call. Requirement The program editor is open. You have already inserted a PUT or GET instruction. A connection has been established between two communication partners. Procedure To define the REQ control parameter, follow these steps: 1. Select the PUT or GET instruction in the program editor. 2. Open the "Configuration" tab in the inspector window. WinCC Basic V13.0 System Manual, 02/2014 507 Editing devices and networks 8.1 Configuring devices and networks 3. Select the "Block parameter assignment" entry in the area navigation. 4. In the "REQ" field, select a tag of the "BOOL" data type to initialize the execution of the instruction. Alternatively, you can also interconnect a previous instruction in the program editor. See also PUT: Set parameters for write and send area (Page 508) GET: Set parameters for read and memory area (Page 509) PUT: Set parameters for write and send area For communication via the PUT instruction, you must specify the memory area of the partner CPU to which the data should be written. In addition, you must specify the memory area of the local CPU from which the data is to be read. Requirement The program editor is open. You have already inserted a PUT instruction. A connection has been established between two communication partners. Procedure To specify the read and the memory area for the instruction, follow these steps: 1. Select the PUT instruction in the program editor. 2. Open the "Configuration" tab in the inspector window. 3. Select the "Block parameter assignment" entry in the area navigation. 4. In the "In/Outputs > Write area (ADDR_1) > Start" field, select a "REMOTE" data type pointer to the area of the partner CPU which is to be written. Only absolute addressing is permitted. Example: P#DB10.DBX5.0 Byte 10 5. In the "Length" field, enter the length of the write area and select the data type of the memory area from the drop-down list. 6. In the "In/Outputs > Send area (SD_1) > Start" field, select a pointer to the area in the local CPU which contains the data to be sent. 7. In the Length field, enter the length of the memory area to be read and select the data type from the drop-down list. Only the data types BOOL (for a bit array, "0" must be used as address and an integer multiple of byte must be used as length), BYTE, CHAR, WORD, INT, DWORD, DINT, REAL, COUNTER, TIMER are permitted. If the VARIANT pointer accesses a DB, the DB must always be specified (for example: P#DB10.DBX5.0 Byte 10). 508 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks See also GET: Set parameters for read and memory area (Page 509) GET: Set parameters for read and memory area For communication via the GET instruction, you must specify the memory area of the local CPU to which the data should be written. In addition, you must specify the memory area of the partner CPU from which the data is to be read. Requirement The program editor is open. You have already inserted a GET instruction. A connection has been established between two communication partners. Procedure To specify the read and the memory area for the instruction, follow these steps: 1. Select the GET instruction in the program editor. 2. Open the "Configuration" tab in the inspector window. 3. Select the "Block parameter assignment" entry in the area navigation. 4. In the "In/Outputs > Read area (ADDR_1) > Start" field, select a "REMOTE" data type pointer to the area of the partner CPU which is to be read. Only absolute addressing is permitted. Example: P#DB10.DBX5.0 Byte 10 5. In the "Length" field, enter the length of the read area and select the data type of the memory area from the drop-down list. 6. In the "In/Outputs > Memory area (RD_1) > Start" field, select a pointer to the area in the local CPU in which the read data is to be stored. 7. In the Length field, enter the length of the memory area and select the data type from the drop-down list. Only the data types BOOL (for a bit array, "0" must be used as address and an integer multiple of byte must be used as length), BYTE, CHAR, WORD, INT, DWORD, DINT, REAL, COUNTER, TIMER are permitted. See also PUT: Set parameters for write and send area (Page 508) WinCC Basic V13.0 System Manual, 02/2014 509 Editing devices and networks 8.1 Configuring devices and networks 8.1.3.3 Displaying and configuring topology Overview of the topology view Functions of the topology view The topology view is one of three working areas of the hardware and network editor. You undertake the following tasks here: Displaying the Ethernet topology - Displaying all the PROFINET devices and passive Ethernet components of the project along with their ports - Displaying interconnections between the ports - Displaying corresponding logical networks - Display diagnostic information of all ports Configuring the Ethernet topology - Creating, modifying and deleting interconnections of the ports - Renaming stations, devices, interfaces or ports - Adding PROFINET devices and passive Ethernet components to the project from the hardware catalog Identifying and minimizing differences between the desired and actual topology - Running an offline/online comparison of Ethernet modules, ports and port interconnections - Adopting existing online topology information in the offline project Note Devices without valid IP address Topology information (LLDP) cannot be read from a device without valid IP address. To prevent devices from having an invalid IP address, specify in the settings of the TIA Portal for hardware configuration that devices without valid IP address are temporarily assigned an IP address. 510 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Differences between network view and topology view The network view shows all the logical subnets of the project. The topology view shows all Ethernet components of the project. These include passive components such as switches, media converters and cables. Note Stations with non-Ethernet components are also displayed if the station has a least one Ethernet component. The position of a device in the network view and its position in the topology view are not dependent on each other; in other words, the same device generally appears at different locations in the two views. If you open the hardware catalog in the topology view, you only see devices with an Ethernet interface. Structure of the topology view The topology view (Page 392) essentially consists of a graphic area (called the graphic view below) and a table area (called the table view below). Which functions are there in the graphic view and which functions are there in the table view? Displaying the Ethernet topology Function Graphic view Table view Displaying all the PROFINET devices and passive Ethernet components of the project along with their ports yes yes Display interconnections between the ports (including type of medium) yes yes Displaying corresponding logical networks no yes Displaying properties of the cables between the ports no yes Display diagnostic information of all ports yes yes Function Graphic view Table view Creating, modifying and deleting interconnections of the ports Create: yes Create: yes Modify: no Modify: yes Delete: yes Delete: yes Renaming stations, devices, interfaces or ports no yes Adding PROFINET devices and passive Ethernet components to the project from the hardware catalog yes no Configuring the Ethernet topology WinCC Basic V13.0 System Manual, 02/2014 511 Editing devices and networks 8.1 Configuring devices and networks Identifying and minimizing differences between the desired and actual topology Function Graphic view Table view Running an offline/online comparison of Ethernet modules, ports and port interconnections no yes Adopting existing online topology information in the offline project no yes See also Overview of settings for hardware configuration (Page 393) Starting the topology view Requirement The device or network view is open in the hardware and network editor. Procedure To start the topology view of your project, follow these steps: 1. Click on the "Topology view" tab. Or: 1. Open the network view of the hardware editor. 2. Select a PROFINET device or a PROFINET module. 3. Select the "Go to topology view" command in the shortcut menu. Result The graphic view of the topology view is started. If you opened the topology view using the shortcut menu, the selected component remains selected after the change of view. Displaying topology Displaying the graphic view of the configured topology What is shown? The graphic view of the configured topology shows the following: Configured PROFINET devices and passive Ethernet components along with their ports Configured stations with non-Ethernet components if there is at least one Ethernet component in the station Configured interconnections between the ports 512 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Type of display The way in which the graphic view of the topology view and the network view are displayed is very similar: Compared with the device view, components are shown in a simplified form. The interconnections between ports are shown as horizontal and vertical lines. These are dashed when an interconnection between a tool changer port and its possible partner ports is involved. Displaying the table view of the configured topology What is shown? The table view of the configured topology shows exactly the same content as the graphic view except for the logical PROFINET subnets. All the configured PROFINET devices and passive Ethernet components along with their ports All the configured stations with non-Ethernet components if there is at least one Ethernet component in the station Configured interconnections between the ports For each port with the "Alternating partner port" property, there are as many completed rows as there are potential partner ports plus one empty row. Type of display As the name implies, the table view of the topology view consists of a table, the topology overview table. It is structured like the network overview table. It consists of the following columns: Device / port This is the most important column of the table. The entries in this column have a hierarchical structure with the PROFINET ports being the last element in the hierarchy. You can expand and collapse the hierarchical entries. For a CPU, for example, an entry consists of the following elements: - Station name - Device name - Name of the PROFINET interface - Names of the ports Note: All the other columns only have entries in the rows containing the port names. Type (as default, this column is not displayed) Shows what type of station, device or interface the table row relates to or whether it belongs to a port. Order no. (as default, this column is not displayed) Order no. of device WinCC Basic V13.0 System Manual, 02/2014 513 Editing devices and networks 8.1 Configuring devices and networks Subnet (as default, this column is not displayed) Configured subnet to which the interface belongs Master / IO system (as default, this column is not displayed) Shows whether or not the interface belongs to a PROFIBUS DP master system or a PROFINET IO system. Device address (as default, this column is not displayed) Configured address of the interface in the subnet Partner station Name of the station that contains the partner port Partner device Name of the device that contains the partner port Partner interface Interface to which the partner port belongs Partner port Cable data Contains the cable length and the signal delay of the cable connecting the ports Basic functions for tables The topology overview table supports the following basic functions for editing a table: Displaying and hiding table columns Note: The columns that define the configuration cannot be hidden. Optimizing column width Displaying the meaning of a column, a row or cell using tooltips. Displaying the diagnostics status of ports and cables in the graphic view Requirements The graphic view of the topology view is open. 514 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Procedure To determine the diagnostics status of the port, follow these steps: 1. Go online with the required component or components. Result The following icons are displayed: The corresponding diagnostics icon is displayed for each device. If there is an error in at least one lower-level component, the diagnostics icon "Error in lowerlevel component" is also displayed in the left-hand lower corner of the diagnostics icon. The corresponding diagnostics icon is displayed for each port. Every cable between two ports that are online has the color that matches its diagnostics status. You will find the possible diagnostics icons for ports and the color coding of Ethernet cables in the description of hardware diagnostics. See: Displaying diagnostics status and comparison status using icons (Page 1087) Showing the diagnostics status of hardware components in the table view Requirement The table view of the topology view is open. Procedure To obtain the diagnostics status of hardware components of the topology overview table, follow these steps: 1. Go online with the required components. Result The following icons are displayed at the left-hand edge of the topology overview table in each row that belongs to the component involved: The diagnostics icon belonging to the hardware component is displayed. If the hardware component has lower-level components and if there is an error in at least one of the lower-level components, the diagnostics icon "Error in lower-level component" is also displayed in the left-hand lower corner of the diagnostics icon of the hardware component. WinCC Basic V13.0 System Manual, 02/2014 515 Editing devices and networks 8.1 Configuring devices and networks For the possible diagnostics icons for hardware components, refer to the description of hardware diagnostics. See: Displaying diagnostics status and comparison status using icons (Page 1087) Note The display of the diagnostics status of hardware components in the topology overview table and the network overview table is identical. Running an offline/online comparison and displaying the results Requirement The topology view is open. There may be an online connection to one or more devices, but this is not actually necessary. Procedure To find the differences between the configured and the actual topology, follow these steps: 1. Click the "Offline/online comparison" button in the toolbar of the topology overview. Result The "Partner station", "Partner interface" and "Cable data" columns in the topology overview table are removed. Two additional groups of columns are added to the right-hand side of the table and these are initially empty: On the far right, columns for the topology to be identified online are added. Between the columns for the offline and the online topology, the "Status", "Action" and "Description" columns are added to show the result of the offline/online comparison. Note As default, the "Description" column is not displayed. The following buttons are enabled in the toolbar of the table: Button Name Meaning Update The detection of the existing online topology is started again. Synchronize Adopting the port interconnections identified online in the project (Page 525) Adopt the devices identified online in the project (Page 526) 516 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks After the actual topology has been identified, the added columns are filled. These steps are described in more detail in the following section. Note A difference between offline and online view is displayed for that port connected with the PG/ PC which is only available online. This is because the PG/PC cannot be configured offline. Columns for the topology identified online The following columns are displayed: "Device / port" "Type" (as default, this column is not displayed) "Order no." (as default, this column is not displayed) "IP address" (as default, this column is not displayed) "Partner device" "Partner port" "Cable data" Columns for the result of the offline/online comparison The following columns are displayed: "Status" The result of the offline/online comparison is shown here in the form of diagnostics icons. The following icons are possible: Diagnostics icon Meaning Differing topology information in at least one lower-level component Identical topology information Topology information only available offline or device is disabled. Topology information only exists online Differing topology information If a device does not support topology functions, the "Status" column remains empty. WinCC Basic V13.0 System Manual, 02/2014 517 Editing devices and networks 8.1 Configuring devices and networks "Action" The possible actions are shown here in the form of icons. The following icons are possible: Icon Meaning No action possible Adopt the interconnection found online "Description" This column describes the selected action in words. Configuring topology Interconnecting ports Overview Interconnecting ports in the topology view In the topology view, you have the following options for interconnecting ports: in the graphic view (Page 519) in the graphic view of a tool changer (Page 521) in the table view (Page 520) in the table view of a tool changer (Page 521) by adopting port interconnections identified online (Page 525) What effects does the interconnection of ports have on the network view? Note In the properties of a subnet in the network view, you can specify that this subnet is used when a port interconnection is created between two devices that are not networked. When you create an interconnection between two ports, the following effects are possible in the network view: If the corresponding interfaces are not networked: If you have specified a default subnet, this is used. Otherwise a new subnet is created to connect the two interfaces. If one (and only one) of the two interfaces involved is networked: The non-networked interface is connected to the same subnet as the already networked interface. In all other cases: The corresponding interfaces are not connected to a logical subnet. 518 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks See also Interconnecting ports (Page 920) Settings for interconnecting Ethernet devices (Page 446) Interconnecting ports in the graphic view Requirement You are in the graphic view of the topology view. Procedure - Creating a new interconnection between two ports To interconnect a port of a device with a port of another device, follow these steps: 1. Place the mouse cursor on the port you want to interconnect. 2. Click with the left mouse button and hold it down. 3. Move the mouse pointer. The pointer now shows the networking symbol to indicate "Interconnect" mode. At the same time, the mouse pointer shows the lock symbol that will only disappear when the pointer is on a valid target. 4. Now drag the mouse cursor to the target port. You can do this while holding down or after releasing the mouse button. 5. Now release the left mouse button or press it again (depending on your previous action). Result: A new port interconnection is created. Note Creating a ring for S7-300, S7-400, and S7-1500 CPUs If you create a ring using port interconnections for S7-300, S7-400, or S7-1500 CPUs, an MRP domain is created automatically. Procedure - Changing an existing port interconnection without deleting it first To do this, follow these steps: 1. Place the mouse cursor on the port of an existing interconnection that is to receive a new partner port. 2. Drag the port to the new partner port. Result: The existing port interconnection is deleted. The new port interconnection is created. Alternative procedure: 1. Place the mouse cursor on a port without an interconnection that is to be connected with an already interconnected port. 2. Drag the port to the already interconnected port. WinCC Basic V13.0 System Manual, 02/2014 519 Editing devices and networks 8.1 Configuring devices and networks Result: The existing port interconnection is deleted. The new port interconnection is created. Procedure - Interconnecting two interconnected ports with each other without first deleting the two existing port interconnections To do this, follow these steps: 1. Place the mouse cursor on the interconnected port that is to receive a new partner port. 2. Drag the port to the new partner port that is also interconnected already. Result: The two existing port interconnections are deleted. The new port interconnection is created. Interconnecting ports in the table view Which actions are possible with port interconnections in the table view? The following actions are possible with port interconnections in the table view: Creating a new port interconnection Changing an existing port interconnection Deleting an existing port interconnection Requirement The row with the port whose interconnection you want to create, modify or delete is visible in the topology overview. Procedure To create the interconnection of a port for the first time, to modify it or delete it, follow these steps: 1. Move the mouse pointer to the "Partner port" column in the row of the source port. 2. Click the drop-down list there. 3. Select the required partner port (when creating or changing a port interconnection) or the "Not interconnected" entry (when deleting a port interconnection). Result The required action is performed. The new partner port (after creating or modifying a port interconnection) or the "Select port" entry (after deleting a port interconnection) is displayed in the "Partner port" column. 520 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Interconnecting a port with more than one partner port in the graphic view Requirement You have configured a port of a PROFINET device with the "Alternative partners" property and have specified its possible partner ports. The graphic view of the topology view is open. Procedure 1. Interconnect this port (referred to hereafter as source port) with one of the partner ports you have specified (referred to hereafter as target port). 2. Interconnect the source port with an additional target port. You can do this in several ways: - Drag the mouse pointer from a partner port that is already interconnected to a target port. - Drag the mouse pointer from an interconnection that has already been created to a target port. - Drag the mouse pointer from a target port to a partner port that is already interconnected. - Drag the mouse pointer from a target port to an already created interconnection. 3. If necessary, repeat the step above one or more times. Result An interconnection is created between the source port and the alternative partner ports. This is indicated by a dashed line. Interconnecting a port with more than one partner port in the table view Which actions are possible with port interconnections to several partner ports in the table view? When working with a tool changer, the following actions can be performed with port interconnections to multiple partner ports in the table view: Creating a new port interconnection Changing an existing port interconnection Deleting an existing port interconnection Requirement You have configured a port of a PROFINET device with the "Alternative partners" property and have specified its possible partner ports. The row with the port whose interconnection you want to create, modify or delete is visible in the topology overview. WinCC Basic V13.0 System Manual, 02/2014 521 Editing devices and networks 8.1 Configuring devices and networks Procedure To create the interconnection of a port to one or more partner ports for the first time, to modify it, or to delete it, follow these steps: 1. Move the mouse pointer to the "Partner port" column in the row of the source port. 2. Click the drop-down list there. 3. Select the required partner port (when creating or changing a port interconnection) or the "Not interconnected" entry (when deleting a port interconnection). Result The required action is performed: If you are creating an interconnection, a new row is inserted in the topology overview table. The new partner port is displayed there in the "Partner port" column. If you change an interconnection, the new partner port is displayed in the "Partner port" column. If you delete an interconnection, the row with the previous port interconnection is deleted. Note With a tool changer, there are normally several rows for a port with port interconnections to more than one partner port. The last row is always an empty row. The first row can be edited, all other rows are read-only. Renaming stations, devices, interfaces or ports Rename a station, a device, an interface or a port Requirement The table view of the configured topology is open. Procedure To rename a station, a device, an interface or a port, proceed as follows: 1. Click twice in the relevant field of the topology overview table (the second click starts the editing mode). 2. Enter the new name and then press the ENTER key (this closes editing mode). Result The object is renamed. 522 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Offline/online comparison Automatic assignment of devices by offline/online comparison Overview During the offline/online comparison, the configured topology is compared with the actual existing topology. Devices identified online are automatically assigned to configured devices as far as this is possible. Start of availability detection You start the availability detection the first time by clicking the "Compare offline/online" button in the toolbar of the topology overview. You restart availability detection by clicking the "Update" button. Note The availability detection can take several seconds. During this time, no user input is possible. Automatic assignment A device identified online is automatically assigned to a configured device if the following properties of the two devices match up: Device name Order number Number of ports The following section describes the situations that can occur and what action you can take: WinCC Basic V13.0 System Manual, 02/2014 523 Editing devices and networks 8.1 Configuring devices and networks Identical port interconnections This is the ideal situation. No action is necessary here. "Action" column Meaning No action There are interconnections for the identified and configured device, there are however differences. The following actions are possible: - If it is possible to adopt the online configuration "Action" column Meaning Adopt online interconnection (Page 525) No action - If it is not possible to adopt the configuration "Action" column Meaning No action The interconnection only exists online. The following actions are possible: - If it is possible to adopt the online configuration "Action" column Meaning Adopt online interconnection (Page 525) No action - If it is not possible to adopt the configuration "Action" column Meaning No action The interconnection only exists in the configuration. The following actions are possible: "Action" column Meaning Adopt the online interconnection (Page 525), in other words, the interconnection in the configuration will be deleted No action 524 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks No automatic assignment In the following situations, no automatic assignment is possible: No device can be identified online to match a configured device. In this case the corresponding columns in the "Online topology" area of the topology overview table are empty. In this case, you should add the already configured device to your system or delete the configured device from the configuration. A device identified online cannot be assigned to any configured device. In this case the corresponding columns in the "Offline topology" area of the topology overview table are empty. In this case, you can adopt the device identified online in the project (Page 526). Adopting the port interconnections identified online in the project Requirement You have run an offline/online comparison in the topology view. The result of this is that at least one device identified online was automatically assigned to a configured device, but that there are differences relating to the interconnection. Procedure To adopt one more port interconnections identified online in the project manually, follow these steps: 1. Select the value "Adopt" in the "Action" column for a port of a configured device to which a device identified online was assigned. 2. Repeat the step if necessary for other ports of the same configured device. 3. Repeat the steps up to now if necessary for other configured devices to which devices identified online were assigned and for which there are differences relating to the interconnection. 4. Click the "Synchronize" button. Result The port interconnections identified online and the cable information for the corresponding devices are adopted in the project. Successful adoption is indicated by the diagnostics icon "Identical topology information" for each port. Note If other port interconnections are recognized for a device identified online and these differ from those that exist in the project, adopting these in the project means that the port interconnections that were previously in the project are replaced by those identified online. If no port interconnections are detected for a device identified online, adopting in the project means that all the port interconnections of this device are deleted in the project. WinCC Basic V13.0 System Manual, 02/2014 525 Editing devices and networks 8.1 Configuring devices and networks Adopt the devices identified online in the project Requirements You have run an offline/online comparison in the topology view. The result of this is that at least one device identified online could not be assigned to any configured device. Procedure To adopt one more devices identified online in the project manually, follow these steps: 1. For a configured device without an online partner, move the mouse pointer to the "Device/ port" column of the online topology. 2. Select the device you want to assign to the configured device from the drop-down list of this box. 3. Repeat the previous steps if necessary for other configured devices without an online partner. Result The selected device that was identified online is moved up from the end of the table. Following this, it is in the row of the configured device to which you have just assigned it. 8.1.3.4 Industrial Ethernet Security Configuring security General Supported devices Supported devices Security functions can be configured for the following products: SCALANCE S: - S602 V2/V3/V4 - S612 V2/V3/V4 - S613 V2 - S623 V3/V4 - S627-2M V4 SOFTNET Security Client: - SOFTNET Security Client V4 526 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks S7-CPs: CP 343-1 GX31 Advanced, CP 443-1 GX30 Advanced, CP 1543-1 PC CP: CP 1628 Mobile wireless router: SCALANCE M875 General terminology "security module" In this section of the information system, the following products are grouped together under the term "security module": SCALANCE S602 / SCALANCE S612 / SCALANCE S613 / SCALANCE S623 / SCALANCE S627-2M, CP 343-1 GX31 Advanced, CP 443-1 GX30 Advanced, CP 1543-1, CP 1628, SCALANCE M875. Use of the terms "interface" and "port" In this documentation, the following terms are used for the ports of SCALANCE S modules: "External interface": The external port of the SCALANCE S602 / S612 / S623 or an external port of the SCALANCE S627-2M (marked red) "Internal interface": The internal port of the SCALANCE S602 / S612 / S623 or an internal port of the SCALANCE S627-2M (marked green) "DMZ interface": The DMZ port of the SCALANCE S623 / S627-2M (marked yellow) The term "port" itself is used when the focus of interest is a special port of an interface. General use of the term "CP x43-1 Adv." In this documentation, the term "CP x43-1 Adv." includes the following products: CP 343-1 GX31 Advanced / CP 443-1 GX30 Advanced. Structure of this section of the help system Topics that are relevant to all security modules can be found in the "General" section. Information that is only relevant to certain module types can be found in the sections relating specifically to these modules. Overview - Scope of performance and method of operation General use of the term "STEP 7" Configuration of security functions is supported as of STEP 7 V12. For this reason, in this section of the information system, the name "STEP 7" will be used for all versions of STEP 7 V12 or higher. WinCC Basic V13.0 System Manual, 02/2014 527 Editing devices and networks 8.1 Configuring devices and networks Scope of performance You can use the following security functions in STEP 7: Configuration of the security modules Creating VPN configuration data for SOFTNET Security Client V4 Creating VPN configuration data for SCALANCE M875 Test and diagnostics functions, status displays Offline configuration view and online diagnostics view The security functions are configured in two views: Offline configuration view In the offline configuration view, you create the configuration data for the security modules and the SOFTNET Security Client. Prior to downloading, there must already be a connection to the security modules. Online diagnostics view The online diagnostics view is used for diagnostics of the security module and, among other things, allows you to run firmware updates. How it works - security and consistency Access only for authorized users The security functions of every project are protected from unauthorized access by assigning user names and passwords. Consistent project data Consistency checks are running even while you make the entries in the dialogs. In addition, cross-dialog, project-wide consistency checks are carried out. Only consistent project data can be downloaded to the security modules. Protecting project data by encryption The project and configuration data relevant to security are protected by encryption. Depending on the security module, data can be stored in the project and/or on the C-PLUG. 528 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks User interface - layout and menu commands User interface for security functions in STEP 7 WinCC Basic V13.0 System Manual, 02/2014 529 Editing devices and networks 8.1 Configuring devices and networks Global security settings The global security settings are located in the project navigation. These security settings can be configured independently of the module and subsequently assigned to individual security modules as required. If the first security module to be configured is a CP, the global security settings are only displayed when the security functions have been enabled in the local security settings of the CP. If the first security module to be configured is a SCALANCE S module, the global security settings are displayed after logging in to the security project. The following main folders and entries are available in the global security settings: User login For the security configuration within a project, there is a separate user management. Log in to the security configuration using the "User login" entry. The first time that there is a login to the security configuration, a user with the system-defined role "Administrator" is created automatically. You can create further users in the security configuration in the user management. User administration In user administration, you can create users, define rights for roles and assign these roles to users. Certificate manager In the certificate manager, you see an overview of all the certificates used in the project. You can, for example, import new certificates as well as export, modify or replace existing certificates. Firewall Under the "Firewall" entry, you can define global IP and MAC firewall rule sets and user-specific IP rule sets (SCALANCE S modules only) and assign security modules. IP and MAC service definitions are used to define the IP and MAC firewall rules compactly and clearly. VPN groups All created VPN groups are contained in this folder. You can create new VPN groups here and assign security modules to these VPN groups. You can also adapt VPN group properties of VPN groups that have already been created. NTP Here, you can create NTP servers and assign them to one or more security modules. This ensures that time synchronization is performed through the assigned NTP server. Unsecured NTP servers can only be configured in the local security settings. 530 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Working area with security module Once you have selected a security module in the work area, you can configure its local security settings in "Properties" > "General". If the selected security module is in a VPN group, related information is displayed in the VPN tab. VPN tab This tab displays information about all the VPN groups to which the security module that was selected in the working area belongs. Information about the respective participants of a VPN group can be displayed and hidden. WinCC Basic V13.0 System Manual, 02/2014 531 Editing devices and networks 8.1 Configuring devices and networks Local security settings Local security settings are configured for a specific security module. After a security module has been selected in the working area, its local security settings are available in the inspector window under "Properties" > "General". Note for CPs: Before security settings can be configured for CPs, the local security settings must be enabled. To do this, log in to your security project and then in the Inspector window, select the "Activate security features" check box under "Properties" > General" > "Security". The local security settings are then displayed below the "Security" entry. When the check box is selected, the following settings (assuming they were enabled) are migrated automatically to the local security settings. CP x43-1 Advanced: SNMP FTP configuration Time-of-day synchronization Web server Entries of IP access lists CP 1543-1: SNMP FTP configuration Time-of-day synchronization CP 1628: SNMP Time-of-day synchronization In addition, firewall rules that enable a connection to be established are created automatically for configured connections. Log settings are available to record blocked packets. Secure and non-secure configuration areas The user interface can be divided into secure and non-secure configuration areas. The secure areas are areas in which configuration is possible only after logging in to the security configuration. These areas are encrypted and therefore only accessible to persons authorized in the user management even if the project is accessible to a wider circle of people. Functions from the non-secure areas, on the other hand, can be configured without logging in to the security configuration. The correctness of the settings must be checked before downloading the project to the plant components if a wider circle of people can make modifications to the project. 532 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Below, you will find a list of the configuration areas of the user interface showing which areas are secure and which are non-secure. To some extent, this depends on the security module for which the configuration is created. All settings from the global security settings are secure. Secure and non-secure configuration areas for SCALANCE S modules: - All the settings for the interfaces and ports, in particular IP addresses, are non-secure. - The settings under the entry "General" in the local security settings are non-secure. - Higher-level settings (e.g. MRP settings such as MRP manager etc.) that are not configured on the security module itself but may affect the security module are nonsecure. This does not relate to the global security settings. - The other settings are protected. Secure and non-secure configuration areas for CP 343-1 GX31 Advanced, CP 443-1 GX30 Advanced, CP 1628, CP 1543-1: - All settings outside the "Security" entry are non-secure. - Higher-level settings (e.g. MRP settings such as MRP manager, PROFINET settings, connections etc.) that are not configured on the security module itself but may affect the security module are non-secure. This does not relate to the global security settings. - All the settings for the interfaces and ports, in particular IP addresses, are non-secure. - All settings below the "Security" entry are secure. Running a consistency check Overview The following consistency checks are available: Local consistency checks Project-wide consistency checks In the individual dialog descriptions in this help system, the rules you need to take into account for your entries are listed under the keyword "Consistency check". Local consistency checks A consistency check is local when it can be performed directly within a dialog. With the following actions, local consistency checks are made: After exiting a box After exiting a row in a table When you confirm a dialog with OK. WinCC Basic V13.0 System Manual, 02/2014 533 Editing devices and networks 8.1 Configuring devices and networks Project-wide consistency checks Project-wide consistency checks provide you with information indicating whether or not project data is correctly configured. With the following actions, there is a consistency check through the entire project: When compiling a configuration When downloading a configuration Note You can only download configured data to a security module when the entire project is consistent. Managing certificates Overview of certificates How do you manage certificates? In the certificate manager, you have an overview of all the certificates, for example, CA certificates used in the project with information about the applicant, issuer, validity, use and the existence of a private key. The CA certificate is issued by a certificate authority from which the device certificates are derived. These include the SSL certificates and if the security module is a member of a VPN group the VPN group certificates. The SSL certificates are required for authentication during secure communication between a network node and a security module. Certificate authorities can be: STEP 7 itself. If the "applicant" and "issuer" are the same, this is a self-signed certificate; in other words, issued by STEP 7. A higher ranking (commercial) certificate authority. These third-party certificates are external to the project and are imported and stored in the certificate store of STEP 7. Certificates created by one of the two certificate authorities always have a private key so that the device certificates can be derived from them. The following functions are also available in the certificate manager: Modification of existing certificates (for example, duration of validity). Import of new certificates and certificate authorities. Import of SSL certificates (CP x43-1 Adv. only), e.g. for FTP communication. Export of the certificates and certificate authorities used in the project. Renewal of expired certificates and certificate authorities. Replacement of existing certificate authorities with others. 534 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Addition of trusted certificates and certificate authorities. Deleting manually imported certificates. Note Downloading the configuration After replacing or renewing certificates, the configuration must be downloaded to the relevant security modules. After replacing or renewing CA certificates, the configuration must be downloaded to all security modules. Note Current date and current time of day on the security modules When using secure communication (for example, HTTPS, VPN...), make sure that the security modules involved have the current time of day and the current date. Otherwise the certificates used are not evaluated as valid and the secure communication does not work. How to access this function Double-click on the "Certificate manager" entry in the global security settings. In the individual tabs, you have the following commands available in the shortcut menu: Command Meaning Import / Export Import / export of device certificates or CA certificates. The certificates are transferred to the security module. The following formats are permitted: *.cer (certificate only) *.crt (certificate only) *.pem (certificate only) *.p12 (certificate and corresponding private key) WinCC Basic V13.0 System Manual, 02/2014 Displays Opens the certificate dialog of Windows where you see an overview of all certificate data. Renew (only in the "CA" and "Device certificates" tabs) Opens the "Create new certificate" dialog in which you can import a certificate or have a new certificate created by STEP 7 when necessary, for example with compromised certificates. Replace (only in the "CA" tab) Opens the "Change certificate authority (CA)" dialog in which you can replace an existing certificate authority with a new one. Delete (only with manually imported certificates) Deletes a certificate in the "Trusted certificates and root certification authorities" tab. 535 Editing devices and networks 8.1 Configuring devices and networks Certificate authorities "CA" tab The certificates displayed here are created by a certificate authority. CA certificates of a project: When you create a new project, a CA certificate is generated for the project. The SSL certificates for the individual security modules are derived from this certificate. CA group certificates: When you create a new VPN group, a CA certificate is generated for the VPN group. The VPN group certificates of security modules located in the VPN group are derived from this certificate. Device certificates "Device certificates" tab Display of the device-specific certificates generated by STEP 7 for a security module. These include: SSL certificate of a security module: An SSL certificate that is derived from a CA certificate of the project is generated for each security module that you create. SSL certificates are used for authentication during secure communication between PG/PC and security module when downloading the configuration. VPN group certificate of a security module: A VPN group certificate is also generated for each security module for each VPN group in which it is located. Trusted certificates and root certification authorities "Trusted root certification authorities" tab Display of the third-party certificates imported into STEP 7. For example, server certificates can be imported from external FTPS servers or project certificates from other projects that were created with STEP 7. With CPs, the imported third-party certificate is transferred to all the CPs managed in the project and these check the certificate. If you classify the certificate sent to the security modules as trusted, a connection can be established, for example, to an FTPS server. The imported certificate is not used at any other point in STEP 7. With SCALANCE S modules, the certificate authorities required for verifying the security modules using external services such as dyn. DNS are displayed in this tab. 536 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Renewing certificates Meaning In this dialog, you renew CA certificates and device certificates. If necessary, for example with compromised certificates, you can import a certificate or have a new certificate generated by STEP 7. How to access this function 1. Right-click on a list entry in the certificate manager. 2. Select the "Renew" entry in the shortcut menu. 3. Decide whether or not the new certificate will be self-signed or signed by a certificate authority. 4. If the certificate is to be signed by a certificate authority, select the certificate authority to be used with the "Select" button. Only certificate authorities stored in the certificate store of the current project can be selected. 5. Depending on the certificate, enter the following values in the "Applicant" or "Alternative applicant name" input box: Certificate to be renewed Parameter Applicant Alternative applicant name CA certificates of the project Name of the CA certificate - CA group certificate Name of the CA group certificate - SSL certificate for S7 CP Name of the security module Comma-separated IP addresses of the Gigabit and PROFINET interface SSL certificate for PC CP Name of the security module IP address of the security module SSL certificate for SCALANCE S, SCALANCE M, SOFTNET Security Client Name of the security module For SCALANCE S: External IP address, internal IP address and, if applicable, IP address of the DMZ interface For SCALANCE M: External IP address, internal IP address For SOFTNET Security Client: DNS name VPN group certificate of the security module Name of the VPN group certificate Derived from the CA group certificate. 6. Select a period during which the certificate is valid. As default the current time is entered in the "Valid from:" box and the value of the current certificate is entered in the "Valid to:". WinCC Basic V13.0 System Manual, 02/2014 537 Editing devices and networks 8.1 Configuring devices and networks Replacing certificates Meaning Open the "Change certification authority (CA)" to replace the existing CA certificate of the project or the CA group certificate with a new one. How to access this function 1. Right-click a list entry in the "CA" tab. 2. Select the "Replace" entry in the shortcut menu. 3. The "Change certification authority (CA)" dialog opens. All certificates listed in the "Certificates involved" table are derived once again. This means that the CA group certificate of an already configured VPN group can be replaced in the project by the CA group certificate of a different project. The VPN group certificates for the VPN group members are therefore derived from the same CA group certificate in both projects. After making changes in the certificate manager, download the configuration to all security modules affected. Which format can the certificate have? Other certificates are derived from the imported certificate authority in STEP 7. For this reason, you can only select certificates with a private key. *.p12 Managing users and roles Rules for user names, roles and passwords Which rules apply to user names, role names and passwords? When creating or modifying a user, a role or a password, remember the following rules: Table 8-1 Rules for user management Permitted characters The following characters from the US-ASCII character set are permitted: 0123456789 A...Z a...z !#$%&()*+,-./:;<=>?@ [\]_{|}~|^ Characters not allowed 538 "' Length of the user name 1 ... 32 characters Length of the password 8 ... 32 characters Length of the role name 1 ... 32 characters WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Maximum number of users per project Maximum number of users on one security module Maximum number of roles per project Maximum number of roles on one security module 128 32 + 1 administrator when creating the project 124 (120 user-defined + 4 system-defined) 33 (29 user-defined + 4 system-defined) Note User names and passwords As vital measure under the aspect of maximizing security, always make sure that user names and passwords have a minimum length of 8 characters and that these contain special characters, uppercase/lowercase letters, number, etc.. Create users Meaning The security functions configured in STEP 7 are protected from unauthorized access by a separate user management. Before you can access the global and local security settings of security modules, you need to log in to the security configuration as a user. Creating the first user in the project After creating the first security module in the project, you first need to create a user. To do this, in the local security settings of the created security module, click the "User login" button under the "Security properties" entry and enter the login data of the user you want to create. You will then be logged in as the created user and the user is assigned the system-defined "Administrator" role. This role includes all configuration and module rights. Creating users in the user management When you are logged in as a user in the security configuration, you can create further users or delete users with the "User management" entry in the global security settings. Note Users with the "Administrator" role There must always be at least one user with full configuration rights within a project. The administrator that is created automatically when you first enable the security functions in the project can only be deleted if at least one other user exists with the system-defined role "Administrator". The following parameters are available in user management in the "User" tab: WinCC Basic V13.0 System Manual, 02/2014 539 Editing devices and networks 8.1 Configuring devices and networks Table 8-2 Information in the "User" tab Parameter Meaning User name Name of the user to be created. Click on the "Add new user" entry in the "User name" column to create a new user. Password Password with which a user authenticates him/herself when logging on. Role Selecting a system-defined or user-defined role. Maximum time of the Entry of the time after which a user logged on to the Web page for usersession (only for specific IP rule sets of SCALANCE S modules is automatically logged SCALANCE S V3 or higher) off. The time entered here starts after the logon and after renewing the session on the Web page of the security module. Default setting: 30 minutes Minimum value: 5 minutes Maximum value: 480 minutes Comment Entry of optional comments. Creating roles Overview You can assign a system-defined or a user-defined role to a user. Specify the module rights of a user-defined role for each security module. System-defined roles The system-defined roles listed below are predefined. Certain rights are assigned to the roles that are the same on all modules and that the administrator can neither change nor delete. Administrator Default role when creating a security configuration. Unlimited access rights to all configuration data and all security modules. Standard Role with restricted access rights. Diagnose Default role when creating new user. - Read access to configurations. - Read access to the security module in the "Online" mode for testing and diagnostics. Remote-Access Can be used as a template when creating user-defined roles. You will find a detailed list of the configuration and module rights assigned to the systemdefined roles "Administrator", "Standard" and "Diagnostics" in tables 1-3 to 1-7 of the section Managing rights (Page 541). 540 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks User-defined role In addition to the system-defined roles, you can create user-defined roles. For a user-defined role, select the configuration or module rights and specify the appropriate module rights for every security module used in the project. You manually assign the user-defined roles to the relevant user. How to access this function 1. Double-click on the "User management" entry in the global security settings. 2. Select the "Roles" tab in User management. Table 8-3 Information in the "Roles" tab Parameter Meaning Role Freely selectable role name. Double-click on the "Add new role" entry to create a new user-defined role. You can then set the rights for the created role. Description Specifying the system-defined role With user-defined roles, the "Userdefined role" character string is displayed. Maximum time of the Entry of the time after which a user with the assigned role is automatically session (only for logged off from the Web page for user-specific IP rule sets of SCALANCE SCALANCE S V3 or higher) S modules. The time entered here starts after the logon and after renewing the session on the Web page of the security module. Default setting: 30 minutes Minimum value: 5 minutes Maximum value: 480 minutes Comment Entry of additional, optional comments. Note Deleting roles A user-defined role can only be deleted when it is no longer assigned to any user. If necessary, assign the user a different role. System-defined roles cannot be deleted. Managing rights How to access this function 1. Double-click on the "User management" entry in the global security settings. 2. Select the "Roles" tab in User management. WinCC Basic V13.0 System Manual, 02/2014 541 Editing devices and networks 8.1 Configuring devices and networks Creating and assigning a user-defined role 1. Double-click on the "Add new role" entry. 2. Enter a role name. 3. If necessary, select the system-defined role whose rights will be used as the template for the user-defined role from the drop-down list labeled "<Copy rights from>". User-defined roles cannot be selected from the drop-down list. Result: In the list of rights of the user roles, the rights are selected that are assigned to the selected system-defined role. 4. For each security module, enable or disable the rights to be assigned to the user-defined role. 5. Assign the role to a user in the "User" tab. Configuration rights Configuration rights are not module dependent and control the rights for configuration in STEP 7. Depending on the user type, the following configuration rights are available for selection: Table 8-4 Configuration rights Configuration right Administrator Standard Diagnose Diagnose security x x x Configure security x x - Managing users and roles x - - Module rights Module rights are configured per module. The "Service" column shows the service to which the particular right relates. With the "Copy rights" and "Paste rights" commands in the shortcut menu, you can transfer the rights from one module to another. Depending on the user type, the following module rights are available for selection: Table 8-5 Module rights CP x43-1 Advanced Right within the service Administrator Standard Diagnose Web: Format CP file system * x - - FTP: Read files from the CP file system x x x FTP: Write files to the CP file system x x - FTP: Read files (DBs) from the S7 CPU ** x x x FTP: Write files (DBs) to the S7 CPU *** x x - Applet: Read tags using configured symbols * x x x Applet: Write tags using configured symbols * x x - Applet: Read tags using absolute addresses * x x x Applet: Write tags using absolute addresses * x x - Applet: Read status of the modules in the rack * x x x 542 Service File system PLC WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Administrator Standard Diagnose Applet: Query order numbers of the modules in the rack * Right within the service x x x SNMP: Read MIB-II x x x SNMP: Write MIB-II x x - SNMP: Read automation MIB x x x SNMP: Read LLDP-MIB x x x SNMP: Read SNMPv2-MIB x x x SNMP: Read MRP MIB x x x SNMP: Write MRP MIB x x - TIA Portal: Run diagnostics of the security module **** x x x Security Web: Expand IP access control list * x - - Web Web: Access Web diagnostics and CP file system x x x Web: Send test e-mails * x x x Web: Update firmware * x x - Web: Load diagnostics texts later * x x - Table 8-6 Service SNMP Maintenance Module rights CP 1628 Right within the service Administrator Standard Diagnose Service SNMP: Read MIB-II x x x SNMP SNMP: Write MIB-II x x - SNMP: Read automation MIB x x x SNMP: Read SNMPv2-MIB x x x TIA Portal: Run diagnostics of the security module **** x x x Security Administrator Standard Diagnose Service Download the configuration files x x - Security TIA Portal: Run diagnostics of the security module **** x x x SNMP: Read automation MIB x x x SNMP: Read MIB-II x x x SNMP: Write MIB-II x x - SNMP: Read MRP-MIB x x x SNMP: Write MRP-MIB x x - SNMP: Read SNMPv2-MIB x x x Web: Update firmware x x - Administrator Standard Diagnose FTP: Read files from the CP file system x x x FTP: Write files to the CP file system x x - TIA Portal: Run diagnostics of the security module **** x x x Table 8-7 Module rights SCALANCE S Right within the service Table 8-8 SNMP Maintenance Module rights CP 1543-1 Right within the service WinCC Basic V13.0 System Manual, 02/2014 Service File system Security 543 Editing devices and networks 8.1 Configuring devices and networks Right within the service Administrator Standard Diagnose Service SNMP: Read automation MIB x x x SNMP SNMP: Read IPv6 MIB x x x SNMP: Read LLDP-MIB x x x SNMP: Read MIB-II x x x SNMP: Write MIB-II x x - SNMP: Read SNMPv2-MIB x x x FTP: Read files (DBs) from the S7 CPU ** x x x FTP: Write files (DBs) to the S7 CPU *** x x - PLC * To be able to use the function, the module right "Web: Access Web diagnostics and CP file system" must be enabled as well. ** To be able to use the function, the module right "FTP: Read files from CP file system" must be enabled as well. *** To be able to use the function, the module right "FTP: Write files to CP file system" must be enabled as well. **** To use the function, the configuration right "Security diagnostics" must also be enabled. Setting module rights before and after creating the security modules Within a user-defined role, the module rights for each security module are defined separately. If a security module was created before this role was added and module rights within a role need to be set, STEP 7 presets the module rights for the security module according to the selected rights template. The preset module rights can then be adapted when adding the role. If a security module was created after adding a role, no rights are preset for this security module. In this case, you will need to edit an existing role and set all the module rights yourself for the security module. You can also transfer existing module rights to another module by copying and, if necessary, adapting them there. To do this, select a module in the shortcut menu in the module rights and select the "Copy rights" or "Paste rights" menu command. Generating configuration data for SCALANCE M modules Context You can generate the VPN information for the assignment of parameters to a SCALANCE M using STEP 7. For this to be possible, the module must be in at least one VPN group with a security module or a SOFTNET Security Client. With the generated files, you can then configure the SCALANCE M using the Web Based Management of the device. 544 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Generated files The following file types are generated: Export file with the configuration data - File type: *.txt file in ASCII format - Contains the exported configuration information for the SCALANCE M including information on the additionally generated certificates. VPN group certificates of the module - File type of the private key: *.p12 file - The file contains the module certificate and the key material. - Access is password protected. CA certificates of VPN groups - File type: *.cer file Figure 8-1 SCALANCE M configuration file Note No transfer to the security module Configuration files are not transferred to the security module. An ASCII file is generated with which you can configure the SCALANCE M. To allow this, the SCALANCE M must be located in at least one VPN group with another security module. Follow the steps below 1. Select the module of the type "SCALANCE M". 2. In the local security settings, select the entry "SCALANCE M configuration". WinCC Basic V13.0 System Manual, 02/2014 545 Editing devices and networks 8.1 Configuring devices and networks 3. Select the "Generate SCALANCE M files" check box and select a storage location for the configuration files. 4. Compile the configuration of the SCALANCE M module. 5. In the dialog that follows, choose whether you want to create your own password for the created .p12 file. If you select "Cancel", the project name is assigned as the password, not the project password. Result: The files (.txt file and certificates) are stored in the folder you specify. Configuring interfaces for SCALANCE S modules Overview You will find information on configuration interfaces of SCALANCE S modules in Auto-Hotspot of the section "SCALANCE S". The information contained here deals with the following configuration options: Mode (bridge mode / routing mode): Setting the operating mode (Page 613) IP address parameters: Configuring IP address parameters (Page 613) Port settings (only for SCALANCE S V3): Configuring port mode (Page 615) Settings for the Internet Service Provider (ISP) if one of the interfaces is operated using PPPoE (only for SCALANCE S V3): Configuring an Internet connection (Page 615) Dynamic DNS (only for SCALANCE S V3): Configuring dynamic DNS (Page 616) LLDP (only for SCALANCE S V4 in routing mode): Configuring LLDP (Page 619) Media redundancy in ring topologies (MRP client), (only for SCALANCE S V4 in routing mode): Auto-Hotspot The configuration of the interfaces of CPs is described in the sections dealing with the CPs. Setting up a firewall Overview of the firewall Meaning The firewall functionality of the security modules is intended to protect networks and stations from third-party influence and interference. This means that only certain, previously specified communications relations are permitted. The firewall discards invalid frames without sending a response. To filter the data traffic, IP addresses, IP subnets, port numbers or MAC addresses can be used. You can also set a bandwidth limitation. The firewall functionality can be configured for the following protocol levels: 546 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks IP firewall with stateful packet inspection (layer 3 and 4) Firewall also for Ethernet "non-IP" frames according to IEEE 802.3 (layer 2) With security modules capable of VPN, the firewall can also be used for the encrypted data traffic (IPsec tunnel). With the SCALANCE S602 Security module, the firewall can only be used for unencrypted data traffic. Firewall rules Firewall rules describe which packets in which direction are permitted or forbidden. Types of firewall rules Global firewall rule sets: Global firewall rule sets can be assigned to several security modules at the same time. Global firewall rule sets are configured in the global security settings. Local firewall rules: Local firewall rules are configured in the local security settings of a security module. User-specific IP rule sets (only for SCALANCE S V3): User-specific IP rule sets can be assigned to individual or several security modules at the same time. User-specific IP rule sets are configured in the global security settings and assigned there to one or more users. You will find information on configuring user-specific IP rule sets for SCALANCE S V3 modules in the following section: Auto-Hotspot Service definitions With the aid of service definitions, you can also define firewall rules clearly in a compact form. Service definitions are configured in the global security settings and can be used in the global, local and user-specific firewall rules. Adapting standard rules for IP services For SCALANCE S modules V3 or higher, you can adapt service-specific firewall rules that are set as default for the interfaces of the security modules. You will find information on configuring these firewall rules in Adapting standard rules for IP services (Page 628) of the section "SCALANCE S". Automatically generated firewall rules for CP connections For connections that were configured using CPs, STEP 7 automatically creates firewall rules that allow communication with the partner of the CP in the specified direction (CP active/ passive). The connection establishment directions are taken into account. To display these firewall rules, if the advanced firewall mode is enabled, the "Update connection rules" button needs to be clicked. The firewall rules are then displayed in advanced firewall mode. Which firewall rules are generated automatically is described in the following sections. WinCC Basic V13.0 System Manual, 02/2014 547 Editing devices and networks 8.1 Configuring devices and networks For S7-300 CPs/S7-400 CPs/PC CPs: Connection-related automatic firewall rules (Page 652) in the section "Security for S7-300 / S7-400 / PC CPs". For S7-1500 CPs: Connection-related automatic firewall rules (Page 661) in the section "Security for S7-1500 CPs". Enabling the firewall Firewall functionality for a specific security module is controlled in the local security settings using the "Enable firewall" check box. If the check box is enabled, the firewall can be configured and is effective following the download. For a security module that is a member of a VPN group, the "Enable firewall" check box is activated by default and cannot be deactivated. After switching to advanced firewall mode, it is not possible to switch back to standard mode. For more information about the standard and advanced firewall modes, refer to the section: Overview of local firewall rules (Page 556). Global firewall rule sets Application Regardless of the module, global firewall rule sets are configured in the global security settings. A firewall rule set consists of one or more firewall rules and is assigned to the individual security modules. In the global firewall rule sets, a distinction is made between the following: IP rule sets MAC rule sets The following schematic illustrates the relationship between globally defined rule sets and locally used rule sets. 3URMHFW JOREDOUXOHVHWQ JOREDOUXOHVHW JOREDOUXOHVHW 5XOHJ 0RGXOH ORFDOUXOHVHW ORFDOUXOHO JOREDOUXOHVHW 5XOHJ 5XOHJ ORFDOUXOHO JOREDOUXOHVHW 548 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Configuring When configuring global firewall rules, you can make detailed firewall settings. You can allow individual services for a single node or all services for the node for access to the station or network. When are global IP and MAC firewall rules useful? Global firewall rules are useful if you want to define identical filter criteria for communication with several security modules. Note Assigning firewall rule sets with incompatible firewall rules For a security module, only the firewall rules from firewall rule sets are adopted correctly if the security module supports them. A firewall rule with the direction "From external" or "To any" in a global firewall rule set is not assigned to a CP 1628. The other firewall rules of the global firewall rule set are adopted if the CP supports them. Global firewall rule sets - conventions Global firewall rule sets are used locally The following conventions apply when creating a global set of firewall rules and when assigning it to a module: Configuration view Global firewall rule sets are configured in the global security settings. Priority As default, locally defined rules have a higher priority than the global IP and MAC firewall rule sets. Newly assigned global IP and MAC firewall rule sets are therefore initially entered at the bottom of the local rule list. The priority can be changed by changing the position in the rule list. Entering, changing or deleting rule sets Global firewall rule sets cannot be edited in the local rule list of the firewall rules in the module properties. They can only be displayed there and positioned according to the required priority. It is not possible to delete a single rule from an assigned rule set in the local security settings. Only the entire rule set can be removed from the local list of rules. The firewall rule sets in the global security settings remain unaffected. WinCC Basic V13.0 System Manual, 02/2014 549 Editing devices and networks 8.1 Configuring devices and networks Creating global firewall rule sets How to access this function 1. In the global security settings, select the entry "Firewall" > "Global firewall rule sets" > "IP rule sets" or "MAC rule sets". Result: The previously created IP rule sets or MAC rule sets are displayed under the selected entry. 2. Double-click on the entry "Add new IP rule set" or "Add new MAC rule set". 3. Enter the following data: - Name: Project-wide, unique name of the rule set. The name appears in the local rule list of the security module after the rule set is assigned. - Description (optional): Enter a description of the global rule set. 4. Enter the firewall rules one by one in the list. Note the parameter description in the following sections: For IP rule sets: Defining IP packet filter rules (Page 557) For MAC rule sets: Defining MAC packet filter rules (Page 560) Result You have created the global firewall rule set and can now assign this to the required security modules. Note the descriptions in the following section: Assigning global firewall rule sets (Page 550) Assigning global firewall rule sets Requirement You have enabled the advanced firewall mode for the security modules you want to assign to a firewall rule set. Procedure 1. In the global security settings, select the entry "Firewall" > "Global firewall rule sets" > "Assign module to a firewall rule set". 2. From the "Rule set" drop-down list, select the rule set to which you want to assign the security module. In the right-hand table, you will see the security modules that you can assign to the selected firewall rule set. In the left-hand table, you will see the security modules already assigned to the selected firewall rule set. 3. In the "Available modules" area, select the security modules you want to assign to the selected rule set. 4. Click the 550 button to assign the selected modules to the selected rule set. WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Result The global rule set is used by the assigned security modules as a local rule set and appears automatically at the end of the list of firewall rules in the local security settings. IP services Defining IP services How to access this function In the global security settings, select the entry "Firewall" > "Services" > "Define services for IP rules". Procedure Using the definition of IP services, you can define succinct and clear firewall rules for specific services. You select a name and assign the service parameters to it. These services defined in this way can also be grouped together under a group name. When you configure the packet filter rules, you then use this name. Parameters for IP services You define the IP services using the following parameters: Table 8-9 IP services: Parameter Parameter Meaning/comment Available options / ranges of values Name Name for the service that is used as identification in the rule definition or in the group. The names of predefined services cannot be changed. Name must start with a letter. Name must not contain any special characters. Name must not be redundant. Protocol Selection of the protocol type TCP UDP All Source port The filtering is based on the specified port number; this defines the service access at the frame sender. Examples: *: Port is not checked 20 or 21: FTP service Destination port The filtering is based on the specified port number; Examples: this defines the service access at the frame recipient. *: Port is not checked TCP 80: Web HTTP service TCP 102: S7 protocol WinCC Basic V13.0 System Manual, 02/2014 551 Editing devices and networks 8.1 Configuring devices and networks Defining ICMP services How to access this function 1. In the global security settings, select the entry "Firewall" > "Services" > "Define services for IP rules". 2. Select the "ICMP" tab. Procedure Using the definition of ICMP services, you can define succinct and clear firewall rules for specific services. You select a name and assign the service parameters to it. These services defined in this way can be grouped together under a group name. When you configure the packet filter rules, you then use this name. Parameters for ICMP services Parameter Meaning/comment Available options / ranges of values Name User-definable name for the service that is used as identification in the rule definition or in the group. The names of predefined ICMPv6 services cannot be modified. Name must start with a letter. Name must not contain any special characters. Name must not contain more than 20 characters. Name must not occur more than once ICMPv6 552 If you enable this check box, the ICMP service is declared as an ICMPv6 service and you can select an ICMPv6-specific type and code for the service. An ICMPv6 service can only be used in the firewall rule of a security module that supports IPv6. Enabled Type Type of the ICMPv4 or ICMPv6 message. If the "ICMPv6" check box is deselected, ICMPv4-specific types can be selected. If the check box is selected, ICMPv6specific types can be selected. Code Code of the ICMP type. Values depend on the selected type. Disabled (default) WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Creating service groups How to access this function 1. In the global security settings, select the entry "Firewall" > "Services" > "Define services for IP rules". 2. Select the "Service groups" tab. Forming service groups You can put several services together by creating service groups. This allows you set up more complex services that you can then use in the packet filter rules simply by selecting the name. IPv4 and IPv6 services can be collected in the same service group. Create groups in the open "Service groups" tab. You can then assign services to a group in the "Group management" tab. Follow the steps below 1. First, create groups in this tab with names to suit your requirements and add a description if required. 2. Select the "Group management" tab. You can assign the previously specified IP services to the groups defined in this tab. Managing service groups How to access this function 1. In the global security settings, select the entry "Firewall" > "Services" > "Define services for IP rules". 2. Select the "Group management" tab. Forming service groups You can put several services together by creating service groups. This allows you set up more complex services that you can then use in the packet filter rules simply by selecting the name. IPv4 and IPv6 services can be collected in the same service group. Use the "Group management" tab to assign services to a selected group you created previously in the "Service groups" tab. Follow the steps below 1. Select a group created previously in the "Service groups" tab from the "Service groups" drop-down list in this tab. 2. Then assign the required services from the right-hand "Available services" list box to the group. WinCC Basic V13.0 System Manual, 02/2014 553 Editing devices and networks 8.1 Configuring devices and networks MAC services Define MAC services How to access this function In the global security settings, select the entry "Firewall" > "Services" > "Define services for MAC rules". Meaning Using the definition of MAC services, you can define succinct and clear firewall rules for specific services. You select a name and assign the service parameters to it. These services defined in this way can be grouped together under a group name. When you configure the global or local packet filter rules, you use this name. Parameters for MAC services A MAC service definition is formed using protocol-specific MAC parameters: Table 8-10 MAC services - parameters Parameter Meaning/comment Available options / ranges of values Name User-definable name for the service that is used as identification in the rule definition or in the group. Name must start with a letter. Name must not contain any special characters. Name must not be redundant. Protocol Name of the protocol type: ISO ISO ISO identifies frames with the following properties: Lengthfield <= 05DC (hex), DSAP= userdefined SSAP= userdefined CTRL= userdefined SNAP PROFINET IO 0x (code entry) SNAP SNAP identifies frames with the following properties: Lengthfield <= 05DC (hex), DSAP=AA (hex), SSAP=AA (hex), CTRL=03 (hex), OUI=userdefined, OUI-Type=userdefined PROFINET IO As an alternative, a protocol number can be entered. The protocol entries 0800 (hex) and 0806 (hex) are not accepted since these values apply to IP or ARP frames. DSAP Destination Service Access Point: LLC recipient address SSAP Source Service Access Point: LLC sender address 554 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Parameter Meaning/comment CTRL LLC control field OUI Organizationally Unique Identifier Available options / ranges of values (the first 3 bytes of the MAC address = vendor ID) OUI type Protocol type/identification Note Processing for S7-CPs Only settings for ISO frames with DSAP=SSAP=FE (hex) are processed. Other frame types are not relevant for S7 CPs and are therefore discarded even before processing by the firewall. Special settings for SIMATIC NET services To filter special SIMATIC NET services, please use the following protocol settings: DCP (Primary Setup Tool): PROFINET SiClock : OUI= 08 00 06 (hex) , OUI-Type= 01 00 (hex) Creating service groups How to access this function 1. In the global security settings, select the entry "Firewall" > "Services" > "Define services for MAC rules". 2. Select the "Service groups" tab. Forming service groups You can put several services together by creating service groups. This allows you set up more complex services that you can then use in the packet filter rules simply by selecting the name. Create groups in the open "Service groups" tab. You can then assign services to a group in the "Group management" tab. Follow the steps below 1. First, create groups in this tab with names to suit your requirements and add a description if required. 2. Select the "Group management" tab. You can assign the previously specified MAC services to the groups defined in this tab. WinCC Basic V13.0 System Manual, 02/2014 555 Editing devices and networks 8.1 Configuring devices and networks Managing service groups How to access this function 1. In the global security settings, select the entry "Firewall" > "Services" > "Define services for MAC rules". 2. Select the "Group management" tab. Forming service groups You can put several services together by creating service groups. This allows you set up more complex services that you can then use in the packet filter rules simply by selecting the name. Use the "Group management" tab to assign services to a selected group you created previously in the "Service groups" tab. Follow the steps below 1. Select a group created previously in the "Service groups" tab from the "Service groups" drop-down list in this tab. 2. Then assign the required services from the right-hand "Available services" list box to the group. Overview of local firewall rules Meaning Local firewall rules are configured in the local security settings of a security module and apply only to this security module. After enabling the firewall functionality you can either use predefined firewall rules or define firewall rules in the advanced firewall mode. Using predefined firewall rules Here, you use simple, predefined rules. You can only enable service-specific rules. The enabled services are allowed for all nodes in the specified direction. You can find detailed information on the definition of firewall rules in this dialog in the following module-specific sections: For SCALANCE S: Auto-Hotspot For S7-300 CPs/S7-400 CPs/PC CPs: Auto-Hotspot For S7-1500 CPs: Auto-Hotspot Defining firewall rules in advanced firewall mode In advanced firewall mode, you can make detailed firewall settings. You can allow individual services for a single node or all services for the node for access to the station or network. You enable the advanced firewall mode using the "Activate firewall in advanced mode" check box. 556 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks In the local security settings, the firewall rules can then be configured in "Firewall" > "IP rules" or "MAC rules". The configuration options available here are described individually in the following section: For IP packet filter rules: Defining IP packet filter rules (Page 557) For MAC packet filter rules: Defining MAC packet filter rules (Page 560) Note Deactivating the advanced firewall mode not possible Once you have activated the advanced firewall mode, you can no longer deactivate it. Quantity structure Number of firewall rules (advanced firewall mode) SCALANCE S Maximum of 256 S7 CPs Maximum of 256 CP 1628 Maximum of 256 Defining IP packet filter rules Meaning With IP packet filter rules, you filter according to IP frames, such as TCP, UDP and ICMP. Within a packet filter rule, you can also fall back on the definitions of the IP services. Entering IP packet filter rules Enter the firewall rules one by one in the list. Note the following parameter description. WinCC Basic V13.0 System Manual, 02/2014 557 Editing devices and networks 8.1 Configuring devices and networks Table 8-11 IP rules: Parameter Parameter Meaning/comment Available options / ranges of values Action Allow/disallow (enable/block) Allow Allow frames according to definition. Drop Block frames according to definition. For firewall rules generated automatically as result of configuring a connection and subsequently adapted manually: Allow* Drop* If you change automatically created connection rules, when the "*" option is selected they are not recreated and overwritten by STEP 7. From / To Selection of the communications directions for which the rule will apply. Described in separate sections. For SCALANCE S modules: IP packet filter directions SCALANCE S (Page 627) For S7-300 CPs/S7-400 CPs/PC CPs: IP packet filter directions S7-300-/ S7-400-/PC-CPs (Page 650) For S7-1500 CPs: IP packet filter directions S7-1500 CPs (Page 660) IPv6 (for the CP 1543-1 only) If this check box is selected, you can use a previously defined ICMPv6 service in the firewall rule. For the CP 1543-1 V1.1, after selecting the check box you can enter additional IPv6 addresses in the "Source IP address" and "Destination IP address" input boxes. For the CP 1543-1 V1.0, after enabling the check box you cannot enter any source IP address or any destination IP address for the firewall rule. The check box can only be selected and deselected if there are no entries in the "Source IP address" and "Destination IP address" input boxes. Source IP address The firewall rule is applied to the frames whose sender has the IP address specified here. If you do not specify an IP address, the firewall rule applies to all nodes in the communications direction you selected in the "From" column. You can find additional information about IP addresses in the IP addresses in IP packet filter rules (Page 561) section. Destination IP address The firewall rule is applied to the frames whose recipient has the IP address specified here. If you do not specify an IP address, the firewall rules applies to all nodes in the communications direction you selected in the "To" column. 558 If IPv6 is disabled in the local settings of the CP 1543-1, you cannot select the "IPv6" check box in the local security settings of the CP and therefore cannot use ICMPv6 services or IPv6 addresses in firewall rules. Existing firewall rules that use IPv6 are shown grayed out if IPv6 is disabled. WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Parameter Meaning/comment Available options / ranges of values Service Name of the IP/ICMP service or service group used. The drop-down list box displays the services and service groups configured in the global security settings and you can select them. Here, you select one of the services you defined in the "IP services" dialog: IP services or ICMP services Before you select an ICMPv6 service, you need to select the "IPv6" check box. Bandwidth (Mbps) Option for setting a bandwidth limitation CP x43-1, CP 1543-1 and SCALANCE S < V3.0: 0.001 ... 100 Mbps Can only be entered if the "Allow" action is selected. For global and user-specific rules: 0.001 ... 100 Mbps CP 1628 and SCALANCE S V3.0: 0.001 ... 1000 Mbps A packet passes through the firewall if the allow rule matches and the permitted bandwidth for this rule has not yet been exceeded. Logging Enable and disable logging for this rule. If logging is enabled, the settings for the packet filter logging configured in the local security settings apply. Number Automatically assigned number for the rule Comment Space for your own explanation of the rule Table 8-12 Note: If the direction "From tunnel to station" is configured in a firewall rule for the CP 1543-1, no bandwidth limitation can be specified. Enabled Disabled (default) If a comment is marked with "AUTO", it was created for an automatic connection rule. For rules you have created, entry of a comment is optional. Meaning of the entries in the shortcut menu Entry in the shortcut menu Meaning Delete This deletes the selected rule or the selected rule set. Notes on removing a globally defined and locally assigned rule set: if you delete a rule set here, this only cancels the assignment to the security module. Save as global rule set (only for local firewall rules) Copies the selected firewall rule(s) and inserts it as a global firewall rule set in the global security settings. The firewall configuration currently configured for the security module remains unaffected by this procedure. Move up Use this button to move the selected rule or selected rule set up one position in the list. The rule / rule set you moved is therefore handled with higher priority. Move down Use this button to move the selected rule or selected rule set down one position in the list. The rule / rule set you moved is therefore handled with lower priority. Define service for IP rules This opens the dialog in which you can manage the IP services and service groups. WinCC Basic V13.0 System Manual, 02/2014 559 Editing devices and networks 8.1 Configuring devices and networks Defining MAC packet filter rules Meaning With the MAC packet filter rules, you filter according to MAC frames. Within a packet filter rule, you can also fall back on the definitions of the MAC services. Entering MAC packet filter rules Enter the firewall rules one by one in the list. Note the following parameter description. Table 8-13 MAC rules: Parameter Parameter Meaning/comment Available options / ranges of values Action Allow/disallow (enable/block) Allow Allow frames according to definition. Drop Block frames according to definition. From / To Selection of the communications directions for which the rule will apply. Described in separate sections. For SCALANCE S modules: MAC packet filter directions SCALANCE S (Page 628) For S7-300 CPs/S7-400 CPs/PC CPs: MAC packet filter directions S7-300-/S7-400-/PC-CPs (Page 651) For S7-1500 CPs: MAC packet filter directions S7-1500 CPs (Page 661) Source MAC address The firewall rule is applied to the frames whose sender has the MAC address specified here. If you do not specify a MAC address, the firewall rule applies to all nodes in the communications direction you selected in the "From" column. Destination MAC address The firewall rule is applied to the frames whose recipient has the MAC address specified here. If you do not specify a MAC address, the firewall rule applies to all nodes in the communications direction you selected in the "To" column. Service Name of the MAC service or service group used The drop-down list box displays the configured services and service groups you can select. Bandwidth (Mbps) Option for setting a bandwidth limitation. Can only be entered if the "Allow" action is selected. CP x43-1, CP 1543-1 and SCALANCE S < V3.0: 0.001 ... 100 Mbps A packet passes through the firewall if the allow rule matches and the permitted bandwidth for this rule has not yet been exceeded. 560 MAC address in the correct format CP 1628 and SCALANCE S V3.0: 0.001 ... 1000 Mbps For global rules: 0.001 ... 100 Mbps Note: If the direction "From tunnel to station" is configured in a firewall rule for the CP 1543-1, no bandwidth limitation can be specified. WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Parameter Meaning/comment Available options / ranges of values Logging Enable and disable logging for this rule. If logging is enabled, the settings for the packet filter logging configured in the local security settings apply. Enabled Number Automatically assigned number for the rule Comment Space for your own explanation of the rule Table 8-14 Disabled (default) If a comment is marked with "AUTO", it was created for an automatic connection rule. For rules you have created, entry of a comment is optional. Meaning of the menu commands Button Meaning Delete This deletes the selected rule or the selected global rule set. Notes on removing a globally defined and locally assigned rule set: if you delete a rule set here, this only cancels the assignment to the security module. Save as global rule set (only for local firewall rules) Copies the selected firewall rule(s) and inserts it as a global firewall rule set in the global security settings. The firewall configuration currently configured for the security module remains unaffected by this procedure. Move up Use this button to move the selected rule or selected global rule set up one position in the list. The rule / rule set you moved is therefore handled with higher priority. Move down Use this button to move the selected rule or selected global rule set down one position in the list. The rule / rule set you moved is therefore handled with lower priority. Define service for MAC rules This opens the dialog in which you can manage the MAC services and service groups. IP addresses in IP packet filter rules Entering IP addresses in IP packet filter rules In IP packet filter rules, you have the following options for entering IP addresses: Nothing specified The rule applies to all IP addresses. An IP address The rule applies specifically to the specified address. WinCC Basic V13.0 System Manual, 02/2014 561 Editing devices and networks 8.1 Configuring devices and networks Address range The rule applies to all the IP addresses covered by the address range. An address range is defined by specifying the number of valid bit places in the IP address in the format: [IP address]/[number of bits to be included] - [IP address]/24 therefore means that only the most significant 24 bits of the IP address are included in the filter rule. These are the first three octets of the IP address. - [IP address ]/25 means that only the first three octets and the highest bit of the fourth octet of the IP address are included in the filter rule. Address area For the source IP address, an address range can be entered in the following format: [Start IP address]-[End IP address] IPv4 addresses An IPv4 address consists of 4 decimal numbers in the range from 0 to 255 separated from each other by a dot. Table 8-15 Examples of address ranges in IPv4 addresses Source IP address or destination IP address Address range Number of addresses*) from to 192.168.0.0/16 192.168.0.0 192.168.255.255 65.536 192.168.10.0/24 192.168.10.0 192.168.10.255 256 192.168.10.0/25 192.168.10.0 192.168.10.127 128 192.168.10.0/26 192.168.10.0 192.168.10.63 64 192.168.10.0/27 192.168.10.0 192.168.10.31 32 192.168.10.0/28 192.168.10.0 192.168.10.15 16 192.168.10.0/29 192.168.10.0 192.168.10.7 8 192.168.10.0/30 192.168.10.0 192.168.10.3 4 *) Note: Note that the network address and the broadcast address are not available as IP addresses of network nodes in an address range. IPv6 addresses IPv6 addresses consist of 8 fields each with four hexadecimal numbers (128 bits in total). The fields are separated by a colon. IPv6 addresses can only be entered in IP packet filter rules for the CP 1543-1 V1.1. Example: fd00:ffff:ffff:ffff:ffff:ffff:2f33:8f21 Rules / simplifications: 562 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Leading zeros within a field can be omitted. Example: Instead of 2001:0db8:2426:08d3:1457:8a2e:0070:7344 it is also possible to use the notation 2001:db8:2426:8d3:1457:8a2e:70:7344. If one or more fields have the value 0 (or 0000), a shortened notation is possible. Example: Instead of 2001:0db8:0:0:0:0:1428:57ab it is also possible to use the notation 2001:db8::1428:57ab. To ensure uniqueness, this shortened form can only be used once within the entire address. Decimal notation with periods The last 2 fields or 4 bytes can be written in the normal decimal notation with periods. Example: The IPv6 address fd00::ffff.125.1.0.1 is equivalent to fd00::ffff:7d01:1. Address range notation in IP packet filter rules: In the same way as IPv4 addresses, IPv6 addresses can also be noted in the form of address ranges. Example: The entry "2001:0db8:85a3:08d3:1319:8a2e:0:0/96" covers all IPv6 addresses from 2001:0db8:85a3:08d3:1319:8a2e:0:0 to 2001:0db8:85a3:08d3:1319:8a2e:ffff:ffff. Carrying out module-specific log settings Log settings - overview Log settings in the configuration The log settings made here are loaded on the module with the configuration and take effect when the security module starts up. You can restrict the configured packet filter log settings in the online functions if necessary. For example, you can use the online functions to specify that merely IP logging is displayed if you have configured IP and MAC logging. Logging procedures and event classes Here, you can specify which data should be logged. As a result, you enable logging as soon as you download the configuration to the security module. During configuration, you also select one or both of the possible logging procedures: Local logging Network Syslog In both logging procedures, the security module recognizes the three following types of events: Packet filter events Audit events System events WinCC Basic V13.0 System Manual, 02/2014 563 Editing devices and networks 8.1 Configuring devices and networks Configuring local logging How to access this function 1. Select the module to be edited. 2. Select the "Log settings" > "Local log memory" entry in the local security settings. 564 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Configuring local logging Table 8-16 Local logging - settings for log events Log event Meaning Comments Packet filter log (firewall) The packet filter log records certain packets of the data traffic. Only those data packets for which a configured packet filter rule (firewall) applies or to which the basic protection reacts (corrupt or invalid packets) are logged. This is only possible when logging is enabled for the packet filter rule. Packet filter log data is not retentive The data is stored in volatile memory on the security module and is therefore no longer available after the power supply has been turned off. For retentive storage, you can also save the log data displayed in the "Online & diagnostics" dialog in a file. In the "Packets to be logged" drop-down list, you can specify the data packets to be logged: "All packets": The data packets that are logged are those to which a configured firewall rule applies. In addition to this, all the response packets to such packets are recorded that have passed the firewall according to a configured allow rule. "Status generating packets": The only data packets that are logged are those to which a configured firewall rule (standard mode or advanced mode) applies and that initially generate a status in the firewall. Data packets that pass through the firewall by using this firewall status are not logged. Audit log The logging of audit events is always enabled. The logged information is always stored in the ring buffer. System log The data is stored in a retentive memory of the security module and is therefore still available after turning off the power supply. The audit log automatically records security-relevant events, for example user actions such as activating or deactivating packet logging or downloading configurations to the security module. Note for CPs: The system log automatically logs successive system events, for example the start of a process or the failed login attempt of a user. System log data is not retentive Select the "Log settings" > "Configure system events" entry to configure the event filter and cable diagnostics functions. WinCC Basic V13.0 System Manual, 02/2014 Audit log data is retentive The audit log files are not retentive on CPs. You should therefore use a Syslog server to backup this data. The data is stored in volatile memory on the security module and is therefore no longer available after the power supply has been turned off. For retentive storage, you can also save the log data displayed in the "Online & diagnostics" dialog in a file. 565 Editing devices and networks 8.1 Configuring devices and networks Table 8-17 Local logging - storage of recorded data Storage Meaning Ring buffer At the end of the buffer, the recording continues at the start of the buffer and overwrites the oldest entries. One-shot buffer Recording stops when the buffer is full. Configuring system events How to access this function 1. Select the module to be edited. 2. Select the "Log settings" > "Configure system events" entry in the local security settings. Filtering of the system events In this dialog, you set a filter level for the system events. As default, the following values are set: SCALANCE S: Level 3 (Error) CP: Level 3 (Error) The priority of the selected filter level must be the same or lower than the severity set for the cable diagnostics; see the "Setting parameters for line diagnostics" table (not for CPs). Recommendation: Select "Error" as the filter level or a higher value to exclude logging of general, uncritical events. Note for CP For CPs, select only level 3 or level 6 since only events of these levels are generated for CPs. Level 0 to level 3 error messages are output if level 3 is selected. If you select level 6, the error messages of levels 0 to 6 are output. Properties of the system events - line diagnostics (not for CPs) Line diagnostics generates a special system event. A system event is generated when a selectable percentage of bad frames is reached. This system event is assigned the severity and facility set in this dialog. Table 8-18 Setting parameters for line diagnostics Function / option / parameter Meaning 566 Enable Enabling and disabling logging Limit Selectable percentage of faulty frames representing the limit at which a system event is triggered. WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Function / option / parameter Meaning Facility Select a facility from the drop-down list that identifies the system event to be logged. Severity Using the severity, you weight the system events of line diagnostics relative to the severity of the other system events. Note Severity of the system events of line diagnostics Make sure that you do not assign a lower severity to the system events of line diagnostics than for the filter. At a lower severity, these events will not pass through the filter and will not be logged. Configuring the network Syslog How to access this function 1. Select the module to be edited. 2. Select the "Log settings" > "Network Syslog" entry in the local security settings. Configuring the network Syslog Table 8-19 Network Syslog - basic settings Option / parameter Enable network Syslog Enables and disables the transfer of logging events to the Syslog server. Syslog server Here, enter the IP address of the Syslog server. As an alternative, an FQDN can be entered for SCALANCE S V4 modules. The Syslog server must be accessible from the security module at the specified address and, if applicable, using the router configuration under the "Routing" entry of the local security settings. If the Syslog server cannot be accessed no Syslog messages are sent. You can recognize this operating state on the basis of corresponding system alarms. To activate the sending of the Syslog information again, you may have to update the routing information and initiate a restart of the security module. Module name WinCC Basic V13.0 System Manual, 02/2014 The module name is displayed and cannot be changed at this point. 567 Editing devices and networks 8.1 Configuring devices and networks Table 8-20 Network Syslog - settings for log events Log event Configuring Comments Packet filter events (firewall) The packet filter log records certain packets of the data traffic. Only those data packets for which a configured packet filter rule (firewall) applies or to which the basic protection reacts (corrupt or invalid packets) are logged. This is only possible if logging is activated for the packet filter rule. The value you select here depends on the evaluation in the Syslog server. If you retain the "default" value setting, the security module specifies the combination of facility and severity with which the event is displayed. Syslog alarms can be classified according to their origin and their severity level by setting Facility and Severity. This assignment is carried out with drop-down lists. The severity and facility that you set here is assigned to every event. Audit events The audit log automatically records security-relevant events, for example user actions such as activating or deactivating packet logging or downloading configurations to the security module. Assignment of the severity and facility is carried out with drop-down lists. The severity and facility that you set here is assigned to every event. System events The system log automatically logs successive system events, for example the start of a process or the failed login attempt of a user. The value you select here for the severity and facility depends on the evaluation in the Syslog server. If you retain the "default" value setting, the security module specifies the combination of facility and severity with which the event is displayed. Select the "Log settings" > "Configure system events" entry in the local security settings to configure the event filter and cable diagnostics functions. Security module as router Overview of the routing settings Meaning If you operate the security module in routing mode, the networks connected to the internal and external interface are transformed into separate subnets. The DMZ interface (SCALANCE S623/S627-2M only) is connected in routing mode regardless of the mode. In routing mode, the frames intended for an existing IP address in the subnet are forwarded. The firewall rules for the direction of transmission also apply. You have the following additional options: 568 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Setting specific routes - can be set in the local security settings under "Routing" (SCALANCE S only), see Specifying routes (Page 630) in the section "SCALANCE S". Use standard router - can be set in the local security settings with "External interface [P1] red", "Internal interface [P2] green" or "DMZ interface [P3] yellow" (SCALANCE S623/ S627-2M only) see Configuring IP address parameters (Page 613) in the section "SCALANCE S". Only one standard router can be used per interface. NAT/NAPT routing - can be set with "NAT / NAPT" (not for CP 1628 and CP 1543-1) in the local security settings. To be able to use NAT/NAPT, the security module must be in routing mode. Enabling routing mode (required for SCALANCE S modules only) For this mode, you configure an internal IP address and an internal subnet mask for addressing the router in the internal subnet in the local security settings. All network requests that do not belong to a subnet are forwarded by the security module to a different subnet. Note: In contrast to the bridge mode of the security module, VLAN tags are lost in routing mode. VLAN is not supported by SCALANCE S modules. Frames with a VLAN tag are therefore discarded by SCALANCE S modules. 1. Select the "Routing mode" option under "Mode" in the local security settings. 2. In the local security settings, enter an internal IP address and an internal subnet mask for addressing the router on the internal subnet in the input boxes under "Internal interface [P2] green" > Ethernet addresses". Overview of NAT/NAPT Module-specific function This function is not available for the CP 1628 and CP 1543-1. Requirement The security module is in routing mode or the DMZ interface is activated (SCALANCE S623 / S627-2M only). How to access this function 1. Select the module to be edited. 2. In the local security settings, select the entry "NAT / NAPT". 3. When required, enable address translation according to NAT(Network Address Translation) or NAPT (Network Address Port Translation). WinCC Basic V13.0 System Manual, 02/2014 569 Editing devices and networks 8.1 Configuring devices and networks Address translation with NAT (Network Address Translation) NAT is a procedure for address translation between two address spaces. The main task is to translate private addresses into public addresses; in other words into IP addresses that are used and even routed on the Internet. As a result, the IP addresses of the internal network are not known to the outside in the external network. The internal nodes are only visible to the external network by means of external IP address that is specified in the address translation list (NAT table). If the external IP address is not the address of the security module and if the internal IP address is unique, this is known as 1:1 NAT. With 1:1 NAT, the internal address is translated to this external address without port translation. Otherwise, n:1 NAT is being used. Address translation with NAPT (Network Address Port Translation) The address translation with NAPT changes the target address and the target port to a communication relation (port forwarding). Frames coming from the external network or DMZ network and intended for the IP address of the security module are translated. If the destination port of the frame is identical to one of the values specified in the "Source port" column, the security module replaces the destination IP address and the destination port as specified in the corresponding row of the NAPT table. With the reply, the security module uses the values for the destination IP address and destination port as contained in the initial frame as the source IP address and the source port. The difference to NAT is that with this protocol ports can also be translated. There is no 1:1 translation of the IP address. There is now only a public IP address that is translated to a series of private IP addresses with the addition of port numbers. Consistency check - these rules must be adhered to When assigning addresses, remember the following rules to obtain consistent entries: Check / rule Check made locally project-wide The internal IP addresses must not be identical to the IP addresses of the module. x Use the part specified by the subnet mask for the IP addresses: x IP addresses that you specify for the direction "external" must be in the same subnet range as the external IP address of the security module under the entry "External interface [P1] red". IP addresses that you specify for the direction "internal" must be in the same subnet range as the internal IP address of the security module under the entry "Internal interface [P2] green". IP addresses that you specify for the direction "DMZ" must be in the same subnet range as the DMZ IP address of the security module under the entry "DMZ interface [P3] yellow". An IP address used in the NAT/NAPT address conversion list must not be a multicast or broadcast address. 570 x WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Check / rule Check made locally The external ports assigned for the NAPT translation are in the range > 0 and 65535. project-wide x Port 123 (NTP), 443 (HTTPS), 514 (Syslog), 161 (SNMP), 67+68 (DHCP), 500+4500 (IPsec) and 161 (SNMP) are excluded if the relevant services are activated on the security module. The external IP address of the security module or the IP address of the DMZ interface may only be used in the NAT table for the action "Source NAT". x Checking for duplicates in the NAT table x An external IP address or an IP address in the DMZ network used in the direction "Destination NAT", "Source NAT +Destination NAT" or "Double NAT" may only be used once in each specified direction. Checking for duplicates in the NAPT table: A source port number may only be entered once for each interface. x Internal NAPT ports can be in the range > 0 and 65535. x See also Overview of the routing settings (Page 568) NAT/NAPT routing Enabling NAT The input boxes for NAT are enabled. NAT address translations only take effect with the entries in the address translation list described below. After creating NAT rules, the corresponding firewall rules are generated and displayed in advanced firewall mode, see section: Relationship between NAT/NAPT router and firewall (Page 576) If PPPoE is activated for the external interface or the DMZ interface, the action "Destination NAT" cannot be configured. When configuring the action "Source NAT", the IP address cannot be entered in the "Source translation" input box because this is obtained dynamically during runtime. Possible address translations for NAT The following tables show the input options for address translation with NAT. Action "Destination NAT" - "Redirect" The action "Destination NAT" can be performed in the following direction: External to internal If the DMZ interface of the security module (SCALANCE S623/S627-2M only) is activated, the action "Destination NAT" can also be performed in the following directions: WinCC Basic V13.0 System Manual, 02/2014 571 Editing devices and networks 8.1 Configuring devices and networks External to DMZ DMZ to internal DMZ to external The following applies, for example for the direction "external to internal": The destination IP address of a frame coming from the external network is checked to see whether it matches the IP address specified in the "Destination IP address" input box. If it matches, the frame is forwarded into the internal network by replacing the destination IP address of the frame with the IP address specified in the "Destination translation" input box. Access from external to internal using the external address is possible. The following table shows the input required for the action "Destination NAT". Box Possible entries Meaning Source IP address Not relevant for this action. Source translation Not relevant for this action. Destination IP address IP address in the source network Destination IP address in the source network with which an IP address in the destination network will be accessed. If the destination IP address in a frame matches the address entered, the address is replaced by the corresponding IP address in the destination network. If the IP address entered here is not the IP address of the security module, this becomes an alias address. This means that the specified IP address is also registered as an IP address on the selected interface. Make sure that the alias address does not cause an IP address conflict in the network. Destination translation IP address in the destination network No. - The destination IP address is replaced by the IP address specified here. Consecutive number assigned by STEP 7 used to reference the firewall rule generated by STEP 7 for the NAT rule. Action "Source NAT" - "Masquerading" The action "Source NAT" can be performed in the following direction: Internal to external If the DMZ interface of the security module (SCALANCE S623/S627-2M only) is activated, the action "Source NAT" can also be performed in the following directions: Internal to DMZ External to DMZ DMZ to external The following applies, for example for the direction "internal to external": The source IP address of a frame coming from the internal network is checked to see whether it matches the IP address specified in the "Source IP address" input box. If it matches, the frame with the external IP address specified in the "Source translation" input box is forwarded to the external network as a new source IP address. In the external network, the external IP address is effective. 572 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks The following table shows the input required for the action "Source NAT". Box Possible entries Meaning Source IP address IP address in the source network The source IP address of the specified node is replaced by the IP address specified in the "Source translation" input box. IP address range in the source network The IP address range is replaced by the IP address specified in the "Source translation" input box. * Source translation IP address in the destination network The IP addresses of all nodes in the source network are replaced by the IP address specified in the "Source translation" input box. Entry of the IP address that will be used as the new source IP address. If the IP address entered here is not the IP address of the security module, this becomes an alias address. This means that the specified address is also registered as an IP address on the selected interface. Make sure that the alias address does not cause an IP address conflict in the network. Destination IP address Not relevant for this action. Not relevant for this action. Destination translation Not relevant for this action. Not relevant for this action. No. - Consecutive number assigned by STEP 7 used to reference the firewall rule generated by STEP 7 for the NAT rule. You can configure an address translation to the module IP address in the destination network for all frames going from a source network to a destination network. The security module also assigns a port number for each frame. This is an n:1 NAT address translation in which multiple IP addresses of the source network are translated to one IP address of the destination network. Enter, for example, the following parameters for the direction "internal to external": Action: "Source NAT" From: "Internal" To "External" Source IP address: "*" Source translation: External IP address of the security module WinCC Basic V13.0 System Manual, 02/2014 573 Editing devices and networks 8.1 Configuring devices and networks Action "Source NAT + Destination NAT" - "1:1-NAT" The action "Source NAT + Destination NAT" can be performed in the following direction: Internal to external If the DMZ interface of the security module (SCALANCE S623/S627-2M only) is activated, the action "Source NAT + Destination" can also be performed in the following directions: Internal to DMZ External to DMZ DMZ to external The following applies, for example for the direction "internal to external": When accessing from internal to external, the action "Source NAT" is performed. When accessing from external to internal, the action "Destination NAT" is performed. The following table shows the input required for the action "Source NAT + Destination NAT": Box Possible entries Meaning Source IP address IP address in the source network The configuration is always specified in the source NAT direction. The IP addresses of the destination NAT direction are then inserted automatically by STEP 7. Source translation IP address in the destination network Destination IP address Not relevant for this action. Destination translation Not relevant for this action. No. - Consecutive number assigned by STEP 7 used to reference the firewall rules generated by STEP 7 for the NAT rule. Action "Double NAT" The action "Double NAT" can be performed in the following directions: Internal to external External to internal If the DMZ interface of the security module (SCALANCE S623/S627-2M only) is activated, the action "Double NAT" can also be performed in the following directions: Internal to DMZ External to DMZ DMZ to internal DMZ to external In every direction, Source and Destination NAT always take place at the same time. The following applies, for example for the direction "external to internal": When accessing from external to internal, the source IP address of the external node is replaced (Source NAT). Access to the internal network also uses the external IP address specified in the "Destination IP address" input box (Destination NAT). You can, for example, use this action if a standard router other than the security module is entered for a device to be accessed using Destination NAT. Response frames from this device are then not sent to the entered standard router but to the corresponding interface of the security module. 574 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks The following table shows the input required for the action "Double NAT": Box Possible entries Meaning Source IP address IP address in the source network IP address of the node in the source network Source translation - Destination IP address IP address in the source network The Source NAT address translation is always to the IP address of the security module in the destination network. For this reason, the "Source translation" input box cannot be configured. Destination IP address in the source network with which an IP address in the destination network will be accessed. If the destination IP address in a frame matches the IP address entered, the IP address is replaced by the IP address specified in the "Destination translation" input box. If the IP address entered here is not the IP address of the security module, this becomes an alias address. This means that the specified address is also registered as an IP address on the selected interface. Make sure that the alias address does not cause an IP address conflict in the network. Destination translation IP address in the destination network No. - The destination IP address is replaced by the IP address specified here. Consecutive number assigned by STEP 7 used to reference the firewall rule generated by STEP 7 for the NAT rule. Enabling NAPT The input boxes for NAPT are enabled. NAPT translations only take effect with the entries in the list described below. After creating NAPT rules, the corresponding firewall rules are generated and displayed in advanced firewall mode, see section: Relationship between NAT/NAPT router and firewall (Page 576) The IP address translation with NAPT can be performed in the following direction: External to internal If the DMZ interface of the security module (SCALANCE S623/S627-2M only) is activated, the IP address translation with NAPT can also be performed in the following directions: External to DMZ DMZ to internal DMZ to external The following applies, for example for the direction "external to internal": Frames intended for the external IP address of the security module and for the port entered in the "Source port" WinCC Basic V13.0 System Manual, 02/2014 575 Editing devices and networks 8.1 Configuring devices and networks column are forwarded to the specified destination IP address in the internal network and to the specified destination port. The following table shows the input required for address translation with NAPT: Box Possible entries Meaning Source port TCP/UDP port or port range A node in the source network can send a frame to a node in the destination network by using this port number. Example of entering a port range: 78:99 Destination IP address IP address in the destination network Frames intended for the IP address of the security module in the source network and the TCP/UDP port specified in the "Source port" box are forwarded to the IP address specified here. Destination port TCP/UDP port Port number to which the frames coming from the source network are forwarded. Protocol TCP+UDP Selection of the protocol family for the specified port numbers TCP UDP No. - Consecutive number assigned by STEP 7 used to reference the firewall rule generated by STEP 7 for the NAPT rule. Relationship between NAT/NAPT router and firewall Meaning After creating NAT/NAPT rules, STEP 7 automatically generates firewall rules that enable communication in the configured address translation direction. The generated firewall rules are visible in advanced firewall mode and can, if necessary, be moved and expanded (additional IP address, services, bandwidth). In addition to this, the generated firewall rules should be checked in terms of their priority and their position. If necessary, the generated firewall rules can be moved. Firewall parameters generated by STEP 7 cannot be adapted. After deactivating NAT/NAPT, the firewall rules generated by 7 are disabled. To clarify the relationship between the NAT/NAPT rules and the corresponding firewall rules, they are identified by corresponding, consecutive numbers. The following table shows the system behind the firewall rules generated for NAT rules. Table 8-21 NAT address translation and corresponding firewall rules NAT action Created firewall rule Action From To Source NAT Allow Source network Destination network IP address of the node specified in the "Source IP address" input box Destination NAT Allow Source network Destination network 576 Source IP address - Destination IP address - IP address of the node specified in the "Destination translation" input box WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks NAT action Created firewall rule Source NAT + Destination NAT Double NAT Action From To Source IP address Allow Source network Destination network IP address of the node specified in the "Source IP address" input box Allow Destination network Source network Allow Source network - Destination network IP address of the node specified in the "Source IP address" input box Destination IP address - IP address of the node that was inserted in the "Destination translation" input box by STEP 7 IP address of the node specified in the "Destination translation" input box The following table shows the system behind the firewall rules generated for NAT rules. Table 8-22 NAPT translations and created firewall rules Created firewall rule Action From To Allow Source network Destination network Source IP address Destination IP address Service - IP address of the node specified in the "Destination IP address" input box [Portnumber_proto col] Configuring time-of-day synchronization Overview of time-of-day synchronization Meaning The date and time are maintained on the security module to verify the validity (time) of a certificate and for time stamping log entries. For CPs, time-of-day synchronization is active as default. The following alternatives can be configured: WinCC Basic V13.0 System Manual, 02/2014 577 Editing devices and networks 8.1 Configuring devices and networks Set time of day when loading (only for SCALANCE S): The module time is set automatically to the PC time when a configuration is downloaded. SIMATIC (for CPs only): If the security module receives MMS time-of-day messages, its local time is synchronized provided the NTP procedure was not configured (MMS = Manufacturing Message Specification). NTP: Automatic setting and cyclic synchronization of the time-of-day by means of Network Time Protocol server. Note Time-of-day synchronization relates solely to the security module and cannot be used to synchronize devices in the internal network of the security module. S7 CPs can forward the time of day to other modules of the station. Note Configuring the firewall for communication with NTP servers If the NTP server cannot be reached by the security module, you will need to allow the frames from the NTP server explicitly in the firewall (UDP, port 123). Defining an NTP server Creating NTP servers in the global security settings In the global security settings only NTP servers of the type "NTP (secure)" can be created and assigned CPs or SCALANCE S V4 modules. Non-secure NTP servers for SCALANCE S modules < V4 and CPs therefore need to be created in the local security settings. 1. Double-click the "NTP" entry in the global security settings. 2. Double-click on the "Add new NTP server" entry. 3. Enter a name for the NTP server (secure). 4. Enter the IP address of the NTP server (secure). If the NTP server will only be assigned SCALANCE S V4 modules, an FQDN can be specified as an alternative. 5. Specify the encryption parameters for the NTP server (secure). Property Meaning Key ID Numeric value between 1 and 65534. Authentication Select the authentication algorithm. Hex/ASCII Select the format for the NTP key. Key Enter the NTP key with the following lengths: Hex: 22 ... 40 characters ASCII: 11 ... 20 characters 6. Assign a the required security module to the NTP server (secure) you have created, see section: Assigning the security module to an NTP server (secure) (Page 582). 578 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Creating NTP servers in the local security settings 1. Select the module to be edited. 2. Select the "Time-of-day synchronization" entry in the local security settings. 3. Select the required synchronization mode. 4. Enter a name and the IP address of the NTP server. If you have selected the "NTP (secure)" synchronization mode, you can select an NTP server (secure) that you created in the global security settings in the "Name" column. Configuration limits for NTP servers The following rules apply when creating NTP servers: You can create 32 NTP servers throughout the project. You can assign a maximum of 4 NTP servers to one security module. Importing/exporting NTP servers (secure) Using the "Import" or "Export" commands in the shortcut menu, you can export the key list of the currently selected NTP server (secure) and import the file into an NTP server (secure) or vice versa. Configuring time-of-day synchronization for a security module How to access this function 1. Select the module to be edited. 2. Select the "Time-of-day synchronization" entry in the local security settings. 3. Select the "Activate time-of-day synchronization" check box. Alternatives for time-of-day synchronization The following alternatives can be configured: Table 8-23 WinCC Basic V13.0 System Manual, 02/2014 Time synchronization for CP and SCALANCE S Possible selection Meaning / effect Set time of day when loading (only for SCALANCE S) The module time is set automatically to the PC time when a configuration is downloaded. SIMATIC (not for SCALANCE S) If the security module receives MMS time-of-day messages, its local time is synchronized provided the NTP procedure was not configured (MMS = Manufacturing Message Specification). NTP (not for SCALANCE S V3) Automatic setting and periodic synchronization of the time using an NTP server. NTP (secure) (not for SCALANCE S < V4) Automatic setting and periodic synchronization of the time using an NTP server (secure). 579 Editing devices and networks 8.1 Configuring devices and networks Selecting the mode of time-of-day synchronization Follow these steps: 1. Select the synchronization mode. 2. The following configuration options are available to you depending on the selected mode: 580 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Set time of day when loading: When a configuration is downloaded to a SCALANCE S module, the module time of day is set with the PC time of day. SIMATIC: For the CP x43-1 select whether the CP is to adopt or forward the time of day. The CP 1628 always forwards the time of day. For CPs you also the set direction for forwarding the time. Available directions: - Automatic (only for CP x43-1): The CP receives the time from the station or from the LAN and forwards it to the station or to the LAN. If multiple CPs are being operated in the station, this automatic setting can cause collisions. To avoid this, you can specifically define the forwarding direction. - From station (for CP x43-1 only). - From LAN. If forwarding of the time of day is enabled, you can use the "Use corrected time" check box to specify whether or not a correction factor included in the time-of-day frame is used. For the CP 1628, this option is enabled as default and cannot be disabled. NTP: - Time zone: In NTP mode, generally UTC (Universal Time Coordinated) is transmitted. This corresponds to GMT (Greenwich Mean Time). The time offset from UTC can be set by configuring the local time zone. - Update interval in seconds: Defines the interval between the time queries in seconds. For SCALANCE S V3, the time interval for querying the NTP server is specified automatically. Note Setting the update interval for CPs If the "Enable security functions" check box is enabled in the local security settings of a CP, the setting for the update interval is transferred from the CP's local settings into the CP's local security settings. - Time-of-day synchronization on the full minute (for CP x43-1/CP 1628 only): With this option, you can decide whether or not the time of day is forwarded to the communications bus on the full minute. This option is required for certain special applications. - Accept time of non-synchronized NTP servers (only for CP x43-1/CP 1628/CP 1543-1): Here you can specify whether the security module also accepts the time-of-day from non-synchronized NTP servers. - Forward time of day to station (only for CP x43-1/CP 1628): Disable this option if the CPU requests the time separately from an NTP server. This prevents the time on the CPU obtained directly from the NTP server from being overwritten by the time detected in the CP. The accuracy may be reduced slightly due to forwarding via the CP. - NTP server: Creating NTP servers in the local security settings is described in the section Defining an NTP server (Page 578). WinCC Basic V13.0 System Manual, 02/2014 581 Editing devices and networks 8.1 Configuring devices and networks Assigning the security module to an NTP server (secure) Requirement You have defined an NTP server (secure) in the global security settings. "NTP" or "NTP (secure)" is selected as the time-of-day synchronization mode in the local security settings of the security module that you want to assign to an NTP server (secure). Procedure 1. Double-click the "NTP" entry in the global security settings. 2. Double-click the entry "Assign module to an NTP server". 3. From the "NTP Server" drop-down list, select the NTP server (secure) to which you want to assign a security module. 4. In the "Available modules" section, select the security module that you want to assign to the selected NTP server (secure). 5. Click the server (secure). button to assign the selected security module to the selected NTP Result You have assigned the security module to the NTP server (secure). The NTP server (secure) is displayed automatically in the local security settings in the list of NTP servers. Security module as DHCP server Module-specific function The use of the security module as a DHCP server is only possible with SCALANCE S modules, see subsection: Auto-Hotspot in the section "SCALANCE S". Configuring SNMP Overview of SNMP What is SNMP? The security module supports the transfer of management information using the Simple Network Management Protocol (SNMP). For this purpose, an SNMP agent that receives and responds to SNMP requests is installed on the security module. The information on the properties of SNMPcompliant devices is entered in MIB files (MIB = Management Information Base) for which the user must have the required rights. 582 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks In SNMPv1, the "community string" is also sent. The "community string" is like a password that is transmitted along with the SNMP request. If the community string is correct, the security module replies with the required information. If the string is incorrect, the security module discards the query and does not reply. The community string is transmitted via SNMPv1 without encryption. SNMPv3 lets you transmit encrypted data. Configuring SNMP - "SNMP" entry Module-specific function The configuration of SNMP is possible only for SCALANCE S V3 or higher, S7 CPs and the CP 1628. How to access this function 1. Select the module to be edited. 2. In the local security settings, select the entry "SNMP". 3. Activate the "Activate SNMP" check box. 4. Select one of the following SNMP protocol versions: Note Encrypted data transmission with SNMPv3 You should use SNMPv3 to transmit data in encrypted form in order to enhance security. - SNMPv1 The security module uses the following default values for the community strings to control the access rights in the SNMP agent. These default values should be adapted to increase security. For read access: public For read and write access: private To enable write access using SNMP, select the "Allow write access" option. - SNMPv3 Select either only an authentication algorithm or an authentication algorithm and an encryption algorithm. Authentication algorithm: none, MD5, SHA-1 Encryption algorithm: none, AES-128, DES Note Preventing the use of DES DES is an insecure encryption algorithm. Therefore, it should only be used for reasons of down compatibility. WinCC Basic V13.0 System Manual, 02/2014 583 Editing devices and networks 8.1 Configuring devices and networks 5. If SNMPv3 is to be used, assign a user a role with corresponding activated SNMP rights to enable access to the module via SNMP. An overview of SNMP rights is available in the section Managing rights (Page 541). 6. In the "Advanced settings" area, configure module-specific information about the author, location and e-mail address overwriting the information from the project properties. The following applies to values written to the security module by an SNMP tool using an SNMP-SET command: If you select the "Keep values written by SNMP set" check box, the values are not overwritten when there is another download of an SCT configuration to the security module. Configuring proxy ARP Module-specific function This function is available only for SCALANCE S V3 modules or higher, see section Configuring proxy ARP (Page 634) Activate Web server on security module Module-specific function This function is only available for CP x43-1 Advanced, see subsection: Activating the Web server on CP x43-1 Advanced (Page 655) in the section "Security for S7-300 / S7-400 / PC CPs". IPsec tunnel: Creating and assigning VPN groups How to create an IPsec tunnel with VPN groups Module-specific function This function is not available for SCALANCE S602 and CP 1543-1 V1.0. CP 1543-1 supports this function only as of firmware V1.1. Requirement Note Current date and current time of day on the security modules When using secure communication (for example, HTTPS, VPN...), make sure that the security modules involved have the current time of day and the current date. Otherwise the certificates used are not evaluated as valid and the secure communication does not work. 584 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks How to access this function 1. Double-click on the entry "VPN groups" > "Add new VPN group" in the global security settings to create a VPN group. 2. Double-click on the entry "VPN groups" > "Assign module to a VPN group" in the global security settings and assign the security modules and SOFTNET security client modules to the VPN group between which VPN tunnels will be established. Here, note the rules for forming VPN groups. You will also find these rules in the section: Modes of VPN groups (Page 589). Display of the VPN groups with their properties If you select a security module that is in one or more VPN group(s), the properties of the VPN group(s) of which the security module is a member are shown in the "Network data" area. The following properties of the VPN groups are displayed in columns in the "VPN" tab of the "Network data" area: WinCC Basic V13.0 System Manual, 02/2014 Property/column Meaning VPN Names of the VPN groups of which the selected security module is member Security module Names of the assigned security modules Authentication Type of authentication: Preshared key or certificate Group membership until Date and time up to which the VPN group certificate of the security module is valid Type Model numbers of the assigned security modules Comment Comment 585 Editing devices and networks 8.1 Configuring devices and networks Setting the life of certificates Open the dialog in which you can set the expiry date of the certificate as follows: 1. Select the VPN group you want to edit in the "VPN" tab. 2. In the "Properties" > "General" tab of the Inspector window, select the entry "Authentication". Note Expiry of a certificate Communication through the VPN tunnel continues after the certificate has expired until the tunnel is terminated or the SA lifetime expires. For more information on certificates, refer to section: Auto-Hotspot. Quantity structure Number of IPSec tunnels SCALANCE S612 V2 Maximum of 64 SCALANCE S612 V3/V4 Maximum of 128 SCALANCE S613 Maximum of 128 SCALANCE S623 V3/V4 Maximum of 128 SCALANCE S627-2M V4 Maximum of 128 CP x43-1 Advanced Maximum of 32 CP 1628 Maximum of 64 CP 1543-1 V1.1 Maximum of 16 Authentication methods The following methods are available: The authentication method is specified per VPN group and decides the type of authentication used. The following key-based or certificate-based authentication methods are supported: 586 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Preshared key Authentication is achieved using a previously specified character string that is distributed to all modules in the group. Enter a preshared key in the "Key" field under "Authentication" > "General" in the VPN group properties dialog. Certificate Certificate-based authentication "Certificate" is the default setting. The procedure is as follows: - When a group is created, a CA certificate is generated as a root certificate. - Each security module that is a member of the VPN group also receives a group certificate signed with the key of the CA certificate. All certificates are based on the ITU standard X.509v3 (ITU, International Telecommunications Union). The certificates are generated by a certificate authority contained in STEP 7. Note Restriction in VLAN operation No VLAN tagging is transmitted in IP frames via the VPN tunnel of the security module. The VLAN tags included in IP frames are lost when they pass through the security modules because IPsec is used to transfer the IP frames. As default, no IP broadcast or IP multicast frames can be transferred with IPsec through a layer 3 VPN tunnel. Through a layer 2 VPN tunnel of the security module, IP broadcast or IP multicast frames are packaged just like MAC packets including the Ethernet header in UDP and transferred. With these packets, the VLAN tagging is therefore retained. Group properties for selected VPN group VPN group properties Note Knowledge of IPsec necessary To be able to set these parameters, you require IPsec experience. If you do not make or modify any settings, the defaults apply. The following settings can be configured in the properties of a VPN group: Authentication method (entry: "General") IKE settings (entry: "Advanced settings phase 1") IPsec settings (entry: "Advanced settings phase 2") WinCC Basic V13.0 System Manual, 02/2014 587 Editing devices and networks 8.1 Configuring devices and networks How to access this function 1. In the global security settings select the VPN group whose properties you want to configure under the entry "VPN groups". 2. Select "Open" in the shortcut menu of this entry. Result: The VPN group properties appear in the area of the local security settings. 3. In the "Authentication" entry, select whether to use a preshared key or certificate for authentication. For more detailed information, refer to section: Authentication methods (Page 586). Parameters for advanced settings phase 1 - IKE settings Phase 1: Key exchange (IKE = Internet Key Exchange): Here, you set the parameters for the protocol of the IPsec key management. Key exchange is handled by means of the standardized IKEv1 method for which you can set the following protocol parameters: Parameter Description IKE mode Key exchange method: Main mode Aggressive mode The difference between the main and aggressive mode is the "identity protection" used in the main mode. The identity is transferred encrypted in main mode but not in aggressive mode. DH group phase 1 Diffie-Hellman key agreement: Group 1 Group 2 Group 5 Group 14 Diffie-Hellman groups (selectable cryptographic algorithms in the Oakley key exchange protocol). SA lifetime type Phase 1 Security Association (SA): Time: Time limit in minutes The lifetime of the current key material is limited in time. When the time expires, the key material is renegotiated. SA lifetime Numeric value: Range of values for time: 1440 ... 2500000 minutes (default: 2500000) Encryption phase 1 Encryption algorithm: DES*: Data Encryption Standard (56 bit key length, mode CBC) 3DES-168: Triple DES (168-bit key length, mode CBC) AES-128, 192, 256: Advanced Encryption Standard (128 bit, 192 bit or 256 bit key length, mode CBC) Authentication phase 1 Authentication algorithm: MD5: Message Digest Algorithm 5 SHA1: Secure Hash Algorithm 1 588 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks *DES is an insecure encryption algorithm. It should only be used for reasons of down compatibility. DES is not supported by the CP 1543-1 V1.1. Parameters for advanced settings phase 2 - IPsec settings Phase 2: Data exchange (ESP = Encapsulating Security Payload) Here, you set the parameters for the protocol of the IPsec data exchange. The data exchange is in "quick mode". The entire communication during this phase is encrypted using the standardized security protocol ESP for which you can set the following protocol parameters: Parameter Description SA lifetime type Phase 2 Security Association (SA): Time: Time limit in minutes. The lifetime of the current key material is limited in time. When the time expires, the key material is renegotiated. Limit: Limitation of the data volume in MB SA lifetime Numeric value: Range of values for time: 60 ... 16666666 minutes (default: 2880) Range of values for limit: 2000 ... 500000 MB (default: 4000) Encryption phase 2 Encryption algorithm: DES*: Data Encryption Standard (56 bit key length, mode CBC) 3DES-168: Triple DES (168-bit key length, mode CBC) AES-128: Advanced Encryption Standard (128-bit key length, mode CBC) Authentication phase 2 Authentication algorithm: MD5: Message Digest Algorithm 5 SHA1: Secure Hash Algorithm 1 Perfect Forward Secrecy Select whether or not before each time an IPsec-SA is renegotiated, the key is negotiated again using the Diffie-Hellman method. Perfect Forward Secrecy safely prevents the new key from being derived from keys generated previously. *DES is an insecure encryption algorithm. It should only be used for reasons of down compatibility. DES is not supported by the CP 1543-1 V1.1. Modes of VPN groups VPN modes Depending on the mode of the security modules that were added to a VPN group, different modes of VPN groups are distinguished. The mode of a VPN group provides information about the security modules and their modes that can be added to the VPN group. WinCC Basic V13.0 System Manual, 02/2014 589 Editing devices and networks 8.1 Configuring devices and networks Rules for forming groups Remember the following rules if you want to create VPN groups: For SCALANCE S612 / S613 / S623 / S627-2M / SCALANCE M The first module assigned in a VPN group decides which other modules can be added to it. If the first SCALANCE S module to be added is in routing mode or if the first security module is a SCALANCE M module, only additional SCALANCE S modules with routing activated or SCALANCE M modules can be added because SCALANCE M modules always operate in routing mode. If the first SCALANCE S module added is in bridge mode, you can only add other SCALANCE S modules in bridge mode. If you want to change the mode of a VPN group, you have to remove all the modules contained in the group and add them again. A CP and an SSC can be added to a group with a SCALANCE S in bridge or routing mode. For CP / SSC If a CP / SSC is the first module in a VPN group, security modules can be added in any mode. The next security module that decides the mode then also decides the mode of the VPN group. A CP / SSC can be assigned to several VPN groups at the same time and use different modes. The CP / SSC is then operated in mixed mode. It is not possible to add a SCALANCE M module to a VPN group that contains a module in bridge mode. Refer to the following table to see which modules can grouped together in a VPN group: Table 8-24 Security modules and VPN modes Module Can be included in a VPN group in... Bridge mode Routing mode SCALANCE S612 / S613 / S623 / S627-2M in bridge mode x -* SCALANCE S612 / S613 / S623 / S627-2M in routing mode - x CP x43-1 Adv. x x CP 1543-1 V1.1 x x CP 1628 x x SOFTNET Security Client V4.0 x x SCALANCE M875 - x * SCALANCE S623/S627-2M modules in bridge mode can be inserted in a VPN group in routing mode if their DMZ interface is activated (not at the same time). Including security module in configured VPN group The configured VPN group properties are adopted for security modules added to in an existing VPN group. 590 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Procedure after including a security module in a configured VPN group Depending on whether or not you have changed the VPN group properties since the last download, you must make a distinction between the following: Case a: If you have not changed the VPN group properties and the module to be added actively establishes the connection to the configured modules: 1. Add the new security module to the VPN group. 2. Download the configuration to the new module. Case b:If you have changed the VPN group properties or the module being added does not actively establish the connection to the already configured modules: 1. Add the new security module to the VPN group. 2. Download the configuration to all modules that belong to the VPN group. In case a, it is not necessary to reconfigure and load the already commissioned security modules. Active communication is not influenced or interrupted. Settings for nodes with an unknown IP address Nodes whose IP address is unknown at the time of configuration (unknown peers) can be inserted in an existing VPN group. Since the nodes are usually mobile and obtain their IP addresses dynamically (for example a SOFTNET security client or SCALANCE M), the VPN tunnel can only be established if you set the parameters for Phase 1 according to one of the following tables ("Encryption parameter 1 to Encryption parameter 4). If you use other settings, you cannot establish a VPN tunnel to the end device. Table 8-25 Parameter Setting Authentication method Certificate DH group phase 1 Group 2 SA lifetime 1440 ... 2500000 minutes Encryption phase 1 AES-256 Authentication phase 1 SHA-1 Table 8-26 WinCC Basic V13.0 System Manual, 02/2014 Encryption parameter 1 Encryption parameter 2 Parameter Setting Authentication method Certificate DH group phase 1 Group 2 SA lifetime 1440 ... 2500000 minutes Encryption phase 1 3DES-168 Authentication phase 1 SHA-1 591 Editing devices and networks 8.1 Configuring devices and networks Table 8-27 Encryption parameter 3 Parameter Setting Authentication method Certificate DH group phase 1 Group 2 SA lifetime 1440 ... 2500000 minutes Encryption phase 1 DES Authentication phase 1 MD5 Table 8-28 Encryption parameter 4 Parameter Setting Authentication method Preshared key DH group phase 1 Group 2 SA lifetime 1440 ... 2500000 minutes Encryption phase 1 3DES-168 Authentication phase 1 SHA1 Additional restrictions for the SOFTNET Security Client For the SOFTNET security client, the following restrictions also apply: Table 8-29 Encryption parameters for the SOFTNET Security Client Parameter Setting / special feature Encryption phase 1 AES-256 possible only with Windows 7 SA lifetime phase 1 1440 to 2879 minutes SA lifetime type Must be selected identical for both phases Encryption phase 2 No AES 128 possible SA lifetime phase 2 60 to 2879 minutes Authentication phase 2 No MD5 possible Procedure after removing an active member from a VPN group If you remove an active node from an existing VPN group, this can still establish a connection to the group members even if you have downloaded the project to all members of the VPN group again. If you do not want the removed active node to be able to establish the connection any longer, renew the CA group certificate and download the project again to the members of the VPN group. The certificate can be renewed in the group properties of the VPN group or in the "CA" tab of Certificate Manager. 592 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Configuring internal network nodes Overview of configuring internal network nodes Configuring internal network nodes Each security module must know the network nodes in the entire internal network to be able to recognize the authenticity of a frame. The security module must know both its own internal nodes as well as the internal nodes of the security modules in the same VPN group. This information is used on a security module to decide which data packet will be transferred in which tunnel. By adding a security module to a VPN group, the local internal nodes/subnets of the security module are automatically made known to the security module. To allow communication via the VPN tunnel with other subnets or nodes of another subnet, these subnets or nodes need to be enabled for VPN tunnel communication in the configuration. SCALANCE S modules allow network nodes to be learned automatically or configured statically. The mode of the security module also decides the options available for learning internal network nodes. SCALANCE S in bridge mode In bridge mode, you can configure the internal IP/MAC nodes and the internal subnets or alternatively can allow automatic learning of internal nodes by the SCALANCE S. SCALANCE S in routing mode In routing mode there is no automatic learning mode available. Instead, enter entire subnets here that need to be released for tunnel communication. CP x43-1 Advanced and CP 1628 CP x43-1 Adv. Decide whether or not tunnel communication to the CP (Gbit interface) and/or to the internal subnet (PROFINET subnet) is permitted for VPN connection partners in routing mode (SCALANCE S / M). CP 1628 Enter the NDIS nodes you want to be reachable through the tunnel of VPN connection partners in routing mode (SCALANCE S / M). Automatic learning of internal network nodes Module-specific function SCALANCE S modules in bridge mode provide a learning mode with which the internal network nodes can be learned automatically during operation. For more detailed information, refer to WinCC Basic V13.0 System Manual, 02/2014 593 Editing devices and networks 8.1 Configuring devices and networks subsection: Using the learning mode to learn internal nodes (Page 634) in the section "SCALANCE S". Configuring IP network nodes manually for SCALANCE S Module-specific function How to configure IP network nodes for SCALANCE S modules manually is explained in: Configuring IP network nodes manually (Page 636) in the section "SCALANCE S". Configuring MAC network nodes manually for SCALANCE S Module-specific function How to configure MAC network nodes for SCALANCE S modules manually is explained in Configuring MAC network nodes manually (Page 636) in the section "SCALANCE S". Configuring internal subnets for SCALANCE S manually Module-specific function How to configure the internal subnets for SCALANCE S modules is explained in Configuring internal subnets manually (Page 637) in the section "SCALANCE S". Allow access to S7-300 / S7-400 CPs for VPN connection partners Module-specific function How to allow access to S7-300 / S7-400 CPs for VPN connection partners is explained in Allow access to S7-300 / S7-400 CPs for VPN connection partners (Page 655) in the section "Security for S7-300 /S7-400 /PC CPs". Configuring NDIS nodes for PC CPs that can be reached through the tunnel Module-specific function How you configure NDIS nodes for PC CPs that can be reached through the tunnel is explained in Configuring NDIS nodes manually for PC CPs that can be reached through the tunnel (Page 655) in the section "Security for S7-300 / S7-400 / PC CPs". 594 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Configuring module- and connection-specific VPN settings Requirement The module is a member of a VPN group. Module- and connection-specific settings With module- and connection-specific settings, you can configure specific VPN settings. Module-specific settings are configured specifically for a security module while connectionspecific settings are configured specifically for a security module in a certain VPN group. You can configure the following module-specific properties in the local security settings with the "VPN" entry: Dead peer detection Permission to initiate connection establishment Public address (IP address / FQDN) for communication via Internet gateways Nodes that need to be enabled for tunnel communication If you select a security module in the list of VPN groups in the "Network data" area, the following connection-specific VPN settings can be seen and can be configured: Permission to initiate connection establishment Partner modules to which tunnel connections exist Type of transferred packets Selection of the local interface of the selected security module that will serve as the tunnel endpoint Selection of the partner interface that will serve as the tunnel endpoint Dead peer detection (DPD) As default, DPD is enabled. When DPD is enabled, the modules exchange additional messages at selectable intervals if no communication occurs at these points in time. This means that it is possible to recognize WinCC Basic V13.0 System Manual, 02/2014 595 Editing devices and networks 8.1 Configuring devices and networks whether the IPsec connection is still valid or possibly needs to be re-established. If there is no longer a connection, the security associations (SA) of phase 2 are terminated prematurely. If DPD is disabled, the SA is ended only after the SA lifetime has expired. For information on setting the SA lifetime, see section Group properties for selected VPN group (Page 587). Permission to initiate connection establishment You can restrict the permission for initiating the VPN connection establishment to certain modules in the VPN. The decisive factor the setting of the parameter described is the assignment of the IP address for the gateway of the module you are configuring. If a static IP address is assigned, the module can be found by the partner. If the IP address is assigned dynamically and therefore changes constantly, the partner cannot establish a connection as things stand. Mode Meaning Start connection to partner (initiator/ responder) (default) If this option is selected, the module is "active", in other words, it attempts to establish a connection to the partner with a fixed IP address. This option is recommended when you obtain a dynamic IP address from the provider for the gateway of the security module you are configuring. The partner is addressed over its external module IP address or its configured WAP IP address. Wait for partner (responder) If this option is selected, the module is "passive", in other words, it waits for the partner to initiate the connection. This option is recommended when you have been assigned a static IP address by the provider for the gateway of the security module you are configuring. It means attempts to establish a connection can only be initiated by the partner. This partner can, for example, have a dynamic WAN IP address. Note Make sure that you do not set all the modules in a VPN group to "Wait for connection from remote VPN gateway" otherwise no connection is established. WAN IP address / FQDN - IP addresses of the modules and gateways in a VPN over Internet When operating a VPN with IPsec tunnel over the Internet, additional IP addresses are generally required for the Internet gateways such as DSL routers. The individual security or 596 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks SCALANCE M modules must know the external IP addresses of the partner modules in the VPN. Note To use a WAN as an external public network, enter the IP address that you received from the provider as the external IP address, through which the security module is then reachable in the WAN (Internet). To allow the security module to send packets via the WAN, you need to enter your DSL router as "Standard router". If you use a DSL router as Internet gateway, the following ports (at least) must be opened on it: Port 500 (ISAKMP) Port 4500 (NAT-T) To allow this, when you configure the module, you have the option of assigning an external IP address as a "WAN IP address". When you download the module configuration, the group members are then informed of the WAN IP addresses of the partner modules. As an alternative to a WAN IP address, you can also enter an FQDN. If you have configured dynamic DNS on the security module at the same time, this FQDN must match the FQDN from the dyn. DNS configuration tab that is registered with a provider for dynamic DNS. Whether the external IP address, the IP address of the DMZ interface (only SCALANCE S623 / S627-2M) or the WAN IP address / the FQDN will be used can be specified in the modulespecific VPN settings of the security module. In these settings, you can also specify the interface to be used for communication by the nodes of a VPN group and the security module that is authorized to set up connections. If you do not enter an access point here, the external IP address or the IP address of the DMZ interface (SCALANCE S623/S627-2M only) will be used as the VPN endpoint. WinCC Basic V13.0 System Manual, 02/2014 597 Editing devices and networks 8.1 Configuring devices and networks 6HFXULW\0RGXO 6HFXULW\0RGXO :$1 WAN ,QWHUQHW*DWHZD\ ,QWHUQHW*DWHZD\ /$1 /$1 *356,QWHUQHW*DWHZD\ 6&$/$1&(0 /$1 Internal IP address - of a module External IP address - of a module IP address of an Internet gateway (for example, GPRS gateway) IP address (WAN IP address) of an Internet gateway (for example, DSL router) Configuring internal network nodes The configuration of internal network nodes is described in the following section: Auto-Hotspot See also How to create an IPsec tunnel with VPN groups (Page 584) Online functions - test / diagnostics and logging Overview of diagnostics and logging in For test and monitoring purposes, the security module has diagnostic and logging functions. Diagnostic functions These include various system and status functions that you can use for an existing network connection to the security module. Logging functions This involves the logging of system and security events and data packets. 598 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Recording events with logging functions You select the events to be logged in the log settings for the relevant security module. You can configure the following variants for logging: Local logging In this variant, you log events in the local buffer of the security module. You can then access these logs, display them and archive them on the service station in the "Online & diagnostics" dialog. The evaluation of the buffer areas of the security module is only possible if there is a network connection to the selected security module. Network Syslog With Network Syslog, you use a Syslog server that exists in the network. This logs the events according to the configuration in the log settings for the relevant security module. Archiving log data and reading in from a file You can save the logged events for archiving in a log file and open this later even without a network connection to the security module. For more detailed information, refer to section Auto-Hotspot. Function overview online dialog Functions of the "Online & diagnostics" dialog In STEP 7, the security module provides the following functions in the "Online & diagnostics" dialog: Entry in the online dialog Function Status Display of status information about the selected security module, such as the current IP addresses of the interfaces and the current time and date. Interface settings (only for SCALANCE S V3 or higher) Overview of the settings of the individual interfaces. Dyn DNS (only for SCALANCE S V3 or higher) Overview of the settings for dynamic DNS. System log Display of logged system events, starting and stopping logging (only if there is an online connection to SCALANCE S modules) and starting and stopping the reading out of log data from the local buffer of the security module. Audit log Display of logged security events, starting and stopping reading out of log data from the local buffer of the security module. Packet filter log Display of logged data packets, starting and stopping logging (only if there is an online connection to SCALANCE S modules) and starting and stopping the reading out of log data from the local buffer of the security module. ARP table (only for SCALANCE S V3 or higher) Display of the ARP table of the security module. Logged in users (only for SCALANCE S V3 or higher) Shows the users logged in to the Internet page for user-specific IP rule sets. Communication status (not for SCALANCE S602 and CP 1543-1 V1.0) Display of status information about VPN tunnel connections and members of VPN groups to which the selected security module belongs. WinCC Basic V13.0 System Manual, 02/2014 599 Editing devices and networks 8.1 Configuring devices and networks Entry in the online dialog Function Internal nodes (not for SCALANCE S602, CP 1543-1 V1.0 and PC CPs) Display of the learned or configured internal network nodes of the security module. Log files (offline view) System log Display of logged system events as well as starting and stopping the display. Audit log Display of logged security events as well as starting and stopping the display. Packet filter log Display of logged data packets as well as starting and stopping the display. Dynamically updated firewall rules (only for S7 CPs) Display of the IP addresses that were released dynamically over HTTP or HTTPS, or loaded by a user. Date and time (only for SCALANCE S) Date and time setting. Requirements for access The following requirements must be met to use the online functions of a security module: There is a network connection to the selected module The project with which the module was configured is open a user with the required rights must be logged in to the project How to access this function 1. Right-click on the module to process. 2. Select the "Online & diagnostics" command from the shortcut menu. 3. If there is no online connection established to the security module, click the "Connect online" button in the "Diagnostics" entry. Online settings are not saved in the configuration Settings that you make in online mode (for example settings for the logging memory) are not stored in the configuration on the security module. This is why the configuration settings are always applied at the restart of the module. Functions of the online diagnostics Status information of the security module - "Status" entry Meaning Display of the status of the security module selected in the project. Table 8-30 Online & diagnostics: - "Status" entry System and status functions Meaning Overview Hardware type 600 The type of the security module. WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks System and status functions Meaning External IP address The external IP address of the security module. For CP 1628: The IP address of the Industrial Ethernet interface. For S7 CPs: The IP address of the Gbit interface. Internal IP address The internal IP address of the security module. For CP 1628: The IP address of the NDIS interface. If there is more than one NDIS address, only one is displayed. For S7 CPs: The IP address of the PROFINET interface. DMZ IP address (SCALANCE S623 / S627-2M only) The DMZ IP address of the security module. Serial number The serial number of the security module. Order number The MLFB identifier of the security module that is used when ordering. Firmware version The firmware version of the security module. Operating mode Mode of the security module (bridge mode / routing mode) External MAC address The external MAC address of the security module. For CP 1628: The MAC address of the Industrial Ethernet interface. For S7 CPs: The MAC address of the Gbit interface. Internal MAC address The internal MAC address of the security module. For CP 1628: The MAC address of the NDIS interface. For S7 CPs: The MAC address of the PROFINET interface. DMZ MAC address (SCALANCE S623 / S627-2M only) The DMZ MAC address of the security module Hardware release The hardware product version of the security module. C-PLUG Shows whether or not a C-PLUG is inserted. Local time WinCC Basic V13.0 System Manual, 02/2014 601 Editing devices and networks 8.1 Configuring devices and networks System and status functions Current time Meaning Date and time that is displayed on the security module. Format for "German" user interface language: dd.mm.yyyy (date) hh:mm:ss (time) Format for "English" user interface language: mm/dd/yyyy (date) hh:mm:ss AM/PM (time) Format for "French" user interface language: dd/mm/yyyy (date) hh:mm:ss (time) Format for "Italian" user interface language: dd/mm/yyyy (date) hh:mm:ss (time) Format for "Spanish" user interface language: dd/mm/yyyy (date) hh:mm:ss (time) Note (not for CPs) You set the local time on the SCALANCE S module in "Functions" > "Date and time". Operating time Time since the last restart of the security module. Format for "German" user interface language: dddd.hh:mm:ss Format for "English" user interface language: dddd.hh:mm:ss Format for "French" user interface language: dddd.hh:mm:ss Format for "Italian" user interface language: dddd.hh.mm.ss Format for "Spanish" user interface language: dddd.hh:mm:ss Time-of-day source The source from which the date and time are obtained. Configuration Created Date and time when the project was first created. Format for "German" user interface language: dddd.hh:mm:ss hh:mm:ss (time) Format for "English" user interface language: dddd.hh:mm:ss hh:mm:ss AM/PM (time) Format for "French" user interface language: dddd.hh:mm:ss hh:mm:ss (time) Format for "Italian" user interface language: dddd.hh.mm.ss hh.mm.ss (time) Format for "Spanish" user interface language: dddd.hh:mm:ss hh:mm:ss (time) 602 Name File name under which the project was last saved. The name is set by default by STEP 7 and is changed when you rename the project. Author Name of the user who created the project. Is adopted from the project properties. WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks System and status functions Meaning Loaded Date and time when the project was last loaded on the security module. Format for "German" user interface language: dddd.hh:mm:ss hh:mm:ss (time) Format for "English" user interface language: dddd.hh:mm:ss hh:mm:ss AM/PM (time) Format for "French" user interface language: dddd.hh:mm:ss hh:mm:ss (time) Format for "Italian" user interface language: dddd.hh.mm.ss hh.mm.ss (time) Format for "Spanish" user interface language: dddd.hh:mm:ss hh:mm:ss (time) Storage location Specifies the location (e.g. town) to be set using an SNMP tool. For SCALANCE S modules, the storage location can be configured as an alternative in the advanced SNMP settings. File system (not for CPs) RAM Flash Indicates how much RAM and flash is occupied in the file system. Overview of the individual interfaces - "Interface settings" entry Module-specific function This function is available only for SCALANCE S V3 modules or higher, see section Overview of the individual interfaces - "Interface settings" entry (Page 638) Overview of the DDNS settings - "Dynamic DNS" entry Module-specific function This function is available only for SCALANCE S V3 modules or higher, see section Overview of the DDNS settings - "Dynamic DNS" entry (Page 639) Display of the ARP table - "ARP table" entry Module-specific function This function is available only for SCALANCE S V3 modules or higher, see section Display of the ARP table - "ARP table" entry (Page 641) WinCC Basic V13.0 System Manual, 02/2014 603 Editing devices and networks 8.1 Configuring devices and networks Users logged in to the Web page - "Logged in users" entry Module-specific function This function is available only for SCALANCE S V3 modules or higher, see section Users logged in to the Web page - "Logged in users" entry (Page 642) VPN connections of the security module - "Communication status" entry Module-specific function This function is not available for SCALANCE S 602 modules. Meaning Display of the communication status of the following network components: Other security modules of the VPN group to which the selected security module belongs Internal network nodes of these security modules Table 8-31 Online & diagnostics: "Communication Status" entry System and status functions Meaning Known security devices or modules Display of the nodes with which the selected security module is in a VPN group. This also shows whether the tunnel status is active or passive. To obtain additional information on one of the nodes, select this in the list. Note: Configured, inactive tunnels are indicated for CPs only. Endpoints Display of information on the internal network nodes of the security module that you selected in the "Known security devices or modules" table. For each internal network node, this shows whether it was learned or configured. It also shows the subnet in which the internal network node is located. With SCALANCE S modules, the subnet of network nodes is only displayed in bridge mode. Tunnel properties 604 Display of properties of the VPN tunnel established to the security module that you selected in the "Known security devices or modules" table. WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Found internal network nodes - "Internal nodes" entry Module-specific function This function is not available for SCALANCE S602 modules and the CP 1543-1. Meaning Display of all learned and configured network nodes. This also displays whether or not the learning mode of the security module is enabled. Updated firewall rules - "Dynamically updated firewall rules" entry Module-specific function This function is only available for CP x43-1, see subsection: Updated firewall rules - "Dynamically updated firewall rules" entry (Page 656) in the section "Security for S7-300 / S7-400 / PC CPs". Display of the firewall blacklist - "Firewall blacklist" entry Module-specific function This function is available only for SCALANCE S V4 modules or higher, see section Display of the firewall blacklist - "Firewall blacklist" entry (Page 642). Setting the date and time - "Date and Time" entry Module-specific function This function is available only for SCALANCE S modules, see section Setting the date and time - "Date and time" entry (Page 643). Logging functions Logging system events - "System log" entry Meaning Display of logged system events and starting and stopping reading system events from the local memory of the security module. The system log automatically logs successive system events, for example the start of a process. The logging can be scaled based on event classes. WinCC Basic V13.0 System Manual, 02/2014 605 Editing devices and networks 8.1 Configuring devices and networks System and status functions Meaning Start/stop logging (not for CPs) Starts/stops recording of system events. The method and the event classes that are logged are configured in the local security settings. Start/stop reading Starts/stops reading of system events from the local memory of the security module. If you select the "Save log file" check box, the recorded log data is also saved as file. Select the storage location and enter a file name. Note If you select the "Save log file" check box after starting reading, the data read out up to then can no longer be saved in a log file. Clear display Deletes the log data shown in the table. For more information on opening saved system events in log files, refer to section Evaluating system events in offline mode - "System log" entry (offline view) (Page 607). Logging security events - "Audit log" entry Meaning Display of logged security events and starting and stopping reading of security events from the local memory of the security module. The audit log automatically logs successive security-relevant events. This includes, for example, user actions such as enabling and disabling packet logging. System and status functions Meaning Start/stop reading Starts/stops reading of security events from the local memory of the security module. If you select the "Save log file" check box, the recorded log data is also saved as file. Select the storage location and enter a file name. Note If you select the "Save log file" check box after starting reading, the data read out up to then can no longer be saved in a log file. Clear display Deletes the log data shown in the table. For more information on opening security events stored in log files, refer to section Evaluating security events in offline mode - "Audit log" entry (offline view) (Page 608). Logging data packets - "Packet filter log" entry Meaning Display of logged data packets and starting and stopping reading of packet filter events. 606 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks The packet filter log records certain packets of the data traffic. Data packets are only logged if they match a configured packet filter rule (firewall) or to which the basic protection reacts (corrupt or invalid packets). This is only possible when logging is enabled for the packet filter rule. For information about activation of the logging, refer to section Auto-Hotspot. As well as reading the log data from the buffer and transferring it to the display, it can also be saved in a file for archiving. System and status functions Meaning Start/stop logging (not for CPs) Starts/stops logging of data packets. The method with which the data is logged is configured in the local security settings. Start/stop reading Starts/stops reading out of logged data packets from the local memory of the security module. If you select the "Save log file" check box, the recorded log data is also saved as file. Select the storage location and enter a file name. Note If you select the "Save log file" check box after starting reading, the data read out up to then can no longer be saved in a log file. Clear display Deletes the log data shown in the table. Log category Select the data packets for which the logging will be displayed. The selection depends on the settings you configured offline in the local security settings. Only the data packets for which logging was enabled are logged. If you select a category for which logging was not enabled, no data will be logged for this category. For information on opening the stored packet filter log data, refer to section Evaluating packet filter events in offline mode - "Packet filter log" entry (offline view) (Page 608). Evaluating log files in offline mode Evaluating system events in offline mode - "System log" entry (offline view) How to access this function 1. Right-click on the module to process. 2. Select the "Online & diagnostics" command from the shortcut menu. 3. Select "Diagnostics" > "Log files (offline view)" > "System log". WinCC Basic V13.0 System Manual, 02/2014 607 Editing devices and networks 8.1 Configuring devices and networks Meaning Opens logged system events that you saved as a file in the online view. For more information, refer to chapter Logging system events - "System log" entry (Page 605). Evaluating security events in offline mode - "Audit log" entry (offline view) How to access this function 1. Right-click on the module to process. 2. Select the "Online & diagnostics" command from the shortcut menu. 3. Select "Diagnostics" > "Log files (offline view)" > "Audit log". Meaning Opens logged security events that you saved as a file in the online view. For more detailed information, refer to section Logging security events - "Audit log" entry (Page 606). Evaluating packet filter events in offline mode - "Packet filter log" entry (offline view) How to access this function 1. Right-click on the module to process. 2. Select the "Online & diagnostics" command from the shortcut menu. 3. Select "Diagnostics" > "Log files (offline view)" > "Packet filter log". Meaning Opens logged data packets that you saved as a file in the online view. For more detailed information, refer to section Logging data packets - "Packet filter log" entry (Page 606). Download functions Special features when downloading security configurations Security configurations can influence the reachability of the security module for the configuration PC. This, for example, is the case if there is a tunnel connection configured for one security module to another security module in a configuration and this configuration is downloaded from the configuration PC to the security module. After the download by the configuration PC, the security module can no longer be reached and the reachability test performed as default by STEP 7 following the download of the configuration fails. The error message output by STEP 7 relates solely to the reachability test; the actual download of the 608 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks configuration is ensured if the project data is consistent and the IP address relationship between the security module and the configuration PC is correct. Special features when downloading configurations and firmware to SCALANCE S modules are described in the following subsection of the section "SCALANCE S": Auto-Hotspot Uploading configurations to the engineering station Uploading a configuration from a SCALANCE S module or from the CP 1628 to an engineering station is not possible. Uploading a configuration from an S7 CP that supports security to an engineering station is also possible if security features were included in the configuration. Configured security functions are not, however, transferred to the engineering station. In the transferred configuration on the engineering station, the "Activate security features" check box is also deselected. SOFTNET Security Client Using the SOFTNET Security Client Area of application - access over VPN With the SOFTNET Security Client (SSC) PC software, secure remote access is possible from PGs/PCs to automation systems protected by a security module via public networks. You require SOFTNET Security Client V4.0 HF1 for S7-300/S7-400 CPs and for the PC CP 1628. These CPs are not approved for operation with SOFTNET Security Client V4.0. The SOFTNET Security Client has not been released for the CP 1543-1. With the SOFTNET Security Client, a PG/PC is configured automatically so that it can establish a secure IPsec tunnel communication in the VPN (Virtual Private Network) with one or more security modules. This IPsec tunnel communication makes it possible for PG/PC applications such as NCM diagnostics to securely access devices or networks that are located in an internal network protected by SCALANCE S. How does the SOFTNET Security Client work? The SOFTNET Security Client reads the configuration that was created by STEP 7 and determines from the file which certificates are to be imported. The CA certificate and, when applicable, the private key are imported and stored on the local PG/PC. Following this, security settings are made based on the data from the configuration so that applications can access IP addresses downstream from the security modules. If the learning mode is enabled for the internal nodes or programmable controllers, a security policy is first set for secure access to security modules. Then, the SOFTNET Security Client WinCC Basic V13.0 System Manual, 02/2014 609 Editing devices and networks 8.1 Configuring devices and networks addresses the security modules in order to obtain the IP addresses of the relevant internal nodes. The SOFTNET Security Client enters these IP addresses in special filter lists belonging to this security policy. Applications can then communicate with the programmable controllers via VPN. Creating a configuration file in STEP 7 Configuring a SOFTNET Security Client module in the project The SOFTNET security client is created as a module in the project. In contrast to the other security modules, you do not need to configure any further properties. Assign the SSC module to the VPN group or groups at which an IPsec tunnel to the PG/PC is to be set up. Note Refer to the information on parameters in section Including security module in configured VPN group (Page 590). Note If you create several SOFTNET Security Clients within a group, no tunnels are set up between these clients but only from the relevant client to the security modules. Configuration files for the SOFTNET Security Client The interface between STEP 7 as configuration tool and the SOFTNET Security Client is controlled by configuration files. :RUNVWDWLRQ FRPSXWHU ([SRUWRIWKHFRQILJXUDWLRQIRU 62)71(76HFXULW\&OLHQWZLWK GDWDPHGLXP 62)71(7 6HFXULW\&OLHQW The configuration is stored in the following file types: *.dat *.p12 *.cer 610 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Procedure To generate the configuration files, perform the following steps in STEP 7: 1. In the "Devices & networks" view, select the "Topology view" or the "Network view" tab. 2. Insert a PC system of the type "SOFTNET Security Client" in the selected tab from the hardware catalog. 3. Assign the SOFTNET Security Client to the VPN groups in which the PG/PC will communicate over IPsec tunnels. 4. Make sure that the "Generate SSC files" check box is selected under the "Configuration of the SOFTNET Security Client" entry in the local security settings of the SOFTNET Security Client. 5. Select the storage location for the configuration files. 6. Compile the configuration of the SOFTNET Security client to export the configuration file. 7. If you selected certificate as the authentication method, specify a password for the certificate of the VPN configuration. If you do not assign a password, the project name (not the project password) is used as the password. Result: Export of the configuration files is completed. 8. Adopt the files of the type *.dat, *.p12, *.cer on the PG/PC on which you want to operate the SOFTNET Security Client. SCALANCE S Configuring interfaces for SCALANCE S modules Overview Configuring the mode With the mode you specify how interface routing is handled (external/internal). The DMZ interface of the security module (SCALANCE S623/S627-2M only) is always connected in routing mode. For more detailed information, refer to the section Configuring IP address parameters (Page 613) Configuring the interfaces If the external interface or the DMZ interface (SCALANCE S623/S627-2M only) of a security module needs to be configured, it must be activated using the "Activate interface" check box. Set the IP address information for each interface and settings for the individual ports. The WinCC Basic V13.0 System Manual, 02/2014 611 Editing devices and networks 8.1 Configuring devices and networks following options are available with which you can assign an IP address for the external interface and for the DMZ interface in the "General" entry (SCALANCE S623/S627-2M only): Static IP address with subnet mask. For more detailed information, refer to the section Configuring IP address parameters (Page 613) Address assignment using PPPoE. For more detailed information, refer to the section Configuring an Internet connection (Page 615) The internal interface can only be configured using a static IP address. Note External interface and DMZ interface as Internet access The simultaneous operation of PPPoE on the external interface and on the DMZ interface (dual ISP) is not possible. Point to Point Protocol over Ethernet (PPPoE) To allow Internet/WAN access directly via a DSL modem, the IP address on the external interface or on the DMZ interface is assigned using PPPoE. PPPoE is a dial-in protocol for obtaining IP addresses from an Internet service provider (ISP). SCALANCE S is operated here in routing mode. To use this IP address assignment mode, specify the ISP in the "PPPoE" entry. The IP address, the subnet mask, the standard router and the DNS server of the interface are specified by the ISP. Note A configured standard router is not taken into account when using PPPoE. This is assigned dynamically to the module by the ISP. Note No network components between SCALANCE S and DSL modem If the interface of a SCALANCE S module is operated using PPPoE, there must be no other network components between this interface and the connected DSL modem, otherwise the dial-in data of the Internet Service Provider will be transferred unencrypted over this link due to the protocol being used. Configuring media modules In addition to the functions of the SCALANCE S623, the S627-2M has two media module slots in which an electrical or optical media module with two ports can be inserted. This expands both the external and internal interface by up to two ports. In routing mode, the additional ports of the security module can be used to link the external and internal interface to ring topologies. To integrate media modules in the SCALANCE S627-2M, select the security module and change to the device view. Then select the required media modules from the hardware catalog. 612 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks For ports with the port type "Copper", you can set the transmission speed and the duplex method manually using the port mode. For ports with the port type "Optical", the port mode is fixed by the media module used or by the SFP transceiver used and cannot be adapted. You will find information on connecting the media module ports to MRP rings in the following section: Auto-Hotspot See also Setting the operating mode (Page 613) Setting the operating mode How to access this function 1. Select the module to be edited. 2. In the local security settings, select the entry "Mode". Operating mode - possible selections You can change the operating mode in this dialog if the security module is not included in a VPN group. If the security module is in a VPN group, the mode cannot be changed. The selection applies to interface routing between the external and internal interface. The DMZ interface (SCALANCE S623 and S627-2M only) is always connected in routing mode. Bridge mode For operation in flat networks. External and internal interface are in the same IP subnet. For S623 / S627-2M: External and internal interface are in the same IP subnet, the DMZ interface is in a different IP subnet or is deactivated. Routing mode All interfaces are in different IP subnets. If you have activated the routing mode, you must configure an internal IP address and subnet mask for the internal interface of the security module. Note If you have enabled the routing mode for the SCALANCE S module, no MAC firewall rules can be defined. Configuring IP address parameters Meaning Specify network parameters such as the IP address and subnet mask for the interface(s) of the security module. WinCC Basic V13.0 System Manual, 02/2014 613 Editing devices and networks 8.1 Configuring devices and networks How to access this function 1. Select the module to be edited. 2. Select "External interface [P1] red" or "DMZ interface [P3] yellow" in the local security settings. Note Configuration of the internal interface in routing mode If you have selected the "Routing" mode for the security module, you must also configure an internal IP address and subnet mask for the internal interface of the security module. You can access this function in the local security settings under "Internal interface [P2] green" > Ethernet addresses". 3. If applicable, enable the interface using the "Activate interface" check box. 4. Select the "Ethernet addresses" entry. 5. Complete the settings specified in the following table. Parameter Meaning IP address IP address for the external interface. The IP address consists of four decimal numbers from 0 to 255, with each number being separated by a period, for example, 141.80.0.16. Subnet mask The subnet mask consists of four decimal numbers that are separated by period, for example, 255.255.0.0 Use router Select this check box if you want to use a standard router and enter its address in the "Router address" input box. Note Networking the interfaces Network the individual interfaces of the security module with suitable subnets to avoid IP address conflicts. Special features with a standard router If the IP assignment configured is via "PPPoE", no standard router needs to be configured because the standard route is always automatically via the PPPoE interface. If the address assignment configured is with "Static address" and if the security module is connected to the Internet via a DSL (NAPT) router, the DSL router must be entered as the standard router. 614 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Configuring port mode Meaning The port mode specifies the transmission speed and the duplex method. For SCALANCE S V2 modules, the port mode is set to "Autonegotiation" as default. This means the transmission speed and the duplex setting are selected automatically. Moreover, the auto-crossing function is supported. Configurable port modes For SCALANCE S V3 and higher, the following port modes can be configured: Port mode Meaning Autonegotiation The transmission speed and the duplex setting are selected automatically. Note A transmission speed of 1000 Mbps and the autocrossing function are supported only if autonegotiation is selected. 10 Mbps, half and full duplex Transmission speed of 10 Mbps 100 Mbps, half and full duplex Transmission speed of 100 Mbps Configuring an Internet connection Module-specific function This function is available only for SCALANCE S V3 modules or higher. Requirement The "PPPoE" entry is only displayed in the local security settings if the IP assignment method "PPPoE" is configured for one of the interfaces. How to access this function 1. Select the security module to be edited 2. In the local security settings, select the entry "PPPoE". WinCC Basic V13.0 System Manual, 02/2014 615 Editing devices and networks 8.1 Configuring devices and networks Meaning In this entry, you make settings related to the Internet Service Provider (ISP) if a connection using PPPoE is set for one of the interfaces of the security module. Table 8-32 Settings for the ISP account Function Description Authentication Select none or one of the following authentication protocols: PAP (Password Authentication Protocol) CHAP (Challenge Handshake Authentication Protocol) Note Both communications partners have to use the same authentication method otherwise no connection can be established. User name Enter the name for logging in with the ISP account. Password Enter the password for logging in with the ISP account. Repeat password Enter the password for logging in with the ISP account again. Table 8-33 Settings for the connection Function Description Permanent connection Permanent Internet connection. After the connection has been terminated by the provider, the connection is automatically restored even if there are currently no packets to be sent. On-demand connection The Internet connection is established automatically if packets need to be sent to the Internet. In this setting, delays in the sending of packets are possible. Maximum idle time (only with the setting "on-demand connection") If no packets are sent during a certain time, the Internet connection is automatically terminated. In the "Maximum idle time" box, enter the time in seconds after which the connection will be terminated. Permitted values: 10 ... 3600. Forced disconnection (only with the "Permanent connection" setting) Select the check box to be able to adapt the time of the forced disconnection by the security module. Forced disconnection time (only with the "Permanent connection" setting) The provider terminates the Internet connection automatically after a certain period. If you enter a time of day in this box, the security module terminates the Internet connection itself at this time. This allows disconnection of the Internet connection by the provider to be delayed under certain circumstances. A selfinitiated forced disconnection is only possible with an existing permanent connection. Permitted entries: 00:00 ... 23:59 Configuring dynamic DNS Module-specific function FQDNs can be configured for SCALANCE S V3 or higher. The resolution of FQDNs by SCALANCE S modules is possible as of SCALANCE S V4. 616 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Meaning With dynamic DNS, you can access a constantly changing IP address with a permanently defined name (FQDN). This is necessary, for example, if you want to access a server that can be reached via a public IP address that changes. How it works The security module signals the current WAN IP address via which the security module can be reached to a provider for dynamic DNS (for example DynDNS.org, no-ip.com). The provider makes sure that DNS queries sent to the FQDN of the security module are replied to with the current WAN IP address of the security module. Dynamic DNS is permitted on the following interfaces: External interface DMZ interface Setting up dynamic DNS - Requirements Requirement: An account has been created with a provider of dynamic DNS and an FQDN has been registered. Setting up dynamic DNS - Follow the steps below: 1. Select the security module to be edited. 2. In the local security settings, select the entry "DNS". 3. If the security module is downstream from a DSL router or DSL modem, you specify a valid DNS server address. To do this, two options are available: WinCC Basic V13.0 System Manual, 02/2014 Option Meaning Obtain DNS server address automatically The address of the DNS server can be obtained automatically using PPPoE if the security module is connected to the Internet via a DSL modem. Can only be set for the external interface and the DMZ interface. Use the following DNS server address: Enter the address of the preferred and of the alternative DNS server manually. 617 Editing devices and networks 8.1 Configuring devices and networks 4. Activate the "Activate service" check box in the "Primary dynamic DNS service" area and make the following settings: Setting Meaning Provider Choose the provider with which you have set up an account for dynamic DNS. User account with the provider Enter the user name that you specified when you created the account. Password with the provider Enter the password that you specified when you created the account. FQDN Enter the host name (e.g. mysecuritymodule) and the domain name (e.g. dyndns.org) that is registered with the provider separated by a period. If an FQDN is also entered in the "VPN" entry, both must match. Monitor IP address change on DSL router If the security module is connected to the Internet via a DSL router, enabling this function activates the function of the Check IP service. The security module periodically sends queries to determine the current IP address of the DSL router and to detect an IP address change on the DSL router. The IP address specified in this way is sent to the provider with each change ID. Period Specify the interval at which the Check IP service is called. Permitted values: 10 to 1440 minutes 5. In case the primary provider fails, create a second provider in the "Secondary dynamic DNS service" area (optional setting). Setting up a user-defined provider - follow the steps below: Select the "User-defined" entry in the "Provider" drop-down list and make the following entries: 618 Setting Meaning Ignore errors when checking the server certificate To ensure that the authentication data is protected, the certificate of the update server is checked as default. If the certificate check fails, the HTTPS connection is terminated and the account data is not transferred. If you select the check box, the function is disabled, for example if the server certificate of the dynamic DNS service is invalid (for example expired). It is advisable not to ignore the check and not to select the check box. Provider update URL With the predefined providers (DynDNS.org and No-IP.com), the URL is already populated. Check IP service URL With the predefined providers (DynDNS.org and No-IP.com), the URL is already populated. WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Configuring LLDP Module-specific function This function is available only for SCALANCE S V4 modules or higher. Requirement The security module is in routing mode. Meaning LLDP (Link Layer Discovery Protocol) is a protocol used to discover network topologies. A device capable of LLDP can send information about itself to neighboring devices at regular intervals and at the same time receive information from neighboring devices. The received information is stored on every device with LLDP capability in an LLDP MIB file. Network management systems can access these LLDP MIB files using SNMP and therefore recreate the existing network topology. Configurable parameters The degree of activity of the security module in terms of LLDP can be configured under the "LLDP mode" entry of the relevant interface. Parameter Description Name Name of the port for which the setting is configured. LLDP mode Configured LLDP mode: RxTx: LLDP frames can be sent and received Off: No LLDP frames can be sent or received Media redundancy in ring topologies Media redundancy with MRP Module-specific function This function is available only for SCALANCE S627-2M modules. Meaning The term "media redundancy" groups together various methods for increasing availability in Industrial Ethernet networks in which devices can be reached over different paths. This might be achieved by meshing networks, arranging parallel transmission paths or by closing a linear bus topology to form a ring. WinCC Basic V13.0 System Manual, 02/2014 619 Editing devices and networks 8.1 Configuring devices and networks Media redundancy method MRP Media redundancy within a ring topology is available with SIMATIC NET products among other things with the MRP method (Media Redundancy Protocol). With this method, one of the nodes is configured as the redundancy manager. The other nodes are redundancy clients. SCALANCE S627-2M modules can only adopt the role of an MRP client. Using test frames, the redundancy manager checks the ring to make sure it is not interrupted. The redundancy clients forward the test frames. If the test frames of the redundancy manager no longer arrive at the other ring port of the redundancy manager due to an interruption, the redundancy manager switches through its two ring ports and informs the redundancy clients of the change immediately. The time the SCALANCE X switches need to switch through their ring ports as redundancy manager is 200 ms. Note on the use of MRP MRP is supported in ring topologies with up to 50 devices. Exceeding this number of devices can lead to a loss of data traffic. It is recommended that you set the ring ports involved to full duplex and 100 Mbps. Otherwise there may be a loss of data traffic. Possible uses of MRP on media module ports MRP is supported only on the media module ports of the SCALANCE S627-2M. The following table shows the possible uses of MRP on the media module ports of a SCALANCE S627-2M: Ring ports Media module 1 P4 MRP Client Media module 2 P5 P6 P7 - - - - Ring 1 Ring 1 - - - - Ring 2 Ring 2 Ring 1 Ring 1 Ring 2 Ring 2 With two lower-layer rings per SCALANCE S module, layer 3 communication is possible between the rings. Configuring MRP for the security module Requirement The security module is in routing mode. The interfaces of the security module to be connected to MRP rings are networked with the relevant ring managers. 620 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks How to access this function 1. Select the security module to be edited. 2. In the settings of the required interface, select the "Media redundancy" entry. Configurable parameters Parameter Meaning Possible selections MRP domain (only if the "MRP client" media redundancy role is selected) The members of an MRP ring are specified with the help of MRP domains. The same MRP domain must be selected for the interfaces of all modules to be connected to the same MRP ring. Display of the MRP domain used for the interface. Media redundancy role Selection of the media redundancy protocol or disabling of media redundancy for the interface. Not a node in the ring MRP Client Ring port 1 (only when the media redundancy role "MRP client" is selected) Name of the first ring port of the selected interface if the media redundancy role "MRP client" was selected for it. - Ring port 2 (only when the media redundancy role "MRP client" is selected) Name of the second ring port of the selected interface if the media redundancy role "MRP client" was selected for it. - Domain settings Using the domain settings, you can add new MRP domains, edit the names of existing MRP domains and delete existing MRP domains. - Alternative media redundancy protocol Select this check box to Enable interface for other media enable the interface of the redundancy protocols security module for other Disable interface for other media media redundancy protocols. redundancy protocols (default setting) Passive listening Enable this check box if the Activate passive listening selected interface will be Deactivate passive listening (default) connected to third-party networks in which STP/RSTP (Spanning Tree Protocol/ Rapid Spanning Tree Protocol) is used. WinCC Basic V13.0 System Manual, 02/2014 621 Editing devices and networks 8.1 Configuring devices and networks Setting up a firewall Local firewall rules for SCALANCE S modules Configuring a firewall with predefined firewall rules Configuring a firewall using predefined firewall rules How to access this function 1. Select the module to be edited. 2. Select the "Firewall" entry in the local security settings. Firewall enabled as default The "Enable firewall" check box is enabled by default. The firewall is therefore activated automatically and all access from external to the security module is blocked. By clicking the relevant check box, enable the firewall rules for the specific direction. Note Detailed firewall settings in advanced firewall mode In advanced firewall mode, you can restrict firewall rules to individual nodes. To change to advanced firewall mode, select the "Enable firewall in advanced mode" check box. For more detailed information about the advanced firewall mode, refer to the section Overview of local firewall rules (Page 556) Firewall configuration with VPN If the security module is in a VPN group, the "Tunnel communication only" check box is enabled as default. This means that only encrypted IPsec data transfer is permitted via the external interface or via the DMZ interface. If you deselect the check box, tunneled communication and also the types of communication selected in the other boxes are permitted. 622 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Table 8-34 Service Available firewall rules and directions From interna l to extern al From external to internal From internal to DMZ (only for S623 / S627-2M) From Enabled ports DMZ to interna l (only for S623 / S6272M) Allow IP communica tion x x x x - IP communication for the selected communication directions is allowed. Allow S7 protocol x x x x TCP port 102 Communication of the nodes using the S7 protocol is allowed. Allow FTP/ FTPS (explicit mode) x x x x TCP port 20 TCP port 21 For file management and file access between server and client. Allow HTTP x x x x TCP port 80 For communication with a Web server. Allow HTTPS x x x x TCP port 443 For secure communication with a Web server, for example, for Web diagnostics. Allow DNS x x x x TCP port 53 Communication connection to a DNS server is allowed. UDP port 53 Allow SNMP x x x x TCP port 161/162 Meaning For monitoring nodes capable of SNMP. UDP port 161/162 Allow SMTP x x x x TCP port 25 For sending e-mails via an SMTP server. Allow NTP x x x x UDP port 123 For synchronization of the time of day. Allow DHCP x x x x UDP port 67 Only in bridge mode Communication connection with a DHCP server is permitted. Table 8-35 UDP port 68 Logging Option Action when activated Log tunneled packets Only active if the security module is a member of a VPN group. All IP packets transferred via the tunnel are logged. Log blocked incoming packets All incoming IP packets that are discarded are logged. Log blocked outgoing packets All outgoing IP packets that are discarded are logged. You can view the logged packets at the "Packet filter log" entry in the "Online & Diagnostics" dialog. For more detailed information, refer to the section Logging data packets - "Packet filter log" entry (Page 606). WinCC Basic V13.0 System Manual, 02/2014 623 Editing devices and networks 8.1 Configuring devices and networks Configuring a firewall with predefined MAC rules How to access this function 1. Select the module to be edited. 2. Select the "Firewall" entry in the local security settings. Firewall enabled as default The "Enable firewall" check box is enabled by default. The firewall is therefore activated automatically and all access from external to the security module is blocked. By clicking the relevant check box, enable the firewall rules for the specific direction. Note Detailed firewall settings in advanced firewall mode In advanced firewall mode, you can restrict firewall rules to individual nodes. To change to advanced firewall mode, select the "Enable firewall in advanced mode" check box. For more detailed information about the advanced firewall mode, refer to the section Overview of local firewall rules (Page 556). Firewall configuration with VPN If the security module is in a VPN group, the "Tunnel communication only" check box is enabled as default. This means that only encrypted IPsec data transfer is permitted via the external interface or via the DMZ interface. If you deselect the check box, tunneled communication and also the types of communication selected in the other boxes are permitted. Available MAC rules and directions Service From internal to external From external to internal Meaning Allow MAC communication x x The MAC traffic from internal to external and vice versa is allowed. Allow ISO protocol x x The ISO traffic from internal to external and vice versa is allowed. Allow SiClock x x SiClock time frames from internal to external nodes and vice versa are permitted. Allow DCP x x Internal to external or external to internal DCP traffic for IP address assignment is permitted. 624 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Table 8-36 Logging Option Action when activated Log tunneled packets Only active if the security module is a member of a VPN group. All MAC packets transferred via the tunnel are logged. Log blocked incoming packets All incoming MAC packets that are discarded are logged. Log blocked outgoing packets All outgoing MAC packets that are discarded are logged. User-specific IP rule sets Overview Module-specific function This function is available only for SCALANCE S V3 modules or higher. Meaning Initially, individual or multiple users are assigned to user-specific IP rule sets. The user-specific IP rule sets are then assigned to individual or multiple security modules. This makes it possible, to allow user-specific access. If, for example all access to the networks downstream from a security module is blocked, certain nodes can be allowed for a user based on their IP addresses. This means that access is allowed for this user but access remains blocked for other users. User logon via the Internet The user can log in to the external interface or the DMZ interface of the security module via a Web page. If authentication is successful, the predefined IP rule set for this user is enabled. The connection of the security module is via HTTPS using the IP address of the connected port and taking into account the valid routing rules: Example: External interface: 192.168.10.1 Call up of the login page with: https://192.168.10.1/ Users can log on with every role as long as the user is assigned to a user-specific firewall rule set. User-specific IP rule sets are used locally - conventions The same conventions as described in the following section apply: Global firewall rule sets - conventions (Page 549) WinCC Basic V13.0 System Manual, 02/2014 625 Editing devices and networks 8.1 Configuring devices and networks Creating and assigning user-specific IP rule sets Creating user-specific IP rule sets 1. In the global security settings, select the entry "Firewall" > "User-specific IP rule sets" > "IP rule sets". Result: The previously created user-specific IP rule sets are displayed under the selected entry. 2. Double-click on the "Add new IP rule set" entry. 3. Enter the following data: - Name: Project-wide, unique name of the rule set. The name appears in the local rule list of the security module after the rule set is assigned. - Description (optional): Enter a description of the user-specific IP rule set. 4. Enter the firewall rules one by one in the list. Note the parameter description in the following sections: Defining IP packet filter rules (Page 557) Assigning user-specific IP rule sets 1. Within the created user-specific IP rule set, change to the "User" tab. 2. In the "Available users" area, select the users you want to assign to the user-specific rule set. 3. Click the button to assign the selected users to the user-specific rule set. Note Assignment of user-specific IP rule sets A security module can only be assigned one user-specific rule set per user. Due to the assignment, the right to log in to the security module is activated implicitly for all users assigned to the IP rule set. 626 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Result The user-specific rule set is used by the assigned security modules as a local rule set and automatically appears in the local list of firewall rules. The user can log on with the security module. IP packet filter directions SCALANCE S Meaning Possible selections for the communication directions "From" and "To" in the IP rules of the advanced firewall mode. The following directions are available Available options / ranges of values From To Internal External Tunnel WinCC Basic V13.0 System Manual, 02/2014 Security module S602 S61x S623 / S627-2M External x x x Tunnel - x x Any - x x DMZ - - x Internal x x x Internal x x x Any - - x Tunnel - - x DMZ - - x Internal - x x 627 Editing devices and networks 8.1 Configuring devices and networks Available options / ranges of values Any DMZ Security module External - x x DMZ - - x Internal - x x External - - x DMZ - - x Internal - - x External - - x Any - - x Tunnel - - x x = communication direction is configurable - = communication direction is not configurable MAC packet filter directions SCALANCE S Meaning Possible selections for the communication directions "From" and "To" in the MAC rules of the advanced firewall mode. The following directions are available Available options / ranges of values From To Internal External Tunnel Any Security module S602 S61x S623 / S627-2M External x x x Tunnel - x x Any - x x Internal x x x Any - - x Tunnel - - x Internal - x x External - x x Internal - x x External - - x x = communication direction is configurable - = communication direction is not configurable Adapting standard rules for IP services Module-specific function This function is available only for SCALANCE S V3 modules or higher. 628 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Requirement This function is available only in advanced firewall mode. How to access this function 1. Select the security module to be edited. 2. In the local security settings, select the entry "Firewall" > "Standard rules for IP services". Meaning of the advanced settings Parameter Meaning when activated Use advanced status options The permitted number of connections and firewall statuses per time unit is limited. If a network node exceeds this limit, its IP address is entered in the IP blacklist of the security module. The IP blacklist of the security module can be viewed in online mode. Log all activated rules Packets that are allowed according to the default rules for IP services are logged. Enable ICMP test for interfaces Ping queries coming in on an interface of the security module can be forwarded to other interfaces. This means that, for example, ping queries can be made from the external network to the internal interface of the security module. Default firewall rules for SCALANCE S The following table lists the default firewall rules for SCALANCE S modules. In some cases, the firewall rules are only set if the relevant service is used by the security module (e.g. SNMP). Service Direction Interface rerouting outgoing HTTPS X1 interface (red) Interface X2 (green) Interface X3 (yellow) (only for S623, S627-2M) Tunnel interface (not for S602) - x - - x x* x x* ICMP incoming - x - x SNMP incoming x x x x Syslog outgoing x x x x NTP outgoing x x x x DNS outgoing x x x x HTTP outgoing x - x - x - x - VPN (IKE) VPN (NAT Traversal) x - x - BootP Server incoming - x x - BootP Client outgoing - x x - WinCC Basic V13.0 System Manual, 02/2014 629 Editing devices and networks 8.1 Configuring devices and networks x enabled as default - disabled as default * cannot be adapted Specifying routes Meaning Specify routes for addressing subnets that cannot be reached directly via the security module. How to access this function 1. Select the module to be edited. 2. In the local security settings, select the "Routing" entry. 3. Double-click "Add new" in the table to add a route. 4. Enter the following values: Parameter Function Example of a value Network ID Requests to nodes of the subnet with the network ID and the subnet mask specified here are forwarded to the subnet via the specified router IP address. 192.168.11.0 Based on the network ID, the router recognizes whether a destination address is inside or outside the subnet. The specified network ID must not be located in the same subnet as the IP address of the security module. Subnet mask The subnet mask determines the network structure. Based on the network ID, the router recognizes whether a destination address is inside or outside the subnet. 255.255.255.0 Router IP address IP address of the router that connects to the subnet. As an alternative, an FQDN can be entered for SCALANCE S V4 modules. 192.168.10.2 The specified router IP address must be in the same subnet as the IP address of the security module. Activate rerouting (only for SCALANCE S V3/V4 modules) 630 Select this check box if the frames of the entered route will enter and leave on the same interface of the security module (rerouting). Rerouting is only supported on the internal interface of the security module. WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Security module as DHCP server Overview DHCP server Overview You can operate the SCALANCE S module on the internal network and on the DMZ network as DHCP server (DHCP = Dynamic Host Configuration Protocol). This allows IP addresses to be assigned automatically to the devices connected to the internal network. Simultaneous DHCP server operation on both interfaces is possible (SCALANCE S623/ S627-2M only). The IP addresses are either distributed dynamically from an address range you have specified or you can select a specific IP address and assign it to a particular device. If devices on the internal interface or on the DMZ interface should always be assigned the same IP address for firewall configuration, the address assignment must only be static based on the MAC address or based on the client ID. Requirements You configure the devices on the internal network or on the DMZ network so that they obtain the IP address from a DHCP server. Depending on the mode, the security module sends an IP address of the standard router to the nodes in the relevant subnet or you need to inform the nodes in the subnet of a router IP address. Router IP address will be transferred In the following situations, the DHCP protocol of the security module will inform the nodes of the router IP address: - The node is connected to the DMZ interface (SCALANCE S623/S627-2M only) In this case, the security module sends its own IP address as the router IP address. - The node is connected to the internal interface and the security module is configured for router mode In this case, the security module sends its own IP address as the router IP address. - The node is connected to the internal interface and the security module is not configured for router mode, there is, however, a standard router specified in the configuration of the security module. In this case, the security module transfers the IP address of the standard router as the router IP address. Router IP address will not be transferred In the following situations, enter the router IP address manually on the node: - The node is connected to the internal interface and the security module is not configured for router mode. There is also no standard router specified in the configuration of the security module. WinCC Basic V13.0 System Manual, 02/2014 631 Editing devices and networks 8.1 Configuring devices and networks See also Configuring a DHCP server (Page 632) Configuring a DHCP server How to access this function 1. Select the module to be edited. 2. In the local security settings, select the entry "DHCP server". 3. Select the interface for which you want to make the DHCP settings. 4. Make the address assignment. You have the following configuration options: - Static address assignment Devices with a specific MAC address or client ID are assigned the specified IP addresses. You specify these addresses by entering the devices in the address list in the "Static address assignment" group box. - Dynamic address assignment Devices whose MAC address or whose client ID was not specified specifically, are assigned a random IP address from a specified address range. For this purpose, activate the "Dynamic IP address pool" check box. Set the address range in the "Dynamic IP address pool" input area. Note Dynamic address assignment - reaction after interrupting the power supply Please note that dynamically assigned IP addresses are not saved if the power supply is interrupted. On return of the power, you must therefore make sure that the nodes request an IP address again. You should therefore only use dynamic address assignment for the following nodes: Nodes that are used temporarily in the subnet (such as service devices). Nodes that have been assigned an IP address and send this as the "preferred address" the next time they request an address from the DHCP server (for example PC stations). For permanent nodes you should preferably use static address assignment by specifying a client ID or the MAC address. 632 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Consistency check - these rules must be adhered to Remember the following rules when making the entries. Check / rule Check made1) locally Project-wide/ module-wide The IP addresses assigned in the address list in the "Static address assignments" group box must not be in the range of the dynamic IP addresses. x IP addresses, MAC addresses and client IDs may only occur once in the "Static address assignment" table (related to the security module). x For the statically assigned IP addresses, you must specify either the MAC address or the client ID (computer name). x The client ID is a string with a maximum of 63 characters. Only the following characters may be used: a-z, A-Z, 0-9 and - (dash). x Note In SIMATIC S7, a client ID can be assigned to the devices on the Ethernet interface to allow them to obtain an IP address using DHCP. With PCs, the procedure depends on the operating system being used; it is advisable to use the MAC address here for the assignment. For the statically assigned IP addresses, you must specify the IP address. x The following IP addresses must not be in the range of the free IP address range (dynamic IP addresses): x All router IP addresses in the "Routing" entry Syslog server Standard router Security module address(es) DHCP is supported by the security module on the interface to the internal subnet and on the interface to the DMZ network. The following additional requirements for IP addresses in the range of the dynamic address assignments result from this operational behavior of the security module: x Bridge mode The range must be within the network defined by the security module. Routing mode The range must be within the internal subnet defined by the security module. Note The DMZ network always represents a separate subnet. When using DHCP on the DMZ interface, make sure that the free IP address range (dynamic IP addresses) is within the DMZ subnet. The free IP address range must be fully specified by entering the start address and the end address. This end address must be higher than the start address. The IP addresses you enter in the address list in the "Static address assignments" input area must be in the address range of the internal subnet or in the DMZ subnet of the security module. WinCC Basic V13.0 System Manual, 02/2014 x x 633 Editing devices and networks 8.1 Configuring devices and networks Legend: Note the explanations in the section Running a consistency check (Page 533). 1) Configuring proxy ARP Module-specific function This function is available only for SCALANCE S V3 modules or higher. Overview Proxy ARP allows routers to respond to ARP queries for hosts. The hosts are in networks separated by routers but use the same IP address range. If PC1 sends an ARP request to PC2, it receives an ARP response and the hardware address of the interface (MAC address of the port of the security module) on which the query was received from the security module located in between and not from PC2. The querying PC1 then sends its data to the security module that then forwards it to PC2. How to access this function This function is only available for the internal interface of a security module that is a member of a VPN group and is in bridge mode. 1. Select the security module to be edited. 2. In the local security settings, select the entry "Proxy ARP". 3. If the security module is to respond to an ARP query from its own LAN as a substitute for the specific connection partner, enter the corresponding IP address. IPsec tunnel: Creating and assigning groups Configuring internal network nodes Using the learning mode to learn internal nodes Finding nodes for tunnel communication automatically One great advantage when configuring and operating tunnel communication is that SCALANCE S modules in bridge mode can find the nodes on the internal interface automatically. New nodes are detected by the security module during operation. The detected nodes are signaled to the security modules belonging to the same group. This allows data exchange within the tunnels of a group in both directions at any time. 634 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Detectable nodes The following nodes are detected: Network nodes with IP capability Network nodes with IP capability are found when they transmit an ICMP response to the ICMP subnet broadcast. IP nodes downstream from routers can be found if the routers pass on ICMP broadcasts. ISO network nodes You can also teach-in network nodes without IP capability that can be addressed by means of ISO protocols. This is only possible if they reply to XID or TEST packets. TEST and XID (Exchange Identification) are auxiliary protocols for exchanging information on layer 2. By sending these packets with a broadcast address, these network nodes can be located. PROFINET nodes Using DCP (Discovery and basic Configuration Protocol), it is possible to find PROFINET nodes. Network nodes that do not meet these conditions must be configured manually. Subnets located on the other side of internal routers also need to be configured manually. How to access the function 1. Select the module. 2. In the local security settings, select the entry "VPN" > "Nodes". Enabling/disabling the learning mode The learning function is enabled in the configuration as default for every security module. Learning can also be disabled completely for SCALANCE S. In this case, you will need to configure all internal network nodes participating in the tunnel communication manually. When is it useful to disable the automatic learning mode? The default settings for the security module assume that internal networks are always secure; in other words, in a normal situation, no network node is connected to the internal network if it is not trustworthy. Disabling the learning mode can be useful if the internal network is static; in other words, when the number of internal nodes and their addresses do not change. If the learning mode is disabled, this reduces the load on the medium and the nodes in the internal network resulting from the learning packets. The performance of the security module is also slightly improved since it does not need to process the learning packets. WinCC Basic V13.0 System Manual, 02/2014 635 Editing devices and networks 8.1 Configuring devices and networks Note: In the learning mode, all nodes in the internal network are detected. The information relating to VPN configuration limits relates only to nodes that communicate over VPN in the internal network. Note If more than 128 internal nodes are being operated, the permitted configuration limits are exceeded and an illegal operating status results. Due to the dynamics in the network traffic, this causes internal nodes that have already been learned to be replaced by new previously unknown internal nodes. See also Configuring internal subnets manually (Page 637) Configuring IP network nodes manually Meaning As an alternative to the learning mode that you enable using the "Enable learning of internal nodes" check box and that allows the security module to learn the internal network nodes dynamically, you can enter the network nodes to be learned manually in the "Internal IP nodes" entry and in doing so enable them for VPN tunnel communication. The MAC address of a network node can be specified as an option. Requirement The security module is in bridge mode. The security module is a member of a VPN group. How to access this function 1. Select the module to be edited. 2. In the local security settings, select the entry "VPN" > "Nodes" > "Internal IP nodes". Configuring MAC network nodes manually Meaning As an alternative to the learning mode that you enable using the "Enable learning of internal nodes" check box and that allows the security module to learn the internal network nodes dynamically, you can enter the network nodes to be learned manually in the "Internal MAC nodes" entry and in doing so enable them for VPN tunnel communication. 636 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Requirement The security module is in bridge mode. The security module is a member of a VPN group. How to access this function 1. Select the module to be edited. 2. In the local security settings, select the entry "VPN" > "Nodes" > "Internal MAC nodes". Configuring internal subnets manually Requirement The security module is a member of a VPN group. How to access this function 1. Select the module to be edited. 2. In the local security settings, select the entry "VPN" > "Nodes" > "Internal subnets". Security module in bridge mode - "Internal subnets" entry To be able to enable internal subnets for VPN tunnel communication manually, you need to enter the following address parameters: Parameter Function Example of a value Network ID Network ID of the subnet to be enabled for VPN tunnel communication. 192.168.11.0 Based on the network ID, the router recognizes whether a destination address is inside or outside the subnet. Must not be located in the same subnet as the IP address of the security module. Subnet mask The subnet mask determines the network structure. Based on the network ID, the router recognizes whether a destination address is inside or outside the subnet. 255.255.255.0 Router IP address IP address of the router via which the subnet you are allowing is reached. 192.168.10.2 Must be located in the same subnet as the IP address of the security module. WinCC Basic V13.0 System Manual, 02/2014 637 Editing devices and networks 8.1 Configuring devices and networks Security module in routing mode - "Subnets reachable through tunnel" entry In routing mode, entire subnets are always tunneled. To be able to enable internal subnets for VPN tunnel communication manually, you need to enter the following address parameters: Parameter Function Example of a value Network ID Network ID of the subnet to be enabled for VPN tunnel communication. 192.168.11.0 Based on the network ID, the router recognizes whether a destination address is inside or outside the subnet. Must not be located in the same subnet as the IP address of the security module. Subnet mask The subnet mask determines the network structure. Based on the network ID, the router recognizes whether a destination address is inside or outside the subnet. Comment Entry of additional, optional comments. 255.255.255.0 Online functions - testing / diagnostics and logging Overview of the individual interfaces - "Interface settings" entry Module-specific function This function is available only for SCALANCE S V3 modules or higher. 638 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Meaning Table 8-37 Online diagnostics: "Interface settings" entry System and status functions Meaning Interfaces Table above: General overview of the interfaces of the security module. Table below: Information on the interface operated via PPPoE. Status: Indicates whether or not a connection was established to the Internet Service Provider (ISP). Current IP address: Current IP address of the interface Gateway: IP address of the gateway Primary dynamic DNS service: Primary service for dynamic DNS Secondary dynamic DNS service: Secondary service for dynamic DNS Error code (numeric): Error information if no connection could be established to the ISP. Media redundancy (SCALANCE S627-2M only) Interface: Interface connected to the MRP ring Protocol: Protocol used (MRP) Ring port 1: Name of the first media module port of the interface connected to the MRP ring Ring port 2: Name of the second media module port of the interface connected to the MRP ring Domain name: Name of the MRP domain Discrepancy: Displays whether or not there is an error in the MRP configuration Domain UUID: UUID of the MRP domain Media modules (SCALANCE S627-2M only) Port: Port ID(s) of the media module port(s) Name: Name of the media module MLFB: MLFB of the media module Revision: Version of the media module Discrepancy: Displays whether or not there is an error in the configuration of the media module Overview of the DDNS settings - "Dynamic DNS" entry Module-specific function This function is available only for SCALANCE S V3 modules or higher. WinCC Basic V13.0 System Manual, 02/2014 639 Editing devices and networks 8.1 Configuring devices and networks Meaning Table 8-38 Online diagnostics: "Dynamic DNS" System and status functions Meaning Client status Indicates whether or not a connection was established to a dyn. DNS server. Current IP address Own (in other words logged on to dyn. DNS provider) IP address. Defined IP address IP address assigned via PPPoE. Current time The current time-of-day. Force update The security module obtains the current IP address of its Internet access and sends an update query to the configured update server(s). This publishes the current IP address on the Internet. The status is displayed in the primary or secondary dynamic DNS service fields. This means, for example that it is possible to check whether configured data such as the user name and password of the dynamic DNS account are correct. Cancel suspension Cancels the suspension (blocking of IP address updates from the dynamic DNS provider on the security module), for example after the dynamic DNS provider password has been corrected or an error has been eliminated. Primary and secondary dynamic DNS service FQDN Fully Qualified Domain Name registered with the provider. Server IP Address IP address of the update server used. Successful update Successful update in the dynamic DNS update service. Last update attempt Last update attempt for DynDNS update service. Last failed update Last update error in the dynamic DNS update service. Error code Error status of the last unsuccessful update attempt during a dynamic DNS update. What is the meaning of the messages? The messages of the last DDNS update attempt have the following meaning: Message Meaning Success DDNS_OK The update query was successful. Connection-related status messages DDNS_E_CON_UPD_SRV_RESOLV_ERR DDNS_E_CONUPD_SRV_UNREACHABLE Security-related status messages (errors) DDNS_E_CERT_SUBJECT_INVALID DDNS_E_CERT_UNABLE_TO_GET_ISSUER_CERT DNS name of the update server unknown, FQDN cannot be resolved using the known DNS server. Update server unreachable ("Timeout"). The common name of the subject in the certificate does not match the domain name of the update server or its IP address. Issuer certificate not found. The certificate chain could not be followed back to the root CA because an issuer certificate was not found. The trust chain is incomplete. DDNS_E_CERT_SIGNATURE_INVALID 640 The signature of a certificate could not be read or is invalid. WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Message Meaning DDNS_E_CERT_NO_TRUST A certificate in the trust chain is invalid, in other words: Not yet valid or ready expired V3 extensions invalid Critical V3 extension is not supported DDNS_E_CERT_DEPTH_ZERO_SELFSIGNED_CERT The update server has supplied a self-signed certificate and the certificate is not in the certificate store for trustworthy root CA certificates. DDNS_E_CERT_SELF_SIGNED_CERT_IN_CHAIN The certificate chain could be established using non trustworthy certificates but no suitable root CA certificate was found in the certificate store for trustworthy certificates. DDNS_E_CERT_CHAIN_TOO_LONG The certificate chain exceeds the maximum supported verification depth. DDNS_E_CERT_INVALID_CA A CA certificate is invalid, in other words expired, not yet valid or the V3 extensions are not suitable for the intended purpose (for example CA not set to TRUE for CA certificates). DDNS_E_CERT_KEYUSAGE_UNSUITED The V3 extensions key usage or extended key usage set in a certificate of the trust chain are not suitable for the use of the certificate. DDNS_E_CERT_EXTENSION_UNSUPPORTED A certificate in the trust chain used an extension marked as critical that is not supported. Agent-related status messages (errors) DDNS_E_AGT_BAD_AGENT The update request does not correspond to the structure required by cRSP, for example URL parameters missing. The update request was sent to an illegal URL on the update server. The configured update string contains errors. Display of the ARP table - "ARP table" entry Module-specific function This function is available only for SCALANCE S V3 modules or higher. WinCC Basic V13.0 System Manual, 02/2014 641 Editing devices and networks 8.1 Configuring devices and networks Meaning Display of the ARP table of the security module. Table 8-39 Online diagnostics: "ARP table" tab System and status functions Meaning ARP table Display of the static (proxy ARP) and dynamic entries of the ARP table on the security module. The "Publication type" tab specifies whether the entry is configured statically or learnt. Users logged in to the Web page - "Logged in users" entry Module-specific function This function is available only for SCALANCE S V3 modules or higher. Meaning Shows the users logged in to the Internet page for user-specific IP rule sets. System and status functions Meaning User name Name of the logged on user. Source IP address IP address with which the user logged on. Time remaining Remaining time before the user is automatically logged off. Maximum time of the session Configured total time of the session. Log off If you click the button, the selected user is logged off. Display of the firewall blacklist - "Firewall blacklist" entry Meaning Displays the IP addresses of nodes that have exceeded the permitted number of connections and firewall statuses per time unit. These nodes are entered in the IP blacklist of the firewall. The number of connections and firewall statuses per time unit is only limited if the "Use extended status options" check box is selected in the "Standard rules for IP services" entry in the local security settings. If you click the "Delete all" button, the displayed IP addresses are removed from the firewall blacklist of the security module. The IP addresses are also no longer displayed. 642 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Setting the date and time - "Date and time" entry How to access this function 1. Select the security module whose time and date you want to check or set. 2. Select the "Online & diagnostics" command from the shortcut menu. 3. In online diagnostics, select the "Functions" > "Date and time" entry. Setting the local time on the security module In this area, you can read out and set the time and date of the security module. When you click the "Apply" button, the security module is assigned the time and date currently entered in the "Date" and "Time" input boxes. Setting the local time on PC This area shows the current time and current date of the PC on which STEP 7 is installed. If you click the "Adopt for module" button, the security module is assigned the current time and current date of the PC. WinCC Basic V13.0 System Manual, 02/2014 643 Editing devices and networks 8.1 Configuring devices and networks Download functions Downloading a configuration This needs to be taken into consideration before downloading a configuration IP address used for downloading configurations Configurations are always downloaded to the security module using the IP address configured in the local security settings for the internal or external port. This IP address must match that of the security module. Ports You can download the configuration data to the security module both via the external and the internal interface. Ideally, you should configure the modules of a VPN group via the common external network of these modules (device port 1). If the configuration computer is located on an internal network, you must enable the IP addresses of the other modules of the group explicitly in the firewall of this SCALANCE S module and first load this module. Note Selecting a network adapter If you are using more than one network adapter in your PC/PG, first select the network adapter via which you can reach the SCALANCE S module in the "PG/PC Interface" dropdown list of the "Extended download to device" dialog. Operating mode Configurations can be downloaded while the SCALANCE S devices are operating. Restart the SCALANCE S module to activate your configuration changes. Note Special characteristics As long as a module has not yet set IP parameters (in other words, prior to the first configuration), there must be no router between the module and the configuration computer. If you swap a PC from the internal to the external interface of the SCALANCE S, access from this PC to the SCALANCE S is blocked for approximately 20 minutes. Transferring firmware This needs to be taken into consideration before transferring new firmware To transfer new firmware to a security module, the following conditions must be met: You have the rights required to transfer firmware; refer to section Auto-Hotspot. The security module is configured with an IP address. 644 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks The transfer is secure The firmware is transferred over a secure connection and can therefore also be transferred from the unprotected network. The firmware itself is signed and encrypted. This ensures that only authentic firmware can be downloaded to the SCALANCE S module. The transfer can take place during operation The firmware can be transferred while a SCALANCE S module is in operation. Newly downloaded firmware only becomes active after the SCALANCE S module has been restarted. If the transfer is disturbed and aborted, the module starts up again with the old firmware version. Security for S7-300 /S7-400 / PC CPs Setting up a firewall Local firewall rules for S7-300 /S7-400 / PC CPs Overview S7-300 CPs / S7-400 CPs /PC CPs Enabling packet filter rules If you enable the security function for the CPs in the local security settings, initially all access to and via the CP is permitted. To enable individual packet filter rules, select the "Activate firewall" check box. Then enable the required services. Firewall rules created automatically due to a connection configuration have priority over rules set manually. Note Detailed firewall settings in advanced firewall mode In advanced firewall mode, you can restrict firewall rules to individual nodes. To change to advanced firewall mode, select the "Activate firewall in advanced mode" check box. Firewall configuration with VPN If the security module is added to a VPN group, the firewall is enabled by default. In addition, the "Tunnel communication only" check box is enabled. This means that only encrypted IPsec data transfer is permitted via the external interface. External data traffic is blocked. If you deselect the check box, tunneled communication and also the types of communication selected in the other boxes are permitted. WinCC Basic V13.0 System Manual, 02/2014 645 Editing devices and networks 8.1 Configuring devices and networks Updating connection rules Changes to the connection configuration of CPs also change the connection-related firewall rules. To display the modified firewall rules, click the "Update connection rules" button. The modified firewall rules are then displayed in advanced firewall mode. Configuring a firewall with predefined firewall rules - CP x43-1 Advanced Configuring a firewall with predefined IP rules - CP x43-1 Advanced How to access this function 1. Select the module to be edited. 2. In the local security settings, select the entry "Firewall" > "Predefined IP rules". Table 8-40 Available services and directions Service From station/ internal to external External to internal From external to station Enabled ports Meaning Allow IP communicatio n x x x All IP traffic for the selected communication directions is allowed. Allow S7 protocol x x x TCP port 102 Communication of the nodes using the S7 protocol is allowed. Allow FTP/ FTPS (explicit mode) x x x TCP port 20 TCP port 21 For file management and file access between server and client. Allow HTTP x x x TCP port 80 For communication with a Web server. Allow HTTPS x x x TCP port 443 For secure communication with a Web server, for example, for Web diagnostics. Allow DNS x x - TCP port 53 Communication connection to a DNS server is allowed. Allow SNMP x x x UDP port 53 TCP port 161/162 For monitoring nodes capable of SNMP. UDP port 161/162 Allow SMTP x x - TCP port 25 For sending e-mails via an SMTP server. Allow NTP x x - UDP port 123 For synchronization of the time of day. 646 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Table 8-41 Logging Option Action when activated Relevant firewall rule IP log settings Log tunneled packets Log blocked incoming packets Action From To Only active if the security module is a member of a VPN group. All IP packets transferred via the tunnel are logged. Allow Station Tunnel Allow Tunnel Station All incoming IP packets that are discarded are logged. Drop External Station Note Relationship between log settings in default mode and firewall rules Log settings that are made in "Predefined IP rules" and "Predefined MAC rules" have no effect on firewall rules that were automatically created as a result of configuring a connection. This means, for example, that tunneled frames belonging to a configured connection cannot be logged. In advanced firewall mode, logging can be extended to the automatically generated firewall rules of connections. Configuring a firewall with predefined MAC rules - CP x43-1 Advanced How to access this function 1. Select the module to be edited. 2. Select the entry "Firewall" > "Predefined MAC rules". Table 8-42 Available services and directions Service From station to external From external to station Allow MAC communication x x The MAC traffic from station to external and vice versa is allowed. Allow ISO protocol x x The ISO traffic from station to external and vice versa is allowed. Table 8-43 Meaning Logging Option Action when activated MAC log settings Log tunneled packets WinCC Basic V13.0 System Manual, 02/2014 Only active if the security module is a member of a VPN group. All MAC packets transferred via the tunnel are logged. Relevant firewall rule Action From To Allow Station Tunnel Allow Tunnel Station 647 Editing devices and networks 8.1 Configuring devices and networks Option Action when activated MAC log settings Relevant firewall rule Action From To Log blocked incoming packets All incoming MAC packets that are discarded are logged. Drop External Station Log blocked outgoing packets All outgoing MAC packets that are discarded are logged. Drop Station External Note Relationship between log settings in default mode and firewall rules Log settings that are made in "Predefined IP rules" and "Predefined MAC rules" have no effect on firewall rules that were automatically created as a result of configuring a connection. This means, for example, that tunneled frames belonging to a configured connection cannot be logged. In advanced firewall mode, logging can be extended to the automatically generated firewall rules of connections. Configuring a firewall with predefined firewall rules - CP 1628 Configuring a firewall with predefined IP rules - CP 1628 How to access this function 1. Select the module to be edited. 2. Select the "Security" > "Firewall" > "Predefined IP rules" entry. Table 8-44 Available services and directions Service From external to station Enabled ports Meaning Allow IP communication x All IP traffic from external to station is allowed. Allow S7 protocol x TCP port 102 Communication of the nodes using the S7 protocol is allowed. Allow FTP/FTPS (explicit mode) x TCP port 20 For file management and file access between server and client. TCP port 21 Allow HTTP x TCP port 80 For communication with a Web server. Allow HTTPS x TCP port 443 For secure communication with a Web server, for example, for Web diagnostics. Allow DNS x TCP port 53 Communication connection to a DNS server is allowed. UDP port 53 648 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Service From external to station Enabled ports Meaning TCP port 161/162 For monitoring nodes capable of SNMP. Allow SNMP x Allow SMTP x TCP port 25 For sending e-mails via an SMTP server. Allow NTP x UDP port 123 For synchronization of the time of day. UDP port 161/162 Table 8-45 Logging Option Action when activated Relevant firewall rule Action From To Only active if the security module is a member of a VPN group. All IP packets transferred via the tunnel are logged. Allow Station Tunnel Allow Tunnel Station All incoming IP packets that are discarded are logged. Drop External Station IP log settings Log tunneled packets Log blocked incoming packets Note Relationship between log settings in default mode and firewall rules Log settings that are made in "Predefined IP rules" and "Predefined MAC rules" have no effect on firewall rules that were automatically created as a result of configuring a connection. This means, for example, that tunneled frames belonging to a configured connection cannot be logged. In advanced firewall mode, logging can be extended to the automatically generated firewall rules of connections. Configuring a firewall with predefined MAC rules - CP 1628 How to access this function 1. Select the module to be edited. 2. Select the entry "Security" > "Firewall" > "MAC rules". Table 8-46 Available services and directions Service From station to external From external to station Allow MAC level communication x x The MAC traffic from external to the station and vice versa is allowed. Allow ISO communication x x ISO traffic from external to the station and vice versa is allowed. Allow SiClock x x SiClock time-of-day frames from external to the station and vice versa are allowed. WinCC Basic V13.0 System Manual, 02/2014 Meaning 649 Editing devices and networks 8.1 Configuring devices and networks Table 8-47 Logging Option Action when activated Relevant firewall rule MAC log settings Log tunneled packets Only active if the security module is a member of a VPN group. All MAC packets transferred via the tunnel are logged. Action From To Allow Station Tunnel Allow Tunnel Station Log blocked incoming packets All incoming MAC packets Drop that are discarded are logged. External Station Log blocked outgoing packets All outgoing MAC packets Drop that are discarded are logged. Station External Note Relationship between log settings in default mode and firewall rules Log settings that are made in "Predefined IP rules" and "Predefined MAC rules" have no effect on firewall rules that were automatically created as a result of configuring a connection. This means, for example, that tunneled frames belonging to a configured connection cannot be logged. In advanced firewall mode, logging can be extended to the automatically generated firewall rules of connections. IP packet filter directions S7-300-/S7-400-/PC-CPs Meaning Possible selections for the communication directions "From" and "To" in the IP rules of the advanced firewall mode. The following directions are available Available options / ranges of values From Internal External Station Tunnel 650 To Security module Meaning CP x43-1 Adv. CP 1628 Station x - Access from the internal network to the station. Any x - Access from internal to the external network, VPN tunnel partner and the station. Station x x Access from the external network to the station. Any x - Access from external to the internal network and the station. Internal x - Access from the station to the internal network. External x x Access from the station to the external network. Tunnel x x Access from the station to the VPN tunnel partner. Station x x Access via the VPN tunnel partner to the station. WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Available options / ranges of values Any Security module Meaning Any x - Access from VPN tunnel partners to the internal network and the station. External x - Access from the internal network and the station to the external network. MAC packet filter directions S7-300-/S7-400-/PC-CPs Context Possible selections for the communication directions "From" and "To" in the MAC rules of the advanced firewall mode. The following directions are available Available options / ranges of values From To External Station Station Tunnel Security module Meaning CP x43-1 Adv. CP 1628 x x Access from the external network to the station. External x x Access from the station to the external network. Tunnel x x Access from the station to the VPN tunnel partner. Station x x Access via the VPN tunnel partner to the station. Configuring the access list Module-specific function This function is not available for the CP 1628. WinCC Basic V13.0 System Manual, 02/2014 651 Editing devices and networks 8.1 Configuring devices and networks Meaning You set access protection for certain IP addresses using the IP access lists. List entries that have already been created and the corresponding rights are displayed in the local settings of the CP in the entry "Firewall" > "IP rules" (advanced firewall mode). Note Changed behavior after activation of security Once you have activated the security function for a CP, access protection will only apply to the external interface. You can apply access protection to the internal interface as well, by configuring suitable firewall rules in advanced firewall mode. The CP also responds to ARP requests from IP addresses that have not been released (layer 2). If the IP access list of a CP contains no entries and you activate security for the CP, the firewall will be activated and prevent access to the CP from external locations. Configure the corresponding firewall rules in advanced firewall mode so that the CP can be reached. Effect of IP access list entries at activation of security If security is enabled in the local settings of a CP, the corresponding rules are created in the advanced firewall mode. A firewall rule "Allow" > "External" > "Station" is created for an IP address you specified in the address list. The IP address from the IP access list is used accordingly as source IP address. IP addresses from a defined IP address range are also integrated into corresponding firewall rules. Requirements for editing Before you can edit created firewall rules, the following condition must be met: for editing using STEP 7: "Configure security" configuration right for editing using a Web server: Module right "Web: Expand IP access control list" The requirements for editing the IP access lists outside the local security settings are described in the sections on the specific CPs. Connection-related automatic firewall rules Meaning For connections that were configured using CPs, STEP 7 automatically creates firewall rules that allow communication with the partner of the CP in the specified direction (CP active/ passive). The connection establishment directions are taken into account. To display these 652 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks firewall rules, if the advanced firewall mode is enabled, the "Update connection rules" button needs to be clicked. The firewall rules are then displayed in advanced firewall mode. Note Enabling UDP multicast and UDP broadcast connections manually No automatic firewall rules are created for UDP multicast and UDP broadcast connections. To enable the connections, add the relevant firewall rules manually in advanced firewall mode. Depending on how the connection establishment is configured, the following level 3 firewall rules are created. If the security module is in a VPN group, the direction "External" changes to "Tunnel". This applies only to CPs that support VPN. The IP address of the connection partner is entered in the "Source IP address" or "Destination IP address" column of these firewall rules. CP->external Action From To active Allow Station External Drop External Station Drop Station External Allow External Station Allow External Station Allow Station External CP->internal Action From To active Allow Station Internal Drop Internal Station Drop Station Internal Allow Internal Station Allow Internal Station Allow Station Internal passive active and passive passive active and passive For level 2 connections, "Allow" rules are created for both directions. If the security module is in a VPN group, the direction "External" changes to "Tunnel". This applies only to CPs that support VPN. The MAC address of the connection partner is entered in the "Source MAC address" or "Destination MAC address" column of these firewall rules. WinCC Basic V13.0 System Manual, 02/2014 CP->external Action From To active, passive, active and passive Allow Station External Allow External Station 653 Editing devices and networks 8.1 Configuring devices and networks Note Changing the connection configuration Changes to the connection configuration of CPs also change the connection-related firewall rules. To display the modified firewall rules, click the "Update connection rules" button. Conventions for automatically created firewall rules Priority The rules have highest priority and are therefore inserted at the top in the local rule list. Deleting rules The rules cannot be deleted. Logging can be enabled and services can be assigned. Moreover, you may insert a bandwidth and a comment. Changing the action If you set the action from "Allow" to "Drop" or vice versa, this is overwritten again during renewed system synchronization. Select "Allow*" or "Drop*" to retain your changes. In this case, only the IP address is synchronized and the action and direction remain as set. Settings for logging, service, bandwidth and comment are also retained after a renewed system synchronization even without changing the action to "Allow*" or "Drop*". If the configured connection is deleted, the corresponding rules are removed from the list. Security module in VPN group As default, the "Tunnel communication only" check box is enabled. If you deselect the check box, in addition to tunnel communication between tunnel partners, communication is also possible with network nodes to which there is no tunnel. Communication is untunneled if the partner address belongs to a station known in STEP 7 for which no VPN tunnel is configured. Communication is through the tunnel if the partner address is a VPN endpoint. If it is not clear whether connection should bypass or run through the VPN tunnel, the connection is assigned to the VPN tunnel and a message to this effect is displayed. The assignment can be adapted in advanced firewall mode, for example, by changing the "From" direction "Tunnel" to "External". To avoid this adaptation being overwritten by the next system synchronization, the "Allow*" or "Drop*" action must be selected. Note If you want to ensure that only communication through the tunnel is possible, you will need to create suitable firewall rules in advanced firewall mode, for example, for internal nodes or NDIS addresses. To allow only tunneled communication for a CP, add a "Drop" > "Any" > "External" rule. For the CP 1628, add a "Drop" > "Station" > "External" rule. In addition to this, you need to remove existing firewall rules that allow untunneled communication. 654 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Activating the Web server on CP x43-1 Advanced Module-specific function This function is only available for CP x43-1. Meaning After activating the Web server, you have access to the Web pages of the module. In the local security settings, you can restrict access to these Web pages using the HTTPS protocol. This access is controlled using the "Allow access only using HTTPS" check box. In addition, you must configure the firewall accordingly. IPsec tunnel: Creating and assigning groups Configuring internal network nodes - "Nodes" entry Allow access to S7-300 / S7-400 CPs for VPN connection partners Possible selections Decide whether or not the VPN connection partner can have access to the CP and/or the internal subnet of the CP in routing mode (SCALANCE S / M). How to access this function 1. Select the module to be edited. 2. In the local security settings, select the entry "Node". 3. Configure access for the VPN connection partner of the CP in routing mode (SCALANCE S / M): - Allow connection to the CP (Gbit interface) - Allow connection to the internal subnet (PROFINET subnet) Configuring NDIS nodes manually for PC CPs that can be reached through the tunnel Configuring NDIS nodes that can be reached through the tunnel The internal nodes are learned and assigned to the routes dynamically. This concerns the NDIS IP addresses of the Windows PC. WinCC Basic V13.0 System Manual, 02/2014 655 Editing devices and networks 8.1 Configuring devices and networks Follow the steps below 1. Select the module to be edited. 2. In the local security settings, select the entry "Nodes" > "NDIS nodes reachable via tunnel". 3. Enter the NDIS IP addresses. Online functions - Debug / Diagnostics and Logging Updated firewall rules - "Dynamically updated firewall rules" entry Meaning Display of the IP addresses or IP address ranges that were enabled dynamically using HTTP or HTTPS, or loaded by a user. The rights assigned for accessing the S7 CP are displayed for the enabled IP addresses. An update of the IP addresses in this tab can only be triggered by the following events: Extension/modification of the IP access control list Update of firewall rules Dynamic extensions transmitted to the CP at runtime, for example, PROFINET IO devices Since only the dynamically updated firewall rules are displayed here, you also need to take into account the firewall rules that were configured offline and downloaded to the station for a full picture of the current firewall status of the module. Security for S7-1500 CPs Setting up a firewall Local firewall rules for S7-1500 CPs Overview of local firewall rules Enabling packet filter rules If you enable the security function for the CPs in the local security settings, initially all access to and via the CP is permitted. To enable individual packet filter rules, select the "Activate 656 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks firewall" check box. Then enable the required services. Firewall rules created automatically due to a connection configuration have priority over rules set manually. Note Detailed firewall settings in advanced firewall mode In advanced firewall mode, you can restrict firewall rules to individual nodes. To change to advanced firewall mode, select the "Activate firewall in advanced mode" check box. Updating connection rules Changes to the connection configuration of CPs also change the connection-related firewall rules. To display the modified firewall rules, click the "Update connection rules" button. The modified firewall rules are then displayed in advanced firewall mode. Configuring a firewall with predefined firewall rules - CP 1543-1 Configuring a firewall with predefined IP rules - CP 1543-1 How to access this function 1. Select the module to be edited. 2. In the local security settings, select the entry "Firewall" > "Predefined IP rules". Table 8-48 Available services and directions Service From external to station Enabled ports Meaning Allow IP communication x All IP traffic from external to station is allowed. Allow S7 protocol x TCP port 102 Communication of the nodes using the S7 protocol is allowed. Allow FTP/FTPS (explicit mode) x TCP port 20 For file management and file access between server and client. Allow HTTP x TCP port 80 For communication with a Web server. Allow HTTPS x TCP port 443 For secure communication with a Web server, for example, for Web diagnostics. Allow SNMP x TCP port 161/162 For monitoring nodes capable of SNMP. TCP port 21 UDP port 161/162 Allow SMTP x TCP port 25 For sending e-mails via an SMTP server. Allow security diagnostics x TCP port 8448 Allow/do not allow security diagnostics. WinCC Basic V13.0 System Manual, 02/2014 657 Editing devices and networks 8.1 Configuring devices and networks Table 8-49 Logging Option Action when activated IP log settings Log tunneled packets Log blocked incoming packets Relevant firewall rule Action From To Only active if the security module is a member of a VPN group. All IP packets transferred via the tunnel are logged. Allow Station Tunnel Allow Tunnel Station All incoming IP packets that are discarded are logged. Drop External Station Note Relationship between log settings in default mode and firewall rules Log settings that are made in "Predefined IP rules" and "Predefined MAC rules" have no effect on firewall rules that were automatically created as a result of configuring a connection. This means, for example, that tunneled frames belonging to a configured connection cannot be logged. In advanced firewall mode, logging can be extended to the automatically generated firewall rules of connections. Configuring a firewall with predefined IPv6 rules - CP 1543-1 Meaning With the predefined IPv6 rules, you have the option of configuring the firewall for services in which IPv6 is used. By enabling a predefined IPv6 rule in the local security settings of the CP 1543-1 V1.1, the system-defined ICMPv6 services that can be seen in the global security settings in the "ICMP" tab in "Firewall" > "Services" > "Define services for IP rules"are also enabled in the firewall. The firewall of the CP 1543-1 V1.0 allows ICMPv6 packets through even without enabling a predefined IPv6 rule. How to access this function 1. Select the module to be edited. 2. Select the "Firewall" > "Pre-defined IPv6 rules" item in the local security settings. Table 8-50 Available services and directions Service From external to station Enabled ports Meaning Allow IP traffic x All IP traffic from external to station is allowed. Allow S7 protocol x TCP port 102 Communication of the nodes using the S7 protocol is allowed. Allow FTP/FTPS (explicit mode) x TCP port 20 For file management and file access between server and client. Allow HTTP x 658 TCP port 21 TCP port 80 For communication with a Web server. WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Service From external to station Enabled ports Meaning Allow HTTPS x TCP port 443 For secure communication with a Web server, for example, for Web diagnostics. Allow SNMP x TCP port 161/162 For monitoring nodes capable of SNMP. Allow SMTP x TCP port 25 For sending e-mails via an SMTP server. Allow security diagnostics x TCP port 8448 Allow/do not allow security diagnostics via IPv6. UDP port 161/162 Table 8-51 Logging Option Action when activated IP log settings Log tunneled packets Log blocked incoming packets Relevant firewall rule Action From To Only active if the security module is a member of a VPN group. All IP packets transferred via the tunnel are logged. Allow Station Tunnel Allow Tunnel Station All incoming IP packets that are discarded are logged. Drop External Station Note Relationship between log settings in default mode and firewall rules Log settings made in "Predefined IPv6 rules" have no effect on firewall rules that were automatically generated as a result of configuring a connection. This means, for example, that tunneled frames belonging to a configured connection cannot be logged. In advanced firewall mode, logging can be extended to the automatically generated firewall rules of connections. Configuring a firewall with predefined MAC rules - CP 1543-1 How to access this function 1. Select the module to be edited. 2. Select the entry "Firewall" > "Predefined MAC rules". WinCC Basic V13.0 System Manual, 02/2014 659 Editing devices and networks 8.1 Configuring devices and networks Table 8-52 Available services and directions Service From station to external From external to station Allow MAC communication x Allow ISO protocol Allow SiCLOCK Table 8-53 Enabled ports Meaning x - The MAC traffic from external to the station and vice versa is allowed. x x - ISO traffic from external to the station and vice versa is allowed. x x - SiCLOCK traffic from external to the station and vice versa is allowed. Logging Option Action when activated MAC log settings Relevant firewall rule Action From To Log blocked incoming packets All incoming MAC packets that are discarded are logged. Drop External Station Log blocked outgoing packets All outgoing MAC packets that are discarded are logged. Drop Station External Note Relationship between log settings in default mode and firewall rules Log settings that are made in "Predefined IP rules" and "Predefined MAC rules" have no effect on firewall rules that were automatically created as a result of configuring a connection. This means, for example, that tunneled frames belonging to a configured connection cannot be logged. In advanced firewall mode, logging can be extended to the automatically generated firewall rules of connections. IP packet filter directions S7-1500 CPs Meaning Possible selections for the communication directions "From" and "To" in the IP rules of the advanced firewall mode. 660 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks The following directions are available Available options / ranges of values Meaning From To External Station Access from the external network to the station. Station External Access from the station to the external network. Tunnel Access from the station to VPN tunnel partners.* Station Access by VPN tunnel partners to the station.* Tunnel * Not for the CP 1543-1 V1.0. MAC packet filter directions S7-1500 CPs Meaning Possible selections for the communication directions "From" and "To" in the MAC rules of the advanced firewall mode. The following directions are available Available options / ranges of values Meaning From To External Station Access from the external network to the station. Station External Access from the station to the external network. Tunnel Access from the station to VPN tunnel partners.* Station Access by VPN tunnel partners to the station.* Tunnel * Not for the CP 1543-1 V1.0. Connection-related automatic firewall rules Meaning For connections that were configured using CPs, STEP 7 automatically creates firewall rules that allow communication with the partner of the CP in the specified direction (CP active/ passive). The connection establishment directions are taken into account. To display these firewall rules, if the advanced firewall mode is enabled, the "Update connection rules" button needs to be clicked. The firewall rules are then displayed in advanced firewall mode. Note Enabling UDP multicast and UDP broadcast connections manually No automatic firewall rules are created for UDP multicast and UDP broadcast connections. To enable the connections, add the relevant firewall rules manually in advanced firewall mode. WinCC Basic V13.0 System Manual, 02/2014 661 Editing devices and networks 8.1 Configuring devices and networks Depending on how the connection establishment is configured, the following level 3 firewall rules are created. If the CP 1543-1 V1.1 is in a VPN group, the direction "External" changes to "Tunnel". The IP address of the connection partner is entered in the "Source IP address" or "Destination IP address" column of these firewall rules. CP->external Action From To active Drop External Station Allow Station External Drop Station External Allow External Station Allow External Station Allow Station External passive active and passive For level 2 connections, "Allow" rules are created for both directions. If the CP 1543-1 V1.1 is in a VPN group, the direction "External" changes to "Tunnel". The MAC address of the connection partner is entered in the "Source MAC address" or "Destination MAC address" column of these firewall rules. CP->external Action From To active, passive, active and passive Allow Station External Allow External Station Note Changing the connection configuration Changes to the connection configuration of CPs also change the connection-related firewall rules. To display the modified firewall rules, click the "Update connection rules" button. Conventions for automatically created firewall rules Priority The rules have highest priority and are therefore inserted at the top in the local rule list. Deleting rules The rules cannot be deleted. Logging can be enabled and services can be assigned. Moreover, you may insert a bandwidth and a comment. Changing the action If you set the action from "Allow" to "Drop" or vice versa, this is overwritten again during renewed system synchronization. Select "Allow*" or "Drop*" to retain your changes. In this case, only the IP address is synchronized and the action and direction remain as set. Settings for logging, service, bandwidth and comment are also retained after a renewed system synchronization even without changing the action to "Allow*" or "Drop*". If the configured connection is deleted, the corresponding rules are removed from the list. 662 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Security module in VPN group As default, the "Tunnel communication only" check box is enabled. If you deselect the check box, in addition to tunnel communication between tunnel partners, communication is also possible with devices to which there is no tunnel. Communication is untunneled if the partner address belongs to a station known in STEP 7 for which no VPN tunnel is configured. Communication is through the tunnel if the partner address is a VPN endpoint. If it is not clear whether connection should bypass or run through the VPN tunnel, the connection is assigned to the VPN tunnel and a message to this effect is displayed. The assignment can be adapted in advanced firewall mode, for example, by changing the "From" direction "Tunnel" to "External". To avoid this adaptation being overwritten by the next system synchronization, the "Allow*" or "Drop*" action must be selected. Note If you want to ensure that only communication through the tunnel is possible, you will need to create suitable firewall rules in advanced firewall mode. To allow only tunneled communication for a CP, add a "Drop" > "Any" > "External" rule. In addition to this, you need to remove existing firewall rules that allow untunneled communication. 8.1.4 Creating configurations 8.1.4.1 Information about the web server Introduction The web server lets you monitor and administer the CPU through authorized users by means of a network. This permits evaluation and diagnostics over long distances. All you need is a web browser. Alarms and status information are visualized on HTML pages. Web browser You need a web browser to access the HTML pages of the CPU. The following web browsers have been tested for communication with the CPU: Internet Explorer (Version 8) Mozilla Firefox (Version 21) mobileSafari (iOS5) WinCC Basic V13.0 System Manual, 02/2014 663 Editing devices and networks 8.1 Configuring devices and networks Web access to the CPU via PG/PC Proceed as follows to access the web server: 1. Connect the client (PG/PC) to the CPU via the PROFINET interface. 2. Open the web browser. Enter the IP address of the CPU in the "Address" field of the web browser in the format http://ww.xx.yy.zz (example: http://192.168.3.141). The start page of the CPU opens. From the start page, you can navigate to further information. Additional information Additional information about the web server of the various CPU families is available under the key word "Web server" in the information system. Information on creating your own web pages for access to the CPU is available under the keyword "User-defined web pages" in the information system. See also S7-1500 web server (http://support.automation.siemens.com/WW/view/en/59193560) Documentation S7-300 (http://support.automation.siemens.com/WW/view/en/12996906) Documentation S7-400 (http://support.automation.siemens.com/WW/view/en/44444467) S7-1200 web server (http://support.automation.siemens.com/WW/view/en/36932465) 8.1.4.2 Things you should know about PROFIBUS DP operating modes Introduction DP master systems that consist of a DP master and DP slaves which are connected via a bus and communicate with one another via the PROFIBUS DP protocol are referred to as distributed I/O. Below, we refer to communication-capable modules with DP interface that can take on the role of DP master or DP slave. "DP master" and "DP slave" option Communication-capable modules, such as CPUs with DP interface and CPs or CMs with DP interface, have the area "Mode" in their module properties. For S7-300 CPUs with integrated DP interface, for example, you can set the mode "DP master" and "DP slave". A CPU or a CP that is configured as DP slave is also referred to as intelligent DP slave (I-slave). For S7-1500 CPUs with integrated DP interface, only the "DP master" mode is possible. To operate S7-1500 CPUs as I-slave, you have to insert the communication module CM 1542-5 and configure it as DP slave. 664 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks S7-1200 CPUs do not have integrated DP interfaces. To operate an S7-1200 as DP master or DP slave, you must insert a communication module CM 1243-5 (DP master only) or a communication module CM 1242-5 (DP slave only; I-slave). Additional information Additional information on distributed I/O is available under the key word "Distributed I/O" and "I-slave" in the information system. 8.1.4.3 Configuring automation systems Addressing modules Addressing modules Introduction In the device overview, you see the addresses or address ranges of the modules in the I address and Q address columns. There are other addresses as well, which are explained below. I/O address I/O addresses (input/output addresses) are required to read inputs and set outputs in the user program. Input and output addresses are assigned automatically when modules are inserted in the rack. The address of the first channel is the start address of a module. The addresses of the other channels are derived from this start address. The address end is obtained from the modulespecific address length. Device address (e.g., Ethernet address) Device addresses are addresses of programmable modules (Industrial Ethernet addresses). They are required to address the different stations of a subnet, for example, to download a user program to a CPU. Hardware identifier for identifying modules and submodules In addition to the I addresses and Q addresses, a hardware identifier (HW ID) is assigned automatically and is used to address and identify the module. Submodules (units of a module), such as an integrated counter, also receive such a hardware identifier. The hardware identifier consists of an integer and is output by the system with diagnostics alarms to allow the faulty module or the faulty submodule to be localized. In addition, the hardware identifier is used for a number of instructions to address the corresponding module. WinCC Basic V13.0 System Manual, 02/2014 665 Editing devices and networks 8.1 Configuring devices and networks The hardware identifier cannot be changed. Example: Identifying high-speed counters of the S7-1200 CPU The hardware identifier is assigned automatically when components are inserted in the device or network view and in the PLC tags. A name is also assigned automatically for the hardware identifier. The system constants of the PLC tags cannot be changed either. See also Specifying input and output addresses (Page 666) Assigning addresses to a location in the program (Page 667) Introduction to loading a configuration (Page 933) Inspector window (Page 397) Specifying input and output addresses Default input and output addresses are set automatically. You can, however, change the address assignment later. All addresses of modules are located in the process image area. The process image is automatically updated cyclically. Requirement You are in the device view. Procedure To change the preset address range proceed as follows: 1. In the device view, click on the module for which you want to set the start address. 2. Go to "I/O addresses" in "Properties" in the inspector window. 3. Under "Start address" enter the required start address. 4. Press <Return> or click on any object to accept a modified value. 666 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks If you have entered an invalid address, a message indicating the next available address is displayed. Note You can also change the addresses directly in the device overview. See also Editing properties and parameters (Page 423) Input and output addresses in the address overview (Page 425) Assigning addresses to a location in the program You can assign addresses of the I/O channels of modules directly to the points of use in the program or to a tag table. Requirement The device view of the hardware and network editor is open. The zoom level in the device view must be set to at least 200% to allow you to see the individual I/O channels. The instruction window of the programming editor or a tag table is open. WinCC Basic V13.0 System Manual, 02/2014 667 Editing devices and networks 8.1 Configuring devices and networks Procedure To assign I/O channels of modules to the points of use in the program or to a tag table, follow these steps: 1. In the device view, navigate to the module with the desired I/O channel. 2. Click and hold down the mouse button to drag the desired I/O address to the corresponding point of use of the block or to the tag table. 668 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks The address of the module is assigned to the point of use in the program or entered as a tag in the tag table. Note The tag for an input or output of a block can also be dragged to the input or output of a module in order to link the tag to the I/O channel of the module. Signal board Inserting a signal board in a CPU Introduction Signal boards allows you to increase the number of the S7-1200 CPU's own inputs and outputs. Just like all other hardware components, you will find signal boards in the hardware catalog. However, you do not insert signal boards in the rack like other modules but directly in a slot of the CPU itself. Note the following points when using a signal board: Each CPU can have only one signal board inserted in it. A signal board can only be inserted when the slot in the CPU is free. There are various ways of inserting a signal board in a CPU: Double click on a signal board in the hardware catalog when there is a free slot in the CPU Drag from the hardware catalog to a free slot in the CPU Shortcut menu of a signal board in the hardware catalog for copying and pasting Requirement The hardware catalog is open. The S7-1200 CPU has a free slot for the signal board. WinCC Basic V13.0 System Manual, 02/2014 669 Editing devices and networks 8.1 Configuring devices and networks Inserting a signal board in a CPU To insert a signal board in a CPU, proceed as follows: 1. Go to the required signal board in the hardware catalog. 2. Select the signal board you want to use. 3. Drag the signal board to the free slot in the CPU. You have now inserted a signal board in the slot of the CPU. If you are in the network view, you can also drag a signal board to a device. If the CPU has a an empty slot for a signal board, the signal board is inserted automatically into this slot. Configurations for Web server Information about the web server Introduction The web server allows you to monitor the CPU via the Internet or the intranet of your company. This permits evaluation and diagnostics over long distances. Alarms and status information are visualized on HTML pages. Web browser You need a web browser to access the HTML pages of the CPU. The following PC web browsers, for example, are suitable for communication with the CPU: Internet Explorer (Version 8.0, 9.0) Mozilla Firefox (Version 17.0.1 and higher) Google Chrome 23.0 Apple Safari 5.1.7 (Windows) Apple Safari 6.0.2 (Mac) The following Web browsers of mobile devices are also suitable: Internet Explorer 6.0 for HMI Panels Mobile Safari (iOS 5.0.1) 670 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Mobile Android Browser 2.3.4 Mobile Google Chrome 23.0 Reading information via the web server The following information can be read from the CPU. The availability of the respective web pages depends on the CPU and its firmware version. As of firmware version 4, the web pages are also available in several languages. Page/information Description Intro/Introduction Entry page for the standard web pages Start Page The start page provides an overview of general information on the CPU, the name of the CPU, the type of CPU and basic information on the current operating state. Start page with general CPU information Identification Identification information Diagnostic Buffer Diagnostic information Module Information Module information Displays the static identification information such as serial number, order number and version numbers. Displays the content of the diagnostics buffer with the most recent entries first. Displays whether the centrally inserted components of a station are OK, whether there are maintenance requirements or components cannot be reached, for example. As of firmware version 4 a firmware update is possible via this Web page. Communication Communication Varable Status Tags Data Logs (File Browser as of firmware version 4) Displays the communication connections during open communication (OUC); displays resources and address parameters. Displays the status of operands of the user program to monitor and change the values. Data logs in CSV format to transfer to the hard disk of the programming device. The data logs are created with data log instructions in the user program and filled with data. As of firmware version 4 you have access to files of the internal load memory and of the external load memory (Memory Card), for example to the content of the directory "DataLogs" and "Recipes" via the Web page "File Browser". User Pages User pages (if user-defined web pages have been configured and loaded) WinCC Basic V13.0 System Manual, 02/2014 The user web pages deliver a list of web pages with customer-specific web applications. 671 Editing devices and networks 8.1 Configuring devices and networks Web access to the CPU via PG/PC Proceed as follows to access the web server: 1. Connect the client (PG/PC) to the CPU via the PROFINET interface. 2. Open the web browser. Enter the IP address of the CPU in the "Address" field of the web browser in the format http://ww.xx.yy.zz (example: http://192.168.3.141). The start page of the CPU opens. From the start page, you can navigate to further information. See also S7-1200 web server (http://support.automation.siemens.com/WW/view/en/36932465) Standard web pages Requirements for web access The requirements for access to standard CPU web pages are explained in the following, as well as the effects of missing or existing configuration information. Requirement The web server must be started. The web server only starts when it has been activated in the properties of the CPU in the "Web server" section. Note the following: The web pages are normally transmitted via an non-secure connection and are not secured against hacker attacks. If you want to transfer the web pages in encrypted form to the browser, use the URL https://, followed by the IP address of the CPU. Logon No logon is required to access the standard web pages read-only. A user must be logged on to execute certain actions like changing the operating mode of the CPU or for write access. For S7-1200 CPUs up to FW version V3: You must be logged on as "admin" for the actions listed above. The logon input boxes are on the top left of each standard web page. If you log on as "admin", you must enter the user name and password there. Name: admin. 672 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Password: configured CPU password (for password-protected CPU). For S7-1200 CPUs as of FW version 4: You can freely select the names of users and the passwords (CPU parameter "Web server", area "User management"). You assign rights to the users, for example the right to query diagnostics or to update the firmware. JavaScript and cookies The standard web pages use JavaScript and cookies. You must enable both in your web browser. If JavaScript is not enabled, the following limitations apply: Data from standard web pages is not automatically updated. You cannot log on as user. Fields cannot be sorted (module information) If cookies are not enabled, you cannot log on. See also Access for HTTPS (Page 674) Settings for operation Settings for operation To be able to use the web server of an S7-1200-CPU, you must select the CPU in the network view or the device view and make the following settings in the inspector window under "Properties > General > Web server": Enable the web server Restricting access to the CPU to HTTPS transmission protocol (encrypted transmission) Access via port 80 is then blocked. Communication is only possible via port 443. WinCC Basic V13.0 System Manual, 02/2014 673 Editing devices and networks 8.1 Configuring devices and networks Enabling automatic update of web pages The update interval is set by default and cannot be changed. The CPU updates web pages with changing content ( (for example, status information or diagnostics information) at regular intervals. Creating and managing users Users are exclusively entitled to options that are assigned to the access rights. Depending on the CPU and firmware used, you can assign different user rights. Rights that your CPU does not support cannot be activated. A user called "Everybody" with minimal access rights, that you can, however, extend, is set by default in the user list. A user who uses the Web server without entering a password has "Everybody" user rights. You have the possibility of configuring further users with different access rights. These users have to log on with the configured user name and password. WARNING Unauthorized access to the CPU by means of the Web server Unauthorized access to the CPU or the changing of PLC variables to invalid values can result in interruptions of the processes controlled by the CPU and cause death, serious bodily harm or material damage! Since the activation of the Web server allows authorized persons for example to change operating modes, to write-access CPU data or to update the firmware, we recommend that the following security measures be taken: If possible limit access to the HTTPS protocol. Create users with secure passwords. An example of a secure password is one which is only used for a single application, is more than 8 characters long, and consists of lower- and upper-case letters as well as symbols and numbers (?!+%$1234...). In addition, passwords based on common keyboard sequences or words from the dictionary should be avoided. Change the password at regular intervals. Do not extend the rights of the "Everybody" user. Check the PLC variables in the user program and limit the range of values to permissible ranges since users can set invalid values via the Web server. Access for HTTPS Access via HTTPS HTTPS is used for encrypting and authentication of communication between the browser and web server. To transfer data between the browser and the CPU using the HTTPS protocol, enter the URL as https://ww.xx.yy.zz in the address line of your browser, whereby ww.xx.yy.zz stands for the IP address of the CPU. You require a valid, installed certificate for error-free HTTPS access to the CPU. If no certificate is installed a warning is displayed with a recommendation not to use this page. To view the page you must explicitly "Add exception". 674 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks You can receive a valid certificate (Certification Authority) "SIMATIC CONTROLLER" as a download from the "Intro" web page under "Download certificate". The help function for your respective web browser provides information on how to install a certificate. Accessing data of the CPU memory You can access data in the internal or external CPU load memory by means of a standard web page. Use the web page "Data logs" for S7-1200 CPUs up to and including FW version 3. From this web page, you transfer the data logs from the CPU to a drive on your PC. Use the web page "File Browser" for S7-1200 CPUs as of FW version 4. From this web page, you transfer data from the folders "Data logs" or "Recipes", for example, to a drive on your PC. Depending on the file type and the access permissions you have configured for the web server user, you can download, delete, rename or upload the files. The actual directories can only be created, deleted or renamed. Example: Data logs To open a data log, click on the link of the desired data log. You can then open the file (.csv), for example, in Microsoft Excel or in another program you choose or you can save the file. Special note: Data logs are saved in U.S. American CSV format. You can only open the file directly using the U.S. version of Microsoft Excel. If you are using another national version of Microsoft Excel, you must import the file, selecting "comma" in the import assistant as the delimiter. Downloading a data log To download a data log, click on the download icon of the desired data log. You can then open the file (.csv), for example, in Microsoft Excel or in another program you choose or you can save the file. Downloading and clearing or deleting a data log For a CPU with FW version up to V3.0: To download and delete the current entries of the data log, you must be logged on. To do this, click on the "Download and delete" icon of the required data log. You can then open the file (.csv), for example, in Microsoft Excel or in another program you choose or you can save the file. For a CPU as of FW version V4.0: To reset the data log, follow these steps: 1. Open the CSV file, for example with Excel. 2. Delete the rows between the headline and the row with the entry "//END", if this row exists. WinCC Basic V13.0 System Manual, 02/2014 675 Editing devices and networks 8.1 Configuring devices and networks 3. Save the file to a drive on your PC. 4. On the web page "File Browser", delete the data log (which means the CSV file) and load the prepared CSV file to the CPU with the "Upload file" button of the "File Browser" web page. Additional information is available in the S7-1500 CPU system manual. Create and download user-defined websites What you need to know about user-defined web pages Concept The concept of user-defined web pages allows you to access freely-designed web pages of the CPU from a web browser. The web server of the CPU provides this function. You are not dependent on special tools for the design and functionality of the user-defined web pages. You can adapt the pages in the layout with CSS, provide dynamic content with JavaScript or use any framework to produce web pages. The totality of files processed by the web server is also referred to as the "web application". Web application and user program Using HTML code in user-defined web pages, you can also transmit data via a web browser to the user program of the CPU for further processing and can display data from the operand area of the CPU in the web browser. You can use script instructions (such as Javascript) to optimize your web pages, for example to dynamically change contents or validate user entries. To synchronize between the user program and the web server, but also to initialize, you must call the WWW (SFC 99) instruction in the user program. If no interaction is required between the web application and the user program, for example, if a web page only provides static information, only initialization in the user program is required. If a simple data exchange is necessary between PLC tags and tags in web applications, to display the contents of PLC tags or write a value in a PLC tag for example, the syntax for reading and writing tags has to be observed. In this case only an initialization is required in the user program, for example in the startup OB. If a further interaction is required between the web application and the user program, you must handle status and control information from the Web Control DB in addition to the synchronization between Web server and user program. This is the case, for example, when user entries are transmitted via the web browser to the web server for evaluation by the CPU. Unlike simple data exchange, the user program directly influences the time at which the requested web page is relayed back to the web browser. In this case, you must be acquainted with the concept of manual fragments and the structure of the Web Control DB. 676 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Initialization User-defined web pages are "packaged" in data blocks for processing by the CPU. You must generate appropriate data blocks from the source data (HTML files, images, JavaScript files, etc.) during configuration to be able to download the web application into the CPU. The Web Control DB takes on a special role (default: DB 333). It contains status and control information as well as links to additional data blocks with coded web pages. Data blocks that contain coded web pages are termed "Fragment DBs". When the data block is downloaded into the CPU, the CPU does not "know" that user-defined web pages are coded inside it. The "WWW" (SFC 99) instruction, for example, in the Startup OB informs the CPU which DB is the Web Control DB. The user-defined web pages can be accessed via a web browser after this initialization. Synchronization If the user program is to exchange data with the user-defined web pages, the WWW (SFC 99) instruction must be used in the cyclic program section. Examples of interaction between user program and web page: Check received data Compiling and returning data for web browser making request In this case, the status information must be able to be evaluated and control information must be transmitted to the web server, for example, to release a requested web page. Procedural overview Basic information This section provides a step-by-step explanation of the basic procedure used to create and download custom web pages and to use them in the operating phase. The following graphic provides a simplified representation of the process used in creating and displaying custom web pages: WinCC Basic V13.0 System Manual, 02/2014 677 Editing devices and networks 8.1 Configuring devices and networks +70/ *,) ::: Programming a web application (using suitable tools when required and AWP commands for dynamic pages when applicable). The web application is comprised of single source files, for example, *.html, *.gif, *.js, etc. Using STEP 7: Generate the data blocks (Web Control DB and fragment DBs) from source files. The DBs contain meta information and the complete web application, including the images and the dynamic and static parts of the web application. The DBs are stored under "System blocks" in the project tree. Call the "WWW" instruction in the user program. This instruction initializes the web server of the CPU for a web application. If required, complete final programming for interaction between the web server and user program Downloading the blocks to the CPU. Call the web page in the browser. The web pages of the CPU are called by entering the IP address of the CPU. Additional information You can find additional information and examples relating to the S7-1200 web server on the Internet (http://support.automation.siemens.com/WW/view/en/36932465). Creating web pages Web design tools from various companies can be used to create user-defined web pages. As a rule, the web pages should be programmed and designed compliant to the conventions of the W3C (World Wide Web Consortium). No check is made for compliance to W3C criteria in the web server of the CPU. 678 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Rules The tool must be able to directly edit the HTML code so that the AWP command can be inserted into the HTML page. Only the AWP commands are parsed in the CPU and, for example, replaced by values from the user program/process image of the CPU. Files containing AWP commands must be coded in UTF-8. In the metadata of the HTML page, therefore, set the attribute charset to UTF-8 and save the file UTF-8 coded. Files containing AWP commands must not contain the following sequence: ]] Files containing AWP commands must not contain the following sequence outside of the "Tag read ranges" (:=<Tag name>:): := Tip: Replace the first character of a prohibited sequence with its character coding; for the colon, for example, &#58;. A small example for a custom web page should make clear the basic design. Requirement The CPU must have a web server and the web server of the CPU must be activated. To be able to access PLC tags with write access as a user, you must be logged on as "admin". For the example below, PLC tags must be defined for those PLC tags that are to be shown on the web page. This is shown here for the first tab used, "Tank_below_max". Creating user-defined web pages The following code for an example web page reads values from the process image and provides them in a table. <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/ TR/html4/strict.dtd"> <html> <head> <meta http-equiv="Content-Type" content="text/html; charset=utf-8"> <title>Mix</title> </head> <body> <h1>Mix</h1> <h2> Actual State </h2> <table border="1"> <tr> <th>Variable</th> <th>State</th> </tr> <tr> <td>Tank below max</td> <td>:="Tank_below_max":</td> WinCC Basic V13.0 System Manual, 02/2014 679 Editing devices and networks 8.1 Configuring devices and networks </tr> <tr> <td>Tank above min</td> <td>:="Tank_above_min":</td> </tr> </table> </body> </html> AWP commands The interface between a freely-programmable web application for a CPU that has a web server and the CPU data is declared by the AWP command (Automation Web Programming). To develop web applications you are only subject to the restrictions of the web browser. In one of the programming languages of STEP 7, control with the user program which CPU data is displayed at what time in the web browser of the viewer. Use AWP commands, which you comment within the HTML files, to declare data to be used for intentional interaction between the web application and the user program. AWP commands are inserted as HTML comments with a special syntax into HTML files; they declare the following features: Read PLC tags Write PLC tag Read special tags Write special tags Define enum types Assign tags to enum types Defining fragments Import fragments Syntax of AWP commands An AWP command begins with "<!--AWP_" and ends with "-->". In JavaScript files, the commands should also be enclosed by JavaScript comments ("/*...*/"). Notation rules for PLC tag names within an AWP command The AWP commands "AWP_In_Variable" and "AWP_Out_Variable" contain a name attribute and optionally a use attribute. A PLC tag name is assigned to these attributes, by means of which the PLC tags in the browser are written or read. The following rules apply to handling PLC tag names in HTML code: PLC tags must be enclosed in quotation marks (" ... "). PLC tags used in AWP commands must also be enclosed by single quotation marks ('" ... "') or with quotation marks masked by a backslash ("\" ... \""). 680 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks If the PLC tag name contains the character \ (backslash), this character must be designated with the escape sequence \\ as standard character of the PLC tag name. If the PLC tag name in the AWP command is also enclosed by single quotation marks and the single quotation mark (') occurs within the name, it must also be designed as normal character by the escape sequence \'. If an absolute address (input, output, bit memory) is used in AWP command, it is enclosed by single quotation marks. PLC tag PLC tag in HTML code "Velocity" <!-- AWP_In_Variable Name='"Velocity"' --> <!-- AWP_In_Variable Name="\"Velocity\"" --> "abc\de" <!-- AWP_In_Variable Name='"abc\\de"' --> "abc'de" <!-- AWP_In_Variable Name='"abc\'de"' --> "abc'de" <!-- AWP_In_Variable Name="abcde" Use'"abc\'de"' --> "DB name".tag <!-- AWP_In_Variable Name='"DB name".tag' --> "DB name"."ta.g" <!-- AWP_In_Variable Name='"DB name"."ta.g"' --> - <!-- AWP_Out_Variable Name='flag1' Use='M0.0' --> See also Reading tags (Page 681) Writing tags (Page 683) Special tags (Page 684) Reading tags User-defined web pages can read PLC tags. The PLC tag must be specified by a PLC tag name. These OUT variables (direction of output as viewed from the controller) are inserted at any location within the HTML text with the syntax described in the following. Syntax :=<varname>: These references are replaced when the web server is in operation by the current values of the PLC tag in each case. <varname> can be a simple, global PLC tag but also a complete tag path to a structural element. WinCC Basic V13.0 System Manual, 02/2014 681 Editing devices and networks 8.1 Configuring devices and networks Notation rules for PLC tag names PLC tags in HTML code are enclosed by quotation marks ("), if they are defined in the tag table. In the case of data block tags, the name of the data block is enclosed by quotation marks. If special characters are used in the structure elements of the data block, for example the dot (.) or blank, this part must also be enclosed by quotation marks. Quotation marks are not used for absolute addresses of inputs, outputs or bit memories. PLC tag PLC tag in HTML code "DB_name".var_name :="DB_name".var_name: "DB_name"."var.name" :="DB_name"."var.name": "memory" :="memory": - :=I0.0: :=Q0.0: :=MW100: :=%MW100: "My_Data_Block".flag1 <!-- AWP_Out_Variable Name='flag1' Use='"My_Data_Block".flag1' --> ... :=flag1: If the PLC tag name contains the character : (colon) or \ (backslash), this character must be designated with the escape sequence \: or \\ as standard character of the PLC tag name. PLC tag PLC tag in HTML code "abc:de" :="abc\:de": "abc\de" :="abc\\de": Special characters "<, &, >" Display problems can occur if these characters are contained in the tag name (for example, "a<b"). Avoid expressions such as :="a<b": in the HTML page. To prevent display problems from occurring, use e.g. an AWP command with a use expression according to the pattern depicted below. The use attribute defines the PLC tag with the problematic character, the name attribute defines the name without problematic character, as it is used in the HTML page. PLC tag "a<b" PLC tag in HTML code <!--AWP_Out_Variable Name='simplename' Use='"a<b"' --> ... :=simplename: See also AWP commands (Page 680) 682 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Writing tags Custom web pages can write data into the CPU. This requires an AWP command that identifies the PLC tag to be written. The PLC tag must also be specified by a PLC tag name. The IN tags (direction of input as viewed from the controller) are placed on the browser page. This can be done, for example, in a form. The tags are either set in the HTTP header (by cookie or POST method) or in the URL (GET method) by the browser and are then written by the web server into the respective PLC tag. Syntax To allow the IN tags to be written to the CPU, the tags must first be defined by an explicit AWP instruction: <!-- AWP_In_Variable Name='<PLC_Varname1>' Name='<PLC_Varname2>' Name='<PLC_Varname3>' --> Several tags can be defined in an instruction - such as that shown above. The specific PLC tag name is hereby written in double quotation marks; for example <PLC_Varname1> = "myVar". In cases where the name of the tag that you use for the web application is not identical to the name of the PLC tag, the "Use" parameter can be used to assign to a PLC tag. <!-- AWP_In_Variable Name='<Webapp_Varname>' Use='<PLC_Varname>' Example The "AWP_In_Variable" AWP command is indispensable when handling forms. <form method='post' action='/awp/appl/x.html'> <p> <input name='"var1"' type='text'> <input value='set' name='Button1' type='submit'> </p> </form> In the form defined above, the HTTP request method "post" is used to transfer the tag "var1" to the web server. The user places the "var1" tag in the form field. The tag 'Button1' has the value 'set', but is not required for the CPU. To allow the "var1" tag to be written to the CPU, the following instruction must be included in the same fragment: <!-- AWP_In_Variable Name='"var1"' --> Since PLC tags are enclosed in double quotation marks ("), the name in the AWP command must be enclosed in single quotation marks (') or in masked quotation marks (\"). To avoid the numerous escape sequences, we recommend the use of single quotation marks. <!-- AWP_In_Variable Name='"Info".par1' --> <!-- AWP_In_Variable Name="\"Info".par1\"" --> WinCC Basic V13.0 System Manual, 02/2014 683 Editing devices and networks 8.1 Configuring devices and networks Conditions for write access during operation The following requirements have to be met in order for a user to be able to write to PLC tags from a user-defined web page. The CPU is is password protected. The user is logged in as "admin". This rules applies to all writing access to web pages on a CPU. See also Requirements for web access (Page 672) AWP commands (Page 680) Special tags Special tags are mainly HTTP tags set in the definition of the World Wide Web Consortium (W3C) . Special tags are also used for cookies and server tags. The AWP command to read and write special tags differ only in that they have additional parameters than the AWP command used to read and write normal tags. Reading a special tag The Web server can read PLC tags and transfer these to special tags in the HTTP Response Header. You can, for example, read a URL for a diversion to another web page and transfer to the special tag HEADER:Location using the special tag HEADER:Location. The following special tags can be read: Name Description COOKIE_VALUE:name Value of cookie with name: "name" COOKIE_EXPIRES:name Execution time of cookie with name: "name" in seconds (must be set beforehand). HEADER:Status HTTP status code (if no other value has been set, status code 302 is returned). HEADER:Location Path for forwarding to another page. Status code 302 must be set. HEADER:Retry-After Anticipated time in which the service is not available. Status code 503 must be set. HEADER: ... All other header tags can also be forwarded in this way. Use the AWP command "AWP_Out_Variable" to specify which PLC tags are to be transferred in the HTTP header to the web browser. Basic structure: <!-- AWP_Out_Variable Name="<Typ>:<Name>" [Use="<Varname>"] --> 684 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Parameter description Name: Type and name of special tag Use (optional parameter): In cases where the name of the special tag is not identical to the name of the PLC tag, parameter "Use" can be used to assign to a PLC tag. Example: <!-- AWP_Out_Variable Name="COOKIE_VALUE:siemens" Use='"info".language' --> Writing a special tag In principle, all HTTP tags written in the HTTP header by the web browser can be evaluated by the user program of the CPU. Examples of tag types: Name Description HEADER:Accept-Language Accepted or preferred language HEADER:Authorization Proof of authorization for a requested resource HEADER:Host Host and port of the requested resource HEADER:User-Agent Information on the browser HEADER: ... All other header tags can also be forwarded in this way SERVER:current_user_id Indicates whether a user is logged on (current_user_id=0: no user logged on) SERVER:current_user_name User name of the user logged on SERVER:GET Request method is GET SERVER:POST Request method is POST COOKIE_VALUE:name Value of cookie with name: "name" The AWP command "AWP_In_Variable" is used to define which special tags are to be evaluated in the user program of the CPU. Basic structure: <!-- AWP_In_Variable Name="<Typ>:<Name>" [Use="<Varname>"] --> Parameter description: Name: Type and name of special tag Use (optional parameter): In cases where the name of the special tag is not identical to the name of the PLC tag, the parameter Use can be used to assign to a PLC tag. WinCC Basic V13.0 System Manual, 02/2014 685 Editing devices and networks 8.1 Configuring devices and networks Examples: <!-- AWP_In_Variable Name="COOKIE_VALUE:siemens" Use='"info".language' --> The tag name in the HTTP header is replaced by the PLC tag name specified by Use . The cookie is written to the PLC tag "info".language . <!-- AWP_In_Variable Name='COOKIE_VALUE:siemens' Use='"info".language' --> The tag name in the HTTP header is replaced by the PLC tag name specified by Use. The cookie is written to the PLC tag "info".language . <!-- AWP_In_Variable Name='"COOKIE_VALUE:siemens"' --> The HTTP-header variable is written in the same-name PLC variable. See also AWP commands (Page 680) Enumeration types Enumeration types (enums) Numerical values from the PLC program can be converted into text and vice versa using enums. The numerical values can also be assigned for several languages. Creating enums Enter an AWP command using the following syntax at the start of the HTML file: <!-- AWP_Enum_Def Name="<Name of the enum type>" Values='0:"<Text_1>", 1:"<Text_2>", ... , x:"<Text_x>"' --> For example, for German values to be saved as an HTML file in the "de" folder of the HTML directory: <!-- AWP_Enum_Def Name="Enum1" Values='0:"an", 1:"aus", 2:"Storung"' --> For example, for English values, to be saved as an HTML file in the "en" folder of the HTML directory: 686 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks <!-- AWP_Enum_Def Name="Enum1" Values='0:"on", 1:"off", 2:"error"' --> Assigning enums Tags are assigned from the user program to the individual enum texts using a special AWP command: <!-- AWP_Enum_Ref Name="<VarName>" Enum="<EnumTypeName>" --> <VarName> is thereby the symbolic name from the user program and <EnumTypeName> is the previously set name of the enum type. Note In each fragment in which enum texts are referenced by a PLC tag, this PLC tag must be assigned by the appropriate AWP command of the enum type name. Ensure that no AWP command for importing fragments is positioned between an enum assignment and enum usage because this import can result in the enum assignment lying in a different fragment than the enum usage. Example Enum type "state" is defined with values "0" and "1". "0" means "off", "1" means "on": <!-- AWP_Enum_Def Name="state" Values='0:"off", 1:"on"' --> The following code is contained in the HTML code of the web page to be output: <!-- AWP_Enum_Ref Name="operating state" Enum="state" --> :=operating state: Depending on the value of the "operating state" tag, the result displayed is no longer "0" or "1", but "off" or "on". Simplified use of enumeration types At S7-1200 CPUs as of firmware version 4 it is possible to use enumerations directly in AWP commands to read and write PLC variables. WinCC Basic V13.0 System Manual, 02/2014 687 Editing devices and networks 8.1 Configuring devices and networks You create enums as described in the previous section, and you can then utilize the values with user program read and write commands. Creating enums <!-- AWP_Enum_Def Name="<Name des Enum Typs>" Values='0:"<Text_1>", 1:"<Text_2>", ... , x:"<Text_x>"' --> Utilizing enums in the user program read and write commands <!-- AWP_In_Variable Name='<Varname>' Enum="<EnumType>" --> <!-- AWP_Out_Variable Name='<Varname>' Enum="<EnumType>" --> Example of reading PLC tags <!-- AWP_Enum_Def Name='AlarmEnum' Values='0:"No alarms", 1:"Tank is full", 2:"Tank is empty"' --><!-- AWP_Out_Variable Name='"Alarm"' Enum="AlarmEnum" -->...<p>The current value of "Alarm" is :="Alarm":</p> If the value of "Alarm" in the CPU is "2", the following text will be displayed on the HTML page: 'The current value of "Alarm" is Tank is empty' because the enum definition assigns the string "Tank is empty" to the numerical value 2. Example of writing PLC tags <!-- AWP_Enum_Def Name='AlarmEnum' Values='0:"No alarms", 1:"Tank is full", 2:"Tank is empty"' --><!-- AWP_In_Variable Name='"Alarm"' Enum='AlarmEnum' -->... <form method="POST"> <p><input type="hidden" name='"Alarm"' value="Tank is full" /></p> <p><input type="submit" value='Set Tank is full' /><p> </form> Because the enum definition assigns the string "Tank is full" to the numerical value "1", the value "1" is written to the PLC tag "Alarm". Definition of fragments Fragments Fragments are "logical sections" of a web page to be processed by the CPU individually. Fragments are usually complete pages but can also be individual elements such as files (for example, images) or complete documents. 688 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Defining fragments <!-- AWP_Start_Fragment Name="<Name>" [Type="<Type>"] [ID="<Id>"] [Mode=<Mode>]--> The start of a fragment is specified by this command. A fragment runs to the start of the next fragment or to the end of the file. <Name> Indicates the name of the fragment. The name must start with a letter [a-zA-Z] or an underscore ( _ ). Letters, underscores or numbers [0-9] can follow after this first character. <Type> Indicates the type of the fragment. - "manual" The user program is informed of the request for a fragment; the web page to be returned can be changed by the user program. - "automatic" The page is automatically processed (default). <id> A numeric ID can be stipulated for the fragment. If no ID is assigned, the fragment is automatically assigned an ID. For manual pages (<Type>=manual) , the fragment can be addressed in the user program of the CPU by this ID. Note Keep the ID low because the highest ID influences the size of the Web Control DB. <Mode> Fragments support the visible and hidden modes. - "visible" The fragment is a part of the web page. This mode is preset and can also be omitted. - "hidden" The fragment is not part of the web page. However, the fragment will be saved in the Web DB and is available to the user program for inserting in a requested web page. You use an exchange of the fragment ID (Web-Control-DB.fragment_index tag) to insert a "hidden" fragment in the requested web page. The input document is completely divided into fragments by the "AWP_Start_Fragment" command. "AWP_End_Fragment" is therefore unnecessary. Without a start fragment command, a file is mapped as a fragment; the fragment name is derived from the file name. If a file is divided into several fragments (by "AWP_Start_Fragment"), the file must begin with the "AWP_Start_Fragment" command. Importing fragments You can declare a fragment in an HTML page and import this fragment into other web pages. Example A company logo is to be displayed on all web pages of a web application. There is only one instance of the HTML code for the fragment that displays the company logo. You can import the fragment as often and into as many HTML files as required. WinCC Basic V13.0 System Manual, 02/2014 689 Editing devices and networks 8.1 Configuring devices and networks Syntax <!-- AWP_Import_Fragment Name = "<name>"--> <name> is the name of the fragment to be imported. Example HTML code within a web page that declares a fragment: <!-- AWP_Start_Fragment Name = "My_Company_Logo"--> <p><img src = "compay_logo.jpg"></p> Example HTML code within another web page that imports the declared fragment: <!-- AWP_Import_Fragment Name = "My_Company_Logo"--> Creating and loading a data block Requirement All source files required for the web application (*.html, *.js, *.png, ...) have been created. The source files are located in one folder, but only those source files that are required for the web application. No other files may be located in this folder. Note Length of file names and tag names If you have a comprehensive web application with many files and directories, the generation of the web data blocks may possibly fail. If this happens, the generation is aborted with the message "Text list overflow...". The cause is system-internal size limitations for management information saved in the web data block. Remedy: Use short file names and short tag names. 690 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Procedure To create data blocks from the source files for user-defined web pages in STEP 7, proceed as follows: 1. Select the CPU, for example, in the device configuration. 2. Select the properties for user-defined web pages in the inspector window under "Properties > General > Web server". 3. As "HTML source", select the folder that contains the source files for the web application. 4. Enter the HTMP page to be opened on starting the web application as the start HTML page. 5. Enter a name for the application if required. 6. You can supplement a range of file name extensions as "Files with dynamic content" if necessary. Only enter those file name extensions that also contain AWP commands. 7. The number for the Web Control DB and for the fragment DB start number can be kept as long as they are not already being used by your user program. 8. Click on the "Generate" button to create DBs from the source files. The generated data blocks are saved in the project navigation in the "System block" folder (in the "Web server" subfolder). 9. In the CPU, select the network view to be loaded and then select the "Download to device" command in the "Online" menu to download the blocks. Compilation of the blocks is implicitly initiated before downloading. If errors are reported during this process, you must correct these errors before you can download the configuration. Structure of the PLC program Your user program must call the " WWW" instruction to even allow the web application, for example, the user-defined web pages, to be available to the CPU on the standard web pages and to allow them to be called up there. The Web Control DB you have created from the source files is the input parameter (CTRL_DB) for the "WWW" instruction. The Web Control DB references the content of the user-defined web pages coded in the fragment DB and then receives status and control information. Calling the "WWW" instruction in the startup program If you do not want the user program to influence requested web pages, it is sufficient to only call the "WWW" instruction once in a startup OB. This instruction initializes communication between the web server and the CPU. Calling the "WWW" instruction in the cyclic program The "WWW" instruction can also be called in an OB processed in cycles (for example, OB 1). This has the advantage of being able to respond to web server requests from within the user program. Manual fragments must be used for this. In this case, you must evaluate information from the Web Control DB in order to identify the requested web page or the requested fragment. On the other hand, you must set a bit in the WinCC Basic V13.0 System Manual, 02/2014 691 Editing devices and networks 8.1 Configuring devices and networks user program in order to explicitly release the web page to be returned by the web server after processing the web page request. The structure of the Web Control DB is described in the following section. Web Control DB The Web Control DB (DB 333 by default) is created by STEP 7 and contains information on the structure of user pages, the status of communication and any errors that occur. Additional fragment DBs are also created as well as the Web Control DB. These fragment DBs (there may also only be one fragment DB) are referenced in the Web Control DB. The fragment DBs contain the web pages and media data coded in fragments, for example, images. The content of the fragment DB cannot be changed by the user program. It is created automatically and is only for data management. The status and control tags of the Web Control DB are accessed via symbols. The following lists the tags of the Web Control DB required for status evaluation and to control interaction. The Web Control DB provides two types of information: Global status information: Not bound to a concrete web page request. Request status and control information: Information about queued requests. Global status information "WEB-Control_DB".commandstate.init Activates and initializes the web application. "WEB-Control_DB".commandstate.deactivate Deactivates the web application. "WEB-Control_DB".commandstate.inititializing The web application is initialized (read Web Control DB, etc.). "WEB-Control_DB".commandstate.error Web application could not be initialized. The reason is coded in "WEBControl_DB".commandstate.last_error . "WEBThe web application is closed. Control_DB".commandstate.deactivating "WEB-Control_DB".commandstate.initialized The web application has been initialized and is ready. "WEB-Control_DB".commandstate.last_error Refer to the next table for a value table of possible errors. 692 Last_error Description 1 Fragment DB is inconsistent (does not match the Web Control DB). 2 A web application already exists with this name. 3 Memory problem initializing in the web server. 4 Inconsistent data in the Web Control DB. 5 A fragment DB is not available (not loaded). 6 No AWP ID for a fragment DB. WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Last_error Description 7 The enum fragment is not available (contains the texts and information on the enum types). 8 An action requested via the command flag in the Web Control DB is prohibited in the current state. 9 Web application is not initialized (if there is no reinitializing after disabling). 10 Web server is disabled. ... Last_error is reset once the web application has been successfully initialized. Request status information Request status information is bound to one of four possible requests, x = [1 ... 4]. "WEB-Control_DB".requesttab[x].idle "WEB-Control_DB".requesttab[x].waiting "WEB-Control_DB".requesttab[x].sending "WEB-Control_DB".requesttab[x].aborting Nothing need be done. The user program must react to a request from a manual fragment and explicitly initiate further processing in the web browser. The web server is occupied with processing the request/fragment. The TCP connection is closed by the web server. Request control information Request control information is bound to one of four possible requests, x = [1 ... 4]. "WEB-Control_DB".requesttab[x].continue "WEB-Control_DB".requesttab[x].repeat "WEB-Control_DB".requesttab[x].abort "WEB-Control_DB".requesttab[x].finish Releases the fragment being processed for transmission. Processing of the next fragment is initiated. Releases the fragment being processed for transmission. The fragment is then processed again. Closes the TCP connection. Releases the fragment being processed for transmission. Stops further processing of requests (terminates the request). Example: The tag for the DB is: "WEB-Control_DB". Whether errors have occurred during initialization of the web application can be determined by requesting bit "WEBControl_DB".commandstate.error in the user program. If an error has occurred you can analyze it using the "WEBControl_DB".commandstate.last_error value. WinCC Basic V13.0 System Manual, 02/2014 693 Editing devices and networks 8.1 Configuring devices and networks Interaction with the user program Using manual fragments ensures that the user program reacts synchronously to the user program, thereby allowing the responding web page to be processed by the user program. Fragment type To react to the received data in the user program the "manual" fragment type must be used for the fragment writing the data (for "manual pages"): <!-- AWP_Start_Fragment Name="testfrag" ID="1" Type="manual" --> The values are always transferred to the web server of the CPU for automatic and manual pages in the same way: Example: <form method="POST" action=""> <p> <input type="submit" value="Set new value"> <input type="text" name='"Velocity"' size="20"> </p> </form> User program for manual fragments When using manual pages, the "WWW" instruction must be called in cycles in the user program of the CPU. To react to values entered in the browser, the request - which is made by the manual page to the web server - must first be evaluated in the user program. To do this, the Web Control DB (for example, DB 333) must be examined in cycles for queued requests. The array that manages four requests is contained in the "requesttab" section of the Web Control DB. Each element of the array thereby contains information on the respective request within a structure. A simple programming example shows how queued requests are checked based on the tags of the Web Control DB. 694 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks In cases where a request has been made, this program section writes the fragment ID in the #frag_index tag and the request no. (value range 1-4) in the #req_index tag. Using the information from this, the information transferred in the request can now be processed separately for each fragment ID in the program (for example, plausibility check). Once processing of the request has been completed by the program, the request must be answered and the appropriate entry is once more reset under"requesttab" of the Web Control DB (for example, DB 333). A simple programming example for replying to requests: WinCC Basic V13.0 System Manual, 02/2014 695 Editing devices and networks 8.1 Configuring devices and networks 696 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Principle sequence of a browser request with interaction from the user program The following figure shows the simplified, principle sequence of the web browser request on the effects of Web Control DB content and the actions required from the user program until the processed web page is returned (response). 5HVSRQVH :HEEURZVHU 5HTXHVW :HEVHUYHU 3URFHVVUHVSRQVH '%ZDLWLQJ 758( '%UHTFRQWLQXH 758( 6HW,1YDULDEOH GDWDWDEOH :ULWH,1YDULDEOH GDWDWDEOH 8VHUSURJUDP 3URFHVVUHTXHVW :HE&RQWURO'% &38 ,GHQWLI\UHTXHVWHG SDJH UHTXHVW (YDOXDWHDQG SURFHVV,1YDULD EOHVVHW287 YDULDEOHV (QDEOHUHTXHVWHG SDJH Displaying custom web pages in the browser Display web pages in browser Web pages are called from the standard web pages of the web browser. WinCC Basic V13.0 System Manual, 02/2014 697 Editing devices and networks 8.1 Configuring devices and networks In addition to the other links in the navigation bar, the standard web pages also have a link to "user pages". Click on the "user pages" link to open the web browser you have configured as the default HTML page. Creating custom web pages in several languages You can make each of your custom web pages available in various languages. Requirements The language-dependent HTML; pages must be stored in a folder structure containing folders with the respective language abbreviations: Specified language abbreviations Language abbreviations "de", "en", "fr", "es", "it" and "zh" are fixed. Additional language folders or other designated language folders are not supported. Additional folders within the same folder hierarchy for other files can be created as required; for example, an "img" folder for images and a "script" folder for JavaScript files. Language switching for custom web pages Requirements The HTML pages are contained in the predefined language folders, for example, HTML pages with German text are in the "de" folder, HTML pages with English text are in the "en" folder. Language switching concept Language switching is based on a predefined cookie named "siemens_automation_language". If the cookie is set to value "de", at the next web page request or web page update, the web server switches to the web page from the "de" folder. Similarly, the web server switches to the web page from the "en" folder when the cookie is set to "en". 698 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Example of language switching The example is structured as follows: The language-dependent HTML files with the same name, for example, "langswitch.html" are located in both language folders "de" and "en". The text to be displayed within the two files are German or English, corresponding to the name of the folder. There is an additional "script" folder in the folder structure containing the JavaScript file "lang.js". Functions required for language switching are stored in this file . Structure of the "langswitch.html" file ("de" folder) Meta data "content language", charset and path to JavaScript file are set in the file header. <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta http-equiv="Content-Language" content="de"> <meta http-equiv="Content-Type" content="text/html; charset=utf-8"> <title>Switch language to German page</title> <script type="text/javascript" src="script/lang.js" ></script> <head> Language selection is implemented in the body of the file by the "select" HTML element. The select element initiates a list box and contains the "de" option, labeled as "German" and "en", labeled as "English"; "de" is the default. The "DoLocalLanguageChange(this)" function is called using the "onchange" event handler. The "this" parameter transmits the select object with the selected option to this function. "onchange" calls the function each time the option is changed. <!-- Language Selection --> <table> <tr> <td align="right" valign="top" nowrap> <!-- change language immediately on change of the selection --> <select name="Language" onchange="DoLocalLanguageChange(this)" size="1"> <option value="de" selected >Deutsch</option> <option value="en" >English</option> </select> </td> </tr> </table> <!-- Language Selection End--> Structure of the "langswitch.html" file ("en" folder) The header of the HTML file with English text is structured similarly to the HTML file with German text. <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta http-equiv="Content-Language" content="en"> WinCC Basic V13.0 System Manual, 02/2014 699 Editing devices and networks 8.1 Configuring devices and networks <meta http-equiv="Content-Type" content="text/html; charset=utf-8"> <title>Language switching english page</title> <script type="text/javascript" src="script/lang.js" ></script> Language selection is also implemented in the body of the file by the "select" HTML element. In contrast to the German HTML file, the English option is already selected as a default and the test or the labels are in English. <!-- Language Selection --> <table> <tr> <td align="right" valign="top" nowrap> <!-- change language immediately on change of the selection --> <select name="Language" onchange="DoLocalLanguageChange(this)" size="1"> <option value="de" >German</option> <option value="en" selected >English</option> </select> </td> </tr> </table> <!-- Language Selection End--> Structure of "lang.js" file (in the "script" folder) The " DoLocalLanguageChange" function is defined in the Java script file and calls the "SetLangCookie" function with the language selection value. SetLangCookie combines the cookie name and cookie value and then sets the cookie by means of the corresponding document.cookie property. The web page must then be reloaded (top.window.location.reload) to allow the web server to react to the setting of the cookie by displaying the required language. function DoLocalLanguageChange(oSelect) { SetLangCookie(oSelect.value); top.window.location.reload(); } function SetLangCookie(value) { var strval = "siemens_automation_language="; // this is the cookie by which the web server // detects the desired language // this name is required by the web server strval = strval + value; strval = strval + "; path=/ ;"; // set path to the application, since otherwise // path would be set to the requesting page // would not get the cookie. // The path for user defined applications follows this sample: // path=/awp/<application name>/<pagename> // example: path=/awp/myapp/myappstartpage.htm //(where myapp is the name of the web application // entered in the web server properties of the cpu) 700 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks /* use expiration if this cookie should live longer than the current browser session var now = new Date(); var endttime = new Date(now.getTime() + expiration); strval = strval + "; expires=" + endttime.toGMTString() + ";"; */ document.cookie = strval; } Additional configurations Configuring additional functions The S7-1200 automation system has numerous additional functions that are useful as integrated CPU functions or available via plug-in modules (for example, communication modules). You can find the description via the following links. See also Overview of point-to-point communication (Page 983) General information on high-speed counters (Page 979) Configuring PID_Compact V1 (Page 4262) Configuring PID_3Step V1 (Page 4294) Motion functionality of the CPU S7-1200 (Page 4309) 8.1.4.4 S7-1200 CM/CP S7-1200 CM/CP Telecontrol S7-1200 CP 1242-7 Copying the CP 1242-7 into another project If you copy a CP 1242-7 from one project into another project, the following parameters in the parameter group "CP identification" are changed on the target station: Project number of the CP Station number of the CP WinCC Basic V13.0 System Manual, 02/2014 701 Editing devices and networks 8.1 Configuring devices and networks Download to device Only use the "Download to device" function with the CP 12427 via a TeleService connection as follows: 1. Select the CP in STEP 7. 2. Select the "Online" > "Download to device" menu. 3. In the "Extended download" dialog that appears, select the TeleService interface. 4. Download the project data from the "Extended download" dialog. Upload from device The function "Upload from device" is not supported by the CP 12427. 702 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks CP 1242-7 configuration Modes of the GPRS-CP Modes of the CP The CP 12427 allows an S71200 to communicate as a GPRS station with a central station or other remote networks via the GSM network. For communication using GPRS, the CP is set to one of the following operating modes: Telecontrol This operating mode of the CP allows the GPRS station to exchange data with the following partners: - Communication with the Telecontrol server This CP mode allows the GPRS station to exchange data with a telecontrol server. The Telecontrol server is a PC connected to the Internet with the "TELECONTROL SERVER BASIC" application. It is generally located in the master station and serves to monitor and control the remote GPRS stations. Data can be exchanged with the OPC client of a central control system via the integrated OPC interface. The Telecontrol server PC is not configured in STEP 7. The "TELECONTROL SERVER BASIC" application has its own configuration user interface. - Communication with another remote GPRS station The message frames are transmitted via the Telecontrol server. - Communication with an engineering station (for TeleService) Communication with the Telecontrol server is performed via the GSM network and the Internet. This operating mode requires a SIM card with GPRS service enabled and a Telecontrol server that can be reached by the CP. GPRS direct This operating mode of the CP is used for direct communication between remote stations via the GSM network. No Telecontrol server is required. To allow network nodes in public wireless networks to be directly accessible, these need to be addressed using a fixed address. Here, SIM cards with a fixed IP address are used that allow the stations to address each other directly. The possible communications services and security functions (for example VPN) depend on what is offered by the network provider. Possible communications partners of the GPRS station with a CP 1242-7 in "GPRS direct" mode are: - A subscriber that can be reached by the CP via an IP address (GPRS station with CP 12427) - An engineering station (for TeleService) WinCC Basic V13.0 System Manual, 02/2014 703 Editing devices and networks 8.1 Configuring devices and networks Establishing a connection using GPRS communication Connection modes "GPRS direct" mode There are no different connection modes in the "GPRS direct" mode. "Telecontrol" mode The CP can be configured for the following connection modes. - "Permanent" connection mode There is a permanent TCP connection to the telecontrol server. Following connection establishment, there is a permanent TCP connection to the telecontrol server even if data is not transferred permanently. - "Temporary" connection mode A connection is only established to the telecontrol server when required. If a TCP connection is established, process data is sent as soon as the telecontrol instructions are called on the CPU. A connection is always established by the CP. If a connection established by the CP is interrupted, the CP automatically attempts to re-establish the connection. Triggering connection establishment for permanent stations ("Telecontrol" mode) In the "Telecontrol" mode, the permanent connection to the telecontrol server is established when the station starts up. If there is an interruption on the connection, the establishment of the connection can be triggered by a wake-up SMS (see below). Triggering connection establishment for temporary stations ("Telecontrol" mode) With "temporary" stations, connection establishment can be triggered by the following events: Event on the local CPU that needs to be evaluated by the program. In terms of the program, two situations need to be distinguished: - Events that lead to a single connection establishment (for example alarms or commands from the operator). - Expiry of an interval that leads to cyclic connection establishment (for example once daily for data transmission) Request by a communications partner (OPC client or S7 station) The request from the communications partner leads to the connection being established. Request for TeleService by an engineering station The request switched by the telecontrol server or TeleService gateway does not need to be evaluated in the program. Wake-up SMS of the telecontrol server The wake-up SMS can be triggered spontaneously on the telecontrol server. It is also possible to configure cyclic sending on the telecontrol server. 704 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Telephone wake-up call The wake-up call can be sent from a telephone that has a phone number authorized in the STEP 7 project. The telephone must support the CLIP function (transfer of its own call number). The connection establishment with the (main) telecontrol server is triggered. Telephone wake-up SMS The wake-up SMS can be sent from a telephone that has a phone number authorized in the STEP 7 project. The telephone must support the CLIP function (transmission of its own number) and sending of SMS. The connection establishment with the telecontrol server specified in the SMS is triggered. When a temporary station is woken up, all the data is transferred if this has changed since the last data transfer. Triggering connection establishment in "GPRS direct" mode In "GPRS direct" mode, a connection establishment is triggered by the following events: Event on the local CPU that is evaluated by the program. Request by a communications partner (not an engineering station) The request in the frame received from the communications partner is evaluated in the program by calling the telecontrol instructions. Request for TeleService by an engineering station The request switched by the telecontrol server or TeleService gateway does not need to be evaluated in the program. Right to wake-up by "authorized phone numbers" The CP only accepts an SMS if the sending communication partner is authorized based on its phone number. These numbers are in configured for the CP in STEP 7 in the "authorized phone numbers" list. Note "Authorized phone numbers" in the STEP 7 project A phone number entered here gives the sender who transfers this phone number the right to trigger connection establishment. If an asterisk (*) is entered in the list, the CP accepts SMS messages from all senders. If the list is empty, the CP cannot be woken up for connection establishment. WinCC Basic V13.0 System Manual, 02/2014 705 Editing devices and networks 8.1 Configuring devices and networks Wake-up SMS Depending on the connection type and the triggering server or intermediary TeleService server, the following text must be transferred in the wake-up SMS: For telecontrol connections: - Text for the wake-up SMS message for establishing a connection to the telecontrol server: TELECONTROL - Text for the wake-up SMS message for establishing a connection to the main telecontrol server: TELECONTROL MAIN - Text for the wake-up SMS message for establishing a connection to the substitute telecontrol server: TELECONTROL BACKUP The configuration of the telecontrol server for the GPRS CP is set in STEP 7 in "Telecontrol interface > Operating mode > main or substitute telecontrol server". Note Wake-up with a mobile phone One of the texts listed above can be used in a wake-up SMS message. With a wake-up call, the station always connects to the main telecontrol server. For TeleService connections: - Text for the wake-up SMS message for establishing a connection to the first configured TeleService server: TELESERVICE or TELESERVICE 1 - Text for the wake-up SMS message for establishing a connection to the second configured TeleService server: TELESERVICE 2 The configuration of the TeleService server for the GPRS CP is set in STEP 7 in "Telecontrol interface > TeleService authorization > 1st or 2nd TeleService server". 706 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Preferred GSM networks Selection of preferred GSM networks The following options are provided to select the GSM networks that the CP 12427 should preferably dial up: Automatic dialup The CP dials with highest priority into the GSM network of the contracted network operator set on the SIM card. If a connection cannot be made within the contracted network, the CP dials up another GSM network with which the network operator has a roaming contract and whose access data is stored on the SIM card. Contract network only The CP only dials up the GSM network of the contracted network operations whose SIM card is plugged into the CP. No roaming. Contracted network and alternative network The CP dials up the contracted network with the highest priority. If dialup to the contracted network is unsuccessful, the CP dials up an alternative GSM network, in decreasing priority, as entered in the list of preferred network operators. The alternative networks are entered in the list as "Public Land Mobile Network" (PLMN). PLMN is a construct of Mobile Country Code (MCC) and Mobile Network Code (MNC). Example: 26276 This is the PLMN for the test network of Siemens AG with MCC = 262 and MNC = 76. Time-of-day synchronization in NTP mode - parameter assignment NTP mode (NTP: Network Time Protocol) In NTP mode, the CP sends time-of-day queries at regular intervals to one or more NTP servers. From the responses of the servers, the CP selects the most accurate time of day. The advantage of this mode is that it allows the time to be synchronized across subnets. In NTP mode, it is generally UTC (Universal Time Coordinated) that is transferred. This corresponds to GMT (Greenwich Mean Time). CP 1242-7 TeleService TeleService via GPRS Communication path for TeleService via GPRS With TeleService for remote S7 stations with the CP 12427 via GPRS, the connection is always established via an intermediary between the engineering station and remote S7 station. This intermediary can be either: WinCC Basic V13.0 System Manual, 02/2014 707 Editing devices and networks 8.1 Configuring devices and networks A telecontrol server (and possibly a substitute telecontrol server) The telecontrol server can be a separate PC or installed on the engineering station in the form of the "TELECONTROL SERVER BASIC" application. A TeleService server A TeleService server is used when no telecontrol server is available; in other words, when the CP operates in "GPRS direct" mode. The telecontrol server or TeleService server can be connected to the engineering station via LAN or Internet and the TeleService function can be called from there. Requirements for TeleService via GPRS A telecontrol server or a TeleService server The STEP 7 project with the required data for GPRS communication Note on project engineering The telecontrol server and TeleService server are not configured in STEP 7. See also Establishing a connection using GPRS communication (Page 704) Modes of the GPRS-CP (Page 703) Establishing a TeleService connection via GPRS Establishing a connection for TeleService via GPRS The request to establish a connection is triggered by the engineering station and transmitted by a wake-up SMS to the station. The CP 12427 in the S71200 station establishes a connection to the engineering station via the GSM network and the Internet. Starting the TeleService via GPRS Start the TeleService via GPRS as follows: 1. In the project on the authorized engineering station, select the remote S7 station with which you want to establish a TeleService connection via GPRS. 2. Alternatively, open the "Connect online" dialog box as follows: - "Connect online" button - "Connect online" shortcut menu (right mouse button) - "Online" > "Connect online" menu The "Connect online" dialog box opens. 3. Choose interface type "TeleService GPRS" in the "Type of PG/PC interface" drop-down list. 708 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks 4. In the "PG/PC interface" drop-down list, select the "GPRS TeleService board" option if it is not automatically displayed. 5. Click on the "Connect" icon next to the "PG/PC interface" drop-down list. The "Establish remote connection" dialog box opens. 6. Make the necessary settings in the "Establish remote connection" dialog. Details of this are contained in the tooltip cascade of STEP 7. The following details are required to successfully establish a connection: Details required to establish a connection with the GPRS station The following information is necessary in the Establish remote connection" dialog: IP address or DNS name of the telecontrol server TCP port number of the telecontrol server or the DSL router via which the connection between the engineering station and the remote GPRS station is running. Server password of the ES to authenticate the engineering station at the telecontrol server Only required if a group-specific password has been configured in the "TELECONTROL SERVER BASIC" application. TeleService user name See CP configuration in STEP 7. TeleService password See CP configuration in STEP 7. Access ID of the CP Only required when there are several CP 12427s in the station. See CP configuration in STEP 7. Status Connection statuses of TeleService via GPRS The following connection statuses can be displayed in the "Establish remote connection" dialog box: Not connected There is no connection to the remote GPRS station. Connection establishment has not yet started. If connection establishment was started by clicking the "Connect" button, the following statuses are displayed one after the other after the connection has been established: Connect to telecontrol server The engineering station connects to the telecontrol server. Wait for S7 station The wake-up SMS has been sent to the remote station. Wait for reply from station. WinCC Basic V13.0 System Manual, 02/2014 709 Editing devices and networks 8.1 Configuring devices and networks Authentication at S7 station The S7 station has established an IP connection with the engineering station via GPRS and Internet and is checking the received logon and authentication data. Connected The station has successfully established the connection to the engineering station. The following states may be displayed if the connection cannot be successfully established: Telecontrol server not accessible Possible causes: - The connection between the engineering station and the telecontrol server has been interrupted. - The telecontrol server is switched off. Wrong server password Cause: The wrong server password for logging on and authentication was entered at the telecontrol server. S7 station not responding Possible causes: - Faulty GSM communication between the telecontrol server and the station. - Faulty connection between the GSM network and the Internet. - Faulty Internet connection. - The telecontrol server could not send a wake-up SMS. - The CP has not received a wake-up SMS. - The sender of the SMS was not configured in the list of authorized wake-up call numbers. Wrong TeleService user name or TeleService password Possible causes: - An incorrect TeleService user name or incorrect TeleService password was entered in the authentication dialog for the CP 12427. - The TeleService user name or TeleService password was not configured in STEP 7. All TeleService access points are in use. The CP is not known to the telecontrol server. Cause: The CP originates from a STEP 7 project that does not match the project of the telecontrol server. No resources available for TeleService on the CP: Please contact the hotline. Protocol error Cause: Wrong frame or frame from wrong subscriber. Please contact the hotline. 710 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks CP 1243-1 CPU scan cycle Structure of the CPU scan cycle The cycle (including the pause) with which the CP scans the memory area of the CPU is made up of the following phases: High-priority read jobs For data points of the type "Input", which are configured with the "High priority" setting in the data point configuration in "General > Priority in the scan cycle", the PLC tags are all read in one scan cycle. Write jobs In every cycle, the values of a certain number of unsolicited write jobs are written to the CPU. The number of tags written per cycle is specified for the CP in the "Communication with the CPU" parameter group with the "Max. number of write jobs" parameter. The tags whose number exceeds this value are then written in the next or one of the following cycles. Low-priority read jobs - proportion For data points of the type "Input", which are configured with the "Low priority" setting in the data point configuration in "General > Priority in the scan cycle", the values of a part of the PLC tags are read in every scan cycle. The number of tags read per cycle is specified for the CP in the "Communication with the CPU" parameter group with the "Max. number of read jobs" parameter. The tags that exceed this value and can therefore not be read in one cycle are then read in the next or one of the following cycles. Cycle pause time This is the waiting time between two scan cycles. It is used to reserve adequate time for other processes that access the CPU via the backplane bus of the station. Duration of the CPU scan cycle Since no fixed time can be configured for the cycle and since the individual phases cannot be assigned a fixed number of objects, the duration of the scan cycle is variable and can change dynamically. Datapoint types During the configuration of the user data to be transferred by the CP, each data point is assigned a protocol-specific data point type. The data point types supported by the CP along with the compatible S7 data types are listed below. They are grouped according to format (memory requirements). The direction relates to the direction of transfer (monitoring direction = "in", control direction = "out"). WinCC Basic V13.0 System Manual, 02/2014 711 Editing devices and networks 8.1 Configuring devices and networks CP 12431 DNP3: Supported data point types Table 8-54 Supported data point types, DNP3 object groups, variants and compatible S7 data types Format (memory requirements) Data point type DNP3 object group Bit Binary Input 1 [1, 2] Binary Input Event 2 [1, 2] Binary Output 1) 1) Binary Command Counter Static Frozen Counter 2) Counter Event Frozen Counter Event 3) Analog Input Analog Input Event Analog Output Status 4) Analog Output Analog Output Event Integer (32 bits) 4) Counter Static Frozen Counter 2) Counter Event Frozen Counter Event 3) Analog Input Analog Input Event Analog Output Status 4) Analog Output Analog Output Event Floating-point number (32 bits) 4) Analog Input Analog Input Event Analog Output Status 4) Analog Output Analog Output Event Floating-point number (64 bits) 4) Analog Input Analog Input Event Analog Output Analog Output Event Block of data (1...64 bytes) 5) S7 data types Address area in BOOL I, Q, M in BOOL I, Q, M BOOL I, Q, M UINT, WORD I, Q, M UINT, WORD I, Q, M [variations] Binary Output Event Integer (16 bits) Direction Octet String Octet String Event 5) 4) 10 [2] out 11 [1, 2] out 12 [1] out 20 [2] in 21 [2, 6] in 22 [2, 6] in 23 [2, 6] in 30 [1] in INT I, Q, M 32 [2, 4] in INT I, Q, M 40 [2] out INT I, Q, M UDINT, DWORD I, Q, M UDINT, DWORD I, Q, M 41 [2] out 42 [2, 4] out 20 [1] in 21 [1, 5] in 22 [1, 5] in 23 [1, 5] in 30 [2] in DINT I, Q, M 32 [1, 3] in DINT I, Q, M 40 [1, 3] out 41 [1] out DINT I, Q, M 42 [1] out 30 [5] in REAL Q, M 32 [5, 7] in REAL Q, M 40 [3] out 41 [3] out REAL Q, M 42 [5, 7] out 30 [6] in LREAL Q, M 32 [6, 8] in LREAL Q, M LREAL Q, M 41 [4] out 42 [6, 8] out 110 [ ] in 5) I, Q, M 111 [ ] in 5) I, Q, M 1) This object group can be configured in the Data point editor of STEP 7 using object group 12. 2) This object group can be configured in the Data point editor of STEP 7 using object group 20. 3) This object group can be configured in the Data point editor of STEP 7 using object group 22. 712 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks 4) This object group can be configured in the Data point editor of STEP 7 using object group 41. With these data point types, contiguous memory areas up to a size of 64 bytes can be transferred. All S7 data types with a size between 1 and 64 bytes are compatible. If the array is modified later, the data point must be recreated. 5) Configuration and feedback of binary and analog values Binary values You configure binary values (inputs) using object groups 1 and 2. The object groups 10 and 11 are used to feed back the current values in the process image of the CPU to the control system. Analog values You configure analog values using the object groups 30, 32 and 41 depending on the transfer direction. The object groups 40 and 42 are used to feed back current values in the process image of the CPU to the control system. CP 12431 IEC: Supported data point types Table 8-55 Supported data point types, IEC types and compatible S7 data types Format (memory requirements) Data point type Bit Byte Integer (16 bits) Integer (32 bits) Floating-point number (32 bits) IEC type Direction S7 data types Address area Single point information <1> in BOOL I, Q, M Single point information with time tag Single command <30> in BOOL I, Q, M <45> out BOOL I, Q, M Step position information <5> in BYTE I, Q, M Step position information with time tag <32> in BYTE I, Q, M Regulating step command <47> out BYTE I, Q, M Measured value, normalized value <9> in INT I, Q, M Measured value, normalized value with time tag <34> in INT I, Q, M Measured value, scaled value <11> in INT I, Q, M Measured value, scaled value with time tag <35> in INT I, Q, M Set point command, normalised value <48> out INT I, Q, M Set point command, scaled value <49> out INT I, Q, M Bitstring of 32 bits <7> in DWORD, UDINT I, Q, M Bitstring of 32 bits with time tag <33> in DWORD, UDINT I, Q, M Integrated totals <15> in DWORD, UDINT I, Q, M Integrated totals with time tag <37> in DWORD, UDINT I, Q, M Measured value, short floating point number <13> in REAL Q, M Measured value, short floating point number with time tag <36> in REAL Q, M WinCC Basic V13.0 System Manual, 02/2014 713 Editing devices and networks 8.1 Configuring devices and networks Format (memory requirements) Block of data (1...32 Bit) 1) Data point type IEC type Direction Set point command, short floating point number <50> out Bitstring of 32 bits <7> in 1) I, Q, M <33> in 1) I, Q, M <51> out 1) I, Q, M 1) Bitstring of 32 bits with time tag Bitstring of 32 bits 1) 1) S7 data types Address area REAL Q, M With these data point types, contiguous memory areas up to a size of 32 bits can be transferred. All S7 data types with a size between 1 and 32 bits are compatible. If the array is modified later, the data point must be recreated. 1) Types of transmission and event classes Storing and transferring values The values of data points can be assigned to different memory areas on the CP and therefore to different types of transfer: Static values Static values are entered in the process image of the CP. The value of a static data point is sent after being requested by the communications partner. Events The values of data points configured as an event are also entered in the process image of the CP. The values of events are also entered in the send buffer of the CP. The value of a data point that was configured as an event is sent unsolicited to the communications partner if this function is enabled by the master. The send buffer has the following size: - With DNP3: Max. 64000 events - With IEC: Max. 65535 events The capacity of the send buffer is divided up equally for all enabled partners. Types of transmission Depending on your CP type, you have the following transmission types available: Transfer after call The current value of the data point is entered in the image memory of the CP. A new value overwrites the older value in the image memory. After being called by the communications partner, the current value at the time is transferred. Every value triggered Whenever the trigger condition is met, the individual value of the data point is entered separately in the send buffer and transferred to the communications partner. 714 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Event class ... The value is transferred to the send buffer triggered as a class 1, 2 or 3 event. If unsolicited transfer is enabled by the master, the value is transferred unsolicited. You will find details of the event classes in the following sections. Current value triggered Only the current value of a data point at the time of the trigger is entered in the send buffer and transferred to the communications partner. Event classes for the DNP3 protocol The process data of the various event classes is handled as follows: Event class 1 / event class 2 Classes according to the DNP3 protocol: Event, class 1 / class 2 Each value change is entered in the send buffer in chronological order. The evaluation of the classification (1 or 2) must be handled by the master. Event class 3 Class according to the DNP3 protocol: Static event, class 3 Only the current value at the time the trigger condition was met is entered in the send buffer and overwrites the last value stored there. Event classes for the IEC protocol The process data of the various event classes is handled as follows: Event class 1 Classes according to the IEC protocol: Event, class 1 Each value change is entered in the send buffer in chronological order. Event class 3 Class according to the IEC protocol: Static event, class 3 Only the current value at the time the trigger condition was met is entered in the send buffer and overwrites the last value stored there. Analog value preprocessing Some CPs have analog value preprocessing that, among other things, supports the functions described below. Smoothing factor Analog values that fluctuate quickly can be evened out using the smoothing function. The smoothing factors are calculated according to the following formula as with S7 analog input modules. yn = xn + ( k - 1) yn - 1 k where yn = smoothed value in the current cycle WinCC Basic V13.0 System Manual, 02/2014 715 Editing devices and networks 8.1 Configuring devices and networks xn = value acquired in the current cycle n k = smoothing factor The following values can be configured for the module as the smoothing factor. 1 = No smoothing 4 = Weak smoothing 32 = Medium smoothing 64 = Strong smoothing Fault suppression time An analog value in the overflow range (32767 / 7FFFh) or underflow range (-32768 / 8000h) is not transferred for the duration of the fault suppression time. This also applies to live zero inputs. The value in the overflow/underflow range is only sent after the fault suppression time has elapsed, if it is still pending. If the value returns to the measuring range before the fault suppression time elapses, the current value is transferred immediately. A typical use case for this parameter is the suppression of peak current values when starting up powerful motors that would otherwise be signaled to the control center as a disruption. The suppression is adjusted to analog values that are acquired by the S7 analog input modules as raw values. These modules return the specified values for the overflow or underflow range for all input ranges (also for live zero inputs). If the CPU makes preprocessed finished values available in the bit memory area or in a data block, fault suppression is only possible or useful if these values have the values listed above (32767 / 7FFFh) or (-32768 / 8000h) in the overflow or underflow range. If this is not the case, the parameter should not be enabled for preprocessed values. Mean value generation With this parameter, acquired analog values are transferred as mean values. The current values of an analog datapoint are acquired cyclically and totaled. The number of acquired values per time unit depends on the read cycle of the CPU and the CPU scan cycle of the CP. The mean value is calculated from the accumulated values as soon as the transfer is triggered by a time trigger. Following this, the accumulation starts again so that the next mean value can be calculated. The mean value can also be calculated if the transmission of the analog value message is triggered by a request from the communications partner. The duration of the mean value calculation period is then the time from the last transmission (for example triggered by the trigger) to the time of the request. Once again, the accumulation restarts so that the next mean value can be calculated. If the acquired analog value in the overflow range (32767 / 7FFFh) or underflow range (-32768 / 8000h), this value can either be taken into account immediately in the calculation of the mean value or it can be suppressed for a specific period for the calculation of the mean value. The required response can be decided with the Fault suppression time parameter: 716 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Fault suppression time = 0 Acquisition of a value in the overflow or underflow range results in the mean calculation being stopped immediately. The value 32767 / 7FFFh or -32768 / 8000h is saved as an invalid mean value for the current mean value calculation period and sent when the next analog value message is triggered. The calculation of a new mean value is then started. If the analog value remains in the overflow or underflow range, this new value is again saved immediately as an invalid mean value and sent when the next frame is triggered. Fault suppression time > 0 If the acquired analog value is in the overflow or underflow range, the bad values are excluded from the calculation of the mean value for a maximum time as defined by the Fault suppression time. If this time is exceeded, the value 32767 / 7FFFh or -32768 / 8000h is saved as an invalid mean value and sent when the next analog value frame is triggered. The procedure is identical in each new averaging period; in other words, bad values are again suppressed for the duration of the fault suppression time. The duration of the fault suppression time also indirectly decides the proportion of invalid values per averaging period. If the mean value is formed, for example in a cycle of 15 minutes, and the fault suppression time is set to 5 minutes, this means that the mean value is only transferred as invalid if more than 33% of the acquired analog values are in the overflow or underflow range in the current averaging period. 8.1.4.5 SCALANCE X, W and M SCALANCE X Useful information VLAN Network definition regardless of the spatial location of the nodes VLAN (Virtual Local Area Network) divides a physical network into several logical networks that are shielded from each other. Here, devices are grouped together to form logical groups. Only nodes of the same VLAN can address each other. Since multicast and broadcast frames are only forwarded within the particular VLAN, they are also known as broadcast domains. The particular advantage of VLANs is the reduced network load for the nodes and network segments of other VLANs. To identify which packet belongs to which VLAN, the frame is expanded by 4 bytes (VLAN tagging (Page 719)). This expansion includes not only the VLAN ID but also priority information. WinCC Basic V13.0 System Manual, 02/2014 717 Editing devices and networks 8.1 Configuring devices and networks Options for the VLAN assignment There are various options for the assignment to VLANs: Port-based VLAN Each port of a device is assigned a VLAN ID. You configure port-based VLAN in "Layer 2 > VLAN > Port-based VLAN". Protocol-based VLAN Each port of a device is assigned a protocol group. You can configure protocol-based VLAN in "Layer 2 > VLAN > Protocol Based VLAN Port" Subnet-based VLAN The IP address of the device is assigned a VLAN ID. You configure subnet-based VLAN in "Layer 2 > VLAN > lpv4 Subnet Based VLAN". processing the VLAN assignment If more than one VLAN assignment is created on the device, the assignments are processed in the following order: 1. Subnet-based VLAN 2. Protocol-based VLAN 3. Port-based VLAN The frame is first examined for the IP address. If a rule on the "lpv4 Subnet Based VLAN" tab applies, the frame is sent to the corresponding VLAN. If no rule applies, the protocol type of the frame is examined. If a rule on the "Protocol Based VLAN Port" tab applies, the frame is sent to the corresponding VLAN. If no rule applies, the frame is sent via the port-based VLAN. The rules for the port-based VLAN are specified on the "Port Based VLAN" tab. See also General (Page 803) GVRP (Page 805) Port-based VLAN (Page 806) Protocol-based VLAN group (Page 807) Protocol-based VLAN port (Page 808) IPv4 subnet-based VLAN (Page 808) 718 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks VLAN tagging Expansion of the Ethernet frames by four bytes For CoS (Class of Service, frame priority) and VLAN (virtual network), the IEEE 802.1 Q standard defined the expansion of Ethernet frames by adding the VLAN tag. Note The VLAN tag increases the permitted total length of the frame from 1518 to 1522 bytes. With the IE switches, the standard MTU size is 1536 bytes. The MTU size can be changed to values from 64 to 9216 bytes. The end devices on the networks must be checked to find out whether they can process this length / this frame type. If this is not the case, only frames of the standard length may be sent to these nodes. The additional 4 bytes are located in the header of the Ethernet frame between the source address and the Ethernet type / length field: 3UHDPEOH E\WHV 'HVWLQDWLRQ DGGUHVV E\WHV 6RXUFH DGGUHVV E\WHV 73,' E\WHV 7&, E\WHV 7\SH E\WHV 'DWD aE\WHV &5& E\WHV [ 3ULRULW\ ELWV 9/$1,' ELWV &), ELW Figure 8-2 Structure of the expanded Ethernet frame The additional bytes contain the tag protocol identifier (TPID) and the tag control information (TCI). Tag protocol identifier (TPID) The first 2 bytes form the Tag Protocol Identifier (TPID) and always have the value 0x8100. This value specifies that the data packet contains VLAN information or priority information. Tag Control Information (TCI) The 2 bytes of the Tag Control Information (TCI) contain the following information: CoS prioritization WinCC Basic V13.0 System Manual, 02/2014 719 Editing devices and networks 8.1 Configuring devices and networks The tagged frame has 3 bits for the priority that is also known as Class of Service (CoS). The priority according to IEEE 802.1p is as follows: CoS bits Type of data 000 Non time-critical data traffic (less then best effort [basic setting]) 001 Normal data traffic (best effort [background]) 010 Reserved (standard) 011 Reserved ( excellent effort ) 100 Data transfer with max. 100 ms delay 101 Guaranteed service, interactive multimedia 110 Guaranteed service, interactive voice transmission 111 Reserved The prioritization of the data packets is possible only if there is a queue in the components in which they can buffer data packets with lower priority. The device has eight parallel queues in which the frames with different priorities can be processed. First, the frames with the highest priority ("Strict Priority" method) are processed. This method ensures that the frames with the highest priority are sent even if there is heavy data traffic. Canonical Format Identifier (CFI) The CFI is responsible for compatibility between Ethernet and the token Ring. The values have the following meaning: Value Meaning 0 The format of the MAC address is canonical. In the canonical representation of the MAC address, the least significant bit is transferred first. Standard-setting for Ethernet switches. 1 The format of the MAC address is not canonical. VLAN ID In the 12-bit data field, up to 4095 VLAN IDs can be formed. The following conventions apply: VLAN ID Meaning 0 The frame contains only priority information (priority tagged frames) and no valid VLAN identifier. 1 - 4094 Valid VLAN identifier, the frame is assigned to a VLAN and can also include priority information. 4095 Reserved SNMP Introduction With the aid of the Simple Network Management Protocol (SNMP), you monitor and control network elements from a central station, for example routers, switches. SNMP controls the communication between the monitored devices and the monitoring station. 720 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Tasks of SNMP: Monitoring of network components Remote control and remote parameter assignment of network components Error detection and error notification In versions v1 and v2c, SNMP has no security mechanisms. Each user in the network can access data and also change parameter assignments using suitable software. For the simple control of access rights without security aspects, community strings are used. The community string is transferred along with the query. If the community string is correct, the SNMP agent responds and sends the requested data. If the community string is not correct, the SNMP agent discards the query. Define different community strings for read and write permissions. The community strings are transferred in plain text. Standard values of the community strings: public has only read permissions private has read and write permissions Note For security reasons, do not use the standard values "public" or "private". Change the values following the initial installation. Further simple protection mechanisms at the device level: Allowed Host The IP addresses of the monitoring systems are known to the monitored system. Read Only If you assign "Read Only" to a monitored device, monitoring stations can only read out data but cannot modify it. SNMP data packets are not encrypted and can easily be read by others. The central station is also known as the management station. An SNMP agent is installed on the devices to be monitored with which the management station exchanges data. The management station sends data packets of the following type: GET Request for a data record from the agent GETNEXT Calls up the next data record. GETBULK (available as of SNMPv2) Requests multiple data records at one time, for example several rows of a table. SET Contains parameter assignment data for the relevant device. The SNMP agent sends data packets of the following type: WinCC Basic V13.0 System Manual, 02/2014 721 Editing devices and networks 8.1 Configuring devices and networks RESPONSE The agent returns the data requested by the manager. TRAP If a certain event occurs, the SNMP agent sends traps. SNMPv1 and SNMPv2 and SNMPv3 use UDP (User Datagram Protocol). The data is described in a Management Information Base (MIB). SNMP v3 Compared with the previous versions SNMP v1 and SNMP v2, SNMP v3 introduces a comprehensive security concept. SNMP v3 supports: Fully encrypted user authentication Encryption of the entire data traffic Access control of the MIB objects at the user/group level Spanning Tree Avoiding loops on redundant connections The spanning tree algorithm allows network structures to be created in which there are several connections between two stations. Spanning tree prevents loops being formed in the network by allowing only one path and disabling the other (redundant) ports for data traffic. If there is an interruption, the data can be sent over an alternative path. The functionality of the spanning tree algorithm is based on the exchange of configuration and topology change frames. Definition of the network topology using the configuration frames The devices exchange configuration frames known as BPDUs (Bridge Protocol Data Unit) with each other to calculate the topology. The root bridge is selected and the network topology created using these frames. BPDUs also bring about the status change of the root ports. The root bridge is the bridge that controls the spanning tree algorithm for all involved components. Once the root bridge has been specified, each device sets a root port. The root port is the port with the lowest path costs to the root bridge. Response to changes in the network topology If nodes are added to a network or drop out of the network, this can affect the optimum path selection for data packets. To be able to respond to such changes, the root bridge sends configuration messages at regular intervals. The interval between two configuration messages can be set with the "Hello Time" parameter. 722 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Keeping configuration information up to date With the "Max Age" parameter, you set the maximum age of configuration information. If a bridge has information that is older than the time set in Max Age, it discards the message and initiates recalculation of the paths. New configuration data is not used immediately by a bridge but only after the period specified in the "Forward Delay" parameter. This ensures that operation is only started with the new topology after all the bridges have the required information. RSTP, MSTP, CIST Rapid Spanning Tree Protocol (RSTP) One disadvantage of STP is that if there is a disruption or a device fails, the network needs to reconfigure itself: The devices start to negotiate new paths only when the interruption occurs. This can take up to 30 seconds. Fur this reason, STP was expanded to create the "Rapid Spanning Tree Protocol" (RSTP, IEEE 802.1w). This differs from STP essentially in that the devices are already collecting information about alternative routes during normal operation and do not need to gather this information after a disruption has occurred. This means that the reconfiguration time for an RSTP controlled network can be reduced to a few seconds. This is achieved by using the following functions: Edge ports (end node port) Edge ports are ports connected to an end device. A port that is defined as an edge port is activated immediately after connection establishment. If a spanning tree BPDU is received at an edge port, the port loses its role as edge port and it takes part in (R)STP again. If no further BPDU is received after a certain time has elapsed (3 x hello time), the port returns to the edge port status. Point-to-point (direct communication between two neighboring devices) By directly linking the devices, a status change (reconfiguration of the ports) can be made without any delays. Alternate port (substitute for the root port) A substitute for the root port is configured. If the connection to the root bridge is lost, the device can establish a connection over the alternate port without any delay due to reconfiguration. Reaction to events Rapid spanning tree reacts to events, for example an aborted connection, without delay. There is no waiting for timers as in spanning tree. Counter for the maximum bridge hops The number of bridge hops a package is allowed to make before it automatically becomes invalid. In principle, therefore with rapid spanning tree, alternatives for many parameters are preconfigured and certain properties of the network structure taken into account to reduce the reconfiguration time. WinCC Basic V13.0 System Manual, 02/2014 723 Editing devices and networks 8.1 Configuring devices and networks Multiple Spanning Tree Protocol (MSTP) The Multiple Spanning Tree Protocol (MSTP) is a further development of the Rapid Spanning Tree Protocol. Among other things, it provides the option of operating several RSTP instances within different VLANs or VLAN groups and, for example, making paths available within the individual VLANs that the single Rapid Spanning Tree Protocol would globally block. Common and internal Spanning Tree (CIST) CIST is a term from the multiple spanning tree. CIST identifies the internal instance used by the switch that is comparable in principle with an internal RSTP instance. Routing function Introduction The term routing describes the specification of routes for communication between different networks; in other words, how does a data packet from subnet A get to subnet B. SCALANCE X supports the following routing functions: Static routing With static routing, the routes are entered manually in the routing table. Router redundancy With standardized VRRP (Virtual Router Redundancy Protocol), the availability of important gateways is increased by redundant routers. Dynamic routing The entries in the routing table are dynamic and are updated continuously. The entries are created by the routing protocol. - OSPF v2 (Open Shortest Path First) Static routing The route is entered manually in the routing table. Enter the route in the routing table on the WBM page "Routes". Router redundancy with VRRP With the Virtual Router Redundancy Protocol (VRRP), the failure of a router in a network can be countered. Several VRRP routers in a network segment are put together as a logical group that forms a virtual router (VR). The group is defined using the virtual ID (VRID). Within the group, the VRID must be the same. The VRID can no longer be used for other groups. The virtual router is assigned a virtual IP address and a virtual MAC address. One of the VRRP routers within the group is specified as the master router. The master router has priority 255. The other VRRP routers are backup routers. The master router assigns the virtual IP address and the virtual MAC address to its network interface. The master router sends VRRP packets 724 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks (advertisements) to the backup routers at specific intervals. With the VRRP packets, the master router signals that it is still alive. The master router also replies to the ARP queries. If the virtual master router fails, a backup router takes over the role of the master router. The backup router with the highest priority becomes the master router. If the priority of the backup routers is the same, the higher MAC address decides. The backup router becomes the new virtual master router. The new virtual master router adopts the virtual MAC and IP address. This means that no routing tables or ARP tables need to be updated. The consequences of a device failure are therefore minimized. You configure VRRP in "Layer 3 > VRRP". OSPFv2 Dynamic routing with OSPF v2 OSPF (Open Shortest Path First) is a cost-based routing protocol. To calculate the shortest and most cost-effective route, the Short Path First algorithm by Dijkstra is used. OSPF was developed by the IETF (Internet Engineering Task Force). You configure OSPFv2 in "Layer 3 > OSPFv2". OSPF v2 divides an autonomous system (AS) into different areas. Areas in OSPF The following areas exist: Backbone The backbone area is area 0.0.0.0. All other areas are connected to this area. The backbone area is connected either directly or via virtual connections with other areas. All routing information is available in the backbone area. As a result, the backbone area is responsible for forwarding information between different areas. Stub Area This area contains the routes within its area within the autonomous system and the standard route out of the autonomous system. The destinations outside this autonomous system are assigned to the standard route. Totally Stubby Area This area knows only the routes within its area and the standard route out of the area. Not So Stubby Area (NSSA) This area can forward (redistribute) packets from other autonomous systems into the areas of its own autonomous system. The packets are further distributed by the NSSA router. WinCC Basic V13.0 System Manual, 02/2014 725 Editing devices and networks 8.1 Configuring devices and networks Routers of OSPF OSPF distinguishes the following router types: Internal router (IR) All OSPF interfaces of the router are assigned to the same area. Area Border Router (ABR) The OSPF interfaces of the router are assigned to different areas. One OSPF interface is assigned to the backbone area. Where possible, routes are grouped together. Backbone Router (BR) At least one of the OSPF interfaces is assigned to the backbone area. Autonomous System Area Border Router (ASBR) One interface of the router is connected to a different AS, for example an AS that uses the routing protocol RIP. Virtual connection Each area must be physically connected to the backbone area. In some situations a physical connection is not possible. The remote router is connected to a backbone router via a virtual connection. In the area through which the virtual connection runs, there is no designated router or designated backup router. LSA types Within the autonomous system, packets are exchanged that contain information about the connections of a router and the connection status message. The packets are also known as LSAs (Link State Advertisements). The LSAs are always sent from the router to the neighbor router. If there are changes in the network, LSAs are sent to all routers in the network. The information depends on the LSA type. 726 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks 166$ $6%5 166$ $UHD $%5 6WXE$UHD ,5 %5 $%5 $%5 ,5 '5 $%5 ,5 6WXE$UHD %DFNERQH $UHD $%5 6WXE$UHD $6%5 WinCC Basic V13.0 System Manual, 02/2014 Router LSA (LSA Type 1) The LSA Type 1 is only sent within an area. For each active connection of the router that belongs to the area in consideration, an LSA Type 1 is generated. The LSA Type 1 contains information about the status and the costs of the connection, for example IP address, network mask, network type Network LSA (LSA Type 2) The LSA Type 2 is sent only within an area. For each network that belongs to the relevant area, the router generates an LSA Type 2. If several routers are interconnected in a network, the LSA Type 2 is sent by the designated router (DR). The LSA Type 2 includes the network address, the network mask and a list of routers that are connected to the network 727 Editing devices and networks 8.1 Configuring devices and networks Summary LSA (LSA Type 3 / LSA Type 4) The Summary LSA is generated by the area border router and sent into the area. The Summary LSA contains information about routes outside the area but inside the AS. Where possible, the routes are grouped together. Summary LSA (LSA Type 3) The LSA Type 3 describes the routes to the networks and advertises the standard route to the areas. AS Summary LSA (LSA Type 4) The LSA Type 4 describes the routes to the ASBR. External LSA (LSA Type 5 / LSA Type 7) The External LSA is generated by the ASBR. The LSA type depends on the area. AS External LSA (LSA Type 5) The LSA Type 5 is sent by the AS border router into the areas of the autonomous system except the Stub and NSSA areas. The LSA contains information about routes to a network in another AS. The routes are either created manually or learned externally. The ASBR uses LSA Type 5 to distribute standard routes to the backbone area. NSSA External LSA (LSA Type 7) The LSA Type 7 is generated by the AS border router of an NSSA. The router is also known as the NSSA ASBR. The LSA Type 7 is sent only within the NSSA. If the P bit in LSA Type 7 = 1, these LSAs are converted to LSA Type 5 by the ABR and sent to the backbone area. Establishing the neighborhood The router runs through the following statuses to establish a connection to the neighbor router. 1. Attempt state / Init state The router activates OSPF and begins to send and receive Hello packets. Based on the received Hello packets, the router learns which OSPF routers are in its vicinity. The router checks the content of the Hello packet. The Hello packet also contains the list of the neighbor routers (neighbor table) of the "sender". 2. Two way state If, for example, the ID of the area, the area type and the settings for the times match, a connection (adjacency) can be established to the neighbor. In a point-to-point network, the connection is established directly. If several neighbor routers can be reached in a network, the designated router (DR) and the designated backup router (DBR) are identified based on Hello packets. The router with the highest router priority becomes the designated router. If two routers have the same router priority, the router with the lower router ID becomes the designated router. The router establishes a connection to the designated router. 3. Exchangestart state The neighbor routers decide which router starts communication. The router with the higher router ID becomes master. 4. Exchange state The neighbor routers send packets that describe the content of their neighborhood database. The neighborhood database (link state database - LSDB) contains information on the topology of the network. 728 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks 5. Loading state The router completes the received information. If the router still has questions relating to the status of a specific connection, it sends a link state request. The neighbor router sends a response (link state update). The response contains a suitable LSA. The router confirms receipt of the response (link state acknowledge). 6. Full State The information exchange with the neighbor router is completed. The neighborhood database of the neighbor router is the same. Based on the Short Path First algorithm, the router calculates a route to every destination. The route is entered in the routing table. Check the neighborhood The Hello packets are only used to establish the neighborhood relations. Hello packets are used to check the connection to the neighbor router by sending them cyclically. If no Hello packet is received within a certain interval (dead interval), the connection to the neighbor is marked as "down". The relevant entries are deleted. Updating the neighborhood database Once the neighborhood database is established, LSAs are sent to all routers in the network if there are changes in the topology. RIPv2 Dynamic routing with RIPv2 The Routing Information Protocol (RIPv2) is used to create routing tables automatically. RIPv2 is used in autonomous systems (AS) with a maximum of 15 routers. It is based on the DistanceVector algorithm. RIPv2 was developed by the IETF (Internet Engineering Task Force) and is described in RFC 2453. You configure RIPv2 in "Layer 3 > RIPv2". Setting up a routing table Since a router initially only knows its directly connected networks, it sends a request to its direct neighbor routers. As the reply, it receives the routing tables of the neighbor routers. Based on the information it receives, the router set up its own routing table. The routing table contains entries for all possible destinations. Each entry includes the distance to the destination and the first router on the route. The distance is also known as the metric. This indicates the number of routers to be passed through on the route to the destination (hop count). The maximum distance is 15 routers (hops). Updating the routing table Once the routing table is set up, the router sends its routing table to each direct neighbor router at intervals of 30 seconds. WinCC Basic V13.0 System Manual, 02/2014 729 Editing devices and networks 8.1 Configuring devices and networks The router compares new routing information with its existing routing table. If the new information includes shorter routes, the existing routes are overwritten. The router only keeps the shortest route to a destination. Checking neighbor routers If a router does not receive messages from a neighbor router for longer than 180 seconds, it marks the router as being invalid. The router assigns the metric 16 for the neighbor router. Link aggregation Link aggregation With link aggregation, several parallel physical connections with the same transmission speed are grouped together to form a logical connection with a higher transmission speed. This method based on IEEE 802.3ad is also known as port trunking or channel bundling. Link aggregation works only with full duplex connections with the same transmission speed in point-to-point mode. This achieves multiplication of the bandwidth or transmission speed. If part of the connection fails, the data traffic is handled via the remaining parts of the connection. To control and monitor, the Link Aggregation Control Layer (LACL) and the Link Aggregation Control Protocol (LACP) are used. Authentication Authentication method You can configure the authentication methods "802,1x" and "MAC Authentication" as well as the "Guest VLAN" option separately for each port. The functions have a hierarchical order. If all three functions are enabled, an attempt is made initially to authenticate the end device using "802.1x". If this authentication is unsuccessful, "MAC Authentication" is started. If this authentication is also unsuccessful, the end device is enabled for communication in the "Guest VLAN". ""Guest VLAN" can only be used if at least one authentication method is active. The two authentication methods depend on the end device. If the end device supports EAP (Extensible Authentication Protocol), it can be authenticated using the "802.1x" method. If the end device does not support EAP, it can be authenticated using "MAC Authentication". In this case, the IE switch adopts the role of the end device and uses the MAC address of the device as the authentication parameter. 802.1x The "802.1x" authentication method works as follows: An end device that supports EAP sends authentication information to the IE switch. The IE switch forwards the information to the authentication server. The authentication server checks the information and allows or denies the end device access to the network. 730 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks MAC Authentication The "MAC Authentication" authentication method works as follows: As soon as the IE switch receives a frame from the end device, the IE switch sends a query to the RADIUS server to allow or deny the end device access to the network. Editing properties and parameters Editing options You have the following options for editing properties and parameters: Hardware and network editor Once you have inserted the network component, you can edit the properties and parameters, for example the device name. You will find more detailed information in "Hardware and network editor". Web Based Management (WBM) The parameters and properties are accessible using the supplied HTML pages (WBM pages). Each WBM page has its own help page that describes the properties and parameters. For further information, refer to the configuration manual "SCALANCE XM400/ X-500 Web Based Management". You will find the MIB at Siemens Industry Automation and Drives Service & Support on the Internet under the entry ID 67428305 (http:// support.automation.siemens.com/WW/view/en/67428305). Command Line Interface All the configuration settings for the device can be made using the CLI. The CLI provides the same options as Web Based Management (WBM). For further information, refer to the configuration manual "SCALANCE XM400/X-500 Command Line Interface". You will find the MIB at Siemens Industry Automation and Drives Service & Support on the Internet under the entry ID 67430663 (http://support.automation.siemens.com/WW/view/en/ 67430663). Availability The availability of the settings depends on the port type on the configuration mode SCALANCE X distinguishes the following port types: Switch port Router port The following configuration modes are available: WinCC Basic V13.0 System Manual, 02/2014 731 Editing devices and networks 8.1 Configuring devices and networks Offline configuration You can configure a PC station the first time offline. In this mode only the settings that require no connection to the device are available. Online configuration mode If there is a connection to the device, there are additional pages available in the Inspector window. These pages include the note "This page is only available if there is an online connection to the device". With some settings, the additional information "only available online" is included. Creating and deleting an entry As an example, an entry will be created and deleted on the Syslog client. The procedure is valid on all pages. Creating a new entry 1. Select the device in the network or device view. 2. Open the properties of the device in the Inspector window. 3. In the Inspector window go to System > Syslog client. 4. Enter the IP address for the Syslog server. 5. Click in the table. 6. Select the entry "New entry" in the shortcut menu. A new entry is created in the table. Deleting an entry 1. Select the required entry in the table. 2. Select the "Delete" entry in the shortcut menu. Buttons you require often Refresh the display with "Refresh" Pages that display current parameters have a "Refresh" button at the lower edge of the page. Click this button to request up-to-date information from the device for the current page. Save settings for all ports with "Transfer to table" Pages on which you can configure several ports have 2 tables. In the first table, you can make the settings for all ports and transfer these to the second table. In the last column of the first table, there is the "Transfer to table" button. Click this button to save the settings you have made for all ports. IP address assignment Configuration options When shipped and after restoring to the factory settings, the device does not have an IP address. 732 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks The following options are available to assign an IP address to the device: DHCP (default setting) Primary Setup Tool For further information, refer to the configuration manual "Primary Setup Tool". You will find the MIB at Siemens Industry Automation and Drives Service & Support on the Internet under the entry ID 19440762 (http://support.automation.siemens.com/WW/view/en/ 19440762). STEP 7 CLI via the serial interface For further information, refer to the configuration manual "SCALANCE X500 Command Line Interface". You will find the MIB at Siemens Industry Automation and Drives Service & Support on the Internet under the entry ID 67430663 (http:// support.automation.siemens.com/WW/view/en/67430663). Requirement "Set IP address on device" is enabled in the properties of the device. You will find more detailed information in "Addressing PROFINET devices". SCALANCE XR500 as IO device: "Compile" and "Download to device" With a SCALANCE XR500 configured as a PROFINET IO device and assigned to an IO controller, the functions "Compile" and "Download to device" only download the data to the switch that can also be configured in Web Based Management (WBM) (layer 2, layer 3, system, security). If you want to use the "Compile" or "Download to device" functions for the PROFINET IO device data of the XR500, first select the assigned IO controller. Information Versions Note The page is only available if there is an online connection to the device. This page shows the versions of the hardware and software of the device. Description Table 1 has the following columns: Hardware Shows the device being used. Name Shows the name of the device or module. WinCC Basic V13.0 System Manual, 02/2014 733 Editing devices and networks 8.1 Configuring devices and networks Revision Shows the hardware version of the device. Order ID Shows the order number of the device or module. Table 2 has the following columns: Software - Firmware Shows the current firmware version. If a new firmware file was downloaded and the device has not yet restarted, the firmware version of the downloaded firmware file is displayed here. After the next restart, the downloaded firmware is activated and used. - Bootloader Shows the version of the boot software stored on the device. Description Shows the short description of the software. Version Shows the version number of the software version. Date Shows the date on which the software version was created. I&M Note The page is only available if there is an online connection to the device. This page contains information about device-specific vendor and maintenance data such as the order number, serial number, version number etc. You cannot configure anything on this page. Description of the displayed values The table has the following rows: Manufacturer ID Shows the manufacturer ID. Order number Shows the order number. Serial number Shows the serial number. Hardware revision Shows the hardware version. Software version Shows the software version. 734 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Revision counter Shows the revision counter: Counter for revisions since the initial commissioning Revision Date Date and time of the last revision Function tag Shows the function tag (plant designation) of the device. The plant designation (HID) is created during configuration of the device with HW Config of STEP 7. Location tag Shows the location tag of the device. The location identifier (LID) is created during configuration of the device with HW Config of STEP 7. ARP table Note The page is only available if there is an online connection to the device. Assignment of MAC address and IP address With the Address Resolution Protocol (ARP), there is a unique assignment of MAC address to IPv4 addresses. This assignment is kept by each network node in its own separate ARP table. The page shows the ARP table of the device. Displayed values The table has the following columns: Interface Shows the interface via which the row entry was learnt. MAC address Shows the MAC address of the target device. IP address Shows the IP address of the target device. Media Type Shows the type of connection. - Dynamic The device recognized the address data automatically. - Static The addresses were entered as static addresses WinCC Basic V13.0 System Manual, 02/2014 735 Editing devices and networks 8.1 Configuring devices and networks Log table Logging events Note The page is only available if there is an online connection to the device. The device allows you to log events that occur, some of which you can specify in " System > Events". This, for example, allows you to record when an authentication attempt failed or when the connection status of a port has changed. The content of the events log table is retained even when the device is turned off. Settings Severity Filters You can filter the entries in the table according to severity. To display all the entries, enable or disable all settings. - Info Information (6) - Warning Warnings (4) - Critical Critical (2) Displayed values The table has the following columns: Restart Counts the number of restarts since you last reset to factory settings and shows the device restart after which the corresponding event occurred. System up time Shows the time the device has been running since the last restart when the described event occurred. If the system time is set, the time is also displayed at which the event occurred. System Time Shows the date and time of the device. Severity Shows the severity. Log Message Displays a brief description of the event that has occurred. 736 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Buttons Delete Click this button to delete the content of the event log file. The display is also cleared. The restart counter is only reset after you have restored the device to the factory settings and restarted the device. Note The number of entries in this table is restricted to 400. When this number is reached, the oldest entries are overwritten. The table remains permanently in memory. Fault Error status Note The page is only available if there is an online connection to the device. This page displays any errors that occur. If there are no more unanswered error/fault messages, the fault LED goes off. The time calculation always begins after the last system start. When the system is restarted, a new entry with the type of restart is created in the fault memory. Description of the displayed values No. of Signaled Faults Shows the number of reported faults. The table contains the following columns: Fault Time Shows the time the device has been running since the last restart when the described error/ fault occurred. Fault description Display of the fault state for the device. Clear Fault State When you can delete faults, the "Clear Fault State" button is enabled. WinCC Basic V13.0 System Manual, 02/2014 737 Editing devices and networks 8.1 Configuring devices and networks Redundancy Spanning Tree Note The page is only available if there is an online connection to the device. The page shows the current information about the Spanning Tree and the settings of the root bridge. If Spanning Tree is turned off, only the basic information about this device is displayed. If Spanning Tree is activated, the following is displayed: - Parameters of the selected instance - Parameters for the ports of the selected instance The information depends on the selected Spanning Tree mode. Displayed values Spanning Tree Mode Shows the set mode. You specify the mode in "Layer 2 > MSTP > General". The following values are possible: - '-' - STP - RSTP - MSTP Instance ID Shows the number of the instance. The parameter depends on the configured mode. Bridge Priority / Root Priority Which device becomes the root bridge is decided by the bridge priority. The bridge with the highest priority (in other words, with the lowest value for this parameter) becomes the root bridge. If several devices in a network have the same priority, the device whose MAC address has the lowest numeric value will become the root bridge. Both parameters, bridge priority and MAC address together form the bridge identifier. Since the root bridge manages all path changes, it should be located as centrally as possible due to the delay of the frames. The value for the bridge priority is a whole multiple of 4096. Bridge address / root address The bridge address shows the MAC address of the device and the root address shows the MAC address of the root bridge. Root Cost Shows the path costs from the device to the root bridge. In MSTP mode, the path costs as far as the root bridge of the CIST are displayed. Bridge Status Shows the status of the bridge, e.g. whether or not the device is the root bridge. 738 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Regional root priority (available only with MSTP) For a description, see Bridge priority / Root priority. Regional root address (available only with MSTP) Shows the MAC address of the device. Regional root costs (only available with MSTP) The path costs from this device to the regional root bridge. The table has the following columns: Port Shows the port via which the device communicates. Role Shows the status of the port. The following values are possible: - Disabled The port was removed manually from the spanning tree and will no longer be taken into account by the spanning tree. - Designated The ports leading away from the root bridge. - Alternate The port with an alternative route to a network segment - Backup If a switch has several ports to the same network segment, the "poorer" port becomes the backup port. - Root The port that provides the best route to the root bridge. - Master This port points to a root bridge located outside the MST region. Status Displays the current status of the port. The values are only displayed. The parameter depends on the configured protocol. The following statuses are possible: - Discarding The port receives BPDU frames. Other incoming or outgoing frames are discarded. - Listening The port receives and sends BPDU frames. The port is involved in the spanning tree algorithm. Other outgoing and incoming frames are discarded. - Learning The port actively learns the topology; in other words, the node addresses. Other outgoing and incoming frames are discarded. - Forwarding Following the reconfiguration time, the port is active in the network. The port receives and sends data frames. Oper. Version Describes the type of spanning tree in which the port operates WinCC Basic V13.0 System Manual, 02/2014 739 Editing devices and networks 8.1 Configuring devices and networks Priority If the path calculated by the spanning tree is possible over several ports of a device, the port with the highest priority (in other words the lowest value for this parameter) is selected. A value between 0 and 240 can be entered for the priority in steps of 16. If you enter a value that cannot be divided by 16, the value is automatically adapted. Path costs This parameter is used to calculate the path that will be selected. The path with the lowest value is selected. If several ports of a device have the same value, the port with the lowest port number will be selected. If the value "Cost Calc." is "0", the automatically calculated value is displayed. Otherwise, the value of "Cost Calc." is displayed. The calculation of the path costs is largely based on the transmission speed. The higher the achievable transmission speed is, the lower the value of the path costs. Typical values for path costs with rapid spanning tree: - 10,000 Mbps = 2,000 - 1000 Mbps = 20,000 - 100 Mbps = 200,000 - 10 Mbps = 2,000,000. Edge type Shows the type of the connection. The following values are possible: - Edge Port An edge port is connected to this port. - No Edge Port There is a spanning tree or rapid spanning tree device at this port. P.t.P. Type Shows the type of point-to-point link. The following values are possible: - P.t.P. With half duplex, a point-to-point link is assumed. - Shared Media With a full duplex connection, a point-to-point link is not assumed. VRRP statistics Introduction Note The page is only available if there is an online connection to the device. This page shows the statistics of the VRRP protocol and all configured virtual routers. 740 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Description of the displayed values The following fields are displayed: VRID errors Shows how many VRRP frames containing an unsupported VRID were received. Version errors Shows how many VRRP frames containing an invalid version number were received. Checksum errors Shows how many VRRP frames containing an invalid checksum were received. The table has the following columns: Interfaces Interface to which the settings relate. VRID Shows the ID of the virtual router. Valid values are 1 to 255. Change to master status Shows how often this virtual router changed to the "Master" role. Advertisements recd. Shows how often a VRRP frame was received that contained a bad address list. Advertisement Interval Errors Shows how many bad VRRP packets were received whose interval does not match the value set locally. IP TTL errors Shows how many bad VRRP packets were received whose TTL (Time to live) value in the IP header is incorrect. Prio 0 received Shows how many VRRP packets with priority 0 were received. VRRP packets with priority 0 are sent when a master router is shut down. These packets allow a fast handover to the relevant backup router. Prio 0 sent Shows how many VRRP packets with priority 0 were sent. Packets with priority 0 are sent when a master router is shut down. These packets allow a fast handover to the relevant backup router. Invalid Type Shows how often a VRRP packet was received that had the wrong type. Address List Errors Shows the number of errors in the address list. Invalid Auth. Type Shows how many bad VRRP packets were received whose authentication type was not type 0. Type 0 means "no authentication". WinCC Basic V13.0 System Manual, 02/2014 741 Editing devices and networks 8.1 Configuring devices and networks Auth. Type Mismatch Shows how many bad VRRP frames were received whose authentication type does not match. Frame length error Shows how many bad VRRP frames were received whose length is not correct. Ring Redundancy Note The page is only available if there is an online connection to the device. Automatic Redundancy Detection (ARD) is the default when the device ships. If you want to use the previous High Speed Redundancy Protocol (HRP), HRP must be configured. Reconfiguration time of the frame traffic following a failover in MRP: 200 ms Reconfiguration time of the frame traffic following a failover in HRP: 300 ms This page informs you about the values currently set for the device. 742 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Description The following fields are displayed: Redundancy Function The following values are shown: - Disabled Ring redundancy is disabled on the device. - MRP Manager The device is operating as MRP manager. - MRP Client The device is operating as MRP client. - HRP Client The device is operating as HRP client. - HRP Manager The device is operating as HRP manager. RM Status The "RM Status" column shows whether or not the IE switch is operating as redundancy manager and whether it has opened or closed the ring in this role. - Passive The IE switch is operating as redundancy manager and has opened the ring; in other words, the line of switches connected to the ring ports is operating problem free. The passive status is also displayed if the IE switch is not operating as the redundancy manager (RM Function Disabled). - Active The IE switch is operating as redundancy manager and has closed the ring; in other words, the line of switches connected to the ring ports is interrupted (problem). The redundancy manager connects its ring ports through and restores an uninterrupted linear topology. - If media redundancy in ring topologies is completely disabled, ring ports configured last are displayed and the text "Ring Redundancy disabled" is displayed. Observer Status Shows the current status of the observer. Ring ports Ring ports 1 and ring port 2 show the ports used for redundancy. No. of Changes to RM Active State Shows how often the device as redundancy manager switched to the active status, i.e. closed the ring. If the redundancy function is disabled or the device is not the HRP/MRP manager, the text "Redundancy manager disabled" appears. Max. delay of the RM test frames [ms] Shows the maximum delay for test frames of the redundancy manager. If the redundancy function is disabled or the device is not the HRP/MRP manager, the text "Redundancy manager disabled" appears. WinCC Basic V13.0 System Manual, 02/2014 743 Editing devices and networks 8.1 Configuring devices and networks Standby Note The page is only available if there is an online connection to the device. This page shows the standby status of the device. For more information on Ethernet cabling and the topological location of master and slave, refer to the "Industrial Ethernet Network Manual". Description The following fields are displayed: Standby ports Shows the ports being used. Standby name Shows the name for the standby connection. The master/slave device pair is defined by this name (both must be in the same ring). This is achieved by entering the same name on two devices in the ring. You can select any name to suit your purposes, however, you can only use the name for one pair of devices in the entire network. Standby Function Shows whether the standby connection is activated or deactivated. - Master The device has a connection to the partner device and is operating as master. In normal operation, the standby port of this device is active. - Slave The device has a connection to the partner device and is operating as slave. In normal operation, the standby port of this device is inactive. - Disabled The standby link is disabled. The device is operating neither as master nor slave. The standby port is working as a normal port without standby function. - Waiting for Connection... No connection has yet been established to the partner device. The standby port is inactive. In this case, either the configuration on the partner device is inconsistent (for example incorrect connection name, standby link disabled) or there is a physical fault (for example device failure, link down). - Connection Lost The existing connection to the partner device has been lost. In this case there is either a physical fault (for example, device failure, link down) or the configuration on the partner device was modified (for example different connection name, standby link disabled). 744 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Standby status Shows the status of the standby port: - Active The standby port of this device is active; in other words is enabled for frame traffic. - Passive The standby port of this device is inactive; in other words is blocked for frame traffic. No. of Changes to Standby Active State Shows the number of changes from the inactive to the active status. Ethernet Statistics Interface statistics Interface statistics The page shows the statistics from the interface table of the Management Information Base (MIB). Note The page is only available if there is an online connection to the device. Displayed values The table has the following columns: Received bytes Shows the number of received bytes. Sent bytes Shows the number of sent bytes. Received unicast frames Shows the number of received unicast frames. Received non-unicast frames Shows the number of received frames that are not of the type unicast. Sent unicast frames Shows the number of sent unicast frames. Sent non-unicast frames Shows the number of sent frames that are not of the type unicast. WinCC Basic V13.0 System Manual, 02/2014 745 Editing devices and networks 8.1 Configuring devices and networks Frame length Frames sorted by length This page displays how many frames of which size were sent and received at each port. Note The page is only available if there is an online connection to the device. Displayed values The table has the following columns: Port Shows the available ports and link aggregations. Note Display of frame statistics In the statistics relating to frame lengths, note that both incoming and outgoing frames are counted. Frame lengths The other columns after the port number contain the absolute numbers of incoming frames according to their frame length. The following frame lengths are distinguished: - 64 bytes - 65 - 127 bytes - 128 - 255 bytes - 256 - 511 bytes - 512 - 1023 bytes - 1024 - max. Button Reset Counter Click "Reset Counter" to reset all counters. The counters are also reset by a restart. 746 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Frame type Received frames sorted by type This page displays how many frames of the type "unicast", "multicast", and "broadcast" were received at each port. Note The page is only available if there is an online connection to the device. Displayed values The table has the following columns: Port Shows the available ports and link aggregations. Unicast/Multicast /Broadcast The other columns after the port number contain the absolute numbers of the incoming frames according to their frame type "unicast", "multicast" and "broadcast". Button Reset Counter Click "Reset Counter" to reset all counters. The counters are also reset by a restart. Packet Errors Received bad frames This page shows how many bad frames were received per port. Note The page is only available if there is an online connection to the device. WinCC Basic V13.0 System Manual, 02/2014 747 Editing devices and networks 8.1 Configuring devices and networks Displayed values The table has the following columns: Port Shows the available ports and link aggregations. Error types The other columns after the port number contain the absolute numbers of the incoming frames according to their error type. In the columns of the table, a distinction is made according to the following error types: - CRC Frames whose content does not match the CRC checksum. - Undersize Frames with a length less than 64 bytes. - Oversize Frames discarded because they were too long. - Fragments Frames with a length less than 64 bytes and a bad CRC checksum. - Jabbers VLAN-tagged frames with an incorrect CRC checksum that were discarded because they were too long. - Collisions Collisions that were detected. Button Reset Counter Click "Reset Counter" to reset all counters. The counters are also reset by a restart. History Samples of the statistics The page shows samples from each port with information from the statistics. Note The page is only available if there is an online connection to the device. 748 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Settings Port Select the port for which the history will be displayed. Displayed values Entries Maximum number of samples that can be saved at the same time. Interval [s] Interval after which the current status of the statistics will be saved as a sample. The table has the following columns: Sample Number of the sample Time for the Sample System up time at which the sample was taken. Unicast Number of received unicast frames. Multicast Number of received multicast frames. Broadcast Number of received broadcast frames. CRC Number of frames with a bad CRC checksum. Undersize Number of frames that are shorter than 64 bytes. Oversize Number of frames discarded because they were too long. Fragments Number of frames that are shorter than 64 bytes and have a bad CRC checksum. Jabbers Number of frames with a VLAN tag that have a bad CRC checksum and will be discarded because they are too long. Collisions Number of collisions of received frames. Utilization Utilization of the port during a sample. Unicast This page shows the learnt and static unicast MAC addresses. WinCC Basic V13.0 System Manual, 02/2014 749 Editing devices and networks 8.1 Configuring devices and networks Description VLAN ID Shows the VLAN-ID assigned to this MAC address. MAC Address Shows the MAC address of the node that the device has learned or the user has configured. Status Shows the status of each address entry: - Learnt The specified address was learned by receiving a frame from this node and will be deleted when the aging time expires if no further packets are received from this node. - Static Configured by the user. Static addresses are stored permanently; in other words, they are not deleted when the aging time expires or when the switch is restarted. Port Shows the port via which the node with the specified address can be reached. Frames received by the device whose destination address matches this address will be forwarded to this port. Multicast This page shows the learnt and static multicast MAC addresses. Description VLAN ID Shows VLAN ID of the VLAN to which the MAC multicast address is assigned. MAC Address Shows the MAC multicast address that the device has learned or the user has configured. Status Shows the status of each address entry. The following information is possible: - static The address was entered statically by the user. Static addresses are stored permanently; in other words, they are not deleted when the aging time expires or when the device is restarted. These must be deleted by the user. - IGMP The destination port for this address was obtained by IGMP configuration. - GMRP The destination port for this address was registered by a received GMRP frame. Routing Routing table This page shows the routing table of the device. 750 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Description The table has the following columns: Destination network Shows the destination address of this route. Subnet mask Shows the subnet mask of this route. Gateway Shows the gateway for this route. Interface Shows the interface for this route. Metric Shows the metric of the route. The higher value, the longer the packets require to their destination. Routing protocol Shows the routing protocol from which the entry in the routing table originates. The following entries are possible: - Connected: Connected routes - Static: Static routes - RIP: Routes using RIP - OSPF: Routes using OSPF - other: Other routes OSPFv2 interfaces Overview Note The page is only available if there is an online connection to the device. This page shows the configuration of the OSPF interface. Description of the displayed values The table has the following columns: IP address Shows the IP address of the OSPF interface Area ID Shows the Area ID to which the OSPF interface belongs. WinCC Basic V13.0 System Manual, 02/2014 751 Editing devices and networks 8.1 Configuring devices and networks Interface Status Shows the status of the WLAN interface: - Down The interface is not available. - Loopback Loopback interface - Waiting Startup and negotiation of the interface. - Point to Point Point-to-point connection - Designated Router The router is a designated router and generates a network LSA. - Backup D. Router The router is backup for the designated router. - Other D. Router The interface is started up. The router is neither a designated router nor a backup designated router. OSPF status Shows the status of OSPF. - Enabled: OSPF is enabled on the interface. - Disabled: OSPF is disabled on the interface. Designated Router Shows the IP address of the designated router for this OSPF interface. Backup Designated Router Shows the IP address of the designated backup router for this OSPF interface. Events Shows the number of status changes of OSPF. OSPFv2 neighbors Note The page is only available if there is an online connection to the device. This page shows the dynamically detected neighbor routers in the relevant networks. Description of the displayed values The table has the following columns: IP address Shows the IP address of the neighbor router in this network. Router ID Shows the ID of the neighbor router. The two addresses can match. 752 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Status Shows the status of the neighbor router. The status can adopt the following values: - unknown Status of the neighbor router is unknown. - down The neighbor router cannot be reached. - attempt and init Short-lived statuses during initialization - two-way Two-way receipt of Hello packets. Specification of the designated router and the designated backup router. - exchangestart, exchange and loading Status during exchange of the LSAs - full The database is complete and synchronized within the area. The routes can now be detected. Note Normal status If the partner router is a designated router or a designated backup router, the status is "full". Otherwise the status is "two-way". Assoc. Area Type Shows the area type via which the neighbor-neighbor relation is maintained. The following area types exist: - Normal - Stub - NSSA - Backbone Priority Shows the priority of the neighbor router. This is only significant when selecting the designated router on a network. For virtual neighbor routers, this information is irrelevant. Hello Suppr. Shows whether there are suppressed Hello packets to the virtual neighbor router. - no: There are no suppressed Hello packets (default). - yes: There are suppressed Hello packets. Hello Queue Shows the length of the queue with Hello packets still to be transmitted. Events Shows the number of status changes. WinCC Basic V13.0 System Manual, 02/2014 753 Editing devices and networks 8.1 Configuring devices and networks OSPFv2 virtual neighbors Note The page is only available if there is an online connection to the device. This page shows the configured virtual neighbor routers. Overview The table has the following columns: IP address Shows the IP address of the virtual neighbor router in this network. Router ID Shows the router ID of the virtual neighbor router. Status Shows the status of the neighbor router. The status can adopt the following values: - unknown Status of the neighbor router is unknown. - down The neighbor router cannot be reached. - attempt and init Short-lived statuses during initialization - two-way Two-way receipt of Hello packets. Specification of the designated router and the designated backup router. - exchangestart, exchange and loading Status during exchange of the LSAs - full The database is complete and synchronized within the area. The routes can now be detected. Note Normal status If the partner router is a designated router or a designated backup router, the status is "full". Otherwise the status is "two-way". Trans. Area ID Shows the ID of the area via which the virtual neighborhood relation exists. Hello Suppr. Shows whether there are suppressed Hello packets to the virtual neighbor router. - no: There are no suppressed Hello packets (default) - yes: There are suppressed Hello packets. 754 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Hello Queue Shows the length of the queue with Hello packets still to be transmitted. Events Shows the number of status changes. OSPFv2 LSDB Overview Note The page is only available if there is an online connection to the device. The link state database is the central database for managing all links within an area. It consists of the link state advertisements (LSAs). The most important data of these LSAs is shown on the this WBM page. WinCC Basic V13.0 System Manual, 02/2014 755 Editing devices and networks 8.1 Configuring devices and networks Description of the displayed boxes The table has the following columns: Area ID Shows the ID of the area to which the LSA belongs. If the LSA is an external connection, '-' is displayed. LSA type Shows the LSA type. The following values are possible: - unknown LSA type is unknown. - Router The router LSA (Type 1) is sent by the OSPF router within an area. The LSA contains information about the status of all router interfaces. - Network The network LSA (Type 2) is sent by the designated router within an area. The LSA contains a list of routers connected to the network. - NSSA External The NSSA external LSA (Type 7) is sent by the NSSA-ASBR within an NSSA. The NSSA-ASBR receives LSAs of Type 5 and converts the information to LSAs of Type 7. The NSSA router can forward these LSAs within an NSSA. - Summary The summary LSA (Type 3) is sent by the ABR within an area. The LSA contains information about routes to other networks. - AS Summary The AS summary LSA (Type 4) is sent by the area border router within an area. The LSA contains information about routes to other autonomous systems. - AS External The AS external LSA (Type 5) is sent by the AS border router within an autonomous system. The LSA contains information about routes from one network to another. Link State ID Shows the ID of the LSA. Router ID Shows the ID of the router that sent this LSA. Sequence number Shows the sequence number of the LSA. Each time an LSA is renewed, this sequence number is incremented by one. RIPv2 statistics Overview Note The page is only available if there is an online connection to the device. 756 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks This page shows the statistics of the RIP interface. Description of the displayed values The table has the following columns: IP address Shows the IP address of the RIPv2 interface Bad packets Number of received RIP packets that were deleted and therefore ignored. Bad Routes Number of routes of valid RIP packets that could not be taken into consideration. Updates Sent Shows how often the router has sent its routing table to its neighbor routers. System Configuration On this page, you specify the services with which the device can be accessed. With some services, there are further configuration pages on which more detailed settings can be made. Settings Telnet Server Enable or disable the "Telnet Server" service for unencrypted access to the CLI. SSH server Enable or disable the "SSH Server" service for encrypted access to the CLI. HTTPS server only Enable or disable access using HTTP. DNS client Enable or disable depending on whether the IE switch should operate as a DNS client. You can configure other settings in "System > DNS Client". SMTP Client Enable or disable the SMTP client. You can configure other settings in "System > SMTP Client". Syslog Client Enable or disable the system event client. You can configure other settings in "System > Syslog client". WinCC Basic V13.0 System Manual, 02/2014 757 Editing devices and networks 8.1 Configuring devices and networks DCP Server Specify whether or not the device can be accessed with DCP (Discovery and Configuration Protocol): - "-" (disabled) DCP is disabled. Device parameters can neither be read nor modified. - Read/write access With DCP, device parameters can be both read and modified. - Read-Only With DCP, device parameters can be read but cannot be modified. Time Select the required setting. The following settings are possible: - Manual The system time is set manually. - SNTP Client The system time is set via an SNTP server. You can configure other settings in "System > System time > SNTP client". - NTP Client The system time is set via an NTP server. You can configure other settings in "System > System time > NTP client". - SIMATIC Time The system time is set using a SIMATIC time transmitter. You can configure other settings in "System > System Time SIMATIC Time Client". - PTP Client The system time is set via a PTP server. You can configure other settings in "System > System Time > PTP Client". This function is only available for SCALANCE X500. SNMP Select the required protocol. The following settings are possible: - "-" (SNMP disabled) Access to device parameters using SNMP is not possible. - SNMPv1/v2c/v3 Access to device parameters is possible with SNMP versions 1, 2c or 3. You can configure other settings in "System > SNMP > General". - SNMPv3 Access to device parameters is possible with SNMP version 3. You can configure other settings in "System > SNMP > General". SNMPv1/v2 Read-Only Enable or disable write access to SNMP variables with SNMPv1/v2c. SNMPv1 traps Enable or disable the sending of SNMP traps (alarm frames). You can configure other settings in "System > SNMP > Traps". 758 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks NFC (Near Field Communikation) Enable or disable the "NFC" function. This function is only available for SCALANCE XM400. Configuration mode Select the required mode. The following modes are possible: - Automatic save Automatic save mode. Approximately 1 minute after the last parameter change or when you restart the device, the configuration is automatically saved. - Trial In the "Trial" configuration mode, although changes are adopted, they are not saved in the configuration file (startup configuration). To save changes in the configuration file, use the "Write startup config" button. The button is displayed when you set this configuration mode. The display area also shows the message "Trial mode active - Press "Write Startup Config" button to make your settings persistent" as soon as there are unsaved modifications. This message can be seen on every page until the changes made have either been saved or the device has been restarted. General Device This page contains the general device information. Settings Current System Time(Only available online) Shows the current system time. The system time is either set by the user or by a time-ofday frame: either SINEC H1 time-of-day frame, NTP or SNTP. (readonly) System Up Time(only available online) Shows the operating time of the device since the last restart. (readonly) Device Type(only available online) Shows the type designation of the device. (readonly) System Name You can enter the name of the device. The entered name is displayed in the selection area. A maximum of 255 characters are possible. The system name is also displayed in the CLI input prompt. The number of characters in the CLI input prompt is limited. The system name is truncated after 16 characters. WinCC Basic V13.0 System Manual, 02/2014 759 Editing devices and networks 8.1 Configuring devices and networks System Contact You can enter the name of a contact person responsible for managing the device. Location You can enter the location of the device. The entered installation location is displayed in the selection area. Note The ASCII characters 0x20 to 0x7e are used in the input boxes. At the start and end of the input boxes"System Name", "System Contact" and "System Location", the characters "<", ">" and "space" are not permitted. Coordinates On this page, you configure the geographic coordinates (latitude, longitude and the height above the ellipsoid according to WGS84). These boxes are purely for information with a maximum length of 32 characters. Getting the coordinates Use suitable maps for obtaining the geographic coordinates of the device. The geographic coordinates can also be obtained using a GPS receiver. The geographic coordinates of these devices are normally displayed directly and only need to be entered in the input boxes of this page. Settings Latitude Enter the north or south latitude for the location of the device. For example, +49 1 31.67" means that the device is located at 49 degrees, 1 arc minute and 31.67 arc seconds north latitude. A south latitude is shown by a preceding minus character. You can also append the letters N (north latitude) or S (south latitude) to the numeric information (49 1 31.67" N). Longitude Enter the value of the eastern or western longitude of the location of the device. For example, +8 20 58.73" means that the device is located at 8 degrees, 20 minutes and 58.73 seconds east. A western longitude is indicated by a preceding minus sign. You can also add the letter E (eastern longitude) or W (western longitude) to the numeric information (8 20 58.73" E). Height Enter the value of the height above sea level in meters. For example, 158 m means that the device is located at a height of 158 m above sea level. Heights below sea level (for example the Dead Sea) are indicated by a preceding minus sign. 760 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Agent IP Configuration of the IP addresses Note The page is only available if there is an online connection to the device. On this page, you set the IP configuration for the device. With devices with more than one IP interface, this call references the "Subnets > Configuration" menu item in the "Layer 3" menu and the configuration of the TIA interface there. Note The IP address of the in-band port and the out-band port must belong to different subnets. Settings IP Address In the input boxes under "In band", enter the IP address, subnet mask and the default gateway. In the input boxes under "Out band", enter the IP address, subnet mask and the default gateway. If you change the IP address, the Web browser should automatically set itself to the new address. If this does not happen, enter the new address in the Web browser manually. Subnet mask Here, in "In-band", you enter the subnet mask of the in-band port and in "Out-band" the subnet mask of the out-of-band port. Default Gateway If the device is required to communicate with devices (diagnostics stations, e-mail servers etc.) in another subnet, enter the IP address of the default gateway here. The out-of-band port it is not accessible from a different subnet. Agent VLAN ID From the drop-down list, select the VLAN ID for the in-band management. You can only select VLANs that have already been configured. Note Changing the agent VLAN ID If the configuration PC is connected directly to the device via Ethernet and you change the agent VLAN ID, the device is no longer reachable via Ethernet following the change. MAC Address Shows the MAC address of the device. The MAC address is linked to the hardware and cannot be modified. WinCC Basic V13.0 System Manual, 02/2014 761 Editing devices and networks 8.1 Configuring devices and networks DNS client The DNS () server (Domain Name System) assigns a domain name to an IP address so that a device can be uniquely identified. If this function is enabled, the IE switch can communicate with a DNS server as a DNS client. Note The DNS client function can only be used if there is a DNS server in the network. Description The page contains the following boxes: DNS Client Enable or disable depending on whether the IE switch should operate as a DNS client. DNS Server IP Address Enter the IP address of the DNS server. Restart On this page, there is a button with which you can restart the device and various options for resetting to the device defaults. Note The page is only available if there is an online connection to the device. Note Note the following points about restarting a device: You can only restart the device with administrator privileges. A device should only be restarted with the buttons of this page or with the appropriate CLI commands and not by a power cycle on the device. Any modifications you have made only become active on the device after clicking the "Set Values" button on the relevant page. If the device is in "Trial Mode", configuration modifications must be saved manually before a restart. In "Automatic Save" mode, the last changes are saved automatically before a restart. 762 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Settings The following options are available for restarting: Restart Click this button to restart the system. You must confirm the restart in a dialog box. During a restart, the device is reinitialized, the internal firmware is reloaded, and the device runs a self-test. The learned entries in the address table are deleted. You can leave the browser window open while the device restarts. You then need to log in again: Restore Factory Defaults and Restart Click this button to restart the system. You must confirm the restart in a dialog box. During a restart, the device is reinitialized, the internal firmware is reloaded, and the device runs a self-test. The learned entries in the address table are deleted. You can leave the browser window open while the device restarts. You then need to log in again. Note By resetting all the defaults to the factory settings, the IP address and the passwords are also lost. Following this, the device can only be accessed using the Primary Setup Tool or using DHCP. With the appropriate attachment, a previously correctly configured device can cause circulating frames and therefore the failure of the data traffic. Load & save Uploading and saving using HTTP Loading and saving data via HTTP On this page, you store device data in an external file on your client PC or load such data from an external file from the PC to the devices. This means, for example, that you can also load new firmware from a file located on your client PC. Note Incompatibility with predecessor versions During the installation of a previous version, the configuration data can be lost. In this case, the device starts up with the factory settings after the firmware has been installed. Incompatibility with previous versions with PLUG inserted During the installation of a previous version, the configuration data can be lost. In this case, the device starts up with the factory settings after the firmware has been installed. In this situation, if a PLUG is inserted in the device, following the restart, this has the status "Not Accepted" since the PLUG still has the configuration data of the previous more up-to-date firmware. This allows you to return to the previous, more up-to-date firmware without any loss of configuration data. If the original configuration on the PLUG is no longer required, the PLUG can be deleted or rewritten manually using System > PLUG. WinCC Basic V13.0 System Manual, 02/2014 763 Editing devices and networks 8.1 Configuring devices and networks Note Configuration files and Trial mode/Automatic Save In "Automatic Save" mode, the data is saved automatically before the configuration files (ConfigPack and Config) are transferred. In Trial mode, although the changes are adopted, they are not saved in the configuration files (ConfigPack and Config). Use the "Write Startup Config" button on the "System > Configuration" WBM page to save changes in the configuration file. Settings The table has the following columns: Type Shows the file type. Description Shows the short description of the file type. Load With this button, you can upload files to the device. The button can be enabled, if this function is supported by the file type. Save With this button, you can save files from the device. The button can only be enabled if this function is supported by the file type and the file exists on the device. Delete With this button, you can delete files from the device. The button can only be enabled if this function is supported by the file type and the file exists on the device. Loading new firmware After successfully downloading the firmware, you will be requested to restart the device. Restart the device and continue to configure the newly started firmware. Procedure Loading files using HTTP 1. Start the upload function by clicking the one of the "Load" buttons. The dialog for uploading a file opens. 2. Go to the file you want to upload. 3. Click the "Open" button in the dialog. The file is now uploaded. 4. When the message "Restart required" appears, click the "Yes" button to trigger the restart. If you click the "No" button, there is no device restart. The changes only take effect after a restart. Saving files using HTTP 764 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks 1. Start the save function by clicking the one of the "Save" buttons. 2. You will be prompted to select a storage location and a name for the file. Or you accept the proposed file name. To make the selection, use the dialog in your browser. After making your selection, click the "Save" button. Deleting files using HTTP 1. Start the delete function by clicking the one of the "Delete" buttons. The file will be deleted. Reusing configuration data If several devices are to receive the same configuration and the IP addresses are assigned using DHCP, the effort for configuration can be reduced by saving and reading in the configuration data. Follow the steps below to reuse configuration data: 1. Save the configuration data of a configured device on your PC. 2. Download this configuration file to all other devices you want to configure in this way. 3. If individual settings are necessary for specific devices, these must be made online on the relevant device. Note that the configuration data is coded when it is saved. This means that you cannot edit the files with a text editor. Uploading and saving using TFTP Loading and saving data via a TFTP server On this page, you can configure the TFTP server and the file names. You can also store device data in an external file on your client PC or load such data from an external file from the PC to the devices. This means, for example, that you can also load new firmware from a file located on your client PC. Note Incompatibility with predecessor versions During the installation of a previous version, the configuration data can be lost. In this case, the device starts up with the factory settings after the firmware has been installed. Incompatibility with predecessor versions with inserted PLUG During the installation of a previous version, the configuration data can be lost. In this case, the device starts up with the factory settings after the firmware has been installed. In this situation, if a PLUG is inserted in the device, following the restart, this has the status "Not Accepted" since the PLUG still has the configuration data of the previous more up-to-date firmware. This allows you to return to the previous, more up-to-date firmware without any loss of configuration data. If the original configuration on the PLUG is no longer required, the PLUG can be deleted or rewritten manually on the "System > PLUG page. WinCC Basic V13.0 System Manual, 02/2014 765 Editing devices and networks 8.1 Configuring devices and networks Note Configuration files and Trial mode/Automatic Save In "Automatic Save" configuration mode, the data is saved automatically before the configuration files (ConfigPack and Config) are transferred. In the "Trial" configuration mode, although the changes are adopted, they are not saved in the configuration files (ConfigPack and Config). Use the "Write Startup Config" button on the "System > Configuration" WBM page to save changes in the configuration files. Settings TFTP Server IP Address Here, enter the IP address of the TFTP server with which you exchange data. TFTP Server Port Here, enter the port of the TFTP server via which data exchange will be handled. If necessary, you can change the default value 69 to your own requirements. The table has the following columns: File type Shows the file type. Description Shows the short description of the file type. File name Enter a file name. Select action (only available online) Select the action from the drop-down list. The selection depends on the selected file type, for example the log file can only be saved. The following actions are possible: - Save file With this selection, you save a file on the TFTP server. - Load file With this selection, you load a file from the TFTP server. Events Configuration On this page, you specify how the device reacts to events. 766 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Settings Signaling Contact Response Select the behavior of the signaling contact. The following reactions are possible: - conventional Default setting for the signaling contact. An error/fault is displayed by the fault LED and the signaling contact is opened. When the error/fault state no longer exists, the fault LED goes off and the signaling contact is closed. - User-defined The way the signaling contact works does not depend on the error/fault that has occurred. The signaling contact can be opened or closed as required by user actions. Signaling Contact Status Select the status of the signaling contact. The following statuses are possible: - close Signaling contact is closed. - open Signaling contact is opened. Table 1 has the following columns: 1st column Shows that the settings are valid for all ports of table 2. E-mail/Trap/Log table/Syslog/Errors Select the required setting. If "No Change" is selected, the entry in table 2 remains unchanged. Transfer to table If you click the button, the setting is adopted for all ports of table 2. Table 2 has the following columns: WinCC Basic V13.0 System Manual, 02/2014 767 Editing devices and networks 8.1 Configuring devices and networks Event The "Event" column contains the following values: - Cold/Warm Start The device was turned on or restarted by the user. - Link Change This event occurs only when the port status is monitored and has changed, see "System > Fault Monitoring > Link Change". - Authentication Failure This event occurs when attempting access with a bad password. - RMON Alarm An alarm or event has occurred relating to the remote monitoring of the system. - Power Supply Switchover This event occurs only when power supply lines 1 and 2 are monitored. It indicates that there was a change to line 1 or line 2, see System > Fault monitoring > Power supply". - RM status change The status of the redundancy manager has changed - Spanning Tree Topology Change The STP or RSTP or MSTP topology has changed. - Fault State Change The fault state has changed. The fault state can relate to the activated port monitoring, the response of the signaling contact or the power supply monitoring. - VRRP State Change (only with routing using VRRP) The status of the virtual router has changed - Loop Detection A loop was detected in the network segment. - OSPF State Change (only with routing using OSFP) The status of OSPF has changed E-mail The device sends an e-mail. This is only possible if the SMTP server is set up and the "SMTP client" function is enabled. Trap The device sends an SNMP trap. This is only possible if "SNMPv1 traps" is enabled in "System > Configuration". Log table The device writes an entry in the log table. Syslog The device writes an entry to the system log server. This is only possible if the system log server is set up and the "Syslog client" function is enabled. Fault The device triggers a fault. The error LED lights up Severity filter On this page, set the threshold levels for sending system event notifications. 768 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Settings The table has the following columns: Client Type Select the client type for which you want to make settings: - E-mail Sending system event messages by e-mail - Log table Entry of system events in the log table. - Syslog Entering system events in the Syslog file Severity Select the required level. The following settings are possible: - Info System events are processed as of the severity level "Info". - Warning System events are processed as of the severity level "Warning". - Critical System events are processed as of the severity level "Critical". SMTP client The device provides the option of automatically sending an e-mail if an alarm event occurs (for example to the network administrator). The e-mail contains the identification of the sending device, a description of the cause of the alarm in plain language, and a time stamp. This allows centralized network monitoring to be set up for networks with few nodes based on an E-mail system. When an e-mail event message is received, the WBM can be started by the browser using the identification of the sender to read out further diagnostics information. On this page, you can configure up to three SMTP servers and the corresponding e-mail addresses. Note Depending on the properties and configuration of the SMTP server, it may be necessary to adapt the "From" input box for the e-mails. Check with the administrator of the SMTP server. Settings SMTP Client Enable or disable the SMTP client. Email address of the sender Enter the name of the sender that will be included in the e-mail, for example the device name. WinCC Basic V13.0 System Manual, 02/2014 769 Editing devices and networks 8.1 Configuring devices and networks SMTP Port Change the port if the SMTP server is not obtainable via port 25. SMTP Server IP Address Enter the IP address of the SMTP server. This table contains the following columns: SMTP Server IP Address Shows the SMTP server IP address. Email address of the recipient Enter the e-mail address to which the device sends an e-mail if a fault occurs. The e-mail address can be the address of a single person or a distribution list. Syntax of email addresses The following conditions apply to e-mail addresses: Alphanumeric characters are permitted. The following special characters are permitted: - @ - _ (underscore) - - (hyphen) - . (period) A @ character must be included. Only one @ may be used. The characters "@" and the "." must not be the first or last character. DHCP client If the DHCP mode is activated, the DHCP client starts a DHCP request to a configured DHCP server and is assigned an IP address as the response. The server manages an address range from which it assigns IP addresses. It is also possible to configure the server so that the client always receives the same IP address in response to its request. 770 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Settings DHCP client configuration request (opt. 66, 67) Select this option if you want the DHCP client to use options 66 and 67 to download and then enable a configuration file. DHCP Mode Select the DHCP mode. The following modes are possible: - via MAC Address Identification is based on the MAC address. - via DHCP Client ID Identification is based on a freely defined DHCP client ID. - via System Name Identification is based on the device name. If the device name is 255 characters long, the last character is not used for identification. This table contains the following columns: Interface Shows the available interfaces. DHCP Enable or disable the DHCP client. SNMP General On this page, you make the basic settings for SNMP. Enable the functions you want to use. Settings SNMP Select the SNMP protocol. The following settings are possible: - "-" (disabled) SNMP is disabled. - SNMPv1/v2c/v3 SNMPv1/v2c/v3 is supported. - SNMPv3 Only SNMPv3 is supported. SNMPv1/v2 Read-Only If you enable this option, SNMPv1/v2c can only read the SNMP variables. Note Community String For security reasons, do not use the standard values "public" or "private". Change the community strings following the initial installation. WinCC Basic V13.0 System Manual, 02/2014 771 Editing devices and networks 8.1 Configuring devices and networks SNMPv1/v2c Read Community String Enter the community string for access of the SNMP protocol. SNMPv1/v2c Read/Write Community String Enter the community string for read and write access of the SNMP protocol. SNMPv1 Traps Enable or disable the sending of SNMP traps (alarm frames). On the "Trap" tab, specify the IP addresses of the devices to which SNMP traps will be sent. SNMPv1/v2c Trap Community String Enter the community string for sending SNMPv1/v2 messages. Traps If an alarm event occurs, a device can send SNMP traps (alarm frames) to up to ten different management stations at the same time. Traps are only sent if events specified in "Events > Configuration" occur. Note SNMP traps are sent only when the "SNMPv1 Traps" setting was selected in "SNMP > General". Settings IP Address Enter the IP address of the stations to which the device sends SNMP traps The table has the following columns: IP Address Shows the IP addresses of the stations to which the device sends SNMP traps. Trap Enable or disable the sending of SNMP traps. Stations that are entered but not selected do not receive SNMP traps. v3 Groups Security settings and assigning permissions SNMP version 3 allows permissions to be assigned, authentication, and encryption at protocol level. The security levels and read/write permissions are assigned according to groups. The settings automatically apply to every member of a group. 772 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Settings Group Name Enter the name of the group. This name must have at least two characters, the maximum length is 32 characters. Security Level Select the security level (authentication, encryption) valid for the selected group. You have the following options for the security levels: - no Auth/no Priv No authentication enabled / no encryption enabled. - Auth/no Priv Authentication enabled / no encryption enabled. - Auth/Priv Authentication enabled / encryption enabled. The table has the following columns: Group Name Shows the defined group names. Note Once a group name and the security level have been specified, they can no longer be modified after the group is created. If you want to change the group name or the security level , you will need to delete the group and recreate it and reconfigure it with the new name. Security Level Shows the configured security level. Read Enable or disable read access. Write Enable or disable write access. Persistence Shows whether or not the group is assigned to an SNMPv3 user. If the group is not assigned to an SNMPv3 user, no automatic saving is triggered and the configured group disappears again after restarting the device. - Yes The group is assigned to an SNMPV3 user. - No The group is not assigned to an SNMPV3 user. v3 users User-specific security settings On the WBM page, you can create new SNMPv3 users and modify or delete existing users. The user-based security model works with the concept of the user name; in other words, a WinCC Basic V13.0 System Manual, 02/2014 773 Editing devices and networks 8.1 Configuring devices and networks user ID is added to every frame. This user name and the applicable security settings are checked by both the sender and recipient. Settings User name Enter a freely selectable user name. After you have entered the data, you can no longer modify the name. The table has the following columns: User name Shows the created users. Group Name Select the group to which the user will be assigned. Authentication Protocol Select the authentication protocol. Can only be enabled, if this group supports the function. The following settings are available: - None - MD5 - SHA Encryption Protocol Specify whether or not the user uses the DES algorithm. Can only be enabled, if the group supports this function. Authentication Password Enter the authentication password in the first input box. Confirm authentication password Confirm the password by repeating the entry. Encryption Password Enter your encryption password. Confirm Encryption Password Confirm the encryption password by repeating the entry. Persistence Shows whether or not the user is assigned to an SNMPv3 group. If the user is not assigned to an SNMPv3 group, no automatic saving is triggered and the configured user disappears again after restarting the device. - Yes The user is assigned to an SNMPv3 group. - No The user is not assigned to an SNMPv3 group. 774 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks System time Manual time setting On this page, you set the date and time of the system. For this setting to be used, enable "Manual time setting". Note The page is only available if there is an online connection to the device. Settings Time Manually Enable or disable the manual time setting. System Time Enter the date and time in the format "MM/DD/YYYY HH:MM:SS". Can only be edited, if manual time setting is enabled. After a restart, the time of day begins at 01/01/2000 00:00:00 Use PC Time Click the button to use the time setting of the PC. Last Synchronization Time This box is read-only and shows when the last time-of-day synchronization took place. If no time-of-day synchronization was possible, the box displays "Date/time not set". Last Synchronization Mechanism This box displays how the last time-of-day synchronization was performed. - Not set The time was not set. - Manual Manual time setting - SNTP Automatic time-of-day synchronization using SNTP - NTP Automatic time-of-day synchronization using NTP - SIMATIC Automatic time-of-day synchronization using the SIMATIC time frame. - PTP Automatic time-of-day synchronization with PTP DST overview On this page, you can create new entries for the daylight saving time changeover. The table provides an overview of the existing entries. WinCC Basic V13.0 System Manual, 02/2014 775 Editing devices and networks 8.1 Configuring devices and networks Settings DST No. Shows the number of the entry. If you create a new entry, a new line with a unique number is created. Name Shows the name of the entry. Year Shows the year for which the entry was created. Start Date Shows the month, day and time for the start of daylight saving time. End Date Shows the month, day and time for the end of daylight saving time. Type Shows how the daylight saving time changeover is made: - Date A fixed date is entered for the daylight saving time changeover. - Recurring A rule was defined for the daylight saving time changeover. DST configuration On this page, you can configure the entries for the daylight saving time changeover. As result of the changeover to daylight saving or standard time, the system time for the local time zone is correctly set. You can define a rule for the daylight saving time changeover or specify a fixed date. Settings Note The content of this page depends on the selection in the "Type" box. The boxes "DST No.", "Type" and "Name" are always shown. 776 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks DST No. Select the type of the entry. Type Select how the daylight saving time changeover is made: - Date You can set a fixed date for the daylight saving time changeover. This setting is suitable for regions in which the daylight saving time changeover is not governed by rules. - Recurring You can define a rule for the daylight saving time changeover. This setting is suitable for regions in which the daylight saving time always begins or ends on a certain weekday. Name Enter a name for the entry. Settings with "Date" selected You can set a fixed date for the start and end of daylight saving time. Year Enter the year for the daylight saving time changeover. Start Date Enter the following values for the start of daylight saving time: - Day - Hour - Month End Date Enter the following values for the end of daylight saving time: - Day - Hour - Month Settings with "Recurring" selected You can create a rule for the daylight saving time changeover. WinCC Basic V13.0 System Manual, 02/2014 777 Editing devices and networks 8.1 Configuring devices and networks Start Date Enter the following values for the start of daylight saving time: - Hour - Month - Week You can select the 1st to 5th or the last week of the month. - Weekday End Date Enter the following values for the end of daylight saving time: - Hour - Month - Week You can select the 1st to 5th or the last week of the month. - Weekday SNTP client SNTP (Simple Network Time Protocol) is used for synchronizing the time in the network. The appropriate frames are sent by an SNTP server in the network. Settings SNTP Client Enable or disable automatic time-of-day synchronization using SNTP. Current System Time (only available online) Shows the values currently set in the system for date and time. Last Synchronization Time (only available online) This box is read-only and shows when the last time-of-day synchronization took place. If no time-of-day synchronization was possible, the box displays "Date/time not set". 778 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Last Synchronization Mechanism (only available online) This box displays how the last time-of-day synchronization was performed. - Not set The time was not set. - Manual Manual time setting - SNTP Automatic time-of-day synchronization using SNTP - NTP Automatic time-of-day synchronization using NTP - SIMATIC Automatic time-of-day synchronization using the SIMATIC time frame - PTP Automatic time-of-day synchronization with PTP Time Zone Enter the time zone you are using in the format "+/- HH:MM". The time zone relates to UTC standard world time. Settings for daylight-saving and standard time are taken into account in this box by specifying the time offset. SNTP Mode Select the synchronization mode. The following types of synchronization are possible: - Poll If you select this protocol type, the input boxes "SNTP Server IP Address", "SNTP Server Port" and "Poll Interval" are displayed for further configuration. With this type of synchronization, the device is active and sends a time query to the SNTP server. - Listen With this type of synchronization, the device is passive and "listens" for SNTP frames that deliver the time of day. SNTP Server IP Address Enter the IP address of the SNTP server. SNTP Server Port Enter the port of the SNTP server. Poll Interval [s] Enter the interval in seconds between two time polls. NTP client If you require time-of-day synchronization using NTP, you can make the relevant settings here. Settings NTP Client Enable or disable automatic time-of-day synchronization using NTP. Current System Time (only available online) Shows the values currently set in the system for date and time. WinCC Basic V13.0 System Manual, 02/2014 779 Editing devices and networks 8.1 Configuring devices and networks Last Synchronization Time (only available online) This box is read-only and shows when the last time-of-day synchronization took place. If no time-of-day synchronization was possible, the box displays "Date/time not set". Last Synchronization Mechanism (only available online) This box displays how the last time-of-day synchronization was performed. - Not set The time was not set. - Manual Manual time setting - SNTP Automatic time-of-day synchronization using SNTP - NTP Automatic time-of-day synchronization using NTP - SIMATIC Automatic time-of-day synchronization using the SIMATIC time frame - PTP Automatic time-of-day synchronization with PTP Time Zone Enter the time zone you are using in the format "+/- HH:MM". The time zone relates to UTC standard world time. Settings for daylight-saving and standard time are taken into account in this box by specifying the time offset. NTP Server IP Address Enter the IP address of the NTP server. NTP Server Port Enter the port of the NTP server. Poll Interval [s] Enter the interval in seconds between two time polls. SIMATIC Time Client On this page, you configure time synchronization with the SIMATIC Time Client. Settings SIMATIC Time Client Enable or disable loop the SIMATIC Time Client. Current System Time (only available online) Shows the values currently set in the system for date and time. 780 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Last Synchronization Time (only available online) This box is read-only and shows when the last time-of-day synchronization took place. If no time-of-day synchronization was possible, the box displays "Date/time not set". Last Synchronization Mechanism (only available online) This box displays how the last time-of-day synchronization was performed. - Not set The time was not set. - Manual Manual time setting - SNTP Automatic time-of-day synchronization using SNTP - NTP Automatic time-of-day synchronization using NTP - SIMATIC Automatic time-of-day synchronization using the SIMATIC time frame - PTP Automatic time-of-day synchronization with PTP PTP Client On this page, you configure time synchronization with PTP (Precision Time Protocol). This function is only available for SCALANCE X500. Settings PTP Client Enable or disable time synchronization using PTP. You can configure other settings in "Layer 2 > PTP". Current System Time (only available online) This box is read-only and displays the current system time. Last Synchronization Time (only available online) This box is read-only and shows when the last time-of-day synchronization took place. If no time-of-day synchronization was possible, the box displays "Date/time not set". WinCC Basic V13.0 System Manual, 02/2014 781 Editing devices and networks 8.1 Configuring devices and networks Last Synchronization Mechanism (only available online) This box displays how the last time-of-day synchronization was performed. - Not set The time was not set. - Manual Manual time setting - SNTP Automatic time-of-day synchronization using SNTP - NTP Automatic time-of-day synchronization using NTP - SIMATIC Automatic time-of-day synchronization using the SIMATIC time frame - PTP Automatic time-of-day synchronization with PTP Time Zone Enter the time zone you are using in the format "+/- HH:MM". The time zone relates to UTC standard world time. Auto logout On this page, set the times after which there is an automatic logout from WBM or the CLI following user in activity. Note No automatic logout from the CLI If the connection is not terminated after the set time, check the setting of the "keepalive" mechanism on the Telnet client. If the interval is shorter than the configured time, the connection is kept alive although no user data is transferred. Example: you selected 300 seconds for the automatic logout and 120 seconds is set for the keepalive function. In this case, a packet is sent every 120 seconds that keeps the connection up. Disable the keepalive mechanism (interval time = 0) or Set the interval high enough so that the underlying connection is terminated when there is inactivity. Settings Web Based Management [s] Enter the time in seconds for the automatic logout from WBM. If you enter the value 0, the automatic logout is disabled. CLI (TELNET, SSH, Serial) [s] Enter the time in seconds for the automatic logout from the CLI. If you enter the value 0, the automatic logout is disabled. 782 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Button The "Select/Set" button has the following functions: Change display mode Enable redundancy manager Restore to factory defaults Fault mask and LED display You will find a detailed description of the individual functions available with the buttons in the operating instructions of the specific device. Settings Restore Factory Defaults Enables or disables the "Restore Factory Defaults" function for the Select/Set button. CAUTION Button function "Restore Factory Defaults" active during startup If you have disabled this function in your configuration, disabling is only valid during operation. When restarting, for example after power down, the function is active until the configuration is loaded so that the device can inadvertently be reset to the factory settings. This may cause unwanted disruption in network operation since the device needs to be reconfigured if this occurs. An inserted PLUG is also deleted and returned to the status as shipped Redundancy Manager Enables or disables the redundancy manager function for the Select/Set button. Set Fault Mask Enable or disable the function "Define fault mask via the LED display" with the Select/set button. This function only works in display mode D. Syslog client Syslog according to RFC 3164 is used for transferring short, unencrypted text messages over UDP in the IP network. This requires a system log server. Requirements for sending log entries: The system log function is enabled on the device. The system log function is enabled for the relevant event. There is a system log server in your network that receives the log entries. Since this is a UDP connection, there is no acknowledgment to the sender. The IP address of the system log server is entered on the device. WinCC Basic V13.0 System Manual, 02/2014 783 Editing devices and networks 8.1 Configuring devices and networks Settings Syslog Client Enable or disable the system log function. Syslog Server IP Address Enter the IP address of the system log server. This table contains the following columns Syslog Server IP Address Shows the IP address of the system log server. Server Port Enter the port of the Syslog server being used. Ports Port overview The page shows the configuration for the data transfer for all ports of the device. Settings Port Shows the configurable ports. Port name Shows the name of the port. MAC Address (only available online) Shows the MAC address of the port. Mode (only available online) Shows the transfer parameters of the port Negotiation Shows whether the automatic configuration is enabled or disabled. Flow Ctrl. Type Shows whether flow control is enabled or disabled for the port. Flow Ctrl. Shows whether or not flow control is working on this port. MTU Shows the maximum packet size. Port Type (only with routing) Shows the type of the port. The following types are possible: - Router Port - Switch Port VLAN Hybrid - Switch-Port VLAN Trunk Status Shows whether the port is on or off. Data traffic is possible only over an enabled port. 784 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Combo Port Media Type(SCALANCE XM400 only) Shows the mode of the combo port: - auto - rj45 - sfp Link (only available online) Shows the connection status to the network. With the connection status, the following is possible: - Up The port has a valid link to the network, a link integrity signal is being received. - Down The link is down, for example because the connected device is turned off. Configuration On this page, you configure the ports of the device Settings Port Select the port to be configured. The port is made up of the port number and the slot number, for example port 0.1 is slot 0, port 1. Status Specify whether the port is enabled or disabled. - enabled The port is enabled. Data traffic is possible only over an enabled port. - disabled The port is disabled but the connection remains. - Link down The port is disabled and the connection to the partner device is terminated. Port name Enter a name for the port. MAC Address (only available online) Shows the MAC address of the port. Mode Type Shows the transmission speed and the transmission method of the port. You make the settings for "Autonegotiation" and "Transmission rate" in the port options. Note Before the port and partner port can communicate with each other, the settings must match at both ends. Mode (only available online) Shows which transmission speed and which transmission mode is currently being used. WinCC Basic V13.0 System Manual, 02/2014 785 Editing devices and networks 8.1 Configuring devices and networks Negotiation Shows whether the automatic configuration of the connection to the partner port is enabled or disabled. Flow Ctrl. Type Shows whether or not flow control is working on this port. Note Turning flow control on/off with autonegotiation Flow control can only be enabled or disabled if the "autonegotiation" function is turned off. The function cannot enabled again afterwards. Flow Ctrl. Shows whether or not flow control is working on this port. MTU Enter the packet size. Port Type (only with routing) Select the type of the port: - Router Port The port is an IP interface. It does not support layer 2 functions. - Switch Port VLAN Hybrid The port sends tagged and untagged frames. It is not automatically a member of a VLAN. - Switch-Port VLAN Trunk The port only sends tagged frames and is automatically a member of all VLANs. Combo Port Media Type(SCALANCE XM400 only) Specify the mode for the combo port: - auto If you select this mode, the SFP transceiver port has priority. As soon as an SFP transceiver is plugged in, an existing connection at the fixed RJ-45 port is terminated. If no SFC transceiver is plugged in, a connection can be established via the fixed RJ-45 port. - rj45 If you select this mode, the fixed RJ-45 port is used regardless of the SFP transceiver port. - sfp If you select this mode, the SFP transceiver port is used regardless of the built-in RJ-45 port. The factory setting is auto mode. Link (only available online) Shows the connection status to the network. With the connection status, the following is possible: - Up The port has a valid link to the network, a link integrity signal is being received. - Down The link is down, for example because the connected device is turned off. 786 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Changing the port configuration Note Optical ports only work with the full duplex mode and at maximum transmission rate. As a result, the following settings cannot be made for optical ports: Automatic configuration Transmission speed Transmission technique Note With various automatic functions, the device prevents or reduces the effect on other ports and priority classes (Class of Service) if a port is overloaded. This can mean that frames are discarded even when flow control is enabled. Port overload occurs when the device receives more frames than it can send, for example as the result of different transmission speeds. Fault monitoring Power supply Configure whether or not the power supply should be monitored by the messaging system. Depending on the hardware variant, there are one or two power connectors (Supply 1 / Supply 2). With a redundant power supply, configure the monitoring separately for each individual feed-in line. If there is no power on one of the monitored lines (Supply 1 or Supply 2) or when the voltage is too low, a fault is signaled by the signaling system. Note You will find the permitted operating voltage limits in the compact operating instructions of the device. An error causes the fault LED to light up on the device. Depending on the configuration, the error may trigger a trap, an e-mail or an entry in the event log table. Settings Line 1 Enable or disable the monitoring of power connector 1. Line 2 Enable or disable the monitoring of power connector 2. WinCC Basic V13.0 System Manual, 02/2014 787 Editing devices and networks 8.1 Configuring devices and networks Link Change On this page, you configure whether or not an error message is triggered if there is a status change on a network connection. If connection monitoring is enabled, an error is signaled when there should be a link on a port and this is missing. or when there should not be a link on a port and a link is detected. An error causes the signaling contact to trigger and the fault LED to light up on the device. Depending on the configuration, the error may trigger a trap, an e-mail or an entry in the event log table. Settings Table 1 has the following columns: 1st column Shows that the settings are valid for all ports. Setting Select the required setting. If "No Change" is selected, the entry in table 2 remains unchanged. Transfer to table If you click the button, the setting is adopted for all ports of table 2. Table 2 has the following columns Port Shows the available ports. Setting Select the setting. You have the following options: - Up Error handling is triggered when the port changes to the active status. (From "Link down" to "Link up") - Down Error handling is triggered when the port changes to the inactive status. (From "Link up" to "Link down") - "-" (disabled) The error handling is not triggered. Redundancy On this page, you configure whether or not an error message is triggered if there is a status change on a network connection. 788 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Setting Redundancy loss (HRP only) Enable or disable connection monitoring. If the redundancy of the connection is lost, an error is signaled. PNIO On this page, you configure the device response to PROFINET input and output. Description The page contains the following boxes: PNIO runtime mode Shows the status of the PNIO operation. PNIO runtime mode for next startup Select the runtime mode that will be active the next time the device starts up. PNIO AR status This box shows the PROFINET IO application relation status; in other words, whether or not the IE switch is connected "online" or "offline" with a PROFINET controller. In this context, online means that a connection to a PROFINET IO controller exists, that the controller has downloaded its configuration data to the IE switch and that the device can send status data to the PROFINET IO controller. In this status known as "in data exchange", the parameters set with the PROFINET IO controller cannot be configured on the IE switch. PNIO Device Name Enter the PROFINET IO device name. Allow PNIO Data Exchange Enable or disable PNIO data exchange Simulate PNIO Data Exchange Enable or disable the simulation of PNIO data exchange. PLUG PLUG configuration Note The page is only available if there is an online connection to the device. WinCC Basic V13.0 System Manual, 02/2014 789 Editing devices and networks 8.1 Configuring devices and networks NOTICE Do not remove or insert a C-PLUG / KEY-PLUG during operation! A PLUG may only be removed or inserted when the device is turned off. The device checks whether or not a PLUG is present at one second intervals. If it is detected that the PLUG was removed, there is a restart. If a valid KEY-PLUG was inserted in the device, the device changes to a defined error state following the restart. Information about the configuration of the C-PLUG / KEY-PLUG This page provides detailed information about the configuration stored on the C-PLUG or KEYPLUG. It is also possible to reset the PLUG to "factory defaults" or to load it with new contents. Note The action is only executed after you click the "Set Values" button. The action cannot be undone. If you decide against executing the function after making your selection, click the "Refresh" button. As a result the data of this page is read from the device again and the selection is canceled. Note Incompatibility with previous versions with PLUG inserted During the installation of a previous version, the configuration data can be lost. In this case, the device starts up with the factory settings after the firmware has been installed. In this situation, if a PLUG is inserted in the device, following the restart, this has the status "NOT ACCEPTED" since the PLUG still has the configuration data of the previous more up-to-date firmware. This allows you to return to the previous, more up-to-date firmware without any loss of configuration data. If the original configuration on the PLUG is no longer required, the PLUG can be deleted or rewritten manually using "System > PLUG". 790 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Settings The table has the following rows: Status Shows the status of the PLUG. The following are possible: - ACCEPTED There is a PLUG with a valid and suitable configuration in the device. - NOT ACCEPTED Invalid or incompatible configuration on the inserted PLUG. - NOT PRESENT There is no C-PLUG or KEY-PLUG inserted in the device. - FACTORY PLUG is inserted and does not contain a configuration. This status is also displayed when the PLUG was formatted during operation. - MISSING There is no PLUG inserted. Functions are configured on the device for which a license is required. Device Family Shows the SIMATIC NET product line that used the C-PLUG or KEY-PLUG previously. Device Type Shows the device type within the product line that used the C-PLUG or KEY-PLUG previously. Configuration Revision The version of the configuration structure. This information relates to the configuration options supported by the device and has nothing to do with the concrete hardware configuration. This revision information does not therefore change if you add or remove additional components (modules or extenders), it can, however, change if you update the firmware. File System Displays the type of file system on the PLUG. NOTICE New file system UBI As of firmware version 3.0, UBI is the standard file system for the C-PLUG or KEY-PLUG. If a C-PLUG with the previous file system IECP is detected in such a device, this C-PLUG will be formatted for the UBI file system and the data will be rewritten to the C-PLUG. The file system is also changed following a firmware update to V3.0. A downgrade to the previous version of the corresponding software is then a problem. The firmware can neither read nor write the C-PLUG or KEY-PLUG and it is not even possible to "Erase PLUG to factory default". File System Size [bytes] Shows the maximum storage capacity of the file system on the C-PLUG. File System Usage Displays the storage space in use in the file system of the C-PLUG. WinCC Basic V13.0 System Manual, 02/2014 791 Editing devices and networks 8.1 Configuring devices and networks Info String Shows additional information about the device that used the PLUG previously, for example, order number, type designation, and the versions of the hardware and software. The displayed software version corresponds to the version in which the configuration was last changed. With the "NOT ACCEPTED" status, further information on the cause of the problem is displayed. Modify PLUG Select the required setting. - Write current configuration to PLUG This option is available only if the status of the PLUG is "NOT ACCEPTED" or FACTORY. The configuration in the internal flash memory of the device is copied to the PLUG. - Erase PLUG to factory default Deletes all data from the C-PLUG and triggers low-level formatting. PLUG license Note The page is only available if there is an online connection to the device. NOTICE Do not remove or insert a C-PLUG / KEY-PLUG during operation! A PLUG may only be removed or inserted when the device is turned off. The device checks whether or not a PLUG is present at one second intervals. If it is detected that the PLUG was removed, there is a restart. If a valid KEY-PLUG was inserted in the device, the device changes to a defined error state following the restart. If the device was configured at some time with a PLUG, the device can no longer be used without this PLUG. To be able to use the device again, reset the device to the factory settings. Note Incompatibility with previous versions with PLUG inserted During the installation of a previous version, the configuration data can be lost. In this case, the device starts up with the factory settings after the firmware has been installed. In this situation, if a PLUG is inserted in the device, following the restart, this has the status "NOT ACCEPTED" since the PLUG still has the configuration data of the previous more up-to-date firmware. This allows you to return to the previous, more up-to-date firmware without any loss of configuration data. If the original configuration on the PLUG is no longer required, the PLUG can be deleted or rewritten manually using "System > PLUG". Information about the license of the KEY-PLUG A C-PLUG can only store the configuration of a device. In addition to the configuration, a KEYPLUG also contains a license that enables certain functions of your SIMATIC NET device. 792 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks This page provides detailed information about the license on the KEY-PLUG. In this example, the KEY-PLUG contains the data for enabling the layer 3 functions of the device. Displayed values Status Shows the status of the KEY-PLUG. The following are possible: - ACCEPTED The KEY-PLUG in the device contains a suitable and valid license. - NOT ACCEPTED The license of the inserted KEY-PLUG is not valid. - NOT PRESENT No KEY-PLUG is inserted in the device. - MISSING There is no KEY-PLUG or a C-PLUG with the status "FACTORY" inserted in the device. Functions are configured on the device for which a license is required. - WRONG The inserted KEY-PLUG is not suitable for the device. - UNKNOWN Unknown content of the KEY-PLUG. - DEFECTIVE The content of the KEY-PLUG contains errors. Order ID Shows the order number of the KEY-PLUG. The KEY-PLUG is available for various functional enhancements and for various target systems. Serial Number Shows the serial number of the KEY-PLUG. Info String Shows additional information about the device that used the KEY-PLUG previously, for example, order number, type designation, and the versions of the hardware and software. The displayed software version corresponds to the version in which the configuration was last changed. With the "NOT ACCEPTED" status, further information on the cause of the problem is displayed. Note When you save the configuration, the information about whether or not a KEY-PLUG was inserted in the device at the time is also saved. This configuration can then only work if a KEY-PLUG with the same order number / license is inserted. WinCC Basic V13.0 System Manual, 02/2014 793 Editing devices and networks 8.1 Configuring devices and networks Ping Reachability of an address in an IP network Note The page is only available if there is an online connection to the device. With the ping function, you can check whether a certain IP address is reachable in the network. Settings The table has the following columns: IP Address Enter the IP address of the device. Repeat Enter the number of ping requests. Ping Click this button to start the ping function. Ping Output This box shows the output of the ping function. PoE General On this page, you specify the maximum power for the power sourcing equipment (PSE). PSE (power sourcing equipment) The SCALANCE X-500 represents a PSE (Power Sourcing Equipment). With a SCALANCE XM400, you can use the "Power over Ethernet" function via the port extender PE408PoE. Each group of four ports with PoE capability is known as a PSE. The numbering of the PSEs is fixed and does not change with the number of plugged-in PoE port extenders or the slot. A maximum of 4 PSEs are possible. Setting PSE Shows the number of the PoE power supply. Maximum Power Maximum power that a PSE provides to supply PoE devices. Allocated Power Sum of the power reserved by the PoE devices according to the "Classification". 794 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Used power Sum of the power used by the end devices. Usage Threshold [%] When the power being used by the end devices exceeds the percentage shown here, an event is triggered. Port Settings for the ports For each individual PoE port, you can specify whether or not the power will be supplied via Ethernet. You can also set a priority for each connected powered device (PD). Devices for which a high priority was set, take preference over other devices for the power supply. Settings The table has the following columns: Port Shows the configurable PoE ports. The port is made up of the port number and the slot number, for example port 0.1 is slot 0, port 1. Setting Enable the PoE power supply for this port or interrupt it. Priority Select which priority this port will have for the power supply. The following settings are possible, in ascending order of relevance: - low low priority - high medium priority - critical high priority If the same priority is set for two ports, the port with the lower port number will be preferred when necessary. Type Here, you can enter a string to describe the connected device in greater detail. Classification The classification specifies the class of the device. From this, it is possible to recognize the maximum power of the device. WinCC Basic V13.0 System Manual, 02/2014 795 Editing devices and networks 8.1 Configuring devices and networks Status Shows the current status of the port. The following states are possible: - disabled The PoE power supply is deactivated for this port. - delivering The PoE power supply is activated for this port and a device is connected. - searching The PoE power supply is activated for this port but there is no device connected. Note If a device is connected to a port with PoE capability, a check is made to determine whether the power of the port is adequate for the connected device. If the power of the port is inadequate, although PoE is enabled in "Setting", the port nevertheless has the status "disabled". This means that the port was disabled by the PoE power management. Power [mW] Shows the power that the SCALANCE provides at this port. Voltage [V] Shows the voltage applied to this port. Current [mA] Shows the current with which a device connected to this port is supplied. Port diagnostics Cable tester Note The page is only available if there is an online connection to the device. With this page, each individual Ethernet port can run independent fault diagnostics on the cable. This test is performed without needing to remove the cable, connect a cable tester and install a loopback module at the other end. Short-circuits and cable breaks can be localized to within a few meters. Note Please note that this test is permitted only when no data connection is established on the port to be tested. 796 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Settings Port Select the required port from the drop-down list. Run Test Activates error diagnostics. The result is shown in the table. This table contains the following columns: Pair Shows the wire pair in the cable. Note Wire pairs Wire pairs 4-5 and 7-8 of 10/100 Mbps network cables are not used. In 1000 Mbps or gigabit Ethernet, all 4 wire pairs are used. The wire pair assignment - pin assignment is as follows (DIN 50173): Pair 1 = pin 4-5 Pair 2 = pin 1-2 Pair 3 = pin 3-6 Pair 4 = pin 7-8 Status Displays the status of the cable. Distance [m] Displays the distance to the cable end, cable break, or short-circuit. SFP diagnostics On this page, you run independent error diagnostics for each individual SFP port. This test is performed without needing to remove the cable, connect a cable tester or install a loopback module at the other end. Note Please note that this test is permitted only when no data connection is established on the port to be tested. If, however, there is a data connection to the port to be tested, this is briefly interrupted. Automatic re-establishment of the connection can fail and then needs to be done manually. WinCC Basic V13.0 System Manual, 02/2014 797 Editing devices and networks 8.1 Configuring devices and networks Description The page contains the following boxes: Port Select the required port from the drop-down list. The values are shown in the following boxes: Name Shows the name of the interface. Model Shows the type of interface. Revision Shows the hardware version of the SFP. Serial Shows the serial number of the SFP. Nominal Bit Rate [Mbps] Shows the nominal bit rate of the interface. Max. Link (50.0/125um) [m] Shows the maximum distance in meters that is possible with this medium. Max. Link (62.5/125um) [m] Shows the maximum distance in meters that is possible with this medium. The following table shows the values of the SFP transceiver used in this port: Temperature [C] Shows the temperature of the interface. Voltage [V] Shows the voltage applied to the interface [V]. Current [mA] Shows the current consumption of the interface [mA]. RX Power [mW] Shows the receive power of the interface [mW]. Tx Power [mW] Shows the transmit power of the interface [mW]. Current Shows the current value. Low Shows the lowest value. High Shows the highest value. 798 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Layer 2 Configuration The functions of layer 2 are configured on this page. With some functions, there are further configuration pages on which more detailed settings can be made. You can also check the settings on the configuration pages. Settings Protocol Based VLAN Enable or disable protocol-based VLAN. You can configure other settings in "Layer 2 > VLAN". Subnet Based VLAN Enable or disable subnet-based VLAN. You can configure other settings in "Layer 2 > VLAN". Dynamic MAC Aging Enable or disable the "Aging" mechanism. You can configure other settings in "Layer 2 > Dynamic MAC Aging". Redundancy Type The following settings are available: - "-" (disabled) The redundancy function is disabled. - Ring Enables ring redundancy. You can configure other settings in "Layer 2 > Ring Redundancy > Ring". - Spanning Tree If you select this option, you specify the required redundancy mode in "Redundancy Mode". WinCC Basic V13.0 System Manual, 02/2014 799 Editing devices and networks 8.1 Configuring devices and networks Redundancy Mode If you select "Spanning Tree" for the "Redundancy Type", the following options are then available: - STP Enables the Spanning Tree Protocol (STP). Typical reconfiguration times with spanning tree are between 20 and 30 seconds. You can configure other settings in "Layer 2 > Spanning Tree". - RSTP Enables the Rapid Spanning Tree Protocol (RSTP). If a spanning tree frame is detected at a port, this port reverts from RSTP to spanning tree. You can configure other settings in "Layer 2 > Spanning Tree". Note When using RSTP (Rapid Spanning Tree Protocol), loops involving duplication of frames or frames being overtaken may occur briefly. If this is not acceptable in your particular application, use the slower standard spanning tree mechanism. - MSTP Enables the Multiple Spanning Tree Protocol (MSTP). You can configure other settings in "Layer 2 > Spanning Tree". If you select "Ring" for the "Redundancy Type", the following options are then available: - Automatic Redundancy Detection Select this setting to create an automatic configuration of the redundancy mode. In this mode, the device automatically detects whether or not there is a device with the "HRP Manager" role in the ring. If this is the case, the device adopts the role of "HRP Client". If no HRP manager is found, all devices with the "Automatic Redundancy Detection" or "MRP Auto Manager" setting negotiate among themselves to establish which device adopts the role of "MRP Manager". The device with the lowest MAC address will always become "MRP Manager". The other devices automatically set themselves to redundancy type "MRP Client". - MRP Auto-Manager Automatic media redundancy manager - MRP Client Media redundancy client - HRP Client High Speed Redundancy Protocol client - HRP Manager High Speed Redundancy Protocol manager Standby Enable or disable the "Standby redundancy" function. You can configure other settings in "Layer 2 > Ring Redundancy > Standby". Passive Listening Enable or disable the "passive listening" function. 800 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks RMON If you select this check box, Remote Monitoring (RMON) allows diagnostics data to be collected on the device, prepared and read out using SNMP by a network management station that also supports RMON. This diagnostic data, for example port-related load trends, allow problems in the network to be detected early and eliminated. Dynamic Multicast The following settings are possible: - "-" (disabled) - IGMP Snooping Enables IGMP (Internet Group Management Protocol). You can configure other settings in "Layer 2 > Multicast > IGMP". - GMRP Enables GMRP (GARP Multicast Registration Protocol). You can configure other settings in "Layer 2 > Multicast > GMRP". Note GMRP and IGMP cannot operate at the same time. GVRP Enable or disable "GVRP" (GARP VLAN Registration Protocol). You can configure other settings in "Layer 2 > VLAN > GVRP". Mirroring Enable or disable port mirroring. You can configure other settings in "Layer 2 > Mirroring > Port". Loop Detection Enable or disable loop detection. You can configure other settings in "Layer 2 > Loop Detection". PTP Specify how the device will process PTP messages. You can configure other settings in "Layer 2 > PTP". - Off The device does not process any PTP messages. PTP messages are, however, forwarded according to the rules of the switch. - transparent The device adopts the function of a transparent clock and forwards PTP messages to other nodes while at the same time making entries in the correction field of the PTP message. QoS CoS map On this page, CoS priorities are assigned to certain queues (traffic queues). WinCC Basic V13.0 System Manual, 02/2014 801 Editing devices and networks 8.1 Configuring devices and networks Settings CoS Shows the CoS priority of the incoming packets. Queue Select the forwarding queue (send priority) that is assigned the CoS priority. The higher the number of the queue, the higher the send priority. DSCP map On this page, DSCP settings are assigned to various queues (traffic queues). Settings DSCP Shows the DSCP priority of the incoming packets. Queue Select the forwarding queue (send priority) that is assigned the DSCP value. The higher the queue number, the higher the send priority. Load limitation Limiting the transfer rate of incoming and outgoing data On this page, you configure the load limitation (maximum number of data packets per second) for the individual ports. You can specify the category of frame for which these limit values will apply. Settings Table 1 has the following columns: 1st column Shows that the settings are valid for all ports. Limit Ingress Unicast (DLF) / Limit Ingress Broadcast / Limit Ingress Multicast Select the required setting. - enabled: Enables the function. - disabled: Disables the function - No Change: The setting in table 2 remains unchanged Total Ingress Rate [pkts/s] Specify the maximum number of incoming packets processed by the device. If "No Change" is entered, the entry in table 2 remains unchanged. 802 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Egress Rate [Kb/s] Specify the data rate for all outgoing frames. If "No Change" is entered, the entry in table 2 remains unchanged Transfer to table If you click the button, the settings are adopted for all ports of table 2. Table 2 has the following columns: Port Shows the port to which the settings relate. Limit Ingress Unicast (DLF) Enable or disable the data rate for limiting incoming unicast frames with an unresolvable address (Destination lookup failure). Limit Ingress Broadcast Enable or disable the data rate for limiting incoming broadcast frames. Limit Ingress Multicast Enable or disable the data rate for limiting incoming multicast frames. Total Ingress Rate [pkts/s] Specify the maximum number of incoming packets processed by the device. Egress Rate [Kb/s] Specify the data rate for all outgoing frames. Note Rounding of the values, deviation from desired value When you enter the values for transmission rates, note that the WBM rounds to correct values. If values are configured for total ingress transmission rate and egress transmission rate, the actual values in operation can exceed or fall below the set values by 10%. VLAN General On this page, you define the VLAN and specify the use of the ports. Note Changing the "Agent VLAN ID" If the configuration PC is connected directly to the device via Ethernet and you change the "agent VLAN ID", the device is no longer reachable via Ethernet following the change. WinCC Basic V13.0 System Manual, 02/2014 803 Editing devices and networks 8.1 Configuring devices and networks Important rules for VLANs Make sure you keep to the following rules when configuring and operating your VLANs: Frames with the VLAN ID "0" are handled as untagged frames but retain their priority value. As default, all ports on the device send frames without a VLAN tag to ensure that the end node can receive these frames. With SCALANCE X devices, the VLAN ID "1" is the default on all ports. If an end node is connected to a port, outgoing frames should be sent without a tag (static access port). If, however, there is a further switch at this port, the frame should have a tag added (trunk port). With a trunk port, the VLAN assignment is dynamic. Static configurations can only be created if, in addition to the trunk port property, the port is also entered statically as a member in the VLANs involved. An example of a static configuration is the assignment of the multicast groups in certain VLANs. Settings VLAN ID Enter the VLAN ID. The table has the following columns: VLAN ID Shows the VLAN ID. The VLAN ID is assigned once when you create a new data record and can then no longer be changed. To make a change, the entire data record must be deleted and created again. Name Enter a name for the VLAN. The name only provides information and has no effect on the configuration. The VLAN name can be a maximum of 32 characters long. 804 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Status Shows the status of the entry. Here, static means that the address was entered as a static address by the user. The entry GVRP means that the configuration was registered by a GVRP frame. This is, however, only possible if GVRP was enabled for the device. List of ports Specify the use of the port. The following options are available: - "-" - The port is not a member of the specified VLAN. With a new definition, all ports have the identifier "-". - M The port is a member of the VLAN. Frames sent in this VLAN are forwarded with the corresponding VLAN tag. - R The port is a member of the VLAN. A GVRP frame is used for the registration. - U (upper case) The port is an untagged member of the VLAN. Frames sent in this VLAN are forwarded without the VLAN tag. Frames without a VLAN tag are sent from this port. - u (lower case) The port is an untagged member of the VLAN, but the VLAN is not configured as a port VLAN. Frames sent in this VLAN are forwarded without the VLAN tag. - F The port is not a member of the specified VLAN and it is not possible for the VLAN to be registered dynamically at this port using GVRP. You can configure other settings in "Layer 2 > VLAN > Port-based VLAN". GVRP Configuration of GVRP functionality Using GVRP frame, a different device can register at the port of the device for a specific VID. A different device, can, for example be an end device or a switch. The device can also send GVRP frames via this port. Settings GVRP Enable or disable the "GVRP" function. Table 1 has the following columns: WinCC Basic V13.0 System Manual, 02/2014 805 Editing devices and networks 8.1 Configuring devices and networks 1st column Shows that the settings are valid for all ports of table 2. Setting Select the setting. You have the following setting options: - enabled Enables the sending of GVRP frames. - disabled Disables the sending of GVRP frames. - No Change No change in table 2. Transfer to table If you click the button, the setting is adopted for all ports of table 2. If you have selected "No Change", the content of table 2 will not be changed. Table 2 has the following columns: Port Shows the available ports. Setting Enable or disable the sending GVRP frames. Port-based VLAN Processing received frames On this page, you specify the configuration of the port properties for receiving frames. Settings Table 1 has the following columns: 1st column Shows that the settings are valid for all ports. Priority / Port VID / Acceptable Frames / Ingress Filtering Select the setting. If "No Change" is selected, the entry in table 2 remains unchanged. Transfer to table If you click the button, the setting is adopted for all ports of table 2. Table 2 has the following columns: 806 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Port Shows the available ports and link aggregations. Priority Select the priority assigned to untagged frames. The CoS priority (Class of Service) used in the VLAN tag. If a frame is received without a tag, it will be assigned this priority. This priority specifies how the frame is further processed compared with other frames. There are a total of eight priorities with values 0 to 7, where 7 represents the highest priority (IEEE 802.1p Port Priority). Port VID Select the VLAN ID. Only VLAN IDs defined on the "VLAN > General" page can be selected. If a received frame does not have a VLAN tag, it has a tag with the VLAN ID specified here added to it and is sent according to the rules at the port. Acceptable Frames Specify which types of frames will be accepted. The following alternatives are possible: - Tagged Frames Only The device discards all untagged frames. Otherwise, the forwarding rules apply according to the configuration. - All The device forwards all frames Ingress Filtering Specify whether the VID of received frames is evaluated. The following options are available: - enabled The VLAN ID of received frames decides whether they are forwarded: To forward a VLAN tagged frame, the receiving port must be a member in the same VLAN. Frames from unknown VLANs are discarded at the receiving port. - disabled All frames are forwarded. Protocol-based VLAN group On this page, you specify groups to which a protocol will be assigned. WinCC Basic V13.0 System Manual, 02/2014 807 Editing devices and networks 8.1 Configuring devices and networks Settings Protocol Based VLAN Enable or disable the protocol-based VLAN assignment. Protocol Value Enter the hexadecimal protocol value. A few examples are shown below: - PROFINET: 88:92 - IP: 08:00 - Novell: 81:37 - netbios: f0:f0 - appletalk: 80:9b Group ID Enter the ID of the group. The table has the following columns: Protocol Value Shows the file value. Group ID Shows the group ID. Protocol-based VLAN port On this page, you specify which protocol and which VLAN is assigned to the individual port. Settings Port Select the required port. All available ports and the link aggregations can be selected. Group ID Select the group ID from the drop-down list. Specify the ID in "Layer 2 > VLAN > Protocol Based VLAN Group". The table has the following columns: Port All available ports and the link aggregations are shown. Group ID Shows the group ID assigned to the port. VLAN ID Select the required VLAN ID to be assigned to the port. IPv4 subnet-based VLAN On this page, you specify which VLAN ID is assigned to the subnet. 808 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Settings Subnet Based VLAN Enable or disable the subnet-based VLAN assignment Port Select the port. All available ports and the link aggregations can be selected. Subnet Address Enter the IP address of the subnet. Example: 192.168.10.0 for the network 192.168.10.x with nodes 192.168.10.1 to 192.168.10.254. Subnet Mask Enter the subnet mask. The table has the following columns: Port All available ports and the link aggregations are shown. Subnet Address Shows the subnet assigned to the port. Subnet Mask Shows the subnet mask. VLAN ID Select the VLAN ID you want to assign to the port or the subnet. Mirroring Basics Mirroring The device provides the option of simultaneously channeling incoming or outgoing data streams via other interfaces for analysis or monitoring. This has no effect on the monitored data streams. This procedure is known as mirroring. In this menu section, you enable or disable mirroring and set the parameters. Mirroring ports Mirroring a port means that the data traffic at a port (mirrored port) of the IE switch is copied to another port (monitor port). You can mirror one or more ports to a monitor port. If a protocol analyzer is connected to the monitor port, the data traffic at the mirrored port can be recorded without interrupting the connection. This means that the data traffic can be investigated without being affected. This is possible only if a free port is available on the device as the monitor port. WinCC Basic V13.0 System Manual, 02/2014 809 Editing devices and networks 8.1 Configuring devices and networks General On this page, you can enable or disable the mirroring function and make the basic settings. Note If the maximum data rate of the mirrored port is higher than that of the monitor port, data may be lost and the monitor port no longer reflects the data traffic at the mirrored port. Several ports can be mirrored to one monitor port at the same time. Mirroring a port does not work beyond switch core boundaries. Disable port mirroring if you want to connect a normal end device to the monitor port. Settings Mirroring Enable or disable mirroring of the data traffic. Monitor Barrier Enable or disable the option to restrict communication via the monitor port. Note Monitor Barrier If you enable the monitor barrier, the data traffic on the destination port is automatically blocked (broadcast, multicast, unicast, DCP forwarding, LLDP) so that only the mirrored traffic is present. To be able to allow other data traffic again, you need to configure this. The previous statuses of these options are not restored after stopping the monitor barrier and must be reconfigured. - enabled The monitor port is taken out of normal frame switching. - disabled Communication via the monitor port is unrestricted. This table has the following columns: 810 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Session ID Enable or disable listening in on incoming packets at the required port. Session Type Specify which data traffic is mirrored. The following options are available: - '-' None - Port Based Port-based mirroring You can configure other settings in "Layer 2 > Mirroring > Port". - VLAN VLAN-based mirroring. You can configure other settings in "Layer 2 > Mirroring > VLAN". - MAC ACL Mirroring of the MAC Access Control List. You can configure other settings in "Layer 2 > Mirroring > MAC Flow". - IP ACL Mirroring of the IP Access Control List. You can configure other settings in "Layer 2 > Mirroring > IP Flow". Status Shows whether or not mirroring is active. Dest. Port Select the destination port to be mirrored to in this session. Port Mirroring ports You can only configure the settings on this page if you have already generated a session ID with the session type "Port Based" on the "General" tab. Settings Session ID Select the session ID. Only session IDs of the session type "Port Based" are available. The table has the following columns: Port Shows the port to be monitored. Ingress Mirroring Enable or disable mirroring of incoming packets at the required port. Egress Mirroring Enable or disable mirroring of outgoing packets at the required port. WinCC Basic V13.0 System Manual, 02/2014 811 Editing devices and networks 8.1 Configuring devices and networks VLAN VLAN sources of the port mirroring function You can only configure the settings on this page if you have already generated a session ID with the session type "VLAN" on the "General" tab. On this page, you specify the VLAN whose incoming data traffic will be mirrored to the monitor port. Settings Session ID Select the session ID. Only session IDs of the session type "VLAN" are available. VLAN ID Enter a VLAN ID. The VLAN ID can only be assigned once when you create a new data record and can then no longer be changed. To make a change, the entire data record must be deleted and created again. The table has the following columns: VLAN ID Shows the VLAN ID. MAC Flow You can only configure the settings on this page if you have already generated a session ID with the session type "MAC ACL" on the "General" tab. The MAC ACL filter decides which data is available at the monitor port. Settings Session ID Select the session ID. Only session IDs of the session type "MAC ACL" are available. The table has the following columns: ACL Filter Number Shows the number of the ACL filter. You configure the MAC ACL filter in "SecurityPort ACL MAC". Ingress Mirroring Shows whether incoming packets are mirrored. Note Rules A rule selected for ingress mirroring only becomes active if it was configured as a port ingress rule on at least one port. You configure the port ingress rules in "Security> Port MAC IP > Port Ingress Rules". 812 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Source MAC Shows the MAC address of the sender. Dest. MAC Shows the MAC address of the recipient. Ingress Port Shows a list of all ports to which this rule applies. Egress Port Shows a list of all ports to which this rule applies. IP Flow You can only configure the settings on this page if you have already generated a session ID with the session type "IP ACL" on the "General" tab. The IP ACL filter decides which data is mirrored to the monitor port. Settings Session ID Select the session ID. Only session IDs of the session type "IP ACL" are available. The table has the following columns: ACL Filter Number Shows the number of the ACL filter. You configure the IP ACL filter in "Security > Port ACL IP". Ingress Mirroring Shows whether incoming packets are mirrored. Note Rules A rule selected for ingress mirroring only becomes active if it was configured as a port ingress rule on at least one port. You configure the port ingress rules in "Security> Port ACL IP > Port Ingress Rules". Source IP Shows the IP address of the sender. Source Subnet Mask Shows the subnet mask of the sender. Dest. IP Shows the IP address of the recipient. Dest. Subnet Mask Shows the subnet mask of the recipient. Ingress Port Shows a list of all ingress ports to which this rule applies. Egress Port Shows a list of all egress ports to which this rule applies. WinCC Basic V13.0 System Manual, 02/2014 813 Editing devices and networks 8.1 Configuring devices and networks Dynamic MAC Aging The device automatically learns the source addresses of the connected nodes. This information is used to forward data frames to the nodes specifically involved. The network load for the other nodes is reduced. If a device does not receive a frame whose source address matches a learnt address within a certain time, the learnt address is deleted. This mechanism is known as aging. Aging prevents frames being forwarded incorrectly, for example when an end device (for example a programming device) is connected to a different port. If the check box is not enabled, a device does not delete learned addresses automatically. Settings Dynamic MAC Aging Enable or disable the function for automatic aging of learned MAC addresses: Aging Time [s] Enter the time in seconds. After this time, a learned address is deleted if the device does not receive any further frames from this sender address. Ring Redundancy Ring On this page, you can select the required mode for fast ring redundancy. The "Automatic Redundancy Detection" ring redundancy mode is the default when the device ships. Note The ring redundancy cannot be enabled if Spanning Tree is still enabled on the device. 814 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Settings Ring Redundancy Enable or disable ring redundancy. Ring redundancy mode Specify the ring redundancy mode. The following options are available: - "-" (disabled) The redundancy function is disabled. - Automatic Redundancy Detection Select this setting to create an automatic configuration of the redundancy mode. In this mode, the device automatically detects whether or not there is a device with the "HRP Manager" role in the ring. If this is the case, the device adopts the role of "HRP Client". If no HRP manager is found, all devices with the "Automatic Redundancy Detection" or "MRP Auto Manager" setting negotiate among themselves to establish which device adopts the role of "MRP Manager". The device with the lowest MAC address will always become "MRP Manager". The other devices automatically set themselves to redundancy mode "MRP Client". - MRP Auto Manager Devices with the setting "Automatic Redundancy Detection" or "MRP Auto Manager" negotiate among themselves which device will adopt the "MRP Manager" role. The device with the lowest MAC address will always become "MRP Manager". In contrast to the setting "Automatic Redundancy Detection", the devices are not capable of detecting whether or not an HRP manager is in the ring. This means that they never adopt the role of HRP client. - MRP Client In a ring whose devices are configured with MRP, at least one device must be set to the "Automatic Redundancy Detection" or "MRP Auto Manager" mode. You can set the "MRP Client" role for all other devices. If all devices except one are configured as "MRP Client", this one device automatically adopts the role of "MRP Manager". Select "MRP Client" mode if you want to operate the device along with components that do not originate from Siemens in the ring. - HRP Client Here, you can select the role "HRP Client". - HRP Manager When you configure an HRP ring, one device must be set as HRP manager. All other devices must be configured as HRP clients. Ring ports Specify the ports to be used as ring ports in media redundancy in ring topologies. The ring port you select in the upper drop-down menu is the "Isolated Port" in HRP. Note If you restore the factory defaults, the default redundancy mode "Automatic Redundancy Detection" becomes active. The ring port configuration is also reset to the factory default ports. If other ports were used previously as ring ports, with the appropriate attachment, a previously correctly configured device can cause circulating frames and therefore the failure of the data traffic. WinCC Basic V13.0 System Manual, 02/2014 815 Editing devices and networks 8.1 Configuring devices and networks Observer Enable or disable the observer. The "Observer" function is only available in HRP rings. The ring port selected in the upper drop-down menu is connected to the "Isolated Port" of an HRP manager. The observer monitors malfunctions of the redundancy manager or incorrect configurations of an HRP ring. If the observer is enabled, it can interrupt the connected ring if errors are detected. To do this, the observer switches a ring port to the "blocking" status. When the error is resolved, the observer enables the port again. Restart Observer (only available online) If numerous errors occur in quick succession, the observer no longer enables its port automatically. The ring port remains permanently in the "blocking" status. This is signaled by the error LED and a message text. After the errors have been eliminated, you can enable the port again using the "Restart Observer" button. Standby Standby manager The standby manager allows the redundant linking of two HRP rings. To do this, two neighboring devices within a ring must be configured as standby partners. Enable the standby manager for both standby partners and select the port via which the device is connected to the ring you want to link to. For the "Standby Connection Name", a name unique within the ring must be assigned for both partners. This identifies the two modules as standby partners that belong together. Note To be able to use the function, HRP must be activated. 816 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Settings Standby Enable or disable the standby manager. Note If two devices are linked by the standby function, the "Standby" function must be enabled on both devices. Note The standby manager always requires an activated HRP client. Standby Connection Name Enter the name for the standby connection. This name defines the master/slave device pair. Both must be located in the same ring. This is achieved by entering the same name on two devices in the ring. Note Make sure that the standby name (for one pair of devices) is used only once in the network. Force device to standby master When selected, the device is configured as standby master regardless of its MAC address. - If the setting is enabled for neither of the two devices for which the standby function is enabled, then assuming that no error has occurred, the device with the higher MAC address adopts the role of standby master. - If the setting is enabled for both devices or if the setting is only supported by one device, the standby master is also selected based on the MAC address. This type of assignment is important in particular when a device is replaced. Depending on the MAC addresses, the previous device with the slave function can take over the role of the standby master. This table has the following columns: Port Shows the port to which the setting relates. Setting Here, you specify which ports are standby ports. The standby ports are involved in the redirection of data traffic. If there are no problems, only the standby ports of the master are enabled and handle to the data traffic into the connected HRP rings (buses). If the master or the Ethernet connection (link) of one of the standby ports of the master fails, all standby ports of the master will be disabled and the standby ports of the slave enabled. As a result, a functioning Ethernet connection to the connected network segments (HRP rings/linear buses) is restored. WinCC Basic V13.0 System Manual, 02/2014 817 Editing devices and networks 8.1 Configuring devices and networks Spanning Tree General General settings of MSTP On this page, you configure the settings for MSTP. As default, Rapid Spanning Tree is enabled that can be set to the MSTP, RSTP or STP compatible mode with a switch. On the configuration pages of these functions, you can make detailed settings. Depending on the compatibility mode, you can configure the corresponding function on the relevant configuration page. Settings Spanning Tree Enable or disable Spanning Tree. Protocol Compatibility Select the compatibility mode of Spanning Tree. If, for example, you select RSTP, Spanning Tree behaves like RSTP. The following settings are available: - STP - RSTP - MSTP Using a link aggregation in an MSTP instance If you want to use a link aggregation in an MSTP instance, follow the steps below during configuration: 1. Create a link aggregation in "Layer 2" > "Link aggregation (Page 828)". 2. Create an MSTP instance in "Layer 2" > "Spanning Tree" > "MST General (Page 823)". 3. Configure the link aggregation in "Layer 2" > "Spanning Tree" > "MST port (Page 824)". Automatic activation of MRP in redundant topologies If you connect SCALANCE X switches with redundant network structures in the topology view, MRP is activated automatically on the switches involved. If there is an existing configuration with other redundancy mechanisms, such as MSTP, this is automatically deactivated. CIST general On this page, you configure CIST. 818 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Settings Bridge Priority / Root Priority (only available online) Which device becomes the root bridge is decided based on the bridge priority. The bridge with the highest priority becomes the root bridge. The lower the value, the higher the priority. If several devices in a network have the same priority, the device whose MAC address has the lowest numeric value will become the root bridge. Both parameters, bridge priority and MAC address together form the bridge identifier. Since the root bridge manages all path changes, it should be located as centrally as possible due to the delay of the frames. Bridge Address / Root Address(only available online) The bridge address shows the MAC address of the device and the root address shows the MAC address of the root bridge. Root Port (only available online) Shows the port via which the switch communicates with the root bridge. Root Cost (only available online) The path costs from this device to the root bridge. In MSTP mode, path costs up to the root bridge are shown. Topology Changes / Last Topology Change (only available online) The entry for the device shows the number of reconfigurations due to the spanning tree mechanism since the last startup. For the root bridge, the time since the last reconfiguration is displayed as follows: - Seconds: sec unit after the number - Minutes: min unit after the number - Hour: hr unit after the number Bridge Hello Time / Root Hello Time (only available online) Each bridge regularly sends configuration frames (BPDUs). The interval between two such frames is the Hello time. The default for this parameter is 2 seconds. Bridge Forward Delay / Root Forward Delay New configuration data is not used immediately by a bridge but only after the period specified in the parameter. This ensures that operation is only started with the new topology after all the bridges have the required information. Bridge Max Age / Root Max Age (only available online) Bridge Max Age defines the maximum "age" of a received BPDU for it to be accepted as valid by the switch. Bridge Max Hop Count This parameter specifies how many MSTP nodes a BPDU may pass through. If an MSTP BPDU is received and has a "Bridge Max Hop Count" that exceeds the value configured here, it is discarded. Regional root priority (only available online) For a description, see Bridge Priority / Root Priority Regional root address (only available online) The MAC address of the device. Regional root costs (only available online) Shows the path costs from this device to the regional root bridge. WinCC Basic V13.0 System Manual, 02/2014 819 Editing devices and networks 8.1 Configuring devices and networks Region Name Enter the name of the MSTP region to which this device belongs. As default, the MAC address of the device is entered here. This value must be the same on all devices that belong to the same MSTP region. Region Version Enter the version number of the MSTP region in which the device is located. This value must be the same on all devices that belong to the same MSTP region. Reset Counter (only available online) Click this button to reset the counters on this page to zero. CIST port MSTP-CIST port configuration When the page is called, the table displays the current status of the configuration of the port parameters. To configure them, click the relevant cells in the port table. Settings Table 1 has the following columns: 1st column Shows that the setting is valid for all ports of table 2. MSTP Status Select the required setting. If "No Change" is selected, the entry in table 2 remains unchanged. Transfer to table If you click the button, the setting is adopted for all ports of table 2. Table 2 has the following columns: Port Shows the available ports. MSTP Status Specify whether or not the port is integrated in the spanning tree. Note If you disable the "MSTP Status" option for a port, this may cause the formation of loops. The topology must be kept in mind. Priority Enter the priority of the port. The priority is only evaluated when the path costs are the same. The value must be divisible by 16. If the value that cannot be divided by 16, the value is automatically adapted. Cost Calc. Enter the path cost calculation. If you enter the value "0" here, the automatically calculated value is displayed in the "Path Costs" box. 820 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Path Costs (only available online) This parameter is used to calculate the path that will be selected. The path with the lowest value is selected as the path. If several ports of a device have the same value for the path costs, the port with the lowest port number is selected. If the value for "Cost Calc." is "0", the automatically calculated value is displayed. Otherwise, the value of the "Cost Calc." box is displayed. The calculation of the path costs is largely based on the transmission speed. The higher the achievable transmission speed is, the lower the value of the path costs. Typical values for path costs with rapid spanning tree: - 10,000 Mbps = 2,000 - 1000 Mbps = 20,000 - 100 Mbps = 200,000 - 10 Mbps = 2,000,000 The values can, however, also be set individually. Status (only available online) Displays the current status of the port. The values are only displayed and cannot be configured. The "Status" parameter depends on the configured protocol. The following is possible for status: - Disabled The port only receives and is not involved in STP, MSTP and RSTP. - Discarding In the "Discarding" mode, BPDU frames are received. Other incoming or outgoing frames are discarded. - Listening In this status, BPDUs are both received and sent. The port is involved in the spanning tree algorithm. - Learning Stage prior to the forwarding status, the port is actively learning the topology (in other words, the node addresses). - Forwarding Following the reconfiguration time, the port is active in the network; it receives and forwards data frames. WinCC Basic V13.0 System Manual, 02/2014 821 Editing devices and networks 8.1 Configuring devices and networks Fwd. Trans (only available online) Specifies the number of changes from the "Discarding" status to the "Forwarding" status Edge type Specify the type of edge port. You have the following options: - "-" Edge port is disabled. The port is treated as a "no edge port". - Admin Select this option when there is always an end device on this port. Otherwise a reconfiguration of the network will be triggered each time a connection is changed. - Auto Select this option if you want a connected end device to be detected automatically at this port. When the connection is established the first time, the port is treated as a "no Edge Port". - Admin/Auto Select these options if you operate a combination of both on this port. When the connection is established the first time, the port is treated as an Edge Port. Edge (only available online) Shows the status of the port. - Enabled An edge port is connected to this port. - Disabled There is a spanning tree or rapid spanning tree device at this port. With an end device, a switch can change over the port faster without taking into account spanning tree frames. If a spanning tree frame is received despite this setting, the port automatically changes to the "Disabled" setting for switches. 822 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks P.t.P. Type Select the required option. The selection depends on the port that is set. - "-" Point to point is calculated automatically. If the port is set to half duplex, a point-to-point link is not assumed. - P.t.P. Even with half duplex, a point-to-point link is assumed. - Shared Media Even with a full duplex connection, a point-to-point link is not assumed. Note Point-to-point connection means a direct connection between two devices. A shared media connection is, for example, a connection to a hub. Hello Time Enter the interval after which the bridge sends configuration BPDUs Note The port-specific setting of the Hello time is only possible in MSTP compatible mode. MST General Multiple Spanning Tree configuration With MSTP, in addition to RSTP, several VLANs can be managed in a LAN with separate RSTP trees. Settings MSTP Instance ID Enter the number of the MSTP instance. The table has the following columns: MSTP Instance ID Shows the number of the MSTP instance. Root Address Shows the MAC address of the root bridge Root Priority Shows the priority of the root bridge. WinCC Basic V13.0 System Manual, 02/2014 823 Editing devices and networks 8.1 Configuring devices and networks Bridge Priority Enter the bridge priority. The value for the bridge priority is a whole multiple of 4096. VLAN ID Enter the VLAN ID. Here, you can also specify ranges with Start ID, "-", End ID. Several ranges or IDs are separated by ",". MST port Configuration of the Multiple Spanning Tree port parameters On this page, you set the parameters for the ports of the configured multiple spanning tree instances. Settings MSTP Instance ID Select the ID of the MSTP instance. Table 1 has the following columns 1st column Shows that the setting is valid for all ports. MSTP Status Select the setting. If "No Change" is selected, the entry in table 2 remains unchanged. Transfer to table If you click the button, the setting is adopted for all ports of table 2 The table has the following columns: Port Shows all available ports and link aggregations. MSTP Instance ID ID of the MSTP instance. MSTP Status Enable or disable MSTP for this port. Priority Enter the priority of the port. The priority is only evaluated when the path costs are the same. The value must be divisible by 16. If the value that cannot be divided by 16, the value is automatically adapted. Cost Calc. Enter the path cost calculation in the input box. If you enter the value "0" here, the automatically calculated value is displayed in the next box "Path Costs". 824 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Path Costs (only available online) This parameter is used to calculate the path that will be selected. The path with the lowest value is selected as the path. If several ports of a device have the same value for the path costs, the port with the lowest port number is selected. If the value for "Cost Calc." is "0", the automatically calculated value is displayed. Otherwise, the value of the "Cost Calc." box is displayed. The calculation of the path costs is largely based on the transmission speed. The higher the achievable transmission speed is, the lower the value of the path costs. Typical values for path costs with rapid spanning tree: - 10,000 Mbps = 2,000 - 1000 Mbps = 20,000 - 100 Mbps = 200,000 - 10 Mbps = 2,000,000 The values can, however, also be set individually. Status (only available online) Displays the current status of the port. The values are only displayed and cannot be configured. The "Status" parameter depends on the configured protocol. The following is possible for status: - Disabled The port only receives and is not involved in STP, MSTP and RSTP. - Discarding In the "Discarding" mode, BPDU frames are received. Other incoming or outgoing frames are discarded. - Listening In this status, BPDUs are both received and sent. The port is involved in the spanning tree algorithm. - Learning Stage prior to the forwarding status, the port is actively learning the topology (in other words, the node addresses). - Forwarding Following the reconfiguration time, the port is active in the network; it receives and forwards data frames. Fwd. Trans (only available online) Specifies the number of changes from the "Discarding" status to the "Forwarding" status Enhanced Passive Listening Compatibility Enabling the function On this page, you enable the expanded compatibility for passive listening. WinCC Basic V13.0 System Manual, 02/2014 825 Editing devices and networks 8.1 Configuring devices and networks Settings Enhanced Passive Listening Compatibility Enable or disable this function for the entire device. Table 1 has the following columns: 1st column Shows that the settings are valid for all ports of table 2. Setting Select the required setting. If "No Change" is selected, the entry in table 2 remains unchanged. Transfer to table If you click the button, the setting is adopted for all ports of table 2. Table 2 has the following columns: Port Displays the port of the device. Setting - enabled Enables the function for all ports of the device. - disabled Disables the function for all ports of the device. Loop detection With the "Loop Detection" function, you specify the ports for which loop detection will be activated. The ports involved send special test frames - the loop detection frames. If these frames are sent back to the device, there is a loop. A "local loop" involving this device means that the frames are received again at a different port of the same device. If the sent frames are received again at the same port, there is a "remote loop" involving other network components. Note A loop is an error in the network structure that needs to be eliminated. The loop detection can help to find the errors more quickly but does not eliminate them. The loop detection is not suitable for increasing network availability by deliberately including loops. Note Note that loop detection is only possible at ports that were not configured as ring ports or standby ports. 826 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Settings Loop Detection Enable or disable loop detection. VLAN Loop Detection Enable or disable loop detection in a VLAN. Table 1 has the following columns: 1st column Shows that the settings are valid for all ports of table 2 Threshold / Remote Reaction / Local Reaction Select the required setting. If "No Change" is selected, the entry in table 2 remains unchanged. Transfer to table If you click the button, the setting is adopted for all ports of table 2. Table 2 has the following columns: Port Shows the available ports. Setting Specify how the port handles loop detection frames. Note Test frames create additional network load. We recommend that you only configure individual switches, for example at branch points of the ring, as "sender" and the others as "forwarder". - sender Loop detection frames are sent out and forwarded. - forwarder Loop detection frames from other devices are forwarded. - blocked The forwarding of loop detection frames is blocked. Threshold Specify the number of received loop detection frames as of which a loop is assumed. Remote Reaction Specify how the port will react if a remote loop occurs. Select one of the two options from the drop-down list: - no action A loop has no effect on the port. - disable The port is blocked. WinCC Basic V13.0 System Manual, 02/2014 827 Editing devices and networks 8.1 Configuring devices and networks Local Reaction Specify how the port will react if a local loop occurs. Select one of the two options from the drop-down list: - no action A loop has no effect on the port. - disable The port is blocked Status (only available online) This box shows whether loop detection is enabled or disabled for this port. Source Port (only available online) Shows the output port of the loop detection frame that triggered the last reaction Source VLAN (only available online) Shows the VLAN ID of the loop detection frame that triggered the last reaction. This is only possible if "VLAN Support Enabled" was selected earlier on the "Loop Detection Configuration" page. Reset (only available online) After a loop in the network has been eliminated, click this button to reset the port again Link aggregation Bundling network connections for redundancy and higher bandwidth A link aggregation according to IEEE 802.3ad allows several connections between neighboring devices to be bundled to achieve higher bandwidths and to protect against failure. Ports on both partner devices are included in link aggregations and the devices are then connected via these ports. To assign ports (in other words links) correctly to a partner device, the Link Aggregation Control Protocol (LACP) from the IEEE 802.3ad standard is used. Up to 8 link aggregations can be defined. A maximum of 8 ports can be assigned to each link aggregation. You can also use link aggregations within an MSTP instance, see "Layer 2" > "Spanning Tree" > "General (Page 818)". Settings The table has the following columns: Port Shows the virtual port number of this link aggregation. This identifier is assigned internally by the firmware. Link Aggregation Name Enter the name for the link aggregation. This name can be specified by the user during configuration. The name is not absolutely necessary but can be useful to distinguish between the various link aggregations. MAC Address Shows the MAC address. 828 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Status Enable or disable link aggregation. MTU Specify the packet size. LACP - on Enables the sending of LACP frames. - off Disables the sending of LACP frames. Frame Distribution Set the type of distribution of packets on the individual links of an aggregation. - Destination&Source Mac The distribution is based on a combination of the destination and source MAC address. - Destination&Source IP-MAC The distribution is based on a combination of the destination and source IP address and MAC address. VLAN Mode Specify how the link aggregation is entered in a VLAN: - Hybrid The link aggregation sends tagged and untagged frames. It is not automatically a member of a VLAN. - Trunk The link aggregation only sends tagged frames and is automatically a member of all VLANs. Port Shows the ports that belong to this link aggregation. The following values can be selected from the drop-down list: - "-" (disabled) Link aggregation is disabled. - "a" (active) The port sends LACP frames and is only involved in the link aggregation when LACP frames are received. - "p" (passive) The port is only involved in the link aggregation when LACP frames are received. - "o" (on) The port is involved in the link aggregation and does not send any LACP frames. Note Within a "link aggregation", only ports with the following configuration are possible: all ports with "o" all ports with "a" or "p". WinCC Basic V13.0 System Manual, 02/2014 829 Editing devices and networks 8.1 Configuring devices and networks DCP forwarding Applications The DCP protocol is used by STEP 7 and the PST Tool for configuration and diagnostics. When shipped, DCP is enabled on all ports; in other words, DCP frames are forwarded at all ports. With this option, you can disable the sending of these frames for individual ports, for example to prevent individual parts of the network from being configured with the PST Tool or to divide the full network into smaller parts for configuration and diagnostics. Settings Table 1 has the following columns: 1st column Shows that the setting is valid for all ports of table 2. Setting Select the required setting. If "No Change" is selected, the entry in table 2 remains unchanged. Transfer to table If you click the button, the setting is adopted for all ports of table 2. Table 2 has the following columns: Port Shows the available ports. Setting Specify whether the port should block or forward outgoing DCP frames. The following options are available: - forward DCP frames are forwarded via this port. - block No outgoing DCP frames are forwarded via this port. It is nevertheless still possible to receive via this port. LLDP Applications PROFINET uses the LLDP protocol for topology diagnostics. In the default setting, LLDP is enabled for all ports; in other words, LLDP frames are sent and received on all ports. With this function, you have the option of enabling or disabling sending and/or receiving per port. 830 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Settings Table 1 has the following columns: 1st column Shows that the setting is valid for all ports of table 2. Setting Select the required setting. If "No Change" is selected, the entry in table 2 remains unchanged. Transfer to table If you click the button, the setting is adopted for all ports of table 2. Table 2 has the following columns: Port Shows the port. Setting Specify the LLDP functionality. The following options are available: - Rx This port can only receive LLDP frames. - Tx This port can only send LLDP frames. - Rx & Tx This port can receive and send LLDP frames. - "-" (disabled) This port can neither receive nor send LLDP frames. Unicast Filter Address filtering This page shows the current content of the unicast filter table. This table lists the source addresses of unicast address frames. The displayed entries were made statically, in other words, the user set them. On this page, you also define the static unicast filters. Settings VLAN ID Select the VLAN ID in which you configure a new static MAC address. If nothing is set, "VLAN1" is set as the basic setting. MAC Address Enter the MAC address here. This table contains the following columns: WinCC Basic V13.0 System Manual, 02/2014 831 Editing devices and networks 8.1 Configuring devices and networks VLAN ID Shows the VLAN-ID assigned to this MAC address. MAC Address Shows the MAC address of the node that the device has learned or the user has configured. Status Shows the status of each address entry: - static Configured by the user. Static addresses are stored permanently; in other words, they are not deleted when the aging time expires or when the switch is restarted. Port Shows the port via which the node with the specified address can be reached. Frames received by the device whose destination address matches this address will be forwarded to this port. Note You can only specify one port for unicast addresses. Learning Starting/stopping learning Note The page is only available if there is an online connection to the device. With the automatic learning function, all connected devices are automatically entered in the unicast filter table. As long as the "Start learning" function is enabled, all learned unicast addresses are created immediately as static unicast entries. The learning process is ended only after clicking the "Stop learning" button. With this method, learning can take a few minutes or several hours in larger networks before all nodes have really been learned. Only nodes that send packets during the learning phase are found. By subsequently enabling the Port Lock function, only packets from the nodes known after the end of the learning phase (static unicast entries) will be accepted at the relevant ports. Note If the Port Lock function was already active on individual ports prior to the automatic learning phase, no addresses will be learned on these ports. This makes it possible to restrict learning to certain ports. To do this, first enable the Port Lock function of the ports that are not intended to learn addresses. 832 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Settings Start learning Click the "Start learning" button to start the learning phase. The device now enters the addresses of connected devices until you stop the function. Stop learning Click the "Stop Learning" button to stop the learning phase. The learned entries are stored. Deleting all static unicast addresses Click the "Clear all static unicast addresses" button to delete all static entries. In large networks with numerous nodes, automatic learning may lead to a lot of undesired static entries. To avoid having to delete these individually, this button can be used to delete all static entries. This function is disabled during automatic learning. Note Depending on the number of entries involved, deleting may take some time. Locked ports Activating the access control On this page, you can block individual ports for unknown nodes. If the Port Lock function is enabled, packets arriving at this port from unknown MAC addresses are discarded immediately. Packets from known nodes are accepted by the port. Since ports with the port lock function enabled cannot learn any MAC addresses, learned addresses on these ports are automatically deleted after the port lock function is enabled. Settings Table 1 has the following columns: 1st column Shows that the setting is valid for all ports of table 2. Setting Select the required setting. If "No Change" is selected, the entry in table 2 remains unchanged. Transfer to table If you click the button, the setting is adopted for all ports of table 2. Table 2 has the following columns: Port Shows the available ports. Setting Enable or disable access the port lock function for the port. WinCC Basic V13.0 System Manual, 02/2014 833 Editing devices and networks 8.1 Configuring devices and networks Blocking Blocking the forwarding of unknown unicast frames On this page, you can block the forwarding of unknown unicast frames for individual ports. Settings Table 1 has the following columns: 1st column Shows that the setting is valid for all ports of table 2. Setting Select the required setting. If "No Change" is selected, the entry in table 2 remains unchanged. Transfer to table If you click the button, the setting is adopted for all ports of table 2. Table 2 has the following columns: Port Shows the available ports. Setting Enable or disable the blocking of unicast frames Note Ring redundancy / standby If ring redundancy or standby is enabled, the ports configured for this are not included in the blocking. Multicast Groups Multicast applications In the majority of cases, a frame is sent with a unicast address to a particular recipient. If an application sends the same data to several recipients, the amount of data can be reduced by sending the data using one multicast address. For some applications, there are fixed multicast addresses (NTP, IETF1 Audio, IETF1 Video etc.). 834 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Reducing network load In contrast to unicast frames, multicast frames represent a higher load for the device. Generally, multicast frames are sent to all ports. There are three ways of reducing the load caused by multicast frames: Static entry of the addresses in the multicast filter table. Dynamic entry of the addresses by listening in on IGMP parameter assignment frames (IGMP Configuration). Active dynamic assignment of addresses by GMRP frames. The result of all these methods is that multicast frames are sent only to ports for which an appropriate address is entered. "Multicast" shows the multicast frames currently entered in the filter table and their destination ports. The displayed entries were made statically, in other words, the user set them. Settings VLAN ID Select the VLAN ID to be assigned to the MAC multicast address. MAC Address Here you enter a new MAC multicast address you want to configure. The table has the following columns: VLAN ID Shows VLAN ID of the VLAN to which the MAC multicast address is assigned. MAC Address Shows the MAC multicast address that the device has learned or the user has configured. Status Shows the status of each address entry. The following information is possible: - static The address was entered statically by the user. Static addresses are stored permanently; in other words, they are not deleted when the aging time expires or when the device is restarted. These must be deleted by the user. IGMP Function IE switches support "IGMP snooping" and the IGMP querier function. If "IGMP snooping" is enabled, IGMP frames are evaluated and the multicast filter table is updated with this information. If "IGMP Querier is also enabled, IE switches also send IGMP queries that trigger responses from IGMP-compliant nodes. WinCC Basic V13.0 System Manual, 02/2014 835 Editing devices and networks 8.1 Configuring devices and networks IGMP Snooping Aging Time In this menu, you can configure the aging time for IGMP Configuration. When the time elapses, entries created by IGMP are deleted from the address table if they are not updated by a new IGMP frame. This applies to all ports; a port-specific configuration is not possible. IGMP Snooping Aging Time depending on the querier SCALANCE XR500 as IGMP querier: If a SCALANCE XR500 is used as an IGMP querier, the query interval is 125 seconds. For the "IGMP Snooping Aging Time", set at least 250 seconds. Other IGMP queriers If a different IGMP querier is used, the value of the "IGMP Snooping Aging Time" should be at least twice as long as the query interval. Settings IGMP Snooping Enable or disable IGMP (Internet Group Management Protocol). The function allows the assignment of IP addresses to multicast groups. If the check box is selected, IGMP entries are included in the table and IGMP frames are forwarded. IGMP Snooping Aging Time Enter the value for the aging time in seconds in this box. IGMP Querier Enable or disable "IGMP Querier". The device sends IGMP queries. GMRP Enabling GMRP By selecting the check box, you specify whether or not GMRP is used for each individual port. If "GMRP" is disabled for a port, no registrations are made for it and it cannot send GMRP frames. Settings GMRP Enable or disable the GMRP function. Table 1 has the following columns: 836 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks 1st column Shows that the setting is valid for all ports of table 2. Setting Select the required setting. If "No Change" is selected, the entry in table 2 remains unchanged. Transfer to table If you click the button, the settings are adopted for all ports of table 2. Table 2 has the following columns: Port Shows the available ports and the link aggregations. Setting Enable or disable GMRP for the port or for the link aggregation. Blocking On this page, you can block the forwarding of unknown multicast frames for individual ports. Settings Table 1 has the following columns: 1st column Shows that the setting is valid for all ports of table 2. Setting Select the required setting. If "No Change" is selected, the entry in table 2 remains unchanged Transfer to table If you click the button, the setting is adopted for all ports of table 2. Table 2 has the following columns: Port Shows the available ports. Setting Enable or disable the blocking of multicast frames. WinCC Basic V13.0 System Manual, 02/2014 837 Editing devices and networks 8.1 Configuring devices and networks Broadcast Blocking the forwarding of broadcast frames On this page, you can block the forwarding of broadcast frames for individual ports. Note Some communication protocols work only with the support of broadcast. In these cases, blocking can lead to loss of data communication. Block broadcast only when you are sure that you do not need it. Settings Table 1 has the following columns: 1st column Shows that the setting is valid for all ports of table 2. Setting Select the required setting. If "No Change" is selected, the entry in table 2 remains unchanged. Transfer to table If you click the button, the setting is adopted for all ports of table 2. Table 2 has the following columns: Port All available ports and the link aggregations are shown. Setting Enable or disable the blocking of broadcast frames. PTP General Note PTP is only available with SCALANCE X500. The Precision Time Protocol (PTP) complying with IEEE 1588v2 allows the time-of-day synchronization of devices connected to the ports of a device. These devices forward the synchronization frames through the network using the "Transparent Clock" (TC) mechanism. The connection mechanisms "end-to-end" and "peer-to-peer" are supported. To use IEEE 1588v2, enable this function and configure every port that is on the synchronization path as well as ports that are blocked due to redundancy mechanisms. IEEE 1588v2 can also be used with redundancy mechanisms in the ring such as HRP, standby linking of rings, MRP and RSTP. 838 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Setting 1588 Mode You can make the following settings: - off The device does not process any PTP messages. PTP messages are, however, forwarded according to the rules of the device. - transparent The device adopts the function of a transparent clock and forwards PTP messages to other nodes while at the same time making entries in the correction field of the PTP message. TC general 1588 Transparent Clock On this page, you specify the general settings for PTP. Settings Delay Mechanism Specify the delay mechanism the device will work with: - End-to-end(delay request response mechanism will be used) - Peer-to-peer (peer delay mechanism will be used) Domain Number Enter the identification number for the time domain. Synchronization is only for the devices within the domain. The device ignores PTP messages with a different domain number. A SCALANCE device can only be assigned to one synchronization domain. TC port On this page, you specify the ports that can process PTP messages. Settings Table 1 has the following columns: 1st column Shows that the settings are valid for all ports of table 2. Setting / Transport Mechanism Select the setting. If "No Change" is selected, the entry in table 2 remains unchanged. Transfer to table If you click the button, the settings are adopted for all ports of table 2. Table 2 has the following columns: WinCC Basic V13.0 System Manual, 02/2014 839 Editing devices and networks 8.1 Configuring devices and networks Port Shows the available ports. Setting Enable or disable PTP. When enabled, the port processes PTP messages. Faulty Flag Shows error status relating to PTP. - true An error occurred. - false No error has occurred on this port. Transport Mechanism Specifies the protocol for transferring the PTP messages. This protocol must also be supported by the communications partner of the port - Ethernet - UDP IPv4 RMON Statistics Statistics On this page you can specify the ports for which statistics are displayed. Settings RMON If you select this check box, Remote Monitoring (RMON) allows diagnostics data to be collected on the device, prepared and read out using SNMP by a network management station that also supports RMON. This diagnostic data, for example port-related load trends, allow problems in the network to be detected early and eliminated. Port Select the ports for which statistics will be displayed. The table has the following columns: 1st column Select the check box of the ports for which no more statistics will be displayed. Port Shows the ports for which statistics will be displayed. 840 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks History Samples of the statistics On this page, you can specify whether or not samples of the statistics are saved for a port. You can specify how many entries should be saved and at which intervals samples should be taken. Settings Table 1 has the following columns: 1st column Shows that the settings are valid for all ports. Setting Select the required setting. If "No Change" is selected, the entry in table 2 remains unchanged. Entries Enter the maximum number of samples to be stored at the same time. If "No Change" is entered, the entry in table 2 remains unchanged. Interval [s] Enter the interval after which the current status of the statistics will be saved as a sample. If "No Change" is entered, the entry in table 2 remains unchanged. Transfer to table If you click the button, the settings are adopted for all ports of table 2. Table 2 has the following columns: Port Shows the port to which the settings relate. Setting Enable the port for which the history will be displayed. Entries Enter the maximum number of samples to be stored at the same time. Interval [s] Enter the interval after which the current status of the statistics will be saved as a sample. Layer 3 Configuration The page contains the overview of the layer 3 functions of the device. To use the "Routing", "VRRP", "OSPF" and "RIP" functions, the device requires a KEY-PLUG. WinCC Basic V13.0 System Manual, 02/2014 841 Editing devices and networks 8.1 Configuring devices and networks Settings Routing (only available on layer 3) Enable or disable the "Routing" function. DHCP Relay Agent Enable or disable the DHCP relay agent. You can configure other settings in "Layer 3 > DHCP Relay Agent". VRRP (only available on layer 3) Enable or disable routing using VRRP. To use VRRP, first enable the "Routing" function. You can configure other settings in "Layer 3 > VRRP". OSPF (only available on layer 3) Enable or disable routing using OSPF. To use OSPF , first enable the "Routing" function. You can configure other settings in "Layer 3 > OSPFv2". RIP (only available on layer 3) Enable or disable routing using RIP. To use RIO , first enable the "Routing" function. You can configure other settings in "Layer 3 > RIPv2". Subnets Overview Subnet The page shows the subnets for the selected interface. If more than one subnet is available on an interface, the first entry of this interface is of the address type "Primary". All other subnets have the address type "Secondary". On this page, you can create further subnets "Layer 3 > Subnets > Overview". In "Layer 3 > Subnets > Configuration", you configure the settings of the created subnets. Settings The following settings are possible for subnets of the "Secondary" address type: Interface Select the interface on which you want to configure another subnet. The table has the following columns: Interface Shows the interface. TIA Interface Shows whether or not the entry is a TIA interface. Interface Name Shows the name of the interface. MAC Address Shows the MAC address. 842 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks IP Address Shows the IP address of the subnet. Subnet Mask Shows the subnet mask. Address Type Shows the address type. The following values are possible: - Primary The first IP address that was configured on an IP interface. - Secondary All other IP addresses that were configured on an interface. IP Assignment Method Shows how the IP address is assigned. - Static The IP address is static. You enter the IP settings in "IP Address" and "Subnet Mask". - Automatic (DHCP) The device obtains a dynamic IP address from a DHCP server. Address Collision Detection Status Shows the status of the "Detection of address collisions" function. - Idle The interface is not enabled and does not have an IP address. - Starting This status indicates the start-up phase. In this phase, the device initially sends a query as to whether the planned IP address already exists. If the address is not yet been assigned, the device sends the message that it is using this IP address as of now. - Conflict The interface is not enabled. The interface is attempting to use an IP address that is already been assigned. - Defending The interface uses a unique IP address. Another interface is attempting to use the same IP address. - Active The interface uses a unique IP address. There are no collisions. - Not supported The function for detection of address collisions is not supported. Configuration On this page, you configure the subnet. You create the subnet in "Layer 3 > Subnets > Overview". WinCC Basic V13.0 System Manual, 02/2014 843 Editing devices and networks 8.1 Configuring devices and networks Settings Interface (Name) Select the required interface. Interface Name Enter the name of the interface, e.g. eth0; P3. MAC Address (only available online) Shows the MAC address of the selected interface DHCP Enable or disable the DHCP client for this interface. IP Address Enter the IP address of the subnet. The IP address must not be used more than once. Subnet Mask Enter the subnet mask of the subnet you are creating. Subnets on different interfaces must not overlap. Address Type Shows the address type. The following values are possible: - Primary The first subnet of the interface. - Secondary All other subnets of the interface. Address Collision Detection Enable or disable the function. If new IP addresses become active in the network, this function checks whether this can result in address collisions. With this function, IP addresses that will be assigned twice can be detected. Note The function does not run a cyclic check. TIA Interface Enable or disable the setting. The following conditions apply to the TIA interface: - Only interfaces with the address type "Primary" can be enabled as the TIA interface. - There must only ever be one TIA interface. - There can only be one TIA interface. - A TIA interface is always a VLAN interface. TIA interface and PROFINET interface The IP address of the TIA interface is linked to the IP address located in the parameter group "Properties > General > PROFINET interface > Ethernet addresses". Both IP addresses always have the same value. If you change the value of one IP address, the other IP address changes accordingly. 844 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks TIA Interface The TIA interface is the interface via which all PROFINET functions of the IE switch are handled. TIA interface is the name of the IP address for PROFINET from the perspective of the IE switch. PROFINET interface You make the IP setting of the PROFINET device in TIA under PROFINET interface. PROFINET interface is the name of the IP address for PROFINET from the perspective of the TIA Portal. Routes Static route On this page, you create the static routes. During automatic adaptations, static routes are not taken into account and need to be adapted manually. Settings Destination Network Enter the network address of the destination. Subnet Mask Enter the corresponding subnet mask. Gateway Enter the IP address of the next gateway. Metric Enter the metric for the route. The metric corresponds to the quality of a connection, for example speed, costs. The table has the following columns: Destination Network Shows the network address of the destination. Subnet mask Shows the corresponding subnet mask. Gateway Shows the IP address of the next gateway. Interface (only available online) Shows the interface of the route. Metric Enter the metric for the route. When creating the route, "not used" is entered automatically. The metric corresponds to the quality of a connection, for example speed, costs. If there are several equal routes, the route with the lowest metric value is used. Status (only available online) Shows the status of the route. WinCC Basic V13.0 System Manual, 02/2014 845 Editing devices and networks 8.1 Configuring devices and networks Route maps General Route maps With route maps, you control how routing information is further processed. You can filter routing information and specify whether the information is further processed, modified or discarded. Route maps operate according to the following principle: Routing information is compared with the filters of the route maps. The comparison is continued until the filters of a route map match the properties of an item of information. The information is then processed according to the route map settings: - The routing information is discarded. - The properties of the routing information are changed. Settings Name Enter the name for the route map. Sequence No Enter a number for the route map. The numbers specify the order in which the route maps are processed. The table has the following columns: Name Shows the name of the route map. Sequence No Shows the sequence number of the route map. Action Specify what happens to the routing information that matches the settings of the route map: - permit The routing information is further processed according to the settings you make in the "Settings" tab. - deny The routing information is discarded. Interface and metric match On this page, you specify whether or not the routing information for a route map is filtered according to interfaces or metric. 846 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Settings Route Map (name/seq. no.) Select a route map. The created route maps are available to you. Type Select the basis for the filtering: - Interface - Metric Interface Select an interface. This box is active only if you have selected the "Interface" entry in the "Type" drop-down list. Metric Enter a value for the metric. This box is active only if you have selected the "Metric" entry in the "Type" drop-down list. The table has the following columns: Type Shows the selected type: - Interface - Metric Value Shows the selected interface or the value of the metric. Source match On this page, you specify whether or not the routing information for a route map is filtered based on the source IP address. Settings Route Map (name/seq. no.) Select a route map. IP Address Enter the IP address of the source on which the filtering is based. Subnet Mask Enter the subnet mask of the source on which the filtering is based. The table has the following columns: IP Address Shows the IP address of the source. Subnet Mask Shows the subnet mask of the source. WinCC Basic V13.0 System Manual, 02/2014 847 Editing devices and networks 8.1 Configuring devices and networks Destination match On this page, you specify whether or not the routing information for a route map is filtered based on the destination IP address. Settings Route Map (name/seq. no.) Select a route map. IP Address Enter the IP address of the destination on which the filtering is based. Subnet Mask Enter the subnet mask of the destination on which the filtering is based. The table has the following columns: IP Address Shows the IP address of the destination. Subnet Mask Shows the subnet mask of the destination. Next hop match On this page, you specify whether or not the filtering for a route map will be based on the router to which the routing information is sent next. Settings Route Map (name/seq. no.) Select a route map. IP Address Enter the IP address of the router to which the routing information will be sent next. The table has the following columns: IP Address Shows the IP address of the next router. Settings On this page, you specify whether or not the routing information for a route map will be changed. If, for example, you have filtered based on a certain metric, you can change the value of the metric here. The routing information is then forwarded with the new value. Settings Route Map (name/seq. no.) Select a route map. The table has the following columns: 848 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Name Shows the name of the route map. Sequence No Shows the sequence number of the route map. Interface Enter the new interface via which the routing information will be forwarded. Metric Enter the new value for the metric with which the routing information will be forwarded. Next Hop IP Address Enter the IP address of the router to which the routing information will be sent next. DHCP Relay Agent General If the DHCP server is in a different network, the device cannot reach the DHCP server. The DHCP relay agent intercedes between a DHCP server and the device. The DHCP relay agent forwards the port number of the device with the DHCP query to the DHCP server. If a DHCP server is unreachable, the device can switch to a different DHCP server. Settings DHCP Relay Agent (Opt. 82) Enable or disable the DHCP relay agent. Server IP Address Enter the IP address of the DHCP server. The table has the following columns: Server IP address Shows the IP address of the DHCP server. Option Parameters of the DHCP relay agent On this page, you can specify parameters for the DHCP server, for example the circuit ID. The circuit ID describes the origin of the DHCP query, for example which port received the DHCP query. You specify the DHCP server on the "General" tab. WinCC Basic V13.0 System Manual, 02/2014 849 Editing devices and networks 8.1 Configuring devices and networks Settings Global configuration Circuit ID router index When enabled, the router index is added to the generated circuit ID. Circuit ID recipient VLAN ID When enabled, the VLAN ID is added to the generated circuit ID. Circuit ID receiving port When enabled, the receiving port is added to the generated circuit ID. Note You need to select a least one option. Remote ID Shows the device ID. Interface-specific configuration Interface Select the required interface. The table has the following columns: Interface Shows the selected interface. Remote ID type Select the type of the device ID. You have the following options: - IP Address The current IP address of the interface will be used as the device identifier and copied to the "Remote ID" box. Note No automatic updating There is no link between the "Remote ID" box and the currently set IP address. If the IP address is changed, the new IP address is not entered in the "Remote ID" box automatically. Only the value of the "Remote ID Type" box changes to "Free Text". To use the current IP address again, select "IP Address" again in the "Remote ID Type" box. - MAC Address The MAC address of the device is used as the device ID. - Free Text If you use "Free Text", you can enter the device name as the device identifier in the "Remote ID" box. Remote ID The box can only be edited if you select the entry "Free Text" for "Remote ID Type". The remote IP must be unique. 850 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Circuit ID Type Select the type of circuit ID from the drop-down list. You have the following options: - Predefined The circuit ID is created automatically based on the router index, VLAN ID or port. - Free Number If you use "Free Number", you can enter the ID for "Circuit ID". Circuit ID Enter the circuit ID. The box can only be edited if you select the "Free Number" entry for the "Circuit ID Type". VRRP Router On this page, you create virtual routers. You can configure other parameters in "Layer 3 > VRRP > Configuration". Note VRRP is available only on layer 3. VRRP can only be used in conjunction with VLAN interfaces. Router ports are not supported. Select "VRRP" to configure VRRP Settings The following settings are available: VRRP Enable or disable routing using VRRP. React to pings on virtual interfaces When enabled, the virtual IP addresses also reply to the ping. Interface Select the interface operating as virtual router. VRID Enter the ID of the virtual router in the input box. This ID defines the group of routers that form a virtual router (VR). In the group, this is the same. it can no longer be used for other groups. The table has the following columns: Interface Shows the Interface that functions as the virtual router. VRID Shows the ID of the virtual router. WinCC Basic V13.0 System Manual, 02/2014 851 Editing devices and networks 8.1 Configuring devices and networks Virtual MAC Address Shows the virtual MAC address of the virtual router. Primary IP Address Shows the primary IP address in this VLAN. The entry 0.0.0.0 means that the "Primary" address on this VLAN is used. Otherwise all IP addresses configured in this VLAN in "Layer 3 > Subnets" are valid values. Router Status Shows the current status of the virtual router. Possible values are as follows: - Master The router is the master router and handles the routing functionality for all assigned IP addresses. - Backup The router is the backup router. If the master router fails, the backup router takes over the tasks of the master router. - Initialize The virtual router has just been turned on. It will soon change to the "Master" or "Backup" status. Master IP Address (only available online) Shows the IP address of the master router. Priority Shows the priority of the virtual router. The current master router is automatically given 255. All other priorities can be distributed freely among the VRRP routers. The higher the priority, the earlier the VRRP router becomes "Master". Advert. Internal Shows the interval at which the master router sends VRRP packets. Preempt Shows the precedence of a router when changing roles between backup and master. - yes This router has precedence when changing roles. - no This router does not have precedence when changing roles. Configuration Introduction On this page, you configure the virtual router. Note VRRP is available only on layer 3. 852 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Description of the displayed values The page contains the following boxes: Interface / VRID Select the ID of the virtual router to be configured. Primary IP Address Select the primary IP address. If the router becomes master router, the router uses this IP address. Note If you only configure one subnet on this VLAN, no entry is necessary. The entry is 0.0.0.0. If you configure more than one subnet on the VLAN and you want a specific IP address to be used as the source address for VRRP packets, select the IP address from the dropdown list. Otherwise, the IP address with priority will be used. Master If this option is enabled, the primary IP address is entered for "Associated IP Address". This means that the highest priority IP address of the VRRP router is used as the virtual IP address of the virtual master router. The option must be disabled for the backup routers in this group and the IP address of the router in "Assigned IP address" must be used. Priority Enter the priority of this virtual router. The current master router is always given 255. All other priorities can be distributed freely among the redundant routers. The higher the priority, the earlier the router becomes "Master". Advertisement Interval [s] Enter the interval in seconds after which a master router sends a VRRP packet again. Preempt lower priority master Allow the precedence when changing roles between Backup and Master based on the selection process. Address overview Overview This page shows which IP addresses the virtual router monitors. Note VRRP is available only on layer 3. WinCC Basic V13.0 System Manual, 02/2014 853 Editing devices and networks 8.1 Configuring devices and networks Settings The table has the following columns: Interface Shows the Interface that functions as the virtual router. VRID Shows the ID of this virtual router. Number of Addresses Shows the number of IP addresses. Associated IP Address (1) ... Associated IP Address (4) Shows the router IP addresses monitored by this virtual router. If a router takes over the role of master, the routing function is taken over by this router for all these IP addresses. Address configuration Note VRRP is available only on layer 3. Settings The following settings are possible: Interface / VRID Select the required virtual router. Associated IP Address Enter the IP address that the virtual router will monitor. The table has the following columns: Associated IP Address Shows the IP addresses that the virtual router monitors. OSPFv2 Configuration Introduction On this page, you configure routing with OSPF. Note OSPF is available only on layer 3. 854 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Settings OSPFv2 Enable or disable routing using OSPF. Router ID Enter the name of one of the OSPF interfaces. The name is entered in the IP address format and does not need to match the local IP address. OSPFv2 RFC1583 Compatibility Enable the option if you still have old OSPF routers in operation that are not compatible with RFC 2328. Border Router Shows the status of the OSPF router. If the local system is an active member in at least 2 areas, this is an area border router. AS Border Router Specify whether the router is an AS border router. An AS border router intercedes between multiple autonomous systems, for example if you have an additional RIP network. An AS border router is also necessary to add and to distribute static routes. New LSA Received (only available online) Shows the number of received LSAs. Updates and local LSAs are not counted. New LSA Configured (only available online) Number of different LSAs sent by this local system. External LSA Maximum To limit the number of entries of external LSAs in the database, enter the maximum number of external LSAs. Exit Interval [s] Enter the interval after which the OSPF router once again attempts to come out of the overflow status. A 0 means that the OSPF router attempts to exit the overflow status only following a restart. Inbound Filter Select a route map that filters inbound routes. WinCC Basic V13.0 System Manual, 02/2014 855 Editing devices and networks 8.1 Configuring devices and networks Redistribute Routes Specify which known routes are distributed using OSPF. The following types of route exist: - Default - Connected - Static - RIPv2 Note The settings can only be enabled on an AS border router. Enabling "Default" and "Static", in particular, can cause problems if they are enabled at too many points in the network, for example, forwarding loops. Route Map Select a route map that filters which routes are forwarded using OSPF. Areas Overview An autonomous system can be divided into smaller areas. On this page, you can view, create, modify or delete the areas of the router. Note OSPF is available only on layer 3. Settings Area ID Enter the ID of the area. The database is synchronized for all routers of an area. Input format: x.x.x.x x = 0 ... 255 This table contains the following columns: 856 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Area ID Shows the ID of the area. Area Type Select the area type from the drop-down list. - Normal - Stub - NSSA - Backbone Summary Specify whether summary LSAs are generated for this area. - Summary: Summary LSAs are sent to the area. - No Summary: Summary LSAs are not sent to the area. Metric Displays the costs for the OSPF interface. Updates Shows the number of recalculations of the routing tables. LSA Count Shows the number of LSAs in the database. Area BR Shows the number of reachable area border routers (ABR) within this area. AS BR Shows the number of reachable autonomous system border routers (ASBR) in this area. Area range Creating a new OSPFv2 area range On this page, networks can be grouped together under one area ID. The method is used only with area border routers. This means that an area border router only propagates one route for each address area to the outside. Note OSPF is available only on layer 3. WinCC Basic V13.0 System Manual, 02/2014 857 Editing devices and networks 8.1 Configuring devices and networks Settings Area ID Select the area ID. You configure the ID in "Layer 3 > OSPFv2 > Areas". Subnet Address Enter the address of the network that will be grouped. Subnet Mask Enter the subnet mask of the network that will be grouped. This table contains the following columns: Area ID Shows the ID of the area. Subnet Address Shows the address of the network that will be grouped with other networks. Subnet Mask Shows the subnet mask of the network that will be grouped with other networks. Advertise Enable this option to advertise the grouped network. Interfaces Overview On this page, you can configure OSPF interfaces. Note OSPF is available only on layer 3. Settings IP Address Select the IP address of the OSPF interface. Area ID Select the area ID of the area with which the OSPF interface is connected. Note For secondary address types, select the same Area ID as for the corresponding primary address type. The information whether an address type is primary or secondary can be found in the "Address Type" column on the "Subnets > Overview" page. This table contains the following columns: 858 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks IP Address Displays the IP address of the OSPF interface. Area ID Select the area ID with which the OSPF interface is connected. OSPF Status Specify whether or not OSPF is active on the interface. - Enabled: OSPF is enabled on the interface. - Disabled: OSPF is disabled on the interface Metric Enter the costs for the OSPF interface. Priority Enter the router priority. The priority is only relevant for selecting the designated router. This parameter can be selected differently on routers within the same subnet. Trans. Delay Enter the required delay when sending a connection update. Retrans. Delay Enter the time after which an OSPF packet is transferred again if no confirmation was received. Hello Interval Enter the interval between two Hello packets. Dead Interval Enter the interval after which the neighbor router is marked as "failed" if no more Hello packets are received from it during this time. Interface authentication Configuring the interface login On this page, you define the authentication of the interface. Note OSPF is available only on layer 3. WinCC Basic V13.0 System Manual, 02/2014 859 Editing devices and networks 8.1 Configuring devices and networks Settings OSPF Interface Select the OSPF interface for which you want to configure authentication. Authentication type Select the authentication method of the OSPF interface. You have the following options: - None: No authentication - simple: Authentication using an unencrypted password - MD5: Authentication using MD5 Simple authentication Password For "Simple authentication, enter the password if you have selected this type of authentication. Confirmation Confirm the entered password. MD5 authentication Authentication Key ID If you have selected this type of authentication, enter the ID for the MD5 authentication under which the password is used as the key. Since the key ID is transferred with the protocol, the same key must be stored under the same key ID on all neighboring routers. The table has the following columns: Authentication Key ID Can only be edited if you set the MD5 authentication method. It is only possible to use several keys there. MD5 Key Enter the MD5 key. Confirm MD5 Key Confirm the entered key. Youngest Key ID (only available online) Shows whether or not the MD5 key is the latest key ID. Virtual links Overview Due to the protocol, each area border router must have access to the backbone area. If a router is not connected directly to the backbone area, a virtual link to it is created. Note OSPF is available only on layer 3. 860 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Note Note that when creating a virtual link both the transit area and the backbone area must already be configured. the virtual link must be configured identically at both ends. Note Virtual links are not effective unless the device is an ABR. (only available online) This is displayed when at least one virtual link entry is configured and the device is not an area border router. Settings Neighbor Router ID Enter the ID of the neighbor router at the other end of the virtual connection. Transit Area ID Select the ID of the area that connects the two routers. This table contains the following columns: Transit Area ID Shows the ID via which the two routers are connected. Neighbor Router ID Shows the ID of the neighbor router at the other end of the virtual connection. Virt. Link Status Specify the status of the virtual link. The following statuses are possible: - down: The virtual link is inactive. - point-to-point: The virtual link is active. Trans. Delay Enter the required delay when sending a link update packet (in seconds). Retrans. Delay Enter the time after which a packet is transferred again if no confirmation was received (in seconds). Hello Interval Enter the interval between two Hello packets (in seconds). Dead Interval Enter the interval after which the neighbor router counts as "failed" if no more Hello packets are received from it during this time (in seconds). WinCC Basic V13.0 System Manual, 02/2014 861 Editing devices and networks 8.1 Configuring devices and networks Virtual Link Authentication Configuring the virtual link login On this page, you define the authentication for the virtual link. Note OSPF is available only on layer 3. Settings Virtual link (area/neighbor) Select the virtual link for which you want to configure authentication. Authentication type Select the authentication method of the OSPF interface. You have the following options: - None: No authentication - simple: Authentication using an unencrypted password. - MD5: Authentication using MD5 Simple authentication Password Enter the password for "simple authentication". Confirmation Confirm the entered password. MD5 authentication Authentication Key ID Enter the ID for MD5 authentication with which the password will be used as a key. Since the key ID is transferred with the protocol, the same key must be stored under the same key ID on all neighboring routers. The table has the following columns: Authentication Key ID Can only be edited if you set the MD5 authentication method. It is only possible to use several keys there. MD5 Key Enter the MD5 key. Confirm MD5 Key Confirm the entered key. Youngest Key ID Shows whether or not the MD5 key is the latest key ID. 862 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks RIPv2 Configuration On this page, you configure routing with RIP. Note RIPv2 is available only on layer 3. Settings RIPv2 Enable or disable routing using RIPv2. Inbound Filter Select a route map that filters inbound routes. Redistribute Routes Specify which known routes are distributed using RIPv2. The following types of route exist: - Static Default - Connected - Static - OSPF Route Map Select a route map that filters which routes are forwarded using RIPv2. Interfaces Overview On this page, you can configure RIPv2 interfaces. Note RIPv2 is available only on layer 3. Settings IP Address Select the IP address of the RIPv2 interface. This table contains the following columns: WinCC Basic V13.0 System Manual, 02/2014 863 Editing devices and networks 8.1 Configuring devices and networks IP Address Displays the IP address of the RIPv2 interface. Send Updates Select the way in which updates are sent: - no send No updates are sent. - RIPv1 Updates for RIPv1 are sent. - RIPv1-compat. RIPv2 updates are sent as broadcasts according to the rules of RIPv1. - RIPv2 Updates for RIPv2 are sent as multicasts. - RIPv1 demand/RIPv2 demand RIP packets are sent only as a response to an explicit query. Receive Updates Select the form in which received updates are accepted: - no receive No updates are received. - RIPv1 Only updates of RIPv1 are received. - RIPv2 Only updates of RIPv2 are received. - RIPv1/v2 Updates of RIPv1 and RIPv2 are received. Default Metric Enter the costs for the RIPv2 interface. Security Passwords Note The page is only available if there is an online connection to the device. Only the administrator can change the device passwords for administrator and users. The factory settings for the passwords when the devices ship are as follows: Administrator: admin User: user 864 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Note If you log on the first time or log on after a "Reset to factory defaults and restart", you will be prompted to change the password. Note Changing the password in "Trial" configuration mode Even if you change the password in "Trial" configuration mode, this change is saved immediately. Settings Current Admin Password Enter the valid administrator password. User name Select the required user. The following options are available: - Administrator: admin - User: user New Password Enter the new password. Password Confirmation Confirm the new password. AAA General The term "AAA" used in the menu stands for "Authentication, Authorization, Accounting" and is used to identify and allow network nodes, to provide them with the appropriate services and to determine the amount of use. On this page, you configure the login. WinCC Basic V13.0 System Manual, 02/2014 865 Editing devices and networks 8.1 Configuring devices and networks Settings Login Authentication Specify how the login is made: - Local Login with local user name and password. - RADIUS Login using a RADIUS server. RADIUS client The term "AAA" used in the menu stands for "Authentication, Authorization, Accounting" and is used to identify and allow network nodes, to provide them with the appropriate services and to determine the amount of use. Authentication over an external server The concept of RADIUS is based on an external authentication server. An end device can only access the network after the device has verified the logon data of the device with the authentication server. Both the end device and the authentication server must support the EAP protocol (Extensive Authentication Protocol). Each column of the table contains access data for one server. In the search order, the primary server is queried first. If the primary server cannot be reached, secondary servers are queried in the order in which they are entered. If no server responds, there is no authentication. The client has no access to the network although a link is indicated at the port. Settings The table has the following columns: Server IP Address Enter the IP address of the RADIUS server. Server Port Here, enter the input port on the RADIUS server. As default, input port 1812 is set. Shared Secret Enter your access ID. Confirm Shared Secret Enter your access ID again as confirmation. Max. Retrans Enter the maximum number of query attempts before another configured RADIUS server is queried or the login counts as having failed. As default, 3 is set. 866 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Primary Server Specify whether or not this server is the primary server. You can select one of the options "yes" or "no". Status Enable or disable the RADIUS server. Note You can configure a maximum of two servers on this page. 802.1x authenticator The term "AAA" used in the menu stands for "Authentication, Authorization, Accounting" and is used to identify and allow network nodes, to provide them with the appropriate services and to determine the amount of use. Enabling authentication for individual ports By selecting the check box, you specify whether or not network access protection according to IEEE 802.1x is enabled on this port. Settings MAC Authentication Enable or disable MAC authentication for the device. Guest VLAN Enable or disable the "Guest VLAN" function for the device. Table 1 has the following columns: 1st column Shows that the settings are valid for all ports of table 2. 802.1x Auth. Control Select the required setting. If "No Change" is selected, the entry in table 2 remains unchanged. 802.1x Re-authentication Select the required setting. If "No Change" is selected, the entry in table 2 remains unchanged. MAC Authentication Select the required setting. If "No Change" is selected, the entry in table 2 remains unchanged. Adopt RADIUS VLAN Assignment Select the required setting. If "No Change" is selected, the entry in table 2 remains unchanged. MAC Auth. Max Permitted Addresses Enter how many end devices are allowed to be connected to the port at the same time. If "No Change" is entered, the entry in table 2 remains unchanged. WinCC Basic V13.0 System Manual, 02/2014 867 Editing devices and networks 8.1 Configuring devices and networks Guest VLAN Select the required setting. If "No Change" is selected, the entry in table 2 remains unchanged. Guest VLAN ID Enter the VLAN ID of the port. If "No Change" is entered, the entry in table 2 remains unchanged. Guest VLAN max. Permitted Addresses Enter how many end devices are allowed in the guest VLAN at the same time. Transfer to table If you click the button, the settings are adopted for all ports of table 2. Table 2 has the following columns: Port Shows the port to which the setting relates. If a configuration is not possible for a port, it is displayed grayed out and you cannot modify the settings. 802.1x Auth. Control Specify the authentication of the port: - Force Unauthorized Data traffic via the port is blocked. - Force Authorized Data traffic via the port is allowed without any restrictions. Default setting - Auto End devices are authenticated on the port with the "802.1x" method. The data traffic via the port is permitted or blocked depending on the authentication result. 802.1x Re-authentication Enable this option if you want reauthentication of an already authenticated end device to be repeated cyclically. MAC Authentication Enable this option if you want end devices to be authenticated with the "MAC Authentication" method. Adopt RADIUS VLAN Assignment The RADIUS server informs the IE switch of the VLAN to which the port belongs. Enable this option if you want the information of the server to be taken into account. The port then belongs to the corresponding VLAN. If the option is disabled, the VLAN information is discarded. MAC Auth. Max Permitted Addresses Enter how many end devices are allowed to be connected to the port at the same time. Guest VLAN Enable this option if you want the end device to be permitted in the guest VLAN if authentication fails. Guest VLAN ID Enter the VLAN ID of the port. 868 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Guest VLAN max. Permitted Addresses Enter how many end devices are allowed in the guest VLAN at the same time. MAC Auth. Currently Permitted Addresses Shows the number of currently connected end devices. MAC Auth. Currently Blocked Addresses Shows the number of currently blocked end devices. Guest VLAN Currently Permitted Addresses Shows how many end devices are currently allowed in the guest VLAN. Port ACL MAC Rule configuration On this page, you specify the ACL rules for the MAC-based ACL. Settings The table has the following columns: Rule Number Shows the number of the ACL rule. When you create a rule, a new row with a unique number is created. Source MAC Enter the unicast MAC address of the source. Dest. MAC Enter the unicast MAC address of the destination. Action Select the action. The following is possible: - Forward If the frame complies with the ACL rule, the frame is forwarded. - Discard If the frame complies with the ACL rule, the frame is not forwarded. Ingress Port Shows a list of all ingress ports to which this rule applies. Egress Port Shows a list of all egress ports to which this rule applies. Note If you enter the address "00:00:00:00:00:00" for the source and/or destination MAC address, the rule created in this way applies to all source or destination MAC addresses. WinCC Basic V13.0 System Manual, 02/2014 869 Editing devices and networks 8.1 Configuring devices and networks Port ingress rules On this page, you specify the ACL rule according to which incoming frames are handled by the port. Settings Ports Select the required port. Add Rule Select the ACL rule to be assigned to the port. You specify the ACL rule on the "Rules Configuration" page. Add To permanently assign the ACL rule to the port, click the "Add" button. The configuration is shown in the table. Remove Rule Select the ACL rule to be deleted. Remove To remove the ACL rule from the port, click the "Remove" button. The table has the following columns: Rule Order Shows the order of the ACL rules. Rule Number Shows the number of the ACL rule. When you create a rule, a new row with a unique number is created. Source MAC Shows the unicast MAC address of the source. Dest. MAC Shows the unicast MAC address of the destination. Action Select the action. The following is possible: - Forward If the frame complies with the ACL rule, the frame is forwarded. - Discard If the frame complies with the ACL rule, the frame is not forwarded. Port egress rules On this page, you specify the ACL rule according to which outgoing frames are handled by the port. 870 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Description Ports Select the required port. Add Rule Select the ACL rule to be assigned to the port. You specify the ACL rule on the "Rules Configuration" page. Add To permanently assign the ACL rule to the port, click the "Add" button. The configuration is shown in the table. Remove Rule Select the ACL rule to be deleted. Remove To remove the ACL rule from the port, click the "Remove" button. The table has the following columns: Rule Order Shows the order of the ACL rules. Rule Number Shows the number of the ACL rule. When you create a rule, a new row with a unique number is created. Source MAC Shows the unicast MAC address of the source. Dest. MAC Shows the unicast MAC address of the destination. Action Select the action. The following is possible: - Forward If the frame complies with the ACL rule, the frame is forwarded. - Discard If the frame complies with the ACL rule, the frame is not forwarded. Port ACL IP Rule configuration On this page, you specify the rules for the IP-based ACL. WinCC Basic V13.0 System Manual, 02/2014 871 Editing devices and networks 8.1 Configuring devices and networks Settings The table has the following columns: Rule Number Shows the number of the ACL rule. When you create a rule, a new row with a unique number is created. Source IP Enter the IP address of the source. Source Subnet Mask Enter the subnet mask in which the source is located. Dest. IP Enter the IP address of the destination. Dest. Subnet Mask Enter the subnet mask in which the destination is located. Action Select the action from the drop-down list. The following is possible: - Forward If the frame complies with the ACL rule, the frame is forwarded. - Discard If the frame complies with the ACL rule, the frame is not forwarded. Ingress Port Shows a list of all ingress ports to which this rule applies. Egress Port Shows a list of all egress ports to which this rule applies. Protocol configuration On this page, you specify the rules for protocols. Settings The table has the following columns: Rule Number Shows the number of the protocol rule. When you create a rule, a new row with a unique number is created. Protocol Select the protocol for which this rule is valid. Protocol Number Enter a protocol number to define further protocols. This box can only be edited if you have set "Other Protocol" for the protocol. Source Port Min. Enter the lowest possible port number of the source port. This box can only be edited if you have set "TCP" or "UDP" for the protocol. 872 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Source Port Max. Enter the highest possible port number of the source port. This box can only be edited if you have set "TCP" or "UDP" for the protocol. Dest. Port Min. Enter the lowest possible port number of the destination port. This box can only be edited if you have set "TCP" or "UDP" for the protocol. Dest. Port Max. Enter the highest possible port number of the destination port. This box can only be edited if you have set "TCP" or "UDP" for the protocol. Message Type Enter a message type to decide the format of the message. This box can only be edited if you have set "ICMP" for the protocol. Message Code Enter a message code to specify the function of the message. This box can only be edited if you have set "ICMP" for the protocol. DSCP Enter a value for classifying the priority. This box cannot be edited if you have set "ICMP" for the protocol. Port ingress rules On this page, you specify the ACL rule according to which incoming frames are handled by the port. Settings Ports Select the required port. Add Rule Select the ACL rule to be assigned to the port. You specify the ACL rule on the "Rules Configuration" page. Add To permanently assign the ACL rule to the port, click the "Add" button. The configuration is shown in the table. Remove Rule Select the ACL rule to be deleted. Remove To remove the ACL rule from the port, click the "Remove" button. The table has the following columns: Rule Order Shows the order of the ACL rules. Rule Number Shows the number of the ACL rule. When you create a rule, a new row with a unique number is created. WinCC Basic V13.0 System Manual, 02/2014 873 Editing devices and networks 8.1 Configuring devices and networks Protocol Shows the protocol for which this rule is valid. Protocol Number Shows the protocol number. Source IP Shows the IP address of the source. Source Subnet Mask Shows the subnet mask in which the source is located. Dest. IP Enter the IP address of the destination. Dest. Subnet Mask Enter the subnet mask in which the destination is located. Action Select the action. The following is possible: - Forward If the frame complies with the ACL rule, the frame is forwarded. - Discard If the frame complies with the ACL rule, the frame is not forwarded. Source Port Min. Shows the lowest possible port number of the source port. Source Port Max. Shows the highest possible port number of the source port. Dest. Port Min. Shows the lowest possible port number of the destination port. Dest. Port Max. Shows the highest possible port number of the destination port. Message Type Shows the message type. Message Code Shows the message code. DSCP Shows the value for classifying the priority. Port egress rules On this page, you specify the ACL rule according to which outgoing frames are handled by the port. 874 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Settings Ports Select the required port. Add Rule Select the ACL rule to be assigned to the port. You specify the ACL rule on the "Rules Configuration" page. Add To permanently assign the ACL rule to the port, click the "Add" button. The configuration is shown in the table. Remove Rule Select the ACL rule to be deleted. Remove To remove the ACL rule from the port, click the "Remove" button. The table has the following columns: Rule Order Shows the order of the ACL rules. Rule Number Shows the number of the ACL rule. When you create a rule, a new row with a unique number is created. Protocol Shows the protocol for which this rule is valid. Protocol Number Shows the protocol number. Source IP Shows the IP address of the source. Source Subnet Mask Shows the subnet mask in which the source is located. Dest. IP Enter the IP address of the destination. Dest. Subnet Mask Enter the subnet mask in which the destination is located. Action Select the action from the drop-down list. The following is possible: - Forward If the frame complies with the ACL rule, the frame is forwarded. - Discard If the frame complies with the ACL rule, the frame is not forwarded. Source Port Min. Shows the lowest possible port number of the source port. Source Port Max. Shows the highest possible port number of the source port. WinCC Basic V13.0 System Manual, 02/2014 875 Editing devices and networks 8.1 Configuring devices and networks Dest. Port Min. Shows the lowest possible port number of the destination port. Dest. Port Max. Shows the highest possible port number of the destination port. Message Type Shows the message type. Message Code Shows the message code. DSCP Shows the value for classifying the priority. Management ACL On this page, you can increase the security of your device. To specify which station with which IP address is allowed to access your device, configure the IP address or an entire address range. You can select the protocols and the ports of the station with which it is allowed to access the device. You define the VLAN in which the station may be located. This ensures that only certain stations within a VLAN have access to the device. Note Note that a bad configuration may mean that you can no longer access the device. Settings Management ACL Enable or disable the function. IP Address Enter the IP address or the network address to which the rule will apply. If you use the IP address 0.0.0.0, the settings apply to all IP addresses. Subnet Mask Enter the subnet mask. The subnet mask 255.255.255.255 is for a specific IP address. If you want to allow a subnet, for example a C subnet, enter 255.255.255.0. The subnet mask 0.0.0.0 applies to all subnets. The table has the following columns: Rule Order Shows the number of the ACL rule. When you create a rule, a new row with a unique number is created. IP Address Shows the IP address. Subnet Mask Shows the subnet mask. 876 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks VLANs Allowed Enter the number of the VLAN from which access is allowed. Only stations located in these VLANs can access the device. If this input box remains empty, there is no restriction. You can enter several individual VLANs and VLAN ranges separated by commas, for example 1,5,10-12. SNMP Specify whether the station or the IP address can access the device using the SNMP protocol. TELNET Specify whether the station or the IP address can access the device using the TELNET protocol. HTTP Specify whether the station or the IP address can access the device using the HTTP protocol. HTTPS Specify whether the station or the IP address can access the device using the HTTPS protocol. SSH Specify whether the station or the IP address can access the device using the SSH protocol. Px.y Specify whether the station or the IP address can access this device via this port. 8.1.4.6 Configuring PROFIBUS DP The basics of configuring a DP master system Distributed I/O DP master systems that consist of a DP master and DP slaves which are connected via a bus and communicate with one another via the PROFIBUS DP protocol are referred to as distributed I/O. Firmware version of the S71200 CPU Use of the PROFIBUS functions with the S71200, requires CPUs with firmware version 2.0 or higher. Configuring distributed I/O Since DP masters and DP slaves are different devices, these instructions only provide a basic configuration procedure. However, the process for configuring distributed I/O is practically identical to that of non-distributed configuration. WinCC Basic V13.0 System Manual, 02/2014 877 Editing devices and networks 8.1 Configuring devices and networks Creating the DP master system in the network view After you have used dragged a DP master and a DP slave (for example, a CM 12435 and a CM 12435) from the hardware catalog to the network view, connect them both to a PROFIBUS subnet. Additional information Observe additional information on the scope of functions in the manuals of the respective device. DP slaves within the hardware catalog DP slaves within the hardware catalog You will find the DP slaves in the "Distributed I/O" folder of the hardware catalog. Compact and modular DP slaves are located there: Compact DP slaves Modules with integrated digital/analog inputs and outputs, for example, ET 200L Modular DP slaves (Interface modules with S7 modules assigned, for example, ET 200M The available DP master and the desired functionality will determine which DP slaves can be used. I slaves within the hardware catalog The CM 1242-5 is, for example, an DP slave that can be configured as intelligent DP slave. You can find it in the hardware catalog at: CM 12425 "PLC > SIMATIC S7 1200 > Communication module > PROFIBUS" DP/DP coupler in the hardware catalog Introduction A DP/DP coupler connects two PROFIBUS DP networks as a gateway so that the DP master from one network can transfer data to the DP master of the other network. The maximum amount of data that can be transferred is 244 bytes input data and 244 bytes output data. DP/DP coupler in the hardware catalog Details of a DP/DP coupler as gateway between two DM master systems are contained in the hardware catalog in the folder "Other field devices > PROFIBUS-DP > Gateways". 878 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Configuring the DP/DP coupler DP/DP couplers are configured in both PROFIBUS networks, each in their own master systems. The input and output areas of both networks must thereby be matched to one another. The output data from one end of the DP/DP coupler are accepted as input data at the other respective end and vice versa. Configurations involving PROFIBUS DP Configurations involving basic DP slaves Communication between DP master and DP slave In the case of a configuration involving simple DP slaves, data is exchanged between the DP master and simple DP slaves, i.e. with I/O modules via the DP master. The DP master sequentially polls each DP slave configured within the DP master system and contained in its polling list. In doing so, it transfers the output data to the slaves and receives their input data in return. Mono-master system The configuration with only one DP master is also described as mono-master system. A single DP master with its associated DP slaves is connected to a physical PROFIBUS DP subnet. '3PDVWHUV\VWHP '3PDVWHU '3VODYH WinCC Basic V13.0 System Manual, 02/2014 '3VODYH '3VODYH 879 Editing devices and networks 8.1 Configuring devices and networks Configurations involving intelligent DP slaves Definition DP slaves that feature their own preprocessing program are referred to as intelligent DP slaves (I-slaves). CM 1242-5 is an intelligent DP slave. I-slave <> DP master data exchange A higher-level automation system processes the automation task, which is broken down into sub-tasks. The sub-tasks are processed in the lower-level automation systems. The necessary control tasks are processed separately and efficiently in the CPUs as preprocessing programs. In the case of configurations involving intelligent DP slaves, the DP master only accesses the operand area of the I-slave's CPU, and not the I/O modules of the intelligent DP slave. The operand area must not be assigned to any actual I/O modules in the I-slave. The assignment must be made during I-slave configuration. The addresses of the data to be exchanged between the master and slave are configured in the transfer area of the I-slave. '3PDVWHUV\VWHP '3PDVWHU 'DWDH[FKDQJH '3VODYH '3VODYH '3VODYH ,VODYH Configuring distributed I/O systems Hint: Quick configuration of master systems If the DP master system has several DP slaves, use drag-and-drop operation to assign to the master in one step all DP slaves that were placed. 880 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Requirements DP master and DP slaves are placed in the network view. Assigning DP slaves to a DP master system To do this, follow these steps: 1. Select an appropriate zoom factor so that you can see as many DP slaves as possible in the network view. 2. Arrange the DP slaves in a maximum of two rows. 3. Select all DP interfaces with the mouse cursor (not all devices!). This only works if you begin to drag the mouse cursor outside of the first DP slave and release the mouse button at the last DP slave (selection with the lasso). 4. Select the shortcut menu "Assign to new master" and select the corresponding DP interface for the DP master in the subsequent dialog. 5. The DP slaves are automatically networked with the DP master and combine with it to form a DP master system. Note When a DP master system is highlighted, you can double-click on a DP slave in the hardware catalog and thereby quickly add additional DP slaves. This will result in the DP slave being added to the highlighted DP master system automatically. WinCC Basic V13.0 System Manual, 02/2014 881 Editing devices and networks 8.1 Configuring devices and networks Creating a DP master system Introduction To create a DP master system, you need to have one DP master and at least one DP slave. As soon as you connect a DP master to a DP slave, a master-slave link is established. DP master You can use any of the following devices as a DP master: CM 12435 Requirement You must be in the network view. The hardware catalog is open. Procedure To create a DP master system, follow these steps: 1. Select a DP master from the hardware catalog. 2. Pull the DP master onto the free area within the network view. 3. Right-click on the DP master's DP interface. 4. Select "Create master system" from the shortcut menu. A DP master system with one DP master will be created as a single node. If you connect a DP slave's DP interface to that of the DP master, the DP slave will be added to the master system. 882 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Assuming that you have already placed both a DP master and a DP slave within the network view, you can drag-and-drop to connect the two and thereby create a DP master system. To do so, follow these steps: 1. Click on the DP interface of either the DP master or DP slave. 2. Hold down the mouse button and draw a connecting line between this DP interface and that of the desired communication partner. This will create a subnet with one DP master system between the DP master and DP slave. WinCC Basic V13.0 System Manual, 02/2014 883 Editing devices and networks 8.1 Configuring devices and networks DP master display on the DP slave When you connect a DP slave to a DP master, the name of the DP master is displayed on the DP slave as a hyperlink. Click the hyperlink to select the associated DP master. Highlighting applied to the DP master system When you create a new DP master system, highlighting will be applied to it. This enables you to identify quickly which devices belong to the DP master system. You can also highlight a DP master system yourself by moving the mouse pointer over a subnet. This will result in the names of the available DP master systems being displayed. Click the required DP master system to highlight it. There are various ways of removing the highlighting from a DP master system: Highlight a different master system. Click on the drawing pin with the name of the master system in the top right-hand corner of the network view. 884 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Editing DP master systems and interfaces Introduction Once you have created a DP master system, you also have the option of disconnecting the DP master system from its components. This can result in subnets with DP slaves but without DP master. Generally, there is no need to edit the interfaces of a DP master. You can change the name and number on the DP master system. Disconnection of master or slaves from the DP master system If you have configured a PROFIBUS CP as a DP master with master system, you can then disconnect the DP master system from the DP master. After this, the device will no longer be connected to the DP master system. Disconnecting the subnet from a DP master effectively eliminates the master system in the sense that it is no longer assigned to a DP master. However, the individual DP slaves are still interconnected via the subnet. If you delete the DP slaves or disconnect them from the master system, the master system is then retained on the DP master. Requirement You must be in the network view. There has to be a DP master system with one DP master and at least one DP slave. Disconnecting the DP master from the DP master system To disconnect the DP master system, proceed as follows: 1. Right-click on the DP master's DP interface. 2. Select "Disconnect from master system" from the shortcut menu. The selected DP master will be disconnected from the DP master system. A subnet with the DP slaves will be retained. Adding a DP master to the DP master system To reassign a DP master to a subnet, proceed as follows: 1. Right-click on the DP master's DP interface. 2. Select "Create master system" from the shortcut menu. 3. Draw connecting lines between the new DP master system and the DP interfaces of the DP slaves. The DP master combines with the DP slaves to recreate a DP master system. WinCC Basic V13.0 System Manual, 02/2014 885 Editing devices and networks 8.1 Configuring devices and networks Editing the properties of a DP master system To edit the properties of a DP master system, proceed as follows: 1. Move the mouse pointer over a subnet with a DP master system. 2. A message will appear displaying the available DP master systems. Click the one you want to edit. The DP master system will now be color-highlighted. 3. Click on the highlighted DP master system. 4. In the inspector window, edit the DP master system attributes under "Properties > General". Note If you click a subnet when no DP master system is highlighted, you will be able to edit the properties of the entire subnet under "Properties" in the inspector window. Adding DP slaves to the master system and configuring them In the network view, you can add various DP slaves from the hardware catalog directly by using the drag-and-drop function or by double-clicking. DP slaves For configuration purposes, DP slaves are broken down into the following categories: Compact DP slaves (Modules with integrated digital/analog inputs and outputs, for example, ET 200L) Modular DP slaves (interface modules with S5 or S7 modules assigned, for example ET 200M) Intelligent DP slaves (I slaves) (CM 12425 or ET 200S with IM 151-7 CPU) Rules Your DP master system should only contain one DP master, but it may contain one or or more DP slaves. You may only configure as many DP slaves in a DP master system as are permitted for the specific DP master. Note When configuring the DP master system, remember to observe the DP master technical data (max. number of nodes, max. number of slots, max. quantity of user data). User data restrictions may possibly prevent you from being able to use the maximum number of nodes that is theoretically possible. 886 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Requirements You must be in the network view. A DP master system must have been created. Adding a DP slave to the DP master system To add a DP slave from the hardware catalog to the DP master system, follow these steps: 1. Select a DP slave from the hardware catalog. 2. Drag-and-drop the DP slave from the hardware catalog into the network view. 3. Draw a connecting line between the DP master's DP interface or a highlighted DP master system and the DP interface of the new DP slave. A DP master system will be created and the DP slave will be connected to the DP master automatically. Note When a DP master system is highlighted, you can double-click the required DP slave in the hardware catalog. This will result in the DP slave being added to the highlighted DP master system automatically. Disconnecting a DP slave from the DP master system To disconnect a DP slave from the DP master system, follow these steps: 1. In the network view, right-click on the DP slave's DP interface. 2. From the shortcut menu, select the method for disconnecting from the DP master system: - "Disconnect from subnet": The PROFIBUS connection is broken and the device is no longer connected to the DP master system or a subnet. - "Disconnect from master system": The DP slave remains connected to the subnet, but is no longer assigned to the DP master system as a DP slave. The selected DP slave will be disconnected from the DP master system. Assigning a DP slave to a new DP master system To assign an existing DP slave to a new DP master system, follow these steps: 1. Right-click on the DP slave's DP interface. 2. From the shortcut menu, select "Assign to new master". It does not matter whether the DP slave concerned is already assigned to another DP master system. 3. From the selection list, select the DP master whose DP master system is to have the DP slave connected to it. The selected DP slave is now assigned to a new DP master system. WinCC Basic V13.0 System Manual, 02/2014 887 Editing devices and networks 8.1 Configuring devices and networks The "Assign to new subnet" function works in a similar way in that it allows you to connect a DP slave to a new subnet. However, in this case, the DP slave will not be connected to an existing DP master system. Configuring a DP slave To configure a DP slave, follow these steps: 1. Switch to the DP slave's device view. 2. Select the module you want. 3. Configure the DP slave in the Inspector window. Configuring intelligent DP slaves Adding an I-slave to a DP master system Introduction One of the characteristics of an intelligent DP slave (I-slave) is that the DP master is not provided with I/O data directly by a real I/O, but by a preprocessing CPU. Together with the CP, this preprocessing CPU forms the I-slave. '3PDVWHU ,QWHOOLJHQW'3VODYH 7UDQVIHUDUHD 2SHUDQGDUHD ,4 &0 &38 &0 2SHUDQGDUHD ,4 &38 352),%86 Difference: DP slave v. intelligent DP slave In the case of a DP slave, the DP master accesses the distributed I/O directly. In the case of an intelligent DP slave, the DP master actually accesses a transfer area in the I/O address space of the preprocessing CPU instead of accessing the connected I/O of the 888 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks intelligent DP slave. The user program running on the preprocessing CPU is responsible for ensuring data exchange between the address area and I/O. Note The I/O areas configured for data exchange between the DP master and DP slaves must not be used by I/O modules. Applications Configurations involving intelligent DP slaves: I-slave <> DP master data exchange Procedure To add an I-slave to a DP master system, follow these steps: 1. In the network view, drag from the hardware catalog to a station one CM 1242-5 as an Islave and one CM 1243-5 as a DP master. 2. Draw a connecting line between the DP interfaces of both devices. This way you connect the I-slave with a DP master in a DP master system. Result: You have now set up a DP master system with one DP master and one I-slave. Configuring access to I slave data Data access The following applies to the CP 1242-5 in its function as I-slave: The addresses for the data transfer area and the address for the I/O modules in the I-slave differ. This means that the start address occupied by an I/O module can no longer be used for the transfer memory. If the higher-level DP master is to access the data of an I/O module in the I-slave, you must configure this data exchange between the I/O module and transfer area in the I-slave user program. '3PDVWHU 2SHUDQGDUHD ,4 &0 ,QWHOOLJHQW'3VODYH 7UDQVIHUDUHD &38 &0 2SHUDQGDUHD ,4 &38 ,2 352),%86 WinCC Basic V13.0 System Manual, 02/2014 889 Editing devices and networks 8.1 Configuring devices and networks Configuration of the transfer area for the CM 1242-5 (transfer area) With CM 12425, the transfer area for the cyclic PROFIBUS data exchange is configured as transfer area in the parameter group "PROFIBUS interface > Mode > I Slave Communication". Direct data access from CPU to CPU Direct data access from CPU to CPU via PROFIBUS is supported by the S7-1200 PROFIBUS CMs only via the PUT/GET services. Configuring DP slaves as distributed I/O devices Configuring an ET 200S Slot rules for configuring an ET 200S The following rules apply when configuring an ET 200S: Do not leave any gaps when inserting the ET 200S modules. Slot 1: only for PM-E or PM-D Power Modules. To the left of an Electronics Module (EM): an EM or a Power Module (PM-E or PM-D) only. To the left of Motor Starter (MS): an MS, a PM-D, PM-D Fx (1..x..4) Power Module or a PMX Power Module only. To the left of a PM-X: a motor starter or a PM-D only Up to 63 modules and one IM Interface Module are permitted Note Remember to ensure that the correct PM-E and EM voltage ranges are assigned. Configuring reference junctions A reference junction is the connection of a thermocouple to a supply line (generally in the terminal box). The voltage that occurs due to the effects of temperature falsifies the temperature value measured by the module. On the ET 200S, one channel of the AI RTD module can be programmed as a reference junction. Other AI TC modules can correct their measured values using the temperature at the reference junction as measured by this module. 890 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks 7KHUPRFRXSOH 5HIHUHQFHMXQFWLRQ 7HPSHUDWXUHPHDVXULQJ PRGXOH $,7& 7HPSHUDWXUHPHDVXULQJ PRGXOH $,57' 5HIHUHQFHMXQFWLRQ &RPSHQVDWLRQ Configuring the AI TC: Selection of the reference junction used Configuring of the AI RTD: Activation of the reference junction Specifying the slot and channel of the AI RTD Special characteristics to be noted when assigning parameters for reference junctions The process of assigning parameters for reference junctions will be explained based on the example of a resistance thermometer with a Pt 100 climatic range that is used for measuring the reference junction temperature. To assign parameters for the reference junction, follow these steps: 1. In the ET 200S device view, insert an analog electronics module, for example a 2AI RTD HF. 2. Select the module on the rack. 3. Under "Properties > Inputs" in the inspector window, set a channel for the reference junctions function to the "RTD-4L Pt 100 climatic range" measuring range. 4. Select the ET 200S. 5. Under "Properties > Module parameters > Reference junctions" in the inspector window, select the "Reference junction" check box and specify the slot and channel number of the relevant RTD module. 6. Insert the analog electronics module for measuring the temperature using a thermocouple (TC module) and parameterize it with the reference junction number of the RTD module. Additional information For additional information on the various types and uses of ET 200S modules, please refer to the operating instructions and the manual titled "ET 200S Distributed I/O System". For additional information on analog value processing, please see the documentation for the ET 200S distributed I/O system. WinCC Basic V13.0 System Manual, 02/2014 891 Editing devices and networks 8.1 Configuring devices and networks Packing addresses Introduction DP slaves and I/O devices from the ET 200S family are configured in the same way as other modular DP slaves and I/O devices. As well as supporting all the standard modular DP slave and I/O device functions, the ET 200S also offers the "Pack addresses" function: When digital electronics modules requiring an address space of 2 or 4 bits are inserted into the device view, they will initially be spread over a total area of 1 byte. However, the address area actually occupied can be compressed after configuration using the "Pack addresses" function. Initial state After "Pack addresses" Module I address I address 2DI (2-bit) Byte 10 10.0...10.1 4DI (4-bit) Byte 11 10.2...10.5 Requirements You are in the device view. An ET 200S, for example an IM 151-1, must be present. A pair of digital electronics modules, for example 2DI AC120V ST, must be inserted into the slots. Packing addresses To pack addressed, follow these steps: 1. Select the electronics modules whose addresses are to be packed. The following options are available for selecting multiple electronics modules: - Press and hold down <Shift> or <Ctrl> while clicking the relevant electronics modules. - Click off the rack and select the required electronics modules by drawing round them with the mouse. 2. Click "Pack addresses" in the shortcut menu for the selected electronics modules. The address areas for inputs, outputs and motor starters are packed separately. The packed addresses will be displayed in the I address and Q address columns of the device overview. 892 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks How packed addresses are generated and structured If you make use of the "Pack addresses" function, the addresses of the selected electronics modules will be packed in accordance with the following rules: The start of the address area is determined by the lowest address of the selected electronics modules: X.0 If the bit address is not "0", then the next (free) byte address as of which the selected area can be compacted will be selected automatically: (X+n).0 If no coherent area exists, the addresses will be automatically packed into any available address gaps. Electronics modules with packed addresses and the same byte address form a packing group. Unpacking addresses To unpack addressed, follow these steps: 1. Select one or more electronics modules with packed addresses. 2. Click "Unpack addresses" in the shortcut menu for the selected electronics modules. The packing groups of the selected electronics modules will be disbanded and the packed addresses for the relevant electronics modules unpacked. The packing group will also be disbanded and the packed addresses unpacked in the following cases: if you delete electronics modules from a packing group, move electronics modules out of a packing group or insert electronics modules on a free slot within a packing group. The start addresses of the unpacked electronics modules will be assigned to the next available byte addresses in each case. Special characteristics of electronics modules with packed addresses The following special characteristics apply to electronics modules with packed addresses: As far as the CPU is concerned, there is no way of assigning a slot for the electronics module. Consequently, the instruction GADR_LGC (SFC 5) outputs error information W#16#8099 "Slot not configured" for the actual slot of the electronic module. The instruction LGC_GADR (SFC 49) and SZL-ID W#16#xy91 "module status information" cannot be evaluated for an electronics module. The electronics module receives an additional diagnostics address via the DPV1 function, because otherwise the packed addresses would prevent interrupts from being assigned as far as the CPU is concerned. The "Insert/remove interrupt" is not possible. This is because the "Pack addresses" and "Insert/remove interrupt" functions are mutually exclusive. Configuring option handling with standby modules You can use the option handling function to prepare the ET 200S with PROFIBUS interface for future expansions (options). This section describes option handling with standby modules. WinCC Basic V13.0 System Manual, 02/2014 893 Editing devices and networks 8.1 Configuring devices and networks You do this by assembling, wiring, configuring, and programming the maximum configuration envisaged for the ET 200S and by using cost-effective standby modules (138-4AA00 or 138-4AA10) during assembly until it becomes time to replace them with the necessary electronics modules. Note The ET 200S can be completely factory-wired with the master cabling, as no connection exists between a standby module and the terminals of the terminal module (and, in turn, to the process). Requirement ET 200S interface module - IM 151-1 STANDARD (6ES7 151-1AA03-0AB0 or higher) - IM 151-1 FO STANDARD (6ES7 151-1AB02-0AB0 or higher) Power module with option handling - PM-E DC24..48V - PM-E DC24..48V/AC24..230V Procedure To activate option handling, follow these steps: 1. Select the IM 151-1 in the device view and enable it in "Option handling" check box under "Properties > General > Option handling" in the inspector window. 2. Select the numbered check boxes for the slots that are initially to accommodate the standby modules prior to the future electronics modules. 3. Select the power module in the device view and enable it in the "Option handling" check box under "Properties > Addresses" in the inspector window. Reserve the necessary address space for the control and check-back interface in the process image output (PIQ) and process image input (PII). The assembled standby modules can be replaced with the configured modules at a later date without having to modify the configuration. Note The addresses for these interfaces are reserved as soon as you activate option handling on the power module. The "Option handling" function must also be activated on the DP slave (IM 151-1 STANDARD Interface Module). If it is not activated, the addresses reserved for the control and check-back interface will be released again. Note that activating and deactivating the option handling function repeatedly can change the address of the control and check-back interface. Option handling may be activated for one PM-E DC24..48V or one PM-E DC24..48V/ AC24..230V Power Module only. 894 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Additional information For additional information on the assignment and significance of bytes within the process image, option handling with PROFIBUS and the use of standby modules, please refer to the documentation for the ET 200S distributed I/O system. How option handling works during startup If "Startup when expected/actual config. differ" is not available, the ET 200S will still start up if a standby module is inserted instead of the configured electronics module and option handling has been activated for the slot concerned. How option handling works during operation During operation, the option handling mode varies in accordance with the following: Option handling enabled for a slot: Either the standby module (option) or the configured electronics module can be plugged into this slot. If any other kind of module is present on this slot, diagnostics will be signaled (no module/incorrect module). Option handling disabled for a slot: Only the configured electronics module can be plugged into this slot. If any other kind of module is present, diagnostics will be signaled (no module/incorrect module). Standby module substitute values Substitute value for digital inputs: 0 Substitute value for analog inputs: 0x7FFF Control and evaluation in the user program The ET 200S is equipped with a control and feedback interface for the "Option handling" function. The control interface is located in the process image output (PIQ). Each bit in this address area controls one of the slots from 2 to 63: Bit value = 0: Option handling parameterized. Standby modules are permitted. Bit value = 1: Option handling canceled. Standby modules are not permitted on this slot. The check-back interface is located in the process image input (PII). Each bit in this address area provides information about the modules that are actually plugged into slots 1 to 63: Bit value = 0: This slot has the standby module, an incorrect module or no module plugged into it. Bit value = 1: The configured module is plugged into this slot. See also Which modules support option handling? (http://support.automation.siemens.com/WW/view/ en/22564754) WinCC Basic V13.0 System Manual, 02/2014 895 Editing devices and networks 8.1 Configuring devices and networks Configuring option handling without standby modules You can use the option handling function to prepare the ET 200S for future expansions (options) without installing standby modules. This section describes option handling without standby modules. Note ET 200S with PROFINET interface This description refers to the ET 200S with PROFIBUS interface. In principle, option handling for ET 200S with PROFINET interface functions as described here without standby modules. PN interface modules are to be used instead of the DP interface modules listed here. You can find additional information about option handling for ET 200S with PROFINET interface in the corresponding manuals. Requirement ET 200S interface module - IM 151-1 HIGH FEATURE (6ES7151-1BA02 or higher) - IM 151-1 STANDARD (6ES7 151-1AA05-0AB0 or higher) Power module with option handling - PM-E DC24..48V - PM-E DC24..48V/AC24..230V 896 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Procedure To activate option handling, follow these steps: 1. Select the IM 151-1 in the device view and enable it in "Option handling" check box under "Properties > General > Option handling" in the inspector window. 2. Select the power module in the device view and enable it in the "Option handling" check box under "Properties > Addresses" in the inspector window. Reserve the necessary address space for the control and check-back interface in the process image output (PIQ) and process image input (PII). 3. Configure the slave's maximum configuration. The selection/clearing of options is controlled via the user program. Note The addresses for these interfaces are reserved as soon as you activate option handling on the power module. The "Option handling" function must also be activated on the DP slave (IM 151-1 interface module). If it is not activated, the addresses reserved for the control and check-back interface will be released again. Note that activating and deactivating the option handling function repeatedly can change the address of the control and check-back interface. Option handling may be activated for one PM-E DC24..48V or one PM-E DC24..48V/ AC24..230V Power Module only. Additional information For additional information on the assignment and significance of bytes within the process image, option handling with PROFIBUS and the use of standby modules, please refer to the documentation for the ET 200S distributed I/O system. Control and evaluation in the user program The ET 200S is equipped with a control and feedback interface for the "Option handling" function. The control interface is located in the process image output (PIQ). Each bit in this address area controls one of the slots from 1 to 63: Bit value = 0: Slot is not available in the actual configuration. Bit value = 1: Slot is available in the actual configuration. The check-back interface is located in the process image input (PII). Each bit in this address area provides information about the modules that are actually plugged into slots 1 to 63: Bit value = 0: Slot belongs to an option that is not available or module status is faulty. Bit value = 1: The configured module is plugged into this slot. See also Sample applications for ET 200S, option handling without standby module (http:// support.automation.siemens.com/WW/view/en/29430270) WinCC Basic V13.0 System Manual, 02/2014 897 Editing devices and networks 8.1 Configuring devices and networks Configuring the ET 200S in DPV1 mode PROFIBUS DPV1 enables you to access extended PROFIBUS functions. Requirement You must be in network view. A DP master with DPV1 functionality must be available. A master-slave connection must be established with PROFIBUS. Procedure To switch the DP slave over to DPV1, follow these steps: 1. Select the DP slave. 2. Under "Properties > Module parameters" in the Inspector window, select "DPV1" mode from the "DP interrupt mode" drop-down list. or 1. Select the DP master. 2. In the I/O communications table, select the row with the connection between the DP master and the desired DP slave. 3. Under "Properties > Module parameters" in the Inspector window, select "DPV1" mode from the "DP interrupt mode" drop-down list. Special characteristics The parameters are subject to interdependencies, which are outlined below: Parameter DPV0 mode DPV1 mode Operation when target configuration does not match actual configuration Fully available Fully available Diagnostics interrupt (OB 82) Not available, not set Fully available Hardware interrupt (OB 40 to 47) Not available, not set Fully available Insert/remove interrupt (OB 83) Only available when addresses are not packed. Not available, not set "Startup when target configuration does not match actual configuration" is activated automatically along with an insert/remove interrupt. Interrupts in the case of modules with packed addresses If the module is capable of triggering interrupts and the bit address is not equal to 0 because of packed addresses, you will need to assign a diagnostics address in the ET 200S address dialog. 898 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks The diagnostics address is required for the purpose of assigning a DPV1 interrupt to the module as an interrupt trigger. The CPU will only be able to assign an interrupt correctly and store information on the interrupt in the interrupt OB start information/in the diagnostics buffer if the module concerned has this "unpacked" address. In this context, the CPU cannot make use of "packed" addresses. From the point of view of interrupt processing (interrupt OB), this means the module will have the assigned diagnostics address, but from the point of view of processing the input and output data in the user program, the module will have the packed addresses. Note When the module addresses are packed, the insert/remove interrupt for the ET 200S is unavailable. Using GSD files GSD revisions What you need to know about GSD revisions The properties of DP slaves are made available to configuration tools by means of GSD files. Functional enhancements in the area of the distributed I/O will have an effect on the GSD specification, for example, they will require the definition of new keywords. This results in the versioning of the specification. In the case of GSD files, the version of the specification on which a GSD file is based is called a "GSD revision". From GSD revision 1, the GSD revision must be included as a keyword "GSD_revision" in GSD files. GSD files without this keyword will therefore be interpreted by configuration tools as GSD revision "0". GSD files can be interpreted up to GSD revision 5. This means that DP slaves that support the following functions, for example, will be supported: Diagnostic alarms for interrupt blocks Isochronous mode and constant bus cycle time SYNC/FREEZE Clock synchronization for DP slaves Installing the GSD file Introduction A GSD file (device data file) contains all the DP slave properties. If you want to configure a DP slave that does not appear in the hardware catalog, you must install the GSD file provided by the manufacturer. DP slaves installed via GSD files are displayed in the hardware catalog and can then be selected and configured. WinCC Basic V13.0 System Manual, 02/2014 899 Editing devices and networks 8.1 Configuring devices and networks Requirement The hardware and network editor is closed. You have access to the required GSD files in a directory on the hard disk. Procedure To install a GSD file, proceed as follows: 1. In the "Options" menu, select the "Install device master data files" command. 2. In the "Install device master data files" dialog box, choose the folder in which you want to save the GSD files. 3. Choose one or more files from the list of displayed GSD files. 4. Click on the "Install" button. 5. To create a log file for the installation, click on the "Save log file" button. Any problems during the installation can be tracked down using the log file. You will find the new DP slave installed by means of the GSD file in a new folder in the hardware catalog. Note Installation of GSD file cannot be undone. Configuring GSD-based DP slave DP slaves that you have inserted through installation of a GSD file can be selected as usual via the hardware catalog and inserted in the network view. If you want to insert the modules of the GSD-based DP slaves, you must take into account some particular details. Requirement You have installed a DP slave using a GSD file. You have inserted the head module in the network view in the usual manner. The device overview opens in the device view. The hardware catalog is open. Procedure To add the modules of a GSD-based DP slave, proceed as follows: 1. In the hardware catalog, navigate to the modules of the GSD-based DP slave. GSD-based DP slaves, also referred to as DP standard slaves, can be found in the "Other field devices" folder of the hardware catalog. 2. Select the desired module. 900 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks 3. Use drag-and-drop to move the module to a free space in the device overview. 4. Select the module in the device overview to edit parameters. You have now inserted the module in a free slot of the GSD-based DP slave and can edit its parameters. Note You can see only the GSD-based DP slave in the graphic area of the device view. The added modules of GSD-based DP slaves are only found in the device overview. Preset configuration For modules with an adjustable preset configuration, you can change this configuration in the inspector window under "Properties > Preset configuration". 8.1.4.7 Configurations for PROFINET IO What you need to know about PROFINET IO What is PROFINET IO? PROFINET IO PROFINET is an Ethernet-based automation standard of PROFIBUS Nutzerorganisation e.V. (PNO) which defines a manufacturer-neutral communication, automation and engineering model. Objective The objective of PROFINET is: Integrated communication via field bus and Ethernet Open, distributed automation Use of open standards Architecture The PROFIBUS User Organisation e.V. (PNO) has designated the following aspects for PROFINET architecture: Communication between controllers as components within distributed systems. Communication between field devices, such as I/O devices and drives. WinCC Basic V13.0 System Manual, 02/2014 901 Editing devices and networks 8.1 Configuring devices and networks Implementation by Siemens The demand for "Communication between controllers as components within distributed systems" is implemented by "Component Based Automation" (CBA). Component Based Automation is used to create a distributed automation solution based on prefabricated components and partial solutions. The demand for "Communication between field devices" is implemented by Siemens with "PROFINET IO". Just as with PROFIBUS DP, the complete configuration and programming of the components involved is possible using the Totally Integrated Automation Portal. The following sections deal with the configuration of communication between field devices using PROFINET IO. Overview of RT classes RT classes in PROFINET IO PROFINET IO is a scalable, real-time communication system based on Ethernet technology. The scalable approach is reflected in several real-time classes: RT: Transmission of data in prioritized, non-isochronous Ethernet frames. The required bandwidth is within the free bandwidth area for TCP/IP communication. IRT: Isochronous transmission of data with high stability for time-critical applications (for example, motion control). The required bandwidth is from the area of bandwidth reserved for cyclic data. Depending on the device, not all real-time classes are supported. Connecting existing bus systems Connection of PROFINET and PROFIBUS PROFINET IO and PROFIBUS DP can be connected with each other as follows: via Industrial Ethernet: To connect the two network types, Industrial Ethernet (plant control level) and PROFIBUS (cell level/field level), use the IE/PB link, for example. via Industrial Wireless LAN: PROFIBUS devices, for example, can be connected to PROFINET IO via a wireless LAN/ PB link. This allows existing PROFIBUS configurations to be integrated into PROFINET. AS interface devices can be connected by an IE/AS-i link PN IO to the interface of a PROFINET device. This allows the existing AS-i network to be integrated into PROFINET. The following figure shows the connection of a PROFIBUS subnet via a PROFINET device with proxy functions. 902 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks ,QGXVWULDO(WKHUQHW 352),%86 PROFINET devices PROFINET device with proxy functions (for example, IE/PB link) PROFIBUS devices PROFINET device with proxy functions used as proxy for a PROFIBUS device The PROFINET device with proxy functions is the proxy for a PROFIBUS device on the Ethernet. The proxy functionality enables a PROFIBUS device to communicate with all devices on the PROFINET and not just with its master. Existing PROFIBUS systems can easily be integrated into PROFINET communication using the proxy functions. If, for instance, you connect a PROFIBUS device via an IE/PB link to PROFINET, the IE/PB link acts as a proxy for the PROFIBUS components for communicating via PROFINET. Configuration using IE/PB link PN IO Configuration using IE/PB Link PN IO You can use the IE/PB Link PN IO to connect PROFIBUS DP configurations to PROFINET IO. From the CPU perspective, the PROFIBUS DP slaves are connected to the same network as the IE/PB Link PN IO. These slaves have the same device name and IP address as the IE/PB Link PN IO, but different device numbers. Furthermore, each also has a specific PROFIBUS address. In the properties of the IE/PB link, the PROFIBUS addresses of the connected DP slaves are displayed in addition to the PROFINET device numbers, as this device has two addressing schemes. WinCC Basic V13.0 System Manual, 02/2014 903 Editing devices and networks 8.1 Configuring devices and networks Handling device numbers and PROFIBUS addresses on the master system During placement, the same number is assigned for the PROFINET device number and the PROFIBUS address. In the Inspector window under "General Properties > PROFINET device number", you can find an overview of the device numbers used and the PROFIBUS addresses of an IE/PB link. The device number can also be changed here. You can also set that the device number and the PROFIBUS address should or should not always be identical. If the "PROFINET device number=PROFIBUS address" option is activated, you do not have to update the device number when the PROFIBUS address changes. The PROFIBUS address can be changed in the properties of the PROFIBUS device. Restrictions The following restrictions apply to DP slaves configured as described above on the PROFIBUS subnet of an IE/PB link: No pluggable IE/PB link No pluggable DP/PA link No pluggable Y link Not CiR-compliant No pluggable redundant slaves No isochronous transmission / constant bus cycle time can be configured SYNC/FREEZE instructions ("DPSYC_FR") of a CPU on the the Ethernet subnet for DP slaves behind the IE/PB-Link are not supported. Configuration using IWLAN/PN link Maximum number of devices in a IWLAN segment If an Ethernet subnet is set up as wireless network (IWLAN = Industrial Wireless LAN), cyclic data exchange between IO controllers and IO devices is possible via a wireless route. On one side of the wireless route there are fixed installed access points (for example, SCALANCE W 788) and on the other side mobile stations (with, for example IWLAN/PB links with PROFIBUS devices). If the action radius of the mobile stations is large, it may be necessary to install several access points (SCALANCE W 788). Since each access point forms a segment with its wireless range, the IWLAN is made up of a series of segments. The mobile devices "on the one side" of the wireless link with their IWLAN/PB links can move along the segments. 904 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Special feature If several IWLAN/PB links are located within a segment, they have to share the bandwidth that is available for wireless transmission. This leads to a lengthening of the update time for these devices. Example In the following example there are two IO devices (IWLAN/PB link) with a segment. If no more than a maximum of two IWLAN/PB links are present in a IWLAN segment at the same time, enter a "2". WinCC Basic V13.0 System Manual, 02/2014 Segment 1 Segment 2 905 Editing devices and networks 8.1 Configuring devices and networks Configure PROFINET IO Addressing PROFINET devices Assigning addresses and names to PROFINET devices In this chapter you will learn which address and naming conventions are valid for the PROFINET devices. IP addresses All PROFINET devices work with the TCP/IP protocol and therefore require an IP address for Ethernet operation. You can set the IP addresses in the module properties. If the network is part of an existing company Ethernet network, ask your network administrator for this data. The IP addresses of the IO devices are assigned automatically, usually at CPU startup. The IP addresses of the IO devices always have the same subnet mask as the IO controller and are assigned in ascending order, starting at the IP address of the IO controller. Device names Before an IO device can be addressed by an IO controller, it must have a device name. This procedure was chosen for PROFINET because names are easier to administer than complex IP addresses. Both the IO controller as well as IO devices have a device name. When the "Generate PROFINET device name automatically" option is activated, the device name is automatically derived from the name configured for the device (CPU, CP or IM): The PROFINET device name is made up of the name of the device (for example, the CPU), the name of the interface (only with multiple PROFINET interfaces) and optionally the name of the IO system: <CPU name>.<Name of the interface>.<IO system name> You cannot change this name directly. You change the PROFINET device name indirectly, by changing the name of the affected CPU, CP or IM in the general properties of the module. This PROFINET device name is also displayed, for example, in the list of accessible devices. If you want to set the PROFINET device name independently of the module name, you have to deactivate the "Generate PROFINET device name automatically" option. A "converted name" is generated from the PROFINET device name. This is the device name that is actually loaded into the device. The PROFINET device name is only converted if it does not comply to the rules of IEC 61158-6-10. You cannot change this name directly either. 906 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Rules for the converted name The rules for the converted name are listed in the following section. If the converted name is not different from the name of the module, the name of the module must comply with this rule. The name consists of one or more labels , which are separated by a dot [.]. Restricted to a total of 240 characters (lower case letters, numbers, dash, or dot) A name component within the device name, which means a character string between two dots, must not exceed 63 characters. A name component consists of the characters [a-z, 0-9]. The device name must not begin or end with the "-" character. The device name must not begin with a number. The device name form n.n.n.n (n = 0, ... 999) is not permitted. The device name must not begin with the string "port-xyz" or "port-xyz-abcde" (a, b, c, d, e, x, y, z = 0, ... 9). Example of device names device-1.machine-1.plant-1.vendor If you assign this name to a CPU, for example, STEP 7 will not convert it since it conforms to the rules described above. Device number In addition to the device name, a device number is also automatically assigned when an IO device is plugged in. You can change this number. Devices in the PROFINET subnet In a PROFINET subnet the maximum allowable number of devices is monitored during configuration. See also Assigning the device name and IP address (Page 907) Retentivity of IP address parameters and device names (Page 915) Assigning the device name and IP address Assigning an IP address and subnet mask for an IO controller the first time There are various options for this. During parameter assignment of the PROFINET interface you must specify if the IP address is set in the project (which means in the hardware configuration) or if the IP address is to be set on the device. WinCC Basic V13.0 System Manual, 02/2014 907 Editing devices and networks 8.1 Configuring devices and networks Assignment of an IP address Comments Option "IP address is set in the project": When the hardware configuration is loaded to the IO controller (e.g. CPU), the IP address and the device name, if set, are also loaded. The IO controller receives the IP address by loading the hardware configuration, for example, via one of the PROFINET interfaces, by means of the PROFIBUS interface or via the MPI interface. Example PROFINET interface: 1. Connect your programming device/PC to the same network as the relevant PROFINET device. The interface of the PG/PC must be set to TCP/IP (Auto) mode. 2. Have a list of accessible devices displayed. 3. Select the target device by using its MAC address and load the hardware configuration including the configured IP address (IP address is then saved retentively). If your PROFINET device has an MPI or PROFIBUS DP interface, connect your programming device/PC directly to the PROFINET device via the MPI or PROFIBUS DP interface. The configured IP address is applied when the hardware configuration is loaded. Option "IP address is set directly at the device": Assign online Assignment by user program (instruction IP_CONFIG for S7-300/400, T_CONFIG for S7-1200/1500) Assign via CPU display (S7-1500) Higher-level IO controller makes assignment (only with I-devices) If you have selected this option in the properties of the PROFINET interface, the IP address can be assigned by the online and diagnostics editor, by the primary setup tool, or by the user program ("IP_CONFIG" instruction). This option is set automatically if the option "Multiple use IO system" has been enabled in the properties of the PROFINET IO system (standard machine project). In case of an S7-1200-CPU, make sure that access to the CPU is not protected by a password. If the CPU is write-protected, no IP address and no device name can be assigned directly on the device. Commissioning a PROFINET interface Further details of how to commission a PROFINET interface can also be found in the operating instructions for the PROFINET devices of the SIMATIC family. Assignment of device name for IO devices when the "Support device replacement without exchangeable medium" option is selected For IO controllers with the "Support device replacement without exchangeable medium" option selected, you do not have to assign device names to the IO devices locally, for example in the event of device replacement. Another application is automatic commissioning, in which the CPU automatically assigns the device name and IP address parameters to the IO devices during startup. 908 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Requirement: The ports of the devices are interconnected, and the devices involved support LLDP. The devices have been put into delivery state or - for S7-1500 CPUs version V1.5 and higher - the "Permit overwriting device names of all assigned IO devices" option is selected for the IO controller ("Ethernet addresses" area, "PROFINET" section of the properties of the PROFINET interface). Assignment of device name and address for an IO device The following graphic illustrates the process for assigning the device name and address. This process does not apply when the "Support device replacement without exchangeable medium" option is selected. 6,0$7,& ; (WKHUQHW 352),QHW6\VWHP 85 &38 ,( ',['&9 '2['&9 ,0 ,0 9HQWLO ,0 9HQWLO ,0 .ODSSH 6FKQHFNH ,0 ,0 ,0 )UGHUEDQG ([WUXGHU $EOXIW 9HUWHLOHU ,2FRQWUROOHU 352),1(7 0$&$GU WinCC Basic V13.0 System Manual, 02/2014 ,QGXVWULDO(WKHUQHW ,2GHYLFHV 0$&$GU Each device receives a name; STEP 7 automatically assigns an IP address. From the name, STEP 7 generates a PROFINET device name that you assign to an IO device online (MAC address) and that is written to the device. You load the configuration to the IO controller. The IO controller assigns the appropriate IP address to the IO device with the assigned PROFINET device name during startup. 909 Editing devices and networks 8.1 Configuring devices and networks Changing the device name and IP address You can change the name and IP address manually. The device name must first be changed in the configuration in order to subsequently assign it to the IO device via the memory card or online with programming device/PC. Offline with memory card: 1. Place the configured data (device name: for example, turbo-3) for the IO device on the MMC in the PG/PC. Use the command "SIMATIC Card Reader > Save Device Name to Memory Card" in the "Project" menu for this. 2. Then insert the MMC into the IO device. The IO device automatically adopts the configured device name. Online with programming device/PC: 1. Connect the programming device/PC directly to the Ethernet subnetwork via the PROFINET interface. 2. Select the subnet in the network view and then select the "Assign device name" shortcut command. 3. In the "Assign PROFINET device name" dialog box, select the suitable PG/PC interface to connect to the Ethernet subnet. All configured PROFINET device names are in the top dropdown list. Select a PROFINET device name from it and select the IO device to receive this device name from the table at the bottom. You can filter the display of devices in the table according to various criteria. 4. You can easily identify the device using the "Flash LED" button. 5. Click "Assign name". The IO controller recognizes the IO device by its device name and automatically assigns the configured IP address to it. IP address assignment for special IO devices Special IO devices, for example, SCALANCE X, S7-300 CPs, support the option of assigning the IP addresses not from the IO controller during startup. In this case, the IP address is assigned in a different way. The option is called "IP address is set directly at the device". For additional information, refer to the manual of the respective PROFINET device of the SIMATIC device family. Another special case is the option "IP address is set by the IO controller during runtime" in the "IP protocol" area of the Ethernet address properties of an IO device. This option is set automatically when the option "Multiple use IO system" is selected for a standard machine project in the associated PROFINET IO system. In this case, an adapted IP address is not assigned by the IO controller until the IO controller itself has received a local IP address. 910 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Requirement for additional procedures when assigning IP address and device name If the IO device, as described above, should not obtain the IP address or device name from the IO controller, proceed as follows: 1. Select device or network view. 2. Open the properties of the respective PROFINET device and select the area "PROFINET interface [X1]" > "Ethernet addresses". 3. Select the option "IP address is set directly at the device" under "IP parameters" or the option "Permit setting of PROFINET device name directly on the device" under "PROFINET". Rules If the "IP address/device name is set directly at the device" option is used for a PROFINET device, note the following: The subnet part of the IP address of the IO device must match the subnet part of the IP address of the IO controller. The corresponding PROFINET device cannot be used as a gateway. See also Assigning a name in the online and diagnostics view opened via "Accessible devices" (Page 1123) Enabling device replacement without exchangeable medium (Page 926) Example of the assignment of the device name In this example you assign device names to a PROFINET IO controller and a PROFINET IO device. To make assignment easier, the device names should also contain the names of the PROFINET IO system. Requirement You must be in the network view. A CPU 1214C (V2.0 or higher) must be available in the network view. An interface module IM 151-3PN exists. The PROFINET interfaces of both modules are networked. WinCC Basic V13.0 System Manual, 02/2014 911 Editing devices and networks 8.1 Configuring devices and networks Procedure To assign the names, follow these steps: 1. Select the CPU. Make sure that you have selected only the CPU and not the complete device! 2. Assign the name "myController" in the Inspector window, under "General". 3. Select the interface module. Ensure that you have selected only the interface module and not the complete ET 200S device. 4. Assign the name "Device_1" in the Inspector window, under "General". 5. Right-click on the PROFINET IO system and select the "Properties" command. 912 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks 6. Assign the name "Plant_section1" to the IO system and select the check box "Use name as extension for PROFINET device names". 7. You can find the automatically generated PROFINET device names at the selected device in the Inspector window, at "PROFINET interface". The PROFINET device name corresponds to the name of the module (with the name of the IO system as extension) with the difference that only lower case text is used. Background: No distinction is made between upper and lower case ("case insensitive") for the storing of the name. If you want to specify the device name independently of the module name, you have to deactivate the "Generate PROFINET device name automatically" option. The PROFINET device name can be edited in this case. WinCC Basic V13.0 System Manual, 02/2014 913 Editing devices and networks 8.1 Configuring devices and networks The converted name is displayed below. This is the name that is automatically generated from the PROFINET device name and satisfies the DNS conventions. If you work with STEP 7, you do not require this name. This name is displayed here as a check and corresponds to the name that is stored in the device. If you work with other tools that are able to record the data exchange and read the actual device names, then you find the converted names. Other special features For PROFINET devices with multiple PROFINET interfaces, the name of the interface is attached to the name of the module, separated by a dot. Example: Name of the module: myController Name of the interface: Interface_1 PROFINET device name: mycontroller.interface_1 Assign device name via memory card Introduction You can configure the device names of PROFINET IO devices offline. To do this, store a configured device name on a memory card and then insert the card into the appropriate IO device. If an IO device has to be completely replaced due to a device defect, the IO controller automatically reconfigures the new device. Using the memory card, a device can be replaced without a programming device. Requirements The programming device has a card reader for memory cards. The IO device must support the assignment of the device name via memory card. The station and its PROFINET IO system is configured. Procedure To store a device name on a memory card, follow these steps: 1. Insert the memory card into the card reader. 2. Select the IO device whose device name is to be assigned by the memory card. 3. Select the "Card reader > Save Device Name to Memory Card" command in the "Project" menu. If the memory card is not empty, a message will be issued informing you of this and you will have the option to delete the card. 914 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Retentivity of IP address parameters and device names The retentivity of IP address parameters (IP address, subnet mask, router setting) and device name depends on how the address is assigned. The non-retentive, temporary assignment means: IP address parameters and device name remain valid for the following time period: - Until the next POWER OFF - Until the next memory reset - Until termination of the online connection (for example, after loading the program) After POWER OFF / POWER ON or a memory reset, the CPU can only be accessed via the MAC address. If the IP address parameters are not retentive, communication based on the IP protocol can no longer take place after the above described events (for example, after POWER OFF/ POWER ON). The assignment of a temporary IP address also deletes retentively saved IP address parameters. Assigning IP address parameters and device name non-retentively IP address parameters and device name are not retentive in the following cases: A temporary IP address that is not retentive is implicitly assigned with the "Accessible devices" function, if the device (e.g. CPU) does not yet have an IP address. The device is a "normal" IO controller (i.e., not an I-device), and it is specified in the user program ("IP_Conf" instruction) that the IP address parameters/device name are not to be retentive. Assigning IP address parameters and device name retentively IP address parameters and device name are retentive in the following cases: In the properties of the PROFINET interface, it is specified that the IP address parameters are set in the project ("Set IP address in the project" option). In the properties of the PROFINET interface, it is specified that the IP address is to be set on the device. - Once the configuration is loaded, the IP address parameters and the device name are assigned via STEP 7 or a setup tool such as PST (STEP 7: online and diagnostic function "Assign IP address"). The assigned IP address parameters are retentive. - The device is a "normal" IO controller (i.e., not an I-device), and it is specified in the user program ("IP_Conf" instruction) that the IP address parameters/device name are to be retentive. WinCC Basic V13.0 System Manual, 02/2014 915 Editing devices and networks 8.1 Configuring devices and networks Special features of the I-device In the properties of the PROFINET interface of the I-device, it is specified that the IP address parameters are to be set on the device. The IP address parameters for the I-device are assigned by the higher-level IO controller. If prioritized startup is set, the IP address parameters are retentive. If no prioritized startup is set, the IP address parameters are not retentive. Recommendation If possible, use the "Set IP address in project" option and specify an appropriate IP address. In this case, the IP address is assigned retentively. Resetting of retentive IP address parameters and device names Retentive IP address parameters and device names are reset via the online and diagnostic function "Reset to factory settings". Note Consequences of reassignment of IP address parameters on top of existing IP parameters The temporary assignment of IP address parameters/device names results in a reset of any retentively saved IP address parameters/device names. With a fixed assignment of IP address parameters/device names, previously retentivelysaved parameters are replaced by the newly assigned parameters. Note Reuse of devices Execute the "Reset to factory settings" before you install a device with retentive IP address parameters and device name in another subnet or system or before you place it in storage. Creating a PROFINET IO system A PROFINET IO system is comprised of a PROFINET IO controller and its assigned PROFINET IO devices. To create a PROFINET IO system you require an IO controller (for example, CPU 1214C) and one or more IO devices (for example, a head module from the distributed I/O family ET 200S). As soon as you connect an IO controller to an IO device, a controller-device link is established. 916 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Procedure To create a PROFINET IO system, proceed as follows: 1. Use drag-and-drop to pull an IO controller from the hardware catalog (for example, CPU 1214C) into the free area of the network view. The IO controller is created in the project. 2. Use drag-and-drop to move an IO device from the hardware catalog (for example, ET 200S) into the free area of the network view. 3. Click on the PROFINET interface of the IO controller or the IO device. 4. Hold down the mouse button and draw a connecting line between this selected interface and that of the partner device. A subnet with an IO system between the IO controller and the IO device is created. 5. If required, adapt the properties of the Ethernet subnet or the IO controller (for example, IP address) under "Properties" in the inspector window. Handling PROFINET IO systems Using shortcut menu commands, you can delete PROFINET IO systems, create new ones or even connect the interface to another subnet from within the network view. An existing PROFINET configuration can thereby be corrected in the network view. Create new PROFINET IO system for IO controller To create a new PROFINET IO for an IO controller, proceed as follows: 1. Make sure that no IO system is already assigned to the IO controller. If an IO system is already assigned to the IO controller, the "Assign IO system" shortcut menu command is disabled. 2. Select the PROFINET interface and then select the "Assign IO system" shortcut menu command. A new PROFINET IO system is created at the IO controller and you can assign IO devices to this IO system. WinCC Basic V13.0 System Manual, 02/2014 917 Editing devices and networks 8.1 Configuring devices and networks Disconnecting PROFINET IO devices from PROFINET IO system To disconnect an already networked PROFINET IO device from its PROFINET IO system, follow these steps: 1. Click on the PROFINET interface of an IO device. 2. Select the "Disconnect from IO system" shortcut menu command. The IO device that was assigned to this IO system is then no longer assigned to it. You can create a new IO systems and can assign each of the non-assigned IO devices to an IO controller. Assign PROFINET IO devices to other IO controllers Existing PROFINET IO systems can be easily reconfigured in the network view: 1. Select the interface of an IO device and then select the shortcut menu. You have the following options here: - Assign a new subnet to the IO device or disconnect it from the existing subnet - Assign a new IO controller to the IO device - Assign a new IO system to the IO device or disconnect it from the existing subnet 2. To assign another IO controller to the IO device, select the "Assign to new IO controller" shortcut menu command. If there is no connection, a subnet is automatically created and the IO device is assigned to the IO system of the new IO controller. Tip: Quick configuration of IO systems If the IO system has a lot of IO devices, assign all IO devices placed by drag-and-drop operation to an IO controller on one step. Requirements IO controller and IO devices are placed in the network view. 918 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Assign IO devices to an IO system To do this, follow these steps: 1. Select an appropriate zoom factor so that you can see as many IO devices as possible in the network view. 2. Arrange the IO devices in not more than of two rows. 3. Select all IO interfaces (not all devices) with the mouse cursor. This only works if you begin to drag the mouse cursor outside of the first IO device and release the mouse button at the last IO device (selection with the lasso). 4. Select the shortcut menu "Assign new IO controller" and select the corresponding IO interface of the IO controller in the subsequent dialog. 5. The IO devices are automatically networked with the IO controller and combine with it to form an IO system. Note When an IO system is highlighted, you can double-click on an IO device in the hardware catalog and thereby quickly add additional IO devices. Result: The IO device is automatically added to the highlighted IO system. WinCC Basic V13.0 System Manual, 02/2014 919 Editing devices and networks 8.1 Configuring devices and networks Interconnecting ports If an IO device is assigned to an IO controller, this does not yet specify how the ports are connected to each other. Although a port interconnection is not required to make use of the Ethernet/PROFINET functions, it does offer the following advantages: A target topology is specified with the port interconnection. Based on an online-offline comparison, it is possible to conduct a target-actual comparison with all devices that support this function. Only with IRT communication: If a port interconnection is configured, STEP 7 can determine the required bandwidth more precisely. As a rule, this leads to a higher performance. Make sure that no invalid ring structures occur through the interconnection of ports. Port interconnection is only advisable for devices that support the topology configuration. Interconnecting ports in the Inspector window To interconnect ports, follow these steps: 1. Select the Ethernet/PROFINET device or the Ethernet/PROFINET interface. 2. Navigate to the port property "Port interconnection". When the Ethernet/PROFINET interface is selected, you can find this setting in the Inspector window as follows: Properties > General > Advanced Options > Port [...] > Port Interconnection. 3. In the "Local port" section, you can find the settings at the local port. In the case of fiberoptic cable you can, for example, set the cable names here. In the "Partner port" section, click on the black triangle in the "Partner port" box to display and select the available partner ports. 4. If the port interconnection is a port interconnection with copper as medium and the devices support IRT communication, you can also set cable length and signal transit time. If the Ethernet/PROFINET interface was not networked, it is automatically networked by this action. In the properties of the subnet you can set whether this subnet should or should not be used for the networking. See also Overview (Page 518) Setting the send clock Requirements to change the send clock at the PROFINET device No IRT (Isochronous Realtime) should be configured. In detail, this means: No device must be configured at the IO system as a sync slave or sync master. All devices at the IO system must be unsynchronized. 920 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks If IRT is configured (in other words, if the IO controller is configured as sync master), the send clock can only be configured in the sync domain. Procedure To set the send clock on the PROFINET device, follow these steps: 1. Select the PROFINET IO controller in the device or network view. 2. Change the value for the shortest possible update interval in the properties of the PROFINET interface under "PROFINET Interface > Advanced options > Real-time settings > IO communication > Send clock". The send clock is valid for all PROFINET devices at the IO system. If the synchronization role is set to a value other than "Unsynchronized", you can only set the send clock in the sync domain, in other words, centrally at the PROFINET IO system. Setting the update time Update time An IO device / IO controller in the PROFINET IO system is supplied with new data from the IO controller / IO device within this time period. The update time can be separately configured for each IO device and determines the time interval in which data is transmitted from the IO controller to the IO device (outputs) as well as data from the IO device to the IO controller (inputs). STEP 7 calculates the update time automatically in the default setting for each IO device of the PROFINET IO system, taking into account the volume of data to be exchanged as well as the set send clock. Setting the update time If you do not want to have the update time calculated automatically, you can change the setting. To change the update time, proceed as follows: 1. Select the PROFINET interface of the IO device in the network or device view. 2. Change the update time in the interface properties under "Advanced options > Realtime settings > IO cycle". - To have a suitable update time calculated automatically, select "Automatic". - To set the update yourself, select "Can be set" and enter the required update time in ms. 3. To ensure consistency between the send clock and the update time, activate the "Adapt update time when send clock changes" option. This option ensures that the update time is not set to less than the send clock. Non-automatic setting of the send clock may result in errors if the available bandwidth is insufficient or if other limits are exceeded (for example, too many devices are configured). WinCC Basic V13.0 System Manual, 02/2014 921 Editing devices and networks 8.1 Configuring devices and networks Setting the watchdog time Watchdog time You can configure the watchdog time for PROFINET IO devices. If the IO device is not supplied with input or output data (IO data) by the IO controller within the watchdog time, it switches to the safe state. Do not enter the watchdog time directly, but as "Accepted number of update cycles when IO data is missing". This makes setting easier because the update time can be shorter or longer, depending on the power of the IO device or the setting. The resulting watchdog time is automatically calculated from the "Accepted number of update cycles when IO data is missing". Configuring the watchdog time To specify the watchdog time, follow these steps: 1. Select the PROFINET interface of the IO device in the network or device view. 2. In the properties of the interface, navigate to "Advanced options > Realtime settings > IO cycle". 3. Select the required number of cycles from the drop-down list "Trigger watchdog after # cycles with missing IO data". The watchdog time is subsequently calculated automatically based on the preset factor. It must not be more than 1.92 seconds. Note The default setting should only be changed in exceptional cases, for example, during the commissioning phase. Calculated bandwidth for cyclic IO data Calculated bandwidth for cyclic IO data Adherence to the maximum available bandwidth for cyclic IO data is monitored by the system. The maximum bandwidth depends on the send clock cycle. If the send clock cycle is greater than or equal to 1 ms, the maximum bandwidth is 0.5 ms. If the send clock cycle is shorter, the maximum available bandwidth is also reduced. The bandwidth actually required for cyclic IO data is determined by the system based on the number of configured IO devices and IO modules. Furthermore, the required bandwidth depends on the update time that is used. In general, the calculated bandwidth increases in the following cases: 922 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks There is a greater number of IO devices There is a greater number of IO modules The update times are shorter. Maximum bandwidth for cyclic IO data depending on the send clock The following table shows how the maximum available bandwidth for cyclic IO data reacts based on the send clock: Send clock cycle Maximum bandwidth for cyclic IO data 250 s - 468.75 s << 125 s 500 s - 968.75 s = send clock / 2 1 - 4 ms = 500 s Setting port options Setting the port options Changing connection settings for the PROFINET IO port You can change the network settings for the PROFINET IO port as required. By default, the settings are made automatically. In normal situations, this guarantees problem-free communication. Possible settings for transmission medium/duplex Depending on the selected device, you can make the following settings for "Transmission medium/duplex": Automatic setting Recommended default setting of the port. The transmission settings are automatically "negotiated" with the partner port. The "Enable autonegotiation" option is automatically selected by default. TP/ITP at x Mbps full duplex (half duplex) Setting of the transmission rate and the full duplex/half duplex mode. The effectiveness depends on the "Enable autonegotiation" setting: - Autonegotiation enabled You can use both cross cable and patch cable. - Autonegotiation disabled Make sure that you use the correct cable (patch cable or cross cable)! The port is also monitored with this setting. Deactivated Depending on the module type, the drop down list box can contain the "- Disabled -" option. This option, for example, allows you to prevent access to an unused port for security reasons. With this setting, diagnostic events are not generated. WinCC Basic V13.0 System Manual, 02/2014 923 Editing devices and networks 8.1 Configuring devices and networks "Monitor" option This option is used to activate or deactivate the port diagnostics. Examples of port diagnostics: The link status is monitored, in other words, the diagnostics are generated during link-down and the system reserve is monitored in the case of fiber optic ports. Option "Enable autonegotiation " The autonegotiation setting can only be changed if a concrete medium (for example, TP 100 Mbps full duplex) is selected. Whether or not a concrete medium can be set depends on the properties of the module. If autonegotiation is disabled, this causes the port to be permanently specified, as for example, is necessary for a prioritized startup of the IO device. You must make sure the partner port has the same settings because, with this option, the operating parameters of the connected network are not detected and the data transmission rate and transmission mode can therefore not be optimally set. Note When a local port is interconnected, STEP 7 makes the setting for the partner port if the partner port supports the setting. If the partner port does not support the setting, an error message is generated. See also Wiring rules for disabled autonegotiation (Page 924) Boundaries at the port (Page 925) Wiring rules for disabled autonegotiation Requirement You have made the following settings for the port in question, for example, to accelerate the startup time of the IO device: Fixed transmission speed Autonegotiation incl. autocrossing disabled This saves you the time required to negotiate the transmission rate during startup. If you have disabled autonegotiation, you must observe the wiring rules. 924 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Wiring rules for disabled autonegotiation PROFINET devices have the following two types of ports: Type of port PROFINET devices Note Switch port with crossed pin assignment For IO devices: Port 2 Crossed pin assignment means that the pin assignment for the ports for sending and receiving between the respective PROFINET devices is exchanged internally. For S7 CPUs with 2 ports: Ports 1 and 2 End device port with uncrossed pin assignment For IO devices: Port 1 - For S7 CPUs with one port: Port 1 Validity of the wiring rules The cabling rules described in the following paragraph apply exclusively for the situation in which you have specified a fixed port setting. Rules for cabling You can connect several IO devices in a line using a patch cable (one-to-one wiring of both connectors). To do this, you connect port 2 (P2) of the IO device to port 1 (P1) of the next IO device. The following graphic gives an example with two IO devices. 6ZLWFKRU 352),1(7GHYLFH 3 ,2GHYLFH 3 3 3DWFKFDEOHV ,2GHYLFH 3 3 3 3DWFKFDEOHV 6ZLWFKSRUW (QGGHYLFHSRUW Boundaries at the port Requirement To use boundaries, the respective device must have more than one port. If the device for PROFINET does not support boundary settings, the corresponding parameters are disabled. WinCC Basic V13.0 System Manual, 02/2014 925 Editing devices and networks 8.1 Configuring devices and networks Enable boundaries "Boundaries" are limits for transmission of certain Ethernet frames. The following boundaries can be set at a port: "End of detection of accessible devices" DCP frames for detection of accessible devices are not forwarded. Devices located behind this port are no longer displayed in the project tree under "Accessible devices". Devices located behind this port can no longer be reached by the CPU. "End of topology discovery" LLDP frames (Link Layer Discovery Protocol) for topology detection are not forwarded. "End of sync domain" Sync frames transmitted for synchronization of devices within a sync domain are not forwarded. For example, if you operate a PROFINET device with more than two ports in a ring, you should prevent the sync frames from being fed into the ring by setting a sync boundary (at the ports not inside the ring). Additional example: If you want to use several sync domains, configure a sync domain boundary for the port connected to a PROFINET device of the other sync domain. Restrictions The following restrictions must be observed: The individual check boxes can only be used if the port supports the function in question. If a partner port has been defined for the port, the following check boxes cannot be used: - "End of detection of accessible devices" - "End of topology discovery" If autonegotiation is disabled, none of the check boxes can be used. Enabling device replacement without exchangeable medium Replacing an IO device without exchangeable medium It is often necessary to replace IO devices in automation systems. The IO devices are generally assigned a device name by either inserting an exchangeable medium or via the programming device. The IO controller uses this device name to identify the IO device. Subject to certain conditions, IO devices can also receive their device names without the insertion of an exchangeable medium (e.g., memory card) or without a programming device. For this purpose, the IO controller uses Ethernet mechanisms (LLDP protocol; Link Layer Discovery Protocol) to analyze the relationships between the individual IO devices and the IO controller. From these relationships, the IO controller detects which IO device was replaced and assigns the configured device name to it. 926 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Requirements A port interconnection is already configured. The affected IO devices in the automation system must support device replacement without exchangeable medium (LLDP protocol). If the individual IO devices in the automation system do not support device replacement without exchangeable medium, a corresponding alarm is output for the IO device. Note Use only new IO devices as replacement devices, or restore IO devices with an existing parameter assignment to delivery state prior to commissioning. For S7-1500 CPUs with firmware version V1.5 or higher, it is not necessary to reset IO devices with an existing parameter assignment to delivery state. The condition for this is that the "Permit overwriting of device name" option is enabled for the IO controller ("Ethernet addresses" area, "PROFINET" section of the properties of the PROFINET interface). Procedure In order to enable the replacement of an IO device without exchangeable medium, proceed as follows: 1. In the device or network view, select the PROFINET interface of the corresponding IO controller. 2. In the interface properties under "Advanced settings > Interface options", select the "Support device replacement without exchangeable medium" check box. The option "Support device replacement without exchangeable medium" also permits automatic commissioning, which means you can commission the IO system with the IO devices without assigning their device names in advance. See also Assigning the device name and IP address (Page 907) Components with the the device replacement without exchangeable medium function (http:// support.automation.siemens.com/WW/view/en/36752540) Using GSD files GSD files for IO devices Basic information on GSD files of IO devices The properties of PROFINET IO devices are not stored in a keyword-based text file (as for PROFIBUS DP slaves), but in an XML file whose structure and rules are determined by a GSDML schema. WinCC Basic V13.0 System Manual, 02/2014 927 Editing devices and networks 8.1 Configuring devices and networks The language used to describe the GSD files is GSDML (Generic Station Description Markup Language). It is defined by the GSDML schema. A GSDML schema contains validation rules that allow it, for example, to check the syntax of a GSD file. GSDML schemas (as schema files) are acquired by IO device manufacturers from PROFIBUS International. Functional enhancements in the area of PROFINET IO will have an effect on the GSDML specification and the corresponding schema. A new version of the specification and of the schema is created by the functional enhancement. Names of GSD files for IO devices One possible example of a GSD file name for IO devices is: "GSDML-V1.0-Siemens-ET200S-20030616.xml" Name component Explanation GSDML String at the start of each GSD file for IO devices V1.0 Version of the GSDML schema Siemens Manufacturer ET200S Name of the device 20030616 Version code (date) .xml File extension Versioning of GSD files for IO devices The version information of GSD files is two-fold: First, the version of the GSDML schema is indicated. This determines the language scope used by a GSD file. This is followed by the version, listed as an issue date. The version number of GSD files is incremented, for example, after elimination of an error or introduction of a functional enhancement. Functional enhancements may result in a new version of the GSDML schema. A new version of a GSDML schema might only be supported with restrictions. Installing the GSD file Introduction A GSD file (generic station description file) contains all properties of an IO device. If you want to configure an IO device that is not available in the hardware catalog, you must install the GSD file provided by the manufacturer. IO devices installed via GSD files are displayed in the hardware catalog and can then be selected and configured. 928 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Requirement The hardware and network editor is closed. You have access to the required GSD files in a directory on the hard disk. Procedure To install a GSD file, follow these steps: 1. In the "Options" menu, select the "Install generic station description files" command. 2. In the "Install generic station description files" dialog box, select the folder in which the GSD files are stored. 3. Choose one or more files from the list of displayed GSD files. 4. Click on the "Install" button. 5. To create a log file for the installation, click on the "Save log file" button. Any problems during the installation can be tracked down using the log file. You will find the new IO devices installed by means of GSD files in the hardware catalog under "Additional field devices > PROFINET". Note Installation of a GSD file cannot be undone. Changing the revision of a GSD file Changing the revision of a GSD file You can change the revision of a GSD file for an IO device: Only for the current IO device All suitable IO devices within the IO system All suitable IO devices within the complete project First, all existing GSD files for the current IO device are shown. The only difference between the GSD files shown is their revision status. The currently used GSD file is highlighted. Requirement The I/O data is the same for all IO devices whose revision is to be changed. The order number has not changed. The number of submodules is identical. The configuration data has not changed. There must be no module or submodule in a slot that is invalid after the new GSD file has been created. WinCC Basic V13.0 System Manual, 02/2014 929 Editing devices and networks 8.1 Configuring devices and networks Procedure To change the revision of one or more IO devices, proceed as follows: 1. Select the IO device whose GSD file revision is to be changed. 2. Click on the "Change revision" button under "General> Catalog information" in the properties of the IO device. The "Change revision" dialog box opens. 3. Select the GSD revision you want to use in the "Available revisions" table. 4. Under "Use selected revision for", select the devices whose version are to be changed: - Only for the current IO device - For all suitable IO devices in the IO system - For all suitable IO devices in the project 5. Click the "Apply" button. 8.1.4.8 Bus coupling with PN/PN coupler Application and function Application The PN/PN coupler is used to link two Ethernet subnets with one another and to exchange data. That way use data about input or output address areas or datasets can be used. The maximum size of the transferable input and output data is 1024 bytes. The division into input and output data is preferable, so that e.g. 800 byte input data and 200 byte output data can be configured. As a device, the PN/PN coupler has two PROFINET interfaces, each of which is linked to one subnet. In the configuration, two IO Devices are produced from this one PN/PN coupler which means that there is one IO Device for each station with its own subnet. The other part of PN/PN coupler in each case is known as the bus node. Once configuring is complete, the two parts are joined. ,2&RQWUROOHU 6 ,2'HYLFH (76 23 3131FRXSOHU ,2'HYLFH (76 6ZLWFK 3* 6ZLWFK ,2&RQWUROOHU 6 6ZLWFK 352),1(7,QGXVWULDO(WKHUQHW Figure 8-3 930 Coupling two PROFINET IO subnets with one PN/PN coupler WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Additional information For additional information on "PN/PN couplers", refer to Service & Support on the Internet (http://support.automation.siemens.com/WW/view/en/44319532). Linking Ethernet subnets Linking Ethernet subnets with a PN/PN coupler You can link Ethernet subnets with the standard device PN/PN coupler. To link Ethernet subnets, follow these steps: 1. Create your Ethernet subnets. 2. Select the standard field devices in the hardware catalog. Find the PN/PN coupler as head module in the "PROFINET IO" folder. 3. In the network view, drag the two components X1 and X2 to the required version of the PN/ PN coupler per drag-and-drop operation. The components form a device, but are shown separately to make handling easier. 4. Connect the Ethernet interface of the PN/PN coupler X1 to the first Ethernet subnet. 5. Connect the Ethernet interface of the PN/PN coupler X2 to the second Ethernet subnet. The Ethernet subnets are now linked through the two components of the PN/PN coupler. 8.1.4.9 Integrating external tools Integrating S7-external tools Introduction Tools external to STEP 7 ("Device Tools") with a special call interface (Tool Calling Interface) can be used to configure distributed devices. Such devices are also referred to as "TCI capable". WinCC Basic V13.0 System Manual, 02/2014 931 Editing devices and networks 8.1 Configuring devices and networks The performance range of these tools exceeds the possibilities provided within GSD configuration, for example, they can provide expanded graphical input options. Distributed devices can be as follows: PROFIBUS DP slaves Modules within a DP slave PROFINET IO devices Modules within an IO device Note Warranty and liability Siemens accepts no liability for third-party software (device tools) called with the TCI (Tool Calling Interface) or for proper interaction with the associated devices. Requirement The call interface of the tool complies with the TCI specification. Parameters and commands are forwarded to the distributed device via this call interface. Such tools have to be installed using a setup provided by the manufacturer. The "S7-PCT" (Port Configuration Tool) device tool for IO-Link master modules and IO-Link devices is an exception; this is supplied with STEP 7. Special note: After the installation, the tool is not shown in the list of installed software or in the list of software products in the project. The GSD file of the distributed device that is to be configured with the Device Tool must be installed. Starting the device tool The command for starting the device tool is available in the shortcut menu of the TCI-capable device in the shortcut menu of the graphical and tabular device view: "Start device tool". See also Starting the SIMATIC S7-PCT (Page 932) Starting the SIMATIC S7-PCT Introduction The "S7-PCT" (Port Configuration Tool) device tool is installed with STEP 7. The tool is used to assign parameters to the ports of IO-Link modules such as 4SI IO-Link (S7-1200, ET 200S) or 4IOL+8DI+4DO (ET 200eco PN). 932 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Requirement You have configured the corresponding CPU, the DP slave or the IO device with an IO-Link module. Procedure To start via the graphical device view, follow these steps: 1. Select the IO-Link module in the device view. 2. Select "Start device tool" from the shortcut menu. OR, to start with the tabular device view, follow these steps: 1. Select the IO-Link module in the device view. 2. Arrange the areas in the work area in such a way that the tabular device overview is visible (it is located between the device view and the inspector window). 3. Select the row with the IO-Link module in the device overview. 4. Select "Start device tool" from the shortcut menu. Result The tool starts and you can configure the ports. See also Integrating S7-external tools (Page 931) 8.1.4.10 Loading a configuration Introduction to loading a configuration In order to commission a device, identical configurations must be stored on the programming device/PC and on the connected devices. To synchronize the configurations on the programming device/PC and the connected devices, you load a configuration. Configuration data can be loaded in two directions: From the programming device/PC to a device From the device to a PG/PC See also Uploading project data from a device (Page 270) General information on loading (Page 265) Downloading a configuration to a device (Page 934) Downloading project data to a device (Page 267) WinCC Basic V13.0 System Manual, 02/2014 933 Editing devices and networks 8.1 Configuring devices and networks General information on loading to PG/PC (Page 935) Special features during startup (Page 953) Downloading a configuration to a device Loading the hardware configuration After you have inserted a new device in the project and configured it or if you have modified an existing hardware configuration, the next step is to load the current configuration to the device. This ensures that the same configuration is set on the programming device/PC and on the module that is physically present. Use the "Online > Download to device (Page 267)" menu command for this. In the first download, the complete hardware configuration is downloaded. In subsequent downloads, only changes to the hardware configuration are downloaded. You have the following options for loading the hardware configuration: Loading in the device or network view Loading in the project tree Loading to an accessible device WARNING Perform load operation only in STOP mode Following loading, the machine or process may behave unexpectedly if the parameter assignment is incorrect. A CPU must be set to STOP mode for the load operation to rule out possible damage to equipment or personal injury. Special considerations for loading isochronous applications Isochronous applications consist of a hardware configuration part and a software part. Example: If you change the number of an IO system, the delay time, or the assignment of a process image partition of the isochronous I/O in the hardware configuration, this affects the parameters of the isochronous mode interrupt OB and thus also the software part. With isochronous applications, you should always load the complete project (hardware and software). With partial loading (loading hardware and software separately at different times), inconsistencies can arise that, for example, can prevent CPU startup or isochronous operation of the application. See also General information on loading (Page 265) 934 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Loading a configuration to PG/PC General information on loading to PG/PC Introduction If you bring your PG/PC to a plant and the STEP 7 project used to create the configuration of this plant is not available, load the configuration to a new project on your PG/PC, for example. Use the "Online > Loading the device as new station (hardware and software) (Page 270)" menu command for this. The list of accessible devices in the project tree is always used when loading a device to your programming device. You can select multiple devices and load them to the project at the same time. Requirements The hardware configuration in the device must be created in TIA Portal V12 or higher. A hardware configuration present in the device that was created with an older version cannot be loaded and must be upgraded (Page 245). Modules present in the device from GSD (ML), HSPs, or service packs must be installed in the TIA Portal on the PG/PC. A project must be open. This project can be a new (empty) project or an existing project. The opened project is in offline mode. Scope of load operation The following list shows an overview of the loadable components of a configuration: The device (e.g., a CPU) with all I/O modules and all parameter settings PROFIBUS master systems and all PROFIBUS-relevant settings PROFINET IO systems and all PROFINET-relevant settings I devices and I slaves Settings for direct data exchange After loading a CPU, all other modules within the address area of the CPU are also loaded. The following connections are also loaded when the configuration is loaded: S7 connections (including routed connections) in combined PB/IE networks, including via IE-CP or PB-CM interfaces. S7 connections are automatically accepted as configured at one end when a device configuration is loaded, even if the S7 connection was configured at both ends in the original project. When both connection partners are loaded, the connection is joined together again during the next compilation. TCP connections via CPU-internal Ethernet interface, UDP/ISOonTCP connections, and TCP, UDP, ISO, and ISOonTCP connections via IE-CP interface Connections via the OUC connection parameter assignment for projects from STEP 7 V13 and higher WinCC Basic V13.0 System Manual, 02/2014 935 Editing devices and networks 8.1 Configuring devices and networks Note The hardware configuration loaded to PG/PC is not completely identical to the configuration originally loaded to the device. Note the additional information on loading, in particular with regard to partially loaded configuration data in the case of cross-device communication. Loading PC systems, such as WinAC or PC-based automation, is not possible. See also General information on loading (Page 265) Loading specific device configurations Information on loading When device configurations are loaded to the PG/PC, all assigned parameters are transferred from the device to the project. If the CPU is connected to a subnet, all parameters of the device are loaded and the CPU is displayed in the network view as networked. Note CPUs reset to their factory settings do not have any hardware configuration. Therefore, nothing is loaded in this case after "Load to PG/PC" is selected in the "Online" menu. Loading S7-300/400 configurations To avoid conflicts when loading a device to an existing project, the following rules must be followed: Device names for CPUs, PROFIBUS slaves (DP slaves, I-slaves) and PROFINET devices (IO devices, I devices) must be unique The combination of network name, subnet ID, and IP/DP address for modules must be unique If conflicts occur, the load operation is canceled and an alarm provides information about the problems that occurred. You can then adapt the project correspondingly or install missing components and then repeat the load operation. Alarm configurations are not loaded to PG/PC. 936 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Loading S7-1200/1500 configurations Take the following into consideration when loading: CPUs of the S7-1200 series with firmware version V1.0 are not supported when loading. Device-specific diagnostic interrupts of the S7-1200 are not supported when loading. For device-specific diagnostic interrupts of the S7-1200 to be generated on the PG/PC once again, the hardware configuration must be compiled once again. Module comments of the S7-1200/1500 are loaded from the device to the PG/PC if the same project language is set that was used during loading to the device. You can deselect the loading of comments, if desired. Note All types of PC systems, such as WinAC, Embedded Controller, CP 1616 or PC CPs, do not support loading to PG/PC. Loading distributed I/O The following functionalities and settings of the distributed I/O are loaded: DP master systems/IO systems with associated DP masters/IO controllers (CPUs and CPs), DP slaves/IO devices, the utilized modules and their parameter assignment and properties, such as options handling, status bytes, or SYNC/FREEZE Connection of process image partitions (PIP) to organization blocks (OB). Applies to the module and OB properties Configured hardware interrupts with the associated properties DP master systems with I-slave CPs as PROFIBUS I-slave or PROFINET I-device Direct data exchange Master-slave relationships between the I-slave/I-device and assigned DP master/IO controller are only established in the project if both the master as well as the I-slave are loaded to the PG. It does not matter whether you load the DP master/IO controller or the I-slave/I-device first. As soon as both devices are loaded, the master-slave/controller-device relationships will also be re-established. WinCC Basic V13.0 System Manual, 02/2014 937 Editing devices and networks 8.1 Configuring devices and networks Loading subnets and devices with MPI, PROFIBUS, Ethernet, and PtP The following special considerations apply to loading subnets and end points of connections for MPI, PROFIBUS, Ethernet, and PtP with their respective connection properties: If a device with PROFIBUS interface is loaded, the bus parameters of the device will initially be different from the settings in the original project. The bus parameters will only match those of the original project after all devices involved are loaded and no additional devices are on the same bus. Passive communication devices that are not connected as DP slaves or IO devices to a corresponding master system or IO system do not participate in the data exchange. They are therefore not loaded. All devices involved should therefore be loaded for cross-device configurations. A warning is output during compiling of the project for missing network stations. Missing routing information due to communication stations that are not loaded is displayed as warning during compilation. If the configuration is loaded from the PG/PC back to the device, different routing information results. When you compile the project after loading devices to the PG/PC, STEP 7 checks if all devices to which communication relationships have been configured are available. If devices are missing, you receive an alarm with the number of missing communication stations. NOTICE Cross-device communication When you load a configuration with cross-device communication to the PG/PC, you must also load all corresponding network stations to the PG/PC. If required network stations are missing and the configuration is loaded back to the device, there is no guarantee that crossdevice communication is working again. See also Upgrading projects (Page 245) Loading configurations with web server Information on loading The hardware configuration of a CPU also contains the web server settings. A number of restrictions apply to loading a web server configuration to the PG/PC: The assignment of the web server language and project language is not loaded for S7-300/400. The project texts are not loaded and an alarm is output that no project languages are assigned. The languages assigned in STEP 7 are loaded without restriction for S7-1200/1500 CPU. User administration data of the S7-1200/1500 can be loaded but not edited. You can use a check box to select whether you want to use the existing data as read-only data or discard these data and enter new data. Watch tables of the web server are not loaded. 938 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks The source files of the user-defined web pages (HTML pages, Java scripts, etc.) are not loaded. The program blocks generated during loading can only be edited if you enter the properties and the HTML page yourself. See also Information about the web server (Page 670) Loading configurations with PROFIBUS Information on loading A DP master is loaded to PG/PC. The DP master system and all connected DP slaves are inserted into the project. The respective settings remain unchanged. If a suitable PROFIBUS subnet has already been created, the loaded devices with PROFIBUS interface are connected to the existing subnet. As a prerequisite for loading DP master systems with standard slaves, the corresponding GSD files must be installed in the TIA Portal and available in the hardware catalog. If a required GSD file is not available in the same version as in the device, differences are identified during the consistency check. Note Direct data exchange in a configuration is only loaded if all communication partners involved in the direct data exchange are loaded to the PG/PC. Missing communication partners are represented by a placeholder device. This means the configuration with direct data exchange can still be compiled. Isochronous mode Note the following when loading DP master systems with activated PROFIBUS functionality "Isochronous mode": Bus parameters and the settings for isochronous mode are only identical after the device is loaded to the PG/PC if all devices relevant for calculation of isochronous mode are loaded. Only mono-master systems with isochronous mode are supported. Therefore, only configurations with just one DP master on the PROFIBUS subnet are loaded. Loading configurations with PROFINET Information on loading If you have selected a CPU in the list of accessible devices and perform an load operation to PG/PC, all IO controllers and IO devices associated with this device along with their IO systems will be loaded. Settings for the topology are also transferred. If there is already a suitable Ethernet network in the project, the loaded devices are integrated into the existing network. WinCC Basic V13.0 System Manual, 02/2014 939 Editing devices and networks 8.1 Configuring devices and networks Relationships between the IO controllers and IO devices are only established within the project if both the IO controller as well as the I-device are loaded to the PG. It does not matter whether you load the IO controller or the I-devices first. Supported functions The following functionalities and settings are loaded: PROFINET configurations (RT and IRT) in IO systems with the associated IO controllers (CPUs and CPs), IO devices, and the modules used Logical addresses and interface properties Port interconnections Isochronous mode Sync domains/MRP domains Redundancy role "Client" or "Manager" for MRP configurations Note Empty Sync domains and MRP domains are not included in the loading. GSD-based IO devices As a prerequisite for loading GSD based IO devices, the corresponding GSD files must be installed in the TIA Portal and available in the hardware catalog. If a required GSD file is not available in the same version as in the device, differences are identified during the consistency check. I-device If you load the IO controller from an IO system with connected I-device, the IO controller and its IO devices will be loaded. An involved I-device is loaded only as an I-device proxy. The CPU parameter assignment, including the parameter assignment of the CPU's "own" 940 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks (subordinate) IO system, is missing in the I-device proxy. Only the interface to the higher-level IO controller is loaded. 6,0$7,&&38&3 ,2FRQWUROOHU HJ(7 ,QGXVWULDO(WKHUQHW 352),1(7,2 HJ(7 ,2GHYLFH ,2GHYLFH ,GHYLFH SUR[\ 6,0$7,&&38&3 DV,GHYLFH +LJKOHYHO ,2V\VWHP /RDGHG,2V\VWHPZLWK ,GHYLFHSUR[\ ,2GHYLFH ,2FRQWUROOHU 8VHUSURJUDP LQWHOOLJHQWSUHSURFHVVLQJ HJ(7 HJ(7 ,2GHYLFH ,QGXVWULDO(WKHUQHW 352),1(7,2 ,2GHYLFH 8QORDGHGORZHUOHYHO,2 V\VWHP /RZHUOHYHO ,2V\VWHP For I-device proxy devices: IO controller can be compiled and loaded Properties are displayed but cannot be changed Diagnostics in the project tree is not carried out In the network view, placeholder devices are represented with a question mark: In order to edit the I-device in the project, you must load the I-device from the device to the PG/PC. This replaces the I-device proxy with the complete I-device along with its subordinate IO devices. WinCC Basic V13.0 System Manual, 02/2014 941 Editing devices and networks 8.1 Configuring devices and networks It is possible to load an IO controller with connected I-device proxy from the PG/PC to the device. Note The replacement of I-device placeholders is only possible if the required I-device is available in the hardware catalog. An I-device proxy representing a SIMOTION I-device cannot be loaded and replaced. Configurations with IE/PB link If one of the following configurations with IE/PB Link PN IO as PROFINET IO device is present, the complete configuration with all subordinate PROFIBUS devices is loaded: CPU/CP of S7-300/400 PC station and connected PROFIBUS master system The complete configuration consists of the following: CPU CP configuration PROFINET IO system with connected IE/PB link PROFIBUS master system of the IE/PB link with connected DP slaves An example configuration consists of an S7-300 CPU with a CP as PROFINET IO controller. An IE/PB link as IO device is connected to the IO controller. As the PROFIBUS DP master, the IE/PB link polls a PROFIBUS DP slave, e.g., ET 200L. If you load the CPU from the device to the PG/PC, the complete configuration is loaded. Note If the IE/PB link is not operated as a PROFINET IO proxy but rather as a gateway in standard mode, the IE/PB link functions as a CPU and can be loaded separately. Loading Shared Devices The following applies to loading comments: If an input/output module with the Module-internal Shared Input (MSI) or Module-internal Shared Output (MSO) function consists of only one submodule, the submodule does not have its own comment. Instead, it uses the comment of the input/output module. The module must be subdivided into several submodules for the input/ output module and all submodules to have their own comment fields. 942 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Loading HMI devices Information on loading We distinguish between the following cases when loading HMI devices to PG/PC: HMI devices connected to a DP master as DP slave or to an IO controller as IO device are loaded as DP slave or IO device respectively (for example, PP 17-I PROFIsafe). HMI devices in a master system as I-slave or in an IO system as I-device are loaded as Islave proxies or I-device proxies (Page 939) (for example, SIMATIC Comfort Panels). The settings of the device proxy are read-only. HMI devices are not loaded if they are connected to a subnet (PROFIBUS or PROFINET) but not to a master system or IO system (for example, KP600 Basic color DP). Going online with loaded configurations You can go online with the loaded project or with loaded portions of the project. Requirement The hardware configuration loaded from the device to the PG/PC has been compiled. The statuses of the central and distributed modules are only correctly displayed after compilation. Note If you go online before compiling, the diagnostics icon "?" is displayed (diagnostics not possible). A corresponding alarm is displayed under "Info > General" in the Inspector window. Dependencies Depending on how completely the hardware configuration was loaded to the PG, restrictions apply to going online and to diagnostics: Completely loaded device with all associated central and distributed modules, such as DP slaves or IO devices: Going online and diagnostics are possible. Loaded device with connected I-devices/I-slaves: - I device/I slave is not loaded: Going online for the device and its modules is possible. For the dependent components of the configuration that are not loaded, device proxies are handled with only minimum diagnostics support. The online status is represented as an icon. The standard diagnostics is shown in the online and diagnostics view. I&M data are not loaded. - I device/I slave is also loaded: Going online is possible for all devices; diagnostics is fully supported. WinCC Basic V13.0 System Manual, 02/2014 943 Editing devices and networks 8.1 Configuring devices and networks 8.1.5 Displaying alarms 8.1.5.1 Overview of the alarm display The "Alarm display" function can be used to output asynchronous alarms of diagnostics events and user-defined diagnostics alarms as well a alarms from ALARM instructions. From the alarm display, you can also start the alarm editor with the "Edit alarm" shortcut menu command and then create user diagnostic alarms. Icons The following table shows the icons and their functions: Icon Function Shows the alarms located in the archive. Archive view Active alarms Shows the currently active (pending) alarms. Alarms that must be acknowledged are shown in blue lettering. Ignore Ignores the arrival of alarms, These alarms are neither shown in the window nor stored in the archive. Acknowledge Confirms the selected alarm as read. Alarms requiring acknowledgment are shown in blue lettering. Deletes all alarms in the archive. Clear archive Export archive 8.1.5.2 Exports the current alarm archive to a file in xml format. Archive view In the archive view, alarms are displayed and archived according to the time they appear. You can set the size of the archive (between 200 and 3000 alarms) with the menu command "Options > Settings > Online & Diagnostics". If the selected archive size is exceeded, the oldest alarm it contains is deleted. Alarms that must be acknowledged are displayed in blue lettering and can be acknowledged with the shortcut menu command "Acknowledge alarm(s)". The archive is constantly updated and does not need to be saved explicitly. 944 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks 8.1.5.3 Layout of the alarms in the archive view In the archive view, all events occurring on the selected CPUs are logged. A new entry is created for each individual event and shown as a further row in the table. Table structure All attributes of the alarms can be shown as columns. You can show or hide individual columns as well as modify the width and order of the columns. These settings are saved when the project is closed. The alarms can be displayed in one or more rows. In the single row display, only the first row of the multiple-row alarm data is displayed. The alarms either require acknowledgment or do not require acknowledgment. The alarms requiring acknowledgment that have not yet been acknowledged are highlighted in blue lettering and can be acknowledged either with the button in the toolbar for the particular context or with the shortcut menu command "Acknowledge alarm(s)". 8.1.5.4 Receiving alarms To allow alarms to be displayed, you must first set the receipt of alarms for each CPU. Procedure Toe receive alarms, follow these steps: 1. Double-click on the "Online & Diagnostics" folder of the relevant CPU in project navigation. 2. Click the "Online access" group in the area navigation. 3. Select the option "Receive alarms". Note If you select this procedure, alarms are only received after you have re-established an online connection to the device. Or: 1. Select the relevant CPU in the device, network, or topology view. 2. Select the command "Receive alarms" in the "Online" menu or in the shortcut menu. Or: 1. Select the CPU in project navigation. 2. Select the command "Receive alarms" in the "Online" menu or in the shortcut menu. Note If you select one of the two above-named procedures, you must have first established an online connection to the device. WinCC Basic V13.0 System Manual, 02/2014 945 Editing devices and networks 8.1 Configuring devices and networks 8.1.5.5 Export archive To archive alarms, you can export the archive. Follow these steps: 1. Go to the archive view. 2. Click the "Export archive" button. 3. In the dialog that opens, select the path to export the archive. Result The archive is saved as an xml file at the location you selected. 8.1.5.6 Clear archive The archive is organized as a ring buffer, in other words, when it is full, the oldest alarms are deleted from the archive. With the "Clear archive" button, you can delete the entire archive. Procedure To clear the archive, follow these steps: 1. Click the "Clear archive" button in the toolbar of the alarm display. 8.1.5.7 "Active alarms" view The "Active alarms" view is an image of the alarm acknowledgement memory of the selected CPU(s). 8.1.5.8 Layout of the alarms in the "Active alarms" view The "Active alarms" view represents an image of the alarm acknowledgment memory of the selected CPUs. One entry is shown in the table per active alarm. Events of an alarm ("incoming", "outgoing" and "acknowledged") are displayed in one row. Table structure All attributes of the alarms can be shown as columns. You can show or hide individual columns as well as modify the width and order of the columns. These settings are saved when the project is closed. The alarms can be displayed in one or more rows. In the single row display, only the first row of the multiple-row alarm data is displayed. The alarms either require acknowledgment or do not require acknowledgment. The alarms requiring acknowledgment that have not yet been acknowledged are highlighted in bold print and can be acknowledged either with the button in the toolbar for the specific context or with the shortcut menu command "Acknowledge alarm(s)". 946 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks 8.1.5.9 Status of the alarms Depending on whether you are in the "Active alarms" view or the archive view, the displayed alarms may have a different status. Status of the alarms in the "Active alarms" view I: Alarm came IA: Alarm came and was acknowledged IO: Alarm has gone If more signal changes occur than can be sent (signal overflow), OV is displayed as the status and the status is shown in red. Status of the alarms in the archive view No information: only with alarms generated by the PG/PC and displayed in the "Archive" tab, for example logon status, connection abort, mode changes I: Alarm came A: Alarm came and was acknowledged O Alarm has gone D: The alarm was deleted. If more signal changes occur than can be sent (signal overflow), OV is displayed as the status and the status is shown in red. 8.1.5.10 Acknowledging alarms Alarms that must be acknowledged are shown in blue lettering. Procedure To acknowledge an alarm, follow these steps: 1. Select the required alarm or alarms from the table. 2. Click the "Acknowledge" button. Note You can select more than one alarm to acknowledge at the same time. To do this, hold down the <Ctrl> key and then select the alarms you want to acknowledge. WinCC Basic V13.0 System Manual, 02/2014 947 Editing devices and networks 8.1 Configuring devices and networks Result The selected alarm was acknowledged and is then shown in normal characters. Note In the "Active alarms" view, acknowledged alarms that have already gone are no longer displayed. 8.1.5.11 Ignoring alarms Ignoring alarms To ignore alarms, follow these steps: 1. Click the "Ignore" button. The icon is shown on a gray background. Result From this point onwards, all alarms will be ignored. A message is created in the archive view indicating that the display of alarms and events is disabled. Canceling the ignoring of alarms To cancel the ignoring of alarms, follow these steps: 1. Click the "Ignore" button. The icon is shown on a white background. Result All alarms, in other words, even the alarms currently pending on the CPU while the "Ignore alarms" function was active, are displayed again from this point onwards. A message is created in the archive view indicating that the display of alarms and events is enabled again. 8.1.5.12 Keyboard commands in the alarm display Alarm display 948 Function Shortcut keys Select all alarms Ctrl+A Acknowledge all selected alarms Ctrl+Q WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks 8.1.6 Additional information on configurations 8.1.6.1 Functional description of S7-1200 CPUs Operating modes Principles of the operating modes of S7-CPUs Introduction Operating modes describe the behavior of the CPU. The following operating modes are possible: STARTUP RUN STOP In these operating modes, the CPU can communicate via the PN/IE interface, for example. Other operating modes If the CPU is not ready for operation, it is in one of following two operating modes: Deenergized, i.e. the supply voltage is switched off. Defective, which means an internal error has occurred. If the "Defective" status is caused by a firmware error, this state is indicated by the status LEDs of the CPU (refer to the description of the CPU). To find out the cause, follow these steps: - Turn the power supply switch off and on again. - Read out the diagnostics buffer when the CPU starts up and send the data for analysis to Customer Support. If the CPU does not start up, replace it. See also STOP mode (Page 954) RUN mode (Page 954) WinCC Basic V13.0 System Manual, 02/2014 949 Editing devices and networks 8.1 Configuring devices and networks Operating mode transitions Overview The following figure shows the operating modes and the operating mode transitions of S7-1200 CPUs: 32:(5 21 6723 67$5783 581 The following table shows the conditions under which the operating modes will change: No. Operating mode transition Conditions POWER ON STARTUP After switching on, the CPU goes to "STARTUP" mode if: "Warm restart" startup type is set, and the hardware configuration and the program blocks are consistent. Non-retentive memory is cleared and the contents of non-retentive DBs are reset to the initial values of the load memory. Retentive memory and retentive DB contents are retained. POWER ON STOP When startup type "No startup" is set, the CPU goes to "STOP" mode after the supply voltage is switched on. Non-retentive memory is cleared and the contents of non-retentive DBs are reset to the initial values of the load memory. Retentive memory and retentive DB contents are retained. STOP STARTUP The CPU switches to "STARTUP" mode if: CPU is set to "RUN" from the programming device, and the hardware configuration and the program blocks are consistent. STARTUP STOP The CPU returns to the "STOP" mode in the following situations: Error detected during startup. The CPU is set to "STOP" from the programming device. A STOP command is processed in the STARTUP OB. STARTUP RUN If the STARTUP is successful, the CPU switches to "RUN". RUN STOP The CPU returns to the "STOP" mode in the following situations: An error is detected that prevents continued processing. The CPU is set to "STOP" from the programming device. A STOP command is processed in the user program. 950 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks "STARTUP" operating mode Principles of the STARTUP mode Function After turning on the CPU, it executes a startup program before starting to execute the cyclic user program. By suitably programming startup OBs, you can specify certain initialization variables for your cyclic program in the startup program. There is no rule in terms of the number of startup OBs. That is, you can set up one or several startup OBs in your program, or none at all. Parameter settings for startup characteristics You can specify whether the CPU remains in STOP mode or whether a warm restart is run. Over and above this, you can set the response during startup (RUN or previous mode) in the "Startup" group of the CPU properties. Special characteristics Note the following points regarding the "STARTUP" mode: The startup OBs are executed. All startup OBs you have programmed are executed, regardless of the selected startup mode. No time-based program execution can be performed. Interrupt controlled program execution limited to: - OB 82 (diagnostics interrupt) The outputs on the modules are disabled. The process image is not updated; direct I/O access to inputs is possible. See also Editing properties and parameters (Page 423) Principles of the operating modes of S7-CPUs (Page 949) Organization blocks for startup (Page 999) Warm restart (Page 951) Warm restart Function During a warm restart, all non-retentive bit memory is deleted and non-retentive DB contents are reset to the initial values from load memory. Retentive bit memory and retentive DB contents are retained. WinCC Basic V13.0 System Manual, 02/2014 951 Editing devices and networks 8.1 Configuring devices and networks Program execution begins at the call of the first startup OB. Triggering a warm restart You can trigger a "Warm restart" using a corresponding menu command on your programming device in the following situations: The CPU must be in "STOP" mode. After a memory reset After downloading a consistent program and a consistent hardware configuration in the "STOP" mode of the CPU. "POWER ON" triggers a "warm restart" if you have set the following parameters for the startup response: Startup type "warm restart - RUN" (regardless of the CPU operating mode prior to POWER OFF). "Warm restart - mode prior to POWER OFF" (depending on the CPU operating mode prior to POWER OFF. The CPU must have been in RUN mode prior to this.) See also Retentive memory areas (Page 959) Startup activities Overview The following table shows which activities the CPU performs at STARTUP: Activities in execution sequence At warm restart Clear non-retentive bit memories Yes Clear all bit memories No Clear the process image output Yes Processing startup OBs Yes Update the process image input Yes Enable outputs after changing to "RUN" mode Yes Sequence The following figure shows the activities of the CPU in "STOP", "STARTUP", and "RUN" modes. You can use the following measures to specify the state of the I/O outputs in the first cycle of the user program: Use assignable output modules to be able to output substitute values or to retain the last value. Set default values for outputs in startup OBs. 952 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks During the startup, all interrupt events are entered in a queue so that they can be processed later during RUN mode. In RUN mode, hardware interrupts can be processed at any time. 6723 67$5783 5HVHWSURFHVVLPDJHLQSXW 'LVDEOH,2RXWSXWV WXUQRIIUHWDLQODVWYDOXH RUVXEVWLWXWHDYDOXH 5XQVWDUWXS2%V 7UDQVIHU,2LQSXWVWRWKH SURFHVVLPDJHLQSXW (QDEOH,2RXWSXWV 581 2XWSXWSURFHVVLPDJH RXWSXW 7UDQVIHU,2LQSXWVWRWKH SURFHVVLPDJHLQSXW 5XQF\FOLF2%V 2SHUDWLQJV\VWHP DFWLYLWLHV FRPPXQLFDWLRQ VHOIWHVWHWF Special features during startup Response when expected and actual configurations do not match The expected configuration is represented by the engineering configuration loaded on the CPU. The actual configuration is the actual configuration of the automation system. If the expected configuration and actual configuration differ, the CPU nevertheless initially changes to RUN. Canceling a STARTUP If errors occur during startup, the startup is canceled and the CPU remains in "STOP" mode. Under the following conditions, a startup will not be performed or will be canceled: WinCC Basic V13.0 System Manual, 02/2014 953 Editing devices and networks 8.1 Configuring devices and networks If an invalid SD card is inserted. If no hardware configuration has been downloaded. See also Overview of the CPU properties (Page 971) RUN mode Function In "RUN" mode the cyclic, time-driven, and interrupt-driven program sections execute: The process image output is read out. The process image input table is read. The user program is executed. Active data exchange between S7-1200 CPUs by means of Open User Communication is only possible in "RUN" mode. Running the user program Once the CPU has read the inputs, the cyclic program runs from the first to the last instruction. If you have configured a minimum cycle time, the CPU will not end the cycle until this minimum cycle time is up even if the user program is completed sooner. A maximum cycle time is set which you can adjust according to your requirements. This ensures that the cyclic program is completed within a specified time. The system will respond with a time error if the cyclic program is not completed within this time. Other events such as hardware and diagnostic interrupts can interrupt the cyclic program flow and prolong the cycle time. See also Principles of the operating modes of S7-CPUs (Page 949) Events and OBs (Page 963) STOP mode Function In "STOP" mode, the user program is not executed. All outputs are disabled or react according to the parameter settings: They provide a substitute value as set in the parameters or retain the last value output and bring the controlled process to a safe status. The CPU checks the following points: 954 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Hardware, for example whether are all modules are available Whether the default settings for the CPU are applicable or parameter sets are present Whether the general conditions for the programmed startup behavior are correct See also Principles of the operating modes of S7-CPUs (Page 949) Basics of a memory reset Function A memory reset on the CPU is possible only in STOP mode. When memory is reset, the CPU is changed to an "initial status". This means: An existing online connection between your programming device/PC and the CPU is terminated. The content of the work memory and the retentive and non-retentive data are deleted. The diagnostic buffer, the time, the IP address, the hardware configuration, and active force jobs are retained. The load memory (code and data blocks) is then copied to work memory. As a result, the data blocks no longer have current values but their configured initial values. Memory areas Useful information on memory cards How the memory card functions The SIMATIC Memory Card for a S7-1200 is an SD memory card preformatted by Siemens for the CPU user program. You may only delete files and folders. If you format the memory card with Windows, for example with a commercially available card reader, you make the memory card unusable as a storage medium for an S7 CPU. WinCC Basic V13.0 System Manual, 02/2014 955 Editing devices and networks 8.1 Configuring devices and networks Setting the card type You can use the memory card as a transfer card, a program card or a firmware update card. To set the card type, insert the memory card into the card reader of the programming device and select the "Card reader/USB memory" folder from the project tree. In the properties of the selected memory card, designate the card type: Program If it is used as a program card, you can load the user program on the memory card. In this case, the internal load memory of the device is replaced by the memory card and the internal load memory is erased. The user program is then fully executable from the memory card. If the memory card with the user program is removed, there is no longer a program available. Transfer If it is used as a transfer card, you can transfer the user program from the memory card to the internal load memory of the CPU. You can then remove the memory card again. Firmware card Firmware for the S7-1200 modules can be stored on a memory card. Therefore it is possible to perform a firmware update with the help of a specifically prepared memory card. Likewise, a backup copy of firmware for a module can be stored on a memory card. Transferring objects from the project to a memory card When the memory card is inserted in the programming device or in an external card reader, you can transfer the following objects from the project tree to the memory card: Individual blocks (multiple selection possible) In this case a consistent transfer is available, as the dependencies of the blocks to each other is taken into account with block selection. PLC In this case, all objects relevant to processing are transferred, such as blocks and the hardware configuration on the memory card, just as with downloading. To perform the transfer, you can move the objects with drag-and-drop or use the command "Card reader/USB memory > Write to memory card" in the "Project" menu. Transferring objects from the memory card to the project You can transfer Individual blocks (multiple selection is possible) by dragging them to the project. A hardware configuration cannot be transferred from the memory card to the project. 956 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Updating firmware with a memory card You can get the latest firmware data on the Internet from the Service & Support pages: http://support.automation.siemens.com (http://support.automation.siemens.com/WW/view/en/ 34143537) Save the firmware files on the hard disk and plug the SIMATIC Memory Card into the card reader of your programming device. To store the file on the memory card, select the memory card in the "Card Reader/USB memory" folder in the project tree. Select the shortcut menu "Card Reader/USB memory > Create firmware update memory card". Then follow the instructions in the Service & Support portal for performing a firmware update with your CPU. Updating the firmware changes the CPU firmware status. If you have used the CPU in the project, you will have to update the CPU already configured to the CPU with the new firmware status by changing devices offline, and adapt and then load the program or configuration. See also Replacing a hardware component (Page 423) Useful information on CPU firmware versions and STEP 7 versions (Page 1021) Load memory Function Each CPU has an internal load memory. The size of this internal load memory depends on the CPU used. This internal load memory can be replaced by using external memory cards. If there is no memory card inserted, the CPU uses the internal load memory; if a memory card is inserted, the CPU uses the memory card as load memory. The size of the usable external load memory cannot, however, be greater than the internal load memory even if the inserted SD card has more free space. See also Using memory cards (Page 322) Work memory Function Work memory is a non-retentive memory area for storing elements of the user program that are relevant for program execution. The user program is executed exclusively in work memory and system memory. WinCC Basic V13.0 System Manual, 02/2014 957 Editing devices and networks 8.1 Configuring devices and networks System memory System memory areas Function System memory contains the memory elements that each CPU makes available to the user program, such as the process image and bit memory. By using appropriate operations in your user program, you address the data directly in the relevant operand area. The following table shows the operand areas of the system memory: Operand area Description Access via units of the following size: S7 notation Process image output The CPU writes the values from the process image output table to the output modules at the start of the cycle. Output (bit) Q Output byte QB Output word QW Output double word QD The CPU reads the inputs from the input modules and saves the values to the process image input table at the start of the cycle. Input (bit) I Input byte IB Input word IW Input double word ID This area provides storage for intermediate results calculated in the program. Bit memory (bit) M Memory byte MB Memory word MW Memory double word MD Data bit DBX Process image input Bit memory Data block Data blocks store information for the program. They can either be defined so that all code blocks can access them (global DBs) or assigned to a specific FB or SFB (instance DB). Data byte DBB Data word DBW Data double word DBD Local data bit L Local data byte LB Local data word LW Local data double word LD I/O input bit <tag>:P Requirement: The block attribute "Optimized block access" is not enabled. Local data This area contains the temporary data of a block while the block is being processed. Requirement: The block attribute "Optimized block access" is not enabled. Recommendation: Access local data (temp) symbolically. I/O input area 958 The I/O input and output areas permit direct access to WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Operand area Description Access via units of the following size: central and distributed input and output modules. I/O input byte S7 notation I/O input word I/O input double word I/O output area I/O output bit I/O output byte I/O output word I/O output double word See also Diagnostics buffer (Page 961) Basic principles of process images (Page 960) Access to the I/O addresses (Page 962) Retentive memory areas Retentive memory areas Data loss after power failure can be avoided by marking certain data as retentive. This data is stored in a retentive memory area. A retentive memory area is an area that retains its content following a warm restart, in other words, after cycling the power when the CPU changes from STOP to RUN. The following data can be assigned retentivity: Bit memory: The precise width of the memory can be defined for bit memory in the PLC tag table or in the assignment list. Tags of a function block (FB): You can define individual tags as retentive in the interface of an FB if you have enabled optimized block access. Retentivity settings can be defined only in the assigned instance data block if optimized block access has not been activated for the FB. Tags of a global data block: You can define retentivity either for individual or for all tags of a global data block depending on the settings for access. - Block with optimized access: retentivity can be set for each individual tag. - Block with standard access: The retentivity setting applies to all tags of the DB; either all tags are retentive or no tag is retentive. See also Warm restart (Page 951) WinCC Basic V13.0 System Manual, 02/2014 959 Editing devices and networks 8.1 Configuring devices and networks process image input/output Basic principles of process images Function When the user program addresses the input (I) and output (O) operand areas, it does not query or change the signal states on the digital signal modules. Instead, it accesses a memory area in the system memory of the CPU. This memory area is referred to as the process image. Advantages of the process image Compared with direct access to input and output modules, the main advantage of accessing the process image is that the CPU has a consistent image of the process signals for the duration of one program cycle. If a signal state on an input module changes during program execution, the signal state in the process image is retained until the process image is updated again in the next cycle. The process of repeatedly scanning an input signal within a user program ensures that consistent input information is always available. Access to the process image also requires far less time than direct access to the signal modules since the process image is located in the internal memory of the CPU. Updating the process images Sequence The operating system updates the process images at cyclic intervals unless defined otherwise in your configuration. The process image input/output is updated in the following order: 1. The internal tasks of the operating system are performed. 2. The process image output (PIQ) table is written to the outputs of the module. 3. The status of inputs is read to the process image input (PII) table. 4. The user program is executed with all the blocks that are called in it. The operating system automatically controls the writing of the process image output to the outputs of the modules and the reading of the process image input. Special characteristics You have the option of accessing inputs or outputs directly using direct I/O access. If an instruction accesses an output directly and the output address is located in the process image output, the process image of the relevant output is updated. If an instruction accesses an output directly and the output address is not located in the process image output, the process image of the relevant output is not updated. 960 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Example of normal I/O access by way of the process image 029( , 0: (1 (12 ,1 287 4 4: Update QW10 in the I/O output area with the value from MW0. I/O access error during process image updating If an error occurs during process image updating (I/O access error), the CPU reacts with the default system reaction "Ignore". See also Start address of a module (Page 962) Access to the I/O addresses (Page 962) Startup activities (Page 952) Diagnostics buffer Function The diagnostics buffer is part of the system memory of the CPU. It contains the errors detected by the CPU or modules with diagnostics capability. It includes the following events: Every mode change of the CPU (for example, POWER UP, change to STOP mode, change to RUN mode) Every diagnostics interrupt The diagnostics buffer of the S7-1200-CPU has a capacity of 50 entries of which the last (most recent) 10 entries are retained following power cycling. Those entries can only be cleared by restoring the CPU to factory defaults. You can read the content of the diagnostics buffer with the help of the Online and Diagnostics view. See also Basic information on the diagnostics buffer (Page 1129) WinCC Basic V13.0 System Manual, 02/2014 961 Editing devices and networks 8.1 Configuring devices and networks I/O data area Start address of a module Definition The start address is the lowest byte address of a module. It acts as the initial address of the module user data area. Configuring module start addresses The addresses used in the user program and the module start addresses are coordinated when the modules are configured. In the module properties ("I/O addresses" group), you can change the start addresses that were assigned automatically after the modules were inserted. You can also make a setting that decides whether or not the addresses are located in the process image. Access to the I/O addresses I/O addresses If you insert a module in the device view, its user data is located in the process image of the S7-1200 CPU (default). The CPU handles the data exchange between the module and the process image area automatically during the update of the process images. Append the suffix ":P" to the I/O address if you want the program to access the module directly instead of using the process image. This could be necessary, for example, during execution of a time-sensitive program which also has to control the outputs within the same cycle. 962 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Basics of program execution Events and OBs Events and OBs The operating system of S7-1200-CPUs is based on events. There are two types of events: Events which can start an OB Events which cannot start an OB An event which can start an OB triggers the following reaction: It calls the OB you possibly assigned to this event. The event is entered in a queue according to its priority if it is currently not possible to call this OB. The default system reaction is triggered if you did not assign an OB to this event. An event which cannot start an OB triggers the default system reaction for the associated event class. The user program cycle is therefore based on events, the assignment of OBs to those events, and on the code which is either contained in the OB, or called in the OB. The following table provides an overview of the events which can start an OB, including the associated event classes and OBs. The table is sorted based on the default OB priority. Priority class 1 is the lowest. Event class OB no. Cyclic program Number of OBs Start event OB priority (default) 1, >= 123 >= 1 Starting or end of the last program cycle OB 1 Startup 100, >= 123 >=0 STOP to RUN transition 1 Time-of-day interrupt >= 10 Max. 2 Start time has been reached 2 Time-delay interrupt >= 20 Max. 4 Delay time expired 3 Cyclic interrupt >= 30 Constant bus cycle time expired 8 Hardware interrupt >= 40 Positive edge (max. 16) 18 Max. 50 (more can be used with DETACH and ATTACH) Negative edge (max. 16) HSC: Count value = reference value (max. 6) 18 HSC: Count direction changed (max. 6) HSC: External reset (max. 6) Status interrupt 55 0 or 1 CPU has received status interrupt 4 Update interrupt 56 0 or 1 CPU has received update interrupt 4 Manufacturer- or profilespecific interrupt 57 0 or 1 CPU has received manufacturer-specific or profile-specific interrupt 4 Diagnostic error interrupt 82 0 or 1 Module has detected an error 5 Pull/plug interrupt 83 0 or 1 Removal/insertion of modules of distributed I/O 6 WinCC Basic V13.0 System Manual, 02/2014 963 Editing devices and networks 8.1 Configuring devices and networks Event class OB no. Number of OBs Start event OB priority (default) Rack error 86 0 or 1 Error in the I/O system of the distributed I/O 6 Time error 80 0 or 1 Maximum cycle time exceeded 22 Called OB is still being executed Time-of-day interrupt missed Time-of-day interrupt missed during STOP Queue overflow Interrupt loss due to high interrupt load The following table describes events which do not trigger an OB start, including the corresponding reaction of the operating system. The table is sorted based on event priority. Event class Event Event priority System reaction 21 STOP I/O access error during process image update I/O access error during process image update 22 Ignore Programming error Programming error in a block for which you use system reactions provided by the operating system (note: the error handling routine in the block program is executed if you activated local error handling). 23 RUN I/O access error I/O access error in a block for which you use 24 system reactions provided by the operating system (note: the error handling routine in the block program is executed if you activated local error handling). RUN Insert/remove central modules Insert/remove a module Maximum cycle time exceeded Maximum cycle time exceeded twice twice 27 STOP Assignment between OBs and events With the exception of the cyclic program and startup program and event can only be assigned to one OB. However, in certain event classes such as hardware interrupts one and the same OB can be assigned to several events. The assignment between OBs and events is defined in the hardware configuration. Defined assignments can be changed at runtime by means of ATTACH and DETACH instructions. OB priority and runtime behavior S7-1200-CPUs support the priority classes 1 (lowest) to 27 (highest). An OB is assigned the priority of its start event. OBs are always executed on a priority basis: The OBs with the highest priority are executed first. Events of the same priority are processed in order of occurrence. 964 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks As of firmware version V4.0 of the S7-1200 CPUs you can specify in the device configuration, under properties of the CPU, if the OBs are interruptible or not. This parameter assignment has an effect on all OBs with exception of the cycle OBs which are always interruptible. The following applies to S7-1200 CPUs with firmware version < V4.0: Any OB with priority >= 2 will interrupt cyclic program execution. An OB of priority 2 to 25 cannot be interrupted by any event of priority group 2 to 25. This rule also applies to events of a priority higher than that of the currently active OB. Such events are processed later. A time error (priority 26) will interrupt any other OB. The following applies to S7-1200 CPUs as of firmware version V4.0: If you do not configure the OBs as interruptible, an OB is always processed completely even if an event of a higher priority occurs during its runtime. Specifically, this means: Any OB with priority >= 2 will interrupt cyclic program execution. An OB of priority 2 to 25 cannot be interrupted by any event. This rule also applies to events of a priority higher than that of the currently active OB, which also includes a time error. Such events are processed later. If you do configure the OBs as interruptible and an event of a higher priority occurs during the runtime of an OB, the running OB is interrupted and the OB associated with the occurring event is processed. Once this OB has been completed, processing of the interrupted OB continues. Specifically, this means: Any OB with priority >= 2 will interrupt cyclic program execution. An OB of priority 2 to 25 can be interrupted by any event whose priority is higher than that of the running OB. This is also true for time errors: A time error (priority 26) will interrupt any OB. OB start information Certain OBs have start information, while others do not. This is explained in greater detail in the description of the relevant OB. See also Event-based program execution (Page 965) Event-based program execution OB priority and runtime behavior S7-1200-CPUs support the priority classes 1 (lowest) to 27 (highest). An OB is assigned the priority of its start event. Interrupt OBs can only be interrupted by time error interrupts. This rule also applies to events of a priority higher than that of the currently active OB. That is, only one interrupt OB can be active, with exception of the time error interrupt OB. WinCC Basic V13.0 System Manual, 02/2014 965 Editing devices and networks 8.1 Configuring devices and networks Any further event of generated while an interrupt OB is being executed is added to a queue in accordance with its priority. Start events within a queue are processed later based on the chronological order of their occurrence. Program execution on the CPU Cyclic OBs are interrupted by interrupt OBs. Reactions to events which start an interrupt OB: For CPUs up to firmware version V3: Interrupt OBs can only be interrupted by time error interrupt OBs. For CPUs as of firmware version V4: Interrupt OBs can be interrupted by interrupt OBs of a higher priority. The figure below shows the basic procedure in case interrupt OBs cannot be interrupted (behavior up to firmware version V3): 966 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks (YHQWV &\FOLF2%V ,QWHUUXSW2%V 7LPHHUURULQWHUUXSW2%V :ULWH3,4 5HDG3,, %HJLQ 2% ,QWHUUXSWLRQ 5HVXPH 2% ,QWHUUXSWLRQ %HJLQ 2%[[ (QG %HJLQ 2%[\ ,QWHUUXSWLRQ 5HVXPH 2%[\ (QG %HJLQ 2% 7LPHHUURU LQWHUUXSW (QG %HJLQ 2%[] (QG 5HVXPH 2% (QG and %HJLQ 2%[] (QG An event (e.g. a hardware interrupt) calls its associated OB. A called OB is executed without interruption, including all of its nested blocks. Execution of the cyclic OB is resumed on completion of interrupt processing, provided the queue does not contain any events which trigger an OB start. An interrupt OB can only be interrupted by a time error interrupt OB (OB 80). An new alarm-triggering event occurs during interrupt processing. Reaction for CPUs up to and including firmware version V3: This new event is added to a queue. The queued events successively call their corresponding OBs only after execution of the current interrupt OBs was completed and according to the following rules: Events are processed in the order of their priority (starting at the highest priority). Events of the same priority are processed in chronological order. Reaction for CPUs as of firmware version V4: You use a CPU parameter to set the interruptibility for CPUs as of firmware version V4. Default behavior: OBs are interruptible. In this case: If the new event has a higher priority than the currently running OB, the OB started by the new event interrupts the currently running OB. WinCC Basic V13.0 System Manual, 02/2014 If you disable the option, the interrupt OBs cannot be interrupted. The cyclic OBs are processed one after the other. 967 Editing devices and networks 8.1 Configuring devices and networks Notes on queues Every priority class (OBs of the same priority to be called) is assigned a separate queue. The size of those queues is set by default. Any new event leading to the overflow of a queue is discarded and therefore lost. A "time error interrupt event" is generated simultaneously. Information identifying the OB that caused the error is included in the start information of the time error interrupt OB (OB 80). A corresponding reaction such as an alarm trigger can be programmed in the time error interrupt OB. Example of a hardware interrupt event The function principle of event-oriented program execution in the S7-1200 CPU is described based on the example of a hardware interrupt-triggering module. Process events and their priority Process events are triggered by the I/O (e.g. at a digital input) and initiate a call of the assigned OB in the S7-1200 CPU. OBs assigned to a process event are called hardware interrupt OBs. Examples of process events and their priority: Process events "rising edge" or "falling edge" at an interrupt-triggering module: The hardware interrupt OB started by such an event is always assigned priority 5. Process events from a high-speed counter - Count value corresponds to the reference value - Change count direction - External reset of the high-speed counter The hardware interrupt OB started by this event is always assigned priority 6. The figure below shows the chronological sequence of hardware interrupt execution: In the case of two hardware interrupt events in immediate succession, the second hardware interrupt triggering event is held back in the queue until the first OBx has been processed. The next hardware interrupt triggering event can only start the associated OBx when the OBx has been processed. Additional hardware interrupt triggering events are lined up in the queue according to this principle. 968 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks &38 0RGXOH %HJLQ 2%[ ', &38 0RGXOH :$,7 %HJLQ 2%[ ', &38 0RGXOH :$,7 %HJLQ 2%[ (QG ', %HJLQ 2%[ Hardware interrupt execution A hardware interrupt-triggering event such as a rising edge at the input calls the OB to which it is assigned. If a new event occurs that triggers a hardware interrupt while the OB is executing, this event is entered in a queue. The new event that triggers a hardware interrupt starts the hardware interrupt OB assigned to the event. Assigning the interrupt-triggering event The interrupt-triggering event is assigned to an OB in the input properties of the device view. An interrupt-triggering event can only be assigned to a single OB. OBs, however, can be assigned to several interrupt-triggering events. This means, for example, that you can assign both the rising and the falling edge to the same interrupt OB in order to trigger the same reaction to any change of the input signal. WinCC Basic V13.0 System Manual, 02/2014 969 Editing devices and networks 8.1 Configuring devices and networks The started OB can interrupt a cycle OB at every instruction. Consistent data access is secured up to dword size. You can parameterize module-specific interrupt-triggering events such as a rising and the falling edge at the input. Assign the interrupt-triggering event and the OB to be started in the configuration of the interrupt-triggering module. However, within the started hardware interrupt OB you can override this assignment using the DETACH instruction, or assign the same event to a different OB using the ATTACH instruction. This functionality allows a flexible reaction to external process signals. Setting the operating behavior Changing properties of the modules Default settings When they leave the factory, all hardware components with parameters have default settings suitable for standard applications. These default values allow the hardware components to be used immediately without making any additional settings. You can, however, modify the behavior and the properties of the hardware components to suit the requirements and circumstances of your application. Hardware components with settable parameters include, for example, communications modules and several analog and digital modules. Setting and loading parameters When you have selected a hardware component in the device or network view, you can set the properties in the Inspector window. When you save a device configuration with its parameters, data is generated that needs to be loaded on the CPU. This data is transferred to the relevant modules during startup. Properties of the CPUs The properties of the CPUs have special significance for system behavior. For example for a CPU you can set: Interfaces Inputs and outputs High-speed counters Pulse generators Startup behavior Time-of-day Protection level Bit memory for system and clock 970 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Cycle time Communications load The entry possibilities specify what is adjustable and in which value ranges. Fields that cannot be edited are disabled or are not shown in the properties window. Requirement You have already arranged the hardware components for which you want to change properties on a rack. Procedure To change the properties and parameters of the hardware components, follow these steps: 1. In the device or network view, select the hardware component or interface that you want to edit. 2. Edit the settings for the selected object: - For example in the device view you can edit addresses and names. - In the Inspector window additional setting possibilities are available. You do not need to confirm your entries, the changed values will be applied immediately. See also Editing properties and parameters (Page 423) Introduction to loading a configuration (Page 933) CPU properties Overview of the CPU properties Overview The following table provides you with an overview of the CPU properties: Group Properties Description General Project information General information to describe the inserted CPU. Except for the slot number, you can change this information. Catalog information Read-only information from the hardware catalog for this CPU. General Name and comment for this PROFINET interface. The name is limited to 110 characters. PROFINET interface WinCC Basic V13.0 System Manual, 02/2014 971 Editing devices and networks 8.1 Configuring devices and networks Group Properties Description Ethernet addresses Select whether the PROFINET interface is networked. If subnets have already been created in the project, they are available for selection in the drop-down list. If not, you can create a new subnet with the "Add new subnet" button. Information on the IP address, subnet mask and IP router usage in the subnet is available in the IP protocol. If an IP router is used, the information about the IP address of the IP router is necessary. Advanced options Name, comment and additional setting options of the Ethernet interface port. Time synchronization Settings for time synchronization in the NTP time format. The NTP (network time protocol) is a general mechanism for synchronizing system clocks in local and global area networks. In NTP mode, the interface of the CPU sends time queries (in client mode) at regular intervals to NTP servers on the subnet (LAN) and the addresses must be set in the parameters here. Based on the replies from the server, the most reliable and most accurate time is calculated and synchronized. The advantage of this mode is that it allows the time to be synchronized across subnets. The accuracy depends on the quality of the NTP server being used. DI#/DO# General Name of and comment on the integrated digital inputs of the CPU. Digital inputs Input delays can be set for digital inputs. The input delays can be set in groups (in each case for 4 inputs). The detection of a positive and a negative edge can be enabled for each digital input. A name and a hardware interrupt can be assigned to this event. Depending on the CPU, pulse catches can be activated at various inputs. When the pulse catch is activated, even pulse edges that are shorter than the cycle time of the program are detected. Digital outputs The reaction to a mode change from RUN to STOP can be set for all digital outputs: The state can either be frozen (corresponds to retain last value) or you set a substitute value ("0" or "1") AI# 972 I/O addresses The address space of the input and output addresses is specified as is the process image. Hardware identifier The hardware identifier of the device is displayed. General Name of and comment on the integrated analog inputs of the CPU. WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Group Properties Description Analog inputs During noise reduction, the specified integration time suppresses interference frequencies at the specified frequency (in Hz). The channel address, measurement type, voltage range, smoothing and overflow diagnostics must be specified in the "Channel #" group. The measurement type and voltage range are set permanently to voltage, 0 to 10 V. Smoothing analog values provides a stable analog signal for further processing. Smoothing analog values can be useful with slow measured value changes, for example, in temperature measurement. The measured values are smoothed with digital filtering. Smoothing is achieved by the module forming mean values from a specified number of converted (digitalized) analog values. The selected level (slight, medium, strong) decides the number of analog signals used to create the mean value. If overflow diagnostics is enabled, a diagnostics event is generated if an overflow occurs. I/O addresses The address space of the input addresses is specified as is the process image. Hardware identifier The hardware identifier of the device is displayed. High-speed counter (HSC) High-speed counter (HSC)# High-speed counters are typically used to drive counting mechanisms. Pulse generators (PTO/PWM) PTO#/PWM# See: Configuring high-speed counters (Page 982) A pulse generator is activated and can be initialized with project information. For the configuration of an activated pulse generator, specify the usage as PWM (Pulse Width Modulation) or as PTO (Pulse Train Output). Specify the output source, time base, pulse width format, cycle time and initial pulse width for PWM. A pulse output is specified as the hardware output. The PWM output is controlled by the CTRL_PWM instruction, see CTRL_PWM. Specify the output source for PTO. A pulse output and a direction output are specified as the hardware outputs. A PTO is operated together with a high-speed counter in the "axis of motion" count mode and controlled by the Motion Control technology object (see keyword "Motion Control S7-1200") . The hardware ID is displayed in the I/O-diagnostics addresses and, if the PWM function is selected, the address space of the output addresses and the process image can be selected. Startup Startup after POWER ON Setting the startup characteristics after cycling power. See: Principles of the STARTUP mode (Page 951) Comparison of preset configuration and actual configuration Specifies whether modules (SM, SB, CM, CP or even the CPU) can be replaced: Startup of the CPU only if compatible Startup of the CPU even if there are differences Example: A signal module with 16 digital inputs and 16 digital outputs (DI16/DQ16) can be a compatible replacement for a signal module with 8 digital outputs (DQ8) or 4 digital inputs (DI4). WinCC Basic V13.0 System Manual, 02/2014 973 Editing devices and networks 8.1 Configuring devices and networks Group Properties Description Parameter assignment time for distributed I/O Specifies a maximum period (standard: 60000 ms) in which the distributed I/O must start up. (The CMs and CPs are supplied with voltage and communication parameters during the CPU startup. This configuration time provides a time period during which I/O modules connected to the CM or CP must start up.) The CPU switches to RUN as soon as the distributed I/O has started and is ready for operation, regardless of the "Parameter assignment time for distributed I/O" parameter. If the distributed I/O has not started up during this period, the CPU switches to RUN without the distributed I/O. Cycle Maximum cycle time and minimum cycle time. Specification of a maximum cycle time or a fixed minimum cycle time. If the cycle time exceeds the maximum cycle time, the CPU goes to STOP mode. See: Cycle time and maximum cycle time (Page 975) Communication load Maximum allocation of the cycle for communication (as a percentage) Controls the duration of communication processes that always also extend the cycle time, within certain limits. Examples of communication processes include: Transferring data to another CPU or loading blocks (initiated via the PC). See: Cycle loading by communications (Page 976) System and clock memory System memory bits and clock memory bits You use system memory bits for the following scans: Is the current cycle the first since cycling power? Have there been any diagnostics state changes compared with the previous cycle? Scan for "1" (high) Scan for "0" (low) Clock memory bits change their values at specified periodic intervals. See: Enabling system memory (Page 992) See: Using clock memory (Page 993) Web server Automatic update Sends the requested web page with current CPU data periodically to the web browser. Enter the period duration under "Update interval". Automatic update can only be activated if the web server is enabled. See: Auto-Hotspot User-defined web pages Allows access to freely-designed web pages of the CPU via a web browser. See: Auto-Hotspot Time Local time and daylight saving time Setting of the time zone in which the CPU is operated and setting of the daylight-saving/standard time changeover. Protection Protection and password for read/ Setting the read/write protection and the password for access to write access the CPU. See: Setting options for the protection level (FW V1 to V3) (Page 994) See: Setting options for the protection (FW as of V4) (Page 995) 974 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Group Properties Description Connection resources - Display of available, reserved and previously configured connection resources of the CPU. Address overview Tabular representation of all addresses used by the CPU for integrated inputs/outputs as well as for the inserted modules. Addresses that are not used by any module are represented as gaps. - The view can be filtered according to Input addresses Output addresses Address gaps See also Specifying input and output addresses (Page 666) Assigning parameters to hardware interrupt OBs (Page 1016) Access to the I/O addresses (Page 962) Addressing modules (Page 665) Special features during startup (Page 953) Cycle time and maximum cycle time Function The cycle time is the time that the operating system requires to execute the cyclic program and all the program sections that interrupt this cycle. The program execution can be interrupted by: Time errors and 2xMaxCycleTime errors System activities, e.g., process image updating The cycle time (Tcyc) is therefore not the same for every cycle. The following schematic shows an example of different cycle times (TZ1 TZ2) for S7-1200 CPUs: WinCC Basic V13.0 System Manual, 02/2014 975 Editing devices and networks 8.1 Configuring devices and networks 'LIIHUHQWF\FOHWLPHVIRU6&38V &XUUHQWF\FOH 1H[WF\FOH 7] 1H[WF\FOH 7] 2% 8SGDWLQJWKH 8SGDWLQJWKH3,, 2% 3,2 2% 2% 8SGDWLQJWKH 3,2 8SGDWLQJWKH 3,, 2% 2% 8SGDWLQJWKH 3,2 3,,3URFHVVLPDJHLQSXW 3,23URFHVVLPDJHRXWSXW In the current cycle, the cyclic OB used here (e.g. OB 1) will be interrupted by a time error (e.g. OB 80). Following the cyclic OB, the next cycle OB 201 is processed. Maximum cycle time The operating system monitors the execution time of the cyclic program for a configurable upper limit known as the maximum cycle time. You can restart this time monitoring at any point in your program by calling the RE_TRIGR instruction. If the cyclic program exceeds the maximum cycle time, the operating system will attempt to start the time error OB (OB 80). If the OB is not available, the CPU ignores the overshoot of the maximum cycle time. In addition to monitoring the runtime for overshooting of the maximum cycle time, adherence to a minimum cycle time is guaranteed. To do this, the operating system delays the start of the new cycle until the minimum cycle time has been reached. During this waiting time, new events and operating system services are processed. If the maximum cycle time is exceeded a second time, for example while the time error OB is being processed (2xMaxCycleTime error), the CPU changes to STOP mode. Cycle loading by communications Function The cycle time of the CPU can be extended due to communications processes. These communications processes include for example: Transferring data to another CPU Loading of blocks initiated by a programming device You can control the duration of these communications processes to some extent using the CPU parameter "Cycle load due to communication". 976 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks In addition to communications processes, test functions also extend the cycle time. The "Cycle load due to communication" parameter can be used to influence the duration. How the parameter works You use the "Cycle load due to communication" parameter to enter the percentage of the overall CPU processing capacity that can be available for communications processes. This CPU processing capacity is now available at all times for communication. This processing capacity can be used for program execution when not required for communication. Effect on the actual cycle time The "Cycle load due to communication" parameter can be used to extend the cycle time of the cyclic organization block (e.g., OB 1) by a factor calculated according to the following formula: &\FOHORDGGXHWRFRPPXQLFDWLRQ The formula does not take into account the effect of asynchronous events such as hardware interrupts or cyclic interrupts on the cycle time. If the cycle time is extended due to communication processes, more asynchronous events may occur within the cycle time of the cyclic organization block. This extends the cycle still further. The extension depends on how many events occur and how long it takes to process them. Example 1 - no additional asynchronous events: If the "Cycle load due to communication" parameter is set to 50%, this can cause the cycle time of the cyclic organization block to increase by up to a factor of 2. Example 2 - additional asynchronous events: For a pure cycle time of 500 ms, a communication load of 50% can result in an actual cycle time of up to 1000 ms, provided that the CPU always has enough communications jobs to process. If, parallel to this, a cyclic interrupt with 20 ms processing time is executed every 100 ms, this cyclic interrupt would extend the cycle by a total of 5*20 ms = 100 ms without communication load. That is, the actual cycle time would be 600 ms. Because a cyclic interrupt also interrupts communications, it affects the cycle time by adding 10 * 20 ms at 50 % communication load. That is, in this case, the actual cycle time amounts to 1200 ms instead of 1000 ms. Note Observe the following: Check the effects of changing the value of the "Cycle load due to communication" parameter while the system is running. You must always consider the communication load when setting the minimum cycle time as time errors will otherwise occur. WinCC Basic V13.0 System Manual, 02/2014 977 Editing devices and networks 8.1 Configuring devices and networks Recommendations Increase this value only if the CPU is used primarily for communication purposes and the user program is not time critical. In all other situations you should only reduce this value. Time-of-day functions Basic principles of time of day functions All S7-1200 CPUs are equipped with an internal clock. The backup supports the display of the correct time for up to 10 hours if the power supply is interrupted. Time-of-day format The clock always shows the time of day with a resolution of 1 millisecond and the date including the day of the week. The time adjustment for daylight-saving time is also taken into account. Setting and reading the time of day Setting and reading the time with instructions You can set, start and read the time-of-day and date on the CPU clock with the following instructions in the user program: Set the time-of-day: "WR_SYS_T" Read time of day "RD_SYS_T" Read local time "RD_LOC_T" Set time zone "SET_TIMEZONE" Manual setting You can also read and set the time-of-day manually in the online and diagnostics view under "Functions > Set time-of-day". 978 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Assigning the clock parameters Clock parameters The clock parameters allow you to make the following settings: Enable time synchronization via NTP server Select this check box if you want the internal clock to be synchronized using the NTP synchronization mode. Network time server The IP addresses of up to four NTP servers need to be configured. Update interval The update interval defines the interval between time queries. High-speed counters General information on high-speed counters Introduction High-speed counters are typically used to drive counting mechanisms in which a shaft turning at a constant speed is equipped with an incremental step encoder. The incremental step encoder ensures a certain number of count values per rotation and a reset pulse once per rotation. The clock memory bit(s) and the reset pulse of the incremental step encoder supply the inputs for the high-speed counter. The various S7-1200 CPUs have differing numbers of high-speed counters available: S7-1200 CPU Number of HSCs HSC designation CPU 1211C 3 (with digital signal board 4)* HSC1...3 (and HSC5)* CPU 1212C 4 (with digital signal board 5)* HSC1...4 (and HSC5)* CPU 1214C 6 HSC1...6 CPU 1215C CPU 1217C * with DI2/DO2 signal board How it works The first of several default values is loaded on the high-speed counter. The required outputs are enabled for the time during which the current value of the counter is lower than the default value. The counter is set up so that an interrupt occurs if the current value of the counter is equal to the default value or when the counter is reset. If the current value is equal to the default value and an interrupt event results, a new default value is loaded and the next signal state is set for the outputs. If an interrupt event occurs because the counter is reset, the first default value and the first signal states of the outputs are set and the cycle repeated. WinCC Basic V13.0 System Manual, 02/2014 979 Editing devices and networks 8.1 Configuring devices and networks Since the interrupts occur much less frequently than the high-speed counter counts, a precise control of the fast operations can be implemented with only a slight influence on the overall cycle of the automation system. Since you can assign specific interrupt programs to interrupts, each new default can be loaded in a separate interrupt program allowing simple control of the state. Note You can also process all interrupt events in a single interrupt program. Count algorithms of the various counters All counters work in the same way, however some high-speed counters do not support all count algorithms. There are four basic count algorithms: Single-phase counter with internal direction control Single-phase counter with external direction control 2-phase counter with 2 clock inputs A/B counter Each high-speed counter can be used with or without a reset input. If the reset input is activated, this resets the current value. The current value remains reset until the reset input is deactivated. See also Configuring high-speed counters (Page 982) Interdependency of the counter mode and counter inputs (Page 980) Interdependency of the counter mode and counter inputs General information on counter mode and counter inputs You can assign not only the counter modes and counter inputs to the high-speed counters but also functions such as clock pulse generator, direction control, and reset. The following rules apply: An input cannot be used for two different functions. If an input is not required by the current counter mode of the defined high-speed counter, it can be used other purposes. If, for example, you set HSC1 to counter mode 1, in which inputs I0.0 and I0.3 are required, you can use I0.1 for edge interrupts or for HSC2. If, for example, you set HSC1 and HSC5, inputs I0.0 (HSC1) and I1.0 (HSC5) are always used with the counting and frequency counter modes. As a result, these two inputs are not available for any other functions when counters are operated. You have additional inputs available if you use a digital signal board. 980 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Overview of the interdependency of counter mode and counter inputs Counter mode Description Inputs HSC1 I0.0 (CPU) I0.1 (CPU) I0.3 (CPU) I4.0 (signal board) I4.1 (signal board) I4.3 (signal board) I0.2 (CPU) I0.3 (CPU) I0.1 (CPU) HSC2 Counting / frequency I4.2 (signal board) I4.3 (signal board) I4.1 (signal board) HSC3* I0.4 (CPU) I0.5 (CPU) I0.7 (CPU) HSC4 (CPU 1212/14/15/17C only) I0.6 (CPU) I0.7 (CPU) I0.5 (CPU) HSC5 (CPU 1214/15/17C only)** I1.0 (CPU) I1.1 (CPU) I1.2 (CPU) I4.0 (signal board) I4.1 (signal board) I4.3 (signal board) HSC6 (CPU 1214/15/17C only)** I1.3 (CPU) I1.4 (CPU) I1.5 (CPU) Single-phase counter with internal direction control Clock pulse generator - - Single-phase counter with external direction control Clock pulse generator Direction 2-phase counter with 2 clock inputs Clock pulse generator forwards Clock pulse generator backwards A/B counter Clock pulse generator A Clock pulse generator B Pulse generators PWM/PTO HSC1 and HSC2 support the motion axis count mode for the PTO1 and PTO2 pulse generators: Counting Resetting Counting / frequency Counting Resetting Counting / frequency Counting Resetting Counting / frequency Counting Resetting Motion axis For PTO1, HSC1 evaluates the Q0.0 outputs for the number of pulses. For PTO2, HSC2 evaluates the Q0.2 outputs for the number of pulses. Q0.1 is used as the output for the motion direction. * HSC3 can only be used for CPU 1211 without a reset input ** HSC5 can be also be used for CPU 1211/12 if a DI2/DO2 signal board is used See also General information on high-speed counters (Page 979) Configuring high-speed counters (Page 982) WinCC Basic V13.0 System Manual, 02/2014 981 Editing devices and networks 8.1 Configuring devices and networks Configuring high-speed counters Requirement An S7-1200 CPU has been inserted in the hardware configuration. Procedure To configure a high-speed counter, follow these steps: 1. Select an S7-1200 CPU in the device or network view. 2. Click on the required high-speed counter under "Properties > High-speed counter" in the inspector window: - CPU 1211C: HSC1 to HSC3 (also HSC5 with a DI2/DO2 signal board) - CPU 1212C: HSC1 to HSC4 (also HSC5 with a DI2/DO2 signal board) - CPU 1214C / 1215C / 1217C: HSC1 to HSC6 3. Enable the high-speed counter in the "General" parameter group using the relevant check box. Note If you use a CPU 1211C or CPU 1212C with a DI2/DO2 signal board, you can also enable the high-speed counter HSC5. Note If you activate the pulse generators and operate them as PTO1 or PTO2, they use the associated high-speed counter HSC1 or HSC2 with "Motion axis" counting mode to evaluate the hardware outputs. If you configure high-speed counter HSC1 or HSC2 for other counting tasks, these cannot be used by pulse generator PTO1 or PTO2, respectively. If required, you can enter a name and a comment for the high-speed counter here. 4. Define the functionality of the high-speed counter in the "Function" parameter group: - Count mode: Select what you want to be counted from the drop-down list. - Operating phase: Select the count algorithm from the drop-down list. - Input source: Select the on-board CPU inputs or the inputs of an optional digital signal board as the input source for the count pulses from the drop-down list. - Count direction is specified by: If you have selected a single-phase operating phase, open the drop-down list and select whether the count direction is set internally by an SFB parameter of the user program or externally via a digital input. - Initial count direction: If the user program is set as the internal direction control for the count direction, you can select the count direction at the start of counting from the dropdown list. - Frequency meter period: If frequency is set as the count mode, you can select the duration of the frequency meter periods in the drop-down list. 982 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks 5. Specify the initial values and reset condition of the high-speed counter in the "Reset to initial values" parameter group: - Initial counter value: Enter a start value for the high-speed counter. - Initial reference value: Enter a maximum value for the high-speed counter. Here, you can also specify whether the high-speed counter will use a reset input and the set the corresponding signal level for the reset input from the drop-down list. 6. Configure the reaction of the high-speed counter to certain events in the "Event configuration" parameter group. The following events can trigger an interrupt: - The counter value matches the reference value. - An external reset event was generated. - A change of direction was triggered. Enable an interrupt reaction using the check box, enter a name and select a hardware interrupt for the interrupt from the drop-down list. 7. Assign the start address for the high-speed counter in the "I/O/Diagnostics addresses" parameter group. Note In the "Hardware inputs" parameter group, you can only see which hardware inputs and values are being used for the clock, direction determination, reset pulse, and maximum count speed. Result You have now adapted the parameters of the high-speed counter to the requirements of your project. See also General information on high-speed counters (Page 979) Interdependency of the counter mode and counter inputs (Page 980) Point-to-point communication Overview of point-to-point communication PtP communication is communication via a serial interface that uses standardized UART data transmission (Universal Asynchronous Receiver/Transmitter). The S7-1200 uses communications modules with an RS-232 or RS-485 interface to establish PtP communication. WinCC Basic V13.0 System Manual, 02/2014 983 Editing devices and networks 8.1 Configuring devices and networks Functions of point-to-point communication Point-to-point communication (PtP) allows numerous applications: Direct transmission of information to an external device, for example a printer or a barcode reader Reception of information from external devices such as barcode readers, RFID readers, cameras and third-party optical systems as well as many other devices. Exchange of information with third-party devices, for example GPS devices, radio modems and many others The Freeport protocol The S7-1200 supports the Freeport protocol for character-based serial communication. Using Freeport communication, the data transmission protocol can be configured entirely by the user program. Siemens provides libraries with Freeport communication functions that you can use in your user program: USS Drive protocol Modbus RTU Master protocol Modbus RTU Slave protocol See also Configuring a communications port (Page 985) Using RS-232 and RS-485 communications modules Communications modules with RS-232 and RS-485 interfaces In an S7-1200 CPU, you can use two different communications modules: RS-232 communications module RS-485 communications module The communications modules can be connected to the S7-1200 CPU via the I/O channel on the left. You can plug in up to three different modules. Properties of the communications modules The communications modules have the following features: Support of the Freeport protocol Configuration by the user program with the aid of expanded instructions and library functions 984 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Configuring a communications port Configuring a communications port After you have inserted a communications module with an RS-232 or RS-485 interface, you then set the interface parameters. You set the parameters for the interface either in the properties of the interface or you control the interface parameters from the user program using the PORT_CFG instruction. The following description relates to the graphic configuration. Note If you use the user program to change the port setting, the settings of the graphic configuration are overwritten. You should also keep in mind that the settings made by the user program are not retained if there is a power down. Requirement A communications module is already plugged in. You are in the device view. Procedure To configure the communications port, proceed as follows: 1. Select the interface in the graphic representation in the device view. The properties of the interface are displayed in the Inspector window. 2. Select the "Port configuration" group in the area navigation of the Inspector window. The settings of the port are displayed. 3. From the "Transmission speed" drop-down list, select the speed for the data transmission. With user-programmed communication, remember the influence of the transmission speed on the changeover time. 4. From the "Parity" drop-down list, select the type of detection of bad information words. 5. Using the "Data bits" drop-down list, decide whether a character consists of eight or seven bits. 6. From the "Stop bit" drop-down list, select how many bits will identify the end of a transmitted word. WinCC Basic V13.0 System Manual, 02/2014 985 Editing devices and networks 8.1 Configuring devices and networks 7. From the "Flow control" drop-down list, select the method for ensuring a trouble-free data stream between sender and receiver. This parameter can only be set for the RS-232 interface. - Enter a HEX value in the "XON character" box that will cause the transmission of the message to be continued when it is detected. This parameter can only be set for software-controlled data flow control. - Enter a HEX value in the "XOFF character" box that will cause the transmission of the message to be suspended for the set wait time. This parameter can only be set for software-controlled data flow control. 8. In the "Wait time" box, enter a wait time in ms that must be kept to after the end of the message before the next transmission can start. Note You can configure the interface in the network view as well. To do so, you must first select the communication module in the tabular network view and then select the interface in the Inspector window. Then you can continue as described above. See also Setting data flow control (Page 986) Setting data flow control Data flow control Data flow control is a method that ensures a balanced send and receive behavior. In the ideal situation, the intelligent control does not allow data to be lost. It ensures that a device does not send more information than the receiving partner can process. There are two methods of data flow control: Hardware-controlled data flow control Software-controlled data flow control With both methods, the DSR signals of the communications partners must be active at the beginning of transmission. If the DSR signals are inactive, the transmission is not started. The RS-232 communications module can handle both methods. The RS-485 communications module does not support data flow control. Hardware-controlled data flow control Hardware-controlled data flow control uses the request to send (RTS) and clear to send (CTS) signals. With the RS-232 communications module, the RTS signal is transmitted via the output by pin 7. The CTS signal is received via pin 8. If hardware-controlled data flow control is enabled, the RTS signal is then always set to activated when data is sent. At the same time, the CTS signal is monitored to check whether 986 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks the receiving device can accept data. If the CTS signal is active, the module can transfer data until the CTS signal becomes inactive. If the CTS signal is inactive, the data transfer must be suspended for the set wait time. If the CTS signal is still inactive after the set wait time, the data transfer is aborted and an error is signaled back to the user program. Data flow control using hardware handshaking If data flow control is controlled by hardware handshaking, the sending device sets the RTS signal to active as default. A device such as a modem can then transfer data at any time. It does not wait for the CTS signal of the receiver. The sending device itself monitors it own transmission by sending only a limited number of frames (characters), for example to prevent overflow of the receive buffer. If there is nevertheless an overflow, the transferring device must hold back the message and signal an error back to the user program. Software-controlled data flow control Software-controlled data flow control uses certain characters within the messages and these control the transfer. These characters are ASCII characters selected for XON and XOFF. XOFF indicates when a transmission must be suspended. XON indicates when a transmission can be continued. If the sending device receives the XOFF character, it must suspend sending for the selected wait time. If the XON character is sent after the selected wait time, the transfer is continued. If no XON character is received after the wait time, an error is signaled back to the user program. Software data flow control requires full duplex communication because the receiving partner needs to send the XON character during the ongoing transfer. See also Configuring a communications port (Page 985) Configuration of message transfer User-programmed communication You can control the data traffic between a communications module and a device connected externally via the serial interface using your own mechanisms. If you want to do this, you will need to define a communications protocol yourself. In freely programmable communication, ASCII and binary protocols are supported for message transfer. Within the communications protocol, you will need to specify the criteria by which the start and end of a transferred message can be recognized in the data stream. User-programmed communication can only be activated in RUN mode. If there is a change to STOP mode, the user-programmed communication is stopped. WinCC Basic V13.0 System Manual, 02/2014 987 Editing devices and networks 8.1 Configuring devices and networks Specifying the communications protocol You can specify the communications protocol as follows: With the user program - The behavior when sending data is controlled by the SEND_CFG instruction. - The behavior when receiving data is controlled by the RCV_CFG instruction. Using parameter settings set graphically in the Inspector window Note If you change the communications protocol from the user program, the settings of the graphic configuration are overwritten. You should keep in mind that the settings made by the user program are not retained if there is a power down. See also User-programmed communication with RS-232 devices (Page 988) Making the settings for sending (Page 990) Specifying the start of the message (Page 990) Specifying the end of the message (Page 991) User-programmed communication with RS-232 devices RS-232/PIP multi-master cable and user-programmed communication with RS-232 devices Using the RS-232/PIP multi-master cable and user-programmed communication, you can connect a wide variety of RS-232-compliant devices to the communications modules of the S7-1200. The cable must, however, be set to the "PIP/user-programmed communication" mode. Settings on the cable The switches on the cable must be set as follows: Switch 5 must be set to 0 Switch 6 sets either the local mode (DCE) or the remote mode (DTE): - Switch set to 0 for the local mode - Switch set to 1 for the remote mode 988 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Changing over between send and receive mode The RS-232/PIP multi-master cable is in send mode when data is sent from the RS-232 interface to the RS-485 interface. The cable is in receive mode when it is idle or when data is sent from the RS-485 interface to the RS-232 interface. The cable changes from receive to send mode immediately when it detects characters on the RS-232 send line. Supported transmission speeds The RS-232/PIP multi-master cable supports transmission rates between 1200 baud and 115.2 kbaud. The RS-232/PIP multi-master cable can be set to the required transmission rate using the DIP switch on the PC/PIP cable. The following table shows the switch settings for the various transmission speeds: Transmission speed Switchover time Settings (1 = up) 115200 bps 0.15 ms 110 57600 bps 0.3 ms 111 38400 bps 0.5 ms 000 19200 bps 1.0 ms 001 9600 bps 2.0 ms 010 4800 bps 4.0 ms 011 2400 bps 7.0 ms 100 1200 bps 14.0 ms 101 The cable returns to receive mode when the RS-232 send line is idle for a certain time that is defined as the changeover time of the cable. The set transmission speed influences the changeover time as shown in the table. Influence of the changeover time When working with an RS-232/PIP multi-master cable in a system in which user-programmed communication is used, the program must take into account the changeover time for the following reasons: The communications module reacts to messages sent by the RS-232 device. Once the communications module has received a request from the RS-232 device, it must delay the reaction message for a period that is equal to or longer than the changeover time of the cable. The RS-232 device reacts to messages sent by the communications module. Once the communications module has received a reaction message from the RS-232 device, it must delay the next request message for a period that is equal to or longer than the changeover time of the cable. In both situations, the RS-232-PIP multi-master cable has enough time to change from send to receive mode so that the data can be sent from the RS-485 interface to the RS-232 interface. WinCC Basic V13.0 System Manual, 02/2014 989 Editing devices and networks 8.1 Configuring devices and networks See also Configuration of message transfer (Page 987) Making the settings for sending (Page 990) Specifying the start of the message (Page 990) Specifying the end of the message (Page 991) Making the settings for sending Sending messages You can program pauses between individual messages. The following table shows which pauses can be set: Parameter Definition RTS ON delay You can set the time that must elapse after the send request RTS (request to send) before the actual data transfer starts. RTS OFF delay You can set the time that must elapse after the complete transfer before RTS signal is deactivated. Send pause at the start of the message You can specify that a pause is sent at the start of every message transfer when the RTS ON delay has elapsed. The pause is specified in bit times. Send Idle Line after a pause You can make a setting so that following a selected pause at the start of the message, the "Idle Line" signal is output to signal that the line is not in use. To enable the parameter, "Send pause at message start" must be set. The duration of the "Idle Line" signal is specified in bit times. See also Specifying the start of the message (Page 990) Specifying the end of the message (Page 991) User-programmed communication with RS-232 devices (Page 988) Specifying the start of the message Recognizing the start of the message To signal to the receiver when the transfer of a message is completed and when the next message transfer starts, criteria must be specified in the transmission protocol to identify the end and start of a message. If a criterion is met that indicates the start of a message, the receiver starts searching the data stream for criteria that mean the end of the message. There are two different methods for identifying the start of a message: 990 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Starting with any character: Any character can defined the start of a message. This is the default method. Starting with a specific condition: The start of a message is identified based on selected conditions. Conditions for detecting the start of a message The following table shows the various options for defining the start of a message: Parameter Definition Recognize start of message by line break The receiver recognizes a line break when the received data stream is interrupted for longer than one character. If this is the case, the start of the message is identified by the line break. Recognize start of message by idle line The start of a message is recognized when the send transmission line is in the idle state for a certain time (specified in bit times) followed by an event such as reception of a character. Recognize start of message with individual characters The start of a message is recognized when a certain character occurs. You can enter the character as a HEX value. Recognize start of message by a character string The start of a message is detected when one of the specified character sequences arrives in the data stream. You can specify up to four character sequences each with up to five characters. The individual conditions can be logically linked in any way. See also Making the settings for sending (Page 990) User-programmed communication with RS-232 devices (Page 988) Specifying the end of the message Recognizing the end of the message To signal to the receiver when the transfer of a message is completed and when the next message transfer starts, criteria must be specified in the transmission protocol to identify the end and start of a message. In total, there are six different methods of recognizing the end of a message and these can all be logically linked in any way. The following table shows the various possible setting options: WinCC Basic V13.0 System Manual, 02/2014 Parameter Definition Recognize end of message by message timeout The end of a message is recognized automatically when a selected maximum duration for a message is exceeded. Values from 0 to 65535 ms can be set. Recognize end of message by reply timeout The end of a message is recognized when there is no reply within a set time after transferring data. Values from 0 to 65535 ms can be set. 991 Editing devices and networks 8.1 Configuring devices and networks Parameter Definition Recognize end of message by timeout between characters The end of a message is detected when the time between two characters specified in bit times is exceeded. Values from 0 to 2500 bit times can be set. The S7-1200 CPU only accepts a maximum time of eight seconds even if the value that is set results in a duration of more than eight seconds. Recognize end of message by maximum length The end of a message is recognized when the maximum length of a message is exceeded. Values from 1 to 1023 characters can be set. Read message length from message The message itself contains information about the length of the message. The end of a message is reached when the value taken from the message is reached. Which characters are used for the evaluation of the message length is specified with the following parameters: Offset of the length field in the message The value decides the position of the character in the message that will be used to indicate the message length. Values from 1 to 1022 characters can be set. Size of the length field This value specifies how many characters starting at the first evaluation position will be used to indicate the message length. Values of 0, 1, 2 and 4 characters can be set. The data following the length field (does not belong to the message length) The value specifies the number of bytes after the length field that must be ignored in the evaluation of the message length. Values from 0 to 255 characters can be set. Recognize message end with a character sequence The end of a message is detected when the specified character sequence arrives in the data stream. You can define up to five characters in the character string that are to be checked. If the specified characters appear at the correct location in the message, the message end is recognized. To recognize the message end when character 1 and character 3 have a certain value, for example, you have to activate the check box for character 1 and character 3 and enter a character value. See also Making the settings for sending (Page 990) User-programmed communication with RS-232 devices (Page 988) Enabling system memory System memory A system memory is a bit memory with defined values. You decide which memory byte of the CPU will become the system memory byte when assigning the system memory parameters. 992 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Benefits You can use system memory in the user program, for example to run program segments in only the first program cycle after start-up. Two system memory bits are constant 1 or constant 0. Bits of the system memory bytes The following table shows the meaning of the system memory: Bit of the system memory bytes 7 6 5 4 3 2 1 0 Meaning Reserved (=0) Reserved (=0) Reserved (=0) Reserved (=0) =0 =1 =1 with change to the diagnosis status =1 in first program cycle after startup, otherwise 0 Note The selected memory byte cannot be used for intermediate storage of data. Using clock memory Clock memory A clock memory is a bit memory that changes its binary status periodically in the pulse-nopulse ratio of 1:1. You decide which memory byte of the CPU will become the clock memory byte when assigning the clock memory parameters. Benefits You can use clock memory, for example, to activate flashing indicator lamps or to initiate periodically recurring operations such as recording of actual values. Available frequencies Each bit of the clock bit memory byte is assigned a frequency. The following table shows the assignment: Bit of the clock memory byte 7 6 5 4 3 2 1 0 Period (s) 2.0 1.6 1.0 0.8 0.5 0.4 0.2 0.1 Frequency (Hz) 0.5 0.625 1 1.25 2 2.5 5 10 WinCC Basic V13.0 System Manual, 02/2014 993 Editing devices and networks 8.1 Configuring devices and networks Note Clock memory runs asynchronously to the CPU cycle, i.e. the status of the clock memory can change several times during a long cycle. The selected memory byte cannot be used for intermediate storage of data. Protection Setting options for the protection level (FW V1 to V3) Protection level The following section describes how to use the various protection levels of the S7-1200 CPUs V1 to V3. Effects of the protection level setting You can choose between the following protection levels: No protection: This corresponds to the default behavior. You cannot enter a password. Read and write access is always permitted. Write protection: Only read-only access is possible. You cannot change any data on the CPU and cannot load any blocks or a configuration. HMI access and communication between CPUs are excluded from the write protection. Assignment of a password is required to select this protection level. Write/read protection: No write or read access is possible in the "Accessible devices" area or in the project for devices that are switched online. Only the CPU type and the identification data can be displayed in the project tree under "Accessible devices". Display of online information or blocks under "Accessible devices", or in the project for devices interconnected online, is possible. HMI access and communication between CPUs are excluded from the write protection. Assignment of a password is required to select this protection level. Behavior of a password-protected CPU during operation The CPU protection takes effect after the settings are downloaded to the CPU. Validity is checked before the online function is executed. If password protection is in place, you are prompted to enter a password. Example: The module was assigned write protection and you want to execute the "Modify tags" function. This requires write access; therefore, the assigned password must be entered to execute the function. The functions protected by a password can only be executed by one programming device/PC at any one time. Another programming device/PC cannot log on with a password. 994 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Access authorization to the protected data is in effect for the duration of the online connection or until the access authorization is manually rescinded with "Online > Delete access rights". Access authorization will also expire when the project is closed. Note You can not restrict functions for process control, monitoring, and communications. Some functions are still protected due to their use as online data. RUN/STOP in the "Online Tools" task card or "Set the time" in the diagnostics and online editor is therefore writeprotected. Setting options for the protection (FW as of V4) Protection level The following section describes how to use the various access levels of the S7-1200 CPUs as of V4. S7-1200 CPUs provide various access levels to limit the access to specific functions. The parameters for the access levels are assigned in a table. The green checkmarks in the columns to the right of the respective access level specify which operations are possible without knowing the password of this access level. If you want to use the functions of check boxes that are not selected, a password has to be entered. NOTICE Configuring an access level does not replace know-how protection Configuring access levels prevents unauthorized changes to the CPU by restricting download privileges. However, blocks on the memory card are not write- or read-protected. Use knowhow protection to protect the code of blocks on the memory card. Default characteristics The default access level is "Full access (no protection)". Every user can read and change the hardware configuration and the blocks. A password is not set and is also not required for online access. WinCC Basic V13.0 System Manual, 02/2014 995 Editing devices and networks 8.1 Configuring devices and networks The access levels in detail With an S7-1200 CPU, you can configure the following access levels: Full access (no protection): The hardware configuration and the blocks can be read and changed by all users. Read access: With this access level, only read access to the hardware configuration and the blocks is possible without entering a password - meaning that you can load the hardware configuration and blocks into the programming device. In addition, HMI access and access to diagnostics data is possible. You cannot load blocks or a hardware configuration into the CPU without entering the password. Moreover, writing test functions and firmware updates are not possible without a password. HMI access: With this access level, only HMI access and access to diagnostics data is possible without entering the password. Without entering the password, you can neither load blocks and hardware configuration into the CPU, nor load blocks and hardware configuration from the CPU into the programming device. In addition, the following is not possible without a password: Writing test functions, changing the operating state (RUN/STOP) and firmware updates. No access (complete protection): When the CPU is completely protected, no read or write access to the hardware configuration and the blocks is possible. HMI access is also not possible. The server function for PUT/GET communication is disabled in this access level (cannot be changed). Authorization with the password again provides you full access to the CPU. Behavior of a password-protected module during operation The CPU protection takes effect after the settings are downloaded to the CPU. Validity is checked before the online function is executed. If password protection is in place, you are prompted to enter a password. Example: The module was configured with read access and you want to execute the "Modify tags" function. This requires write access; therefore, the assigned password must be entered to execute the function. The functions protected by a password can only be executed by one programming device/PC at any one time. Another programming device/PC cannot log on. Access authorization to the protected data is in effect for the duration of the online connection or until the access authorization is manually rescinded with "Online > Delete access rights". Each access level allows unrestricted access to certain functions without entering a password, for example, identification using the "Accessible devices" function. Configuring access levels The following section describes how to configure an access level and enter passwords for an S7-1200 CPU as of V4. For an S7-1200 CPU, you can enter multiple passwords and thereby set up different access rights for individual user groups. 996 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks The passwords are entered in a table in such a way that exactly one access level is assigned to each password. The effect of the password is visualized in the "Access" column and explained in the text below the table. Example You select the "No access (complete protection)" access level for a standard CPU (in other words, not an F-CPU) and enter a separate password for each of the access levels that lie above it in the table. For users who do not know any of the passwords, the CPU is completely protected. Not even HMI access is possible. For users who know one of the set passwords, the effect depends on the table row in which the password occurs: The password in row 1 (Full access (no protection)) allows access as if the CPU were completely unprotected. Users who know this password have unrestricted access to the CPU. The password in row 2 (read access) allows access as if the CPU were write-protected. Users who know this password have read-only access to the CPU. The password in row 3 (HMI access) allows access as if the CPU were write-protected and read-protected so that only HMI access is possible for users who know this password. Procedure To configure the access levels of an S7-1200 CPU, follow these steps: 1. Open the properties of the module in the inspector window. 2. Open the "Protection" entry in the area navigation. A table with the possible access levels appears in the inspector window. Figure 8-4 Access protection 3. Activate the required access level in the first column of the table. The green checkmarks in the columns to the right of the respective protection level show you which operations are still available without entering the password. WinCC Basic V13.0 System Manual, 02/2014 997 Editing devices and networks 8.1 Configuring devices and networks 4. In the "Password" column, specify a password for full access in the first row. In the "Confirmation" column, enter the selected password again to protect against incorrect entries. Ensure that the password is sufficiently secure, in other words, that is does not follow a machine-recognizable pattern! You must enter a password in the first row "Full access (no protection)". This enables unrestricted access to the CPU for those who know the password, regardless of the selected protection level. 5. Assign additional passwords as needed to other access levels if the selected protection level allows you to do so. 6. Download the hardware configuration so that the access level takes effect. Result The hardware configuration and the blocks are protected against unauthorized access according to the set access level. If an operation cannot be executed without a password due to the set access level, a dialog for entering a password is displayed. Restriction of communication services Introduction The CPU can be the server for a number of communication services. This means that other communication participants can access CPU data even if you have not configured and programmed connections for the CPU. The local CPU as a server thus does not have the possibility to control communication to the clients. The parameter "Connection mechanisms" in the "Protection" area of the CPU parameters is used to specify whether this type of communication is permitted or not for the local CPU during operation. Permit access with PUT/GET communication from remote partners By default, the "Permit access with PUT/GET communication from remote partners (...)" option is disabled. In this case, read and write access to CPU data is only possible for communication connections that require configuration or programming both for the local CPU and for the communication partner. Access through BSEND/BRCV instructions is possible, for example. Connections for which the local CPU is only a server (meaning that no configuration/ programming of the communication with the communication partner exists at the local CPU), are therefore not possible during operation of the CPU, for example, For PUT/GET, FETCH/WRITE or FTP access via communication modules For PUT/GET access from other S7 CPUs For HMI access that is realized via PUT/GET communication 998 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks If you want to allow access to CPU data from the client side, meaning that you do not want to restrict the communication services of the CPU, activate the "Permit access with PUT/GET communication from remote partners" option. Organization blocks Organization blocks for startup Description You can determine the boundary conditions for the startup characteristics of your CPU, for example, the initialization values for "RUN". To do this, write a startup program. The startup program consists of one or more startup OBs (OB numbers 100 or >= 123). The startup program is executed once during the transition from "STOP" mode to "RUN" mode. Current values from the process image of the inputs are not available for startup program, nor can these values be set. After the complete execution of the startup OBs, the process image of the inputs is read in and the cyclic program is started. There is no time limit for executing the startup routine. Therefore the scan cycle monitoring time is not active. Time-driven or interrupt-driven organization blocks cannot be used. Start information A startup OB has the following start information: Tag Data type Description LostRetentive BOOL = 1, if retentive data storage areas have been lost LostRTC BOOL = 1, if realtime clock has been lost See also Events and OBs (Page 963) Organization blocks for cyclic program execution Introduction For the program execution to start, at least one program cycle OB must be present in the project. The operating system calls this program cycle OB once in each cycle and thereby starts the execution of the user program. You can use multiple OBs (OB numbers >= 123). When multiple program cycle OBs are used, these are called in one after the other in the order of their OB numbers. The program cycle OB with the lowest OB number is called first. The program cycle OBs have the priority class 1. This corresponds to the lowest priority of all OBs. The cyclic program can be interrupted by events of any other event class. WinCC Basic V13.0 System Manual, 02/2014 999 Editing devices and networks 8.1 Configuring devices and networks Programming cyclic program execution You program cyclic program execution by writing your user program in the cycle OBs and the blocks that they call. The first cyclic program execution begins as soon as the startup program has ended without errors. The cycle restarts after the end of each cyclic program execution. Sequence of cyclic program execution One cycle of the program execution encompasses the following steps: 1. The operating system starts the maximum cycle time. 2. The operating system writes the values from the process image output to the output modules. 3. The operating system reads out the state of the inputs of the input modules and updates the process image input. 4. The operating system processes the user program and executes the operations contained in the program. 5. At the end of a cycle, the operating system executes any tasks that are pending, for example, loading and deleting blocks or calling other cycle OBs. 6. Finally, the CPU returns to the start of the cycle and restarts the scan cycle monitoring time. See also: Auto-Hotspot Options for interrupting Cyclic program execution can be interrupted by the following events: Interrupt A STOP command, triggered by - Operation of the programming device - "STP" instruction Supply voltage failure Occurrence of a device fault or program error Start information None Optimized start information: Name Data type Meaning first_scan BOOL = TRUE in the first call of this OB: Transition from STOP or HOLD to RUN After reloading retentivity 1000 BOOL = TRUE, if retentive data are available WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks See also Events and OBs (Page 963) Organization blocks for interrupt-driven program execution Organization blocks for time-of-day interrupt Function Organization blocks for time-of-day interrupt (OB number >=123) can be processed as follows: One time to a preset time (date with time of day) Periodically with preset start time and the following intervals: - Every minute - Hourly - Daily - Weekly - Monthly - Yearly - End of month Time-of-day interrupt-OBs are therefore used to run parts of the user program on a timecontrolled basis. Status for time-of-day interrupt The following table contains the possible status of a time-of-day interrupt as well as it's meaning. Status Meaning Cancelled The one-time processing has already taken place, or the start event of an not yet processed time-of-day interrupt has been deleted with the extended instruction CAN_TINT. Set You have scheduled the time or start time for processing. Activated You have scheduled whether processing takes place one time or periodically, and in the case of periodic processing, you have scheduled the interval. Rules for time-of-day interrupts The following rules apply to the use of time-of-day interrupts: A time-of-day interrupt can only be processed if it is set and activated, and a corresponding organization block exists in the user program. The start times of periodic time-of-day interrupts must correspond to a real date. For example, it is not possible to repeat an organization block monthly which first occurs on January 31st. In this case, on OB will only be started in the months that have 31 days. WinCC Basic V13.0 System Manual, 02/2014 1001 Editing devices and networks 8.1 Configuring devices and networks A time-of-day interrupt activated during startup by extended instruction call ACT_TINTwill not be executed until the startup is complete. After each CPU startup, you must reactivate previously set time-of-day interrupts Setting and activating a time-of-day interrupt OB Before a time-of-day interrupt can be deleted and the corresponding time-of-day interrupt OB can be processed from the operating system, you must set and activate the interrupt. You have the following options: Set time-of-day interrupt Activate time-of-day interrupt Means of configuring Means of configuring Means of configuring By extended instruction call ACT_TINT By extended instruction call SET_TINTL By extended instruction call ACT_TINT Note If you configure a time-of-day interrupt in such a way that the corresponding OB is to be processed once, the start time must not be in the past (relative to the real-time clock of the CPU). If you configure a time-of-day interrupt in such a way that the corresponding OB is to be processed periodically, but the start time is in the past, then the time-of-day interrupt will be processed the next time it is due. Time-of-day interrupt status query In order to query the status of the time-of-day interrupt, call the extended instruction QRY_TINT. Cancelling a time-of-day interrupt You can cancel a time-of-day interrupt which has not yet been processed with the extended instruction CAN_TINT. You can reset cancelled time-of-day interrupts with the extended instruction SET_TINTL and activate them with the extended instruction ACT_TINT. Conditions that effect the time-of-day interrupt OBs Since a time-of-day interrupt occurs only at specific intervals, certain conditions can affect the function of the associated OBs during execution of your program. The following table shows 1002 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks some of these conditions and describes how these affect the processing of a time-of-day interrupt OB. Condition Result The extended instruction CAN_TINT is called in the user program. The operating system deletes the start event (date and time) of the time-of-day interrupt. You must reset and reactivate the time-of-day interrupt if you are going to call the corresponding time-of-day interrupt OB again. By synchronizing or correcting the CPU system clock, the time of day will be set ahead. With this, the start time for a time-of-day interrupt OB will be bypassed. The operating system calls the time error interrupt OB (OB 80) and records the start event, the number, and the priority of the first bypassed time-of-day interrupt OB in its start information. After completion of the OB 80, the operating system processes the bypassed time-of-day interrupt OB only once. By synchronizing or correcting the CPU system clock, the time of day will be set back. The corrected clock time is before the start time of an already processed time-of-day interrupt OB. The time-of-day interrupt OB is repeated. A time-of-day interrupt OB is still being processed when the start event for its next execution occurs. The operating system then calls time error interrupt OB 80. The requested OB is processed only after the processing and further execution of the current time-of-day interrupt OB has completed. Start information A time-of-day interrupt OB has the following start information: Tag Data type Description CaughtUp BOOL =1, if the OB call is executed because clock time is turned ahead. SecondTime BOOL =1 if the OB is called a second time because clock time is turned back (more exactly, if the planned time of the current OB processing is earlier than or the same time as the planned time for the previous OB processing). Note: SecondTime is only set once. Organization block for status interrupts Description When it receives a status interrupt, the operating system of the S7-1200 CPU calls the status interrupt OB from a DP master or IO controller. This may be the case if a module of a slave changes its operating mode, for example, from "RUN" to "STOP". For more detailed information on events that trigger a status interrupt, refer to the documentation of the slave or device manufacturer. WinCC Basic V13.0 System Manual, 02/2014 1003 Editing devices and networks 8.1 Configuring devices and networks Structure of the start information The status-interrupt OB has the following start information: Name Data type Meaning LADDR HW_IO Hardware address of the component triggering the interrupt Slot UINT Slot number of the component triggering the interrupt Specifier WORD Interrupt specifier from the interrupt frame See also Events and OBs (Page 963) Organization block for update interrupts Description When it receives a status interrupt, the operating system of the S7-1200 CPU calls the update interrupt OB from a DP master or IO controller. This may be the case if you changed a parameter on a slot of a slave or device. For more detailed information on events that trigger an update interrupt, refer to the documentation of the slave or device manufacturer. Structure of the start information The update interrupt OB has the following start information: Name Data type Meaning LADDR HW_IO Hardware address of the component triggering the interrupt Slot UINT Slot number of the component triggering the interrupt Specifier WORD Interrupt specifier from the interrupt frame See also Events and OBs (Page 963) Organization block for manufacturer-specific or profile-specific interrupts Description When it receives a manufacturer-specific or profile-specific interrupt from a DP master or IO controller, the operating system of the S7-1200 CPU calls OB 57. For more detailed information on events that trigger this type of interrupt, refer to the documentation of the slave or device manufacturer. 1004 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Structure of the start information The OB for manufacturer-specific and profile-specific interrupts has the following start information: Name Data type Meaning LADDR HW_IO Hardware address of the component triggering the interrupt Slot UINT Slot number of the component triggering the interrupt Specifier WORD Interrupt specifier from the interrupt frame See also Events and OBs (Page 963) Organization blocks for time-delay interrupts Description A time-delay interrupt OB is started after a configurable time delay of the operating system. The delay time starts after the SRT_DINT instruction is called. You can use up to four time-delay interrupt OBs or cyclic OBs (OB numbers >= 123) in your program. If, for example, you are already using two cyclic interrupt OBs, you can insert a maximum of two further time-delay interrupt OBs in your program. You can use the CAN_DINT instruction to prevent the execution of a time-delay interrupt that has not yet started. Function of time-delay interrupt OBs The operating system starts the corresponding OB after the delay time, which you have transferred with an OB number and an identifier to the SRT_DINT instruction. To use a time-delay interrupt OB, you must execute the following tasks: You must call the instruction SRT_DINT. You must download the time-delay interrupt OB to the CPU as part of your program. The delay time is measured with a precision of 1 ms. A delay time can immediately start again after it expires. Time delay interrupt OBs are executed only when the CPU is in the "RUN" mode. A warm restart clears all start events of time-delay interrupt OBs. The operating system calls the time-delay interrupt OB if one of the following events occurs: If the operating system attempts to start an OB that is not loaded and you specified its number when calling the SRT_DINT instruction. If the next start event for a time-delay interrupt occurs before the time delay OB has completely executed. WinCC Basic V13.0 System Manual, 02/2014 1005 Editing devices and networks 8.1 Configuring devices and networks You can disable and re-enable time-delay interrupts using the DIS_AIRT and EN_AIRT instructions. Note If you disable an interrupt with DIS_AIRT after executing SRT_DINT, this interrupt executes only after it has been enabled with EN_AIRT. The delay time is extended accordingly. Start information None Optimized start information: Name Data type Meaning sign WORD User ID: Input parameter SIGN from the call of the "SRT_DINT" instruction See also Events and OBs (Page 963) Organization blocks for cyclic interrupts Description Cyclic interrupt OBs serve to start program in periodic time intervals independently of the cyclic program execution. The start times of a cyclic interrupt OB are specified using the time base and the phase offset. The time base defines the intervals at which the cyclic interrupt OB is started and is an integer multiple of the basic clock cycle of 1 ms. The phase offset is the time by which the start time is offset compared with the basic clock cycle. If several cyclic interrupt OBs are being used, you can use this offset to prevent a simultaneous start time if the time bases of the cyclic interrupt OBs have common multiples. You can specify a time period between 1 ms and 60000 ms as the time base. You can use up to four cyclic interrupt OBs or time-delay OBs (OB numbers >= 123) in your program. If, for example, you are already using two time-delay interrupt OBs, you can insert a maximum of two further cyclic interrupt OBs in your program. Note The execution time of each cyclic interrupt OB must be noticeably smaller than its time base. If a cyclic interrupt OB has not been completely executed but execution is again pending because the cycle clock has expired, the time error OB is started. The cyclic interrupt that caused the error is executed later or discarded. 1006 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Example of the use of phase offset You have inserted two cyclic interrupt OBs in your program: Cyclic interrupt OB1 Cyclic interrupt OB2 For cyclic interrupt OB1, you have set a time base of 20 ms and for cyclic interrupt OB2 a time base of 100 ms. After expiration of the time base of 100 ms, the cyclic interrupt OB1 reaches the start time for the fifth time, cyclic interrupt OB2 for the first time. To nevertheless execute the cyclic interrupt OBs offset, enter a phase offset for one of the two cyclic interrupt OBs. Start information None Optimized start information: Name Data type Meaning first_scan BOOL = TRUE in the first call of this OB At the transition from STOP or HOLD to RUN After reloading event_count INT Number of lost start events since the last start of this OB See also Assigning parameters to cyclic interrupt OBs (Page 1015) Events and OBs (Page 963) Organization blocks for hardware interrupts Description You can use hardware interrupt OBs to react to specific events. You can assign an event that triggers an alarm to precisely one hardware interrupt OB. A hardware interrupt OB in contrast can be assigned to several events. Hardware interrupts can be triggered by high-speed counters and input channels. For each high-speed counter and input channel that should trigger a hardware interrupt, the following properties need to be configured: The process event that should trigger the hardware interrupt (for example, the change of a count direction of a high-speed counter) The number of the hardware interrupt OB which is assigned to this process event You can use up to 50 hardware interrupt OBs (OB numbers >= 123) that are independent of each other in your program. WinCC Basic V13.0 System Manual, 02/2014 1007 Editing devices and networks 8.1 Configuring devices and networks Functionality of a hardware interrupt OB After triggering a hardware interrupt, the operating system identifies the channel of the input or the high-speed counter and determines the assigned hardware interrupt OB. If no other interrupt OB is active, the determined hardware interrupt OB is called. If a different interrupt OB is already being executed, the hardware interrupt is placed in the queue of its priority class. The hardware interrupt is acknowledged after the completion of the assigned hardware interrupt OB. If another event that triggers a hardware interrupt occurs on the same module during the time between identification and acknowledgement of a hardware interrupt, the following applies: If the event occurs on the channel that previously triggered the hardware interrupt, then no additional hardware interrupt is triggered. Another hardware interrupt can only be triggered if the current hardware interrupt is acknowledged. If the event occurs on a different channel, a hardware interrupt is triggered. Hardware interrupt OBs are called only in the CPU's "RUN" mode. Start information None Optimized start information: Name Data type Meaning Laddr HW_IO Hardware identifier of the module that triggers the hardware interrupt USI WORD Identifier for future extensions (not user-relevant) IChannel USINT Number of the channel that triggered the hardware interrupt EventType BYTE Identifier for the event type associated with the event triggering the interrupt (e.g., positive edge) This identifier can be found in the description of the respective module. See also Assigning parameters to hardware interrupt OBs (Page 1016) Events and OBs (Page 963) Organization block for time error Description The operating system calls the time error OB (OB 80) if one of the following events occurs: The cyclic program exceeds the maximum cycle time. The OB called is currently still being executed (possible for time-delay interrupt OBs and cyclic interrupt OBs). A time-of-day interrupt was missed because the clock time was set forward by more than 20 seconds. 1008 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks A time-of-day interrupt was missed during a STOP. An overflow has occurred in an interrupt OB queue. An interrupt was lost due to the excessive interrupt load. If you have programmed no time error OB, the S7-1200 CPU reacts as follows: CPUs with firmware version V1.0: The CPU remains in RUN mode. CPUs with firmware version V2.0: - The CPUs goes to STOP mode when the maximum cycle time is exceeded. - With all other start events of the time error OB, the CPU remains in RUN mode. With CPUs with firmware version V1.0, the two-time overshooting of the maximum cycle time does not lead to the calling of an OB, but to the STOP of the CPU. You can avoid the second violation by restarting the cycle monitoring of the CPU with the RE_TRIGR instruction. You can use only one time error OB in your program. Start information The time error OB has the following start information: Tag Data type Description fault_id BYTE 0x01: Maximum cycle time exceeded 0x02: Called OB is still being executed 0x05: Expired time-of-day interrupt due to time jump 0x06: Expired time-of-day interrupt on return to RUN mode 0x07: Queue overflow 0x09: Interrupt loss due to high interrupt load csg_OBnr OB_ANY Number of the OB being executed at the time of the error csg_prio UINT Priority of the OB being executed at the time of the error See also Events and OBs (Page 963) Organization block for diagnostic interrupts Description You can enable the diagnostic error interrupt for diagnostics-capable modules so that the module detects changes in the I/O status. As a result, the module triggers a diagnostic error interrupt in the following cases: A fault is present (incoming event) A fault is no longer present (outgoing event) WinCC Basic V13.0 System Manual, 02/2014 1009 Editing devices and networks 8.1 Configuring devices and networks If no other interrupt OB is active, then the diagnostic interrupt OB (OB 82) is called. If another interrupt OB is already being executed, the diagnostic error interrupt is placed in the queue of its priority group. You can use only one diagnostic interrupt OB in your program. Start information The diagnostic interrupt OB has the following start information: Tag Data type Description IO_state WORD Contains the I/O status of the diagnosticscapable module. laddr HW_ANY HW-ID Channel UINT Channel number multi_error BOOL = 1, if there is more than one error IO_state tag The following table shows the possible I/O states that the IO_state tag can contain: IO_state Description Bit 0 Configuration correct: = 1, if the configuration is correct = 0, if the configuration is no longer correct Bit 4 Error: = 1, if an error is present, e.g., a wire break = 0, if the error is no longer present Bit 5 Configuration not correct: = 1, if the configuration is not correct = 0, if the configuration is correct again Bit 6 I/O cannot be accessed: = 1, if an I/O access error has occurred In this case, laddr contains the hardware identifier of the I/O with the access error. = 0, if the I/O can be accessed again See also Events and OBs (Page 963) 1010 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Organization block for pulling and plugging Description The S7-1200 CPU operating system calls the pull/plug interrupt OB (OB 83) if a configured and non-disabled distributed I/O module or submodule (PROFIBUS, PROFINET, AS-i) is removed or inserted. Note The removal or insertion of a central module leads to the STOP of the CPU. Start information The pull/plug interrupt OB has the following start information: Name Data type Meaning LADDR HW_IO Hardware identifier of the affected module or submodule Event_Class BYTE B#16#38: (Sub)module plugged B#16#39: (Sub)module pulled or not responding Fault_ID BYTE Error code (possible values: B#16#51, B#16#54, B#16#55, B#16#56, B#16#57, B#16#58) The following table shows which event caused the start of the pull/plug interrupt OB. ev_class (B#16# ...) fault_id (B#16# ...) Meaning 39 51 Module pulled 39 54 Submodule pulled 38 54 Submodule plugged, which conforms to the parameterized submodule 38 55 Submodule inserted, which does not conform to the submodule parameter assignment 38 56 Submodule inserted, but error in module parameter assignment 38 57 Submodule or module inserted, but with a fault or maintenance 38 58 Submodule access error remedied See also Events and OBs (Page 963) WinCC Basic V13.0 System Manual, 02/2014 1011 Editing devices and networks 8.1 Configuring devices and networks Organization block for rack fault Description The S7-1200 CPU operating system calls the OB 86 in the following cases: The failure of a DP master system or of a PROFINET IO system is detected (in the case of either an incoming or an outgoing event). The failure of a DP slave or of an IO device is detected (in the case of either an incoming or an outgoing event). Failure of some of the submodules of a PROFINET I-device is detected. Structure of the start information The rack fault OB has the following start information: Name Data type Meaning LADDR HW_IO Hardware identifier of the defective hardware object Event_Class BYTE B#16#32: Activation of a DP slaves or an IO device B#16#33: Deactivation of a DP slaves or an IO device B#16#38: outgoing event B#16#39: incoming event Fault_ID BYTE Error code (possible values: B#16#C3, B#16#C4, B#16#C5, B#16#C6, B#16#C7, B#16#C8, B#16#C9, B#16#CA, B#16#CB, B#16#CC, B#16#CD, B#16#CE, B#16#CF, B#16#F8, B#16#F9) The following table shows which event caused the start of OB 86. 1012 Ev_class Fault_id Meaning B#16# ... B#16# ... 39 C3 Failure of a DP master system 39/38 C4 Failure/return of a DP slave 38 C5 Return of a DP slave; however, slave is faulty 38 C6 Expansion unit return, but error in module parameter assignment 38 C7 Return of a DP device, but there is error in module configuration 38 C8 Return of a DP device, but discrepancy between preset/actual configuration 32/33 C9 Activation/deactivation of a DP slave with the "D_ACT_DP" instruction 39 CA Failure of a PROFINET IO system 39/38 CB Failure/return of a PROFINET IO device 38 CC Return of a PROFINET IO device with fault or maintenance 38 CD Return of a PROFINET IO device, deviation between preset/actual configuration 38 CE Return of a PROFINET IO device, error in module configuration 32/33 CF Activation/deactivation of an IO device with the "D_ACT_DP" instruction WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Ev_class Fault_id B#16# ... B#16# ... Meaning 39/38 F8 Failure/return of some of the submodules of a PROFINET I-device 38 F9 Return of some of the submodules of a PROFINET I-device with a device configuration difference See also Events and OBs (Page 963) Block parameters of organization blocks Basics of block parameters Introduction Several organization blocks (OBs) have properties with which you can control their behavior or their assignment to specific events. You can influence these properties by assigning parameters. Overview You can assign parameters to the properties for the following organization blocks: Time-of-day interrupt OBs Cyclic interrupt OBs Hardware interrupt OBs See also Assigning parameters to hardware interrupt OBs (Page 1016) Assigning parameters to cyclic interrupt OBs (Page 1015) Parameter assignment for time-of-day interrupt OBs Procedure for setting the parameters To set the parameters of a time-of-day interrupt OB, proceed as follows: 1. Open the "Properties" dialog belonging to the time-of-day interrupt OB in question. 2. Click the "Time-of-day interrupt" group in the area navigation. WinCC Basic V13.0 System Manual, 02/2014 1013 Editing devices and networks 8.1 Configuring devices and networks Overview of the parameters that can be set You can set the following parameters: Execution Start date and time-of-day Option buttons "Local time" and "System time" "Execution" parameter Use the drop-down list "Execution" to define the periods at which the time-of-day interrupt OB is to be executed. The time intervals relate to the settings for "Start date" and "Time-of-day". The following values are possible for "Execution": Never Once Every minute Hourly Daily Weekly Monthly Yearly End of month Note With the value "End of month", the value specified under "Start date" is irrelevant. "Start date" and "Time-of-day" parameter Here, you specify the time at which the time-of-day interrupt is to be executed for the first time. Example: Start date = 07/05/2013, time =11:16 Depending on the value of the "Execution" parameter, the CPU generates additional time-ofday interrupts periodically. Depending on the setting, the start time relates either to the local time or to the coordinated universal timeUTC. Note If you set the "Execution" parameter to "Monthly", the start date cannot be set to the 29th, the 30th, or the 31st. If you want the time-of-day interrupt OB to start at the end of the month, you should set the parameter "Execution" to "End of month". 1014 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks "Local time" or "System time" Here, you decide which time the start time of the time-of-day interrupt OB relates to: "Local time": The start time relates to the time zone set for the CPU. "System time": The start time relates to the coordinated universal time UTC (Universal Time Coordinated). Assigning parameters to cyclic interrupt OBs Introduction You can use cyclic interrupt OBs to start programs at regular time intervals. To do so you must enter a scan time and a phase shift for each cyclic interrupt OB used. You can use up to four cyclic interrupt OBs or time-delay OBs (OB numbers >= 200) in your program. If, for example, you are already using two time-delay interrupt OBs, you can insert a maximum of two further cyclic interrupt OBs in your program. Note If you assign multiple cyclic OBs, make sure that you assign a different cycle time or phase offset to each cyclic interrupt OB to avoid them executing at the same time or having to queue. When you create a cyclic interrupt OB, the cycle time 100 and the phase offset 0 are entered as start value. Procedure To enter a scan time and a phase shift for a cyclic interrupt OB, proceed as follows: 1. Open the "Program blocks" folder in the project tree. 2. Right-click on an existing cyclic interrupt OB. 3. Select the "Properties" command in the shortcut menu. The "<Name of the cyclic interrupt OB>" dialog box opens. 4. Click the "Cyclic interrupt" group in the area navigation. The text boxes for the scan time and the phase shift are displayed. 5. Enter the scan time and the phase shift. 6. Confirm your entries with "OK". See also Basics of block parameters (Page 1013) Organization blocks for cyclic interrupts (Page 1006) WinCC Basic V13.0 System Manual, 02/2014 1015 Editing devices and networks 8.1 Configuring devices and networks Assigning parameters to hardware interrupt OBs Introduction You must select the corresponding event and assign the following parameters for every input channel and high-speed counter that should trigger a hardware interrupt: Event name Number of the hardware interrupt OB that is assigned to this process event The parameters of the hardware interrupt are assigned in the properties of the corresponding device. You can assign parameters for up to 50 hardware interrupt OBs. You can create the hardware interrupt OB to be assigned parameters either before or during activation of an event. Procedure To configure a hardware interrupt event, follow these steps: 1. Double-click the "Devices & Networks" command in the project tree. The hardware and network editor opens in the network view. 2. Change to the device view. 3. If the Inspector window closed in the device view, select the "Inspector window" check box in the "View" menu. The Inspector window opens. 4. Click the "Properties" tab. 5. In the device view, select the module for which you want to a assign a hardware interrupt. 6. Select the corresponding event that will trigger a hardware interrupt, e.g., a positive edge. 7. Enter an event name. 8. Select an existing hardware interrupt OB from the "Hardware interrupt" drop-down list or create a new hardware interrupt OB. If you have not previously created any hardware interrupt OBs, you can click the "Add new block" button in the drop-down list. The start information of the corresponding hardware interrupt OB, including all specifications for the interrupt-triggering event, is updated. 9. If you want to assign further hardware interrupts, repeat steps 5 to 8. 1016 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks A system constant of data type Event_HwInt is created automatically for the event identified by the explicit event name. The system constants are displayed in the standard tag table. See also Basics of block parameters (Page 1013) Organization blocks for hardware interrupts (Page 1007) Events and OBs (Page 963) Symbolic and numerical names of instructions Description The instructions from the task card are comprised of functions (FC), function blocks (FB), system functions (SFC) and system function blocks (SFB) that are identified internally by numbers. The following tables show the assignment of numerical and symbolic names. Function blocks (FBs) WinCC Basic V13.0 System Manual, 02/2014 Numerical name Symbolic name FB 105 TC_CONFIG FB 110 Port_Config FB 111 Send_Config FB 112 Receive_Config FB 113 Send_P2P FB 114 Receive_P2P FB 115 Receive_Reset FB 116 Signal_Get FB 117 Get_Features FB 118 Set_Features FB 163 TC_SEND FB 164 TC_RECV FB 165 TC_CON FB 166 TC_DISCON FB 804 SET_TIMEZONE FB 1030 TSEND_C FB 1031 TRCV_S FB 1071 USS_DRIVE FB 1080 MB_COMM_LOAD FB 1081 MB_MASTER 1017 Editing devices and networks 8.1 Configuring devices and networks Numerical name Symbolic name FB 1082 MB_SLAVE FB 1084 MB_CLIENT FB 1085 MB_SERVER FB 1100 MB_Halt FB 1101 MC_Home FB 1102 MC_MoveAbsolute FB 1103 MC_MoveJog FB 1104 MC_MoveRelative FB 1105 MC_MoveVelocity FB 1107 MC_Power FB 1108 MC_Reset FB 1110 MC_MoveInterrupt FB 1111 MC_ChangeDynamik FB 1112 MC_CommandTable FB 1113 MC_MoveLinearAbs_2D FB 1114 MC_MoveLinearRel_2D FB 1115 MC_MoveCircular_2D FB 1130 PID_Compact FB 1134 PID_3Step FB 1140 HSC FB 2040 RecipeCreate FB 2041 RecipeOpen FB 2042 RecipeRead FB 2043 RecipeWrite FB 2044 RecipeAppend FB 2045 RecipeClose Numerical name Symbolic name FC 2 (1) CONCAT FC 4 (1) DELETE Functions (FCs) FC 11 (1) FIND FC 17 INSERT (1) FC 20 (1) FC 21 LEFT LEN FC 22 (1) LIMIT FC 25 (1) MAX FC 26 1018 (1) (1) MID FC 27 (1) MIN FC 31 (1) REPLACE FC 32 (1) RIGHT WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Numerical name Symbolic name FC 36 (1) ENCO FC 36 SEL (1) FC 37 DECO FC 800 LED FC 801 IM_DATA FC 802 DeviceStates FC 803 ModuleStates FC 1070 USS_PORT FC 1072 USS_RPM FC 1073 USS_WPM (1) MC7+ instruction System data types (SDTs) Numerical name Symbolic name SDT 99 WWW_CDB SDT 513 CONDITIONS SDT 581 Send_Conditions SDT 582 Receive_Conditions System function blocks (SFBs) WinCC Basic V13.0 System Manual, 02/2014 Numerical name Symbolic name SFB 0 (1) CTU SFB 1 (1) CTD SFB 2 (1) CTUD SFB 3 (1) TP SFB 4 (1) TON SFB 5 TOF (1) SFB 27 START_OB SFB 52 RDREC SFB 53 WRREC SFB 54 RALRM SFB 105 T_CONFIG SFB 106 TDIAG SFB 107 TRESET SFB 110 PORT_CFG SFB 111 SEND_CFG SFB 112 RCV_CFG SFB 113 SEND_PTP SFB 114 RCV_PTP 1019 Editing devices and networks 8.1 Configuring devices and networks Numerical name Symbolic name SFB 115 SGN_GET SFB 116 SGN_SET SFB 117 RCV_RST SFB 120 CTRL_HSC SFB 122 CTRL_PWM SFB 140 DataLogCreate SFB 141 DataLogOpen SFB 142 DateLogWrite SFB 143 DataLogClear SFB 144 DataLogClose SFB 145 DataLogDelete SFB 146 DataLogNewFile System functions (SFCs) 1020 Numerical name Symbolic name SFC 7 DP_PRAL SFC 11 DPSYC_FR SFC 13 DPNRM_DG SFC 14 DPRD_DAT SFC 16 RD_OBINF SFC 23 DEL_DB SFC 28 SET_TINT SFC 29 CAN_TINT SFC 30 ACT_TINT SFC 31 QRY_TINT SFC 32 SRT_DINT SFC 33 CAN_DINT SFC 34 QRY_DINT SFC 41 DIS_AIRT SFC 42 EN_AIRT SFC 43 RE_TRIGR SFC 45 DE_ACT SFC 46 STP SFC 82 CREA_DBL SFC 83 READ_DBL SFC 84 WRIT_DBL SFC 86 CREATE_DB SFC 89 RST_EVOV SFC 99 WWW SFC 101 RTM SFC 117 GET_DIAG WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Numerical name Symbolic name SFC 124 ATTR_DB SFC 140 IO2MOD SFC 143 RD_ADDR SFC 154 RD_LOC_T SFC 154 DPWR_DAT SFC 161 WR_LOC_T SFC 180 ID2LOG SFC 181 LOG2ID SFC 182 ID2GEO SFC 190 SET_CINT SFC 191 QRY_CINT SFC 192 ATTACH SFC 193 DETACH MC7+ Anweisung GET_ERROR MC7+ Anweisung GET_ERR_ID Useful information on CPU firmware versions and STEP 7 versions CPUs and engineering software for configuring the CPUs is constantly developed further to improve performance and security. New versions that have some special features with respect to the interaction of the components are created in this way. The sections below describe the special features of the S7-1200 CPUs with firmware version V4 as compared to firmware versions V1 to V3. For a detailed comparison of the range of functions, read the S7-1200 System Manual (description of new instructions, new organization blocks and advanced configuration options). Required engineering software S7-1200 CPUs V4 can be configured with STEP 7 as of V13. Compatibility between memory card content and firmware version of the CPU Memory cards (transfer cards or program cards) with configuration and program for an S7-1200 CPU V1, V2 or V3 do not work with an S7-1200 CPU V4. Memory cards with configuration and program for an S7-1200 CPU V4 do not work with an S7-1200 CPU V1, V2 or V3. You must change an S7-1200 CPU V1 to V3 configuration to an S7-1200 CPU V4 configuration (device replacement) and then download it to the CPU. A gradual device replacement is required for an S7-1200 CPU V1-V2 (see below). When you insert the memory card into a CPU with an incompatible firmware version, the CPU does not start up. When you insert a memory card for a CPU V1, V2 or V3 into an S7-1200 CPU V4, this CPU outputs a version error. WinCC Basic V13.0 System Manual, 02/2014 1021 Editing devices and networks 8.1 Configuring devices and networks Going online and loading When you have configured an S7-1200 CPU with firmware version V1, V2 or V3 with STEP 7, the CPU to which you want to go online or which you want to download must have one of these firmware versions. You cannot go online to an S7-1200 CPU V4 with a configured S7-1200 CPU V1, V2 or V3. On the other hand, you cannot go online to an S7-1200 CPU V1, V2 or V3 with a configured S7-1200 CPU V4 or download this CPU. Replacing an existing CPU You can replace a configured S7-1200-CPU V1, V2 or V3 with a new CPU with a firmware version greater than or equal to 4. In case of an existing S7-1200 CPU V1 or V2, you must start by replacing the device with an S7-1200 CPU V3: It is not possible to directly replace it with an S7-1200 CPU V4. 1. S7-1200 CPU V1 (V2) > S7-1200 CPU V3 2. S7-1200 CPU V3 > S7-1200 CPU V4 As long as you do not download the configuration, you can undo the device replacement ("Undo" command in the "Edit" menu). When you download the configuration for the new CPU firmware version ("V4 configuration") to the CPU, you can no longer return to version V3. This means you should save the existing project, for example, with a V3 configuration as project archive so that you can access it later. Special notes for device replacement (V3 > V4): The interrupt behavior of interrupt OBs remains the same; they are not configured as interruptible. This is also the default behavior of S7-1200 CPUs V1-V3. The interrupt behavior of the interrupt OB can be configured for S7-1200 V4 CPUs. If you drag an S7-1200 CPU V4 directly from the hardware catalog into the network view, this option is activated (interrupt OBs are interruptible). The behavior for PUT/GET access of remote partners remains the same; access is permitted. This is also the default behavior of S7-1200 CPUs V1-V3. The access via PUT/ GET communication by means of remote partners can be configured for S7-1200 V4 CPUs ("Protection" area of CPU parameters). If you drag an S7-1200 CPU V4 directly from the hardware catalog into the network view, access is not permitted and must be explicitly enabled. The wording for the protection levels changes but the effect of the settings remains the same. You can also select the access level "No access (complete protection)". The web server settings for activation of the web server and HTTP/HTTPS settings are applied. You also have the option to create users and assign them specific rights (Web server area > User management of CPU parameters). Web server users only have access to standard websites when you do not configure users. An S7-1200 CPU V4 no longer supports the user "admin" and his/her password. Communication with HMI devices When you connect an HMI device to an S7-1200 CPU V4, make sure that you use the appropriate Runtime software version of the HMI device. 1022 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks You may have to transfer the latest HMI Runtime version by means of the WinCC engineering software. You must compile the HMI configuration once again and download it to the HMI device for the CPU-HMI communication to work. See also Useful information on memory cards (Page 955) 8.1.6.2 Identification systems RFID systems Communications module RF120C Reader parameter group The "Reader" parameter group contains the following: Diagnostics: Setting to decide whether or not hardware diagnostics messages are output. Reader System: Selection of the connected RFID system. Depending on the selection you make, the "Reader System" parameter group is adapted. "Diagnostics" parameter Parameter assignment options: None Apart from standard diagnostics messages, no other diagnostics messages are generated. Hard Errors Extended diagnostics messages are generated if the following events occur. - Hardware error (memory test) - Firmware error (checksum) - Connection to reader lost - Short-circuit fault/interruption if supported by the hardware Further information For further information on diagnostics, refer the documentation for the RF120C communications module with application blocks for S7-1200 and S7-1500. WinCC Basic V13.0 System Manual, 02/2014 1023 Editing devices and networks 8.1 Configuring devices and networks Reader System parameter group The parameters for the selected identification system are set in the "Reader system" parameter group. The table shows the parameters that exist for all identification systems (RFID and code reader systems). Table 8-56 Standard parameters for all identification systems Parameter Parameter value Default value Description Baud rate reader 19.2 kBd 115.2 kBd After changing the baud rate, the reader must be turned off and on again. On On = presence is reported as soon as there is a transponder in the antenna field of the reader 57.6 kBd 115.2 kBd Presence Check On Off (RF field off) Off (RF field on ) = the presence check in the FB is suppressed. The antenna on the reader is nevertheless turned on as long as it has not been turned off by a command. Off (RF field on) Off (RF field off) = the antenna is turned on only when a command is sent and it then turns itself off again (RF300 only) Reset ERRLED On Off Off On = the flashing of the error LED on the RF120C is reset by each FB reset. Off = the error LED always indicates the last error. The display can only be reset by turning off the RF120C. The following parameters are system specific according to the selection you made in the "Reader" parameter group. RF200 Table 8-57 RF200 general Parameter Parameter value Default value Description - - - Only the standard parameters are available. Parameter Parameter value Default value Description RF power 0.50 - 5.00 W 1.00 W Setting for the output power of the reader. Table 8-58 1024 RF290R WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks RF300 Table 8-59 RF300 general Parameter Parameter value Default value Description Transponder type RF300 RF300 Selection of the transponders used. ISO 15693 Table 8-60 RF380R Parameter Parameter value Default value Description RF power 0.50 - 2.00 W 1.25 W Setting for the output power of the reader. Transponder type RF300 RF300 Selection of the transponders used. ISO 15693 RF600 Table 8-61 Reader System: RF600 Parameter Parameter value Default value Description Max. no. of transponders 1 - 80 1 Number of transponders expected in the antenna field. Permitted values: 1 - 40 for RF620R 1 - 80 for RF630R with 2 antennas 1 - 40 for RF630R with 1 antenna The value stored in "multitag" defines the expected number of transponders to be read (EPC-ID) in the inventory. The value does not restrict the number of transponders to be processed in the antenna field. To ensure an efficient inventory of transponders in the antenna field, make sure that the values specified here do not deviate by more than approximately 10% from the maximum number of transponders to be expected in the antenna field. Reader type RF620R ETSI RF620R FCC RF620R CMIIT RF630R ETSI RF620R ETSI Selection of the reader used. By selecting a reader, you open the "Reader type" parameter group. The parameters are described in the following table. RF630R FCC RF630R CMIIT WinCC Basic V13.0 System Manual, 02/2014 1025 Editing devices and networks 8.1 Configuring devices and networks Reader type (RF600 only) In the "Reader type" parameter group further specific parameters are set for the reader type selected in the "Reader system" parameter group. Table 8-62 RF600 menu: Reader type Parameter Parameter value Default value Description Wireless profile - - Selection of the relevant wireless profile for ETSI, FCC or CMIIT. Multitag mode UID = EPC-ID (8 bytes) UID = EPC-ID (8 bytes) UID = EPC-ID (8 bytes) 8 byte UID of the bytes 5-12 of the 12 byte long EPC-ID UID = Handle ID (4 bytes) Intelligent Single Tag Mode (ISTM) On Black List On UID = handle ID (4 bytes) 4 byte UID as handle ID for access to transponders with an EPC-ID of any length Off Enable/disable the "Intelligent Single Tag Mode ISTM" algorithm 1) Off Enable/disable the "Black list" 1) Off Off Radiated power internal antenna (RF620R) 0-B 4 Setting the radiated power for the internal antenna 1) 2) Internal antenna (RF620R) - - Enable/disable the internal antenna. With the RF620R, either only the internal or only the external antenna can be set. Transmit power (external antenna RF620R) 0-9 4 Setting the transmit power for the external antenna 1) 2) External antenna (SetAnt block required) (RF620R) - - Enable/disable the external antenna. Transmit power ANT 1 (RF630R) 0-9 4 Setting the transmit power for antenna 11) 2) Transmit power ANT 2 (RF630R) 0-9 4 Setting the transmit power for the antenna 21) 2) Communications speed Reliable detection Reliable detection 1) Off Enable/disable "Tag hold" 1) Off Enable/disable the "Scanning mode" 1) - Selection of the wireless channels to be used 1) With the RF620R, either only the internal or only the external antenna can be set. Fast detection Tag hold On Off Scanning mode On Off Channel assignment (only with wireless profile ETSI) - 1) You will find further information in the "Configuration manual RF620R/RF630R". * 2) The values for the transmit/radiated power of the antennas can be found in the following table. * You will find the configuration manual RF620R/RF630R here (http:// support.automation.siemens.com/WW/view/en/10805817). 1026 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Table 8-63 Transmit / radiated power of the antennas Hex value RF630R transmit power RF620R radiated power (internal antenna) RF620R transmit power ETSI FCC CMIIT dBm / (mW) dBm / (mW) ERP dBm / (mW) EIRP dBm / (mW) ERP dBm / (mW) 0 18 / (63) 18 / (63) 20 / (100) 18 / (65) 18 / (63) 1 19 / (79) 19 / (79) 21 / (126) 19 / (79) 19 / (79) ... ... ... ... ... ... 4 22 / (158) 22 / (158) 24 / (251) 22 / (158) 22 / (158) ... ... ... ... ... ... 9 27 / (501) 27 / (501) 29 / (794) 27 / (501) 27 / (501) A 27 / (501) 28 / (631) 30 / (1000) 28 / (631) 27 / (501) B (...F) 27 / (501) 29 / (794) 31 / (1259) 29 / (794) 27 / (501) SLG D10S Table 8-64 SLG D10S Parameter Parameter value Default value Description RF power 0.50 - 10.00 W 1.00 W Setting for the output power of the reader. Transponder type ISO ISO Selection of the transponders used. I-Code (e.g. MDS D139) SLG D11S/D12S Table 8-65 SLG D11S/D12S Parameter Parameter value Default value Description Transponder type ISO ISO Selection of the transponders used. I-Code (e.g. MDS D139) WinCC Basic V13.0 System Manual, 02/2014 1027 Editing devices and networks 8.1 Configuring devices and networks MOBY U Table 8-66 MOBY U Parameter Parameter value Default value Description Standby time 0 - 1400 ms 0 ms Standby time (scanning_time) for the transponder. If the transponder receives a further command before the standby time has elapsed, this command can be executed immediately. If the transponder receives a command after standby time has elapsed, command execution is delayed by the "sleep_time" of the transponder. Range limitation 0.2 m 1.5 m - 0.5 m 1.0 m 1.5 m 2.0 m 2.5 m 3.0 m 3.5 m Max. no. of transponders 1 - 12 1 Maximum number of transponders that can be processed at the same time in the antenna field. BERO mode Without BEROs Without BEROs Without BEROs No reader synchronization 1 or 2 BEROs 1 or 2 BEROs The BEROs are logically ORed. The antenna field is turned on during the actuation of a BERO. 1st BERO on, 2nd BERO off Synchronization by cable connection 1st BERO on, 2nd BERO off 1st BERO turns on the antenna field and the 2nd BERO turns the antenna field off. If there are two BEROs present and "BERO time in s" is set, the antenna field is turned off automatically if the 2nd BERO does not switch within this BERO time. If no "BERO time in s" is set, the antenna field remains turned on until the 2nd BERO is activated. Synchronization by cable connection Enable reader synchronization via cable connection (see manual on configuration, installation and service for MOBY U). BERO time in s 0 - 255 s 0s Can only be set if the BERO mode is set to "1st BERO on, 2nd BERO off". 0 The time monitoring is disabled. To turn off the field, the 2nd BERO is required. 1 ... 255 s Operating time for the reader field 1028 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks General Reader Table 8-67 General Reader Parameter Parameter value Default value Description Input box for byte sequence (hexadecimal) 00000000 00000000 Expert mode With this function, you can specify the reset parameters directly in hexadecimal notation. This setting may only be selected if you have previously received the hexadecimal string for the setting from a member of the SIEMENS staff. Parameters via FB / code readers Table 8-68 Parameters via FB / code readers Parameter Parameter value Default value Description MOBY mode RF200, RF300, RF600, MOBY D/U, MV RF200, RF300, RF600, MOBY D/U, MV Only the mode "RF200, RF300, RF600, MOBY D/U, MV" is supported. For further information on resetting a function block, refer to the documentation for the RF120C communications module with application blocks for S7-1200 and S7-1500. * * You will find information on the documentation here (http://support.automation.siemens.com/ WW/view/en/10805817). 8.1.6.3 Distributed I/O Distributed I/O systems SIMATIC ET 200 - The right solution for all applications SIMATIC ET 200 provides the most varied range of distributed I/O systems. Solutions for use in the control cabinet Solutions without control cabinet directly at the machine Additionally, there are also components that can be used in explosive areas. SIMATIC ET 200 systems for construction without a control cabinet are contained in robust, glass-fibre reinforced plastic casing and are therefore shock-resistant, resistant to dirt and watertight. Their modular design allows the ET 200 systems to be easily scaled and expanded in small steps. Fully-integrated auxiliary modules lower costs and also provide a wide range of possible applications. There are several combination possibilities available: Digital and analog I/OS Intelligent modules with CPU functions, WinCC Basic V13.0 System Manual, 02/2014 1029 Editing devices and networks 8.1 Configuring devices and networks Safety technology, Pneumatics, Frequency converters Various technology modules. Communication via PROFIBUS and PROFINET, uniform engineering, clear diagnostic possibilities as well as optimal connection to SIMATIC controller and HMI devices vouch for the unique consistency provided by Totally Integrated Automation. The following table provides an overview of I/O devices for use in the control cabinet: I/O device Properties ET 200S Highly modular design with multiple conductor connections Multifunctional due to a wide range of modules Use in explosive areas (Zone 2) ET 200S COMPACT Highly modular design with multiple conductor connections Multifunctional due to a wide range of modules Use in explosive areas (Zone 2) Integrated DE/DA ET 200L Cost-effective digital block I/OS Digital electronic blocks up to 32 channels ET 200M Modular design with standard modules from SIMATIC-S7-300 Failsafe I/O modules Use in explosive areas up to Zone 2, sensors and actuators up to Zone 1 High level of plant availability, for example by plugging and unplugging when in operation ET 200iSP Modular design, also possible with redundancy Robust and intrinsically safe design Use in explosive areas up to Zone 1/21; sensors and actuators even up to Zone 0/20 High level of plant availability, for example by plugging and unplugging when in operation The following table provides an overview of I/O devices for use without a control cabinet: 1030 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks I/O device Properties ET 200pro Modular design with compact housing Easy assembly Multifunctional due to a wide range of modules High level of availability due to plugging and unplugging in operation and permanent wiring Comprehensive diagnostics ET 200eco PN Cost-efficient, space-saving block I/OS Digital modules up to 16 channels (also configurable) Analog modules, IO-link master and load voltage distributor PROFINET connection with 2-port switch in each module Can be flexibly distributed via PROFINET in line or star shape directly within the plant ET 200eco Cost-effective digital block I/OS Flexible connection possibilities Failsafe modules High level of plant availability ET 200R Specially for use on robots Assembled directly on the chassis Resistant to weld spatter due to robust metal housing See also Documentation on ET 200L (http://support.automation.siemens.com/WW/view/de/1142908/0/ en) Documentation on ET 200S (http://support.automation.siemens.com/WW/view/en/1144348) Documentation on ET 200M (http://support.automation.siemens.com/WW/view/de/1142798/0/ en) Documentation on ET 200pro (http://support.automation.siemens.com/WW/view/de/ 21210852/0/en) Documentation on ET 200iSP (http://support.automation.siemens.com/WW/view/de/ 28930789/0/en) Documentation on ET 200R (http://support.automation.siemens.com/WW/view/de/ 11966255/0/en) Documentation on ET 200eco PN (http://support.automation.siemens.com/WW/view/de/ 29999018/0/en) Documentation on ET 200eco (http://support.automation.siemens.com/WW/view/de/ 12403834/0/en) WinCC Basic V13.0 System Manual, 02/2014 1031 Editing devices and networks 8.1 Configuring devices and networks ET 200iSP ET 200iSP Distributed I/O Station Definition The ET 200iSP distributed I/O station is a highly modular and intrinsically safe DP slave with degree of protection IP 30. Area of application The ET 200iSP distributed I/O station can be operated in potentially explosive atmospheres characterized by gas and dust: Approval ET 200iSP Station* Inputs and outputs ATEX Zone 1, Zone 21 up to Zone 0, Zone 20 ** IECEx Zone 2, Zone 22 up to Zone 0, Zone 20 ** * In combination with an appropriate enclosure ** for electronic module 2 DO Relay UC60V/2A: up to Zone 1, Zone 21 The ET 200iSP distributed I/O station can, of course, also be used in the safety area. You can insert almost any combination of ET 200iSP I/O modules directly next to the interface module that transfers the data to the DP master. This means you can adapt the configuration to suit your on-site requirements. Every ET 200iSP consists of a power supply module, an interface module and a maximum of 32 electronic modules (for example digital electronics modules). Remember not to exceed the maximum current consumption. Terminal modules and electronic modules In principle, the ET 200iSP distributed I/O station consists of various passive terminal modules onto which you plug the power supply and the electronic modules. The ET 200iSP is connected to PROFIBUS RS 485-IS by means of a connector on terminal module TM-IM/EM. Every ET 200iSP is a DP slave on the PROFIBUS RS 485IS. DP master All ET 200iSP modules support communication with DP masters that are compliant with IEC 61784-1:2002 Ed1 CP 3/1 and operate with "DP" transmission protocol (DP stands for distributed peripherals or distributed I/O). See also Documentation on ET 200iSP (http://support.automation.siemens.com/WW/view/de/ 28930789/0/en) 1032 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Assigning the channel and IEEE tag Properties Analog electronic modules 4 AI I 2WIRE/HART, 4 AI I 4WIRE/ HART and 4 AO I HART support up to four IEEE tags. The process input image (PII) provides up to 20 bytes per module for the IEEE tags. Thus, four blocks of 5 bytes each are available for the four IEEE tags within the PII. Requirements The HART field device must support the assigned number of IEEE tags. WinCC Basic V13.0 System Manual, 02/2014 1033 Editing devices and networks 8.1 Configuring devices and networks Assigning IEEE tags You assign the IEEE tags of the field devices to any one of the four blocks in the PII. IL[HGDVVLJQPHQWRIDQDORJYDOXHVLQWKH3,, DQ\DVVLJQPHQWRI,(((YDULDEOHVLQWKH3,, 3,,RID+$57LQSXW PRGXOHZLWKFRQILJXUD WLRQ: ,%[ ,%[ ,%[ ,%[ ,%[ ,%[ ,%[ ,%[ $QDORJ YDOXH $QDORJ YDOXH $QDORJ YDOXH $QDORJ YDOXH 6HFRQGDU\YDOXH ,%[ ,((( ,%[ YDULDEOH ,%[ IURP ,%[ FKDQQHO ,%[ 6HFRQGDU\YDOXH ,%[ ,((( ,%[ YDULDEOH ,%[ IURP ,%[ FKDQQHO ,%[ 6HFRQGDU\YDOXH ,%[ ,((( ,%[ YDULDEOH ,%[ IURP ,%[ FKDQQHO ,%[ 6HFRQGDU\YDOXH ,%[ ,((( ,%[ YDULDEOH ,%[ IURP ,%[ FKDQQHO ,%[ HJ+$57 LQSXWPRGXOH +$57ILHOGGHYLFHRQFKDQQHO $QDORJYDOXH FRUUHVSRQGVWR+9 ,(((YDULDEOH +9 ,(((YDULDEOH ,(((YDULDEOH ,(((YDULDEOH +$57ILHOGGHYLFHRQFKDQQHO $QDORJYDOXH FRUUHVSRQGVWR+9 ,(((YDULDEOH +9 ,(((YDULDEOH ,(((YDULDEOH ,(((YDULDEOH +$57ILHOGGHYLFHRQFKDQQHO $QDORJYDOXH FRUUHVSRQGVWR+9 ,(((YDULDEOH +9 ,(((YDULDEOH ,(((YDULDEOH ,(((YDULDEOH +$57ILHOGGHYLFHRQFKDQQHO $QDORJYDOXH FRUUHVSRQGVWR+9 ,(((YDULDEOH +9 ,(((YDULDEOH ,(((YDULDEOH ,(((YDULDEOH +9 PDLQYDULDEOH See also Documentation on ET 200iSP (http://support.automation.siemens.com/WW/view/de/ 28930789/0/en) 1034 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Assigning parameters to reference junctions for thermocouples Compensation of the reference junction temperature There are various ways of obtaining the reference junction temperature in order to get an absolute temperature value from the temperature difference between the reference junction and the measuring point. Table 8-69 Compensation of the reference junction temperature Option Explanation Reference junction parameters No compensation You record not only the temperature of the measurement point. The temperature of the reference junction (transition from Cu line to thermocouple line) also affects the thermoelectromotive force. The measured value then includes an error. None Use of a Pt100 Climatic Range resistance thermometer to record the reference junction temperature (best method) You can record the reference junction temperature using a resistance thermometer (Pt100 Climatic Range). If parameterized accordingly, this temperature value is distributed to the 4 AI TC modules in the ET 200iSP where it is offset against the temperature value obtained at the measuring location. The parameter assignment of the IM 152 and the 4 AI TC must be coordinated: Number of reference junctions: 2 4 AI RTD assigned parameters for Pt100 climatic range in correct slot; 4 AI TC: Reference junction : "yes"; select reference junction number "1" or "2" IM 152-1:Assignment of the reference junction to a slot with 4 AI RTD; channel selection; Internal compensation 4 AI TC The TC sensor module (temperature sensor) is mounted onto the terminals of terminal module EM 4 AI TC. The temperature sensor reports the temperature of the terminals to the 4 AI TC. This value is then calculated together with the measured value from the channel of the electronic module. 4 AI TC: Reference junction number "internal" Compensation by means of a resistance thermometer at the 4 AI RTD If thermocouples that are connected to the inputs of the 4 AI RTD have the same reference junction, compensate by means of a 4 AI RTD. For both channels of the 4 AI TC module, you can select "1", "2" or "internal" as the reference junction number. If you select "1" or "2", the same reference junction (RTD channel) is always used for all four channels. WinCC Basic V13.0 System Manual, 02/2014 1035 Editing devices and networks 8.1 Configuring devices and networks Setting parameters for the reference junction You set the reference junctions for the 4 AI TC electronic modules by means of the following parameters: Table 8-70 Reference junction parameters Parameter Module Range of values Explanation Slot reference junction 1 to slot 2 IM 152 none, 4 to 35 With this parameter, you can assign up to 2 slots (none, 4 to 35), on which the channels for reference temperature measurement (calculating the compensation value) are located. Input reference junction 1 to 4 input reference junction RTD on channel 0 This parameter allows you to set the channel (0/1/2/3) for measuring the reference temperature (calculation of the compensation value) for the assigned slot. IM 152 RTD on channel 1 RTD on channel 2 RTD on channel 3 Reference junction E0 to reference junction E3 4 AI TC None Reference junction number 4 AI TC 1 yes 2 Internal This parameter allows you to enable the use of the reference junction. This parameter allows you to assign the reference junction (1, 2) that contains the reference temperature (compensation value). See also Documentation on ET 200iSP (http://support.automation.siemens.com/WW/view/de/ 28930789/0/en) Fundamentals of Time Stamping Properties Time stamping is possible with the IM 152 in customer applications using FB 62 (FB TIMESTMP). Principle of operation A modified input signal is assigned a time stamp and stored in a buffer (data record). If time stamped signals exists or a data record is full, a hardware interrupt is generated to the DP master. The buffer is evaluated with "Read data record". Special messages are generated for events that influence the time stamping (communication with the DP master interrupted, frame failure of time master, ...). 1036 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Parameter Assignment With the parameter assignment you define which IM 152 user data will be monitored. For the time stamping these are digital inputs that are monitoring for signal changes. Parameter Setting Description Time stamping disabled Activate the time staming for the channels of the electronics module 8 DI NAMUR. enabled Edge evaluation incoming event rising edge falling edge Determine the type of signal change that will be time-stamped. Counting Count properties Counting functions The 8 DI NAMUR electronics module has configurable counting functions: 2 x 16-bit up counters (standard counting function) or 2 x 16-bit down counters (standard counting function) or 1 x 32-bit down counter (cascading counter function) Setting a setpoint with the PIQ GATE function You can configure the control signals of the counters: - Configuration channel 0..1: "Counter", channel 2..7: "DI": Two counters are configured. The control signals of the counters are stored in the PIQ (process image output). - Configuration channel 0..1: "Counter", channel 2..7: "Control": Two counters are configured. The control signals of the counters are stored in the PIQ (process image output). They are also controlled by the digital inputs of the 8 DI NAMUR. See also Principle of operation (Page 1037) Configuring counters (Page 1040) Assigning parameters to counters (Page 1043) Principle of operation 16-bit up counters (standard counting function) The counting range is 0 to 65,535. WinCC Basic V13.0 System Manual, 02/2014 1037 Editing devices and networks 8.1 Configuring devices and networks With each count pulse at the digital input, the count is incremented by 1. Once the count limit is reached, the counter is reset to 0 and it counts up again from this value. If there is counter overflow, the corresponding output is set in the PII. A positive edge of the Reset output control signal resets the output in the PII. This does not affect the current count value. In 16-bit up counting operations, the system does not set any outputs in the PIQ. These are always reset. The positive edge of the Reset counter control signal sets the counter to 0 and resets the set counter output. The GATE control signal pauses the counting on a positive edge. Count pulses are processed at the digital input again, but only at the negative edge. The Reset counter control signal is also effective when GATE is active. $FWXDOYDOXHRIWKHFRXQWHU &RXQWLQJOLPLW &RXQWHURXWSXWLQ 3,, &RQWUROVLJQDO5HVHW RXWSXW &RQWUROVLJQDO5HVHW FRXQWHU &RQWUROVLJQDO *$7( 3XOVHVDWGLJLWDO LQSXW 7LPH 7LPH 7LPH 7LPH 7LPH 7LPH 16-bit down counters (periodic counting function) The maximum counting range is always 65,535 to 0. When the counter is started, the actual value is set to the selected setpoint. Each counted pulse reduced the actual value by 1. Once the actual value reaches 0, the corresponding output in the PII is turned on and the actual value is set to the selected setpoint. The counter then counts down from this value. The positive edge of the Reset counter control signal resets the selected setpoint and the corresponding output in the PII. A positive edge of the Reset output control signal resets the output in the PII. This does not affect the current count value. 1038 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks The GATE control signal pauses the counting on a positive edge. At the same time, the assigned output in the PII is reset. Count pulses are processed at the digital input again, but only at the negative edge. The Reset output and Reset counter control signals are also effective when GATE is active. The setpoint of the counter is set and changed using the PIQ. The setpoint is adopted on a positive edge of the Reset counter control signal or when the counter has reached zero. $FWXDOYDOXHRIWKH FRXQWHU 6SHFLILHGYDOXH &RXQWHURXWSXW LQ3,, &RQWUROVLJQDO 5HVHWRXWSXW &RQWUROVLJQDO 5HVHWFRXQWHU &RQWUROVLJQDO *$7( 3XOVHVDW GLJLWDOLQSXW 7LPH 7LPH 7LPH 7LPH 7LPH 7LPH 32-bit down counter (cascading counter function) The maximum counting range is always 4294967295 to 0. The principle of operation is identical to that of the 16-bit down counter. Channel 1 has no function. See also Count properties (Page 1037) WinCC Basic V13.0 System Manual, 02/2014 1039 Editing devices and networks 8.1 Configuring devices and networks Configuring counters Procedure 1. Using the mouse, pull module 8 DI Namur from the hardware catalog into distributed I/O station ET 200iSP. 2. Select the required configuration (channel 0..1: "Counter", channel 2..7: "DI" or "Control"). In the module properties (inspector window), you can find this setting under "Parameters > Inputs > Configuration". Configuration channel 0..1: "Counter", channel 2..7: "DI" Assignment of the digital inputs on the electronic module 8 DI NAMUR Table 8-71 1040 Assignment of digital inputs for channel 0..1: "Counter", channel 2..7: "DI": Digital input Terminal Assignment Channel 0 1, 2 Counter 1 Channel 1 5, 6 Counter 2 (does not apply to 32-bit down counters) Channel 2 9, 10 Digital input 2 Channel 3 13, 14 Digital input 3 Channel 4 3, 4 Digital input 4 Channel 5 7, 8 Digital input 5 Channel 6 11, 12 Digital input 6 Channel 7 15, 16 Digital input 7 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Assignment of the process image input (PII) (%[ (%[ (%[ (%[ %LWVWR $FWXDOYDOXHRIFRXQWHU %LWVWR %LWVWR %LWVWR $FWXDOYDOXHRIFRXQWHU %LWVWR %LWVWR %LWVWR %LWVWR 6HWSRLQWFRXQWHU ELW GRZQFRXQWHU (%[ &RXQWHURXWSXW &RXQWHURXWSXW 'LJLWDOLQSXW 'LJLWDOLQSXW 'LJLWDOLQSXW 'LJLWDOLQSXW 'LJLWDOLQSXW 'LJLWDOLQSXW 6IRUPDW (%[ (%[ 1RWDVVLJQHG 9DOXHVWDWXVIRUFKDQQHOVWR %,QSXWVLJQDOLVYDOLG %,QSXWVLJQDOLVLQYDOLG Assignment of the process image output (PIQ) $%[ $%[ $%[ $%[ %LWVWR 6SHFLILHGYDOXHRIFRXQWHU %LWVWR %LWVWR 6SHFLILHGYDOXHRIFRXQWHU %LWVWR %LWVWR %LWVWR %LWVWR %LWVWR 6HWSRLQWFRXQWHU ELW GRZQFRXQWHU $%[ 1RWDVVLJQHG 1RWDVVLJQHG &RQWUROVLJQDO*$7( &RQWUROVLJQDO*$7( &RQWUROVLJQDO5HVHWFRXQWHU &RQWUROVLJQDO5HVHWFRXQWHU &RQWUROVLJQDO5HVHWFRXQWHURXWSXW &RQWUROVLJQDO5HVHWFRXQWHURXWSXW WinCC Basic V13.0 System Manual, 02/2014 1041 Editing devices and networks 8.1 Configuring devices and networks Configuration channel 0..1: "Counter", channel 2..7: "CONTROL" With this configuration, you can also control the counters over the digital inputs. Assignment of the digital inputs on electronic module 8 DI NAMUR For further information on input assignments, refer to the technical data for electronic module 8 DI NAMUR. Table 8-72 Assignment of the digital inputs for 2 Count/ 6 Control Digital input Terminal Assignment Channel 0 1, 2 Counter 1 Channel 1 5, 6 Counter 2 (does not apply to 32-bit down counters) Channel 2 9, 10 control signal GATE 1 Channel 3 13, 14 control signal GATE 2 Channel 4 3, 4 control signal Reset counter 1 Channel 5 7, 8 control signal Reset counter 2 Channel 6 11, 12 control signal Reset counter output 1 Channel 7 15, 16 control signal Reset counter output 2 Assignment of the process image input (PII) Assignment is identical to configuration 0..1: "Counter", channel 2..7: "DI". Assignment of the process image output (PIQ) Assignment is identical to configuration 0..1: "Counter", channel 2..7: "DI". See also Count properties (Page 1037) 1042 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Assigning parameters to counters Parameters for the counting function Only those parameters that are relevant for the counters are explained below. These belong to the parameters of electronic module 8 DI NAMUR and depend on the selected configuration: Table 8-73 Parameters for the counters Parameter Setting Description Sensor type counter inputs Channel disabled Select the sensor for the respective counter of channels 0 or 1. NAMUR sensor Single contact, no load resistance Mode for counter 1 Standard counting function Select the mode for counter 1. Periodic counting function Cascaded counting function Mode for counter 2 Standard counting function Periodic counting function Cascaded counting function Select the mode for counter 2. This parameter is not relevant if you have set the "Mode for counter 1" parameter to "Cascaded counter function". See also Count properties (Page 1037) Frequency measurement Frequency measurement properties Properties The electronic module 8 DI NAMUR allows the frequencies to be measured on channel 0 and 1: 2 frequency meters from 1 Hz to 5 kHz Configurable metering window (GATE) The signals of the frequency meter are read in by means of the digital inputs of the electronic module. See also Principle of operation (Page 1044) Configuring frequency meters (Page 1044) Assigning parameters for the frequency meters (Page 1046) WinCC Basic V13.0 System Manual, 02/2014 1043 Editing devices and networks 8.1 Configuring devices and networks Principle of operation Frequency measurement The signal frequencies are identified from the input signals of channel 0 or 1 of the electronic module. To calculate the frequency the signals are measured within a configurable gate. The frequency is displayed as 16-bit value in fixed-point format and transferred to the PII. The frequency meter calculates the frequency according to the follow formula: )UHTXHQF\>+]@ 1XPEHURIULVLQJHGJHVDWGLJLWDOLQSXW 0HDVXULQJZLQGRZ>V@ Exceeding the input frequency If the input frequency exceeds 5kHz, 7FFFH is reported as actual value. If the input frequency is above approx. 8 kHz it is no longer possible to display correct actual values. See also Frequency measurement properties (Page 1043) Configuring frequency meters Procedure 1. Using the mouse, pull module 8 DI Namur from the hardware catalog into distributed I/O station ET 200iSP. 2. Select the required configuration (channel 0..1: "Trace", channel 2..7: "DI"). In the module properties (inspector window), you can find this setting under "Parameters > Inputs > Configuration". Configuration 0..1: "Trace", channel 2..7: "DI" Assignment of the digital inputs on electronic module 8 DI NAMUR Digital input Terminal Assignment Channel 0 1, 2 Frequency counter 1 Channel 1 5, 6 Frequency counter 2 Channel 2 9, 10 Digital input 2 Channel 3 13, 14 Digital input 3 Channel 4 3, 4 Digital input 4 Channel 5 7, 8 Digital input 5 Channel 6 11, 12 Digital input 6 Channel 7 15, 16 Digital input 7 1044 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Assignment of process image input (PII) for configuration of channel 0..1: "Trace", channel 2..7: "DI" (%[ (%[ (%[ (%[ (%[ %LWVWR %LWVWR %LWVWR %LWVWR )UHTXHQF\PHWHU )UHTXHQF\PHWHU 1RWDVVLJQHG 1RWDVVLJQHG 'LJLWDOLQSXW 'LJLWDOLQSXW 'LJLWDOLQSXW 'LJLWDOLQSXW 'LJLWDOLQSXW 'LJLWDOLQSXW 6IRUPDW (%[ (%[ 1RWDVVLJQHG 9DOXHVWDWXVIRUFKDQQHOVWR %,QSXWVLJQDOLVYDOLG %,QSXWVLJQDOLVLQYDOLG Assignment of the process image output (PIQ): The PIQ is not assigned. See also Frequency measurement properties (Page 1043) WinCC Basic V13.0 System Manual, 02/2014 1045 Editing devices and networks 8.1 Configuring devices and networks Assigning parameters for the frequency meters Parameters for frequency meter Only those parameters that are relevant for the frequency meters are explained below. These are part of the parameters of electronic module 8 DI NAMUR. Table 8-74 Parameters for the frequency meters Parameter Setting Description Sensor type frequency inputs Channel disabled Select the sensor for the relevant frequency meter for channel 0 or 1. NAMUR sensor Single contact, no load resistance Measuring window (GATE) 50 ms 200 ms 1s Select the required measuring window for channel 0 or 1. To achieve the highest possible accuracy when metering frequencies, remember the following rules: High frequencies (> 4 kHz): Set a low measuring window (50 ms) Variable/medium frequencies: set medium measuring window (200 ms) Low frequencies (< 1 kHz): Set a high measuring window (1 s) See also Frequency measurement properties (Page 1043) ET 200eco PN ET 200eco PN Distributed I/O Device Definition The ET 200eco PN distributed I/O device is a compact PROFINET IO device in degree of protection IP 65/66 or IP 67 and UL Enclosure Type 4x, Indoor use only. 1046 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Field of application The fields of application of the ET 200eco PN are derived from its special properties. A robust design and degree of protection IP 65/66 or IP 67 make the ET 200eco PN distributed I/O device suitable in particular for use in rugged industrial environments. The compact design of the ET 200eco PN is particularly favorable for applications in confined areas. The easy handling of ET 200eco PN facilitates efficient commissioning and maintenance. Properties The ET 200eco PN has the following properties: Integrated switch with 2 ports Supported Ethernet services: - ping - arp - Network diagnostics (SNMP) - LLDP Interrupts - Diagnostics interrupts - Maintenance interrupts Port diagnostics Isochronous real-time communication Prioritized startup Device replacement without programming device Media redundancy Connection to intelligent sensors/actuators via IO link master interface module. IO Controller The ET 200eco PN can communicate with all IO Controllers that conform to IEC 61158. ET 200eco PN can be configured on a CPU with advanced diagnostics. See also Documentation on ET 200eco PN (http://support.automation.siemens.com/WW/view/en/ 29999018) WinCC Basic V13.0 System Manual, 02/2014 1047 Editing devices and networks 8.1 Configuring devices and networks Parameter description analog input Group diagnostics You can generally enable and disable the diagnostics function of the device with this parameter. The "Fault" and "Parameter assignment error" diagnostics functions are always independent of the group diagnostics. Diagnostics, missing 1L+ If you enable this parameter, the check for missing supply voltage is enabled. Diagnostics, sensor supply short circuit If you enable this parameter, a diagnostics event is generated if a short-circuit of the sensor supply to ground is detected and the channel is enabled. The sensor supply is monitored for connectors X1, X3, X5 and X7. It is not possible to differentiate which connector has experienced the sensor short circuit. Interference frequency suppression With this parameter, you set the integration time of the device, based on the selected interference frequency. Select the frequency of the supply voltage used. Interference frequency suppression Off means 500 Hz, which corresponds to an integration time of 2 ms for a measurement channel. Temperature unit Specify the unit of the temperature measurement here. Measurement type (channel-wise) With this parameter, you set the measurement type, for example, voltage. For any unused channels, you must select the disabled setting. For a disabled channel, the conversion time and integration time of the channel = 0 s and the cycle time is optimized. Measuring range With this parameter, you set the measuring range of the selected measurement type. Temperature coefficient (for RTD, thermoresistor) The correction factor for the temperature coefficients (-value) indicates by what extent the resistance of specific material changes relatively if the temperature increases by 1 . The -values conform to EN 60751, GOST 6651, JIS C 1604 and ASTM E-1137. The temperature coefficient depends on the chemical composition of the material. 1048 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Smoothing Smoothing of the analog values produces a stable analog signal for further processing. The smoothing of analog values is useful when handling wanted signals (measured values) with a slow rate of change, for example, temperature measurements. The measured values are smoothed by digital filtering. To achieve smoothing, the device generates a mean value from a specified number of converted (digitized) analog values. You assign a maximum of four levels for the smoothing (none, weak, medium, strong). The level determines the number of module cycles, from which the mean value is generated. The stronger the smoothing, the more stable the smoothed analog value and the longer it takes until the smoothed analog value is applied following a signal change (see the example below). The figure below shows the number of cycles a module requires to apply the smoothed analog value at almost 100% after a step response, based on the smoothing function settings. The figure applies to all signal changes at the analog input. The smoothing value defines the number of cycles a module requires to reach 63% of the end value of the changed signal. 6LJQDO FKDQJH [ [ [ 0RGXOHF\FOHV Smoothing, weak Smoothing, medium Smoothing, strong Diagnostics, wire break When this parameter is enabled, the Wire break diagnostics event is generated when a wire break is detected. Observe the rules outlined below to handle a wire break in the 1 to 5 V and 4 to 20 mA measuring ranges: WinCC Basic V13.0 System Manual, 02/2014 1049 Editing devices and networks 8.1 Configuring devices and networks Parameter Enable wire break1 Wire break disabled 1 Event Measured value Explanation Wire break 7FFFH Diagnostics, wire break Wire break 8000H Measured value after leaving the underrange Underflow enabled Wire break disabled1 Diagnostic message Lower limit value undershot Wire break Underflow disabled 1 8000H Measured value after leaving the underrange Measuring range limits for wire break detection and measuring range undershoot detection: 1 to 5 V: At 0.296 V 4 to 20 mA: At 1.185 mA Diagnostics, underflow If you enable this parameter, the Underflow diagnostics event is generated when the measured value reaches the underflow range. Diagnostics, overflow If you enable this parameter, the Overflow diagnostics event is generated when the measured value reaches the overflow range. Reference junction for thermoresistor (TC) A difference in temperature between the measuring point and the free ends of the thermocouple (terminal point) generates a voltage between the free ends, namely the thermoelectric voltage. The value of this thermoelectric voltage is determined by the temperature difference between the measuring point and the free ends and by the type of material combination of the thermocouple. Since a thermocouple always measures a temperature difference, the free ends at the reference junction must be maintained at a known temperature in order to determine the temperature of the measuring point. If you specify Internal compensation, the temperature of the measuring point in the housing of the I/O device is measured. With the External compensation setting, you can connect a compensation box in series in order to increase the accuracy of the temperature measurement. Parameter description analog output Group diagnostics You can generally enable and disable the diagnostics function of the device with this parameter. The "Fault" and "Parameter assignment error" diagnostics functions are always independent of the group diagnostics. 1050 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Diagnostics, missing 1L+ If you enable this parameter, the check for missing supply voltage is enabled. Diagnostics, sensor supply short circuit When this parameter is enabled, the system generates a diagnostics event if it detects a shortcircuit of the sensor supply to ground. This diagnostics function is activated when the group diagnostics function is enabled. Response to CPU/Master STOP Select how the module's outputs will respond to a CPU STOP: Shut down The I/O device goes to the safe state. The process image output is deleted (=0). Keep last value The I/O device retains the last value to be output before STOP. Substitute value The I/O device outputs the value for the channel set beforehand. Note Make sure that the plant is always in a safe state if "Keep last value" is selected. Type of output With this parameter, you set the output type, for example, voltage. For any unused channels, select the disabled setting. For a disabled channel, the conversion time and integration time of the channel = 0 s, and the cycle time is optimized. Output range With this parameter, you set the output range of the selected output type. Diagnostics, wire break (in current mode) When this parameter is enabled, the Wire break diagnostics event is generated when a wire break is detected. This diagnostics event cannot be detected in the zero range. Diagnostics, short circuit (in voltage mode) If you enable this parameter, a diagnostics event is generated in the event of a short circuit in the output line. This diagnostics event cannot be detected in the zero range. Diagnostics, overload If you enable this parameter, the diagnostics event is generated in the event of an overload. WinCC Basic V13.0 System Manual, 02/2014 1051 Editing devices and networks 8.1 Configuring devices and networks Substitute values With this parameter, you enter a substitute value that the module is to output in CPU-STOP mode. The substitute value must be in the nominal range, overrange, or underrange. ET 200SP ET 200SP distributed I/O system Definition The ET 200SP distributed I/O system is a scalable, highly flexible distributed I/O system for connection of process signals to a central controller via a field bus. Application area The ET 200SP is a multi-functional distributed I/O system for various fields of application. The scalable design allows you to configure the system exactly to the specific requirements on location. The ET 200SP is approved for degree of protection IP 20 and for installation in a control cabinet. Structure The ET 200SP is mounted on a mounting rail and comprises: An interface module which can communicate with all IO controllers that conform to the PROFINET standard IEC 61158 Up to 32 I/O modules which can be inserted on passive BaseUnits in any combination A server module that completes the design of the ET 200SP. Interface module parameters Status bytes Status bytes If you enable the "Status bytes" option, 4 bytes of input data are reserved for the status of the supply voltage of each I/O module. 1052 %\WH %\WH %\WH %\WH ,2PRGXOHVORWV %LW %LW /RDGYROWDJHPLVVLQJRU,2PRGXOHQRW SUHVHQW /RDGYROWDJHDQG,2PRGXOHSUHVHQW WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Note An inserted or missing server module always reports for the slot bit = 0. Group diagnostics, missing supply voltage L+ Group diagnostics, missing supply voltage L+ This diagnostics is a group diagnostics that covers the supply voltage status of all I/O modules of a potential group which are defined by BaseUnits with incoming power supply (light-colored BaseUnit BU...D). The group diagnostics is formed from the states of the supply voltage of the inserted I/O modules within the potential group. The group diagnostics does not depend on the "Missing supply voltage L+" parameter of the I/O modules being enabled. The server module does not influence the missing supply voltage L+ group diagnostics. Requirements for the correct operation of the group diagnostics for missing supply voltage L+: I/O modules or BU covers must be inserted on the light-colored and dark-colored BaseUnits. If no I/O module is inserted on a light-colored BaseUnit, the start of this potential group will not be detected by the interface module; the I/O modules of this potential group will thus belong to the previous potential group. A supply voltage L+ group error will then be assigned to the wrong potential group. When an I/O module is inserted on the light-colored BaseUnit, the interface module detects the new potential group, re-evaluates the status, and reports a new group diagnostics in the case of an error. The server module must be inserted. The server module itself does not influence the missing supply voltage L+ group diagnostics. Configuration control Operating principle Configuration control allows you to operate various real configurations (options) with a single configuration of the distributed I/O device ET 200SP. Configuration control provides you with the option of configuring the ET 200SP distributed I/ O device with its maximum configuration and nevertheless operating it with missing modules. If missing modules are retrofitted later, no new configuration is required and the hardware configuration does not have to be reloaded either. Using control data records, which are transferred to the interface module in the user program, you define a current preset configuration. WinCC Basic V13.0 System Manual, 02/2014 1053 Editing devices and networks 8.1 Configuring devices and networks The configured module is not present on a slot. - A base unit cover may be inserted on this slot instead of the configured I/O module. As there is no configured module on the slot, the term "Configuration control with empty slots" is also used. - The module that is configured to the right of the missing module can be inserted on this slot instead of the configured module. The missing module makes the actual configuration appear pushed together. As the configured module is missing but no gap arises in the configuration, this is also referred to as a "Configuration without empty slots". The configuration is extended by an already configured module. - In the case of configuration control with empty spaces, you extend the configuration by inserting the configured module on the corresponding empty slot. - In the case of configuration control without empty spaces, insert the configured module on the right-hand side next to the last module of the ET 200SP. Addressing the interface module using the hardware identifier To transfer data record 196 with the instruction WRREC, you must enter the hardware identifier of the interface module as input parameter for the instruction. The system constant of this hardware identifier is, for example, "IO-Device_2 [Head]". The system constants of a selected device are, for example, displayed in the network view in the "System constants" tab. Use the associated value for addressing. More information and examples For information on the rules for configuration control, the structure of the control data record, and the behavior during operation as well as examples of the structure of the control data record for various configurations, refer to the IM 155-6 PN interface module manual (http:// support.automation.siemens.com/WW/view/en/59768173). Output module parameters Substitute value reaction Substitute value reaction In the ET 200SP, the substitute value reaction is executed by the IO controller per slot. The respective output reacts according to its set substitute value reaction: "Turn off" "Output substitute value" "Keep last value" This substitute value reaction is triggered in the following cases: 1054 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks IO controller in STOP Controller failure (connection interruption) Firmware update Reset to factory settings More than one I/O module withdrawn simultaneously Disable the IO device Station stop - Missing server module - More than one I/O module withdrawn simultaneously - At least one I/O module is inserted on the wrong BaseUnit Note Reducing a configuration If you reduce the configuration of the ET 200SP and download the configuration to the CPU, the modules which are no longer configured but still present retain their original substitute value reaction. This applies until the supply voltage on the BaseUnit BU...D or on the interface module is turned off. Input module parameters Parameters of the digital input modules Diagnostics missing supply voltage L+ Enabling of the diagnostics for missing or insufficient supply voltage L+. WinCC Basic V13.0 System Manual, 02/2014 1055 Editing devices and networks 8.1 Configuring devices and networks Diagnostics short-circuit to ground Enabling of the diagnostics if a short-circuit of the actuator supply to ground occurs. 0 / 1056 Encoder supply Short-circuit WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Diagnostics short-circuit to L+ Enabling of the diagnostics if a short-circuit of the encoder supply to L+ occurs. 0 / Encoder supply Short-circuit Diagnostics wire break Enabling diagnostics if the line to the encoder is interrupted. Operating mode Determines whether a channel is enabled or disabled. Pulse extension (only High Feature modules) Pulse extension is a function for changing a digital input signal. A pulse at a digital input is extended to at least the configured length. If the input pulse is already longer than the configured length, the pulse is not changed. Pulse extension is started whenever the state of the input signal changes and no pulse extension is active for this channel. WinCC Basic V13.0 System Manual, 02/2014 1057 Editing devices and networks 8.1 Configuring devices and networks Potential group of the left module / new potential group Specifies whether the I/O module is located on a base unit with supply voltage feed (new potential group) or whether it is it located on a base unit without supply voltage feed (in which case it belongs to the potential group of the left module). Parameters of the analog input modules Missing supply voltage L+ Enabling of the diagnostics, with missing or too little supply voltage L+. Reference junction (AI 4xRTD/TC 2-/3-/4-wire HF) A BaseUnit with internal temperature sensor (BU..T) or the channel 0 of the I/O module can be used as reference junction, provided this has been configured as "Thermal resistance Pt100 climatic range Celsius". A possible configuration is shown below: Table 8-75 RTD channel Setting Description No reference channel operation Temperature value at channel 0 can be used as module-wide reference value if the parameters of the other channels are assigned accordingly. Reference channel of Group 0 The channel acts as sender for the reference junction temperature of Group 0. Distribution is performed via the interface module. Table 8-76 TC channel Setting Description Reference channel of the module The corresponding TC channel uses the channel 0 of the same module as reference junction temperature. This must be set as "Thermal resistance Pt 100 climatic range Celsius" and "No reference channel operation"; otherwise, reference junction diagnostics is triggered. Internal reference junction The reference junction temperature is read by an internal temperature sensor on the BaseUnit. Reference junction diagnostics is triggered if there is a wrong BaseUnit type. Reference channel of Group 0 With the setting "TC" (thermocouple...), the channel acts as receiver for the reference junction temperature of Group 0 Fixed reference temperature No temperature compensation occurs. The linearization is executed with an assumed reference junction temperature of 0 C. Overflow Enabling of the diagnostics if the measured value exceeds the overflow range. 1058 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Underflow Enabling of the diagnostics if the measured value falls below the underflow range. Wire break Enabling of the diagnostics if the module has no current flow or too low a current flow for the measurement on the corresponding configured input. Smoothing The individual measurements are smoothed using digital filtering. The smoothing can be set in 4 stages, whereby the smoothing factor k multiplied by the cycle time of the I/O module corresponds to the time constant of the smoothing filter. The larger the smoothing, the larger the time constant of the filter. The following figure shows the step response for the various smoothing factors depending on the number of module cycles. QRQHN ZHDNN PHGLXPN VWURQJN 6WHSUHVSRQVH [ [ [ [ 0RGXOHF\FOHV Figure 8-5 Smoothing with AI 4xRTD/TC 2/3/4wire HF Interference frequency suppression With analog input modules, suppresses the disturbance caused by the frequency of the AC network used. The frequency of the AC network may interfere with measured values, particularly for measurements within low voltage ranges and when thermocouples are being used. This parameter is used to define the predominant power frequency of the system. Hardware interrupt limits If the high limit 1/2 or the low limit 1/2 is violated, the module triggers a hardware interrupt. WinCC Basic V13.0 System Manual, 02/2014 1059 Editing devices and networks 8.1 Configuring devices and networks Below are some examples for the selection of the limits 1 and 2. +LJKOLPLW +LJKOLPLW +LJKOLPLW +LJKOLPLW +LJKOLPLW +LJKOLPLW +LJKOLPLW /RZOLPLW +LJKOLPLW /RZOLPLW /RZOLPLW /RZOLPLW 0HDVXUHGYDOXH /RZOLPLW 0HDVXUHGYDOXH /RZOLPLW /RZOLPLW 0HDVXUHGYDOXH /RZOLPLW 0HDVXUHGYDOXH Low limit 1/2 Specify a threshold whose undershoot triggers a hardware interrupt. High limit 1/2 Specify a threshold whose overrange triggers a hardware interrupt. Potential group of the left module / new potential group Specifies whether the I/O module is located on a base unit with supply voltage feed (new potential group) or whether it is it located on a base unit without supply voltage feed (in which case it belongs to the potential group of the left module). Temperature coefficient (measuring type thermoresistor) The correction factor for the temperature coefficient ( value) defines the relative rate of change of the resistance of a specific material at a temperature rise of 1 . The temperature coefficient depends on the chemical composition of the material. In Europe, only one value is used per sensor type (default value). The further values facilitate a sensor-specific setting of the temperature coefficient and enhance accuracy. See also Special features of AI 4xRTD/TC 2-/3-/4-wire HF (Page 1061) 1060 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Special features of AI 4xRTD/TC 2-/3-/4-wire HF Use of Cu10 sensors Select "3-wire thermal resistor" and "Cu10" in the parameter assignment. Wire the Cu10 sensor using 3-wire connection technology. An automatic, internal compensation of the line resistance of the missing measuring line takes place during operation. Note To ensure optimum line compensation for Cu10, please note the following: The sum of cable resistance and measuring resistance must not exceed 31 . Cable resistance should not exceed 8 if you want to use the temperature range up to over 312 C. Example: A 200 m long copper cable with 0.5 mm2 core cross-section has approx. 7 . A lower cross-section reduces the permissible cable length accordingly. Use of PTC resistors PTCs are suitable for temperature monitoring of or as thermal protective equipment for complex drives or transformer windings. Select "2-wire resistor" and "PTC" in the parameter assignment. Connect the PTC using 2-wire technology. Use type A PTC resistors (PTC thermistors) in accordance with DIN/VDE 0660, Part 302. If the "Over-/underflow" diagnostics is enabled, a "low limit violation" diagnostics which shows a short circuit is generated for resistance values < 18 . Sensor data on PTC resistance: Table 8-77 Use of PTC resistors Property Switching points Technical specifications Note Reaction to rising temperature < 550 Normal range: SIMATIC S7: bit 0 = "0", bit 2 = "0" (in the PII) 550 to 1650 Prewarning range: SIMATIC S7: bit 0 = "0", bit 2 = "1" (in the PII) < 1650 Response range: SIMATIC S7: bit 0 = "1", bit 2 = "0" (in the PII) Reaction to falling temperature < 750 Response range: SIMATIC S7: bit 0 = "1", bit 2 = "0" (in the PII) 750 to 540 Prewarning range: SIMATIC S7: bit 0 = "0", bit 2 = "1" (in the PII) WinCC Basic V13.0 System Manual, 02/2014 1061 Editing devices and networks 8.1 Configuring devices and networks Property Technical specifications < 540 Note Normal range: SIMATIC S7: bit 0 = "0", bit 2 = "0" (in the PII) (TNF-5) C max. 550 (TNF+5) C min. 1330 (TNF+15) C min. 4000 Measuring voltage max. 7.5 V RRT= rated response temperature Voltage on the PTC Assignment in the process image inputs (PII) with SIMATIC S7 (%[ PHDVXUHGUHVLVWDQFHUHVSRQVHYDOXH PHDVXUHGUHVLVWDQFH!UHVSRQVHYDOXH %HWZHHQSUHZDUQLQJWKUHVKROGDQGUHVSRQVHYDOXH (%[ 6KRUWFLUFXLW Figure 8-6 Assignment in the process image inputs (PII) Notes on programming Note Only the bits 0+2 are relevant for the evaluation in the process image inputs. You can use the bits 0+2 to monitor the temperature, for example, of a motor. The bits 0+2 in the process image inputs have no latching function. When you are assigning parameters, take into consideration that a motor, for example, starts up in a controlled manner (via an acknowledgment). Bits 0+2 can never be set simultaneously, but are instead set consecutively. For safety reasons, always evaluate the diagnostic entries of the AI 4xRTD/TC 2-/3-/4wire HF, as no measurement is possible if I/O modules are unplugged, if the supply voltage of the I/O module has failed, or if there is a wire break or short circuit of the measuring lines. 1062 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Example The following diagram shows the temperature variation and the associated switching points. 5>@ 1RUPDO UDQJH 3UHZDUQLQJ UDQJH $GUHVVDEOHUDQJH 3UHZDUQLQJUDQJH 1RUPDO UDQJH 6KRUW FLUFXLW 7>r&@ See also Parameters of the analog input modules (Page 1058) ET 200MP ET 200MP distributed I/O system Definition The ET 200MP distributed I/O system is a scalable and flexible distributed I/O system for connection of process signals to a central controller via a field bus. Application area The ET 200MP is a multi-functional distributed I/O system for various fields of application. The scalable design allows you to configure the system exactly to the specific requirements on location. The ET 200MP complies with IP 20 degree of protection and is intended for installation in a control cabinet. WinCC Basic V13.0 System Manual, 02/2014 1063 Editing devices and networks 8.1 Configuring devices and networks Structure The ET 200MP is installed on a mounting rail and comprises: An interface module that communicates with all IO controllers conforming to the PROFINET standard IEC 61158 Up to 30 modules (power supply modules and I/O modules from the S7-1500 I/O range) can be inserted to the right of the interface module. If you insert a power supply module to the left of the interface module, this yields a possible maximum configuration of 32 modules in total. The number of insertable I/O modules is limited by their power requirements. Slot rules Slot 0: Power supply module (optional) Slot 1: Interface module Slot 2 to 31: I/O modules or power supply modules Interface module parameters Supply voltage L+ connected Parameter "Supply voltage L+ connected" This parameter influences the diagnostics and the checking of the power budget. Diagnostics of the ET 200MP: If the actual configuration does not conform to the setpoint configuration with regard to the supply voltage of the interface module, the interface module generates a diagnostic alarm. Example: You have deactivated the "Supply voltage L+ connected" option, but you have connected the supply voltage in the actual configuration. Power budget check during configuration: The power budget changes in accordance with the parameter setting: Either the interface module feeds power into the backplane bus or it draws power from the backplane bus. The default ("Supply voltage L+ connected" option is activated) means that the front of the interface module is supplied with 24 V DC and the power is stored in the backplane bus. If the "Supply voltage L+ connected" option is deactivated, the interface module may not be supplied with 24 V DC on the front. 1064 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks In this case, insert a power supply unit (PS) on the left next to the interface module that supplies the interface module and the modules to the right of the interface module. Note We recommend that you always supply the interface module on the front side with 24 V DC. If a system power supply unit (PS) is inserted and connected additionally before or on the left next to the interface module, both the power from the system power supply unit (PS) as well as the power from the integrated power supply of the interface module are then available to the configuration. In this case, you do not have to change the default setting of the parameter. Configuration control Operating principle Configuration control allows you to operate various real configurations (options) with a single configuration of the ET 200MP distributed I/O device. Configuration control provides you with the option of configuring the ET 200MP distributed I/ O device with its maximum configuration and nevertheless operating it with missing modules. If missing modules are retrofitted later, no new configuration is required and the hardware configuration does not have to be reloaded either. Using control data records, which are transferred to the interface module in the user program, you define a current preset configuration. We distinguish between the following procedures: Configuring configuration control without empty slots (option handling) Expanding configuration (step-by-step commissioning) Requirement Enable the Configuration control" option of the interface module ("Configuration control" area). Control takes place with control data record 196 to specify the required configuration. Configuration control is not ready for operation without a control data record. You transfer the control data record with the instruction WRREC in the user program. Addressing the interface module using the hardware identifier To transfer data record 196 with the instruction WRREC, you must enter the hardware identifier of the interface module as input parameter for the instruction. The system constant of this hardware identifier is, for example, "IO-Device._V2 [Head]". The system constants of a selected device are, for example, displayed in the network view in the "System constants" tab. Use the associated value for addressing. WinCC Basic V13.0 System Manual, 02/2014 1065 Editing devices and networks 8.1 Configuring devices and networks More information and examples For information on the rules for configuration control, the structure of the control data record and the behavior during operation, as well as examples of the structure of the control data record for various configurations, refer to the IM 155-5 PN ST interface module manual (http:// support.automation.siemens.com/WW/view/en/67295970). Input module parameters Parameters of the analog input modules Missing supply voltage L+ Enabling of the diagnostics for missing or insufficient supply voltage L+. Wire break Enabling of the diagnostics if the module has no current flow or the current is too weak for the measurement at the corresponding configured input or the applied voltage is too low. Current limit for wire break diagnostics Threshold at which a wire break is reported. The value can be set to 1.185 mA or 3.6 mA, depending on the sensor used. Overflow Enabling of the diagnostics if the measured value exceeds the overrange. Underflow Enabling of the diagnostics if the measured value undershoots the underrange. Common mode error Enable diagnostics if the valid common mode voltage is exceeded. Reference channel error (only for AI 8xU/I/RTD/TC ST) Enable diagnostics on error at the temperature compensation channel, e.g. wire break. Dynamic reference temperature compensation type is configured and no reference temperature has been transferred to the module yet. 1066 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Temperature coefficient The temperature coefficient depends on the chemical composition of the material. In Europe, only one value is used per sensor type (default value). The correction factor for the temperature coefficient ( value) specifies how much the resistance of a certain material changes when the temperature is raised by 1 C. The further values facilitate a sensor-specific setting of the temperature coefficient and enhance accuracy. Interference frequency suppression At analog input modules, this suppresses interference caused by the frequency of AC mains. The frequency of the AC network may interfere with measured values, particularly for measurements within low voltage ranges and when thermocouples are being used. With this parameter, you define the mains frequency in your system. Smoothing The individual measured values are smoothed using filtering. Smoothing can be set in 4 stages for the analog input modules AI 8xU/I/RTD/TC ST and AI 8xU/I HS. Smoothing time = number of module cycles (k) x cycle time of the module. The figure below shows the number of module cycles after which the smoothed analog value is almost 100%, depending on the set smoothing. Is valid for each signal change at the analog input. 6LJQDOFKDQJHLQ SHUFHQWDJH 1 3 4 2 WinCC Basic V13.0 System Manual, 02/2014 0RGXOHF\FOHV N None (k = 1) Weak (k = 4) Medium (k = 16) Strong (k = 32) 1067 Editing devices and networks 8.1 Configuring devices and networks Reference junction (only for AI 8xU/I/RTD/TC ST) The following settings can be configured for the reference junction parameter: Table 8-78 Possible parameter assignments for the reference junction parameter Setting Description Fixed reference temperature The reference junction temperature is configured and stored in the module as a fixed value. Dynamic reference temperature The reference junction temperature is transferred in the user program from the CPU to the module by data records 192 to 199 using the WRREC (SFB 53) instruction. Internal reference junction The reference junction temperature is determined using an integrated sensor of the module. Reference channel of the module The reference junction temperature is determined using an external resistance thermometer (RTD) at the reference channel (COMP) of the module. Note Fixed reference temperature During parameter assignment of a thermocouple Type B, only the setting "Fixed reference temperature" with a temperature of 0 C is possible. Enable hardware interrupt 1 or 2 Enable a hardware interrupt if high limit 1 or 2 is exceeded, or low limit 1 or 2 is violated. Low limit 1 or 2 Specifies the low limit threshold that triggers hardware interrupt 1 or 2. High limit 1 or 2 Specifies the high limit threshold that triggers hardware interrupt 1 or 2. Temperature compensation for thermocouples Introduction You have several options of measuring the reference junction temperature in order to obtain an absolute temperature value as a function of the temperature difference between the reference junction and the measuring point. 1068 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks You can use various compensation options depending on the required location of the reference junction. Note During parameter assignment of a thermocouple Type B, only the setting "Fixed reference temperature" with a temperature of 0 C is possible. Options of compensating for the reference junction temperature Compensation options Explanation Application case Internal reference junction With this compensation, the reference junction temperature is determined using an integrated sensor of the module. For the connection, you use compensating lines matching the thermocouple material. Procedure If the reference junction temperature and the module temperature are identical in your system, you may also use lines made from a different material. Connect the thermocouple to the I/O module directly or with compensating lines. Reference channel of the module The reference junction temperature is determined using an external resistance thermometer (RTD). Procedure Connect the thermocouple to the supply lines at the reference junction, either directly or with compensating lines. You connect the supply lines to the appropriate terminals of the module. Connect the resistance thermometer (RTD) to the reference channel of the module. The resistance thermometer (RTD) must be placed in the area of the reference junction. WinCC Basic V13.0 System Manual, 02/2014 You want to measure the temperature directly at the reference junction. The measured temperatures of all channels that you have configured for this compensation type is corrected automatically by the temperature value of the reference junction. You can use inexpensive lines, e.g., copper lines, from the reference junction to the module. 1069 Editing devices and networks 8.1 Configuring devices and networks Compensation options Explanation Application case Dynamic reference temperature The temperature of the reference junction is determined via a module. This temperature value is transferred to other modules via a data record in the user program. You use multiple modules at the reference junction and can therefore compensate all channels using a common temperature value. Procedure You require only one resistance thermometer (RTD) to acquire the temperature value. Connect the resistance thermometer (RTD) for the reference junction to any channel. The reference junction temperature is communicated from the CPU to the module by data records 192 to 199 using the WRREC instruction. You can use inexpensive lines, e.g., copper lines, from the reference junction to the module. Fixed reference temperature The reference junction temperature is stored in the module as a fixed value. You keep the reference junction temperature constant and know the temperature value. Procedure Connect the thermocouple to the supply lines at the reference junction, either directly or with compensating lines. You connect the supply lines to the appropriate terminals of the module. You can use inexpensive lines, e.g., copper lines, from the reference junction to the module. When configuring the module, specify a fixed temperature value for the reference junction (e.g. 20 C). Output module parameters Parameters of the analog output modules Missing supply voltage L+ Enabling of the diagnostics, with missing or too little supply voltage L+. Short-circuit to ground Enabling of the diagnostics if a short-circuit of the actuator supply to ground occurs. Wire break Enabling diagnostics if the line to the encoder is interrupted. Overflow Enabling of the diagnostics if the measured value exceeds the overflow range. Underflow Enabling of the diagnostics if the measured value falls below the underflow range. 1070 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Reaction to CPU STOP Determines the reaction of the output to the CPU going into STOP state. Substitute value The substitute values are values that the outputs (the output) issue in the event of a CPU STOP. ET 200M Configuring an ET 200M Introduction For the ET 200M series, you can find a wide range of modules in the hardware catalog under "Distributed I/O". Configuration and parameter assignment Information on configuration and parameter assignment can be found in the following sections. ET 200M configuration Definition The distributed IO device, ET 200M, is a modular DP slave with an IP 20 degree of protection. The ET 200M has the configuration technology of the S7300 automation system and consists of an IM 153x and I/O modules of the S7300. ET 200M supports communication with: all DP masters compliant with IEC 61784-1:2002 Ed1 CP 3/1 all IO controllers compliant with IEC 61158 WinCC Basic V13.0 System Manual, 02/2014 1071 Editing devices and networks 8.1 Configuring devices and networks Configuration of the ET 200M (example) 1 2 3 Power supply module PS 307 Interface module IM 153x up to 12 I/O modules (SM / FM / CP) Configuration of the 'Module replacement during operation' function Introduction The ET 200M supports the "Replace modules during operation" function and the associated pull/plug interrupt. The "Replace modules during operation" function makes it possible for you to pull modules from or plug modules into the ET 200M rack during operation. Requirement You have configured an interface module that supports replacing modules during operation. (as of IM 153-1, order no. 153-1AA02-0XB0). In addition, the configured CPU must also support the function, e.g. for PROFIBUS an S7-400 with DP interface. You must use the active backplane bus (bus rail with slots) for the hardware configuration. The conventional profile rail with bus connectors between the modules does not support this function. Configuring If the configuration requirements have been met, the "Replace modules during operation" parameter is available for selection in the inspector window's "Module parameters" area. Below this parameter, a table for the configured modules is displayed, which shows the required active bus modules for the hardware configuration. For a PROFIBUS configuration, the "Startup if preset configuration does not match actual configuration" option is displayed. This option is automatically enabled if "Replace modules during operation" is enabled. 1072 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Configuring HART variables Introduction Numerous HART field devices make available additional measured quantities (e.g. sensor temperature). These can be read if they are set accordingly in the field device configuration. Using the HART variables. it is possible to apply the set measured values directly from the field device into the I/O area of your automation system. Regardless of the number of configured channels, a maximum of 8 HART variables can be assigned for HART modules and no more than 4 HART variables per channel. You assign the HART variables to a channel in the properties for the module ("HART variable settings" area). Requirement The HART module is plugged into an ET 200 M (as of IM 153-2, 6ES7 153-2BA02-0AB0). Address assignment The HART module occupies 16 input/output bytes. If you configure HART variables, the module occupies an additional 5 bytes for each HART variable. If you use all 8 HART variables, the HART input module occupies a total of 56 input/output bytes (16 bytes + 8 x 5 bytes = 56 bytes). The "None" configuration occupies no additional input bytes. Configuration of HART variables You can configure up to 4 HART variables for a channel PV (Primary Variable) SV (Secondary Variable) TV (Tertiary Variable) QV (Quaternary) CiR is a placeholder that reserves the address space for a HART variable. You must configure the HART variables you are not using with the "None" parameter. Configuration of HART variables The HART variables are structured as follows: E\WHVRI+$57GDWD WinCC Basic V13.0 System Manual, 02/2014 E\WH4& 1073 Editing devices and networks 8.1 Configuring devices and networks Structure of the "Quality-Code" byte The Quality-Code (QC) can assume the following values: Quality-Code (QC) Meaning 0x4C or 0 Initialization: 0 value of IM and 4C of module 0x18 Communication cancelled / no communication 0x0C Fault in HART device 0x47 HART device is busy 0x84 OK "Configuration changed" 0x80 OK See also Documentation for HART analog modules (http://support.automation.siemens.com/WW/view/ en/22063748) Signal modules for process automation Fundamentals Introduction Signal modules for the process automation are S7-300 models, such as SM 321; DI 16xNAMUR or SM 322; DO 16x24VDC/0.5A. They are being operated in a DP slave (IM 153-2). Unlike standard modules, they offer the following additional technical functions, such as pulse extension and chatter monitoring. See also Changeover contact (Page 1074) Technological parameters (Page 1075) Changeover contact "Changeover contact" sensor type If the digital inputs of a channel group are configured as "changeover contacts", the module runs diagnostics for the changeover contact sensor type for this channel group. 1074 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Changeover contact A changeover contact is an auxiliary switch with only one moving switch element with one close setting each for closed and open switching device. Remember the following rule: Always connect a normally open contact to the "even" channel Always connect a normally closed contact to the "odd" channel. The tolerated switchover time between the two channels is fixed at 300 ms. If the result of the check is negative, then the module identifies the value status of the normally open channel as "invalid" the module generates a diagnostic entry for the normally open channel triggers a diagnostic interrupt (if diagnostic interrupts have been enabled) The digital input signal and the value status are updated only for the normally open channel. For the normally closed channel, the digital input signal is set permanently to "zero" and the value status to "invalid" since this channel is used only to check the sensor. Diagnostics depends on the "Selection" parameter (of the sensor). You should also note the special features of diagnostics with the changeover contact sensor type in the "Signal Modules for Process Automation" manual. See also Documentation on modules for process automation (http://support.automation.siemens.com/ WW/view/de/7215812/0/en) Technological parameters Pulse extension and flutter monitoring Pulse extension is a function for changing a digital input signal. A pulse at a digital input is extended to at least the length set in the parameters. If the input pulse is already longer than the specified length, it is not changed. If you want the pulse to be extended, click in the box to select the time. If you do not want the pulses to be extended, select the "---" entry. Flutter monitoring is a process control function for digital input signals. It detects and reports signal changes that are unexpected in process control, for example when an input signal fluctuates too often between "0" and "1". Flutter monitoring is possible only when group diagnostics has also been enabled for this input. Monitoring window and number of signal changes Flutter monitoring works with aid of the two parameters Monitoring window and Number of signal changes. WinCC Basic V13.0 System Manual, 02/2014 1075 Editing devices and networks 8.1 Configuring devices and networks The first time the signal changes, the time set as the monitoring window is started. If the signal changes more often during this time than allowed by the number of signal changes parameter, this is signaled as a flutter error. If no flutter error is detected during the monitoring window time, the monitoring window can be restarted at the next signal change. Note If you set pulse extension for an input channel, this also affects the flutter monitoring enabled for this channel. The "extended pulse" signal is the input signal for the flutter monitoring. You should therefore make sure that the values set for pulse extension and flutter monitoring are compatible with each other. See also Documentation on modules for process automation (http://support.automation.siemens.com/ WW/view/de/7215812/0/en) IQ Sense module Properties of 8 IQ-SENSE Properties The 8 IQ-SENSE module has the following properties: Connection of sensors with IQ-SENSE(R), photoelectric proximity switches: for example, reflex sensors, diffuse sensors, and laser sensors. It can be used centrally in an S7-300 or distributed in an ET 200M. You can connect up to 8 sensors to every module. Each sensor requires a two-wire cable. Function reserve that can be assigned parameters. Time functions, switching hysteresis, synchronous mode that can be assigned parameters Sensitivity and distance values can be specified (IntelliTeach using the "IQ-SENSE Opto" FB) Teach-in Sensors can be removed and inserted during operation (automatic reassignment of parameters) Anti-interference group Only for optical IQ Sense devices (IQ profile ID 1). For IQ Sense devices with IQ profile ID 128 (ultrasound), see "Multiplex/synchronous mode" under the channel-specific parameters. Prevention of interference (e.g., scattered light) by assigning an anti-interference group. This means: 1076 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Anti-interference group: None (= default) Optical sensors on one or more modules can mutually influence each other when unfavorably arranged. Anti-interference group: 3 or 4 Optical sensors on the same module with anti-interference group 3 or 4 cannot mutually influence each other. Similarly, optical sensors on different modules with anti-interference group 3 or 4 cannot mutually influence each other. You need not maintain minimum clearance between the IQ Sense devices and can, for example, align two retroreflective sensors on a single reflector. Operating principle The diagram below explains the functioning of the anti-interference group parameter: 6ORW [,46HQVH QRQH $QWLLQWHUIHUHQFH JURXS SDUDPHWHU Mutual interference is only possible between the optical sensors of the modules in slot 5, 6, 7 and 9 because they are in the same anti-interference group 3 or "None" is set. Note Sensors in the same anti-interference group must be installed to maintain the minimum clearance (see sensor package insert) and to prevent mutual interference. Encoder type This parameter is used to set the sensor type per channel: Reflex sensor or Diffuse sensor or Disabled WinCC Basic V13.0 System Manual, 02/2014 1077 Editing devices and networks 8.1 Configuring devices and networks Diffuse sensor Table 8-79 Diffuse sensor Diffuse sensor Object Transmitter Circuit state 0: No object detected, which means the object is not in the beam. The receiver does not see any light. Receiver Transmitter Circuit state 1: Object detected, which means the object is in the beam. The receiver does not see any light. Receiver Reflex sensor Table 8-80 Reflex sensor Reflex sensor Transmitter Receiver Transmitter Receiver Object Circuit state 0: No object detected, which means the object is not in the beam. The receiver sees light. Circuit state 1: Object detected, which means the object is in the beam. The receiver does not see any light. Switching hysteresis Faults with the diffuse sensor or in the production process can result in signal wobbles. The measured value then changes the switching threshold by 100 % (object detected - object not detected). You can prevent this switching threshold wobble using the switching hysteresis parameter. This will ensure a stable output signal on the sensor. You can assigned parameters to 5 %/10 %/20 %/50 % for switching hysteresis. Requirements You can only set the switching hysteresis parameter for diffuse sensors with background fadeout. 1078 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks Operating principle 5HFHLYLQJOHYHO 6ZLWFKLQJ WKUHVKROG 'LIIHUHQWLDOWUDYHO 7LPH W 6ZLWFKLQJRXWSXWRQVHQVRU Figure 8-7 7LPH W Switching hysteresis parameter Time function,time value These parameters can be used to set the electronic module for its specific application. WinCC Basic V13.0 System Manual, 02/2014 1079 Editing devices and networks 8.1 Configuring devices and networks Operating principle 7LPHU 1RQH GHIDXOW 6ZLWFKLQJVWDWXV &XUYH 5HVHWGHOD\HG 7 7 3LFNXSGHOD\HG 7 7 3LFNXSDQG UHVHWWLQJGHOD\ 7 7 7 0RPHQWDU\ LPSXOVH 6ZLWFKLQJVWDWH RQVHQVRU 7 7 7 2EMHFWGHWHFWHG 2EMHFWQRWGHWHFWHG 7 WLPHYDOXHSDUDPHWHU Figure 8-8 Time functions, time values parameters Multiplex/synchronous mode For the prevention of mutual influence between IQ Sense ultrasound devices in spatial proximity (devices with IQ profile ID 128), use the "Multiplex/synchronous operation" parameter. Settings for the multiplex/synchronous mode parameter Disabled: Mutual influence between IQ Sense ultrasound sensors in spatial proximity is possible (default). The cycle time is determined by the IQ Sense ultrasound sensor. Multiplex: The IQ Sense ultrasound sensors determine the process value (distance) one after another, preventing them from affecting one another. The cycle time here is the sum of the configured synchronous cycle times of the IQ Sense ultrasound sensors that are to be multiplexed. Synchronization: The IQ Sense ultrasound sensors determine the process value (distance) at exactly the same time, preventing them from affecting one another. The cycle time here 1080 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks corresponds to the greatest configured synchronous cycle time from among the IQ Sense ultrasound sensors that are to be synchronized. You can, for example, use synchronous operation for a curtain function in which several IQ Sense ultrasound sensors aligned in parallel share a single extended detection area. The sensors simultaneously emit an ultrasound impulse. When an object enters the detection area, the sensor nearest to the object receives the echo most quickly. The object can therefore not only be detected, it can be located as well. AFI value Using the AFI value (application series identifier, as defined in the ISO 15693-3 international standard), transponders can be selected for different applications. Only transponders whose AFI value coincides with the value set on the sensor are processed. If a transponder has the AFI value "0", it can be identified and processed regardless of the AFI value of the sensor. This parameter is only important if it is supported by the ident system, otherwise any value (normally "0") may be assigned. Transponder type Depending on the type of the transponder, you must configure whether it is an ISO transponder or a vendor-specific type. For transponders in accordance with international standard ISO 15693, the value "1" should be selected; for all other types "0" is set. Based on this setting, one of the two possible air interface drivers is selected in the sensor. This parameter is only important if it is supported by the ID system, otherwise any value (normally "0") may be assigned. ET 200S Configuring an ET 200S Introduction For the ET 200S series, you can find a wide range of modules in the hardware catalog under "Distributed I/O". Assigning parameters For information on configuration and parameter assignment, refer to "See also". WinCC Basic V13.0 System Manual, 02/2014 1081 Editing devices and networks 8.1 Configuring devices and networks Frequency converters Use of the frequency converter Frequency converters The frequency converter ICU24 and ICU24F ( as fail-safe version) are modular design frequency converters that are completely embedded in the distributed I/O system ET 200S. For parameterization of both modules, please see the following. Message frame The message frame number and the operating mode of the module are only displayed and cannot be modified. Application ID You indicate the saved parameters in the frequency converter as a whole with the application ID. Enter an application ID from the value range 0 to 65535. During startup (or pull/plug), this ID is compared with the application ID stored on the converter. Converters that work with identical applications are usually also identically parameterized and should be identified with the same application ID. Converters with the same application ID may be exchanged between each other. Copying of the complete parameterization of a converter to another converter, for example, via an MMC, is only accepted, if both have the same application ID. Converters that work with different applications and are parameterized differently must be identified by different application IDs. This prevents a converter with unsuitable parameterization from starting on an incorrect slot, i.e. on the wrong application. This also prevents the parameterization that is saved in the converter from being accidently overwritten with any parameteriation that is stored on an MMC. Enable diagnostic interrupt You can enable the diagnostic interrupt for the frequency converter. If diagnostic interrupt is enabled, an OB 82 must be available in a CPU to process the diagnostic events. See also Documentation for the frequency converter (http://support.automation.siemens.com/WW/view/ en/26291825/0/en) 1082 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.1 Configuring devices and networks ET 200pro Use of the frequency converter Frequency converters The frequency converters ET 200pro FC and ET 200pro F-FC (as fail-safe version) are modularly design frequency converters that are completely embedded in the distributed I/O system ET 200pro. The following section describes how to configure the two modules. Message frame The message frame number and the operating mode of the module are only displayed and cannot be modified. Application ID You indicate the saved parameters in the frequency converter as a whole with the application ID. Enter an application ID from the value range 0 to 65535. During startup (or pull/plug), this ID is compared with the application ID stored on the converter. Converters that work with identical applications are usually also identically configured and should be identified with the same application ID. Converters with the same application ID may be exchanged between each other. Copying of the complete configuration of a converter to another converter, for example, via an MMC, is only applied, if both have the same application ID. Converters that work with different applications and are configured differently must be identified by different application IDs. This prevents a converter with unsuitable configuration from starting on an incorrect slot, in other words on the wrong application. This also prevents the configuration that is saved in the converter from being accidently overwritten with any configuration that is stored on an MMC. Enable diagnostic interrupt You can enable the diagnostic interrupt for the frequency converter. If diagnostic interrupt is enabled, an OB 82 must be available in a CPU to process the diagnostic events. 8.1.6.4 IPv6 configuration IPv6 protocol The Internet Protocol version 6 - called IPv6 below - extends the Internet Protocol version 4 (IPv4) that is used predominantly at the current time. WinCC Basic V13.0 System Manual, 02/2014 1083 Editing devices and networks 8.1 Configuring devices and networks Address format IPv6: Notation IPv6 addresses consist of 8 fields each with four-character hexadecimal numbers (128 bits in total). The fields are separated by a colon. Example: fd00:ffff:ffff:ffff:ffff:ffff:2f33:8f21 Rules / simplifications: Leading zeros within a field can be omitted. Example: fd01:0:ffff::2d12:7d23 If one or more fields have the value 0, a shortened notation is possible. The address fd00:0:0:0:0:0:0:0:8f21 can also be shortened and written as follows: fd00::8f21 To ensure uniqueness, this shortened form can only be used once within the entire address. Decimal notation with periods The last 2 fields or 4 bytes can be written in the normal decimal notation with periods. Example: The IPv6 address fd00::ffff.125.1.0.1 is equivalent to fd00::ffff:7d01:1 Entry and appearance The entry of IPv6 addresses is possible in the notations described above. IPv6 addresses are always shown in the same notation in which they were entered. See also IPv6 with the CP 1543-1 (Page 1084) IPv6 with the CP 1543-1 Use of IPv6 with the CP 1543-1 The CP supports the Internet Protocol version 4 (IPv4) for all IP services The additional specification of addresses in IPv6 format can be used with the CP for the following services and applications: FETCH/WRITE Direct write/read access by PC stations, SIMATIC S5 or third-party devices FTP client FTP access from the S7-1500 CPU to an FTP server with the program block FTP_CMD FTP server FTP access from an FTP client to data areas of the S7-1500 CPU SNMP Data query using MIB objects according to SNMP E-mail Data transfer from the S7-1500 CPU using the program block T_Mail 1084 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.2 Device and network diagnostics 8.2 Device and network diagnostics 8.2.1 Hardware diagnostics 8.2.1.1 Overview of hardware diagnostics Principal methods of hardware diagnostics Principal methods of hardware diagnostics Hardware diagnostics can be performed as follows: Using the Online and Diagnostics view Using the "Online Tools" task card Using the "Diagnostics > Device Info" area of the Inspector window Using diagnostics icons, for example, in the device view and the project tree Structure of the Online and Diagnostics view The Online and Diagnostics view consists of two windows alongside each other: The left window shows a tree structure with folders and - when you open the folder - groups. The right window contains detailed information on the selected folder or selected group. The "Online access" group and the "Diagnostics" and "Functions" folders are located here: "Online access" group: Displays whether or not there is currently an online connection with the associated target. In addition, you can establish or disconnect the online connection. "Diagnostics": Contains several diagnostics groups for the selected module. "Functions": Contains several groups, in which you can make settings for the selected module or issue commands to the module. Function and structure of the "Online Tools" task card For modules with their own operating mode (such as CPUs), the "Online tools" task card allows you to read current diagnostics information and commands to the module. If you selected a module without its own operating mode or if you selected several modules before activation of the "Online Tools" task card, the task card relates to the relevant CPU. The "Online Tools" task card consists of the following panes: WinCC Basic V13.0 System Manual, 02/2014 1085 Editing devices and networks 8.2 Device and network diagnostics CPU control panel Cycle time Memory Note A pane is filled with content only if the module controls the associated functions and an online connection exists. If there is no online connection to the respective module, the display "No online connection" appears in blue. If an existing online connection was disconnected, then "This target is not available" will be displayed. Structure or the "Diagnostics" tab of the Inspector window The "Diagnostics" tab of the Inspector window itself consists of several tabs: Of these tabs, the following is relevant for the hardware diagnostics. Device information This tab relates to all CPUs of the project to which the online connection is established. Alarms are reported here if one or more CPUs are defective or are not in RUN mode. See also Basics on task cards (Page 205) Inspector window (Page 203) Determination of which of the devices that are connected online are defective Overview of the defective devices In the "Diagnostics > Device Info" area of the Inspector window you will obtain an overview of the defective devices that are or were connected online. The "Diagnostics> Device Info" area of the Inspector window consists of the following elements: Header line with the number of defective devices Table with detailed information on each defective device If you originate the establishment of an online connection to a device which is not reachable or reports one or more faults or is not in RUN mode, it will rank as defective. Structure of the table with detailed information on the defective devices The table consists of the following columns: Online status: Contains the online status as a diagnostic symbol and in words Operating mode: Contains the operating mode as a symbol and in words Device / module: Name of the affected device or the affected module 1086 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.2 Device and network diagnostics Message: explains the entry of the previous column Details: The link opens the online and diagnostics view for the device, and places it in the foreground. If an online connection does not exist any longer, the link will open the connection establishment dialog. Help: The link supplies further information on the defect that has occurred. See also Displaying diagnostics status and comparison status using icons (Page 1087) Displaying diagnostics status and comparison status using icons Determining diagnostics status online and displaying using icons When the online connection to a device is established, the diagnostics status of the device and, if applicable, its lower-level components is determined. The operating state of the device is also determined, where applicable. The following is a description of which icons are displayed in specific views. WinCC Basic V13.0 System Manual, 02/2014 1087 Editing devices and networks 8.2 Device and network diagnostics Device view - The associated diagnostic icon is displayed for every hardware component (except the signal board on the CPU). - For a hardware component with lower-level components, if there is a hardware error in at least one lower-level component, the diagnostic icon appears as follows: The hardware component's diagnostic icon has a pale appearance and the diagnostic icon "Hardware error in lower-level component" is also shown in the lower right corner. - For hardware components with their own operating state, the operating state icon is also displayed to the left of or above the diagnostic icon. - The following applies to modules or submodules of a shared device with an S7-1500 CPU: No diagnostic icons are displayed (due to the configuration as GSDML device). Device overview - The associated diagnostic icon is displayed for every hardware component. - For a hardware component with lower-level components, if there is a hardware error in at least one lower-level component, the diagnostic icon appears as follows: The hardware component's diagnostic icon has a pale appearance and the diagnostic icon "Hardware error in lower-level component" is also shown in the lower right corner. - The following applies to modules or submodules of a shared device with an S7-1500 CPU: For modules assigned to the CPU, the associated diagnostic icon is displayed (modules that are not assigned do not receive a diagnostic icon). The associated diagnostic icon is displayed for plug-in submodules of an assigned module (submodules that are not pluggable are not visible and therefore do not receive a diagnostic icon). Network view - The associated diagnostic icon is displayed for every device. - For a hardware component with lower-level components, if there is a hardware error in at least one lower-level component, the diagnostic icon appears as follows: The hardware component's diagnostic icon has a pale appearance and the diagnostic icon "Hardware error in lower-level component" is also shown in the lower right corner. - The following applies to modules or submodules of a shared device with an S7-1500 CPU: A diagnostic icon is displayed. It belongs to that part of the station that is assigned to the CPU. 1088 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.2 Device and network diagnostics Network overview - The associated diagnostic icon is displayed for every hardware component. - For a hardware component with lower-level components, if there is a hardware error in at least one lower-level component, the diagnostic icon appears as follows: The hardware component's diagnostic icon has a pale appearance and the diagnostic icon "Hardware error in lower-level component" is also shown in the lower right corner. - The following applies to modules or submodules of a shared device with an S7-1500 CPU: A diagnostic icon is displayed. It belongs to that part of the station that is assigned to the CPU. Topology view - The associated diagnostic icon is displayed for every device. - For a hardware component with lower-level components, if there is a hardware error in at least one lower-level component, the diagnostic icon appears as follows: The hardware component's diagnostic icon has a pale appearance and the diagnostic icon "Hardware error in lower-level component" is also shown in the lower right corner. - The associated diagnostic icon is displayed for every port. The meaning of the individual colors is described further below. - Each cable between two online ports is assigned the color associated with its diagnostics status. The color of the cable between two ports depends on the status of the individual ports: Color of the first port Color of the second port Color of the connecting cable green green green green gray gray green red red gray red red - The following applies to modules or submodules of a shared device with an S7-1500 CPU: A diagnostic icon is displayed. It belongs to that part of the station that is assigned to the CPU. Topological overview - The associated diagnostic icon is displayed for every hardware component. - For a hardware component with lower-level components, if there is a hardware error in at least one lower-level component, the diagnostic icon appears as follows: The hardware component's diagnostic icon has a pale appearance and the diagnostic icon "Hardware error in lower-level component" is also shown in the lower right corner. - The following applies to modules or submodules of a shared device with an S7-1500 CPU: A diagnostic icon is displayed. It belongs to that part of the station that is assigned to the CPU. WinCC Basic V13.0 System Manual, 02/2014 1089 Editing devices and networks 8.2 Device and network diagnostics Project tree - The associated diagnostic icon is displayed behind every hardware component. - For a hardware component with lower-level components (e.g., distributed I/O, Slave_1), if there is a hardware error in at least one lower-level component, the diagnostic icon appears as follows: The hardware component's diagnostic icon has a pale appearance and the diagnostic icon "Hardware error in lower-level component" is also shown in the lower right corner. - For hardware components with their own operating state, the operating state icon is also displayed in the top right corner of the diagnostic icon. - If forcing is active on a CPU, a red F is displayed at the left margin of the diagnostic icon. - The diagnostic icon "Hardware error in lower-level component" is displayed behind the "Local modules" folder when there is a hardware error in at least one of the associated modules. - The diagnostic icon "Hardware error in lower-level component" is displayed behind the "Distributed I/O" folder when there is a hardware error in at least one of the associated modules. - The diagnostic icon "Hardware error in lower-level component" is displayed behind the project folder when the "Hardware error in lower-level component" diagnostic icon is displayed behind at least one of the "Local modules" or "Distributed I/O" folders. - The following applies to modules or submodules of a shared device with an S7-1500 CPU: The associated diagnostic icon is displayed for modules assigned to the CPU (modules that are not assigned are grayed out and do not receive a diagnostic icon). The associated diagnostic icon is displayed for plug-in submodules of an assigned module (submodules that are not pluggable are not visible and therefore do not receive a diagnostic icon). Note If the diagnostic for a hardware component is "not reachable from the CPU", the diagnostic icon "Hardware error in lower-level component" is not additionally shown. Diagnostic icons for modules and devices The following table shows the available icons and their respective meaning. Icon Meaning The connection with a CPU is currently being established. The CPU is not reachable at the set address. The configured CPU and the CPU actually present are of incompatible types. On establishment of the online connection to a protected CPU, the password dialog was terminated without specification of the correct password. No fault 1090 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.2 Device and network diagnostics Icon Meaning Maintenance required Maintenance demanded Error The module or device is deactivated. The module or the device cannot be reached from the CPU (valid for modules and devices below a CPU). Diagnostics data are not available because the current online configuration data differ from the offline configuration data. The configured module or device and the module or device actually present are incompatible (valid for modules or devices under a CPU). The configured module does not support display of the diagnostics status (valid for modules under a CPU). The connection is established, but the module status has not yet been determined or is unknown. The configured module does not support display of the diagnostics status. Hardware error in lower-level component: A hardware error is present in at least one lower-level hardware component. (occurs as a separate icon only in the project tree) Note Some modules, for example, the FM 450-1, are only indicated as having a problem in the case of an error if you have enabled the diagnostic interrupt when assigning the module property parameters. Icons for the comparison status The diagnostic icons can be combined at the bottom right with additional smaller icons that indicate the result of the online/offline comparison. The following table shows the available comparison icons and their meaning. Icon Meaning Hardware error in lower-level component: The online and offline versions differ (only in the project tree) in at least one lower-level hardware component. Software error in lower-level component: The online and offline versions differ (only in the project tree) in at least one lower-level software component. Online and offline versions of the object are different Object only exists online Object only exists offline Online and offline versions of the object are the same WinCC Basic V13.0 System Manual, 02/2014 1091 Editing devices and networks 8.2 Device and network diagnostics Note If both a comparison icon and the "Error in lower-level component" diagnostic icon are to be displayed at the bottom right in the device view, the following rule applies: The diagnostic icon for the lower-level hardware component has a higher priority than the comparison icon. This means that a comparison icon is only displayed if the lower-level hardware components have no errors. Display of software errors in the project tree The associated comparison icon is shown behind each block. Behind each folder, under which exclusively blocks are contained, the diagnostic icon "Software error in lower-level component" is displayed when there is a software error in at least one of the associated blocks. For a hardware component with lower-level software components, if there is no hardware error and there is an error in at least one lower-level software component, the diagnostic icon appears as follows: The hardware component's diagnostic icon has a pale appearance and the diagnostic icon "Software error in lower-level component" is also shown in the lower right corner. Combined diagnostics and comparison icons The following table shows examples of icons that are displayed in the diagnostics icon. Icon Meaning Folder contains objects whose online and offline versions differ (only in the project tree) Object only exists online Operating state icons for CPUs and CPs The following table shows the available icons and their respective operating states. Icon Operating state RUN STOP STARTUP HOLD DEFECTIVE 1092 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.2 Device and network diagnostics Icon Operating state Unknown operating state The configured module does not support display of the operating state. Note If forcing is active on a CPU, a red F is displayed on a pink background at the bottom right of the operating state icon. Color marking of ports and Ethernet cables The following table shows the available colors and their respective meaning. Color Meaning No fault or maintenance required Maintenance demanded Communication error or topological error no diagnostic capability Start online and diagnostics view Overview of possible ways of starting the Online and Diagnostics view You can start the Online and Diagnostics view of a module to be diagnosed at the following locations: Overview Project tree Device view Device overview Network view Network overview Topology view In the following, examples are used to show how to proceed. WinCC Basic V13.0 System Manual, 02/2014 1093 Editing devices and networks 8.2 Device and network diagnostics Requirement The project with the module to be diagnosed is open. Note This requirement does not apply if you call the online and diagnostics view from the project tree after you have identified the accessible devices. Procedure To start the online and diagnostics view of a module, follow these steps: 1. In the project tree, open the respective device folder. 2. Double click on "Online & Diagnostics". Or: 1. In the project tree, select the respective device folder. 2. Select the "Online & Diagnostics" command in the shortcut menu or the "Online" main menu. Or: 1. In the project tree, open the "Online access" folder. 2. Open the folder for the interface with which you want to establish the online connection. 3. Double click on "Show/Update accessible devices". 4. Select the module to be diagnosed. 5. Select the "Online & Diagnostics" command in the shortcut menu or the "Online" main menu. Or: 1. In the project tree, open the "Local modules" folder. 2. Select the respective device or the module that is to be diagnosed. 3. Select the "Online & Diagnostics" command in the shortcut menu or the main menu. Or: 1. Open the device view in the device configuration. 2. Select the module to be diagnosed. 3. Select the "Online & Diagnostics" command in the shortcut menu or the "Online" main menu. Or: 1. Open the device view in the device configuration. 2. Establish an online connection to the module to be diagnosed. 3. Double-click on the diagnostics icon above the module. Or: 1094 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.2 Device and network diagnostics 1. Open the network view in the device configuration. 2. Select the station with the module to be diagnosed. 3. Select the "Online & Diagnostics" command in the shortcut menu or the "Online" main menu. Or: Result The online and diagnostics view of the module to be diagnosed will be started. If an online connection to the associated CPU had previously been created, the header bar of the Online and Diagnostics view will now have an orange background. Note If no online connection exists when the online and diagnostics view is started, no online information is displayed and the display fields remain empty. Activation of the "Online Tools" task card Activation of the "Online Tools" task card You can activate this task card as follows: 1. Start the online and diagnostics view. 2. Click on the "Online Tools" task card. Or: 1. Start the device view. 2. Click on the "Online Tools" task card. Or: 1. Start the network view. 2. Click on the "Online Tools" task card. 8.2.1.2 Showing non-editable and current values of configurable module properties Showing general properties and system-relevant information for a module Where do I find the information I need? The general properties and system-relevant information for a module can be found in the "General" group in the "Diagnostics" folder in the online and diagnostics view of the module to be diagnosed. WinCC Basic V13.0 System Manual, 02/2014 1095 Editing devices and networks 8.2 Device and network diagnostics Structure of the "General" group The "General" group consists of the following areas: Module Module information Vendor information "Module" area This area shows the following data of the module: Short designation, for example, CPU 1214C DC/DC/DC Order no. Hardware Firmware Racks Slot "Module information" area This area shows the following data of the module that you configured during hardware configuration: Module name Installation date (not displayed for all modules) Additional information (not displayed for all modules) "Manufacturer information" area This area shows the following data of the module: Manufacturer Serial number Profile: Profile ID as hexadecimal number Note You will find the corresponding profile name in the profile ID table for PROFIBUS International (see "www.profibus.com"). Profile details: Profile-specific type as hexadecimal number Note You will find the corresponding profile-specific type name in the profile-specific type table for PROFIBUS International (see "www.profibus.com"). 1096 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.2 Device and network diagnostics Display configured cycle times Where do I find the information I need? The required information can be found in the following places: In the "Cycle time" group of the "Diagnostics" folder in the Online and Diagnostics view of the module to be diagnosed. In the "Cycle time" pane of the "Online Tools" task card Structure of the "Cycle time" group in the "Diagnostics" folder of the Online and Diagnostics view The "Cycle time" group consists of the following areas: Cycle time diagram (graphical display of the assigned and measured cycle times) Cycle time configured (display of the assigned cycle times as absolute values) Cycle times measured (display of the measured cycle times as absolute values) Structure of the "Cycle time" pane of the "Online Tools" task card The "Cycle time" pane displays the cycle time diagram and below it the measured cycle times as absolute values. Assigned cycle times The following assigned cycle times are displayed in the cycle time diagram and in the "Cycle time configured" area. Minimum cycle time Maximum cycle time In the cycle time diagram, the minimum cycle time and the maximum cycle time correspond to the two markings on the time axis. In the "Cycle time configured" area, the assigned cycle times are displayed as absolute values. WinCC Basic V13.0 System Manual, 02/2014 1097 Editing devices and networks 8.2 Device and network diagnostics Show interfaces and interface properties of a module Where do I find the information I need? The interfaces and interface properties of a module can be found in the "Diagnostics" folder in the online and diagnostics view of the module to be diagnosed in the following group: PROFINET interface "PROFINET interface" group This group is divided into the following areas: "Ethernet address" with the "Network connection" and "IP Parameters" subareas "Ports" "Network connection" subarea of the "Ethernet address" area This subarea shows the following data for the module: MAC Address: MAC address of the interface. The MAC address consists of two parts. The first part ("Basic MAC address") identifies the manufacturer (Siemens, 3COM, ...). The second part of the MAC address differentiates between the various Ethernet devices. Each Ethernet module is assigned a unique MAC address. "IP Parameters" subarea of the "Ethernet address" area This subarea shows the following data for the module: IP address: Internet protocol address of the device on the bus (TCP/IP) Subnet mask: The subnet mask shows which part of the IP address determines the membership of a particular sub-network. Default router: If the subnet is connected via a router to other subnets, the IP address of the default router must be known. This is the only way a datagram can be forwarded with a non-matching subnet address. IP settings: Identifier for the path by which the device has obtained its IP settings (IP address, subnet mask, default router). 1098 Identifier Meaning 0 IP address is not initialized 1 By configuration (i.e., by the configuration loaded to the device from the device or network view) 2 Via the "Assign IP address" group of the online and diagnostics view WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.2 Device and network diagnostics Identifier Meaning 3 Via the DHCP server (i.e., the IP parameters are obtained by a special service from a DHCP server (Dynamic Host Configuration Protocol) and assigned for a limited time) 4 IP address is set by a user program 5 Source of IP address unknown IP setting time: Time stamp of the last change to the IP address directly through the Ethernet connection of the module "Ports" area This area shows the following data for the module: Ethernet ports Physical properties of the PROFINET interface Properties of the PROFINET interface Meaning Port no. Port number The short description of interface (X + interface no.) and port (P + port no.) is specified in parentheses. An "R" in the short description of a port means that it is a ring port. Status Displays the status of the port LINK LED. Status "OK" means another device (such as a switch) is connected to the port and the physical connection is available. Status "disconnected" means no other device is connected to the port. Status "deactivated" means that access to the port is blocked. Settings "Automatic" for automatic network settings of the device Network settings for speed and transmission method for manual network settings of the device Operating mode Network settings for speed and transmission method If you select a line in the port table, additional help information will be provided for the corresponding port. WinCC Basic V13.0 System Manual, 02/2014 1099 Editing devices and networks 8.2 Device and network diagnostics Displaying IO controllers that access modules of a Shared Device Where do I find the information I need? The display of those IO controllers that access the modules of a Shared Device can be found in the Online and Diagnostics view of the interface module of the Shared Device in the "Diagnostics" folder in the following area of the "PROFINET interface" group: IO controller Displaying sync domain properties of a PROFINET device Where do I find the information I need? The sync domain properties of a PROFINET device can be found in the following area of the "PROFINET interface" group in the "Diagnostics" folder of the Online and Diagnostics view of the device to be diagnosed: Domain "Domain" area This area is divided into the following subareas: Sync domain MRP domain What is a sync domain? A sync domain is a group of PROFINET devices that are synchronized to a common clock. Exactly one device has the role of the sync master (clock generator); all other devices assume the role of a sync slave. The sync master is usually an IO controller or a switch. Non-synchronized PROFINET devices are not part of a sync domain. "Sync domain" subarea of the "Domain" area This subarea shows the following properties of the sync domain: Name: Name of sync domain Role: Role of the PROFINET device in the sync domain. The following roles are possible: - Sync master - Sync slave Synchronization interval: Interval at which the synchronization is performed 1100 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.2 Device and network diagnostics Send clock Smallest possible send interval for the data exchange Jitter accuracy of the send clock Reserved bandwidth for cyclic communication Displaying MRP domain properties of a PROFINET device Where do I find the information I need? The MRP domain properties of a PROFINET device can be found in the following area of the "PROFINET interface" group in the "Diagnostics" folder of the Online and Diagnostics view of the device to be diagnosed: Domain "Domain" area This area is divided into the following subareas: Sync domain MRP domain What is an MRP domain? The Media Redundancy Protocol (MRP) enables redundant networks to be structured. Redundant transmission paths (ring topology) ensure that, if one transmission path fails, an alternative communication path is available. The PROFINET devices that are part of this redundant network form an MRP domain. "MRP domain" subarea of the "Domain" area This subarea shows the following properties of the MRP domain: Name: Name of MRP domain Role: Role of the PROFINET device in the MRP domain. The following roles are possible: - Manager - Manager (Auto) - Client - Not a device of the ring Ring port 1: The port of the PROFINET device that has the "Ring port 1" property WinCC Basic V13.0 System Manual, 02/2014 1101 Editing devices and networks 8.2 Device and network diagnostics Ring port 2: The port of the PROFINET device that has the "Ring port 2" property Status of the MRP ring: Indicates whether the ring is interrupted ("open" status) or not ("closed" status). Displaying current firmware of a module Displaying firmware You can display the currently installed firmware of a module. Requirements The module supports a firmware update. The module is connected online. Procedure To display the current firmware, follow these steps: 1. Open the module in the Online and Diagnostics view. 2. Select the "Firmware update" group in the "Functions" folder. 3. You read off the current firmware in the "Online data" area under "Firmware". 8.2.1.3 Showing the current values of dynamic modules properties Display measured cycle times Where do I find the information I need? The measured cycle times can be found at each of the following places: In the "Cycle time" group of the "Diagnostics" folder in the Online and Diagnostics view of the module to be diagnosed. In the "Cycle time" pane of the "Online Tools" task card Structure of the "Cycle time" group in the "Diagnostics" folder of the Online and Diagnostics view The "Cycle time" group consists of the following areas: Cycle time diagram (graphical display of the assigned and measured cycle times) Cycle time configured (display of the assigned cycle times as absolute values) Cycle times measured (display of the measured cycle times as absolute values) 1102 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.2 Device and network diagnostics Structure of the "Cycle time" pane of the "Online Tools" task card The "Cycle time" pane displays the cycle time diagram and below it the measured cycle times as absolute values. Graphical display of the measured cycle times The following measured cycle times are displayed in the cycle time diagram: Shortest cycle time: Duration of the shortest cycle since the last transition from STOP to RUN This corresponds to the dashed gray arrow on the left in the diagram. Current / last cycle time: Duration of the last cycle This corresponds to the green arrow in the diagram. If the current / last cycle time exceeds the maximum cycle time, the arrow will turn red. Note If the duration of the last cycle comes close to the maximum cycle time, it may be possible that it will be exceeded. Depending on the CPU type, parameter assignment and your user program, the CPU can switch to STOP mode. If for instance you are monitoring the tags in your program, this will increase the cycle time. If the cycle lasts longer than double the maximum cycle time, and you do not restart the maximum cycle time in the user program (by calling the extended RE_TRIGR) instruction, the CPU will switch to STOP mode. Longest cycle time: Duration of the longest cycle since the last transition from STOP to RUN. This corresponds to the dashed blue arrow on the right in the diagram. A blue band extends between the two dashed lines; this band corresponds to the entire range of the measured cycle times. If a measured cycle time is greater than the maximum cycle time, the portion of the band that lies outside the assigned limits will be colored red. Display of the measured cycle times as absolute values The following measured times are displayed in the "Cycle times measured" area and in the "Cycle time" pane. Shortest cycle time since the last transition from STOP to RUN. Current/last cycle time: Longest cycle time since the last transition from STOP to RUN. Showing the current status of the LEDs of a CPU Where do I find the information I need? The current status of the LEDs of a CPU can be found in the display area of the "CPU control panel" pane of the "Online tools" task card. WinCC Basic V13.0 System Manual, 02/2014 1103 Editing devices and networks 8.2 Device and network diagnostics Display area of the "CPU control panel" pane of the "Online Tools" task card This area contains the following displays: Station name and CPU type (short designation) RUN / STOP (corresponds to the "RUN / STOP" LED of the CPU) ERROR (corresponds to the "ERROR" LED on the CPU) MAINT (corresponds to the "MAINT" LED on the CPU) Showing fill levels of all types of memory on a CPU Where do I find the information I need? The fill levels of all types of memory on a CPU can be found on the following two pages: In the display area of the "Memory" group in the "Diagnostics" folder in the online and diagnostics view of the module to be diagnosed In the display area of the "Memory" pane on the "Online Tools" task card Display area of the "Memory" group in the "Diagnostics" folder of the online and diagnostics view This area contains the current memory utilization of the associated module and details of the individual memory areas. The memory utilization is shown both as a bar diagram and as a numerical value (percentage). The following memory utilizations are shown: Load memory If no memory card is inserted, the internal load memory is displayed. If a memory card is inserted, the operating system only uses the inserted load memory as the load memory. This is displayed here. Work memory Retentive memory Display area of the "Memory" pane of the "Online Tools" task card This area contains the current memory utilization of the associated module. The available memory is shown both as a bar diagram and as a numerical value (percentage). The numerical value is rounded to an integer value. Note If less than 1% of a memory area is utilized, the available portion of this memory area is shown as "99%". The following memory utilizations are shown: 1104 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.2 Device and network diagnostics Load memory If no memory card is inserted, the internal load memory is displayed. If a memory card is inserted, the operating system only uses the inserted load memory as the load memory. This is displayed here. Work memory Retentive memory See also Load memory (Page 957) Work memory (Page 957) Retentive memory areas (Page 959) Displaying fill level of all types of memory of an S7-1500 CPU Where do I find the information I need? The fill levels of all types of memory of an S7-1500 CPU can be found at the following two places: In the display area of the "Memory" group in the "Diagnostics" folder in the online and diagnostics view of the module to be diagnosed In the display area of the "Memory" pane on the "Online Tools" task card Display area of the "Memory" group in the "Diagnostics" folder of the online and diagnostics view This area contains the current memory utilization of the associated module and details of the individual memory areas. The memory utilization is shown both as a bar diagram and as a numerical value (percentage). The following memory utilizations are shown: Load memory Note The load memory is located on the SIMATIC memory card. Code work memory: work memory for program code Data work memory: work memory for data blocks Retentive memory WinCC Basic V13.0 System Manual, 02/2014 1105 Editing devices and networks 8.2 Device and network diagnostics Display area of the "Memory" pane of the "Online Tools" task card This area contains the current memory utilization of the associated module. The available memory is shown both as a bar diagram and as a numerical value (percentage). The numerical value is rounded to an integer value. Note If less than 1% of a memory area is utilized, the available portion of this memory area is shown as "99%". The following memory utilizations are shown: Load memory Note The load memory is located on the SIMATIC memory card. Code work memory: work memory for program code Data work memory: work memory for data blocks Retentive memory 8.2.1.4 Checking a module for defects Determining the diagnostic status of a module Where is the diagnostics status of a module displayed? The diagnostic status of a module is displayed in the "Diagnostic status" group in the "Diagnostics" folder in the online and diagnostics view of the module to be diagnosed. The "Diagnostics status" group consists of the following areas: Status Standard diagnostics (for S7-300 and S7-400 only for non-CPU modules) 1106 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.2 Device and network diagnostics "Status" area The following status information is displayed in this area: Status of the module as viewed by the CPU, for example: - Module available and OK. - Module defective. If the module experiences a fault and you have enabled the diagnostic error interrupt during configuration, the "Module defective" status is displayed. - Module configured, but not available. Example: Diagnostics data is not available because the current online configuration differs from the offline configuration. Detected differences between the configured and the inserted module. Provided it can be ascertained, the order number will be displayed for the set and actual type. The scope of the displayed information depends on the selected module. "Standard diagnostics" area The following diagnostics information for non-CPU modules is displayed in this area: Internal and external faults that relate to the overall module Associated diagnostics events Examples of such diagnostics information are: Entire backup failed Module defective Note Diagnostic interrupts A diagnostic interrupt can be reported to the CPU only if the module has diagnostic interrupt capability and the diagnostic interrupt has been enabled. The display of the diagnostic interrupt is a snapshot. Sporadic module defects can be identified in the diagnostics buffer of the respective CPU. Reading out the diagnostics buffer of a CPU Where do you read out the diagnostics buffer of a CPU? You read out the diagnostics buffer of a CPU in the "Diagnostics buffer" group in the "Diagnostics" folder in the Online and Diagnostics view. WinCC Basic V13.0 System Manual, 02/2014 1107 Editing devices and networks 8.2 Device and network diagnostics Structure of the "Diagnostics buffer" group The "Diagnostics buffer" group consists of the following areas: "Events" "Settings" Diagnostics buffer The diagnostics buffer is used as a log file for the diagnostics events that occurred on the CPU and the modules assigned to it. These are entered in the order of their occurrence, with the latest event shown at the top. "Events" area The "Events" area consists of the following elements: Check box "CPU time stamp takes into account local PG/PC time" Event table "Freeze display" or "Cancel freeze" button Details of the event: Event no., event ID, description, time stamp, incoming/outgoing information "Help on event", "Open in editor", "Save as ..." buttons Check box "CPU time stamp takes into account local PG/PC time" If you have not activated the check box, the diagnostics buffer entries are shown with the module time. If you have activated the check box, the diagnostics buffer entries are shown with the time given by the following formula: Displayed time = module time + time zone offset on your programming device / PC This requires the module time to be identical to UTC. You should use this setting if you wish to see the times of the diagnostics buffer entries for the module expressed in the local time of your programming device / PC. Selecting or clearing the check box immediately changes the times displayed for the diagnostics buffer entries. Note If you use the "WR_SYS_T" instruction in your program or if you set the real-time clock of the CPU using an HMI device instead of using UTC, we recommend that you clear the "CPU time stamp takes into account local PG/PC time" check box. In this case, the module time is the sole time of concern. 1108 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.2 Device and network diagnostics Event table The following information is displayed in the table for each diagnostics event: Sequential number of the entry The first entry contains the latest event. Date and time of the diagnostics event If no date and time are shown, the module has no integral clock. Short name of the event and, if applicable, the reaction of the CPU Note If an individual parameter of a text cannot be determined, the character string "###" is shown in its place. If no display text is yet available for new modules or new events, the numbers of the events and the individual parameters are stated as hexadecimal values. Icon for information related to incoming/outgoing status The following table shows the available icons and their respective meaning. Icon Meaning Incoming event Outgoing event Incoming event to which there is no independent outgoing event User-defined diagnostics event Only for S7-1200 and S7-1500 CPUs: Icon for the severity of the event The following table shows the available icons and their respective meaning. Icon Meaning No maintenance and/or no fault Maintenance required Maintenance demanded Error You can change the order of the columns, adjust the column widths and remove and add individual columns in the event table. In addition, you can sort as follows: by sequential number, by "Date and time" and by "Event". "Freeze display" or "Cancel freeze" button The "Freeze display" or "Cancel freeze" button is only enabled when there is an online connection to the CPU. The default setting is "Freeze display". The following happens when you click the "Freeze display" button: WinCC Basic V13.0 System Manual, 02/2014 1109 Editing devices and networks 8.2 Device and network diagnostics The current display of the diagnostics buffer entries is frozen. The labeling of the button changes to "Cancel freeze". If an error has occurred in your system, diagnostics events can occur very quickly in succession. This produces a high update rate on the display. Freezing the display allows you to calmly examine the situation in more detail. If the display is frozen and you click the "Cancel freeze" button, the following happens: The display of the diagnostics buffer entries is updated again. The labeling of the button changes to "Freeze display". Note If you freeze the diagnostics buffer display, the CPU continues to enter events in the diagnostics buffer. Details of the event If you select a line in the list of events, you obtain detailed information on the respective event: Sequential number of the event in the diagnostics buffer Event ID Description of the event with event-dependent additional information. Examples of this additional information: - Command that caused the event - Operating mode switch caused by the diagnostics event Time stamp Only for S7-1200 and S7-1500 CPUs: Associated I&M data (module, rack/slot, plant designation, location designation) Priority of the event Information on whether the event is an incoming or outgoing event "Help on event" button If you click on this button, the selected event is explained in more detail and any remedies given. Note For a small number of events, the "Help on event" button is grayed out. 1110 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.2 Device and network diagnostics "Open in editor" button The following table shows if the "Open block" button is active and which function it conceals. When is the "Open in editor" button enabled? What happens when you click this button? If the diagnostics event references the relative address of a block. The "Open in editor" function opens the referenced block in the offline view at the programming instruction that causes the error. This allows you to check and, if necessary, change the source code of the block at the specified place and then download it again to the CPU. This is the address of the command that caused the event. If the diagnostics event was triggered by a module. The "Open in editor" function opens the Device view of the module involved. "Save as ..." button If you click this button, the content of the diagnostics buffer is saved in a text file. "Diagnostics", depending on the language, with the extension ".txt" is suggested as the file name. You can however change this name. "Settings" area The "Settings" area consists of the following elements: "Display events" list "Apply settings as default" button "Output event information in hexadecimal format" check box "Display events:" list There is an check box in this list for every event class (default setting: all check boxes are selected). If you clear a check box, the events of that event class is no longer displayed in the "Events" area. Reselecting the check box displays the associated events once again. "Apply settings as default" button If you click this button, the settings are also applied to future occasions when the "Events" tab is opened. "Output event information in hexadecimal format" check box If you select the check box, the event IDs in the Events list of the "Events" area is displayed in hexadecimal format. If you clear the check box, the event information is given in text form. See also Basic information on the diagnostics buffer (Page 1129) WinCC Basic V13.0 System Manual, 02/2014 1111 Editing devices and networks 8.2 Device and network diagnostics Saving service data Purpose In the event of servicing it may be possible that the SIEMENS Customer Support requires very special information about the state of a module of your system for diagnostic purposes. If such a case occurs in your system, you will be asked by Customer Support to save the service data of the module and send the resulting file to them. Where do you carry out the saving of service data of a module? You carry out the saving of service data of a module in its online and diagnostics view at the following points: In the "Functions" folder in the "Save service data" group" The "Save service data" group consists of the following areas: Online data Saving service data "Online data" area This area shows the following data for the module: Order number Firmware version Module name (you configured this while configuring the hardware.) Rack Slot "Save service data" area Proceed as follows to create and save a file with special service data: 1. Select the point in the file system at which you want to save the file: - You use the path preset in the "Path" field. - Click the three-dot (browse) button. In the dialog that opens specify the desired path and enter the file name. 2. Click the "Save data" button. 1112 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.2 Device and network diagnostics 8.2.1.5 Changing the properties of a module or the programming device/PC Changing the mode of a CPU Requirement There is an online connection to the CPU whose mode you want to change. Procedure To change the mode of the CPU, follow these steps: 1. Enable the "Online tools" task card of the CPU. 2. Click the "RUN" button in the "CPU control panel" pane if you want to change the CPU to RUN mode or the "STOP" button if you want to change the CPU to STOP mode. Note The only button active is the one that can be selected in the current operating mode of the CPU. 3. Acknowledge the confirmation prompt with "OK". Or: 1. Open the "Online" menu. 2. Choose the "Start CPU" menu command if you want to set the CPU to RUN mode and "Stop CPU" if you want to set the CPU to STOP mode. Note The only button that is active is the one that can be chosen in the current operating mode of the CPU. 3. Acknowledge the confirmation prompt with "OK". Or: 1. Click the "Start CPU" button in the toolbar if you want to set the CPU to RUN mode and the "Stop CPU" button if you want to set the CPU to STOP mode. Note The only button that is active is the one that can be chosen in the current operating mode of the CPU. 2. Acknowledge the confirmation prompt with "OK". Result The CPU will be switched to the required operating mode. WinCC Basic V13.0 System Manual, 02/2014 1113 Editing devices and networks 8.2 Device and network diagnostics Performing a memory reset Requirement There is an online connection to the CPU on which the memory reset is to be performed. The CPU is in STOP mode. Note If the CPU is still in RUN mode and you start the memory reset, you can place it in STOP mode after acknowledging a confirmation prompt. Procedure To perform a memory reset on a CPU, follow these steps: 1. Enable the "Online Tools" task card of the CPU. 2. Click the "MRES" button in the "CPU control panel" pane. 3. Acknowledge the confirmation prompt with "OK". Result The CPU is switched to STOP mode, if necessary, and the memory reset is performed on the CPU. See also Basics of a memory reset (Page 955) Determining and setting the time of day on a CPU Where do I find the functions I need? You determine and change the time of day on a CPU in the "Set time of day" group in the "Functions" folder of the Online and Diagnostics view. This requires an online connection. Structure of the "Set time of day" group The "Set time of day" group consists of the following areas: Area for reading out and setting the time of day Time system (This area does not exist for S7-1200 and will not be examined here.) 1114 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.2 Device and network diagnostics Structure of the area for reading out and setting the time of day This area consists of the following parts: Programming device / PC time Here the time zone setting, the current date and the current time setting of your programming device / PC are displayed. Module time Here the date and time values currently read from the module (for example the CPU), are converted to local time and date and displayed. If the "Take from PG/PC" check box is selected, when you click the "Apply" button, the date and the PG/PC time converted to UTC are transferred to the module. If the "Take from PG/PC" check box is not selected, you can assign the date and time for the integrated clock of the module. After clicking the "Apply" button, the date and the time recalculated to UTC time are transferred to the module. Updating the firmware of a module Performing a firmware update Using firmware files, you can update the firmware of a module. Requirements The module is connected online. The module supports a firmware update. For those modules that require a supply voltage to perform the firmware update correctly: The supply voltage of the module is secured. For details, see the documentation of the module. Procedure To perform a firmware update, follow these steps: 1. Open the module in the Online and Diagnostics view. 2. Select the "Firmware update" group in the "Functions" folder. Note For S7-1500-CPUs, this group is subdivided into "PLC" and "Display". 3. Click the "Browse" button in the "Firmware update" area in order to select the path to the firmware update files. 4. Select one of these files. The table then lists all modules for which an update is possible with the selected firmware file. WinCC Basic V13.0 System Manual, 02/2014 1115 Editing devices and networks 8.2 Device and network diagnostics 5. Optional: Select the "Run firmware after update" check box to reset the module after the load operation and to start the new firmware. 6. Click the "Start update" button. If the selected file can be interpreted by the module, it is downloaded to the module. If the mode of the CPU needs to be changed, you will be prompted to do this in dialogs. WARNING Invalid plant states possible An S7-1500 CPU immediately goes to STOP mode when you start the firmware update, which can have an effect on the operation of an online process or a machine. Unexpected operation of a process or a machine can result in severe or fatal injuries and/or damage to property. Note After you have run a firmware update, you will need to replace the module involved with the same module with the current firmware version in the hardware configuration of your project. The engineering configuration then matches the actual physical configuration again. "Run firmware after update" check box If you have not selected the "Run firmware after update" check box, the previous firmware remains active until the module is reset (for example by cycling power). The new firmware only becomes active after the module has been reset. If you have selected the check box, the module is automatically reset after the firmware has been downloaded and it then continues with the new firmware. Activating the firmware following the update has the following consequences: A station executes a restart. This means that all modules in the station become unavailable. If the corresponding CPU is in RUN, activating the firmware can lead to access errors or other problems in the user program and might even mean that the CPU remains permanently in STOP. Note For some CPUs, the "Run firmware after update" check box is grayed out and deactivated. In this case, you must restart the CPU manually. For S7-1500 CPUs, the "Run firmware after update" check box is grayed out and selected. In this case, the new firmware is activated immediately after the download operation. See also Replacing a hardware component (Page 423) 1116 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.2 Device and network diagnostics Resetting an S7-1200 CPU to factory settings Requirement There is no memory card inserted in the CPU. There is an online connection to the CPU that you want to reset to the factory settings. The CPU is in STOP mode. Note If the CPU is still in RUN mode and you start the reset operation, you can place it in STOP mode by answering the security prompt with yes. Procedure To reset an S7-1200 CPU to factory settings, follow these steps: 1. Open the Online and Diagnostics view of the CPU. 2. Select the "Reset to factory settings" group in the "Functions" folder. 3. Select the "Keep IP address" check box if you want to keep the IP address or the "Delete IP address" check box if you want to delete the IP address. Note The two check boxes mentioned are only available if the module to be reset is able to choose whether to retain or delete the IP address. 4. Click the "Reset" button. 5. Acknowledge the confirmation prompt with "OK". Result The module is switched to STOP mode if necessary and the settings are then reset to factory settings. This means: The work memory and the internal load memory and all operand areas are cleared. All parameters are reset to their defaults. The diagnostic buffer is cleared. The time is reset. The IP address is kept or deleted depending on which setting you made. WinCC Basic V13.0 System Manual, 02/2014 1117 Editing devices and networks 8.2 Device and network diagnostics Resetting an S7-1500 CPU to factory settings Requirement If you start a reset to factory settings from the project context, an online connection to the relevant CPU must exist. The relevant CPU is in STOP mode. Note If the CPU is still in RUN mode and you start the reset operation, you can place it in STOP mode after acknowledging a confirmation prompt. Procedure To reset an S7-1500 CPU to factory settings, follow these steps: 1. Open the Online and Diagnostics view of the CPU (either from the project context or via "Accessible devices"). 2. Select the "Reset to factory settings" group in the "Functions" folder. 3. Select the "Keep IP address" check box if you want to keep the IP address or the "Delete IP address" check box if you want to delete the IP address. Note With "Delete IP address", all IP addresses are deleted. This applies regardless of how you created the online connection. If a memory card is inserted, selecting the "Delete IP address" option causes the following: The IP addresses are deleted and the CPU is reset to factory settings. Then, the configuration (including IP addresses) that is stored on the memory card is transferred into the CPU (see below). If the memory card was formatted before resetting to factory settings or if it is empty, no IP address is transferred into the CPU. 4. Click the "Reset" button. 5. Acknowledge the confirmation prompt with "OK". Result The module is switched to STOP mode if necessary and the settings are then reset to factory settings. This means: The work memory and the internal retentive system memory and all operand areas are cleared. All parameters are reset to their defaults. The diagnostic buffer is cleared. The time of day is reset. The I&M data are deleted except for I&M0 data. 1118 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.2 Device and network diagnostics The runtime meters are reset. The IP address is kept or deleted depending on which setting you made. If a memory card was inserted prior to the reset to factory settings, the configuration contained on the memory card (hardware and software) is downloaded to the CPU. Formatting an S7-1500 memory card Requirement If you start the formatting of the memory card from the project context, an online connection to the relevant CPU must exist. The relevant CPU is in STOP mode. Note If the CPU is still in RUN mode and you start a formatting operation, you can place it in STOP mode after acknowledging a confirmation prompt. Procedure To format an S7-1500 memory card, follow these steps: 1. Open the Online and Diagnostics view of the CPU (either from the project context or via "Accessible devices"). 2. Select the "Format memory card" group in the "Functions" folder. 3. Click the "Format" button. 4. Answer the safety prompt with "Yes". Result The memory card is formatted. The CPU is temporarily unavailable. The project data on the CPU are deleted with the exception of the IP address. If you start the formatting of the memory card from the project context, the Online and Diagnostics view remains open. If formatting is started via "Accessible devices", the Online and Diagnostics view will close. WinCC Basic V13.0 System Manual, 02/2014 1119 Editing devices and networks 8.2 Device and network diagnostics Assigning an IP address to a PROFINET IO device Basic information on assigning an IP address to a PROFINET IO device Overview All PROFINET IO devices work with the TCP/IP protocol and therefore require an IP address for operation on Industrial Ethernet. Once an IP address has been assigned to an IO device, it can be accessed via this address. You can then download configuration data or perform diagnostics, for example. Requirement The Ethernet LAN connection must already be established. The Ethernet interface of your programming device or PC must be accessible. The IO device that is to be assigned an IP address must be in the same IP band as the programming device or PC. Starting the address assignment via "Accessible devices" Requirement You have opened the Online and Diagnostics view of the PROFINET IO device using "Update accessible devices" (in the project tree) or "Accessible devices..." ("Online" menu). Procedure 1. Open the "Functions" folder and the "Assign IP address" group inside this folder. The "MAC address" field displays the MAC address of the PROFINET IO device. The "Accessible devices" button is grayed out. 2. Enter the desired IP address. 3. Enter the subnet mask. 4. If a router is to be used, select the "Use router" check box and enter its IP address. 5. Click the "Assign IP address" button. 1120 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.2 Device and network diagnostics Result The IP address is permanently assigned to the IO device or to the relevant PROFINET interface of the IO device. It is retained even through a startup or a power failure. Note For an S7-1500 CPU, you can also use the above-described method to change the IP address of a PROFINET interface, if a project has already been downloaded to the CPU via this interface. This overwrites the IP address downloaded via the project. See also Retentivity of IP address parameters and device names (Page 915) Starting the address assignment from the project context Requirement An online connection to the PROFINET IO device exists. You have opened the Online and Diagnostics view of the PROFINET IO device from the project context. The PROFINET IO device is not assigned to any IO controller. Procedure 1. Open the "Functions" folder and the "Assign IP address" group inside this folder. 2. Click the "Accessible devices" button in order to identify the devices that can be accessed. Note: For an S7-1500 CPU, there are two entries here because it has two PROFINET interfaces. 3. Select the IO device. The "IP address" field, "Subnet mask" field, "Use router" check box and "Router address" field are grayed out and contain the node properties you used to establish the current online access. 4. Click the "Assign IP address" button. Result The IP address is permanently assigned to the IO device or to the relevant PROFINET interface of the IO device. It is retained even through a startup or a power failure. See also Retentivity of IP address parameters and device names (Page 915) WinCC Basic V13.0 System Manual, 02/2014 1121 Editing devices and networks 8.2 Device and network diagnostics Assigning a PROFINET device name Basic information on assigning a name to a PROFINET IO device Device name Before an IO device can be addressed by an IO controller, it must have a device name. This procedure was chosen for PROFINET because names are easier to handle than complex IP addresses. Assigning a device name to a PROFINET IO device is comparable to setting the PROFIBUS address for a DP slave. An IO device has no device name in its delivery state. For an IO controller to address an IO device, it must first be assigned a device name using the programming device or PC. It is now ready to transfer the configuration information including the IP address during startup or exchange user data in cyclic operation. Rules for the device name The device name is subject to the following limitations: Restricted to a total of 240 characters (lower case letters, numbers, dash, or dot) A name component within the device name, which is a character string between two dots, must not exceed 63 characters. No special characters such as umlauts, brackets, underscore, slash, blank space, etc. The only special character permitted is the dash. The device name must not begin or end with the "-" character. The device name must not begin with a number. The device name form n.n.n.n (n = 0, ... 999) is not permitted. The device name must not begin with the string "port-xyz" or "port-xyz-abcde" (a, b, c, d, e, x, y, z = 0, ... 9). Where do I find the function I am seeking? You can assign the name of a PROFINET IO device at the following places: In the online and diagnostics view of the device in the "Assign name" group of the "Functions" folder. The user interface for this group differs depending on how you open the online and diagnostics view: - Open via "Accessible devices" - Open from the project context In the "Assign PROFINET device name" dialog 1122 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.2 Device and network diagnostics See also Assigning a name in the online and diagnostics view opened via "Accessible devices" (Page 1123) Assigning a name in the online and diagnostics view opened from the project context (Page 1123) Assigning a name in the "Assign PROFINET device name" dialog (Page 1124) Assigning a name in the online and diagnostics view opened via "Accessible devices" Requirement You have opened the online and diagnostics view of the PROFINET IO device using "Update accessible devices" (in the project tree) or "Accessible devices..." ("Online" menu). Procedure 1. Open the "Functions" folder and the "Assign name" group inside this folder. The "Type" field displays the module type of the PROFINET IO device. 2. Enter the required device name in the "PROFINET device name" input box. 3. Optional: Select the "Flash LED" check box in order to run an LED flash test on the PROFINET IO device. In this way, you verify that you are naming the desired IO device. Note The LED flash test is not supported by all PROFINET IO devices. The LED flash test runs until you cancel it. This is done, for example, by clearing the "Flash LED" check box or by closing the online and diagnostics view. 4. Click "Assign name". Result The entered name is assigned to the PROFINET IO device. Assigning a name in the online and diagnostics view opened from the project context Requirement You have opened the online and diagnostics view of the PROFINET IO device from the project context. The PROFINET IO device can be accessed using at least one PG/PC interface. WinCC Basic V13.0 System Manual, 02/2014 1123 Editing devices and networks 8.2 Device and network diagnostics Procedure 1. Open the "Functions" folder and the "Assign name" group inside this folder. The "PROFINET device name" drop-down list displays the current name in the offline project, and the "Type" box shows the module type of the PROFINET IO device. Note For CPUs with several PROFINET interfaces, the names of all existing PROFINET interfaces are displayed in the offline project. 2. Choose a different name from the drop-down list, if necessary. Note In steps 3 to 5, you determine the IO devices that are present in the PROFINET subnet. 3. In the "PG/PC interface for assignment" drop-down list, select the PG/PC interface you want to use to establish the online connection. 4. Optional: Use the three check boxes to make a selection from all IO devices available online. 5. Click the icon for determining the IO devices present in the PROFINET subnet. The table is then updated. 6. Select the desired IO device in the table. 7. Optional: Select the "Flash LED" check box in order to run an LED flash test on the PROFINET IO device. In this way, you verify that you are naming the desired IO device. Note The LED flash test is not supported by all PROFINET IO devices. The LED flash test runs until you cancel it. This is done, for example, by clearing the "Flash LED" check box, by selecting another IO device in the table, or by closing the online and diagnostics view. 8. Click "Assign name". Result The selected name is assigned to the PROFINET IO device or one of its PROFINET interfaces. Assigning a name in the "Assign PROFINET device name" dialog Requirement You have opened the "Assign PROFINET device name" dialog from the network view (from the shortcut menu of a PN/IE connection). The PROFINET IO device can be accessed using at least one PG/PC interface. 1124 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.2 Device and network diagnostics Procedure 1. The following is displayed in the "PROFINET device name" drop-down list: - the name of the interface that was used to open the project in the current offline project - the names of those IO devices that are connected by means of this interface The "Type" field displays the module type of the PROFINET IO device. Choose a different name from the drop-down list, if necessary. Note In steps 2 to 4, you determine the IO devices that are present in the PROFINET subnet. 2. In the "PG/PC interface for assignment" drop-down list, select the PG/PC interface you want to use to establish the online connection. 3. Optional: Use the three check boxes to make a selection from all IO devices available online. 4. Click the icon for determining the IO devices present in the PROFINET subnet. The table is then updated. 5. Select the desired IO device in the table. 6. Optional: Select the "Flash LED" check box in order to run an LED flash test on the PROFINET IO device. In this way, you verify that you are naming the desired IO device. Note The LED flash test is not supported by all PROFINET IO devices. The LED flash test runs until you cancel it. This is done, for example, by clearing the "Flash LED" check box or by selecting another IO device in the table. 7. Click "Assign name". Result The selected name is assigned to the PROFINET IO device or the interface that was used to open the dialog. Calibrating an S7-1500 analog module Calibrating an S7-1500 analog module - Overview Where do you calibrate an S7-1500 analog module? You calibrate an S7-1500 analog module in its Online and Diagnostics view in the "Calibrate" group of the "Functions" folder. WinCC Basic V13.0 System Manual, 02/2014 1125 Editing devices and networks 8.2 Device and network diagnostics Overview of the function scope of the calibrating function You can perform the following functions for an S7-1500 analog module in the "Calibrate" group: Specifying the current calibration of all channels Calibrating a channel Canceling a running calibration Resetting the calibration of a channel to the factory settings Requirement for the calibrating function described below The following is required for the calibrating function described below: You have opened the Online and Diagnostics view from the project context (thus not from the project tree or via the "Online" menu). There is an online connection to the analog module that is to be calibrated. Offline and online configuration are identical. Calibrating an S7-1500 analog module Overview of the calibration of a channel of an S7-1500 analog module The calibration of a channel of an S7-1500 analog module consists of the following steps: 1. Start calibration 2. Perform the second step up to the next to last step of the calibration 3. Complete calibration These steps are described in more detail in the following section. Requirement You have opened the Online and Diagnostic view of the S7-1500 analog module from the project context and are in the "Calibrate" group of the "Functions" folder. The associated CPU is online. No calibration is currently running on the analog module (if you want to start the calibration) or the last step initiated has been performed successfully (if you want to resume or complete the calibration). Procedure for starting the calibration To start the calibration, follow these steps: 1. In the overview table, select the line that belongs to the channel to be calibrated. 2. Click the "Start manual calibration" button. The user interface then changes as follows: 1126 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.2 Device and network diagnostics The overview table and the "Start manual calibration" button and "Set to factory settings" buttons become inactive. The step display is activated and displays the numbers of the current and last steps. The "Command" field becomes active and indicates what the user must do in the next calibration step. The "Status" field becomes active and shows the current status of the calibration, e.g., "Calibration successfully started". The "Measured value" field becomes active. For an input module a value is displayed here; you must enter a value here for an output module. The "Cancel" button becomes active. The "Next" button becomes active. This button can be used to advance to the next step of the calibration. Procedure for the second to the next to last step of the calibration Follow these steps: 1. Click the "Next" button. The fields of the user interface described above are then updated. Procedure for the last step of the calibration Follow these steps: 1. Click the "Next" button. The user interface then changes as follows: The overview table becomes active. The calibration display of the calibrated channel is updated. The "Start manual calibration" button and "Set to factory settings" buttons become active. The step display is deactivated and the numbers of the current step and last steps are empty. The "Command" field becomes inactive and is empty. The "Status" field becomes inactive and shows the last status of the calibration, e.g., "Calibration successfully finished". The "Measured value" field becomes inactive and is empty. The "Cancel" button becomes inactive. The "Next" button becomes inactive. Error occurrence If an error occurs during the calibration, the module cancels the calibration. Afterwards, the channel that was to be calibrated has the same settings as before the start of the calibration. WinCC Basic V13.0 System Manual, 02/2014 1127 Editing devices and networks 8.2 Device and network diagnostics Except for the "Status" field, the user interface appears the same after the occurrence of an error as before the calibration. The "Status" field displays the error that the module detected during the calibration. Canceling a running calibration of an S7-1500 analog module Requirement You have opened the Online and Diagnostic view of the S7-1500 analog module from the project context and are in the "Calibrate" group of the "Functions" folder. The associated CPU is online. A calibration is currently running on the analog module. Procedure To cancel a running calibration, follow these steps: 1. Click the "Cancel" button. Result The running calibration is canceled, and afterwards the channel to be calibrated has the same settings as before the calibration. All operator controls in the user interface are deactivated until the cancelation is complete. Except for the "Status" field, the user interface appears the same afterwards as before the calibration. The "Status" field displays the result of the cancelation. Resetting an S7-1500 analog module to factory settings Requirement You have opened the Online and Diagnostic view of the S7-1500 analog module from the project context and are in the "Calibrate" group of the "Functions" folder. The associated CPU is online. Procedure To reset a channel of an S7-1500 analog module to factory settings, follow these steps: 1. Select the line associated with the channel to be reset in the overview table. 2. Click the "Set to factory settings" button. 1128 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.2 Device and network diagnostics Result All operator controls in the user interface are deactivated until the reset operation is complete. Except for the "Status" field, the user interface appears the same afterwards as before the reset operation. The "Status" field displays the result of the reset operation. 8.2.1.6 Diagnostics in STOP mode Basic information on the diagnostics buffer Function The operating system of the CPU enters the errors detected by the CPU and the diagnosticscapable modules into the diagnostics buffer in the order in which they occurred. This includes the following events: Every mode change of the CPU (POWER UP, change to STOP mode, change to RUN mode) Every hardware and diagnostic error interrupt The top entry contains the most recent event. The entries in the diagnostics buffer are stored permanently. They are retained even if the power supply fails and can only be deleted by resetting the CPU to factory settings. A diagnostics buffer entry contains the following elements: Time stamp Error ID Additional information specific to the error ID Advantages of the diagnostics buffer The diagnostics buffer offers the following advantages: After the CPU has changed to STOP mode, you can evaluate the last events prior to the STOP so that you can locate and identify the cause of the STOP. You can detect and eliminate the causes of errors more quickly and thus increase the availability of the system. You can evaluate and optimize the dynamic system response. Organization of the diagnostics buffer The diagnostics buffer is a ring buffer. The maximum number of entries for the S7-1200 CPUs is 50. When the diagnostics buffer is full and a further entry needs to be made, all existing entries are shifted by one position (which means that the oldest entry is deleted) and the new entry is made at the top position that is now free (FIFO principle: first in, first out). WinCC Basic V13.0 System Manual, 02/2014 1129 Editing devices and networks 8.2 Device and network diagnostics Evaluation of the diagnostics buffer The contents of the diagnostics buffer can be accessed as follows: Using the Online and Diagnostics view The evaluation of events occurring prior to the error event (e.g., transition to STOP mode) allows you to obtain a picture of the possible causes or to zero in more closely or specify in more detail the possible causes (depending on the error type). Read the detailed information about the events carefully and use the "Help on event" button to obtain additional information and possible causes of individual entries. Note To make the best use of the time stamp information on the diagnostics buffer entries in timecritical systems, it is advisable to check and correct the date and time of day on the CPU occasionally. Alternatively, it is possible to perform a time-of-day synchronization using an NTP time server. See also Resetting an S7-1200 CPU to factory settings (Page 1117) Determining the cause of a STOP of a CPU (Page 1130) Determining and setting the time of day on a CPU (Page 1114) Assigning the clock parameters (Page 979) Determining the cause of a STOP of a CPU Requirement The CPU you want to analyze is in STOP mode. Procedure To find out the reason why a CPU changed to STOP, follow these steps: 1. Open the online and diagnostics view of the CPU. 2. Select the "Diagnostics buffer" group from the "Diagnostics" folder. 3. Evaluate the events occurring prior to the transition to STOP mode. Use this to obtain a picture of the possible causes or to zero in on or specify in more detail the possible causes (depending on the error type). Read the detailed information about the events carefully and use the "Help on event" button to obtain additional information and possible causes of individual entries. 1130 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.2 Device and network diagnostics Result You were able to zero in on or determine in more detail the cause of the CPU STOP. Note If the analysis does not enable you to overcome the problem, contact Customer Support. In this case, use the "Save as" button to back up the content of the diagnostics data to a text file and submit it to Customer Support. See also Reading out the diagnostics buffer of a CPU (Page 1107) 8.2.1.7 Online accesses in the Online and Diagnostics view Displaying status of the online connection Requirement The associated device can be accessed using at least one PG/PC interface. Procedure 1. Open the online and diagnostics view for the device whose online connection status you want to display. 2. Select the "Online access" group. Note The "Online access" group exists only for CPUs and some CPs. However, if you have opened the online and diagnostics view using the "Show/update accessible devices" function, it is not displayed. Result The status of the online connection is displayed in the "Status" area both graphically and in text form. Specifying a PG/PC interface, going online Requirement The associated device can be accessed using at least one PG/PC interface. There is currently no online connection to the relevant device. WinCC Basic V13.0 System Manual, 02/2014 1131 Editing devices and networks 8.2 Device and network diagnostics Procedure 1. Open the Online and Diagnostics view of the device to which you want to establish an online connection. 2. Choose the "Online access" group and the "Online access" area within this group. Note The "Online access" group exists only for CPUs and some CPs. If you have opened the Online and Diagnostics view using the "Show/update accessible devices" function, it is not displayed. 3. If an online connection was established previously for the device, the associated data for this online connection is preset in the drop-down lists. In this case, you can immediately continue with the last step of this operation, provided you have not changed the IP address in the meantime using the Online and Diagnostics view. 4. Choose the interface type in the "Type of PG/PC interface" drop-down list. The "PG/PC interface for online access" drop-down list then shows only the interfaces of the programming device or PC that match the selected interface type. 5. In the "PG/PC interface for online access" drop-down list, select the programming device or PC interface via which you want to establish the online connection. 6. Optional: Click the "Properties" button to change the properties of the associated CP. 7. In the "Connection to subnet" drop-down list, select the subnet via which the device is connected to the PG/PC interface. Note The PG/PC interface is connected to an interface of a device. If you only want to access this device, select the setting "Directly at slot <interface name>" in the drop-down list. If you want to access another device by means of routing, however, create a subnet at this interface in the hardware configuration and then select this subnet in the drop-down list. 8. If the device is accessible via a gateway, select the gateway that connects the two subnets involved in the "1st gateway" drop-down list. 9. In the "Device address" entry field, enter the IP address of the device to which you want to establish an online connection, if necessary. Note For CPUs with multiple IP addresses, select the IP address of the PROFINET interface you want to use to establish an online connection from the "Device address" drop-down list. 10.Alternatively: Click the "Show accessible devices" button and choose the device from the list of accessible devices to which you want to establish an online connection. 11.Click the "Go online" button. 1132 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.2 Device and network diagnostics Result The online connection to the desired device is established. Going offline Requirement There is currently an online connection to the relevant device. Procedure 1. Open the online and diagnostics view of the device for which you want to disconnect the online connection. 2. Choose the "Online access" group and the "Online access" area within this group. Note The "Online access" group exists only for CPUs and some CPs. However, if you have opened the online and diagnostics view using the "Show/update accessible devices" function, it is not displayed. 3. Click the "Go offline" button. Result The online connection to the desired device will be disconnected. Performing the flash test for a device with an online connection Requirement There is currently an online connection to the relevant device. The FORCE function is not active. WinCC Basic V13.0 System Manual, 02/2014 1133 Editing devices and networks 8.2 Device and network diagnostics Procedure 1. Open the online and diagnostics view of the device for which you want to perform a flash test. 2. Choose the "Online access" group and the "Status" area within this group. Note The "Online access" group exists only for CPUs and some CPs. However, if you have opened the online and diagnostics view using the "Show/update accessible devices" function, it is not displayed. 3. Select the "LED flash test" check box. Result On an S7-1200 CPU, the RUN/STOP, ERROR and MAINT LEDs flash. On an S7-1500 CPU, the RUN/STOP, ERROR, and MAINT LEDs flash. On an S7-300 or S7-400 CPU, the FRCE LED flashes. The LEDs flash until you cancel the flash test. This is done, for example, by clearing the "LED flash test" check box, by changing to another group of the online and diagnostics view, or by changing settings in the "Online access" area. 8.2.1.8 Checking PROFIBUS DP subnets for faults Basic information on the diagnostic repeater What is the diagnostic repeater? The diagnostic repeater is a repeater that can monitor a segment of an RS 485 PROFIBUS subnet (copper cable) during operation and signal line errors to the DP master via a diagnostics message frame. The diagnostic repeater detects, localizes and visualizes line errors during operation at an early stage. As a result, problems in the system are identified early and production downtimes will be minimized. Function of the diagnostic repeater The diagnostic repeater can perform line diagnostics on the DP2 and DP3 segments because it has a measuring circuit for these segments. The line diagnostics run in two steps: 1134 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.2 Device and network diagnostics Step 1: Topology determination You start the topology determination by calling the "DP_TOPOL" instruction in your program. The diagnostic repeater then determines the PROFIBUS addresses and the distance of the devices and creates a topology table. Step 2: Error localization The diagnostic repeater checks the lines during operation. It determines the distance to the point of the error and the reason for the error; it then issues a diagnostics alarm with relative information on the error location. Display of detailed information on the determined error location You receive detailed information on the determined error location in the Online and Diagnostics view of the diagnostic repeater. By means of icons By means of a display with graphics and text See also Displaying the status of the segment diagnostics using icons (Page 1135) Displaying the status of the segment diagnostics using graphics and text (Page 1136) Displaying the status of the segment diagnostics using icons Where do I find the information I need? The icons for the status of the segment diagnostics are available: In the expanded "Segment diagnostics" folder in the navigation pane of the Online and Diagnostics view of the relevant diagnostic repeater. The diagnostics icon associated with the segment will be displayed behind the segment designation. It must be noted here that line errors will be displayed for the DP2 and DP3 segments only. The DP1 and programming device segments do not display errors in the form of a diagnostics icon; rather, they signal only a few bus errors. Diagnostics icons The following table shows the available icons and their meaning. Icon Meaning Segment is error-free Segment contains errors Segment is deactivated WinCC Basic V13.0 System Manual, 02/2014 1135 Editing devices and networks 8.2 Device and network diagnostics Displaying the status of the segment diagnostics using graphics and text Where is the status of the segment diagnostics displayed with graphics and text? The status of the segment diagnostics will be displayed using graphics and text in the "DP1", "DP2", "DP3", and "PG" groups of the "Segment diagnostics" folder in the Online and Diagnostics view of the relevant diagnostic repeater. Structure of the "DP1", "DP2" "DP3", and "PG" groups The "DP1", "DP2", "DP3", and "PG" groups consist of the following elements: "Error location" field "Error" field "Resolution" field "Help on event" button "Freeze display" or "Cancel freeze" button "Error location" field This field displays the error location graphically, provided the diagnostic repeater can determine the location. The following picture shows an example for a line error occurring in the DP2 segment. In this example, the diagnostic repeater has the PROFIBUS address 2, and a line error has occurred between the devices with PROFIBUS addresses 16 and 17. This line error is located 25 m from device 16, 4 m from device 17, and 72 m from the diagnostic repeater. "Error" field The error is explained in plain text in this field. "Resolution" field Here, you will find actions for resolving the error. 1136 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.2 Device and network diagnostics "Help on event" button Click this button to obtain a more detailed explanation of the error and additional details on resolving the error, if applicable. "Freeze display" or "Cancel freeze" button The "Freeze display" or "Cancel freeze" button is only enabled when there is an online connection to the diagnostic repeater. The default setting is "Freeze display". The following happens when you click the "Freeze display" button: The current display of the segment diagnostics is frozen. The labeling of the button changes to "Cancel freeze". If the display is frozen and you click the "Cancel freeze" button, the following happens: The display of the segment diagnostics is updated again. The labeling of the button changes to "Freeze display". 8.2.2 Connection diagnostics 8.2.2.1 Overview of connection diagnostics Basics Connection diagnostics, as described below, refers to the diagnostics of communication connections. The connection diagnostics is started each time an online connection is established to a module (CPU or CP) that participates in one or more communication services. The connection status is updated automatically in the background. In the case of one-way connections, an online connection must exist to the communication partner that has established the communication connection. On connections configured at both ends, a distinction between the following two situations must be made: If there is an online connection to only one connection endpoint, only the part of the connection belonging to this connection endpoint can be diagnosed. If there is an online connection to both connection endpoints, both parts of the connection (and therefore the entire connection) can be diagnosed. WinCC Basic V13.0 System Manual, 02/2014 1137 Editing devices and networks 8.2 Device and network diagnostics Basic connections diagnostics options Connection diagnostics can be performed as follows: Using icons on the connection status display This display is generated in the connection table. Through detailed connection diagnostics This step is available in the "Diagnostics > Connection information" area of the Inspector window. Requirement for the connection diagnostics described below You can display the details of either all the communication connections created in the project (default) or selected communication connections in the connection table. The connection diagnostics described in the following assume that you display the details of selected communication connections. To do this, clear the "Show all connections" option in the shortcut menu. 8.2.2.2 Displaying the connection status using icons Content of connection table without an online connection For a CPU or CP, the connection table lists the communication connections (including properties) configured offline, if an online connection is not established. Content of connection table with an online connection After the online connection has been established, the properties of the communication connections listed offline will be expanded to include diagnostics icons for the connection status ("Online status" column). In addition, entries for all communication connections that exist online only (e.g., connections for the instructions for Open User Communication, programming device and OP connections, connections for web server access) will now be added to the connection table. For connections that exist online or offline only, the diagnostics icon at the bottom right is combined with a smaller additional comparison status icon. Diagnostics icons for communication connections The following table shows the diagnostics icons for communication connections. Icon Meaning Connection setup Connection not setup / is being setup Connection not available 1138 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.2 Device and network diagnostics Diagnostics icons for the comparison status The diagnostic icons for communication connections can be combined at the bottom right with additional smaller icons that indicate the result of the online/offline comparison. The following table shows the available comparison icons and their meaning. Icon Meaning Connection exists online only Connection exists offline only 8.2.2.3 Detailed connection diagnostics Detailed connection diagnostics - overview Where do I perform detailed connection diagnostics? To perform detailed connection diagnostics, go to the "Diagnostics > Connection" information of the Inspector window. How do I open the "Diagnostics > Connection information" area of the Inspector window? The following options are available for opening the "Connection information" tab of the Inspector window. Select the line of the relevant connection in the connection table. Click the "Diagnostics" and "Connection information" tabs one after the other in the Inspector window. Double-click the diagnostics icon of the relevant connection in the connection table. This step takes you to the programming editor for a S7 communication instruction or open user communication instruction. Double-click the diagnostic icon of the instruction (stethoscope). Structure or the "Diagnostics > Connection information" area of the Inspector window Requirements: the content of the "Connection information" tab has been filled, and an online connection to at least one end point of the relevant connection has been established. If a module has been selected (network view), the tab will contain the following group: Connection resources (for S7-1200 and S7-1500) If a connection has been selected (connection table), it will contain the following groups: Connection details Address details of the connection (for S7-1200 and S7-1500) WinCC Basic V13.0 System Manual, 02/2014 1139 Editing devices and networks 8.2 Device and network diagnostics Determining online connection resources for S7-1200 Where do you determine the online connection resources? The online connection resources are obtained in the "Connection resources" group. This group is located in the "Diagnostics > Connection information" area of the Inspector window. It is displayed only if you have selected a module in the network view to which an online connection exists. Number of connection resources Maximum number: Specifies the maximum number of available connection resources of the module. Not assigned: Indicates how many connection resources are not yet assigned. If connection resources are already reserved for certain types of communication, then the unreserved connection resources cannot always be used for the various connection types. Reserved and currently assigned connection resources For the communication types indicated below, the connection resources that are reserved and currently assigned by the module will be displayed. Communication type Meaning PG communication Resources for connections between the module and programming devices (for example, for the establishment of a connection from the project tree, for online diagnostics, etc.) HMI communication Resources for connections between the module and HMI devices Open User Communication Resources for connection of open user communication instructions S7 communication Resources for configured S7 connections, through which data can be exchanged by calling instructions in the user program. Other communication Specifies other assigned connection resources for which connection resources are not reserved. Determining online connection resources for S7-1500 Where do you determine the online connection resources? The online connection resources are obtained in the "Connection resources" group. This group is located in the "Diagnostics > Connection information" area of the Inspector window. It is displayed only if you have selected a module in the network view to which an online connection exists. 1140 WinCC Basic V13.0 System Manual, 02/2014 Editing devices and networks 8.2 Device and network diagnostics Description of the detailed display of the connection resources The detailed display of the connection resources includes: Number of available connection resources Number of configured connection resources Number of connection resources still available For a description of these, go to here . Determining connection details Where do I determine the connection details? The connection details are obtained in the "Connection details" group. This group is located in the "Diagnostics > Connection information" area of the Inspector window. When is the "Connection details" group filled in? The following requirements must be met to fill in the "Connection details" group on the "Connection information" tab: An online connection to the end point of the relevant connection must exist. You have selected a line in the connection table. Structure of the "Connection details" group The "Connection details" group consists of the following elements: Local ID (hex) Connection type (for S7-1200 and S7-1500) Protocol Connection status: icon and description Details Last status change (for S7-300 and S7-400 only) Determining the address details of a connection Where do I determine the address details of a connection? The address details of a connection are obtained in the "Connection address details" group. This group is located in the "Diagnostics > Connection information" area of the Inspector window. WinCC Basic V13.0 System Manual, 02/2014 1141 Editing devices and networks 8.2 Device and network diagnostics For which CPUs is the "Connection address details" group available? The "Connection address details" group of the "Connection information" tab is available for S7-1200 and S7-1500 CPUs. When is the "Connection address details" group filled in? The following requirements must be met to fill in the "Connection address details" group on the "Connection information" tab: An online connection to the end points of the relevant connection must exist. You have selected a line in the connection table. Structure of the "Connection address details" group The address details relevant to the connection type are specified for the two communication partners. 1142 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program 9.1.1 Programming basics 9.1.1.1 Operating system and user program 9 Operating system Function The operating system is contained in every CPU and organizes all CPU functions and sequences that are not associated with a specific control task. The tasks of the operating system, for example, include the following: Processing a warm restart Updating the process image of the inputs and outputs Calling the user program Detecting interrupts and calling interrupt OBs Detecting and handling errors Managing memory areas The operating system is a component of the CPU and is already installed there upon delivery. See also User program (Page 1143) User program Function The user program contains all functions that are necessary for processing your specific automation task. The tasks of the user program include: WinCC Basic V13.0 System Manual, 02/2014 1143 Programming the PLC 9.1 Creating the user program Checking the requirements for a (warm) restart using startup OBs, for example, limit switch in correct position or safety relay active. Processing process data, e.g. linking binary signals, reading in and evaluating analog values, defining binary signals for output, and outputting analog values Reaction to interrupts, for example, diagnostic error interrupt if the limit value of an analog expansion module is overshot. Error handling in normal program execution You write the user program and load it into the CPU. See also Operating system (Page 1143) 9.1.1.2 Blocks in the user program Linear and structured programming Linear programming Solutions for small automation tasks can be programmed linearly in a program cycle OB. This is only recommended for simple programs. The following figure shows a linear program schematically: The "Main1" program cycle OB contains the complete user program. 0DLQSURJUDP 0DLQ Structured programming Complex automation tasks can be more easily handled and managed by dividing them into smaller sub-tasks that correspond to the technological functions of the process or that can be reused. These sub-tasks are represented in the user program by blocks. Each block is then an independent section of the user program. 1144 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program Structuring the program offers the following advantages: Extensive programs are easier to program through the structure. Individual program sections can be standardized and used repeatedly with changing parameters. Program organization is simplified. Changes to the program can be made more easily. Debugging is simplified since separate sections can be tested. Commissioning is simplified. The following figure shows a structured program schematically: The "Main1" program cycle OB calls subprograms one after the other that execute defined subtasks. 0DLQSURJUDP 6XESURJUDPV 0DLQ %ORFNB %ORFNB Overview of the block types Block types Different BLOCK types are available to perform tasks within an automation system. The following table shows the available block types: Block type Brief description Organization blocks (Page 1146) (OB) Organization blocks define the structure of the user program. Functions (Page 1146) (FC) Functions contain program routines for recurring tasks. They have no "memory". Function blocks (Page 1147) (FB) Function blocks are code blocks that store their values permanently in instance data blocks, so that they remain available even after the block has been executed. Instance data blocks (Page 1149) Instance data blocks are assigned to a function block when it is is called for the purpose of storing program data. Global data blocks (Page 1148) Global data blocks are data areas for storing data that can be used by any blocks. WinCC Basic V13.0 System Manual, 02/2014 1145 Programming the PLC 9.1 Creating the user program Organization blocks (OB) Definition Organization blocks (OBs) form the interface between the operating system and the user program. They are called by the operating system and control, for example, the following operations: Startup characteristics of the automation system Cyclic program processing Interrupt-driven program execution Error handling You can program the organization blocks and at the same time determine the behavior of the CPU. Various organization blocks are available to you depending on the CPU used. For more information on organization blocks, refer to the descriptions of the modes of operation of CPUs in the "Additional information on configurations" chapter in "Configuring Hardware and Networks". Start information of organization blocks When certain organization blocks are started, the operating system provides information that can be evaluated in the user program. Refer to the descriptions of the organization blocks to find out which information is provided, if any. See also Creating organization blocks (Page 1332) Functions (FCs) Definition Functions (FCs) are code blocks without memory. You have no data memory in which values of block parameters can be stored. Therefore, when a function is called, all formal parameters must be assigned actual parameters. Functions can use global data blocks to store data permanently. Application A function contains a program that is executed when the function is called by another code block. Functions can be used, for example, for the following purposes: To return function values to the calling block, e.g. for mathematical functions To execute technological functions, e.g. individual controls using bit logic operations 1146 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program A function can also be called several times at different points in a program. As a result, they simplify programming of frequently recurring functions. Note Parameter transfer when calling functions To avoid errors when working with functions, observe the information in chapter "AutoHotspot". See also Creating functions and function blocks (Page 1333) Function blocks (FB) Definition Function blocks are code blocks that store their input, output and in-out parameters permanently in instance data blocks, so that they remain available even after the block has been executed. Therefore they are also referred to as blocks "with memory". Function blocks can also operate with temporary tags. Temporary tags are will not be stored in the instance DB, but are available for one cycle only. Application Function blocks contain subroutines that are always executed when a function block is called by another code block. A function block can also be called several times at different points in a program. As a result, they simplify programming of frequently recurring functions. Instances of function blocks A call of a function block is referred to as an instance. An instance data block is required for each instance of a function block; it contains instance-specific values for the formal parameters declared in the function block. The function block can store its instance-specific data in its own instance data block or in the instance data block of the calling block. WinCC Basic V13.0 System Manual, 02/2014 1147 Programming the PLC 9.1 Creating the user program Access modes S7-1200 and S7-1500 offer two different access options for the instance data blocks, which can be assigned to a function block when this is called: Data blocks with optimized access Data blocks with optimized access have no firmly defined memory structure. The data elements contain only a symbolic name in the declaration, no fixed address within the block. Data blocks with standard access (compatible with S7-300/400) Data blocks with standard access have a fixed memory structure. The declaration elements contain both a symbolic name in the declaration and a fixed address within the block. Note To avoid errors when working with function blocks, refer to the section "Auto-Hotspot". See also Creating functions and function blocks (Page 1333) Multi-instances (Page 1159) Instance data blocks (Page 1149) Basics of block access (Page 1151) Global data blocks (DB) Definition Data blocks are used to store program data. Data blocks thus contain variable data that is used by the user program. Global data blocks store data that can be used by all other blocks. The maximum size of data blocks varies depending on the CPU. You can define the structure of global data blocks anyway you please. You also have the option of using PLC data types (UDT) as a template for creating global data blocks. Global data blocks in the user program Every function block, function, or organization block can read the data from a global data block or can itself write data to a global data block. This data remains in the data block even after the data block is exited. A global data block and an instance data block can be open at the same time. The following figure shows the different accesses to data blocks: 1148 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program )XQFWLRQB *OREDO'% '%B*OREDO $FFHVVIRUDOOEORFNV )XQFWLRQB )XQFWLRQ%ORFNB ,QVWDQFH'% '%B,QVWDQFH $FFHVVRQO\IRUIXQFWLRQ GDWDERFNB Access modes S7-1200 and S7-1500 offer two different access options for global data blocks: Data blocks with optimized access Data blocks with optimized access have no fixed defined structure. In the declaration, the data elements are assigned only a symbolic name and no fixed address within the block. Data blocks with standard access (compatible with S7-300/400) Data blocks with standard access have a fixed structure. In the declaration, the data elements are assigned both a symbolic name and a fixed address within the block. ARRAY data blocks (S7-1500) ARRAY data blocks are a particular type of global data block. These consist of an ARRAY of any data type. For example, an ARRAY of a PLC data type (UDT) is possible. The DB contains no other elements besides the ARRAY. Because of their flat structure, ARRAY data blocks facilitate access to the ARRAY elements and their transfer to called blocks. The "Optimized block access" attribute is always enabled for ARRAY data blocks. ARRAY data blocks with standard access are not possible. The "Move operations" section of the "Instructions" task card offers options for addressing of ARRAY DBs. See also Creating data blocks (Page 1334) Basics of block access (Page 1151) Instance data blocks Definition The call of a function block is referred to as an instance. The data with which the instance works is stored in an instance data block. WinCC Basic V13.0 System Manual, 02/2014 1149 Programming the PLC 9.1 Creating the user program The maximum size of instance data blocks varies depending on the CPU. The tags declared in the function block determine the structure of the instance data block. Access modes S7-1200 and S7-1500 offer two different access options for the instance data blocks, which can be assigned to a function block when this is called: Data blocks with optimized access Data blocks with optimized access have no firmly defined structure. The declaration elements contain only one symbolic name in the declaration, and no fixed address within the block. Data blocks with standard access (compatible with S7-300/400) Data blocks with standard access have a fixed structure. The declaration elements contain both a symbolic name in the declaration and a fixed address within the block. See also: Auto-Hotspot See also Creating data blocks (Page 1334) Basics of block access (Page 1151) CPU data blocks Definition CPU data blocks are generated by the CPU at runtime. To this purpose, insert the "CREATE_DB" instruction into your user program. You can use the data block that is generated at runtime to save your data. CPU data blocks are indicated by means of a small CPU icon in the "Program blocks" folder of an available node. You can monitor the values of the variables of a CPU data block in online mode, similar to those of a different data block type. You cannot create CPU data blocks in your offline project. Loading CPU data blocks The CPU data block that the user program has generated by means of the "CREATE_DB" instruction is initially only available on the device in online mode. All CPU data blocks will be included with the other blocks the next time you perform a complete download from the device to the project. The CPU data blocks are marked with a small CPU icon in the process. However, you cannot upload these CPU data blocks to your device again. 1150 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program Restrictions on CPU data blocks in the project Once the CPU data blocks have been loaded into your offline project, you can open and view their content. However, note that the CPU data blocks in the project are write-protected. The CPU data blocks in the project are therefore subject to the following restrictions: You cannot edit CPU data blocks, or convert these into a different data block type. CPU data blocks cannot be assigned a know-how protection. You cannot change the programming language of a CPU data block. CPU data blocks cannot be compiled or downloaded to a device. Comparing CPU data blocks Once the CPU data blocks have been loaded into your offline project, you can run an online/ offline comparison for the CPU DBs loaded. The comparison editor provides you with a corresponding overview of the differences. It is possible to synchronize the online and off-line version of CPU data blocks if differences are found, but not by downloading the offline version to the device. Deleting CPU data blocks You can delete CPU data blocks both from the project and from the CPU. See also Deleting CPU data blocks (Page 1353) Blocks with optimized access Basics of block access Introduction STEP 7 offers data blocks with different access options: Data blocks with optimized access (S7-1200/S7-1500) Data blocks with standard access (S7-300 / S7-400 / S7-1200 / S7-1500) Within one program you can combine the two types of blocks. Data blocks with optimized access Data blocks with optimized access have no fixed defined structure. In the declaration, the data elements are assigned only a symbolic name and no fixed address within the block. The elements are saved automatically in the available memory area of the block so that there are no gaps in the memory. This makes for optimal use of the memory capacity. WinCC Basic V13.0 System Manual, 02/2014 1151 Programming the PLC 9.1 Creating the user program Tags are identified by their symbolic names in these data blocks. To address the tag, enter its symbolic name. For example, you access the "Fill Level" tag in the "Data" DB as follows: "Data".Fill Level Blocks with optimized access offers the following advantages: You can create data blocks with any structure without paying attention to the physical arrangement of the individual data elements. Quick access to the optimized data is always available because the data storage is optimized and managed by the system. Access errors, as with indirect addressing or from the HMI, for example, are not possible. You can define specific individual tags as retentive. Optimized blocks are equipped with a memory reserve by default which lets you expand the interfaces of function blocks or data blocks during operation. You can download the modified blocks without setting the CPU to STOP and without affecting the values of already loaded tags. Note The "Optimized block access" attribute is always enabled for the following blocks and cannot be deselected. GRAPH blocks ARRAY data blocks Data blocks with standard access Data blocks with standard access have a fixed structure. In the declaration, the data elements are assigned both a symbolic name and a fixed address within the block. The address is shown in the "Offset" column. Tags in these data blocks can be addressed in both symbolic and absolute form. "Data".Fill Level DB1.DBW2 Setting Retentivity for Optimized Access or Standard Access If you define data as retentive, its values are retained even after a power failure or a network off. A retentive tag is not initialized after the hot restart but retains the value it had prior to the power failure. If a DB tag is defined as retentive, it is stored in the retentive memory area of the data block. The options for setting the retentivity depend on the access type of the block. 1152 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program In data blocks with standard access, you cannot set the retentive behavior of individual tags. The retentivity setting is valid for all tags of the data block. In data blocks with optimized access you can define the retentive behavior of individual tags. For structured data type tags, the retentivity setting always applies to the entire structure. You cannot make any individual retentivity setting for separate elements within the data type. Setting Addressing Options for Optimized Access or Standard Access Blocks with optimized access permit only "type-safe" access. Type-safe access addresses tags by their symbolic name only. This means even changes to the block or the block interface will not result in inconsistencies in the program or access errors. The following table shows the permitted addressing options for optimized data: Addressing Symbolic addressing Block with standard access Block with optimized access x x Indexed addressing of ARRAYs x Slice access x x Overlapping with AT x - Absolute addressing x - Indirect addressing via ANY x - Indirect addressing via POINTER and VARIANT x with symbolic notation only See also Setting up block access (Page 1153) Setting up block access Introduction Block access is set up automatically when you create a block: Blocks created on CPUs of the S7-1200/1500 product range provide optimized access by means of a default setting. New blocks created on CPUs of the S7-300/S7-400 product range provide standard access by means of a default setting. Access to a block that you copy or migrate to a CPU of a different product range is not converted automatically. However, in certain situations it may be useful to change block access in manual mode, e.g., in order to utilize the full functional scope of the CPU. WinCC Basic V13.0 System Manual, 02/2014 1153 Programming the PLC 9.1 Creating the user program In most cases, you will have to recompile and load the program after block access has been converted. NOTICE Optimized block access for GRAPH blocks The "Optimized block access" attribute is always enabled for GRAPH blocks in S7-1500 and cannot be deselected. Procedure To set the block access, proceed as follows: 1. Open the "Program blocks" folder in the project tree. 2. Right-click on the block whose block access you want to change. 3. Select the "Properties" command in the shortcut menu. The properties dialog box of the block opens. 4. Click "Attributes" in the area navigation. 5. Enable or disable the "Optimized block access" option. 6. Confirm your entries with "OK". Restrictions and special features As a matter of principle, you can only convert block access on CPUs of the S7-1200/1500 product range, as only these support the "optimized" access mode. The following restrictions or special features apply in this context: Instance data blocks The block access of instance data blocks is always determined by the assigned function block and cannot be changed in manual mode. If you change the access mode on a function block, you also need to update the assigned instance data blocks. This update procedure adapts the access mode of the instance data block. System blocks and know-how protected blocks You cannot manually edit the block access for system blocks and know-how protected blocks. Organization blocks The start information of an OB with standard access is always stored in the first 20 bytes of the "Temp" section in the block interface. By contrast, the start information of an OB with optimized access is always written to the "Input" section. For this reason, the block interface of OBs will also change whenever you convert block access. Additional information is provided in the following sections. Converting block access from "standard" to "optimized". A block copied from the CPU of the S7-300/400 product range to a CPU of the S7-1200/1500 product range will initially retain the "standard" access mode. However, you can significantly 1154 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program increase the performance of program execution by using blocks with optimized access, which is why it may be useful to modify the access mode manually. The blocks are adapted as follows in the course of conversion: Function blocks All interface parameters are assigned the "Non-retain" retentivity setting. Global data blocks The retentivity setting that was assigned centrally to the entire data block is transferred to the individual interface parameters. It is now possible to manipulate the retentivity setting of the various parameters. However, the following rule will still apply: For structured data type tags, the retentivity setting always applies to the entire structure. You cannot assign separate retentivity settings to the various elements within a structured data type. It therefore follows that you cannot assign individual retentivity settings to the tags of data blocks that are based on PLC data types. Organization blocks All interface parameters that are stored in the first 20 bytes of the "Temp" section will be deleted. New CPU-specific start information is entered in the "Input" section. Naming conflicts with user-defined interface parameters occurring in the process are resolved by renaming the user-defined interface parameters. CAUTION The conversion of the block access has the following consequences: Absolute addressing of the interface parameters of the block is no longer possible after conversion of block access to the "optimized mode. Example: #L0.1 is no longer valid. Since conversion to the "optimized" block access mode of organization blocks also modifies the OB interface, you may possibly have to adapt, recompile and load the program again due to these changes. See also: Auto-Hotspot Converting block access from "optimized" to "standard". If you want to copy or move a block from the CPU of the S7-300/400 product range to a CPU of the S7-1200/1500 product range, you first need to set the "standard" access mode. The blocks are adapted as follows in the course of conversion: WinCC Basic V13.0 System Manual, 02/2014 1155 Programming the PLC 9.1 Creating the user program Function blocks and global data blocks. You can no longer set a retentivity in the function block. The corresponding setting is made in the instance data block. All interface parameters in the instance DB or global DB are assigned the same retentivity setting. The conversion is subject to the following rule: - If all interface parameters in the original block were retentive, the entire block will be retentive after conversion. - If all interface parameters in the original block were non-retentive, the entire block will be non-retentive after conversion. - If the interface parameters in the original block had different retentivity settings, the entire block will be non-retentive after conversion. Organization blocks All interface parameters stored in the "Input" section will be deleted. New CPU-specific start information is entered in the "Temp" section. This data is written to the first 20 bytes. Naming conflicts with user-defined interface parameters occurring in the process are resolved by renaming the user-defined interface parameters. CAUTION The conversion of the block access has the following consequences: Since a conversion to "standard" block access mode might change the retentivity settings of the interface parameters, you may possibly have to adapt, recompile and load the program again due to these changes. See also: Auto-Hotspot See also Basics of block access (Page 1151) 9.1.1.3 Block calls Principles of block calls Function of block calls For your blocks to be executed in the user program, they need to be called from another block. When one block calls another block, the instructions of the called block are executed. Only when execution of the called block has been completed does execution of the calling block resume. The execution is continued with the instruction that follows on the block call. The following figure shows the sequence of a block call within a user program: 1156 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program &DOOLQJEORFN 2%)%)& 3URJUDPH[HFXWLRQ &DOOLQJEORFN )%RU)& 3URJUDPH[HFXWLRQ 2SHUDWLRQWKDWFDOOV DQRWKHUEORFN %ORFNHQG Parameter transfer When a block is called, you must assign values to the parameters in the block interface. By providing input parameters you specify the data with which the block is executed. By providing the output parameters you specify where the execution results are saved. See also Call hierarchy (Page 1157) Principles for single instances and multi-instances (Page 1158) Call hierarchy Definition The order and nesting of block calls is referred to as the call hierarchy. The permissible nesting depth depends on the CPU. The following figure shows an example of the order and nesting of block calls within an execution cycle: WinCC Basic V13.0 System Manual, 02/2014 1157 Programming the PLC 9.1 Creating the user program 1HVWLQJGHSWK 6WDUWRI F\FOH )%B )&B 2SHUDWLQJV\VWHP ,QVWDQFH'% )%B 0DLQ ,QVWDQFH'% )%B )&B ,QVWDQFH'% )&B '%B*OREDO See also Principles for single instances and multi-instances (Page 1158) Principles of block calls (Page 1156) Call function blocks as single or multi-instances Principles for single instances and multi-instances Use of single instances and multiple instances Function blocks (FBs) store their data in instance data blocks. Instance data blocks store the values of the block parameters and the static local data of the function blocks. You can assign instance data blocks as follows: Single instance: One instance data block for each instance of a function block Multiple instance: An instance data block for the instance of a function block and all instances of function blocks called in it. See also Principles of block calls (Page 1156) Multi-instances (Page 1159) Single instances (Page 1159) Call hierarchy (Page 1157) 1158 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program Single instances Definition The call of a function block, which is assigned its own instance data block, is called a single instance data block. By assignment of the instance data block, you specify where the instance data of the FB is to be stored. By assigning a different instance data block to each call, you can use the same FBs several times with different instance data in each case. Example of a single instance You can control several motors using one function block. For this purpose, you assign a different instance data block for each function block call for motor control. The different data for the various motors, such as speed, ramp-up time, total operating time, are saved in the different instance data blocks. A different motor will be controlled, depending on the instance data block assigned. The following figure shows the control of three motors using one function block and three different data blocks: 5RWDWLRQDOVSHHG 0DLQ )%B0RWRU )%B0RWRU 'DWD )%B0RWRU 3RZHUXS )%B0RWRU 5RWDWLRQDO VSHHG 3RZHUXS 2SHUDWLRQ 'DWD 2SHUDWLRQ 'DWD See also Principles for single instances and multi-instances (Page 1158) Multi-instances (Page 1159) Multi-instances Definition Multi-instances enable a called function block to store its data in the instance data block of the calling function block. WinCC Basic V13.0 System Manual, 02/2014 1159 Programming the PLC 9.1 Creating the user program This allows you to concentrate the instance data in one instance data block and thus make better use of the number of instance data blocks available. One instance data block for the instances of different function blocks The following figure shows how multiple different function blocks store their data in a calling block. The FB_Workpiece calls the following on after the other: FB_Grid, FB_Punch and FB_Conveyor. The called blocks store their data in the DB_Workpiece, the instance data block of the calling block. )%B:RUNSLHFH 0DLQ '%B:RUNSLHFH VWDW)%B*ULG VWDW)%B3XQFK VWDW)%B&RQYH\RU )%B*ULG &RQWUROOLQJ DJULG '%B:RUNSLHFH 'DWDIRU JULG )%B:RUNSLHFH )%B3XQFK )%B*ULG )%B3XQFK )%B&RQYH\RU &RQWUROOLQJ DSXQFK )%B&RQYH\RU &RQWUROOLQJ DFRQYH\RUb 'DWDIRU SXQFK 'DWDIRU FRQYH\RU ,QVWDQFH'%RI)%B:RUNSLHFH 1160 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program One instance data block for multi-instances of a function block The following figure shows how a function block that is called in multi-instances stores the data for all the instances in one instance data block. )%B0RWRUV )%B0RWRUB VWDW)%B0RWRUB VWDW)%B0RWRUB VWDW)%B0RWRUB 0DLQ '%B0RWRU'DWD '%B0RWRU'DWD 'DWDIRU 0RWRUB )%B0RWRUV )%B0RWRUB )%B0RWRUB 'DWDIRU 0RWRUB )%B0RWRUB 'DWDIRU 0RWRUB )%B0RWRUB )%B0RWRUB ,QVWDQFH'%RI)%B0RWRUV The function block FB_Motors calls three instances of the FB_Motor. The instances are "Motor_1", "Motor_2" and "Motor_3". Each call uses different instance data. However, all instance data are located in a single instance data block, DB_MotorData. See also Principles for single instances and multi-instances (Page 1158) Single instances (Page 1159) Parameter transfer at block call Basics of block parameters Introduction The calling block gives the called block the values with which it is to work. These values are referred to as block parameters. The input parameters provide the called block with the values that it has to process. The block returns the results via the output parameters. Block parameters are therefore the interface between the calling and the call block. You use input parameters when you want to only query or read values, and output parameters when you want to set or write these values. If block parameters are read and written you have to create these as in-out parameters. WinCC Basic V13.0 System Manual, 02/2014 1161 Programming the PLC 9.1 Creating the user program Formal and actual parameters The block parameters are defined in the interface of the called block. These parameters are referred to as formal parameters. They are placeholders for the parameters that are transferred to the block when it is called. The parameters transferred to the block when it is called are referred to as actual parameters. Rules for using the block parameters The following rules apply to the use of block parameters within the block: Input parameters may only be read. Output parameters may only be written. In/out parameters may be read and written. See also Parameter assignment to function blocks (Page 1165) Parameter assignment to functions (Page 1163) General rules for assigning parameters (Page 1162) Using tags within the program (Page 1179) Keywords (Page 1173) Supplying block parameters during call General rules for assigning parameters Introduction When you call a block with block parameters, assign actual parameters to its formal parameters. The rules described below apply here. Compatible data types The data types of actual and formal parameters must be identical or convertible according to the rules of data type conversion. Transferring ARRAYs You can transfer ARRAYs as parameters. If a block has an input parameter of ARRAY type, you must transfer as actual parameter an ARRAY with identical structure. You can also transfer individual elements of an ARRAY as actual parameter if the element corresponds to the data type of the formal parameter. 1162 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program Transferring PLC data types You can also transfer tags that are declared as PLC data type as actual parameters. If the formal parameter is declared as PLC data type in the tag declaration, you must transfer a tag that has the same PLC data type as actual parameter. An element of a tag declared by means of PLC data type can also be transferred as actual parameter at block call, provided that the data type of the element of the tag matches the data type of the formal parameter. Transferring structures (STRUCT) You can transfer structures as parameters. If a block has an input parameter of the STRUCT type, you must transfer as actual parameter a STRUCT with identical structure. This means that the names and data types of all structure components have to be identical. You can also transfer individual elements of an STRUCT as actual parameter if the element corresponds to the data type of the formal parameter. Note We recommend programming structures as PLC data types. PLC data types make programming easier, since they can be used multiple times and modified centrally. See also Parameter assignment to function blocks (Page 1165) Parameter assignment to functions (Page 1163) Basics of block parameters (Page 1161) Parameter assignment to functions Parameters of functions (FC) Functions have no data memory in which values of block parameters can be stored. Therefore, when a function is called, all formal parameters must be assigned actual parameters. Input parameters (Input) Input parameters are read only once per cycle, namely before the block call. Therefore, the rule is that writing an input parameter within the block does not affect the actual parameter. Only the formal parameter is written. Output parameters (Output) Output parameters are read only once per cycle, namely after the block call. Therefore, the rule is that output parameters should not be read within the block. If you nevertheless read an WinCC Basic V13.0 System Manual, 02/2014 1163 Programming the PLC 9.1 Creating the user program output parameter, please note that only the value of the formal parameter is read. The value of the actual parameter cannot be read within the block. If an output parameter of a function is not written in this function, the value that is predefined for the specified data type is used. For example, the value "false" is predefined for BOOL. However, structured output parameters are not pre-assigned with a value. To prevent unintentional further processing of the predefined value or an undefined value, note the following when programming the block: Make sure that the output parameters are written with values for all possible program paths within the block. In doing so, note that jump commands may skip instruction sequences in which outputs are set, for example. Note that the set and reset commands are dependent on the result of the logic operation. If the value of an output parameter is determined with these commands and RLO = 0, a value will not be generated. If possible, assign a default value for the output parameters of functions. In/out parameters (InOut) In/out parameters are read before the block call and written after the block call. If you read or write the parameter within the block, you only access its formal parameter. An exception is in/out parameters with a structured data type. Structured data types consist of several data elements, for example ARRAY or STRUCT. These are passed to the called block through a POINTER. You therefore always access the actual parameter when you read or write a structured in/out parameter within a block. When an in/out parameter of a function is not written to this function, the old output value or the input value is used as a value. Nevertheless, you should observe the information provided above for output parameters so that old values are not inadvertently processed further. Temporary local data (Temp) Temporary local data is only available within a cycle. It is treated differently depending on the block type: Standard access The following rule applies to code blocks with standard access as well as to all tags with retentivity setting "Set in IDB": If you use temporary local data, you have to make sure that the values are written within the cycle in which you want to read them. Otherwise, the values will be random. Temporary data of the STRING data type is an exception: It is automatically pre-assigned the correct length information. Optimized access The following rule applies to code blocks with optimized access: If a temporary tag is not written within a function, the value that is predefined for the specified data type is used. For example, the value "false" is predefined for BOOL. Elements of the PLC data types are pre-assigned with the default value that is specified in the declaration of the PLC data type (UDT). ARRAY elements are pre-assigned with the value "0", even if they are used within a PLC data type. Strings are pre-assigned the correct length information. 1164 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program Function value (Return) Functions normally calculate a function value. This function value can be returned to the calling block via the RET_VAL output parameter. For this, the RET_VAL output parameter must be declared in the interface of the function. RET_VAL is always the first output parameter of a function. All data types are permitted for the RET_VAL parameter except ARRAY and STRUCT, as well as parameter types TIMER and COUNTER. In the SCL programming language functions can be call directly in an expression. The result of the expression is then formed with the calculated function value. Therefore, the data type ANY is not permitted in SCL for the function value. See also Parameter assignment to function blocks (Page 1165) Basics of block parameters (Page 1161) General rules for assigning parameters (Page 1162) Calling functions (Page 1506) Examples for calling functions in SCL (Page 1509) Parameter assignment to function blocks Supplying parameters of function blocks (FB) In the case of function blocks the parameter values will be stored in the instance data. If the input, output, or in-out parameters of a function block were not assigned with values, the stored values are used. In some cases, it is mandatory to specify an actual parameter. The following table shows which parameters of a function block must be assigned actual parameters: Parameter Elementary data type Structured data type Parameter type Input (Input) optional optional required Output (Output) optional optional required In-out (InOut) optional required Permitted with S7-1200 only, parameter assignment required Temporary (Temp) required required required S7-1500: Optional with optimized block access S7-1500: Optional with optimized block access WinCC Basic V13.0 System Manual, 02/2014 1165 Programming the PLC 9.1 Creating the user program See also Basics of block parameters (Page 1161) General rules for assigning parameters (Page 1162) Parameter assignment to functions (Page 1163) Access to block parameters during program execution Introduction Block parameters of functions and function blocks are processed differently during program execution. The type of access varies depending on the CPU family, block type and data type of the block parameter. We generally distinguish between the two following types of access: Parameters are transferred as parameter pointers A parameter pointer is transferred to the called block. This means that the called block can directly access the operand that is specified as actual parameter. Writing a parameter in the called block results in a change of the actual parameter in the calling block. Read access to a block parameter reads the actual parameter directly. Parameters are transferred as copy The value of the actual parameter is copied to the temporary data of the called blocks during a block call. This means that the called block always works with the value that the actual parameter had at the block call. It cannot directly access the operand that is specified as actual parameter. Writing a parameter in the called block does not result in a change of the actual parameter in the calling block. During read access, the formal parameter and not the actual parameter is accessed. The procedure for copying is as follows: - Input parameter: The value of the actual parameter is copied to the formal parameter of the called blocks during a block call. - Output parameter: The value of the formal parameter is copied to the actual parameter after leaving the block. - In/out parameter: The value of the actual parameter is copied to the formal parameter of the called block prior to the block call and copied back to the actual parameter after exiting the function. Parameter transfer for elementary data types The following table shows how the different CPU families transfer block parameters with elementary data type. Elementary data types are, for example, Bool, Int, Byte. 1166 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program Called block Actual parameter in the area S7-300/400 S7-1500 FC I, Q, M, P, L Pointer Pointer Partially qualified DB address (e.g. DBW 2) Pointer Partially qualified DB addresses are not supported in S7-1500. Fully qualified DB address (e.g. "MyDB".value), forwarded parameters of the caller, static parameters of the caller Copy Copy All actual parameters Copy Copy FB Parameter transfer for structured data types The following table shows how the different CPU families transfer block parameters with structured data type. Structured data types are data types that consist of several data elements, e.g. ARRAY or STRUCT. Called block Actual parameter in the area S7-300/400 S7-1500 FC IN, OUT, InOut Pointer Pointer FB IN, OUT Copy Copy InOut Pointer Pointer Forwarding of block parameters Basic information on forwarding block parameters Introduction Definition The "Forwarding" of block parameters is a special type of parameter use. In this case the block parameters of the calling block are forwarded to the parameters of the called block. The called block uses the values that are currently present at the block parameters of the calling block as the actual parameters. The following figure shows how the parameters of the function FC_10 are forwarded to the function FC_12: WinCC Basic V13.0 System Manual, 02/2014 1167 Programming the PLC 9.1 Creating the user program )XQFWLRQ )& )&B &DOO )XQFWLRQ )& )&B 7DJGHFODUDWLRQ 7DJGHFODUDWLRQ 3DUDPB ,QSXW $B3DUDP ,QSXW 3DUDPB 2XWSXW %B3DUDP 2XWSXW 3DUDPB ,QRXW &B3DUDP ,QRXW )&B $B3DUDP 3DUDPB %B3DUDP 3DUDPB &B3DUDP 3DUDPB Rules for LAD/FBD The following general rules apply in LAD and FBD: Input parameters can only be forwarded to input parameters. Output parameters can only be forwarded to output parameters. In/out parameters can be forwarded to all parameter types. In S7-300/400, the two block parameters must have the same data type. In S7-1200/1500, the parameters can also be converted according to the rules of implicit conversion. Rules for STL The following general rules apply in STL: Input parameters can only be forwarded to input parameters. Output parameters can only be forwarded to output parameters. In/out parameters can be forwarded to all parameter types. Both block parameters must have the same data type. In STL, this rule applies to all CPU families. Rules for SCL The rules for SCL are less stringent. So that programs from previous SCL versions can be taken over more easily, additional parameter transfer options are permissible, but subject to warning. You can, for example, forward an in/out parameter to an input parameter, but a warning is output as the transferred in/out parameter cannot be written by the program. Additional rules are described in detail in the following chapters. 1168 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program See also Calling a function by another function (Page 1169) Call of a function by a function block (Page 1170) Call of a function block by a function (Page 1171) Call of a function block by another function block (Page 1172) Calling a function by another function Permissible data types for the call of a function by another function Specific rules apply to the forwarding of formal parameters. The following table shows the rules according to which parameters can be forwarded in the various CPU families: FC calls FC Actual parameter (calling block) Input Data types Formal parameter s Standard data types (called block) Input ARRAY, STRUCT, STRING, WSTRING, DT S7-300/400 S7-1200 S7-1200 S7-1500 ANY, POINTER S7-1500 VARIANT Parameter types (TIMER, COUNTER, BLOCK_XX) S7-1200 S7-1500 S7-1500 Output S7-300/400 S7-1200 S7-1200 S7-1500 - S7-1200 S7-1200 as of V2 S7-1500 S7-1500 Output DB_Any - - - - - - - - S7-1500 S7-1500 InOut Input S7-300/400 S7-1200 S7-1200 S7-1500 S7-1500 S7-1200 S7-1500 S7-1500 InOut Output S7-300/400 S7-1200 S7-1200 S7-1500 - S7-1200 S7-1500 S7-1500 InOut InOut S7-300/400 S7-1200 S7-1200 S7-1500 S7-1500 S7-1200 S7-1500 S7-1500 See also Basic information on forwarding block parameters (Page 1167) WinCC Basic V13.0 System Manual, 02/2014 1169 Programming the PLC 9.1 Creating the user program Call of a function by a function block Permissible data types for the call of a function by a function block Specific rules apply to the forwarding of formal parameters. The following table shows the rules according to which parameters can be forwarded in the various CPU families: FB calls FC Actual parameter (calling block) Input Output InOut Data types Formal parameter s Standard data types (called block) Input Output Input ARRAY, STRUCT, STRING, WSTRING, DT S7-300/400 S7-300/400 S7-1200 S7-1200 S7-1500 S7-1500 S7-300/400 S7-300/400 S7-1200 S7-1200 S7-1500 S7-1500 S7-300/400 S7-1200 S7-1200 S7-1500 ANY, POINTER S7-1500 VARIANT Parameter types (TIMER, COUNTER, BLOCK_XX) S7-1200 S7-1500 S7-1500 - DB_Any S7-1200 S7-1200 as of V2 S7-1500 - - - - - - - - S7-1500 S7-1500 S7-1200 S7-1500 S7-1500 InOut Output S7-300/400 S7-1200 S7-1200 S7-1500 - S7-1200 S7-1500 S7-1500 InOut InOut S7-300/400 S7-1200 S7-1200 S7-1500 S7-1500 S7-1200 S7-1500 S7-1500 See also Basic information on forwarding block parameters (Page 1167) 1170 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program Call of a function block by a function Permissible data types for the call of a function block by a function Specific rules apply to the forwarding of formal parameters. The following table shows the rules according to which parameters can be forwarded in the various CPU families: FC calls FB Actual parameter (calling block) Input Data types Formal parameter s Standard data types (called block) Input ARRAY, STRUCT, STRING, WSTRING, DT S7-300/400 S7-1200 S7-1200 S7-1500 ANY, POINTER S7-1500 VARIANT Parameter types (TIMER, COUNTER, BLOCK_XX) S7-1200 S7-300/400 S7-1500 S7-1500 S7-1200 as of V2 S7-1200 - - - - - - - - S7-1500 Output Output S7-300/400 S7-1200 S7-1200 S7-1500 - DB_Any S7-1500 S7-1500 S7-1500 InOut Input S7-300/400 S7-1200 S7-1200 S7-1500 S7-1500 S7-1200 S7-1500 S7-1500 InOut Output S7-300/400 S7-1200 S7-1200 S7-1500 - S7-1200 S7-1500 S7-1500 InOut InOut S7-300/400 S7-1200 S7-1200 S7-1500 S7-1500 S7-1200 S7-1500 S7-1500 See also Basic information on forwarding block parameters (Page 1167) WinCC Basic V13.0 System Manual, 02/2014 1171 Programming the PLC 9.1 Creating the user program Call of a function block by another function block Permissible data types for the call of a function block by another function block Specific rules apply to the forwarding of formal parameters. The following table shows the rules according to which parameters can be forwarded in the various CPU families: FB calls FB Actual parameter (calling block) Input Output InOut Data types Formal parameter s Standard data types (called block) Input Output Input ARRAY, STRUCT, STRING, WSTRING, DT S7-300/400 S7-300/400 S7-1200 S7-1200 S7-1500 S7-1500 S7-300/400 S7-300/400 S7-1200 S7-1200 S7-1500 S7-1500 S7-300/400 S7-1200 S7-1200 S7-1500 ANY, POINTER S7-1500 - VARIANT Parameter types DB_Any (TIMER, COUNTER, BLOCK_XX) S7-1200 S7-300/400 S7-1500 S7-1500 S7-1200 as of V2 S7-1200 - - - - - - - - S7-1500 S7-1500 S7-1500 S7-1200 S7-1500 S7-1500 InOut Output S7-300/400 S7-1200 S7-1200 S7-1500 - S7-1200 S7-1500 S7-1500 InOut InOut S7-300/400 S7-1200 S7-1200 S7-1500 S7-1500 S7-1200 S7-1500 S7-1500 See also Basic information on forwarding block parameters (Page 1167) 1172 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program 9.1.1.4 Using and addressing operands Basic information about operands Introduction When you program instructions you must specify which data values the instruction should process. These values are referred to as operands. You can, for example, use the following elements as operands: PLC tags Constants Tags in instance data blocks Tags in global data blocks Absolute address and symbolic name Operands are identified by means of an absolute address and a symbolic name. You define the names and addresses in the PLC tag table or in the tag declaration of the blocks. Data blocks with optimized access (S7-1200, S7-1500) Data elements in data blocks with optimized access only receive a symbolic name and no absolute address in the declaration. For more information on this, refer to "See also". See also Displaying symbolic and absolute addresses (Page 1364) Basics of block access (Page 1151) Keywords SIMATIC recognizes a range of key words whose definitions are fixed and which have a certain meaning in the program. You should not use these keywords as names for tags or constants. Table of keywords The following table shows all keywords. WinCC Basic V13.0 System Manual, 02/2014 Keywords German mnemonics Keywords English mnemonics Description & & And logical operation of logical expressions A Q Output, bit A1 CC1 Condition code bit 1173 Programming the PLC 9.1 Creating the user program 1174 Keywords German mnemonics Keywords English mnemonics Description A0 CC0 Condition code bit AB QB Output, byte AD QD Output, double word AND AND And logical operation of logical expressions ANY ANY Data type, pointer AR1 AR1 Address Register 1 AR2 AR2 Address Register 2 ARRAY ARRAY Introduces the specification of an array and is followed by the index list between "[" and "]" AT AT Overlaying tag declaration AUTHOR AUTHOR Name of the author, company name, department name, or other name (max. 8 characters, no spaces) AW QW Output, word B B Byte BEGIN BEGIN Introduces the instruction part for code blocks or initialization part for a data block BIE BR Binary result BLOCK_FB BLOCK_FB Parameter type for specification of an FB BLOCK_FC BLOCK_FC Parameter type for specification of an FC BLOCK_SDB BLOCK_SDB Parameter type for specification of an SDB BOOL BOOL Data type BY BY Increment of the FOR loop BYTE BYTE Data type CALL CALL Call CASE CASE Introduction to the CASE statement CHAR CHAR Elementary data type CODE_VERSION1 CODE_VERSION1 Label, whether an FB is multiple instance capable or not. If you want to declare multiple instances, the FB must not have this characteristic. CONST CONST Start of the constant declaration CONTINUE CONTINUE Instruction to exit a loop in SCL COUNTER COUNTER Parameter type for specification of a counter DATA_BLOCK DATA_BLOCK Introduces the data block DATE DATE Data type WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program WinCC Basic V13.0 System Manual, 02/2014 Keywords German mnemonics Keywords English mnemonics Description DATE_AND_TIME DATE_AND_TIME Data type DB DB Data block DB_ANY DB_ANY Data type DBB DBB Data block, data byte DBD DBD Data block, data double word DBLG DBLG Data block length DBNO DBNO Data block number DBW DBW Data block, data word DBX DBX Data block, data bit DI DI Instance data block DIB DIB Instance data block, data byte DID DID Instance data block, data double word DILG DILG Instance data block length DINO DINO Instance data block number DINT DINT Data type DIW DIW Instance data block, data word DIX DIX Instance data block, data bit DO DO Introduction of the instruction part in FOR and WHILE instruction DT DT Data type DTL DTL Data type DWORD DWORD Data type E I Input (via process image), bit EB IB Input (via process image), byte ED ID Input (via process image), double word ELSE ELSE Alternative branch in IF and CASE statement ELSIF ELSIF Alternative condition of the IF instruction EN EN System operand of the EN/ENO mechanism ENO ENO System operand of the EN/ENO mechanism END_CASE END_CASE End of the CASE statement END_DATA_BLOCK END_DATA_BLOCK Ends the data block END_FOR END_FOR End of the FOR statement END_FUNCTION END_FUNCTION Ends the function END_FUNCTION_BLOCK END_FUNCTION_BLOCK Ends the function block END_IF END_IF End of the IF instruction END_ORGANIZATION_BLOCK END_ORGANIZATION_BLOCK Ends the organization block END_REPEAT END_REPEAT End of the REPEAT statement 1175 Programming the PLC 9.1 Creating the user program 1176 Keywords German mnemonics Keywords English mnemonics Description END_STRUCT END_STRUCT Ends the specification of a structure END_SYSTEM_FUNCTION END_SYSTEM_FUNCTION Ends the system function END_SYSTEM_FUNCTION_BL OCK END_SYSTEM_FUNCTION_BL OCK Ends the system function block END_TYPE END_TYPE Ends the PLC data type END_VAR END_VAR Ends a declaration block END_WHILE END_WHILE End of the WHILE instruction EW IW Input (via process image), word EXIT EXIT Instruction to exit a loop in SCL FALSE FALSE Predefined Boolean constant: Logical condition false, value equal to 0 FAMILY FAMILY Block family name: e.g. controller FB FB Function block FC FC Function FOR FOR Introduction of the FOR statement FUNCTION FUNCTION Introduces the function FUNCTION_BLOCK FUNCTION_BLOCK Introduces the function block GOTO GOTO Introduction of the GOTO statement IF IF Introduction of the IF instruction INSTANCE INSTANCE Data type INT INT Data type KNOW_HOW_PROTECT KNOW_HOW_PROTECT Block protection L L Local data bit LB LB Local data byte LD LD Local data double word LDT LDT Data type LINT LINT Data type LTIME LTIME Data type LTOD LTOD Data type LW LW Local data word LWORD LWORD Data type M M Memory bit MB MB Memory byte MD MD Memory double word MOD MOD Modulo operator MW MW Memory word NAME NAME Block name NETWORK NETWORK Network NOT NOT Logic inversion WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program WinCC Basic V13.0 System Manual, 02/2014 Keywords German mnemonics Keywords English mnemonics Description NULL NULL Zero pointer OB OB Organization block OF OF Introduction of the data type specification / Introduction of the instruction part of the CASE statement OR OR Or logical operation of logical expressions ORGANIZATION_BLOCK ORGANIZATION_BLOCK Introduces the organization block OS OS Save overflow OV OV Overflow PA PQ Output (direct peripherals), bit PAB PQB Output (direct peripherals), byte PAD PQD Output (direct peripherals), double word PAW PQW Output (direct peripherals), word PE PI Input (direct peripherals), bit PEB PIB Input (direct peripherals), byte PED PID Input (direct peripherals), double word PEW PIW Input (direct peripherals), word POINTER POINTER Data type READ_ONLY READ_ONLY Write protection for data blocks REAL REAL Data type REPEAT REPEAT Introduction of the REPEAT statement RET_VAL RET_VAL Return value RETURN RETURN RETURN statement in SCL S5T S5T Syntax for data type S5TIME S5TIME S5TIME Data type S7_ S7_ Keywords for system attributes SDB SDB System data block SFB SFB System function block SFC SFC System function SINT SINT Data type STRING STRING Data type STRUCT STRUCT Introduces the specification of a structure and is followed by a list of components STW STW Status word SYSTEM_FUNCTION SYSTEM_FUNCTION System function SYSTEM_FUNCTION_BLOCK SYSTEM_FUNCTION_BLOCK System function block T T Time element (timer) 1177 Programming the PLC 9.1 Creating the user program 1178 Keywords German mnemonics Keywords English mnemonics Description THEN THEN Introduction of the instruction part of an IF instruction THIS THIS Syntax for access to an ARRAY data block TIME TIME Elementary data type for time information TIME_OF_DAY TIME_OF_DAY Data type TIMER TIMER Parameter type for specification of a timer TITLE TITLE Optional block title or network title TO TO Definition of the full-scale value of a FOR statement TOD TOD Data type TRUE TRUE Predefined Boolean constant: Logical condition true, value not equal to 0 TYPE TYPE Introduction of the PLC data type UDT UDT Global or PLC data type UDINT UDINT Data type UINT UINT Data type ULINT ULINT Data type UNLINKED UNLINKED Marking 'non runtime-related' UNTIL UNTIL End of the instruction part of a REPEAT statement USINT USINT Data type UO UO Query after (Q1=1) AND (Q0=1) VAR VAR Introduces a declaration block VAR_IN_OUT VAR_IN_OUT Introduces a declaration block VAR_INPUT VAR_INPUT Introduces a declaration block VAR_OUTPUT VAR_OUTPUT Introduces a declaration block VAR_TEMP VAR_TEMP Introduces a declaration block VARIANT VARIANT Data type VERSION VERSION Version number of the block VOID VOID Function has no return value WCHAR WCHAR Data type WSTRING WSTRING Data type WHILE WHILE Introduction of a WHILE instruction WORD WORD Data type XOR XOR Logic operation Z C Counter WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program Using tags within the program Definition A variable is a placeholder for a data value that can be changed in the program. The format of the data value is defined. The use of variables makes your program more flexible. For example, you can assign different values to variables that you have declared in the block interface for each block call. As a result, you can reuse a block you have already programmed for various purposes. A variable consists of the following elements: Name Data type Absolute address - PLC tags and DB tags in blocks with standard access have an absolute address. - DB variables in blocks with optimized access have no absolute address. Value (optional) Declaring Variables You can define variables with different scopes for your program: PLC tags that apply in all areas of the CPU DB variables in global data block that can be used by all blocks throughout the CPU. DB tags in instance data blocks that are predominantly used within the block in which they are declared. The following table shows the difference between the variable types: PLC tags Range of application Permissible characters Use Are predominantly used in the block in which they Can be used by all blocks on the CPU. are defined. The name is unique within the CPU. The name is unique within the instance DB. Letters, numbers, special characters Quotation marks are not permitted. Letters, numbers, special characters Variables in global DBs Can be used by all blocks on the CPU. The name is unique within the global DB. Letters, numbers, special characters Reserved keywords are not permitted. Reserved keywords are not permitted. Reserved keywords are not permitted. I/O signals (I, IB, IW, ID, Q, QB, QW, QD) Static data Bit memory (M, MB, MW, MD) Location of definition Variables in instance DBs Are valid throughout the entire CPU. PLC tag table WinCC Basic V13.0 System Manual, 02/2014 Block parameters (input, output and in-out parameters), Static data of a block Block interface Declaration table of the global DB 1179 Programming the PLC 9.1 Creating the user program See also Keywords (Page 1173) Basic information about operands (Page 1173) Displaying symbolic and absolute addresses (Page 1364) Valid names of PLC tags (Page 1307) Permissible addresses and data types of PLC tags (Page 1308) Constants Basics of constants Definition Constants are data with a fixed value that you cannot change during program runtime. Constants can be read by various program elements during the execution of the program but cannot be overwritten. There are defined notations for the value of a constant, depending on the data type and data format. A distinction is made between the typed and non-typed notation. Non-typed constants In the non-typed notation, you only enter the value of the constant without a data type. Nontyped constants do not receive their type until the first arithmetic or logical operation in which they are used. The example below shows the non-typed notation: SCL #My_Int1 := #My_Int2 + 12345 (*The data type of the constant "12345" results from the addition with My_Int 2. "12345" receives the data type INT.*) #My_Real1 := #My_Real2 + 12345 (*The data type of the constant "12345" results from the addition with My_Real2. "12345" receives the data type REAL.*) Typed constants In the typed notation, you specify a data type in addition to the value of the constant. The example below shows the typed notation: SCL #My_Int1 := 1180 INT#12345 (*The data type of the constant is always INT.*) WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program Note Constants of the BOOL type Constants of the BOOL type may not be used as inputs in LAD or FBD in S7-300/400. Additional information Additional information on the data types of constants, their input formats and value ranges: Data types See also Layout of the block interface (Page 1375) Declaration of symbolic names for constants Symbolic constants You have the option of declaring symbolic names for constants and thus making constant values available under a name in the program. This makes a program more readable and easier to maintain when changing constant values. A symbolic constant consists of the following elements: Name Data type Symbolic constants always have a data type; non-typed notation is not possible for symbolic constants. Constant value You can select any value from the value range of the specified data type as constant value. For information on the value ranges, refer to the "Data types" chapter. Declaration of constants You can define constants with different scopes of validity: Global constants that apply to all areas of the CPU Local constants that only apply within a block The table below shows the difference between the constant types: WinCC Basic V13.0 System Manual, 02/2014 1181 Programming the PLC 9.1 Creating the user program Scope of validity Global constants Local constants Are valid throughout the entire CPU Are valid only in the block in which they were declared. The name is unique within the CPU. The name is unique within the block. Permitted characters The permitted characters in The permitted characters in constant names are letters, constant names are letters, digits and special characters. digits and special characters. Location of definition "Constants" tab from the PLC tag Block interface table Representation In quotation marks, for example.: Prefixed with a number sign, for example: "Glob_Const" #Loc_Const Note Downloading constant declarations (S7-300/400) Local and global constant declarations are not downloaded into the CPU. If you download a program from a device, the constant declarations may no longer be available. Additional information Additional information on the procedure for declaring constants: Auto-Hotspot Auto-Hotspot Auto-Hotspot Data types of constants Permitted data types For constants, all basic data types as well as all derived data types are permitted: Binary numbers Bit strings Integers Floating-point numbers Timers Date and time Character strings All general rules for explicit and implicit type conversion apply. 1182 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program Data types of non-typed constants Non-typed constants do not contain an explicit type specification. They do not receive their type until the first arithmetic or logical operation in which they are used. The example below shows how non-typed constants are used: SCL #My_Int1 := #My_Int2 + 12345 (*The data type of the constant "12345" results from the addition with My_Int 2. "12345" receives the data type INT.*) #My_Real1 := #My_Real2 + 12345 (*The data type of the constant "12345" results from the addition with My_Real2. "12345" receives the data type REAL.*) Note STEP 7 always uses the data type with the highest possible precision Unless the data type of a constant can be clearly defined in an expression, the data type with the highest precision available on the current CPU is used. Example: #My_Real := #My_Int / 3.5 In this expression an integer tag is combined with a non-typed floating point constant. In S7-300/400 the right part of the assignment is calculated in the REAL format. In S7-1200/1500, calculation is performed using the highest possible precision, which in this case means LREAL. As a result, the assignment to a REAL tag is invalid or generates a warning. To precisely define the data type of a constant, use the typed notation. Example: #My_Real := #My_Int / REAL#3.5 Additional information Additional information on the data types of constants, their input formats and value ranges: Data types Examples of using constants Use in instructions, assignments and expressions Constants can be used in place of tags in instructions or assignments. You can also use constants in expressions in SCL. But because constants cannot be written, they may only be used as inputs. WinCC Basic V13.0 System Manual, 02/2014 1183 Programming the PLC 9.1 Creating the user program The example below shows possible uses of constants: SCL #My_Int := 3; #My_Real1 := #My_Real2 * 3; #My_Real1 := #My_Real2 * #My_local_const; #My_Real1 := #My_Real2 * "My_global_const"; Use as a default value You can also use a constant as the default value of a tag. To do so, enter either the value or the symbolic name of the constant in the "Default value" column of the block interface. The data type of the constant must match the data type of the tag or be convertible with it according to the implicit conversion with IEC check. Name conflicts can occur if you have declared a local and a global constant with the same symbolic name and have used this doubly specified name as the default value of a tag. In this case, the local constant is automatically used. Use as an ARRAY limit Local constants of data type INT or DINT can also be used as ARRAY limits. The example below shows the use of local constants as ARRAY limits: SCL Array[My_local_const1..My_local_const1] of REAL Note Constants as ARRAY limits Note the following information on the topic of "Constants as ARRAY limits": Global constants are not permitted as ARRAY limits. Local constants which are used as ARRAY limits cannot be changed if the memory reserve of the block is activated. 1184 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program Addressing operands Addressing global variables Addressing global variables To address a global PLC variable, you can use the absolute address or the symbolic name. Note The LWORD, LINT, ULINT, LREAL, LTIME, LTOD and LDT data types can only be addressed by means of their symbolic name. Addressing global variables in symbolic form When you use addressing in symbolic form, you enter the variable name from the PLC tag table. The symbolic name of global variables are automatically enclosed in quotation marks. You address structured tags that are based on a PLC data type with the symbolic name of the PLC tag. You can also indicate the names of the individual components separated by a dot. Addressing global variables in absolute form When you use addressing in absolute form, you enter the address of the variables from the PLC tag table. The absolute address uses numerical addresses starting with zero for each operand range. The address identifier % is set automatically as prefix for the absolute address of global tags. Examples The following examples show applications of symbolic and absolute addressing: Addressing Description %Q1.0 Absolute address: Output 1.0 %I16.4 Absolute address: Input 16.4 %IW4 Absolute address: Input word 4 "Motor" Symbolic address "Motor" "Value" Symbolic address "Value" "Structured_Tag" Symbolic address of a tag that is based on a PLC data type "Structured_Tag".Component Symbolic address of the component of a structured tag. See also: Permissible addresses and data types of PLC tags (Page 1308) WinCC Basic V13.0 System Manual, 02/2014 1185 Programming the PLC 9.1 Creating the user program See also Displaying symbolic and absolute addresses (Page 1364) Accessing I/O devices (Page 1186) Accessing I/O devices Description The process image of the CPU is updated once in a cycle. In time-critical applications, however, it can be that the current state of a digital input or output has to be read or transferred more often than once per cycle. For this purpose you can use a suffix for I/O access identifiers on the operand to directly access the I/O. If you want to read the input directly from the peripherals, use the peripheral inputs memory area (PI) instead of the process input image (I). The peripherals memory area can be read as a bit, byte, word, or double word. If you want to write directly to the output, use the peripheral output (PQ) memory area instead of the process output image (Q). The peripheral output memory area can be written as a bit, byte, word, or double word. To read or write a signal directly from a peripheral input, you can add the suffix for I/O access ":P", to the operand. Components of structured PLC tags can also be addressed with ":P". However, access to the higher-level tag with ":P" is not possible. WARNING Direct writing of the I/O Immediate writing to the I/O can lead to hazardous states, for example when writing multiple times to an output in one program cycle. Syntax <Operand>:P Example The following example shows applications of I/O access identifiers: 1186 Addressing Description "Motor" Addresses the "Motor" tag in the process image. "Motor":P Addresses the "Motor" tag in the I/O memory area (PI or PQ). "Structured_Tag".Component Addresses the component of a structured PLC tag in the process image. WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program Addressing Description "Structured_Tag".Component:P Addresses the component of a structured PLC tag in the I/O memory area (PI or PQ). See also Addressing global variables (Page 1185) Addressing variables in data blocks Addressing variables in global data blocks Description Tags in global data blocks can be addressed in symbolic or absolute form. For symbolic addressing, you use the name of the data block and the name of the tag, separated by a dot. The name of the data block is enclosed in quotation marks. For absolute addressing, you use the number of the data block and the absolute address of the tags in the data block, separated by a dot. The address identifier % is set automatically as prefix for the absolute address. The S7-1200/1500 provides you with an option of accessing a data block that is not yet known during programming. For this purpose, create a block parameter of data type DB_Any in the block interface of the accessing block. The data block name or data block number is transferred to this parameter during runtime. In order to access the internal tags of the data block, use the name of the block parameter of data type DB_Any and the absolute address of the tag, separated by a dot. Note Absolute addressing is not possible for the following tags: Tags in blocks with optimized access. Tags of data type LWORD, LINT, ULINT, LREAL, LTIME, LTOD and LDT. Best practice is to use the more convenient symbolic addressing for these tags. ARRAY data blocks ARRAY data blocks are a particular type of global data block. These consist of an ARRAY of any data type. For example, an ARRAY of a PLC data type (UDT) is possible. You address elements in ARRAY data blocks with the help of the keyword "THIS". The index is then specified in square brackets. The index can be a constant as well as a tag. Integers with a width of up to 32 bits are permitted as tags for the index. Extended options for addressing ARRAY DBs are available in the "Move" section of the "Instructions" task card. These instructions give you the option, for example, to also address the DB name indirectly. WinCC Basic V13.0 System Manual, 02/2014 1187 Programming the PLC 9.1 Creating the user program Syntax "<DBname>".TagName %<DBnumber>.absoluteAddress #<DBAny_name>.%absoluteAddress "<ArrayDBname".THIS[#i].<Component>.<ComponentElement> SCL: "<ArrayDBname"."THIS"[#i].<Component>.<ComponentElement> The following table show the possible absolute addresses of tags in data blocks: Data type Absolute address Example Description BOOL %DBn.DBXx.y %DB1.DBX1.0 Data bit 1.0 in DB1 BYTE, CHAR, SINT, USINT %DBn.DBBy %DB1.DBB1 Data bit 1 in DB1 WORD, INT, UINT %DBn. DBWy %DB1.DBW1 Data word 1 in DB1 DWORD, DINT, UDINT, REAL, TIME %DBn.DBDy %DB1.DBD1 Data double word 1 in DB1 Example The following examples show the addressing of tags in global data blocks: Addressing Description "Motor".Value Symbolic addressing of the "Value" tag in the "Motor" global data block. %DB1.DBX1.0 Absolute addressing of the "DBX1.0" tags in the "DB1" global data block. #MyDBAny.%DBX30.0 Absolute addressing of the "DBX30.0" tag in the global DB that is transferred at runtime at the "MyDBany" parameter. "MyARRAY_DB".THIS[#MyIndex].MyCom ponent.MyComponentElement Addressing an ARRAY data block. The ARRAY index is specified with the "MyIndex" tag. The ARRAY element has two additional substructures: "MyComponent" and "MyComponentElement". See also Addressing structured variables (Page 1190) Addressing areas of a tag with slice access (Page 1192) Basics of indirect addressing (Page 1196) Addressing instance data (Page 1189) 1188 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program Addressing instance data Description You can address data elements from the interface of the current block. These tags are stored in the instance data block. Note Tags in blocks with optimized access can only be addressed in symbolic form. To address a tag from the interface of the current block, enter the character # followed by the symbolic tag name. You can also access the tags of a multiple instance block. Within the multiple instance block, also use the character # followed by the tag name to address the data. You access the data of the multiple instance block from the calling block using #<Multiple instanceName.TagName>. Syntax Use the following syntax for addressing tags in instance data blocks: #<TagName> #<Multiple instanceName.TagName> Examples The following examples show the addressing of tags in instance data blocks: Addressing Description #Value Addressing the "Value" tag in the instance data block. #On Addressing the "On" tag within the multiple instance block #Multi.On Addressing the "On" tag of the multiple instance block from the calling block See also Addressing variables in global data blocks (Page 1187) Addressing structured variables (Page 1190) Addressing areas of a tag with slice access (Page 1192) Basics of indirect addressing (Page 1196) WinCC Basic V13.0 System Manual, 02/2014 1189 Programming the PLC 9.1 Creating the user program Addressing structured variables Addressing data elements of an ARRAY You access an element in an ARRAY using the syntax ArrayName[i,j,k...]. The index of the element is specified in square brackets. The index includes an integer value (-2147483648 ... 2147483647) for each ARRAY dimension. Access errors result when you access an element during runtime which is located outside the declared ARRAY limits. The various CPU families react differently to violations of the ARRAY limits: S7-300/400 - The CPU changes to "STOP" mode. - You can program the program execution error OB (OB 85) to prevent this. - In SCL, you also have the option of enabling the attribute "Check ARRAY limits" in the block properties. This causes the enable output ENO to be set to FALSE in the case of ARRAY access errors. S7-1200 - The CPU generates a diagnostic buffer entry and remains in "RUN" mode. S7-1500 - The CPU changes to "STOP" mode. - You can program the programming error OB (OB 121) to prevent this. - You also have the option of programming the local error handling with the instructions "GET_ERROR: Get error locally" or "GET_ERROR_ID: Get error ID locally". Note Monitoring ARRAY access errors with ENO The enable output ENO is not set to the signal state FALSE if the ARRAY limits are violated during execution of an instruction. The only exception is SCL blocks on CPUs of the S7-300/400 series for which the block property "Check ARRAY limits" is set. See also: Auto-Hotspot Indirect indexing of ARRAY components (Page 1198) Addressing ARRAY data blocks ARRAY data blocks are a particular form of the ARRAY. ARRAY data blocks are global data blocks that consist of exactly one ARRAY. You address elements in ARRAY data blocks using the following syntax: "<GlobArrayDBname".THIS[#i].<componentname>."<elementname>" SCL: 1190 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program "<GlobArrayDBname"."THIS"[#i].<componentname>."<elementname>". The "Move" section of the "Instructions" task card offers extended options for addressing ARRAY DBs. These instructions give you the option, for example, to also address the DB name indirectly. Addressing data elements in structures You access individual elements in a structure using StructureName.ElementName. See also: Auto-Hotspot Addressing data elements of an PLC data type The syntax PLCDataTypeName.ElementName is used to access elements of a PLC data type. See also: Auto-Hotspot Addressing individual characters of a STRING or WSTRING Use the syntax StringName[i] to access an individual character of a STRING or WSTRING tag. The counting index "i" begins with "1". Thus, you access the first character of the string with StringName[1]. You cannot access individual characters of a STRING or WSTRING constant. Errors result when you access a character during runtime which is located outside the STRING length. The various CPU families react differently to violations of the STRING length: S7-300/400 - If the instruction has the enable output ENO, ENO is set to the signal state FALSE. - If the instruction does not have an enable output ENO, violation of the STRING length is not monitored: If access takes place outside the STRING, the wrong memory area is accessed. If the access takes place outside the data block, the CPU goes to STOP. You can program the program execution error OB (OB 85) to prevent this. S7-1200/1500 - If the access takes place outside the declared length, the CPU goes to STOP. You can choose whether you want to respond to violations with the global error handing of the CPU or with separate local error handling. - If the access is located within the declared STRING length but outside the actual STRING length, violation of the STRING length is not monitored and the CPU does not go to STOP. You receive the character '$00' or '$0000' with read access; write access is not executed. If the instruction has the enable output ENO, ENO is set to the signal state FALSE. See also: WinCC Basic V13.0 System Manual, 02/2014 1191 Programming the PLC 9.1 Creating the user program Auto-Hotspot Examples: The following examples show the addressing of structured data type tags: Addressing Description Motor.Value_1x3[2] Addressing of a one-dimensional array Motor.Value_2x4[2,4] Addressing of a two-dimensional array Motor.Value_4x7[2,4,1,3] Addressing of a four-dimensional array Batch_1.Temperature Addressing of the element "Temperature" in the structure "Batch_1" Values.Temperature Addressing of the "Temperature" element in the "Values" tag, which is based on a PLC data type. STRING[3] Addresses the third character of the string. See also Basics of indirect addressing (Page 1196) Addressing areas of a tag with slice access Description You have the option to specifically address areas within declared tags. You can access areas of the 1-bit, 8-bit, 16-bit, or 32-bit width. The type of access is referred to as "slice access". Constants cannot be addressed by slice access. Syntax The following syntax is used for addressing: <Tag>.X<Bit number> <Tag>.B<BYTE number> <Tag>.W<WORD number> <Tag>.D<DWORD number> The syntax has the following components: 1192 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program Part Description <Tag> Tag that you access. The tag must be of the "Bit string" data type. In the case of activated IEC check, the access to tags of the "Integer" data type is also possible. X ID for the access width "Bit (1Bit)" B ID for the access width "Byte (8 Bit)" W ID for the access width "Word (16 Bit)" D ID for access width "DWord (32-bit)" <BIT number> Bit number within <tag> that is accessed. Number 0 accesses the least significant BIT. <BYTE number> Byte number within <tag> that is accessed. The number 0 accesses the least significant BYTE. <WORD number> Word number within <tag> that is accessed. The number 0 accesses the least significant WORD. <DWORD number> DWord number within <tag> that is accessed. The number 0 accesses the least significant DWORD. Examples The following examples show the addressing of individual bits: Addressing Description "Engine".Motor.X0 "Motor" is a tag of the BYTE, WORD, DWORD or LWORD data type in the global data block "Engine". "Engine".Motor.X7 X0 addresses the bit address 0, X7 the bit address 7 within "Motor". "Engine".Speed.B0 "Engine".Speed.B1 "Speed" is a tag of the WORD, DWORD or LWORD data type in the global data block "Engine". B0 addresses the byte address 0, B1 the byte address 1 within "Speed". "Engine".Fuel.W0 "Engine".Fuel.W1 "FUEL" is a tag of the DWORD or LWORD data type in the global data block "Engine". W0 addresses the word address 0, W1 the word address 1 within "Fuel". "Engine".Data.D0 "Engine".Data.D1 "Data" is a tag of the LWORD data type in the global data block "Engine". D0 addresses the double word address 0, D1 the double word address 1 within "Data". Overlaying tags with AT Description To access data areas within a declared tag, you can overlay the declared tags with an additional declaration. This provides you with the option of addressing an already declared tag with a different data type. You can, for example, address the individual bits of a tag of WORD data type with an ARRAY of BOOL. WinCC Basic V13.0 System Manual, 02/2014 1193 Programming the PLC 9.1 Creating the user program Rules The following general rules are valid for tag overlaying: Overlaying is possible in S7-1200 and S7-1500 in STL, LAD, FBD and GRAPH. SCL supports overlaying in all CPU families. Overlaying of tags is possible in the following blocks: - In code blocks with standard access - In code blocks with optimized access for tags with the retain setting "Set in IDB" The data width of the overlaying tag must be equal to or less than that of the overlaid tag. It is not possible to overlay tags of the VARIANT and INSTANCE data types. Blocks from libraries which are declared as parameters in the interface cannot be overlaid. Structured PLC tags that are declared as parameters in the interface cannot be overlaid. Note S7-1200/1500: Using AT in FCs The data widths of the overlaying tag and the overlaid tag must be identical for FCs in S7-1200/1500. If this is not possible in your program, you can also address areas within existing tags with the .X, .B, .W or .D syntax. See also: Addressing individual areas of a tag (Page 1192) The following combination rules are also valid: Overlaying tag Overlaid tag Elementary Structured * Any/Pointer DB_ANY FB Input Elementary x x Structured * x x Any/Pointer Temp x x Elementary x x Structured x x Any/Pointer Static, Output x x x x Elementary x x x Structured x x x Any/Pointer InOut Elementary x Structured x x Any/Pointer FC Temp Elementary x x Structured x x Any/Pointer 1194 x x WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program Input, Output, InOut Overlaying tag Overlaid tag Elementary x x (both tags must have the same bit width) Structured x x Any/Pointer OB Temp Elementary x x Structured x x Any/Pointer x x * Structured data types consist of several data elements, e.g. ARRAY or STRUCT. Declaration To overlay a tag, declare an additional tag directly after the tag that is to be overlaid and identify it with the keyword "AT". Example The following figure shows the declaration of an overlaid tag in the interface of a FB: When a block is called with the shown tag declaration, the "MyByte" tag is assigned. Within the block there are now two options for interpreting the data: as a byte As one-dimensional ARRAY of BOOL WinCC Basic V13.0 System Manual, 02/2014 1195 Programming the PLC 9.1 Creating the user program Addressing operands indirectly Basics of indirect addressing Introduction Indirect addressing offers the option of addressing operands whose address is not calculated until during runtime. With indirect addressing, program sections can be executed several times and a different operand can be used during each run. WARNING Risk of access errors Since operands are only calculated during runtime with indirect addressing, there is a risk that access errors may occur and that the program will operate with incorrect values. In addition, memory areas may inadvertently be overwritten with incorrect values. The automation system can then react in unexpected manner. Therefore, use indirect addressing only with caution. Indirect addressing Basics of indirect addressing General indirect addressing options in S7-1200 and S7-1500 The following indirect addressing options are available in all programming languages: Indirect addressing via pointer Indirect indexing of ARRAY components Indirect addressing of a data block via DB_ANY data type. 1196 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program Language-specific options of indirect addressing The following specific addressing options are also available in the various programming languages: In STL, you can address operands indirectly via the address register. In SCL, you can read or write a variable memory area with the following instructions: - POKE - Write memory address - POKE_BOOL - Write memory bit - PEEK - Read memory address - PEEK_BOOL - Read memory bit - POKE_BLK - Write memory area For a detailed description of these addressing options, refer to "See also". See also Addressing variables in global data blocks (Page 1187) POKE: Write memory address (Page 2397) POKE_BOOL: Write memory bit (Page 2399) PEEK: Read memory address (Page 2393) PEEK_BOOL: Read memory bit (Page 2395) POKE_BLK: Write memory area (Page 2400) Indirect addressing via pointer (Page 1197) Indirect indexing of ARRAY components (Page 1198) Indirect addressing in STL (Page 1202) Indirect addressing via pointer Description For indirect addressing, a special data format is required that contains the address and possibly also the range and the data type of an operand. This data format is referred to as pointer. The following types of pointers are available to you: POINTER (S7-1500) ANY (S7-1500, only for blocks with standard access) VARIANT (S7-1200/1500) WinCC Basic V13.0 System Manual, 02/2014 1197 Programming the PLC 9.1 Creating the user program For more information on the pointer data types, refer to "See also". Note In SCL the use of the POINTER is restricted. The only option available is to forward it to the called block. Example The following example shows an indirect addressing with an area-internal pointer: Addressing in STL Explanation L P#10.0 // Load pointer (P#10.0) in accumulator 1 T MD20 // Transfer pointer to the operand MD20 L MW [MD20] // Load MW10 in accumulator 1 .... // Any program L MD [MD20] // Load MD10 in accumulator 1 .... // Any program = M [MD20] // If RLO=1, set the memory bit M10.0 The pointer P#10.0 is transferred to the operand MD20. If the operand MD20 in square brackets is programmed, this will be replaced in runtime by the address that is contained in the pointer. See also Basics of indirect addressing (Page 1196) Indirect indexing of ARRAY components Description For addressing the components of an ARRAY, you can specify tags of the integer data type as well as constants as the index. Integers with a length of up to 32 bits are allowed here. When tags are used, the index is calculated during runtime. You can, for example, use a different index for each cycle in program loops. Note When you call a block and transfer an indirectly indexed ARRAY component ("<Data block>".<ARRAY>["i"]) to it as in/out parameter (InOut), you cannot change the value of the index tag [i] while the block is being executed. The value is therefore always written back to the same ARRAY component from which it was read. 1198 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program Syntax The following syntax is used for the indirect indexing of a ARRAY: "<Data block>".<ARRAY>["i"] // one-dimensional ARRAY "<Data block>".<ARRAY>["i"] // one-dimensional ARRAY of STRUCT "<Data block>".<ARRAY>["i"] // multidimensional ARRAY "<Data block>".<ARRAY>["i"] // multidimensional ARRAY of STRUCT The syntax has the following components: Part Description Data block Name of the data block in which the ARRAY is located ARRAY Tag of the ARRAY data type i, j PLC tags of the integer data type that are used as pointers a Additional partial tag of the structure Examples The following example shows indirect array indexing of an ARRAY component in STL: Several axes traverse at different angles. The values for axis number and angle are stored in the two-dimensional ARRAY "control_axis". You can use the "SEL" instruction to select the components of the "control_axis" ARRAY to be written at the "#out" output parameter. The axis number is defined by the constants "Constant_Axis_NoX" and "Constant_Axis_NoY"; the angle is defined by the "#Angle" tag. Addressing in STL CALL SEL value_type:=Int G :="Select" IN0 :=#control_axis["Constant_Axis_NoX", #Angle] IN1 :=#control_axis["Constant_Axis_NoY", #Angle] OUT :=#out The following examples are based on SCL and demonstrate indirect indexing of an ARRAY component. "MOTOR" is a one-dimensional ARRAY_of_INT with three rows. "VALUES" is a PLC tag of data type "Integer". WinCC Basic V13.0 System Manual, 02/2014 Addressing in SCL Explanation MOTOR[2] := VALUES; (*Direct addressing: Assignment of VALUES to the second row of the ARRAY MOTOR*) MOTOR["Tag_1"] := VALUES; (*Indirect addressing: Assignment of VALUES to the rows of ARRAY MOTOR*) specified by "Tag_1" 1199 Programming the PLC 9.1 Creating the user program Addressing in SCL Explanation #MOTOR["Tag_2"+"Tag_3"] := #Values; (*Indirect addressing: Assignment of VALUES to the row of the MOTOR*) ARRAY specified by the expression "Tag_2"+"Tag_3" The following example shows the indirect indexing of an ARRAY component as an example of LAD. "ARRAY" is a three-dimensional ARRAY. "Tag_1", " "Tag_2" and ""Tag_3" are PLC tags of the "Integer" data type. Depending on their values, one of the "ARRAY" components will be copied to the "MyTarget" tag. 7DJ,Q 0\'%$55$<>7DJB 7DJB7DJB@ 029( (1 (12 ,1 287 7DJ2XW 0\7DUJHW Indexing ARRAY components using the "FieldRead" and "FieldWrite" instructions You may also use the following instructions for indirect indexing of ARRAY components in LAD and FBD: FieldWrite - Write field FieldRead - Read field For more information on these instructions, refer to the "References" chapter. Additional information For more information on the ARRAY data type, refer to "See also". See also Basics of indirect addressing (Page 1196) Addressing structured variables (Page 1190) Indirect addressing of individual characters of a STRING Description For addressing the individual characters of a STRING or WSTRING, you can specify constants and also tags as the index. The tags must be of the Integer data type. When tags are used, the index is calculated during runtime. You can, for example, use a different index for each cycle in program loops. 1200 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program If you transfer a STRING or WSTRING with variable index to an in/out parameter during a block call, please note that: The index tag [i] is read once at the start of the block call and cannot be changed by the called block while it is being executed. Note Monitoring STRING access in runtime When a STRING or WSTRING that exceeds the defined length is written in runtime, unwanted reactions may occur in the program. Violation of the STRING or WSTRING length is monitored in S7-1200/1500. You can choose whether you want to respond to violations with the global error handing of the CPU or with separate local error handling. Syntax The following syntax is used for the indirect indexing of a STRING or WSTRING: "<Data block>".<STRING>["i"] "<Data block>".<WSTRING>["i"] Example The indirect indexing of a STRING is illustrated below based on the example of SCL. "STRING" is a tag of the STRING data type. "Tag_1" is a PLC tag of the "Integer" data type. Addressing in SCL Description STRING["Tag_1"] := CHARACTER; (*Indirect addressing: Assignment of "CHARACTER" to the characters of the *) STRING specified by "Tag_1" Additional information For additional information on the STRING data type, refer to "See also". See also STRING (Page 1231) Indirect addressing in STL Basic information about address registers Introduction Two address registers are available for the indirect addressing of operands: address register 1 (AR1), and address register 2 (AR2). The address registers are equal and are 32 bits in length. You can store area-internal and cross-area pointers in the address registers. To define the address of an operand, you can call the stored data in the program. WinCC Basic V13.0 System Manual, 02/2014 1201 Programming the PLC 9.1 Creating the user program Data is exchanged between the registers and the other available memory areas with the assistance of load and transfer instructions. Note In S7-1500, special rules apply to data exchange via address register and data block register: The values in the registers do not remain in existence beyond the block limits. The registers are reset when the language is changed within a block. You can only reference data in blocks with optimized access if these have the retain setting "Set in IDB". It is not possible to reference local data in blocks with optimized access with the help of the address registers (across areas). Additional information For more information on the statements that address registers use and on indirect addressing, refer to "See also". See also Indirect addressing in STL (Page 1202) Addressing areas of a tag with slice access (Page 1192) Indirect addressing in STL In STL, the following options are available for indirect addressing: Memory-indirect addressing Register-indirect area-internal addressing Register-indirect cross-area addressing Memory-indirect addressing In the case of memory-indirect addressing, you store the address in a tag. The tag can be of WORD or DWORD data type. The tag can be located in the memory areas "Data" (DB or DI), "Bit memory" (M) or "Temporary local data" (L). In S7-1500, FB parameters can also be used to store the address. If the tag is located in a data block, it must be a data black with standard access. The following example shows applications of memory-indirect addressing: 1202 Addressing in STL Explanation U E [MD 2] // Execute an AND logic operation with a variable input bit. The address of the input bit is located in the memory double word MD2. = DIX [DBD 2] // Assign the RLO to a variable data bit. The address of the data bit is located in the data double word DBD2. WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program Addressing in STL Explanation L EB [DID 4] // Load a variable input byte to ACCU 1. The address of the input byte is located in the instance double word DID4. AUF DB [LW 2] // Open a variable data block. The number of the data block is located in the local data word LW2. Register-indirect area-internal addressing Register-indirect addressing uses one of the address registers (AR1 or AR2) to pick up the address of the operand. In the case of register-indirect, area-internal addressing, you index only the bit address and the byte address via the address register (e.g. P#10.0). You do not enter the memory area for which the address in the address register is to apply until during programming of the instruction. The address in the address register then moves to the memory area specified in the instruction. Possible memory areas are "Inputs" (I), "Outputs" (Q), "I/O" (PI or PQ), "Bit memory" (M), "Temporary local data" (L) and "Data" (DB or DI). If the operand is located in a data block, it must be a data black with standard access. When you enter register-indirect, area-internal addressing, specify an offset after the specification of the address register. This offset is added to the contents of the address register without changing the address register. This offset also has the format of a pointer. The specification of a pointer is mandatory and must be entered as constant (e.g. P#0.0 or P#2.0). The following example shows an application of register-indirect area-internal addressing: STL Explanation LAR1 P#10.0 // Load pointer (P#10.0) to address register 1 L IW [AR1, P#2.0] // Increase contents of address register 1 (P#10.0) by offset P#2.0. // Load contents of input word IW12 into accumulator 1 L IW [AR1, P#0.0] // Increase contents of address register 1 (P#10.0) by offset P#0.0. // Load contents of input word IW10 into accumulator 1 Register-indirect cross-area addressing In the case of register-indirect, cross-area addressing, use the address register to index the entire address of the operand, in other words, the bit address and byte address, as well as the memory area. Possible memory areas are "Inputs" (I), "Outputs" (Q), "I/O" (P), "Bit memory" (M), "Temporary local data" (L) and "Data" (DB or DI). If the operand is located in a data block, it must be a data black with standard access or the operand must have the retain setting "Set in IDB". WinCC Basic V13.0 System Manual, 02/2014 1203 Programming the PLC 9.1 Creating the user program In the instruction, program only the operand width. Possible operand widths are bit, byte, word, and double word. The following example shows an application of register-indirect cross-area addressing: LAR1 P#M10.0 // Load cross-area pointer (P#M10.0) to address register 1 L W [AR1, P#2.0] // Increase contents of address register 1 (P#M10.0) by offset P#2.0. // Load contents of memory word "MW12" into accumulator 1 LAR1 P#A10.0 // Load cross-area pointer (P#A10.0) to address register 1 L W [AR1, P#2.0] // Add contents of address register 1 (P#A10.0) by offset P#2.0 // Load contents of output word QW12.0 into accumulator 1 Note Special features in S7-1500 In S7-1500, special rules apply to data exchange via address register and data block register: The values in the registers do not remain in existence beyond the block limits. The registers are also reset when the language is changed within a block. If you access an operand of the BYTE, WORD or DWORD type using register-indirect addressing, the address must begin at a byte limit. Examples: LAR1 P#0.0 L MW [AR1, P#0.0] // P#0.0 + P#0.0 = P#0.0 - The addressing is allowed, because P#0.0 points to a byte limit. L MW [AR1, P#2.1] // P#0.0 + P#2.1 = P#2.1 - The addressing is not allowed, because P#2.1 does not point to a byte limit. See also Basics of indirect addressing (Page 1196) Addressing structured variables (Page 1190) Basic information about address registers (Page 1201) 9.1.1.5 Data types Overview of the valid data types Validity of data type groups The data type groups define the properties of the data, for example, the representation of the contents and the valid memory areas. In the user program, you can use predefined data type or also data types that you have defined. 1204 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program The following tables show the availability of predefined data types in the various S7-CPUs: Table 9-1 Binary numbers Binary numbers S7-300/400 S7-1200 S7-1500 BOOL (Page 1208) X X X BYTE (Page 1209) X X X WORD (Page 1210) X X X DWORD (Page 1211) X X X LWORD (Page 1211) - - X Integers S7-300/400 S7-1200 S7-1500 SINT (Page 1212) - X X INT (Page 1214) X X X DINT (Page 1216) X X X USINT (Page 1213) - X X UINT (Page 1215) - X X UDINT (Page 1216) - X X LINT (Page 1217) - - X ULINT (Page 1219) - - X Floating-point numbers S7-300/400 S7-1200 S7-1500 REAL (Page 1220) X X X LREAL (Page 1221) - X X Timers S7-300/400 S7-1200 S7-1500 S5TIME (Page 1223) X - X TIME (Page 1225) X X X LTIME (Page 1225) - - X Date and time S7-300/400 S7-1200 S7-1500 DATE (Page 1226) X X X TIME_OF_DAY (TOD) (Page 1227) X X X LTOD (LTIME_OF_DAY) (Page 1227) - - X DT (DATE_AND_TIME) (Page 1228) X - X LDT (Page 1229) - - X DTL (Page 1229) - X X Bit strings Table 9-2 Table 9-3 Table 9-4 Table 9-5 WinCC Basic V13.0 System Manual, 02/2014 Integers Floating-point numbers Timers Date and time 1205 Programming the PLC 9.1 Creating the user program Table 9-6 Character S7-300/400 S7-1200 S7-1500 CHAR (Page 1230) X X X WCHAR (Page 1231) - - X STRING (Page 1231) X X X WSTRING (Page 1233) - - X Array S7-300/400 S7-1200 S7-1500 ARRAY [....] OF <type> (Page 1235) X X X Table 9-7 Table 9-8 Array Structures Structures S7-300/400 S7-1200 S7-1500 STRUCT (Page 1239) X X X Pointer S7-300/400 S7-1200 S7-1500 POINTER (Page 1240) X - X ANY (Page 1242) X - X VARIANT (Page 1245) - X X Parameter types S7-300/400 S7-1200 S7-1500 TIMER (Page 1247) X - X COUNTER (Page 1247) X - X BLOCK_FC (Page 1247) X - X BLOCK_FB (Page 1247) X - X BLOCK_DB (Page 1247) X - - BLOCK_SDB (Page 1247) X - - BLOCK_SFB (Page 1247) X - - BLOCK_SFC (Page 1247) X - - BLOCK_OB (Page 1247) X X X VOID (Page 1247) X X X PLC data types S7-300/400 S7-1200 S7-1500 PLC data type (Page 1248) X X X Table 9-9 Table 9-10 Table 9-11 1206 Character Pointer Parameter types PLC data types WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program Table 9-12 System data types S7-300/400 S7-1200 S7-1500 IEC_TIMER (Page 1249) X X X IEC_LTIMER (Page 1249) - - X 1) IEC_SCOUNTER (Page 1249) - X X IEC_USCOUNTER (Page 1249) - X X IEC_COUNTER (Page 1249) X2) X X IEC_UCOUNTER (Page 1249) - X X IEC_DCOUNTER (Page 1249) - X X IEC_UDCOUNTER (Page 1249) - X X IEC_LCOUNTER (Page 1249) - - X IEC_ULCOUNTER (Page 1249) - - X ERROR_STRUCT (Page 1249) - X X NREF (Page 1249) - X X CREF (Page 1249) - X X FBTREF (Page 1249) - - - VREF (Page 1249) - - - STARTINFO (Page 1249) X - X SSL_HEADER (Page 1249) X - X CONDITIONS (Page 1249) - X X TADDR_Param (Page 1249) - X X TCON_Param (Page 1249) - X X 1) For S7-300/400 CPUs, the data type is represented by TP, TON and TOF. 2) For S7-300/400 CPUs, the data type is represented by CTU, CTD and CTUD. Table 9-13 WinCC Basic V13.0 System Manual, 02/2014 System data types Hardware data types Hardware data types S7-300/400 S7-1200 S7-1500 REMOTE (Page 1251) - X X GEOADDR (Page 1251) - - X HW_ANY (Page 1251) - X X HW_DEVICE (Page 1251) - X X HW_DPMASTER (Page 1251) - - X HW_DPSLAVE (Page 1251) - X X HW_IO (Page 1251) - X X HW_IOSYSTEM (Page 1251) - X X HW_SUBMODULE (Page 1251) - X X HW_MODULE (Page 1251) - - X HW_INTERFACE (Page 1251) - X X HW_IEPORT (Page 1251) - X X HW_HSC (Page 1251) - X X HW_PWM (Page 1251) - X X HW_PTO (Page 1251) - X X AOM_AID (Page 1251) - X X 1207 Programming the PLC 9.1 Creating the user program Hardware data types S7-300/400 S7-1200 S7-1500 AOM_IDENT (Page 1251) - X X EVENT_ANY (Page 1251) - X X EVENT_ATT (Page 1251) - X X EVENT_HWINT (Page 1251) - X X OB_ANY (Page 1251) - X X OB_DELAY (Page 1251) - X X OB_TOD (Page 1251) - X X OB_CYCLIC (Page 1251) - X X OB_ATT (Page 1251) - X X OB_PCYCLE (Page 1251) - X X OB_HWINT (Page 1251) - X X OB_DIAG (Page 1251) - X X OB_TIMEERROR (Page 1251) - X X OB_STARTUP (Page 1251) - X X PORT (Page 1251) - X X RTM (Page 1251) - X X PIP (Page 1251) - - X CONN_ANY (Page 1251) - X X CONN_PRG (Page 1251) - X X CONN_OUC (Page 1251) - X X CONN_R_ID (Page 1251) - - X DB_ANY (Page 1251) - X X DB_WWW (Page 1251) - X X DB_DYN (Page 1251) - X X Note Depending on the CPU version, the actually valid data types can deviate slightly from the table. Binary numbers BOOL (bit) Description An operand of data type BOOL represents a bit value and contains one of the following values: TRUE FALSE The following table shows the properties of data type BOOL: 1208 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program Length (bits) Format Range of values Examples of value input 1 Boolean FALSE or TRUE TRUE BOOL#0 or BOOL#1 BOOL#1 BOOL#FALSE or BOOL#TRUE BOOL#TRUE Unsigned integers 0 or 1 1 Binary numbers 2#0 or 2#1 2#0 Octal numbers 8#0 or 8#1 8#1 Hexadecimal numbers 16#0 or 16#1 16#1 Note Applies to CPUs of the S7-1500 series For a block with the block property "Optimized block access", the bit has a length of 1 byte. See also Overview of the valid data types (Page 1204) Basics of constants (Page 1180) Bit strings BYTE (byte) Description An operand of data type BYTE is a bit string of 8 bits. The following table shows the properties of data type BYTE: Length (bits) Format Value range Examples of value input 8 Unsigned integers1) -128 to +127 or 0 to +255 15, BYTE#15, B#15 Binary numbers 2#0 to 2#11111111 2#00001111, BYTE#2#00001111, B#2#00001111 Octal numbers 8#0 to 8#377 8#17, BYTE#8#17, B#8#17 Hexadecimal numbers B#16#0 to B#16#FF, 16#0 to 16#FF 16#0F, BYTE#16#0F, B#16#0F 1) WinCC Basic V13.0 System Manual, 02/2014 The value range depends on the relevant interpretation or conversion. 1209 Programming the PLC 9.1 Creating the user program Note The BYTE data type cannot be compared for more than or less than. It can only be supplied with the same decimal data that can be processed by the SINT and USINT data types. See also Overview of the valid data types (Page 1204) Basics of constants (Page 1180) WORD Description An operand of data type WORD is a bit string of 16 bits. The following table shows the properties of data type WORD: Length (bits) Format Value range Examples of value input 16 Unsigned integers -32768 to 65535 61680, WORD#61680, W#61680 Binary numbers 2#0 to 2#1111111111111111 2#1111000011110000, WORD#2#11110000111100 00, W#2#1111000011110000 Octal numbers 8#0 to 8#177777 8#170360, WORD#8#170360, W#8#170360 Hexadecimal numbers W#16#0 to W#16#FFFF, 16#0 to 16#FFFF 16#F0F0, WORD#16#F0F0, W#16#F0F0 BCD C#0 to C#999 C#55 Decimal sequence B#(0, 0) to B#(255, 255) B#(127, 200) Note The WORD data type cannot be compared for more than or less than. It can only be supplied with the same decimal data that can be processed by the INT and UINT data types. See also Overview of the valid data types (Page 1204) Basics of constants (Page 1180) 1210 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program DWORD Description An operand of data type DWORD is a bit string of 32 bits. The following table shows the properties of data type DWORD: Length (bits) Format Value range Examples of value input 32 Unsigned integers -2147483648 to 4294967295 15793935, DWORD#15793935, DW#15793935 Binary numbers 2#0 to 2#11111111111111111111 111111111111 2#0000000011110000111111110 0001111, DWORD#2#00000000111100001 111111100001111, DW#2#000000001111000011111 11100001111 Octal numbers 8#0 to 8#37777777777 8#74177417, DWORD#8#74177417, DW#8#74177417 Hexadecimal numbers DW#16#00000000 to DW#16#FFFFFFFF, 16#00000000 to 16#FFFFFFFF 16#00F0FF0F, DWORD#16#00F0FF0F, DW#16#00F0FF0F Decimal sequence B#(0, 0, 0, 0) to B#(255, 255, 255, 255) B#(127, 200, 127, 200) Note The DWORD data type cannot be compared for more than or less than. It can only be supplied with the same decimal data that can be processed by the DINT and UDINT data types. See also Overview of the valid data types (Page 1204) Basics of constants (Page 1180) LWORD Description An operand of data type LWORD is a bit string of 64 bits. The following table shows the properties of data type LWORD: WinCC Basic V13.0 System Manual, 02/2014 1211 Programming the PLC 9.1 Creating the user program Length (bits) Format Value range Examples of value input 64 Unsigned integers -9223372036854775808 to 18446744073709551615 26123590360715, LWORD#26123590360715, LW#26123590360715 Binary numbers 2#0 to 2#11111111111111111111 1111111111111111111111 1111111111111111111111 2#0000000000000000000101111 100001001011110101001011011 11010001011, LWORD#2#00000000000000000 001011111000010010111101010 0101101111010001011, LW#2#000000000000000000010 111110000100101111010100101 101111010001011 Octal numbers 8#0 to 8#17777777777777777777 77 8#13724557213, LWORD#8#13724557213, LW#8#13724557213 Hexadecimal numbers LW#16#00000000 to LW#16#FFFFFFFFFFFFFF FF, 16#00000000 to 16#FFFFFFFFFFFFFFFF 16#000000005F52DE8B, LWORD#16#000000005F52DE8 B, LW#16#000000005F52DE8B Decimal sequence B#(0, 0, 0, 0, 0, 0, 0, 0) to B#(255, 255, 255, 255, 255, 255, 255, 255) B#(127, 200, 127, 200, 127, 200, 127, 200) Note The LWORD data type cannot be compared for more than or less than. It can only be supplied with the same decimal data that can be processed by the LINT and ULINT data types. See also Overview of the valid data types (Page 1204) Basics of constants (Page 1180) Integers SINT (8-bit integers) Description An operand of data type SINT (Short INT) has a length of 8 bits and consists of two components: a sign and a numerical value in the two's complement. The signal states of bits 0 to 6 represent the number value. The signal state of bit 7 represents the sign. The sign may assume "0" for the positive, or "1" for the negative signal state. An operand of data type SINT occupies one BYTE in the memory. The following table shows the properties of data type SINT: 1212 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program Length (bits) Format Range of values Examples of value input 8 Signed integers -128 to 127 +44, SINT#+44 Binary numbers 2#0 to 2#01111111 2#00101100, SINT#2#00101100 Octal numbers (only positive) 8#0 to 8#177 8#54, SINT#8#54 Hexadecimal numbers (only positive) 16#0 to 16#7F 16#2C, SINT#16#2C Example The following figure shows the integer +44 as a binary number: %LW 6LJQ 'HFLPDOYDOXHV See also Overview of the valid data types (Page 1204) Basics of constants (Page 1180) USINT (8-bit integers) Description An operand of data type USINT (Unsigned Short INT) has a length of 8 bits and contains unsigned numerical values: An operand of data type USINT occupies one BYTE in the memory. The following table shows the properties of data type USINT: WinCC Basic V13.0 System Manual, 02/2014 Length (bits) Format Range of values Examples of value input 8 Unsigned integers 0 to 255 78, USINT#78 Binary numbers 2#0 to 2#11111111 2#01001110, USINT#2#01001110 Octal numbers 8#0 to 8#377 8#116, USINT#8#116 Hexadecimal numbers 16#0 to 16#FF 16#4E, USINT#16#4E 1213 Programming the PLC 9.1 Creating the user program Example The following figure shows the integer 78 as a binary number: %LW 'HFLPDOYDOXHV See also Overview of the valid data types (Page 1204) Basics of constants (Page 1180) INT (16-bit integers) Description An operand of data type INT has a length of 16 bits and consists of two components: a sign and a numerical value in the two's complement. The signal states of bits 0 to 14 represent the number value. The signal state of bit 15 represents the sign. The sign may assume "0" for the positive, or "1" for the negative signal state. An operand of data type INT occupies two BYTE in the memory. The following table shows the properties of data type INT: Length (bits) Format Range of values Examples of value input 16 Signed integers -32768 to 32767 +3785, INT#+3785 Binary numbers (only positive) 2#0 to 2#0111111111111111 2#0000111011001001, INT#2#0000111011001001 Octal numbers 8#0 to 8#77777 8#7311, INT#8#7311 Hexadecimal numbers (only positive) 16#0 to 16#7FFF 16#0EC9, INT#16#0EC9 Example The following figure shows the integer +3785 as a binary number: %LW 6LJQ 'HFLPDOYDOXHV 1214 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program See also Overview of the valid data types (Page 1204) Basics of constants (Page 1180) UINT (16-bit integers) Description An operand of data type UINT (Unsigned INT) has a length of 16 bits and contains unsigned numerical values. An operand of data type UINT occupies two BYTE in the memory. The following table shows the properties of data type UINT: Length (bits) Format Range of values Examples of value input 16 Unsigned integers 0 to 65535 65295, UINT#65295 Binary numbers 2#0 to 2#1111111111111111 2#1111111100001111, UINT#2#1111111100001111 Octal numbers 8#0 to 8#177777 8#177417, UINT#8#177417 Hexadecimal numbers 16#0 to 16#FFFF 16#FF0F, UINT#16#FF0F Example The following figure shows the integer 65295 as a binary number: %LW 'HFLPDOYDOXHV See also Overview of the valid data types (Page 1204) Basics of constants (Page 1180) WinCC Basic V13.0 System Manual, 02/2014 1215 Programming the PLC 9.1 Creating the user program DINT (32-bit integers) Description An operand of data type DINT (Double INT) has a length of 32 bits and consists of two components: a sign and a numerical value in the two's complement. The signal states of bits 0 to 30 represent the number value. The signal state of bit 31 represents the sign. The sign may assume "0" for the positive, or "1" for the negative signal state. An operand of data type DINT occupies four BYTE in the memory. The following table shows the properties of data type DINT: Length (bits) Format Range of values Examples of value input 32 Signed integers -2147483648 to +2147483647 125790, DINT#125790, L#275 Binary numbers (only positive) 2#0 to 2#0111111111111111111111 1111111111 2#0000000000000001111010 1101011110, DINT#2#00000000000000011 110101101011110 Octal numbers (only positive) 8#0 to 8#17777777777 8#365536, DINT#8#365536 Hexadecimal numbers 16#00000000 to 16#7FFFFFFF 16#0001EB5E, DINT#16#0001EB5E Example The following figure shows the integer +125790 as a binary number: %LW 6LJQ 'HFLPDOYDOXHV See also Overview of the valid data types (Page 1204) Basics of constants (Page 1180) UDINT (32-bit integers) Description An operand of data type UDINT (Unsigned Double INT) has a length of 32 bits and contains unsigned numerical values. 1216 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program An operand of data type UDINT occupies four BYTE in the memory. The following table shows the properties of data type UDINT: Length (bits) Format Range of values Examples of value input 32 Unsigned integers 0 to 4294967295 4042322160, UDINT#4042322160 Binary numbers 2#0 to 2#111111111111111111 11111111111111 2#1111000011110000111100001 1110000, UDINT#2#111100001111000011 11000011110000 Octal numbers 8#0 to 8#37777777777 8#36074170360, UDINT#8#36074170360 Hexadecimal numbers 16#00000000 to 16#FFFFFFFF 16#F0F0F0F0, UDINT#16#F0F0F0F0 Example The following figure shows the integer 4042322160 as a binary number: %LW 'HFLPDOYDOXHV See also Overview of the valid data types (Page 1204) Basics of constants (Page 1180) LINT (64-bit integers) Description An operand of data type LINT (Long INT) has a length of 64 bits and consists of two components: a sign and a numerical value in the two's complement. The signal states of bits 0 to 62 represent the number value. The signal state of bit 63 represents the sign. The sign may assume "0" for the positive, or "1" for the negative signal state. An operand of data type LINT occupies eight BYTE in the memory. The following table shows the properties of data type LINT: WinCC Basic V13.0 System Manual, 02/2014 1217 Programming the PLC 9.1 Creating the user program Length (bits) Format Range of values Examples of value input 64 Signed integers -9223372036854775808 to +9223372036854775807 +154325790816159, LINT# +154325790816159 Binary numbers (only positive) 2#0 to 2#0111111111111111111111111111 111111111111111111111111111111 111111 2#0000000000000000100011000101 101111000101111100001111011110 011111, LINT#2#00000000000000001000110 001011011110001011111000011110 11110011111 Octal numbers 8#0 to 8#777777777777777777777 8#4305570574173637, LINT#8#4305570574173637 Hexadecimal numbers (only positive) 16#0 to 16#7FFFFFFFFFFFFFFF 16#00008C5BC5F0F79F, LINT#16#00008C5BC5F0F79F Example The following figure shows the integer +154325790816159 as a binary number: %LW %LW 6LJQ 'HFLPDOYDOXHV See also Overview of the valid data types (Page 1204) Basics of constants (Page 1180) 1218 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program ULINT (64-bit integers) Description An operand of data type ULINT (Unsigned Long INT) has a length of 64 bits and contains unsigned numerical values. An operand of data type ULINT occupies eight BYTE in the memory. The following table shows the properties of data type ULINT: Length (bits) Format Value range Examples of value input 64 Unsigned integers 0 to 18446744073709551615 154325790816159, ULINT#154325790816159 Binary numbers 2#0 to 2#1111111111111111111111111111 111111111111111111111111111111 111111 2#0000000000000000100011000101 101111000101111100001111011110 011111, ULINT#2#000000000000000010001 100010110111100010111110000111 1011110011111 Octal numbers 8#0 to 8#1777777777777777777777 8#4305570574173637, ULINT#8#4305570574173637 Hexadecimal numbers 16#0 to 16#FFFFFFFFFFFFFFFF 16#00008C5BC5F0F79F, ULINT#16#00008C5BC5F0F79F Example The following figure shows the integer 154325790816159 as a binary number: %LW %LW 'H]LPDOZHUWH WinCC Basic V13.0 System Manual, 02/2014 1219 Programming the PLC 9.1 Creating the user program See also Overview of the valid data types (Page 1204) Basics of constants (Page 1180) Floating-point numbers REAL Description Operands of the data type REAL have a length of 32 bits and are used to display floating-point numbers. An operand of the REAL data type consists of the following three components: Sign: The sign is determined by the signal state of bit 31. The bit 31 assume the value "0" (positive) or "1" (negative). 8-bit exponents to basis 2: The exponent is increased by a constant (base, +127), so that it has a value range of 0 to 255. 23-bit mantissa: Only the fraction part of the mantissa is shown. The integer part of the mantissa is always 1 with normalized floating-point numbers and is not stored. The REAL data type is processed with a precision of 7 digits after the decimal point. The following figure shows the structure of the REAL data type: %LW 6 6LJQ ELW H P ([SRQHQWH ELWV 0DQWLVVDP ELWV Note With floating-point numbers, only the precision defined by the IEEE754 standard is stored. Additionally specified decimals are rounded off according to IEEE754. The number of decimal places may decrease for frequently nested arithmetic calculations. If more decimal places are specified than can be stored by the data type, the number is rounded to the corresponding value of the precision allowed by this value range . The following table shows the properties of data type REAL: 1220 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program Length (bits) Format Value range Examples of value input 32 Floating-point numbers according to IEEE754 -3.402823e+38 to -1.175495e-38 1.0e-5, REAL#1.0e-5 Floating-point numbers 0.0 +1.175495e-38 to +3.402823e+38 1.0, REAL#1.0 See also Overview of the valid data types (Page 1204) Basics of constants (Page 1180) LREAL Description Operands of the data type LREAL have a length of 64 bits and are used to represent floatingpoint numbers. An operand of the LREAL data type consists of the following three components: Sign: The sign is determined by the signal state of bit 63. The bit 63 assumes the value "0" (positive) or "1" (negative). 11-bit exponents to base 2: The exponent is increased by a constant (base, +1023), so that it has a value range of 0 to 2047. 52-bit mantissa: Only the fraction part of the mantissa is shown. The integer part of the mantissa is always 1 with normalized floating-point numbers and is not stored. The LREAL data type is processed with a precision of 15 digits after the decimal point. The following figure shows the structure of the LREAL data type: %LW 9 6LJQ9 ELWV H P ([SRQHQWH 0DQWLVVDP ELWV ELWV The following table shows the properties of data type LREAL: WinCC Basic V13.0 System Manual, 02/2014 Length (bits) Format Value range Examples of value input 64 Floating-point numbers according to IEEE754 -1.7976931348623158e+308 to -2.2250738585072014e-308 1.0e-5, LREAL#1.0e-5 Floating-point numbers +2.2250738585072014e-308 to +1.7976931348623158e+308 0.0 1.0, LREAL#1.0 1221 Programming the PLC 9.1 Creating the user program Note With floating-point numbers, only the precision defined by the IEEE754 standard is stored. Additionally specified decimals are rounded off according to IEEE754. The number of decimal places may decrease for frequently nested arithmetic calculations. If more decimal places are specified than can be stored by the data type, the number is rounded to the corresponding value of the precision allowed by this value range . See also Overview of the valid data types (Page 1204) Basics of constants (Page 1180) Invalid floating-point numbers Description We distinguish between four number ranges for data types REAL and LREAL: normalized numbers stored with full accuracy denormalized numbers not stored with full accuracy Infinite numbers: +Inf/-Inf (infinity) Invalid numbers: NaN (Not a Number) Note Floating-point numbers are stored as specified by the IEEE754 standard. Results of conversion or arithmetic functions with a denormalized, infinite or NaN (Not a Number) floating point depend on the CPU. If you are not working with normalized floating-point numbers in mathematical functions, the result will show significant differences depending on the series of the CPU which you are using. A CPU cannot calculate with denormalized floating-point numbers, with the exception of older CPU versions of the S7-300 and S7-400 series. The bit pattern of a denormalized number is interpreted as a zero. If the result of calculation falls into this range, it is continued with zero; the status bits OV and OS are set (number range undershoot). Even though the values of invalid floating-point numbers can only be displayed with limited accuracy for mathematical functions, numbers with an exponent of -39 (e.g., 2.4408e-039) can 1222 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program be monitored in the TIA Portal and therefore do not necessarily represent a faulty result. This means that floating-point values may be located outside the range of valid numerical values. Note The following applies to CPUs of the series S7-1200 V1, V2 and V3: The comparison operation "Equal" uses the bit pattern of the invalid floating-point number. If two "NaN numbers" with the same bit pattern are compared, the output of the "Equal" comparison operation returns the result TRUE. Note The following applies to CPUs of the S7-1200 V4 and S7-1500 series: If two invalid numbers (NaN) are compared with each other, the result is always FALSE, regardless of the bit pattern of the invalid number or the relation (>, >, ...). Note Comparison of denormalized floating-point numbers For the comparison operation "Equal" with two denormalized floating-point numbers, the output for CPUs of the S7-300/400 series is set to the signal state "0" and for CPUs of the S7-1200/1500 series to the signal state "1". If the input variables of a mathematical function represent an invalid floating-point number, an invalid floating-point number will also be output as result. You have the following options to evaluate possible errors caused by invalid floating-point numbers: In LAD/FBD and SCL, you can query the enable output ENO for FALSE In STL, you can evaluate the status bit OV See also Overview of the valid data types (Page 1204) Basics of constants (Page 1180) Timers S5TIME (duration) Format Data type S5TIME stores the duration in BCD format. The duration is the product from a time in the range 0 to 999 and a time basis. The time basis indicates the interval at which a timer decrements the time value by one unit until it reaches "0". The resolution of the times can be controlled via the time basis. WinCC Basic V13.0 System Manual, 02/2014 1223 Programming the PLC 9.1 Creating the user program The following table shows the range of values for data type S5TIME: Length (bits) Format Range of values Examples of value input 16 S7 time in increments of 10 ms (default value) S5T#0MS to S5T#2H_46M_30S_0MS S5T#10s, S5TIME#10s Hexadecimal numbers 16#0 to 16#3999 16#2 The following table shows the time base coding for S5TIME: Time basis Binary code for time basis 10 ms 00 100 ms 01 1s 10 10 s 11 Always observe range limits and the resolution of time values when using data type S5TIME with timers. The table below specifies the range associated with each resolution: Resolution Range 0.01 s 10 ms to 9 s 990 ms 0.1 s 100 ms to 1 min 39 s 900 ms 1s 1 s to 16 min 39 s 10 s 10 s to 2 h 46 min 30 s Values that exceed 2h46m30s are not accepted. Example The following figure shows the content of the time operand for a time value of 127 and a time base of 1 s: %LW [ [ 7LPHEDVLV VHFRQG 7LPHYDOXHLQ%&'IRUPDW WR ,UUHOHYDQW7KHVHELWDUHGLVUHJDUGHGZKHQWKHWLPHULVVWDUWHG 1224 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program See also Overview of the valid data types (Page 1204) Basics of constants (Page 1180) TIME (IEC time) Description The contents of an operand of the data type TIME is interpreted as milliseconds. The representation contains information for days (d), hours (h), minutes (m), seconds (s) and milliseconds (ms). The following table shows the properties of data type TIME: Length (bits) Format Value range Examples of value input 32 Signed duration T#-24d20h31m23s648ms to T#+24d20h31m23s647ms T#10d20h30m20s630ms, TIME#10d20h30m20s630ms Hexadecimal numbers 16#00000000 to 16#7FFFFFFF 16#0001EB5E It is not necessary to specify all time units. T#5h10s is a valid entry, for example. If only one unit is specified, the absolute value of days, hours, and minutes must not exceed the high or low limits. When more than one time unit is specified, the value must not exceed 24 days, 23 hours, 59 minutes, 59 seconds or 999 milliseconds. See also Overview of the valid data types (Page 1204) Basics of constants (Page 1180) LTIME (IEC time) Description The contents of an operand of data type LTIME is interpreted as nanoseconds. The representation contains information for days (d), hours (h), minutes (m), seconds (s) and milliseconds (ms), microseconds (us) and nanoseconds (ns). The following table shows the properties of data type LTIME: WinCC Basic V13.0 System Manual, 02/2014 1225 Programming the PLC 9.1 Creating the user program Length (bits) Format Range of values Examples of value input 64 Signed duration LT#-106751d23h47m16s854ms7 75us808ns to LT# +106751d23h47m16s854ms775u s807ns LT#11350d20h25m14s830ms6 52us315ns, LTIME#11350d20h25m14s830 ms652us315ns Hexadecimal numbers 16#0 to 16#8000000000000000 16#2 It is not necessary to specify all time units. LT#5h10s is therefore a valid entry, for example. If only one unit is specified, the absolute value of days, hours, and minutes must not exceed the high or low limits. When more than one time unit is specified, the value must not exceed 106751 days, 23 hours, 59 minutes, 59 seconds, 999 milliseconds, 999 microseconds or 999 nanoseconds. See also Overview of the valid data types (Page 1204) Basics of constants (Page 1180) Date and time DATE Format The DATE data type saves the date as an unsigned integer. The representation contains the year, the month, and the day. The contents of an operand of DATE data type correspond in hexadecimal format to the number of days since 01-01-1990 (16#0000). The following table shows the properties of data type DATE: Length (bytes) Format Range of values Examples of value input 2 IEC date D#1990-01-01 to D#2168-12-31 D#2009-12-31, DATE#2009-12-31 16#0000 to 16#FF62 16#00F2 (Year-Month-Day) Hexadecimal numbers See also Overview of the valid data types (Page 1204) Basics of constants (Page 1180) 1226 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program TIME_OF_DAY (TOD) Format Data type TOD (TIME_OF_DAY) occupies a double word and stores the number of milliseconds since the beginning of the day (0:00 h) as unsigned integer. The following table shows the properties of data type TOD: Length (bytes) Format Range of values Examples of value input 4 Time-of-day (hours:minutes:seconds) TOD#00:00:00.000 to TOD#23:59:59.999 TOD#10:20:30.400, TIME_OF_DAY#10:20:30.40 0 You always need to specify the hours, minutes and seconds. The specification of milliseconds is optional. See also Overview of the valid data types (Page 1204) Basics of constants (Page 1180) LTOD (LTIME_OF_DAY) Format Data type LTOD (LTIME_OF_DAY) occupies two double words and stores the number of nanoseconds since the beginning of the day (0:00 h) as unsigned integer. The following table shows the properties of data type LTOD: Length (bytes) Format Range of values Examples of value input 8 Time-of-day (hours:minutes:seconds.millis econds.microseconds.nanose conds) LTOD#00:00:00.0000000 00 to LTOD#23:59:59.9999999 99 LTOD#10:20:30.400_365_21 5, LTIME_OF_DAY#10:20:30.4 00_365_215 You always need to specify the hours, minutes and seconds. The specification of milliseconds, microseconds and nanoseconds is optional. See also Overview of the valid data types (Page 1204) Basics of constants (Page 1180) WinCC Basic V13.0 System Manual, 02/2014 1227 Programming the PLC 9.1 Creating the user program DATE_AND_TIME (date and time of day) Format The DT (DATE_AND_TIME) data type saves the information on date and time of day in BCD format. The following table shows the properties of data type DT: Length (bytes) Format Range of values 8 Date and time Min.: DT#2008-10-25-8:12:34.567, DT#1990-01-01-00:0 DATE_AND_TIME#2008-10-25 0:00.000 -08:12:34.567 (year-month-dayhour:minute:second:millisecond 3) ) Example of value input Max.: DT#2089-12-31-23:5 9:59.999 The following table shows the structure of the DT data type: Byte Contents Range of values 0 Year 0 to 99 (Years 1990 to 2089) BCD#90 = 1990 ... BCD#0 = 2000 ... BCD#89 = 2089 1 Month BCD#0 to BCD#12 2 Day BCD#1 to BCD# 31 3 Hour BCD#0 to BCD#23 4 Minute BCD#0 to BCD#59 5 Second BCD#0 to BCD#59 6 The two most significant digits of MSEC BCD#0 to BCD#999 The least significant digit of MSEC BCD#0 to BCD#9 Weekday BCD#1 to BCD#7 7 (4MSB) 1) 7 (4LSB) 2) BCD#1 = Sunday ... BCD#7 = Saturday 1228 1) MSB: Most significant bit 2) LSB: Least significant bit 3) Fixed point number WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program See also Overview of the valid data types (Page 1204) Basics of constants (Page 1180) LDT (DATE_AND_LTIME) Format Data type LDT (DATE_AND_LTIME) stores the date and time-of-day information in nanoseconds since 01/01/1970 0:0. The following table shows the properties of data type LDT: Length (bytes) Format Range of values 8 Date and time Min.: LDT#2008-10-25-8:12:34.567 LDT#1970-01-01-0:0:0.0000 00000 (Year-Month-DayHour:Minute:Second) Hexadecimal numbers Example of value input Max.: LDT#2200-12-31-23:59:59.9 99999999 16#0 to 16#7FFF_FFFF_FFFF_FFF F 16#7FFF See also Overview of the valid data types (Page 1204) Basics of constants (Page 1180) DTL Description An operand of data type DTL has a length of 12 bytes and stores date and time information in a predefined structure. The following table shows the properties of data type DTL: Length (bytes) Format Value range 12 Date and time Min.: DTL#2008-12-16-20:30:20 DTL#1970-01-01-00:00:00.0 .250 (Year-Month-DayHour:Minute:Second.Nanos econds) WinCC Basic V13.0 System Manual, 02/2014 Example of value input Max.: DTL#2200-12-31-23:59:59.9 99999999 1229 Programming the PLC 9.1 Creating the user program The structure of data type DTL consists of several components each of which can contain a different data type and range of values. The data type of a specified value must match the data type of the corresponding components. The following table shows the structure components of data type DTL and their properties: Byte Component Data type Value range 0 Year UINT 1970 to 2200 2 Month USINT 1 to 12 3 Day USINT 1 to 31 4 Weekday USINT 1(Sunday) to 7(Saturday) 1 The weekday is not considered in the value entry. 5 Hour USINT 0 to 23 6 Minute USINT 0 to 59 7 Second USINT 0 to 59 8 Nanosecond UDINT 0 to 999999999 9 10 11 See also Overview of the valid data types (Page 1204) Basics of constants (Page 1180) Character strings CHAR (character) Description An operand of data type CHAR has a length of 8 bits and occupies one BYTE in the memory. The CHAR data type stores a single character in ASCII format. You can find information on the encoding of special characters under "See also > STRING". The following table shows the value range of the CHAR data type: 1230 Length (bits) Format Value range Example of value inputs 8 ASCII characters ASCII character set 'A', CHAR#'A' WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program See also Overview of the valid data types (Page 1204) Basics of constants (Page 1180) STRING (Page 1231) WCHAR (character) Description An operand of data type WCHAR (Wide Characters) has a length of 16 bits and occupies two BYTE in the memory. The WCHAR data type saves a single character of an expanded character set which is stored in Unicode format. However, only a subset of the entire Unicode range is covered. When a control character is entered, it is represented with a dollar sign. The following table shows the value range of the WCHAR data type: Length (bits) Format Range of values Example of value input 16 Unicode $0000 - $D7FF WCHAR#'a' See also Overview of the valid data types (Page 1204) STRING Description An operand of the STRING data type saves several characters in a character string that can consist of up to 254 characters. In a character string, all characters of the ASCII code are permitted. The characters are specified in single quotation marks. The following table shows the properties of a STRING tag: Length (bytes) Format Value range Example of value input n+2* ASCII character string incl. special characters 0 to 254 characters 'Name', STRING#'NAME' * An operand of the STRING data type occupies two bytes more than the specified maximum length in the memory. A character string can also contain special characters. The escape character $ is used to identify control characters, dollar signs and single quotation marks. The table below shows examples for the notation of special characters: WinCC Basic V13.0 System Manual, 02/2014 1231 Programming the PLC 9.1 Creating the user program Character Hex Meaning Example $L or $l 0A Line feed '$LText', '$0AText' $N 0A and 0D Line break '$NText', '$0A$0DText' The line break occupies 2 characters in the character string. $P or $p 0C Page feed '$PText', '$0CText' $R or $r 0D Carriage return (CR) '$RText','$0DText' $T or $t 09 Tab '$TText', '$09Text' $$ 24 Dollar sign '100$$t', '100$26' $' 27 Single quotation mark '$'Text$'','$27Text$27' The maximum length of the character string can be specified during the declaration of an operand using square brackets after the keyword STRING (for example, STRING[4]). If the specification of the maximum length is omitted, the standard length of 254 characters is set for the respective operand. If the actual length of a specified character string is shorter than the declared maximum length, the characters are written to the character string left-justified and the remaining character spaces remain undefined. Only occupied character spaces are considered in the value processing. Note For S7-300/400 CPUs, please note: If a temporary tag of the STRING data type was defined, you must describe the BYTE "Max. length of string" with the defined length before you use the tags in the user program. Example The example below shows the byte sequence if the STRING[4] data type is specified with output value 'AB': %\WH %\WH 0D[OHQJWKRIWKH VWULQJ %\WH $FWXDOOHQJWKRI WKHVWULQJ $% %\WH $6&,,YDOXH RI$ %\WH %\WH $6&,,YDOXH RI% See also Overview of the valid data types (Page 1204) Basics of constants (Page 1180) 1232 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program WSTRING Description An operand of data type WSTRING (Wide String) stores several Unicode characters of data type WCHAR in one character string. If you do not specify a length, the character string has a preset length of 254 characters. In a character string, all characters of the Unicode format are permitted. This means you can also use Chinese characters in a character string. When declaring an operand of data type WSTRING you can define its length using square brackets (for example WSTRING[10]). If you do not specify a length, the length of the WSTRING is set to 254 characters by default. You can declare a length of up to 16382 characters (WSTRING[16382]). Note Use in the watch table If you wish to monitor or control a tag with data type WSTRING in the watch table, it cannot contain more than 254 characters. The specification of the characters occurs in single quotes and always with the qualifier WSTRING#. The table below shows the properties of a WSTRING tag: Length (WORD) Format Range of values Example of value input n+2* Unicode character string; Preset value: 0 to 254 characters WSTRING#'Hello World' n specifies the length of the character string. Max. possible value: 0 to 16382 * An operand of the WSTRING data type occupies two WORDs more in the memory than the specified maximum length. A character string can also contain special characters. The escape character $ is used to identify control characters, dollar signs and single quotation marks. The table below shows examples for the notation of special characters: Character Hex Meaning Example $L or $l 000A Line feed '$LText', '$000AText' $N 000A and 000D Line break '$NText', '$000A $000DText' The line break occupies 2 characters in the character string. WinCC Basic V13.0 System Manual, 02/2014 $P or $p 000C Page feed '$PText', '$000CText' $R or $r 000D Carriage return (CR) '$RText','$000DText' $T or $t 0009 Tab '$TText', '$0009Text' $$ 0024 Dollar sign '100$$t', '100$0024t' $' 0027 Single quotation mark '$'Text$'','$0027Text $0027' 1233 Programming the PLC 9.1 Creating the user program The maximum length of the character string can be specified during the declaration of an operand using square brackets after the keyword WSTRING (for example, WSTRING[4]). If the specification of the maximum length is omitted, the standard length of 254 characters is set for the respective operand. If the actual length of a specified character string is shorter than the declared maximum length, the characters are written to the character string left-justified and the remaining character spaces remain undefined. Only occupied character spaces are considered in the value processing. Note Conversion of WSTRING tags Implicit conversion of the WSTRING data type is not possible. Explicit conversion from the WSTRING data type to STRING is generally possible. However, normally only the conversion of characters in the code range from 0 - 127 will work in all Windows code pages. For all characters outside this range, the code page character and the Unicode character must be in exactly the same position for the conversion to work without errors. Access to block parameters of data type WSTRING Operands of the data type WSTRING can be transferred as parameters up to the maximum length for blocks with "optimized" access. For function blocks (FB) with "standard" access, operands of the data type WSTRING can be declared as parameters in all sections of the block interface except in the section "InOut". For a function (FC) with "standard" access, only operands of the data type STRING can be transferred as parameters. The function value of an FC in the "Return" section and expressions in the SCL programming language are another exception to this rule. In these cases, the WSTRING tag must not be longer than 1022 characters. If you need a WSTRING tag with more than 1022 characters, declare a tag of the data type "WSTRING" with the required character length in the section "Temp" and assign the function value to the tag. Example The example below shows the byte sequence if the WSTRING[4] data type is specified with output value 'AB': %\WH %\WH 0D[OHQJWKRIWKHVWULQJ 1234 %\WH %\WH $FWXDOOHQJWKRIWKHVWULQJ $% %\WH %\WH %\WH 8QLFRGHYDOXHRI$ 8QLFRGHYDOXHRI% WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program See also Overview of the valid data types (Page 1204) Array Format of array (16-bit limits) Description The Array data type represents a data structure that consists of a fixed number of components of the same data type. All data types except Array are permitted. A tag with the Array data type always starts at a WORD limit. The array components are addressed by means of an index. In the array declaration, the index limits are defined in square brackets after the keyword Array. The low limit must be smaller than or equal to the high limit. An array may contain up to six dimensions, the limits of which can be specified separated by a comma. The following table shows the property of the Array data type: Length Format Index limits Data type Number of components * length of the data type Array [low limit...high limit] of <data type> [-32768..32767] of <data type> Bit strings, integers, floating-point numbers, timers, character strings, structures Example The following example shows how operands of data type Array can be declared: Name Declaration Comment Measured value Array[1..20] of REAL One-dimensional array with 20 components Time-of-day Array[-5..5] of INT One-dimensional array with 11 components Character Array[1..2, 3..4] of CHAR Two-dimensional array with 4 components Maximum array limits The maximum Array limits depend on the following factors: Data type of the Array elements Maximum storage capacity of the CPU (you can find more information in the relevant device manual) WinCC Basic V13.0 System Manual, 02/2014 1235 Programming the PLC 9.1 Creating the user program See also Overview of the valid data types (Page 1204) Indirect indexing of ARRAY components (Page 1198) Format of array (32-bit limits) Description The Array data type represents a data structure that consists of a fixed number of components of the same data type. All data types except Array are permitted. The array components are addressed by means of an index. In the array declaration, the index limits are defined in square brackets after the keyword Array. The low limit must be smaller than or equal to the high limit. An array may contain up to six dimensions, the limits of which can be specified separated by a comma. Note Depending on the CPU, the storage capacity of a data block is limited and the number of components of the Array is therefore also limited. However, you may initialize the addressing of the array components at any position within index limits. The following table shows the property of the Array data type: Length Format Index limits Data type Number of components * length of the data type Array [low limit...high limit] of <data type> [-2147483648..214748 3647] of <data type> Bit strings, integers, floating-point numbers, timers, character strings, structures Note The length of the array depends on whether the block was created with the "Standard" or "with optimized access" block property. Note Applies to CPUs of the S7-1500 series For a block with the block property "Optimized block access", a bit requires 1 byte of memory. This is also true when you use an ARRAY of <data type>. An ARRAY [0..1] of BOOL, for example, thus requires 2 bytes in an optimized block. 1236 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program Example The following example shows how operands of data type Array can be declared: Name Declaration Comment Measured value Array[1..20] of REAL One-dimensional array with 20 components Time-of-day Array[-5..5] of INT One-dimensional array with 11 components Character Array[1..2, 3..4] of CHAR Two-dimensional array with 4 components Maximum array limits The maximum array limits depend on the following factors: Data type of the array elements Memory reserve (only in blocks with optimized access) You can find additional information on this topic in the section "Loading block changes without reinitialization". Maximum size of a data block for a CPU (you can find more information in the respective device manual) The entire length of the array is available within a data block. Within a program block (OB, FB or FC), the possible length is reduced by the memory capacity required by the program code. Example based on a CPU of the S7-1200 series The following table shows the maximum number of elements within a block with the "with optimized access" block property: Data type width (bits) Maximum number of elements Note 1 524272 = 65534*8 8 65534 Refer to the respective device manual of the CPU for the value. 16 32767 = 65534/2 (integer division, remainder 0) 32 16383 = 65534/4 (integer division, remainder 2) 64 8191 = 65534/8 (integer division, remainder 6) Due to various technical/internal constraints, the actual usable memory area may be approximately 70 - 100 bytes less. The memory area may be further restricted due to a default setting, for example, by the "Load without reinitialization" block property. See also Overview of the valid data types (Page 1204) Indirect indexing of ARRAY components (Page 1198) WinCC Basic V13.0 System Manual, 02/2014 1237 Programming the PLC 9.1 Creating the user program Example of a one-dimensional array Declaration The following table shows the declaration of a one-dimensional Array tag: Name Data type Comment Op_Temp Array[1..3] of INT One-dimensional array tag with 3 components. The following figure shows the structure of the declared array tag: 2SB7HPS $55$<>@ ,17(*(5 2SB7HPS>@ 2SB7HPS>@ 2SB7HPS>@ Access to ARRAY components The individual array components are accessed via an index.. The index of the first ARRAY component is [1], of the second [2], and of the third [3]. To access the value of the second ARRAY component, you need to declare "Op_Temp[2]" in the program. Example of a multi-dimensional array Declaration The following table shows the declaration of a two-dimensional Array tag: Name Data type Value Comment Betr_Temp Array[1..2, 1..3] of INT 1,1,4(0) Two-dimensional array tag with 6 components. The first two components are assigned the value "1". The remaining four components are assigned the value "0". The following figure shows the structure of the declared array tag: 1238 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program ,QWHJHU ,QWHJHU ,QWHJHU 2SHUDWLQJB7HPS $55$<>@ ,17(*(5 ,QWHJHU ,QWHJHU ,QWHJHU Access to the array components The values of the individual array components are accessed via an index. The index of the first array component is, for example, [1,1] and the index of the fourth array component is [2,1]. For example, you need to declare "Betr_Temp[2,1]" in the program to enable access to the value of the fourth array component. Additional access option You can also declare the "Betr_Temp" TAG as a six-dimensional array. The following table shows an example of the declaration of a six-dimensional Array tag: Name Data type Value Comment Betr_Temp Array[1..3, 1..2, 1..3, 1..4, 1..3, 1..4] of INT - Six-dimensional array tag The index of the first array component is in this case [1,1,1,1,1,1] and the index of the last component is [3,2,3,4,3,4]. Intermediate values are accessed by entering the corresponding value for each dimension. Structures STRUCT Description Data type STRUCT represents a data structure that consists of a fixed number of components of various data types. Components of STRUCT or ARRAY data type can also be nested in a structure. The nesting depth is hereby limited to eight levels. Structures can be used to group data according to the process control system and to transfer parameters as one data unit. You can create up to 65534 structures for a CPU of the S7-1200 or S7-1500 series. Each of these structures can include up to 252 components. In addition, you can create up to 65534 function blocks, 65535 functions and 65535 organization blocks with up to 252 components each. A component of the ARRAY data type always starts at a WORD limit. The following table shows the properties of data type STRUCT: WinCC Basic V13.0 System Manual, 02/2014 1239 Programming the PLC 9.1 Creating the user program Length Format A STRUCT variable STRUCT starts with one byte with even address and occupies the memory up to the next word limit. Range of values Example of value input The value ranges of the used data types apply. The value input rules of the used data types apply. Example The following figure shows an example of the structure of a STRUCT variable: 6758&7 ,17 %<7( &+$5 5($/ %22/ ,QWHJHU %\WH &KDUDFWHU )ORDWLQJSRLQW QXPEHU %RROHDQYDOXH See also Overview of the valid data types (Page 1204) Pointer POINTER Description A parameter of the type POINTER is a pointer that can point to a specific tag. It occupies 6 bytes (48 bits) in memory and may contain the following tag information: DB number, or 0 if the data is not stored in a DB Memory area in the CPU Tag address The following figure shows the structure of parameter type POINTER: 1240 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program 3RLQWHUIRUPDW %LW %LW %\WH %\WH '%QXPEHU RU %\WH %\WH 0HPRU\DUHD E E E E E E E E E E E %\WH E E E E E [ [ [ %\WH E %\WHDGGUHVVRIWKHWDJ [ %LWDGGUHVVRI WKHWDJ Types of pointer Depending on the information, you can use parameter type POINTER to declare the following four types of pointer: Area-internal pointer: An area-internal pointer contains information on the address of a tag. Cross-area pointer: A cross-area pointer contains information on the memory area and the address of a tag. DB pointer: You can use a DB pointer to point to a data block tag. A DB pointer also contains a data block number in addition to the memory area and the address of a tag. Zero pointer: Use the zero pointer to indicate a missing value. A missing value may indicate that no value exists, or that the value is not yet known. A zero value represents the absence of a value, but is also a value. The following table shows the formats for the declaration of various pointer types: P#ByteRepresentation Format Example of value input Description Symbolic P#Byte.Bit "MyTag" Area-internal pointer P#OperandAreaByte.Bit "MyTag" Cross-area pointer P#Data_block.Data_oper and "MyDB"."MyTag" DB pointer P#Zero value - Zero pointer P#Byte.Bit P#20.0 Area-internal pointer P#OperandAreaByte.Bit P#M20.0 Cross-area pointer P#Data_block.Data_oper and P#DB10.DBX20.0 DB pointer P#Zero value P#0.0, ZERO Zero pointer Absolute WinCC Basic V13.0 System Manual, 02/2014 1241 Programming the PLC 9.1 Creating the user program You can enter a parameter of the type POINTER without prefix (P#). The entry is then automatically converted to the POINTER format. Note If you use the prefix P#, you can only point to memory areas with "standard" access mode. Memory areas The following table shows the hexadecimal codes of the memory areas for parameter type POINTER: Hexadecimal code Memory area Description B#16#801) P Peripherals on a CPU S7-300/400 16#1 P Peripheral inputs on a CPU S7-1500 16#2 P Peripheral outputs on a CPU S7-1500 B#16#81 I Memory area of inputs B#16#82 Q Memory area of outputs B#16#83 M Memory area of bit memory B#16#84 DBX Data block B#16#85 DIX Instance data block B#16#86 L Local data B#16#87 V Previous local data 1) These data types can only be used for the POINTER pointer on a CPU S7-300/400. See also Basics of indirect addressing (Page 1196) Overview of the valid data types (Page 1204) Basics of constants (Page 1180) ANY Description An ANY type parameter points to the start of a data area and specifies its length. An ANY pointer occupies 10 bytes of memory and may contain the following information: Data type: Data type of the elements of the data area Repetition factor: Number of elements of the data area 1242 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program DB number: Data block that contains the declaration of data area elements. Memory area: Memory area of the CPU that stores the data area elements. Start address of the data in the format "byte.bit": Data area start identified by the ANY pointer. Zero pointer: Use the zero pointer to indicate a missing value. A missing value may indicate that no value exists, or that the value is not yet known. A zero value represents the absence of a value, but is also a value. Note Memory area For an S7-1500 CPU, the ANY pointer can also only point to memory areas with "Standard" access mode. The following figure shows the structure of the ANY pointer: %LW %LW %\WH KIRU6 %\WH 'DWDW\SH %\WH %\WH 5HSHWLWLRQIDFWRU %\WH %\WH '%QXPEHU RU %\WH %\WH 0HPRU\DUHD E E E E E E E E E E E %\WH E E E E E [ [ [ %\WH E %\WHDGGUHVVRIWKHWDJ [ %LWDGGUHVVRI WKHWDJ An ANY pointer cannot identify structures. It can only be assigned to local tags. The following table shows the formats for the declaration of an ANY pointer: Representation Format Example of value input Symbolic P#DataBlock.MemoryA rea DataAddress Type Number "MyDB".StructTag.Initia Area with 10 words in lComponents global DB11 starting with DBB20.0 P#MemoryArea DataAddress Type Number "MyMarkerTag" Area with 4 bytes starting with MB 20.0 "MyTag" Input I1.0 P#Zero value - Zero value P#DataBlock.MemoryA rea DataAddress Type Number P#DB11.DBX20.0 INT 10 Area with 10 words in global DB11 starting with DBB20.0 Absolute WinCC Basic V13.0 System Manual, 02/2014 Description 1243 Programming the PLC 9.1 Creating the user program Representation Format Example of value input Description P#MemoryArea DataAddress Type Number P#M20.0 BYTE 10 Area with 10 bytes starting with MB 20.0 P#E1.0 BOOL 1 Input I1.0 P#Zero value P#0.0 VOID 0, ZERO Zero value Coding of data types The following table lists the coding of data types for the ANY pointer: Hexadecimal code Data type Description B#16#00 NIL Null pointer B#16#011) BOOL Bits B#16#02 BYTE bytes, 8 bits B#16#03 CHAR 8-bit characters B#16#04 WORD 16-bit words B#16#05 INT 16-bit integers B#16#06 DWORD 32-bit words B#16#07 DINT 32-bit integers B#16#08 REAL 32-bit floating-point numbers B#16#0B TIME Time duration B#16#0C S5TIME Time duration B#16#09 DATE Date B#16#0A TOD Date and time B#16#0E DT Date and time B#16#13 STRING Character string 1) BLOCK_FB Function block B#16#181) BLOCK_FC Function B#16#19 B#16#17 BLOCK_DB Data block B#16#1A1) BLOCK_SDB System data block B#16#1C COUNTER Counter TIMER Timer 1) 1) B#16#1D1) 1) These data types can only be used for the ANY pointer on a CPU S7-300/400. Coding of the memory area The following table lists the coding of the memory areas for the ANY pointer: 1244 Hexadecimal code Area Description B#16#801) P I/O B#16#81 I Memory area of inputs B#16#82 Q Memory area of outputs B#16#83 M Memory area of bit memory B#16#84 DBX Data block WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program Hexadecimal code Area Description B#16#85 DIX Instance data block B#16#86 L Local data B#16#87 V Previous local data 1) These memory areas can only be used for the ANY pointer on an S7-300/400 CPU. See also Basics of indirect addressing (Page 1196) Overview of the valid data types (Page 1204) Basics of constants (Page 1180) VARIANT Description A parameter of the VARIANT type is a pointer that can point to tags of different data types other than an instance. The VARIANT pointer can be an object of an elementary data type, such as INT or REAL. It can also be a STRING, DTL, array of STRUCT, UDT, or array of UDT. The VARIANT pointer can recognize structures and point to individual structure components. An operand of data type VARIANT occupies no space in the instance DB or L stack. However, it will occupy memory space on the CPU. A tag of the VARIANT type is not an object but rather a reference to another object. Individual elements of the VARIANT type can only be declared within the block interface of a function. For this reason, it cannot be declared in a data block or in the static section of the block interface of a function block, for example, because its size is unknown. The size of the referenced objects can change. The VARIANT data type can only be defined on formal parameters in the block interface of a block. Note You can only point to a complete data block if it was originally derived from a user-defined data type (UDT). The following table shows the properties of the VARIANT pointer: Length (bytes) Representat Format ion Example of value input 0 Symbolic Operand "TagResult" NameDataBlock.NameOperand.Component "Data_TIA_Portal".StructVariable.FirstCompon ent Operand %MW10 Absolute WinCC Basic V13.0 System Manual, 02/2014 1245 Programming the PLC 9.1 Creating the user program Length (bytes) Representat Format ion Example of value input DataBlockNumber.Operand Type Length P#DB10.DBX10.0 INT 12 (valid only for blocks with standard access) P#Zero value P#0.0 VOID 0, ZERO Note If you use the prefix P#, you can only point to memory areas with "standard" access mode. Coding of data types If you use absolute addressing with P#, the following data types are permitted: Hexadecimal code Data type Description B#16#00 NIL Null pointer B#16#01 BOOL Bits B#16#02 BYTE bytes, 8 bits B#16#03 CHAR 8-bit characters B#16#04 WORD 16-bit words B#16#05 INT 16-bit integers B#16#06 DWORD 32-bit words B#16#07 DINT 32-bit integers B#16#08 REAL 32-bit floating-point numbers B#16#0B TIME Time duration B#16#0C S5TIME Time duration B#16#09 DATE Date B#16#0A TOD Date and time B#16#0E DT Date and time B#16#13 STRING Character string B#16#17 BLOCK_FB Function block B#16#18 BLOCK_FC Function B#16#19 BLOCK_DB Data block B#16#1A BLOCK_SDB System data block B#16#1C COUNTER Counter B#16#1D TIMER Timer Example The following example shows how VARIANT works using the "MOVE: Move value" instruction of STL: STL Description CALL MOVE // The "Move value" instruction is called. 1246 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program STL Description VARIANT // Data type of the instruction IN := "Data_TIA_Portal".StructVariable.FirstComponent // The contents of the "FirstComponent" operand are moved from the "Data_TIA_Portal" DB. OUT := "MotorDB".StructResult.TagResult // And transferred to the "TagResult" operand from the "MotorDB" DB. See also Basics of indirect addressing (Page 1196) Overview of the valid data types (Page 1204) Basics of constants (Page 1180) Basics of block access (Page 1151) Principles of block calls (Page 1156) Using VARIANT instructions (Page 174) Parameter types Parameter types Description The parameter types are data types for formal parameters that are transferred to called blocks. A parameter type can also be a PLC data type. The following table shows the available parameter data types and their purpose: Parameter type Length (bits) Description TIMER 16 Is used to specify a timer that is used in the called code block. If you supply a formal parameter of the TIMER parameter type, the associated actual parameter must be a timer. Example: T1 COUNTER 16 Is used to specify a counter that is used in the called code block. If you supply a formal parameter of the COUNTER parameter type, the associated actual parameter must be a counter. Example: C10 WinCC Basic V13.0 System Manual, 02/2014 BLOCK_FC 16 BLOCK_FB 16 BLOCK_DB 16 BLOCK_SDB 16 BLOCK_SFB 16 BLOCK_SFC 16 Is used to specify a block that is used as input in the called code block. The declaration of the parameter determines the block type (for example FB, FC, DB) that is to be used. If you supply a formal parameter of the BLOCK parameter type, specify a block address as the actual parameter. Example: DB3 1247 Programming the PLC 9.1 Creating the user program Parameter type Length (bits) BLOCK_OB 16 VOID - Description The VOID parameter type does not save any values. This parameter type is used if the return values of an output are not required. The VOID parameter type can be specified at the STATUS output, for example, if no error information is required. See also Overview of the valid data types (Page 1204) Basics of PLC data types (Page 1551) PLC data types PLC data types Description PLC data types are data structures that you define and that can be used multiple times within the program. The structure of a PLC is made up of several components, each of which can contain different data types. You define the type of components during the declaration of the PLC data type. You can create up to 65534 PLC data types for a CPU of the S7-1200 or S7-1500 series. Each of these PLC data types can include up to 252 components. PLC data types can be used for the following applications: PLC data types can be used as data types for variables in the variable declaration of logic blocks or in data blocks. PLC data types can be used as templates for the creation of global data blocks with identical data structures. PLC data types can be used in S7-1200 and S7-1500 as a template for the creation of structured PLC tags. See also Addressing structured variables (Page 1190) Example of a PLC data type Example You can declare PLC data types as the type when creating data blocks. Based on this type you can create a number of data blocks, all of which have the same data structure. These data blocks can be adapted by entering different actual values for the corresponding task. 1248 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program For instance, create a PLC data type for a recipe for blending paints. You can then assign this data type to several data blocks, each of which contains other quantity information. The following figure shows this application: '%%/8( '%/,*+7B%/8( 3/&GDWDW\SH 8'75HFLSH '%3853/( System data types System data types Description The system data types (SDT) are made available by the system and have a predefined structure. The structure of a system data type consists of a fixed number of components that can have various data types. It is not possible to change the structure of a system data type. The system data types can only be used for specific instructions. The following table shows the available system data types and their purpose: System data type Length (bytes) Description IEC_TIMER 16 Structure of a timer whose timer values are of TIME data type. This data type is used for the "TP", "TOF", "TON", "TONR", "RT" and "PT" instructions, for example. IEC_LTIMER 32 Structure of a timer whose timer values are of LTIME data type. This data type is used for the "TP", "TOF", "TON", "TONR", "RT" and "PT" instructions, for example. IEC_SCOUNTER 3 Structure of a counter whose count values are of SINT data type. This data type is used for the "CTU", "CTD" and "CTUD" instructions, for example. IEC_USCOUNTER 3 Structure of a counter whose count values are of USINT data type. This data type is used for the "CTU", "CTD" and "CTUD" instructions, for example. WinCC Basic V13.0 System Manual, 02/2014 1249 Programming the PLC 9.1 Creating the user program System data type Length (bytes) Description IEC_COUNTER 6 Structure of a counter whose count values are of INT data type. This data type is used for the "CTU", "CTD" and "CTUD" instructions, for example. IEC_UCOUNTER 6 Structure of a counter whose count values are of UINT data type. This data type is used for the "CTU", "CTD" and "CTUD" instructions, for example. IEC_DCOUNTER 12 Structure of a counter whose count values are of DINT data type. This data type is used for the "CTU", "CTD" and "CTUD" instructions, for example. IEC_UDCOUNTER 12 Structure of a counter whose count values are of UDINT data type. This data type is used for the "CTU", "CTD" and "CTUD" instructions, for example. IEC_LCOUNTER 24 Structure of a counter with count values of data type UDINT. This data type is used for the "CTU", "CTD" and "CTUD" instructions, for example. IEC_ULCOUNTER 24 Structure of a counter with count values of data type UINT. This data type is used for the "CTU", "CTD" and "CTUD" instructions, for example. ERROR_STRUCT 28 Structure of an error information to a programming or I/O access error. This data type is used, for example, for the "GET_ERROR" instruction. CREF 8 Components of the ERROR_STRUCT data type, in which information about the address of a block is saved. NREF 8 Components of the ERROR_STRUCT data type, in which information about the address of an operand is saved. VREF 12 Is used for storage of a VARIANT pointer. This data type is, for example, used for instructions from S7-1200 Motion Control. STARTINFO 12 Specifies the data structure in which the start information is saved. This data type is used, for example, for the "RD_SINFO" instruction. SSL_HEADER 4 Specifies the data structure in which information about the data records are saved during the reading of the system status lists. This data type is used, for example, for the "RDSYSST" instruction. CONDITIONS 52 User-defined data structure defining the conditions for start and end of a data reception. This data type is used, for example, for the "RCV_CFG" instruction. 1250 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program System data type Length (bytes) Description TADDR_Param 8 Specifies the structure of a data block which stores descriptions of connections for Open User Communication via UDP. This data type is used for the "TUSEND" and "TURSV" instructions, for example. TCON_Param 64 Specifies the structure of a data block which stores descriptions of connections for Open User Communication via Industrial Ethernet (PROFINET). This data type is used for the "TSEND" and "TRSV" instructions, for example. See also Overview of the valid data types (Page 1204) Hardware data types Hardware data types Description The hardware data types are made available by the CPU. The number of available hardware data types depends on the CPU. Constants of a specific hardware data type are stored based on the modules set in the hardware configuration. When an instruction for controlling or activating a configured module is inserted in the user program, the available constants can be used for the parameters. The following table shows the available hardware data types and their purpose: Data type Basic data type Description REMOTE ANY Serves to specify the address of a remote CPU. This data type is used, for example, for the "PUT" and "GET" instructions. GEOADDR HW_IOSYSTEM Geographical address information HW_ANY WORD Identification of any hardware component, e.g. a module. HW_DEVICE HW_ANY Identification of a DP slave/PROFINET IO device HW_DPMASTER HW_INTERFACE Identification of a DP master HW_DPSLAVE HW_DEVICE Identification of a DP slave HW_IO HW_ANY Identification number of the CPU or the interface The number is automatically allocated and is stored in the properties of the CPU or of the interface in the hardware configuration. WinCC Basic V13.0 System Manual, 02/2014 HW_IOSYSTEM HW_ANY Identification of a PN/IO system or DP master system HW_SUBMODULE HW_IO Identification of a central hardware component 1251 Programming the PLC 9.1 Creating the user program Data type Basic data type Description HW_MODULE HW_IO Identification of a module HW_INTERFACE HW_SUBMODULE Identification of an interface component HW_IEPORT HW_SUBMODULE Identification of a port (PN/IO) HW_HSC HW_SUBMODULE Identification of a high-speed counter This data type is used, for example, for the "CTRL_HSC" instruction. HW_PWM HW_SUBMODULE Identification of a pulse width modulation This data type is used, for example, for the "CTRL_PWM" instruction. HW_PTO HW_SUBMODULE Identification of a pulse encoder This data type is used for Motion Control. AOM_AID DWORD Is used only in connection with a system function block. AOM_IDENT DWORD Identification of an object in the runtime system of the AS EVENT_ANY AOM_IDENT Used to identify any event EVENT_ATT EVENT_ANY Is used to specify an event that can be assigned dynamically to an OB This data type is used, for example, for the "ATTACH" and "DETACH" instructions. EVENT_HWINT EVENT_ATT Is used to specify a hardware interrupt event OB_ANY INT Serves to specify any organization block. OB_DELAY OB_ANY Used to specify an organization block that is called when a time-delay interrupt occurs. This data type is used, for example, for the "SRT_DINT" and "CAN_DINT" instructions. OB_TOD OB_ANY Specifies the number of a time-of-day interrupt OB. This data type is used, for example, for the "SET_TINT", "CAN_TINT", "ACT_TINT" and "QRY_TINT" instructions. OB_CYCLIC OB_ANY Is used to specify an organization block that is called when a watchdog interrupt occurs. OB_ATT OB_ANY Is used to specify an organization block that can be assigned dynamically to an event. This data type is used, for example, for the "ATTACH" and "DETACH" instructions. 1252 OB_PCYCLE OB_ANY Is used to specify an organization block that can be assigned to an event of the "Cyclic program" event class. OB_HWINT OB_ATT Is used to specify an organization block that is called when a hardware interrupt occurs. OB_DIAG OB_ANY Is used to specify an organization block that is called when a diagnostic interrupt occurs. OB_TIMEERROR OB_ANY Is used to specify an organization block that is called when a time error occurs. OB_STARTUP OB_ANY Is used to specify an organization block that is called when a startup event occurs. WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program Data type Basic data type Description PORT HW_SUBMODULE Serves to specify a communication port. This data type is used for point-to-point communication. RTM UINT Serves to specify the number of an operating hours counter. This data type is used, for example, for the "RTM" instruction. PIP UINT Is used to create and connect a "Synchronous Cycle" OB. This data type is used for the SFCs 26, 27, 126 and 127. CONN_ANY WORD Serves to specify any connection. CONN_PRG CONN_ANY Serves to specify a connection for open communication over UDP. CONN_OUC CONN_ANY Used to specify a connection for open communication over Industrial Ethernet (PROFINET). CONN_R_ID DWORD Data type for the R_ID parameter on the S7 communication blocks. DB_ANY UINT Identification (number) of any DB The data type "DB_ANY" has the length 0 in the section "Temp". DB_WWW DB_ANY Number of a DB generated via the Web application (for example, "WWW" instruction) The data type "DB_WWW" has the length 0 in the section "Temp". DB_DYN DB_ANY Number of a DB generated by the user program See also Overview of the valid data types (Page 1204) Data type conversion Data type conversion Overview of data type conversion Introduction If you link several operands in an instruction, you must make sure that the data types are compatible. This applies also for assignments or for supplying block parameters. If the operands are not the same data type, a conversion has to be carried out. There are two options for the conversion: WinCC Basic V13.0 System Manual, 02/2014 1253 Programming the PLC 9.1 Creating the user program Implicit conversion The conversion take place automatically when the instruction is executed. Explicit conversion You use an explicit conversion instruction before the actual instruction is executed. Note The data type conversion options described always refer to the latest version of the CPU (V. 4) Conversions marked as possible may not be available in CPU versions 1 - 3. Note Converting bit strings in SCL All bit strings (BYTE, WORD, DWORD and LWORD) are handled like the corresponding unsigned integers (USINT, UINT, UDINT and ULINT) in expressions. Therefore, implicit conversion from DWORD to REAL is carried out like a conversion from UDINT to REAL, for example. Implicit conversion An implicit conversion is executed automatically if the data types of the operands are compatible. This compatibility test can be carried out according to criteria that are more or less strict: With IEC check (default) If IEC check is set, the following rules are applied: - Implicit conversion of BOOL to other data types is not possible. - Only the REAL, BYTE, WORD, DINT, INT, SINT, UDINT, UINT, USINT, TIME, DT, STRING and CHAR data types can be converted implicitly. - The bit length of the source data type must not exceed the bit length of the target data type. An operand of data type WORD, for example, cannot be declared at a parameter at which data type BYTE is expected. Without IEC check If IEC check is not set, the following rules are applied: - Implicit conversion of BOOL to other data types is not possible. - Only the REAL, LREAL, BYTE, WORD, DWORD, SINT, INT, DINT, USINT, UINT, UDINT, TIME, DTL, TOD, DATE, STRING and CHAR data types can be converted implicitly. - The bit length of the source data type must not exceed the bit length of the target data type. An operand of data type DWORD, for example, cannot be declared at a parameter at which data type WORD is expected. - The bit length of an operand entered in-out parameters InOut) must be the same as the programmed bit length for the parameter in question. 1254 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program Note Implicit conversion without IEC check The programming editor uses a gray rectangle to mark operands that are implicitly converted. The dark gray rectangle signals that an implicit conversion is possible without any accuracy loss, for example, if you convert the data type SINT to INT. A light gray rectangle signals that implicit conversion is possible, but errors could occur during runtime. If, for example, you are converting the data type DINT to INT and an overflow occurs, the enable output ENO is set to "0". For more information about the setting of the IEC check and the implicit conversion, refer to "See also". Explicit conversion If the operands are not compatible and an implicit conversion is therefore not possible, you can use an explicit conversion instruction. You can find the conversion instructions in the "Instructions" task card. A possible overflow is displayed at the ENO enable output. An overflow is created, for example, if the value of the source data type is greater than the value of the target data type. For more information about explicit conversion, refer to "See also". The following figure shows an example in which an explicit data type conversion must be carried out: %ORFNB'DWD &219(57 ',17WR,17 ,1B',17 (1 (12 ,1 287 %ORFN (1 287B,17 287B,17 (12 ,1B,17 287B%22/ The "Block" function block expects a tag of the INT data type at the "IN_INT" input parameter. Therefore, the value of the "IN_DINT" tag must first be converted from DINT to INT. If the value of the "IN_DINT" tag is within the permitted value range of the INT data type, the conversion takes place. Otherwise, an overflow is signaled. A conversion still takes place even in case of an overflow, but the values are cut off and the enable output ENO is set to "0". See also Setting and canceling the IEC check (Page 1256) WinCC Basic V13.0 System Manual, 02/2014 1255 Programming the PLC 9.1 Creating the user program Implicit conversion Setting and canceling the IEC check The data types of the operands used are check for compatibility. This compatibility test can be carried out according to criteria that are more or less strict. If "IEC check" is activated, stricter criteria are applied. You can set the IEC check centrally for all new blocks of the project or for individual blocks. Setting IEC check for new blocks To set the IEC check for all new blocks in the project, proceed as follows: 1. Select the "Settings" command in the "Options" menu. The "Settings" window is displayed in the work area. 2. Select the "PLC programming > General" group in the area navigation. 3. Select or clear the "IEC check" check box in the "Default settings for new blocks" group. The IEC check is enabled or disabled for all new blocks in the program. Setting IEC check for a block To set the IEC check for a block, proceed as follows: 1. Open the block. 2. Open the "Properties" tab in the Inspector window. 3. Select the "Attributes" group in the area navigation. 4. Select or clear the "IEC check" check box. The IEC check is enabled or disabled for this block. The setting is stored together with the project. Binary numbers Implicit conversion of BOOL Options for implicit conversion The implicit conversion of the BOOL data type is not possible. See also BOOL (bit) (Page 1208) 1256 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program Bit strings Implicit conversion of BYTE Options for implicit conversion The following table shows the options for implicit conversion of the BYTE data type: Source BYTE Target With Without IEC check IEC check BOOL - - No implicit conversion WORD x x DWORD x x The bit pattern of the source value is transferred unchanged rightjustified to the target data type. SINT - x USINT - x INT - x UINT - x DINT - x UDINT - x REAL - - LREAL - - TIME - - DTL - - TOD - - DATE - - STRING - - CHAR - x Description No implicit conversion The bit pattern of the source value is transferred unchanged to the target data type. x: Conversion possible -: Conversion not possible See also BYTE (byte) (Page 1209) Setting and canceling the IEC check (Page 1256) Overview of data type conversion (Page 1253) Explicit conversion of BYTE (Page 1274) WinCC Basic V13.0 System Manual, 02/2014 1257 Programming the PLC 9.1 Creating the user program Implicit conversion of WORD Options for implicit conversion The following table shows the options for implicit conversion of the WORD data type: Source WORD Target With Without IEC check IEC check Description BOOL - - No implicit conversion BYTE - X The least significant byte is transferred to the target data type, while the most significant byte is ignored. DWORD X X The bit pattern of the source value is transferred unchanged rightjustified to the target data type. SINT - X The least significant byte is transferred to the target data type, while the most significant byte is ignored. USINT - X INT - X The bit pattern of the source value is transferred unchanged rightjustified to the target data type. UINT - X DINT - X UDINT - X REAL - - LREAL - - TIME - - DTL - - TOD - - DATE - X The bit pattern of the source value is transferred unchanged to the target data type. STRING - - No implicit conversion CHAR - X The bit pattern of the source value is transferred unchanged to the target data type. No implicit conversion x: Conversion possible -: Conversion not possible See also WORD (Page 1210) Setting and canceling the IEC check (Page 1256) Overview of data type conversion (Page 1253) Explicit conversion of WORD (Page 1275) 1258 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program Implicit conversion of DWORD Options for implicit conversion The following table shows the options for implicit conversion of the DWORD data type: Source DWORD Target With Without IEC check IEC check Description BOOL - - No implicit conversion BYTE - X WORD - X The right bytes are transferred to the target data type; the left bytes are ignored. SINT - X USINT - X INT - X UINT - X DINT - X UDINT - X REAL - X The value is converted to the format of the target data type. (The value "-1", for example, is converted to the value "-1.0".) LREAL - - No implicit conversion TIME - X The bit pattern of the source value is transferred unchanged rightjustified to the target data type. DTL - - No implicit conversion TOD - X The bit pattern of the source value is transferred unchanged rightjustified to the target data type. DATE - - No implicit conversion STRING - - CHAR - X The bit pattern of the source value is transferred unchanged rightjustified to the target data type. The bit pattern of the source value is transferred unchanged rightjustified to the target data type. x: Conversion possible -: Conversion not possible See also DWORD (Page 1211) Setting and canceling the IEC check (Page 1256) Overview of data type conversion (Page 1253) Explicit conversion of DWORD (Page 1277) WinCC Basic V13.0 System Manual, 02/2014 1259 Programming the PLC 9.1 Creating the user program Integers Implicit conversion of SINT Options for implicit conversion The following table shows the options for implicit conversion of the SINT data type: Source SINT Target With Without IEC check IEC check BOOL - - No implicit conversion BYTE - X WORD - X The bit pattern of the source value is transferred unchanged rightjustified to the target data type. The remaining bits are filled with "0". DWORD - X USINT - X INT X X UINT - X DINT X X UDINT - X REAL X X LREAL X X The value is converted to the format of the target data type. (The value "-1", for example, is converted to the value "-1.0".) TIME - - No implicit conversion DTL - - TOD - - DATE - - STRING - - CHAR - X Description The bit pattern of the source value is converted and transferred to the target data type. (for example, value transfer from SINT #-1 -> INT #-1, not filled with "0".) The bit pattern of the source value is transferred unchanged rightjustified to the target data type. x: Conversion possible -: Conversion not possible See also SINT (8-bit integers) (Page 1212) Setting and canceling the IEC check (Page 1256) Overview of data type conversion (Page 1253) Explicit conversion of SINT (Page 1280) 1260 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program Implicit conversion of USINT Options for implicit conversion The following table shows the options for implicit conversion of the USINT data type: Source USINT Target BOOL With Without IEC check IEC check Description - - No implicit conversion The bit pattern of the source value is transferred unchanged rightjustified to the target data type. The remaining bits are filled with "0". BYTE - X WORD - X DWORD - X SINT - X INT X X UINT X X DINT X X UDINT X X REAL X X LREAL X X The value is converted to the format of the target data type. (The value "1", for example, is converted to the value "1.0".) TIME - - No implicit conversion DTL - - TOD - - DATE - - STRING - - CHAR - X The bit pattern of the source value is converted and transferred to the target data type. (for example, value conversion from USINT #10 -> DINT #10 or USINT #128 -> SINT #-128) The bit pattern of the source value is transferred unchanged rightjustified to the target data type. x: Conversion possible -: Conversion not possible See also USINT (8-bit integers) (Page 1213) Setting and canceling the IEC check (Page 1256) Overview of data type conversion (Page 1253) Explicit conversion of USINT (Page 1282) WinCC Basic V13.0 System Manual, 02/2014 1261 Programming the PLC 9.1 Creating the user program Implicit conversion of INT Options for implicit conversion The following table shows the options for implicit conversion of the INT data type: Source INT Target With Without IEC check IEC check Description BOOL - - No implicit conversion BYTE - X WORD - X The bit pattern of the source value is transferred unchanged rightjustified to the target data type. DWORD - X SINT - X USINT - X UINT - X DINT X X UDINT - X REAL X X LREAL X X The value is converted to the format of the target data type. (The value "-1", for example, is converted to the value "-1.0".) TIME - - No implicit conversion DTL - - TOD - - DATE - X The bit pattern of the source value is transferred unchanged rightjustified to the target data type. STRING - - No implicit conversion CHAR - X The bit pattern of the source value is transferred unchanged rightjustified to the target data type. The bit pattern of the source value is converted and transferred to the target data type. (for example, value conversion from INT #-1 -> SINT #-1, or INT #-32 767 -> UINT #32 769) x: Conversion possible -: Conversion not possible See also INT (16-bit integers) (Page 1214) Setting and canceling the IEC check (Page 1256) Overview of data type conversion (Page 1253) Explicit conversion of INT (Page 1283) 1262 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program Implicit conversion of UINT Options for implicit conversion The following table shows the options for implicit conversion of the UINT data type: Source UINT Target With Without IEC check IEC check Description BOOL - - No implicit conversion BYTE - X WORD - X The bit pattern of the source value is transferred unchanged rightjustified to the target data type. DWORD - X SINT - X USINT - X INT - X DINT X X UDINT X X REAL X X LREAL X X The value is converted to the format of the target data type. (The value "1", for example, is converted to the value "1.0".) TIME - - No implicit conversion DTL - - TOD - - DATE - X The bit pattern of the source value is transferred unchanged rightjustified to the target data type. STRING - - No implicit conversion CHAR - X The bit pattern of the source value is transferred unchanged rightjustified to the target data type. The bit pattern of the source value is converted and transferred to the target data type. (for example, value conversion from UINT #100 -> DINT #100 or UINT #60 000 -> INT #-5536) x: Conversion possible -: Conversion not possible See also UINT (16-bit integers) (Page 1215) Setting and canceling the IEC check (Page 1256) Overview of data type conversion (Page 1253) Explicit conversion of UINT (Page 1285) WinCC Basic V13.0 System Manual, 02/2014 1263 Programming the PLC 9.1 Creating the user program Implicit conversion of DINT Options for implicit conversion The following table shows the options for implicit conversion of the DINT data type: Source DINT Target With Without IEC check IEC check Description BOOL - - No implicit conversion BYTE - X WORD - X The bit pattern of the source value is transferred unchanged rightjustified to the target data type. DWORD - X SINT - X USINT - X INT - X UINT - X UDINT - X REAL - X The bit pattern of the source value is converted and transferred to the target data type. (for example, value conversion from DINT #-1 -> REAL #-1.0, but there is a loss in accuracy for numbers with an absolute value greater than 8 388 608) LREAL X X The value is converted to the format of the target data type. (The value "-1", for example, is converted to the value "-1.0".) TIME - X The bit pattern of the source value is transferred unchanged rightjustified to the target data type. DTL - - No implicit conversion TOD - X The bit pattern of the source value is transferred unchanged rightjustified to the target data type. DATE - - No implicit conversion STRING - - CHAR - X The bit pattern of the source value is converted and transferred to the target data type. (for example, value conversion from DINT #-1 -> SINT #-1 or DINT #-1 -> USINT #255) The bit pattern of the source value is transferred unchanged rightjustified to the target data type. x: Conversion possible -: Conversion not possible See also DINT (32-bit integers) (Page 1216) Setting and canceling the IEC check (Page 1256) Overview of data type conversion (Page 1253) Explicit conversion of DINT (Page 1287) 1264 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program Implicit conversion of UDINT Options for implicit conversion The following table shows the options for implicit conversion of the UDINT data type: Source UDINT Target With Without IEC check IEC check Description BOOL - - No implicit conversion BYTE - X WORD - X The bit pattern of the source value is transferred unchanged rightjustified to the target data type. DWORD - X SINT - X USINT - X INT - X UINT - X DINT - X REAL - X The bit pattern of the source value is converted and transferred to the target data type. (for example, value conversion from DINT #-1 -> REAL #-1.0, but there is a loss in accuracy for numbers with an absolute value greater than 8 388 608) LREAL X X The value is converted to the format of the target data type. (The value "1", for example, is converted to the value "1.0".) TIME - X The bit pattern of the source value is transferred unchanged rightjustified to the target data type. DTL - - No implicit conversion TOD - X The bit pattern of the source value is transferred unchanged rightjustified to the target data type. DATE - - No implicit conversion STRING - - CHAR - X The bit pattern of the source value is converted and transferred to the target data type. (for example, value conversion from DINT #-1 -> SINT #-1 or DINT #-1 -> USINT #255) The bit pattern of the source value is transferred unchanged rightjustified to the target data type. x: Conversion possible -: Conversion not possible See also UDINT (32-bit integers) (Page 1216) Setting and canceling the IEC check (Page 1256) Overview of data type conversion (Page 1253) Explicit conversion of UDINT (Page 1289) WinCC Basic V13.0 System Manual, 02/2014 1265 Programming the PLC 9.1 Creating the user program Floating-point numbers Implicit conversion of REAL Options for implicit conversion The following table shows the options for implicit conversion of the REAL data type: Source REAL Target With Without IEC check IEC check Description BOOL - - BYTE - - WORD - - DWORD - X The bit pattern of the source value is transferred unchanged rightjustified to the target data type. SINT - X USINT - X INT - X UINT - X The bit pattern of the source value is rounded off and converted and transferred to the target data type. (for example, rounding off and value conversion of REAL #2.5 -> INT #2 or negative number REAL #-2.5 -> INT #-2 -> USINT #254. With an overflow, the remainder is determined REAL #305.5 -> INT #306 -> USINT #50) DINT - X UDINT - X LREAL X X The value is transferred to the target data type. TIME - - No implicit conversion DTL - - TOD - - DATE - - STRING - - CHAR - - No implicit conversion x: Conversion possible -: Conversion not possible See also REAL (Page 1220) Setting and canceling the IEC check (Page 1256) Overview of data type conversion (Page 1253) Explicit conversion of REAL (Page 1290) 1266 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program Implicit conversion of LREAL Options for implicit conversion The following table shows the options for implicit conversion of the LREAL data type: Source LREAL Target With Without IEC check IEC check BOOL - - BYTE - - WORD - - DWORD - - SINT - X USINT - X INT - X UINT - X DINT - X UDINT - X REAL - - TIME - - DTL - - TOD - - DATE - - STRING - - CHAR - - Explanation No implicit conversion The bit pattern of the source value is rounded off and converted and transferred to the target data type. (for example, rounding off and value conversion of REAL #2.5 -> INT #2 or negative number REAL #-2.5 -> INT #-2 -> USINT #254. With an overflow, the remainder is determined REAL #305.5 -> INT #306 -> USINT #50) No implicit conversion x: Conversion possible -: Conversion not possible See also Explicit conversion of LREAL (Page 1292) WinCC Basic V13.0 System Manual, 02/2014 1267 Programming the PLC 9.1 Creating the user program Timers Implicit conversion of TIME Options for implicit conversion The following table shows the options for implicit conversion of the TIME data type: Source TIME Target With Without IEC check IEC check Description BOOL - - BYTE - - WORD - - DWORD - X The bit pattern of the source value is transferred unchanged to the target data type. The result of the conversion shows the duration in milliseconds. SINT - - No implicit conversion USINT - - INT - - UINT - - DINT - X UDINT - X The bit pattern of the source value is transferred unchanged to the target data type. The result of the conversion shows the duration in milliseconds. REAL - - No implicit conversion LREAL - - DTL - - TOD - X The bit pattern of a source value that is less than 24 h (86 400 00 ms) is transferred without changes to the target data type. No further changes are made to the target value. The result of the conversion shows the time that has passed since midnight. DATE - - No implicit conversion STRING - - CHAR - - No implicit conversion x: Conversion possible -: Conversion not possible See also TIME (IEC time) (Page 1225) Setting and canceling the IEC check (Page 1256) Overview of data type conversion (Page 1253) Explicit conversion of TIME (Page 1293) 1268 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program Date and time Implicit conversion of DTL Options for implicit conversion The DTL data type cannot be implicitly converted. See also Explicit conversion of DTL (Page 1296) Implicit conversion of TOD Options for implicit conversion The following table shows the options for implicit conversion of the TOD data type: Source TOD Target With Without IEC check IEC check Description BOOL - - BYTE - - WORD - - DWORD - X The bit pattern of the source value is transferred unchanged to the target data type. The result of the conversion corresponds to the number of milliseconds since the start of day (0:00 hrs). No implicit conversion No implicit conversion SINT - - USINT - - INT - - UINT - - DINT - X UDINT - X The bit pattern of the source value is transferred unchanged to the target data type. The result of the conversion corresponds to the number of milliseconds since the start of day (0:00 hrs). REAL - - No implicit conversion LREAL - - TIME - X The bit pattern of the source value is transferred unchanged to the target data type. The result of the conversion corresponds to the number of milliseconds since the start of day (0:00 hrs). DTL - - No implicit conversion DATE - - STRING - - CHAR - - x: Conversion possible -: Conversion not possible WinCC Basic V13.0 System Manual, 02/2014 1269 Programming the PLC 9.1 Creating the user program See also TIME_OF_DAY (TOD) (Page 1227) Setting and canceling the IEC check (Page 1256) Overview of data type conversion (Page 1253) Explicit conversion of TOD (Page 1295) Implicit conversion of DATE Options for implicit conversion The following table shows the options for implicit conversion of the DATE data type: Source DATE Target With Without IEC check IEC check Description BOOL - - BYTE - - WORD - X The bit pattern of the source value is transferred unchanged to the target data type. The result of the conversion corresponds to the number of days since 01-01-1990. DWORD - - No implicit conversion SINT - - USINT - - INT - X UINT - X The bit pattern of the source value is transferred unchanged to the target data type. The result of the conversion corresponds to the number of days since 01-01-1990. DINT - - No implicit conversion UDINT - - REAL - - LREAL - - TIME - - DTL - X The bit pattern of the source value is transferred unchanged to the target data type. The result of the conversion corresponds to the number of days since 01-01-1990. TOD - - No implicit conversion STRING - - CHAR - - No implicit conversion x: Conversion possible -: Conversion not possible See also DATE (Page 1226) Setting and canceling the IEC check (Page 1256) 1270 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program Overview of data type conversion (Page 1253) Explicit conversion of DATE (Page 1294) Character strings Implicit conversion of CHAR Options for implicit conversion The following table shows the options for implicit conversion of the CHAR data type: Source Target With Without CHAR BOOL Description IEC check IEC check - - No implicit conversion BYTE - X WORD - X DWORD - X The bit pattern of the source value is transferred unchanged rightjustified to the target data type. The remaining bits are filled from the left with "0". SINT - X USINT - X INT - X UINT - X DINT - X UDINT - X REAL - - LREAL - - TIME - - DTL - - TOD - - DATE - - STRING X X No implicit conversion The STRING is shortened to length 1 and includes the character. x: Conversion possible -: Conversion not possible See also CHAR (character) (Page 1230) Setting and canceling the IEC check (Page 1256) Overview of data type conversion (Page 1253) Explicit conversion of CHAR (Page 1297) WinCC Basic V13.0 System Manual, 02/2014 1271 Programming the PLC 9.1 Creating the user program Implicit conversion of STRING Options for implicit conversion The following table shows the options for implicit conversion of the STRING data type: Source STRING Target With Without IEC check IEC check BOOL - - BYTE - - WORD - - DWORD - - SINT - - USINT - - INT - - UINT - - DINT - - UDINT - - REAL - - LREAL - - TIME - - DTL - - DATE - - TOD - - CHAR - X Description No implicit conversion The first character of the STRING is returned if the STRING includes one or more characters. Otherwise, the character is output with coding $00. x: Conversion possible -: Conversion not possible See also Explicit conversion of STRING (Page 1298) 1272 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program Explicit conversion Binary numbers Explicit conversion of BOOL Options for explicit conversion The following table shows the options and instructions for the explicit conversion of the BOOL data type: Source Target Conversion Description Mnemonics of the instruction BOOL BYTE X BOOL_TO_BYTE WORD X DWORD X Only the LSB (Least Significant Bit) is set in the target data type. The enable output ENO is always "1". SINT X BOOL_TO_SINT USINT X BOOL_TO_USINT INT X BOOL_TO_INT UINT X BOOL_TO_UINT DINT X BOOL_TO_DINT UDINT X BOOL_TO_UDINT REAL - LREAL - - TIME - - DTL - - TOD - - DATE - - STRING - - CHAR - - No explicit conversion BOOL_TO_WORD BOOL_TO_DWORD - x: Conversion possible - : Conversion not possible See also BOOL (bit) (Page 1208) Implicit conversion of BYTE (Page 1257) Overview of data type conversion (Page 1253) WinCC Basic V13.0 System Manual, 02/2014 1273 Programming the PLC 9.1 Creating the user program Bit strings Explicit conversion of BYTE Options for explicit conversion The following table shows the options and instructions for the explicit conversion of the BYTE data type: Source Target Conversion Description Mnemonics of Instruction BYTE 1) BOOL X The following scenarios are possible: BYTE_TO_BOOL If the source is "0", the target data type is also "0" and enable output ENO is "1". If only the LSB (Least Significant Bit) "1" is set in the source value, the target data type is also "1" and enable output ENO is "1". If bits are not equal to LSB in the source value, the target data type is set according to LSB and enable output ENO is "0". WORD1) DWORD 1274 X 1) X The bit pattern of the source value is transferred unchanged right-justified to the target data type. BYTE_TO_WORD BYTE_TO_DWORD SINT X USINT X BYTE_TO_USINT INT X BYTE_TO_INT UINT X BYTE_TO_UINT DINT X BYTE_TO_DINT UDINT X BYTE_TO_UDINT REAL - LREAL - TIME X The bit pattern of the source value is transferred unchanged right-justified to the target data type. BYTE_TO_TIME DTL - No explicit conversion - TOD X X The bit pattern of the source value is transferred unchanged right-justified to the target data type. BYTE_TO_TOD DATE STRING - No explicit conversion - No explicit conversion BYTE_TO_SINT - BYTE_TO_DATE WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program Source Target Conversion Description Mnemonics of Instruction CHAR X The bit pattern of the source value is transferred unchanged right-justified to the target data type. BYTE_TO_CHAR x: Conversion possible - : Conversion not possible Bit strings (BYTE, WORD, DWORD) are interpreted as an unsigned integer with the same bit length.. Data type BYTE is interpreted as USINT, WORD as UINT and DWORD as UDINT. 1) See also BYTE (byte) (Page 1209) Implicit conversion of BYTE (Page 1257) Overview of data type conversion (Page 1253) Explicit conversion of WORD Options for explicit conversion The following table shows the options and instructions for the explicit conversion of the WORD data type: Source Target Conversion Description Mnemonics of the instruction WORD BOOL X The following scenarios are possible: WORD_TO_BOOL 1) If the source is "0", the target data type is also "0" and enable output ENO is "1". If only the LSB (Least Significant Bit) "1" is set in the source value, the target data type is also "1" and enable output ENO is "1". If bit is not equal to LSB in the source value, the target data type is set according to LSB and enable output ENO is "0". BYTE1) X DWORD1) X WinCC Basic V13.0 System Manual, 02/2014 The bit pattern of the source value is transferred unchanged right-justified to the target data type. WORD_TO_BYTE WORD_TO_DWORD 1275 Programming the PLC 9.1 Creating the user program Source Target Conversion Description Mnemonics of the instruction SINT X ENO = TRUE WORD_TO_SINT #sint1 := WORD_TO_SINT(16#FFFF); // -1 to #sint1 := WORD_TO_SINT(16#FF80); // -128 #sint1 := WORD_TO_SINT(16#0); // 0 to #sint1 := WORD_TO_SINT(16#007F); // 127 ENO = FALSE #sint1 := WORD_TO_SINT(16#FF7F); // -129 to #sint1 := WORD_TO_SINT(16#8000); // -32768 #sint1 := WORD_TO_SINT(16#0080); // 128 to #sint1 := WORD_TO_SINT(16#7FFF); // 32767 USINT X INT X The bit pattern of the source value is transferred unchanged right-justified to the target data type. UINT X DINT X WORD_TO_DINT UDINT X WORD_TO_UDINT REAL - LREAL - TIME X The bit pattern of the source value is transferred unchanged right-justified to the target data type. WORD_TO_TIME DTL - No explicit conversion - TOD X X The bit pattern of the source value is transferred unchanged right-justified to the target data type. WORD_TO_TOD DATE STRING - No explicit conversion - CHAR X The bit pattern of the source value is transferred unchanged right-justified to the target data type. WORD_TO_CHAR WORD_BCD16 INT X WORD_BCD16_TO_INT BCD16 INT X The value to be converted has data type WORD and is accepted as a BCD-coded value between -999 and +999. The result is available after conversion as an integer (in binary notation) of the type INT. A real conversion takes place. If the bit pattern includes an invalid tetrad, a synchronous error is not triggered but only the status bit OV is set instead. No explicit conversion WORD_TO_USINT WORD_TO_INT WORD_TO_UINT - WORD_TO_DATE BCD16_TO_INT x: Conversion possible - : Conversion not possible Bit strings (BYTE, WORD, DWORD) are interpreted as an unsigned integer with the same bit length.. Data type BYTE is interpreted as USINT, WORD as UINT and DWORD as UDINT. 1) 1276 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program See also WORD (Page 1210) Implicit conversion of WORD (Page 1258) Overview of data type conversion (Page 1253) Explicit conversion of DWORD Options for explicit conversion The following table shows the options and instructions for the explicit conversion of the DWORD data type: Source DWORD 1) Target Conversion Description Mnemonics of the instruction BOOL X The following scenarios are possible: DWORD_TO_BOOL If the source is "0", the target data type is also "0" and enable output ENO is "1". If only the LSB (Least Significant Bit) "1" is set in the source value, the target data type is also "1" and enable output ENO is "1". If bit is not equal to LSB in the source value, the target data type is set according to LSB and enable output ENO is "0". BYTE1) WORD X 1) WinCC Basic V13.0 System Manual, 02/2014 X The bit pattern of the source value is transferred unchanged right-justified to the target data type. DWORD_TO_BYTE DWORD_TO_WORD 1277 Programming the PLC 9.1 Creating the user program Source Target Conversion Description Mnemonics of the instruction SINT X ENO = TRUE DWORD_TO_SINT #sint1 := DWORD_TO_SINT(16#FFFF_FFFF); // -1 bis #sint1 := DWORD_TO_SINT(16#FFFF_FF80); // -128 #sint1 := DWORD_TO_SINT(16#0); // 0 bis #sint1 := DWORD_TO_SINT(16#0000_007F); / / 127 ENO = FALSE #sint1 := DWORD_TO_SINT(16#FFFF_FF7F); // -129 #sint1 := DWORD_TO_SINT(16#8000_0000); / / -2147483648 #sint1 := DWORD_TO_SINT(16#0000_0080); / / 128 bis #sint1 := DWORD_TO_SINT(16#7FFF_FFFF); // 2147483647 USINT 1278 X The bit pattern of the source value is transferred unchanged right-justified to the target data type. DWORD_TO_USINT WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program Source Target Conversion Description Mnemonics of the instruction INT X ENO = TRUE DWORD_TO_INT #int1 := DWORD_TO_INT(16#FFFF_FFFF); // -1 bis #int1 := DWORD_TO_INT(16#FFFF_8000); // -32768 #int1 := DWORD_TO_INT(16#0); // 0 bis #int1 := DWORD_TO_INT(16#0000_7FFF); // 32767 ENO = FALSE #int1 := DWORD_TO_INT(16#FFFF_7FFF); // -32769 #int1 := DWORD_TO_INT(16#8000_0000); // -2147483648 #int1 := DWORD_TO_INT(16#8000); // 32768 bis #int1 := DWORD_TO_INT(16#7FFF_FFFF); // 2147483647 DWORD_BCD32 UINT X DINT X The bit pattern of the source value is transferred unchanged right-justified to the target data type. DWORD_TO_UINT UDINT X REAL X The bit pattern of the source value is transferred unchanged right-justified to the target data type. If no errors occur during the conversion, the signal state of ENO = 1; if an error occurs during processing, the signal state of ENO = 0. DWORD_TO_REAL LREAL - No explicit conversion - TIME X The bit pattern of the source value is transferred unchanged right-justified to the target data type. DWORD_TO_TIME DTL - No explicit conversion - TOD X X The bit pattern of the source value is transferred unchanged right-justified to the target data type. DWORD_TO_TOD DATE STRING - No explicit conversion - CHAR X The bit pattern of the source value is transferred unchanged right-justified to the target data type. DWORD_TO_CHAR DINT X The value to be converted has data type DWORD and is accepted as a BCD-coded value between -9999999 DWORD_BCD32_TO_DINT WinCC Basic V13.0 System Manual, 02/2014 DWORD_TO_DINT DWORD_TO_UDINT DWORD_TO_DATE 1279 Programming the PLC 9.1 Creating the user program Source Target Conversion Description Mnemonics of the instruction BCD32 DINT X and +9999999. The result is available after conversion as an integer (in binary notation) of the type DINT. A real conversion takes place. If the bit pattern includes an invalid tetrad, a synchronous error is not triggered but only the status bit OV is set instead. BCD32_TO_DINT x: Conversion possible - : Conversion not possible Bit strings (BYTE, WORD, DWORD) are interpreted as an unsigned integer with the same bit length.. Data type BYTE is interpreted as USINT, WORD as UINT and DWORD as UDINT. 1) See also DWORD (Page 1211) Implicit conversion of DWORD (Page 1259) Overview of data type conversion (Page 1253) Integers Explicit conversion of SINT Options for explicit conversion The following table shows the options and instructions for explicit conversion of the SINT data type: Source Target Conversion Description Mnemonics of the instruction SINT BOOL X The following scenarios are possible: SINT_TO_BOOL If the source is "0", the target data type is also "0" and enable output ENO is "1". If only the LSB (Least Significant Bit) "1" is set in the source value, the target data type is also "1" and enable output ENO is "1". If bit is not equal to LSB in the source value, the target data type is set according to LSB and enable output ENO is "0". BYTE1) X WORD X 1) DWORD 1280 1) X USINT X INT X UINT X The bit pattern of the source value is transferred unchanged right-justified to the target data type. If a negative value is converted to an unsigned target data type, the enable output ENO is set to "0". The bit pattern of the source value is converted and transferred to the target data type. (The value "-1" (16#FF) becomes the value "-1" (16#FFFFFFFF). SINT_TO_BYTE SINT_TO_WORD SINT_TO_DWORD SINT_TO_USINT SINT_TO_INT SINT_TO_UINT WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program Source Target Conversion Description Mnemonics of the instruction DINT X SINT_TO_DINT UDINT X Enable output ENO is set to "0" if a negative value is converted to an unsigned target data type. REAL X SINT_TO_REAL, NORM_X LREAL X The value is converted into the format of the target data type (the value "-1" will be converted into the value "-1.0" with the "Convert value" (CONVERT) instruction. TIME X The value is transferred to the target data type and interpreted as milliseconds. SINT_TO_TIME DTL - No explicit conversion - TOD X The bit pattern of the source value is converted and transferred to the target data type. (The value "-1" (16#FF) becomes the value "-1" (16#FFFFFFFF). Enable output ENO is set to "0" if a negative value is converted to an unsigned target data type. (interpretation in milliseconds since 0:0) SINT_TO_TOD DATE X The bit pattern of the source value is converted and transferred to the target data type. (The value "-1" (16#FF) becomes the value "-1" (16#FFFFFFFF). Enable output ENO is set to "0" if a negative value is converted to an unsigned target data type. (interpretation in days since 1990-1-1) SINT_TO_DATE STRING X The value is converted to a character string. The character string is shown preceded by a sign. If the permitted length of the character string is violated, the enable output ENO is set to "0". SINT_TO_STRING, S_CONV, VAL_STRG CHAR1) X The bit pattern of the source value is transferred SINT_TO_CHAR unchanged to the target data type. If negative values are converted, the enable output ENO is set to "0". SINT_TO_UDINT SINT_TO_LREAL, NORM_X x: Conversion possible - : Conversion not possible Bit strings (BYTE, WORD, DWORD) and data type CHAR are first extended to the necessary width including sign, and then the bits are copied. The source type determines the interpretation. 1) See also SINT (8-bit integers) (Page 1212) Implicit conversion of SINT (Page 1260) Overview of data type conversion (Page 1253) WinCC Basic V13.0 System Manual, 02/2014 1281 Programming the PLC 9.1 Creating the user program Explicit conversion of USINT Options for explicit conversion The following table shows the options and instructions for explicit conversion of the USINT data type: Source Target Conversion Description Mnemonics of the instruction USINT BOOL X The following scenarios are possible: USINT_TO_BOOL If the source is "0", the target data type is also "0" and enable output ENO is "1". If only the LSB (Least Significant Bit) "1" is set in the source value, the target data type is also "1" and enable output ENO is "1". If bit is not equal to LSB in the source value, the target data type is set according to LSB and enable output ENO is "0". 1282 BYTE1) X WORD1) X The bit pattern of the source value is transferred unchanged right-justified to the target data type. USINT_TO_BYTE DWORD1) X SINT X The bit pattern of the source value is transferred unchanged to the target data type. If the sign is changed during the conversion, the enable output ENO is set to "0". USINT_TO_SINT INT X USINT_TO_INT UINT X DINT X The bit pattern of the source value is transferred unchanged right-justified to the target data type. UDINT X REAL X LREAL X TIME USINT_TO_WORD USINT_TO_DWORD USINT_TO_UINT USINT_TO_DINT USINT_TO_UDINT The value is converted into the format of the target data type (the value "1" will be converted into the value "1.0" with the "Convert value" (CONVERT) instruction. USINT_TO_REAL, NORM_X X The value is transferred to the target data type and interpreted as milliseconds. USINT_TO_TIME DTL - No explicit conversion - TOD X USINT_TO_TOD DATE X The bit pattern of the source value is transferred unchanged right-justified to the target data type. STRING X The value is converted to a character string. If the permitted length of the character string is violated, the enable output ENO is set to "0". USINT_TO_STRING, S_CONV, VAL_STRG USINT_TO_LREAL, NORM_X USINT_TO_DATE WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program Source Target Conversion Description CHAR1) X The bit pattern of the source value is USINT_TO_CHAR transferred unchanged to the target data type. Mnemonics of the instruction x: Conversion possible - : Conversion not possible Bit strings (BYTE, WORD, DWORD) and data type CHAR are first extended to the necessary width (the non-existing sign is replaced with zeros) and then the bits are copied. The source type determines the interpretation. 1) See also USINT (8-bit integers) (Page 1213) Implicit conversion of USINT (Page 1261) Overview of data type conversion (Page 1253) Explicit conversion of INT Options for explicit conversion The following table shows the options and instructions for explicit conversion of the INT data type: Source Target Conversion Description Mnemonics of the instruction INT BOOL X The following scenarios are possible: INT_TO_BOOL If the source is "0", the target data type is also "0" and enable output ENO is "1". If only the LSB (Least Significant Bit) "1" is set in the source value, the target data type is also "1" and enable output ENO is "1". If bit is not equal to LSB in the source value, the target data type is set according to LSB and enable output ENO is "0". BYTE1) X WORD X DWORD1) X SINT X USINT X UINT X DINT X UDINT X 1) REAL X LREAL X WinCC Basic V13.0 System Manual, 02/2014 The bit pattern of the source value is transferred INT_TO_BYTE unchanged right-justified to the target data type. INT_TO_WORD If a negative value is converted to an unsigned target data type, the enable output ENO is set INT_TO_DWORD to "0". The bit pattern of the source value is converted and transferred to the target data type. (The value "-1" (16#FF) becomes the value "-1" (16#FFFFFFFF). Enable output ENO is set to "0" if a negative value is converted to an unsigned target data type. INT_TO_SINT The value is converted to the format of the target data type (the value "-1", for example, is converted with the instruction "Convert value" (CONVERT) to the value "-1.0"). INT_TO_REAL, NORM_X INT_TO_USINT INT_TO_UINT INT_TO_DINT INT_TO_UDINT INT_TO_LREAL, NORM_X 1283 Programming the PLC 9.1 Creating the user program Source Target Conversion Description Mnemonics of the instruction TIME X The value is transferred to the target data type and interpreted as milliseconds. INT_TO_TIME DTL - No explicit conversion - TOD X The bit pattern of the source value is converted and transferred to the target data type. (The value "-1" (16#FF) becomes the value "-1" (16#FFFFFFFF). Enable output ENO is set to "0" if a negative value is converted to an unsigned target data type. (interpretation in milliseconds since 0:0; check for 24h limit) INT_TO_TOD DATE X The bit pattern of the source value is converted INT_TO_DATE and transferred to the target data type. (The value "-1" (16#FF) becomes the value "-1" (16#FFFFFFFF). Enable output ENO is set to "0" if a negative value is converted to an unsigned target data type. (interpretation in days since 1990-1-1; check for negative value) STRING X The value is converted to a character string. The character string is shown preceded by a sign. If the permitted length of the character string is violated, the enable output ENO is set to "0". INT_TO_STRING, S_CONV, VAL_STRG) CHAR1) X The bit pattern of the source value is converted and transferred to the target data type. (The value "-1" (16#FF) becomes the value "-1" (16#FFFFFFFF). Enable output ENO is set to "0" if a negative value is converted to an unsigned target data type. INT_TO_CHAR BCD16 X INT_TO_BCD16 BCD16_WORD X The value to be converted has type INT and is accepted as an integer with a value between -999 and +999. The result is available after conversion as a BCD-coded number of the type WORD. A real conversion takes place. If the value is outside the target area, a synchronous error is not triggered, but rather only the status bit OV is set. INT_TO_BCD16_WORD x: Conversion possible - : Conversion not possible Bit strings (BYTE, WORD, DWORD) and data type CHAR are first extended to the necessary width including sign, and then the bits are copied. The source type determines the interpretation. 1) See also INT (16-bit integers) (Page 1214) Implicit conversion of INT (Page 1262) Overview of data type conversion (Page 1253) 1284 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program Explicit conversion of UINT Options for explicit conversion The following table shows the options and instructions for explicit conversion of the UINT data type: Source Target Conversion Description Mnemonics of the instruction UINT BOOL X The following scenarios are possible: UINT_TO_BOOL If the source is "0", the target data type is also "0" and enable output ENO is "1". If only the LSB (Least Significant Bit) "1" is set in the source value, the target data type is also "1" and enable output ENO is "1". If bit is not equal to LSB in the source value, the target data type is set according to LSB and enable output ENO is "0". BYTE1) X WORD1) X DWORD1) X SINT X USINT X INT X The bit pattern of the source value is transferred unchanged to the target data type. If the sign bit is changed during the conversion, the enable output ENO is set to "0". UINT_TO_INT DINT X UINT_TO_DINT UDINT X The bit pattern of the source value is transferred unchanged right-justified to the target data type. REAL X UINT_TO_REAL, NORM_X LREAL X The value is converted to the format of the target data type (the value "1", for example, is converted with the instruction "Convert value" (CONVERT) to the value "1.0"). TIME X The value is transferred to the target data type and interpreted as milliseconds. UINT_TO_TIME DTL - No explicit conversion - TOD X The bit pattern of the source value is converted and transferred to the target data type. (The value "-1" (16#FF) becomes the value "-1" (16#FFFFFFFF). Enable output ENO is set to "0" if a negative value is converted to an unsigned target data type. (interpretation in milliseconds since 0:0; check for 24h limit) UINT_TO_TOD WinCC Basic V13.0 System Manual, 02/2014 The bit pattern of the source value is transferred unchanged right-justified to the target data type. If bits are lost in the process, the enable output ENO is set to "0". UINT_TO_BYTE UINT_TO_WORD UINT_TO_DWORD UINT_TO_SINT UINT_TO_USINT UINT_TO_UDINT UINT_TO_LREAL, NORM_X 1285 Programming the PLC 9.1 Creating the user program Source Target Conversion Description Mnemonics of the instruction DATE X The bit pattern of the source value is converted and transferred to the target data type. (The value "-1" (16#FF) becomes the value "-1" (16#FFFFFFFF). Enable output ENO is set to "0" if a negative value is converted to an unsigned target data type. (interpretation in days since 1990-1-1; check for negative value) UINT_TO_DATE, T_CONV STRING X The value is converted to a character string. If the permitted length of the character string is violated, the enable output ENO is set to "0". UINT_TO_STRING, S_CONV, VAL_STRG CHAR1) X The bit pattern of the source value is transferred unchanged to the target data type. The enable output ENO is set to "0" in the event of overflow. UINT_TO_CHAR x: Conversion possible - : Conversion not possible Bit strings (BYTE, WORD, DWORD, LWORD) and the data type CHAR are initially extended to the necessary width (the non-existing sign is replaced with zeros) and then the bits are copied. The source type determines the interpretation. 1) See also UINT (16-bit integers) (Page 1215) Implicit conversion of UINT (Page 1263) Overview of data type conversion (Page 1253) 1286 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program Explicit conversion of DINT Options for explicit conversion The following table shows the options and instructions for explicit conversion of the DINT data type: Source Target Conversio n Description Mnemonics of the instruction DINT BOOL X The following scenarios are possible: DINT_TO_BOOL If the source is "0", the target data type is also "0" and enable output ENO is "1". If only the LSB (Least Significant Bit) "1" is set in the source value, the target data type is also "1" and enable output ENO is "1". If bit is not equal to LSB in the source value, the target data type is set according to LSB and enable output ENO is "0". BYTE1) X WORD1) X DWORD 1) X The bit pattern of the source value is transferred unchanged right-justified to the target data type. If a negative value is converted to an unsigned target data type, the enable output ENO is set to "0". DINT_TO_BYTE The bit pattern of the source value is converted and transferred to the target data type. (The value "-1" (16#FF) becomes the value "-1" (16#FFFFFFFF). Enable output ENO is set to "0" if a negative value is converted to an unsigned target data type. DINT_TO_SINT The value is converted to the format of the target data type (the value "-1", for example, is converted with the instruction "Convert value" (CONVERT) to the value "-1.0"). DINT_TO_REAL, NORM_X DINT_TO_WORD DINT_TO_DWORD SINT X USINT X INT X UINT X UDINT X REAL X LREAL X TIME X The value is transferred to the target data type and interpreted as milliseconds. DINT_TO_TIME, T_CONV DTL - No explicit conversion - TOD X The bit pattern of the source value is converted and transferred to the target data type. (The value "-1" (16#FF) becomes the value "-1" (16#FFFFFFFF). Enable output ENO is set to "0" if a negative value is converted to an unsigned target data type. (interpretation in milliseconds since 0:0) DINT_TO_TOD WinCC Basic V13.0 System Manual, 02/2014 DINT_TO_USINT DINT_TO_INT DINT_TO_UINT DINT_TO_UDINT DINT_TO_LREAL, NORM_X 1287 Programming the PLC 9.1 Creating the user program Source Target Conversio n Description Mnemonics of the instruction DATE X The bit pattern of the source value is converted and transferred to the target data type. (The value "-1" (16#FF) becomes the value "-1" (16#FFFFFFFF). Enable output ENO is set to "0" if a negative value is converted to an unsigned target data type. (interpretation in days since 1990-1-1) DINT_TO_DATE STRING X The value is converted to a character string. The character string is shown preceded by a sign. If the permitted length of the character string is violated, the enable output ENO is set to "0". DINT_TO_STRING, S_CONV, VAL_STRG CHAR1) X The bit pattern of the source value is converted and transferred to the target data type. (The value "-1" (16#FF) becomes the value "-1" (16#FFFFFFFF). Enable output ENO is set to "0" if a negative value is converted to an unsigned target data type. DINT_TO_CHAR BCD32 X DINT_TO_BCD32 BCD32_DWORD X The value to be converted has type DINT and is accepted as an integer with a value between -999999 and +9999999. The result is available after conversion as a BCD-coded number of the type DWORD. The enable output is set to "0" in the event of overflow. A real conversion takes place. If the value is outside the target area, a synchronous error is not triggered, but rather only the status bit OV is set. DINT_TO_BCD32_DWORD x: Conversion possible - : Conversion not possible 1) Bit strings (BYTE, WORD, DWORD) and data type CHAR are first extended to the necessary width including sign, and then the bits are copied. The source type determines the interpretation. See also DINT (32-bit integers) (Page 1216) Implicit conversion of DINT (Page 1264) Overview of data type conversion (Page 1253) 1288 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program Explicit conversion of UDINT Options for explicit conversion The following table shows the options and instructions for explicit conversion of the UDINT data type: Source Target Conversion Description Mnemonics of the instruction UDINT BOOL X The following scenarios are possible: UDINT_TO_BOOL If the source is "0", the target data type is also "0" and enable output ENO is "1". If only the LSB (Least Significant Bit) "1" is set in the source value, the target data type is also "1" and enable output ENO is "1". If bit is not equal to LSB in the source value, the target data type is set according to LSB and enable output ENO is "0". BYTE1) X WORD1) X DWORD1) X SINT X USINT X UDINT_TO_USINT INT X UDINT_TO_INT UINT X UDINT_TO_UINT DINT X The bit pattern of the source value is transferred unchanged to the target data type. If the sign bit is changed during the conversion, the enable output ENO is set to "0". UDINT_TO_DINT REAL X UDINT_TO_REAL, NORM_X LREAL X The value is converted to the format of the target data type (the value "1", for example, is converted with the instruction "Convert value" (CONVERT) to the value "1.0"). TIME X The bit pattern of the source value is transferred unchanged right-justified and interpreted as milliseconds to the target data type. UDINT_TO_TIME DTL - No explicit conversion - TOD X The bit pattern of the source value is converted and transferred to the target data type. (The value "-1" (16#FF) becomes the value "-1" (16#FFFFFFFF). Enable output ENO is set to "0" if a negative value is converted to an unsigned target data type. (interpretation in milliseconds since 0:0; check for 24h limit) UDINT_TO_TOD, T_CONV WinCC Basic V13.0 System Manual, 02/2014 The bit pattern of the source value is transferred unchanged to the target data type. If bits are lost in the process, the enable output ENO is set to "0". UDINT_TO_BYTE UDINT_TO_WORD UDINT_TO_DWORD UDINT_TO_SINT UDINT_TO_LREAL, NORM_X 1289 Programming the PLC 9.1 Creating the user program Source Target Conversion Description Mnemonics of the instruction DATE X The bit pattern of the source value is converted and transferred to the target data type. (The value "-1" (16#FF) becomes the value "-1" (16#FFFFFFFF). Enable output ENO is set to "0" if a negative value is converted to an unsigned target data type. (interpretation in days since 1990-1-1; check for negative value) UDINT_TO_DATE STRING X The value is converted to a character string. If the permitted length of the character string is violated, the enable output ENO is set to "0". UDINT_TO_STRING, S_CONV, VAL_STRG CHAR1) X The bit pattern of the source value is transferred unchanged to the target data type. The enable output ENO is set to "0" in the event of overflow. UDINT_TO_CHAR x: Conversion possible - : Conversion not possible Bit strings (BYTE, WORD, DWORD, LWORD) and the data type CHAR are initially extended to the necessary width (the non-existing sign is replaced with zeros) and then the bits are copied. The source type determines the interpretation. 1) See also UDINT (32-bit integers) (Page 1216) Implicit conversion of UDINT (Page 1265) Overview of data type conversion (Page 1253) Floating-point numbers Explicit conversion of REAL Options for explicit conversion The following table shows the options and instructions for explicit conversion of the REAL data type: Source Target Conversion Description Mnemonics of the instruction REAL BOOL - No explicit conversion - BYTE - WORD - DWORD X The bit pattern of the source value is REAL_TO_DWORD transferred unchanged to the target data type. SINT X The value is converted to the target data type. REAL_TO_SINT, ROUND, The result of the conversion depends on the CEIL, FLOOR, TRUNC, instruction used. Enable output ENO is set to NORM_X, SCALE_X "0" if the valid range of values of the target 1290 - WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program Source Target Conversion Description Mnemonics of the instruction USINT X data type is exceeded during conversion, or if the value to be converted is an invalid floating-point number. REAL_TO_USINT, ROUND, CEIL, FLOOR, TRUNC, NORM_X, SCALE_X INT X REAL_TO_INT, ROUND, CEIL, FLOOR, TRUNC, NORM_X, SCALE_X UINT X REAL_TO_UINT, ROUND, CEIL, FLOOR, TRUNC, NORM_X, SCALE_X DINT X REAL_TO_DINT, ROUND, CEIL, FLOOR, TRUNC, NORM_X, SCALE_X UDINT X REAL_TO_UDINT, ROUND, CEIL, FLOOR, TRUNC, NORM_X, SCALE_X LREAL X The value is converted to the target data type. REAL_TO_LREAL, ROUND, The result of the conversion depends on the CEIL, FLOOR, TRUNC, instruction used, e.g. TRUNC(2.5) = 2.0; NORM_X, SCALE_X CEIL(2.5) = 3.0 TIME - No explicit conversion DTL - - TOD - - DATE - - STRING X The value is converted to a character string. Enable output ENO is set to "0" if the character string length is exceeded, or if the value to be converted is an invalid floatingpoint number. The string has a minimum length of 14 characters. REAL_TO_STRING, S_CONV, VAL_STRG CHAR - No explicit conversion - - x: Conversion possible -: Conversion not possible See also REAL (Page 1220) Implicit conversion of REAL (Page 1266) Overview of data type conversion (Page 1253) WinCC Basic V13.0 System Manual, 02/2014 1291 Programming the PLC 9.1 Creating the user program Explicit conversion of LREAL Options for explicit conversion The following table shows the options and instructions for explicit conversion of the LREAL data type: Source Target Conversion Description Mnemonics of the instruction LREAL BOOL - No explicit conversion - BYTE - - WORD - - DWORD - - SINT X USINT X INT X UINT X LREAL_TO_UINT, ROUND, CEIL, FLOOR, TRUNC, NORM_X, SCALE_X DINT X LREAL_TO_DINT, ROUND, CEIL, FLOOR, TRUNC, NORM_X, SCALE_X UDINT X LREAL_TO_UDINT, ROUND, CEIL, FLOOR, TRUNC, NORM_X, SCALE_X REAL X The value is converted to the target data type. Enable output ENO is set to "0" if the valid range of values of the target data type is exceeded during conversion, or if the value to be converted is an invalid floating-point number. A loss in accuracy is tolerated. LREAL_TO_LREAL, ROUND, CEIL, FLOOR, TRUNC, NORM_X, SCALE_X TIME - No explicit conversion - DTL - - TOD - - DATE - - STRING X 1292 The value is converted to the target data type. The result of the conversion depends on the instruction used. Enable output ENO is set to "0" if the valid range of values of the target data type is exceeded during conversion, or if the value to be converted is an invalid floating-point number. The value is converted to a character string. Enable output ENO is set to "0" if the character string length is exceeded, or if the value to be converted is an invalid floating-point number. The string has a minimum length of 21 characters. LREAL_TO_SINT, ROUND, CEIL, FLOOR, TRUNC, NORM_X, SCALE_X LREAL_TO_USINT, ROUND, CEIL, FLOOR, TRUNC, NORM_X, SCALE_X LREAL_TO_INT, ROUND, CEIL, FLOOR, TRUNC, NORM_X, SCALE_X REAL_TO_STRING, S_CONV, VAL_STRG WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program Source Target Conversion Description Mnemonics of the instruction CHAR - No explicit conversion - x: Conversion possible -: Conversion not possible See also LREAL (Page 1221) Overview of data type conversion (Page 1253) Timers Explicit conversion of TIME Options for explicit conversion The following table shows the options and instructions for explicit conversion of the TIME data type: Source Target Conversion Description Mnemonics of the instruction TIME BOOL - No explicit conversion - BYTE X WORD1) X The bit pattern of the source value is TIME_TO_BYTE transferred unchanged to the target data type. TIME_TO_WORD 1) DWORD1 X TIME_TO_DWORD ) SINT X The bit pattern of the source value is transferred unchanged right-justified and interpreted as milliseconds to the target data type. TIME_TO_SINT TIME_TO_DINT, T_CONV USINT X INT X UINT X DINT X The bit pattern of the source value is transferred unchanged to the target data type. The result of the conversion shows the duration in milliseconds. UDINT X The bit pattern of the source value is TIME_TO_UDINT transferred unchanged right-justified and interpreted as milliseconds to the target data type. Enable output ENO is set to "0" if the sign changes. REAL - No explicit conversion LREAL - - DTL - - WinCC Basic V13.0 System Manual, 02/2014 TIME_TO_USINT TIME_TO_INT TIME_TO_UINT - 1293 Programming the PLC 9.1 Creating the user program Source Target Conversion Description Mnemonics of the instruction TOD X The bit pattern of the source value is transferred unchanged right-justified to the target data type. If the source value exceeds the range of values of TOD, the target data type remains unchanged. TIME_TO_TOD DATE - No explicit conversion - STRING - - CHAR - - x: Conversion possible -: Conversion not possible Bit strings (BYTE, WORD, DWORD) and data type CHAR are first extended to the necessary width and then the bits are copied. The source type determines the interpretation. 1) See also TIME (IEC time) (Page 1225) Implicit conversion of TIME (Page 1268) Overview of data type conversion (Page 1253) Clock and calendar Explicit conversion of DATE Options for explicit conversion The following table shows the options and instructions for explicit conversion of the DATE data type: Source Target Conversion Description Mnemonics of the instruction DATE BOOL - No explicit conversion - X The bit pattern of the source value is transferred unchanged rightjustified to the target data type. DATE_TO_BYTE BYTE 1) WORD X DWORD1) X SINT X USINT X INT X DATE_TO_INT UINT X DATE_TO_UINT DINT X DATE_TO_DINT UDINT X REAL - LREAL - - TIME - - 1) 1294 The number of days since 1/1/1990 is returned as result. DATE_TO_WORD DATE_TO_DWORD DATE_TO_SINT DATE_TO_USINT DATE_TO_UDINT No explicit conversion - WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program Source Target Conversion Description Mnemonics of the instruction DTL X The bit pattern of the source value is transferred unchanged rightjustified to the target data type. DATE_TO_DTL TOD - No explicit conversion - STRING - - CHAR - - x: Conversion possible - : Conversion not possible Bit strings (BYTE, WORD, DWORD) and data type CHAR are first extended to the necessary width and then the bits are copied. The source type determines the interpretation. 1) See also DATE (Page 1226) Implicit conversion of DATE (Page 1270) Overview of data type conversion (Page 1253) Explicit conversion of TOD Options for explicit conversion The following table shows the options and instructions for explicit conversion of the TOD data type: Source Target Conversion Description Mnemonics of the instruction TOD BOOL - No explicit conversion - BYTE X X The bit pattern of the source value is transferred unchanged to the target data type. TOD_TO_BYTE WORD1) 1) TOD_TO_WORD DWORD X SINT X USINT X INT X TOD_TO_INT UINT X TOD_TO_UINT DINT X UDINT X The result of the conversion corresponds to the number of milliseconds since the start of day (0:00 hrs). TOD_TO_UDINT, T_CONV REAL - No explicit conversion - LREAL - TIME X The duration since midnight is returned as result. TOD_TO_TIME DTL X The date is set to 1.1.1970 as a result. TOD_TO_DTL 1) WinCC Basic V13.0 System Manual, 02/2014 The number of milliseconds since midnight is returned as result. TOD_TO_DWORD TOD_TO_SINT TOD_TO_USINT TOD_TO_DINT - 1295 Programming the PLC 9.1 Creating the user program Source Target Conversion Description Mnemonics of the instruction DATE - No explicit conversion - STRING - - CHAR - - x: Conversion possible -: Conversion not possible Bit strings (BYTE, WORD, DWORD) and data type CHAR are first extended to the necessary width including the sign and then the bits are copied. The source type determines the interpretation. 1) See also TIME_OF_DAY (TOD) (Page 1227) Implicit conversion of TOD (Page 1269) Overview of data type conversion (Page 1253) Explicit conversion of DTL Options for explicit conversion The following table shows the options and instructions for explicit conversion of the DTL data type: Source Target Conversion Description Mnemonics of the instruction DTL BYTE - No explicit conversion - WORD - - DWORD - - SINT - - USINT - - INT - - UINT - - DINT - - UDINT - - REAL - - LREAL - - TIME - - TOD X During the conversion, the time-of-day is extracted from the DTL format and written to the target data type. DTL_TO_TOD, T_CONV DATE X During the conversion, the date is extracted from the DTL format and written to the target data type. The enable output ENO is set to "0" in the event of overflow. DTL_TO_DATE, T_CONV STRING - No explicit conversion - 1296 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program Source Target Conversion CHAR - Description Mnemonics of the instruction - x: Conversion possible -: Conversion not possible See also DTL (Page 1229) Overview of data type conversion (Page 1253) Character strings Explicit conversion of CHAR Options for explicit conversion The following table shows the options and instructions for explicit conversion of the CHAR data type: Source Target Conversion Description Mnemonics of the instruction CHAR BOOL - No explicit conversion - BYTE X WORD1) X CHAR_TO_WORD DWORD1) X The bit pattern of the source value is transferred unchanged right-justified to the target data type. SINT X CHAR_TO_SINT USINT X CHAR_TO_USINT INT X CHAR_TO_INT UINT X CHAR_TO_UINT DINT X CHAR_TO_DINT UDINT X CHAR_TO_UDINT REAL - LREAL - - TIME - - DTL - - TOD - - DATE - - 1) WinCC Basic V13.0 System Manual, 02/2014 No explicit conversion CHAR_TO_BYTE CHAR_TO_DWORD - 1297 Programming the PLC 9.1 Creating the user program Source Target Conversion Description Mnemonics of the instruction STRING X The value is converted to the first character in the character string (STRING). If the length of the character string is not defined, the length "1" is set after the conversion. If the length of the character string is defined, this remains unchanged after the conversion. CHAR_TO_STRING x: Conversion possible - : Conversion not possible Bit strings (BYTE, WORD, DWORD) and data type CHAR are first extended to the necessary width and then the bits are copied. The source type determines the interpretation. 1) See also CHAR (character) (Page 1230) Implicit conversion of CHAR (Page 1271) Overview of data type conversion (Page 1253) Explicit conversion of STRING Options for explicit conversion The following table shows the options and instructions for explicit conversion of the STRING data type: Source Target Conversion Description Mnemonics of the instruction STRING BOOL - No explicit conversion - BYTE - - WORD - - DWORD - - SINT X USINT X INT X UINT X Sign DINT X UDINT X REAL X The first character of the string may be a sign (+, -) or a number. Leading spaces will be ignored. The dot is used as separation for the conversion of floating-point numbers. The exponential notation "e" or "E" is not permitted. The comma as thousand separator is permitted to the left of the decimal point but will be ignored. If the layout of the character string is invalid for the 1298 Conversion begins with the first character in the character string (STRING) and stops at the end of the string or at the first inadmissible character. The following characters are permitted for conversion: Digit Dot STRING_TO_SINT, S_CONV, STRG_VAL STRING_TO_USINT, S_CONV, STRG_VAL STRING_TO_INT, S_CONV, STRG_VAL STRING_TO_UINT, S_CONV, STRG_VAL STRING_TO_DINT, S_CONV, STRG_VAL STRING_TO_UDINT, S_CONV, STRG_VAL STRING_TO_REAL, S_CONV, STRG_VAL WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program Source Target Conversion Description Mnemonics of the instruction LREAL X conversion or an overflow occurs, then the enable output ENO will be set to "0". STRING_TO_LREAL, S_CONV, STRG_VAL TIME - No explicit conversion - DTL - - TOD - - DATE - CHAR1) X The first character in the character string STRING_TO_CHAR, (STRING) is transferred to the destination S_CONV data type. If the string is empty, then the value "0" will be written in the destination data type. x: Conversion possible - : Conversion not possible See also STRING (Page 1231) Overview of data type conversion (Page 1253) 9.1.1.6 Program flow control EN/ENO mechanism Basics of the EN/ENO mechanism Introduction Runtime errors that require a program abort can occur during the processing of instructions. You can use the EN/ENO mechanism to avoid such program aborts. This mechanism can be used at two levels: EN/ENO mechanism for individual instructions EN/ENO mechanism for block calls EN/ENO mechanism for instructions in LAD/FBD In LAD and FBD, certain instructions have an enable input EN and an enable output ENO. You can use the enable input EN to make the execution of the instruction dependent on conditions. The instructions are only executed if the signal state is "1" at the enable input EN. You can use the enable output ENO to query runtime errors in instructions and react to these. The enable output ENO returns the signal state "1" if one of the following conditions applies: No error occurred during processing. The enable output ENO returns signal state "0" if one of the following conditions applies: WinCC Basic V13.0 System Manual, 02/2014 1299 Programming the PLC 9.1 Creating the user program The EN input has signal state "0". An error occurred during processing. The EN/ENO mechanism is used for the following basic instructions: Mathematical functions Move operations Conversion operations Word logic operations Shift + rotate In LAD and FBD, you can switch the evaluation of the enable output ENO on and off by means of the shortcut menu specifically for certain instructions. EN/ENO mechanism for block calls in LAD/FBD All blocks that you call in LAD or FBD are provided with an enable input EN and an enable output ENO when called. This applies to all called blocks, regardless of the programming language in which they were created. You can use the enable input EN to call the block depending on conditions. The block is only executed if the signal state is "1" at the enable input EN. You can query the error status of the block with the enable output ENO. It has signal "1" as soon as the execution of the block starts. If you do not explicitly set the output ENO to "0" in the program code, it retains signal "1". However, you can explicitly set it to "0" to return an error statement to the called block. In LAD or FBD, the output ENO is set with the instruction "RET: Return". See also: Example of the use of the EN/ENO mechanism in LAD (Page 1302) Example of the use of the EN/ENO mechanism in FBD (Page 1302) EN/ENO mechanism for STL In STL, the EN/ENO mechanism is not required for individual instructions. This function is mapped by language-specific instruction sequences. Blocks that you call from an STL block are not provided with the EN and ENO parameters. Regardless of the programming language in which they were created, you can transfer an error statement to the calling STL block using the BR bit of the status word. In STL, you can evaluate the error status of the called block by linking the BR bit of the status word with the RLO. It has signal "1" as soon as the execution of the block starts. If you do not explicitly set it to "0" in the program code, it retains signal "1". However, you can explicitly set it to "0" to return an error statement to the calling block. In STL, the error statement is set with the instructions "SAVE" or "JNB". See also: Example of the simulation of the EN/ENO mechanism in STL (Page 1304) 1300 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program EN/ENO mechanism in SCL With SCL, the use of the EN/ENO mechanism for instructions is optional. You can activate it with the block property "Set ENO automatically". If the property is active, all blocks implicitly receive an error handling. You can implement a conditional block call with the enable input EN. Use the enable input EN in the parameter list as a normal input parameter. If EN has signal "1" or when EN is not used, the block is called. If EN has signal "0", the block is not called. Note When you call functions in SCL, you cannot use the release mechanism via EN. Use an IF statement instead to call functions conditionally. You can query the error status of the block with the enable output ENO. If the ENO has signal "1", the block was processed without errors. If the ENO has signal "0", an error occurred during processing. To query the state of the enable output, insert an additional output parameter with the name ENO in the parameter list during a block call. See also: Example of the use of the EN/ENO mechanism in SCL (Page 1303) ENO in GRAPH (S7-1500) In GRAPH, you can use the ENO operand to evaluate whether an action has been completed successfully. You can select the "Set ENO automatically" option for this. Select the option in the program properties in order for it to be used as the default setting for new GRAPH blocks. Select the option in the block properties in order for it to be used for specific blocks. If this option is selected, the ENO operand is displayed when testing with program status. This operand has the value "TRUE" if the action was successful and "FALSE" if the action failed. The ENO operand can be used in the following cases: When blocks are called that have the enable output ENO. For instructions in which errors can occur, e.g., conversions or mathematical functions. EN/ENO mechanism for memory and I/O access errors You cannot evaluate memory and I/O access errors with the EN/ENO mechanism. You do this either with the global troubleshooting via OBs (S7-300/400 and S7-1200/1500) or local troubleshooting using the "GetError" instruction (S7-1200/1500 only). If a memory access error occurred for an instruction, you can evaluate the associated ENO. See also Enabling and disabling the EN/ENO mechanism (Page 1429) WinCC Basic V13.0 System Manual, 02/2014 1301 Programming the PLC 9.1 Creating the user program Example of the use of the EN/ENO mechanism in LAD Description The following figure shows an ADD instruction with EN and ENO protective circuit: $'' ,17 7DJ,Q (1 7DJB9DOXH ,1 7DJB9DOXH ,1 7DJ2XW 6 (12 287 7DJB5HVXOW After the normally open contact, the RLO contains the previous result of logic operation: If "TagIn" signal is "0", the addition is not executed. EN and ENO both lead to the signal state "0". If "TagIn" signal is "1", EN is also "1" and the addition is executed. If no errors occur during the processing of the instruction, the output ENO also has the signal state "1" and the output ""TagOut"" is set. See also Basics of the EN/ENO mechanism (Page 1299) ADD: Add (Page 1848) Example of the use of the EN/ENO mechanism in FBD Description The following figure shows an ADD instruction with EN and ENO protective circuit: $'' ,17 7DJ,Q (1 7DJB9DOXH ,1 287 7DJB9DOXH ,1 (12 7DJB5HVXOW 7DJ2XW If "TagIn" signal is "1", EN is also "1" and the addition is executed. If no errors occur during the processing of the instruction, the output ENO also has the signal state "1" and the output ""TagOut"" is set. If "TagIn" signal is "0", the addition is not executed. EN and ENO both lead to the signal state "0". 1302 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program See also Basics of the EN/ENO mechanism (Page 1299) Example of the use of the EN/ENO mechanism in SCL Example of the EN/ENO mechanism for basic instructions To use the EN/ENO mechanism for instructions in SCL, you have to activate the block property "Set ENO automatically". The following example shows the use of the enable output ENO for the "a/b" instruction. SCL "MyoutputREAL" :=a/b; IF ENO THEN "MyOutputBool":=1; ELSE "MyOutputBool":=0; END_IF; If the "a/b" instruction is executed error-free, MyOutputBool has signal "1". Example of the use of the EN/ENO mechanism in block calls The following example shows the use of the enable output ENO for a block call. SCL "MyDB"."MyFB"(EN:="MyTag1">"MyTag2", in1:="MyInputBool1", in2:="MyInputBool1", EN0=>"MyOutputBool"); If MyTag1 is not greater than MyTag2 the block call is not processed. EN and ENO both lead to the signal state "0". If MyTag1 is greater than MyTag2, EN has signal "1" and the block call is executed. If all instructions within MyFB are executed error-free, MyOutputBool has signal "1". See also Basics of the EN/ENO mechanism (Page 1299) WinCC Basic V13.0 System Manual, 02/2014 1303 Programming the PLC 9.1 Creating the user program Example of the simulation of the EN/ENO mechanism in STL Description The following example shows an program section for adding values with EN and ENO connected: STL Description A"Tag_Input_1" // Query whether the signal state of the operand is "1" and AND with current RLO JNBMyLABEL // Evaluation of the EN input // If RLO="0" jump to jump label "MyLABEL" and save the current RLO in the BR // Execute next instruction if RLO="1" L"Tag_Input_2" // Load first value of addition L"Tag_Input_3" // Load second value of addition +I // Add values T "Tag_Result" // Transfer sum to the operand "Tag_Result" AN OV // Query if errors occurred SAVE // Transfer signal state of the RLO to the BR bit CLR // Reset RLO to "0" MyLABEL: U BR // Jump label "MyLABEL" // Query BR and AND with RLO = "Tag_Output" // Assign signal state of the RLO to the operand "Tag_Output" The query of the operand "U" Tag_Input_1"" provides the result of the preceding logic operation (RLO). The instruction "Jump at RLO = 0 and save RLO (SPBNB)" saves the RLO to the BR. The instruction "Jump if RLO = 0 and save RL0" also evaluates the RLO and executes one of the following actions depending on the evaluation: If the RLO is "0", the processing of the program is continued at the jump label "MyLABEL" with the query of the BR. The addition is not executed. Assign the current RLO to the operand "Tag_Output". If the RLO is "1", the addition is executed. A query of the overflow bit (OV) shows if an error occurred during the addition. The query result is saved in the BR. The operation "CLR" resets the RLO to "0". The BR is then queried for "1" and AND'd with the current RLO. The result is assigned to the operand "Tag_Output". The signal state of the BR and of the operand "Tag_Output" shows if the addition was carried out with any error See also Basics of the EN/ENO mechanism (Page 1299) 1304 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program 9.1.2 Declaring PLC tags 9.1.2.1 Overview of PLC tag tables Introduction PLC tag tables contain the definitions of the PLC tags and symbolic constants that are valid throughout the CPU. A PLC tag table is created automatically for each CPU used in the project. You can create additional tag tables and use these to sort and group tags and constants. In the project tree there is a "PLC tags" folder for each CPU of the project. The following tables are included: "All tags" table Standard tag table Optional: Other user-defined tag tables All tags The "All tags" table gives an overview of all PLC tags, user constants and system constants of the CPU. This table cannot be deleted or moved. Standard tag table There is one standard tag table for each CPU of the project. It cannot be deleted, renamed or moved. The default tag table contains PLC tags, user constants and system constants. You can declare all PLC tags in the default tag table, or create additional user-defined tag tables as you want. User-defined tag tables You can create multiple user-defined tag tables for each CPU to group tags according to your requirements. You can rename, gather into groups, or delete user-defined tag tables. Userdefined tag tables can contain PLC tags and user constants. See also Structure of the PLC tag tables (Page 1306) Using tags within the program (Page 1179) Basics of constants (Page 1180) WinCC Basic V13.0 System Manual, 02/2014 1305 Programming the PLC 9.1 Creating the user program 9.1.2.2 Structure of the PLC tag tables Introduction Each PLC tag table contains a tab for tags and a tab for user constants. The default tag table and the "All tags" table also have a "System constants" tab. Structure of the "PLC tags" tab In the "Tags" tab you declare the global PLC tags that you require in the program. The following figure shows the tab structure. The number of columns shown may vary. The following table shows the meaning of the individual columns. The number of columns shown may vary. You can show or hide the columns as required. Column Description Symbol you can click on to drag-and-drop a tag to a program for use as an operand. Name Unique name for the constants throughout the CPU. Data type Data type of the tags. Address Tag address. Retain Marks the tag as retentive. The values of retentive tags are retained even after the power supply is switched off. Accessible from HMI Shows whether HMI can access this tag during runtime. Visible in HMI Shows whether the tag is visible by default in the operand selection of HMI. Monitor value Current data value in the CPU. This column only appears if an online connection is established and you select the "Monitor all" button. Tag table Shows which tag table includes the tag declaration. This column is only available in the "All tags" table. Comment Comment to document the tags. Structure of the "User constants" and "System constants" tabs In the "User constants" you define symbolic constants that are valid throughout the CPU. The constants required by the system are shown in the "Systems constants" tab. System constants can be hardware IDs, for example, which can be used for identification of modules. The following figure shows the structure of both tabs. The number of columns shown may vary. 1306 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program The following table shows the meaning of the individual columns. You can show or hide the columns as required. Column Description Symbol you can click to move a tag into a network via a drag-anddrop operation for use as an operand. Name Unique name for the constants throughout the CPU. Data type Data type of the constants Value Value of the constants Tag table Shows which tag table includes the constant declaration. This column is only available in the "All tags" table. Comment Comments to document the tags. See also Using tags within the program (Page 1179) Basics of constants (Page 1180) Overview of PLC tag tables (Page 1305) Show and hide table columns (Page 1327) Editing tables (Page 226) 9.1.2.3 Rules for PLC tags Valid names of PLC tags Permissible characters The following rules apply to the use of names for PLC tags: Letters, numbers, special characters are permitted. Quotation marks are not permitted. WinCC Basic V13.0 System Manual, 02/2014 1307 Programming the PLC 9.1 Creating the user program Unique tag names The names of the PLC tags must be unique throughout the CPU, even if the tags are located in different tag tables of a CPU. A name that is already used for a block, another PLC tag or a constant within the CPU, cannot be used for a new PLC tag. The uniqueness check does not differentiate between use of small and capital letters. If you enter an already assigned name another time, a sequential number is automatically appended to the second name entered. For example, if you enter the name "Motor" a second time, the second entry is changed to "Motor(1)". Unique table names The names of the PLC tag tables must also be unique throughout the CPU. A unique name is automatically suggested when user-defined PLC tag tables are being created. See also Using tags within the program (Page 1179) Permissible addresses and data types of PLC tags (Page 1308) Keywords (Page 1173) Permissible addresses and data types of PLC tags The addresses of PLC tags are made up of the particulars of the operand area and the address within this area. The addresses must be unique throughout the CPU. If you enter an address that is already assigned to another tag, the address will be highlighted at both places in yellow and an error message will be issued. 1308 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program Operand areas The following table shows the possible operand areas. The available data types depend on the CPU you use: Operand area Description Data type Format Internatio nal mnemoni cs German mnemoni cs I E Input bit BOOL I x.y I E Input (64-bit) LWORD, LINT, ULINT, LTIME, LTOD, LDT, LREAL, PLC data type I x.0 BYTE, CHAR, SINT, USINT, PLC data type IB x WORD, INT, UINT, DATE, S5TIME, PLC data type IW x Input double word DWORD, DINT, UDINT, REAL, TIME, TOD, PLC data type ID x Output bit BOOL Q x.y Address area: S7-1200 S7-300/400 S7-1500 0.0..1023.7 0.0..65535.7 0.0..32767.7 - - 0.0..32760.0 0..1023 0..65535 0..32767 0..1022 0..65534 0..32766 0..1020 0..65532 0..32764 0.0..1023.7 0.0..65535.7 0.0..32767.7 - - 0.0..32760.0 0..1023 0..65535 0..32767 0..1022 0..65534 0..32766 E x.y IB IW ID Q EB EW ED A Input byte Input word E x.0 EB y EW y ED y A x.y Q QB QW A AB AW WinCC Basic V13.0 System Manual, 02/2014 Output (64bit) LWORD, LINT, ULINT, LTIME, LTOD, LDT, LREAL, PLC data type Q x.0 Output byte BYTE, CHAR, SINT, USINT, PLC data type QB x WORD, INT, UINT, DATE, S5TIME, PLC data type QW x Output word A x.0 AB y AW y 1309 Programming the PLC 9.1 Creating the user program Operand area Description Internatio nal mnemoni cs German mnemoni cs QD AD Data type Format Output double word DWORD, DINT, UDINT, REAL, TIME, TOD, PLC data type QD x Address area: S7-1200 S7-300/400 S7-1500 0..1020 0..65532 0..32764 AD y M M Memory bit BOOL M x.y 0.0..8191.7 0.0..65535.7 0.0..16383.7 M M Bit memory (64-bit) LREAL M x.0 0.0..8184.0 - 0.0..16376.0 M M Bit memory (64-bit) LWORD, LINT, ULINT, LTIME, LTOD, LDT M x.0 - - 0.0..16376.0 MB MB Memory byte BYTE, CHAR, SINT, USINT MB x 0..8191 0..65535 0..16383 MW MW Memory word WORD, INT, UINT, DATE, S5TIME MW x 0..8190 0..65534 0..16382 MD MD Memory double word DWORD, DINT, UDINT, REAL, TIME, TOD MD x 0..8188 0..65532 0..16380 T T Time function (for S7-300/400 only) Timer Tn - 0..65535 0..2047 C Z Counter function (for S7-300/400 only) Counter Zn - 0..65535 0..2047 Cn Addresses The following table shows the possible addresses of tags: 1310 Data type Address Example BOOL Tags with BOOL data type are addressed with a byte number and a bit number. The numbering of the bytes begins for each operand area at 0. The numbering of the bits goes from 0 to 7. A 1.0 BYTE, CHAR, SINT, USINT Tags with BYTE, CHAR, SINT, and USINT data type are addressed with a byte number. MB 1 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program Data type Address Example WORD, INT, UINT, DATE, S5TIME Tags with WORD, INT, UINT, DATE, S5TIME data type consist of two bytes. They are addressed with the number of the lowest byte. IW 1 DWORD, DINT, UDINT, REAL, TIME, TOD Tags with DWORD, DINT, UDINT, REAL, TIME, TOD data type consist of four bytes. They are addressed with the number of the lowest byte. AD 1 LWORD, LINT, ULINT, LTIME, LTOD, LDT, LREAL Tags of data type LWORD, LINT, ULINT, LTIME, LTOD, LDT, and LREAL consist of eight bytes. They are addressed with it number 0 and the number of the lower byte. I 1.0 Mnemonics used The addresses that you enter in the PLC tag table are automatically adapted to the set mnemonics. See also Setting the mnemonics (Page 1364) Using tags within the program (Page 1179) Valid names of PLC tags (Page 1307) Overview of the valid data types (Page 1204) 9.1.2.4 Creating and managing PLC tag tables Creating a PLC tag table You can created multiple user-defined PLC tag tables in a CPU. Each tag table must have have a unique name throughout the CPU. Requirement The project view is open. Procedure To created a new PLC tag table, follow these steps: 1. Open the "PLC tags" folder under the CPU in the project tree. 2. Double-click the "Add new tag table" entry. A new PLC tag table with the default name "TagTable_x" is created. 3. Select the PLC tag table in the project tree. WinCC Basic V13.0 System Manual, 02/2014 1311 Programming the PLC 9.1 Creating the user program 4. Select the "Rename" command in the shortcut menu. 5. Type in a name that is unique throughout the CPU. Result A new PLC tag table is created. You can now declare tag and constants in this table. See also Overview of PLC tag tables (Page 1305) Structure of the PLC tag tables (Page 1306) Grouping PLC tag tables You can gather the user-defined tag tables of the CPU into groups. You cannot, however, move the standard tag table and the "All tags" table into a group. Requirement Multiple user-defined tag tables are contained in the "PLC tags" folder of the CPU. Procedure To gather multiple PLC tag tables into a group, follow these steps: 1. Select the "PLC tags" folder under the CPU in the project tree. 2. Select the "Insert > Group" menu command. A new group with the standard name "Group_x" is inserted. 3. Select the newly inserted group in the project tree. 4. Select the "Rename" command in the shortcut menu. 5. Assign the new group a unique name throughout the CPU. 6. Drag to the new group the tables you want to group together. Result The tag tables are gathered in the new group. See also Overview of PLC tag tables (Page 1305) Structure of the PLC tag tables (Page 1306) 1312 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program Opening the PLC tag table Procedure To open the PLC tag table in a CPU, proceed as follows: 1. Open the "PLC tags" folder under the CPU in the project tree. 2. Double-click the PLC tag table in the folder. 3. Select the desired tab in the upper corner. Result The PLC tag table associated with the CPU opens. You can declare the required tags and constants. See also Overview of PLC tag tables (Page 1305) Structure of the PLC tag tables (Page 1306) 9.1.2.5 Declaring PLC tags Entering a PLC tag declaration Declaring tags in the PLC tag table Requirements The "Tags" tab of the PLC tag table is open. Procedure To define PLC tags, follow these steps: 1. Enter a tag name in the "Name" column. 2. Enter the required data type in the "Data type" column. You will be supported by autocompletion during input. An address corresponding to the data type is automatically appended. 3. Optional: Click on the arrow key in the "Address" column and enter an operand identifier, an operand type, an address and a bit number in the dialog which then opens. 4. Optional: Enter a comment in the "Comments" column. 5. Repeat steps 1 to 4 for all the tags you require. See also: Permissible addresses and data types of PLC tags (Page 1308) WinCC Basic V13.0 System Manual, 02/2014 1313 Programming the PLC 9.1 Creating the user program Syntax check A syntax check is performed automatically after each entry, and any errors found are displayed in red. You do not have to correct these errors immediately - you can continue editing and make any corrections later. As long as the tag declaration contains syntax errors and the tag is used in the program, you will not be able to compile the program. See also Valid names of PLC tags (Page 1307) Declaring PLC tags in the program editor (Page 1314) Structure of the PLC tag tables (Page 1306) Editing tables (Page 226) Declaring PLC tags in the program editor Requirement The program editor is open. Procedure To declare operands as global PLC tags, follow these steps: 1. Insert an instruction in your program. The "<???>", "<??.?>" or "..." strings represent operand placeholders. 2. Replace an operand placeholder with the name of the PLC tag to be created. 3. Select the tag name. If you want to declare multiple PLC tags, select the names of all the tags to be declared. 4. Select the "Define tag" command in the shortcut menu. The "Define tag" dialog box opens. This dialog displays a declaration table in which the name of the tag is already entered. 5. Click the arrow key in the "Section" column and select one of the following entries: - Global Memory - Global Input - Global Output 6. In the other columns, enter the address, data type, and comments. See also: Permissible addresses and data types of PLC tags (Page 1308) 7. If the CPU contains multiple PLC tag tables, you can use an entry in the "PLC tag table" column to indicate in which table the tag is to be inserted. If you make no entry in the column, the new tag will be inserted in the default tag table. 8. Click the "Define" button to complete your entry. 1314 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program Result The tag declaration is written to the PLC tag table and is valid for all blocks in the CPU. See also Valid names of PLC tags (Page 1307) Editing tables (Page 226) Declaring tags in the PLC tag table (Page 1313) Setting the retentivity of PLC tags Retentive behavior of PLC tags Retentive PLC tags Each CPU has a memory area whose content remains available even after the supply voltage has been switched off. This area is referred to as retentive memory area. To avoid data loss during power failure, you can save specific PLC tags to this memory area. You specify the retain setting of PLC tags in the PLC tag table. Depending on the CPU family, the retentive memory area can accommodate various type of PLC tags. The following table provides an overview of the options of the various CPUs: CPU type Retentive bit memories Retentive SIMATIC timers Retentive SIMATIC counters S7-300/400 series - - S7-1200 series - - S7-1500 series See also Setting the retentive behavior of PLC tags (Page 1315) Setting the retentive behavior of PLC tags Introduction In the PLC tag table you can specify the width of the retentive memory area for PLC tags. All tags with addresses in this memory area are then designated as retentive. You can recognize the retentivity setting of a tag by the check mark set in the "Retain" column of the PLC tag table. Requirement The "PLC tags" tab of the PLC tag table is open. WinCC Basic V13.0 System Manual, 02/2014 1315 Programming the PLC 9.1 Creating the user program Procedure To define the width of the retentive memory area for PLC tags, follow these steps: 1. On the toolbar, click the "Retain" button. The "Retain memory" dialog will open. 2. Specify the width of the retentive memory area by entering the number of retentive bytes, timers or counters in the input field. 3. Click the "OK" button. Result The width if the retentive memory area is defined. In the "Retain" column of the tag table a check mark is automatically set for all tags that are located within the retentive memory area. See also Retentive behavior of PLC tags (Page 1315) Editing tables (Page 226) 9.1.2.6 Grouping PLC tags for inputs and outputs in structures Other useful information regarding structured PLC tags Use of structured PLC tags (S7-1200 V4 and higher/S7-1500) To make your program easier to view, you can group several input or output addresses in a higher-level PLC tag. The higher-level PLC tag represents a structure that contains several logically related inputs or outputs. When the block is called, you transfer the higher-level tag and thus need only an input or output parameter for all associated inputs or outputs. Principle of operation To create a structured PLC tag, you initially define a PLC data type (UDT). In it you declare the necessary data elements and specify their names and data types. Then, you switch to the PLC tag table and specify the higher-level PLC tag there. As a data type for the tag, you select your PLC data types. The system now reserves a certain number of input or output addresses starting from the start address of the higher-level tag. The number of reserved addresses depends on the length of your PLC data type. If you call a block that requires the reserved inputs or outputs for program execution, you transfer the higher-level tag as a block parameter. You can address the individual PLC tags like structure elements in the program code. A detailed description of the individual handling steps can be found in the following chapters. 1316 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program Application example You can use structured PLC tags in order to group the inputs or outputs of a function module. The following figure shows the schematic representation of a motor: A component was created in the "Datatype_Motor" PLC data type for each of the three inputs. The memory areas of the declared tags must not overlap. In the example, you see that the "Speed" component has the data type "Integer" and therefore must start at a word address. For this reason, the first input word has been filled with the "Dummy" fill tag. This means that "Speed" is located on the second input word. 0RWRU 2Q 2II 6SHHG The following figure shows the higher-level "Motor" PLC tag that is based on the "Data type_Motor" data type. With the declaration of "Motor", the addresses IW0 and IW1 are reserved on the input module. The following figure shows the transfer of the "Motor" PLC tag as an input parameter of the "Motor_Control" block. You can address the individual components of the tag in the "Motor_Control" block. WinCC Basic V13.0 System Manual, 02/2014 1317 Programming the PLC 9.1 Creating the user program Addressing Description "Motor" Addressing the higher-level PLC tag. "Motor".On Addressing a component of a structured PLC tag. "Motor".On:P Addressing an I/O input or output (PI or PO). Rules for use of structured PLC tags Note the following rules when creating and using structured PLC tags. Structured PLC tags can be used in the "Inputs" and "Outputs" operand areas. Structured tags are not permitted in the bit memory address area. Structured PLC tags cannot be addressed from HMI. Observe the following rules when creating the PLC data type that is to serve as the basis for a PLC tag: The memory areas of the individual elements must not overlap. See also: Permissible addresses and data types of PLC tags (Page 1308) Do not group inputs and outputs in one PLC data type but create different PLC data types for inputs and outputs. Do not group inputs or outputs from different modules in a PLC data type because it is not guaranteed that the process images of the modules are updated synchronously. In the lower-level PLC data types, all data types are permitted except for the "STRING" data type. See also Creating structured PLC tags (Page 1318) Creating structured PLC tags Rules Note the following rules when creating structured PLC tags: Use separate PLC data types for the "Inputs" and "Outputs" operand areas. Structured tags are not permitted in the bit memory address area. Do not group inputs or outputs from different modules in a PLC data type because it is not guaranteed that the process images of the modules are updated synchronously. 1318 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program Procedure To create a structured PLC tag, follow these steps: 1. Double-click the "Add new data type" command in the "PLC data types" folder in the project tree. A new declaration table for creating a PLC data type will be created and opened. 2. Declare all the necessary components in the PLC type. All data types except the "STRING" data type are permitted. 3. Select the PLC data type in the project tree and select the "Compile > Software (only changes)" command from the shortcut menu. The PLC data type is compiled and can then be used in the PLC tag table. Even when you make changes to existing PLC data types, you must recompile the program. This updates all locations of use of the PLC data type. 4. Open a PLC tag table within the same CPU. 5. Declare a new tag or select an existing tag. 6. In the "Data type" column, select the PLC data type and assign it to the PLC tag. The PLC tag receives the structure of the PLC data type. A suitable address is assigned automatically. Structured PLC tags always start at word addresses. The highest structure element is displayed without its subelements in the table. Note Assignment rules and default values For the declaration of the PLC data type, note that the memory areas of the individual tags must not overlap. For example, tags of data type "Integer" must start at a word limit. If necessary, insert "fill tags" to prevent overlaps. See also: Permissible addresses and data types of PLC tags (Page 1308) It is not possible to assign default values for the individual components. Values that you enter in the "Default value" column are not evaluated. Tags of data types "DT" and "DTL" may therefore contain invalid values. See also Other useful information regarding structured PLC tags (Page 1316) 9.1.2.7 Declaring global constants Rules for global constants Permitted characters Names of global constants may consist of the following characters: Letters, numbers, special characters are permitted. Quotation marks are not permitted. WinCC Basic V13.0 System Manual, 02/2014 1319 Programming the PLC 9.1 Creating the user program Unique constant names The names of global constants must be unique throughout the CPU, even if the constants are located in different tag tables of a CPU. A name that is already used for a block, a PLC tag or another constant within the CPU, cannot be used for new constant. The uniqueness check does not differentiate between use of small and capital letters. If you enter an already assigned name another time, a sequential number is automatically appended to the second name entered. For example, if you enter the name "Motor" a second time, the second entry is changed to "Motor(1)". Permitted data types For constants, all data types supported by the CPU are permitted, with the exception of structured data types. Permitted values You can select any value from the value range of the specified data type as constant value. For information on the value ranges, refer to the "Data types" chapter. See also: Auto-Hotspot See also Basics of constants (Page 1180) Declaring global constants (Page 1320) Declaring global constants Introduction You declare constants in the "User constants" tab of a PLC tag table. During declaration you have to to enter a symbolic name, a data type and a fixed value for each constant. You can select any value from the value range of the specified data type as constant value. For information on the value ranges, refer to the "Data types" chapter. See also: Auto-Hotspot Procedure To declare constants, follow these steps: 1. Open a PLC tag table. 2. Open the "User constants" tab. The constants table opens. 3. Enter a constant name in the "Name" column. 4. Enter the required data type in the "Data type" column. You will be supported by autocompletion during input. 1320 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program 5. Enter a constant value in the "Value" column; this constant value must be valid for the selected data type. 6. If you want, enter comments on the constants in the "Comments" column. The entry of a comment is optional. 7. If you want to declare additional constants, place the cursor in the next row and repeat steps 3 to 6. Syntax check A syntax check is performed automatically after each entry, and any errors found are displayed in red. You do not have to correct these errors immediately - you can continue editing and make any corrections later. As long as the tag declaration contains syntax errors and the constant is used in the program, you will not be able to compile the program. See also Opening the PLC tag table (Page 1313) Inserting a table row in the PLC tag table (Page 1324) Structure of the PLC tag tables (Page 1306) Rules for global constants (Page 1319) Editing tables (Page 226) 9.1.2.8 Editing properties Editing the properties of PLC tags Properties of PLC tags Overview The following table provides an overview of the properties of PLC tags. The display of properties may vary depending on the CPU type. Group Property Description General Name A unique name within the CPU. Data type Data type of the tags. Address Tag address. Retain Shows whether the tag is in the retentive memory area. Comment Comment on the tag. Date created Time when the tag was created (cannot be changed). Last modified Time when the tag was last changed (cannot be changed). History WinCC Basic V13.0 System Manual, 02/2014 1321 Programming the PLC 9.1 Creating the user program Group Property Description Usage Visible in HMI Shows whether the tag is visible by default in the HMI selection list. Accessible from HMI Shows whether HMI can access this tag during runtime. See also Editing the properties of PLC tags (Page 1322) Editing the properties of PLC tags Editing properties in a PLC tag table To edit the properties of one or more tags, follow these steps: 1. In the project tree, double-click the PLC tag table that contains the tags. The PLC tag table opens. 2. Change the entries in the columns. Editing addresses in the program editor To edit the address of a tag in the program editor, follow these steps: 1. Select the tag name. 2. Select the "Rewire tag" command in the shortcut menu. The "Rewire tag" dialog will open. The dialog shows a declaration table. 3. Enter the new address in the "Address" column. 4. Click the "Change" button to confirm the input. Editing names in the program editor To edit the name of a tag in the program editor, follow these steps: 1. Select the tag name. 2. Select the "Rename tag" command in the shortcut menu. The "Rename tag" dialog opens. The dialog shows a declaration table. 3. Enter the new name in the "Name" column. 4. Click the "Change" button to confirm the input. Effect in the program In the case of a change of the tag's name, data type or address, each location of use of the tag is automatically updated in the program. 1322 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program See also Properties of PLC tags (Page 1321) Editing properties of global constants Properties of global constants Overview The following table gives an overview of the properties of constants: Group Property Description General Name A unique name within the table Data type Data type of the constants Value Value that you defined for the constants. This value must be compatible with the declared data type. See also: Auto-Hotspot History Comment Comment on the constants Date created Time when the constant was created (cannot be changed) Last modified Time when the constant was last changed (cannot be changed) Editing properties of global constants Editing properties in a PLC tag table To edit the properties of one or more constants, follow these steps: 1. In the project tree, double-click the PLC tag table that contains the constants. The PLC tag table opens. 2. Open the "User constants" tab. 3. Change the entries in the "Name", "Data type", "Value", or "Comments" column. Effect in the program In the case of a change of a constant's name, data type or value, each location of use of the constant is automatically updated in the program. See also Editing tables (Page 226) WinCC Basic V13.0 System Manual, 02/2014 1323 Programming the PLC 9.1 Creating the user program 9.1.2.9 Monitoring of PLC tags Monitoring of PLC tags You can monitor the current data values of the tags on the CPU directly in the PLC tag table. Requirements An online connection to the CPU is available. Procedure To monitor the data values, proceed as follows: 1. Open a PLC tag table. 2. Start monitoring by clicking the "Monitor all" button. The additional "Monitor value" column is displayed in the table. This shows the current data values. 3. End the monitoring by clicking the "Monitor all" button again. Note You also have the option of copying PLC tags to a monitor or force table so that you can monitor, control or force them in the table. See also Structure of the PLC tag tables (Page 1306) Introduction to testing with the watch table (Page 1655) Introduction for testing with the force table (Page 1682) Copying entries in the PLC tag table (Page 1325) 9.1.2.10 Editing PLC tag tables Inserting a table row in the PLC tag table Procedure Proceed as follows to insert a row above the selected row: 1. Select the row in front of which you want to insert a new row. 2. Click the "Insert row" button on the toolbar of the table. 1324 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program Result A new row is inserted above the selected row. See also Editing tables (Page 226) Copying entries in the PLC tag table You can copy PLC tags within a table or to other tables. Procedure To copy a tag, follow these steps: 1. Select the tags you want to copy. You can also select several tags by clicking on them one after the other while holding down the <Ctrl> key or by pressing and holding down <Shift> and clicking on the first and last tag. 2. Select "Copy" in the shortcut menu. 3. Position the insertion pointer at the location where you want to insert the tags. 4. Select "Paste" in the shortcut menu. Or 1. Select the tag. 2. Hold down the left mouse button. 3. At the same time, press <Ctrl>. 4. Drag the tag to the destination. Result The tag is copied to the destination. If there is a name conflict, a number is automatically appended to the tag name. For example, "Tag" becomes "Tag(1)". All other properties of the tag remain unchanged. See also Editing tables (Page 226) WinCC Basic V13.0 System Manual, 02/2014 1325 Programming the PLC 9.1 Creating the user program Deleting entries in the PLC tag table Procedure Follow the steps below to delete elements: 1. Select the row with the element to be deleted. You can also select several rows by clicking on them one after the other while holding down the <Ctrl> key or by pressing and holding down <Shift> and clicking on the first and last row. 2. Select the "Delete" command in the shortcut menu. See also Editing tables (Page 226) Sorting rows in the PLC tag tables You can sort the rows in the tables alphanumerically by name, data type, or address. Procedure To sort the table rows, follow these steps: 1. Select the column by which you want to sort. 2. Click the column header. The column will be sorted in order of increasing values. An up arrow shows the sort sequence. 3. In order to change the sort sequence, click the arrow. The column will be sorted in order of decreasing values. A down arrow shows the sort sequence. 4. To restore the original sequence, click a third time on the column header. See also Editing tables (Page 226) Automatically filling in cells in the PLC tag table You can load the contents of one or several table cells into the cells below, automatically filling in the successive cells. If you automatically fill in cells in the "Name" column, a consecutive number will be appended to each name. For example, "Motor" will become "Motor_1". If you fill the cells in the column "Address" automatically, the addresses will be increased depending on the indicated data type. 1326 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program Procedure To automatically fill in successive cells, follow these steps: 1. Select the cells to be loaded. 2. Click the "Fill" symbol in the bottom right corner of the cell. The mouse pointer is transformed into a crosshair. 3. Keep the mouse button pressed and drag the mouse pointer downwards over the cells that you want to fill in automatically. 4. Release the mouse button. The cells are filled in automatically. If entries are already present in the cells that are to be automatically updated, a dialog appears in which you can indicate whether you want to overwrite the existing entries or whether you want to insert new rows for the new tags. See also Editing tables (Page 226) Show and hide table columns You can show or hide the columns in a table as needed. Procedure To show or hide table columns, follow these steps: 1. Click a column header. 2. Select the "Show/Hide" command in the shortcut menu. The selection of available columns is displayed. 3. To show a column, select the column's check box. 4. To hide a column, clear the column's check box. See also Editing tables (Page 226) Editing PLC tags with external editors Basics for importing and exporting Introduction You can export PLC tag tables to a standardized XLSX format for editing with external table editors. Similarly, you can import PLC tag tables created with external table editors to the TIA Portal. WinCC Basic V13.0 System Manual, 02/2014 1327 Programming the PLC 9.1 Creating the user program Overwriting existing PLC tags and constants during import Existing entries of the same name will be overwritten during import if they have the same name as the entries that will be imported. Link to existing objects References to PLC tags or constants that already exist in the project are updated automatically during import. The update is executed based on the name of the PLC tags and constants. See also Format of the export file (Page 1328) Exporting PLC tags (Page 1329) Importing PLC tags (Page 1329) Format of the export file Introduction During the export of PLC tag tables, a standardized XSLX format will be generated that you can edit with external table editors. This format is also expected during the import of tables. Format of the export file The sheet is always named "PLC Tags". This sheet can contain the displayed columns. The sorting order of columns can vary. The sheet does not necessarily have to include all columns. During import, the following values will be identified by a <no value> entry. The names of the column headers are also clearly defined and are always expected in English. The following table specifies the contents expected for the individual columns: 1328 Element Explanation Name Name of the tags Path Group and name of the PLC tag table Data Type The notation of the data type corresponds to the notation used in the PLC tag table. Logical Address The address can be specified with German or international mnemonics. Comment Free-form comments Hmi Visible The value TRUE or FALSE is expected. Hmi Accessible The value TRUE or FALSE is expected. WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program See also Basics for importing and exporting (Page 1327) Exporting PLC tags (Page 1329) Importing PLC tags (Page 1329) Exporting PLC tags Requirement A PLC tag table is open. Procedure To export PLC tags and constants, follow these steps: 1. In the PLC tag table, click the "Export" button. The "Export to Excel" dialog opens. 2. Select the path to which you want to save the export file. 3. Select whether to export tags and/or constants. 4. Click the "OK" button. Result The export file will be generated. Errors and warnings generated during export are indicated in the "Info" tab of the Inspector window. See also Basics for importing and exporting (Page 1327) Format of the export file (Page 1328) Importing PLC tags (Page 1329) Importing PLC tags Requirement A table exists and it conforms to format specifications. WinCC Basic V13.0 System Manual, 02/2014 1329 Programming the PLC 9.1 Creating the user program Procedure To import a PLC tag table, follow these steps: 1. Open the "All tags" table. 2. Click the "Import" button. The "Import from Excel" dialog opens. 3. Select whether to import PLC tags and/or constants. 4. Select the table you want to import. 5. Click the "OK" button. Result The PLC tag table will be imported. Errors and warnings generated during export are indicated in the "Info" tab of the Inspector window. See also Basics for importing and exporting (Page 1327) Format of the export file (Page 1328) Exporting PLC tags (Page 1329) Editing individual PLC tags with external editors To edit individual PLC tags in external editors outside the TIA portal, you can export or import these tags using copy and paste. However, you cannot copy structured tags to an editor. Requirement A PLC tag table and an external editor are opened. Procedure To export and import individual PLC tags, follow these steps: 1. Select one or more PLC tags. 2. Select "Copy" in the shortcut menu. 3. Switch to the external editor and paste the copied tags. 4. Edit the tags as required. 5. Copy the tags in the external editor. 6. Switch back to the PLC tag table. 7. Select "Paste" in the shortcut menu. 1330 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program Note You also have the option of export or importing PLC tags as mass data. See also: Auto-Hotspot 9.1.3 Creating and managing blocks 9.1.3.1 Creating blocks Block folder Function You can find a "Program blocks" folder in the project tree, in which you can create and manage the following blocks: Organization blocks (OB) Function blocks (FB) Functions (FCs) Data blocks (DB) A "System blocks" subfolder containing another subfolder, "Program resources", is also created in the "Program blocks" folder the first time you drag an instruction to your program which is an internal system function block. The instance data block of the internal system function block is also pasted to the "Program resources" folder. You can move or copy such instance data blocks from the "Program resources" folder to any other folder and rename or delete them. You can also move your blocks into the "Program resources" folder. Blocks in the "Program resources" folder that are not required to run the user program are removed during the next compilation. If the "Program resources" folder contains no more blocks then it is also deleted with the "System blocks" folder. A program cycle OB is automatically generated for each device and inserted in the "Program blocks" folder. See also Creating functions and function blocks (Page 1333) Creating data blocks (Page 1334) Creating organization blocks (Page 1332) Using blocks from libraries (Page 1335) WinCC Basic V13.0 System Manual, 02/2014 1331 Programming the PLC 9.1 Creating the user program Creating organization blocks Requirement The "Program blocks" folder in the project tree is open. Procedure To create an organization block, follow these steps: 1. Double-click the "Add new block" command. The "Add new block" dialog box opens. 2. Click the "Organization block (OB)" button. 3. Select the type of new organization block. 4. Enter a name for the new organization block. 5. Enter the properties of the new organization block. 6. To enter additional properties for the new organization block, click "Additional information". An area with further input fields is displayed. 7. Enter all the properties you require. 8. Activate the "Add new and open" check box if the organization block does not open as soon as it is created. 9. Confirm your entries with "OK". Result The new organization block is created. You can find the organization block in the project tree in the "Program blocks" folder. You can assign additional parameters to some organization blocks in the inspector window or device view after they have been created. The organization block description will state whether the newly created organization block has additional parameters. See also Organization blocks (OB) (Page 1146) Block folder (Page 1331) Creating functions and function blocks (Page 1333) Creating data blocks (Page 1334) Using blocks from libraries (Page 1335) Entering a block title (Page 1341) Entering a block comment (Page 1342) 1332 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program Creating functions and function blocks Requirement The "Program blocks" folder in the project tree is open. Procedure To create a function (FC) or a function block (FB), follow these steps: 1. Double-click the "Add new block" command. The "Add new block" dialog box opens. 2. Click the "Function block (FB)" or "Function (FC)" button. 3. Enter a name for the new block. 4. Enter the properties of the new block. 5. To enter additional properties for the new block, click "Additional information". An area with further input fields is displayed. 6. Enter all the properties you require. 7. Activate the "Add new and open" check box if the block does not open as soon as it is created. 8. Confirm your entries with "OK". Result The new block is created. You can find the block in the project tree in the "Program blocks" folder. See also Function blocks (FB) (Page 1147) Functions (FCs) (Page 1146) Basics of block access (Page 1151) Block folder (Page 1331) Creating organization blocks (Page 1332) Creating data blocks (Page 1334) Using blocks from libraries (Page 1335) Entering a block title (Page 1341) Entering a block comment (Page 1342) WinCC Basic V13.0 System Manual, 02/2014 1333 Programming the PLC 9.1 Creating the user program Creating data blocks Requirement The "Program blocks" folder in the project tree is open. Procedure To create a data block, follow these steps: 1. Double-click the "Add new block" command. The "Add new block" dialog box opens. 2. Click the "Data block (DB)" button. 3. Select the type of the data block. You have the following options available to you: - To create a global data block, select the list entry "Global DB". - To create an ARRAY data block, select the "ARRAY DB" entry in the list. - To create an instance data block, select the function block to which you want to assign the instance data block from the list. The list contains only the function blocks that were previously created for the CPU. - To create a data block based on a PLC data type, select the PLC data type from the list. The list contains only the PLC data types that were previously created for the CPU. - To create a data block based on a system data type, select the system data type from the list. The list contains only those system data types that have already been inserted to program blocks in the CPU. 4. Enter a name for the data block. 5. Enter the properties of the new data block. 6. If you have selected an ARRAY DB as the data block type, enter the ARRAY data type and the high limit for the ARRAY. You can change the high limit for the ARRAY at any time in the property window of the created block. The ARRAY data type cannot be changed subsequently. 7. To enter additional properties of the new data block, click "Additional information". An area with further input fields is displayed. 8. Enter all the properties you require. 9. Activate the "Add new and open" check box if the block does not open as soon as it is created. 10.Confirm your entry with "OK". Result The new data block is created. You can find the data block in the project tree in the "Program blocks" folder. 1334 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program See also Global data blocks (DB) (Page 1148) Instance data blocks (Page 1149) Block folder (Page 1331) Creating organization blocks (Page 1332) Creating functions and function blocks (Page 1333) Using blocks from libraries (Page 1335) Basics of block access (Page 1151) System data types (Page 1249) Using blocks from libraries You can save blocks in the project library or in a global library, so that you can use them more than once within a user program. You can insert the blocks as master copies or as types. See also: Library basics (Page 325) Requirement The "Libraries" task card is displayed. No write protection is set for global libraries. Adding blocks as master copies to the project library or to a global library To add new blocks as master copies to the project library or to a global library, follow these steps: 1. Maximize the project library or the global library. 2. Use drag-and-drop to move the block you wish to add to the library to the "Master copies" folder or any one of the "Master copies" subfolders in the project library or a global library. Do not release the left mouse button until a small plus sign appears underneath the mouse pointer. Or: 1. Copy the element you want to add as master copy. 2. Maximize the project library or the global library. 3. Right-click the "Master copies" folder or any of its subfolders. 4. Select "Paste" in the shortcut menu. WinCC Basic V13.0 System Manual, 02/2014 1335 Programming the PLC 9.1 Creating the user program Adding blocks as types to the project library or to a global library To add new blocks as types to the project library or to a global library, follow these steps: 1. Maximize the project library or the global library. 2. Drag-and-drop the element you want to add as a type into the "Types" folder or any of its subfolders in the project library or a global library. Do not release the left mouse button until a small plus sign appears underneath the mouse pointer. Or: 1. Copy the element you want to add as a type. 2. Maximize the project library or the global library. 3. Right-click the "Types" folder or any of its subfolders. 4. Select "Paste" in the shortcut menu. Using blocks of the project library or a global library To use a block from the project library or a global library in your project, follow these steps: 1. Maximize the project library or the global library so that you can see the block you wish to use. 2. Use a drag-and-drop operation to move the block to the CPU block folder. If the selected insertion points is not allowed, the mouse pointer will appear as a circle with a slash. Note If you derive an instance from a type in a global library, the type is also inserted into the project library. The instance is then only linked to the type in the project library. See also Using libraries (Page 325) 1336 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program Copying and pasting blocks Basics of copying and pasting blocks Function You can also create new blocks by copying existing blocks and pasting the copy. Note the following principles when copying to CPUs of the same device family: You can copy organization blocks (OBs), functions (FCs), function blocks (FBs), and global data blocks (DBs) without restriction. You can copy instance data blocks only for the same function block, since the assignment to the function block cannot be changed afterwards. However, the assignment is canceled if you copy the instance data block to a different CPU. If a function block with the same name exists there, the instance data block will be assigned to this function block. If you copy the instance data block together with the function block into the other CPU, the instance data block is assigned to the copy of the function block. The various device families sometimes support different blocks, especially in the case of organization blocks. However, function blocks and functions can also be programmed on the various devices with different access types. Therefore, not all blocks are supported on all devices. Note the following principles when copying to a different device family: WinCC Basic V13.0 System Manual, 02/2014 1337 Programming the PLC 9.1 Creating the user program Copying to an S7-1200 CPU: - Organization blocks with "Optimized" access type can be copied to an S7-1200. If the copied OB type is supported by the S7-1200 CPU, the copied OB retains the properties of its event. You must, however, compile it again. - Although organization blocks with the "Standard" access type can be copied to an S7-1200, they are not supported by the CPU. - Function blocks (FBs), functions (FCs) and global data blocks (DBs) with "Optimized" access type can be copied to an S7-1200. However, they must be recompiled after this. - Although function blocks (FBs), functions (FCs) and global data blocks (DBs) with "Standard" access type can be copied to an S7-1200, they are not supported by the CPU. - Instance data blocks: If there is a function block in the target CPU with the name that was assigned to the instance data block in the source CPU, the instance data block is assigned to the function block in the target CPU. If you copy the instance data block together with the function block to which it was assigned in the source CPU into the target CPU, the instance data block is assigned to the copy of the function block. Copying to an S7-1500 CPU: - Organization blocks with "Optimized" access type can be copied to an S7-1500. If the copied OB type is supported by the S7-1500 CPU, the copied OB retains the properties of its event. You must, however, compile it again. OB types that are not supported receive a no parking symbol. - Organization blocks with "Standard" access type can be copied to an S7-1500. If the OB derives from an S7-300/400 CPU, it receives the standard event of the corresponding OB type. If the OB derives from an S7-1200/1500 CPU, it receives the properties of its event. However, it must be compiled again. - Function blocks (FBs), functions (FCs) and global data blocks (DBs) with "Optimized" access type can be copied to an S7-1500. However, they must be recompiled after this. - Although function blocks (FBs), functions (FCs) and global data blocks (DBs) with "Standard" access type can be copied to an S7-1500, they are not supported by the CPU. - Instance data blocks: If there is a function block in the target CPU with the name that was assigned to the instance data block in the source CPU, the instance data block is assigned to the function block in the target CPU. If you copy the instance data block 1338 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program together with the function block to which it was assigned in the source CPU into the target CPU, the instance data block is assigned to the copy of the function block. Copying to S7-300/400 CPUs: - Organization blocks can be copied as required between S7-300 and S7-400. - Although organization blocks from S7-1200/1500 CPUs can be copied to S7-300/400 CPUs, they are not supported by the target CPU. - Function blocks (FBs), functions (FCs) and global data blocks (DBs) can be copied as required between S7-300 and S7-400. - Although function blocks (FBs), functions (FCs) and global data blocks (DBs) can be copied from S7-1200/1500 CPUs to S7-300/400 CPUs, they are not supported by the target CPU. - Instance data blocks: If there is a function block in the target CPU with the name that was assigned to the instance data block in the source CPU, the instance data block is assigned to the function block in the target CPU. If you copy the instance data block together with the function block to which it was assigned in the source CPU into the target CPU, the instance data block is assigned to the copy of the function block. In the project tree, blocks that are not supported are indicated by the no parking symbol. Blocks with a no parking symbol cannot be edited, but only used again as copy source. Copying data With paste, all the block data is copied and forwarded to the copy. This data includes: Block interface tags All networks Comments in all existing compilations Messages defined in the block The entire program code of the copied block including the call instructions contained in the block. However, called blocks and their associated instance data blocks are not copied. Avoiding name conflicts during pasting When pasting copied blocks with identical names to already existing blocks, the following mechanisms are used to avoid name conflicts: Pasting the copied block into the same CPU: The copy of the block gets a name that is extended by a number. For example, if block "A" is copied, a possible name for the copy is "A_1". Consecutive numbering is not used, but rather the smallest free number. The copy of block "A" can also get the name "A_25", if no lower number is available. Pasting the copied block into another CPU: A dialog box opens in which you can select whether the block with the same name will be replaced or the copied block will be pasted with a duplicate designation (Name_Number). WinCC Basic V13.0 System Manual, 02/2014 1339 Programming the PLC 9.1 Creating the user program Note Number conflicts Number conflicts may occur, if the pasted block has the same block number as an existing block. The block number is not automatically changed during pasting. This double number may have an effect on block calls. When you copy blocks you should therefore check the block number carefully and correct duplicate block numbers manually or using the block properties. Duplicate block numbers lead to a compilation error. See also Copying blocks (Page 1340) Pasting blocks (Page 1340) Copying blocks Requirement The "Program blocks" folder is opened in the project tree. Procedure To copy a block, follow these steps: 1. Right-click the block that you want to copy. 2. Select "Copy" in the shortcut menu. Result A copy of the block is now on the clipboard and can be pasted either into the same CPU or into another one. See also Basics of copying and pasting blocks (Page 1337) Pasting blocks (Page 1340) Pasting blocks Requirement You have copied a block. 1340 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program Procedure To paste a copied block and its data into a CPU, follow these steps: 1. In the project tree, open the folder structure for the CPU into which you want to paste the copied block. Note Please note that you can only paste the copied block into a CPU which supports the block programming language and type. 2. Right-click on the "Program blocks" folder. 3. Select "Paste" in the shortcut menu. - If you are pasting the block into the same CPU as the original block, "_<consecutive number>" will be appended to the name of the copy. - If you are pasting the block into a different CPU where a block of the same name already exists, the "Paste" dialog box opens. Select the required option and confirm with "OK". See also Basics of copying and pasting blocks (Page 1337) Copying blocks (Page 1340) Entering a block title The block title is the title of the block. It is not the same thing as the block name, which was assigned when the block was created. The length of the block title is restricted to one row. You can enter the block title for open and closed blocks. Requirement A code block is available. Enter block title for open block To insert the block title in an open block, follow these steps: 1. Click on the title bar of the block in the program editor. 2. Enter the block title. Enter block title for closed blocks To insert the block title in a closed block, follow these steps: 1. Right-click the block in the project tree. 2. Select the "Properties" command in the shortcut menu. The dialog with the properties of the block opens. WinCC Basic V13.0 System Manual, 02/2014 1341 Programming the PLC 9.1 Creating the user program 3. Select the entry "Information" in the area navigation. 4. Enter the block title in the "Title" input field. 5. Confirm your entry with "OK". See also Creating organization blocks (Page 1332) Creating functions and function blocks (Page 1333) Entering a block comment (Page 1342) Entering a block comment You can use the block comment to document the entire code block. For example, you can indicate the purpose of the block or draw attention to special characteristics. You can enter the block comment for open and closed blocks. Requirement A code block is available. Enter block comment for open blocks To insert a block comment in an open block, proceed as follows: 1. Click the small arrow in front of the block title. The right arrow becomes a down arrow, and the comment area is displayed. 2. Click "Comment" in the comment area. The "Comment" text passage is selected. 3. Enter the block comment. Enter block comments for closed blocks To insert the block comment in a closed block, follow these steps: 1. Right-click the block in the project tree. 2. Select the "Properties" command in the shortcut menu. The dialog with the properties of the block opens. 3. Select the entry "Information" in the area navigation. 4. Enter the block comment in the "Comment" input field. 5. Confirm your entry with "OK". 1342 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program See also Creating organization blocks (Page 1332) Creating functions and function blocks (Page 1333) Entering a block title (Page 1341) 9.1.3.2 Specifying block properties Basics of block properties Block properties Each block has certain properties, which you can display and edit. These properties are used amongst other things to: Identify the block Display the memory requirements and the compilation status of the block Display the time stamp Display the reference information Specify the access protection See also Overview of block properties (Page 1343) Block time stamps (Page 1346) Displaying and editing block properties (Page 1348) Setting the mnemonics (Page 1364) Overview of block properties Overview The properties of the blocks are block and CPU-specific. Not all properties are therefore available for all blocks or in all CPU families. The following table gives an overview of block properties: Group Property Description General Name Unique block name within the station Constant name Name of the constant pasted for the OB in the PLC tag table Type Block type (cannot be changed) Number Block number Event class Event class of an OB (cannot be changed) WinCC Basic V13.0 System Manual, 02/2014 1343 Programming the PLC 9.1 Creating the user program Group Property Description Language Programming language of the block Language in networks Language used to program conditions in GRAPH blocks. Process image partition number Display of the process image partitions that are assigned to the organization block (cannot be changed) ARRAY data type Data type of an ARRAY data block (cannot be changed) ARRAY limit High limit of an ARRAY data block The "Move operations" section of the "Instructions" task card offers options for addressing of ARRAY data blocks. Information Time stamps Compilation Protection Title Block title Comment Block comment Version Version number of the block Family Block family name Author Name of the author, company name, department name, or other names User-defined ID ID created by the user Block Times of creation and time of change of the block (cannot be changed) Interface Time of creation of the block interface (cannot be changed) Code Code modification time (non-editable) Data Data modification time (non-editable) Status Details of the last compilation run (cannot be changed) Lengths Details of the block lengths (cannot be changed) Protection Setting up know-how protection and copy protection for the block See also: Protecting blocks Attributes Optimized block access The tag declaration for blocks with optimized access contains only the symbolic names of the data elements. The system automatically optimizes and manages the addresses. The CPU performance increases and access errors, for example, from SIMATIC HMI, are prevented. See also: Auto-Hotspot IEC check The compatibility of the operands in comparison operations and arithmetic operations are tested according to IEC 61131. You have to explicitly convert non-compatible operands. See also: Overview of data type conversion (Page 1253) Handle errors within block Troubleshooting inside the block with the GET_ERROR or GET_ERR_ID instruction (cannot be changed). See also: Auto-Hotspot 1344 Create extended status information Allows you to monitor all tags in an SCL block. This option does, however, increase the program memory space required and the execution times. Check ARRAY limits Checks whether array indexes are within the range declared for an ARRAY during the runtime of an SCL block. The block enable output ENO is set to "0" if an array index is outside of the permitted range. Set ENO automatically Checks whether errors occur in the processing of certain instructions during the runtime of an SCL block. The block enable output ENO is set to "0" if a runtime error occurs. WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program Group Property Description Create minimized DB Creates instance data blocks for GRAPH blocks of the S7-300 and S7-400 in minimized format. This option reduces the GRAPH FB memory space required, however you will only receive limited program status information. Skip steps If the transitions before and after a step become valid simultaneously in a GRAPH block, the step will not be activated and will be skipped. Acknowledge supervision alarms Any supervision error which occurs during the operation of a GRAPH block must be acknowledged before the program can continue. Permanent processing of all interlocks in manual mode Permanently monitors all interlock conditions in a GRAPH block in manual mode. Lock operating mode selection Prevents a GRAPH block operating mode being selected. Data block write-protected in the device Indicates whether the data block is read-only in the target system, and cannot be overwritten while the program is running (for data blocks only) Only store in load memory On activation the data block is stored only in the load memory, occupies no space in the work memory, and is not linked into the program. The "Move operations" section of the "Instructions" task card offers options for transferring data blocks to the work memory (for data blocks only). Start information Here you specify the structure of the start information of the OB for S7-1500 CPUs: either like for S7-300 and S7-400 CPUs or optimized start information. Priority Shows the priority set for organization blocks. The CPU family used and the type of the organization block determine whether you can change the priority. Parameter assignment by means of registers Enables parameter input by means of registers in an STL block of S7-1500. This feature allows you to use the "Conditional call of blocks" (CC) and "Unconditional call of blocks" (UC) instructions in the block. Block can be used as know-how protected library item Shows whether or not the block in the library can be used with know-how protection. Enable readback Enables you to mark individual parameters of the block for readback. The "Tag readback" function is relevant if the block is used in a CFC chart. Block representation Specifies how the block is represented in a CFC chart. Time-of-day interrupt Time-of-day interrupt Parameters of the time-of-day interrupt OB: active (yes or no), execution, start date and time, local time or system time Cyclic interrupt Cyclic interrupt Cycle time and phase shift of the cyclic interrupt OB Triggers Triggers Display of start events of the hardware interrupt OB Isochronous mode Isochronous mode Parameters of the isochronous mode interrupt OB: application cycles, automatic setting (yes or no), delay time. Also indicated is the PROFINET IO system or DP master system whose IO devices or DP slaves are assigned to the isochronous mode interrupt OB. Download without reinitialization Reserve in volatile memory Defines the reserve in volatile memory that can be used for interface extensions. The number of currently available bytes is displayed in parentheses. This information is updated with each compilation. WinCC Basic V13.0 System Manual, 02/2014 1345 Programming the PLC 9.1 Creating the user program Group Property Description Activate download without reinitialization for retentive tags Enables definition of a reserve in retentive memory. Reserve in retentive memory Defines the reserve in retentive memory that can be used for interface extensions. The number of currently available bytes is displayed in parentheses. This information is updated with each compilation. See also Basics of block properties (Page 1343) Block time stamps (Page 1346) Displaying and editing block properties (Page 1348) Basics of block access (Page 1151) Block time stamps Introduction Blocks receive a number of different time stamps which show you when the block was created and when it was last changed. These time stamps are also used for automatic consistency checks before compilation. Code block time stamps The following time stamps are generated for code blocks (OBs, FBs, FCs): Block: Created on, Modified on Interface: Modified on Code/data: Modified on A time stamp conflict is displayed during compilation if the time stamp for the block calling is older than that of the interface for the block called. Time stamps for code blocks are updated as follows: Block: The time stamp for the last block modification is always the same as the time stamp either of the interface or of the code depending on which area was modified last. Interface: The interface time stamp is updated each time the interface is modified. Even if you manually undo a change to the interface, for example change the name back, that is also a change which updates the time stamp. However, if you undo the change using the "Undo" function, the time stamp will be reset to the value it had before the undone change. Code/data: The code time stamp is updated each time the block code is changed. Even if you manually undo a change to the code, for example remove an instruction, that is also a change which will update the time stamp. However, if you undo the change using the "Undo" function, the time stamp will be reset to the value it had before the undone change. 1346 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program Global data block time stamps The following time stamps are generated for global data blocks: Block: Created on, Modified on Interface: Modified on Data: Modified on Time stamp conflict is reported during compilation of a global data block based on a PLC data type if the time stamp of the global data block is older than the time stamp of the PLC data type used. The time stamps for global data blocks are updated as follows: Block: The time stamp for the last change to a global data block is always the same as the time stamp for the interface and the data. Interface and data: The interface time stamps and the data are updated each time the global data block is changed. Even if you manually undo a change, for example remove a tag, that is also a change which will update the time stamp. However, if you undo the change using the "Undo" function, the time stamps will be reset to the value they had before the undone change. Instance data block time stamps The following time stamps are generated for instance data blocks: Block: Created on, Modified on Interface: Modified on Data: Modified on A time stamp conflict will be reported during compilation of an instance data block if the interface time stamps of the instance data block are not identical to those of the function block. The time stamps for instance data blocks are updated as follows: Block: The time stamp for the last change to an instance data block is always the same as the time stamp for the interface and the data. Interface and data: The interface time stamps and the data are updated each time the instance data block is changed. Even if you manually undo a change, for example cancel the tag retain setting, that is also a change which will update the time stamps. However, if you undo the change using the "Undo" function, the time stamps will be reset to the value they had before the undone change. PLC data type time stamps The following time stamps are generated for PLC data types: Block: Created on, Modified on Interface: Modified on The time stamps for PLC data types are updated as follows: WinCC Basic V13.0 System Manual, 02/2014 1347 Programming the PLC 9.1 Creating the user program Block: The time stamp for the last change to a PLC data type is always the same as the interface time stamp. Interface: The interface time stamp is updated each time the PLC data type is changed. Even if you manually undo a change, for example delete the content of a PLC data type, that is also a change which will update the time stamp. However, if you undo the change using the "Undo" function, the time stamp will be reset to the value it had before the undone change. See also Basics of block properties (Page 1343) Overview of block properties (Page 1343) Displaying and editing block properties (Page 1348) Basic information on compiling blocks (Page 1594) Displaying and editing block properties The properties of the blocks are block and CPU-specific. Not all properties are therefore available for all blocks or in all CPU families. Properties that can only be displayed are writeprotected. Displaying and editing properties of a closed block To display and edit the properties of a closed block, follow these steps: 1. Open the "Program blocks" folder in the project tree. 2. Right-click the block whose properties you want to display or edit. 3. Select the "Properties" command in the shortcut menu. The properties dialog box of the block opens. 4. In the area navigation, click a group whose properties you want to display or edit. 5. Change the relevant property. 6. Confirm your entries with "OK". Displaying and editing properties of an open block To display or edit the properties of an open block, follow these steps: 1. Select the "Inspector window" check box in the "View" menu. The Inspector window opens. 2. Click the "Properties" tab. The properties of the block are shown in the "Properties" tab of the Inspector window. 3. In the area navigation, click a group whose properties you want to display or edit. 4. Change the relevant property. 1348 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program Result The properties of the block will be changed. The changes are not saved until the project is saved. See also Basics of block properties (Page 1343) Overview of block properties (Page 1343) Block time stamps (Page 1346) 9.1.3.3 Managing blocks Opening blocks You can open a block in several different ways: Open block directly You can open a block directly if the corresponding block folder is open in the project tree or in the overview window. Find and open block You can look for blocks within a project, a device or the "Program blocks" folder and then open them. Open block directly To open a block directly, follow these steps: 1. Open the folder with the block you wish to open in the project tree or in the overview window. 2. Double-click on the block you wish to open. Find and open block To find and then open a block, follow these steps: 1. Right-click on the project, a device, the "Program blocks" folder or a lower-level folder of "Program blocks" in the project tree. 2. Select the "Search in PLC and open" command from the shortcut menu. The "Search in PLC and open" dialog box is displayed. 3. Enter the name, the address or the type of block you are looking for. The block list is filtered further with each letter entered. The block list is closed if there is no block that matches the input. You can show the complete block list at any time by clicking the button to the right of the text box. Keep in mind that there is no filtering in this case. If you want to filter for your inputs again, click the button once again. 4. In the block list, click the block you wish to open. WinCC Basic V13.0 System Manual, 02/2014 1349 Programming the PLC 9.1 Creating the user program Result The block will open in the program editor. See also Saving blocks (Page 1350) Closing blocks (Page 1350) Renaming blocks (Page 1351) Deleting blocks offline (Page 1352) Deleting blocks online (Page 1352) Opening know-how protected blocks (Page 1614) Saving blocks Blocks are always saved together with the project. Faulty blocks can also be saved. This allows the error to be resolved at a convenient time. Procedure To save a block, follow these steps: 1. Select the "Save" or "Save as" command in the "Project" menu. See also: Saving projects (Page 248) See also Opening blocks (Page 1349) Closing blocks (Page 1350) Renaming blocks (Page 1351) Deleting blocks offline (Page 1352) Deleting blocks online (Page 1352) Closing blocks Procedure To close a block, follow these steps: 1. Click the "Close" button in the title bar of the program editor. Note Note that the block will not be saved on closing. 1350 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program See also Opening blocks (Page 1349) Saving blocks (Page 1350) Renaming blocks (Page 1351) Deleting blocks offline (Page 1352) Deleting blocks online (Page 1352) Renaming blocks Requirement The "Program blocks" folder is opened in the project tree. Procedure To change the name of a block, follow these steps: 1. Right-click the block that you want to rename. 2. Select the "Rename" command in the shortcut menu. The block name in the project tree changes to an input field. 3. Input the new name for the block. 4. Confirm your entry with the Enter key. Result The name of the block is now changed at all points of use in the program. See also Opening blocks (Page 1349) Saving blocks (Page 1350) Closing blocks (Page 1350) Deleting blocks offline (Page 1352) Deleting blocks online (Page 1352) WinCC Basic V13.0 System Manual, 02/2014 1351 Programming the PLC 9.1 Creating the user program Deleting blocks offline Requirement The "Program blocks" folder opens in the project tree. Procedure To delete a block that exists offline, proceed as follows: 1. In the project tree in the "Program blocks" folder, right-click on the block that you want to delete. 2. Select the "Delete" command in the shortcut menu. 3. Confirm the safety prompt with "Yes". The block is deleted offline from the project. Note If you are deleting organization blocks, note that events may be assigned to these blocks. If you delete such organization block the program cannot respond to parameterized events. See also Opening blocks (Page 1349) Saving blocks (Page 1350) Closing blocks (Page 1350) Renaming blocks (Page 1351) Deleting blocks online (Page 1352) Deleting blocks online Requirement The "Program blocks" folder in the project tree is open. Procedure To delete a block that exists online, follow these steps: 1. In the "Program blocks" folder in the project tree, right-click on the block that you wish to delete from the device. 2. Select the "Delete" command from the shortcut menu. The "Delete" dialog opens. 1352 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program 3. Select the "Delete from device" check box. 4. Click "Yes". The block will be deleted from the device online. See also Opening blocks (Page 1349) Saving blocks (Page 1350) Closing blocks (Page 1350) Renaming blocks (Page 1351) Deleting blocks offline (Page 1352) Deleting CPU data blocks You may delete CPU data blocks both in offline and online mode. Deleting CPU data blocks in offline mode Proceed as follows to delete a CPU data block from the offline project: 1. Right-click the CPU data blocks that you want to delete in the project navigation, "Program blocks" folder. 2. Select the "Delete" command from the shortcut menu. 3. Confirm the safety prompt with "Yes". The CPU data block is deleted from the offline project. Deleting CPU data blocks in online mode Proceed as follows to delete a CPU data block from the online project: 1. Establish an online connection to the device containing the CPU data block that you want to delete. 2. Right-click the CPU data block that you want to delete from the device in the project navigation, "Program blocks" folder. 3. Select the "Delete" command from the shortcut menu. The "Delete" dialog opens. 4. Select the "Delete from device" check box. 5. Click "Yes". The CPU data block is deleted from the online device. See also CPU data blocks (Page 1150) WinCC Basic V13.0 System Manual, 02/2014 1353 Programming the PLC 9.1 Creating the user program 9.1.4 Programming blocks 9.1.4.1 Program editor Overview of the program editor Function of the program editor The program editor is the integrated development environment for programming functions, function blocks, and organization blocks. If offers comprehensive support for programming and troubleshooting. The appearance and functionality of the program editor can vary depending on the CPU, programming language and block type used. 1354 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program Structure of the program editor Using LAD as an example, the following figure shows the components of the program editor: Toolbar Block interface "Favorites" pane in the "Instructions" task card and favorites in the program editor Programming window "Instructions" task card "Testing" task card WinCC Basic V13.0 System Manual, 02/2014 1355 Programming the PLC 9.1 Creating the user program Toolbar The toolbar allows you to access the principal functions of the program editor, such as: Show and hide absolute operands Showing and hiding favorites Skip to syntax errors Update block calls Show and hide program status The functions available in the toolbar can vary depending on the programming language used. Block interface The block interface contains the declarations for local tags used solely within the block. The sections available depend on the block type. Favorites You can save frequently used instructions as favorites. These favorites are then displayed in the "Instructions" task card and the "Favorites" pane. You can also display favorites in the program editor using the program editor toolbar. This allows you to access your favorites even when the "Instructions" task card is not visible. Programming window The programming window is the work area of the program editor. You can enter the program code in this window. The appearance and functionality of the program window can vary depending on the programming language used. "Instructions" task card The "Instructions" task card offers you easy access to all instructions available for creating your program. The instructions are broken down by area into a number of different palettes. You can show additional information on the instructions via the "Show column headers and additional columns" button in the task card toolbar. You can modify the arrangement of columns by clicking a column header and moving the column to the new position by means of drag-anddrop. If an instruction profile is active, the offered instructions may vary. See also: Using instruction profiles "Testing" task card You can set settings in the "Testing" task card for troubleshooting using the program status. The functions of the "Testing" task card are only available in online mode. It contains the 1356 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program following panes, which are displayed depending on the selected CPU and the configured programming language of the block: CPU operator panel The CPU operator panel allows you to switch the CPU operating mode. Breakpoints You can test blocks you created in the textual programming languages STL and SCL in single step mode. To do this, set breakpoints in the program code. In the "Breakpoints" pane, you can find all breakpoints that you have set and you can activate, delete, navigate to, or set the call environment for the individual breakpoints. PLC register This pane allows you to read off the values for the PLC registers and the accumulators. Sequence control In this pane you can set the operating mode for testing sequencers for GRAPH blocks. Test settings This pane allows you to specify the test settings for the GRAPH block. Call environment This pane allows you to specify the call environment for the block. Call hierarchy In this pane, you can trace the call hierarchy of the blocks. You only see the call hierarchy during block monitoring. See also Layout of the block interface (Page 1375) Enlarging the programming window (Page 1362) Using the keyboard in the program editor Navigating in the editor Function Shortcut key Open "Instructions" task card <Ctrl+Shift+C> Open "Testing" task card <Ctrl+Shift+O> Add new block <Ctrl+N> Expand all networks <Alt+F11> Collapse all networks <Alt+F12> Navigate to the next point of use of the selected block or operand <Ctrl+Shift+F> WinCC Basic V13.0 System Manual, 02/2014 Navigate to the previous point of use of the selected block or operand <Ctrl+Shift+G> Navigate to the next read/write access <Alt+F8> Navigate to the previous read/write access <Alt+F9> 1357 Programming the PLC 9.1 Creating the user program Navigating in the program code (LAD/FBD) Function Selected object Shortcut key Navigating between objects in the network Object in the network Arrow keys Navigate to the first element of the network Object in the network <Home> Navigate to the last element of the network Object in the network <End> Navigate to the next element of the network Object in the network <Tab> Navigate to the previous element of the network Object in the network <Shift+Tab> Insert network Any <Ctrl+R> Function Position of the cursor Shortcut key Navigating in the program code Line Arrow keys One word to the right/left Line <Ctrl+arrow keys> Cursor to start of line Line <Home> Cursor to end of line Line <End> Cursor to start of code section Line <Ctrl+Home> Cursor to end of code section Line <Ctrl+End> To the next network (STL only) Network title <Down arrow> To the next network (STL only) Line <Tab> Navigating in the program code (STL/SCL) Repeat the shortcut keys until the insertion point is in the next network. To the previous network (STL only) Network title <Up arrow> To the previous network (STL only) Line <Shift+Tab> Repeat the shortcut keys until the insertion point is in the previous network. Insert network Any <Ctrl+R> Function Selected object Shortcut key Insert normally open contact Rung <Shift+F2> Insert normally closed contact Rung <Shift+F3> Insert empty box Rung <Shift+F5> Insert assignment Rung <Shift+F7> "Insert "Open branch" Rung <Shift+F8> "Insert "Close branch" Rung <Shift+F9> Inserting instructions (LAD) 1358 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program Inserting instructions (FBD) Function Selected object Shortcut key Insert assignment Network, input or output <Shift+F7> Insert empty box Network <Shift+F5> "Insert "Open branch" Connection line between two boxes <Shift+F8> Invert RLO Network, input or output <Ctrl+Shift+4> Insert input Network, input or output <Ctrl+Shift+3> Entering operands (LAD/FBD/GRAPH) Function Selected object Shortcut key Activate the input field for the first operand of the instruction Instruction <Return> Or <Any letters/numbers> An empty input field opens on <Return>, any letters or numbers will be entered in the input field. WinCC Basic V13.0 System Manual, 02/2014 Activate input field for the operand Operand <F2> Delete operand Operand <Del> Define tag Operand <Ctrl+Shift+I> Rewire tag Operand <Ctrl+Shift+P> Rename tag Operand <Ctrl+Shift+T> Entering operands Input field for operands <Any letters/numbers> Confirm entry of the operand Input field for operands <Return> Open autocompletion Input field for operands <Ctrl+I> Discard current change Input field for operands <Esc> The input field is deactivated and the previous contents restored. 1359 Programming the PLC 9.1 Creating the user program Process instructions (STL/SCL) Function Selected object Shortcut key Indent line (SCL only) Line <Tab> or <Ctrl+R> Outdent line (SCL only) Line <Shift+Tab> or <Ctrl+Shift+R> Automatically formatting selected text (SCL only) <Ctrl+Shift+W> Open "Call options" dialog Cursor after block call <Return> Define tag Operand <Ctrl+Shift+I> Rewire tag Operand <CtrlShift+P> Rename tag Operand <Ctrl+Shift+T> Expand/collapse parameter list (SCL only) Operand <Ctrl+Shift+Space> Expand/collapse code section Insertion mark within the code section <Ctrl+Shift+Num+> Any <Ctrl+Shift+Num*> Expand/collapse all code sections <Ctrl+Shift+Num-> <Ctrl+Shift+Num/> Open autocompletion Any <Ctrl+I> or <Ctrl+Spacebar> Set/delete bookmarks <Ctrl+Shift+M> To the next bookmark <Ctrl+Shift+6> To the previous bookmark <Ctrl+Shift+5> Comment out selection Line <Ctrl+Shift+Y> Remove comment Line <Ctrl+Shift+U> Function Area Shortcut key Page Up/Down Navigation view, single step view, sequence view, permanent instructions <Page Up>/ Navigate in the navigation view Navigation view <Up arrow> Expand/collapse object Navigation view Switch between single step view and sequence view when a step or a transition is selected Navigation view <Return> Switch between navigation view and work area Navigation view, single step view, sequence view, permanent instructions <ALT+F6> Programming window of GRAPH <Page Down> <Down arrow> <+> or <Right arrow> <-> or <Left arrow> 1360 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program Function Area Shortcut key Go to first element in a network Single step view <Home> Go to last element in a network Single step view <End> Switch to interlock Single step view <Ctrl+Home> Switch to transition Single step view <Ctrl+End> Navigate in the structure Sequence view Arrow keys Go to first step Sequence view <Home> or <Ctrl+Home> Go to last step Sequence view <End> or <Ctrl+End> Open branch Sequence view <Shift+F8> Close branch Sequence view <Shift+F9> Insert sequence end Sequence view <Shift+F7> Insert jump Sequence view <Shift+F12> Insert step and transition Sequence view <Shift+F5> Delete element Sequence view <Del> Go to first editable element Permanent instructions <Home> Go to next editable element Permanent instructions <Tab> Go to last editable element Permanent instructions <End> Go to previous editable element Permanent instructions <Shift+Tab> Jump to the start of the "Action" cell Actions <Home> Jump to the end of the "Action" cell Actions <End> Insert new action Actions <Return> Monitor program WinCC Basic V13.0 System Manual, 02/2014 Function Shortcut key Set/remove breakpoint (STL, SCL) <Ctrl+Shift+F9> Step over breakpoint (STL, SCL) <Ctrl+Shift+F10> Jump to lower-level block (STL, SCL) <Ctrl+Shift+F11> Return to calling block (STL, SCL) <Ctrl+Shift+F12> Run program up to marker (cursor position) (STL, SCL) <Ctrl+F3> Display program status (SCL, STL) <Ctrl+T> Enable all breakpoints (STL, SCL) <Ctrl+Shift+F2> Disable all breakpoints (STL, SCL) <Ctrl+Shift+F3> Modify to 0 (LAD, FBD) <Ctrl+Shift+9> Modify to 1 (LAD, FBD) <Ctrl+Shift+1> Modify operand (LAD, FBD) <Ctrl+Shift+2> 1361 Programming the PLC 9.1 Creating the user program See also Keyboard operation in the TIA Portal (Page 218) Using project-related functions (Page 220) Arranging windows (Page 220) Editing tables (Page 226) Text editing (Page 225) Enlarging the programming window Introduction The programming window is relatively small when all components of the application are shown. If the program code is large, you may find you have to rearrange the work area constantly. To avoid this problem, you can hide or minimize the display of the following components of the application and of the program editor: Project tree Task cards Block interface Favorites Comments Networks Note You can also use the "Reduce automatically" option for the task cards, project tree, and Inspector window. These windows will then be minimized automatically when you do not need them. See also: Maximizing and minimizing the work area Hiding and showing the project tree The project tree allows you to access all areas of the project. You can hide the project tree while you are creating a program so you have more space for the programming window. To show and hide the project tree, follow these steps: 1. To hide the project tree, deselect the "Project tree" check box in the "View" menu, or click on "Collapse" on the project tree title bar. 2. To show the project tree, select the "Project tree" check box in the "View" menu or click on "Extend" on the project tree title bar. 1362 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program Opening and closing task cards The task cards are located at the right-hand edge of the programming window. To open or close the task cards, follow these steps: 1. To close the task cards, deselect the "Task card" check box in the "View" menu or click "Collapse" on the task cards title bar. 2. To open the task cards, select the "Task card" check box in the "View" menu or click "Expand" on the task cards title bar. Hiding and showing the block interface The block interface is shown in the upper section of the program editor. During programming you can show and hide it as required. To show and hide the block interface, follow these steps: 1. In the lower part of the interface within the window splitter, click on the Up arrow or Down arrow. Showing and hiding favorites To hide or show the favorites in the program editor, follow these steps: 1. Click the "Display favorites in the editor" button in the program editor toolbar. Showing and hiding comments Within a block you can enter a comment for the block or for each network. These two types of comments are shown and hidden differently. To show or hide a block comment, follow these steps: 1. Click the the triangle at the start of the line with the block title. To show or hide network comments, follow these steps: 1. Click "Network comments on/off" on the program editor toolbar. Note The comments available can vary depending on the programming language used. Opening and closing networks Some programming languages use networks. You can open or close these networks as required. To open or close networks, follow these steps: 1. If you want to open a network, click the right arrow in front of the network title. If you want to close a network, click the down arrow in front of the network title. To open and close all networks, follow these steps: WinCC Basic V13.0 System Manual, 02/2014 1363 Programming the PLC 9.1 Creating the user program 1. Click "Open all networks" or "Close all networks" in the program editor toolbar. Note Networks are not used in every programming language. See also Overview of the program editor (Page 1354) Maximizing and minimizing the work area (Page 197) Setting the mnemonics You can program blocks using German or international mnemonics. If you open the TIA portal for the first the international mnemonics is set as default. You can change the mnemonics at any time. Procedure To set the mnemonics, 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. In the "General settings" group, select the mnemonics that you want to use. The mnemonics is changed in all blocks. Displaying symbolic and absolute addresses You have the following options for displaying operands in the program editor: Symbolic representation The symbolic operands are displayed in the program. The corresponding absolute addresses are shown in tooltips if you hold the mouse pointer over the operand. Absolute representation The absolute addresses are displayed in the program. The corresponding symbolic operands are displayed in tooltips. Symbolic and absolute representation Symbolic operands and absolute addresses are displayed in program. Requirement The program editor is open. 1364 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program Procedure To change the representation of the operands, follow these steps: 1. Click the "Absolute/symbolic operands" button in the program editor toolbar. Each time you click the button, the representation and the symbol on the button change. Or: 1. Click the small arrow next to the "Absolute/symbolic operands" button in the program editor toolbar. A drop-down list is displayed. 2. Select the required representation from the drop-down list. The symbol on the button changes. See also Basic information about operands (Page 1173) Use instruction versions Basic information on instruction versions The instructions available to you for programming the user program are managed in system libraries. If a new version of a system library is installed by an update, the newer versions of the instructions of this system library may also be installed. If there are several versions for an instruction, these are listed in the "Instructions" task card after the respective instruction. If the instruction versions are not shown, you can show them via the "Show column headers and additional columns" button in the toolbar of the "Instructions" task card. You can then select the versions of the instructions to be used in the program from the dropdown-list box of the "Version" column. If you do not select any versions, the most recent versions are used. Note Note the following information: You can only ever use the same version of an instruction within a device. If you change the version of an instruction that other instructions depend on, the versions of the dependent instructions are also changed. If you select a version for an instruction that can not be run on the CPU used, the instruction is shaded out. This means that you cannot use this instruction in this version with your CPU. When you change the version of an instruction, you must compile the block before the new version number is displayed in the properties of the instruction. If an instruction is a block within the system, the block also receives its own block version number. This version number can be different from the instruction version and can vary on different CPU types. WinCC Basic V13.0 System Manual, 02/2014 1365 Programming the PLC 9.1 Creating the user program Changes in the versions New versions can be main versions or secondary versions. New versions, such as 2.0 or 3.0, have more substantial changes to them. New main versions may therefore result in changes to the block interface. New secondary versions, such as 1.3 or 1.4, contain lesser changes or remedies to errors. Using instruction versions You can decide within a device which version of an instruction you want to use. If you select another version for an instruction, the new version is specified for all locations of use of this instruction within your program. These instructions are identified in the program by a red frame. You must then download your program to the device to use the new instruction version. Using instruction profiles Basics of instruction profiles Introduction The TIA Portal provides you with numerous instructions that you can use to program the user program. However, you may filter out specific instructions that you do not want to use. To this end you can create instruction profiles in which you can explicitly specify the instructions to be listed in the "Instructions" task card. However, although you may create several instruction profiles in a project, only one of these profiles may be active at any given time. You can exchange instruction profiles with other users by means of shared libraries. Note Please note the following: The use of instructions that are not allowed in the active profile in a block will trigger the output of a block compilation error. Such a situation may be triggered if you drag-and-drop a block from the library to your program. Instructions of a profile that are not supported by the currently installed products are deleted from the profile the next time it is edited. If you transfer this profile to an engineering system in which these instructions are supported by the installed products, the instructions are again present in the profile but they are disabled. You can enable these instructions as required at any time. If you want to make changes to the active profile, you must recompile the blocks in the project. This is also necessary when you disable or delete the active profile or when you enable a profile. See also Creating new instruction profiles (Page 1367) Opening and editing instruction profiles (Page 1368) 1366 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program Activating and deactivating instruction profiles (Page 1369) Deleting instruction profiles (Page 1370) Creating new instruction profiles Requirement The "Common data > Instruction profiles" folder is open in the project navigation. Procedure Proceed as follows to create a new instruction profile: 1. Double-click the "Add new profile" command. The Instruction Profile Editor opens and displays the new instruction profile. All instructions are activated for the new instruction profile. 2. Edit the new instruction profile to suit your requirements. If necessary, you can rename the new instruction profile. To do this, follow these steps: 1. Right-click on the new instruction profile. 2. Select the "Rename" command in the shortcut menu. 3. Enter a name for the new instruction profile. Note The first instruction profile that you create will be used as active profile. In this case, compile all blocks in the project. If other instruction profiles are already available you must explicitly activate the new one in order to use it as active profile. You can identify the active profile by its icon in the project navigation. See also Basics of instruction profiles (Page 1366) Opening and editing instruction profiles (Page 1368) Activating and deactivating instruction profiles (Page 1369) Deleting instruction profiles (Page 1370) WinCC Basic V13.0 System Manual, 02/2014 1367 Programming the PLC 9.1 Creating the user program Opening and editing instruction profiles Once you have opened an instruction profile, you can edit it as follows: Activating and deactivating instructions You can explicitly specify the instructions to be allowed in the instruction profile. Note Note that dependencies exist between some instructions. As a result, it is possible that several instructions may be activated or deactivated by an action. The check box icon indicates the folders in which instructions are deactivated. Activating and deactivating instruction versions Certain instructions are available with different versions. You can explicitly specify the instruction versions to be allowed in the instruction profile. Renumbering blocks An instruction representing an internal function block (FB) or function (FC) in the system is assigned a specific block number by the system. You can replace this block number with your own block number. Within a version, there are several implementations for certain instructions. The block numbers in such instructions can only be changed for the specific implementation. Note If an instruction from the instruction profile is used in the program and the specified block number is already in use by a different block, the specified block number of the instruction will be replaced by a free block number. Requirement The "Common data > Instruction profiles" folder is open in the project navigation. Opening instruction profiles Proceed as follows to open an instruction profile: 1. Double-click the instruction profile that you want to edit. The instruction profile opens in the Instruction Profile Editor. Editing instruction profiles Proceed as follows to edit an instruction profile in the Instruction Profile Editor: 1. Select the device that you want to edit from the "Device family" drop-down list box. 2. Select the programming language for which you want to edit the instruction profile from the "Language" drop-down list box. 3. Deactivate the instructions or instruction versions that you want to exclude from the instruction profile. You can deactivate a folder to deactivate all subordinate instructions. 1368 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program 4. Activate the instructions or instruction versions that you want to allow in the instruction profile. 5. You may assign your own block numbers. Note You can assign the number up to 65535 for CPUs of the S7-1200/1500 series. For CPUs of the S7300/400 series you find the restrictions of the number ranges in the respective CPU manual. Note A new compilation process is required for all blocks in the project when you change the active profile. See also Basics of instruction profiles (Page 1366) Creating new instruction profiles (Page 1367) Activating and deactivating instruction profiles (Page 1369) Deleting instruction profiles (Page 1370) Use instruction versions (Page 1365) Activating and deactivating instruction profiles You first need to activate an instruction profile in order to include filtering of its instructions. You can always deactivate the instruction profile to reset the instructions task card to the default scope of instructions. Note A new compilation process is required for all blocks in the project. Requirement The "Common data > Instruction profiles" folder is open in the project navigation. Activating instruction profiles Proceed as follows to activate an instruction profile: 1. Right-click on the instruction profile that you want to activate. 2. Select the "Activate profile" command from the shortcut menu. The selected instruction profile is now active. Instructions can now only be used in accordance with the settings of this profile. WinCC Basic V13.0 System Manual, 02/2014 1369 Programming the PLC 9.1 Creating the user program Deactivating instruction profiles Proceed as follows to deactivate the instruction profile: 1. Right-click on the instruction profile that you want to deactivate. 2. Select the "Deactivate profile" command from the shortcut menu. No instruction profile is active and the "Instructions" task card once again shows all instructions that are available for use. See also Basics of instruction profiles (Page 1366) Creating new instruction profiles (Page 1367) Opening and editing instruction profiles (Page 1368) Deleting instruction profiles (Page 1370) Deleting instruction profiles Requirement The "Common data > Instruction profiles" folder is open in the project tree. Procedure Proceed as follows to delete an instruction profile: 1. Right-click on the instruction profile that you want to delete. 2. Select the "Delete" command in the shortcut menu. Note A new compilation process is required for all blocks in the project when you delete the active profile. Result The selected instruction profile is deleted. If you deleted the active instruction profile, no more active profiles are available and the "Instructions" task card once again shows all instructions that are available for use. See also Basics of instruction profiles (Page 1366) Creating new instruction profiles (Page 1367) 1370 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program Opening and editing instruction profiles (Page 1368) Activating and deactivating instruction profiles (Page 1369) Using autocompletion Basics of autocompletion Function You can use autocompletion in the program window of the program editor as an easy way to access available tags or instructions during programming. Autocompletion means a contextspecific list appears in a dialog from which you can select the tags or instructions you need. See also Using autocompletion in graphic programming languages (Page 1371) Using autocompletion in textual programming languages (Page 1372) Using autocompletion in graphic programming languages Inserting tags using autocompletion To insert tags in graphic programming languages using autocompletion, follow these steps: 1. Select an operand of the instruction to which you wish to assign a tag. The input field for the operand opens. The autocompletion button will appear beside the input field. 2. Either click the autocompletion button or use the shortcut <Ctrl+l>. Autocompletion opens. It contains only the local and global tags, data blocks and multiple instances which are admissible for the operand in the given context. You can exit autocompletion at any time by pressing <Esc>. WinCC Basic V13.0 System Manual, 02/2014 1371 Programming the PLC 9.1 Creating the user program 3. Select the required tag from the list. If necessary, you can also filter the list: - For example, enter the first few letters of the name of the tag or instruction you wish to insert. Autocompletion will be filtered further with each letter entered. If there is no tag or instruction starting with the letters entered, autocompletion will remain at the last match. - Enter # to access the local tags from the block interface. - Enter " to access the global tags. - Enter % to access absolute addresses. If the tag is a structured tag, a data block or a multiple instance, then an arrow is displayed at the end of the row. Click on the arrow to display the lower-level elements. You can navigate to the very last level in this way. If a structure is allowed as a data type for the operand, you can choose "None" from the list. This assigns the entire structure to the operand as a tag. Use the <Backspace> key to return to the previous level. 4. Press the <Return> key to apply the tag. See also Basics of autocompletion (Page 1371) Using autocompletion in textual programming languages (Page 1372) Using autocompletion in textual programming languages Inserting tags and instructions using autocompletion To insert tags and instructions in textual programming languages using autocompletion, follow these steps: 1. Enter the first few letters of the name of the tag or instruction you wish to insert. If necessary, you can directly filter the kind of tags: - Enter # to access the local tags from the block interface. - Enter " to access the global tags. - Enter % to access absolute addresses. Autocompletion opens. It contains only the local and global tags, data blocks, multiple instances and instructions which are admissible at the current position. You can exit autocompletion at any time by pressing <Esc>. 2. Enter more letters of the name of the tag or instruction you wish to insert. You can use <Enter> or <Tab> to apply the tag or instruction and close autocompletion. Autocompletion will be filtered further with each letter entered. If there is no tag or instruction starting with the letters entered, autocompletion only contains the previous matches. 1372 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program 3. Select the tag or instruction required from the list. If a tag is a structured tag, a data block or a multiple instance, first select the tag, the data block or multiple instance from the autocompletion and apply the selection with <Enter>. To select the additional components of the structure, data block, or multiple instance, enter a period. Autocompletion then reopens and you can select the next component. 4. Press the <Return> key to apply the tag. See also Basics of autocompletion (Page 1371) Using autocompletion in graphic programming languages (Page 1371) General settings for the PLC programming Overview of the general settings Overview The following table shows the general settings that you can make: Group Setting Description View With comments Network comments are shown. Tag information Additional information for the tags used is displayed in the program editor. When you select the option "Tag information with hierarchy", the comments of the higher structure levels are also displayed for structured tags. Compilation Delete actual parameters on interface update Actual parameters are deleted if the associated formal parameters were deleted in the called block, and you run the "Update block call" function or compile the block. Default settings for new blocks IEC check The compatibility of operands in comparison operations and arithmetic operations are tested according to IEC rules. You have to explicitly convert noncompatible operands. Additional settings Set network title automatically Sets the title of a network based on the comment of the output parameter of the first writing instruction in the network. See also: Inserting network title (Page 1405) WinCC Basic V13.0 System Manual, 02/2014 Show autocompletion list The autocompletion list is displayed. Mnemonics German or international designation of operations and operands 1373 Programming the PLC 9.1 Creating the user program Group Setting Description Download without reinitialization Memory reserve Defines the size of reserve in volatile memory that can be used for interface extensions. Block interface / data blocks Set "HMI accessible" for new elements and ARRAY data blocks Enables the option "HMI accessible" for new tags in the block interface and in data blocks. The use of this option makes sense especially when working with large amounts of data in ARRAY data blocks. See also: Basic principles for programming of data blocks (Page 1523) See also Layout of the block interface (Page 1375) Changing the settings (Page 1374) Permissible addresses and data types of PLC tags (Page 1308) Overview of the print settings (Page 186) Basics of block access (Page 1151) Setting and canceling the IEC check (Page 1256) Changing the settings Procedure To change the settings, follow these steps: 1. Select the "Settings" command in the "Options" menu. The "Settings" window is displayed in the work area. 2. In the area navigation, select the "PLC programming" group. 3. Change the settings. Result The change will be loaded directly, there is no need to save it explicitly. See also Overview of the general settings (Page 1373) 1374 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program 9.1.4.2 Programming code blocks Declaring the block interface Layout of the block interface Introduction The interface contains the declarations of local tags and constants that are used within the block. The tags are subdivided into two groups: Block parameters that form the block interface when it is called in the program. Local data that are used for storage of intermediate results. You use the tag declaration to define the call interface of a block in the program and the names and data types of tags and constants that you want to use in the block. The interface of function blocks also defines the structure of the instances that are assigned to the function block. Layout of the block interface The following figure shows the structure of the block interface. The number of columns and sections varies depending on the type of block. Block parameters The following table shows the types of block parameters: Type Section Function Available in Input parameters Input Parameters whose values are read by the block. Functions, function blocks and some types of organization blocks Output parameters Output Parameters whose values are written by the block. Functions and function blocks WinCC Basic V13.0 System Manual, 02/2014 1375 Programming the PLC 9.1 Creating the user program Type Section Function Available in In/out parameters InOut Parameters whose values are read by the block when it is called, and whose values are written again by the block after execution. Functions and function blocks Return value Return Value that is returned to the calling block. Functions Depending on the type of block opened, additional sections may be displayed. Local data The following table shows the types of local data: Type Section Function Available in Temporary local data Temp Tags that are used to store temporary intermediate results. Temporary local data are retained for only one cycle. If you use temporary local data, you have to make sure that the values are written within the cycle in which you want to read them. Otherwise the values will be random. Functions, function blocks and organization blocks Note: Temporary local data is not shown in instance data blocks. Static local data Static Tags that are used for storage of static intermediate results in the instance data block. Static data is retained until overwritten, which may be after several cycles. The names of the blocks, which are called in this code block as multiple instance, will also be stored in the static local data. Function blocks Constant Constant Constants with declared symbolic names that are used within the block. Functions, function blocks and organization blocks Note: Local constants are not shown in instance data blocks. Meaning of the columns The following table shows the meaning of the individual columns. You can show or hide the columns as required. The number of columns displayed varies depending on the CPU series and the type of the open object. Column Description Symbol you can click on to drag-and-drop an element to a program for use as an operand. 1376 Name Name of the element. Data type Data type of the element. Offset Relative address of a tag. The column is only visible in blocks with standard access. WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program Column Description Default value Value with which you can pre-assign specific tags in the interface of the code block, or the value of a local constant. Specification of the default value is optional for tags. If you do not specify any value the predefined value for the indicated data type is used. For example, the value "false" is predefined for BOOL. The default value of a tag is applied as the start value in the corresponding instance data block. You can replace these values with instance-specific start values in the instance data block. Constants always have the default value declared in the block interface. They are not shown in instance data blocks and cannot be assigned instance-specific values there. Retentivity Marks a tag as retentive. The values of retentive tags are retained even after the power supply is switched off. This column is only visible in the interface of the function block with optimized access. Visible in HMI Shows whether a tag is visible by default in the HMI selection list. Accessible from HMI Shows whether HMI can access this tag during runtime. Setting value Marks a tag as a setpoint. Setting values are the values that will probably have to be fine tuned during commissioning. The column is only available in the interface of function blocks. Comment Comments on documentation of the element. See also Using tags within the program (Page 1179) Keywords (Page 1173) Valid data types in the block interface (Page 1379) Setting the retentivity of local tags (Page 1391) Basics of constants (Page 1180) Rules for declaring the block interface General rules for declaring the block interface Using POINTER The following rules apply to the use of block parameters within the block: Input parameters may only be read. Output parameters may only be written. In/out parameters may be read and written. WinCC Basic V13.0 System Manual, 02/2014 1377 Programming the PLC 9.1 Creating the user program Assigning default values to block parameters You can assign default values to specific parameters in the function block interface. The possibility of the assignment depends on the declaration subsection and data type of the parameter. The following table shows which parameters can be assigned a default value: Parameter type Section Assignment of a default value is possible Elementary data types Structured data types Parameter types Input parameters Input X X - Output parameters Output X X - In/out parameters InOut X - Static local data Static X X - Temporary local data Temp - - - Constants Constant X - - (1) Exception: In blocks with optimized access, you have the option to use PLC data types as default values under certain conditions. (1) See also: Declaring PLC data types (UDT) as actual parameters for in-out parameters. (Page 1394) See also Using tags within the program (Page 1179) Keywords (Page 1173) Valid data types in the block interface Valid data types in the block interface in S7-300/400 The following table shows which data types you can assign to the parameters in the individual sections of the interface. Section Standard ARRAY Data types STRUCT Parameter types VOID POINTER ANY STRING DT Organization block Temp X X - - - X Constant X X - - - - Input X X X - X X Output X X - - - - (3) Function block 1378 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program Section Standard ARRAY Data types STRUCT Parameter types VOID POINTER ANY STRING DT InOut X X (1) - - X X Static X X - - - - Temp X X - - - X Constant X X - - - - Input X X (1) X - X X Output X X (1) - - X X InOut X X (1) - - X X Temp X X - - - X Return X X - X X X (2) Constant X X(3) - - - - (3) Function (1) STRING can only be defined in the standard length of 254 characters. (2) In SCL, ANY is not permitted as a function value. (3) Constants with the ARRAY or STRUCT data type are not permitted. Valid data types in the block interface Valid data types in the block interface in S7-1200 The following table shows which data types you can assign in the parameters in the individual sections of the interface. Section Standard ARRAY Data types STRUCT VOID VARIANT STRING DT Organization block Temp X X - X Constant X X(2) - - Input X X - X Output X X - - Function block InOut X X - X Static X X - - Temp X X - X Constant X X - - Input X X(1) - X Output X X(1) - X (1) (2) Function WinCC Basic V13.0 System Manual, 02/2014 1379 Programming the PLC 9.1 Creating the user program Section Standard ARRAY Data types STRUCT VOID VARIANT STRING DT InOut X X(1) - X Temp X X - X Return X X X - Constant X X - - (2) (1) STRING can only be defined in the standard length of 254 characters. (2) Constants with the ARRAY or STRUCT data type are not permitted. Valid data types in the block interface in S7-1500 The following table shows which data types you can assign in the parameters in the individual sections of the interface. Section Standard ARRAY Data types STRUCT Paramete r types VOID DB_ANY POINTER ANY VARIANT -(4) - X - X(3) X STRING / WSTRING DT Organization block Temp X X Constant X X - - - - - - Input X X X - X X X X Output X X - - X - - - InOut X X - - X X X X Static X X - - X - - - Temp X X -(4) - - - X(3) X Constant X X - - - - - - Input X X(1) X - X X X X Output X X(1) - - X X X X InOut X X - - X X X X (5) Function block (1) (5) (4) Function (1) (4) Temp X X - - X - X X Return X X - X X X x(2) - Constant X X - - - - - - (4) (5) (3) You cannot make length declarations for STRING and WSTRING in these sections. Here, STRINGs always have the standard length 254, WSTRINGs the standard length 16832. A declaration in the format MyString[3] would not be permitted. WSTRING is only permitted in blocks with optimized access in these sections. (1) (2) In SCL, ANY is not permitted as a function value. (3) ANY can only be used in blocks with standard access in the "Temp" section. (4) The "INSTANCE" parameter type is the only exception permissible in the "TEMP" and "InOut" sections. (5) Constants with the ARRAY or STRUCT data type are not permitted. 1380 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program Declaring local tags and constants Declaring local tags and constants in the block interface Requirement The block interface is open. Procedure To declare a tag or constant of the elementary data type, follow these steps: 1. Select the appropriate declaration section in the interface. 2. Enter a name for the element in the "Name" column. 3. Enter the required data type in the "Data type" column. You will be supported by autocompletion during input. 4. For constants, enter a value in the "Default value" column. 5. Optional: Change the properties that are displayed in the other columns of the block interface. Result The element is created. Syntax check A syntax check is performed after each entry, and any errors found are displayed in red. You do not have to correct these errors immediately - you can continue editing and make any corrections later. However, you will not be able to compile the program if the tag declaration contains syntax errors. Note If you change the interface of a block, the calls of the block in the program will possibly become inconsistent. The call locations are automatically updated, if possible. If an automatic updating is not possible, the inconsistent blocks have to be updated manually. See also: Updating block calls in LAD (Page 1418) Updating block calls in FBD (Page 1460) See also Editing tables (Page 226) Basic information on start values (Page 1533) WinCC Basic V13.0 System Manual, 02/2014 1381 Programming the PLC 9.1 Creating the user program Using tags within the program (Page 1179) Keywords (Page 1173) Properties of local tags and constants (Page 1390) Setting the retentivity of local tags (Page 1391) Declaring a local tag in the program editor Requirement The program editor is open. Procedure To declare a local tag, follow these steps: 1. Insert an instruction in your program. The "<???>", "<??.?>" or "..." strings represent operand placeholders. 2. Replace an operand placeholder with the name of the tag to be created. 3. Select the name of the element. If you want to declare multiple elements, select the names of all the elements to be declared. 4. Select the "Define tag" command in the shortcut menu. The "Define tag" dialog box opens. It displays a declaration table in which the name of the element is already entered. 5. To declare a local tag, select one of the following sections: - Local In - Local Out - Local InOut - Local Static - Local Temp 6. In the other columns, enter data type and comments. 7. Click the "Define" button to complete your entry. 1382 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program Result The declaration is written directly into the block interface and is valid within the entire block. Note If you change the interface of a block, the calls of the block in the program will possibly become inconsistent. The call locations are automatically updated, if possible. If an automatic updating is not possible, the inconsistent blocks have to be updated manually. See also: Updating block calls in LAD (Page 1418) Updating block calls in FBD (Page 1460) See also Editing tables (Page 226) Using tags within the program (Page 1179) Keywords (Page 1173) Basic information on start values (Page 1533) Properties of local tags and constants (Page 1390) Setting the retentivity of local tags (Page 1391) Declaring tags of the ARRAY data type Requirement The block interface is open. Procedure To declare a tag of the ARRAY data type, follow these steps: 1. Select the appropriate declaration section in the interface. 2. Enter a tag name in the "Name" column. 3. In the "Data type" column, click the button for the data type selection. A list of the permissible data types is opened. 4. Select the "Array" data type. The "Array" dialog opens. 5. In the "Data type" text box, specify the data type of the array elements. WinCC Basic V13.0 System Manual, 02/2014 1383 Programming the PLC 9.1 Creating the user program 6. In the "ARRAY limits" text box, specify the high and low limit for each dimension. Example of a one-dimensional ARRAY: [0..3] Example of a three-dimensional ARRAY: [0..3, 0..15, 0..33] 7. Confirm your entry. 8. Optional: Change the properties of the tags that are displayed in the other columns of the block interface. Result The tag of ARRAY data type is created. Note You cannot define specific default values for ARRAY elements. However, you can assign them start values in the instance. See also Using tags within the program (Page 1179) Keywords (Page 1173) Properties of local tags and constants (Page 1390) Setting the retentivity of local tags (Page 1391) Editing tables (Page 226) Declaring tags of STRUCT data type Requirement The block interface is open. Procedure To declare a tag of the STRUCT data type, follow these steps: 1. Select the appropriate declaration section in the interface: 2. Enter a tag name in the "Name" column. 3. Enter "Struct" in the "Data type" column. You will be supported by autocompletion during input. An empty, indented row is inserted after the new tag. 4. Insert the first structural element in the first empty row. An additional empty row is inserted after the element. 5. Select a data type for the structure element. 1384 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program 6. Optional: Change the properties of the structural element that is displayed in the other columns of the block interface. 7. Repeat the step 4 to 7 for all additional structure elements. It is not necessary to end the structure explicitly. The structure ends with the last element that is entered. 8. To insert a new tag after the structure, leave a blank row after the end of the structure and then start the new tag in the second empty row. Result The tag of STRUCT data type is created. See also Using tags within the program (Page 1179) Keywords (Page 1173) Properties of local tags and constants (Page 1390) Setting the retentivity of local tags (Page 1391) Editing tables (Page 226) Declaring tags based on a PLC data type Requirement A PLC data type is declared in the current CPU. Procedure To declare a tag based on a PLC data type, follow these steps: 1. Select the appropriate declaration section in the interface: 2. Enter the PLC data type in the "Data type" column. You will be supported by Autocomplete during input. Result The tag is created. WinCC Basic V13.0 System Manual, 02/2014 1385 Programming the PLC 9.1 Creating the user program Note You define the default values of tags within a PLC data type when the PLC data type is created. You cannot change these values at the point of use of the PLC data type. If you change or delete PLC data types that are used in the block interface, the interface becomes inconsistent. To remedy this inconsistency, the interface has to be updated. See also: Updating the block interface (Page 1387) See also Editing tables (Page 226) Basics of PLC data types (Page 1551) Declaring higher-level tags Introduction To access data areas within a declared tag, you can overlay the declared tags with an additional declaration. This provides you with the option of addressing an already declared tag with a different data type. You can, for example, address the individual bits of a tag of WORD data type with an ARRAY of BOOL. Overlaying tags To overlay a tag with a new data type, follow these steps: 1. Open the block interface. 2. In the interface, select the tag that you want to overlay with a new data type. 3. Click "Add row" in the toolbar. A row is inserted after the tag to be overlaid. The overlaying tag must be declared in the row directly after the tag that is to be overlaid. 4. Enter a tag name in the "Name" column. 5. Enter the "AT" entry in the "Data type" column. You will be supported by Autocomplete in this step. The following is added to the entry in the "Name" column. "AT<Name of the higher-level tag>" 6. Click the data type selection button again and select the data type for the new tag. The tag is created. It points to the same data as the higher-level tag, however interprets this data with the new data type. 1386 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program Removing overlay To remove the overlay of a tag, follow these steps: 1. Select the overlaid tag that you want to remove. 2. Select the "Delete" command in the shortcut menu. 3. The overlay is removed. See also Editing tables (Page 226) Overlaying tags with AT (Page 1193) Declaring multi-instances Requirement The function block to be called exists in project tree and is multi-instance capable. The block interface of the calling function block is open. Procedure To declare a function block to be called as a multi-instance, follow these steps: 1. In the "Name" column of the "Static" section, enter a designation for the block call. 2. In the "Data type" column, enter the symbolic name for the function block to be called. Note The program editor will declare the multi-instance automatically if you program a block call in a network and then specify in the "Call options" dialog that you want to call the block as a multiple instance. See also Updating the block interface (Page 1387) Updating the block interface Introduction If you change or delete PLC data types or multiple instances that are used in the block interface, the interface will become inconsistent. To remedy this inconsistency, the interface has to be updated. You have two options for updating the block interface: WinCC Basic V13.0 System Manual, 02/2014 1387 Programming the PLC 9.1 Creating the user program Explicit updating of the block interface. The used PLC data types and multiple instances will be updated. The instance data blocks that belong to the block are not implicitly updated during this process. Implicit updating during compilation. All used PLC data types and multiple instances as well as the related instance data blocks will be updated. Explicit updating of the block interface To explicitly update the block interface, follow these steps: 1. Open the block interface. 2. Select the "Update" command in the shortcut menu. Implicit Updating during Compilation Proceed as follows to implicitly update all uses of PLC data types and multiple instances as well as the instance data blocks during compilation: 1. Open the project tree. 2. Select the "Program blocks" folder. 3. Select the command "Compile > Software (rebuild all blocks)" in the shortcut menu. See also Basics of PLC data types (Page 1551) Declaring tags based on a PLC data type (Page 1385) Editing tables (Page 226) Basic information on start values (Page 1533) Using tags within the program (Page 1179) Keywords (Page 1173) Properties of local tags and constants (Page 1390) Setting the retentivity of local tags (Page 1391) Updating block calls in LAD (Page 1418) Declaring multi-instances (Page 1387) Extending the block interface Description In order to enable the editing of PLC programs that have already been commissioned and that are running without error on a system, CPUs of the S7-1500 series and most CPUs of the S7-1200 V4 series support the option of extending the interfaces of function blocks during runtime. 1388 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program You can download the modified blocks without setting the CPU to STOP and without affecting the values of already loaded tags. This is a simple means of implementing program changes. This load process (download without reinitialization) will not have a negative impact on the controlled process. Principle of operation Each function block is always assigned a default memory reserve. The memory reserve is not used initially. Activate the memory reserve if you decide on loading interface changes after having compiled and downloaded the block. All tags that you subsequently declare will be saved to the memory reserve. The subsequent download does not influence any tags that are already loaded or have a negative impact on runtime. If you decide to review your program at a later time while the plant is not in operation, you are also provided an option of reworking the memory layout of individual or several blocks in a single pass. With this action, you move all tags from the reserve area to the regular area. The memory reserve is now cleared and made available for further interface extensions. Requirements This "Download without reinitialization" function is available if the following requirements are met: The project is in the "TIA Portal V12" format or a higher version. You are working with a CPU that supports "Download without reinitialization". The blocks were created in LAD, FBD, STL, or SCL. The blocks were created by the user, i.e. they are not included with the blocks delivered in your package. These blocks are assigned the optimized access attribute. Basic steps Perform the following steps if you want to extend the interface of a function block and then load the block without re-initialization. 1. All blocks have a default memory reserve of 100 bytes. You can adapt this memory reserve to suit your requirements. 2. Activate the memory reserve. 3. Extend the block interface. 4. Compile the block. 5. Download the block to the CPU as usual. WinCC Basic V13.0 System Manual, 02/2014 1389 Programming the PLC 9.1 Creating the user program For more information on the various steps, refer to chapter "Loading blocks (S7-1200/1500) ". Note The full scope of the "Download without reinitialization" function is only available on CPUs of the S7-1500 and S7-1200 V4 series. However, all CPU families support the option of extending the interface of function blocks and downloading newly declared tags without repercussion: You may add new tags in the "Temp" section and download these without influencing the process. You may create new tags of a structured data type in the "InOut" section and download these without influencing the process. Editing the properties of local tags and constants Properties of local tags and constants Properties The table below provides an overview of the properties of local tags and constants: Group Property Description General Name Name of the element. Data type Data type of the element. Default value Value with which you can pre-assign specific tags in the interface of the code block, or the value of a local constant. Specification of the default value is optional for tags. If you do not specify any value the predefined value for the indicated data type is used. For example, the value "false" is predefined for BOOL. The default value of a tag is applied as the start value in the corresponding instance. You can then replace these adopted values with instance-specific start values. Attributes Comment Comment for the element. Retain Marks the tag as retentive. The values of retentive tags are retained even after the power supply is switched off. This attribute is only available in the interface of the function block with optimized access. 1390 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program Group Property Description Accessible from HMI Indicates whether the tag can be used in HMI. When the attribute is set, you have read or write access to the tag from the HMI. When the attribute is not set, you cannot access the tag from the HMI. Please note, however, that you cannot implement general access protection for the tag with the "Accessible from HMI" attribute. Read or write access from other applications is possible even if the attribute is not enabled. Visible in HMI Shows whether the tag is visible by default in the HMI selection list. Hidden parameter Indicates whether the tag should be hidden for the block call. This is only possible if you have specified a valid predefined actual parameter beforehand. Predefined actual parameter Defines a parameter that is to be used as actual parameter during the block call. Configurable Indicates whether a parameter is configurable in CFC. For test Indicates whether a parameter is registered for the CFC test mode. Visible Indicates whether a parameter is visible in CFC. Interconnectable Indicates whether a parameter is interconnectable in CFC. Enable tag readback Indicates whether a parameter is relevant for the "Read back chart" function in CFC. Enumeration texts Assigns a parameter to an enumeration in CFC. Engineering unit Assigns a parameter to a unit in CFC. Low limit Defines the low limit for the parameter in CFC. High limit Defines the high limit for the parameter in CFC. See also Setting the retentivity of local tags (Page 1391) Changing properties of local tags and constants (Page 1392) Keywords (Page 1173) Setting the retentivity of local tags Introduction Function blocks store their data in an instance. To prevent data loss in the event of power failure, you can mark the data as retentive. This data is stored in a retentive memory area. The option of setting the retentivity depends on the set access type of the function block. WinCC Basic V13.0 System Manual, 02/2014 1391 Programming the PLC 9.1 Creating the user program Retentive behavior in blocks with standard access In blocks with standard access you cannot set the retentive behavior of individual tags. You can only define them as retentive in the assigned instance. All tags contained in the block are then considered as retentive. Retentivity for optimized block access In data blocks with optimized access you can define the retentive behavior of individual tags. For structured data type tags, the retentivity setting always applies to the entire structure. You can make no individual retentivity setting for individual elements within the structure. You cannot create retentive tags of the structured data type in the "InOut" section. In/out parameters with structured data type, for example ARRAY, STRUCT, or STRING, are always non-retentive. The following settings are available: Retentive The values of the tags or the structure are available even after a power failure. Non-retentive The values of the tags or the structure are lost in the event of a power failure. Set in IDB The retentivity can be set in the instance data block. The setting that is made in the instance data block than applies, however, centrally to all tags that are selected with "Set in IDB". See also Properties of local tags and constants (Page 1390) Basics of block access (Page 1151) Changing properties of local tags and constants Editing properties of an element in the block interface To edit the properties of an element in the block interface, follow these steps: 1. Open the block interface. 2. Select the required element in the table. 3. Change the entries in the columns. Editing properties of several elements in the block interface You can also simultaneously set or reset the "Retain", "Visible in HMI", "Accessible in HMI" and "Setpoint" columns for one or more selected elements. To change one of these properties for several elements, follow these steps: 1392 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program 1. Open the block interface. 2. Hold down the CTRL key. 3. In the required column, select each of the table cells whose value you want to change. 4. Select the "Set <property>" or "Reset <property>" command in the shortcut menu. Editing properties in the properties window To edit the properties of an individual tag or constant, follow these steps: 1. Select an element in the table. The properties of the element are shown in the Inspector window. 2. Change the entries in the inspector window. Renaming tags directly in the program editor To rename one or more elements, follow these steps: 1. Select one or more elements in the program. 2. Select the "Rename tag" command in the shortcut menu. The "Rename tag" dialog opens. It displays a declaration table with the selected elements. 3. Change the entries in the "Name" column. 4. Confirm the input by clicking the "Change" button. Editing the data type or comment in the program editor Proceed as follows to edit the data type or tag comment in the program editor: 1. Select the name of the tag. 2. Select the "Rewire tag" command in the shortcut menu. The "Rewire tag" dialog will open. The dialog shows a declaration table. 3. Change the entry in the "Data type" or "Comment" columns. 4. Click the "Change" button to confirm the input. Effect in the program In case of a change of the name, data type or address of a tag or constant, each location of use of the tag is automatically updated in the program. WinCC Basic V13.0 System Manual, 02/2014 1393 Programming the PLC 9.1 Creating the user program Note If you change the interface of a block, the program may become inconsistent. The inconsistencies are automatically updated, if possible. If an automatic updating is not possible, the inconsistent calls are marked in red. You than have to manually updated the inconsistencies. See also: Updating block calls in LAD (Page 1418) Updating block calls in FBD (Page 1460) See also Layout of the block interface (Page 1375) Editing tables (Page 226) Properties of local tags and constants (Page 1390) Setting the retentivity of local tags (Page 1391) Basic information on start values (Page 1533) Using tags within the program (Page 1179) Keywords (Page 1173) Updating the block interface (Page 1387) Declaring PLC data types (UDT) as actual parameters for in-out parameters. Use of PLC data types as predefined actual parameters In blocks with optimized access, you have the option to use PLC data types as actual parameters for in/out parameters (InOut) under certain conditions. This can be useful if you are using program blocks as library elements and want to store information about the actual parameters to be used along with the library element. Additionally, you have the option of hiding in/out parameters that have a vaild predefined actual parameter when the block is called. Hidden parameters are not visible initially when the block is called but can be displayed via a small arrow at the bottom edge of the box. 1394 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program Requirements The in/out parameter (InOut) is based on a PLC data type or a system data type. The in/out parameter has the retentivity setting "Retain" or "Non-retain". For in/out parameters with setting "Set in IDB", it is not possible to predefine actual parameters. The program block is a block with optimized access. Procedure To predefine the actual parameter of an in/out parameter, follow these steps: 1. Open the block interface. 2. Select an in/out parameter (InOut) in the block interface. 3. Open the "Properties" tab in the Inspector window. 4. Select the "Attributes" group in the area navigation. 5. Enter the required actual parameter in the "Predefined actual parameter" input box. 6. Select the "Hidden parameter" check box (optional). Result An actual parameter is predefined. If you save the program block as a library element, it thus also contains information about the actual parameter to be used. If the library element is used in the program, a check is made to determine whether the actual parameter you have predefined can be addressed. If so, it is automatically used as the actual parameter. If the actual parameter is not found in the program, a syntax error is signaled. The parameter is not hidden and the parameter must be initialized manually. Editing the block interface Inserting table rows Procedure Proceed as follows to insert a row above the selected row: 1. Select the row in front of which you want to insert a new row. 2. Click the "Insert row" button on the toolbar of the table. Result A new row is inserted above the selected row. WinCC Basic V13.0 System Manual, 02/2014 1395 Programming the PLC 9.1 Creating the user program See also Editing tables (Page 226) Inserting table rows Procedure Proceed as follows to insert a row below the selected row: 1. Select the row below which you want to insert a new row. 2. Click the "Add row" button on the table toolbar. Result A new empty row will be inserted below the selected row. See also Editing tables (Page 226) Deleting tags Procedure Follow the steps below to delete elements: 1. Select the row with the element to be deleted. You can also select several rows by clicking on them one after the other while holding down the <Ctrl> key or by pressing and holding down <Shift> and clicking on the first and last row. 2. Select the "Delete" command in the shortcut menu. See also Editing tables (Page 226) Automatically filling in successive cells You can load the contents of one or several table cells into the cells below, automatically filling in the successive cells. If you automatically fill in cells in the "Name" column, a consecutive number will be appended to each name. For example, "Motor" will become "Motor_1". You can define individual or more cells as well as entire rows as source area. If less rows exist in the open table than you want to fill, then you will first have to insert additional empty rows. 1396 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program Requirement The table is open. Sufficient declaration rows are available. Procedure To automatically fill in successive cells, follow these steps: 1. Select the cells to be loaded. 2. Click the "Fill" symbol in the bottom right corner of the cell. The mouse pointer is transformed into a crosshair. 3. Keep the mouse button pressed and drag the mouse pointer downwards over the cells that you want to fill in automatically. 4. Release the mouse button. The cells are filled in automatically. 5. If entries are already present in the cells that are to be automatically filled in, a dialog appears. In this dialog you can indicate whether you want to overwrite the existing entries or insert new rows for the new tags. See also Editing tables (Page 226) Show and hide table columns You can show or hide the columns in a table as needed. Procedure To show or hide table columns, follow these steps: 1. Click a column header. 2. Select the "Show/Hide" command in the shortcut menu. The selection of available columns is displayed. 3. To show a column, select the column's check box. 4. To hide a column, clear the column's check box. Editing tags with external editors To edit individual tags in external table editors, such as Excel, you can export or import these tags using copy and paste. However, you cannot copy structured tags to an editor. Requirements The block interface and an external editor are opened. WinCC Basic V13.0 System Manual, 02/2014 1397 Programming the PLC 9.1 Creating the user program Procedure To export individual tags to an external editor and import them again, follow these steps: 1. Select one or more tags. 2. Select "Copy" in the shortcut menu. 3. Switch to the external editor and paste the copied tags. 4. Edit the tags as required. 5. Copy the tags in the external editor. 6. Select the tags in the external editor. 7. Switch back to the block interface. 8. Select "Paste" in the shortcut menu. Creating program code Creating LAD programs Basic information on LAD LAD programming language Overview of the Ladder Logic (LAD) programming language LAD is a graphical programming language. The representation is based on circuit diagrams. The program is mapped in one or more networks. A network contains a power rail on the left where the rungs originate. The binary signal scans are arranged in the form of contacts on the rungs. The serial arrangement of the elements on a rung creates a series connection; arrangement on simultaneous branches creates a parallel connection. Complex functions are represented by boxes. Example of networks in LAD The following figure shows a LAD network with two normally open contacts, one normally closed contact and one coil: 1HWZRUN 6WDUW 6WRS &RLO &RLO 1398 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program Overview of the LAD elements LAD elements A LAD program consists of separate elements that you can arrange in series or parallel on the power rail of a network. Most program elements must be supplied with tags. There is at least one rung from the power rail. Network programming starts at the left edge of the rung. You can expand the power rail by several rungs and branches. For example, the following figure shows elements of a LAD network: 1) Power rail 2) Rung 3) Branch 4) Contact 5) Coil 6) Box Power rail Each LAD network consists of a power rail that contains at least one rung. A network can be extended by adding additional rungs. You can use branches to program parallel connections in the specific rungs. Contacts You can use contacts to create or interrupt a current-carrying connection between two elements. The current is relayed from left to right. You can use contacts to query the signal state or the value of an operand and control it depending on the result of the current flow. The following types of contact are available to you in a LAD program: WinCC Basic V13.0 System Manual, 02/2014 1399 Programming the PLC 9.1 Creating the user program Normally open contact: Normally open contacts forward the current if the signal state of a specified binary operand is "1". Normally closed contacts: Normally closed contacts forward the current if the signal state of a specified binary operand is "0". Contact with additional function: Contacts with additional function forward the current if a specific condition is met. With these contacts you can also execute an additional function, such as an RLO edge detection and a comparison. Coils You can use coils to control binary operands. Coils can set or reset a binary operand depending on the signal state of the result of logic operation. The following types of coils are available to you in a LAD program: Standard coils: Standard coils set a binary operand if current flows in the coil. The "Assignment" instruction is an example of a standard coil. Coils with additional function: These coils have additional functions in addition to the evaluation of the logic operation result. Coils for RLO edge detection and program control are examples of coils with additional function. Boxes Boxes are LAD elements with complex functions. The empty box is an exception. You can use the empty box as a placeholder in which you can select the required instruction. The following types of boxes are available to you in a LAD program: Boxes without EN/ENO mechanism: A box is executed depending on the signal state at the box inputs. The error status of the processing cannot be queried. Boxes with EN/ENO mechanism: A box is only executed if the enable input "EN" carries the signal state "1". If the box is processed correctly, the "ENO" enable output has signal state "1". If an error occurs during the processing, the "ENO" enable output is reset. Calls of code block are also shown in the network as boxes with EN/ENO mechanism. See also Rules for the use of LAD elements (Page 1409) 1400 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program Settings for LAD Overview of the settings for LAD Overview The following table shows the settings that you can make: Group Setting Description Font Font size Font size in program editor View Layout Compact or wide Changes the vertical spacing between operands and other objects (such as operand and contact). The change becomes visible once the block is reopened. Operand field With absolute information Additional display of the absolute addresses Maximum width Maximum number of characters that can be entered horizontally in the operand field. This setting recalculates the layout of the networks. Maximum height Maximum number of characters that can be entered vertically in the operand field. This setting recalculates the layout of the networks. See also Changing the settings (Page 1401) Changing the settings Procedure To change the settings, follow these steps: 1. Select the "Settings" command in the "Options" menu. The "Settings" window is displayed in the work area. 2. In the area navigation, select the "PLC programming" group. 3. Change the settings. Result The change will be loaded directly, there is no need to save it explicitly. WinCC Basic V13.0 System Manual, 02/2014 1401 Programming the PLC 9.1 Creating the user program See also Overview of the settings for LAD (Page 1401) Working with networks Using networks Function The user program is created in the block within networks. For a code block to be programmed, it must contain at least one network. To achieve a better overview of the user program, you can also subdivide your program into several networks. See also Inserting network title (Page 1405) Entering a network comment (Page 1407) Navigating networks (Page 1408) Inserting networks Requirement A block is open. Procedure To insert a new network, follow these steps: 1. Select the network after which you want to insert a new network. 2. Select the "Insert network" command in the shortcut menu. Result A new empty network is inserted into the block. See also Selecting networks (Page 1403) Copying and pasting networks (Page 1403) Deleting networks (Page 1404) Expanding and collapsing networks (Page 1405) Inserting network title (Page 1405) 1402 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program Entering a network comment (Page 1407) Navigating networks (Page 1408) Selecting networks Requirements A network is available. Selecting a network To select a network, follow these steps: 1. Click the title bar of the network that you want to select. Selecting several networks Proceed as follows to select several individual networks: 1. Press and hold down the <Ctrl> key. 2. Click all the networks that you want to select. To select several successive networks, follow these steps: 1. Press and hold down the <Shift> key. 2. Click the first network that you want to select. 3. Click the last network that you want to select. The first and last networks and all those in between are selected. See also Inserting networks (Page 1402) Copying and pasting networks (Page 1403) Deleting networks (Page 1404) Expanding and collapsing networks (Page 1405) Inserting network title (Page 1405) Entering a network comment (Page 1407) Navigating networks (Page 1408) Copying and pasting networks Copied networks can be pasted within the block or in another block. Networks that were created in LAD or FBD can also be inserted in blocks of the respective other programming language. WinCC Basic V13.0 System Manual, 02/2014 1403 Programming the PLC 9.1 Creating the user program Requirement A network is available. Procedure To copy and paste a network, follow these steps: 1. Select the network or networks to be copied. 2. Select "Copy" in the shortcut menu. 3. Select the network after which you want to paste in the copied network. 4. Select "Paste" in the shortcut menu. See also Inserting networks (Page 1402) Selecting networks (Page 1403) Deleting networks (Page 1404) Expanding and collapsing networks (Page 1405) Inserting network title (Page 1405) Entering a network comment (Page 1407) Navigating networks (Page 1408) Deleting networks Requirement A network is available. Procedure To delete a network, follow these steps: 1. Select the network that you want to delete. 2. Select the "Delete" command in the shortcut menu. See also Inserting networks (Page 1402) Selecting networks (Page 1403) Copying and pasting networks (Page 1403) Expanding and collapsing networks (Page 1405) Inserting network title (Page 1405) 1404 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program Entering a network comment (Page 1407) Navigating networks (Page 1408) Expanding and collapsing networks Requirements A network is available. Opening and closing a network To open a network, follow these steps: 1. Click on the right arrow in the network title bar. To close a network, follow these steps: 1. Click on the down arrow in the network title bar. Opening and closing all networks To open and close all networks, follow these steps: 1. In the toolbar, click "Open all networks" or "Close all networks". See also Inserting networks (Page 1402) Selecting networks (Page 1403) Copying and pasting networks (Page 1403) Deleting networks (Page 1404) Inserting network title (Page 1405) Entering a network comment (Page 1407) Navigating networks (Page 1408) Inserting network title The network title is the header of a network. The length of the network title is limited to one line. You can enter the title manually or set it automatically. When you set it automatically, you can do this for individual networks or use the settings to specify that the network title is always set automatically. For automatic insertion of the network title, the comment of the operand in one of the following instructions in the network is evaluated: WinCC Basic V13.0 System Manual, 02/2014 1405 Programming the PLC 9.1 Creating the user program Assignment Set output Reset output The instruction that is listed first in the network is used. The network title is only inserted automatically when the following conditions are fulfilled: The network does not have a title yet. The operand of the instruction used for the comment has a comment. Note Note the following restrictions for automatic insertion of the network title: The network title is not adapted if you change the comment of the operand at a later time. The network title is not adapted if you change the operand of the instruction. The network title is only set by the writing instructions listed above. If the operand is of the data type array, the comment of the array is used and not the comments of the array elements. Comments of invalid operands are not taken into consideration. Entering the network title manually To enter a network title, follow these steps: 1. Click on the title bar of the network. 2. Enter the network title. Setting the network title automatically To specify that the network titles are always set automatically, follow these steps: 1. Select the "Settings" command in the "Options" menu. The "Settings" window is displayed in the work area. 2. In the area navigation, select the "PLC programming" group. 3. Select the "Set network title automatically" check box in the "Additional settings" group. The network titles are set automatically as of this time if the conditions listed above are fulfilled. To set an individual network title automatically, follow these steps: 1. Right-click "Network <Number of the network>" in the title bar of a network. 2. Select the "Set network title automatically" command in the shortcut menu. The title of the selected network is set based on the comment of the operand if the conditions listed above are fulfilled. 1406 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program See also Using networks (Page 1402) Inserting networks (Page 1402) Selecting networks (Page 1403) Copying and pasting networks (Page 1403) Deleting networks (Page 1404) Expanding and collapsing networks (Page 1405) Entering a network comment (Page 1407) Navigating networks (Page 1408) Entering a network comment You can use network comments to provide comments on the program contents of individual networks. For example, you can indicate the function of the network or draw attention to special characteristics. Requirement A network is available. Procedure To enter a network comment, follow these steps: 1. Click on the right arrow before the network title. 2. If the comment area is not visible, click "Network comments on/off" in the toolbar. The comment area is displayed. 3. Click "Comment" in the comment area. The "Comment" text passage is selected. 4. Enter the network comment. See also Using networks (Page 1402) Inserting networks (Page 1402) Selecting networks (Page 1403) Copying and pasting networks (Page 1403) Deleting networks (Page 1404) Expanding and collapsing networks (Page 1405) WinCC Basic V13.0 System Manual, 02/2014 1407 Programming the PLC 9.1 Creating the user program Inserting network title (Page 1405) Navigating networks (Page 1408) Navigating networks You can navigate straight to a specific position within a block. Procedure To navigate to a specific position within a block, follow these steps: 1. Right-click in the code area of the programming window. 2. Select the "Go to > Network/line" command in the shortcut menu. The "Go to" dialog will open. 3. Enter the network to which you want to navigate. 4. Enter the line number of the network to which you want to navigate. 5. Confirm your entry with "OK". Result The relevant line will be displayed if this is possible. If the network or line requested does not exist, the last existing network or the last existing line in the network requested will be displayed. See also Using networks (Page 1402) Inserting networks (Page 1402) Selecting networks (Page 1403) Copying and pasting networks (Page 1403) Deleting networks (Page 1404) Expanding and collapsing networks (Page 1405) Inserting network title (Page 1405) Entering a network comment (Page 1407) 1408 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program Inserting LAD elements Rules for the use of LAD elements Rules Note the following rules when inserting LAD elements: Every LAD network must terminate with a coil or a box. However, the following LAD elements must not be used to terminate a network: - Comparator boxes - Instructions for positive and negative RLO edge detection The starting point of the branch for a box connection must always be the power rail. Logic operations or other boxes can be present in the branch before the box. Only contacts can be inserted into simultaneous branches with preceding logic operations. The contact for negating the result of logic operation (-|NOT|-) is an exception here. The contact for negating the result of logic operation, as well as coils and boxes, can be used in simultaneous branches if they originate directly from the power rail. Constants (e.g. TRUE or FALSE) cannot be assigned to normally closed or normally open contacts. Instead, use operands of the BOOL data type. Only one jump instruction can be inserted in each network. Only one jump label can be inserted in each network. Instructions with positive or negative edge detection may not be arranged directly at the left margin of the rung as they requires a prior logic operation. Placement rules for S7-1200/1500 CPUs The following table sets out the instructions that can only be positioned at the end of the network: Instruction WinCC Basic V13.0 System Manual, 02/2014 Mnemonics Name Preceding logic operation required SET_BF Set bit field No RESET_BF Reset bit field No JMP Jump if RLO = 1 No JMPN Jump if RLO = 0 Yes JMP_LIST Define jump list No SWITCH Jump distributor No RET Return No 1409 Programming the PLC 9.1 Creating the user program Placement rules for S7-300/400 CPUs The following table sets out the instructions that can only be positioned at the end of the network: Mnemonic s Name Instruction Preceding logic operation required S Set output Yes R Reset output Yes SP Start pulse timer Yes SE Start extended pulse timer Yes SD Start on-delay timer Yes SS Start retentive on-delay timer Yes SF Start off-delay timer Yes SC Set counter value Yes CU Count up Yes CD Count down Yes JMP Jump if RLO = 1 No JMPN Jump if RLO = 0 Yes RET Return No OPN Open global data block No OPNI Open instance data block No CALL Call block No SAVE Save RLO in BR bit No MCRA Enable MCR range No MCRD Disable MCR range No MCR< Open MCR ranges No MCR> Close MCR ranges No See also Prohibited interconnections in LAD (Page 1411) Overview of the LAD elements (Page 1399) 1410 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program Prohibited interconnections in LAD Power flow from right to left No branches can be programmed that could result in a power flow in the reverse direction. , , , , , , 4 ,PSHUPLVVLEOHUDWHRIIORZ , , Short-circuit No branches may be programmed that would cause a short-circuit. , , , 4 6KRUWFLUFXLWLPSHUPLVVLEOH Logic operations The following rules apply to logic operations: Only Boolean inputs can be combined with preceding logic operations. Only the first Boolean output can be combined with a further logic operation. Only one complete logical path can exist per network. Paths that are not connected can be linked. See also Rules for the use of LAD elements (Page 1409) Inserting LAD elements using the "Instructions" task card Requirement A network is available. WinCC Basic V13.0 System Manual, 02/2014 1411 Programming the PLC 9.1 Creating the user program Procedure To insert a LAD element into a network using the "Instructions" task card, follow these steps: 1. Open the "Instructions" task card. 2. Navigate to the LAD element that you want to insert. 3. Use drag-and-drop to move the element to the desired place in the network. If the element is an internal system function block (FB), the "Call options" dialog opens. In this dialog you can create an instance data block of the single-instance or multiple-instance type for the function block in which the data of the inserted element will be saved. You will find the new instance data block created in the project tree in the "Program resources" folder under "Program blocks > System blocks". If you have selected "multiple instance", these are located in the block interface in the "Static" section. Or: 1. Select the point in the network at which you want to insert the element. 2. Open the "Instructions" task card. 3. Double-click on the element you want to insert. If the element is an internal system function block (FB), the "Call options" dialog opens. In this dialog you can create an instance data block of the single-instance or multiple-instance type for the function block in which the data of the inserted element will be saved. You will find the new instance data block created in the project tree in the "Program resources" folder under "Program blocks > System blocks". If you have selected "multiple instance", these are located in the block interface in the "Static" section. Result The selected LAD element is inserted with placeholders for the parameters. Inserting LAD elements using an empty box Requirement A network is available. Procedure To insert an LAD element into a network using an empty box, follow these steps: 1. Open the "Instructions" task card. 2. Navigate to "General > Empty box" in the "Basic instructions" palette. 3. Use a drag-and-drop operation to move the "Empty box" element to the desired place in the network. 1412 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program 4. Position the cursor over the triangle in the top right-hand corner of the empty box. A drop-down list is displayed. 5. Select the required LAD element from the drop-down list. If the element is an internal system function block (FB), the "Call option" dialog opens. In this dialog you can create an instance data block of the single-instance or multiple-instance type for the function block in which the data of the inserted element will be saved. You will find the new instance data block created in the project tree in the "Program resources" folder under "Program blocks > System blocks". If you have selected "multi-instance", these are located in the block interface in the "Static" section. Result The empty box is changed to the respective LAD element. Placeholders are inserted for the parameters. Selecting the data type of a LAD element Selecting a data type Introduction Some instructions can be executed with several different data types. If you use one of these instructions in the program, you have to specify a valid data type for the instruction at the specific point in the program. For some instructions, you have to select the data types for the inputs and outputs separately. Note The valid data type (BOOL) for the tags on the enable input EN and the enable output ENO is predefined by the system and cannot be changed. The valid data types for an instruction are listed in the instruction drop-down list. You specify the data type of the instruction by selecting an entry from the drop-down list. If the data type of an operand differs from the data type of the instruction and cannot be converted implicitly, the operand is displayed in red and a rollout with the corresponding error message appears. Data type selection of mathematical instructions Some mathematical instructions provide you with the option of having the data type automatically set corresponding to the data types of the operand. In the drop-down list for data type selection, these instructions have the entry "Auto" in addition to the actual data types. If you select this entry and then allocate the first operand, the data type of the operand is selected as data type for the instruction. The entry in the drop-down list changes to "Auto (<Data type>)", WinCC Basic V13.0 System Manual, 02/2014 1413 Programming the PLC 9.1 Creating the user program e.g. "Auto (Real)". If you allocate additional operands, the automatically set data type of the instruction is adjusted according to the following criteria: You supply all other operands with tags of the same data type: The data type of the instruction is not changed. You supply all other operands with tags whose data type is smaller than the data type of the instruction: The data type of the instruction is not changed. For the operand with the smaller data type, an implicit conversion is conducted if necessary. You supply an additional operand with a tag whose data type is greater than the data type of the instruction: The data type of the instruction is changed to the larger data type. An implicit conversion is performed, if necessary, for operands that deviate from the newly set data type of the instruction. Each change in the data type of an operand can result in a change of the data type of the instruction. Other operands may possibly be implicitly converted as a result. Operands for which an implicit conversion is performed are marked with a gray square. Note Please also observe the information on data type conversion for your device and, in particular, the notes on the IEC check. See also: Data type conversion See also Defining the data type of an instruction (Page 1414) Defining the data type of an instruction Introduction Some instructions can be executed with several different data types. When you insert such instructions into your program, you must specify the data type for these instructions at the actual point in the program. Specifying the data type by means of the drop-down list To define the data type of an instruction using the drop-down list, follow these steps: 1. Insert the instruction at the required point in the program using drag-and-drop. The entry "???" (undefined) is displayed in the drop-down list of the inserted instruction. 2. Click the triangle in the upper corner of the drop-down list. The drop-down list will open to display the data types valid for the instruction. 1414 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program 3. Select a data type from the drop-down list. The selected data type is displayed. 4. If the instruction has two drop-down lists, select the data type for the instruction inputs in the left-hand drop-down list and the data type for the instruction outputs in the right-hand drop-down list. Specifying data type by assigning tags To define the data type of an instruction by assigning tags, follow these steps: 1. Insert the instruction at the required point in the program using drag-and-drop. The entry "???" (undefined) is displayed in the drop-down list of the inserted instruction. 2. At an input or output, specify a valid tag, the data type of which is to be applied as the instruction data type. The data type of the tag is displayed in the drop-down list. 3. Enter a valid tag at an input and a valid tag at an output if data types need to be defined for both the inputs and outputs of the instruction. The tag specified at the input determines the data type of the inputs; the tag specified at the output determines the data type of the outputs of the instruction. Automatically specifying the data type of mathematical instructions To automatically specify the data type for mathematical instructions, follow these steps: 1. Insert the mathematical instruction at the required point in the program using drag-and-drop. The entry "???" (undefined) is displayed in the drop-down list of the inserted instruction. 2. Select the "Auto" entry from the drop-down list. 3. Enter a valid tag at an input or output. The data type of the tag is applied as data type of the instruction. The entry in the dropdown list changes to "Auto (<Data type>)". See also: Selecting a data type (Page 1413) See also Selecting a data type (Page 1413) Using favorites in LAD Adding LAD elements to Favorites Requirement A block is open. The multipane mode is set for the "Instructions" task card or the Favorites are also displayed in the editor. WinCC Basic V13.0 System Manual, 02/2014 1415 Programming the PLC 9.1 Creating the user program Procedure To add SCL instructions to the Favorites, follow these steps: 1. Open the "Instructions" task card. 2. Maximize the "Basic instructions" pane. 3. Navigate in the "Basic instructions" pane to the instruction that you want to add to the Favorites. 4. Drag-and-drop the instruction into the "Favorites" pane or into the Favorites area in the program editor. Note To additionally display the Favorites in the program editor, click the "Display favorites in the editor" button in the program editor toolbar. See also Removing LAD elements from Favorites (Page 1417) Overview of the program editor (Page 1354) Inserting LAD elements using favorites Requirement A block is open. Favorites are available. Procedure To insert an instruction into a program using Favorites, follow these steps: 1. Drag-and-drop the desired instruction from Favorites to the desired position. Or: 1. Select the position in the program where you want to insert the instruction. 2. In the Favorites, click on the instruction you want to insert. Note To additionally display the Favorites in the program editor, click the "Display favorites in the editor" button in the program editor toolbar. 1416 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program See also Removing LAD elements from Favorites (Page 1417) Overview of the program editor (Page 1354) Removing LAD elements from Favorites Requirement A code block is open. Procedure To remove instructions from Favorites, follow these steps: 1. Right-click on the instruction you want to remove. 2. Select the "Remove instruction" command in the shortcut menu. Note To additionally display the Favorites in the program editor, click the "Display favorites in the editor" button in the program editor toolbar. See also Adding LAD elements to Favorites (Page 1415) Inserting LAD elements using favorites (Page 1416) Overview of the program editor (Page 1354) Insert block calls in LAD Inserting block calls using a drag-and-drop operation You can insert calls for existing functions (FC) and function blocks (FB) using a drag-and-drop operation from the project tree. If you call function blocks from other function blocks, you can either call them as single-instance or multi-instance blocks. If a function block is called as single instance, it will store its data in a data block of its own. If a function block is called as multiinstance, it will store its data in the instance data block of the calling function block. Requirement A network is available. The block that is to be called is available. WinCC Basic V13.0 System Manual, 02/2014 1417 Programming the PLC 9.1 Creating the user program Inserting a call of a function (FC) To insert a call of a function (FC) into a network using a drag-and-drop operation, follow these steps: 1. Drag the function from the project tree to the required network. Inserting a call for a function block (FB) To insert a call for a function block (FB), follow these steps: 1. Drag the function block from the project tree to the required network. The "Call options" dialog opens. 2. Enter in the dialog whether you wish to call the block as single or multi-instance. - If you click on the "Single instance" button, you will have to enter a name in the "Name" text box for the data block that you want to assign to the function block. - If you click on the "Multi-instance" button, you will have to enter the name of the tag in the "Name in the interface" text box; this is the name that you use to enter the called function block as a static tag in the interface of the calling block. 3. Confirm your entries with "OK". Result The function or the function block is inserted with its parameters. You can then assign the parameters. See also: Auto-Hotspot Note If when calling a function block you specify an instance data block that does not exist, it will be created. If you have called a function block as a multi-instance, this will be entered as a static tag in the interface. See also Updating block calls in LAD (Page 1418) Changing the instance type (Page 1419) Single instances (Page 1159) Multi-instances (Page 1159) Updating block calls in LAD If interface parameters of a called block are changed, the block call can no longer be executed correctly. You can avoid such inconsistent block calls by updating the block calls. You have two options to update the block calls: 1418 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program Explicit updating in the program editor. The block calls in the open block will be updated. Implicit updating during compilation. All block calls in the program as well as the used PLC data types will be updated. Update blocks in the program editor To update a block call within a block, follow these steps: 1. Open the block in the program editor. 2. Click "Update inconsistent block calls" in the toolbar. Or: 1. Open the block in the program editor. 2. Right-click on the instruction with the block call. 3. Select the "Update" command in the shortcut menu. The "Interface update" dialog opens. This dialog shows the differences between the block interface in use and the changed interface of the called block. 4. If you want to update the block call, click "OK". To cancel the update, click "Cancel". Update block calls during compilation Follow these steps to update all block calls and uses of PLC data types during compilation implicitly: 1. Open the project tree. 2. Select the "Program blocks" folder. 3. Select the command "Compile > Software (rebuild all blocks)" in the shortcut menu. See also Inserting block calls using a drag-and-drop operation (Page 1417) Changing the instance type (Page 1419) Changing the instance type Instance type There are two ways of calling function blocks: As a single instance As a multiple instance See also: Auto-Hotspot You can modify a defined instance type at any time. WinCC Basic V13.0 System Manual, 02/2014 1419 Programming the PLC 9.1 Creating the user program Requirement The user program contains a block call. Procedure To change the instance type of a function block, follow these steps: 1. Open the code block and select the block call. 2. Select the "Change instance" command in the shortcut menu. The "Call options" dialog opens. 3. Click the "Single instance" or "Multi instance" button. - If you select the "Single instance" instance type, enter a name for the data block that is to be assigned to the function block. - If you select "Multiple instance" as the instance type, enter in the "Name in the interface" text field the name of the tag with which the called function block is to be entered as a static tag in the interface of the calling block. 4. Confirm your entries with "OK". Note The previous single and multiple instances will not be deleted automatically. See also Inserting block calls using a drag-and-drop operation (Page 1417) Updating block calls in LAD (Page 1418) Inserting complex LAD instructions Using the "Calculate" instruction Requirement A network is available. Procedure Proceed as follows to use the "Calculate" instruction: 1. Open the "Instructions" task card. 2. Navigate to "Math functions > CALCULATE" in the "Basic instructions" pane. 1420 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program 3. Use drag-and-drop to move the element to the desired place in the network. The instruction "Calculate" will be inserted for the data type with a placeholder expression and question mark. 4. Enter the data type for the calculation. 5. Enter the operands for the calculation. Note The calculation is run with the inputs of the "Calculate" instruction. If you want to use constants you must also insert appropriate inputs for them. 6. Click on the "Edit 'Calculate' instruction" button to replace the placeholder expression with the correct expression. The "Edit 'Calculate' instruction" dialog will open. 7. Enter the required expression in the "OUT:= " text box. Note In the "Example" area you can find an example of a valid expression and possible instructions that you can use. To determine a value with the help of Pythagoras' theorem, for example, enter "OUT := SQRT (SQR (IN1) + SQR (IN2))". 8. Confirm your entry with "OK". See also CALCULATE: Calculate (Page 1845) Using free-form comments Basic information on using free-form comments in LAD Introduction Free-form comments allow you to add comments to the source code for graphic programming languages similar to line comments for textual languages. Free-form comments can be used for the following elements: Boxes Coils WinCC Basic V13.0 System Manual, 02/2014 1421 Programming the PLC 9.1 Creating the user program See also Inserting free-form comments (Page 1422) Editing free-form comments (Page 1422) Deleting free-form comments (Page 1424) Inserting free-form comments Requirement A network with instructions is available. Procedure To insert a free comment on an instruction, proceed as follows: 1. If necessary, activate the "Free-form comments on/off" button in the toolbar. 2. Right-click on the instruction for which you want to insert a free-form comment. 3. Select the "Insert comment" command in the shortcut menu. A comment box with a standard comment opens. The comment box is connected by an arrow to the corresponding instruction. 4. Enter the required comment in the comment box. See also Basic information on using free-form comments in LAD (Page 1421) Editing free-form comments (Page 1422) Deleting free-form comments (Page 1424) Editing free-form comments Introduction Free-form comments can be edited as follows: Changing the comment text Changing the position and size of the comment box Attaching a comment to another element Showing and hiding free comments 1422 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program Changing the comment text To change the text of free-form comments, follow these steps: 1. Click on the comment box. 2. Enter the desired text. Changing the position of the comment box To change the positioning of the comment box, follow the steps below: 1. Left-click the comment box and keep the mouse button pressed. 2. Drag the comment box to the desired location. Changing the size of the comment box To change the size of the comment box, follow the steps below: 1. Click on the comment box. 2. Drag the comment box on the move handle in the lower right corner to the desired size. Attaching a comment to another element To attach a free-form comment to another element, follow these steps: 1. Left-click the point of the arrow that links the comment box with the instruction and keep the mouse button pressed. 2. Drag the arrow to the element to which you want to attach the comment. Possible insertion points are marked with a green square. 3. Release the mouse button. Showing and hiding free comments To show or hide a free-form comments, follow these steps: 1. Click the "Free-form comment on/off" button in the toolbar. See also Basic information on using free-form comments in LAD (Page 1421) Inserting free-form comments (Page 1422) Deleting free-form comments (Page 1424) WinCC Basic V13.0 System Manual, 02/2014 1423 Programming the PLC 9.1 Creating the user program Deleting free-form comments Procedure To delete a free-form comment, proceed as follows: 1. Right-click on the free-form comment that you want to delete. 2. Select the "Delete" command in the shortcut menu. See also Basic information on using free-form comments in LAD (Page 1421) Inserting free-form comments (Page 1422) Editing free-form comments (Page 1422) Editing LAD elements Selecting LAD elements You can select several individual elements or all elements in a network. Requirement LAD elements are available Selecting several individual LAD elements To select several individual LAD elements, follow these steps: 1. Press and hold down the <Ctrl> key. 2. Click on all the LAD elements you wish to select. 3. Now release the <Ctrl> key. Selecting all LAD elements in a network To select all LAD elements in a network, follow these steps: 1. Go to the network whose elements you wish to select. 2. Select the "Select all" command in the "Edit" menu or press <Ctrl A>. 1424 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program See also Copying LAD elements (Page 1425) Cutting LAD elements (Page 1426) Pasting an LAD element from the clipboard (Page 1426) Replacing LAD elements (Page 1427) Inserting additional inputs and outputs in LAD elements (Page 1428) Removing inputs and outputs (Page 1429) Enabling and disabling the EN/ENO mechanism (Page 1429) Deleting LAD elements (Page 1431) Copying LAD elements Requirement An LAD element is available. Procedure To copy a LAD element, follow these steps: 1. Right-click the LAD element that you want to copy. 2. Select "Copy" in the shortcut menu. Result The LAD element will be copied and saved to the clipboard. See also Selecting LAD elements (Page 1424) Cutting LAD elements (Page 1426) Pasting an LAD element from the clipboard (Page 1426) Replacing LAD elements (Page 1427) Inserting additional inputs and outputs in LAD elements (Page 1428) Removing inputs and outputs (Page 1429) Enabling and disabling the EN/ENO mechanism (Page 1429) Deleting LAD elements (Page 1431) WinCC Basic V13.0 System Manual, 02/2014 1425 Programming the PLC 9.1 Creating the user program Cutting LAD elements Requirement An LAD element is available. Cutting To cut a LAD element, follow these steps: 1. Right-click the LAD element that you want to cut. 2. Select "Cut" in the shortcut menu. Result The LAD element will be cut and saved to the clipboard. See also Selecting LAD elements (Page 1424) Copying LAD elements (Page 1425) Pasting an LAD element from the clipboard (Page 1426) Replacing LAD elements (Page 1427) Inserting additional inputs and outputs in LAD elements (Page 1428) Removing inputs and outputs (Page 1429) Enabling and disabling the EN/ENO mechanism (Page 1429) Deleting LAD elements (Page 1431) Pasting an LAD element from the clipboard Requirement An LAD element is available. Procedure To paste an LAD element from the clipboard, follow these steps: 1. Copy a LAD element or cut a LAD element. 2. Right-click the point in the network where you want to paste the element. 3. Select "Paste" in the shortcut menu. 1426 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program See also Selecting LAD elements (Page 1424) Copying LAD elements (Page 1425) Cutting LAD elements (Page 1426) Replacing LAD elements (Page 1427) Inserting additional inputs and outputs in LAD elements (Page 1428) Removing inputs and outputs (Page 1429) Enabling and disabling the EN/ENO mechanism (Page 1429) Deleting LAD elements (Page 1431) Replacing LAD elements You can easily exchange LAD elements with other LAD elements of the same type. This has the advantage that the parameters are retained and need not be entered again. For example, you can exchange normally open contacts and normally closed contacts or RS FlipFlop and SR FlipFlop. Requirements A network with at least one LAD element is present. Procedure To replace an LAD element with another LAD element, follow these steps: 1. Select the LAD element that you want to replace. 2. Position the cursor over the triangle in the top right-hand corner of the LAD element. A drop-down list is displayed. 3. From the drop-down list, select the LAD element that you want to use to replace the existing LAD element. See also Selecting LAD elements (Page 1424) Copying LAD elements (Page 1425) Cutting LAD elements (Page 1426) Pasting an LAD element from the clipboard (Page 1426) Inserting additional inputs and outputs in LAD elements (Page 1428) Removing inputs and outputs (Page 1429) Enabling and disabling the EN/ENO mechanism (Page 1429) Deleting LAD elements (Page 1431) WinCC Basic V13.0 System Manual, 02/2014 1427 Programming the PLC 9.1 Creating the user program Inserting additional inputs and outputs in LAD elements Introduction You can expand LAD elements which execute commutative arithmetic instructions by adding additional inputs. Such elements are, for example, the instructions "Add" (ADD) and "Multiply" (MUL). You can expand the MOVE and DEMUX instruction boxes by adding additional outputs. Requirement An LAD element is available that permits the insertion of additional inputs and outputs. Inserting an additional input To add an additional input to the box of a LAD element, follow these steps: 1. Right-click on an existing input of the LAD element. 2. Select "Insert input" in the shortcut menu. An additional input is added to the box of the LAD element. Or: 1. Click on the yellow star symbol beside the last input in the instruction box. An additional input is added to the box of the LAD element. Inserting an additional output To add an additional output to the box of a LAD element, follow these steps: 1. Right-click on an existing output of the LAD element. 2. Select "Insert output" from the shortcut menu. An additional output is added to the box of the LAD element. Or: 1. Click on the yellow star symbol beside the last input in the instruction box. An additional output is added to the box of the LAD element. See also Selecting LAD elements (Page 1424) Copying LAD elements (Page 1425) Cutting LAD elements (Page 1426) Pasting an LAD element from the clipboard (Page 1426) Replacing LAD elements (Page 1427) Removing inputs and outputs (Page 1429) Enabling and disabling the EN/ENO mechanism (Page 1429) Deleting LAD elements (Page 1431) 1428 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program Removing inputs and outputs Introduction Inputs and outputs which you have added to an instruction can be removed. Requirement An LAD element is available to which you have added additional inputs and outputs. Remove input To remove an input, follow these steps: 1. Select the input that you want to remove. 2. Select the "Delete" command in the shortcut menu. The input of the LAD element is removed. Remove output To remove an output, follow these steps: 1. Select the output that you want to remove. 2. Select the "Delete" command in the shortcut menu. The output of the LAD element will be removed. See also Selecting LAD elements (Page 1424) Copying LAD elements (Page 1425) Cutting LAD elements (Page 1426) Pasting an LAD element from the clipboard (Page 1426) Replacing LAD elements (Page 1427) Inserting additional inputs and outputs in LAD elements (Page 1428) Enabling and disabling the EN/ENO mechanism (Page 1429) Deleting LAD elements (Page 1431) Enabling and disabling the EN/ENO mechanism In LAD and FBD, certain instructions have an enable output ENO and thus use the EN/ENO mechanism. This allows you to query runtime errors in instructions and react to them. In order to increase the performance of the CPU, the EN/ENO mechanism is disabled in the default setting. This means that you are not initially able to react to runtime errors of the instruction WinCC Basic V13.0 System Manual, 02/2014 1429 Programming the PLC 9.1 Creating the user program using the ENO value. However, you can enable the EN/ENO mechanism again at any time, if required. You can enable the EN/ENO mechanism individually for each instruction in order to generate the ENO. If you enable the EN/ENO mechanism for an instruction, other instructions that you subsequently add to your program are also inserted with the EN/ENO mechanism enabled. You can disable the EN/ENO mechanism again at any time if you do not want to use the evaluation of ENO for an instruction. Further instructions that you subsequently add to your program will then be inserted without the EN/ENO mechanism. See also: Basics of the EN/ENO mechanism (Page 1299) Activating the EN/ENO mechanism Proceed as follows to activate the EN/ENO mechanism of an instruction: 1. In your program, right-click the instruction at which you want to activate the EN/ENO mechanism. 2. Select the "Generate ENO" command from the shortcut menu. The ENO value is again generated for the instruction. Other instructions are inserted with the enable output. Deactivating the EN/ENO mechanism Proceed as follows to deactivate the EN/ENO mechanism of an instruction: 1. In your program, right-click the instruction at which you want to deactivate the EN/ENO mechanism. 2. Select the "Do not generate ENO" command from the shortcut menu. The ENO value is no longer generated for the instruction. Other instructions are inserted without enable output. See also Selecting LAD elements (Page 1424) Copying LAD elements (Page 1425) Cutting LAD elements (Page 1426) Pasting an LAD element from the clipboard (Page 1426) Replacing LAD elements (Page 1427) Inserting additional inputs and outputs in LAD elements (Page 1428) Removing inputs and outputs (Page 1429) Deleting LAD elements (Page 1431) 1430 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program Deleting LAD elements Requirement An LAD element is available. Procedure To delete a LAD element, follow these steps: 1. Right-click the LAD element that you want to delete. 2. Select the "Delete" command in the shortcut menu. See also Selecting LAD elements (Page 1424) Copying LAD elements (Page 1425) Cutting LAD elements (Page 1426) Pasting an LAD element from the clipboard (Page 1426) Replacing LAD elements (Page 1427) Inserting additional inputs and outputs in LAD elements (Page 1428) Removing inputs and outputs (Page 1429) Enabling and disabling the EN/ENO mechanism (Page 1429) Inserting operands into LAD instructions Inserting operands The character strings "<???>", "<??.?>" and "..." are inserted as placeholders for the parameters when an LAD element is inserted. The "<???>" and "<??.?>" strings displayed in red indicate parameters that need to be connected. The "..." string displayed in black indicates parameters that may be connected. "<??.?>" stands for Boolean placeholders. Note If you position the cursor over the placeholder, the expected data type will be displayed. Requirement An LAD element is available. WinCC Basic V13.0 System Manual, 02/2014 1431 Programming the PLC 9.1 Creating the user program Procedure To connect the parameters of a LAD element, follow these steps: 1. Double-click the placeholder of the parameter. An entry field opens, and the placeholder is selected. 2. Enter the appropriate parameter. Note If you enter the absolute address of a parameter that has already been defined, this absolute address will be changed to the symbolic name of the parameter as soon as the input is confirmed. If you have not yet defined the parameter, a new tag with this absolute address and the default name "Tag_<n>" will be entered in the PLC tag table. When you confirm your input, the absolute address will be replaced with the symbolic name "Tag_<n>". 3. Confirm the parameter with the Enter key. 4. If you have not yet defined the parameter, you can define it directly in the program editor using the shortcut menu. See also: Declaring PLC tags in the program editor (Page 1314) Declaring local tags in the program editor (Page 1382) Or drag from it the PLC tag table: 1. In the project tree, select the "PLC tags" folder or open the PLC tag table. 2. If you have opened the PLC tag table, drag the symbol from the first column of the desired tag to the appropriate place in your program. If you have not opened the PLC tag table yet, open the detail view now. Drag the desired tag from the detail view to the appropriate place in your program. Or drag from it the block interface: 1. Open the block interface. 2. Drag the required operand from the block interface to the instruction window. Result If the syntax is error-free, the displayed parameter is black. The editor then jumps to the next placeholder. If there is an error in the syntax, the cursor stays in the entry field and a corresponding error message is displayed in the status line. If you press the Enter key again, the entry field is closed and the faulty entry is displayed in red italics. 1432 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program Wiring hidden parameters Introduction Depending on the CPU used, you can use complex instructions in your program that are dispatched with the TIA portal. These instructions can contain parameters that are declared as hidden. If an instruction contains hidden parameters, the instruction box has a small arrow on the lower edge. You can recognize hidden parameters by their white font. You can show and wire the hidden parameters at any time. Showing or hiding hidden parameters To show or hide hidden parameters, follow these steps: 1. Click on the down arrow at the bottom edge of the instruction box to show hidden parameters. 2. Click on the up arrow at the bottom edge of the instruction box to hide hidden parameters. Wiring hidden parameters To wire parameters, follow these steps: 1. Wire the hidden parameters like normally visible parameters. The hidden parameter is transformed into a visible parameter. See also Using libraries (Page 325) Displaying or hiding variable information Introduction You can display the following information about the tags to be used in the Program editor: Name of the tag Address of the tag Simple or hierarchical comments for tag documentation The information is taken from the block interface for local tags and DB tags and from the PLC tag table for tags that are valid CPU-wide. You can display the tag information either for all the blocks or for individually opened blocks. If you display the tag information for all the blocks, the tag information for all the blocks currently opened and opened in future is shown. You can hide the tag information at any time again. If you have hidden the tag information for all blocks, you can display it again for individual blocks that are open. WinCC Basic V13.0 System Manual, 02/2014 1433 Programming the PLC 9.1 Creating the user program When you select the display of tag information with hierarchical comments, the comments of the higher structure levels are also displayed for structured tags. The comments are shown in brackets after the tag comment; the comments of the individual levels are separated by a dot. If there is no comment for a tag on a structure level, it is not displayed. This is indicated by two successive dots. Displaying or hiding tag information for all the blocks Proceed as follows to display or hide the tag information for all the blocks: 1. Select the "Settings" command in the "Options" menu. The "Settings" window is displayed in the work area. 2. In the area navigation, select the "PLC programming" group. 3. If you want to display the tag information, select the "Show" option or the "Tag information with hierarchical comments" option in the drop-down list, depending on whether you want to display simple or hierarchical comments. 4. If you want to hide the tag information, select the option "Collapse" in the "Tag information" drop-down list. The tag information is displayed or hidden for all the blocks. When you open additional blocks, the tag information is displayed or hidden depending on the selected setting. Displaying or hiding tag information for an opened block Proceed as follows to display or hide the tag information for an opened block: 1. If you want to display the tag information, select the "Show tag information" option or the "Tag information with hierarchical comments" option in the "Shows the tag information" drop-down list, depending on whether you want to display simple or hierarchical comments. 2. If you want to hide the tag information, select the option "Hide tag information" in the "Shows the tag information" drop-down list. The tag information is displayed or hidden. Branches in LAD Basic information on branches in LAD Definition You use branches to program parallel circuits with the Ladder Logic (LAD) programming language. Branches are inserted in the main rung. You can insert several contacts into the branch and thus achieve a parallel circuit of series connections. This allows you to program complex ladder logic. The figure below shows an example of the use of branches: 1434 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program 6 02725 5 6 6 MOTOR carries signal 1, if one of the following conditions is fulfilled: Signal 1 is pending on S2 or S4 Signal 0 is pending on S5. See also Rules for branches in LAD (Page 1435) Inserting branches into the LAD network (Page 1436) Closing branches in the LAD network (Page 1436) Deleting branches in LAD networks (Page 1437) Rules for branches in LAD Rules The following rules apply to simultaneous branches: A simultaneous branch can only be inserted if the main branch already contains an LAD element. Simultaneous branches are opened downwards or are connected directly to the power rail. They are terminated upwards. Simultaneous branches are opened after the selected LAD element. Simultaneous branches are terminated after the selected LAD element. To delete a simultaneous branch, you must delete all LAD elements of this branch. When the last LAD element is removed from the branch, the rest of the branch is also removed. See also Basic information on branches in LAD (Page 1434) Inserting branches into the LAD network (Page 1436) Deleting branches in LAD networks (Page 1437) Closing branches in the LAD network (Page 1436) WinCC Basic V13.0 System Manual, 02/2014 1435 Programming the PLC 9.1 Creating the user program Inserting branches into the LAD network You can create several branches in a network. Requirement A network is available. The network contains elements. Procedure To insert a new branch in a network, follow these steps: 1. Open the "Instructions" task card. 2. Navigate to "General > Open branches" in the "Simple instructions" palette. 3. Use drag-and-drop to move the element to the desired place in the network. If you want to connect the new branch directly to the power rail, drag the element to the power rail. See also Basic information on branches in LAD (Page 1434) Rules for branches in LAD (Page 1435) Deleting branches in LAD networks (Page 1437) Closing branches in the LAD network Branches must be closed again at suitable places. If necessary, branches will be arranged so that they do not cross each other. Requirement A branch is available. Procedure To close an open branch, follow these steps: 1. Select the open branch. 2. Press and hold down the left mouse button. A dashed line will appear as soon as the cursor is moved. 3. Drag the dashed line to a suitable place on the network. Permissible connections are indicated by green lines. 4. Release the left mouse button. 1436 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program See also Basic information on branches in LAD (Page 1434) Rules for branches in LAD (Page 1435) Deleting branches in LAD networks Requirement A branch is available. Procedure To delete a branch, follow these steps: 1. Select the connection line that links the branch to the main branch. 2. Select the "Delete" command in the shortcut menu. See also Basic information on branches in LAD (Page 1434) Rules for branches in LAD (Page 1435) Inserting branches into the LAD network (Page 1436) Crossings in LAD Basic information on crossings in LAD Definition A crossing is a place in a LAD network where one branch is closed and at the same time another branch is opened. 7DJ,QB 7DJ,QB 7DJ,QB 7DJ,QB 7DJ2XW &URVVLQJ "TagOut" receives signal 1, if the following two conditions are met: "TagIn_1" or "TagIn_3" has signal 1 "TagIn_2" or "TagIn_4" has signal 0 WinCC Basic V13.0 System Manual, 02/2014 1437 Programming the PLC 9.1 Creating the user program Inserting crossings You can insert crossings in a LAD network by creating connections between the main branch and an additional branch or between different branches. Requirements A branch is available. Procedure To insert a new crossing in an LAD network, follow these steps: 1. Open the "Instructions" task card. 2. Navigate to "General > Open branches" in the "Simple instructions" palette. 3. Drag the element behind the existing branch. 4. Insert any element into the open branch. 5. Click the arrow of the open branch after the inserted element. 6. Hold down the left mouse button and drag the dashed connecting line to the main branch. 7. Release the left mouse button. See also Rearranging crossings (Page 1438) Deleting crossings (Page 1439) Inserting branches into the LAD network (Page 1436) Rearranging crossings Requirement A crossing is available. Procedure To rearrange a connection, follow these steps: 1. Select the connection line that defines the crossings in the respective branches. 2. Select the "Delete" command in the shortcut menu. 3. Open the "Instructions" task card. 4. Navigate to "General > Open branches" in the "Simple instructions" palette. 5. Use a drag-and-drop operation to move the element to the place in the network where you want to insert the new crossing. 6. Click on the arrow for the open branch. 1438 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program 7. Hold down the left mouse button and drag the dashed connecting line to the subsidiary branch in which you wish to insert the new crossing. 8. Release the left mouse button. See also Inserting crossings (Page 1438) Deleting crossings (Page 1439) Deleting crossings Requirement A crossing is available. Procedure To delete a crossing, follow these steps: 1. Select the connection line that defines the crossings in the respective branches. 2. Select the "Delete" command in the shortcut menu. See also Inserting crossings (Page 1438) Rearranging crossings (Page 1438) Rungs in LAD Basic information on rungs in LAD Using rungs The program is mapped in one or more networks. A network contains a power rail on the left where one or more rungs originate. The binary signal scans are arranged in the form of contacts on the rungs. The serial arrangement of the elements on a rung creates a series connection; arrangement on simultaneous branches creates a parallel connection. A rung is closed by a coil or a box in which the result of logic operation will be written. The figure below shows an example of the use of several rungs within a network: WinCC Basic V13.0 System Manual, 02/2014 1439 Programming the PLC 9.1 Creating the user program 6WDUW6ZLWFKB/HIW 02725B21 6 6WDUW6ZLWFKB5LJKW 6WRS6ZLWFKB/HIW 02725B21 5 6WRS6ZLWFKB5LJKW Rules Remember the following rules when using several rungs: Connections are not permitted between rungs. Only one jump instruction is permissible per network. The positioning rules for jump instructions remain valid. Running rungs Rungs and networks are executed from top to bottom and from left to right. This means that the first instruction in the first rung of the first network is processed first. All instructions of this rung are then processed. After this come all other rungs of the first network. The next network is processed only after all rungs have first been run. Differences between branches and rungs The difference between branches and rungs is that the rungs are independent branches that can also stand in a different network. Branches, on the other hand, permit the programming of a parallel connection. See also Insert rung (Page 1440) Deleting a rung (Page 1441) Insert rung Requirement A block is open. A network is available. 1440 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program Procedure To insert a new rung in a network, proceed as follows: 1. Insert any coil on the power rail. A new rung will be inserted and the coil positioned at the end of the rung. 2. Insert additional instructions in the new rung. See also Basic information on rungs in LAD (Page 1439) Deleting a rung (Page 1441) Deleting a rung Requirement A rung is available. Procedure To delete a rung, proceed as follows: 1. Hold down the left mouse button and draw a frame around the rung. At the same time, make sure that you select all instructions. Alternatively, you can hold down the <Shift> key and select the first the last instruction of the rung. 2. Right-click on one of the instructions in the rung. 3. Select the "Delete" command in the shortcut menu. See also Basic information on rungs in LAD (Page 1439) Insert rung (Page 1440) Creating FBD programs Basic information on FBD FBD programming language Overview of the Function Block Diagram (FBD) programming language FBD is a graphical programming language. The representation is based on electronic circuit systems. WinCC Basic V13.0 System Manual, 02/2014 1441 Programming the PLC 9.1 Creating the user program The program is mapped in one or more networks. A network contains one or more logic operation paths. The binary signal scans are linked by boxes. The representation of the logic is based on the graphical logic symbols used in Boolean algebra. Example of networks in FBD The following figure shows an FBD network with AND and OR boxes and an assignment: 1HWZRUN 2SHUDQG 2SHUDQG ! 2XWSXW 6WRS Overview of the FBD elements FBD elements An FBD program consists of separate elements that are linked by means of a binary signal flow. Most program elements must be supplied with tags. A FBD network is programmed from left to right. For example, the following figure shows elements of an FBD network: 1) Binary function 2) Standard box 3) Complex box 1442 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program Binary functions You can use binary functions to query binary operands and to combine their signal states. The following operations are examples of binary functions: "AND operation", "OR operation" and "EXCLUSIVE OR operation". Standard boxes: You can use standard boxes to control binary operands, perform RLO edge detection or execute jump functions in the program. Standard boxes generally have only one single input. Complex boxes Complex boxes represent program elements with complex functions. The empty box is an exception. You can use the empty box as a placeholder in which you can select the required instruction. The following types of boxes are available to you in an FBD program: Complex boxes without EN/ENO mechanism: A box is executed independently of the signal state at the box inputs. The error status of the processing cannot be queried. Complex boxes with EN/ENO mechanism: A box is only executed if the enable input "EN" has the signal state "1". If the box is processed correctly, the "ENO" enable output has signal state "1". If an error occurs during processing, the "ENO" output is reset. If the EN enable input is not interconnected, the box is always executed. Calls of code block are also shown in the network as complex boxes with EN/ENO mechanism. Settings for FBD Overview of the settings for FBD Overview The following table shows the settings that you can make: Group Setting Description Font Font size Font size in program editor View Layout Compact or wide Changes the vertical spacing between operands and other objects (such as operand and contact). The change becomes visible once the block is reopened. With absolute information WinCC Basic V13.0 System Manual, 02/2014 Additional display of the absolute addresses 1443 Programming the PLC 9.1 Creating the user program Group Setting Description Operand field Maximum width Maximum number of characters that can be entered horizontally in the operand field. This setting recalculates the layout of the networks. Maximum height Maximum number of characters that can be entered vertically in the operand field. This setting recalculates the layout of the networks. See also Changing the settings (Page 1444) Changing the settings Procedure To change the settings, follow these steps: 1. Select the "Settings" command in the "Options" menu. The "Settings" window is displayed in the work area. 2. In the area navigation, select the "PLC programming" group. 3. Change the settings. Result The change will be loaded directly, there is no need to save it explicitly. See also Overview of the settings for FBD (Page 1443) Working with networks Using networks Function The user program is created in the block within networks. For a code block to be programmed, it must contain at least one network. To achieve a better overview of the user program, you can also subdivide your program into several networks. 1444 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program See also Inserting network title (Page 1448) Entering a network comment (Page 1450) Navigating networks (Page 1450) Inserting networks Requirement A block is open. Procedure To insert a new network, follow these steps: 1. Select the network after which you want to insert a new network. 2. Select the "Insert network" command in the shortcut menu. Result A new empty network is inserted into the block. See also Inserting network title (Page 1448) Entering a network comment (Page 1450) Navigating networks (Page 1450) Selecting networks Requirements A network is available. WinCC Basic V13.0 System Manual, 02/2014 1445 Programming the PLC 9.1 Creating the user program Selecting a network To select a network, follow these steps: 1. Click the title bar of the network that you want to select. Selecting several networks Proceed as follows to select several individual networks: 1. Press and hold down the <Ctrl> key. 2. Click all the networks that you want to select. To select several successive networks, follow these steps: 1. Press and hold down the <Shift> key. 2. Click the first network that you want to select. 3. Click the last network that you want to select. The first and last networks and all those in between are selected. See also Inserting networks (Page 1445) Inserting network title (Page 1448) Entering a network comment (Page 1450) Navigating networks (Page 1450) Copying and pasting networks Copied networks can be pasted within the block or in another block. Networks that were created in LAD or FBD can also be inserted in blocks of the respective other programming language. Requirement A network is available. Procedure To copy and paste a network, follow these steps: 1. Select the network or networks to be copied. 2. Select "Copy" in the shortcut menu. 3. Select the network after which you want to paste in the copied network. 4. Select "Paste" in the shortcut menu. 1446 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program See also Inserting networks (Page 1445) Selecting networks (Page 1445) Inserting network title (Page 1448) Entering a network comment (Page 1450) Navigating networks (Page 1450) Deleting networks Requirement A network is available. Procedure To delete a network, follow these steps: 1. Select the network that you want to delete. 2. Select the "Delete" command in the shortcut menu. See also Inserting networks (Page 1445) Selecting networks (Page 1445) Copying and pasting networks (Page 1446) Inserting network title (Page 1448) Entering a network comment (Page 1450) Navigating networks (Page 1450) Expanding and collapsing networks Requirements A network is available. Opening and closing a network To open a network, follow these steps: 1. Click on the right arrow in the network title bar. To close a network, follow these steps: WinCC Basic V13.0 System Manual, 02/2014 1447 Programming the PLC 9.1 Creating the user program 1. Click on the down arrow in the network title bar. Opening and closing all networks To open and close all networks, follow these steps: 1. In the toolbar, click "Open all networks" or "Close all networks". See also Inserting networks (Page 1445) Selecting networks (Page 1445) Copying and pasting networks (Page 1446) Deleting networks (Page 1447) Inserting network title (Page 1448) Entering a network comment (Page 1450) Navigating networks (Page 1450) Inserting network title The network title is the header of a network. The length of the network title is limited to one line. You can enter the title manually or set it automatically. When you set it automatically, you can do this for individual networks or use the settings to specify that the network title is always set automatically. For automatic insertion of the network title, the comment of the operand in one of the following instructions in the network is evaluated: Assignment Set output Reset output The instruction that is listed first in the network is used. The network title is only inserted automatically when the following conditions are fulfilled: The network does not have a title yet. The operand of the instruction used for the comment has a comment. 1448 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program Note Note the following restrictions for automatic insertion of the network title: The network title is not adapted if you change the comment of the operand at a later time. The network title is not adapted if you change the operand of the instruction. The network title is only set by the writing instructions listed above. If the operand is of the data type array, the comment of the array is used and not the comments of the array elements. Comments of invalid operands are not taken into consideration. Entering the network title manually To enter a network title, follow these steps: 1. Click on the title bar of the network. 2. Enter the network title. Setting the network title automatically To specify that the network titles are always set automatically, follow these steps: 1. Select the "Settings" command in the "Options" menu. The "Settings" window is displayed in the work area. 2. In the area navigation, select the "PLC programming" group. 3. Select the "Set network title automatically" check box in the "Additional settings" group. The network titles are set automatically as of this time if the conditions listed above are fulfilled. To set an individual network title automatically, follow these steps: 1. Right-click "Network <Number of the network>" in the title bar of a network. 2. Select the "Set network title automatically" command in the shortcut menu. The title of the selected network is set based on the comment of the operand if the conditions listed above are fulfilled. See also Using networks (Page 1444) Inserting networks (Page 1445) Selecting networks (Page 1445) Copying and pasting networks (Page 1446) Deleting networks (Page 1447) Expanding and collapsing networks (Page 1447) WinCC Basic V13.0 System Manual, 02/2014 1449 Programming the PLC 9.1 Creating the user program Entering a network comment (Page 1450) Navigating networks (Page 1450) Entering a network comment You can use network comments to provide comments on the program contents of individual networks. For example, you can indicate the function of the network or draw attention to special characteristics. Requirement A network is available. Procedure To enter a network comment, follow these steps: 1. Click on the right arrow before the network title. 2. If the comment area is not visible, click "Network comments on/off" in the toolbar. The comment area is displayed. 3. Click "Comment" in the comment area. The "Comment" text passage is selected. 4. Enter the network comment. See also Using networks (Page 1444) Inserting networks (Page 1445) Selecting networks (Page 1445) Copying and pasting networks (Page 1446) Deleting networks (Page 1447) Expanding and collapsing networks (Page 1447) Inserting network title (Page 1448) Navigating networks (Page 1450) Navigating networks You can navigate straight to a specific position within a block. 1450 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program Procedure To navigate to a specific position within a block, follow these steps: 1. Right-click in the code area of the programming window. 2. Select the "Go to > Network/line" command in the shortcut menu. The "Go to" dialog will open. 3. Enter the network to which you want to navigate. 4. Enter the line number of the network to which you want to navigate. 5. Confirm your entry with "OK". Result The relevant line will be displayed if this is possible. If the network or line requested does not exist, the last existing network or the last existing line in the network requested will be displayed. See also Using networks (Page 1444) Inserting networks (Page 1445) Selecting networks (Page 1445) Copying and pasting networks (Page 1446) Deleting networks (Page 1447) Expanding and collapsing networks (Page 1447) Inserting network title (Page 1448) Entering a network comment (Page 1450) Inserting FBD elements Rules for the use of FBD elements Rules Note the following rules when inserting FBD elements: An FBD network can consist of several elements. All elements of a logic path must be linked to each other according to IEC 61131-3. Standard boxes (flip flops, counters, timers, math operations, etc.) can be added as output to boxes with binary logic operations (for example, AND, OR). Comparison boxes are excluded from this rule. Only Boolean inputs in an instruction can be combined with preceding logic operations. Only the bottom Boolean output in an instruction can be combined with an additional logic operation. WinCC Basic V13.0 System Manual, 02/2014 1451 Programming the PLC 9.1 Creating the user program Enable input EN or enable output ENO can be connected to boxes, but this is not mandatory. Constants (for example, TRUE or FALSE) cannot be assigned to binary logic operations. Instead, use tags of the BOOL data type. Only one jump instruction can be inserted in each network. Only one jump label can be inserted in each network. Instructions for positive or negative RLO edge detection may not be arranged right at the left of the network as this requires a prior logic operation. Placement rules for S7-1200/1500 CPUs The following table sets out the instructions that can only be positioned at the end of the network: Mnemonics Name Instruction Preceding logic operation required SET_BF Set bit field No RESET_BF Reset bit field No JMP Jump if RLO = 1 No JMPN Jump if RLO = 0 Yes JMP_LIST Define jump list No SWITCH Jump distributor No RET Return No Placement rules for S7-300/400 CPUs The following table sets out the instructions that can only be positioned at the end of the network: Instruction 1452 Mnemonic s Name Preceding logic operation required S Set output Yes R Reset output Yes SP Start pulse timer Yes SE Start extended pulse timer Yes SD Start on-delay timer Yes SS Start retentive on-delay timer Yes SF Start off-delay timer Yes SC Set counter value Yes CU Count up Yes CD Count down Yes JMP Jump if RLO = 1 No JMPN Jump if RLO = 0 Yes WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program Mnemonic s Name Instruction Preceding logic operation required RET Return No OPN Open global data block No OPNI Open instance data block No CALL Call block No SAVE Save RLO in BR bit No MCRA Enable MCR range No MCRD Disable MCR range No MCR< Open MCR ranges No MCR> Close MCR ranges No Inserting FBD elements using the "Instructions" task card Requirement A network is available. Procedure To insert FBD elements into a network using the "Instructions" task card, follow these steps: 1. Open the "Instructions" task card. 2. Navigate to the FBD element that you want to insert. 3. Use drag-and-drop to move the element to the desired place in the network. If the element is an internal system function block (FB), the "Call options" dialog opens. In this dialog you can create an instance data block of the single-instance or multiple-instance type for the function block in which the data of the inserted element will be saved. You will find the new instance data block created in the project tree in the "Program resources" folder under "Program blocks > System blocks". If you have selected "multiple instance", these are located in the block interface in the "Static" section. Or: 1. Select the point in the network at which you want to insert the element. 2. Open the "Instructions" task card. 3. Double-click on the element you want to insert. If the element is an internal system function block (FB), the "Call options" dialog opens. In this dialog you can create an instance data block of the single-instance or multiple-instance type for the function block in which the data of the inserted element will be saved. You will find the new instance data block created in the project tree in the "Program resources" folder under "Program blocks > System blocks". If you have selected "multiple instance", these are located in the block interface in the "Static" section. WinCC Basic V13.0 System Manual, 02/2014 1453 Programming the PLC 9.1 Creating the user program Result The selected FBD element is inserted with dummy entries for the parameters. See also Rules for the use of FBD elements (Page 1451) Inserting FBD elements using an empty box Requirement A network is available. Procedure To insert FBD elements into a network using an empty box, follow these steps: 1. Open the "Instructions" task card. 2. Navigate to "General > Empty box" in the "Basic instructions" palette. 3. Use a drag-and-drop operation to move the "Empty box" element to the desired place in the network. 4. Position the cursor over the triangle in the top right-hand corner of the empty box. A drop-down list is displayed. 5. Select the desired FBD element from the drop-down list. If the element is an internal system function block (FB), the "Call options" dialog opens. In this dialog you can create an instance data block of the single-instance or multiple-instance type for the function block in which the data of the inserted element will be saved. You will find the new instance data block created in the project tree in the "Program resources" folder under "Program blocks > System blocks". If you have selected "multi-instance", these are located in the block interface in the "Static" section. Result The empty box is changed to the respective FBD element. Placeholders are inserted for the parameters. Selecting the data type of an FBD element Selecting a data type Introduction Some instructions can be executed with several different data types. If you use one of these instructions in the program, you have to specify a valid data type for the instruction at the 1454 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program specific point in the program. For some instructions, you have to select the data types for the inputs and outputs separately. Note The valid data type (BOOL) for the tags on the enable input EN and the enable output ENO is predefined by the system and cannot be changed. The valid data types for an instruction are listed in the instruction drop-down list. You specify the data type of the instruction by selecting an entry from the drop-down list. If the data type of an operand differs from the data type of the instruction and cannot be converted implicitly, the operand is displayed in red and a rollout with the corresponding error message appears. Data type selection of mathematical instructions Some mathematical instructions provide you with the option of having the data type automatically set corresponding to the data types of the operand. In the drop-down list for data type selection, these instructions have the entry "Auto" in addition to the actual data types. If you select this entry and then allocate the first operand, the data type of the operand is selected as data type for the instruction. The entry in the drop-down list changes to "Auto (<Data type>)", e.g. "Auto (Real)". If you allocate additional operands, the automatically set data type of the instruction is adjusted according to the following criteria: You supply all other operands with tags of the same data type: The data type of the instruction is not changed. You supply all other operands with tags whose data type is smaller than the data type of the instruction: The data type of the instruction is not changed. For the operand with the smaller data type, an implicit conversion is conducted if necessary. You supply an additional operand with a tag whose data type is greater than the data type of the instruction: The data type of the instruction is changed to the larger data type. An implicit conversion is performed, if necessary, for operands that deviate from the newly set data type of the instruction. Each change in the data type of an operand can result in a change of the data type of the instruction. Other operands may possibly be implicitly converted as a result. Operands for which an implicit conversion is performed are marked with a gray square. Note Please also observe the information on data type conversion for your device and, in particular, the notes on the IEC check. See also: Data type conversion See also Defining the data type of an instruction (Page 1456) WinCC Basic V13.0 System Manual, 02/2014 1455 Programming the PLC 9.1 Creating the user program Defining the data type of an instruction Introduction Some instructions can be executed with several different data types. When you insert such instructions into your program, you must specify the data type for these instructions at the actual point in the program. Specifying the data type by means of the drop-down list To define the data type of an instruction using the drop-down list, follow these steps: 1. Insert the instruction at the required point in the program using drag-and-drop. The entry "???" (undefined) is displayed in the drop-down list of the inserted instruction. 2. Click the triangle in the upper corner of the drop-down list. The drop-down list will open to display the data types valid for the instruction. 3. Select a data type from the drop-down list. The selected data type is displayed. 4. If the instruction has two drop-down lists, select the data type for the instruction inputs in the left-hand drop-down list and the data type for the instruction outputs in the right-hand drop-down list. Specifying data type by assigning tags To define the data type of an instruction by assigning tags, follow these steps: 1. Insert the instruction at the required point in the program using drag-and-drop. The entry "???" (undefined) is displayed in the drop-down list of the inserted instruction. 2. At an input or output, specify a valid tag, the data type of which is to be applied as the instruction data type. The data type of the tag is displayed in the drop-down list. 3. Enter a valid tag at an input and a valid tag at an output if data types need to be defined for both the inputs and outputs of the instruction. The tag specified at the input determines the data type of the inputs; the tag specified at the output determines the data type of the outputs of the instruction. Automatically specifying the data type of mathematical instructions To automatically specify the data type for mathematical instructions, follow these steps: 1. Insert the mathematical instruction at the required point in the program using drag-and-drop. The entry "???" (undefined) is displayed in the drop-down list of the inserted instruction. 2. Select the "Auto" entry from the drop-down list. 3. Enter a valid tag at an input or output. The data type of the tag is applied as data type of the instruction. The entry in the dropdown list changes to "Auto (<Data type>)". See also: Selecting a data type (Page 1454) 1456 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program See also Selecting a data type (Page 1454) Using favorites in FBD Adding FBD elements to Favorites Requirement A block is open. The multipane mode is set for the "Instructions" task card or the Favorites are also displayed in the editor. Procedure To add SCL instructions to the Favorites, follow these steps: 1. Open the "Instructions" task card. 2. Maximize the "Basic instructions" pane. 3. Navigate in the "Basic instructions" pane to the instruction that you want to add to the Favorites. 4. Drag-and-drop the instruction into the "Favorites" pane or into the Favorites area in the program editor. Note To additionally display the Favorites in the program editor, click the "Display favorites in the editor" button in the program editor toolbar. See also Removing FBD elements from Favorites (Page 1458) Overview of the program editor (Page 1354) Inserting FBD elements using favorites Requirement A block is open. Favorites are available. WinCC Basic V13.0 System Manual, 02/2014 1457 Programming the PLC 9.1 Creating the user program Procedure To insert an instruction into a program using Favorites, follow these steps: 1. Drag-and-drop the desired instruction from Favorites to the desired position. Or: 1. Select the position in the program where you want to insert the instruction. 2. In the Favorites, click on the instruction you want to insert. Note To additionally display the Favorites in the program editor, click the "Display favorites in the editor" button in the program editor toolbar. See also Overview of the program editor (Page 1354) Removing FBD elements from Favorites (Page 1458) Removing FBD elements from Favorites Requirement A code block is open. Procedure To remove instructions from Favorites, follow these steps: 1. Right-click on the instruction you want to remove. 2. Select the "Remove instruction" command in the shortcut menu. Note To additionally display the Favorites in the program editor, click the "Display favorites in the editor" button in the program editor toolbar. See also Adding FBD elements to Favorites (Page 1457) Inserting FBD elements using favorites (Page 1457) Overview of the program editor (Page 1354) 1458 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program Inserting block calls in FBD Inserting block calls using a drag-and-drop operation You can insert calls for existing functions (FC) and function blocks (FB) using a drag-and-drop operation from the project tree. If you call function blocks from other function blocks, you can either call them as single-instance or multi-instance blocks. If a function block is called as single instance, it will store its data in a data block of its own. If a function block is called as multiinstance, it will store its data in the instance data block of the calling function block. Requirement A network is available. The block that is to be called is available. Inserting a call of a function (FC) To insert a call of a function (FC) into a network using a drag-and-drop operation, follow these steps: 1. Drag the function from the project tree to the required network. Inserting a call for a function block (FB) To insert a call for a function block (FB), follow these steps: 1. Drag the function block from the project tree to the required network. The "Call options" dialog opens. 2. Enter in the dialog whether you wish to call the block as single or multi-instance. - If you click on the "Single instance" button, you will have to enter a name in the "Name" text box for the data block that you want to assign to the function block. - If you click on the "Multi-instance" button, you will have to enter the name of the tag in the "Name in the interface" text box; this is the name that you use to enter the called function block as a static tag in the interface of the calling block. 3. Confirm your entries with "OK". Result The function or the function block is inserted with its parameters. You can then assign the parameters. See also: Auto-Hotspot Note If when calling a function block you specify an instance data block that does not exist, it will be created. If you have called a function block as a multi-instance, this will be entered as a static tag in the interface. WinCC Basic V13.0 System Manual, 02/2014 1459 Programming the PLC 9.1 Creating the user program See also Updating block calls in FBD (Page 1460) Changing the instance type (Page 1461) Single instances (Page 1159) Multi-instances (Page 1159) Updating block calls in FBD If interface parameters of a called block are changed, the block call can no longer be executed correctly. You can avoid such inconsistent block calls by updating the block calls. You have two options to update the block calls: Explicit updating in the program editor. The block calls in the open block will be updated. Implicit updating during compilation. All block calls in the program as well as the used PLC data types will be updated. Update blocks in the program editor To update a block call within a block, follow these steps: 1. Open the block in the program editor. 2. Click "Update inconsistent block calls" in the toolbar. Or: 1. Open the block in the program editor. 2. Right-click on the instruction with the block call. 3. Select the "Update" command in the shortcut menu. The "Interface update" dialog opens. This dialog shows the differences between the block interface in use and the changed interface of the called block. 4. If you want to update the block call, click "OK". To cancel the update, click "Cancel". Update block calls during compilation Follow these steps to update all block calls and uses of PLC data types during compilation implicitly: 1. Open the project tree. 2. Select the "Program blocks" folder. 3. Select the command "Compile > Software (rebuild all blocks)" in the shortcut menu. 1460 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program See also Inserting block calls using a drag-and-drop operation (Page 1459) Changing the instance type (Page 1461) Changing the instance type Instance type There are two ways of calling function blocks: As a single instance As a multiple instance See also: Auto-Hotspot You can modify a defined instance type at any time. Requirement The user program contains a block call. Procedure To change the instance type of a function block, follow these steps: 1. Open the code block and select the block call. 2. Select the "Change instance" command in the shortcut menu. The "Call options" dialog opens. 3. Click the "Single instance" or "Multi instance" button. - If you select the "Single instance" instance type, enter a name for the data block that is to be assigned to the function block. - If you select "Multiple instance" as the instance type, enter in the "Name in the interface" text field the name of the tag with which the called function block is to be entered as a static tag in the interface of the calling block. 4. Confirm your entries with "OK". Note The previous single and multiple instances will not be deleted automatically. See also Inserting block calls using a drag-and-drop operation (Page 1459) Updating block calls in FBD (Page 1460) WinCC Basic V13.0 System Manual, 02/2014 1461 Programming the PLC 9.1 Creating the user program Inserting complex FBD instructions Using the "Calculate" instruction Requirement A network is available. Procedure Proceed as follows to use the "Calculate" instruction: 1. Open the "Instructions" task card. 2. Navigate to "Math functions > CALCULATE" in the "Basic instructions" pane. 3. Use drag-and-drop to move the element to the desired place in the network. The instruction "Calculate" will be inserted for the data type with a placeholder expression and question mark. 4. Enter the data type for the calculation. 5. Enter the operands for the calculation. Note The calculation is run with the inputs of the "Calculate" instruction. If you want to use constants you must also insert appropriate inputs for them. 6. Click on the "Edit 'Calculate' instruction" button to replace the placeholder expression with the correct expression. The "Edit 'Calculate' instruction" dialog will open. 7. Enter the required expression in the "OUT:= " text box. Note In the "Example" area you can find an example of a valid expression and possible instructions that you can use. To determine a value with the help of Pythagoras' theorem, for example, enter "OUT := SQRT (SQR (IN1) + SQR (IN2))". 8. Confirm your entry with "OK". See also CALCULATE: Calculate (Page 2123) 1462 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program Using free-form comments Basic information on using free comments in FBD Introduction Free-form comments allow you to add comments to the source code for graphic programming languages similar to line comments for textual languages. Free-form comments can be used for all non-binary boxes. See also Inserting free-form comments (Page 1463) Editing free-form comments (Page 1464) Deleting free-form comments (Page 1465) Inserting free-form comments Requirement A network with instructions is available. Procedure To insert a free comment on an instruction, proceed as follows: 1. If necessary, activate the "Free-form comments on/off" button in the toolbar. 2. Right-click on the instruction for which you want to insert a free-form comment. 3. Select the "Insert comment" command in the shortcut menu. A comment box with a standard comment opens. The comment box is connected by an arrow to the corresponding instruction. 4. Enter the required comment in the comment box. See also Basic information on using free comments in FBD (Page 1463) Editing free-form comments (Page 1464) Deleting free-form comments (Page 1465) WinCC Basic V13.0 System Manual, 02/2014 1463 Programming the PLC 9.1 Creating the user program Editing free-form comments Introduction Free-form comments can be edited as follows: Changing the comment text Changing the position and size of the comment box Attaching a comment to another element Showing and hiding free comments Changing the comment text To change the text of free-form comments, follow these steps: 1. Click on the comment box. 2. Enter the desired text. Changing the position of the comment box To change the positioning of the comment box, follow the steps below: 1. Left-click the comment box and keep the mouse button pressed. 2. Drag the comment box to the desired location. Changing the size of the comment box To change the size of the comment box, follow the steps below: 1. Click on the comment box. 2. Drag the comment box on the move handle in the lower right corner to the desired size. Attaching a comment to another element To attach a free-form comment to another element, follow these steps: 1. Left-click the point of the arrow that links the comment box with the instruction and keep the mouse button pressed. 2. Drag the arrow to the element to which you want to attach the comment. Possible insertion points are marked with a green square. 3. Release the mouse button. 1464 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program Showing and hiding free comments To show or hide a free-form comments, follow these steps: 1. Click the "Free-form comment on/off" button in the toolbar. See also Basic information on using free comments in FBD (Page 1463) Inserting free-form comments (Page 1463) Deleting free-form comments (Page 1465) Deleting free-form comments Procedure To delete a free-form comment, proceed as follows: 1. Right-click on the free-form comment that you want to delete. 2. Select the "Delete" command in the shortcut menu. See also Basic information on using free comments in FBD (Page 1463) Inserting free-form comments (Page 1463) Editing free-form comments (Page 1464) Editing FBD elements Selecting FBD elements You can select several individual elements or all elements in a network. Requirement FBD elements are available Selecting several individual FBD elements To select several individual FBD elements, follow these steps: 1. Press and hold down the <Ctrl> key. 2. Click on all the FBD elements you wish to select. 3. Now release the <Ctrl> key. WinCC Basic V13.0 System Manual, 02/2014 1465 Programming the PLC 9.1 Creating the user program Selecting all FBD elements in a network To select all FBD elements in a network, follow these steps: 1. Go to the network whose elements you wish to select. 2. Select the "Select all" command in the "Edit" menu or press <Ctrl+A>. See also Copying FBD elements (Page 1466) Cutting FBD elements (Page 1467) Pasting an FBD element from the clipboard (Page 1467) Replacing FBD elements (Page 1468) Adding additional inputs and outputs to FBD elements (Page 1469) Removing instruction inputs and outputs (Page 1470) Enabling and disabling the EN/ENO mechanism (Page 1471) Deleting FBD elements (Page 1472) Copying FBD elements Requirement An FBD element is available. Procedure To copy an FBD element, follow these steps: 1. Right-click the FBD element that you want to copy. 2. Select "Copy" in the shortcut menu. Result The FBD element will be copied and saved to the clipboard. See also Selecting FBD elements (Page 1465) Cutting FBD elements (Page 1467) Pasting an FBD element from the clipboard (Page 1467) Replacing FBD elements (Page 1468) Adding additional inputs and outputs to FBD elements (Page 1469) Removing instruction inputs and outputs (Page 1470) 1466 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program Enabling and disabling the EN/ENO mechanism (Page 1471) Deleting FBD elements (Page 1472) Cutting FBD elements Requirement An FBD element is available. Cutting To cut an FBD element, follow these steps: 1. Right-click the FBD element that you want to cut. 2. Select "Cut" in the shortcut menu. Result The FBD element will be cut and saved to the clipboard. See also Selecting FBD elements (Page 1465) Copying FBD elements (Page 1466) Pasting an FBD element from the clipboard (Page 1467) Replacing FBD elements (Page 1468) Adding additional inputs and outputs to FBD elements (Page 1469) Removing instruction inputs and outputs (Page 1470) Enabling and disabling the EN/ENO mechanism (Page 1471) Deleting FBD elements (Page 1472) Pasting an FBD element from the clipboard Requirement An FBD element is available. WinCC Basic V13.0 System Manual, 02/2014 1467 Programming the PLC 9.1 Creating the user program Procedure To paste an FBD element from the clipboard, follow these steps: 1. Copy an FBD element or cut an FBD element. 2. Right-click the point in the network where you want to paste the element. 3. Select "Paste" in the shortcut menu. See also Selecting FBD elements (Page 1465) Copying FBD elements (Page 1466) Cutting FBD elements (Page 1467) Replacing FBD elements (Page 1468) Adding additional inputs and outputs to FBD elements (Page 1469) Removing instruction inputs and outputs (Page 1470) Enabling and disabling the EN/ENO mechanism (Page 1471) Deleting FBD elements (Page 1472) Replacing FBD elements You can easily exchange FBD elements with other FBD elements of the same type. This has the advantage that the parameters are retained and need not be entered again. For example, you can exchange OR and AND, RS-FlipFlop and SR-FlipFlop, comparison functions or jump instructions. Requirements A network with at least one FBD element is present. Procedure To replace an FBD element with another FBD element, follow these steps: 1. Select the FBD element that you want to replace. If elements compatible with the selected FBD element are available, a triangle will appear in the upper right-hand corner of the element. 2. Position the cursor above the triangle of the FBD element. A drop-down list is displayed. 3. From the drop-down list, select the FBD element that you want to use to replace the existing FBD element. 1468 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program See also Selecting FBD elements (Page 1465) Copying FBD elements (Page 1466) Cutting FBD elements (Page 1467) Pasting an FBD element from the clipboard (Page 1467) Adding additional inputs and outputs to FBD elements (Page 1469) Removing instruction inputs and outputs (Page 1470) Enabling and disabling the EN/ENO mechanism (Page 1471) Deleting FBD elements (Page 1472) Adding additional inputs and outputs to FBD elements Introduction You can expand several FBD elements with additional inputs that execute arithmetic or binary operations. Such elements are, for example, the instructions "Add" (ADD), "Multiply" (MUL), AND or OR. You can expand the "MOVE value" (MOVE) and "Demultiplex" (DEMUX) instruction boxes by adding additional outputs. The name of the new inputs and outputs is comprised of the type of inserted element and a consecutive number. The name of a new input is may be "IN2"; the name of a new output may be "OUT2". Requirements An FBD element is available that permits the insertion of additional inputs and outputs. Inserting an additional input To add an additional input to the box of an FBD element, follow these steps: 1. Right-click on an existing input of the FBD element. 2. Select "Insert input" in the shortcut menu. An additional input is added to the box of the FBD element. Or: 1. Click on the yellow star symbol beside the last input in the instruction box. An additional input is added to the box of the FBD element. Inserting an additional output To add an additional output to the box of an FBD element, follow these steps: 1. Right-click on an existing output of the FBD element. 2. Select "Insert output" from the shortcut menu. An additional output is added to the box of the FBD element. WinCC Basic V13.0 System Manual, 02/2014 1469 Programming the PLC 9.1 Creating the user program Or: 1. Click on the yellow star symbol beside the last output of the instruction box. An additional output is added to the box of the FBD element. See also Selecting FBD elements (Page 1465) Copying FBD elements (Page 1466) Cutting FBD elements (Page 1467) Pasting an FBD element from the clipboard (Page 1467) Replacing FBD elements (Page 1468) Removing instruction inputs and outputs (Page 1470) Enabling and disabling the EN/ENO mechanism (Page 1471) Deleting FBD elements (Page 1472) Removing instruction inputs and outputs Introduction Inputs and outputs which you have added to an instruction can be removed. Requirement An FBD element is available, which you have expanded with additional inputs or outputs. Remove input To remove an input, follow these steps: 1. Select the input that you want to remove. 2. Select the "Delete" command in the shortcut menu. The input of the FBD element is removed. Remove output To remove an output, follow these steps: 1. Select the output that you want to remove. 2. Select the "Delete" command in the shortcut menu. The output of the FBD element will be removed. 1470 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program See also Selecting FBD elements (Page 1465) Copying FBD elements (Page 1466) Cutting FBD elements (Page 1467) Pasting an FBD element from the clipboard (Page 1467) Replacing FBD elements (Page 1468) Adding additional inputs and outputs to FBD elements (Page 1469) Enabling and disabling the EN/ENO mechanism (Page 1471) Deleting FBD elements (Page 1472) Enabling and disabling the EN/ENO mechanism In LAD and FBD, certain instructions have an enable output ENO and thus use the EN/ENO mechanism. This allows you to query runtime errors in instructions and react to them. In order to increase the performance of the CPU, the EN/ENO mechanism is disabled in the default setting. This means that you are not initially able to react to runtime errors of the instruction using the ENO value. However, you can enable the EN/ENO mechanism again at any time, if required. You can enable the EN/ENO mechanism individually for each instruction in order to generate the ENO. If you enable the EN/ENO mechanism for an instruction, other instructions that you subsequently add to your program are also inserted with the EN/ENO mechanism enabled. You can disable the EN/ENO mechanism again at any time if you do not want to use the evaluation of ENO for an instruction. Further instructions that you subsequently add to your program will then be inserted without the EN/ENO mechanism. See also: Basics of the EN/ENO mechanism (Page 1299) Activating the EN/ENO mechanism Proceed as follows to activate the EN/ENO mechanism of an instruction: 1. In your program, right-click the instruction at which you want to activate the EN/ENO mechanism. 2. Select the "Generate ENO" command from the shortcut menu. The ENO value is again generated for the instruction. Other instructions are inserted with the enable output. Deactivating the EN/ENO mechanism Proceed as follows to deactivate the EN/ENO mechanism of an instruction: 1. In your program, right-click the instruction at which you want to deactivate the EN/ENO mechanism. 2. Select the "Do not generate ENO" command from the shortcut menu. The ENO value is no longer generated for the instruction. Other instructions are inserted without enable output. WinCC Basic V13.0 System Manual, 02/2014 1471 Programming the PLC 9.1 Creating the user program See also Selecting FBD elements (Page 1465) Copying FBD elements (Page 1466) Cutting FBD elements (Page 1467) Pasting an FBD element from the clipboard (Page 1467) Replacing FBD elements (Page 1468) Adding additional inputs and outputs to FBD elements (Page 1469) Removing instruction inputs and outputs (Page 1470) Deleting FBD elements (Page 1472) Deleting FBD elements Requirement An FBD element is available. Procedure To delete an FBD element, follow these steps: 1. Right-click the FBD element that you want to delete. 2. Select the "Delete" command in the shortcut menu. See also Selecting FBD elements (Page 1465) Copying FBD elements (Page 1466) Cutting FBD elements (Page 1467) Pasting an FBD element from the clipboard (Page 1467) Replacing FBD elements (Page 1468) Adding additional inputs and outputs to FBD elements (Page 1469) Removing instruction inputs and outputs (Page 1470) Enabling and disabling the EN/ENO mechanism (Page 1471) Inserting operands in FBD instructions Inserting operands The character strings "<???>", "<??.?>" and "..." are inserted as placeholders for the parameters when a FBD element is inserted. The "<???>" and "<??.?>" strings displayed in 1472 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program red indicate parameters that need to be connected. The "..." string displayed in black indicates parameters that may be connected. "<??.?>" stands for Boolean placeholders. Note To display the available data types in a tooltip, move the cursor over the placeholder. Requirement An FBD element is available. Procedure To connect the parameters of an FBD element, follow these steps: 1. Click the placeholder of the parameter. An input field is opened. 2. Enter the corresponding parameters, for example a PLC tag, a local tag or a constant. Note If you enter the absolute address of a parameter that has already been defined, this absolute address will be changed to the symbolic name of the parameter as soon as the input is confirmed. If you have not yet defined the parameter, a new tag with this absolute address and the default name "Tag_1" will be entered in the PLC tag table. When you confirm your input, the absolute address will be replaced with the symbolic name "Tag_1". 3. Confirm the parameter with the Enter key. 4. If you have not yet defined the parameter, you can define it directly in the program editor using the shortcut menu. See also: "Declaring PLC tags in the program editor (Page 1314)". Or drag from it the PLC tag table: 1. In the project tree, select the "PLC tags" folder and open the PLC tag table. 2. If you have opened the PLC tag table, drag the desired tag to the corresponding location in your program. If you have not opened the PLC tag table yet, open the detail view now. Drag the desired tag from the detail view to the appropriate place in your program. Or drag from it the block interface: 1. Open the block interface. 2. Drag the desired operand from the block interface to the corresponding location in your program. WinCC Basic V13.0 System Manual, 02/2014 1473 Programming the PLC 9.1 Creating the user program Result If the syntax is error-free, the displayed parameter is black. If there is an error in the syntax, the cursor stays in the input field and a corresponding error message is displayed in the inspector window in the "Info > Syntax" register. Wiring hidden parameters Introduction Depending on the CPU used, you can use complex instructions in your program that are dispatched with the TIA portal. These instructions can contain parameters that are declared as hidden. If an instruction contains hidden parameters, the instruction box has a small arrow on the lower edge. You can recognize hidden parameters by their white font. You can show and wire the hidden parameters at any time. Showing or hiding hidden parameters To show or hide hidden parameters, follow these steps: 1. Click on the down arrow at the bottom edge of the instruction box to show hidden parameters. 2. Click on the up arrow at the bottom edge of the instruction box to hide hidden parameters. Wiring hidden parameters To wire parameters, follow these steps: 1. Wire the hidden parameters like normally visible parameters. The hidden parameter is transformed into a visible parameter. See also Using libraries (Page 325) Displaying or hiding variable information Introduction You can display the following information about the tags to be used in the Program editor: Name of the tag Address of the tag Simple or hierarchical comments for tag documentation 1474 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program The information is taken from the block interface for local tags and DB tags and from the PLC tag table for tags that are valid CPU-wide. You can display the tag information either for all the blocks or for individually opened blocks. If you display the tag information for all the blocks, the tag information for all the blocks currently opened and opened in future is shown. You can hide the tag information at any time again. If you have hidden the tag information for all blocks, you can display it again for individual blocks that are open. When you select the display of tag information with hierarchical comments, the comments of the higher structure levels are also displayed for structured tags. The comments are shown in brackets after the tag comment; the comments of the individual levels are separated by a dot. If there is no comment for a tag on a structure level, it is not displayed. This is indicated by two successive dots. Displaying or hiding tag information for all the blocks Proceed as follows to display or hide the tag information for all the blocks: 1. Select the "Settings" command in the "Options" menu. The "Settings" window is displayed in the work area. 2. In the area navigation, select the "PLC programming" group. 3. If you want to display the tag information, select the "Show" option or the "Tag information with hierarchical comments" option in the drop-down list, depending on whether you want to display simple or hierarchical comments. 4. If you want to hide the tag information, select the option "Collapse" in the "Tag information" drop-down list. The tag information is displayed or hidden for all the blocks. When you open additional blocks, the tag information is displayed or hidden depending on the selected setting. Displaying or hiding tag information for an opened block Proceed as follows to display or hide the tag information for an opened block: 1. If you want to display the tag information, select the "Show tag information" option or the "Tag information with hierarchical comments" option in the "Shows the tag information" drop-down list, depending on whether you want to display simple or hierarchical comments. 2. If you want to hide the tag information, select the option "Hide tag information" in the "Shows the tag information" drop-down list. The tag information is displayed or hidden. WinCC Basic V13.0 System Manual, 02/2014 1475 Programming the PLC 9.1 Creating the user program Branches in FBD Basic information on branches in FBD Definition You can use the Function Block Diagram (FBD) programming language to program parallel branches. This is done using branches that are inserted between the boxes. You can insert additional boxes within the branch and in this way build up complex function block diagrams. The figure below shows an example of the use of branches: 6 6 6 ! /()7 5 5,*+7 6 See also Rules for branches in FBD (Page 1476) Inserting branches in FBD networks (Page 1477) Deleting branches in FBD networks (Page 1477) Rules for branches in FBD Rules The following rules apply to the use of branches in FBD: Branches are opened downward. Branches can be inserted only between FBD elements. To delete a branch, you must delete all FBD elements, including the branch itself. If you delete the connection between two branches, the FBD elements of the interrupted branch will be positioned freely in the network. See also Basic information on branches in FBD (Page 1476) Inserting branches in FBD networks (Page 1477) Deleting branches in FBD networks (Page 1477) 1476 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program Inserting branches in FBD networks Requirement A network is available. Procedure To insert a new branch in a network, follow these steps: 1. Open the "Instructions" task card. 2. Navigate to "General > Branch" in the "Basic instructions" palette. 3. Drag the element from the "Elements" pane to the a required location on a connection line between two boxes. See also Rules for branches in FBD (Page 1476) Basic information on branches in FBD (Page 1476) Deleting branches in FBD networks (Page 1477) Deleting branches in FBD networks Requirement A branch is available. Procedure To delete a branch, follow these steps: 1. Select the connection line that links the branch to the main branch. 2. Select the "Delete" command in the shortcut menu. Result The branch is now deleted. Boxes connected to the deleted branch are placed freely within the network. See also Rules for branches in FBD (Page 1476) Basic information on branches in FBD (Page 1476) Inserting branches in FBD networks (Page 1477) WinCC Basic V13.0 System Manual, 02/2014 1477 Programming the PLC 9.1 Creating the user program Logic paths in FBD Basic information on logic paths in FBD Use of logic paths The user program will be mapped in one or more networks. The networks can contain one or more logic paths on which the binary signals are arranged in the form of boxes. The following figure shows an example of the use of several logic paths within a network: 6WDUW6ZLWFKB/HIW ! 02725B21 6 6WDUW6ZLWFKB5LJKW 6WRS6ZLWFKB/HIW ! 02725B21 6WRS6ZLWFKB5LJKW 5 Rules Remember the following rules when using logic paths: Connections are not permitted between logic paths. Only one jump instruction is permissible per network. The positioning rules for jump instructions remain valid. Executing logic paths Logic paths are executed from top to bottom and from left to right. This means that the first instruction in the first logic path of the first network is executed first. All instructions of this logic path are then executed. After this come all other logic paths of the first network. The next network is executed only after all logic paths have first been executed. When jumps are used the regular execution of the logic paths is circumvented and the instruction is executed at the jump destination. Differences between branches and logic paths The difference between branches and logic paths is that the logic paths are independent branches that can also stand in a different network. Branches, on the other hand, permit the programming of a parallel connection and have a common preceding logic operation. See also Inserting a logic path (Page 1479) Deleting a logic operation path (Page 1479) 1478 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program Inserting a logic path Requirement A block is open. A network is available. Procedure To insert a new logic path in a network, follow these steps: 1. Insert any instruction in a network in such a way that it has no connection to existing instructions. A new logic path is inserted. 2. Insert an assignment at the end of the new logic path. 3. Insert additional instructions in the new logic path. See also Basic information on logic paths in FBD (Page 1478) Deleting a logic operation path (Page 1479) Deleting a logic operation path Requirement A logic path is available. Procedure To delete a logic path, proceed as follows: 1. Hold down the left mouse button and draw a frame around the logic path. At the same time, make sure that you select all instructions of the logic path. Alternatively, you can hold down the <Shift> key and select the first the last instruction of the logic path. 2. Right-click on one of the instructions in the logic path. 3. Select the "Delete" command in the shortcut menu. See also Basic information on logic paths in FBD (Page 1478) Inserting a logic path (Page 1479) WinCC Basic V13.0 System Manual, 02/2014 1479 Programming the PLC 9.1 Creating the user program Creating SCL programs Basics of SCL Programming language SCL Programming language SCL SCL (Structured Control Language) is a high-level programming language based on PASCAL. The language is based on DIN EN 61131-3 (international IEC 1131-3). The standard standardizes programming languages for programmable logic controllers. The SCL programming language fulfills the PLCopen Basis Level of ST language (Structured Text) defined in this standard. Language elements SCL also contains higher programming languages in addition to the typical elements of the PLC, such as inputs, outputs, timers or memory bits. Expressions Value assignments Operators Program control SCL provides convenient instructions for controlling the program allowing you, for example, to create program branches, loops or jumps. Application SCL is therefore particularly suitable for the following areas of application: Data management Process optimization Recipe management Mathematical / statistical tasks Expressions Description Expressions are calculated during the runtime of the program and return a value. An expression consists of operands (such as constants, tags or function calls) and optionally out of operators (such as *, /, + or -). Expressions can be linked together or nested within each other by operators. 1480 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program Evaluation order The evaluation of the expression occurs in a specific order that is defined by the following factors: Priority of the operators involved Left-to-right order Brackets Types of expressions The following expression types are available depending on the operator: Arithmetic expressions Arithmetic expressions consist of either a numerical value or combine two values or expressions with arithmetic operators. Relational expressions Relational expressions compare the values of two operands and yield a Boolean value. The result is TRUE if the comparison is true, and FALSE if it is not met. Logical expressions Logical expressions combine two operands with logical operators (AND, OR, XOR) or negating operands (NOT). How expressions are used You can use the result of an expression in different ways: As a value assignment for a tag As as a condition for a control instruction As a parameter for a calling a block or instruction See also Operators and operator precedence (Page 1486) Arithmetic expressions (Page 1481) Relational expressions (Page 1484) Logical expressions (Page 1485) Arithmetic expressions Description Arithmetic expressions consist of either a numerical value or combine two values or expressions with arithmetic operators. WinCC Basic V13.0 System Manual, 02/2014 1481 Programming the PLC 9.1 Creating the user program Arithmetic operators can process the data types that are allowed in the CPU in use. If two operands are involved in the operation, the data type of the result is determined based on the following criteria: If both operands are integers with sign and have different lengths, the result receives the data type of the longer integer (e. g. INT + DINT = DINT). If both operands are integers without sign and have different lengths, the result receives the data type of the longer integer (e. g. USINT + UDINT = UDINT). If one operand is an integer with sign and the other integer is an operand without sign, the result receives the next larger data type with sign that covers the integer without sign (e. g. SINT + USINT = INT). You can only execute an operation with such operands if the IEC check is not set. If one operand is an integer and the other operand is a floating-point number, the result receives the data type of the floating-point number (e. g. INT + REAL = REAL). If both operands are floating-point numbers and have different lengths, the result receives the data type of the longer floating-point number (e. g. REAL + LREAL = LREAL). The data type of the result of an operation that involves operands of the data type groups "Times" and "Date and time" can be found in the table in section "Data types of arithmetic expressions". You cannot use data types of the data type groups "Times" and "Date and time" when the IEC check is set. Data types of arithmetic expressions The following table shows the data types you can use in arithmetic expressions: Operation Operator 1st Operand 2nd Operand Result Power ** Integer/floating-point number Integer/floating-point number Integer/floating-point number Unary plus + Integer/floating-point number - Integer/floating-point number TIME, LTIME Unary minus - Multiplication * Division / Modulo function MOD Addition + Integer/floating-point number TIME, LTIME - TIME, LTIME 1482 Integer/floating-point number TIME, LTIME Integer/floating-point number Integer/floating-point number Integer/floating-point number TIME, LTIME Integer TIME, LTIME Integer/floating-point number Integer/floating-point number (not equal 0) Integer/floating-point number TIME, LTIME Integer TIME, LTIME Integer Integer Integer Integer/floating-point number Integer/floating-point number Integer/floating-point number TIME TIME TIME TIME DINT TIME WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program Operation Operator 1st Operand 2nd Operand Result LTIME TIME, LTIME LTIME LTIME LINT LTIME TOD TIME TOD TOD DINT TOD LTOD TIME, LTIME LTOD LTOD LINT LTOD DATE LTOD DTL DATE TOD S7-300/400: DT S7-1200/1500: DTL Subtraction - DT TIME DT LDT TIME, LTIME LDT DTL TIME, LTIME DTL Integer/floating-point number Integer/floating-point number Integer/floating-point number TIME TIME TIME DINT TIME TIME LTIME TIME, LTIME LTIME LTIME LINT LTIME TOD TIME TOD DINT TOD LTOD TIME, LTIME LTOD LTOD LINT LTOD DATE DATE S7-300/400/1200: TIME 1) S7-1500: LTIME DT TIME DT LDT TIME, LTIME LDT DTL TIME, LTIME DTL DTL DTL S7-1200: TIME S7-1500: LTIME 1) Combinations between nanoseconds and milliseconds are not possible within expressions. For additional information on valid data types, refer to "See also". Example The following example shows an arithmetic expression: SCL "MyTag1":= "MyTag2" * "MyTag3"; WinCC Basic V13.0 System Manual, 02/2014 1483 Programming the PLC 9.1 Creating the user program See also Expressions (Page 1480) Operators and operator precedence (Page 1486) Relational expressions Description Relational expressions compare the values of two operands and yield a Boolean value. The result is TRUE if the comparison is true, and FALSE if it is not met. Relational operators can process the data types that are allowed in the CPU in use. The data type of the result always is BOOL. Note the following rules when forming relational expressions: All tags are comparable within the following data type groups: - Integers/floating-point numbers - Binary numbers - String With the following data types/data groups, only tags of the same type can be compared: - TIME, LTIME - Date and time The comparison of strings is based on the ASCII character set. The length of the tags and the numerical value of each ASCII character are used for the comparison. S5TIME tags are not permitted as comparison operands. An explicit conversion from S5TIME to TIME or LTIME is necessary. Data types of relational expressions The following table shows the data types/data type groups you can use in relational expressions: Operation Operator 1st Operand 2nd Operand Result Compare for equal, not equal =, <> Integer/floatingpoint number Integer/floatingpoint number BOOL Binary number Binary number BOOL String String BOOL TIME, LTIME TIME, LTIME BOOL Date and time Date and time BOOL Integer/floatingpoint number Integer/floatingpoint number BOOL Bit strings Bit strings BOOL (S7-1200/1500 only) (S7-1200/1500 only) Compare for less than, less thanequal to, greater than, greater than or equal to 1484 <, <=, >, >= WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program Operation Operator 1st Operand 2nd Operand Result String String BOOL TIME, LTIME TIME, LTIME BOOL Date and time Date and time BOOL For additional information on valid data types, refer to "See also". Example The following example shows a relational expression: SCL IF a > b THEN c:= a; IF A > 20 AND B < 20 THEN C:= TRUE; IF A<>(B AND C) THEN C:= FALSE; Note The comparison for STRING and DT are executed internally in the S7-300/400 by extended instructions. The following operands are not permitted for these functions: Parameter of a FC In-out parameter of an FB of type STRUCT or ARRAY See also Expressions (Page 1480) Operators and operator precedence (Page 1486) Logical expressions Description Logical expressions combine two operands with logical operators AND OR XOR or negating operands NOT. Logical operators can process the data types that are allowed in the CPU in use. The result of a logical expression is of BOOL data type, if both operands are of BOOL data type. If at least one of both operands is a bit string, then the result is also a bit string and is determined by the type of the highest operand. For example, when you link a BYTE type operand to a WORD type operand, the result is type WORD. To link a BOOL type operand with a bit string, you must first explicitly convert it to a bit string. WinCC Basic V13.0 System Manual, 02/2014 1485 Programming the PLC 9.1 Creating the user program Data types of logical expressions The following table shows the data types you can use in logical expressions: Operation Operator 1st Operand 2nd Operand Result Negation NOT BOOL - BOOL AND logic operation AND or & BOOL BOOL BOOL Bit string Bit string Bit string BOOL BOOL BOOL Bit string Bit string Bit string BOOL BOOL BOOL Bit string Bit string Bit string OR logic operation OR EXCLUSIVE OR logic operation XOR Example The following example shows a logical expression: SCL IF "MyTag1" AND NOT "MyTag2" THEN c:=a; MyTag:=ALPHA OR BETA; See also Expressions (Page 1480) Operators and operator precedence (Page 1486) Operators and operator precedence Operators and their order of evaluation Expressions can be linked together or nested within each other by operators. The order of evaluation for expressions depends on the precedence of operators and brackets. The following basic rules apply: Arithmetic operators are evaluated before relational operators and relational operators are evaluated before logical operators. Operators with no precedence are evaluated according to their occurrence from left to right. Operations in brackets are evaluated first. The following table provides an overview of the operators and their precedence: Operator Operation Precedence + (Page 1481) Unary plus 2 - (Page 1481) Unary minus 2 Arithmetic expressions 1486 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program Operator Operation Precedence ** (Page 1481) Power 3 * (Page 1481) Multiplication 4 / (Page 1481) Division 4 MOD (Page 1481) Modulo function 4 + (Page 1481) Addition 5 - (Page 1481) Subtraction 5 < (Page 1484) Less than 6 > (Page 1484) Greater than 6 <= (Page 1484) Less than or equal 6 >= (Page 1484) Greater than or equal 6 = (Page 1484) Equal 7 <> (Page 1484) Not equal 7 NOT (Page 1485) Negation 3 AND (Page 1485) or & (Page 1485) Boolean AND 8 XOR (Page 1485) Exclusive OR 9 OR (Page 1485) Boolean OR 10 ( ) (Page 1480) Brackets 1 := (Page 1487) Assignment 11 Relational expressions Logical expressions Miscellaneous operations Value assignments Definition You can use a value assignment to assign the value of an expression to a tag. On the left side of the assignment is the tag that takes the value of the expression on the right. The name of a function can also be specified as an expression. The function is called by the value assignment and returns its function value to the tag on the left. The data type of value assignment is defined by the data type of the tag on the left. The data type of the expression on the right must match this type. For additional information on compatibility and conversion of data types, refer to "See also". Value assignments for STRUCT data type or PLC data types An entire structure can be assigned to another if the structures are identically organized and the data types as well as the names of the structural components match. You can assign a tag, an expression or another structural element to an individual structural element. WinCC Basic V13.0 System Manual, 02/2014 1487 Programming the PLC 9.1 Creating the user program Value assignments for the ARRAY data type An entire ARRAY can be assigned to another ARRAY if both the data types of the ARRAY elements as well as the ARRAY limits match. You can assign a tag, an expression or another ARRAY element to an individual ARRAY element. Value assignments for the STRING data type An entire STRING can be assigned to another STRING. You can assign another STRING element to an individual STRING element. Value assignments for the ANY data type You can assign a tag with the ANY data type only to the following objects: Input parameters or temporary local data of FBs that also have the data type ANY. Temporary local data of FCs that also have the data type ANY. Note that you can only point to memory areas with "standard" access mode with the ANY pointer. Value assignments for the POINTER data type You cannot use POINTER in value assignments in SCL. Examples The following table shows examples for value assignments: SCL "MyTag1" := "MyTag2"; (* Assignment of a tag*) "MyTag1" := "MyTag2" * "MyTag3"; (* Assignment of an expression*) "MyTag" := "MyFC"(); (* Call for a function that assigns its function value to the "MyTag" tag*) #MyStruct.MyStructElement := "MyTag"; (* Assignment of a tag to a structure element*) #MyArray[2] := "MyTag"; (* Assignment of a tag to an ARRAY element*) "MyTag" := #MyArray[1,4]; (* Assignment of an ARRAY element to a tag*) #MyString[2] := #MyOtherString[5]; (* Assignment of a STRING element to another STRING element*) See also Operators and operator precedence (Page 1486) 1488 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program Settings for SCL Overview of the settings for SCL Overview The following tables show the settings you can make for SCL: Editor settings Group Setting Description View Keyword highlighting Notation used to represent the keywords of the programming language. You can choose between uppercase and lowercase letters or a notation corresponding to the conventions of the Pascal programming language. Default settings for new blocks If you create new blocks, the following settings are set as default values. You can change these in the block properties at a later point in time. Group Setting Description Compile Create extended status information Allows all tags in a block to be monitored. The memory requirements of the program and execution times increase, however, with this option. Check ARRAY limits1) Checks at runtime whether array indices are within the declared range for an ARRAY. If an array index exceeds the permissible range, the enable output ENO of the block is set to "0". Set ENO automatically Checks at runtime whether errors occur in the processing of certain instructions. If a runtime error occurs, the enable output ENO of the block is set to "0". For CPUs of the S7-300/400 series: When the ARRAY limits are violated, the enable output ENO is set to FALSE. 1) For CPUs of the S7-1200/1500 series: When the ARRAY limits are violated, the enable output ENO is not set to FALSE. See "Addressing structured variables (Page 1190)" for error query options. See also Changing the settings (Page 1490) WinCC Basic V13.0 System Manual, 02/2014 1489 Programming the PLC 9.1 Creating the user program Changing the settings Procedure To change the settings, follow these steps: 1. Select the "Settings" command in the "Options" menu. The "Settings" window is displayed in the work area. 2. In the area navigation, select the "PLC programming" group. 3. Change the settings. Result The change will be loaded directly, there is no need to save it explicitly. See also Overview of the settings for SCL (Page 1489) The programming window of SCL Overview of the programming window Function The programming window is the work area, where you enter the SCL program. The following figure shows the programming window of SCL: The programming window consists of the following sections: 1490 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program Section Meaning Sidebar Line numbers You can set bookmarks and breakpoints in the sidebar. Outline view Code area Display of the absolute operands The line numbers are displayed to the left of the program code. The outline view highlights related code sections. You edit the SCL program in the code area. This table shows the assignment of symbolic operands to absolute addresses. See also Customizing the programming window (Page 1491) Formatting SCL code (Page 1492) Expanding and collapsing sections of code (Page 1493) Customizing the programming window Introduction You can customize the appearance of the programming window and the program code in the following way: By setting the font, size and color By setting the tab spacing By displaying the line numbers By showing or hiding the absolute operands Setting the font, size and color To set the font, size and color, 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 > Script/text editors" group. 3. Select the desired font and font size or choose a font color for the individual language elements. Setting the tab spacing To provide a better overview of the program, lines are indented according to syntax. Define the depth of indentation with the tab spacing. To set the tab spacing, follow these steps: WinCC Basic V13.0 System Manual, 02/2014 1491 Programming the PLC 9.1 Creating the user program 1. Select the "Settings" command in the "Options" menu. The "Settings" window is displayed in the work area. 2. Select the "General > Script/text editors" group. 3. Set the tab spacing. Show line numbers To display the line numbers, 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 > Script/text editors" group. 3. Select the "Show line numbers" option. Show or hide the absolute operands You can show the assignment of symbolic and absolute operands in a table next to the program code, if required. To hide or show the display of the absolute operands, follow these steps: 1. Click the "Absolute/symbolic operands" icon in the toolbar. The display of the absolute operands appears. 2. To move the display, click the table and drag it to the desired position while holding down the mouse button. 3. To change the width of the table, click on the right or left table border and drag it to the right or left while holding down the mouse button. See also Overview of the programming window (Page 1490) Formatting SCL code (Page 1492) Expanding and collapsing sections of code (Page 1493) Formatting SCL code Introduction To make the program clearer, you can indent or outdent individual lines manually or format code sections. Note the following information about formatting code sections: The type of formatting is based on the general settings for indents, but at least the line or the section is always indented. If you selected the setting "Smart", unnecessary spaces within the SCL instruction are also removed. Only syntactically correct code sections can be formatted. 1492 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program If you place the insertion point in the first or last line of an instruction for program control, for example in an IF instruction in the line with the "IF", the entire instruction is formatted. If you select text, only the selected text is formatted. Indenting or outdenting lines To indent or outdent individual lines, follow these steps: 1. Click on the line you want to indent or outdent. 2. Press the "Indent text", "Outdent text" button into the toolbar of the programming editor. Note You can set the width of the indent in "Options > Settings". Formatting code sections To format code sections, follow these steps: 1. Select the text that you want to format or place the insertion point in the appropriate line. 2. Select the "Format selected text automatically" button into the toolbar of the programming editor. See also Overview of the programming window (Page 1490) Customizing the programming window (Page 1491) Expanding and collapsing sections of code (Page 1493) Overview of the script and text editor settings (Page 185) Expanding and collapsing sections of code Introduction SCL instructions can span several lines. Examples for this are program control instructions or block calls. These instructions are identified as follows: An outline view between the display line number and the program code marks the entire code section. When you select the opening keyword, the closing keyword is automatically highlighted. WinCC Basic V13.0 System Manual, 02/2014 1493 Programming the PLC 9.1 Creating the user program Procedure To expand or collapse the code section, follow these steps: 1. Click the minus sign in the outline view. The code section closes. 2. Click the plus sign in the outline view. The code section opens. See also Overview of the programming window (Page 1490) Customizing the programming window (Page 1491) Formatting SCL code (Page 1492) Using bookmarks Basics of bookmarks Function You can use bookmarks to mark program locations in extensive programs so that you can find them quickly later if they need revising. Bookmarks are displayed in the sidebar of the programming window. You can navigate between multiple bookmarks within a block using menu commands. Bookmarks are saved with the project and are therefore available for anyone who wants to edit the block. However, they are not loaded to a device. Bookmarks are not evaluated when blocks are compared. See also Setting bookmarks (Page 1494) Navigating between bookmarks (Page 1495) Deleting bookmarks (Page 1496) Setting bookmarks Requirement The SCL block is open. 1494 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program Procedure To set a bookmark, follow these steps: 1. Right-click on the desired line in the sidebar. 2. Select the "Bookmarks > Set" command in the shortcut menu. Or: 1. Click on the line in which you want to place the bookmark. 2. Click the "Set/delete bookmark" button in the toolbar. Or: 1. Hold down the <Ctrl> key. 2. Click on the line in the sidebar in which you want to place the bookmark. Result A bookmark is placed in the program code. See also Basics of bookmarks (Page 1494) Navigating between bookmarks (Page 1495) Deleting bookmarks (Page 1496) Navigating between bookmarks Requirement Several bookmarks are set in a block. Procedure To navigate between bookmarks, follow these steps: 1. Set the insertion cursor in the program code. 2. In the "Edit" menu, select the "Go to > Next bookmark" or "Go to > Previous bookmark" command. Or: 1. Set the insertion cursor in the program code. 2. In the toolbar of the programming editor, click the "Go to next bookmark", "Go to previous bookmark" button. Or: WinCC Basic V13.0 System Manual, 02/2014 1495 Programming the PLC 9.1 Creating the user program 1. Click in the sidebar. 2. Select the "Bookmarks > Next" or "Bookmarks > Previous" command in the shortcut menu. Result The line with the bookmark is highlighted. See also Basics of bookmarks (Page 1494) Setting bookmarks (Page 1494) Deleting bookmarks (Page 1496) Deleting bookmarks You can delete individual bookmarks or all bookmarks from the block or the CPU. Deleting individual bookmarks To delete an individual bookmark, follow these steps: 1. Right-click in the sidebar on the line in which you want to delete the bookmark. 2. Select the "Bookmarks > Remove" command in the shortcut menu. Or: 1. Click on the line in which you want to delete the bookmark. 2. In the "Edit" menu, select the "Bookmarks > Remove" command. Or: 1. Click on the line in which you want to delete the bookmark. 2. Click the "Set/delete bookmark" button in the toolbar. Deleting all bookmarks from the block To delete all bookmarks from the block, follow these steps: 1. Right-click in the sidebar. 2. Select the "Bookmarks > Delete all from block" command in the shortcut menu. Or: 1. In the "Edit" menu, select the "Bookmarks > Delete all from block" command. 1496 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program See also Basics of bookmarks (Page 1494) Setting bookmarks (Page 1494) Navigating between bookmarks (Page 1495) Entering SCL instructions Rules for SCL instructions Instructions in SCL SCL recognizes the following types of instructions: Value assignments Value assignments are used to assign a tag a constant value, the result of an expression or the value of another tag. Instructions for program control Instructions for program control are used to implement program branches, loops or jumps. Additional instructions from the "Instructions" task card The "Instructions" task card offers a wide selection of standard instructions that you can use in your SCL program. Block calls Block calls are used to call up subroutines that have been placed in other blocks and to further process their results. Rules You need to observe the following rules when entering SCL instructions: Instructions can span several lines. Each instruction ends with a semicolon (;). No distinction is made between upper and lower case. Comments serve only for documentation of the program. They do not affect the program execution. Examples The following examples shows the various types of instructions: SCL // Example of a value assignment "MyTag":= 0; // Example of a block call "MyDB"."MyFB" (ParamInput:= 10); WinCC Basic V13.0 System Manual, 02/2014 1497 Programming the PLC 9.1 Creating the user program SCL // Example of a program control instruction WHILE "Counter" < 10 DO "MyTAG" := "MyTag" + 2; END_WHILE; Entering SCL instructions manually Requirement An SCL block is open. Procedure To enter SCL instructions, follow these steps: 1. Enter the syntax of the instruction using the keyboard. You are supported by the auto-complete function when performing this task. It offers all the instructions and operands that are allowed at the current location. 2. Select the required instruction or the desired operand from the auto-complete function. If you select an instruction that requires specification of operands, placeholders for the operands are inserted into the program. The placeholders for the operands are highlighted in yellow. The first placeholder is selected. 3. Replace this placeholder with an operand. 4. Use the <TAB> key to navigate to all other placeholders and replace them with operands. Note You can also drag-and-drop a defined operand from the PLC tag table or from the block interface into the program. To replace an operand that has already been inserted, hover the mouse pointer briefly over the operand to be replaced before releasing the mouse button. This selects the operand and when you release the mouse button it is replaced by the new operand. Result The instruction is inserted. The programming editor performs a syntax check. Incorrect entries are displayed in red and italics. In addition, you also receive a detailed error message in the inspector window. See also Using autocompletion in textual programming languages (Page 1372) Expanding and reducing the parameter list (Page 1513) 1498 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program Inserting SCL instructions using the "Instructions" task card The "Instructions" task card offers a wide selection of instructions that you can use in your SCL program. The SCL-specific instructions for program control are available in the "Instructions" task card. Requirement An SCL block is open. Procedure To insert SCL instructions into a program using the "Instructions" task card, follow these steps: 1. Open the "Instructions" task card. 2. To insert the instruction, select one of the following steps: - Navigate to the SCL instruction you want to insert and drag-and-drop it to the required line in the program code. The insertion location is highlighted by a green rectangle. - Select the location in the program code where you want to insert the instruction and then double-click on the instruction you want to insert. The instruction is inserted in the program. The placeholders for the operands are highlighted in yellow. The first placeholder is selected. 3. Replace this placeholder with an operand. You can also drag a tag from the interface or the PLC tag table with drag-and-drop to the placeholder. 4. Use the <TAB> key to navigate to all other placeholders and replace them with operands. Result The instruction is inserted. The programming editor performs a syntax check. Incorrect entries are displayed in red and italics. In addition, you also receive a detailed error message in the inspector window. See also Using autocompletion in textual programming languages (Page 1372) Expanding and reducing the parameter list (Page 1513) Defining the data type of an SCL instruction Basic information on the data types of SCL instructions Introduction The SCL instructions that you employ for block programming use specific data types to calculate function values. Certain SCL instructions only support the use of a specific data type. WinCC Basic V13.0 System Manual, 02/2014 1499 Programming the PLC 9.1 Creating the user program You cannot change the data type for these instructions. However, most of the SCL instructions support the use of different data types. We differentiate between the following two types of such instructions: Instructions for which the data type of the function value is determined by the data type of the input parameters. This is the case for most instructions. Instructions with default data type. The instructions listed in the following table are of this type. You will have to change the default data type if this is incompatible with the data type of the input parameter used. You can always change the data type based on the following syntax: _<data type> SCL instructions with default data type The following table lists the SCL instructions with default data types: Instruction Default data type CEIL DINT DECO DWORD FLOOR DINT NORM_X REAL PEEK BYTE SCALE_X INT TRUNC DINT CONCAT STRING See also Changing the data type of an SCL instruction (Page 1500) Example for changing the data type of an SCL instruction (Page 1501) Changing the data type of an SCL instruction Procedure Proceed as follows to insert an SCL instruction and change its data type: 1. Insert the instruction at the required point in the program using drag-and-drop. 2. Specify the operands for the instruction. The data type of the function value is specified based on the input parameters, or the default data type of the instruction is used. 3. Append the "_<data type>" string to the instruction name. "<data type>" represents the data type you need for the instruction. 1500 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program See also Basic information on the data types of SCL instructions (Page 1499) Example for changing the data type of an SCL instruction (Page 1501) Modifying the data types of IEC timers and IEC counters IEC timers and IEC counters are internal system function blocks and require an instance data block. You can create the instance data blocks either as single or multi-instance. The data type of the instance data block is determined according to the associated instruction. For CPUs of the S7-1200 and S7-1500 series, you can, however execute the instructions with different data types, depending on your requirements. If the newly set data type of the instance data block does not match the data type of the input parameter, an implicit conversion takes place if possible. If the conversion is not possible, you will receive an error message. Procedure To change the data type of an IEC timer or IEC-counter instance data block, proceed as follows: 1. Open the block in which you call the IEC timer or IEC counter. Depending on the instance type of the instance data block, there is a green-bordered box before (multi-instance) or after (single instance) the name of the instance data block. 2. Click the green-bordered box. A drop-down list box with the valid data types for the instance data block is opened. 3. Select the desired data type. Example for changing the data type of an SCL instruction Changing the default data type of the "Decode" instruction (DECO) Data type DWORD is set as default if you insert the "Decode" instruction in the program. "Tag_Result" := DECO(IN := "Tag_Value"); Modify the program code as follows to convert the data type from DWORD to BYTE: "Tag_Result_BYTE" := DECO_BYTE(IN := "Tag_Value"); See also Basic information on the data types of SCL instructions (Page 1499) Changing the data type of an SCL instruction (Page 1500) WinCC Basic V13.0 System Manual, 02/2014 1501 Programming the PLC 9.1 Creating the user program Displaying or hiding tag information Introduction Regardless of whether the operands are represented in absolute or symbolic form, you can show and hide simple or hierarchical comments used to document global tags. This information is taken from the PLC tag table. You can display the tag information either for all the blocks or for individually opened blocks. If you display the tag information for all the blocks, the tag information for all blocks currently opened and opened in future is shown. You can hide the tag information at any time again. If you have hidden the tag information for all blocks, you can display it again for individual ones that you have opened. If you select the display of tag information with hierarchical comments, the comments of the higher structure levels of structured tags will also be displayed. The display is in brackets after the comment of the tags; the comments of the individual levels are separated by a period. If there is no comment at a structure level for a tag, it is omitted in the display and this is recognizable because there are two periods. Displaying or hiding tag information for all blocks Follow the steps below to display or hide the tag information for all blocks: 1. Select the "Settings" command in the "Options" menu. The "Settings" window is displayed in the work area. 2. In the area navigation, select the "PLC programming" group. 3. If you want to show the tag information, either select the "Expand" option in the "Tag information" drop-down list or the "Tag information with hierarchy" depending on whether you want to display simple or hierarchical comments. 4. If you want to hide the tag information, select the "Collapse" option in the "Tag information" drop-down list. The tag information is displayed or hidden for all blocks. When you open further blocks, the tag information is displayed or hidden depending on the selected setting. Displaying or hiding tag information for an opened block Follow the steps below to display or hide the tag information for an opened block: 1. If you want to show the tag information, either select the "Show tag information" option in the "Shows the tag information" drop-down list or the "Tag information with hierarchy" depending on whether you want to display simple or hierarchical comments. 2. If you want to hide the tag information, select the "Hide tag information" option in the "Hides tag information" drop-down list. The tag information is displayed or hidden. 1502 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program Using Favorites in SCL Adding SCL instructions to the Favorites Requirement A block is open. The multipane mode is set for the "Instructions" task card or the Favorites are also displayed in the editor. Procedure To add SCL instructions to the Favorites, follow these steps: 1. Open the "Instructions" task card. 2. Maximize the "Basic instructions" pane. 3. Navigate in the "Basic instructions" pane to the instruction that you want to add to the Favorites. 4. Drag-and-drop the instruction into the "Favorites" pane or into the Favorites area in the program editor. Note To additionally display the Favorites in the program editor, click the "Display favorites in the editor" button in the program editor toolbar. See also Overview of the program editor (Page 1354) Inserting SCL instructions using Favorites (Page 1503) Removing SCL instructions from the Favorites (Page 1504) Inserting SCL instructions using Favorites Requirement A block is open. Favorites are available. WinCC Basic V13.0 System Manual, 02/2014 1503 Programming the PLC 9.1 Creating the user program Procedure To insert an instruction into a program using Favorites, follow these steps: 1. Drag-and-drop the desired instruction from Favorites to the desired position. Or: 1. Select the position in the program where you want to insert the instruction. 2. In the Favorites, click on the instruction you want to insert. Note To additionally display the Favorites in the program editor, click the "Display favorites in the editor" button in the program editor toolbar. See also Overview of the program editor (Page 1354) Adding SCL instructions to the Favorites (Page 1503) Removing SCL instructions from the Favorites (Page 1504) Removing SCL instructions from the Favorites Requirement A code block is open. Procedure To remove instructions from Favorites, follow these steps: 1. Right-click on the instruction you want to remove. 2. Select the "Remove instruction" command in the shortcut menu. Note To additionally display the Favorites in the program editor, click the "Display favorites in the editor" button in the program editor toolbar. 1504 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program See also Overview of the program editor (Page 1354) Adding SCL instructions to the Favorites (Page 1503) Inserting SCL instructions using Favorites (Page 1503) Insert block calls in SCL Basic information on the block call in SCL Calling function blocks Syntax of a call The following syntax is used to call a function block as a single or multi-instance: Single instance: - If the function block originates from the project: <DBName> (Parameter list) - If the function block originates from the "Instructions" task card: <DB name>.<Instruction name> (Parameter list) Multi-instance <#Instance name> (Parameter list) Calling as single instance or multi-instance Function blocks can be called either as a single instance or a multi-instance. Calling as a single instance The called function block stores its data in a data block of its own. Calling as a multi-instance The called function block stores its data in the instance data block of the calling function block. For additional information on the types of calls, refer to "See also". Parameter list If you call another code block from a SCL block, you can supply the formal parameters of the called block with actual parameters. The specification of the parameters has the form of a value assignment. This value assignment enables you to assign values (actual parameters) to the parameters you have defined in the called block. The formal parameters of the called code block are listed in brackets directly after the call. Input and in-out parameters have the assignment identifier ":=", output parameters have the WinCC Basic V13.0 System Manual, 02/2014 1505 Programming the PLC 9.1 Creating the user program assignment identifier "=>". A placeholder placed after the parameter shows the required data type and the type of the parameter. Rules for supplying parameters The following rules apply to supplying parameters: Constants, tags and expressions can be used as actual parameters. The assignment order is not of importance. The data types of formal and actual parameters must match. The individual assignments are separated by commas. If the called block has only one parameter, it is sufficient to specify the actual parameter in the brackets. The formal parameter need not be specified. See also Manually inserting block calls (Page 1510) Inserting block calls with drag-and-drop (Page 1511) Examples for calling a function block in SCL (Page 1508) Calling functions Syntax of a call The following syntax is used to call a function: <Function name> (Parameter list); //Standard call <Operand>:=<Function name> (Parameter list); // Call in an expression Function value Functions that provide a return value can be used in any expression in place of an operand. For this reason, the return value is also known as the "function value" in SCL. The call options of functions depend on whether the function returns a function value to the calling block. The function value is defined in the RET_VAL parameter. If the RET_VAL parameter is of the VOID data type, then the function will not return a value to the calling block. If the RET_VAL parameter has another data type, then the function returns a function value of this data type. In SCL, all data types are permitted for the RET_VAL parameter except ANY, ARRAY, STRUCT and VARIANT, as well as the parameter types TIMER and COUNTER. 1506 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program Call options There are two possibilities for calling functions in SCL: Standard call for functions with and without a function value With a standard call, the results of the function is made available as an output and in-out parameter. Call in an expression for functions with a function value Functions that return a function value can be used in any expression in place of an operand, for example, a value assignment. The function calculates the function value, which has the same name as the function and returns it to the calling block. There the value replaces the function call. Following the call, the results of the function is made available as a function value or as an output and in-out parameter. Parameter list If you call another code block from a SCL block, you need to supply the formal parameters of the called block with actual parameters. The specification of the parameters has the form of a value assignment. This value assignment enables you to assign values (actual parameters) to the parameters you have defined in the called block. The formal parameters of the called code block are listed in brackets directly after the call. Input and in-out parameters have the assignment identifier ":=", output parameters have the assignment identifier "=>". A gray placeholder placed after the parameter shows the required data type and the type of the parameter. Rules for supplying parameters The following rules apply to supplying parameters to functions: All parameters of the function must be supplied. The assignment order is not of importance. Constants, tags and expressions can be used as actual parameters. The data types of formal and actual parameters must match. The individual assignments are separated by commas. If the called block has only one parameter, it is sufficient to specify the actual parameter in the brackets. The formal parameter need not be specified. When you call functions in SCL, you cannot use the release mechanism via EN. Use an IF statement instead to call functions conditionally. WinCC Basic V13.0 System Manual, 02/2014 1507 Programming the PLC 9.1 Creating the user program See also Manually inserting block calls (Page 1510) Inserting block calls with drag-and-drop (Page 1511) Examples for calling functions in SCL (Page 1509) Examples for calling a function block in SCL Calling as a single instance The following example shows the call of an FB as a single instance: SCL // Call as a single instance "MyDB" (MyInput:=10, MyInout:= "Tag1"); Result After the call is executed, the value determined for the "MyInout" in/out parameter is available in "Tag1" in the "MyDB" data block. Calling as a multi-instance The following example shows the call of an FB as a multi-instance: SCL // Call as a multi-instance "MyFB" (MyInput:= 10, MyInout:= "Tag1"); Result After the "MyFB" block is executed, the value determined for the "MyInout" in-out parameter is made available in "Tag1" in the data block of the calling code block. See also Calling function blocks (Page 1505) Manually inserting block calls (Page 1510) Inserting block calls with drag-and-drop (Page 1511) 1508 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program Examples for calling functions in SCL Standard call The following example shows a standard function call: SCL // Standard function call "MyFC" (MyInput := 10, MyInOut := "Tag1"); Result After the "MyFC" block is executed, the value determined for the "MyInOut" in/out parameter is available in "Tag1" in the calling block and needs to be further processed there. Call in a value assignment The following example shows a function call in a value assignment: SCL (*Call in a value assignment, a function value was defined for "MyFC" *) #MyOperand := "MyFC" (MyInput1 := 3, MyInput2 := 2, MyInput3 := 8.9, MyInOut := "Tag1"); Result The function value of "MyFC" is transferred to "#MyOperand". Call in an arithmetic expression The following example shows a function call in an arithmetic expression: SCL (*Call in a mathematical expression, a function value was defined for "MyFC" *) #MyOperand := "Tag2" + "MyFC" (MyInput1 := 3, MyInput2 := 2, MyInput3 := 8.9); Result The function value of "MyFC" will be added to "Tag2" and the result will be transferred to "MyOperand". WinCC Basic V13.0 System Manual, 02/2014 1509 Programming the PLC 9.1 Creating the user program See also Calling functions (Page 1506) Manually inserting block calls (Page 1510) Inserting block calls with drag-and-drop (Page 1511) Manually inserting block calls You can insert calls for functions (FCs) and function blocks (FBs). Inserting a call for a function (FC) Proceed as follows to insert a function call: 1. Enter the function name. 2. Confirm your entry with the Return key. The syntax for the function call including the parameter list is added to the SCL program. The placeholders for the actual parameters are highlighted in yellow. The first placeholder is selected. 3. Replace this placeholder with an actual parameter. You can also drag a tag from the interface or the PLC tag table with drag-and-drop to the placeholder. 4. Use the <TAB> key to navigate to all other placeholders and replace them with actual parameters. Inserting a call for a function block (FB) To insert a call for a function block (FB), follow these steps: 1. Enter the name of the function block. 2. Confirm your entry with the Return key. The "Call options" dialog opens. 3. In the dialog, specify whether you want to call the block as a single or multi-instance. - If you click the "Single instance" button, in the "Name" field enter a name for the data block to be assigned to the call. - If you click the "Multi-instance" button, in the "Name in the interface" field enter a name of the tag with which the called function block is to be entered as a static tag in the interface of the calling block. 4. Confirm your entries with "OK". The syntax for the function block call including the parameter list is added to the SCL program. The placeholders for the actual parameters are highlighted in yellow. The first placeholder is selected. 5. Replace this placeholder with an actual parameter. You can also drag a tag from the interface or the PLC tag table with drag-and-drop to the placeholder. 6. Use the <TAB> key to navigate to all other placeholders and replace them with actual parameters. 1510 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program Result The block call is inserted. If you specify an instance data block that does not exist when calling a function block, it is created. See also Updating block calls (Page 1512) Expanding and reducing the parameter list (Page 1513) Using autocompletion in textual programming languages (Page 1372) Inserting block calls with drag-and-drop You can insert calls for existing functions (FC) and function blocks (FB) using a drag-and-drop operation from the project tree. Requirement The function to be called (FC) or the function block (FB) to be called is present. Inserting a call for a function (FC) To insert a function call using drag-and-drop, follow these steps: 1. Drag the function from the project tree into the program. The syntax for the function call including the parameter list is added to the SCL program. The placeholders for the actual parameters are highlighted in yellow. The first placeholder is selected. 2. Replace this placeholder with an actual parameter. You can also drag a tag from the interface or the PLC tag table with drag-and-drop to the placeholder. 3. Use the <TAB> key to navigate to all other placeholders and replace them with actual parameters. Inserting a call for a function block (FB) To insert a call for a function block (FB) using drag-and-drop, follow these steps: 1. Drag the function block from the project tree and drop it into the program. The "Call options" dialog opens. 2. In the dialog, specify whether you want to call the block as a single or multi-instance. - If you click the "Single instance" button, in the "Name" field enter a name for the data block to be assigned to the call. - If you click the "Multi-instance" button, in the "Name in the interface" field enter a name of the tag with which the called function block is to be entered as a static tag in the interface of the calling block. WinCC Basic V13.0 System Manual, 02/2014 1511 Programming the PLC 9.1 Creating the user program 3. Confirm your entries with "OK". The syntax for the function block call including the parameter list is added to the SCL program. The placeholders for the actual parameters are highlighted in yellow. The first placeholder is selected. 4. Replace this placeholder with an actual parameter. You can also drag a tag from the interface or the PLC tag table with drag-and-drop to the placeholder. 5. Use the <TAB> key to navigate to all other placeholders and replace them with actual parameters. Result The block call is inserted. If you specify an instance data block that does not exist when calling a function block, it is created. See also Updating block calls (Page 1512) Expanding and reducing the parameter list (Page 1513) Using autocompletion in textual programming languages (Page 1372) Updating block calls If interface parameters of a called block are changed, the block call can no longer be executed correctly. You can avoid such inconsistent block calls by updating the block calls. You have two options to update the block calls: Explicit updating in the program editor. The inconsistencies within the open block are displayed and can be updated. Implicit updating during compilation. All block calls in the program as well as the used PLC data types will be updated. Update blocks in the program editor To update a block call within a block, follow these steps: 1. Open the block in the program editor. 2. Click "Update inconsistent block calls" in the toolbar. Inconsistent calls are displayed. 3. Correct the inconsistencies. 1512 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program Update block calls during compilation Proceed as follows to update all block calls and uses of PLC data types during compilation implicitly: 1. Open the project tree. 2. Select the "Program blocks" folder. 3. Select the command "Compile > Software (rebulid all blocks)" in the shortcut menu. See also Manually inserting block calls (Page 1510) Inserting block calls with drag-and-drop (Page 1511) Expanding and reducing the parameter list In SCL, if you call blocks or insert instructions that are system-internal function blocks, the syntax and the parameter list with the placeholders for the actual parameters are inserted in the SCL program. To make the program code easier to read, the unused optional parameters are removed from the parameter list when you edit other instructions. You can restore these at any time. You can also explicitly reduce the parameter list when you have finished assigning the parameters. Expanding the parameter list To expand the parameter list, follow these steps: 1. Right-click in the block call or the instruction. 2. Select the "Expand parameter list" command from the shortcut menu or press the key combination <Ctrl+Shift+Space bar>. The parameter list is displayed in full again. Reducing the parameter list To reduce the parameter list, follow these steps: 1. Right-click in the block call or the instruction. 2. Select the "Reduce parameter list" command from the shortcut menu or press the key combination <Ctrl+Shift+Space bar>. All unused optional parameters are hidden. See also Entering SCL instructions manually (Page 1498) Inserting SCL instructions using the "Instructions" task card (Page 1499) Manually inserting block calls (Page 1510) Inserting block calls with drag-and-drop (Page 1511) WinCC Basic V13.0 System Manual, 02/2014 1513 Programming the PLC 9.1 Creating the user program Inserting comments Commenting program code You have various options for commenting SCL programs: Line comment A line comment starts with "//" and extends to the end of the line. Comment section A comment section is started with "(* and completed by "*)". It can span several lines. Inserting a line comment To insert line comments, follow these steps: 1. Type "//" at the position where you want to place the comment. This does not have to be the beginning of the line. 2. Enter the comment text. Inserting a comment section To insert a comment section, follow these steps: 1. Type "(*" at the position where you want to place the comment. This does not have to be the beginning of the line. 2. Enter the comment text. 3. Complete the comment with "*)". Disabling one or more lines with comments To disable program code with comments, follow these steps: 1. Select the code lines you want to comment out. 2. Click the "Comment selection" button in the editor. "//" is inserted at the beginning of the line in the selected lines. The code that follows is interpreted as a comment. If lines already containing a line comment are disabled, "//" is inserted as well. If these lines are enabled again, the original comments are retained. Enabling comment lines To enable lines that have been commented out to be enabled as code again, proceed as follows: 1. Select the code lines you want to enable. 2. Click the "Remove comment" button in the editor. The "//" mark for line comments at the beginning of the line is removed. 1514 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program Example The following code contains comment sections and line comments (************************************************************************************* A description of the instructions that follow can be placed here **************************************************************************************) IF "MyVal1" > 0 THEN //No division by 0 "MyReal" := "MyVal2" (* input value *) / "MyVal1" (* measured value *); END_IF; //Data type conversion "MyInt" := REAL_TO_INT("MyReal"); Editing SCL instructions Selecting instructions You can select individual instructions or all instructions of a block. Requirement An SCL block is open. Selecting individual instructions To select individual instructions, follow these steps: 1. Set the insertion mark before the first character that you want to select. 2. Press and hold down the left mouse button. 3. Move the cursor to a position after the last character that you want to select. 4. Release the left mouse button. Selecting all the instructions of a program To select all instructions, follow these steps: 1. In the "Edit" menu, select the "Select All" command or use the keyboard shortcut <Ctrl+A>. Note When you select the opening keyword of an instructing, the closing keyword is automatically highlighted. WinCC Basic V13.0 System Manual, 02/2014 1515 Programming the PLC 9.1 Creating the user program Copying, cutting and pasting instructions Copying an instruction To copy an instruction, follow these steps: 1. Select the instruction you want to copy. 2. Select "Copy" in the shortcut menu. Cutting an instruction To cut an instruction, follow these steps: 1. Select the instruction you want to cut. 2. Select the "Cut" command in the shortcut menu. Inserting an instruction from the clipboard To insert an instruction from the clipboard, follow these steps: 1. Copy or cut an instruction. 2. Click on the position at which you want to insert the instruction. 3. Select "Paste" in the shortcut menu. Deleting instructions Requirement An SCL block is open. Procedure To delete an instruction, follow these steps: 1. Select the instruction you want to delete. 2. Select the "Delete" command in the shortcut menu. 1516 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program Eliminating syntax errors in the program Basic information on syntax errors Syntax errors Below are some examples of syntax errors: Missing separators or the use of too many separators Incorrect keyword spelling Incorrect jump label spelling/notation Notation which does not match the set mnemonics (for example, "I2.3" instead of "E2.3") The use of key words as operands Identification of syntax errors Syntax errors are underlined in red or appear in red type. This identification allows you to recognise incorrect inputs at a glance and jump from error to error to eliminate them. Syntax errors are also listed in the "Info" tab of the inspector window with an error message. See also Finding syntax errors in the program (Page 1517) Finding syntax errors in the program Procedure To find syntax errors in the program, follow these steps: 1. Select the position in the program in which you wish to look for errors. 2. Click "Go to next error" in the toolbar. The first error after the position you have selected will be marked. You can use "Go to next error" and "Go to previous error" in the toolbar to find and correct all errors in the block. Or: WinCC Basic V13.0 System Manual, 02/2014 1517 Programming the PLC 9.1 Creating the user program 1. Open the error list in the inspector window with "Info > Syntax". All syntax errors are listed in the table with a short description of the error. 2. If there are any errors, click on the blue question mark next to the error text to obtain information on eliminating the problem. 3. Double-click the error you want to correct. The corresponding error is highlighted. See also Basic information on syntax errors (Page 1517) Changing the programming language Rules for changing the programming language Rules Observe the following rules if you want to change the programming language for a block: All CPU series: - You can only change the programming language of entire blocks. The programming language cannot be changed for individual networks. - You cannot switch blocks programmed in the programming languages SCL or GRAPH. In GRAPH blocks, however, you can change between LAD and FBD as network languages. S7-300/400: - You can only change between the programming languages LAD, FBD and STL. - You can create networks within a block using another programming language and then copy them into the desired block. - If the language of individual networks of the block cannot be changed, these networks is displayed in their original language. S7-1200/1500: - You can change between the programming languages LAD and FBD. S7-1500: - You can create STL networks within the LAD and FBD blocks. However, you cannot copy between STL and LAD/FBD. 1518 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program Change the programming language Procedure To change the programming language, follow these steps: 1. Right-click the block in the project tree. 2. Select the "Properties" command in the shortcut menu. The dialog with the properties of the block opens. 3. Select the "General" entry in the area navigation. 4. Select the new programming language in the "Language" drop-down list. 5. Confirm your selection with "OK". See also Rules for changing the programming language (Page 1518) Handling program execution errors Basics of error handling Introduction Program execution errors are programming or I/O access errors. You have a number of different options for responding to program execution errors depending on the CPU used. Handling program execution errors in S7-300/400 You can program the program execution error OB (OB 85) for S7-300/400 CPUs. If a program execution error occurs and you do not use the program execution error OB, the CPU will switch to "STOP" mode. You will find additional information about the program execution error OB in the description of the mode of operation of S7-300/400 CPUs. WinCC Basic V13.0 System Manual, 02/2014 1519 Programming the PLC 9.1 Creating the user program Handling program execution errors in S7-1200/1500 You can select the type of error handling for CPUs of the S7-1200 and S7-1500 series. You have the following two options: Use the CPU's global troubleshooting: - S7-1200: The CPU generates a diagnostic buffer entry and remains in "RUN" mode. - S7-1500: You can program the programming error OB (OB 121) and the I/O access error OB (OB 122) for S7-1500 CPUs. If no programming error OB exists in the CPU, the CPU switches to "STOP" mode when a programming error occurs. In the event of an I/O access error, the CPU always remains in "RUN" mode, regardless of whether the I/O access error OB is present. Please note, however, that an existing I/O access or programming error OB is not called synchronously to the error. Therefore, depending on the selected priority, the execution of I/O access or programming error OBs may be delayed instead of taking place immediately when the error occurs. If other errors occur before execution of the I/O access or programming error OB is complete, no further I/O access or programming error OB is called. If you want to prevent I/O access or programming error OBs from being discarded, set the priority correspondingly high. You can use the enable output ENO to detect I/O access and programming errors for the instructions "Read field" (FieldRead), "Write field" (FieldWrite) , "Read memory address" (PEEK) and "Write memory address" (POKE). You can find more information about these error OBs in the description of the mode of operation of S7-1500 CPUs. You use separate local error handling. Local error handling is error handling within a block. Local error handling has the following advantages: - The error information is stored in the system memory, which you can query and evaluate. - You can use the error information to program a response in the block to the error that has occurred. - Programmed error evaluation and error reactions do not interrupt the program cycle. - The system performance is not unnecessarily burdened by the local error handling. If no errors occur, programmed error analyses and reactions are not executed. Local error handling applies only to blocks for which it has been set explicitly. If local error handling is set for a block, no global error handling is conducted for errors in this block. Note Note the following information: All memory access errors and I/O access errors must be captured either by global or local error handling. If the parameters of an instruction do not cause any memory access errors, you can query the associated ENO. 1520 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program See also GET_ERROR: Get error locally (Page 2244) GET_ERR_ID: Get error ID locally (Page 2248) GET_ERROR: Get error locally (Page 1961) GET_ERR_ID: Get error ID locally (Page 1964) Querying and fixing errors in the program code (Page 170) Local error handling Principles of local error handling Introduction Local error handling makes it possible to query the occurrence of errors within a block and evaluate the associated error information. You can set local error handling for organization blocks (OBs), function blocks (FBs), and functions (FCs). If local error handling is enabled, the system reaction is ignored. Local error handling applies only to blocks for which it has been set explicitly. The local error handling setting is not assumed by a calling block, nor is it transferred to called blocks. For higher-level blocks and lower-level blocks, the system settings still apply provided dedicated error handling has not been programmed for these blocks. General procedure for local error handling When errors occur while a block is being executed with local error handling, a predefined response is initiated based on the following error types: Write errors: These errors are ignored, and program execution simply continues. Read errors: Program execution continues with the substitute value "0". Execution errors: Execution of the instruction is aborted. Program execution resumes with the next instruction. Information about the first error that occurs is stored in the system memory. This information can be queried and output with an instruction (GET_ERROR or GET_ERR_ID). Error information is output in a format that can undergo additional processing. You can use additional instructions to analyze error information and program a reaction to the error based. When information about the first error is queried, the error memory space in the system memory is enabled. Then, when additional errors occur, information about the next error is output. Instructions for local error handling You can use the following instructions for local error handling: GET_ERROR: Get error locally GET_ERR_ID: Get error ID locally WinCC Basic V13.0 System Manual, 02/2014 1521 Programming the PLC 9.1 Creating the user program The instructions differ in the amount of error information that is output with each one. For additional information on the instructions, refer to "See also". See also GET_ERROR: Get error locally (Page 2244) GET_ERR_ID: Get error ID locally (Page 1964) GET_ERR_ID: Get error ID locally (Page 2248) GET_ERROR: Get error locally (Page 1961) Error output priorities Overview of the priorities In local error handling, information about the first error that occurred is displayed. If multiple errors occur at the same time while an instruction is being executed, these errors are displayed according to their priority. The following table shows the priority of different types of errors. Priority Error type 1 Error in the program code 2 Missing reference 3 Invalid range 4 DB does not exist 5 Operands are not compatible 6 Width of specified area is not sufficient 7 Timers or counters do not exist 8 No write access to a DB 9 I/O error 10 Instruction does not exist 11 Block does not exist 12 Invalid nesting depth The highest priority is 1 and the lowest priority is 12. See also GET_ERROR: Get error locally (Page 2244) GET_ERR_ID: Get error ID locally (Page 1964) GET_ERR_ID: Get error ID locally (Page 2248) GET_ERROR: Get error locally (Page 1961) 1522 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program Enabling local error handling for a block Introduction Local error handling is enabled for a block if you insert one of the following instructions in a network. GET_ERROR: Get error locally GET_ERR_ID: Get error ID locally For additional information on the instructions, refer to "See also". If local error handling is enabled for a block, the system reactions for this block are ignored. Requirement The block is open. Die "Instructions" task card is open. Procedure To enable local error handling for a block, proceed as follows: 1. Navigate to the "Basic instructions" pane of the "Instructions" task card. 2. Open the "Program Control" folder. 3. Drag the instruction "Get error locally" (GET_ERROR) or "Get error ID locally" (GET_ERR_ID) to the required network. Result Local error handling is enabled for the open block. The "Handle errors within block" check box is selected in the Inspector window under "Properties > Attributes". This setting cannot be edited in the Inspector window. Local error handling can be deactivated by deleting the inserted instructions on local error handling. See also GET_ERROR: Get error locally (Page 2244) GET_ERR_ID: Get error ID locally (Page 1964) GET_ERR_ID: Get error ID locally (Page 2248) GET_ERROR: Get error locally (Page 1961) 9.1.4.3 Programming data blocks Basic principles for programming of data blocks A data block (DB) is used to save the values that are written during execution of the program. WinCC Basic V13.0 System Manual, 02/2014 1523 Programming the PLC 9.1 Creating the user program In contrast to the code block, the data block contains only tag declarations. It contains no networks or instructions. The tag declarations define the structure of the data block. Types of data blocks There are two types of data blocks: Global data blocks The global data block is not assigned to a code block. You can access the values of a global data block from any code block. A global data block contains only static tags. The structure of the global data block can be freely defined. In the declaration table for data blocks, you declare the data elements that are to contained in the global data block. Instance data blocks The instance data block is assigned directly to a function block (FB). The structure of an instance data block cannot be freely defined, but is instead determined by the interface declaration of the function block. The instance data block contains exactly those block parameters and tags that are declared there. However, you can define instance-specific values in the instance data block, for example, start values for the declared tags. ARRAY data blocks (S7-1500) ARRAY data blocks are global data blocks that consist of an ARRAY. This ARRAY can be based on any data type. For example, an ARRAY of a PLC data type (UDT) is possible. The DB contains no other elements besides the ARRAY. Because of their flat structure, ARRAY data blocks facilitate access to the ARRAY elements and their transfer to called blocks. The "Move operations" section of the "Instructions" task card offers options for addressing of ARRAY DBs. PLC data types as a template for global data blocks PLC data types can be used as templates for the creation of global data blocks with identical data structures. You create the structure as PLC data type only once and then generate the required data blocks by assigning the PLC data type. System data types as a template for global data blocks System data types can also be used as templates for creating global data blocks with identical data structure. System data types already have a pre-defined structure. You insert the system data type in the program only once and then generate additional data blocks with an identical structure by assigning the system data type. 1524 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program Access modes There are two different modes of accessing data values in data blocks: Data blocks with optimized access (only S7-1200) Data blocks with optimized access have no fixed defined structure. In the declaration, the data elements are assigned only a symbolic name and no fixed address within the block. You access the data values in these block via symbolic names. The "Optimized block access" attribute is always enabled for ARRAY data blocks. Data blocks with standard access (all CPU families) Data blocks with standard access have a fixed structure. In the declaration, the data elements are assigned both a symbolic name and a fixed address within the block. You can access the data values in these blocks via symbolic names or the address. ARRAY data blocks with standard access are not possible. Retentivity of data values To prevent data loss in the event of power failure, you can store the data values in a retentive memory area. See also Creating data blocks (Page 1334) Global data blocks (DB) (Page 1148) Instance data blocks (Page 1149) Structure of the declaration table for data blocks Structure of the declaration table for data blocks The figure below shows the structure of the declaration table for data blocks. The display will vary depending on type of block and type of access. Display of instance-specific values In instance data blocks, you can apply the already defined values from the interface of the assigned function block or define instance-specific start values. Values that are applied from the function block cannot be edited. You can replace the grayed-out values with instancespecific values. Values that were already changed instance specific are not grayed out. WinCC Basic V13.0 System Manual, 02/2014 1525 Programming the PLC 9.1 Creating the user program Meaning of the columns The following table shows the meaning of the individual columns. You can show or hide the columns as required. The number of columns displayed varies depending on the CPU series. Column Explanation Symbol you can click to move or copy the tag. You can, for example, dragand-drop the tag into a program and use it there as operand. Name Name of the tags. Data type Data type of the tags. Offset Relative address of the tags. The column is only visible in data blocks with standard access. Default value Default value of the tag in the interface of a higher-level code block or in a PLC data type. The values contained in the "Default value" column can only be changed in the higher-level code block or PLC data type. The values are only displayed in the data block. Start value Value that the tag should assume at startup. The default values defined in a code block are used as start values during the creation of the data block. You can then replace these adopted values with instance-specific start values. Specification of an start value is optional. If you do not specify any value, the tag assumes the default value at startup. If a default is not defined either, the default value valid for the data type is used. For example, the value "FALSE" is specified as standard for BOOL. Monitor value Current data value in the CPU. This column only appears if an online connection is available and you click "Monitor". Snapshot Shows values that were loaded from the device. Retentivity Marks the tag as retentive. The values of retentive tags are retained even after the power supply is switched off. Visible in HMI Shows whether the tag is visible by default in the HMI selection list. Accessible from HMI Shows whether HMI can access this tag during runtime. Setting value Setting values are the values that will probably have to be fine tuned during commissioning. After commissioning, the values of these tags can be transferred to the offline program as start values and stored there. Comment Comment to document the tags. See also Creating data blocks (Page 1334) Basic information on start values (Page 1533) 1526 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program Creating data blocks Requirement The "Program blocks" folder in the project tree is open. Procedure To create a data block, follow these steps: 1. Double-click the "Add new block" command. The "Add new block" dialog box opens. 2. Click the "Data block (DB)" button. 3. Select the type of the data block. You have the following options available to you: - To create a global data block, select the list entry "Global DB". - To create an ARRAY data block, select the "ARRAY DB" entry in the list. - To create an instance data block, select the function block to which you want to assign the instance data block from the list. The list contains only the function blocks that were previously created for the CPU. - To create a data block based on a PLC data type, select the PLC data type from the list. The list contains only the PLC data types that were previously created for the CPU. - To create a data block based on a system data type, select the system data type from the list. The list contains only those system data types that have already been inserted to program blocks in the CPU. 4. Enter a name for the data block. 5. Enter the properties of the new data block. 6. If you have selected an ARRAY DB as the data block type, enter the ARRAY data type and the high limit for the ARRAY. You can change the high limit for the ARRAY at any time in the property window of the created block. The ARRAY data type cannot be changed subsequently. 7. To enter additional properties of the new data block, click "Additional information". An area with further input fields is displayed. 8. Enter all the properties you require. 9. Activate the "Add new and open" check box if the block does not open as soon as it is created. 10.Confirm your entry with "OK". Result The new data block is created. You can find the data block in the project tree in the "Program blocks" folder. WinCC Basic V13.0 System Manual, 02/2014 1527 Programming the PLC 9.1 Creating the user program See also Instance data blocks (Page 1149) Global data blocks (DB) (Page 1148) Overview of block properties (Page 1343) Updating data blocks Introduction Changes in the interface of a function block or a PLC data type can lead to the corresponding data blocks becoming inconsistent. These inconsistencies are marked in red in the declaration table and at the call point of the block. To remedy these inconsistencies, the data blocks must be updated. You have three options to update block calls: Explicit updating in the declaration table for data blocks. The data block is updated. Changes from the interface of the assigned function block and changes to the used PLC data types are applied. Explicit updating in the program editor. The block calls in the open block will be updated. The associated instance data block is also adjusted in the process. Implicit updating during compilation. All block calls in the program as well as the used PLC data types and the corresponding instance data blocks are updated. Explicit Updating in the Declaration Table for Data Blocks To explicitly update an individual data block, follow these steps: 1. Open the data block. 2. Select "Update interface" in the shortcut menu. Explicit Updating in the Program Editor To update all block calls or a specific call within a block, follow these steps: 1. Open the block in the program editor. 2. Right-click on the instruction with the block call. 3. Select the "Update" command in the shortcut menu. 4. The "Interface update" dialog opens. This dialog shows the differences between the block interface in use and the changed interface of the called block. 5. If you want to update the block call, click "OK". To cancel the update, click "Cancel". 1528 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program Implicit Updating during Compilation To implicitly update all block calls and uses of PLC data types as well as the instance data blocks during the compiling, follow these steps: 1. Open the project tree. 2. Select the "Program blocks" folder. 3. Select the command "Compile > Software (rebuild all blocks)" in the shortcut menu. See also Changing the properties of tags in instance data blocks (Page 1540) Extending data blocks Description In order to enable the editing of PLC programs that have already been commissioned and that are running without error on a system, CPUs of the S7-1500 series and most CPUs of the S7-1200 V4 series support the option of extending global data blocks during runtime. You can download the modified blocks without setting the CPU to STOP and without affecting the values of already loaded tags. This is a simple means of implementing program changes. This load process (download without reinitialization) will not have a negative impact on the controlled process. Principle of operation Each data block is always assigned a default memory reserve. The memory reserve is not used initially. Activate the memory reserve if you decide on loading interface changes after having compiled and downloaded the block. All tags that you subsequently declare will be saved to the memory reserve. A subsequent download has no impact on the values of tags that have already been loaded. If you decide to review your program at a later time while the plant is not in operation, you are also provided an option of reworking the memory layout of individual or several blocks in a single pass. With this action, you move all tags from the reserve area to the regular area. The memory reserve is now cleared and made available for further interface extensions. Requirements This "Download without reinitialization" function is available if the following requirements are met: The project is in the "TIA Portal V12" format or a higher version. You are working with a CPU that supports "Download without reinitialization". The blocks were created in LAD, FBD, STL, or SCL. WinCC Basic V13.0 System Manual, 02/2014 1529 Programming the PLC 9.1 Creating the user program The blocks were created by the user, i.e. they are not included with the blocks delivered in your package. These blocks are assigned the optimized access attribute. Basic steps Perform the following steps if you want to extend the data block and then load the block without re-initialization. 1. All blocks have a default memory reserve of 100 bytes. You can adapt this memory reserve to suit your requirements. 2. Activate the memory reserve. 3. Extend the block interface. 4. Compile the block. 5. Download the block to the CPU as usual. Reference For more information on the various steps, refer to chapter "Loading blocks (S7-1200/1500) ". Creating a data structure for global data blocks Declaring tags of elementary data type Requirement A global data block is open. Note You cannot change the structure of instance data blocks and of data blocks based on a PLC data type directly, since the structures of these blocks are defined by the respective function block or the PLC data type. The type of the data block is entered in the block properties. Procedure To declare a tag of the elementary data type, follow these steps: 1. Enter a tag name in the "Name" column. 2. In the "Data type" column, click the button for the data type selection. A list of the permissible data types is opened. 3. Select the desired data type. 1530 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program 4. Optional: Change the properties of the tags that are displayed in the other columns. 5. Repeat steps 1 to 4 for all tags that are to be declared. See also Displaying and editing block properties (Page 1348) Declaring tags of the ARRAY data type (Page 1531) Declaring tags of STRUCT data type (Page 1532) Editing tables (Page 226) Declaring tags of the ARRAY data type Requirement A global data block is open. Procedure To declare a tag of the ARRAY data type, follow these steps: 1. Enter a tag name in the "Name" column. 2. Enter the "Array" data type in the "Data type" column. You will be supported by autocompletion in this step. The "Array" dialog opens. 3. In the "Data type" text box, specify the data type of the array elements. 4. In the "ARRAY limits" text box, specify the high and low limit for each dimension. Example of a one-dimensional ARRAY: [0..3] Example of a three-dimensional ARRAY: [0..3, 0..15, 0..33] 5. Confirm your entry. 6. Optional: Change the properties of the tags that are displayed in the other columns. The tag is created but remains collapsed. To expand the ARRAY, click the triangle in front of the tag. Not that you cannot expand very large ARRAYs for reasons of clarity. Entering start values of ARRAY elements To set default start values for the individual elements of an ARRAY, follow these steps: 1. Click the triangle in front of the ARRAY data type tags. The ARRAY opens and the individual ARRAY elements are shown in separate rows. 2. Enter the required value in the "Start value" column. WinCC Basic V13.0 System Manual, 02/2014 1531 Programming the PLC 9.1 Creating the user program Declaring tags of STRUCT data type Requirement A global data block is open. Procedure To declare a tag of the STRUCT data type, follow these steps: 1. Enter a tag name in the "Name" column. 2. Enter "Struct" in the "Data type" column. You will be supported by autocompletion during input. An empty, indented row is inserted after the new tag. 3. Insert the first structural element in the first empty row. An additional empty row is inserted after the element. 4. Select a data type for the structure element. 5. Optional: Change the properties of the structural element that is displayed in the other columns of the block interface. 6. Repeat the step 4 to 7 for all additional structure elements. It is not necessary to end the structure explicitly. The structure ends with the last element that is entered. 7. To insert a new tag after the structure, leave a blank row after the end of the structure and then start the new tag in the second empty row. Result The tag of STRUCT data type is created. Enter start values of structure elements To set default start values for the individual elements of a structure, follow these steps: 1. Click the triangle in front of the STRUCT data type tags. The structure opens and the individual structure elements are shown in separate rows. 2. Enter the required value in the "Start value" column. See also STRUCT (Page 1239) 1532 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program Declaring tags based on a PLC data type Requirements A global data block is open. A PLC data type is declared in the current CPU. Procedure To declare a tag based on a PLC data type, follow these steps: 1. Enter a tag name in the "Name" column. 2. Enter the PLC data type in the "Data type" column. You will be supported by autocompletion during input. 3. Optional: Change the properties of the tags that are displayed in the other columns of the table. Result The tag is created. See also Layout of the block interface (Page 1375) Define start values Basic information on start values Definition of "Start value" The start value of a tag is a value defined by you which the tag assumes after a CPU startup. The retentive tags have a special status. Their values take the defined start value only after a "cold restart". After a "warm restart", they retain their values and are not reset to the start value. Definition of "Default value" The structure of the data blocks can be derived from higher-level elements. An instance data block is based, for example, on the interface of a higher-level code block. A global data block can be based on a predefined PLC data type. In this case you can define a default value for each tag in the higher-level element. These default values are used as start values during the creation of the data block. You can then replace these values with instance-specific start values in the data block. WinCC Basic V13.0 System Manual, 02/2014 1533 Programming the PLC 9.1 Creating the user program Specification of an start value is optional. If you do not specify any value, the tag assumes the default value at startup. If a default is not defined either, the default value valid for the data type is used. For example, the value "FALSE" is specified as standard for BOOL. See also Define start values (Page 1534) Structure of the declaration table for data blocks (Page 1525) Declaring local tags and constants in the block interface (Page 1381) Applying values from the online program as start values (Page 1549) Define start values Define start values To define the start values for the tags of a data block, follow these steps: 1. Open the data block. The "Default value" column shows the default values that were defined for the tags in the interface of a higher-level code block or in a PLC data type. 2. Click the "Expanded mode" button to show all elements of structured data types. 3. Enter the desired start values in the "Start value" column. The value must match the data type of the tag and should not exceed the range of the data type. The start values are defined. The tag takes the defined value at startup, provided it was not declared as retentive. Resetting a tag to the default value To reset a tag for which you have defined a start value to the default value, follow these steps: 1. Select a modified value in the table. 2. Delete the value. The default value is entered. The default value is displayed. 1534 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program Resetting all tags to the default value To reset to the default value all tags for which you have defined an start value, follow these steps: 1. Select the "Reset start values" icon in the toolbar. The default values are transferred to the "Start value" column. Write-protected start values are not overwritten. See also Basic information on start values (Page 1533) Applying values from the online program as start values (Page 1549) Loading changed values Introduction To apply the changed start values from the offline program to the online program, you must load the changes. The following cases must be distinguished: Loading changed start values of non-retentive tags Loading changed start values of retentive tags Loading changed start values of setting values Requirement The start values in the offline program were changed. Procedure To load changed start values of non-retentive tags, follow these steps: 1. Select the blocks to be loaded in the project tree. 2. Select the "Download to device > Software (only changes)" command from the shortcut menu. The blocks are compiled and loaded. The start values of the newly defined tags are placed in the load memory of the CPU. The program runs with the new start values at the next transition from STOP to RUN. To load changed start values of retentive tags, follow these steps: 1. Select the blocks to be loaded in the project tree. 2. Select the "Compile > Software (rebuild all blocks)" command in the shortcut menu. 3. In the "Online" menu, select the "Download and reset PLC program" command. The online blocks are deleted and replaced with the new blocks. This reinitializes all tags, including the retentive tags. WinCC Basic V13.0 System Manual, 02/2014 1535 Programming the PLC 9.1 Creating the user program Information about loading changed setting values and general information about loading can be found under "See also". See also Initializing setting values in the online program (Page 1548) Setting retentivity Retentivity of tags in data blocks Retentive behavior To prevent data loss in the event of power failure, you can mark the data as retentive. This data is stored in a retentive memory area. The options for setting the retentivity depend on the type of data block and the type of block access that is set. See also Setting retentivity in an instance data block (Page 1536) Setting retentivity in a global data block (Page 1537) Setting retentivity in an instance data block Introduction In an instance data block, the editability of the retentive behavior depends on the type of access of the higher-level function block: Function block with standard access You can define the instance data both as retentive or non-retentive. Individual retentivity settings are not possible for individual tags. Function block with optimized access In the instance data block, you can define the retentivity settings of the tags that are selected in the block interface with "Set in IDB". With these tags also, you cannot individually set the retentive behavior for each tag. The retentivity setting has an impact on all tags that are selected in the block interface with "Set in IDB". 1536 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program Setting Retentivity for Standard Access To centrally set the retentivity of all tags in the data block with standard access, follow these steps: 1. Open the instance data block. 2. Select the check box in the "Retain" column of a tag. All tags are defined as retentive. 3. To reset the retentivity setting for all tags, clear the check box in the "Retain" column of a tag. All tags will be defined as non-retentive. Setting Retentivity for Optimized Access To set the retentive behavior of the tags that are selected with "Set in IDB" in data blocks with optimized access, follow these steps: 1. Open the instance data block. 2. Select the check box in the "Retain" column of a tag. All tags selected with "Set in IDB" in the data block interface are defined as retentive. 3. To reset the retentivity setting for the tags, clear the check box in the "Retain" column of a tag. All tags selected with "Set in IDB" in the data block interface will be defined as non-retentive. See also Basics of block access (Page 1151) Retentivity of tags in data blocks (Page 1536) Setting retentivity in a global data block Introduction In a global data block, the editability of the retentive behavior depends on the type of access: Global data block with standard access You can define the data both as retentive or non-retentive. Individual retentivity settings are not possible for individual tags. Global data block with optimized access You can individually define the retentivity settings of the tags. For tags with structured data types, retentivity settings are transferred for all tag elements. WinCC Basic V13.0 System Manual, 02/2014 1537 Programming the PLC 9.1 Creating the user program Setting Retentivity for Standard Access To centrally set the retentivity of all tags in the data block with standard access, follow these steps: 1. Open the global data block. 2. Select the check box in the "Retain" column of a tag. All tags are defined as retentive. 3. To reset the retentivity setting for all tags, clear the check box in the "Retain" column of a tag. All tags are defined as non-retentive. Setting Retentivity for Optimized Access To individually set the retentivity of all tags in data blocks with optimized access, follow these steps: 1. Open the global data block. 2. In the "Retain" column, select the check box for the tags for which you want to set a retentive behavior. The selected tag is defined as retentive. 3. To reset the retentivity setting for the tags, clear the check box in the "Retain" column of a tag. All selected tags are defined as non-retentive. See also Basics of block access (Page 1151) Retentivity of tags in data blocks (Page 1536) Editing the properties of tags in data blocks Properties of the tags in data blocks Properties The following table provides an overview of the properties of tags in data blocks: 1538 Group Property Description General Name Name of the tags. Data type Data type of the tags. WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program Group Property Description Default value Default value of the tag in the interface of a higher-level code block or in a PLC data type. The values contained in the "Default value" column can only be changed in the higher-level code block or PLC data type. The values are only displayed in the data block. Start value Value that the tag should assume at CPU startup. The default values defined in a code block are used as start values during the creation of the data block. You can then replace these adopted values with instance-specific start values. Specification of an start value is optional. If you do not specify any value, the tag assumes the default value at startup. If a default is not defined either, the default value valid for the data type is used. For example, the value "FALSE" is specified as standard for BOOL. Attributes Comment Comment on the tag. Retain Marks the tag as retentive. The values of retentive tags are retained even after the power supply is switched off. This attribute is only available in the interface of the function block with optimized access. Accessible from HMI Indicates whether the tag can be used in HMI. When the attribute is set, you have read or write access to the tag from the HMI. When the attribute is not set, you cannot access the tag from the HMI. Please note, however, that you cannot implement general access protection for the tag with the "Accessible from HMI" attribute. Read or write access from other applications is possible even if the attribute is not enabled. WinCC Basic V13.0 System Manual, 02/2014 Visible in HMI Shows whether the tag is visible by default in the HMI selection list. Hidden parameter Indicates whether the tag should be hidden for the block call. This is only possible if you have specified a valid predefined actual parameter beforehand. Predefined actual parameter Defines a parameter that is to be used as actual parameter during the block call. Visible Indicates whether a parameter is visible in CFC. Configurable Indicates whether a parameter is configurable in CFC. For test Indicates whether a parameter is registered for the CFC test mode. Interconnectable Indicates whether a parameter is interconnectable in CFC. Enable tag readback Indicates whether a parameter is relevant for the "Read back chart" function in CFC. Enumeration texts Assigns a parameter to an enumeration in CFC. Engineering unit Assigns a parameter to a unit in CFC. Low limit Defines the low limit for the parameter in CFC. High limit Defines the high limit for the parameter in CFC. 1539 Programming the PLC 9.1 Creating the user program See also Changing the properties of tags in instance data blocks (Page 1540) Changing the properties of tags in global data blocks (Page 1541) Changing the properties of tags in instance data blocks Instance-specific tag properties Two options are available for defining the tag properties: The tag properties are applied from the interface of the assigned function block. Properties that are applied from the function block are displayed grayed out out in the columns of the declaration table. The "Name" and "Data type" properties are always applied. You define instance-specific properties. You can change some properties instance specific. Changeable values are, for example, "Comment" or "Visible in HMI". Properties that were changed instance specific are not grayed out in the columns of the declaration table. The instance-specific changes are retained, even if the interface of the higher-level function block is changed and the instance data blocks are subsequently updated. Editing properties of an element in the declaration table To edit the properties of an element, follow these steps: 1. Open the instance data block. 2. Select the required element in the table. 3. Change the entries in the columns. Editing properties of several elements in the declaration table You can also simultaneously set or reset the "Retain", "Visible in HMI", "Accessible in HMI" and "Setpoint" columns for one or more selected elements. To change one of these properties for several elements, follow these steps: 1. Open the data block. 2. Hold down the CTRL key. 3. In the required column, select each of the table cells whose value you want to change. 4. Select the "Set <property>" or "Reset <property>" command in the shortcut menu. 1540 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program Editing properties in the properties window To edit the properties of an individual tag, follow these steps: 1. Select a tag in the table. 2. Select the "Properties" command in the shortcut menu. The properties window opens. It shows the properties of the tag in the "General" and "Attributes" areas. 3. Select the required area in the area navigation. 4. Change the entries in the text boxes. Reset individual properties to the default value. To reset individual tag properties to the value that was defined as default in the function block, follow these steps: 1. Select an instance-specific, modified value in the table. 2. Delete the value. The instance-specific value will be deleted and the default value from the interface of the function block entered. The default value is displayed grayed out. See also Updating data blocks (Page 1528) Properties of the tags in data blocks (Page 1538) Changing the properties of tags in global data blocks Introduction Two options are available for defining the tag properties: The tag properties are applied from the PLC data type. Properties that are applied from the PLC data type are shown grayed out in the columns of the declaration table. The "Name" and "Data type" properties are always applied. You define specific properties. You can change some properties in the global data block. Changeable values are, for example, "Comment" or "Visible in HMI". Properties that were changed are not grayed out in the columns of the declaration table. The changes are retained, even if the PLC data type changes and the global data block is subsequently updated. Editing properties of an element in the declaration table To edit the properties of an element, follow these steps: 1. Open the global data block. 2. Select the required element in the table. 3. Change the entries in the columns. WinCC Basic V13.0 System Manual, 02/2014 1541 Programming the PLC 9.1 Creating the user program Editing properties of several elements in the declaration table You can also simultaneously set or reset the "Retain", "Visible in HMI", "Accessible in HMI" and "Setpoint" columns for one or more selected elements. To change one of these properties for several elements, follow these steps: 1. Open the data block. 2. Hold down the CTRL key. 3. In the required column, select each of the table cells whose value you want to change. 4. Select the "Set <property>" or "Reset <property>" command in the shortcut menu. Editing properties in the properties window To edit the properties of an individual tag, follow these steps: 1. Select a tag in the table. 2. Select the "Properties" command in the shortcut menu. The properties window opens. It shows the properties of the tag in the "General" and "Attributes" areas. 3. Select the required area in the area navigation. 4. Change the entries in the text boxes. Reset individual properties to the default value. To reset individual tag properties to the value that was defined as default in the PLC data type, follow these steps: 1. Select a modified value in the table. 2. Delete the value. The default value from the PLC data type is entered. The default value is displayed grayed out. See also Properties of the tags in data blocks (Page 1538) Editing the declaration table for data blocks Inserting table rows Procedure Proceed as follows to insert a row above the selected row: 1. Select the row in front of which you want to insert a new row. 2. Click the "Insert row" button on the toolbar of the table. 1542 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program Result A new row is inserted above the selected row. See also Editing tables (Page 226) Inserting table rows Procedure Proceed as follows to insert a row below the selected row: 1. Select the row below which you want to insert a new row. 2. Click the "Add row" button on the table toolbar. Result A new empty row will be inserted below the selected row. See also Editing tables (Page 226) Deleting tags Requirements A global data block is open. Procedure To delete a tag, follow these steps: 1. Select the row with the tag to be deleted. You can also select several rows by clicking on them one after the other while holding down the <Ctrl> key or by pressing and holding down <Shift> and clicking on the first and last row. 2. Select the "Delete" command in the shortcut menu. WinCC Basic V13.0 System Manual, 02/2014 1543 Programming the PLC 9.1 Creating the user program Note You cannot directly change the structure of instance data blocks and of global data blocks based on a PLC data type, since the structures of these blocks are defined in the higher-level object. The type of the data block is entered in the block properties. See also: Displaying and editing block properties (Page 1348) See also Editing tables (Page 226) Automatically filling in successive cells You can load the contents of one or several table cells into the cells below, automatically filling in the successive cells. If you automatically fill in cells in the "Name" column, a consecutive number will be appended to each name. For example, "Motor" will become "Motor_1". You can define individual or more cells as well as entire rows as source area. If less rows exist in the open table than you want to fill, then you will first have to insert additional empty rows. Requirement The table is open. Sufficient declaration rows are available. Procedure To automatically fill in successive cells, follow these steps: 1. Select the cells to be loaded. 2. Click the "Fill" symbol in the bottom right corner of the cell. The mouse pointer is transformed into a crosshair. 3. Keep the mouse button pressed and drag the mouse pointer downwards over the cells that you want to fill in automatically. 4. Release the mouse button. The cells are filled in automatically. 5. If entries are already present in the cells that are to be automatically filled in, a dialog appears. In this dialog you can indicate whether you want to overwrite the existing entries or insert new rows for the new tags. 1544 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program Show and hide table columns You can show or hide the columns in a table as needed. Procedure To show or hide table columns, follow these steps: 1. Click a column header. 2. Select the "Show/Hide" command in the shortcut menu. The selection of available columns is displayed. 3. To show a column, select the column's check box. 4. To hide a column, clear the column's check box. Editing tags with external editors To edit individual tags in external editors outside the TIA portal, you can export or import these tags using copy & paste. However, you cannot copy structured tags to an editor. Requirement The data block and an external editor are opened. Procedure To export and re-import individual tags by drag-and-drop operation, follow these steps: 1. Select one or more tags. 2. Select "Copy" in the shortcut menu. 3. Switch to the external editor and paste the copied tags. 4. Edit the tags as required. 5. Copy the tags in the external editor. 6. Switch back to the declaration table. 7. Select "Paste" in the shortcut menu. Monitoring data values online Monitoring data values in data blocks online You can monitor the current data values of the tags in the CPU directly in the declaration table. Requirement An online connection is available. The data block has been loaded to the CPU. WinCC Basic V13.0 System Manual, 02/2014 1545 Programming the PLC 9.1 Creating the user program The program execution is active (CPU in "RUN"). The data block is open. Procedure To monitor the data values, proceed as follows: 1. Start monitoring by clicking the "Monitor all" button. The additional "Monitor value" column is displayed in the table. This shows the current data values. See also: Structure of the declaration table for data blocks (Page 1525) 2. End the monitoring by clicking the "Monitor all" button again. Displaying data values loaded from the device During the loading of a data block from a device, the current tag values are also loaded. You can display these values. Requirement A data block was loaded from the device. Procedure To display the current values, follow these steps: 1. Open the data block. 2. Click a column header. 3. In the shortcut menu, select the "Show/hide columns" command. The selection of available columns is displayed. 4. Select the check box in the "Snapshot" column. Result The current values will be applied in the "Snapshot" column. Note If you subsequently change the structure of the data block, the display of the current values gets lost. The "Snapshot" column will then be empty. 1546 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program Setting data values during commissioning Basic information on adjusting data values during commissioning Introduction During commissioning of a plant, data values have to be frequently adjusted in order to optimally adapt the program to the general operating conditions on site. The declaration table for data blocks offers the following functions for this purpose: Initialize data values in "RUN" mode This function enables you to change data values online in order to quickly determine the optimum tag values. Transfer tag values from the online program to the offline program as start values When you have determined the optimum tag values, you can apply these as start values in the offline program. This allows you to ensure that the program starts with the optimized values the next time it is loaded. To use the function, first define specific tags as "Setting values" in the program. Setting values are the values that will probably have to be fine tuned during commissioning. Marking data as values that can be set You can mark specific tags in the program as "Setting values". Setting values are the values that will probably have to be fine tuned during commissioning. Rules You can mark tags as "Setting value" in the following block types: In function blocks (FB), but only in the "Static" section in global data blocks (DB) in PLC data types (UDT) In the case of PLC data types (UDT), however, the setting is only effective, if the UDT is used in the "Static" section of a function block or data block. It is not possible to define setting values in the following block types: In data blocks based on a PLC data type, and in instance data blocks. These inherit the setting from the higher-level FB or UDT. You cannot mark tags as a "Setting value" in ARRAY data blocks. You also cannot mark tags as a "Setting value" at the call point of a multi-instance. You have to make the setting in the interface of the function block that is called as multiple instance. You cannot change the "Setting value" marking in know-how-protected blocks. To do so, you must first remove the know-how protection. WinCC Basic V13.0 System Manual, 02/2014 1547 Programming the PLC 9.1 Creating the user program Requirement A function block, a global data block or a PLC data type (UDT) is open. Procedure To mark a tag as "Setting value", follow these steps: 1. Select a tag from the "Static" section. 2. Select the check box in the "Setting value" column. - You cannot define the higher-level element of a structure or a PLC data type as "Setting value". You have to make the setting for the lower-level elements individually. - In the case of ARRAYs, you can only mark the higher-level element as "Setting value". The lower-level elements inherit the setting. - For ARRAYs of STUCT, you can only mark the elements below the first structure as setting values. The elements of other structures inherit the setting. Result The tags are marked as setting values. During commissioning, these tags can be initialized online. You do not need to set the CPU to "STOP" mode; it can remain in "RUN". In addition, the current tag values can be transferred as start values to the offline program and saved there. Initializing setting values in the online program Basics on initializing setting values You can initialize all tags marked as a "Setting value" with new values in the online program. At the same time, the start values will be loaded from the offline program to the online program. The CPU remains in "RUN" mode. All tags that are marked as a setting value are initialized once at the next cycle control point. This applies both to retentive and non-retentive tags. The program execution is then continued with the new tag values. DANGER Danger when changing tag values Changing the tag values while the plant is operating can cause serious damage to property or injury to persons if there are functional disturbances or program errors! Make sure that no dangerous situations can arise before you re-initialize the setting values. Requirement An online connection to the CPU exists. The structure of the data block is identical offline and online. One or more tags are marked as a "Setting value". 1548 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program Procedure To initialize all setting values of the data block, follow these steps: 1. Open a global data block or an instance data block. 2. Enter the desired values in the "Start value" column. The start values must correspond to the indicated data type. 3. Click the "Initialize setting values" button. Result The setting values in the online program are initialized with the start values from the offline program at the next cycle control point. The maximum number of tags that can be initialized is dependent on the CPU. If too many setting values are marked, an alarm informs you about this. In this case, you can insert the tags in a watch table and initialize them using the "Modify" function in the watch table. Alternatively, you can also load the entire data block. For more information on this, refer to "See also". See also Loading changed values (Page 1535) Applying values from the online program as start values In order to apply tag values from the online program to the offline program as start values, first create a snapshot of the tag values from the online program. You can then apply them to the offline program. Note that the values from the snapshot are always copied. There is no check to determine whether all values originate from the same cycle. Write-protected start values are not overwritten. You have the following basic options for applying the values: Applying the values of an open data block You can apply all values or only the values of the tags marked as a "setting value" as start values in an open data block. Applying the values of multiple blocks in the project tree You can either apply all setting values or all retentive values as start values in the project tree. Requirement An online connection to the CPU is available. As least one data block has been loaded to the CPU. WinCC Basic V13.0 System Manual, 02/2014 1549 Programming the PLC 9.1 Creating the user program Procedure In order to apply all values or only the values of the tags marked as a "setting value" in a data block, follow these steps: 1. Open the data block. 2. Start monitoring by clicking the "Monitor all" button. The "Monitor value" column is displayed in the table. This shows the current data values. 3. On the toolbar, click "Snapshot of monitored values". The latest monitored values will be applied in the "Snapshot" column. 4. Click one of the following buttons on the toolbar: - "Apply setting values from the snapshot as start values" - "Apply all values from the snapshot as start values" The values from the "Snapshot" column are applied to the "Start value" column. To apply the monitored values of multiple data blocks in the project tree, follow these steps: 1. Select the blocks in the project tree. 2. Select the "Snapshot of the monitored values" command in the shortcut menu. The current monitored values of all selected blocks will be applied in the "Snapshot" column. An alarm is shown in the Inspector window after the operation is complete. 3. Then select one of the following commands in the shortcut menu: - "Apply monitor values as start values > Only setpoints" - "Apply monitor values as start values > Only retain values" The values from the "Snapshot" column are applied to the "Start value" column. Result The new start values are stored in the offline program. Note Applying values of individual tags You can also transfer the values of individual tags that were not marked as a setting value beforehand from the "Snapshot" column to the "Start values" column. Use the "Copy" and "Paste" commands from the shortcut menu to copy the values and insert them in the "Start value" column. Note that only the values that are currently located in the visible area of the table are copied. See also Basic information on start values (Page 1533) Define start values (Page 1534) 1550 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program 9.1.4.4 Programming PLC data types Basics of PLC data types Description PLC data types are data structures that you define and that can be used multiple times within the program. The structure of a PLC is made up of several components, each of which can contain different data types. You define the type of components during the declaration of the PLC data type. You can create up to 65534 PLC data types for a CPU of the S7-1200 or S7-1500 series. Each of these PLC data types can include up to 252 components. PLC data types can be used for the following applications: PLC data types can be used as data types for variables in the variable declaration of logic blocks or in data blocks. PLC data types can be used as templates for the creation of global data blocks with identical data structures. PLC data types can be used in S7-1200 and S7-1500 as a template for the creation of structured PLC tags. See also Creating PLC data types (Page 1552) Structure of the declaration table for PLC data types Structure of the declaration table for PLC data types The figure below shows the structure of the declaration table for PLC data types. WinCC Basic V13.0 System Manual, 02/2014 1551 Programming the PLC 9.1 Creating the user program Meaning of the columns The following table shows the meaning of the individual columns. You can show or hide the columns as required. The number of columns displayed varies depending on the CPU series. Column Explanation Symbol you can click to move or copy the tag. Name Name of the tags. Data type Data type of the tags. Default value Value with which you predefine the tag in the declaration of the PLC data type. Specification of the default value is optional. If you do not specify any value the predefined value for the indicated data type is used. For example, the value "false" is predefined for BOOL. Visible in HMI Shows whether the tag is visible by default in the HMI selection list. Accessible from HMI Shows whether HMI can access this tag during runtime. Setting value Setting values are the values that will probably have to be fine tuned during commissioning. After commissioning, the values of these tags can be transferred to the offline program as start values and stored there. Comment Comment to document the tags. See also Creating PLC data types (Page 1552) Show and hide table columns (Page 1559) Creating PLC data types Requirement The "PLC data types" folder opens in the project tree. Procedure To create a PLC data type, proceed as follows: 1. In the "PLC data types" folder, click the "Add new data type" command. A new declaration table for creating a PLC data type will be created and opened. 2. Select the PLC data type and select the "Rename" command in the shortcut menu. 3. Enter the name of the PLC data type. Result The new PLC data type is created. You can find the PLC data type in the project tree in the "PLC data types" folder. 1552 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program See also Structure of the declaration table for PLC data types (Page 1551) Basics of PLC data types (Page 1551) Delete PLC data types Requirement The PLC data type you want to delete is not open. Procedure To delete a PLC data type, follow these steps: 1. In the project tree, open the "PLC data types" folder. 2. Select the PLC data type to be deleted. You can also select several PLC data types by clicking on them one after the other while holding down the <Ctrl> key or by pressing and holding down <Shift> and clicking on the first and last data type. 3. Select the "Delete" command in the shortcut menu. Note If you delete a PLC data type, the blocks that use the data type will become inconsistent. These inconsistencies are marked in red in the block used. To remedy these inconsistencies, the data blocks have to be updated. See also: Updating the block interface (Page 1387) Updating data blocks (Page 1528) Programming the structure of PLC data types Declaring tags of elementary data type Requirement A PLC data type is open. WinCC Basic V13.0 System Manual, 02/2014 1553 Programming the PLC 9.1 Creating the user program Procedure To declare a tag, follow these steps: 1. Enter a tag name in the "Name" column. 2. Enter the required data type in the "Data type" column. You will be supported by autocompletion during input. 3. Optional: Change the properties of the tags that are displayed in the other columns. 4. Repeat steps 1 to 3 for all tags that are to be declared. See also Editing tables (Page 226) Declaring tags of the ARRAY data type Requirement A PLC data type is open. Procedure To declare a tag of the ARRAY data type, follow these steps: 1. Enter a tag name in the "Name" column. 2. Enter the "Array" data type in the "Data type" column. You will be supported by autocompletion in this step. The "Array" dialog opens. 3. In the "Data type" text box, specify the data type of the array elements. 4. In the "ARRAY limits" text box, specify the high and low limit for each dimension. Example of a one-dimensional ARRAY: [0..3] Example of a three-dimensional ARRAY: [0..3, 0..15, 0..33] 5. Confirm your entry. 6. Optional: Change the properties of the tags that are displayed in the other columns. Note You cannot define specific default values for ARRAY elements. You can, however, assign them start values at the usage point in the data block. See also Structure of the declaration table for PLC data types (Page 1551) 1554 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program Declaring tags of STRUCT data type Requirements A PLC data type is open. Procedure To declare a tag of the STRUCT data type, follow these steps: 1. Enter a tag name in the "Name" column. 2. Enter "Struct" in the "Data type" column. You will be supported by autocompletion during input. An empty, indented row is inserted after the new tag. 3. Insert the first structural element in the first empty row. An additional empty row is inserted after the element. 4. Select a data type for the structure element. 5. Optional: Change the properties of the structural element that is displayed in the other columns. 6. Repeat steps 3 to 5 for all additional structure elements. It is not necessary to end the structure explicitly. The structure ends with the last element that is entered. 7. To insert a new tag after the structure, leave a blank row after the end of the structure and then start the new tag in the second empty row. Result The tag of STRUCT data type is created. See also STRUCT (Page 1239) Structure of the declaration table for PLC data types (Page 1551) Declaring tags based on a different PLC data type Requirements A global data block is open. A PLC data type is declared in the current CPU. WinCC Basic V13.0 System Manual, 02/2014 1555 Programming the PLC 9.1 Creating the user program Procedure To declare a tag based on a different PLC data type, follow these steps: 1. Enter a tag name in the "Name" column. 2. Enter the PLC data type in the "Data type" column. You will be supported by autocompletion during input. Result The tag is created. Note You define the default values of tags within a PLC data type when the PLC data type is created. You cannot change these values at the point of use of the PLC data type. See also Basics of PLC data types (Page 1551) Structure of the declaration table for PLC data types (Page 1551) Editing tag properties in PLC data types Properties of tags in PLC data types Properties The following table gives an overview of tag properties in PLC data types: Group Property Description General Name Name of the tags. Data type Data type of the tags. Default value Default value of the tag in the interface of a higher-level code block or in a PLC data type. The values contained in the "Default value" column can only be changed in the higher-level code block or PLC data type. The values are only displayed in the data block. Attributes 1556 Start value Not relevant in PLC data types Comment Comment on the tag. Retain Not relevant in PLC data types Visible Indicates whether a parameter is visible in CFC. Configurable Indicates whether a parameter is configurable in CFC. WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program Group Property Description For test Indicates whether a parameter is registered for the CFC test mode. Interconnectable Indicates whether a parameter is interconnectable in CFC. See also Changing the properties of tags in PLC data types (Page 1557) Basics of PLC data types (Page 1551) Structure of the declaration table for PLC data types (Page 1551) Changing the properties of tags in PLC data types Editing general properties in the declaration table To edit the general properties of one or more tags, follow these steps: 1. Open the PLC data type. 2. Change the entries in the columns. Editing detailed properties in the properties window To edit the detailed properties of an individual tag, follow these steps: 1. Select a tag in the table. 2. Select the "Properties" command in the shortcut menu. The inspector window shows the properties of the tag in the "General" and "Attributes" areas. 3. Select the required area in the area navigation. 4. Change the entries in the text boxes. See also Updating the block interface (Page 1387) Updating data blocks (Page 1528) WinCC Basic V13.0 System Manual, 02/2014 1557 Programming the PLC 9.1 Creating the user program Editing the declaration table for PLC data types Inserting table rows Procedure Proceed as follows to insert a row above the selected row: 1. Select the row in front of which you want to insert a new row. 2. Click the "Insert row" button on the toolbar of the table. Result A new row is inserted above the selected row. Inserting table rows Procedure Proceed as follows to insert a row below the selected row: 1. Select the row below which you want to insert a new row. 2. Click the "Add row" button on the table toolbar. Result A new empty row will be inserted below the selected row. Deleting tags Procedure Follow the steps below to delete elements: 1. Select the row with the element to be deleted. You can also select several rows by clicking on them one after the other while holding down the <Ctrl> key or by pressing and holding down <Shift> and clicking on the first and last row. 2. Select the "Delete" command in the shortcut menu. See also Updating the block interface (Page 1387) Updating data blocks (Page 1528) 1558 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program Automatically filling in successive cells You can load the contents of one or several table cells into the cells below, automatically filling in the successive cells. If you automatically fill in cells in the "Name" column, a consecutive number will be appended to each name. For example, "Motor" will become "Motor_1". You can define individual or more cells as well as entire rows as source area. If less rows exist in the open table than you want to fill, then you will first have to insert additional empty rows. Requirement The table is open. Sufficient declaration rows are available. Procedure To automatically fill in successive cells, follow these steps: 1. Select the cells to be loaded. 2. Click the "Fill" symbol in the bottom right corner of the cell. The mouse pointer is transformed into a crosshair. 3. Keep the mouse button pressed and drag the mouse pointer downwards over the cells that you want to fill in automatically. 4. Release the mouse button. The cells are filled in automatically. 5. If entries are already present in the cells that are to be automatically filled in, a dialog appears. In this dialog you can indicate whether you want to overwrite the existing entries or insert new rows for the new tags. Show and hide table columns You can show or hide the columns in a table as needed. Procedure To show or hide table columns, follow these steps: 1. Click a column header. 2. Select the "Show/Hide" command in the shortcut menu. The selection of available columns is displayed. 3. To show a column, select the column's check box. 4. To hide a column, clear the column's check box. WinCC Basic V13.0 System Manual, 02/2014 1559 Programming the PLC 9.1 Creating the user program 9.1.4.5 Using external source files Basics of using external source files Function The textual programming languages STL and SCL allow you to enter the program code in any ASCII editor and save it as an external source file. This enables you to perform a range of tasks, for example: Declaring tags Specify block properties Programming blocks You can import these source files to your project and use them to generate blocks. You can generate a number of different blocks from one source file. Observe the following special features when generating blocks from a source file: A block that exists under the same name in the project will be overwritten. Always name organization blocks according to their type, e.g., "Main" or "Cyclic interrupt" so that the event assignment is retained. If you are using multiple organization blocks of the same type, you can add underscores and numbers to the name, e.g., "Main_2" or "Main_2_1". If a block was programmed with its absolute block number instead of a symbolic name in the source file and this number is already assigned by a block in the project, the new generated block is initially assigned the next free symbolic name. If you have not explicitly defined the access mode for a block in the external source file, the block access mode is set depending on the CPU series used: - Blocks generated for a CPU of the S7-1200/1500 series are assigned "optimized" access mode by default. - Blocks generated for a CPU of the S7-300/400 product range are assigned "standard" access mode by default. Organization blocks are the exception in this case, as they are always assigned the "standard" access mode by default, regardless of the CPU series. You have the option of changing the block access mode manually. It is possible that not all comments from the source file will be applied in the block. If you use absolute addressing in the external source file, a symbolic tag is created for each absolute address during the generation of the block. The names of these tags are made up of "Tag_" and a time stamp. This may result in relatively long tag names, which you can change manually if required. If you are using instructions in a different version in the external source file than in the target device, this may result in compilation errors. Correct the respective instructions in this case and start the compilation process once again. You can also select a different version for the target device. You also have the option of saving existing blocks as external source files. 1560 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program See also Rules for programming external source files (Page 1561) Saving blocks as external source files (Page 1562) Inserting external source files (Page 1563) Opening and editing external source files (Page 1563) Generating blocks from external source files (Page 1564) Rules for programming external source files An external source file basically consists of continuous text. To compile the source into blocks, certain structures and syntax rules must however be adhered to. Syntax rules The syntax of the instructions in external source files is very similar to that in the creation of user programs in the program editor with STL or SCL. Note, however, the following additional syntax rules: Block call When calling a block, transfer the parameters in the defined order in the ASCII editor. If you do not, the comment assignments for these lines may not match. Enter the parameters in brackets. The individual parameters are separated by a comma. Upper or lower case The program editor generally disregards upper or lower case. Jump labels are an exception to this. Character string entries are also case-sensitive ("STRING" data type). Keywords are displayed in upper case. For compilation purposes, however, case is disregarded; you can therefore specify keywords in upper or lower case or a mixture of the two. Semicolon Mark the end of every instruction and every tag declaration with a semicolon. You can enter several instructions per line. Forward slashes Begin every comment with two forward slashes (//) and end the comment with the <Enter> key. See also Basics of using external source files (Page 1560) Saving blocks as external source files (Page 1562) Inserting external source files (Page 1563) Opening and editing external source files (Page 1563) Generating blocks from external source files (Page 1564) WinCC Basic V13.0 System Manual, 02/2014 1561 Programming the PLC 9.1 Creating the user program Saving blocks as external source files Depending on the programming language used for the block, you have the following options for storing blocks as external source files: STL and SCL: copy a block as text SCL: generate external source file from one or more blocks Copying a block as text To copy a block as text and export it to an external source file, follow these steps: 1. In the project tree, right-click on the block you want to export to an external source file. 2. Select the "Copy as text" command in the shortcut menu. 3. Open an external text editor. 4. Paste the copied text from the clipboard. 5. Save the file with one of the following file name extensions: - ".scl" if you wish to generate a source file for SCL - ".stl" if you wish to generate a source file for STL Generating an external source file from SCL blocks To generate an external source file from SCL blocks, follow these steps: 1. In the project tree or in the overview window, select the SCL blocks from which you want to generate an external source file. 2. Select the "Generate source from blocks" command from the shortcut menu. The "Generate source from blocks" dialog opens. 3. Specify a path and a name for the external source. 4. Click "OK". You can also generate an external source file from an open SCL block. To do this, follow these steps: 1. Click on the "Generate source from block" button in the programming editor. The "Generate source from blocks" dialog opens. 2. Specify a path and a name for the external source. 3. Click "OK". Result The block has been saved as an external source file. You can include this source file in a project in the TIA portal and use it to generate other blocks. However, please note that you can use STL source files only in S7-300/400/1500 CPUs. 1562 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program See also Basics of using external source files (Page 1560) Rules for programming external source files (Page 1561) Inserting external source files (Page 1563) Opening and editing external source files (Page 1563) Generating blocks from external source files (Page 1564) Inserting external source files Requirement An external source file is available and complies with the syntax and structure rules. The "External source files" folder is open in the project tree. Procedure Follow these steps to insert an external source file: 1. Double-click on the "Add new external file" command. The "Open" dialog box is opened. 2. Navigate to and select existing external source files. 3. Confirm your selection with "Open". Result The new source file will be added to the "External source files" folder. See also Basics of using external source files (Page 1560) Rules for programming external source files (Page 1561) Saving blocks as external source files (Page 1562) Opening and editing external source files (Page 1563) Generating blocks from external source files (Page 1564) Opening and editing external source files By linking the files with the file name extensions "stl" and "scl" to an editor you will be able to open and edit external source files with these formats directly. Use Notepad as editor because other text editors may not let you open several sources at the same time. This means you do not need to insert the external source files again after editing. WinCC Basic V13.0 System Manual, 02/2014 1563 Programming the PLC 9.1 Creating the user program Linking files with the file name extensions "stl" and "scl" file types to an editor Proceed as follows to link files with the file name extensions "stl" and "scl" to an editor: 1. Open Windows Explorer. 2. Right-click on an STL file. 3. Select "Properties" in the shortcut menu. The "Properties" dialog box opens. 4. Click "Change" in the "File type" area on the "General" tab. The "Open with" dialog box opens. 5. Select the text editor you want to link to the "stl" file type. 6. Confirm your selection with "OK". 7. Close the "Properties" dialog with "OK". 8. Repeat steps 2 to 7 with an SCL file. Opening and editing an external source file To open an external source file, follow these steps: 1. Open the "External source files" folder in the project tree. 2. Double-click on the external source file you want to open. The external source file will open in the linked editor and can be edited. See also Basics of using external source files (Page 1560) Rules for programming external source files (Page 1561) Saving blocks as external source files (Page 1562) Inserting external source files (Page 1563) Generating blocks from external source files (Page 1564) Generating blocks from external source files Requirement The "External source files" folder is open in the project tree. An external source file is available. Procedure To generate blocks from an external source file, follow these steps: 1. Open the external source file from which you wish to generate blocks. 2. Select the "Generate blocks from source" command in the "Edit" menu. 1564 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program 3. A prompt will appear telling you any existing blocks will be overwritten. 4. Confirm the safety prompt with "Yes". Result The external source file blocks will be generated and inserted in the "Program blocks" folder in the project tree. In the event of errors, information about the errors which have occurred will be displayed in the inspector window. This information, however, relates to the external source file and not to the block generated. See also Basics of using external source files (Page 1560) Rules for programming external source files (Page 1561) Saving blocks as external source files (Page 1562) Inserting external source files (Page 1563) Opening and editing external source files (Page 1563) 9.1.5 Comparing PLC programs 9.1.5.1 Basic information on comparing PLC programs Introduction to comparing PLC programs Function You can compare the following objects of a PLC program in order to detect any differences: Code blocks with other code blocks Data blocks with other data blocks PLC tags of a PLC tag table with the PLC tags of another PLC tag table PLC data types with other PLC data types WinCC Basic V13.0 System Manual, 02/2014 1565 Programming the PLC 9.1 Creating the user program Types and levels of comparison Two different basic types of comparison can be used: Online/offline comparison: The objects in the project are compared with the objects of the corresponding device. An online connection to the device is necessary for this comparison. Offline/offline comparison: The objects of two devices either within a project or from different projects or libraries are compared. No online connection is required for this comparison. Please note that you cannot carry out an unlimited number of comparisons at the same time, but only one comparison per comparison type (online/offline or offline/offline). You can choose between the following levels of comparison depending on how in-depth an object comparison you require: Compare editor Detailed comparison When you start a comparison, you will first receive an overview in the compare editor. For some comparison objects, you can then start a detailed comparison in which the objects compared will be opened side-by-side, each in its own program editor instance. Any differences will be highlighted. The table below gives an overview of the types and levels of comparison you can apply for each object: Object Online/offline Compare editor Detailed comparison Compare editor Detailed comparison LAD block X X X X FBD block X X X X STL block X X X X SCL block X X X X GRAPH block2 X X4 X X5 Global data block X X X X Instance data block X X X X PLC tags - - X X PLC data type X4 X4 X X 1 Offline/offline 34 Legend: X: available -: not available : STL is not available for S7-1200 1 : GRAPH is not available for S7-1200 2 : not for S7-1200 prior to version 2.0 3 : not for S7-300/400 4 : only comparable with a GRAPH block from the same CPU family 5 1566 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program Note Please note the following: You cannot perform a detailed comparison for know-how protected blocks. If the detail comparison detects differences only with respect to the data types of local tags, with offline being an interrupt data type (C_ALARM C_ALARM_S C_ALARM_8 C_ALARM_8P C_ALARM_T C_AR_SEND C_NOTIFY C_NOTIFY_8P) and online a DWORD, this difference is not marked as such. You cannot run a detailed comparison for types and master copies from libraries. See also Basics of project data comparison (Page 273) Comparison of code blocks (Page 1567) Comparison of data blocks (Page 1568) Comparing PLC tags and PLC data types (Page 1569) Carrying out an online/offline comparison (Page 274) Carrying out offline/offline comparisons (Page 274) Using the compare editor (Page 275) Comparison of code blocks Introduction The blocks to be compared in a code block comparison are assigned for comparison on the basis of the following criteria: Online/offline comparison: Addresses, e.g. FB100 Offline/offline comparison: Symbolic names of the blocks The comparison involves an evaluation of the block time stamps. The results are displayed as an overview in the comparison editor. You can then use actions to define what is to be done about the differences. You can also start detailed comparisons for the individual blocks. The versions of a block compared are opened beside each other and the differences are highlighted. For the comparison of code blocks, both the block interfaces and the individual networks are compared. Any differing tag names are also determined. All comments and other block attributes are excluded from an online/offline comparison. If the block interface changes, the time stamp of the code block interface will also change. This change means a change in the time stamp of the program code. The first step in comparing block interfaces is therefore a comparison of the program code time stamps. If these time stamps are the same, it is assumed that the interfaces are the same. If the time stamps of the interfaces differ, the next step is to compare the data types of the interfaces, section by section. WinCC Basic V13.0 System Manual, 02/2014 1567 Programming the PLC 9.1 Creating the user program Multiple instances and PLC data types are included in the comparison. If the data types in the sections are the same, the start values of the tags are compared. All differences are displayed. When networks are compared, first inserted or deleted networks are detected. Then the other networks are compared. Instructions are the same if the operator and operand are the same. The first difference in each instruction is displayed. However, several differences per network can be displayed. See also Introduction to comparing PLC programs (Page 1565) Comparison of data blocks (Page 1568) Comparing PLC tags and PLC data types (Page 1569) Carrying out an online/offline comparison (Page 274) Carrying out offline/offline comparisons (Page 274) Using the compare editor (Page 275) Comparison of data blocks Introduction The blocks to be compared in a data block comparison are assigned for comparison on the basis of the following criteria: Online/offline comparison: Addresses, e.g. DB100 Offline/offline comparison: Symbolic names of the blocks The first step in data block comparison is comparing the time stamps of the data block. If these time stamps are the same, it is assumed that the data structures are the same. If the time stamps differ, the structures are then compared until the first difference is found. If the data structures in the sections are the same, the initial and current values of the tags are then compared. All differences are displayed. Any differing tag names are also determined. Comments and PLC data type structures used in the data block are not included in the comparison. See also Introduction to comparing PLC programs (Page 1565) Comparison of code blocks (Page 1567) Comparing PLC tags and PLC data types (Page 1569) Carrying out an online/offline comparison (Page 274) Carrying out offline/offline comparisons (Page 274) Using the compare editor (Page 275) 1568 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program Comparing PLC tags and PLC data types Introduction The device PLC tag tables and the device PLC data types will also be shown in the comparison editor if you carry out an offline/offline comparison. The PLC tag tables and the PLC data types will be matched by name and you will receive the following information: Status: A symbol shows whether the PLC tags/PLC data types are identical or differ. Missing PLC tag tables / PLC data types: You can see at a glance whether the PLC tag tables / PLC data types are available in both devices. You obtain the following information with an online/offline comparison of CPUs of the S7-1200/1500 series: PLC tags: A symbol shows whether the PLC tags are identical or differ. Because PLC tag tables are not downloaded to the device during loading, they cannot be displayed during an online/offline comparison. PLC data types: You receive the status symbol for each PLC data type. You can see at a glance whether the PLC data types are available in both devices. See also Introduction to comparing PLC programs (Page 1565) Comparison of code blocks (Page 1567) Comparison of data blocks (Page 1568) Carrying out an online/offline comparison (Page 274) Carrying out offline/offline comparisons (Page 274) Using the compare editor (Page 275) 9.1.5.2 Comparing blocks Comparing blocks in the compare editor You have the following options for comparing blocks in the compare editor: Online/offline comparison The blocks in the project are compared with the blocks of the selected device. Automatic offline/offline comparison All blocks of the selected devices are compared offline. Manual offline/offline comparison The selected blocks of the devices are compared offline. WinCC Basic V13.0 System Manual, 02/2014 1569 Programming the PLC 9.1 Creating the user program Carrying out an online/offline comparison of blocks To perform an online/offline comparison, follow these steps: 1. In the project tree, select a device that allows online/offline comparison. 2. Select the "Compare > Offline/online" command in the shortcut menu. 3. If you have not already established an online connection to this device, the "Go online" dialog opens. In this case, set all the necessary parameters for the connection and click "Connect". The online connection is established and the compare editor opens. 4. Open the "Program blocks" folder. You can identify the status based on the symbols in the status and action area. You can define certain actions depending on the status of the objects. Note, however, that you can only perform actions in one direction in a synchronization action. Carrying out an automatic offline/offline comparison of blocks To perform an automatic offline/offline comparison of blocks, follow these steps: 1. Select a device in the project tree that allows offline/offline comparison. 2. Select the "Compare > Offline/offline" command in the shortcut menu. The compare editor opens and the selected device is displayed in the left area. 3. Drag-and-drop an additional device to the drop area of the right pane. The device to be compared can originate from the same project, a reference project or the library. 4. Open the "Program blocks" folder. You can identify the status of the objects based on the symbols in the status and action area. You can define certain actions depending on the status of the objects. When you select an object, the object's properties and the corresponding object of the assigned device are clearly shown in the properties comparison. You can drag any other device to the drop area at any time to perform further comparisons. Carrying out a manual offline/offline comparison of blocks To perform a manual offline/offline comparison of blocks, follow these steps: 1. Select a device in the project tree that allows offline/offline comparison. 2. Select the "Compare > Offline/offline" command in the shortcut menu. The compare editor opens and the selected device is displayed in the left area. 3. Drag-and-drop an additional device to the drop area of the right pane. The device to be compared can originate from the same project, a reference project or the library. 4. In the status and action area, click on the button for switching between automatic and manual comparison. 5. Select the objects that you want to compare. The properties comparison is displayed. You can identify the status of the objects based on the symbols. You can define certain actions depending on the status of the objects. You can drag any other device to the drop area at any time to perform further comparisons. 1570 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program See also Introduction to comparing PLC programs (Page 1565) Using the compare editor (Page 275) Comparing PLC tags (Page 1591) Comparing PLC data types (Page 1592) Performing detailed block comparisons Starting a detailed comparison You can start a detailed comparison for blocks. The versions of a block compared are opened beside each other and the differences highlighted. Note Please note the following: For blocks that are created in the programming language SCL, the detail comparison is not available for S7-1200 series CPUs with a version older than 2.0. You can only start the detailed comparison with the compare editor for blocks created in the GRAPH programming language. Starting detailed comparisons using the compare editor To start a detailed comparison for a block using the compare editor, follow these steps: 1. First, perform an online/offline or an offline/offline comparison. The compare editor opens. 2. In the compare editor, select the block for which you want to perform a detailed comparison. 3. Click the "Start detailed comparison" button in the toolbar. Starting detailed comparisons in the program editor For the comparison type online/offline, you can start the detailed comparison directly in the programming editor. To do this, follow these steps: 1. Open the block for which you wish to carry out a detailed comparison. 2. Establish an online connection. See also: Go online and Go offline Note Please note that the block must be available online in order for you to be able to start the detailed comparison for the block within the programming editor. WinCC Basic V13.0 System Manual, 02/2014 1571 Programming the PLC 9.1 Creating the user program 3. Click the "Detailed comparison" button in the toolbar. 4. Confirm the dialog for closing the block with "Yes". Result One instance of the program editor will be opened for each version of the block compared and the two instances are displayed side by side. Any differences will be highlighted. If there are structural differences for GRAPH blocks, the comparison results are only displayed up to the first structural difference in the sequence view. See also Carrying out offline/offline comparisons (Page 274) Carrying out an online/offline comparison (Page 274) Using the compare editor (Page 275) Visualization of the comparison result for LAD/FBD (Page 1572) Navigating in the detailed comparison (Page 1588) Changing blocks during detailed comparison (Page 1589) Updating comparison results (Page 1590) Visualization of the comparison result Visualization of the comparison result for LAD/FBD Introduction The detailed comparison allows you to identify the exact places where versions of a block differ. The following color coding allows you to find these places as quickly as possible: The lines where there are differences are highlighted in gray. Differing operands and instructions are highlighted in green. If the number of networks differs, pseudo-networks are added to allow the display of identical networks to be synchronized. These pseudo-networks are highlighted in gray and contain the text "No corresponding network found" in the title bar of the network. Pseudonetworks cannot be edited. For the sake of clarity, not all the differences are highlighted but rather the first difference of an operation in each case. For example, if all the inputs in an instruction with multiple inputs are different in the offline and online versions of the block, only the first input is highlighted as a difference. You can resolve this difference and update the comparison list. The next input will then be highlighted as a difference. The number of differences highlighted within a network therefore depends on the number of instructions. 1572 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program Structure of the detailed comparison The following figure shows an example of the online/offline detailed comparison for the LAD programming language: Toolbar of the detailed comparison for LAD Reference block Compared block Comparison result in the Inspector window The following figure shows an example of the online/offline detailed comparison for the FBD programming language: WinCC Basic V13.0 System Manual, 02/2014 1573 Programming the PLC 9.1 Creating the user program Toolbar of the detailed comparison for FBD Reference block Compared block Comparison result in the Inspector window Note Display of the symbolic names of the online version of the block is only possible for S7-1200 and S7-1500. 1574 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program Toolbar of the detailed comparison With the toolbar, you can access the following functions: General functions - Insert network - Delete network - Insert row - Add row - Open all networks - Close all networks Comparison-specific functions - Position on first difference - Position on previous difference - Position on next difference - Position on last difference - Synchronize scrolling between editors - Update comparison results Reference block The reference block is displayed in the left window. In an online/offline comparison, the reference block is the offline version of the block. Compared block The compared block is displayed in the right window. In an online/offline comparison, the compared block is the online version of the block. Comparison result in the Inspector window The differences are displayed in the form of a table in the "Info > Comparison result" tab of the Inspector window. Double-click on a row to navigate to the corresponding difference in the block. See also Carrying out an online/offline comparison (Page 274) Carrying out offline/offline comparisons (Page 274) Using the compare editor (Page 275) Starting a detailed comparison (Page 1571) Navigating in the detailed comparison (Page 1588) WinCC Basic V13.0 System Manual, 02/2014 1575 Programming the PLC 9.1 Creating the user program Changing blocks during detailed comparison (Page 1589) Updating comparison results (Page 1590) Visualization of the comparison result for STL Introduction The detailed comparison allows you to identify the exact places where versions of a block differ. The following color coding allows you to find these places as quickly as possible: The lines where there are differences are highlighted in gray. Differing operands and instructions are highlighted in green. If the number of networks differs, pseudo-networks are added to allow the display of identical networks to be synchronized. These pseudo-networks are highlighted in gray and contain the text "No corresponding network found" in the title bar of the network. Pseudonetworks cannot be edited. 1576 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program Structure of the detailed comparison The following figure shows an example of the online/offline detailed comparison for the STL programming language: Toolbar of the detailed comparison for STL Reference block Compared block Comparison result in the Inspector window Note The display of the symbolic names of the online version of the block is only possible for S7-1500. WinCC Basic V13.0 System Manual, 02/2014 1577 Programming the PLC 9.1 Creating the user program Toolbar of the detailed comparison With the toolbar, you can access the following functions: General functions - Insert network - Delete network - Insert row - Add row - Open all networks - Close all networks Comparison-specific functions - Position on first difference - Position on previous difference - Position on next difference - Position on last difference - Synchronize scrolling between editors - Update comparison results Reference block The reference block is displayed in the left window. In an online/offline comparison, the reference block is the offline version of the block. Compared block The compared block is displayed in the right window. In an online/offline comparison, the compared block is the online version of the block. Comparison result in the Inspector window The differences are displayed in the form of a table in the "Info > Comparison result" tab of the Inspector window. Double-click on a row to navigate to the corresponding difference in the block. See also Carrying out an online/offline comparison (Page 274) Carrying out offline/offline comparisons (Page 274) Using the compare editor (Page 275) Starting a detailed comparison (Page 1571) Navigating in the detailed comparison (Page 1588) 1578 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program Changing blocks during detailed comparison (Page 1589) Updating comparison results (Page 1590) Visualization of the comparison result for SCL Introduction The detailed comparison allows you to identify the exact places where versions of a block differ. The following color coding allows you to find these places as quickly as possible: The lines where there are differences are highlighted in gray. Differing operands and instructions are highlighted in green. Note The online/offline detailed comparison is not available for the CPU families S7-300/400 and for S7-1200 with a version less than 2.0. WinCC Basic V13.0 System Manual, 02/2014 1579 Programming the PLC 9.1 Creating the user program Structure of the detailed comparison The following figure shows an example of the online/offline detailed comparison for the SCL programming language: Toolbar of the detailed comparison for SCL Reference block Compared block Comparison result in the Inspector window Note The display of the symbolic name of the online version of the block is only possible for S7-1200 and S7-1500. 1580 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program Toolbar of the detailed comparison With the toolbar, you can access the following functions: General functions - Insert row - Add row Comparison-specific functions - Position on first difference - Position on previous difference - Position on next difference - Position on last difference - Synchronize scrolling between editors - Update comparison results Reference block The reference block is displayed in the left window. In an online/offline comparison, the reference block is the offline version of the block. Compared block The compared block is displayed in the right window. In an online/offline comparison, the compared block is the online version of the block. Comparison result in the Inspector window The differences are displayed in the form of a table in the "Info > Comparison result" tab of the Inspector window. Double-click on a row to navigate to the corresponding difference in the block. See also Carrying out an online/offline comparison (Page 274) Carrying out offline/offline comparisons (Page 274) Using the compare editor (Page 275) Starting a detailed comparison (Page 1571) Navigating in the detailed comparison (Page 1588) Changing blocks during detailed comparison (Page 1589) Updating comparison results (Page 1590) WinCC Basic V13.0 System Manual, 02/2014 1581 Programming the PLC 9.1 Creating the user program Visualization of the comparison result for GRAPH Introduction The detailed comparison allows you to identify the exact places where versions of a block differ. When you start a detailed comparison for a GRAPH block, navigation is opened first. Use the dividers to toggle between the navigation and the currently set view. You can select other views with the toolbar of the detailed comparison. The result of the comparison is indicated by the comparison symbols. See also: Overview of the comparison editor (Page 275) Structure of the detailed comparison The following figure shows an example for the navigation view with an online/offline detailed comparison for the GRAPH programming language: 1582 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program Toolbar of the detailed comparison for GRAPH Reference block Compared block Navigation toolbar Dividers Comparison result in the Inspector window The following figure shows an example for the sequence view with an online/offline detailed comparison for the GRAPH programming language: Toolbar of the detailed comparison for GRAPH Reference block Compared block Dividers WinCC Basic V13.0 System Manual, 02/2014 1583 Programming the PLC 9.1 Creating the user program Comparison result in the Inspector window Note If there are structural differences between the blocks, the comparison results are only displayed up to the first structural difference in the sequence view. The following figure shows an example for the single step view with an online/offline detailed comparison for the GRAPH programming language: Toolbar of the detailed comparison for GRAPH Reference block Compared block Dividers 1584 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program Comparison result in the Inspector window Note The result of the comparison refers to the complete network Differences within the networks are not identified. The following figure shows an example for the view of permanent instructions with an online/ offline detailed comparison for the GRAPH programming language: Toolbar of the detailed comparison for GRAPH Reference block Compared block Dividers WinCC Basic V13.0 System Manual, 02/2014 1585 Programming the PLC 9.1 Creating the user program Comparison result in the Inspector window Note The result of the comparison refers to the complete network Differences within the networks are not identified. The following figure shows an example for the alarm view with an online/offline detailed comparison for the GRAPH programming language: Toolbar of the detailed comparison for GRAPH Reference block Compared block Dividers Comparison result in the Inspector window 1586 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program Toolbars With the toolbar of the detailed comparison, you can access the following functions: General functions - Change to permanent pre-instructions - Change to sequence view - Change to single step view - Change to permanent post-instructions - Change to alarm view - Open all networks - Close all networks Comparison-specific functions - Position on first difference - Position on previous difference - Position on next difference - Position on last difference - Synchronize scrolling between editors - Update comparison results The navigation has its own toolbar with the following functions: Zoom in or zoom out of elements within the navigation Synchronize navigation Reference block The reference block is displayed in the left window. In an online/offline comparison, the reference block is the offline version of the block. Compared block The compared block is displayed in the right window. In an online/offline comparison, the compared block is the online version of the block. Dividers You can click the dividers to toggle quickly between the navigation and the current view. Comparison result in the Inspector window The differences are displayed in the form of a table in the "Info > Comparison result" tab of the Inspector window. Double-click on a row to navigate to the corresponding difference in the block. WinCC Basic V13.0 System Manual, 02/2014 1587 Programming the PLC 9.1 Creating the user program See also Carrying out an online/offline comparison (Page 274) Carrying out offline/offline comparisons (Page 274) Using the compare editor (Page 275) Starting a detailed comparison (Page 1571) Navigating in the detailed comparison (Page 1588) Changing blocks during detailed comparison (Page 1589) Updating comparison results (Page 1590) Navigating in the detailed comparison Requirement You have run a detailed comparison. Navigate to the differences To navigate to a difference between the two blocks, follow these steps: 1. Open the list of results for the detailed comparison under "Info > Comparison result" in the Inspector window. 2. Double-click a difference. The difference is selected in both editors. Or: 1588 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program 1. Click one of the following navigation buttons on the toolbar: - Position on first difference Navigates to the first difference in the block, and displays the difference in both editors. - Position on previous difference Navigates to the previous difference starting from the current position, and displays the difference in both editors. - Position on next difference Navigates to the next difference starting from the current position, and displays the difference in both editors. - Position on last difference Navigates to the last difference in the block, and displays the difference in both editors. Switching off/on the synchronization of the vertical scrolling between the editors The scrolling for both editors is synchronized to ensure that the corresponding networks are visible parallel to each other during vertical scrolling. You can switch this mode off and on. To do this, follow these steps: 1. To switch off synchronized scrolling, click the "Synchronize scrolling between editors" button in the toolbar. 2. To switch on synchronized scrolling again, click the "Synchronize scrolling between editors" button one more time in the toolbar. See also Carrying out an online/offline comparison (Page 274) Carrying out offline/offline comparisons (Page 274) Using the compare editor (Page 275) Starting a detailed comparison (Page 1571) Visualization of the comparison result for LAD/FBD (Page 1572) Changing blocks during detailed comparison (Page 1589) Updating comparison results (Page 1590) Changing blocks during detailed comparison Changing offline blocks You can change offline blocks that serve as a reference block of the comparison at any time. The compared block, on the other hand, is write protected and cannot be changed. Changing online blocks You cannot change online blocks. WinCC Basic V13.0 System Manual, 02/2014 1589 Programming the PLC 9.1 Creating the user program See also Carrying out an online/offline comparison (Page 274) Carrying out offline/offline comparisons (Page 274) Using the compare editor (Page 275) Starting a detailed comparison (Page 1571) Visualization of the comparison result for LAD/FBD (Page 1572) Navigating in the detailed comparison (Page 1588) Updating comparison results (Page 1590) Updating comparison results As soon as you change an object, the comparison results are no longer valid and must be updated. Requirement You have run a detailed comparison. Procedure To update the comparison results, follow these steps: 1. Click "Update the comparison result" in the toolbar. See also Carrying out an online/offline comparison (Page 274) Carrying out offline/offline comparisons (Page 274) Using the compare editor (Page 275) Starting a detailed comparison (Page 1571) Visualization of the comparison result for LAD/FBD (Page 1572) Navigating in the detailed comparison (Page 1588) Changing blocks during detailed comparison (Page 1589) 1590 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program 9.1.5.3 Comparing PLC tags You have the following options for comparing PLC tags: Automatic offline/offline comparison in the compare editor The PLC tag tables of the selected devices are compared offline. Manual offline/offline comparison in the compare editor The selected PLC tag tables of the devices are compared offline. Detailed comparison Use the detailed comparison to determine differences within the PLC tag tables. Performing automatic offline/offline comparison in the compare editor To perform an automatic offline/offline comparison of PLC tag tables, follow these steps: 1. Select a device in the project tree that allows offline/offline comparison. 2. Select the "Compare > Offline/offline" command in the shortcut menu. The compare editor opens and the selected device is displayed in the left area. 3. Drag-and-drop an additional device to the drop area of the right pane. The device to be compared can originate from the same project, a reference project or the library. 4. Open the "PLC tags" folder. You can identify the status of the PLC tag tables based on the symbols in the status and action area. You can define certain actions depending on the status. You can drag any other device to the drop area at any time to perform further comparisons. Performing manual offline/offline comparison in the compare editor To perform a manual offline/offline comparison of PLC tag tables, follow these steps: 1. Select a device in the project tree that allows offline/offline comparison. 2. Select the "Compare > Offline/offline" command in the shortcut menu. The compare editor opens and the selected device is displayed in the left area. 3. Drag-and-drop an additional device to the drop area of the right pane. The device to be compared can originate from the same project, a reference project or the library. 4. In the status and action area, click on the button for switching between automatic and manual comparison. 5. Select the PLC tag tables that you want to compare. The properties comparison is displayed. You can identify the status based on the symbols. You can drag any other device to the drop area at any time to perform further comparisons. WinCC Basic V13.0 System Manual, 02/2014 1591 Programming the PLC 9.1 Creating the user program Running a detailed comparison To start a detailed comparison for a PLC tag table, follow these steps: 1. Perform an automatic or manual offline/offline comparison. 2. For an automatic offline/offline comparison in the compare editor, select the PLC tag table for which you want to run a detailed comparison. Note that two PLC tag tables must be selected for comparison for a manual offline/offline comparison. 3. Click the "Start detailed comparison" button in the toolbar. A separate compare editor opens. All existing PLC tags of the selected PLC tag tables are displayed depending on the settings of the compare editor. User and system constants are not shown, however. You can identify the status of the PLC tags based on the symbols. You can define certain actions depending on the status of the PLC tags. See also Introduction to comparing PLC programs (Page 1565) Using the compare editor (Page 275) Comparing PLC data types (Page 1592) 9.1.5.4 Comparing PLC data types You have the following options for comparing PLC data types: Online/offline comparison (S7-1200/1500 only) The PLC data types in the project are compared with the PLC data types of the selected device. Automatic offline/offline comparison in the compare editor The PLC data types of the selected devices are compared offline. Manual offline/offline comparison in the compare editor The selected PLC data types of the devices are compared offline. Detailed comparison Use the detailed comparison to determine differences between PLC data types. Performing online/offline comparison of PLC data types To perform an online/offline comparison, follow these steps: 1. In the project tree, select a device that allows online/offline comparison. 2. Select the "Compare > Offline/online" command in the shortcut menu. If you have not already established an online connection to this device, the "Go online" dialog opens. In this case, set all the necessary parameters for the connection and click "Connect". The online connection is established and the compare editor opens. 3. Open the "PLC data types" folder. You can identify the status based on the symbols in the status and action area. When you select an object, the properties of the PLC data type and the corresponding PLC data type of the assigned device are displayed in the properties comparison. 1592 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program Performing automatic offline/offline comparison in the compare editor To perform an automatic offline/offline comparison of PLC tag tables, follow these steps: 1. Select a device in the project tree that allows offline/offline comparison. 2. Select the "Compare > Offline/offline" command in the shortcut menu. The compare editor opens and the selected device is displayed in the left area. 3. Drag-and-drop an additional device to the drop area of the right pane. The device to be compared can originate from the same project, a reference project or the library. 4. Open the "PLC data types" folder. You can identify the status of the PLC tag tables based on the symbols in the status and action area. You can define certain actions depending on the status. You can drag any other device to the drop area at any time to perform further comparisons. Performing manual offline/offline comparison in the compare editor To perform a manual offline/offline comparison of PLC data types, follow these steps: 1. Select a device in the project tree that allows offline/offline comparison. 2. Select the "Compare > Offline/offline" command in the shortcut menu. The compare editor opens and the selected device is displayed in the left area. 3. Drag-and-drop an additional device to the drop area of the right pane. The device to be compared can originate from the same project, a reference project or the library. 4. In the status and action area, click on the button for switching between automatic and manual comparison. 5. Select the PLC data types that you want to compare. The properties comparison is displayed. You can identify the status based on the symbols. You can drag any other device to the drop area at any time to perform further comparisons. Running a detailed comparison To start a detailed comparison for a PLC data type, follow these steps: 1. Perform an offline/offline comparison. You can also perform an online/offline comparison for CPUs of the S7-1200/1500 series. 2. For an automatic offline/offline comparison in the compare editor, select the PLC data type for which you want to run a detailed comparison. Note that two PLC data types must be selected for comparison with a manual offline/offline comparison. 3. Click the "Start detailed comparison" button in the toolbar. The two PLC data types are opened next to each other so that you can easily identify the differences. WinCC Basic V13.0 System Manual, 02/2014 1593 Programming the PLC 9.1 Creating the user program See also Introduction to comparing PLC programs (Page 1565) Using the compare editor (Page 275) Comparing PLC tags (Page 1591) 9.1.6 Compiling and downloading blocks 9.1.6.1 Compiling blocks Basic information on compiling blocks Introduction A user program must first be compiled before the CPU can execute it. You need to recompile your program each time you make a change. The following procedures take place during compilation: The user program is checked for syntax errors. Unneeded instructions are removed from the user program. All the block calls within the compiled blocks are checked. In case of changes to the interface of called blocks, errors will be shown in the "Compilation" tab of the information window. You have to correct these errors first. The blocks must be numbered uniquely in the user program. If more than one block has the same number, the blocks with number conflicts are renumbered automatically during compilation. A block will not be renumbered in the following cases: - The block was selected either individually or as part of a multiselection for the compilation. - The block is know-how protected. - The number assignment is set to "manual" in the properties of the block. Number conflicts that cannot be resolved by automatic renumbering must be corrected manually. Note the messages in the Inspector window for this. You can only correct knowhow-protected blocks manually if you know the password since the blocks must then be recompiled. Finally, the user program is compiled into a code that can be read by the CPU. 1594 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program Compilation methods You can start compilation in the following windows or editors: Compiling blocks in the project tree Serves to compile individual blocks or the simultaneous compilation of one or several blocks in the "Program blocks" folder. Compiling blocks in the program editor This is intended for compilation of a single open block. Compiling blocks in the call or dependency structure Used to compile individual blocks. See also: Call structure (Page 1626), Dependency structure (Page 1633) Compilation options If you are compiling blocks in project tree, you have further options: Software (changes only) All program changes of the selected blocks are compiled. If you have selected a block folder, all program changes to the bocks contained in the folder are compiled. Software (compile all blocks) All blocks are compiled. This is recommended for the first compilation and after major revisions. Software (reset memory reserve) All tags declared in the reserve area of the interface of selected blocks are moved to the standard area of the interface. Memory reserve is now available for further interface extensions. Note This option is only available for CPUs of the S7-1500 and S7-1200 V4 series. Consistency check Changing the interfaces of blocks called or PLC data types used can result in inconsistencies between calling blocks and called blocks or between the PLC data types and the global data blocks which use these PLC data types. To avoid such inconsistencies in the user program, the system performs an automatic consistency check before each compilation process. The time stamps are compared and compilation is then either carried out or canceled depending on the results of the comparison. The calling block can only be compiled if the time stamps of the interfaces of the called blocks are older than those of the calling block. A global data block based on a PLC data type can only be compiled correctly if the time stamp of the global data block is newer than the time stamp of the PLC data type used. The instance data block can only be compiled correctly if the interface time stamps for the interface of the instance data block are identical to those of the assigned function block. If the compilation process is cancelled, an alarm is displayed in the inspector window. Update the block calls in the relevant blocks and the PLC data types in the global data blocks and then WinCC Basic V13.0 System Manual, 02/2014 1595 Programming the PLC 9.1 Creating the user program restart compilation. The consistency check also finds know-how protected blocks which cannot be compiled. The corresponding messages will also be shown in the inspector window. If you start loading immediately instead of first compiling, the blocks selected will be automatically compiled and the block call and global data blocks implicitly updated. Please note the following differences between the CPU families: S7-1200/1500: All blocks affected are loaded to ensure no inconsistencies can arise. S7-300/400: Only the block selected is loaded. See also Compiling blocks in the project tree (Page 1596) Compiling blocks in the program editor (Page 1597) Correcting compilation errors (Page 1598) Block time stamps (Page 1346) Updating block calls in LAD (Page 1418) Updating block calls in FBD (Page 1460) Compiling project data (Page 263) Compiling blocks in the project tree You can compile one block, multiple blocks or all of the blocks in the project tree. For CPUs of the S7-1500 and S7-1200 V4 series, you can also reset the memory layout of blocks with memory reserve by running a compilation. For more information on memory reserve, refer to chapter "Loading blocks (S7-1200/1500) > Loading block changes without reinitialization". Requirement The project tree is open. Compiling one or more blocks in the project tree To compile multiple blocks in the project tree, follow these steps: 1. Open the "Program blocks" folder in project tree. 2. Select the blocks you want to compile. 3. Select the "Compile > Software (only changes)" command from the shortcut menu. 1596 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program Compiling all blocks in the project tree To compile all blocks in the "Program blocks" folder in project tree, follow these steps: 1. Select the "Program blocks" folder in the project tree. 2. You can select one of two different options for the compilation: - If you want to compile only the changes since the last compilation, select the "Compile > Software (only changes)" command in the shortcut menu. - If you want to compile all blocks completely, select the "Compile > Software (compile all blocks)" command in the shortcut menu. Resetting memory layout (S7-1500/S7-1200 V4) Proceed as follows to reset the memory layout of blocks: 1. Select the "Program blocks" folder, or specific blocks in this folder. 2. Select the "Compile > Software (Reset memory reserve)" command from the shortcut menu. Result The code for the blocks will be generated if the consistency check has been successful. Instance data blocks generated by the system which are no longer needed will be deleted. The message under "Info > Compilation" in the inspector window reports whether the compilation was successful. See also Basic information on compiling blocks (Page 1594) Compiling blocks in the program editor (Page 1597) Correcting compilation errors (Page 1598) Finding syntax errors in the program (Page 1517) Compiling blocks in the program editor Note Note that the block is recompiled even if you have not made any changes and the time stamp of the block is modified. Requirement The block to be compiled is open. WinCC Basic V13.0 System Manual, 02/2014 1597 Programming the PLC 9.1 Creating the user program Procedure To compile a block in the program editor, follow these steps: 1. Right-click in the instruction window of the programming editor. 2. Select the "Compile" command in the shortcut menu. Result The code for the block is generated. Instance data blocks generated by the system which are no longer needed will be deleted. The message under "Info > Compilation" in the inspector window reports whether the compilation was successful. See also Basic information on compiling blocks (Page 1594) Compiling blocks in the project tree (Page 1596) Correcting compilation errors (Page 1598) Correcting compilation errors In the Inspector window in "Info > Compile", you can see whether any compilation was successful or whether errors were detected in the program. If errors occur, you will need to correct them and then start the compilation again. Procedure To correct errors following compilation, follow these steps: 1. Open the error list in the Inspector window with "Info > Compile". 2. If there is one, click on the blue question mark next to the error text for information on remedying errors. 3. Double-click the error you want to correct. The corresponding error is highlighted. 4. Correct the error. 5. Restart compilation. See also Basic information on compiling blocks (Page 1594) Compiling blocks in the program editor (Page 1597) Compiling blocks in the project tree (Page 1596) 1598 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program 9.1.6.2 Downloading blocks Introduction to downloading blocks Downloading blocks to device So that the CPU can execute the user program, the program must first be compiled and then downloaded to the device. The following options are available for downloading: Downloading blocks to the program editor You can load a single open block in the program editor. Downloading blocks to the project tree You can download several or all of the blocks in the block folder via the project tree. During the loading operation, all information that is required for the reconstruction of the program, including symbolic information such as the names and comments for code and data blocks, is also loaded in the current project language. If you change the project language, you must therefore re-load the program. The symbolic information is not loaded to the work memory, but rather to the load memory. After the data has been loaded from a device, the symbolic information is available again in your program, which increases the readability of your program code. Please note, however, that loading to and from a device is not a substitute for storing data in an offline project, as watch tables or multi-language capability of projects cannot be reproduced by loading to and from a device. After loading from a device, you can only display all data from know-how-protected blocks by entering the correct password. Note To avoid inconsistencies between calling and called blocks, all blocks affected are compiled and loaded after each global change, such as a change in the block interface. Note S7-1200 Version 1.0 If you download an element of your project to the CPU, for example a program block, a data block or the hardware configuration, the CPU runs a cold restart the next time it changes to RUN mode. Apart from deleting the inputs, initializing the outputs and deleting the nonretentive memory, cold restart also deletes the retentive memory areas. All subsequent changes from STOP to RUN are warm restarts in which the retentive memory is not deleted. Note S7-1500 The load memory of S7-1500 series CPUs is on the SIMATIC memory card. Therefore, a SIMATIC memory card absolutely must be inserted in order to operate the CPU. WinCC Basic V13.0 System Manual, 02/2014 1599 Programming the PLC 9.1 Creating the user program Uploading blocks from device You can load the blocks of a device to your project. This is necessary, for example, if you want to edit blocks that only exist in this device. You have the option of loading either all available blocks (organization blocks, function blocks, functions and data blocks) and global PLC tags or individual blocks to the project. Uploading blocks from or downloading blocks to a memory card Memory cards are plug-in cards used with an S7-1200 series CPU, for example, to replace the load memory of a device. In the case of S7-1500 series CPUs, they contain the load memory. Only Siemens SD cards can be used for devices of the S7-1200 and S7-1500 product range. To use a memory card as load memory, you must download the user program or individual blocks to a memory card. You can just as well upload blocks from a memory card back into the project. Note S7-1200 Note the following when uploading to or downloading from a memory card: If the CPU contains no previous program and you insert an empty memory card in the CPU the program will be loaded from the PG/PC to the memory card and not to the CPU. If you insert an empty memory card prior to the startup of the CPU, the program that is on the CPU will be transferred automatically to the memory card. The program on the CPU will then be deleted. If you insert a memory card with a program in the CPU prior to the startup of the CPU and the CPU already contains a program, the program on the memory card will be executed and not the program on the CPU. The program on the CPU will be deleted. Loading GRAPH function blocks If you load a GRAPH function block together with its instance data block, the processing of the sequencer starts over at the initial step. As a result, problems may occur when synchronizing the sequencer with the process. You can avoid these problems by switching off the sequencer before loading. Loading block changes without reinitialization It often proves necessary to edit or expand a PLC program that was already commissioned and that is running on the plant without error. Such operations should be performed without causing any major interruptions of current operations. S7-1500 therefore offers the option of extending the interfaces of function or data blocks during runtime and loading the modified blocks without setting the CPU to STOP or affecting the value of tags that are already loaded. This is a simple means of implementing program changes. This load process (download without reinitialization) will not have a negative impact on the controlled process. 1600 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program Effects of a load operation on the tag values of a data blocks When data blocks are downloaded to a device in STOP mode, the next transition of the device to RUN affects the current tag values as follows: Tags not marked as being retentive retain their defined start values. Retentive tags of the S7-1200 only retain their values if the following conditions are met: - You loaded the data block by means of "Download to device > Software (changes only)". - You made no changes to the DB structure. Otherwise the retentive tags will also retain their defined start values. Retentive tags of the S7-1500 only retain their values if the following conditions are met: - You loaded the data block by means of "Download to device > Software (changes only)". - You made no changes to the structure of the data block or modified it within the memory reserve. Otherwise the retentive tags will also retain their defined start values. Loading blocks with synchronization In team engineering, it is possible for several users to work on one project with several engineering systems at the same time and access one S7-1500 CPU. To ensure consistency within the shared project, it is necessary to synchronize the changed data prior to loading so that nothing gets overwritten unintentionally. If differences are determined between the online and offline data management within the shared project during loading that were caused by a different engineering system, automatic synchronization of the data to be loaded is offered during loading. In this case, the "Synchronization" dialog displays the data to be synchronized with the current status (online-offline comparison) and the possible actions. The following options are available for synchronization: Application case Recommendation Synchronization One or more blocks on the CPU (online) are more recent than in the engineering system (offline). These blocks should be downloaded from the CPU to the engineering system before loading. Automatic synchronization is possible: One or more new blocks have been created and exist only in the CPU (online). These blocks should be downloaded from the CPU to the engineering system before loading. Automatic synchronization is possible: One or more blocks on the CPU have been deleted. The blocks should also be deleted prior to the download in the engineering system. Automatic synchronization is not possible. WinCC Basic V13.0 System Manual, 02/2014 The blocks in the engineering system are updated prior to loading. The new blocks are added prior to the download in the engineering system. The blocks deleted on the CPU should be manually deleted in the offline project in the engineering system. 1601 Programming the PLC 9.1 Creating the user program Application case Recommendation Synchronization One or more blocks on the CPU and in the engineering system are different. These blocks with competing changes must be adapted manually. You decide in this case which changes you are going to accept. Automatic synchronization is not possible: This is the case when a different user has changed blocks to which you have also made corrections and has already downloaded them to the CPU. If the blocks on the CPU are to be retained, you should accept these blocks prior to download from the CPU to your engineering system. The affected blocks on the CPU or in the engineering system must be adapted manually. One of the existing block versions (online or offline) will be overwritten in the process. If the blocks that you have changed are to be applied, you can continue with the download without synchronization. There are differences in the hardware configuration on the CPU (online) and in the engineering system (offline). Differences in the hardware configuration must be adapted manually. You decide in this case which hardware configuration you are going to accept. If the existing hardware configuration on the CPU is to be retained, you should apply these in your engineering system prior to loading. Automatic synchronization is not possible: The hardware configuration must be adapted manually. One of the existing hardware configurations (online or offline) will be overwritten in the process. If you want to apply the changed hardware configuration, you can continue with the download without synchronization. You can use the "Force download to device" command to download blocks without synchronization, if desired. Downloading blocks in the "RUN" operating mode to the device Basics on downloading blocks in the "RUN" operating mode When you download modified blocks to the device, it is not always necessary to switch the device to the "STOP" operating mode. Prior to a download operation, the Engineering System checks whether the device must be stopped before downloading. The result of this check is displayed in the "Load preview" dialog. If it is necessary to change to the "STOP" operating mode, you cannot continue the download process until you have set the appropriate option. Note Actual parameters are not overwritten by a download process in the "RUN" operating mode. Changes to the actual parameters will not become effective until the next time you change the operating mode from "STOP" to "RUN". The following table shows the actions after which you can execute the download process in the "RUN" operating mode: 1602 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program Action Download in "RUN" operating mode possible S7-1200 S7-1500 Downloading individual blocks Yes Yes Downloading all blocks No No Adding or deleting OBs No Yes Adding or deleting DBs, FCs or FBs Yes Yes Changing block interfaces for FBs No Only within the memory reserve Changing block interfaces for FCs Yes Yes Changing the structure of a DB or an instance DB No Only within the memory reserve Changing the hardware configuration No No Changing the retentivity settings of bit memories and DBs No No Changing the program code of FC, FB or OB Yes Yes Changing the attributes of OBs Yes Yes Adding comments Yes Yes Adding input, output or bit memory areas Yes Yes Changing tag names Yes Yes Maximum number of blocks that can be downloaded for the device used in "RUN" not exceeded Yes Yes See also Downloading blocks from program editor to device (Page 1603) Downloading blocks from the project tree to the device (Page 1605) Downloading project data to a device (Page 267) Downloading blocks from program editor to device Requirement The block to be downloaded is open. WinCC Basic V13.0 System Manual, 02/2014 1603 Programming the PLC 9.1 Creating the user program Procedure To download a block from the program editor to the device, follow these steps: 1. Right-click in the instruction window of the programming editor. 2. Select the "Download to device" command in the shortcut menu. - If you have not already established an online connection, the "Extended download to device" dialog opens. In this case, set all parameters required for the connection and click "Load". You have the option of showing all compatible devices by selecting the corresponding option and clicking the "Start search" command. You can also open the "Extended download to device" dialog explicitly via the "Online" menu. See also: Go online and Go offline - If you have already specified an online connection, then the project data is compiled if necessary and the "Load preview" dialog opens. This dialog displays messages and proposes actions necessary for loading. 3. Check the messages and, where necessary, enable the actions in the "Action" column. Note Actions Performing the proposed actions during ongoing plant operation can cause serious damage to property or injury to persons if there are functional faults or program errors. Make sure that no dangerous situations can arise before you start the actions. As soon as downloading becomes possible, the "Load" button is enabled. 4. Click "Load". If there is a need for synchronization, the system automatically displays the "Synchronization" dialog. This dialog displays messages and suggests actions that are needed for the synchronization. You have the option of performing these actions or forcing the download without synchronization by clicking "Force download to device". If you have performed the suggested actions, you will be asked whether you want to continue with the download. Click "Continue download" in order to download the block. The "Load results" dialog then opens and shows you the status and the actions after the download operation. 5. If you want to start the modules again directly after downloading, select the "Start all" check box. 6. To close the "Load results" dialog box, click "Finish". Result The code for the block will be downloaded to the device. If the changes affect additional blocks, these will be compiled and also downloaded to the device. Blocks that only exist online in the device are deleted. Existing CPU data blocks are retained, however. Inconsistencies between the blocks in the user program are avoided by loading all blocks affected and deleting the unneeded blocks in the device. The messages under "Info > General" in the Inspector window show whether the downloading process was successful. 1604 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program See also Downloading blocks from the project tree to the device (Page 1605) Downloading project data to a device (Page 267) Downloading blocks in the "RUN" operating mode to the device (Page 1602) Downloading blocks from the project tree to the device In the project tree you can download one block, multiple blocks or all blocks to a device. Downloading one or more blocks from the project tree to the device To download one block or multiple blocks to the device from the project tree, follow these steps: 1. Open the "Program blocks" folder in project tree. 2. Select the blocks you want to download. 3. Select the "Download to device > Software (only changes)" command from the shortcut menu. - If you have not already established an online connection, the "Extended download to device" dialog opens. In this case, set all parameters required for the connection and click "Load". You have the option of showing all compatible devices by selecting the corresponding option and clicking the "Start search" command. You can also open the "Extended download to device" dialog explicitly via the "Online" menu. See also: Go online and Go offline - If you have already specified an online connection, then the project data is compiled if necessary and the "Load preview" dialog opens. This dialog displays messages and proposes actions necessary for loading. 4. Check the messages and, where necessary, enable the actions in the "Action" column. Note Performing the proposed actions during ongoing plant operation can cause serious damage to property or injury to persons if there are functional faults or program errors. Make sure that no dangerous situations can arise before you start the actions. As soon as downloading becomes possible, the "Load" button is enabled. 5. Click "Load". If there is a need for synchronization, the system automatically displays the "Synchronization" dialog. This dialog displays messages and suggests actions that are needed for the synchronization. You have the option of performing these actions or forcing the download without synchronization by clicking "Force download to device". If you have performed the suggested actions, you will be asked whether you want to continue with the download. Click "Continue download" in order to download the block. The "Load results" dialog then opens and shows you the status and the actions after the download operation. 6. If you want to start the modules again directly after downloading, select the "Start all" check box. 7. To close the "Load results" dialog box, click "Finish". WinCC Basic V13.0 System Manual, 02/2014 1605 Programming the PLC 9.1 Creating the user program Downloading blocks from the project tree to the device To download all blocks in the "Program blocks" folder to the device from the project tree, follow these steps: 1. Select the "Program blocks" folder in the project tree. 2. Select the "Download to device" submenu in the shortcut menu. 3. If you only want to download the changes since the last download, select the "Software (only changes)" option. If all blocks are to be fully loaded and all values are to be reset to their start values, select "Download PLC program to the device and reset". - If you have not already established an online connection, the "Extended download to device" dialog opens. In this case, set all parameters required for the connection and click "Load". You have the option of showing all compatible devices by selecting the corresponding option and clicking the "Start search" command. You can also open the "Extended download to device" dialog explicitly via the "Online" menu. See also: Go online and Go offline - If you have already specified an online connection, then the project data is compiled if necessary and the "Load preview" dialog opens. This dialog displays messages and proposes actions necessary for loading. 4. Check the messages and, where necessary, enable the actions in the "Action" column. Note Performing the proposed actions during ongoing plant operation can cause serious damage to property or injury to persons if there are functional faults or program errors. Make sure that no dangerous situations can arise before you start the actions. As soon as downloading becomes possible, the "Load" button is enabled. 5. Click "Load". If there is a need for synchronization, the system automatically displays the "Synchronization" dialog. This dialog displays messages and suggests actions that are needed for the synchronization. You have the option of performing these actions or forcing the download without synchronization by clicking "Force download to device". If you have performed the suggested actions, you will be asked whether you want to continue with the download. Click "Continue download" in order to download the block. The "Load results" dialog then opens and shows you the status and the actions after the download operation. 6. If you want to start the modules again directly after downloading, select the "Start all" check box. 7. To close the "Load results" dialog box, click "Finish". Result The code for the blocks is downloaded to the device. If the changes affect additional blocks, these will be compiled and also downloaded to the device. Blocks that only exist online in the device are deleted. Inconsistencies between the blocks in the user program are avoided by loading all blocks affected and deleting the unneeded blocks in the device. The messages under "Info > General" in the Inspector window show whether the downloading process was successful. 1606 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program See also Downloading blocks from program editor to device (Page 1603) Downloading project data to a device (Page 267) Downloading blocks in the "RUN" operating mode to the device (Page 1602) Uploading blocks from device You can load either all blocks or individual blocks from a device into your project. Note Note the following information: Please note that when you load individual blocks, no tags or other required blocks to which you may refer are loaded together with the individual blocks. During the loading operation, reference to tags and blocks are reassigned where possible based on the names. After the loading operation, check whether these assignments are correct. S7-1500: When GRAPH function blocks are loaded from a device to your project, the stepspecific alarm texts for the interlock and supervision alarms are not loaded. Requirement The online and offline versions of a block to be loaded are different or the blocks only exists online. Uploading all blocks from a device To upload all blocks from a device, follow these steps: 1. Establish an online connection with the device from which you want to upload the blocks. See also: Establishing and terminating an online connection 2. In the project tree, select the device folder from which you want to upload blocks. 3. In the "Online" menu, select the "Upload from device" command. The "Upload preview" dialog box opens. This dialog displays alarms and proposes actions necessary for loading. 4. Check the alarms and, where necessary, enable the actions in the "Action" column. The "Upload from device" button will be enabled as soon as uploading becomes possible. 5. Click on the "Upload from device" button. The load is executed. Uploading individual blocks from a device To upload individual blocks from a device, follow these steps: 1. Establish an online connection with the device from which you want to upload the blocks. See also: Establishing and terminating an online connection 2. In the project tree, select the blocks that you want to upload from the device. WinCC Basic V13.0 System Manual, 02/2014 1607 Programming the PLC 9.1 Creating the user program 3. In the "Online" menu, select the "Upload from device" command. The "Upload preview" dialog box opens. This dialog displays alarms and proposes actions necessary for loading. 4. Check the alarms and, where necessary, enable the actions in the "Action" column. The "Upload from device" button will be enabled as soon as uploading becomes possible. 5. Click on the "Upload from device" button. The load is executed. Result The blocks will be uploaded from the device to the project. You can edit them as normal, recompile them and download them to the device again. Downloading blocks to a memory card Requirement The memory card is marked as a program card. The "Program blocks" folder of the memory card is open. Procedure To download blocks to a memory card, follow these steps: 1. Open the "Program blocks" folder of the device in the project tree. 2. Select the blocks you want to download to the memory card. 3. Drag the blocks in project tree to the "Program blocks" folder of the memory card. The "Load preview" dialog opens. This dialog displays messages and proposes actions necessary for loading. 4. Check the messages and, where necessary, enable the actions in the "Action" column. 5. As soon as downloading becomes possible, the "Load" button is enabled. 6. Click the "Load" button. If there is a need for synchronization, the system automatically displays the "Synchronization" dialog. This dialog displays messages and suggests actions that are needed for the synchronization. You have the option of performing these actions or forcing the download without synchronization by clicking "Force download to device". If you have performed the suggested actions, you will be asked whether you want to continue with the download. Click "Continue download" in order to download the block. The "Load results" dialog then opens and shows you the status and the actions after the download operation. 7. Click "Finish". Result The block is downloaded to the memory card If the changes affect additional blocks, these will also be downloaded to the memory card. Blocks that exist only on the memory card are deleted. 1608 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program Inconsistencies between the blocks in the user program are avoided by downloading all affected blocks and the deleting of the non-required blocks on the memory card. The messages under "Info > General" in the Inspector window show whether the downloading process was successful. See also Uploading blocks from a memory card (Page 1609) Accessing memory cards (Page 324) Uploading blocks from a memory card You can only upload all blocks from one memory card back into your project. Requirement The memory card is displayed. See also: Accessing memory cards (Page 324) Procedure To upload blocks from a memory card to your project, follow these steps: 1. In the project tree, drag the folder of the memory card to the folder of the device in the project. The "Upload preview" dialog box opens. This dialog displays alarms and proposes actions necessary for loading. 2. Check the alarms and, where necessary, enable the actions in the "Action" column. The "Upload from device" button will be enabled as soon as uploading becomes possible. 3. Click on the "Upload from device" button. See also Downloading blocks to a memory card (Page 1608) Switching off the sequencer prior to loading a GRAPH DB You can specify the switching off of the sequencer prior to loading an instance data block either globally or during the load operation. WinCC Basic V13.0 System Manual, 02/2014 1609 Programming the PLC 9.1 Creating the user program Globally switching off the sequencer To switch off the sequencer globally for each loading operation of an instance data block, follow these steps: 1. Select the "Settings" command in the "Options" menu. The "Settings" window is displayed in the work area. 2. Select the "PLC programming > GRAPH" group in the area navigation. 3. Select the "Turn off sequence before downloading DB" check box. For future loading operations, the sequencer is switched off prior to loading of the instance data block. Switching off the sequencer during the loading operation To switch off the sequencer during the loading operation, follow these steps: 1. Load the GRAPH function block to the device. During the loading operation, the "Load preview" dialog opens. This dialog displays alarms and suggests the required actions for loading. If the instance data block must be loaded together with the GRAPH function block, the "Load preview" dialog suggests the action "Turn off sequence before downloading the DB". 2. Select the "Turn off sequence before downloading DB" check box. 9.1.7 Protecting blocks 9.1.7.1 Protecting blocks Introduction You can use a password to protect one or more blocks of the OB, FB, FC type and global data blocks from unauthorized access. Note the following particularities: You can not manually protect instance data blocks; they depend on the know-how protection of the assigned FB. This means that when you create an instance data block for a know-how protected FB, the instance data block also receives this know-how protection. This is independent of whether you explicitly create the instance data block or if it is created by a block call. The know-how protection acts as write protection in global blocks and in instance data blocks. You cannot provide ARRAY data blocks with know-how protection. If a block is know-how protected, only the following data is readable without the correct password: Interface parameters Input, Output, InOut, Return, Static Block title Block comment 1610 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program Block properties Tags of global data blocks without specification of the location of use The following actions can be performed with a know-how protected block: Copying and deleting Calling in a program Online/offline comparison Load The code of the block, on the other hand, is protected from unauthorized reading and modification. For S7-1200/1500 CPUs, you can also set up copy protection which binds execution of the block to the CPU, or to the SD card with the defined serial number. Note Note the following information: S7-1200 version 1.0 and S7-300/400 (only GRAPH and SCL blocks): If you download a know-how-protected block to a device, no restore information is loaded along with it. This means that you cannot open a know-how-protected block again even with the correct password if you upload it from the device. Only the non-protected data is compared in offline-online comparison of know-how protected blocks. You will no longer be able to access the block if you do not have the password. If you add a know-how-protected block to a library, the master copy created will also be know-how protected. For S7-1500, you can select the "Block can be used as know-how protected library item" check box in the block properties to obtain the information on whether or not the block can be used as protected library item. For this purpose, the block cannot use any tags from the operand areas Output (Q), Input (I), Bit memory (M), Timer function (T) or Count function (C), and cannot access data blocks. Cross references to used tags, bit memories, inputs and outputs in know-how protected blocks are not displayed even after the correct password is entered.. If you change the number of a block, the loadable binary component of the block is out of date. This means that the block must be recompiled before loading it to a device. For knowhow-protected blocks, this is only possible with the correct password. Keep this in mind particularly if you want to copy a know-how-protected block to another device in which there is already a block with the same number. Always pass on a project that includes know-how-protected blocks as a project archive or library archive. In this way, you ensure that the know-how protection cannot be bypassed. If you wish to assign know-how protection to several blocks using multiple selection, no instance data block can be included in the selection. Otherwise, it will not be possible to set know-how protection. You cannot change the know-how protection settings for an open, know-how protected block. WinCC Basic V13.0 System Manual, 02/2014 1611 Programming the PLC 9.1 Creating the user program See also Setting up and removing block copy protection (Page 1612) Setting up block know-how protection (Page 1613) Opening know-how protected blocks (Page 1614) Printing know-how protected blocks (Page 1615) Removing block know-how protection (Page 1616) Changing a password (Page 1616) Archiving projects (Page 259) Archiving global libraries (Page 347) 9.1.7.2 Setting up and removing block copy protection For S7-1200 /1500 CPUs, you can set up copy protection which binds execution of the block to a specific CPU or SD card. The block can then only be executed if it is in the device with the set serial number. It is important that you also know-how-protect any block for which you have set up copy protection. If you do not, anyone can reset the copy protection. Note S7-1500 and S7-1200 V2.2 and higher: If you download a copy protected block to a device that does not match the specified serial number, the entire download operation will be rejected. This means that blocks without copy protection, too, will not be downloaded. Setting up copy protection To set up copy protection for a block, follow these steps: 1. Open the block you wish to copy-protect. 2. Open the "Properties" tab in the inspector window. 3. Select "Protection" in the area navigation in the inspector window. 4. Select either "Bind to serial number of the CPU" or "Bind to serial number of the memory card" from the drop-down list in the "Copy protection" area. 5. Enter the serial number of the CPU or the memory card for a S7-1500 CPU. You can either enter the serial number directly for a S7-1200 CPU or enable the option "Serial number inserted when downloading to a device or memory card" if the serial number is to be inserted automatically during loading. 6. You can now set up the know-how protection for the block in the "Know-how protection" area, if the block does not already have know-how protection. 1612 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program Removing copy protection To remove copy protection, follow these steps: 1. Open the block for which you wish to remove copy protection. 2. Open the "Properties" tab in the inspector window. 3. Select "Protection" in the area navigation in the inspector window. 4. Select "No binding" in the drop-down list in the "Copy protection" area. See also Protecting blocks (Page 1610) Setting up block know-how protection (Page 1613) Opening know-how protected blocks (Page 1614) Printing know-how protected blocks (Page 1615) Removing block know-how protection (Page 1616) Changing a password (Page 1616) 9.1.7.3 Setting up block know-how protection You can set up know-how protection for blocks in the devices in your project. Procedure To set up block know-how protection, follow these steps: 1. Select the blocks with no know-how protection which you want to protect. 2. Select the command "Know-how protection" in the "Edit" menu. The "Know-how protection" dialog will open. 3. Click "Define". The "Define password" dialog box opens. 4. Enter a password in the "New" field. 5. Enter the same password in the "Confirm" field. 6. Confirm your entries with "OK". 7. Close the "Know-how protection" dialog by clicking on "OK". Result The blocks selected will be know-how-protected. Know-how protected blocks are marked with a lock in the project tree. The password entered is valid for all blocks selected. WinCC Basic V13.0 System Manual, 02/2014 1613 Programming the PLC 9.1 Creating the user program See also Protecting blocks (Page 1610) Setting up and removing block copy protection (Page 1612) Opening know-how protected blocks (Page 1614) Printing know-how protected blocks (Page 1615) Removing block know-how protection (Page 1616) Changing a password (Page 1616) 9.1.7.4 Opening know-how protected blocks You can only open multiple know-how protected blocks at once if they are protected with the same password. Procedure To open a know-how protected block, follow these steps: 1. Double-click on the block you wish to open. The "Access protection" dialog will open. 2. Enter the password for the know-how protected block. 3. Confirm your entry with "OK". Result The know-how protected block will open provided you have entered the correct password. However, the block will remain know-how protected. If you copy the block or add it to a library, for example, the copies will also be know-how protected. Once you have opened the block, you can edit the program code and the block interface of the block for as long as the block or TIA portal is open. The password must be entered again the next time the block is opened. If you close the "Access protection" dialog with "Cancel", the block will open but the block code will not be displayed and you will not be able to edit the block. See also Protecting blocks (Page 1610) Setting up and removing block copy protection (Page 1612) Setting up block know-how protection (Page 1613) Printing know-how protected blocks (Page 1615) Removing block know-how protection (Page 1616) Changing a password (Page 1616) 1614 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.1 Creating the user program 9.1.7.5 Printing know-how protected blocks You can only print complete know-how protected blocks if they have been opened with the correct password. If you print a closed block or if the block was not opened with the correct password, only the non-protected block data will be printed. Procedure To print a know-how protected block in full, follow these steps: 1. Open the know-how protected block you wish to print. See also: Opening know-how protected blocks (Page 1614) 2. Select the "Print" command in the "Project" menu. The "Print" dialog will open. 3. Select the printer in the "Name" field. 4. Click "Advanced" to modify the Windows printer settings. 5. Select the documentation information set in the "Document information" drop-down list that you want to use for the frame layout. 6. Under "Print objects/area" select whether you want to print all objects or the complete area, or only a selection. 7. Under "Properties" select the print scope. - Select "All" to print the complete block. - Choose "Visible" to print all the information within the block that is visible on the screen. - Select "Compact" to print a shortened form of the block. 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. See also Printing project contents (Page 290) Protecting blocks (Page 1610) Setting up and removing block copy protection (Page 1612) Setting up block know-how protection (Page 1613) Removing block know-how protection (Page 1616) Changing a password (Page 1616) WinCC Basic V13.0 System Manual, 02/2014 1615 Programming the PLC 9.1 Creating the user program 9.1.7.6 Changing a password Procedure To change the password, follow these steps: 1. Select the know-how protected blocks for which you want to change the password. Note You can only change the password for several blocks at once if all blocks selected have the same password. 2. Select the command "Know-how protection" in the "Edit" menu. The "Know-how protection" dialog will open. 3. Click the "Change" button. 4. Enter the old password in the "Old" field. 5. Enter the new password in the "New" field. 6. Enter the new password again in the "Confirm" field. 7. Confirm your entries with "OK". 8. Close the "Know-how protection" dialog by clicking on "OK". See also Protecting blocks (Page 1610) Setting up and removing block copy protection (Page 1612) Setting up block know-how protection (Page 1613) Opening know-how protected blocks (Page 1614) Printing know-how protected blocks (Page 1615) Removing block know-how protection (Page 1616) 9.1.7.7 Removing block know-how protection Procedure To remove block know-how protection, follow these steps: 1. Select the blocks for which you want to remove know-how protection. Note You can only remove know-how protection for several blocks at once if all blocks selected have the same password. 2. Select the command "Know-how protection" in the "Edit" menu. The "Know-how protection" dialog will open. 1616 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.2 Displaying program information 3. Deactivate the check box "Hide code (know-how protection)". 4. Enter the password. 5. Confirm your entries with "OK". Result Know-how protection will be disabled for the blocks selected. See also Protecting blocks (Page 1610) Setting up and removing block copy protection (Page 1612) Setting up block know-how protection (Page 1613) Opening know-how protected blocks (Page 1614) Printing know-how protected blocks (Page 1615) Changing a password (Page 1616) 9.2 Displaying program information 9.2.1 Overview of available program information Program information The program information of a user program contains the view specified in the following table. View Application Assignment list (Page 1618) Provides an overview of the address bits for the I, Q, and M memory areas already allocated within the user program. Also indicates if an address has been allocated by access from an S7 program or if the address has been assigned to a SIMATIC S7 module. Call structure (Page 1626) WinCC Basic V13.0 System Manual, 02/2014 Shows the call structure of the blocks within the user program and provides an overview of the blocks used and their relationships. 1617 Programming the PLC 9.2 Displaying program information View Application Dependency structure (Page 1633) Shows the list of blocks used in the user program. A block is shown at the first level and blocks that call or use this block are indented below it. In contrast to the call structure, instance blocks are listed separately. Resources (Page 1638) Shows the hardware resources of the CPU for objects (OB, FC, FB, DB, user-defined data types and PLC tags), for CPU memory areas and for the existing I/O modules. Displaying several views simultaneously You can generate and display several views for one or more user programs to facilitate testing and changing your user program. Displaying multiple views, for example, enables you to: Display all program information for a user program next to one another Compare different user programs 9.2.2 Displaying an assignment list 9.2.2.1 Introduction to the assignment list Program information in the assignment list The assignment list shows if an address has been allocated by access from an S7 program or if the address has been assigned to a SIMATIC S7 module. It is therefore an important basis for locating errors or changes in the user program. In the assignment list, you have a CPU-specific overview of which bit is used in which byte of the memory areas listed below: Input (I) Output (O) Bit memory (M) Timer (T) Counter (C) I/O (P) Display of the assignment list The assignment list of inputs, outputs, and bit memory is displayed in several separate work windows. 1618 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.2 Displaying program information Filters You can filter the display within the assignment list. You can use predefined filters or create your own. Displaying cross-reference information You have the option of displaying cross-reference information for selected addresses in the assignment list. You can display the cross-references for a selected address in the Inspector window using the "Cross-reference information" shortcut menu command. The command "Tools > Crossreferences" allows you to also open the cross-reference list for the selected object. Displaying the PLC tag table You can open the PLC tag table from the assignment list and edit the properties of the tags used. To do this select an address of the assignment list and select the "Open editor" command in the shortcut menu. Enabling the display of retentivity You can enable and disable the display of the retentive state of bit memory by selecting the "Hide/show retain area" toolbar button. See also Symbols in the assignment list (Page 1620) Layout of the assignment list (Page 1619) 9.2.2.2 Layout of the assignment list Layout of the assignment list Depending on the CPU, the assignment list is displayed in several work windows with the following operands. For S7-300/400 CPUs: Inputs Outputs Bit memory Timers Counters For S7-1200 CPUs: WinCC Basic V13.0 System Manual, 02/2014 1619 Programming the PLC 9.2 Displaying program information Inputs Outputs Bit memory Displaying inputs, outputs, bit memory, timers and counters It shows all operands used and their assignment in the S7 program. For all displayed operands, each line in the assignment list is dedicated to a byte of the memory area, in which the corresponding eight bits from 7 to 0 are labeled according to their access. In conclusion, a "bar" indicates if access is made by a byte (B), word (W) or double word (D). You can find an explanation of the symbols in the assignment list here. (Page 1620) See also Introduction to the assignment list (Page 1618) 9.2.2.3 Symbols in the assignment list Meaning of the symbols in the assignment list The following table shows the meaning of the symbols in the assignment list: Symbol Meaning Indicates the address assignment in the selected state. Indicates the address assignment in the non-selected state. Indicates that a pointer start address and a tag address access the same address range and that they are selected. Indicates that a pointer start address and a tag address access the same address range and that they are not selected. Indicates the pointer assignment in the selected state. Indicates the pointer assignment in the non-selected state. Indicates that the byte is in use with byte access and the corresponding tag is selected. The shortcut menu allows you to display cross-reference information for the selected variables as well as the PLC tag table. Indicates that the byte is in use with byte access and the corresponding tag is not selected. Indicates that the byte is in use with word access and the corresponding tag is selected. The shortcut menu allows you to display cross-reference information for the selected variables as well as the PLC tag table. Indicates that the byte is in use with word access and the corresponding tag is not selected. 1620 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.2 Displaying program information Symbol Meaning Indicates that the byte is in use with double word access and the corresponding tag is selected. The shortcut menu allows you to display cross-reference information for the selected variables as well as the PLC tag table. Indicates that the byte is in use with double word access and the corresponding tag is not selected. Background color: gray Indicates that a byte is in use with byte, word or double word access and that the address is also in use by the hardware. The gray background color indicates overlapping memory access. Background color: yellow Indicates that the address is not in use by the hardware. Indicates that the memory area has been defined as system memory. Indicates that the memory area has been defined as clock memory. See also Layout of the assignment list (Page 1619) Introduction to the assignment list (Page 1618) 9.2.2.4 Displaying an assignment list Requirement A project has been created with programmed blocks. Procedure Proceed as follows to display the assignment list: 1. Select the "Program blocks" folder or one or more of the blocks it contains. 2. Select the "Assignment list" command in the "Tools" menu. Result The assignment list for the selected program is displayed. View options in the assignment list Refer to view respective view options that are set to display the desired information in the assignment list. WinCC Basic V13.0 System Manual, 02/2014 1621 Programming the PLC 9.2 Displaying program information See also Setting the view options for the assignment list (Page 1622) Layout of the assignment list (Page 1619) 9.2.2.5 Setting the view options for the assignment list Introduction The following view options are available for the assignment list: Used addresses: When this check box is activated, the addresses, I/Os and pointers used in the program are displayed. Free hardware addresses: When this check box is activated, only the free hardware addresses are displayed. Requirement A project has been created with programmed blocks. The assignment list is open. Procedure Proceed as follows to set the view options for the assignment list: 1. Click on the arrow of the symbol ("View options") in the task bar. The view options for the assignment list are opened. Check marks are set in front of the activated view options. 2. If you want to activate or deactivate a view option, click on the respective check box and set or remove the check mark. Result The view options are set and the desired information is displayed in the assignment list. 1622 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.2 Displaying program information 9.2.2.6 Filter options in the assignment list Filter settings You can define your own filter settings for the assignment list. The following options are available for defining filters: Display all addresses of the address areas specified. Display of single, defined addresses from the selected address area, for example, "0" and "200". Display of complete areas from the selected address area, for example, "0 - 256". The following table provides an overview of all available options: Selection in the Selection Symbol Meaning Address area All CPU-dependent displayed addresses (I, O, M, T, C) can be activated as they are by default, or individual address areas can be activated. Check box is activated Only the activated address areas (I, O, M, T, C) are shown in the assignment list. Filter area Show assignment for all addresses * Displays the assignment of all addresses of the enabled address areas (I, Q, M). Show assignment for selected addresses, for example, for the inputs "IB 0" and "IB 256" 0;256 Assignments of selected addresses for the activated address areas (I) are shown. Show assignment for selected areas, for example, for the inputs "IB 0 to IB 100" and "IB 200 to IB 256". 0-100;200-256 9.2.2.7 Separate individual addresses and areas by a semicolon. Contiguous areas should be connected by a hyphen. Assignments of selected areas for the activated address areas (I) are shown. Defining filters for assignment list Requirement A project has been created with programmed blocks. The assignment list is open. Defining filter Proceed as follows to define a filter for the assignment list: 1. Click on the symbol ("Filter") in the task bar. The "Assignment List Filter" dialog opens. 2. Click on the symbol ("Create new filter") in the task bar. A new filter is created with the name "Filter_1". The check boxes for all addresses (inputs, outputs, memory bits, timers and counters) are activated by default for the filter. WinCC Basic V13.0 System Manual, 02/2014 1623 Programming the PLC 9.2 Displaying program information 3. If you want to change the name of the filter, click on the drop-down list in the task bar and enter a new filter name. 4. Deactivate the check boxes of addresses that are not to be affected by the filter. 5. Enter one of the following options in the filter area of the activated address: - Show all addresses used = "*" - Show single, defined addresses, for example, IB 0" and IB 25 = "0.25". Individual addresses and address areas are separated by commas or semicolons. - Show complete address areas, for example, IB 0 to IB 256 = "0-256". Complete address areas should be connected by a hyphen. 6. Confirm your entries with "OK". The newly defined filter is shown in the task bar of the assignment list under the specified name. Delete filter Proceed as follows to delete a filter: 1. Click on the symbol ("Filter") in the task bar. The filter dialog for the assignment list opens. 2. In the drop-down list of the task bar, select the filter you want to delete. 3. Click on the symbol ("Delete selected filter") in the task bar. The selected filter is deleted. See also Filter options in the assignment list (Page 1623) Displaying an assignment list (Page 1621) Introduction to the assignment list (Page 1618) 9.2.2.8 Filtering an assignment list Requirement A project has been created with programmed blocks. The assignment list is open. Procedure 1. Click on the arrow on the drop-down list. The available filter are displayed. 2. Select the desired filter. 1624 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.2 Displaying program information Result The assignment list is filtered according to the settings of the selected filter. Note The filter settings are saved when the project is closed. 9.2.2.9 Defining retentive memory areas for bit memories Introduction In the assignment list you can define the width of the retentive memory area for bit memories. The content of tags which are addressed in retentive memory is retained after power off and at the STOP to RUN transition after power on. The display of retentive bit memories can be enabled and disabled in the assignment list. If their display is enabled, retentive bit memories are identified by an icon in the "Address" column. Requirement The assignment list is open. Procedure Proceed as follows to define the width of the retentive memory area for bit memories: 1. Click "Retain" in the toolbar. The "Retain memory" dialog will open. 2. Starting at the count of 0, define the width of the retentive memory area by entering the last byte of this area in the input field. Watch out for any addresses of tags already assigned to the retentive area. 3. Load the block to the target system. Select the "Program blocks" folder in the Project tree and select the "Download to device" submenu in the shortcut menu. Result The width of the retentive memory area is defined. If enabled in the assignment list, an icon will indicate the retentive state of all tags in the "Address" column. WinCC Basic V13.0 System Manual, 02/2014 1625 Programming the PLC 9.2 Displaying program information 9.2.2.10 Enabling the display of retentive bit memories Introduction In the assignment list you can enable and disable the display of retentive bit memories. The retentive bit memories are identified by means of an icon in the "Address" column if the display of retentivity is enabled. Requirement The assignment list is open. Procedure Proceed as follows to enable and disable the display of retentive bit memories: 1. Click "Display/hide retentivity" in the toolbar. Result The retentive tags are identified by means of an icon in the "Address" column of the bit memory area if the display of retentivity is enabled. The icons in the "Address" column are hidden if the display of retentivity is disabled. 9.2.3 Displaying the call structure 9.2.3.1 Introduction to the call structure Call structure The call structure describes the call hierarchy of the block within an S7 program. It provides an overview of: The blocks used Jumps to the places of use of the blocks Relationships between blocks Local data requirements of the blocks Status of the blocks 1626 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.2 Displaying program information Information in the call structure Displaying the call stucture provides you with a list of the blocks used in the user program. The first level of the call structure is highlighted in color and shows the blocks that are not called by any other block in the program. Organization blocks are always shown on the first level of the call structure. Functions, function blocks and data blocks are only shown on the first level if they are not called by an organization block. When a block calls other blocks or functions, they are listed indented under the calling block. Instructions and blocks are shown in the call structure only if they are called by a block. View options The following view options are available for the call structure: Show conflicts only: When this check box is activated, only the conflicts within the call structure are displayed. Group multiple calls together: When this check box is activated, several block calls are grouped together. The number of block calls is displayed in the "Call frequency" column. The links to the various call locations are offered in a drop-down list in the "Details" column. Displaying the block calls You can display the block calls in a block by clicking on the arrow in front of the block title. To display the call information of all blocks, click on the "Expand list" icon in the toolbar. You can hide the total overview by clicking the "Collapse list" icon. Displaying cross-reference information You can display the cross-reference information for a block in the Inspector window by rightclicking on the relevant block and selecting the "Cross-reference information" command from the shortcut menu. To open the "Cross-references" view, click the "Cross-references" command in the shortcut menu. Displaying blocks in the program editor You can open the program editor and edit blocks there from the call structure. To do this select the required block in the call structure and select the "Open editor" command in the shortcut menu. WinCC Basic V13.0 System Manual, 02/2014 1627 Programming the PLC 9.2 Displaying program information Displaying deleted blocks The rows belonging to deleted blocks are identified by an icon. Note Please note that any existing local data can only be displayed or updated after compiling a block. See also Symbols in the call structure (Page 1628) 9.2.3.2 Symbols in the call structure Meaning of the symbols in the call structure The following table shows the meaning of the symbols in the call structure: Symbol Meaning Indicates an organization block (OB). Indicates a function block (FB). Indicates a function (FC). Indicates a data block (DB). Indicates that the block is declared as a multiinstance. The object has an interface dependency to an object connected to the left. Indicates that the block needs to be compiled again. Indicates that the data block needs to be compiled again. Indicates that the object is not available. Indicates that the interface causes a time stamp conflict. Indicates that the variable causes a time stamp conflict. Indicates that the block is not called directly or indirectly from an OB. Indicates that an object has know-how protection. 1628 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.2 Displaying program information Symbol Meaning Indicates that the block is normally called recursively. Indicates that a tag declaration in the interface has a recursive dependency: Scenario 1: FB1 calls FB2 and this then calls FB1. The instance data blocks of these FBs have a recursion in the interface. Scenario 2: A multiple instance FB uses the instance DB of its parent FB as a global DB. 9.2.3.3 Layout of the call structure Layout of the call structure The view of the call structure consists of the following columns: Column Content/meaning Call structure Shows an overview of the blocks called If the viewing option "Group multiple calls together" is enabled, several block calls are grouped together and the "Number of calls" column is displayed. Call type (!) Shows the type of call, for example recursive block call. Address Shows the absolute address of the block. With a function block, the absolute address of the corresponding instance data block is also shown. Call frequency Indicates the number of multiple calls of blocks. Details Shows the network or interface of the calling block. All information are offered as a link in this column. With this link, you can jump to the location of the block call in the program editor. If the viewing option "Group multiple calls together" option is enabled, the calls are grouped together and are available as links in a drop-down list. Local data (in path) Indicates the local data requirement of the full path. Blocks with optimized access have higher local data requirements because the information for the symbolic addressing is stored with them. Please note that any existing local data can only be displayed or updated after compiling a block. Local data (for blocks) Show the local data requirements of the block. Blocks with optimized access have higher local data requirements because the information for the symbolic addressing is stored with them. Please note that any existing local data can only be displayed or updated after compiling a block. WinCC Basic V13.0 System Manual, 02/2014 1629 Programming the PLC 9.2 Displaying program information See also Symbols in the call structure (Page 1628) Introducing the consistency check in the call structure (Page 1631) 9.2.3.4 Displaying the call structure Requirement A project has been created with blocks. Procedure Proceed as follows to display the call structure: 1. Select the "Program blocks" folder or one or more of the blocks it contains. 2. Select the "Call structure" command in the "Tools" menu. Result The call structure for the selected program is displayed. Note Please note that any existing local data can only be displayed or updated after compiling a block. See also Setting the view options for the call structure (Page 1631) 1630 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.2 Displaying program information 9.2.3.5 Setting the view options for the call structure Introduction The following view options are available for the call structure: Show conflicts only: Only the blocks causing conflicts within the call structure are displayed if this check box is activated. The following blocks cause conflicts: - Blocks executing any calls with older or newer code time stamps. - Blocks calling a block with modified interface. - Blocks using a tag with modified address and/or data type. - Block called neither directly, nor indirectly by an OB. - Blocks calling a block which no longer exists. Group multiple calls together: When this viewing option is enabled, several block calls and data block accesses are grouped together. The number of block calls is displayed in the "Call frequency" column. The links to the various call locations are offered in a drop-down list in the "Details" column. Requirement A project has been created with programmed blocks. The call structure is open. Procedure Proceed as follows to set the view options for the call structure: 1. Click on the arrow of the symbol ("View options") in the task bar. The view options for the call structure opens. Check marks are set in front of the activated view options. 2. If you want to activate or deactivate a view option, click on the respective check box and set or remove the check mark. Result The view options are set and the required information is displayed in the call structure. 9.2.3.6 Introducing the consistency check in the call structure Consistency check WinCC Basic V13.0 System Manual, 02/2014 1631 Programming the PLC 9.2 Displaying program information Changing the time stamp of a block during or after the program is generated can lead to time stamp conflicts, which in turn cause inconsistencies among the blocks that are calling and being called. Using the consistency check The "Consistency check" function is used to visualize inconsistencies when time stamp conflicts occur. Whe the consistency check is performed, the inconsistent blocks are shown in the call structure and marked with the correspoinding symbols. Most time stamp and interface conflicts can be rectified by recompiling the blocks. If compilation fails to clear up inconsistencies you can use the link in the "Details" column to go to the source of the problem in the program editor and manually eliminate any inconsistencies. The blocks marked in red must be recompiled. See also Symbols in the call structure (Page 1628) 9.2.3.7 Checking block consistency in the call structure Requirement A project has been created with programmed blocks. The call structure is open. Procedure Proceed as follows to check the block consistency: 1. Click on the symbol ("Consistency check") in the task bar. The block consistency is checked. Blocks found to be inconsistent are marked accordingly by a symbol. 2. If a block is inconsistent, click on the arrow in front of the block title in the call structure. The inconsistent blocks are displayed. The exact problem locations are listed as links in the "Details" column. 3. Click on the respective link in the "Details" column to jump to the location in the block requiring correction. 4. Check and correct the inconsistencies in the blocks. 5. Recompile the blocks by selecting the required blocks and clicking on the command "Compile" in the shortcut menu. 6. Download the corrected blocks to the target system by clicking the command "Download to device" in the shortcut menu. 1632 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.2 Displaying program information Result The block consistency is checked. The inconsistencies in the blocks are corrected. The corrected blocks are loaded to the target system. See also Symbols in the call structure (Page 1628) 9.2.4 Displaying the dependency structure 9.2.4.1 Introduction to the dependency structure Introduction The dependency structure shows the dependencies each block has to other blocks in the program. Information in the dependency structure Displaying the dependency structure provides you with a list of the blocks used in the user program. A block is shown at the far left and blocks that call or use this block are indented below it. The dependency structure also shows the status of the individual blocks using symbols. Objects causing a time stamp conflict and perhaps leading to an inconsistency in the program are marked with various symbols. The dependency structure is an extension of the cross-reference list for objects. View options The following view options are available for the dependency structure: Show conflicts only: When this check box is activated, only the conflicts within the dependency structure are displayed. Group multiple calls together: When this check box is activated, several block calls are grouped together. The number of block calls is shown numerically in the "Dependency structure" column. The links to the various call locations are offered in a drop-down list in the "Details" column. Displaying the dependency structure Clicking on the arrow in front of the block title displays the blocks that call or use this block. To display the dependencies of all blocks, click the "Expand list" icon in the toolbar. WinCC Basic V13.0 System Manual, 02/2014 1633 Programming the PLC 9.2 Displaying program information You can hide the total overview by clicking the "Collapse list" icon. Displaying cross-reference information You can display the cross-reference information for a block in the Inspector window by rightclicking on the respective block and selecting the "Display Usage" command from the shortcut menu. Displaying blocks in the program editor You can open the program editor and edit blocks there from the dependency structure. To do this select the required block in the dependency structure and select the "Open editor" command in the shortcut menu. 9.2.4.2 Layout of the dependency structure Layout of the dependency structure The view of the dependency structure consists of the following columns: Column Content/meaning Dependency It indicates the dependencies between each block and the other blocks in the program. Call type (!) Shows the type of call, for example recursive block call. Address Shows the absolute address of the block. Call frequency Indicates the number of multiple calls of blocks. Details Shows the network or interface of the called block. All information are offered as a link in this column. With this link, you can jump to the location of the block call in the program editor. If the viewing option "Group multiple calls together" option is enabled, the calls are grouped together and are available as links in a drop-down list. See also Symbols in the dependency structure (Page 1635) 1634 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.2 Displaying program information 9.2.4.3 Symbols in the dependency structure Meaning of the symbols in the dependency structure The following table shows the meaning of the symbols in the dependency structure: Symbol Meaning Indicates an organization block (OB). Indicates a function block (FB). Indicates a function (FC). Indicates a data block (DB). The object has an interface dependency to an object connected to the left. Indicates that the block needs to be compiled again. Indicates that the data block needs to be compiled again. Indicates that there is an inconsistency with this object. Indicates that an object has know-how protection. Indicates that a tag declaration in the interface has a recursive dependency: Scenario 1: FB1 calls FB2 and this then calls FB1. The instance data blocks of these FBs have a recursion in the interface. Scenario 2: A multiple instance FB uses the instance DB of its parent FB as a global DB. 9.2.4.4 Displaying the dependency structure Requirement A project has been created with programmed blocks. Procedure Proceed as follows to display the dependency structure: 1. Select the block folder or one or more of the blocks contained therein. 2. Select the "Dependency structure" command in the "Tools" menu. Result The dependency structure for the selected program is displayed. WinCC Basic V13.0 System Manual, 02/2014 1635 Programming the PLC 9.2 Displaying program information See also Setting the view options for the dependency structure (Page 1636) 9.2.4.5 Setting the view options for the dependency structure Introduction The following view options are available for the dependency structure: Show conflicts only: When this check box is activated, only the conflicts within the dependency structure are displayed. The following blocks cause conflicts: - Blocks executing any calls with older or newer code time stamps. - Blocks called by a block with modified interface. - Blocks using a tag with modified address and/or data type. - Block called neither directly, nor indirectly by an OB. Group multiple calls together: When this check box is activated, several block calls are grouped together. The number of block calls is shown in the relevant column. The links to the various call locations are offered in a drop-down list in the "Details" column. Requirement A project has been created with programmed blocks. The dependency structure is open. Procedure Proceed as follows to set the view options for the dependency structure: 1. Click on the arrow of the symbol ("View options") in the task bar. The view options for the dependency structure are opened. Check marks are set in front of the activated view options. 2. If you want to activate or deactivate a view option, click on the respective check box and set or remove the check mark. Result The view options are set and the required information is displayed in the dependency structure. 1636 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.2 Displaying program information 9.2.4.6 Introducing the consistency check in the dependency structure Consistency check Changing the time stamp of a block during or after the program is generated can lead to time stamp conflicts, which in turn cause inconsistencies among the blocks that are calling and being called. Using the consistency check The "Consistency check" function is used to visualize inconsistencies. Whe the consistency check is performed, the inconsistent blocks are shown in the dependency structure and marked with the correspoinding symbols. Most time stamp and interface conflicts can be rectified by recompiling the blocks. If compilation fails to clear up inconsistencies you can use the link in the "Details" column to go to the source of the problem in the program editor and manually eliminate any inconsistencies. The blocks marked in red must be recompiled. See also Layout of the dependency structure (Page 1634) Symbols in the dependency structure (Page 1635) 9.2.4.7 Checking block consistency in the dependency structure Requirement A project has been created with programmed blocks. The dependency structure is open. Procedure Proceed as follows to check the block consistency: 1. Click on the symbol ("Consistency check") in the task bar. The block consistency is checked. Blocks found to be inconsistent are marked accordingly by a symbol. 2. If a block is inconsistent, click on the arrow in front of the block title in the dependency structure. The inconsistent blocks are displayed. The exact problem locations are listed as links in the "Details" column. 3. Check and correct the inconsistencies in the blocks. WinCC Basic V13.0 System Manual, 02/2014 1637 Programming the PLC 9.2 Displaying program information 4. Recompile the blocks by selecting the required blocks and clicking on the command "Compile" in the shortcut menu. 5. Download the corrected blocks to the target system by clicking the command "Download to device" in the shortcut menu. Result The block consistency is checked. The inconsistencies in the blocks are corrected. The corrected blocks are loaded to the target system. See also Symbols in the dependency structure (Page 1635) 9.2.5 Displaying CPU resources 9.2.5.1 Introducing resources Introduction The "Resources" tab indicates the hardware resources of the configured CPU for: the used programming objects, the assignment of the different memory areas within the CPU and the assigned inputs and outputs of the existing input and output modules. Information provided in the "Resources" tab The resources tab provides an overview of the hardware resources. The display in this tab depends on the CPU which you are using. The following information is displayed: the programming objects used in the CPU (e.g. OB, FC, FB, DB, data types and PLC tags) the memory areas available on the CPU (load memory, work memory - divided into code work memory and data work memory depending on the CPU -, retentive memory), their maximum size and utilization by the programming objects stated above the I/O of modules which can be configured for the CPU (I/O modules, digital input modules, digital output modules, analog input modules, and analog output modules), including the I/ O already in use. Display of the maximum available load memory The maximum size of available load memory can be selected from a drop-down list box in the "Total" row of the "Load memory" column. 1638 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.2 Displaying program information Display of the maximum available work memory The maximum size of available work memory is displayed in the "Work memory" column or in the "Code work memory" and "Data work memory" columns in the "Total" row. Display of the maximum available retentive memory The maximum size of available retentive memory can be selected from a drop-down list box in the "Total" row of the "Retentive memory" column. Note Retentive memory data All bit memories and data blocks specified as retentive will be integrated in the calculation of the retentive data. Updating the display in the "Resources" tab Click the "Update view" toolbar button to update the display of objects. Benefits of the display in the "Resources" tab The "Resources" tab of the program information dialog provides a detailed list of all objects and of the corresponding memory area used. The tab also indicates shortage of resources and helps to avoid such states. Blocks which are not compiled can be identified as their size is indicated by a question mark. See also Layout of the "Resources" tab (Page 1640) Displaying resources (Page 1641) Selecting the maximum load memory available (Page 1642) WinCC Basic V13.0 System Manual, 02/2014 1639 Programming the PLC 9.2 Displaying program information 9.2.5.2 Layout of the "Resources" tab Layout of the "Resources" tab in the program information The view of the "Resources" tab consists of the following columns: Column Content/meaning Objects The "Details" area provides an overview of the programming objects available in the CPU, including their memory assignments. Load memory Displays the maximum load memory resources of the CPU as a percentage and as absolute value. The values displayed under "Total" provide information on the maximum memory available in the load memory. The values displayed under "Used" provide information on the memory actually used in the load memory. If a value is displayed in red, the available memory capacity has been exceeded. Work memory or code and data work memory Displays the maximum work memory resources of the CPU as a percentage and as absolute value. The work memory depends on the CPU and is divided into "Code work memory" and "Data work memory" for a CPU from the S7-400 or S7-1500 series, for example. The values displayed under "Total" provide information on the maximum memory available in the work memory. The values displayed under "Used" provide information on the memory space actually used in the work memory. If a value is displayed in red, the available memory capacity has been exceeded. Retentive memory Displays the maximum resources for retentive memory in the CPU as a percentage and as absolute value. The values displayed under "Total" provide information on the maximum memory available in the retentive memory. The values displayed under "Used" provide information on the memory actually used in the retentive memory. If a value is displayed in red, the available memory capacity has been exceeded. 1640 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.2 Displaying program information Column Content/meaning I/O Displays the I/Os which are available on the CPU, including their module-specific availability in the next columns. The values displayed at "Configured" provide information about the maximum number of I/O available. The values displayed under "Used" provide information on the actually used inputs and outputs. DI / DQ / AI / AQ Displays the number of configured and used inputs/outputs: DI = Digital inputs DQ = Digital outputs AI = Analog inputs AQ = Analog outputs The values displayed at "Configured" provide information about the maximum number of I/O available. The values displayed under "Used" provide information on the actually used inputs and outputs. See also Displaying resources (Page 1641) Selecting the maximum load memory available (Page 1642) Introducing resources (Page 1638) 9.2.5.3 Displaying resources Requirement A project with programmed blocks has been created. Procedure Proceed as follows to display the resources of the respective CPU memory areas: 1. Select the block folder below the relevant CPU, or one or several of the blocks contained therein. 2. Select the "Resources" command in the "Tools" menu. Result The memory resources of the assigned CPU are displayed. WinCC Basic V13.0 System Manual, 02/2014 1641 Programming the PLC 9.3 Displaying cross-references 9.2.5.4 Selecting the maximum load memory available Requirement A project with programmed blocks has been created. Procedure Proceed as follows to display the available maximum of load memory resources: 1. Select the block folder below the relevant CPU, or one or several of the blocks contained therein. 2. Select the "Resources" command in the "Tools" menu. 3. In the dialog that is displayed, open the drop-down list in the "Total" field of the "Load memory" column by clicking the icon. 4. Select a corresponding value for the CPU used by clicking it in the drop-down list box. Result The "Total" field displays the selected maximum memory resources. Note Display of maximum memory resources If a value is displayed in red for the maximum memory resources, the available memory capacity has been exceeded. In this case, adapt the memory capacity as described above. 9.3 Displaying cross-references 9.3.1 General information about cross references Introduction The cross-reference list provides an overview of the use of operands and tags within the user program. 1642 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.3 Displaying cross-references 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 operands, tags and block calls you have used. From the cross-references, you can jump directly to the point of use of operands and tags. During a program test or when troubleshooting, you are informed of the following: - Which operand is processed by which command in which block. - Which tag is used in which picture. - Which block is called by which other block. - Cross-reference information for subordinate and higher-level structures. As part of the project documentation, the cross-references provide a comprehensive overview of all operands, memory areas, blocks, tags and pictures used. See also Structure of the cross-reference list (Page 1643) Displaying the cross-reference list (Page 1644) Displaying cross-references in the Inspector window (Page 1646) 9.3.2 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. Here, you can see the users of the object. The assigned tool tips provide additional information about each object. Structure of the cross-reference list The cross-reference list has the following structure: WinCC Basic V13.0 System Manual, 02/2014 Column Content/meaning Object Name of the object that uses the lower-level objects or that is being used by the lower-level objects. Number Number of uses Point of use Each point of use, for example, network 1643 Programming the PLC 9.3 Displaying cross-references Column Content/meaning Property Special properties of referenced objects, for example, the tag names in multi-instance declarations. as Shows additional information about the object, e.g., that an instance DB is used as template or as multiple instance. Access Type of access, whether access to the operand is read access (R) and/ or write access (W). Address Address of the operand Type Information on the type and language used to create the object Path Path of object in project tree 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 buttons in the toolbar of the cross-reference list: Update cross-reference list Updates the current cross-reference list. Making settings for the cross-reference list Here, you select check boxes to 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, including other product-specific columns, in ascending or descending order. To do this, click on the relevant column title. See also General information about cross references (Page 1642) Displaying the cross-reference list (Page 1644) 9.3.3 Displaying the cross-reference list Requirements You have created a project. 1644 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.3 Displaying cross-references Introduction There are several ways of displaying cross-references depending on whether you are in the Portal view or in the Project view and which object you have selected in the project tree. In the Portal view, you can only display cross-references for the entire CPU; in the Project view, you can, for example, display cross-references for the following objects: "PLC tags" folder "PLC data types" folder "Program blocks" folder "Tags and connections" folder Individual tags Individual PLC data types Individual blocks Technological objects Watch tables Displaying cross-references Proceed as follows to display cross-references: 1. Select the required action in the Portal view, for example "PLC programming" and the "Show cross-references" command or select one of the objects listed above in the Project view and select the "Cross-references" command in the "Tools" menu. The cross-reference list is displayed. 2. Click the "Used by" button to display where the objects shown in the cross-reference list are used. 3. Click the "Uses" button to view the users of the objects displayed in the cross-reference list. 4. You can perform the following actions using the buttons in the toolbar: - Update cross-reference list - Making settings for the cross-reference list - Collapse entries - Expand entries 5. You can sort the entries in the "Object" and "Address" columns in ascending or descending order by clicking on the relevant column title. 6. To go to the point of use of the object, click on the displayed link. See also General information about cross references (Page 1642) Structure of the cross-reference list (Page 1643) WinCC Basic V13.0 System Manual, 02/2014 1645 Programming the PLC 9.3 Displaying cross-references 9.3.4 Displaying cross-references in the Inspector window Introduction The Inspector window displays cross-reference information about an object you have selected in the "Info > Cross-references" tab. This tab displays the instances where a selected object is being used and the other objects using it. The Inspector window also includes blocks which are only available online in the crossreferences. You can use the "Show overlapping access..." shortcut menu command to also have overlapping access across block borders displayed for selected objects. Structure The Inspector window displays the cross-reference information in tabular format. Each column contains specific and detailed information on the selected object and its application. The table below shows the additional information listed in the "Info > 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. Number Number of uses Point of use Each location of use, for example, network Property Special properties of referenced objects, for example, the tag name in multi-instance declarations as Shows additional information about the object, e.g., that an instance DB is used as template or as multiple instance. Access Access mode Shows whether the operand is accessed by a read (R) and/or write (W) operation. Address Address of the operand Monitor value This column will only be displayed when the program editor is open. Type Information about the type and language used to create the object Path Path of object in project tree Depending on the installed products, additional columns or different columns are displayed for the cross-references. 1646 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.4 Testing the user program 9.4 Testing the user program 9.4.1 Basics of testing the user program Functions You have the option of testing the running of your user program on the device. You can then monitor signal states and values of tags and can assign values to tags to simulate certain situations in the running of the program. Requirement There must be an executable program loaded on the device. Test options The following test options are available: Testing with program status The program status allows you to monitor the running of the program. You can display the values of operands and the results of logic operations (RLO) allowing you to recognize and fix logical errors in your program. Testing in single step mode (S7-300/400 only) You can test blocks you created in STL or SCL in the single step mode. You do this by setting breakpoints in the program code at which program execution stops. You can then continue to run the program one step at a time. Within a CPU, you can test either with program status or in single step mode. You cannot, however, use both test options at the same time within a CPU. Testing with the watch table With the watch table, you can monitor and modify the current values of individual tags in the user program or on a CPU. You can assign values to individual tags for testing and run the program in a variety of different situations. You can also assign fixed values to the I/O outputs of a CPU in STOP mode, for example to check the wiring. Testing with the force table With the force table, you can monitor and force the current values of individual tags in the user program or on a CPU. When you force, you overwrite individual tags with specified values. This allows you to test your user program and run through various situations. When forcing, make sure that you keep to the necessary safety measures for forcing (Page 1700)! See also Introduction to testing with program status (Page 1648) Introduction to testing with the watch table (Page 1655) Introduction for testing with the force table (Page 1682) WinCC Basic V13.0 System Manual, 02/2014 1647 Programming the PLC 9.4 Testing the user program 9.4.2 Testing with program status 9.4.2.1 Introduction to testing with program status Program Status function If you display the program status, you can monitor the execution of the program. This provides you with an overview of the values of the individual operands and the results of the logic operations and you can check whether the components of the automation system are correctly controlled. The display of the program execution in the program status can differ slightly, depending on the CPU family used. Testing with program status for S7-300/400 During testing with program status, the CPU cycle time can become extended in test mode because the recording of all test data can deviate from the duration of the programmed instructions due to the CPU capacity and therefore not run in realtime. During the execution of the following test functions an alarm indicating the danger of a timeout is displayed once for each online session. During testing with call conditions During testing with breakpoints You can only perform these test functions after you have acknowledged the alarm. Note With older CPUs from the S7-300/400 CPU family, you will need to change the operating response using the hardware configuration and then download the hardware configuration to the device. You have the option to set the "Process operation" or "Test operation" operating response. Restrictions with the "Program status" function The monitoring of loops can increase the cycle time significantly, depending in each case on the number of tags to be monitored and on the actual number of loops processed. To ensure that the cycle time is influenced as little as possible, the "Program status" function is restricted as follows: 1648 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.4 Testing the user program The status display of a programmed loop is stopped at the return point. WARNING Testing with program status A test with the "Program status" function can cause serious damage to property or injury to persons if there are functional disturbances or program errors. Make sure that no dangerous situations can arise before you conduct a test with the "Program status" function. 9.4.2.2 Switching test with program status on/off You can monitor all blocks by switching on the program status of the block. This function is available to you for all code blocks, regardless of the programming language used. For blocks that were programmed with LAD or FBD, you can also enable the program status from a specific position or for a specific selection. You can switch on the program status for an open block directly, or open a block from the calling block and view the program status. Note The resources for testing with program status are limited. If there are not enough resources for the current test, earlier tests will be terminated. Requirement The identical block exists in the device. Switching the program status on or off directly in the block To switch the program status for a block on or off directly in the block, follow these steps: 1. Open the block for which you wish to switch on the program status. 2. Click the "Monitoring on/off" button in the toolbar. If you have not already established an online connection, the "Go online" dialog opens. In this dialog, you can establish an online connection. See also: Establishing and terminating an online connection 3. Click the "Monitoring on/off" button in the toolbar again to switch the program status off. Switching on or off program status starting at a specific point in a network To start the program status for LAD and FBD at a specific point, follow these steps: 1. Open the block for which you wish to switch on the program status. 2. Click the "Monitoring on/off" button in the toolbar. 3. Right-click on the tag you want program status to start from. WinCC Basic V13.0 System Manual, 02/2014 1649 Programming the PLC 9.4 Testing the user program 4. Select "Modify > "Monitor from here" in the shortcut menu. 5. Click the "Monitoring on/off" button in the toolbar again to switch the program status off. Switching on or off program status for selected tags To start the program status for LAD and FBD for selected tags, follow these steps: 1. Open the block for which you wish to switch on the program status. 2. Click the "Monitoring on/off" button in the toolbar. 3. Select the tags for which you want to start the program status. 4. Select "Modify > Monitor selection" in the shortcut menu. 5. Click the "Monitoring on/off" button in the toolbar again to switch the program status off. Switching on program status from the calling block To switch on the program status for a block from the calling block (e.g. OB1), follow these steps: 1. Open the calling block. 2. Right-click on the block call. 3. Select the command "Open and monitor" in the shortcut menu. The block will open in the program editor. An online connection is established and the program status is displayed. Note If the calling block is programmed in SCL and the called block is an FB, the FB is opened with "Open and monitor". To monitor the FB, you then need to switch on the program status directly in the FB. Result If you enable the display of the program status, an online connection is established and the program status is displayed. When you turn off the display of the program status, you can terminate the online connection at the same time. The call path of the block is shown under the block interface. For S7-300/400 and S7-1500 CPUs, you can change the call condition if required using the button on the right edge. 9.4.2.3 Editing blocks during the program test If you edit blocks while the test with program status is still running, online monitoring will be interrupted and you will be able to edit the block offline. If the block is not available offline in the project, you will first have to load it from the device to the project. After editing the block, you will also have to compile and download it again. 1650 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.4 Testing the user program Procedure To edit blocks while the test with program status is still running, follow these steps: 1. Edit the block as necessary. The test with program status is interrupted and the block is switched offline assuming it exists offline. 2. If the block does not exist offline, load it to the project from the device. 3. Compile the block. See also: Auto-Hotspot 4. Download the block to the device. See also: Auto-Hotspot Result The block now contains your modifications both online and offline. The online connection is reestablished and testing with program status continues. 9.4.2.4 Modifying tags in the program status While testing with the program status, you have the option of modifying tags to the following values once and immediately: Modify to 1 Modifies tags of the "Bool" data type to the value "True". Modify to 0 Modifies tags of the "Bool" data type to the value "False" Modify operand You can enter a modify value for tags that do not belong to the "Bool" data type. Note that you cannot modify peripheral inputs, for example, via TagName:P. Procedure To modify tags during testing with the program status, proceed as follows: 1. Right-click on the tag you want to modify. 2. Select one of the following commands in the shortcut menu: - "Modify > Modify to 1" - "Modify > Modify to 0" - "Modify > Modify operand" 3. If you select "Modify operand", the "Modify operand" dialog opens. Enter the value you require in the "Modify value" box and confirm with "OK". WinCC Basic V13.0 System Manual, 02/2014 1651 Programming the PLC 9.4 Testing the user program 9.4.2.5 Switching display formats in the program status Introduction The display formats for tags are generally displayed in "integer" form. In the program status, you have the option of switching the current display format by means of the shortcut menu. The possible display formats for a tag are offered in a list. This is useful, for example, when you need a hexadecimal display in order to search for a hexadecimal error code. Procedure To switch the display format, follow these steps: 1. Open the desired block in the programming editor. 2. Switch on the program status by clicking "Monitoring on/off" in the toolbar. If you have not already established an online connection, the "Go online" dialog opens. In this dialog, you can establish an online connection. 3. Select the tags for which you want to start the program status. 4. Select "Modify > Monitor selection" in the shortcut menu to start monitoring this tag. 5. Select the desired tag at the corresponding block output and then select the desired display format in the shortcut menu, for example, "Modify > Display format > Hexadecimal". Result The display format for the selected tag is shown in hexadecimal form. Note Switching the display format in the program status Please note that it is not possible to switch the display format for unconnected outputs, as no monitoring value is output in this case. 9.4.2.6 Examples of program status display Program status display for LAD programs Displays in program status The display of the program status is updated cyclically. The following figure shows an example of the program status display for LAD: 1652 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.4 Testing the user program Representation of the program status You can recognize the status of individual instructions and lines of a network quickly based on the color and type of lines and symbols. The following table shows the relationship between representation and status: Representation Status Green solid Satisfied Blue dashed Not satisfied Gray solid Unknown or not executed Black Not interconnected Parameter in a frame with a saturation of 100 % Value is current Parameter in a frame with a saturation of 50 % Value originates from an earlier cycle. The point in the program was not executed in the current cycle. Program status display for FBD programs Displays in program status The display of the program status is updated cyclically. The following figure shows an example of the program status display for FBD: WinCC Basic V13.0 System Manual, 02/2014 1653 Programming the PLC 9.4 Testing the user program Representation of the program status You can recognize the status of individual instructions and lines of a network quickly based on the color and type of lines and symbols. The following table shows the relationship between representation and status: Representation Status Green solid Satisfied Blue dashed Not satisfied Gray solid Unknown or not executed Black Not interconnected Parameter in a frame with a saturation of 100 % Value is current Parameter in a frame with a saturation of 50 % Value originates from an earlier cycle. The point in the program was not executed in the current cycle. The values of the operands are displayed above the relevant operand name in a gray box. Note Program status display for outputs which are not interconnected Please note that a monitor value cannot be displayed for outputs which are not interconnected. Program status display for SCL programs Displays in program status The display of the program status is updated cyclically and shown in a table. The table is displayed immediately beside the SCL program and you can see the program status for each line of the program. The table contains the following information: Tag names Value You can move the table to the left or right at any time. The following figure shows an example of the program status display for SCL: In the first column, you can see the name of the tag for which the current value is being displayed. If the line includes the "IF", "WHILE" or "REPEAT" instruction, the result of the instruction is displayed in the line as "True" or "False". If the line contains more than one tag, the value of the first tag is displayed. In both cases, all tags of these lines are displayed with 1654 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.4 Testing the user program their values in a separate list as soon as you select a line. If you place the cursor in a tag in the program code, this is shown in bold face in the list. You can also display the other tags of a line explicitly by clicking the arrow right located in front of lines containing more than one tag. If the code of the line is not executed, the tag name is displayed in the values table in gray text. The current values of the tags are displayed in the last column. If no values can be displayed for a tag, the line has a yellow background and three question marks are shown. In this case, select the "Create extended status information" check box in the properties of the block and download the block to the device again. All values are then displayed. 9.4.3 Testing with the watch table 9.4.3.1 Introduction to testing with the watch table Overview The following functions are available in the watch table: Monitoring tags This displays the current values of the individual tags of a user program or a CPU on the programming device or PC. Modifying tags You can use this function to assign specific values to the individual tags of a user program or CPU. Modifying is also possible with Test with program status . "Enable peripheral outputs" and "Modify now" These two functions enable you to assign specific values to individual peripheral outputs of a CPU in STOP mode. You can also use them to check your wiring. Monitoring and modifying tags The following tags can be monitored and modified: Inputs, outputs, and bit memory Contents of data blocks I/O Possible applications The advantage of the watch table is that a variety of test environments can be stored. This enables you to reproduce tests during commissioning or for service and maintenance purposes. WinCC Basic V13.0 System Manual, 02/2014 1655 Programming the PLC 9.4 Testing the user program See also Creating and editing watch tables (Page 1659) Layout of the watch table (Page 1656) Basic mode and expanded mode in the watch table (Page 1657) Icons in the watch table (Page 1658) 9.4.3.2 Layout of the watch table Introduction A watch table contains the tags you defined for the entire CPU. A "Watch and force tables" folder is automatically generated for each CPU created in the project. You create a new watch table in this folder by selecting the "Add new Watch table" command. Layout of the watch table The columns displayed in the watch table depend on the mode you are working in: basic mode or expanded mode. The following additional columns are shown in expanded mode: Monitor with trigger Modify with trigger The names of the columns can also be changed dynamically based on the action. Meaning of the columns The following table shows the meaning of the individual columns in basic mode and expanded mode: Mode Column Basic mode Meaning Identifier column Name Name of the inserted tag Address Address of the inserted tag Display format Selected display format Monitor value Values of the tags, depending on the selected display format. Modify value Value with which the tag is modified. Select the tag to be modified by clicking the corresponding check box. The following additional columns are shown in expanded mode: 1656 Comment Comment for documentation of the tags Monitor with trigger Display of selected monitoring mode Modify with trigger Display of selected modify mode WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.4 Testing the user program See also Icons in the watch table (Page 1658) 9.4.3.3 Basic mode and expanded mode in the watch table Difference between basic mode and expanded mode in the watch table Depending on the mode specified, the watch table displays different columns and column headings that can be used to perform different actions. You will find a detailed list of the columns in Layout of the watch table (Page 1656). Switching between basic mode and expanded mode You have the following options of toggling between the basic and expanded mode: Click the icon "Show/hide advanced setting columns". Click this icon again to return to the basic mode. Or: Activate the check box for the "Expanded Mode" command in the "Online" menu. Deactivate this check box to return to the basic mode. Functionality in expanded mode The following functionality is only possible in expanded mode: Monitor with trigger Modify with trigger Enable peripheral outputs Monitoring peripheral inputs Controlling peripheral outputs NOTICE Danger of a time-out while monitoring peripheral inputs and controlling peripheral outputs Note that the monitoring of peripheral inputs and the controlling of peripheral outputs in the watch table can result in a time-out. The CPU assumes the "STOP" mode. See also Setting the monitoring and modify mode (Page 1670) WinCC Basic V13.0 System Manual, 02/2014 1657 Programming the PLC 9.4 Testing the user program 9.4.3.4 Icons in the watch table Meaning of the icons The following table shows the meaning of the icons in the watch table: Icon Meaning Identifies a table inside the project tree as a watch table. Shows information in the identifier column. Inserts a row before the selected row. Inserts a row after the selected row. Modifies the addresses of all selected tags immediately and once. This command is executed once and as quickly as possible without reference to a defined trigger point in the user program. Modifies the addresses of all selected tags with reference to a defined trigger point in the user program. Disables the command output disable of the peripheral outputs. You can then modify the peripheral outputs when the CPU is in STOP mode. Displays all columns of expanded mode. If you click this icon again, the columns of expanded mode will be hidden. Displays all modify columns. If you click this icon again, the modify columns will be hidden. Starts monitoring of the visible tags in the active watch table. The default setting for the monitoring mode in basic mode is "permanent". In expanded mode, you can set defined trigger points for the monitoring of tags. Starts monitoring of the visible tags in the active watch table. This command is executed immediately and the tags are monitored once. Displays the check box for the selection of tags to be modified. Indicates that the value of the selected tag has been modified to "1". Indicates that the value of the selected tag has been modified to "0". Indicates that the address is being used multiple times. Indicates that the substitute value is being used. Substitute values are values that are output to the process in case of signal output module faults or are used instead of a process value in the user program in case of signal input module faults. The substitute values can be assigned by the user (e.g., retain old value). Indicates that the address is blocked because it is already being modified. Indicates that the address cannot be modified. Indicates that the address cannot be monitored. Indicates that an address is being forced. Indicates that an address is being partly forced. 1658 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.4 Testing the user program Icon Meaning Indicates that an associated I/O address is being fully or partly forced. Indicates that an address cannot be fully forced. Example: It is indeed possible to force the address QW0:P, but it is not possible to force the address QD0:P since this address area is eventually not available on the CPU. Indicates that a syntax error occurred. Indicates that the address is selected but at the moment e.g. has not yet been modified. See also Layout of the watch table (Page 1656) 9.4.3.5 Creating and editing watch tables Creating a watch table Introduction The watch table allows you to monitor and modify tags in the user program. Once you have created a watch table, you can save it, duplicate it, and print it and use it again and again to monitor and modify tags. Requirement A project is open. Procedure To create a watch table, follow these steps: 1. Click "Project view" in the status bar. The project view is displayed. 2. In the project tree, double-click the CPU for which you want to create a watch table. 3. Double-click the "Watch and force tables" folder and then the "Add new watch table" command. A new watch table is added. 4. In the "Name" column or in the "Address" column, enter the name or the absolute address for the tags that you want to monitor or modify. 5. You can select a display format from the drop-down list in the "Display format" column if you want to change this default setting. 6. Now decide whether you want to monitor or modify the entered tags and, if applicable, enter the desired values for modifying. WinCC Basic V13.0 System Manual, 02/2014 1659 Programming the PLC 9.4 Testing the user program Opening a watch table Requirement A watch table has been created. Procedure To open a watch table, follow these steps: 1. Open the "Watch and force tables" folder below the desired CPU. 2. Double-click on the required watch table in the folder. Result The selected watch table opens. Copying and pasting a watch table Requirement A watch table has been created. Procedure To copy a watch table, follow these steps: 1. Right-click the watch table that you want to copy. 2. In the context menu, select "Copy". 3. In the project tree, open the folder structure for the CPU in which you want to paste the copied watch table. 4. Right-click on the "Watch and force tables" folder. 5. In the context menu, select "Paste". 6. Alternatively, you can select the entire contents of the watch table and Drag & Drop it onto another watch table. Result A copy of the selected watch table is placed in the "Watch and force tables" folder of the relevant CPU. 1660 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.4 Testing the user program Saving a watch table Prerequisite A watch table has been created. Procedure To save a watch table, follow these steps: 1. In the project tree select the watch table you want to save. 2. If you wish to change the preset name of the table, select the "Rename" command in the context menu and enter a new name for the table. 3. In the "Project" menu, select "Save". Note that this save operation will save the entire project. Result The contents of the watch table and the project are saved. Note You can reuse saved watch tables to monitor and modify tags when retesting your program. 9.4.3.6 Entering tags in the watch table Basic information on entering tags in the watch table Recommended procedure Select the tags whose values you want to monitor or modify, and enter them in the watch table. When entering tags into the watch table, please note that these tags must be previously defined in the PLC tag table. When entering tags, work from the outside to the inside. This means that you start by entering the tags for the inputs in the watch table. Then, you enter the tags that are affected by the inputs or that affect the outputs. Finally, you enter the tags for the outputs. Example of filling out a watch table Enter the absolute address to be monitored or modified in the "Address" column. Enter the symbolic name for the tag in the "Name" column. WinCC Basic V13.0 System Manual, 02/2014 1661 Programming the PLC 9.4 Testing the user program Select the display format you require from the drop-down list in the "Display format" column, if you do not want to use the default setting. Now decide whether you want to monitor or modify the entered tags. Enter the desired values for modifying as well as a comment in the corresponding columns of the watch table. Create comment row If required, you can create a comment row by entering the string "//" in the "Name" column. Syntax check When you enter the tags in the watch table, the syntax of each cell is checked when you exit the cell. Incorrect entries are marked in red. Note When you place the mouse pointer in a cell marked in red, brief information is displayed with additional notes on the error. See also Permitted operands for the watch table (Page 1662) Permissible modify values for the watch table (Page 1663) Permitted operands for the watch table Permissible operands for the watch table The following table shows the operands that are permitted for the watch table: Permitted operand Example of data type Example (International mnemonics) Input/output/bit memory BOOL I1.0, Q1.7, M10.1 I0.0:P; Q0.0:P Input/output/bit memory BYTE IB1/QB10/MB100 IB1:P; QB1:P Input/output/bit memory WORD IW1; QW10; MW100 IW2:P; QW3:P Input/output/bit memory DWORD ID4; QD10; MD100 ID2:P; QD1:P 1662 Timers TIMER T1 Counters COUNTER C1 Data block BOOL DB1.DBX1.0 Data block BYTE DB1.DBB1 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.4 Testing the user program Permitted operand Example of data type Example (International mnemonics) Data block WORD DB1.DBW1 Data block DWORD DB1.DBD1 Note Please observe the following notes to work with the watch table. You cannot enter "DB0..." because it is used by the system! Peripheral outputs can be modified but not monitored. Peripheral inputs can be monitored but not modified. NOTICE Danger of a time-out while monitoring peripheral inputs and controlling peripheral outputs Note that the monitoring of peripheral inputs and the controlling of peripheral outputs in the watch table can result in a time-out. The CPU assumes the "STOP" mode. See also Basic information on entering tags in the watch table (Page 1661) Permissible modify values for the watch table Entry of modify values in the watch table The following table shows the operands that are permitted for the entry of modify values in the watch table: Table 9-14 WinCC Basic V13.0 System Manual, 02/2014 Bit operands Possible bit operands Example for permitted modify values I1.0 True M1.7 False Q1.0 0 Q1.1:P 1 DB1.DBX1.1 2#0 M1.6 2#1 1663 Programming the PLC 9.4 Testing the user program Table 9-15 Possible byte operands Example for permitted modify values IB1 2#00110011 MB12 B#16#1F QB10 1F QB11:P 'a' DB1.DBB1 10 Table 9-16 Word operands Possible word operands Example for permitted modify values IW1 2#0011001100110011 MW12 W#16#ABCD MW14 ABCD QW10 B#(12, 34) QW12:P 12345 DB1.DBW1 'ab' MW16 S5T#9s_340ms MW18 C#123 MW9 D#2006-12-31 Table 9-17 Double word operands Possible double word operands Example for permitted modify values ID1 2#00110011001100110011001100110011 QD10 Dw#16#abcdef10 QD12:P ABCDEF10 DB1.DBD2 b#(12,34,56,78) MD8 L#-12 MD12 L#12 MD16 123456789 MD20 123456789 MD24 T#12s345ms MD28 Tod#1:2:34.567 MD32 P#e0.0 Table 9-18 1664 Byte operands Timers Possible operands of the "Timer" type Permitted control values Explanation T1 0 ms Time value in milliseconds (ms) T12 20 ms Time value in milliseconds (ms) T14 12345 ms Time value in milliseconds (ms) T16 S5t#12s340ms Time value 12s 340 ms WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.4 Testing the user program Table 9-19 Counters Possible operands of the "Counter" type Permitted control values C1 0 C14 20 C16 C#123 Notes on timers and counters Timers Note Modifying a timer influences only the value, not the status. Timer T1 can be modified to the value "0", but the result of logic operation for A T1 is not changed. The time sequences "s5t" and "s5time" can be written in both lower-case and upper-case characters. Counter Note Modifying a counter influences only the value, not the status. Counter C1 can be changed to the value "0", but the result of the logic operation for A C1 is not changed. Overview of the display formats Display formats in the watch table The display format you select specifies the representation of a tag value. When entering the address a display format is automatically preset. If you want to change this, you can select a display format from the drop-down list in the "Display formats" column. The drop-down list only offers the display formats which are valid for this data type. The display format that appears first in the list is the pre-selected format. Example The following table shows the 32-bit data types permitted for all CPU families in the watch table and their possible display formats: WinCC Basic V13.0 System Manual, 02/2014 Data type Possible display formats BOOL Bool, Hex, BCD, Octal, Bin, Dec, Dec+/- BYTE Hex, BCD, Octal, Bin, Dec, Dec+/-, Character WORD Hex, BCD, Octal, Bin, Dec, Dec+/-, Dec_Sequence, Character, Unicode_Character, SIMATIC_Timer, Date, Counter DWORD Hex, BCD, Octal, Bin, Dec, Dec+/-, Dec_Sequence, Character, Unicode_Character, Floating-point number, Time of day, Timer, Pointer 1665 Programming the PLC 9.4 Testing the user program Data type Possible display formats SINT Dec, Dec+/-, Hex, BCD, Octal, Bin, Character INT Dec, Dec+/-, Hex, BCD, Octal, Bin, Character, Unicode_Character, Dec_Sequence, SIMATIC_Timer, Counter, Date DINT Dec, Dec+/-, Hex, BCD, Octal, Bin, Character, Unicode_Character, Dec_Sequence, Floating-point number, Time of day, Timer, Pointer USINT Dec, Dec+/-, Hex, BCD, Octal, Bin, Character UINT Dec, Dec+/-, Hex, BCD, Octal, Bin, Character, Unicode_Character, Dec_Sequence, SIMATIC_Timer, Counter, Date UDINT Dec, Dec+/-, Hex, BCD, Octal, Bin, Character, Unicode_Character, Dec_Sequence, Floating-point number, Time of day, Timer, Pointer REAL Floating-point number, Hex, BCD, Octal, Bin, Character, Unicode_Character,Dec, Dec+/-, Dec_Sequence, Time of day, Timer, Pointer DATE Date, Dec, Hex, BCD, Bin TIME_OF_DAY Time of day, Dec, Hex, BCD, Bin TIME Timer, Hex, BCD, Bin DATE_AND_TIME Date and time, TIMER SIMATIC_Timer, Hex, BCD, Bin CHAR Character, Hex, BCD, Octal, Bin, Dec, Dec+/- WCHAR Unicode_Character, Character, Hex, BCD, Octal, Bin, Dec, Dec+/- STRING Character string WSTRING Unicode_character string POINTER Pointer, Hex, BCD, Octal, Bin, Character, Unicode_Character, Dec, Dec+/-, Dec_Sequence, Floating-point number, Time of day, Timer, Block number COUNTER Counter, Hex, BCD, Bin S5TIME SIMATIC_Timer, Hex, BCD, Bin For the S7-1200 CPU family, all 32-bit data types are permitted (see table above), as well as the 64-bit data type LREAL with the following possible display formats: Data type Possible display formats LREAL In a project created with TIA Portal < V12: Floating-point number Note: The display of LREAL is limited to 13 digits plus exponent. LREAL In a project created with TIA Portal >= V12: Floating-point number, Hex, BCD, Octal, Bin, Character, Unicode_Character, Dec, Dec+/-, Dec_Sequence, Time of day, Timer, Date and time Note: The display of LREAL is limited to 13 digits plus exponent. For the S7-1500 CPU family, in addition to 32-bit data types, the 64-bit data types listed in the table are also permitted with the following possible display formats: 1666 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.4 Testing the user program Data type Possible display formats LWORD Hex, Octal, BCD, Bin, Character, Unicode_Character, Dec, Dec+/-, Dec_Sequence, Floating-point number, Time of day, Timer, Date and time LINT Dec+/-, Dec, Hex, BCD, Octal, Bin, Character, Unicode_Character, Dec_Sequence, Time of day, Timer, Date and time ULINT Dec, Dec+/-, Hex, BCD, Octal, Bin, Character, Unicode_Character, Dec_Sequence, Time of day, Timer, Date and time LREAL Floating-point number, Hex, BCD, Octal, Bin, Character, Unicode_Character, Dec, Dec+/-, Dec_Sequence, Time of day, Timer, Date and time LTIME Timer, Dec+/-, Dec, Hex LTOD Time of day, Dec, Hex, BCD, Bin LDT Date and time, Dec, Hex For more information, refer to the description of the valid data types. Note Rounding of floating-point numbers In the watch table, floating-point numbers are stored as binary numbers in IEEE format. Because not every floating point number (real, longreal) that can be displayed on the user interface can be mapped to the IEEE format, there is a possibility that floating-point numbers will be rounded. If a rounded floating-point number in the watch table is copied and, in turn, inserted in another input field, the rounding may cause a slight difference. Note Only symbolic addressing is possible In the watch table, LongDataTypes such as LWORD or LREAL can only be addressed symbolically. WinCC Basic V13.0 System Manual, 02/2014 1667 Programming the PLC 9.4 Testing the user program Selecting the display format for tags Procedure To select the display format of the tags, follow these steps: 1. Enter the desired address in the watch table. 2. Click the desired cell in the "Display format" column, and open the drop-down list. The permissible display formats are shown in the drop-down list. 3. Select the desired display format from the drop-down list. Note If the selected display format cannot be applied, then the last selected display format will be displayed automatically. Creating and editing comment lines Basic principles of comment lines In addition to the row related comments in the comment column, you can now also create complete comment lines to enhance the structure of the watch table. The contents of the comment line are stored in the "Languages & Resources" folder in the "Project texts" tab and can be compiled in other project languages. Creating comment lines To create comment lines, follow these steps: 1. Open the watch table and enter the required addresses. 2. To create a comment line, enter the character string "//" in the "Name" column. No comment lines can be created in the other columns. 3. Enter the required comment in the comment line. The entered comment is shown in green. 4. To show all comments you entered, double-click "Project texts" in the project tree under "Languages & Resources". 5. If you are working in multi-lingual projects and want your comment to be translated into other languages, you can set the project languages required in addition to the editing language in the project tree under "Languages & Resources > Project languages". 1668 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.4 Testing the user program Deleting comment lines To delete comment lines, follow these steps: 1. Open a watch table containing comment lines. 2. Delete the entire comment including the introductory string "//", if you no longer required this. 3. Alternatively, delete only the introductory string "//". In this case the existing comment is retained and is displayed in the "Comment" column in the watch table. Note Deleting comment lines When you delete comment lines the project languages and any existing translations for these comments are also deleted. 9.4.3.7 Monitoring tags in the watch table Introduction to monitoring tags in the watch table Introduction The watch table allows you to monitor the tags of the configured input and output modules in the CPU, depending on the monitoring and modify mode (Page 1670) selected. To monitor tags, an online connection to the CPU must exist. NOTICE Danger of a time-out while monitoring peripheral inputs Note that the monitoring of peripheral inputs can result in a time-out. The CPU assumes the "STOP" mode. WinCC Basic V13.0 System Manual, 02/2014 1669 Programming the PLC 9.4 Testing the user program Options for monitoring tags The following options are available for monitoring tags: Monitor now This command starts the monitoring of the visible tags in the active watch table immediately and once only. Monitor all This command starts the monitoring of all visible tags in the active watch table, depending on the selected watch mode: - In basic mode, the monitoring mode is set to "permanent" by default. - In expanded mode, you can specify defined trigger points for the monitoring of tags. Note If the monitoring mode is changed while in expanded mode and then a switch is made to basic mode, the monitoring mode set before will also be applied in basic mode. CPU-specific limitations when monitoring tags The following CPU-specific differences exist: CPU S7-300/400: CPUs from this family can only monitor the first 30 characters of a string. CPU S7-1200/1500: CPUs from this family can monitor a string up to the total size of 254 characters. Setting the monitoring and modify mode Introduction By selecting the monitoring and modify mode, you specify the trigger point and the duration of the tag monitoring in the watch table and the force table. Possible monitoring and modify modes (duration of monitoring or modifying) The following monitoring and modifying modes are available: Permanent Once only, at start of scan cycle Once only, at end of scan cycle Permanently, at start of scan cycle Permanently, at end of scan cycle 1670 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.4 Testing the user program Once only, at transition to STOP Permanently, at transition to STOP Special features when using "Permanent" mode The "Permanent" mode is executed differently for the monitoring and modifying of tags. Monitoring: The inputs are monitored at the end of the cycle and the outputs at the start of the cycle. Modifying: The inputs are monitored at the start of the cycle and the outputs at the end of the cycle. Selecting the trigger point The trigger points "Beginning of scan cycle", "End of scan cycle", and "Switch to stop" specify the time at which the tags are to be read from the CPU or updated in the CPU. The following diagram shows the position of these trigger points: 3URFHVVLPDJHLQSXW 7ULJJHUSRLQW$WVWDUWRIVFDQF\FOH 2% 7ULJJHUSRLQW$WWUDQVLWLRQIURP 581WR6723 7ULJJHUSRLQW$WHQGRIVFDQF\FOH 3URFHVVLPDJHRXWSXW WinCC Basic V13.0 System Manual, 02/2014 1671 Programming the PLC 9.4 Testing the user program Position of the trigger points From the position of the trigger points, it follows that: Modifying of inputs is only appropriate at the beginning of the scan cycle (corresponding to the beginning of the user program OB 1), because otherwise the process image input is updated again after modifying and is thus overwritten. Modifying of outputs is only appropriate at the end of the scan cycle (corresponding to the end of the user program OB 1), because otherwise the process image output can be overwritten by the user program. The modified value is displayed in the "Monitor value" column, provided that monitoring is active and the modified value is not overwritten by the user program. Monitoring of tags When tags are being modified, the following applies to the trigger points: If you have specified the modify mode as "once only", you will receive a message if the selected tags cannot be modified. In "permanent" modify mode, you do not receive a message. Note regarding the "Modify now" command You can modify the values of selected tags immediately using the "Online > Modify >Modify now" command. This command is executed once only and as quickly as possible without reference to a defined position (trigger point) in the user program. This function is used mainly for modifying when the CPU is in STOP mode. "Monitor all" command for tags Introduction The "Monitor all" command allows you to start monitoring the visible tags in the active watch table. The default setting for the monitoring mode in basic mode of the watch table is "permanent". In expanded mode, you can specify defined trigger points for the monitoring of tags. In this case, the tags are monitored with reference to the specified trigger points. NOTICE Danger of a time-out while monitoring peripheral inputs Note that the monitoring of peripheral inputs can result in a time-out. The CPU assumes the "STOP" mode. 1672 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.4 Testing the user program Requirements A watch table has been created. An online connection to the CPU exists. Procedure To execute the "Monitor all" command, follow these steps: 1. Enter the tags to be monitored and the corresponding addresses in the watch table. 2. Switch to expanded mode by clicking the icon "Show/hide advanced setting columns" in the toolbar. 3. If you want to change the default monitoring mode for a tag, click the appropriate cell in the "Monitor with trigger" column and select the desired monitoring mode from the drop-down list. 4. Click the "Monitor all" icon in the toolbar. Result The tags of the active watch table are monitored using the monitoring mode selected. See also Icons in the watch table (Page 1658) Entering tags in the watch table (Page 1661) Basic mode and expanded mode in the watch table (Page 1657) "Monitor now" command for tags Introduction The "Monitor now" command starts the monitoring of tags immediately without reference to defined trigger points. The tag values are read out once only and displayed in the watch table. NOTICE Danger of a time-out while monitoring peripheral inputs Note that the monitoring of peripheral inputs can result in a time-out. The CPU assumes the "STOP" mode. WinCC Basic V13.0 System Manual, 02/2014 1673 Programming the PLC 9.4 Testing the user program Requirements A watch table has been created. An online connection to the CPU exists. Procedure To execute the "Monitor now" command, follow these steps: 1. Enter the tags to be monitored and the corresponding addresses in the watch table. 2. Click the "Monitor now" icon in the toolbar. Result The tags of the active watch table are monitored immediately and once only. See also Icons in the watch table (Page 1658) Entering tags in the watch table (Page 1661) Basic mode and expanded mode in the watch table (Page 1657) 9.4.3.8 Modifying tags in the watch table Introduction to modifying tags Introduction The watch table allows you to modify the tags of the configured input and output modules in the CPU, depending on the monitoring and modify mode (Page 1670) selected. To monitor the tags, an online connection to the CPU must exist. DANGER Danger when modifying: Serious personal injury and material damage can result from changes in the tags or addresses during plant operation in the event of malfunctions or program errors! Make sure that dangerous conditions cannot occur before you execute the "Modify" function. 1674 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.4 Testing the user program NOTICE Danger of a time-out while controlling peripheral outputs Note that the controlling of peripheral outputs in the watch table can result in a time-out. The CPU assumes the "STOP" mode. Options for modifying tags The following options are available for modifying tags: Modify to "0" This command modifies the selected address to the modify value "0". Modify to "1" This command modifies the selected address to the modify value "1". Modify once only and immediately This command modifies all selected addresses in the active watch table "once only and immediately". Modify with trigger This command modifies all selected addresses in the active watch table using the monitoring and modify mode (Page 1670) selected. The "Modify with trigger" function is only available in expanded mode. You will not receive a message indicating whether or not the selected addresses were actually modified with the specified value. You should use the "Modify once only and immediately" function if you require such a confirmation. Enable peripheral outputs This command disables the command output disable. This function can only be executed in expanded mode, when the CPU is in STOP and the option Force (Page 1699) of tags is not enabled. If desired, deactivate this function in the force table. Note When modifying, note the following: Modifying can not be undone. WinCC Basic V13.0 System Manual, 02/2014 1675 Programming the PLC 9.4 Testing the user program Modify tags to "0" Introduction You can assign one-time values to tags independent of the monitoring and modify mode and modify them. The modify command is executed as fast as possible, similar to a "Trigger now" command, without reference to a defined position in the user program. DANGER Danger when modifying: Serious personal injury and material damage can result from changes in the tags or addresses during plant operation in the event of malfunctions or program errors! Make sure that dangerous conditions cannot occur before you execute the "Modify" function. NOTICE Danger of a time-out while controlling peripheral outputs Note that the controlling of peripheral outputs in the watch table can result in a time-out. The CPU assumes the "STOP" mode. Requirements A watch table has been created. An online connection to the CPU exists. Procedure To modify tags to "0", follow these steps: 1. Enter the desired address in the watch table. 2. Select the "Online > Modify > Modify to 0" command in order to modify the selected address with the specified value. Result The selected address is modified to "0". Note When modifying, note the following: Modifying can not be undone! 1676 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.4 Testing the user program Modify tags to "1" Introduction You can assign one-time values to tags independent of the monitoring and modify mode and modify them. The modify command is executed as fast as possible, similar to a "Trigger now" command, without reference to a defined position in the user program. DANGER Danger when modifying: Serious personal injury and material damage can result from changes in the tags or addresses during plant operation in the event of malfunctions or program errors! Make sure that dangerous conditions cannot occur before you execute the "Modify" function. NOTICE Danger of a time-out while controlling peripheral outputs Note that the controlling of peripheral outputs in the watch table can result in a time-out. The CPU assumes the "STOP" mode. Requirements A watch table has been created. An online connection to the CPU exists. Procedure To modify tags to "1", follow these steps: 1. Enter the desired address in the watch table. 2. Select the "Online > Modify > Modify to 1" command in order to modify the selected address with the specified value. Result The selected address is modified to "1". Note When modifying, note the following: Modifying can not be undone! WinCC Basic V13.0 System Manual, 02/2014 1677 Programming the PLC 9.4 Testing the user program "Modify now" command for tags Introduction You can assign one-time values to tags independent of the monitoring and modify mode and modify them immediately. The modify command is executed as fast as possible, similar to a "Trigger now" command, without reference to a defined position in the user program. DANGER Danger when modifying: Serious personal injury and material damage can result from changes in the tags or addresses during plant operation in the event of malfunctions or program errors! Make sure that dangerous conditions cannot occur before you execute the "Modify" function. NOTICE Danger of a time-out while controlling peripheral outputs Note that the controlling of peripheral outputs in the watch table can result in a time-out. The CPU assumes the "STOP" mode. Requirements A watch table has been created. An online connection to the CPU exists. Procedure To modify tags immediately, follow these steps: 1. Enter the desired addresses and modify values in the watch table. 2. Select the addresses to be modified by selecting the check boxes for modifying in the column after the "Modify value". A yellow triangle appears behind the selected check box, indicating that the address is now selected for modifying but has not yet been modified. 3. Select the "Online > Modify > Modify once and now" command in order to immediately modify the selected address once only with the specified value. 1678 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.4 Testing the user program Result The selected addresses are modified immediately and once only. Note When modifying, note the following: Modifying can not be undone! "Modify with trigger" command for tags Introduction You can assign values to addresses dependent on the defined monitoring and modify mode and modify them. The modify command is executed as specified in the monitoring and modify mode, with reference to the defined trigger position in the user program. DANGER Danger when modifying: Serious personal injury and material damage can result from changes in the tags or addresses during plant operation in the event of malfunctions or program errors! Make sure that dangerous conditions cannot occur before you execute the "Modify" function. NOTICE Danger of a time-out while controlling peripheral outputs Note that the controlling of peripheral outputs in the watch table can result in a time-out. The CPU assumes the "STOP" mode. Requirements A watch table has been created. An online connection to the CPU exists. The watch table has to be in expanded mode. WinCC Basic V13.0 System Manual, 02/2014 1679 Programming the PLC 9.4 Testing the user program Procedure To modify tags "with trigger", follow these steps: 1. Enter the desired addresses and modify values in the watch table. 2. Select the addresses to be modified by selecting the check boxes for modifying in the column after the "Modify value". A yellow triangle appears behind the selected check box, indicating that the address is now selected for modifying but has not yet been modified. 3. Switch to expanded mode using the icon "Show/hide advanced settings columns" in the toolbar or the "Online > Expanded mode" command. The "Monitor with trigger" and "Modify with trigger" columns are displayed. 4. In the "Modify with trigger" column, select the desired modify mode from the drop-down list box. The following options are available: - Permanent - Permanently, at start of scan cycle - Once only, at start of scan cycle - Permanently, at end of scan cycle - Once only, at end of scan cycle - Permanently, at transition to STOP - Once only, at transition to STOP 5. Start modifying using the "Online > Modify > Modify with trigger" command. 6. Confirm the prompt with "Yes" if you want to start modifying with trigger. Result The selected tags are modified using the selected monitoring and modify mode. The yellow triangle is no longer displayed. Note When modifying, note the following: Modifying can not be undone! 1680 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.4 Testing the user program Enable peripheral outputs Introduction The "Enable peripheral outputs" function deactivates the command output disable of the peripheral outputs. You can then modify the peripheral outputs when the CPU is in STOP mode. This function is available in the watch table in "Expanded mode" only. DANGER Danger when enabling the peripheral outputs: Attention, the enabling of the peripheral outputs can cause serious personal injury and material damage! Make certain that dangerous conditions cannot occur before you execute the "Enable peripheral outputs" function. Prerequisites A watch table has been created. An online connection to the CPU exists. The CPU is in STOP mode before you can enable the peripheral outputs. The watch table has to be in expanded mode. The option Force (Page 1699) of tags must not be enabled. Note "Enable peripheral outputs" function This function is possible only in STOP mode. The function is exited by an operating state change of the CPU and by the termination of the online connection. While the function is enabled, forcing is not possible. Procedure To enable the peripheral outputs in STOP mode, follow these steps: 1. Enter the desired addresses and modify values in the watch table. 2. Select the addresses to be modified by selecting the check boxes for modifying in the column after the "Modify value". A yellow triangle appears behind the selected check box, indicating that the address is now selected for modifying but has not yet been modified. 3. Switch to expanded mode using the icon "Show/hide advanced settings columns" in the toolbar or the "Online > Expanded mode" command. The "Monitor with trigger" and "Modify with trigger" columns are displayed. WinCC Basic V13.0 System Manual, 02/2014 1681 Programming the PLC 9.4 Testing the user program 4. Change the relevant CPU to STOP using the operator panel. 5. Right-click to open the shortcut menu and select "Enable peripheral outputs". 6. Confirm the prompt with "Yes" if you want to unlock the command output disable for the peripheral outputs. 7. Modify the peripheral outputs using the "Online > Modify > Modify now" command. Result The peripheral outputs are modified with the selected modify values. The yellow triangle is no longer displayed. Enabling the peripheral outputs The "Enable peripheral outputs" function remains active until: The "Enable peripheral outputs" command is deactivated again via the shortcut menu or via the "Online > Modify > Enable peripheral outputs" command. The CPU is no longer in STOP mode. The online connection is terminated. Note When modifying, note the following: Modifying can not be undone! 9.4.4 Testing with the force table 9.4.4.1 Introduction for testing with the force table Overview You can use the force table to assign permanent values to individual tags of the user program. This action is referred to as "forcing". The following functions are available in the force table: Monitoring tags This displays the current values of the individual tags of a user program or a CPU on the programming device or PC. Tags can be monitored with or without a trigger condition. Forcing tags This function lets you assign a permanent value to individual peripheral tags of the user program. 1682 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.4 Testing the user program Monitoring and forcing tags The monitoring and forcing of tags is always dependent on the operand scope of the CPU used. The following tags can be monitored: Inputs, outputs, and bit memories Contents of data blocks Peripheral inputs The following tags can be forced: Peripheral inputs Peripheral outputs Example Independent of the CPU used, only I/O can be forced, such as: "Tag_1":P or "QW0:P" or "IW0:P". Note that "Tag_1":P must not be the symbolic name of a bit memory. Possible applications One advantage of the force table is that you can simulate different test environments and overwrite tags in the CPU with a permanent value. This enables you to intervene in the ongoing process for regulating purposes. See also Layout of the force table (Page 1684) Basic mode and expanded mode in the force table (Page 1685) Icons in the force table (Page 1686) Open and edit force table (Page 1687) WinCC Basic V13.0 System Manual, 02/2014 1683 Programming the PLC 9.4 Testing the user program 9.4.4.2 Safety precautions when forcing tags Safety precautions when forcing tags Because the forcing function allows you to intervene permanently in the process, observance of the following notices is essential: DANGER Prevent personal injury and material damage! Note that an incorrect action when executing the "Force" function can: Harm persons or pose a health hazard. Cause damage to machinery or the entire plant. CAUTION Prevent personal injury and material damage! Before you start the "Force" function, you should ensure that no one else is currently executing this function on the same CPU. Forcing can only be stopped by clicking the "Stop forcing" icon or using the "Online > Force > Stop forcing" command. Closing the active force table does not stop the forcing! Forcing can not be undone! Review the differences between " modifying tags" (Page 1674) and "forcing tags" (Page 1699). If a CPU does not support the "Force" function, the relevant icons cannot be selected. If the function "Enable peripheral outputs" is active on your CPU, then forcing is not possible on this CPU. If desired, deactivate this function in the watch table. 9.4.4.3 Layout of the force table Introduction In the force table, enter the CPU-wide tags that you have defined and selected and which are to be forced in the allocated CPU. Only peripheral inputs and peripheral outputs can be forced. For each CPU created in the project, a force table will automatically be created in the "Watch and force tables" folder. Only one force table can be allocated to a CPU. This force table displays all the addresses forced in the allocated CPU. 1684 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.4 Testing the user program Layout of the force table The columns displayed in the force table depend on the mode you are working in: basic mode or expanded mode. In expanded mode the "Monitor with trigger" column is also displayed. Meaning of the columns The following table shows the meaning of the individual columns in basic mode and expanded mode: Mode Column Basic mode Meaning Identification column Name Name of the inserted tag Address Address of the inserted tag Display format Selected display format Monitor value Values of the tags, dependent on the selected display format. Force value Value with which the tag is forced. ("Force") The following additional column is shown in expanded mode: Select the tag to be forced by activating the corresponding check box. Comment Comment for documentation of the tags Monitor with trigger Display of selected monitoring mode See also Icons in the force table (Page 1686) Basic mode and expanded mode in the force table (Page 1685) 9.4.4.4 Basic mode and expanded mode in the force table Difference between basic mode and expanded mode in the force table In expanded mode the "Monitor with trigger" column is also displayed in the force table. You will find a detailed list of the columns under Layout of the force table (Page 1684). WinCC Basic V13.0 System Manual, 02/2014 1685 Programming the PLC 9.4 Testing the user program Switching between basic mode and expanded mode You have the following options of toggling between the basic and expanded mode: Click the icon "Show/hide advanced setting columns". Click this icon again to return to the basic mode. Or: Activate the check box for the "Expanded mode" command in the "Online" menu. Deactivate this check box to return to the basic mode. Functionality in expanded mode The following functionality is only possible in expanded mode: Monitor with trigger Monitor peripheral inputs 9.4.4.5 Icons in the force table Meaning of the icons The following table shows the meaning of the icons in the force table: Icon Meaning Identifies a table inside the project tree as a force table. Identification column Inserts a row before the selected row. Inserts a row after the selected row. Displays all columns of expanded mode. If you click this icon again, the columns of the expanded mode will be hidden. Starts forcing for all addresses of the selected tags. If forcing is already running, the previous action is replaced without interruption. Stops forcing of addresses in the force table. Starts monitoring of the visible tags in the force table. The default setting for monitoring in basic mode is "permanent". In expanded mode an additional column is shown and you can set certain trigger points for monitoring tags. Starts monitoring of the visible tags in the force table. This command is executed immediately and the tags are monitored once. Displays the check box for the selection of tags to be forced. Indicates that an address cannot be forced. Indicates that an address cannot be fully forced. Example: It is possible to force the address QW0:P, but it is not possible to force the address QD0:P because this address area is potentially not available on the CPU. 1686 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.4 Testing the user program Icon Meaning Indicates that an address cannot be monitored. Indicates that an address is being forced. Indicates that an address is being partly forced. Indicates that the associated peripheral address is being forced. Indicates that a syntax error occurred. Indicates that the address is selected but has not been forced yet. See also Layout of the force table (Page 1684) 9.4.4.6 Open and edit force table Display force table Introduction You cannot create a new force table; one force table already exists for each CPU. It is permanently allocated to this CPU and cannot be copied or duplicated. Requirements A project with an allocated CPU has to be open. Displaying a force table The force table is always displayed below a CPU in the "Watch and force tables" folder. Open force table Requirements A project with an allocated CPU must be created. Procedure Proceed as follows to open a force table: 1. Open the "Watch and force tables" folder below the desired CPU. 2. Double-click the "Force table" in this folder. WinCC Basic V13.0 System Manual, 02/2014 1687 Programming the PLC 9.4 Testing the user program Result The selected force table opens. Save force table Requirements A project with an allocated CPU has been created. Procedure Proceed as follows to save a force table: 1. Enter the desired changes in the force table. 2. Select the "Save" command in the "Project" menu or click the "Save project" icon in the toolbar. Note that this save operation will save the entire project. Result The contents of the force table and the associated project are saved. Note You cannot rename a force table. 9.4.4.7 Entering tags in the force table Basic principles for entering tags in the force table Recommended procedure Select the tags whose values you want to monitor or force, and enter them in the force table. When entering tags in the force table, please note that these tags must be previously defined in the PLC tag table. Example of filling out a force table You can enter the absolute address that is to be forced or monitored in the "Address" column or you can enter the symbolic name of the tag in the "Name" column. Select the display format you require from the drop-down list in the "Display format" column, if you do not want to use the default setting. 1688 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.4 Testing the user program Now you have to decide whether you want to monitor or force the entered tags. Enter the required force value and a comment in the appropriate columns of the force table. Note that only peripheral inputs and peripheral outputs can be forced and review the Safety precautions when forcing tags (Page 1700). Create comment line If required, you can create a comment row by entering the string "//" in the "Name" column. Syntax check When you enter tags in the force table, the syntax of each cell will be checked when you exit the cell. Incorrect entries are marked in red. Note When you place the mouse pointer in a cell marked in red, brief information is displayed with additional notes on the error. Permitted operands for the force table Permitted operands for the force table The following table shows the operands that are permitted for forcing in the force table: Permitted operand Example of data type Example (International mnemonics) Peripheral input/peripheral output BOOL I0.0:P; Q0.0:P Peripheral input/peripheral output BYTE IB1:P; QB1:P Peripheral input/peripheral output WORD IW2:P; QW3:P Peripheral input/peripheral output DWORD ID2:P; QD1:P The following table shows the operands that are permitted for monitoring in the force table: Permitted operand Example of data type Example (International mnemonics) Input/output/bit memory BOOL I1.0, Q1.7, M10.1 I0.0:P Input/output/bit memory BYTE IB1/QB10/MB100 IB1:P Input/output/bit memory WORD IW1; QW10; MW100 IW2:P WinCC Basic V13.0 System Manual, 02/2014 1689 Programming the PLC 9.4 Testing the user program Permitted operand Example of data type Example (International mnemonics) Input/output/bit memory DWORD ID4; QD10; MD100 Timers TIMER T1 Counters COUNTER C1 Data block BOOL DB1.DBX1.0 Data block BYTE DB1.DBB1 Data block WORD DB1.DBW1 Data block DWORD DB1.DBD1 ID2:P Note You cannot enter "DB0..." because it is used by the system! Permitted force values for the force table Entering force values in the force table The following table shows the operands that are permitted for entering force values in the force table: Table 9-20 Possible bit operands Example for permitted force values I1.0:P True I1.1:P False Q1.0P 0 Q1.1:P 1 I2.0:P 2#0 I2.1:P 2#1 Table 9-21 1690 Bit operands Byte operands Possible byte operands Example for permitted force values IB1:P 2#00110011 IB2:P B#16#1F QB14:P 1F QB10:P 'a' IB3:P 10 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.4 Testing the user program Table 9-22 Word operands Possible word operands Example for permitted force values IW0:P 2#0011001100110011 IW2:P W#16#ABCD QW10:P ABCD QW12:P B#(12, 34) IW4:P 'ab' IW6:P 12345 IW8:P S5T#9S_340ms IW10:P C#123 IW12:P D#2006-12-31 Table 9-23 Double word operands Possible double word operands Example for permitted force values ID0:P 2#00110011001100110011001100110011 ID4:P 1.2 QD10:P 1.234.e4 QD14:P Dw#16#abcdef10 ID8:P 16#ABCDEF10 ID12:P b#(12,34,56,78) ID16:P L#-12 ID20:P L#12 ID24:P 123456789 ID28:P 123456789 ID32:P T#12s345ms ID36:P Tod#14:20:40.645 ID40:P P#e0.0 Overview of the display formats Display formats in the force table The display format you select specifies the representation of a tag value. When entering the address a display format is automatically preset. If you want to change this, you can select a display format from the drop-down list in the "Display formats" column. The drop-down list only offers the display formats which are valid for this data type. The display format that appears first in the list is the pre-selected format. WinCC Basic V13.0 System Manual, 02/2014 1691 Programming the PLC 9.4 Testing the user program Example The following table shows the 32-bit data types permitted for all CPU families in the force table and their possible display formats: Data type Possible display formats BOOL Bool, Hex, BCD, Octal, Bin, Dec, Dec+/- BYTE Hex, BCD, Octal, Bin, Dec, Dec+/-, Character WORD Hex, BCD, Octal, Bin, Dec, Dec+/-, Dec_Sequence, Character, SIMATIC_Timer, Date, Unicode_Character, Counter DWORD Hex, BCD, Octal, Bin, Dec, Dec+/-, Dec_Sequence, Character, Floating-point number, Time of day, Timer, Pointer, Unicode_Character SINT Dec, Dec+/-, Hex, BCD, Octal, Bin, Character INT Dec, Dec+/-, Hex, BCD, Octal, Bin, Character, Unicode_Character, Dec_Sequence, SIMATIC_Timer, Counter, Date DINT Dec, Dec+/-, Hex, BCD, Octal, Bin, Character, Unicode_Character, Dec_Sequence, Floating-point number, Time of day, Timer, Pointer USINT Dec, Dec+/-, Hex, BCD, Octal, Bin, Character UINT Dec, Dec+/-, Hex, BCD, Octal, Bin, Character, Unicode_Character, Dec_Sequence, SIMATIC_Timer, Counter, Date UDINT Dec, Dec+/-, Hex, BCD, Octal, Bin, Character, Unicode_Character, Dec_Sequence, Floating-point number, Time of day, Timer, Pointer REAL Floating-point number, Hex, BCD, Octal, Bin, Character, Unicode_Character,Dec, Dec+/-, Dec_Sequence, Time of day, Timer, Pointer DATE Date, Dec, Hex, BCD, Bin TIME_OF_DAY Time of day, Dec, Hex, BCD, Bin TIME Timer, Hex, BCD, Bin DATE_AND_TIME Date and time, TIMER SIMATIC_Timer, Hex, BCD, Bin CHAR Character, Hex, BCD, Octal, Bin, Dec, Dec+/- WCHAR Unicode_Character, Character, Hex, BCD, Octal, Bin, Dec, Dec+/- STRING Character string WSTRING Unicode_character string POINTER Pointer, Hex, BCD, Octal, Bin, Character, Unicode_Character, Dec, Dec+/-, Dec_Sequence, Floating-point number, Time of day, Timer, Number COUNTER Counter, Hex, BCD, Bin S5TIME SIMATIC_Timer, Hex, BCD, Bin For the S7-1200 CPU family, all 32-bit data types are permitted (see table above), as well as the 64-bit data type LREAL with the following possible display formats: 1692 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.4 Testing the user program Data type Possible display formats LREAL In a project created with TIA Portal < V12: Floating-point number Note: The display of LREAL is limited to 13 digits plus exponent. LREAL In a project created with TIA Portal >= V12: Floating-point number, Hex, BCD, Octal, Bin, Character, Unicode_Character, Dec, Dec+/-, Dec_Sequence, Time of day, Timer, Date and time Note: The display of LREAL is limited to 13 digits plus exponent. For the S7-1500 CPU family, in addition to 32-bit data types, the 64-bit data types listed in the table are also permitted with the following possible display formats: Data type Possible display formats LWORD Hex, Octal, BCD, Bin, Character, Unicode_Character, Dec, Dec+/-, Dec_Sequence, Floating-point number, Time of day, Timer, Date and time LINT Dec+/-, Dec, Hex, BCD, Octal, Bin, Character, Unicode_Character, Dec_Sequence, Time of day, Timer, Date and time ULINT Dec, Dec+/-, Hex, BCD, Octal, Bin, Character, Unicode_Character, Dec_Sequence, Time of day, Timer, Date and time LREAL Floating-point number, Hex, BCD, Octal, Bin, Character, Unicode_Character, Dec, Dec+/-, Dec_Sequence, Time of day, Timer, Date and time LTIME Timer, Dec+/-, Dec, Hex LTOD Dec, Hex, BCD, Bin, Time of day LDT Dec, Hex, Date and time For more information, refer to the description of the valid data types. Note Rounding of floating-point numbers In the force table, floating-point numbers are stored as binary numbers in IEEE format. Because not every floating point number (real, longreal) that can be displayed on the user interface can be mapped to the IEEE format, there is a possibility that floating-point numbers will be rounded. If a rounded floating-point number in the force table is copied and, in turn, inserted in another input field, the rounding may cause a slight difference. WinCC Basic V13.0 System Manual, 02/2014 1693 Programming the PLC 9.4 Testing the user program Note Only symbolic addressing is possible In the force table, LongDataTypes such as LWORD or LREAL can only be addressed symbolically. Selecting the display format for tags Procedure To select the display format of the tags, follow these steps: 1. Enter the desired address in the force table. 2. Click the desired cell in the "Display format" column, and open the drop-down list. The permitted display formats are shown in the drop-down list. 3. Select the desired display format from the drop-down list. Note If the selected display format cannot be applied, then the last selected display format will be displayed automatically. Creating and editing comment lines Basic principles of comment lines In addition to the row-related comments in the comment column, you can now also create complete comment lines to enhance the structure of the force table. The contents of the comment line are stored in the "Languages & Resources" folder in the "Project texts" tab and can be compiled in other project languages. Creating comment lines To create comment lines, follow these steps: 1. Open the force table and enter the required addresses. 2. To create a comment line, enter the character string "//" in the "Name" column. No comment lines can be created in the other columns. 1694 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.4 Testing the user program 3. Enter the required comment in the comment line. The entered comment is shown in green. 4. To show all comments you entered, double-click "Project texts" in the project tree under "Languages & Resources". 5. If you are working in multi-lingual projects and want your comment to be translated into other languages, you can set the project languages required in addition to the editing language in the project tree under "Languages & Resources > Project languages". Deleting comment lines To delete comment lines, follow these steps: 1. Open a force table containing comment lines. 2. Delete the entire comment including the introductory string "//", if you no longer require this. 3. Alternatively, delete only the introductory string "//". In this case the existing comment is retained and is displayed in the "Comment" column in the force table. Note Deleting comment lines When you delete comment lines the project languages and any existing translations for these comments are also deleted. 9.4.4.8 Monitoring tags in the force table Introduction to monitoring tags in the force table Introduction Use the force table to monitor the tags of the configured input and output modules in the CPU, dependent on the monitoring mode (Page 1696) you have selected. An online connection to the CPU must exist to monitor tags. WinCC Basic V13.0 System Manual, 02/2014 1695 Programming the PLC 9.4 Testing the user program Options for monitoring tags The following options are available for monitoring tags: Monitor all This command starts the monitoring of all visible tags in the active force table, dependent on the selected monitoring mode: - In basic mode, the monitoring mode is set to "permanent" by default. - In expanded mode, you can specify defined trigger points for the monitoring of tags. Note If the monitoring mode is changed while in expanded mode and then a switch is made to basic mode, the monitoring mode set before will also be applied in basic mode. Monitor now This command starts the monitoring of the visible tags in the active force table immediately and once only. CPU-specific limitations when monitoring tags The following CPU-specific differences exist: CPU S7-300/400: CPUs from this family can only monitor the first 30 characters of a string. CPU S7-1200: CPUs from this family can monitor a string up to the total size of 254 characters. Setting the monitoring mode in the force table Introduction By selecting the monitoring mode, you specify the trigger point and the duration of tag monitoring in the force table. Possible monitoring mode (duration of monitoring) The following selection options are available: Permanent Once only, at start of scan cycle Once only, at end of scan cycle Permanently, at start of scan cycle Permanently, at end of scan cycle Once only, at transition to STOP Permanently, at transition to STOP 1696 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.4 Testing the user program Special features when using "Permanent" mode The "Permanent" mode is executed as follows for the monitoring of tags: The inputs are monitored at the end of the cycle and the outputs at the start of the cycle. Selecting the trigger point The trigger points "Beginning of scan cycle", "End of scan cycle", and "Switch to stop" specify the time at which the tags are to be read from the CPU or updated in the CPU. The following diagram shows the position of these trigger points: 3URFHVVLPDJHLQSXW 7ULJJHUSRLQW$WVWDUWRIVFDQF\FOH 2% 7ULJJHUSRLQW$WWUDQVLWLRQIURP 581WR6723 7ULJJHUSRLQW$WHQGRIVFDQF\FOH 3URFHVVLPDJHRXWSXW "Monitor all" command for tags Introduction Use the "Monitor all" command to start monitoring the visible tags in the active force table. In basic mode of the force table, the default setting for the monitoring mode is "permanent". In expanded mode, you can specify defined trigger points for the monitoring of tags. In this case, the tags are monitored with reference to the specified trigger points. Requirements An online connection to the CPU exists. WinCC Basic V13.0 System Manual, 02/2014 1697 Programming the PLC 9.4 Testing the user program Procedure To execute the "Monitor all" command, follow these steps: 1. Enter the tags to be monitored and the corresponding addresses in the force table. 2. Switch to expanded mode by clicking the icon "Show/hide advanced setting columns" in the toolbar. 3. If you want to change the default monitoring mode for a tag, click the appropriate cell in the "Monitor with trigger" column and select the desired monitoring mode from the drop-down list. 4. Click the "Monitor all" icon in the toolbar. Result The tags of the active force table will be monitored using the set monitoring mode. "Monitor now" command for tags Introduction The "Monitor now" command starts the monitoring of tags immediately without reference to defined trigger points. The tag values are read out only once and displayed in the force table. Requirements An online connection to the CPU exists. Procedure To execute the "Monitor now" command, follow these steps: 1. Enter the tags to be monitored and the corresponding addresses in the force table. 2. Click the "Monitor now" icon in the toolbar. Result The tags of the active force table are monitored immediately and once only. 1698 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.4 Testing the user program 9.4.4.9 Forcing tags in the force table Introduction to forcing tags Introduction You can use the force table to assign permanent values to individual tags of the user program. This action is referred to as forcing. Only peripheral inputs and peripheral outputs can be forced. To use the forcing function, you must have an online connection to the CPU and the utilized CPU must support this functionality. If you open a force table in the "Watch and force tables" folder below a CPU, all values forced in the allocated CPU will be displayed in this force table, provided that an online connection to the CPU exists. Possible applications By permanently assigning defined values to tags, you can specify defined default settings for your user program and, thus, test the programmed functions. Forcing is possible in basic mode and in expanded mode (Page 1685). Caution when forcing tags Before forcing, you must review the safety precautions (Page 1700) for this procedure. DANGER Prevent personal injury and material damage! Note that an incorrect action when executing the "Force" function can: Harm persons or pose a health hazard. Cause damage to machinery or the entire plant. Options for forcing tags The following options are available for forcing tags: Force to "0" This command forces the selected address in the CPU to the force value "0". Force to "1" This command forces the selected address in the CPU to the force value "1". Force all This command starts the forcing of enabled addresses in the active force table or replaces an existing force job without interruption. Stop forcing This command stops the forcing of all addresses in the active force table. WinCC Basic V13.0 System Manual, 02/2014 1699 Programming the PLC 9.4 Testing the user program Constraints when forcing tags Note the following constraints when forcing: Forcing is always dependent on the operand scope of the CPU used. In principle, only peripheral inputs and peripheral outputs can be forced. If the function "Enable peripheral outputs" is active on your CPU, then forcing is not possible. If desired, deactivate this function in the watch table. Unique aspects when forcing tags Note that forcing of tags will overwrite values in the CPU and will continue even after the online connection to the CPU is terminated. Stop forcing Terminating the online connection is not sufficient to stop the forcing operation! To stop forcing, you must select the "Online > Force > Stop forcing" command. Only then will the tags that are visible in the active force table no longer be forced. Stop forcing of individual tags The "Online > Force > Stop forcing" command always applies to all tags displayed in the force table. To stop forcing individual tags, you must clear the check mark for forcing of these tags in the force table and restart forcing using the "Online > Force > Force all" command. Safety precautions when forcing tags Safety precautions when forcing tags Because the forcing function allows you to intervene permanently in the process, observance of the following notices is essential: DANGER Prevent personal injury and material damage! Note that an incorrect action when executing the "Force" function can: Harm persons or pose a health hazard. Cause damage to machinery or the entire plant. 1700 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.4 Testing the user program CAUTION Prevent personal injury and material damage! Before you start the "Force" function, you should ensure that no one else is currently executing this function on the same CPU. Forcing can only be stopped by clicking the "Stop forcing" icon or using the "Online > Force > Stop forcing" command. Closing the active force table does not stop the forcing! Forcing can not be undone! Review the differences between " modifying tags" (Page 1674) and "forcing tags" (Page 1699). If a CPU does not support the "Force" function, the relevant icons cannot be selected. If the function "Enable peripheral outputs" is active on your CPU, then forcing is not possible on this CPU. If desired, deactivate this function in the watch table. Force tags to "0" Introduction You can use the force function to assign permanent values to individual tags of a user program. Caution when forcing tags Before forcing, you must review the safety precautions when forcing tags (Page 1700). DANGER Prevent personal injury and material damage! Note that an incorrect action when executing the "Force" function can: Pose a risk to the life or health of persons. Cause damage to machinery or the entire plant. Requirements An online connection to the CPU exists. The utilized CPU supports the force function. The "Enable peripheral outputs" function is not enabled on the CPU on which the tags are to be forced. If desired, deactivate this function in the watch table. WinCC Basic V13.0 System Manual, 02/2014 1701 Programming the PLC 9.4 Testing the user program Procedure To force tags to "0", follow these steps: 1. Open the force table. 2. Enter the desired address in the force table. 3. Select the "Online > Force> Force to 0" command in order to force the selected address with the specified value. 4. Confirm the next dialog with "Yes". Result The selected address is forced to "0". The yellow triangle is no longer displayed. A red "F" is displayed in the first column, for example, indicating that the tag is being forced. Stop forcing To stop forcing, follow these steps: 1. Open the force table. 2. Select the "Online > Force > Stop forcing" command. 3. Confirm the next dialog with "Yes". Result Forcing of the selected values is stopped. The red "F" in the first column is no longer displayed. The yellow triangle reappears behind the check box again to indicate that the address is selected for forcing but is not being forced at the moment. Note When forcing, note the following: Forcing cannot be undone! Terminating the online connection does not stop the forcing! To stop forcing, the forced address must be visible in the active force table. Force tags to "1" Introduction You can use the force function to assign permanent values to individual tags of a user program. 1702 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.4 Testing the user program Caution when forcing tags Before forcing, you must review the safety precautions when forcing tags (Page 1700). DANGER Prevent personal injury and material damage! Note that an incorrect action when executing the "Force" function can: Endanger the life or health of personnel Cause damage to machinery or the entire plant. Requirements An online connection to the CPU exists. The utilized CPU supports the force function. The "Enable peripheral outputs" function is not enabled on the CPU on which the tags are to be forced. If desired, deactivate this function in the watch table. Procedure To force tags to "1", follow these steps: 1. Open the force table. 2. Enter the desired address in the force table. 3. Select the "Online > Force> Force to 1" command in order to force the selected address with the specified value. 4. Confirm the next dialog with "Yes". Result The selected address is forced to "1". The yellow triangle is no longer displayed. A red "F" is displayed in the first column, for example, indicating that the tag is being forced. Stop forcing To stop forcing, follow these steps: 1. Open the force table. 2. Select the "Online > Force > Stop forcing" command. 3. Confirm the next dialog with "Yes". WinCC Basic V13.0 System Manual, 02/2014 1703 Programming the PLC 9.4 Testing the user program Result Forcing of the selected values is stopped. The red "F" in the first column is no longer displayed. The yellow triangle reappears behind the check box again to indicate that the address is selected for forcing but is not being forced at the moment. Note When forcing, note the following: Forcing cannot be undone! Terminating the online connection does not stop the forcing! To stop forcing, the forced address must be visible in the active force table. "Force all" command for tags Introduction You can use the force function to assign permanent values to individual tags of a user program. If forcing is already active, this forcing operation is replaced without interruption by the "Online > Force > Force all" command. Any forced addresses that are not selected will no longer be forced. Caution when forcing tags Before forcing, you must review the safety precautions when forcing tags (Page 1700). DANGER Prevent personal injury and material damage! Note that an incorrect action when executing the "Force" function can: Pose a risk to the life or health of persons. Cause damage to machinery or the entire plant. Requirements An online connection to the CPU exists. The utilized CPU supports the force function. The "Enable peripheral outputs" function is not enabled on the CPU on which the tags are to be forced. If desired, deactivate this function in the watch table. 1704 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.4 Testing the user program Procedure To force tags with the "Online > Force > Force all" command, follow these steps: 1. Open the force table. 2. Enter the desired addresses and force values in the force table. 3. Select the addresses to be forced by selecting the check boxes for forcing in the column after the "Force value". A yellow triangle appears behind the selected check box, indicating that the address is selected for forcing but is not being forced at the moment. 4. Select the "Online > Force> Force all" command in order to force the selected addresses with the specified values. 5. Confirm the next dialog with "Yes". Result The selected addresses are forced to the specified values. The yellow triangle is no longer displayed. A red "F" is displayed in the first column, for example, indicating that the tag is being forced. Stop forcing To stop forcing, follow these steps: 1. Open the force table. 2. Select the "Online > Force > Stop forcing" command. 3. Confirm the next dialog with "Yes". Result Forcing of the selected addresses is stopped. The red "F" in the first column is no longer displayed. The yellow triangle reappears behind the check box again to indicate that the address is selected for forcing but is not being forced at the moment. Note When forcing, note the following: Forcing cannot be undone! Terminating the online connection does not stop the forcing! To stop forcing, the forced address must be visible in the active force table. WinCC Basic V13.0 System Manual, 02/2014 1705 Programming the PLC 9.4 Testing the user program 9.4.4.10 Stop forcing tags Stop forcing all tags Introduction Note the following before you stop forcing tags: Stopping forcing cannot be undone! Terminating the online connection does not stop the forcing! To stop forcing, the forced address must be visible in the active force table. Caution when forcing tags Before forcing, you must review the safety precautions when forcing tags (Page 1700). DANGER Prevent personal injury and material damage! Note that an incorrect action when stopping the "Force" function can: Pose a risk to the life or health of persons. Cause damage to machinery or the entire plant. Requirements Tags are forced in a force table. An online connection to the CPU exists. The utilized CPU supports the force function. The "Enable peripheral outputs" function is not enabled on the CPU on which the tags are to be forced. If desired, deactivate this function in the watch table. Procedure Proceed as follows to stop forcing all tags : 1. Open the force table. 2. Select the "Online > Force > Stop forcing" command in order to stop forcing the displayed addresses. 3. Confirm the "Stop forcing" dialog with "Yes". 1706 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.4 Testing the user program Result The forcing of all tags is stopped. The red "F" in the first column is no longer displayed. The yellow triangle reappears behind the check box again to indicate that the address is flagged for forcing but is not being forced at the moment. Stop forcing individual tags Introduction Note the following before you stop forcing tags: Stopping forcing cannot be undone! Terminating the online connection does not stop the forcing! To stop forcing, the forced address must be visible in the active force table. Caution when forcing tags Before forcing, you must review the safety precautions when forcing tags (Page 1684). DANGER Prevent personal injury and material damage! Note that an incorrect action when stopping the "Force" function can: Pose a risk to the life or health of persons. Cause damage to machinery or the entire plant. Requirements Tags are forced in a force table. An online connection to the CPU exists. The utilized CPU supports the force function. The "Enable peripheral outputs" function is not enabled on the CPU on which the tags are to be forced. If desired, deactivate this function in the watch table. Procedure Proceed as follows to stop forcing individual tags : 1. Open the force table. 2. Deactivate the check boxes for the addresses that are no longer to be forced. 3. Reselect the "Online > Force" command. WinCC Basic V13.0 System Manual, 02/2014 1707 Programming the PLC 9.5 Using Team Engineering Result Forcing of the disabled addresses will be stopped. The red "F" in the first column is no longer displayed. The yellow triangle reappears behind the check box again to indicate that the address is flagged for forcing but is not being forced at the moment. 9.5 Using Team Engineering 9.5.1 Exchanging data with Inter Project Engineering (IPE) 9.5.1.1 Basics of Inter Project Engineering (IPE) Introduction to Inter Project Engineering (IPE) The functionality of Inter Project Engineering, hereinafter referred to as IPE, is used to exchange the controller data in a source project between different projects with the help of a device proxy. You can then transfer this data to other projects, for visualization in HMI, for example, and use it there for further configuration. Inter Project Engineering gives you a simple way of providing controller data from a PLC programming across multiple projects for an HMI configuration. Using the object "Device Proxy Data", you exchange controller data across multiple projects consistently and easily without redundant configuration overheads. This makes it possible for HMI project engineers to work on a project without the hardware configuration having to be present in their project. This means they can work on the PLC project and on the HMI project at the same time. You can exchange the following controller data between projects via the device proxy: Program blocks Technological objects PLC tags PLC alarms The following data is automatically included in the exchange: Controller interfaces Configured communication processors and communication modules This automatic data exchange ensures that the interfaces and the configured communication processors and modules are transferred along with the data you selected. This data is required to allow you to continue working consistently and without problems in your target project. 1708 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.5 Using Team Engineering Cross-project data exchange The following options are available for cross-project data exchange with Inter Project Engineering: Exchanging controller data via IPE file Exchanging controller data via project file Exchanging controller data via IPE file The figure below shows cross-project data exchange via an IPE file. 6RXUFHSURMHFW 7DUJHWSURMHFW 3/&B$ ([SRUW 'HYLFHSUR[\GDWD 3/&B$ 'HYLFHSUR[\GDWD 3/&B$ ,QLWLDOL]DWLRQ ,3(ILOH 3/&GHYLFHSUR[\ The PLC controller data from the source project is transferred to the PLC in the target project via the object "Device Proxy Data". Controller data that is exchanged via an IPE file must originate from TIA Portal Projects V13 or higher. Exchanging controller data via a project file The figure below shows cross-project data exchange via a project file. WinCC Basic V13.0 System Manual, 02/2014 1709 Programming the PLC 9.5 Using Team Engineering 6RXUFHSURMHFW 3/&B$ 'HYLFHSUR[\GDWD 7DUJHWSURMHFW ,QLWLDOL]DWLRQ 3URMHFWILOH 3/&B% 'HYLFHSUR[\GDWD 3/&GHYLFHSUR[\ The PLC controller data from the source project is transferred to the PLC in the target project via a project file. You can easily transfer and continue to use controller data from older TIA Portal projects as well as STEP 7 Classic projects that are not integrated in TIA Portal in your current TIA Portal projects. 9.5.1.2 Requirements for Inter Project Engineering (IPE) Software and hardware requirements To use the functionality of Inter Project Engineering, the minimum software and hardware requirements for the installation of TIA Portal V13 or higher must be met. The following requirements also apply: You have installed TIA Portal V13 or higher and the "SIMATIC STEP 7 Professional" software package. You are using a CPU of the S7-1200/1500 or S7-300/400 series. The same software version must be installed on all involved controllers. Requirements for IPE The requirements for accepting controller data from projects are as follows: You have created a project with hardware configuration and PLC data that can be transferred to another project. You have made sure that the project is consistent before you transfer the controller data by means of the device proxy data. You are familiar with the defined procedures for Inter Project Engineering. Notes on compatibility mode The functions for Inter Project Engineering are not available in compatibility mode. 1710 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.5 Using Team Engineering 9.5.1.3 Procedure for working with Inter Project Engineering (IPE) Exchanging controller data across projects You can use the functionality of Inter Project Engineering to exchange existing controller data between different projects with the help of a device proxy and to continue using this data in another project. The device proxy provides you with a consistent and convenient way of exchanging data between projects without redundant configuration overheads. Procedure for exchanging controller data via an IPE file To exchange data via an IPE file, follow these steps: 1. Using TIA Portal V13 or higher, create a project with all required controller data and an executable user program. 2. Configure the hardware required for the project. 3. Compile the project to ensure consistency in your project. 4. In your project, create the object "Device Proxy Data" below the required CPU by clicking the corresponding command "Add device proxy data" in the "Device Proxy Data" folder. Result: The "Device Proxy Data" object has been created. 5. Select the required device proxy data in the project tree and double-click the object to open it in the editor. 6. Enter the required data for the device proxy data in the editor under "General" or apply the default setting. You can change the name and enter a comment for export of the controller data. In the "Define content" area of the editor select which of the existing controller data you wish to export as IPE file and click "Export device proxy data". 7. In the subsequent dialog, enter the name and storage location for the IPE file to be created and click "Save". You will be notified as soon as the export has been completed successfully. Result: The selected controller data are exported as IPE file. 8. In your target project, create a device proxy to be able to import the controller data contained in the IPE file. To do so, click the command "Add new device" and select the required device proxy in the dialog that opens. 9. Click the newly created device proxy and select the "Initialize device proxy" command from the shortcut menu. 10.Select the previously created IPE file to be used for the initialization, and confirm the selection in the following dialog with "OK". This starts the initialization. Result: The controller data from the source project contained in the IPE file is transferred to the device proxy in the target project. After the successful exchange of controller data, you can continue with the configuration in your target project and, for example, connect PLC tags with HMI tags. The controller data can be updated as often as required when it is changed in the source project. WinCC Basic V13.0 System Manual, 02/2014 1711 Programming the PLC 9.5 Using Team Engineering Procedure for exchanging controller data via a project file When exchanging controller data via a project file, device proxy data can either be predefined in the source project or it can be defined and selected from the target project. Follow these steps to exchange data via a project file: 1. Using TIA Portal V13 or higher, create a project with all required controller data and an executable user program. 2. Configure the hardware required for the project. 3. Compile the project to ensure consistency in your project. 4. Open the TIA Portal project from which you want to import the controller data into the target project. 5. In your project, create the object "Device Proxy Data" below the required CPU by clicking the corresponding command "Add device proxy data" in the "Device Proxy Data" folder. Result: The "Device Proxy Data" object has been created. 6. Enter the required data for the device proxy data in the editor under "General" or apply the default setting. You can change the name and enter a comment for the device proxy data. 7. In the "Define content" area of the editor select which of the existing controller data you want to provide by means of the device proxy data. 8. Click "Save" to save the changes in the project. Result: You have successfully saved the selected controller data in your device proxy data. 9. In your target project, create a device proxy to import the controller data contained in the project file. To do so, click the command "Add new device" and select the required device proxy in the dialog that opens. 10.Click the newly created device proxy and select the "Initialize device proxy" command from the shortcut menu. 11.Select the previously created project file with the prepared device proxy data to be used for the initialization, and confirm the selection in the following dialog with "OK". This starts the initialization. Result: The controller data from the source project contained in the project file is transferred to the device proxy in the target project. After the successful exchange of controller data, you can continue with the configuration in your target project and, for example, connect PLC tags with HMI tags. The controller data can be updated as often as required when it is changed in the source project. Procedure for updating already transferred controller data System requirements for the update: The following requirements must be met for updating already transferred controller data with the help of the already created "Device Proxy Data" object: You are using the same project for the update as for the previous transfer of the controller data. You are using the already created "Device Proxy Data" for transfer of the controller data. You have not made any changes to the hardware configuration or the communication interfaces in the meantime. You can add new hardware components. 1712 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.5 Using Team Engineering Updating procedure: 1. Open the TIA Portal project from which you want to update the controller data in the target project. 2. Double-click the existing "Device Proxy Data" object and select under content which controller data you want to make available for the update. 3. Save the project or export the IPE file once again. 4. Open the required target project in the TIA Portal. 5. Click the existing device proxy in the target project and select the "Update device proxy" command from the shortcut menu. 6. Select the source which is to be used for the update, and confirm the selection. 7. In the following dialog, select under "Device" the CPU that was previously used as source, from which the controller data is to be re-imported. 8. Under "Defined device proxy data", select the required object and exit the dialog with "OK". 9. The update is then started and the selected device proxy data is transferred from the source project to the device proxy in the target project. After the successful update of the controller data, you can continue with the configuration in your target object and, for example, connect PLC tags with HMI tags. The controller data can be updated as often as required when it is changed in the source project. 9.5.1.4 Creating device proxy data Creating device proxy data To create a device proxy data, follow these steps: 1. Open the folder "Device Proxy Data" below the CPU to which you want to create a device proxy data. 2. Click the command "Add new device proxy data". Result The new device proxy data is created and displayed in the project tree. See also Basics of Inter Project Engineering (IPE) (Page 1708) Requirements for Inter Project Engineering (IPE) (Page 1710) Procedure for working with Inter Project Engineering (IPE) (Page 1711) WinCC Basic V13.0 System Manual, 02/2014 1713 Programming the PLC 9.5 Using Team Engineering Opening device proxy data (Page 1714) Exchange of controller data via IPE file (Page 1714) 9.5.1.5 Opening device proxy data Opening device proxy data To open a device proxy data in the editor, follow these steps: 1. Open the required "Device Proxy Data" with a double-click in the "Device Proxy Data" folder in the project tree below the CPU. Result The device proxy data is opened in the editor and displays the controller data assigned to it. You can either apply the defaults displayed in the editor or customize them as needed. See also Exchange of controller data via IPE file (Page 1714) Creating device proxy data (Page 1713) Basics of Inter Project Engineering (IPE) (Page 1708) Requirements for Inter Project Engineering (IPE) (Page 1710) Procedure for working with Inter Project Engineering (IPE) (Page 1711) 9.5.1.6 Exchange of controller data via IPE file Exchange of controller data via "IPE file" To export the controller data of the higher-level CPU displayed in the device proxy data, follow these steps: 1. Open the TIA Portal project from which you want to import the controller data into the target project. 2. Compile the project to ensure consistency in your project. 3. In your project, create the object "Device Proxy Data" below the required CPU by clicking the corresponding command "Add Device Proxy Data" in the "Device Proxy Data" folder. Result: The "Device Proxy Data" object has been created. 4. Select the device proxy data in the project tree and double-click the object to open it in the editor. 5. Enter the required data for the device proxy data in the editor under "General" or apply the default setting. You can change the name and enter a comment. 1714 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.5 Using Team Engineering 6. In the "Define content" area of the editor select which of the existing controller data you want to provide by means of the device proxy data. 7. Click the command "Export device proxy data" to export. 8. In the subsequent dialog, enter the name and storage location for the data to be exported and click "Save". The ".ipe" format is automatically specified as file format for the device proxy data file during the export. Result The selected device proxy data is exported and a progress bar for the export is displayed. You receive a message as soon as the export is successfully completed. The controller data of the selected CPU were stored in the saved ".ipe" file and can be conveniently forwarded, for example, by e-mail. The controller data can be imported in other devices without additional configuration, for example, for visualization and can be used further. See also Basics of Inter Project Engineering (IPE) (Page 1708) Requirements for Inter Project Engineering (IPE) (Page 1710) Procedure for working with Inter Project Engineering (IPE) (Page 1711) Creating device proxy data (Page 1713) Opening device proxy data (Page 1714) 9.5.1.7 Exchange of controller data via project file Exchange of controller data via a project file When exchanging controller data via a project file, device proxy data must be predefined in the source project. To export the controller data of the higher-level CPU displayed in the device proxy data as project file, follow these steps: 1. Open the TIA Portal project from which you want to import the controller data into the target project. 2. Compile the project to ensure consistency in your project. 3. In your project, create the object "Device Proxy Data" below the required CPU by clicking the corresponding command "Add Device Proxy Data" in the "Device Proxy Data" folder. Result: The "Device Proxy Data" object has been created. 4. Select the device proxy data in the project tree and double-click the object to open it in the editor. 5. Enter the required data for the device proxy data in the editor under "General" or apply the default setting. You can change the name and enter a comment. WinCC Basic V13.0 System Manual, 02/2014 1715 Programming the PLC 9.6 Programming examples 6. In the "Define content" area of the editor select which of the existing controller data you want to provide by means of the device proxy data. 7. Click "Save" to save the changes in the project. Result: You have successfully saved the selected controller data in your device proxy data. 8. Open the target project into which the controller data are to be imported. In your target project, create a device proxy to import the controller data contained in the project file. To do so, click the command "Add new device" and select the required device proxy in the dialog that opens. 9. Click "Save" to save the changes in the project. 10.Click the newly created device proxy and select the "Initialize device proxy" command from the shortcut menu. 11.Select the previously created project file with the prepared device proxy data to be used for the initialization, and confirm the selection in the following dialog with "OK". 12.In the following dialog, select the required CPU and select the prepared device proxy data. Confirm the dialog with "OK". This starts the initialization. Result: The controller data from the source project contained in the project file is transferred to the device proxy in the target project. After the successful exchange of controller data, you can continue with the configuration in your target project and, for example, connect PLC tags with HMI tags. The controller data can be updated as often as required when it is changed in the source project. 9.6 Programming examples 9.6.1 LAD programming examples 9.6.1.1 Example of controlling a conveyor belt Controlling a conveyor belt The following figure shows a conveyor belt that can be activated electrically. There are two pushbutton switches at the beginning of the conveyor belt: S1 for START and S2 for STOP. 1716 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.6 Programming examples There are also two pushbutton switches at the end of the conveyor belt: S3 for START and S4 for STOP. It is possible to start and stop the conveyor belt from either end. 6 6 2VWDUW 2VWRS 6 6 2VWDUW 2VWRS 02725B21 Implementation The following table shows the definition of the tags used: Name Data type Description StartSwitch_Left (S1) BOOL Start switch on the left side of the conveyor belt StopSwitch_Left (S2) BOOL Stop switch on the left side of the conveyor belt StartSwitch_Right (S3) BOOL Start switch on the right side of the conveyor belt StopSwitch_Right (S4) BOOL Stop switch on the right side of the conveyor belt MOTOR_ON BOOL Turn on the conveyor belt motor The following networks show the LAD programming for solving this task: Network 1: The conveyor belt motor is switched on when Start switch "S1" or "S3" is pressed. 6WDUW6ZLWFKB/HIW 02725B21 6 6WDUW6ZLWFKB5LJKW Network 2: The conveyor belt motor is switched off when Stop switch "S2" or "S4" is pressed. WinCC Basic V13.0 System Manual, 02/2014 1717 Programming the PLC 9.6 Programming examples 6WRS6ZLWFKB/HIW 02725B21 5 6WRS6ZLWFKB5LJKW 9.6.1.2 Example of detecting the direction of a conveyor belt Detecting the direction of a conveyor belt The following figure shows a conveyor belt that is equipped with two photoelectric barriers (PEB1 and PEB2). The photoelectric barriers are designed to detect the direction in which an object is moving on the conveyor belt. 3(% 3(% Implementation The following table shows the definition of the tags used: Name Data type Description PEB1 BOOL Photoelectric barrier 1 PEB2 BOOL Photoelectric barrier 2 RIGHT BOOL Display during movement to right LEFT BOOL Display during movement to left CM1 BOOL Edge bit memory 1 CM2 BOOL Edge bit memory 2 The following networks show the LAD programming for solving this task: Network 1: If the signal state changes from "0" to "1" (positive edge) at photoelectric barrier "PEB1" and, at the same time, the signal state at "PEB2" is "0", the object on the belt is moving to the left. 1718 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.6 Programming examples 3(% 3(% 3 &0 /()7 6 5,*+7 5 Network 2: If the signal changes from "0" to "1" (positive edge) at photoelectric barrier "PEB2" and, at the same time, the signal state at "PEB1" is "0", the object on the belt is moving to the right. 3(% 3 &0 9.6.1.3 3(% 5,*+7 6 /()7 5 Example of detecting the fill level of a storage area Detecting the fill level of a storage area The following figure shows a system with two conveyor belts and a temporary storage area between them. Conveyor belt 1 delivers packages to the storage area. A photoelectric barrier at the end of conveyor belt 1 near the storage area detects how many packages are delivered to the storage area. Conveyor belt 2 transports packages from the temporary storage area to a loading dock onto which the packages are loaded for delivery to customers by truck. A photoelectric barrier at the storage area exit detects how many packages leave the storage area to be transported to the loading dock. Five display lamps indicate the capacity of the temporary storage area. When a conveyor belt is restarted, the current count value is set to the number of packages available in the storage area. WinCC Basic V13.0 System Manual, 02/2014 1719 Programming the PLC 9.6 Programming examples 'LVSOD\SDQHO 6WRUDJHDUHD HPSW\ 6WRUDJHDUHD QRWHPSW\ 6WRUDJHDUHD IXOO LQFRPLQJ SDFNDJHV 6WRUDJHDUHD IXOO 6WRUDJHDUHD IXOO RXWJRLQJ SDFNDJHV 7HPSRUDU\ VWRUDJHDUHD IRU SDFNDJHV &RQYH\RUEHOW &RQYH\RUEHOW 3KRWRHOHFWULFEDUULHU 3KRWRHOHFWULFEDUULHU Implementation The following table shows the definition of the tags used: 1720 Name Data type Description PEB1 BOOL Photoelectric barrier 1 PEB2 BOOL Photoelectric barrier 2 RESET BOOL Reset counter LOAD BOOL Set counter to value of "PV" parameter STOCK INT Stock at restart PACKAGECOUNT INT Number of packages in the storage area (current count value) STOCK_PACKAGES BOOL Is set if the current count value is greater than or equal to the value of the tag "STOCK". STOR_EMPTY BOOL Display lamp: Storage area empty STOR_NOT_EMPTY BOOL Display lamp: Storage area not empty STOR_50%_FULL BOOL Display lamp: Storage area 50% full STOR_90%_FULL BOOL Display lamp: Storage area 90% full STOR_FULL BOOL Display lamp: Storage area full VOLUME_50 INT Comparison value: 50 packages WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.6 Programming examples Name Data type Description VOLUME_90 INT Comparison value: 90 packages VOLUME_100 INT Comparison value: 100 packages The following networks show the LAD programming for activating the lamps: Network 1: When a package is delivered to the storage area, the signal state at "PEB1" switches from "0" to "1" (positive signal edge). On a positive signal edge at "PEB1", the "Up" counter is enabled, and the current count value of "PACKAGECOUNT" is increased by one. When a package is delivered from the storage area to the loading dock, the signal state at "PEB2" switches from "0" to "1" (positive signal edge). On a positive signal edge at "PEB2", the "Down" counter is enabled, and the current count value of "PACKAGECOUNT" is decreased by one. If there are no packages in the storage area ("PACKAGECOUNT" = "0"), the "STOR_EMPTY" tag is set to signal state "1", and the "Storage area empty" lamp is switched on. The current count value can be reset to "0" if the "RESET" tag is set to signal state "1". If the "LOAD" tag is set to signal state "1", the current count value is set to the value of the "STOCK" tag. If the current count value is greater than or equal to the value of the "STOCK" tag, the "STOCK_PACKAGES" tag supplies the signal state "1". &78'B'% &78' 3(% 3(% 5(6(7 /2$' 672&. &8 ,17 672&.B3$&.$*(6 48 &' 4' 6725B(037< 5 &9 3$&.$*(&2817 /' 39 Network 2: As long as there are packages in the storage area, the "STOR_NOT_EMPTY" tag is set to signal state "1", and the "Storage area not empty" lamp is switched on. 6725B(037< 6725B127B(037< Network 3: If the number of packages in the storage area is greater than or equal to 50, the lamp for the*"Storage area 50% full" message switches on. WinCC Basic V13.0 System Manual, 02/2014 1721 Programming the PLC 9.6 Programming examples 3$&.$*(&2817 3$&.$*(&2817 ! ,17 ,17 92/80(B 6725BB)8// 92/80(B Network 4: If the number of packages in the storage area is greater than or equal to 90, the "Storage area 90% full" lamp switches on. 3$&.$*(&2817 3$&.$*(&2817 ! ,17 ,17 92/80(B 6725BB)8// 92/80(B Network 5: 3$&.$*(&2817 6725B)8// ! If the number of packages in the storage area reaches 100, the lamp for the "Storage area ,17 full" message switches on. 92/80(B 9.6.1.4 Example of controlling room temperature Controlling room temperature In a cold room, the temperature must be maintained below zero degrees Celsius. Any temperature fluctuations are monitored by a sensor. If the temperature rises above zero degrees Celsius, the cooling system switches on for a preset time. The "Cooling system On" lamp is lit during this time. The cooling system and the lamp are turned off if one of the following conditions is met: The sensor reports a temperature fall below zero degrees Celsius. The preset cooling time has elapsed. The pushbutton switch "STOP" has been pressed. If the preset cooling time has expired and the temperature in the cold room is still too high, the cooling system can be restarted by means of the pushbutton switch "RESET". 6723 7(03(5$785( 6(1625 1722 &22/,1* 6<67(0 /$03 5(6(7 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.6 Programming examples Implementation The following table shows the definition of the tags used: Name Data type Comment Sensor BOOL Temperature sensor signal RESET BOOL Restart STOP BOOL The cooling system is switched off. MaxCoolTime TIME Preset cooling time This tag is defined in the "DB_Cool" data block. CurrCoolTime TIME Currently elapsed cooling time This tag is defined in the "DB_Cool" data block. Cooling system BOOL The cooling system is switched on. Lamp BOOL The lamp for the "Cooling system on" message is switched on. TempVariable BOOL Temporary tag This tag stores the signal state of the IEC time TP. The following network shows the LAD programming for controlling room temperature: Network 1: 73B'% 73 7LPH 6HQVRU 5(6(7 '%B&RRO 0D[&RRO7LPH 7HPS9DULDEOH ,1 4 37 (7 '%B&RRO &XUU&RRO7LPH Network 2: 7HPS9DULDEOH 6723 6HQVRU &RROLQJV\VWHP /DPS When the temperature in the cold room rises above zero degrees Celsius, the signal state at the "Sensor" operand switches from "0" to "1" (positive signal edge). In the case of a positive signal edge at the input IN of the time function, the preset cooling time is started and the "TempVariable" receives the signal state "1". The signal state "1" of the "TempVariable" has the result in network 2 that the cooling system as well as the display lamp are turned on. The outputs "Sensor", "Cooling system" and "Lamp" must be programmed in network 2, because you can program only one coil at output Q of the time function. WinCC Basic V13.0 System Manual, 02/2014 1723 Programming the PLC 9.6 Programming examples If the temperature in the cold room falls below zero degrees Celsius, the signal state of the sensor switches back to "0". This switches the cooling system and lamp off. If the sensor does not signal a temperature drop, the cooling system and lamp are switched off after the preset cooling time has elapsed, at the latest. In this case, the cooling process can be restarted by pressing the "RESET" pushbutton switch. Pressing and releasing the pushbutton switch generates a new positive signal edge at input IN, which restarts the cooling system. Using the pushbutton switch "STOP", the cooling system and the display lamp can be turned off at any time. 9.6.2 FBD programming examples 9.6.2.1 Example of controlling a conveyor belt Controlling a conveyor belt The following figure shows a conveyor belt that can be activated electrically. There are two pushbutton switches at the beginning of the conveyor belt: S1 for START and S2 for STOP. There are also two pushbutton switches at the end of the conveyor belt: S3 for START and S4 for STOP. It is possible to start and stop the conveyor belt from either end. 6 6 2VWDUW 2VWRS 6 6 2VWDUW 2VWRS 02725B21 Implementation The following table shows the definition of the tags used: 1724 Name Data type Description StartSwitch_Left (S1) BOOL Start switch on the left side of the conveyor belt StopSwitch_Left (S2) BOOL Stop switch on the left side of the conveyor belt StartSwitch_Right (S3) BOOL Start switch on the right side of the conveyor belt WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.6 Programming examples Name Data type Description StopSwitch_Right (S4) BOOL Stop switch on the right side of the conveyor belt MOTOR_ON BOOL Turn on the conveyor belt motor The following networks show the FBD programming for solving this task: Network 1: The conveyor belt motor is switched on when Start switch "S1" or "S3" is pressed. 6WDUW6ZLWFKB/HIW ! 02725B21 6 6WDUW6ZLWFKB5LJKW Network 2: The conveyor belt motor is switched off when stop switch "S2" or "S4" is pressed. 6WRS6ZLWFKB/HIW ! 5 6WRS6ZLWFKB5LJKW 9.6.2.2 02725B21 Example of detecting the direction of a conveyor belt Detecting the direction of a conveyor belt The following figure shows a conveyor belt that is equipped with two photoelectric barriers (PEB1 and PEB2). The photoelectric barriers are designed to detect the direction in which an object is moving on the conveyor belt. 3(% WinCC Basic V13.0 System Manual, 02/2014 3(% 1725 Programming the PLC 9.6 Programming examples Implementation The following table shows the definition of the tags used: Name Data type Description PEB1 BOOL Photoelectric barrier 1 PEB2 BOOL Photoelectric barrier 2 RIGHT BOOL Display during movement to right LEFT BOOL Display during movement to left CM1 BOOL Edge bit memory 1 CM2 BOOL Edge bit memory 2 The following networks show the FBD programming for solving this task: Network 1: If the signal state changes from "0" to "1" (positive edge) at photoelectric barrier "PEB1" and, at the same time, the signal state at "PEB2" is "0", the object on the belt is moving to the left. 3(% 3 &0 3(% /()7 6 5,*+7 5 Network 2: If the signal changes from "0" to "1" (positive edge) at photoelectric barrier "PEB2" and, at the same time, the signal state at "PEB1" is "0", the object on the belt is moving to the right. 3(% 3 &0 3(% 5,*+7 6 /()7 5 9.6.2.3 Example of detecting the fill level of a storage area Detecting the fill level of a storage area The following figure shows a system with two conveyor belts and a temporary storage area between them. Conveyor belt 1 delivers packages to the storage area. A photoelectric barrier at the end of conveyor belt 1 near the storage area detects how many packages are delivered to the storage area. Conveyor belt 2 transports packages from the temporary storage area to a loading dock onto which the packages are loaded for delivery to customers by truck. A photoelectric barrier at the storage area exit detects how many packages leave the storage 1726 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.6 Programming examples area to be transported to the loading dock. Five display lamps indicate the capacity of the temporary storage area. When a conveyor belt is restarted, the current count value is set to the number of packages available in the storage area. 'LVSOD\SDQHO 6WRUDJHDUHD HPSW\ 6WRUDJHDUHD QRWHPSW\ 6WRUDJHDUHD IXOO LQFRPLQJ SDFNDJHV 6WRUDJHDUHD IXOO 6WRUDJHDUHD IXOO RXWJRLQJ SDFNDJHV 7HPSRUDU\ VWRUDJHDUHD IRU SDFNDJHV &RQYH\RUEHOW &RQYH\RUEHOW 3KRWRHOHFWULFEDUULHU 3KRWRHOHFWULFEDUULHU Implementation The following table shows the definition of the tags used: WinCC Basic V13.0 System Manual, 02/2014 Name Data type Description PEB1 BOOL Photoelectric barrier 1 PEB2 BOOL Photoelectric barrier 2 RESET BOOL Reset counter LOAD BOOL Set counter to value of "CV" parameter STOCK INT Stock at restart PACKAGECOUNT INT Number of packages in the storage area (current count value) STOCK_PACKAGES BOOL Is set if the current count value is greater than or equal to the value of the tag "STOCK". STOR_EMPTY BOOL Display lamp: Storage area empty STOR_NOT_EMPTY BOOL Display lamp: Storage area not empty STOR_50%_FULL BOOL Display lamp: Storage area 50% full 1727 Programming the PLC 9.6 Programming examples Name Data type Description STOR_90%_FULL BOOL Display lamp: Storage area 90% full STOR_FULL BOOL Display lamp: Storage area full VOLUME_50 INT Comparison value: 50 packages VOLUME_90 INT Comparison value: 90 packages VOLUME_100 INT Comparison value: 100 packages The following networks show the FBD programming for activating the lamps: Network 1: When a package is delivered to the storage area, the signal state at "PEB1" switches from "0" to "1" (positive signal edge). On a positive signal edge at "PEB1", the "Up" counter is enabled, and the current count value of "PACKAGECOUNT" is increased by one. When a package is delivered from the storage area to the loading dock, the signal state at "PEB2" switches from "0" to "1" (positive signal edge). On a positive signal edge at "PEB2", the "Down" counter is enabled, and the current count value of "PACKAGECOUNT" is decreased by one. If there are no packages in the storage area ("PACKAGECOUNT" = "0"), the "STOR_EMPTY" tag is set to signal state "1", and the "Storage area empty" lamp is switched on. The current count value can be reset to "0" if the "RESET" tag is set to signal state "1". If the "LOAD" tag is set to signal state "1", the current count value is set to the value of the "STOCK" tag. If the current count value is greater than or equal to the value of the "STOCK" tag, the "STOCK_PACKAGES" tag supplies the signal state "1". &78'B'% &78' ,17 3(% &8 3(% &' 5 4' 6725B(037< /2$' /' &9 672&. 39 48 5(6(7 3$&.$*(&2817 672&.B3$&.$*( Network 2: As long as there are packages in the storage area, the "STOR_NOT_EMPTY" tag is set to signal state "1", and the "Storage area not empty" lamp is switched on. 6725B127B(037< 6725B(037< Network 3: 1728 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.6 Programming examples If the number of packages in the storage area is greater than or equal to 50, the lamp for the "Storage area 50% full" message switches on. ! ,17 3$&.$*(&2817 ,1 92/80(B ,1 ,17 6725BB)8// 3$&.$*(&2817 ,1 92/80(B ,1 Network 4: If the number of packages in the storage area is greater than or equal to 90, the "Storage area 90% full" lamp switches on. ! ,17 3$&.$*(&2817 ,1 92/80(B ,1 ,17 6725BB)8// 3$&.$*(&2817 ,1 92/80(B ,1 Network 5: If the number of packages in the storage area reaches 100, the lamp for the "Storage area full" message switches on. ! ,17 3$&.$*(&2817 ,1 92/80(B 9.6.2.4 6725B)8// ,1 Example of controlling room temperature Controlling room temperature In a cold room, the temperature must be maintained below zero degrees Celsius. Any temperature fluctuations are monitored by a sensor. If the temperature rises above zero WinCC Basic V13.0 System Manual, 02/2014 1729 Programming the PLC 9.6 Programming examples degrees Celsius, the cooling system switches on for a preset time. The "Cooling system on" lamp is lit during this time. The cooling system and the lamp are turned off if one of the following conditions is met: The sensor reports a temperature fall below zero degrees Celsius. The preset cooling time has elapsed. The pushbutton switch "Stop" has been pressed. If the preset cooling time has expired and the temperature in the cold room is still too high, the cooling system can be restarted by means of the pushbutton switch "RESET". 6723 7(03(5$785( 6(1625 &22/,1* 6<67(0 /$03 5(6(7 Implementation The following table shows the definition of the tags used: Name Data type Comment Sensor BOOL Temperature sensor signal RESET BOOL Restart STOP BOOL The cooling system is switched off. MaxCoolTime TIME Preset cooling time This tag is defined in the "DB_Cool" data block. CurrCoolTime TIME Currently elapsed cooling time This tag is defined in the "DB_Cool" data block. Cooling system BOOL The cooling system is switched on. Lamp BOOL The lamp for the "Cooling system on" message is switched on. TempVariable BOOL Temporary tag This tag stores the signal state of the IEC time TP. The following network shows the FBD programming for controlling room temperature: Network 1: 1730 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.6 Programming examples 73B'% 73 7LPH 6HQVRU 5HVHW ,1 (7 '%B&RROLQJ &XUU&RRO7LPH 7HPS9DULDEOH '%B&RROLQJ 0D[&RRO7LPH 37 4 Network 2: 7HPS9DULDEOH 6HQVRU &RRO6\VWHP /DPS 6WRS When the temperature in the cold room rises above zero degrees Celsius, the signal state at the "Sensor" operand switches from "0" to "1" (positive signal edge). In the case of a positive signal edge at the input IN of the time function, the preset cooling time is started and the "TempVariable" receives the signal state "1". The signal state "1" of the "TempVariable" has the result in network 2 that the cooling system as well as the display lamp are turned on. The outputs "Sensor", "Cooling system" and "Lamp" must be programmed in network 2, because you can program only one coil at output Q of the time function. If the temperature in the cold room falls below zero degrees Celsius, the signal state of the sensor switches back to "0". This switches the cooling system and lamp off. If the sensor does not signal a temperature drop, the cooling system and lamp are switched off after the preset cooling time has elapsed, at the latest. In this case, the cooling process can be restarted by pressing the pushbutton switch "RESET". Pressing and releasing the pushbutton switch generates a new positive signal edge at input IN, which restarts the cooling system. Using the pushbutton switch "STOP", the cooling system and the display lamp can be turned off at any time. 9.6.3 SCL programming examples 9.6.3.1 Example: Bit logic instructions Controlling a conveyor belt The following figure shows a conveyor belt that can be activated electrically. There are two pushbutton switches at the beginning of the conveyor belt: S1 for START and S2 for STOP. WinCC Basic V13.0 System Manual, 02/2014 1731 Programming the PLC 9.6 Programming examples There are also two pushbutton switches at the end of the conveyor belt: S3 for START and S4 for STOP. It is possible to start and stop the conveyor belt from either end. 6 6 26WDUW 26WRS 6 6 26WDUW 26WRS 02725B21 Implementation The following table shows the definition of the tags used: Operand Declaration Data type Description StartSwitch_Left (S1) Input BOOL Start switch on the left side of the conveyor belt StopSwitch_Left (S2) Input BOOL Stop switch on the left side of the conveyor belt StartSwitch_Right (S3) Input BOOL Start switch on the right side of the conveyor belt StopSwitch_Right (S4) Input BOOL Stop switch on the right side of the conveyor belt MOTOR_ON Output BOOL Turn on the conveyor belt motor MOTOR_OFF Output BOOL Turn off the conveyor belt motor The following SCL program shows how to implement this task: SCL IF "StartSwitch_Left" OR "StartSwitch_Right" THEN "MOTOR_ON" := 1; END_IF; IF "StopSwitch_Left" OR "StopSwitch_Right" THEN "MOTOR_OFF" := 1; END_IF; The conveyor belt motor is switched on when start switch "StartSwitch_Left" or "StartSwitch_Right" is pressed. The conveyor belt motor is switched off when stop switch "StopSwitch_Left" or "StopSwitch_Right" is pressed. 1732 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.6 Programming examples 9.6.3.2 Example of detecting the direction of a conveyor belt Detecting the direction of a conveyor belt The following figure shows a conveyor belt that is equipped with two photoelectric barriers (PEB1 and PEB2). The photoelectric barriers are designed to detect the direction in which an object is moving on the conveyor belt. 3(% 3(% Implementation The following table shows the definition of the tags used: Name Declaration Data type Description Photoelectric barrier LS1 Input BOOL Photoelectric barrier 1 Photoelectric barrier LS2 Input BOOL Photoelectric barrier 2 RIGHT Output BOOL Display for movement to the right LEFT Output BOOL Display for movement to the left The following SCL program shows how to implement this example: SCL IF "LS1" = 1 AND NOT "LS2" = 0 THEN "LEFT" = 1; IF "LS2" = 1 AND NOT "LS1" = 0 THEN "RIGHT" := 1; IF "LS2" = 0 THEN "RIGHT" := 0; IF "LS1" = 0 THEN "LEFT" = 0; If the photoelectric barrier "PEB1" has signal state "1" and the photoelectric barrier "PEB2" has signal state "0" at the same time, the object on the belt is moving to the left. If the photoelectric barrier "PEB2" has signal state "1" and the photoelectric barrier "PEB1" has signal WinCC Basic V13.0 System Manual, 02/2014 1733 Programming the PLC 9.6 Programming examples state "0" at the same time, the object on the belt is moving to the right. The displays for a movement to the left or right will be turned off when the signal state at both photoelectric barriers is "0". 9.6.3.3 Example of detecting the fill level of a storage area Detecting the fill level of a storage area The following figure shows a system with two conveyor belts and a temporary storage area between them. Conveyor belt 1 delivers packages to the storage area. A photoelectric barrier at the end of conveyor belt 1 near the storage area detects how many packages are delivered to the storage area. Conveyor belt 2 transports packages from the temporary storage area to a loading dock onto which the packages are loaded for delivery to customers by truck. A photoelectric barrier at the storage area exit detects how many packages leave the storage area to be transported to the loading dock. Five display lamps indicate the capacity of the temporary storage area. When a conveyor belt is restarted, the current count value is set to the number of packages available in the storage area. 'LVSOD\SDQHO 6WRUDJHDUHD HPSW\ 6WRUDJHDUHD QRWHPSW\ LQFRPLQJ SDFNDJHV 6WRUDJHDUHD IXOO 6WRUDJHDUHD IXOO 6WRUDJHDUHD IXOO RXWJRLQJ SDFNDJHV 7HPSRUDU\ VWRUDJHDUHD IRU SDFNDJHV &RQYH\RUEHOW &RQYH\RUEHOW 3KRWRHOHFWULFEDUULHU 3KRWRHOHFWULFEDUULHU Implementation The following table shows the definition of the tags used: 1734 Name Declaration Data type Description PEB1 Input BOOL Photoelectric barrier 1 PEB2 Input BOOL Photoelectric barrier 2 RESET Input BOOL Reset counter WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.6 Programming examples Name Declaration Data type Description LOAD Input BOOL Set counter to value of "CV" parameter STOCK Input INT Stock at restart PACKAGECOUNT Output INT Number of packages in the storage area (current count value) STOCK_PACKAGES Output BOOL Is set if the current count value is greater than or equal to the value of the tag "STOCK". STOR_EMPTY Output BOOL Display lamp: Storage area empty STOR_NOT_EMPTY Output BOOL Display lamp: Storage area not empty STOR_50%_FULL Output BOOL Display lamp: Storage area 50% full STOR_90%_FULL Output BOOL Display lamp: Storage area 90% full STOR_FULL Output BOOL Display lamp: Storage area full VOLUME_50 Input INT Comparison value: 50 packages VOLUME_90 Input INT Comparison value: 90 packages VOLUME_100 Input INT Comparison value: 100 packages The following SCL program shows how to implement this example: When a package is delivered to the storage area, the signal state at "PEB1" switches from "0" to "1" (positive signal edge). On a positive signal edge at "PEB1", the "Up" counter is enabled, and the current count value of "PACKAGECOUNT" is increased by one. When a package is delivered from the storage area to the loading dock, the signal state at "PEB2" switches from "0" to "1" (positive signal edge). On a positive signal edge at "PEB2", the "Down" counter is enabled, and the current count value of "PACKAGECOUNT" is decreased by one. If there are no packages in the storage area ("PACKAGECOUNT" = "0"), the "STOR_EMPTY" tag is set to signal state "1", and the "Storage area empty" lamp is switched on. The current count value can be reset to "0" if the "RESET" tag is set to signal state "1". If the "LOAD" tag is set to signal state "1", the current count value is set to the value of the "STOCK" tag. If the current count value is greater than or equal to the value of the "STOCK" tag, the "STOCK_PACKAGES" tag supplies the signal state "1". SCL "CTUD_DB".CTUD(CU := "PEB1", CD := "PEB2", R WinCC Basic V13.0 System Manual, 02/2014 := "RESET", 1735 Programming the PLC 9.7 References SCL LD := "LOAD", PV := "STOCK", QU := "STOCK_PACKAGES", QD := "STOR_EMPTY", CV := "PACKAGECOUNT"); As long as there are packages in the storage area, the "STOR_NOT_EMPTY" tag is set to signal state "1", and the "Storage area not empty" lamp is switched on. SCL "STOR_NOT_EMPTY" := NOT "STOR_EMPTY" If the number of packages in the storage area is greater than or equal to 50, the lamp for the*"Storage area 50% full" message switches on. SCL IF "PACKAGECOUNT" >= "VOLUME_50" THEN "STOR_50%_FULL" := 1; IF "PACKAGECOUNT" <= "VOLUME_90" THEN "STOR_50%_FULL" := 1; If the number of packages in the storage area is greater than or equal to 90, the "Storage area 90% full" lamp switches on. SCL IF "PACKAGECOUNT" >= "VOLUME_90" THEN "STOR_90%_FULL" := 1; IF "PACKAGECOUNT" <= "VOLUME_100" THEN "STOR_90%_FULL" := 1; If the number of packages in the storage area reaches 100, the lamp for the "Storage area full" message switches on. SCL IF "PACKAGECOUNT" >= "VOLUME_100" THEN "STOR_FULL" := 1; 9.7 References 9.7.1 General parameters of the instructions 9.7.1.1 Meaning of the parameters REQ, RET_VAL and BUSY with asynchronous instructions Asynchronous instructions For instructions that work asynchronously, the function is executed with several calls. 1736 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Identification of the job If you use asynchronous instructions to trigger a process interrupt, output control commands to DP slaves, start a data transfer, or abort a non-configured connection with one of the SFCs listed above and then call the same SFC again before the current job is completed, then the reaction of the SFC will depend on whether the second call involves the same job. Parameter REQ The input parameter REQ (request) is used solely to start the job: If you call the instruction for a job that is not currently active, the job is started with REQ = 1 (case 1). If a particular job has been started and not yet completed and you call the instruction again to perform the same job (for example, in a cyclic interrupt OB), then REQ is not evaluated by the instruction (case 2). Parameter RET_VAL and BUSY The output parameters RET_VAL and BUSY indicate the status of the job. Pay attention to the note in section: Evaluating errors with output parameter RET_VAL (Page 1738) In case 1 (first call with REQ=1), the input parameter will be entered in RET_VALW#16#7001 if system resources are available and supply is correct. BUSY will be set. If the required system resources are currently being used or the input parameters have errors, the corresponding error code is entered in RET_VAL and BUSY has the value 0. In case 2 (interim call) W#16#7002 will be entered in RET_VAL (this corresponds to a warning: Job still being processed!), and BUSY will be set. The following applies to the last call for a job: - For instruction "DPNRM_DG", the number of data in bytes will entered as integer in RET_VAL in case there are no errors in data transmission. BUSY has the value "0" in this case. If there is an error, then the error information will be entered in RET_VAL and you should not evaluate BUSY in this case. - For all other instructions, "0" will be entered in RET_VAL if the job was executed without errors and BUSY has the value "0" in this case. If there is an error, the error code is entered in RET_VAL and BUSY has the value "0" in this case. Note If the first and last call coincide, the reaction is the same for RET_VAL and BUSY as described for the last call. WinCC Basic V13.0 System Manual, 02/2014 1737 Programming the PLC 9.7 References Overview The following table provides you with an overview of the relationships explained above. In particular, it shows the possible values of the output parameters if the execution of the job is not completed after an instruction call has been completed. Note Following every call, you must evaluate the relevant output parameters in your program. Relationship between call, REQ, RET_VAL and BUSY during execution of a "running" job. Number of the call Type of call REQ RET_VAL BUSY 1 First call 1 W#16#7001 1 Error code 0 2 to (n - 1) Intermediate call irrelevant W#16#7002 1 n Last call irrelevant W#16#0000, if no errors have occurred. 0 Error code if errors occurred 0 9.7.1.2 Evaluating errors with output parameter RET_VAL Types of error information An executed instruction indicates in the user program whether or not the CPU was able to execute the function of the instruction successfully. You can obtain information about any errors that occurred in two ways: In the BR bit of the status word in the output parameter RET_VAL (return value). Note Before evaluating the output parameters specific to an instruction, you should always follow the steps below: First, evaluate the BR bit of the status word. Then check the output parameter RET_VAL. If the BR bit indicates that an error has occurred or if RET_VAL contains a general error code, you should not evaluate the instruction-specific output parameters. Error information in the return value An instruction indicates that an error occurred during its execution by entering the value "0" in the binary result bit (BR) of the status word. Some instructions provide an additional error code at an output parameter known as the return value (RET_VAL). If a general error is entered in the output parameter RET_VAL (see below for explanation), this is only indicated by the value "0" in the BR bit of the status word. 1738 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References The return value is of the data type integer (INT). The relationship of the return value to the value "0" indicates whether or not an error occurred during execution of the function. CPU execution of the instruction BR Return value Sign of the integer With error(s) 0 less than "0" negative (sign bit is "1") Without error 1 greater than or equal to "0" positive (sign bit is "0") Reacting to error information There are two types of error codes in RET_VAL: A general error code that all instructions can output and A specific error code that an instruction can output and which relates to its specific function. You can write your program so that it reacts to the errors that occur during execution of an instruction. This way you prevent further errors occurring as a result of the first error. General and specific error information The return value (RET_VAL) of an instruction provides one of the two following types of error codes: A general error code that relates to errors that can occur in any instruction. A specific error code that relates only to the particular instruction. Even though the data type of the output parameter RET_VAL is an integer (INT), the error codes for the instruction are grouped according to hexadecimal values. If you want to examine a return value and compare the value with the error codes listed in this documentation, then display the error code in hexadecimal format. The figure below shows the structure of a system function error code in hexadecimal format. WinCC Basic V13.0 System Manual, 02/2014 1739 Programming the PLC 9.7 References (UURUFRGHHJ: [ (YHQWQXPEHURUHUURUFODVVDQGVLQJOHHUURU ,I[ WKHQ\RXDUHGHDOLQJZLWKDVSHFLILFHUURUFRGHRIDQLQVWUXFWLRQ7KH VSHFLILFHUURUFRGHLVLQFOXGHGLQWKHGHVFULSWLRQRIWKHLQGLYLGXDOLQVWUXFWLRQ ,I[! WKHQ\RXDUHGHDOLQJZLWKDJHQHUDOHUURUFRGHRIDQLQVWUXFWLRQ,QWKLV FDVH[LVWKHQXPEHURIWKHLQVWUXFWLRQSDUDPHWHUWKDWKDVFDXVHGWKHHUURU7KH SRVVLEOHJHQHUDOHUURUFRGHVDUHOLVWHGLQWKHIROORZLQJWDEOH 6LJQELW LQGLFDWHVWKDWDQHUURUKDVRFFXUUHG General error information The general error code indicates errors that can occur in all instructions. A general error code consists of the following two numbers: A parameter number from 1 to 111, where 1 indicates the first parameter of the called instruction, 2 the second parameter, and so forth. An event number from 0 to 127. The event number indicates that a synchronous error occurred. The following table lists the codes for general errors and an explanation of each error. %LWV 3DUDPHWHUQXPEHU (YHQWQXPEHU 6LJQ Note If a general error code was entered in RET_VAL, then the following situations are possible: The action associated with the instruction may have been started or already completed. A specific instruction error may have occurred when the action was performed. As a result of a general error that occurred later, the specific error could, however, no longer be indicated. Specific error information Some instructions have a return value that provides an error code specific for the instruction. A specific error code indicates errors that can occur only in specific instructions. 1740 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References A specific error code consists of the following two numbers: An error class from 0 to 7. An error number from 0 to 15. %LWV (UURUFODVV 6LQJOHHUURU 6LJQ General error codes The following table explains the general error codes of a return value. The error code is shown in hexadecimal format. The letter x in each code number is simply a place holder and represents the number of the system function parameter that caused the error. General error codes Error code Explanation (W#16#...) 8x7F Internal error This error code indicates an internal error at parameter x. 8x01 Illegal syntax ID at an VARIANT parameter 8x22 Range length error when reading a parameter. 8x23 Range length error when writing a parameter. This error code indicates that the parameter x is located either entirely or partly outside the range of an address, or that the length of a bit range is not a multiple of 8 with an VARIANT parameter. 8x24 Range error when reading a parameter. 8x25 Range error when writing a parameter. This error code indicates that the parameter x is located in a range that is illegal for the system function. Refer to the descriptions of the individual functions for information about the illegal ranges. 8x26 The parameter contains a timer cell number that is too high. This error code indicates that the timer cell specified in parameter x does not exist. 8x27 The parameter contains a counter cell number that is too high (counter number error). This error code indicates that the counter cell specified in parameter x does not exist. 8x28 Alignment error when reading a parameter. 8x29 Alignment error when writing a parameter. This error code indicates that the reference to parameter x is an operand with bit address that is not equal to 0. 8x30 The parameter is located in a read-only global DB. 8x31 The parameter is located in a read-only instance DB. This error code indicates that parameter x is located in a read-only data block. If the data block was opened by the system function itself, the system function always returns the value W#16#8x30. WinCC Basic V13.0 System Manual, 02/2014 1741 Programming the PLC 9.7 References Error code Explanation (W#16#...) 8x32 The parameter contains a DB number that is too high (DB number error). 8x34 The parameter contains an FC number that is too high (FC number error). 8x35 The parameter contains an FB number that is too high (FB number error). This error code indicates that parameter x contains a block number higher than the highest permitted number. 8x3A The parameter contains the number of a DB that is not loaded. 8x3C The parameter contains the number of an FC that is not loaded. 8x3E The parameter contains the number of an FB that is not loaded. 8x42 An access error occurred while the system was attempting to read a parameter from the peripheral input area. 8x43 An access error occurred while the system was attempting to write a parameter to the peripheral output area. 8x44 Error in the nth (n > 1) read access after an error occurred. 8x45 Error in the nth (n > 1) write access after an error occurred. This error code indicates that access to the required parameter is denied. 9.7.2 Basic instructions 9.7.2.1 LAD Bit logic operations ---| |---: Normally open contact Description The activation of the normally open contact depends on the signal state of the associated operand. When the operand has signal state "1", the normally open contact closes and the signal state at the output is set to the signal state of the input. When the operand has signal state "0", the normally open contact is not activated and the signal state at the output of the instruction is reset to "0". Two or more normally open contacts are linked bit-by-bit by AND when connected in series. With a series connection, power flows when all contacts are closed. The normally open contacts are linked by OR when connected in parallel. With a parallel connection, power flows when one of the contacts is closed. 1742 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameter The following table shows the parameters of the instruction: Paramete Declaratio Data r n type <Operan d> Input BOOL Memory area S7-1200 S7-1500 I, Q, M, D, L I, Q, M, D, L, T, C Description Operand whose signal state is queried. Example The following example shows how the instruction works: 7DJ,QB 7DJ,QB 7DJ2XW 7DJ,QB The "TagOut" operand is set when one of the following conditions is fulfilled: The operands "TagIn_1" and "TagIn_2" have signal state "1". The operand "TagIn_3" has the signal state "1". See also Overview of the valid data types (Page 1204) ---| / |---: Normally closed contact Description The activation of the normally closed contact depends on the signal state of the associated operand. When the operand has signal state "1", the normally closed contact opens and the signal state at the output of the instruction is reset to "0". When the operand has signal state "0", the normally closed contact is not enabled and the signal state of the input is transferred to the output. Two or more normally closed contacts are linked bit-by-bit by AND when connected in series. With a series connection, power flows when all contacts are closed. The normally closed contacts are linked by OR when connected in parallel. With a parallel connection, power flows when one of the contacts is closed. WinCC Basic V13.0 System Manual, 02/2014 1743 Programming the PLC 9.7 References Parameter The following table shows the parameters of the instruction: Parameter <Operand> Declaratio n Data type Input BOOL Memory area Description S7-1200 S7-1500 I, Q, M, D, L I, Q, M, D, L, T, C Operand whose signal state is queried. Example The following example shows how the instruction works: 7DJ,QB 7DJ,QB 7DJ2XW 7DJ,QB The "TagOut" operand is set when one of the following conditions is fulfilled: The operands "TagIn_1" and "TagIn_2" have signal state "1". The operand "TagIn_3" has the signal state "0". See also Overview of the valid data types (Page 1204) --|NOT|--: Invert RLO Description You use the "Invert RLO" instruction to invert the signal state of the result of logic operation (RLO). If the signal state is "1" at the input of the instruction, the output of the instruction has signal state "0". If the signal state is "0" at the input of the instruction, the output has the signal state "1". 1744 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Example The following example shows how the instruction works: 7DJ,QB 127 7DJ2XW 7DJ,QB 7DJ,QB Operand "TagOut" is reset when one of the following conditions is fulfilled: The operand "TagIn_1" has the signal state "1". The signal state of the operands "TagIn_2" and "TagIn_3" is "1". ---( )---: Assignment Description You can use the "Assignment" instruction to set the bit of a specified operand. If the result of logic operation (RLO) at the input of the coil has signal state "1", the specified operand is set to signal state "1". If the signal state is "0" at the input of the coil, the bit of the specified operand is reset to "0". The instruction does not influence the RLO. The RLO at the input of the coil is sent directly to the output. Parameter The following table shows the parameters of the "Assignment" instruction: Parameter Declaration Data type Memory area Description <Operand> Output BOOL I, Q, M, D, L Operand to which the RLO is assigned. Example The following example shows how the instruction works: 7DJ,QB 7DJ,QB 7DJ,QB 7DJ2XWB 7DJ,QB 7DJ2XWB The "TagOut_1" operand is set when one of the following conditions is fulfilled: WinCC Basic V13.0 System Manual, 02/2014 1745 Programming the PLC 9.7 References The operands "TagIn_1" and "TagIn_2" have signal state "1". The signal state of the operand "TagIn_3" is "0". The "TagOut_2" operand is set when one of the following conditions is fulfilled: Operands "TagIn_1", "TagIn_2", and "TagIn_4" have signal state "1". The signal state of the "TagIn_3" operand is "0" and the signal state of the "TagIn_4" operand is "1". See also Overview of the valid data types (Page 1204) --( / )--: Negate assignment Description The "Negate assignment" instruction inverts the result of logic operation (RLO) and assigns it to the specified operand. When the RLO at the input of the coil is "1", the operand is reset. When the RLO at the input of the coil is "0", the operand is set to signal state "1". Parameter The following table shows the parameters of the "Negate assignment" instruction: Parameter Declaration Data type Memory area Description <Operand> Output BOOL I, Q, M, D, L Operand to which the RLO is assigned. Example The following example shows how the instruction works: 7DJ,QB 7DJ,QB 7DJ,QB 7DJ2XWB 7DJ,QB 7DJ2XWB Operand "TagOut_1" is reset when one of the following conditions is fulfilled: The operands "TagIn_1" and "TagIn_2" have signal state "1". The signal state of the operand "TagIn_3" is "0". 1746 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References See also Overview of the valid data types (Page 1204) ---( R )---: Reset output Description You can use the "Reset output" instruction to reset the signal state of a specified operand to "0". The instruction is only executed if the result of logic operation (RLO) at the input of the coil is "1". If power flows to the coil (RLO = "1"), the specified operand is reset to "0". If the RLO at the input of the coil is "0" (no signal flow to the coil), the signal state of the specified operand remains unchanged. Parameter The following table shows the parameters of the "Reset output" instruction: Parameter <Operand> Declaration Output Data type BOOL Memory area S7-1200 S7-1500 Description I, Q, M, D, L I, Q, M, D, L, T, C Operand that is reset when RLO = "1". Example The following example shows how the instruction works: 7DJ,QB 7DJ,QB 7DJ2XW 5 7DJ,QB Operand "TagOut" is reset when one of the following conditions is fulfilled: The operands "TagIn_1" and "TagIn_2" have signal state "1". The signal state of the operand "TagIn_3" is "0". See also Overview of the valid data types (Page 1204) WinCC Basic V13.0 System Manual, 02/2014 1747 Programming the PLC 9.7 References ---( S )---: Set output Description You can use the "Set output" instruction to set the signal state of a specified operand to "1". The instruction is only executed if the result of logic operation (RLO) at the input of the coil is "1". If power flows to the coil (RLO = "1"), the specified operand is set to "1". If the RLO at the input of the coil is "0" (no signal flow to the coil), the signal state of the specified operand remains unchanged. Parameter The following table shows the parameters of the "Set output" instruction: Parameter Declaration Data type Memory area Description <Operand> Output BOOL I, Q, M, D, L Operand which is set with RLO = "1". Example The following example shows how the instruction works: 7DJ,QB 7DJ,QB 7DJ2XW 6 7DJ,QB The "TagOut" operand is set when one of the following conditions is fulfilled: The operands "TagIn_1" and "TagIn_2" have signal state "1". The signal state of the operand "TagIn_3" is "0". See also Overview of the valid data types (Page 1204) SET_BF: Set bit field Description You use the instruction "Set bit field" to set multiple bits starting from a certain address. You determine the number of bits to be set using the value of <Operand1>. The address of the first bit to be set is defined by <Operand2>. If the value of <Operand1> is greater than the number of bits in a selected byte, then the bits of the next byte will be set. The bits remain set until they are explicitly reset, for example, by another instruction. 1748 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References The instruction is only executed if the result of logic operation (RLO) at the input of the coil is "1". If the RLO at the input of the coil is "0", the instruction does not execute. Parameter The following table shows the parameters of the "Set bit field" instruction: Parameter Declaration Data type Memory area Description <Operand2> Output BOOL I, Q, M Pointer to the first bit to be set. In the case of a DB or an IDB, an element of an ARRAY[..] of BOOL <Operand1> Input UINT Constant Number of bits to be set. Example The following example shows how the instruction works: 7DJ,QB 7DJ,QB 0\'%0\%RRO$UUD\>@ 6(7B%) If the operands "TagIn_1" and "TagIn_2" have the signal state "1", 5 bits are set starting at the address of the operand "MyDB".MyBoolArray[4] See also Overview of the valid data types (Page 1204) RESET_BF: Reset bit field Description You use the "Reset bit field" instruction to reset several bits starting from a certain address. You specify the number of bits to be reset using the value of <Operand1>. The address of the first bit to be reset is specified by <Operand2>. If the value of <Operand1> is greater than the number of bits in a selected byte, the bits of the next byte will be reset. The bits remain reset until they are explicitly set, for example, by another instruction. The instruction is only executed if the result of logic operation (RLO) at the input of the coil is "1". If the RLO at the input of the coil is "0", the instruction does not execute. WinCC Basic V13.0 System Manual, 02/2014 1749 Programming the PLC 9.7 References Parameter The following table shows the parameters of the "Reset bit field" instruction: Parameter Declaration Data type Memory area Description <Operand2> Output BOOL I, Q, M Pointer to the first bit to be reset. In the case of a DB or an IDB, an element of an ARRAY[..] of BOOL <Operand1> Input UINT Constant Number of bits to be reset. Example The following example shows how the instruction works: 7DJ,QB 7DJ,QB 0\'%0\%RRO$UUD\>@ 5(6(7B%) If the operands "TagIn_1" and "TagIn_2" have the signal state "1", 5 bits are reset starting at the address of the operand "MyDB".MyBoolArray[4] See also Overview of the valid data types (Page 1204) SR: Set/reset flip-flop Description Use the instruction "Set/reset flip-flop" to set or reset the bit of the specified operand, depending on the signal state of the inputs S and R1. If the signal state is "1" at input S and "0" at input R1, the specified operand is set to "1". If the signal state is "0" at input S and "1" at input R1, the specified operand will be reset to "0". Input R1 takes priority over input S. When the signal state is "1" on both inputs S and R1, the signal state of the specified operand is reset to "0". The instruction is not executed if the signal state at the two inputs S and R1 is "0". The signal state of the operand then remains unchanged. The current signal state of the operand is transferred to output Q and can be queried there. 1750 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameter The following table shows the parameters of the "Set/reset flip-flop" instruction: Parameter Declaration Data type Memory area S7-1200 S7-1500 Description S Input BOOL I, Q, M, D, L I, Q, M, D, L Enable setting R1 Input BOOL I, Q, M, D, L I, Q, M, D, L, T, C Enable resetting <Operand> InOut BOOL I, Q, M, D, L I, Q, M, D, L Operand that is set or reset. Q Output BOOL I, Q, M, D, L I, Q, M, D, L Signal state of the operand Example The following example shows how the instruction works: 7DJ65 7DJ,QB 6 65 4 7DJ2XW 7DJ,QB 5 The operands "TagSR" and "TagOut" are set when the following conditions are fulfilled: The operand "TagIn_1" has the signal state "1". The operand "TagIn_2" has the signal state "0". The operands "TagSR" and "TagOut" are reset when one of the following conditions is fulfilled: The operand "TagIn_1" has signal state "0" and the operand "TagIn_2" has signal state "1". The operands "TagIn_1" and "TagIn_2" have signal state "1". See also Overview of the valid data types (Page 1204) RS: Reset/set flip-flop Description You can use the "Reset/set flip-flop" instruction to reset or set the bit of a specified operand based on the signal state of the inputs R and S1. If the signal state is "1" at input R and "0" at input S1, the specified operand will be reset to "0". If the signal state is "0" at input R and "1" at input S1, the specified operand is set to "1". Input S1 takes priority over input R. When the signal state is "1" at both inputs R and S1, the signal state of the specified operand is set to "1". WinCC Basic V13.0 System Manual, 02/2014 1751 Programming the PLC 9.7 References The instruction is not executed if the signal state at the two inputs R and S1 is "0". The signal state of the operand then remains unchanged. The current signal state of the operand is transferred to output Q and can be queried there. Parameter The following table shows the parameters of the "Reset/set flip-flop" instruction: Parameter Declaration Data type Memory area S7-1200 S7-1500 Description R Input BOOL I, Q, M, D, L I, Q, M, D, L Enable resetting S1 Input BOOL I, Q, M, D, L I, Q, M, D, L, T, C Enable setting <Operand> InOut BOOL I, Q, M, D, L I, Q, M, D, L Operand that is reset or set. Q Output BOOL I, Q, M, D, L I, Q, M, D, L Signal state of the operand Example The following example shows how the instruction works: 7DJ56 7DJ,QB 5 56 4 7DJ2XW 7DJ,QB 6 The operands "TagRS" and "TagOut" are reset when the following conditions are fulfilled: The operand "TagIn_1" has the signal state "1". The operand "TagIn_2" has the signal state "0". The operands "TagRS" and "TagOut" are set when one of the following conditions is fulfilled: The operand "TagIn_1" has signal state "0" and the operand "TagIn_2" has signal state "1". The operands "TagIn_1" and "TagIn_2" have signal state "1". See also Overview of the valid data types (Page 1204) 1752 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References --|P|--: Scan operand for positive signal edge Description You can use the "Scan operand for positive signal edge" instruction to determine if there is a "0" to "1" change in the signal state of a specified operand (<Operand1>). The instruction compares the current signal state of <Operand1> with the signal state of the previous scan that is saved in an edge memory bit (<Operand2>). If the instruction detects a change in the result of logic operation (RLO) from "0" to "1", there is a positive, rising edge. If a positive edge is detected, the output of the instruction has the signal state "1". In all other cases, the signal state at the output of the instruction is "0". Specify the operand to be queried (<Operand1>) in the operand placeholder above the instruction. Specify the edge memory bit (<Operand2>) in the operand placeholder below the instruction. Note The address of the edge memory bit must not be used more than once in the program, otherwise the bit memory is overwritten. This step influences the edge evaluation and the result is therefore no longer unique. The memory area of the edge memory bit must be located in a DB (static area for FB) or in the bit memory area. Parameter The following table shows the parameters of the "Scan operand for positive signal edge" instruction: Parameter Declaration Data type Memory area S7-1200 S7-1500 Description <Operand1> Input BOOL I, Q, M, D, L I, Q, M, D, L, T, C Signal to be scanned <Operand2> InOut BOOL I, Q, M, D, L I, Q, M, D, L Edge memory bit in which the signal state of the previous query is saved. Example The following example shows how the instruction works: 7DJ,QB 7DJ,QB 7DJ,QB 7DJ,QB 7DJ,QB 7DJ2XW 3 7DJB0 Operand "TagOut" is set when the following conditions are fulfilled: WinCC Basic V13.0 System Manual, 02/2014 1753 Programming the PLC 9.7 References The operands "TagIn_1", "TagIn_2", and "TagIn_3" have signal state "1". There is a rising edge at operand "TagIn_4". The signal state of the previous scan is stored in the edge memory bit "Tag_M". The signal state of the operand "TagIn_5" is "1". See also Overview of the valid data types (Page 1204) --|N|--: Scan operand for negative signal edge Description You can use the "Scan operand for negative signal edge" instruction to determine if there is a "1" to "0" change in the signal state of a specified operand (<Operand1>). The instruction compares the current signal state of <Operand1> with the signal state of the previous scan that is saved in an edge memory bit <Operand2>. If the instruction detects a change in the result of logic operation (RLO) from "1" to "0", there is a negative, falling edge. If a negative signal edge is detected, the output of the instruction has the signal state "1". In all other cases, the signal state at the output of the instruction is "0". Specify the operand to be queried (<Operand1>) in the operand placeholder above the instruction. Specify the edge memory bit (<Operand2>) in the operand placeholder below the instruction. Note The address of the edge memory bit must not be used more than once in the program, otherwise the bit memory is overwritten. This step influences the edge evaluation and the result is therefore no longer unique. The memory area of the edge memory bit must be located in a DB (static area for FB) or in the bit memory area. Parameter The following table shows the parameters of the "Scan operand for negative signal edge" instruction: Parameter 1754 Declaration Data type Memory area S7-1200 S7-1500 Description <Operand1 > Input BOOL I, Q, M, D, L I, Q, M, D, L, T, C Signal to be scanned <Operand2 > InOut BOOL I, Q, M, D, L I, Q, M, D, L Edge memory bit in which the signal state of the previous query is saved. WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Example The following example shows how the instruction works: 7DJ,QB 7DJ,QB 7DJ,QB 7DJ,QB 7DJ,QB 7DJ2XW 1 7DJB0 Operand "TagOut" is set when the following conditions are fulfilled: The operands "TagIn_1", "TagIn_2", and "TagIn_3" have signal state "1". There is a negative signal edge at operand "TagIn_4". The signal state of the previous scan is stored in the edge memory bit "Tag_M". The signal state of the operand "TagIn_5" is "1". See also Overview of the valid data types (Page 1204) --(P)--: Set operand on positive signal edge Description You can use the "Set operand on positive signal edge" instruction to set a specified operand (<Operand1>) when there is a "0" to "1" change in the result of logic operation (RLO). The instruction compares the current RLO with the RLO from the previous query, which is saved in the edge memory bit (<Operand2>). If the instruction detects a change in the RLO from "0" to "1", there is a positive signal edge. When a positive signal edge is detected, <Operand1> is set to signal state "1" for one program cycle. In all other cases, the operand has the signal state "0". Specify the operand to be set (<Operand1>) in the operand placeholder above the instruction. Specify the edge memory bit (<Operand2>) in the operand placeholder below the instruction. Note The address of the edge memory bit must not be used more than once in the program, otherwise the bit memory is overwritten. This step influences the edge evaluation and the result is therefore no longer unique. The memory area of the edge memory bit must be located in a DB (static area for FB) or in the bit memory area. WinCC Basic V13.0 System Manual, 02/2014 1755 Programming the PLC 9.7 References Parameter The following table shows the parameters of the "Set operand on positive signal edge" instruction: Parameter Declaration Data type Memory area Description <Operand1> Output BOOL I, Q, M, D, L Operand which is set by a positive edge. <Operand2> InOut BOOL I, Q, M, D, L Edge memory bit Example The following example shows how the instruction works: 7DJ,QB 7DJ,QB 7DJ2XW 3 7DJB0 7DJ,QB Operand "TagOut" is set for one program cycle, when the signal state at the input of the coil switches from "0" to "1" (positive signal edge). In all other cases, the operand "TagOut" has the signal state "0". See also Overview of the valid data types (Page 1204) --(N)--: Set operand on negative signal edge Description You can use the "Set operand on negative signal edge" instruction to set a specified operand (<Operand1>) when there is a "1" to "0" change in the result of logic operation (RLO). The instruction compares the current RLO with the RLO from the previous query, which is saved in the edge memory bit (<Operand2>). If the instruction detects a change in the RLO from "1" to "0", there is a negative edge. When a negative signal edge is detected, <Operand1> is set to signal state "1" for one program cycle. In all other cases, the operand has the signal state "0". 1756 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Specify the operand to be set (<Operand1>) in the operand placeholder above the instruction. Specify the edge memory bit (<Operand2>) in the operand placeholder below the instruction. Note The address of the edge memory bit must not be used more than once in the program, otherwise the bit memory is overwritten. This step influences the edge evaluation and the result is therefore no longer unique. The memory area of the edge memory bit must be located in a DB (static area for FB) or in the bit memory area. Parameter The following table shows the parameters of the "Set operand on negative signal edge" instruction: Parameter Declaration Data type Memory area Description <Operand1> Output BOOL I, Q, M, D, L Operand which is set by a negative edge. <Operand2> InOut BOOL I, Q, M, D, L Edge memory bit Example The following example shows how the instruction works: 7DJ,QB 7DJ,QB 7DJ2XW 1 7DJB0 7DJ,QB Operand "TagOut" is set for one program cycle, when the signal state at the input of the coil switches from "1" to "0" (negative signal edge). In all other cases, the operand "TagOut" has the signal state "0". See also Overview of the valid data types (Page 1204) P_TRIG: Scan RLO for positive signal edge Description Use the "Scan RLO for positive signal edge" instruction to query a "0" to "1" change in the signal state of the result of logic operation (RLO). The instruction compares the current signal state of the RLO with the signal state of the previous query, which is saved in an edge memory WinCC Basic V13.0 System Manual, 02/2014 1757 Programming the PLC 9.7 References bit (<operand>). If the instruction detects a change in the RLO from "0" to "1", there is a positive signal edge. If a positive edge is detected, the output of the instruction has the signal state "1". In all other cases, the signal state at the output of the instruction is "0". Note The address of the edge memory bit must not be used more than once in the program, otherwise the bit memory is overwritten. This step influences the edge evaluation and the result is therefore no longer unique. The memory area of the edge memory bit must be located in a DB (static area for FB) or in the bit memory area. Parameter The following table shows the parameters of the "Scan RLO for positive signal edge" instruction: Parameter Declaration Data type Memory area Description CLK Input BOOL I, Q, M, D, L Current RLO <Operand> InOut BOOL M, D Edge memory bit in which the RLO of the previous query is saved. Q Output BOOL I, Q, M, D, L Result of edge evaluation Example The following example shows how the instruction works: 7DJ,QB 7DJ,QB 3B75,* &/. 4 &$6 -03 7DJB0 7DJ,QB The RLO of the previous query is saved in the edge memory bit "Tag_M". If a "0" to "1" change is detected in the signal state of the RLO, the program jumps to jump label CAS1. See also Overview of the valid data types (Page 1204) 1758 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References N_TRIG: Scan RLO for negative signal edge Description Use the "Scan RLO for negative signal edge" instruction to query a "1" to "0" change in the signal state of the result of logic operation (RLO). The instruction compares the current signal state of the RLO with the signal state of the previous query, which is saved in an edge memory bit (<operand>). If the instruction detects a change in the RLO from "1" to "0", there is a negative edge. If a negative signal edge is detected, the output of the instruction has the signal state "1". In all other cases, the signal state at the output of the instruction is "0". Note The address of the edge memory bit must not be used more than once in the program, otherwise the bit memory is overwritten. This step influences the edge evaluation and the result is therefore no longer unique. The memory area of the edge memory bit must be located in a DB (static area for FB) or in the bit memory area. Parameter The following table shows the parameters of the "Scan RLO for negative signal edge" instruction: Parameters Declaration Data type Memory area Description CLK Input BOOL I, Q, M, D, L Current RLO <Operand> InOut BOOL M, D Edge memory bit in which the RLO of the previous query is saved. Q Output BOOL I, Q, M, D, L Result of edge evaluation Example The following example shows how the instruction works: 7DJ,QB 7DJ,QB 1B75,* &/. 4 &$6 -03 7DJB0 7DJ,QB The RLO of the previous query is saved in the edge memory bit "Tag_M". If a "1" to "0" change is detected in the signal state of the RLO, the program jumps to jump label CAS1. WinCC Basic V13.0 System Manual, 02/2014 1759 Programming the PLC 9.7 References See also Overview of the valid data types (Page 1204) R_TRIG: Set tag on positive signal edge Description You can use the "Set tag on positive signal edge" instruction to set a specified tag in the instance DB when there is a "0" to "1" change in the result of logic operation (RLO). The instruction compares the current RLO at the input CLK with the RLO from the previous query, which is saved in the specified instance DB. If the instruction detects a change in the RLO from "0" to "1", there is a positive signal edge. If a positive edge is detected, the tag in the instance DB is set to signal state "1" and the output Q returns the signal state "1" In all other cases, the signal state at the output of the instruction is "0". When you insert the instruction in the program, the "Call options" dialog opens automatically. In this dialog you can specify whether the edge memory bit is stored in its own data block (single instance) or as a local tag (multiple instance) in the block interface. If you create a separate data block, you will find it in the project tree in the "Program resources" folder under "Program blocks > System blocks". For additional information on this topic, refer to "See also". Parameter The following table shows the parameters of the instruction "Set tag on positive signal edge": 1760 Parameter Declaration Data type Memory area Description EN Input BOOL I, Q, M, D, L Enable input ENO Output BOOL I, Q, M, D, L Enable output CLK Input BOOL I, Q, M, D, L or constant Incoming signal, the edge of which is to be queried. Q Output BOOL I, Q, M, D, L Result of edge evaluation WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Example The following example shows how the instruction works: '% 5B75,*B'% 5B75,* (1 7DJ,QB (12 7DJ,QB &/. 4 7DJ2XWB4 7DJ,QB The RLO of the preceding query is saved in the instance DB "R_TRIG_DB". If a change is the signal state of the RLO from "0" to "1" is detected in the operands "TagIn_1" and "TagIn_2" or in the operand "TagIn_3", the output "TagOut_Q" has signal state "1". See also Overview of the valid data types (Page 1204) F_TRIG: Set tag on negative signal edge Description You can use the "Set tag on negative signal edge" instruction to set a specified tag in the instance DB when there is a "1" to "0" change in the result of logic operation (RLO). The instruction compares the current RLO at the input CLK with the RLO from the previous query, which is saved in the specified instance DB. If the instruction detects a change in the RLO from "1" to "0", there is a negative edge. If a negative edge is detected, the tag in the instance DB is set to signal state "1" and the output Q returns the signal state "1" In all other cases, the signal state at the output of the instruction is "0". When you insert the instruction in the program, the "Call options" dialog opens automatically. In this dialog you can specify whether the edge memory bit is stored in its own data block (single instance) or as a local tag (multiple instance) in the block interface. If you create a separate data block, you will find it in the project tree in the "Program resources" folder under "Program blocks > System blocks". For additional information on this topic, refer to "See also". Parameter The following table shows the parameters of the instruction "Set tag on negative signal edge": WinCC Basic V13.0 System Manual, 02/2014 Parameter Declaration Data type Memory area Description EN Input BOOL I, Q, M, D, L Enable input ENO Output BOOL I, Q, M, D, L Enable output 1761 Programming the PLC 9.7 References Parameter Declaration Data type Memory area Description CLK Input BOOL I, Q, M, D, L or constant Incoming signal, the edge of which is to be queried. Q Output BOOL I, Q, M, D, L Result of edge evaluation Example The following example shows how the instruction works: '% )B75,*B'% )B75,* (1 7DJ,QB (12 7DJ,QB &/. 4 7DJ2XWB4 7DJ,QB The RLO of the preceding query is saved in the instance DB "F_TRIG_DB". If a change is the signal state of the RLO from "1" to "0" is detected in the operands "TagIn_1" and "TagIn_2" or in the operand "TagIn_3", the output "TagOut_Q" has signal state "1". See also Overview of the valid data types (Page 1204) Timer operations IEC Timers TP: Generate pulse Description You can use the "Generate pulse" instruction to set the output Q for a programmed duration. The instruction is started when the result of logic operation (RLO) at input IN changes from "0" to "1" (positive signal edge). The programmed time PT begins when the instruction starts. Output Q is set for the duration PT, regardless of the subsequent course of the input signal. Even if a new positive signal edge is detected, the signal state at the output Q is not affected as long as the PT time duration is running. 1762 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References You can scan the current time value at the ET output. The time value starts at T#0s and ends when the value of duration PT is reached. When the duration PT is reached and the signal state at input IN is "0", the ET output is reset. Each call of the "Generate pulse" instruction must be assigned to an IEC timer in which the instruction data is stored. Note If the timer is not called in the program because it is skipped, for example, the ET output returns a constant value as soon as the timer has expired. For S7-1200 CPU An IEC timer is a structure of the data type IEC_TIMER or TP_TIME that you can declare as follows: Declaration of a data block of system data type IEC_TIMER (for example, "MyIEC_TIMER") Declaration as a local tag of the type TP_TIME, TP_LTIME or IEC_TIMER in the "Static" section of a block (for example, #MyIEC_TIMER) For S7-1500 CPU An IEC timer is a structure of the data type IEC_TIMER, IEC_LTIMER, TP_TIME or TP_LTIME that you can declare as follows: Declaration of a data block of system data type IEC_TIMER or IEC_LTIMER (for example, "MyIEC_TIMER") Declaration as a local tag of the type TP_TIME, TP_LTIME, IEC_TIMER or IEC_LTIMER in the "Static" section of a block (for example, #MyIEC_TIMER) When you insert the instruction in the program, the "Call options" dialog opens in which you can specify whether the IEC timer is stored in its own data block (single instance) or as a local tag (multi-instance) in the block interface. If you create a separate data block, you will find it in the project tree in the "Program resources" folder under "Program blocks > System blocks". For additional information on this topic, refer to "See also". The instruction data is updated both when the instruction is called and also each time the outputs Q or ET are accessed. The execution of the "Generate pulse" instruction requires a preceding logic operation. It can be placed within or at the end of the network. WinCC Basic V13.0 System Manual, 02/2014 1763 Programming the PLC 9.7 References Parameters The following table shows the parameters of the "Generate pulse" instruction: Parameter Declaration Data type Memory area S7-1200 S7-1500 S7-1200 S7-1500 I, Q, M, D, L I, Q, M, D, L, P Description IN Input BOOL BOOL Start input PT Input TIME TIME, LTIME I, Q, M, D, L or constant I, Q, M, D, L, Duration of P or constant the pulse The value of the PT parameter must be positive. Q Output BOOL BOOL I, Q, M, D, L I, Q, M, D, L, P Pulse output ET Output TIME TIME, LTIME I, Q, M, D, L I, Q, M, D, L, P Current time value For additional information on valid data types, refer to "See also". Pulse timing diagram The following figure shows the pulse timing diagram of the "Generate pulse" instruction: ,1 4 37 37 37 (7 37 See also Overview of the valid data types (Page 1204) 1764 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References TON: Generate on-delay Description You can use the "Generate on-delay" instruction to delay setting of the Q output by the programmed duration PT. The instruction is started when the result of logic operation (RLO) at input IN changes from "0" to "1" (positive signal edge). The programmed time PT begins when the instruction starts. When the duration PT expires, the output Q has the signal state "1". Output Q remains set as long as the start input is still "1". When the signal state at the start input changes from "1" to "0", the Q output is reset. The timer function is started again when a new positive signal edge is detected at the start input. The current time value can be queried at the ET output. The time value starts at T#0s and ends when the value of duration PT is reached. The ET output is reset as soon as the signal state at the IN input changes to "0". Each call of the "Generate on-delay" instruction must be assigned to an IEC timer in which the instruction data is stored. Note If the timer is not called in the program because it is skipped, for example, the ET output returns a constant value as soon as the timer has expired. For S7-1200 CPU An IEC timer is a structure of the data type IEC_TIMER or TON_TIME that you can declare as follows: Declaration of a data block of system data type IEC_TIMER (for example, "MyIEC_TIMER") Declaration as a local tag of the type TON_TIME or IEC_TIMER in the "Static" section of a block (for example, #MyIEC_TIMER) For S7-1500 CPU An IEC timer is a structure of the data type IEC_TIMER, IEC_LTIMER, TON_TIME or TON_LTIME that you can declare as follows: Declaration of a data block of system data type IEC_TIMER or IEC_LTIMER (for example, "MyIEC_TIMER") Declaration as a local tag of the type TON_TIME, TON_LTIME, IEC_TIMER or IEC_LTIMER in the "Static" section of a block (for example, #MyIEC_TIMER) When you insert the instruction in the program, the "Call options" dialog opens in which you can specify whether the IEC timer is stored in its own data block (single instance) or as a local tag (multi-instance) in the block interface. If you create a separate data block, you will find it in the project tree in the "Program resources" folder under "Program blocks > System blocks". For additional information on this topic, refer to "See also". The instruction data is updated both when the instruction is called and also each time the outputs Q or ET are accessed. WinCC Basic V13.0 System Manual, 02/2014 1765 Programming the PLC 9.7 References The execution of the "Generate on-delay" instruction requires a preceding logic operation. It can be placed within or at the end of the network. Parameters The following table shows the parameters of the "Generate on-delay" instruction: Parameter Declaration Data type Memory area S7-1200 S7-1500 S7-1200 S7-1500 I, Q, M, D, L I, Q, M, D, L, P Description IN Input BOOL BOOL Start input PT Input TIME TIME, LTIME I, Q, M, D, L or constant I, Q, M, D, L, Duration of P or constant the on-delay The value of the PT parameter must be positive. Q Output BOOL BOOL I, Q, M, D, L I, Q, M, D, L, P Output that is set when the time PT expires. ET Output TIME TIME, LTIME I, Q, M, D, L I, Q, M, D, L, P Current time value For additional information on valid data types, refer to "See also". Pulse timing diagram The following figure shows the pulse timing diagram of the "Generate on-delay" instruction: ,1 4 37 37 (7 37 1766 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References See also Overview of the valid data types (Page 1204) TOF: Generate off-delay Description You can use the "Generate off-delay" instruction to delay resetting of the Q output by the programmed duration PT. The Q output is set when the result of logic operation (RLO) at input IN changes from "0" to "1" (positive signal edge). When the signal state at input IN changes back to "0", the programmed time PT starts. Output Q remains set as long as the duration PT is running. When duration PT expires, the Q output is reset. If the signal state at input IN changes to "1" before the PT time duration expires, the timer is reset. The signal state at the output Q continues to be "1". The current time value can be queried at the ET output. The time value starts at T#0s and ends when the value of duration PT is reached. When the time duration PT expires, the ET output remains set to the current value until the IN input changes back to "1". If input IN switches to "1" before the duration PT has expired, the ET output is reset to the value T#0s. Each call of the "Generate off-delay" instruction must be assigned to an IEC timer in which the instruction data is stored. Note If the timer is not called in the program because it is skipped, for example, the ET output returns a constant value as soon as the timer has expired. For S7-1200 CPU An IEC timer is a structure of the data type IEC_TIMER or TOF_TIME that you can declare as follows: Declaration of a data block of system data type IEC_TIMER (for example, "MyIEC_TIMER") Declaration as a local tag of the type TOF_TIME or IEC_TIMER in the "Static" section of a block (for example, #MyIEC_TIMER) For S7-1500 CPU An IEC timer is a structure of the data type IEC_TIMER, IEC_LTIMER, TOF_TIME or TOF_LTIME that you can declare as follows: Declaration of a data block of system data type IEC_TIMER or IEC_LTIMER (for example, "MyIEC_TIMER") Declaration as a local tag of the type TOF_TIME, TOF_LTIME, IEC_TIMER or IEC_LTIMER in the "Static" section of a block (for example, #MyIEC_TIMER) When you insert the instruction in the program, the "Call options" dialog opens in which you can specify whether the IEC timer is stored in its own data block (single instance) or as a local tag (multi-instance) in the block interface. If you create a separate data block, you will find it WinCC Basic V13.0 System Manual, 02/2014 1767 Programming the PLC 9.7 References in the project tree in the "Program resources" folder under "Program blocks > System blocks". For additional information on this topic, refer to "See also". The instruction data is updated both when the instruction is called and also each time the outputs Q or ET are accessed. The execution of the "Generate off-delay" instruction requires a preceding logic operation. It can be placed within or at the end of the network. Parameters The following table shows the parameters of the "Generate off-delay" instruction: Parameter Declaration Data type Memory area S7-1200 S7-1500 S7-1200 S7-1500 I, Q, M, D, L I, Q, M, D, L, P Description IN Input BOOL BOOL Start input PT Input TIME TIME, LTIME I, Q, M, D, L or constant I, Q, M, D, L, Duration of P or constant the off delay The value of the PT parameter must be positive. Q Output BOOL BOOL I, Q, M, D, L I, Q, M, D, L, P Output that is reset when the timer PT expires. ET Output TIME TIME, LTIME I, Q, M, D, L I, Q, M, D, L, P Current time value For additional information on valid data types, refer to "See also". 1768 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Pulse timing diagram The following figure shows the pulse timing diagram of the "Generate off-delay" instruction: ,1 4 37 37 (7 37 See also Overview of the valid data types (Page 1204) TONR: Time accumulator Description The "Time accumulator" instruction is used to accumulate time values within a period set by the PT parameter. When the signal state at input IN changes from "0" to "1" (positive signal edge), the instruction executes and the duration PT starts. While the duration PT is running, the time values are accumulated that are recorded when the IN input has signal state "1". The accumulated time is written to output ET and can be queried there. When the duration PT expires, the output Q has the signal state "1". The Q parameter remains set to "1", even when the signal state at the IN parameter changes from "1" to "0" (negative signal edge). The R input resets the outputs ET and Q regardless of the signal state at the start input. Each call of the "Time accumulator" instruction must be assigned to an IEC timer in which the instruction data is stored. For S7-1200 CPU An IEC timer is a structure of the data type IEC_TIMER or TONR_TIME that you can declare as follows: Declaration of a data block of system data type IEC_TIMER (for example, "MyIEC_TIMER") Declaration as a local tag of the type TONR_TIME or IEC_TIMER in the "Static" section of a block (for example, #MyIEC_TIMER) WinCC Basic V13.0 System Manual, 02/2014 1769 Programming the PLC 9.7 References For S7-1500 CPU An IEC timer is a structure of the data type IEC_TIMER, IEC_LTIMER, TONR_TIME or TONR_LTIME that you can declare as follows: Declaration of a data block of system data type IEC_TIMER or IEC_LTIMER (for example, "MyIEC_TIMER") Declaration as a local tag of the type TONR_TIME, TONR_LTIME, IEC_TIMER or IEC_LTIMER in the "Static" section of a block (for example, #MyIEC_TIMER) When you insert the instruction in the program, the "Call options" dialog opens in which you can specify whether the IEC timer is stored in its own data block (single instance) or as a local tag (multi-instance) in the block interface. If you create a separate data block, you will find it in the project tree in the "Program resources" folder under "Program blocks > System blocks". For additional information on this topic, refer to "See also". The instruction data is updated both when the instruction is called and also each time the outputs Q or ET are accessed. The execution of the Time accumulator" instruction requires a preceding logic operation. It can be placed within or at the end of the network. Parameters The following table shows the parameters of the "Time accumulator" instruction: Parameter Declaration Data type Memory area S7-1200 S7-1500 S7-1200 S7-1500 Description IN Input BOOL BOOL I, Q, M, D, L I, Q, M, D, L, P Start input R Input BOOL BOOL I, Q, M, D, L or constant I, Q, M, D, L, Reset input P or constant PT Input TIME TIME, LTIME I, Q, M, D, L or constant I, Q, M, D, L, Maximum P or constant duration of time recording The value of the PT parameter must be positive. Q Output BOOL BOOL I, Q, M, D, L I, Q, M, D, L, P Output that is set when the time PT expires. ET Output TIME TIME, LTIME I, Q, M, D, L I, Q, M, D, L, P Accumulated time For additional information on valid data types, refer to "See also". 1770 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Pulse timing diagram The following figure shows the pulse timing diagram of the "Time accumulator" instruction: ,1 5 4 37 (7 See also Overview of the valid data types (Page 1204) ---( TP )---: Start pulse timer Description Use the "Start pulse timer" instruction to start an IEC timer with a specified duration as pulse. The IEC timer is started when the result of logic operation (RLO) changes from "0" to "1" (positive signal edge). The IEC timer runs for the specified duration regardless of any subsequent changes in the RLO. The run of the IEC timer is also not affected by the detection of a new positive signal edge. As long as the IEC timer is running, the querying of the timer status for "1" returns the signal state "1". When the IEC timer has expired, the timer status returns the signal state "0". Note You can start and query the IEC timer at various execution levels, as each querying of the outputs Q or ET updates the IEC_TIMER structure. WinCC Basic V13.0 System Manual, 02/2014 1771 Programming the PLC 9.7 References For S7-1200 CPU The instruction "Start pulse timer" stores its data in a structure of the data type IEC_TIMER or TP_TIME. You can declare the structure as follows: Declaration of a data block of system data type IEC_TIMER (for example, "MyIEC_TIMER") Declaration as a local tag of the type TP_LTIME or IEC_TIMER in the "Static" section of a block (for example, #MyIEC_TIMER) For S7-1500 CPU The instruction "Start pulse timer" stores its data in a structure of the data type IEC_TIMER, IEC_LTIMER, TP_TIME or TP_LTIME. You can declare the structure as follows: Declaration of a data block of system data type IEC_TIMER or IEC_LTIMER (for example, "MyIEC_TIMER") Declaration as a local tag of the type TP_TIME, TP_LTIME, IEC_TIMER or IEC_LTIMER in the "Static" section of a block (for example, #MyIEC_TIMER) The instruction data is updated both when the instruction is called and also each time the assigned timer is accessed. The current timer status is stored in the Q structure component of the IEC timer. You can use a normally open contact to query timer status for "1" or a normally closed contact for "0". The query on Q or ET (for example, "MyTimer".Q or "MyTimer".ET) updates the IEC_TIMER structure. The execution of the "Start pulse timer" instruction assumes a preceding logic operation. It can be placed only at the end of the network. Parameter The following table shows the parameters of the "Start pulse timer" instruction: Parameter Declaration Data type S7-1200 S7-1500 Memory area Description <Time duration> Input TIME TIME, LTIME I, Q, M, D, L or constant Duration with which the IEC timer runs. <IEC timer> InOut IEC_TIMER, TP_TIME IEC_TIMER, IEC_LTIMER, TP_TIME, TP_LTIME D, L IEC timer that is started. For additional information on valid data types, refer to "See also". 1772 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Example The following example shows how the instruction works: 7DJB,QSXW '% 0\,(&B7,0(5 73 7DJ7LPH The "Start pulse timer" instruction is executed when the signal state of the operand "Tag_Input" changes from "0" to "1". The timer "DB1".MyIEC_TIMER is started for the time stored in the operand "TagTime". '% 0\,(&B7,0(54 7DJB2XWSXW As long as the timer "DB1". MyIEC_TIMER is running, the timer status ("DB1".MyIEC_TIMER.Q) has signal state "1" and the operand "Tag_Output" is set. When the IEC timer has expired, the signal state of the time status changes back to "0" and the "Tag_Output" operand is reset. See also Overview of the valid data types (Page 1204) ---( TON )---: Start on-delay timer Description Use the "Start on-delay timer" instruction to start an IEC timer with a specified duration as ondelay. The IEC timer is started when the result of logic operation (RLO) changes from "0" to "1" (positive signal edge). The IEC timer runs for the specified time. The output returns the signal state "1" if the RLO at the input of the instruction has the signal state "1". If the RLO changes to "0" before the time expires, the IEC timer is reset. In this case, querying the timer status for "1" returns signal state "0". The IEC timer restarts when the next positive signal edge is detected at the input of the instruction. Note You can start and query the IEC timer at various execution levels, as each querying of the outputs Q or ET updates the IEC_TIMER structure. WinCC Basic V13.0 System Manual, 02/2014 1773 Programming the PLC 9.7 References For S7-1200 CPU The instruction "Start on-delay timer" stores its data in a structure of the data type IEC_TIMER or TON_TIME. You can declare the structure as follows: Declaration of a data block of system data type IEC_TIMER (for example, "MyIEC_TIMER") Declaration as a local tag of the type TON_TIME or IEC_TIMER in the "Static" section of a block (for example, #MyIEC_TIMER) For S7-1500 CPU The "Start on-delay timer" instruction stores its data in a structure of the data type IEC_TIMER, IEC_LTIMER, TON_TIME or TON_LTIME. You can declare the structure as follows: Declaration of a data block of system data type IEC_TIMER or IEC_LTIMER (for example, "MyIEC_TIMER") Declaration as a local tag of the type TON_TIME, TON_LTIME, IEC_TIMER or IEC_LTIMER in the "Static" section of a block (for example, #MyIEC_TIMER) The instruction data is updated both when the instruction is called and also each time the assigned timer is accessed. The current timer status is stored in the ET structure component of the IEC timer. You can use a normally open contact to query timer status for "1" or a normally closed contact for "0". The query on Q or ET (for example, "MyTimer".Q or "MyTimer".ET) updates the IEC_TIMER structure. The execution of the "Start on-delay timer" instruction assumes a preceding logic operation. It can be placed only at the end of the network. Parameter The following table shows the parameters of the "Start on-delay timer" instruction: Parameter Declaration Data type S7-1200 S7-1500 Memory area Description <Time duration> Input TIME TIME, LTIME I, Q, M, D, L or constant Duration with which the IEC timer runs. <IEC timer> InOut IEC_TIMER, TON_TIME IEC_TIMER, IEC_LTIMER, TON_TIME, TON_LTIME D, L IEC timer that is started. For additional information on valid data types, refer to "See also". 1774 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Example The following example shows how the instruction works: 7DJB,QSXW 0\,(&B7,0(5 721 7DJ7LPH The "Start on-delay timer" instruction is executed when the signal state of the operand "Tag_Input" changes from "0" to "1". The "MyIEC_TIMER timer is started for the time stored in the "TagTime" operand. 0\,(&B7,0(54 7DJB2XWSXW If the timer "MyIEC_TIMER" has expired and the operand "Tag_Input" has the signal state "1", querying the timer status ("MyIEC_TIMER).Q) returns signal state "1" and the "Tag_Output" operand is set. When the signal state of the operand "Tag_Input" changes to "0", the querying of the timer status returns the signal state "0" and the operand "Tag_Output" is reset. See also Overview of the valid data types (Page 1204) ---( TOF )---: Start off-delay timer Description Use the "Start off-delay timer" instruction to start an IEC timer with a specified duration as ondelay. The query of the timer status for "1" returns the signal state "0" if the result of logic operation (RLO) at the input of the instruction has the signal state "1". When the RLO changes from "1" to "0" (negative signal edge), the IEC timer starts with the specified time. The timer status remains at signal state "1" as long as the IEC timer is running. When the timer has run out and the RLO at the input of the instruction has the signal state "0", the timer status is set to the signal state "0". If the RLO changes to "1" before the time expires, the IEC timer is reset and the timer status remains at signal state "1". Note You can start and query the IEC timer at various execution levels, as each querying of the outputs Q or ET updates the IEC_TIMER structure. WinCC Basic V13.0 System Manual, 02/2014 1775 Programming the PLC 9.7 References For S7-1200 CPU The instruction "Start off-delay timer" stores its data in a structure of the data type IEC_TIMER or TOF_TIME. You can declare the structure as follows: Declaration of a data block of system data type IEC_TIMER (for example, "MyIEC_TIMER") Declaration as a local tag of the type TOF_TIME or IEC_TIMER in the "Static" section of a block (for example, #MyIEC_TIMER) For S7-1500 CPU The "Start off-delay timer" instruction stores its data in a structure of the data type IEC_TIMER, IEC_LTIMER, TOF_TIME or TOF_LTIME. You can declare the structure as follows: Declaration of a data block of system data type IEC_TIMER or IEC_LTIMER (for example, "MyIEC_TIMER") Declaration as a local tag of the type TOF_TIME, TOF_LTIME, IEC_TIMER or IEC_LTIMER in the "Static" section of a block (for example, #MyIEC_TIMER) The instruction data is updated both when the instruction is called and also each time the assigned timer is accessed. The current timer status is stored in the ET structure component of the IEC timer. You can use a normally open contact to query timer status for "1" or a normally closed contact for "0". The query on Q or ET (for example, "MyTimer".Q or "MyTimer".ET) updates the IEC_TIMER structure. The execution of the "Start off-delay timer" instruction assumes a preceding logic operation. It can be placed only at the end of the network. Parameters The following table shows the parameters of the "Start off-delay timer" instruction: Parameter Declaration Data type S7-1200 S7-1500 Memory area Description <Time duration> Input TIME TIME, LTIME I, Q, M, D, L or constant Duration with which the IEC timer runs. <IEC timer> InOut IEC_TIMER, TOF_TIME IEC_TIMER, IEC_LTIMER, TOF_TIME, TOF_LTIME D, L IEC timer that is started. For additional information on valid data types, refer to "See also". 1776 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Example The following example shows how the instruction works: 7DJB,QSXW 0\,(&B7,0(5 72) 7DJ7LPH The "Start off-delay timer" instruction is executed when the signal state of the operand "Tag_Input" changes from "1" to "0". The timer #MyIEC_TIMER is started for the time stored in the operand "TagTime". 0\,(&B7,0(54 7DJB2XWSXW As long as timer #MyIEC_TIMER is running, the query of the time status (#MyIEC_TIMER.Q) returns the signal state "1" and operand "Tag_Output" is set. If the timer has expired and the operand "Tag_Input" has the signal state "0", the query of the timer status returns the signal state "0". If the signal state of the operand "Tag_Input" changes to "1" before timer #MyIEC_TIMER expires, the timer is reset. When the signal state of the operand "Tag_Input" is "1", the query of the timer status returns the signal state "1". See also Overview of the valid data types (Page 1204) ---( TONR )---: Time accumulator Description You can use the "Time accumulator" instruction to record how long the signal is at the input of instruction "1". The instruction is started when the result of logic operation (RLO) changes from "0" to "1" (positive signal edge). The time is recorded as long at the RLO is "1". If the RLO changes to "0", the instruction is halted. If the RLO changes back to "1", the time recording is continued. The query of the timer status for "1" returns the signal state "1" if the recorded time exceeds the value of the specified duration and the RLO at the input of coil is "1". The timer status and the currently expired timer can be reset to "0" using the "Reset timer" instruction. Note You can start and query the IEC timer at various execution levels, as each querying of the outputs Q or ET updates the IEC_TIMER structure. WinCC Basic V13.0 System Manual, 02/2014 1777 Programming the PLC 9.7 References For S7-1200 CPU The "Time accumulator" instruction stores its data in a structure of the data type IEC_TIMER or TONR_TIME. You can declare the structure as follows: Declaration of a data block of system data type IEC_TIMER (for example, "MyIEC_TIMER") Declaration as a local tag of the type TONR_TIME or IEC_TIMER in the "Static" section of a block (for example, #MyIEC_TIMER) For S7-1500 CPU The "Time accumulator" instruction stores its data in a structure of the data type IEC_TIMER, IEC_LTIMER, TONR_TIME or TONR_LTIME. You can declare the structure as follows: Declaration of a data block of system data type IEC_TIMER or IEC_LTIMER (for example, "MyIEC_TIMER") Declaration as a local tag of the type TONR_TIME, TONR_LTIME, IEC_TIMER or IEC_LTIMER in the "Static" section of a block (for example, #MyIEC_TIMER) The instruction data is updated both when the instruction is called and also each time the assigned timer is accessed. The current timer status is stored in the ET structure component of the IEC timer. You can use a normally open contact to query timer status for "1" or a normally closed contact for "0". The query on Q or ET (for example, "MyTimer".Q or "MyTimer".ET) updates the IEC_TIMER structure. The execution of the Time accumulator" instruction requires a preceding logic operation. It can be placed only at the end of the network. Parameter The following table shows the parameters of the "Time accumulator" instruction: Parameter Declaration Data type S7-1200 S7-1500 Memory area Description <Time duration> Input TIME TIME, LTIME I, Q, M, D, L or constant Duration with which the IEC timer runs. <IEC timer> InOut IEC_TIMER, TONR_TIME IEC_TIMER, IEC_LTIMER, TONR_TIME, TONR_LTIME D, L IEC timer that is started. For additional information on valid data types, refer to "See also". 1778 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Example The following example shows how the instruction works: 7DJB,QSXW 0\,(&B7,0(5 7215 7DJ7LPH The "Time accumulator" instruction executes on a positive signal edge in the RLO. The time is recorded as long as the operand "Tag_Input" has the signal state "1". 0\,(&B7,0(54 7DJB2XWSXW If the recorded time exceeds the value of the operand "TagTime", then the query of the timer status ("MyIEC_TIMER".Q) will return the signal state "1" and the operand "Tag_Output" will be set. See also Overview of the valid data types (Page 1204) ---( RT )---: Reset timer Description You can use the "Reset timer" instruction to reset an IEC timer to "0". The instruction is only executed if the result of logic operation (RLO) at the input of the coil is "1". If current is flowing to the coil (RLO is "1"), the structure components of the timer in the specified data block are reset to "0". If the RLO at the input of the instruction is "0", the timer remains unchanged. The instruction does not influence the RLO. The RLO at the input of the coil is sent directly to the output of the coil. You assign the "Reset timer" instruction an IEC timer that has been declared in the program. The instruction data is updated only when the instruction is called and not each time the assigned IEC timer is accessed. Querying the data is only identical from the call of the instruction to the next call of the instruction. WinCC Basic V13.0 System Manual, 02/2014 1779 Programming the PLC 9.7 References Parameters The following table shows the parameters of the "Reset timer" instruction": Parameter Declaration <IEC timer> Data type Output S7-1200 S7-1500 IEC_TIMER, TP_TIME, TON_TIME, TOF_TIME, TONR_TIME IEC_TIMER, IEC_LTIMER, TP_TIME, TP_LTIME, TON_TIME, TON_LTIME, TOF_TIME, TOF_LTIME, TONR_TIME, TONR_LTIME Memory area Description D, L IEC timer that is reset. For additional information on valid data types, refer to "See also". Example The following example shows how the instruction works: 721B'% 721 7,0( 7DJB,QSXWB 7DJB37 7DJB6WDWXV ,1 4 37 (7 7DJB(7 The "Generate on-delay" instruction executes when the signal state of the "Tag_Input_1" operand changes from "0" to "1". The timer stored in the "TON_DB" instance data block starts running for the time duration specified by operand "Tag_PT". 7DJB,QSXWB 7DJB,QSXWB 721B'% 57 If operands "Tag_Input_2" and "Tag_Input_3" have the signal state "1", the "Reset timer" instruction is executed and the timer stored in the "TON_DB" data block. See also Overview of the valid data types (Page 1204) ---( PT )---: Load time duration Description You can use the "Load time duration" instruction to set the time for an IEC timer. The instruction is executed in every cycle when the result of logic operation (RLO) at the input of the instruction 1780 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References has the signal state "1". The instruction writes the specified time to the structure of the specified IEC timer. Note If the specified IEC timer is running while the instruction executes, the instruction overwrites the current time of the specified IEC timer. This can change the timer status of the IEC timer. You assign an IEC timer declared in the program to the "Load time duration" instruction. The instruction data is updated only when the instruction is called and each time the assigned IEC timer is accessed. The query on Q or ET (for example, "MyTimer".Q or "MyTimer".ET) updates the IEC_TIMER structure. Parameter The following table shows the parameters of the "Load time duration" instruction: Parameter Declaration Data type S7-1200 S7-1500 Memory area Description <Time duration> Input TIME TIME, LTIME I, Q, M, D, L or constant Duration with which the IEC timer runs. <IEC timer> Output IEC_TIMER, TP_TIME, TON_TIME, TOF_TIME, TONR_TIME IEC_TIMER, IEC_LTIMER, TP_TIME, TP_LTIME, TON_TIME, TON_LTIME, TOF_TIME, TOF_LTIME, TONR_TIME, TONR_LTIME D, L IEC timer, the duration of which is set. For additional information on valid data types, refer to "See also". Example The following example shows how the instruction works: 721B'% 721 7,0( 7DJB,QSXWB 7DJB37 7DJB6WDWXV ,1 4 37 (7 7DJB(7 The "Generate on-delay" instruction executes when the signal state of the "Tag_Input_1" operand changes from "0" to "1". The IEC timer stored in the instance data block "TON_DB" is started with the time duration that is specified by the operand "Tag_PT". WinCC Basic V13.0 System Manual, 02/2014 1781 Programming the PLC 9.7 References 7DJB,QSXWB 721B'% 37 7DJB37B The "Load time duration" instruction is executed when the operand "Tag_Input_2" has the signal state "1". The instruction writes the time duration "Tag_PT_2" in the instance data block "TON_DB" and at the same time overwrites the value of the operand "Tag_PT" within the data block. The signal state of the timer status may therefore change at the next query or when "MyTimer".Q or "MyTimer".ET are accessed. See also Overview of the valid data types (Page 1204) SIMATIC Timers S_PULSE: Assign pulse timer parameters and start Description The "Assign pulse timer parameters and start" instruction starts a programmed timer when a change from "0" to "1" (positive signal edge) is detected in the result of logic operation (RLO) at input S. The timer expires with the programmed duration (TV) as soon as the signal state at input S is "1". If the signal state at input S changes to "0" before the programmed duration expires, the timer is stopped. In this case, the signal state at output Q is "0". The duration is made up internally of a time value and a time base and is programmed at parameter TV. When the instruction is started, the programmed time value is counted down towards zero. The time base indicates the time period with which the time value is changed. The current time value is output BI-coded at output BI and BCD-coded at output BCD. If the timer is running and the signal state at input R changes to "1" then the current time value and the time base are also set to zero. If the timer is not running, the signal state "1" at the R input has no effect. The "Assign pulse timer parameters and start" instruction requires a preceding logic operation for edge evaluation and can be placed within or at the end of the network. The instruction data is updated at every access. It can therefore happen that the query of the data at the start of the cycle returns different values than at the end of the cycle. Note In the time cell, the operating system reduces the time value in an interval specified by the time base by one unit until the value equals "0". The decrementation is performed asynchronously to the user program. The resulting timer is therefore at maximum up to one time interval shorter than the desired time base. You can find an example of how a time cell can be formed under: See also "L: Load timer value". 1782 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameters The following table shows the parameters of the instruction "Assign pulse timer parameters and start": Parameter Declaration Data type Memory area Description <Timer> InOut/Input TIMER T Time of the instruction The number of timers depends on the CPU. S Input BOOL I, Q, M, D, L Start input TV Input S5TIME, WORD I, Q, M, D, L or constant Preset time value R Input BOOL I, Q, M, T, C, D, L, P or constant Reset input BI Output WORD I, Q, M, D, L, P Current time value (BI-coded) BCD Output WORD I, Q, M, D, L, P Current time value (BCD format) Q Output BOOL I, Q, M, D, L Status of the timer For additional information on valid data types, refer to "See also". WinCC Basic V13.0 System Manual, 02/2014 1783 Programming the PLC 9.7 References Pulse timing diagram The following figure shows the pulse timing diagram of the instruction "Assign pulse timer parameters and start": W W W 5/2DWLQSXW6 5/2DWLQSXW5 7LPHUXQQLQJ 4XHU\ 4XHU\ W SURJUDPPHGWLPH Example The following example shows how the instruction works: 7LPHUB 7DJ,QB 7DJ,QB1XPEHU 7DJ,QB 6B38/6( 7DJ2XW 6 4 79 %, 7DJ9DOXHB %&' 7DJ9DOXHB 5 The timer "Timer_1" is started when the signal state of the operand "TagIn_1" changes from "0" to "1". The timer expires with the time value of the operand "TagIn_Number" as long as the operand "TagIn_1" has the signal state "1". If the signal state of the operand "TagIn_1" changes from "1" to "0" before the timer expires, the timer "Timer_1" is stopped. The operand "TagOut" is reset to "0" in this case. 1784 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References The operand "TagOut" has the signal state "1" as long as the timer is running and the operand "TagIn_1" has the signal state "1". When the timer expires or is reset, the operand "TagOut" is reset to "0". See also Overview of the valid data types (Page 1204) S_PEXT: Assign extended pulse timer parameters and start Description The "Assign extended pulse timer parameters and start" instruction starts a programmed timer when a change from "0" to "1" (positive signal edge) is detected in the result of logic operation (RLO) at input S. The timer expires with the programmed duration (TV), even if the signal state at input S changes to "0". As long as the timer is running, the output Q has the signal state "1". When the timer expires, the output Q is reset to "0". If the signal state at input S changes from "0" to "1" while the timer is running, the timer is restarted with the duration programmed at input TV. The duration is made up internally of a time value and a time base and is programmed at parameter TV. When the instruction is started, the programmed time value is counted down towards zero. The time base indicates the time period with which the time value is changed. The current time value is output BI-coded at output BI and BCD-coded at output BCD. If the timer is running and the signal state at input R changes to "1" then the current time value and the time base are also set to zero. If the timer is not running, the signal state "1" at the R input has no effect. The "Assign extended pulse timer parameters and start" instruction requires a preceding logic operation for edge evaluation and can be placed within or at the end of the network. The instruction data is updated at every access. It can therefore happen that the query of the data at the start of the cycle returns different values than at the end of the cycle. Note In the time cell, the operating system reduces the time value in an interval specified by the time base by one unit until the value equals "0". The decrementation is performed asynchronously to the user program. The resulting timer is therefore at maximum up to one time interval shorter than the desired time base. You can find an example of how a time cell can be formed under: See also "L: Load timer value". WinCC Basic V13.0 System Manual, 02/2014 1785 Programming the PLC 9.7 References Parameter The following table shows the parameters of the instruction "Assign extended pulse timer parameters and start": Parameter Declaration Data type Memory area Description <Timer> InOut/Input TIMER T Time of the instruction The number of timers depends on the CPU. S Input BOOL I, Q, M, D, L Start input TV Input S5TIME, WORD I, Q, M, D, L or constant Preset time value R Input BOOL I, Q, M, T, C, D, L, P or constant Reset input BI Output WORD I, Q, M, D, L, P Current time value (BI-coded) BCD Output WORD I, Q, M, D, L, P Current time value (BCD format) Q Output BOOL I, Q, M, D, L Status of the timer For additional information on valid data types, refer to "See also". 1786 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Pulse timing diagram The following figure shows the pulse timing diagram of the "Assign extended pulse timer parameters and start" instruction: W W W 5/2DWLQSXW6 5/2DWLQSXW5 7LPHULVUXQQLQJ 4XHU\ 4XHU\ W SURJUDPPHGWLPHU Example The following example shows how the instruction works: 7LPHUB 7DJ,QB 7DJ,QB1XPEHU 7DJ,QB 6B3(;7 7DJ2XW 6 4 79 %, 7DJ9DOXHB %&' 7DJ9DOXHB 5 The timer "Timer_1" is started when the signal state of the operand "TagIn_1" changes from "0" to "1". The timer expires with the time value of the operand "TagIn_Number" without being affected by a negative edge at input S. If the signal state of the operand "TagIn_1" changes from "0" to "1" before the timer expires, the timer is restarted. WinCC Basic V13.0 System Manual, 02/2014 1787 Programming the PLC 9.7 References The operand "TagOut" has the signal state "1" as long as the timer is running. When the timer expires or is reset, the operand "TagOut" is reset to "0". See also Overview of the valid data types (Page 1204) S_ODT: Assign on-delay timer parameters and start Description The "Assign on-delay timer parameters and start" instruction starts a programmed timer when a change from "0" to "1" (positive signal edge) is detected in the result of logic operation (RLO) at input S. The timer expires with the programmed duration (TV) as soon as the signal state at input S is "1". If the timer expires correctly and input S still has signal state "1" then output Q returns signal state "1". If the signal state at input S changes from "1" to "0" while the timer is running, the timer is stopped. In this case, output Q is reset to signal state "0". The duration is made up internally of a time value and a time base and is programmed at parameter TV. When the instruction is started, the programmed time value is counted down towards zero. The time base indicates the time period with which the time value is changed. The current time value is output BI-coded at output BI and BCD-coded at output BCD. If the time is running and the signal state at input R changes from "0" to "1" then the current time value and the time base are also set to zero. In this case, the signal state at output Q is "0". The timer is reset if the signal state is "1" at the R input even if the timer is not running and the RLO at input S is "1". Specify the timer of the instruction in the placeholder above the box. The timer must be declared with the data type TIMER. The "Assign on-delay timer parameters and start" instruction requires a preceding logic operation for edge evaluation and can be placed within or at the end of the network. The instruction data is updated at every access. It can therefore happen that the query of the data at the start of the cycle returns different values than at the end of the cycle. Note In the time cell, the operating system reduces the time value in an interval specified by the time base by one unit until the value equals "0". The decrementation is performed asynchronously to the user program. The resulting timer is therefore at maximum up to one time interval shorter than the desired time base. You can find an example of how a time cell can be formed under: See also "L: Load timer value". 1788 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameter The following table shows the parameters of the "Assign on-delay timer parameters and start" instruction: Parameter Declaration Data type Memory area Description <Timer> InOut/Input TIMER T Time of the instruction The number of timers depends on the CPU. S Input BOOL I, Q, M, D, L Start input TV Input S5TIME, WORD I, Q, M, D, L or constant Preset time value R Input BOOL I, Q, M, T, C, D, L, P or constant Reset input BI Output WORD I, Q, M, D, L, P Current time value (BI-coded) BCD Output WORD I, Q, M, D, L, P Current time value (BCD format) Q Output BOOL I, Q, M, D, L Status of the timer For additional information on valid data types, refer to "See also". WinCC Basic V13.0 System Manual, 02/2014 1789 Programming the PLC 9.7 References Pulse timing diagram The following figure shows the pulse timing diagram of the "Assign on-delay timer parameters and start" instruction: W W W 5/2DWLQSXW6 5/2DWLQSXW5 7LPHULVUXQQLQJ 4XHU\ 4XHU\ W SURJUDPPHGWLPHU Example The following example shows how the instruction works: 7LPHUB 7DJ,QB 7DJ,QB1XPEHU 7DJ,QB 6B2'7 7DJ2XW 6 4 79 %, 7DJ9DOXHB %&' 7DJ9DOXHB 5 The timer "Timer_1" is started when the signal state of the operand "TagIn_1" changes from "0" to "1". The timer expires with the time value of the operand "TagIn_Number". If the timer expires and the operand has the signal state "1", the operand "TagOut" is set to "1". If the signal state of the operand "TagIn_1" changes from "1" to "0" before the timer expires, the timer is stopped. The operand "TagOut" has the signal state "0" in this case. 1790 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References See also Overview of the valid data types (Page 1204) S_ODTS: Assign retentive on-delay timer parameters and start Description The "Assign retentive on-delay timer parameters and start" instruction starts a programmed timer when a change from "0" to "1" (positive signal edge) is detected in the result of logic operation (RLO) at input S. The timer expires with the programmed duration (TV), even if the signal state at input S changes to "0". If the timer expires, the "Q" output returns signal state "1" regardless of the signal state at input "S". If the signal state at input S changes from "0" to "1" while the timer is running, the timer is restarted with the duration programmed at input (TV). The duration is made up internally of a time value and a time base and is programmed at parameter TV. When the instruction is started, the programmed time value is counted down towards zero. The time base indicates the time period with which the time value is changed. The current time value is output BI-coded at output BI and BCD-coded at output BCD. Signal state "1" at input R resets the current time value and time base to "0" regardless of the signal state at start input S. In this case, the signal state at output Q is "0". The "Assign retentive on-delay timer parameters and start" instruction requires a preceding logic operation for edge evaluation and can be placed within or at the end of the network. The instruction data is updated at every access. It can therefore happen that the query of the data at the start of the cycle returns different values than at the end of the cycle. Note In the time cell, the operating system reduces the time value in an interval specified by the time base by one unit until the value equals "0". The decrementation is performed asynchronously to the user program. The resulting timer is therefore at maximum up to one time interval shorter than the desired time base. You can find an example of how a time cell can be formed under: See also "L: Load timer value". Parameter The following table shows the parameters of the "Assign retentive on-delay timer parameters and start" instruction: Parameter Declaration Data type Memory area Description <Timer> InOut/Input TIMER T Time of the instruction The number of timers depends on the CPU. S WinCC Basic V13.0 System Manual, 02/2014 Input BOOL I, Q, M, D, L Start input 1791 Programming the PLC 9.7 References Parameter Declaration Data type Memory area Description TV Input S5TIME, WORD I, Q, M, D, L or constant Preset time value R Input BOOL I, Q, M, T, C, D, L, P or constant Reset input BI Output WORD I, Q, M, D, L, P Current time value (BI-coded) BCD Output WORD I, Q, M, D, L, P Current time value (BCD format) Q Output BOOL I, Q, M, D, L Status of the timer For additional information on valid data types, refer to "See also". Pulse timing diagram The following figure shows the pulse timing diagram of the "Assign retentive on-delay timer parameters and start" instruction: W W W 5/2DWLQSXW6 5/2DWLQSXW5 7LPHULVUXQQLQJ 4XHU\ 4XHU\ W SURJUDPPHGWLPHU 1792 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Example The following example shows how the instruction works: 7LPHUB 7DJ,QB 7DJ,QB1XPEHU 7DJ,QB 6B2'76 7DJ2XW 6 4 79 %, 7DJ9DOXHB %&' 7DJ9DOXHB 5 The timer "Timer_1" is started when the signal state of the operand "TagIn_1" changes from "0" to "1". The timer expires with the time value of the operand "TagIn_Number", even if the signal state of the operand "TagIn_1" changes to "0". When the timer expires, the operand "TagOut" is set to "1". If the signal state of the operand "TagIn_1" changes from "0" to "1" while the timer is running, the timer is restarted. See also Overview of the valid data types (Page 1204) S_OFFDT: Assign off-delay timer parameters and start Description The "Assign off-delay timer parameters and start" instruction starts a programmed timer when a change from "1" to "0" (negative signal edge) is detected in the result of logic operation (RLO) at input S. The timer expires with the programmed duration (TV). As long as the timer is running or input S returns signal state "1", then output Q has signal state "1". When the timer expires and the signal state at input S is "0", output Q is reset to the signal state "0". If the signal state at input S changes from "0" to "1" while the timer is running, the timer is stopped. The timer is only restarted after a falling signal edge is detected at input S. The duration is made up internally of a time value and a time base and is programmed at parameter TV. When the instruction is started, the programmed time value is counted down towards zero. The time base indicates the time period with which the time value is changed. The current time value is output BI-coded at output BI and BCD-coded at output BCD. Signal state "1" at input R resets the current time value and time base to "0". In this case, the signal state at output Q is "0". The "Assign off-delay timer parameters and start" instruction requires a preceding logic operation for edge evaluation and can be placed within or at the end of the network. WinCC Basic V13.0 System Manual, 02/2014 1793 Programming the PLC 9.7 References The instruction data is updated at every access. It can therefore happen that the query of the data at the start of the cycle returns different values than at the end of the cycle. Note In the time cell, the operating system reduces the time value in an interval specified by the time base by one unit until the value equals "0". The decrementation is performed asynchronously to the user program. The resulting timer is therefore at maximum up to one time interval shorter than the desired time base. You can find an example of how a time cell can be formed under: See also "L: Load timer value". Parameter The following table shows the parameters of the "Assign off-delay timer parameters and start" instruction: Parameter Declaration Data type Memory area Description <Timer> InOut/Input TIMER T Time of the instruction The number of timers depends on the CPU. S Input BOOL I, Q, M, D, L Start input TV Input S5TIME, WORD I, Q, M, D, L or constant Preset time value R Input BOOL I, Q, M, T, C, D, L, P or constant Reset input BI Output WORD I, Q, M, D, L, P Current time value (BI-coded) BCD Output WORD I, Q, M, D, L, P Current time value (BCD format) Q Output BOOL I, Q, M, D, L Status of the timer For additional information on valid data types, refer to "See also". 1794 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Pulse timing diagram The following figure shows the pulse timing diagram of the "Assign off-delay timer parameters and start" instruction: W W W W 5/2DWLQSXW6 5/2DWLQSXW5 7LPHULVUXQQLQJ 4XHU\ 4XHU\ W SURJUDPPHGWLPHU Example The following example shows how the instruction works: 7LPHUB 7DJ,QB 7DJ,QB1XPEHU 7DJ,QB 6B2))'7 7DJ2XW 6 4 79 %, 7DJ9DOXHB %&' 7DJ9DOXHB 5 The timer "Timer_1" is started when the signal state of the operand "TagIn_1" changes from "1" to "0". The timer expires with the time value of the operand "TagIn_Number". The operand "TagOut" is set to "1" when the timer is running and when the operand "TagIn_1" has the signal state "0". If the signal state of the operand "TagIn_1" changes from "0" to "1" while the timer is running, the timer is reset. See also Overview of the valid data types (Page 1204) WinCC Basic V13.0 System Manual, 02/2014 1795 Programming the PLC 9.7 References ---( SP ): Start pulse timer Description The "Start pulse timer" instruction starts a programmed timer when a change from "0" to "1" (positive signal edge) is detected in the result of logic operation (RLO). The time runs with the specified duration as long as the RLO has the signal state "1". As long as the timer is running, the querying of the timer status for "1" returns the signal state "1". If there is a change from "1" to "0" in the RLO before the time value has elapsed, the timer stops. In this case, the querying of the timer status for "1" returns the signal state "0". The duration is made up internally of a time value and a time base. When the instruction is started, the programmed time value is counted down towards zero. The time base indicates the time period with which the time value is changed. The "Start pulse timer" instruction requires a preceding logic operation for edge evaluation and can only be placed at the right side of the network. Note In the time cell, the operating system reduces the time value in an interval specified by the time base by one unit until the value equals "0". The decrementation is performed asynchronously to the user program. The resulting timer is therefore at maximum up to one time interval shorter than the desired time base. You can find an example of how a time cell can be formed under: See also "L: Load timer value". Parameters The following table shows the parameters of the "Start pulse timer" instruction: Parameter Declaration Data type Memory area Description <Time duration> Input S5TIME, WORD I, Q, M, D, L or constant Duration with which the timer expires. <Timer> InOut/Input TIMER T Timer which is started. The number of timers depends on the CPU. For additional information on valid data types, refer to "See also". 1796 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Example The following example shows how the instruction works: 1HWZRUN 1HWZRUN 7DJ,QB 7LPHUB 63 7DJ,QB1XPEHU 7LPHUB 7DJ2XW 7DJ,QB 7LPHUB 5 1HWZRUN The timer "Timer_1" is started when the signal state of the operand "TagIn_1" changes from "0" to "1". The timer expires with the time value of the operand "TagIn_Number" as long as the signal state of the operand "TagIn_1" is "1". If the signal state of the operand "TagIn_1" changes from "1" to "0" before the timer expires, the timer is stopped. As long as the timer is running, the operand "TagOut" has the signal state "1". A signal state change of the operand "TagIn_1" from "0" to "1" resets the timer, which stops the timer and sets the current time value to "0". See also Overview of the valid data types (Page 1204) ---( SE ): Start extended pulse timer Description The "Start extended pulse timer" instruction starts a programmed timer when a change from "0" to "1" (positive signal edge) is detected in the result of logic operation (RLO). The timer expires with the specified duration, even if the RLO changes to the signal state "0". As long as the timer is running, the querying of the timer status for "1" returns the signal state "1". If the RLO changes from "0" to "1" while the timer is running, the timer is restarted with the programmed duration. The querying of the timer status for "1" returns the signal state "0" when the timer expires. The duration is made up internally of a time value and a time base. When the instruction is started, the programmed time value is counted down towards zero. The time base indicates the time period with which the time value is changed. WinCC Basic V13.0 System Manual, 02/2014 1797 Programming the PLC 9.7 References The "Start extended pulse timer" instruction requires a preceding logic operation for edge evaluation and can only be placed at the right side of the network. Note In the time cell, the operating system reduces the time value in an interval specified by the time base by one unit until the value equals "0". The decrementation is performed asynchronously to the user program. The resulting timer is therefore at maximum up to one time interval shorter than the desired time base. You can find an example of how a time cell can be formed under: See also "L: Load timer value". Parameter The following table shows the parameters of the "Start extended pulse timer" instruction: Parameter Declaration Data type Memory area Description <Time duration> Input S5TIME, WORD I, Q, M, D, L or constant Duration with which the timer expires. <Timer> InOut/Input TIMER T Timer which is started. The number of timers depends on the CPU. For additional information on valid data types, refer to "See also". Example The following example shows how the instruction works: 1HWZRUN 1HWZRUN 7DJ,QB 7LPHUB 6( 7DJ,QB1XPEHU 7LPHUB 7DJ2XW 7DJ,QB 7LPHUB 5 1HWZRUN The timer "Timer_1" is started when the signal state of the operand "TagIn_1" changes from "0" to "1". The timer expires with the time value of the operand "TagIn_Number" without being affected by a negative edge in the RLO. As long as the timer is running, the operand "TagOut" has the signal state "1". If the signal state of the operand "TagIn_1" changes from "0" to "1" before the timer expires, the timer is restarted. 1798 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References See also Overview of the valid data types (Page 1204) ---( SD ): Start on-delay timer Description The "Start on-delay timer" instruction starts a programmed timer when a change from "0" to "1" (positive signal edge) is detected in the result of logic operation (RLO). The timer runs for the specified duration as long as the RLO is "1". If the timer expires and the RLO still has the signal state "1", the query of the timer status for "1" returns the signal state "1". If the RLO changes from "1" to "0" while the timer is running, the timer is stopped. In this case, the querying of the timer status for "1" returns the signal state "0". The duration is made up internally of a time value and a time base. When the instruction is started, the programmed time value is counted down towards zero. The time base indicates the time period with which the time value is changed. The "Start on-delay timer" instruction requires a preceding logic operation for edge evaluation and can only be placed at the right side of the network. Note In the time cell, the operating system reduces the time value in an interval specified by the time base by one unit until the value equals "0". The decrementation is performed asynchronously to the user program. The resulting timer is therefore at maximum up to one time interval shorter than the desired time base. You can find an example of how a time cell can be formed under: See also "L: Load timer value". Parameter The following table shows the parameters of the "Start on-delay timer" instruction: Parameter Declaration Data type Memory area Description <Time duration> Input S5TIME, WORD I, Q, M, D, L or constant Duration with which the timer expires. <Timer> InOut/Input TIMER T Timer which is started. The number of timers depends on the CPU. For additional information on valid data types, refer to "See also". WinCC Basic V13.0 System Manual, 02/2014 1799 Programming the PLC 9.7 References Example The following example shows how the instruction works: 1HWZRUN 1HWZRUN 7DJ,QB 7LPHUB 6' 7DJ,QB1XPEHU 7LPHUB 7DJ2XW 7DJ,QB 7LPHUB 5 1HWZRUN The timer "Timer_1" is started when the signal state of the operand "TagIn_1" changes from "0" to "1". The timer expires with the time value of the operand "TagIn_Number". If the timer expires and the RLO has the signal state "1", the operand "TagOut" is set to "1". If the signal state of the operand "TagIn_1" changes from "1" to "0" before the timer expires, the timer is stopped. If the signal state of the operand "TagIn_2" is "1", the timer "Timer_1" is reset, which stops the timer and sets the current time value to "0". See also Overview of the valid data types (Page 1204) ---( SS ): Start retentive on-delay timer Description The "Start retentive on-delay timer" instruction starts a programmed timer when a change from "0" to "1" (positive signal edge) is detected in the result of logic operation (RLO). The timer expires with the specified duration, even if the RLO changes to the signal state "0". When the timer expires, the querying of the timer status for "1" returns the signal state "1". After expiry of the timer, the timer can only be restarted if it is explicitly reset. The duration is made up internally of a time value and a time base. When the instruction is started, the programmed time value is counted down towards zero. The time base indicates the time period with which the time value is changed. The "Start retentive on-delay timer" instruction requires a preceding logic operation for edge evaluation and can only be placed at the right side of the network. Note In the time cell, the operating system reduces the time value in an interval specified by the time base by one unit until the value equals "0". The decrementation is performed asynchronously to the user program. The resulting timer is therefore at maximum up to one time interval shorter than the desired time base. 1800 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References You can find an example of how a time cell can be formed under: See also "L: Load timer value". Parameters The following table shows the parameters of the "Start retentive on-delay timer" instruction: Parameter Declaration Data type Memory area Description <Time duration> Input S5TIME, WORD I, Q, M, D, L or constant Duration with which the timer expires. <Timer> InOut/Input TIMER T Timer which is started. The number of timers depends on the CPU. For additional information on valid data types, refer to "See also". Example The following example shows how the instruction works: 1HWZRUN 1HWZRUN 7DJ,QB 7LPHUB 66 7DJ,QB1XPEHU 7LPHUB 7DJ2XW 7DJ,QB 7LPHUB 5 1HWZRUN The timer "Timer_1" is started when the signal state of the operand "TagIn_1" changes from "0" to "1". The timer expires with the time value of the operand "TagIn_Number". When the timer expires, the operand "TagOut" is set to "1". If the signal state of the operand "TagIn_1" changes from "0" to "1" while the timer is running, the timer is restarted. If the signal state of the operand "TagIn_2" is "1", the timer "Timer_1" is reset, which stops the timer and sets the current time value to "0". See also Overview of the valid data types (Page 1204) WinCC Basic V13.0 System Manual, 02/2014 1801 Programming the PLC 9.7 References ---( SF ): Start off-delay timer Description The "Start off-delay timer" instruction starts a programmed timer when a change from "1" to "0" (negative signal edge) is detected in the result of logic operation (RLO). The timer expires with the specified duration. As long as the timer is running, the querying of the timer status for "1" returns the signal state "1". If the RLO changes from "0" to "1" while the timer is running, the timer is reset. The timer is always restarted when the RLO changes from "1" to "0". The duration is made up internally of a time value and a time base. When the instruction is started, the programmed time value is counted down towards zero. The time base indicates the time period with which the time value is changed. The "Start off-delay timer" instruction requires a preceding logic operation for edge evaluation and can only be placed at the right side of the network. Note In the time cell, the operating system reduces the time value in an interval specified by the time base by one unit until the value equals "0". The decrementation is performed asynchronously to the user program. The resulting timer is therefore at maximum up to one time interval shorter than the desired time base. You can find an example of how a time cell can be formed under: See also "L: Load timer value". Parameter The following table shows the parameters of the "Start off-delay timer" instruction: Parameter Declaration Data type Memory area Description <Time duration> Input S5TIME, WORD I, Q, M, D, L or constant Duration with which the timer expires. <Timer> InOut/Input TIMER T Timer which is started. The number of timers depends on the CPU. For additional information on valid data types, refer to "See also". 1802 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Example The following example shows how the instruction works: 1HWZRUN 1HWZRUN 7DJ,QB 7LPHUB 6) 7DJ,QB1XPEHU 7LPHUB 7DJ2XW 7DJ,QB 7LPHUB 5 1HWZRUN The timer "Timer_1" is started when the signal state of the operand "TagIn_1" changes from "1" to "0". The timer expires with the time value of the operand "TagIn_Number". As long as the timer is running, the operand "TagOut" is set to "1". If the signal state of the operand "TagIn_1" changes from "1" to "0" while the timer is running, the timer is restarted. If the signal state of the operand "TagIn_2" is "1", the timer "Timer_1" is reset, which stops the timer and sets the current time value to "0". See also Overview of the valid data types (Page 1204) Counter operations IEC Counters CTU: Count up Description You can use the "Count up" instruction to increment the value at output CV. When the signal state at the CU input changes from "0" to "1" (positive signal edge), the instruction is executed and the current counter value at the CV output is incremented by one. When the instruction executes for the first time, the current counter value at the CV output is set to zero. The counter is incremented each time a positive signal edge is detected, until it reaches the high limit for the specified data type at output CV. When the high limit is reached, the signal state at the CU input no longer has an effect on the instruction. You can scan the counter status at the Q output. The signal state at the Q output is determined by the PV parameter. If the current counter value is greater than or equal to the value of the PV parameter, the Q output is set to signal state "1". In all other cases, the Q output has signal state "0". WinCC Basic V13.0 System Manual, 02/2014 1803 Programming the PLC 9.7 References The value at the CV output is reset to zero when the signal state at input R changes to "1". As long as the R input has the signal state "1", the signal state at the CU input has no effect on the instruction. Note Only use a counter at a single point in the program to avoid the risk of counting errors. Each call of the "Count up" instruction must be assigned to an IEC counter in which the instruction data is stored. An IEC counter is a structure with one of the following data types: For S7-1200 CPU Data block of system data type IEC_<Counter> (Shared DB) Local tag IEC_SCOUNTER / IEC_USCOUNTER CTU_SINT / CTU_USINT IEC_COUNTER / IEC_UCOUNTER CTU_INT / CTU_UINT IEC_DCOUNTER / IEC_UDCOUNTER CTU_DINT / CTU_UDINT IEC_SCOUNTER / IEC_USCOUNTER IEC_COUNTER / IEC_UCOUNTER IEC_DCOUNTER / IEC_UDCOUNTER For S7-1500 CPU Data block of system data type IEC_<Counter> (Shared DB) Local tag IEC_SCOUNTER / IEC_USCOUNTER CTU_SINT / CTU_USINT IEC_COUNTER / IEC_UCOUNTER CTU_INT / CTU_UINT IEC_DCOUNTER / IEC_UDCOUNTER CTU_DINT / CTU_UDINT IEC_LCOUNTER / IEC_ULCOUNTER CTU_LINT / CTU_ULINT IEC_SCOUNTER / IEC_USCOUNTER IEC_COUNTER / IEC_UCOUNTER IEC_DCOUNTER / IEC_UDCOUNTER IEC_LCOUNTER / IEC_ULCOUNTER You can declare an IEC counter as follows: Declaration of a data block of system data type IEC_<Counter> (for example, "MyIEC_COUNTER") Declaration as a local tag of the type CTU_<Data type> or IEC_<Counter> in the "Static" section of a block (for example #MyIEC_COUNTER) When you insert the instruction in the program, the "Call options" dialog opens in which you can specify whether the IEC counter is stored in its own data block (single instance) or as a local tag (multi-instance) in the block interface. If you create a separate data block, you will find it in the project tree in the "Program resources" folder under "Program blocks > System blocks". For additional information on this topic, refer to "See also". 1804 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References If you create the IEC counter in a separate data block (single instance), the instance data block is created by default with "optimized block access" and the individual tags defined as retentive. For additional information on setting retentivity in a instance data block, refer to "See also". If you create the IEC counter as local tag (multi-instance) in a function block with "optimized block access", this is defined as retentive in the block interface. The execution of the "Count up" instruction requires a preceding logic operation. It can be placed within or at the end of the network. Parameters The following table lists the parameters of the "Count up" instruction: Parameter Declaration Data type Memory area S7-1200 S7-1500 I, Q, M, D, L or constant Description CU Input BOOL I, Q, M, D, L or constant Count input R Input BOOL I, Q, M, D, L, I, Q, M, T, C, D, Reset input P or constant L, P or constant PV Input Integers I, Q, M, D, L, I, Q, M, D, L, P P or constant or constant Q Output BOOL I, Q, M, D, L I, Q, M, D, L Counter status CV Output Integers, CHAR, DATE I, Q, M, D, L, P I, Q, M, D, L, P Current counter value Value at which the output Q is set. You can select the data type of the instruction from the "<???>" drop-down list of the instruction box. For additional information on valid data types, refer to "See also". Example The following example shows how the instruction works: &78B'% &78 7DJ,QB 7DJ,QB 7DJB39 ,17 &8 4 5 &9 7DJ2XW 7DJB&9 39 When the signal state of the "TagIn_1" operand changes from "0" to "1", the "Count up" instruction executes and the current counter value of the "Tag_CV" operand is incremented by one. With each additional positive signal edge, the counter value is incremented until the high limit of the data type (INT = 32767) is reached. The value of the PV parameter is adopted as the limit for determining the "TagOut" output. The "TagOut" output has signal state "1" as long as the current counter value is greater than WinCC Basic V13.0 System Manual, 02/2014 1805 Programming the PLC 9.7 References or equal to the value of the "Tag_PV" operand. In all other cases, the "TagOut" output has signal state "0". See also Overview of the valid data types (Page 1204) Setting the retentivity of local tags (Page 1391) Setting retentivity in an instance data block (Page 1536) CTD: Count down Description You can use the "Count down" instruction to decrement the value at output CV. When the signal state at the CD input changes from "0" to "1" (positive signal edge), the instruction is executed and the current counter value at the CV output is decremented by one. When the instruction executes the first time, the counter value of the CV parameter is set to the value of the PV parameter. Each time a positive signal edge is detected, the counter value is decremented until it reaches the low limit of the specified data type. When the low limit is reached, the signal state at the CD input no longer has an effect on the instruction. You can scan the counter status at the Q output. If the current counter value is less than or equal to zero, the Q output is set to signal state "1". In all other cases, the Q output has signal state "0". The value at the CV output is set to the value of the PV parameter when the signal state at the LD input changes to "1". As long as the LD input has the signal state "1", the signal state at the CD input has no effect on the instruction. Note Only use a counter at a single point in the program to avoid the risk of counting errors. Each call of the "Count down" instruction must be assigned an IEC counter in which the instruction data is stored. An IEC counter is a structure with one of the following data types: For S7-1200 CPU Data block of system data type IEC_<Counter> (Shared DB) Local tag IEC_SCOUNTER / IEC_USCOUNTER CTD_SINT / CTD_USINT IEC_COUNTER / IEC_UCOUNTER CTD_INT / CTD_UINT IEC_DCOUNTER / IEC_UDCOUNTER CTD_DINT / CTD_UDINT IEC_SCOUNTER / IEC_USCOUNTER IEC_COUNTER / IEC_UCOUNTER IEC_DCOUNTER / IEC_UDCOUNTER 1806 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References For S7-1500 CPU Data block of system data type IEC_<Counter> (Shared DB) Local tag IEC_SCOUNTER / IEC_USCOUNTER CTD_SINT / CTD_USINT IEC_COUNTER / IEC_UCOUNTER CTD_INT / CTD_UINT IEC_DCOUNTER / IEC_UDCOUNTER CTD_DINT / CTD_UDINT IEC_LCOUNTER / IEC_ULCOUNTER CTD_LINT / CTD_ULINT IEC_SCOUNTER / IEC_USCOUNTER IEC_COUNTER / IEC_UCOUNTER IEC_DCOUNTER / IEC_UDCOUNTER IEC_LCOUNTER / IEC_ULCOUNTER You can declare an IEC counter as follows: Declaration of a data block of system data type IEC_<Counter> (for example, "MyIEC_COUNTER") Declaration as a local tag of the type CTD_<Data type> or IEC_<Counter> in the "Static" section of a block (for example #MyIEC_COUNTER) When you insert the instruction in the program, the "Call options" dialog opens in which you can specify whether the IEC counter is stored in its own data block (single instance) or as a local tag (multi-instance) in the block interface. If you create a separate data block, you will find it in the project tree in the "Program resources" folder under "Program blocks > System blocks". For additional information on this topic, refer to "See also". If you create the IEC counter in a separate data block (single instance), the instance data block is created by default with "optimized block access" and the individual tags defined as retentive. For additional information on setting retentivity in a instance data block, refer to "See also". If you create the IEC counter as local tag (multi-instance) in a function block with "optimized block access", this is defined as retentive in the block interface. The execution of the "Count down" instruction requires a preceding logic operation. It can be placed within or at the end of the network. Parameters The following table lists the parameters of the "Count down" instruction: Parameter WinCC Basic V13.0 System Manual, 02/2014 Declaration Data type Memory area S7-1200 S7-1500 I, Q, M, D, L or constant Description CD Input BOOL I, Q, M, D, L or constant Count input LD Input BOOL I, Q, M, D, L, I, Q, M, T, C, D, Load input P or constant L, P or constant PV Input Integers I, Q, M, D, L, I, Q, M, D, L, P P or constant or constant Value at which the output Q is set. 1807 Programming the PLC 9.7 References Parameter Declaration Data type Memory area S7-1200 S7-1500 Description Q Output BOOL I, Q, M, D, L I, Q, M, D, L Counter status CV Output Integers, CHAR, DATE I, Q, M, D, L, P I, Q, M, D, L, P Current counter value You can select the data type of the instruction from the "<???>" drop-down list of the instruction box. For additional information on valid data types, refer to "See also". Example The following example shows how the instruction works: &7'B'% &7' 7DJ,QB 7DJ,QB 7DJB39 ,17 &' 4 /' &9 7DJ2XW 7DJB&9 39 When the signal state of the "TagIn_1" operand changes from "0" to "1", the "Count down" instruction executes and the value at the "Tag_CV" output is decremented by one. With each additional positive signal edge, the counter value is decremented until the low limit of the specified data type (INT = -32768) is reached. The "TagOut" output has signal state "1" as long as the current counter value is less than or equal to zero. In all other cases, the "TagOut" output has signal state "0". See also Overview of the valid data types (Page 1204) Setting retentivity in an instance data block (Page 1536) Setting the retentivity of local tags (Page 1391) CTUD: Count up and down Description You can use the "Count up and down" instruction to increment and decrement the counter value at the CV output. If the signal state at the CU input changes from "0" to "1" (positive signal edge), the current counter value is incremented by one and stored at the CV output. If the signal state at the CD input changes from "0" to "1" (positive signal edge), the counter value at the CV output is decremented by one. If there is a positive signal edge at the CU and CD inputs in one program cycle, the current counter value at the CV output remains unchanged. 1808 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References The counter value can be incremented until it reaches the high limit of the data type specified at the CV output. When the high limit is reached, the counter value is no longer incremented on a positive signal edge. When the low limit of the specified data type is reached, the counter value is not decremented any further. When the signal state at the LD input changes to "1", the counter value at the CV output is set to the value of the PV parameter. As long as the LD input has the signal state "1", the signal state at the CU and CD inputs has no effect on the instruction. The counter value is set to zero when the signal state at the R input changes to "1". As long as the R input has the signal state "1", a change in the signal state of the CU, CD and LD inputs has no effect on the "Count up and down" instruction. You can scan the current status of the up counter at the QU output. If the current counter value is greater than or equal to the value of the PV parameter, the QU output is set to signal state "1". In all other cases, the QU output has signal state "0". You can scan the current status of the down counter at the QD output. If the current counter value is less than or equal to zero, the QD output is set to signal state "1". In all other cases, the QD output has signal state "0". Note Only use a counter at a single point in the program to avoid the risk of counting errors. Each call of the "Count up and down" instruction must be assigned an IEC counter in which the instruction data is stored. An IEC counter is a structure with one of the following data types: For S7-1200 CPU Data block of system data type IEC_<Counter> (Shared DB) Local tag IEC_SCOUNTER / IEC_USCOUNTER CTUD_SINT / CTUD_USINT IEC_COUNTER / IEC_UCOUNTER CTUD_INT / CTUD_UINT IEC_DCOUNTER / IEC_UDCOUNTER CTUD_DINT / CTUD_UDINT IEC_SCOUNTER / IEC_USCOUNTER IEC_COUNTER / IEC_UCOUNTER IEC_DCOUNTER / IEC_UDCOUNTER WinCC Basic V13.0 System Manual, 02/2014 1809 Programming the PLC 9.7 References For S7-1500 CPU Data block of system data type IEC_<Counter> (Shared DB) Local tag IEC_SCOUNTER / IEC_USCOUNTER CTUD_SINT / CTUD_USINT IEC_COUNTER / IEC_UCOUNTER CTUD_INT / CTUD_UINT IEC_DCOUNTER / IEC_UDCOUNTER CTUD_DINT / CTUD_UDINT IEC_LCOUNTER / IEC_ULCOUNTER CTUD_LINT / CTUD_ULINT IEC_SCOUNTER / IEC_USCOUNTER IEC_COUNTER / IEC_UCOUNTER IEC_DCOUNTER / IEC_UDCOUNTER IEC_LCOUNTER / IEC_ULCOUNTER You can declare an IEC counter as follows: Declaration of a data block of system data type IEC_<Counter> (for example, "MyIEC_COUNTER") Declaration as a local tag of the type CTUD_<Data type> or IEC_<Counter> in the "Static" section of a block (for example #MyIEC_COUNTER) When you insert the instruction in the program, the "Call options" dialog opens in which you can specify whether the IEC counter is stored in its own data block (single instance) or as a local tag (multi-instance) in the block interface. If you create a separate data block, you will find it in the project tree in the "Program resources" folder under "Program blocks > System blocks". For additional information on this topic, refer to "See also". If you create the IEC counter in a separate data block (single instance), the instance data block is created by default with "optimized block access" and the individual tags defined as retentive. For additional information on setting retentivity in a instance data block, refer to "See also". If you create the IEC counter as local tag (multi-instance) in a function block with "optimized block access", this is defined as retentive in the block interface. The execution of the "Count up and down" instruction requires a preceding logic operation. It can be placed within or at the end of the network. Parameters The following table lists the parameters of the "Count up and down" instruction: Parameter 1810 Declaration Data type Memory area S7-1200 S7-1500 Description CU Input BOOL I, Q, M, D, L or constant I, Q, M, D, L or constant Count up input CD Input BOOL I, Q, M, D, L or constant I, Q, M, D, L or constant Count down input R Input BOOL I, Q, M, D, L, I, Q, M, T, C, D, Reset input P or constant L, P or constant LD Input BOOL I, Q, M, D, L, I, Q, M, T, C, D, Load input P or constant L, P or constant WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameter Declaration Data type Memory area S7-1200 Description S7-1500 PV Input Integers I, Q, M, D, L, I, Q, M, D, L, P P or constant or constant Value at which the output QU is set. QU Output BOOL I, Q, M, D, L I, Q, M, D, L Status of the up counter QD Output BOOL I, Q, M, D, L I, Q, M, D, L Status of the down counter CV Output Integers, CHAR, DATE I, Q, M, D, L, P I, Q, M, D, L, P Current counter value You can select the data type of the instruction from the "<???>" drop-down list of the instruction box. For additional information on valid data types, refer to "See also". Example The following example shows how the instruction works: &78'B'% &78' ,17 7DJ,QB 7DJ2XW &8 48 &' 4' 7DJ2XWB4' 5 &9 7DJB&9 7DJ,QB 7DJ,QB 7DJ,QB /' 7DJB39 39 If the signal state at the "TagIn_1" or "TagIn_2" input changes from "0" to "1" (positive signal edge), the "Count up and down" instruction is executed. When there is a positive signal edge at the "TagIn_1" input, the current counter value is incremented by one and stored at the "Tag_CV" output. When there is a positive signal edge at the "TagIn_2" input, the counter value is decremented by one and stored at the "Tag_CV" output. When there is a positive signal edge at the CU input, the counter value is incremented until it reaches the high limit of 32767. If input CD has a positive signal edge, the counter value is decremented until it reaches the low limit of INT = -32768. The "TagOut" output has signal state "1" as long as the current counter value is greater than or equal to the value at the "Tag_PV" input. In all other cases, the "TagOut" output has signal state "0". The "TagOut_QD" output has signal state "1" as long as the current counter value is less than or equal to zero. In all other cases, the "TagOut_QD" output has signal state "0". WinCC Basic V13.0 System Manual, 02/2014 1811 Programming the PLC 9.7 References See also Overview of the valid data types (Page 1204) Setting retentivity in an instance data block (Page 1536) Setting the retentivity of local tags (Page 1391) SIMATIC Counters S_CUD: Assign parameters and count up / down Description You can use the "Assign parameters and count up / down" instruction to increment or decrement the value of a counter. If the signal state at the CU input changes from "0" to "1" (positive signal edge), the current counter value is incremented by one. If the signal state at the CD input changes from "0" to "1" (positive signal edge), the counter value is decremented by one. The current counter value is output as a hexadecimal value at output CV and BCDcoded at output CV_BCD. If there is a positive signal edge at the CU and CD inputs in one program cycle, the counter value remains unchanged. The counter value can be incremented until the high limit of "999" is reached. When the high limit value is reached, the counter value is no longer incremented on a positive signal edge. When the low limit "0" is reached, the counter value is not decremented any further. When the signal state at input S changes from "0" to "1", the counter value is set to the value of the PV parameter. If the counter is set and if RLO is "1" at the inputs CU and CD, the counter counts accordingly in the next scan cycle, even if no change in the signal edge was detected. The counter value is set to zero when the signal state at the R input changes to "1". As long as the R input has the signal state "1", processing of the signal state of the CU, CD and S inputs has no effect on the counter value. The signal state at output Q is "1" if the counter value is greater than zero. If the counter value is equal to zero, output Q has the signal state "0". Note Only use a counter at a single point in the program to avoid the risk of counting errors. The "Assign parameters and count up / down" instruction requires a preceding logic operation for edge evaluation and can be placed within or at the end of the network. 1812 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameters The following table shows the parameters of the "Assign parameters and count up / down" instruction: Parameter Declaration Data type Memory area Description <Counter> InOut/Input COUNTER C Counter of the instruction The number of counters depends on the CPU. CU Input BOOL I, Q, M, D, L Count up input CD Input BOOL I, Q, M, D, L, T, C or constant Count down input S Input BOOL I, Q, M, D, L, T, C or constant Input for presetting counter PV Input WORD I, Q, M, D, L or constant Preset counter value (C#0 to C#999) R Input BOOL I, Q, M, D, L, T, C or constant Reset input BI Output WORD, S5TIME, DATE I, Q, M, D, L Current counter value (hexadecimal) CV_BCD Output WORD, S5TIME, DATE I, Q, M, D, L Current counter value (BCD format) Q Output BOOL I, Q, M, D, L Status of the counter For additional information on valid data types, refer to "See also". Example The following example shows how the instruction works: &RXQWHUB 6B&8' 7DJ,QB &8 7DJ,QB 7DJ,QB 7DJ3UHVHW9DOXH 7DJ2XW 4 &' 6 39 &9 7DJ9DOXHB &9B%&' 7DJ9DOXHB 7DJ,QB 5 If the signal state at the "TagIn_1"" or "TagIn_2" input changes from "0" to "1" (positive signal edge), the "Assign parameters and count up / down" instruction is executed. When there is a WinCC Basic V13.0 System Manual, 02/2014 1813 Programming the PLC 9.7 References positive signal edge at the "TagIn_1" input and the current counter value is less than "999", the counter value is incremented by one. When there is a positive signal edge at the "TagIn_2" input and the current counter value is greater than "0", the counter value is decremented by one. When the signal state at input "TagIn_3" changes from "0" to "1", the counter value is set to the value of the operand "TagPresetValue". The counter value is reset to "0" when the "TagIn_4" operand has signal state "1". The current counter value is saved as a hexadecimal value in the operand "TagValue_1" and BCD-coded in the operand "TagValue_2". The "TagOut" output has the signal state "1" as long as the current counter value is not equal to "0". See also Overview of the valid data types (Page 1204) S_CU: Assign parameters and count up Description You can use the "Assign parameters and count up" instruction to increment the value of a counter. If the signal state at the CU input changes from "0" to "1" (positive signal edge), the current counter value is incremented by one. The current counter value is output as a hexadecimal value at output CV and BCD-coded at output CV_BCD. The counter value can be incremented until the limit of "999" is reached. When the limit is reached, the counter value is no longer incremented on a positive signal edge. When the signal state at input S changes from "0" to "1", the counter value is set to the value of the PV parameter. If the counter is set and if RLO at input CU is "1", the counter will count accordingly in the next scan cycle, even when no change has been detected in the signal edge. The counter value is set to zero when the signal state at the R input changes to "1". As long as the R input has the signal state "1", processing of the signal state of the CU and S inputs has no effect on the counter value. The signal state at output Q is "1" if the counter value is greater than zero. If the counter value is equal to zero, output Q has the signal state "0". Note Only use a counter at a single point in the program to avoid the risk of counting errors. The "Assign parameters and count up" instruction requires a preceding logic operation for edge evaluation and can be placed within or at the end of the network. 1814 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameter The following table shows the parameters of the "Assign parameters and count up" instruction: Parameter Declaration Data type Memory area Description <Counter> InOut/Input COUNTER C Counter of the instruction The number of counters depends on the CPU. CU Input BOOL I, Q, M, D, L Count up input S Input BOOL I, Q, M, D, L, T, C or constant Input for presetting counter PV Input WORD I, Q, M, D, L or constant Preset counter value (C#0 to C#999) R Input BOOL I, Q, M, D, L, T, C or constant Reset input CV Output WORD, S5TIME, DATE I, Q, M, D, L Current counter value (hexadecimal) CV_BCD Output WORD, S5TIME, DATE I, Q, M, D, L Current counter value (BCD format) Q Output BOOL I, Q, M, D, L Status of the counter For additional information on valid data types, refer to "See also". Example The following example shows how the instruction works: &RXQWHUB 6B&8 7DJ,QB &8 7DJ2XW 4 7DJ,QB 6 7DJ3UHVHW9DOXH 7DJ,QB 39 5 &9 7DJ9DOXHB &9B%&' 7DJ9DOXHB When the signal state at the "TagIn_1" input changes from "0" to "1" (positive signal edge) and the current counter value is less than "999", the counter value is incremented by one. When the signal state at input "TagIn_2" changes from "0" to "1", the counter value is set to the value of the operand "TagPresetValue". The counter value is reset to "0" when the "TagIn_3" operand has signal state "1". WinCC Basic V13.0 System Manual, 02/2014 1815 Programming the PLC 9.7 References The current counter value is saved as a hexadecimal value in the operand "TagValue_1" and BCD-coded in the operand "TagValue_2". The "TagOut" output has the signal state "1" as long as the current counter value is not equal to "0". See also Overview of the valid data types (Page 1204) S_CD: Assign parameters and count down Description You can use the "Assign parameters and count down" instruction to decrement the value of a counter. If the signal state at the CD input changes from "0" to "1" (positive signal edge), the counter value is decremented by one. The current counter value is output as a hexadecimal value at output CV and BCD-coded at output CV_BCD. The counter value is decremented until the low limit of "0" is reached. When the low limit is reached, the counter value is no longer decremented on a positive signal edge. When the signal state at input S changes from "0" to "1", the counter value is set to the value of the PV parameter. If the counter is set and if RLO at input CD is "1", the counter will count accordingly in the next scan cycle, even when no change has been detected in the signal edge. The counter value is set to zero when the signal state at the R input changes to "1". As long as the R input has the signal state "1", processing of the signal state of the CD and S inputs has no effect on the counter value. The signal state at output Q is "1" if the counter value is greater than zero. If the counter value is equal to zero, output Q has the signal state "0". Note Only use a counter at a single point in the program to avoid the risk of counting errors. The "Assign parameters and count down" instruction requires a preceding logic operation for edge evaluation and can be placed within or at the end of the network. 1816 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameter The following table shows the parameters of the "Assign parameters and count down" instruction: Parameter Declaration Data type Memory area Description <Counter> InOut/Input COUNTER C Counter of the instruction The number of counters depends on the CPU. CD Input BOOL I, Q, M, D, L or constant Count down input S Input BOOL I, Q, M, D, L, T, C or constant Input for presetting counter PV Input WORD I, Q, M, D, L or constant Preset counter value (C#0 to C#999) R Input BOOL I, Q, M, D, L, T, C or constant Reset input CV Output WORD, S5TIME, DATE I, Q, M, D, L Current counter value (hexadecimal) CV_BCD Output WORD, S5TIME, DATE I, Q, M, D, L Current counter value (BCD format) Q Output BOOL I, Q, M, D, L Status of the counter For additional information on valid data types, refer to "See also". Example The following example shows how the instruction works: &RXQWHUB 6B&' 7DJ,QB &' 7DJ2XW 4 7DJ,QB 6 7DJ3UHVHW9DOXH 7DJ,QB 39 5 &9 7DJ9DOXHB &9B%&' 7DJ9DOXHB When the signal state at the "TagIn_1" input changes from "0" to "1" (positive signal edge) and the current counter value is greater than "0", the counter value is decremented by one. When the signal state at input "TagIn_2" changes from "0" to "1", the counter value is set to the value of the operand "TagPresetValue". The counter value is reset to "0" when the "TagIn_3" operand has signal state "1". WinCC Basic V13.0 System Manual, 02/2014 1817 Programming the PLC 9.7 References The current counter value is saved as a hexadecimal value in the operand "TagValue_1" and BCD-coded in the operand "TagValue_2". The "TagOut" output has the signal state "1" as long as the current counter value is not equal to "0". See also Overview of the valid data types (Page 1204) ---( SC ): Set counter value Description You can use the "Set counter value" instruction to set the value of a counter. The instruction is executed when the result of logic operation (RLO) at the input changes from "0" to "1". When the instruction is executed, the counter is set to the specified counter value. The "Set counter value" instruction needs a preceding logic operation for the edge evaluation and can only be placed on the right edge of the network. Parameter The following table lists the parameters of the "Set counter value" instruction: Parameter Declaration Data type Memory area Description <Count value> Input WORD I, Q, M, D, L or constant Value with which the counter is preset in the BCD format. (C#0 to C#999) <Counter> InOut/Input COUNTER C Counter that is preset. For additional information on valid data types, refer to "See also". Example The following example shows how the instruction works: 7DJ,Q &RXQWHUB 6& & the counter "Counter_1" starts with the value "100" when the signal state of the "TagIn" operand changes from "0" to "1". 1818 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References See also Overview of the valid data types (Page 1204) ---( CU ): Count up Description With the "Count up" instruction you can increment the value of the specified counter by one if there is a positive signal edge in the result of logic operation (RLO). The counter value can be incremented until the limit of "999" is reached. When the limit is reached, the counter value is no longer incremented on a positive signal edge. The "Count up" instruction requires a preceding logic operation for edge evaluation and can only be placed at the right side of the network. Parameter The following table shows the parameters of the "Count up" instruction: Parameter Declaration Data type Memory area Description <Counter> InOut/Input COUNTER C Counter whose value is incremented. For additional information on valid data types, refer to "See also". Example The following example shows how the instruction works: 1HWZRUN 7DJ,QB &RXQWHUB 6& & 1HWZRUN 7DJ,QB &RXQWHUB &8 1HWZRUN 7DJ,QB &RXQWHUB 5 When the signal state of the "TagIn_1" operand changes from "0" to "1" (positive signal edge), the counter "Counter_1" is preset with the value "100". The value of the counter "Counter_1" is incremented by one when the signal state of the operand "TagIn_2" changes from "0" to "1". When the operand "TagIn_3" has the signal state "1", the value of the counter "Counter_1" is reset to "0". WinCC Basic V13.0 System Manual, 02/2014 1819 Programming the PLC 9.7 References See also Overview of the valid data types (Page 1204) ---( CD ): Count down Description With the "Count down" instruction you can increment the value of the specified counter by one if there is a positive signal edge in the result of logic operation (RLO). The counter value can be decremented until the limit of "0" is reached. When the limit is reached, the counter value is no longer changed on a positive signal edge. The "Count down" instruction requires a preceding logic operation for edge evaluation and can only be placed at the right side of the network. Parameter The following table shows the parameters of the "Count down" instruction: Parameter Declaration Data type Memory area Description <Counter> InOut/Input COUNTER C Counter whose value is decremented. For additional information on valid data types, refer to "See also". Example The following example shows how the instruction works: 1HWZRUN 7DJ,QB &RXQWHUB 6& & 1HWZRUN 7DJ,QB &RXQWHUB &' 1HWZRUN 7DJ,QB &RXQWHUB 5 When the signal state of the "TagIn_1" operand changes from "0" to "1" (positive signal edge), the counter "Counter_1" is preset with the value "100". The value of the counter "Counter_1" is decremented by one when the signal state of the operand "TagIn_2" changes from "0" to "1". When the operand "TagIn_3" has the signal state "1", the value of the counter "Counter_1" is reset to "0". 1820 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References See also Overview of the valid data types (Page 1204) Comparator operations CMP ==: Equal Description You can use the "Equal" instruction to determine if a first comparison value (<Operand1>) is equal to a second comparison value (<Operand2>). If the condition of the comparison is fulfilled, the instruction returns the result of logic operation (RLO) "1". If the comparison condition is not fulfilled, the instruction returns RLO "0". The RLO of the instruction is logically combined with the RLO of the entire rung as follows: By AND, when the comparison instruction is connected in series. By OR, when the comparison instruction is connected in parallel. Specify the first comparison value (<Operand1>) at the operand placeholder above the instruction. Specify the second comparison value (<Operand2>) at the operand placeholder below the instruction. The individual characters are compared by means of their code (for example, 'a' is greater than 'A') during the comparison of the strings. The comparison is performed from left to right. The first character to be different decides the result of the comparison. The following table lists examples of string comparisons: <Operand1> <Operand2> RLO of the instruction 'AA' 'AA' 1 'Hello World' 'HelloWorld' 0 'AA' 'aa' 0 You can also use the "Equal" instruction to compare individual characters of a string. The number of the character to be compared is specified in square brackets next to the operand name. "MyString[2]", for example, compares the second character of the "MyString" string. If IEC check is enabled, the operands to be compared must be of the same data type. If IEC check is not enabled, the width (length) of the operands must be the same. When floating-point numbers are compared, the operands to be compared must have the same data type regardless of the setting for the IEC Check. Note Comparison of floating-point numbers If you want to compare the data types REAL or LREAL, instead of the instruction "CMP ==: Equal", use the instruction "IN_RANGE: Value within range". WinCC Basic V13.0 System Manual, 02/2014 1821 Programming the PLC 9.7 References Note Comparison of the data type PORT To be able to compare the operands of the PORT data type with the "Equal" instruction, you need to select the WORD data type from the drop-down list of the instructions box. Parameters The following table lists the parameters of the "Equal" instruction: Parameter Declaration Data type S7-1200 S7-1500 Memory area Description <Operand1> Input Bit strings, integers, floating-point numbers, character strings, TIME, DATE, TOD, DTL Bit strings, integers, floating-point numbers, character strings, TIME, LTIME, DATE, TOD, LTOD, DTL, DT, LDT I, Q, M, D, L, P or constant First comparison value <Operand2> Input Bit strings, integers, floating-point numbers, character strings, TIME, DATE, TOD, DTL Bit strings, integers, floating-point numbers, character strings, TIME, LTIME, DATE, TOD, LTOD, DTL, DT, LDT I, Q, M, D, L, P or constant Second value to compare You can select the data type of the instruction from the "<???>" drop-down list of the instruction box. For additional information on valid data types, refer to "See also". Example The following example shows how the instruction works: 7DJ,QB 7DJ,QB 7DJB9DOXH ,17 7DJ2XW 6 7DJB9DOXH The "TagOut" output is set when the following conditions are fulfilled: The operands "TagIn_1" and "TagIn_2" have signal state "1". The condition of the comparison instruction is fulfilled if "Tag_Value1" = "Tag_Value2". 1822 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References See also Overview of the valid data types (Page 1204) CMP <>: Not equal Description You can use the "Not equal" instruction to determine if a first comparison value (<Operand1>) is not equal to a second comparison value (<Operand2>). If the condition of the comparison is fulfilled, the instruction returns the result of logic operation (RLO) "1". If the comparison condition is not fulfilled, the instruction returns RLO "0". The RLO of the instruction is logically combined with the RLO of the entire rung as follows: By AND, when the comparison instruction is connected in series. By OR, when the comparison instruction is connected in parallel. Specify the first comparison value (<Operand1>) at the operand placeholder above the instruction. Specify the second comparison value (<Operand2>) at the operand placeholder below the instruction. The individual characters are compared by means of their code (for example, 'a' is greater than 'A') during the comparison of the strings. The comparison is performed from left to right. The first character to be different decides the result of the comparison. The following table lists examples of string comparisons: <Operand1> <Operand2> RLO of the instruction 'AA' 'aa' 1 'Hello World' 'HelloWorld' 1 'AA' 'AA' 0 You can also use the "Not equal" instruction to compare individual characters of a string. The number of the character to be compared is specified in square brackets next to the operand name. "MyString[2]", for example, compares the second character of the "MyString" string. If IEC check is enabled, the operands to be compared must be of the same data type. If IEC check is not enabled, the width (length) of the operands must be the same. If the floating-point numbers are being compared, the operands to be compared must be of the same data type regardless of the IEC check setting. Note Comparison of the data type PORT To be able to compare the operands of the PORT data type with the "Not equal" instruction, you need to select the WORD data type from the drop-down list of the instructions box. WinCC Basic V13.0 System Manual, 02/2014 1823 Programming the PLC 9.7 References Parameters The following table lists the parameters of the "Not equal" instruction: Parameter Declaration Data type S7-1200 S7-1500 Memory area Description <Operand1> Input Bit strings, integers, floating-point numbers, character strings, TIME, DATE, TOD, DTL Bit strings, integers, floating-point numbers, character strings, TIME, LTIME, DATE, TOD, LTOD, DTL, DT, LDT I, Q, M, D, L, P or constant First comparison value <Operand2> Input Bit strings, integers, floating-point numbers, character strings, TIME, DATE, TOD, DTL Bit strings, integers, floating-point numbers, character strings, TIME, LTIME, DATE, TOD, LTOD, DTL, DT, LDT I, Q, M, D, L, P or constant Second value to compare You can select the data type of the instruction from the "<???>" drop-down list of the instruction box. For additional information on valid data types, refer to "See also". Example The following example shows how the instruction works: 7DJ,QB 7DJ,QB 7DJB9DOXH ! ,17 7DJ2XW 6 7DJB9DOXH The "TagOut" output is set when the following conditions are fulfilled: The operands "TagIn_1" and "TagIn_2" have signal state "1". The condition of the comparison instruction is fulfilled if "Tag_Value1" <> "Tag_Value2". See also Overview of the valid data types (Page 1204) 1824 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References CMP >=: Greater or equal Description You can use the "Greater or equal" instruction to determine if a first comparison value (<Operand1>) is greater than or equal to a second comparison value (<Operand2>). Both values to be compared must be of the same data type. If the condition of the comparison is fulfilled, the instruction returns the result of logic operation (RLO) "1". If the comparison condition is not fulfilled, the instruction returns RLO "0". The RLO of the instruction is logically combined with the RLO of the entire rung as follows: By AND, when the comparison instruction is connected in series. By OR, when the comparison instruction is connected in parallel. Specify the first comparison value (<Operand1>) at the operand placeholder above the instruction. Specify the second comparison value (<Operand2>) at the operand placeholder below the instruction. The individual characters are compared by means of their code (for example, 'a' is greater than 'A') during the comparison of the strings. The comparison is performed from left to right. The first character to be different decides the result of the comparison. If the left part of the longer string is identical to the shorter string, the longer string is considered greater. The following table lists examples of string comparisons: <Operand1> <Operand2> RLO of the instruction 'BB' 'AA' 1 'AAA' 'AA' 1 'Hello World' 'Hello World' 1 'Hello World' 'HelloWorld' 0 'AA' 'aa' 0 'AAA' 'a' 0 You can also use the "Greater or equal" instruction to compare individual characters of a string. The number of the character to be compared is specified in square brackets next to the operand name. "MyString[2]", for example, compares the second character of the "MyString" string. When time values are compared, the RLO of the instruction is "1" if the point of time at <Operand1> is greater (more recent) than or equal to the point of time at <Operand2>. WinCC Basic V13.0 System Manual, 02/2014 1825 Programming the PLC 9.7 References Parameters The following table lists the parameters of the "Greater or equal" instruction: Parameters Declaration Data type S7-1200 S7-1500 Memory area Description <Operand1> Input Integers, floating-point numbers, character strings, TIME, DATE, TOD, DTL Integers, floating-point numbers, character strings, TIME, LTIME, DATE, TOD, LTOD, DTL, DT, LDT I, Q, M, D, L, P or constant First comparison value <Operand2> Input Integers, floating-point numbers, character strings, TIME, DATE, TOD, DTL Integers, floating-point numbers, character strings, TIME, LTIME, DATE, TOD, LTOD, DTL, DT, LDT I, Q, M, D, L, P or constant Second value to compare You can select the data type of the instruction from the "<???>" drop-down list of the instruction box. For additional information on valid data types, refer to "See also". Example The following example shows how the instruction works: 7DJ,QB 7DJ,QB 7DJB9DOXH ! ,17 7DJ2XW 6 7DJB9DOXH The "TagOut" output is set when the following conditions are fulfilled: The operands "TagIn_1" and "TagIn_2" have signal state "1". The condition of the comparison instruction is fulfilled if "Tag_Value1" >= "Tag_Value2". See also Overview of the valid data types (Page 1204) Example of detecting the fill level of a storage area (Page 1719) 1826 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References CMP <=: Less or equal Description You can use the "Less or equal" instruction to determine if a first comparison value (<Operand1>) is less than or equal to a second comparison value (<Operand2>). Both values to be compared must be of the same data type. If the condition of the comparison is fulfilled, the instruction returns the result of logic operation (RLO) "1". If the comparison condition is not fulfilled, the instruction returns RLO "0". The RLO of the instruction is logically combined with the RLO of the entire rung as follows: By AND, when the comparison instruction is connected in series. By OR, when the comparison instruction is connected in parallel. Specify the first comparison value (<Operand1>) at the operand placeholder above the instruction. Specify the second comparison value (<Operand2>) at the operand placeholder below the instruction. The individual characters are compared by means of their code (for example, 'a' is greater than 'A') during the comparison of the strings. The comparison is performed from left to right. The first character to be different decides the result of the comparison. If the left part of the longer string is identical to the shorter string, the shorter string is considered smaller. The following table lists examples of string comparisons: <Operand1> <Operand2> RLO of the instruction 'AA' 'aa' 1 'AAA' 'a' 1 'Hello World' 'Hello World' 1 'HelloWorld' 'Hello World' 0 'BB' 'AA' 0 'AAA' 'AA' 0 You can also use the "Less or equal" instruction to compare individual characters of a string. The number of the character to be compared is specified in square brackets next to the operand name. "MyString[2]", for example, compares the second character of the "MyString" string. When time values are compared, the RLO of the instruction is "1" if the point of time at <Operand1> is less (less recent) than or equal to the point of time at <Operand2>. WinCC Basic V13.0 System Manual, 02/2014 1827 Programming the PLC 9.7 References Parameters The following table lists the parameters of the "Less or equal" instruction: Parameters Declaration Data type S7-1200 S7-1500 Memory area Description <Operand1> Input Integers, floating-point numbers, character strings, TIME, DATE, TOD, DTL Integers, floating-point numbers, character strings, TIME, LTIME, DATE, TOD, LTOD, DTL, DT, LDT I, Q, M, D, L, P or constant First comparison value <Operand2> Input Integers, floating-point numbers, character strings, TIME, DATE, TOD, DTL Integers, floating-point numbers, character strings, TIME, LTIME, DATE, TOD, LTOD, DTL, DT, LDT I, Q, M, D, L, P or constant Second value to compare You can select the data type of the instruction from the "<???>" drop-down list of the instruction box. For additional information on valid data types, refer to "See also". Example The following example shows how the instruction works: 7DJ,QB 7DJ,QB 7DJB9DOXH ,17 7DJ2XW 6 7DJB9DOXH The "TagOut" output is set when the following conditions are fulfilled: The operands "TagIn_1" and "TagIn_2" have signal state "1". The condition of the comparison instruction is fulfilled if "Tag_Value1" <= "Tag_Value2". See also Overview of the valid data types (Page 1204) 1828 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References CMP >: Greater than Description You can use the "Greater than" instruction to determine if a first comparison value (<Operand1>) is greater than a second comparison value (<Operand2>). Both values to be compared must be of the same data type. If the condition of the comparison is fulfilled, the instruction returns the result of logic operation (RLO) "1". If the comparison condition is not fulfilled, the instruction returns RLO "0". The RLO of the instruction is logically combined with the RLO of the entire rung as follows: By AND, when the comparison instruction is connected in series. By OR, when the comparison instruction is connected in parallel. Specify the first comparison value (<Operand1>) at the operand placeholder above the instruction. Specify the second comparison value (<Operand2>) at the operand placeholder below the instruction. The individual characters are compared by means of their code (for example, 'a' is greater than 'A') during the comparison of the strings. The comparison is performed from left to right. The first character to be different decides the result of the comparison. If the left part of the longer string is identical to the shorter string, the longer string is considered greater. The following table lists examples of string comparisons: <Operand1> <Operand2> RLO of the instruction 'BB' 'AA' 1 'AAA' 'AA' 1 'AA' 'aa' 0 'AAA' 'a' 0 You can also use the "Greater than" instruction to compare individual characters of a string. The number of the character to be compared is specified in square brackets next to the operand name. "MyString[2]", for example, compares the second character of the "MyString" string. When time values are compared, the RLO of the instruction is "1" if the point of time at <Operand1> is greater (more recent) than the point of time at <Operand2>. WinCC Basic V13.0 System Manual, 02/2014 1829 Programming the PLC 9.7 References Parameters The following table lists the parameters of the "Greater than" instruction: Parameters Declaration Data type S7-1200 S7-1500 Memory area Description <Operand1> Input Integers, floating-point numbers, character strings, TIME, DATE, TOD, DTL Integers, floating-point numbers, character strings, TIME, LTIME, DATE, TOD, LTOD, DTL, DT, LDT I, Q, M, D, L, P or constant First comparison value <Operand2> Input Integers, floating-point numbers, character strings, TIME, DATE, TOD, DTL Integers, floating-point numbers, character strings, TIME, LTIME, DATE, TOD, LTOD, DTL, DT, LDT I, Q, M, D, L, P or constant Second value to compare You can select the data type of the instruction from the "<???>" drop-down list of the instruction box. For additional information on valid data types, refer to "See also". Example The following example shows how the instruction works: 7DJ,QB 7DJ,QB 7DJB9DOXH ! ,17 7DJ2XW 6 7DJB9DOXH The "TagOut" output is set when the following conditions are fulfilled: The operands "TagIn_1" and "TagIn_2" have signal state "1". The condition of the comparison instruction is fulfilled if "Tag_Value1" > "Tag_Value2". See also Overview of the valid data types (Page 1204) 1830 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References CMP <: Less than Description You can use the "Less than" instruction to determine if a first comparison value (<Operand1>) is less than a second comparison value (<Operand2>). Both values to be compared must be of the same data type. If the condition of the comparison is fulfilled, the instruction returns the result of logic operation (RLO) "1". If the comparison condition is not fulfilled, the instruction returns RLO "0". The RLO of the instruction is logically combined with the RLO of the entire rung as follows: By AND, when the comparison instruction is connected in series. By OR, when the comparison instruction is connected in parallel. Specify the first comparison value (<Operand1>) at the operand placeholder above the instruction. Specify the second comparison value (<Operand2>) at the operand placeholder below the instruction. The individual characters are compared by means of their code (for example, 'a' is greater than 'A') during the comparison of the strings. The comparison is performed from left to right. The first character to be different decides the result of the comparison. If the left part of the longer string is identical to the shorter string, the shorter string is considered smaller. The following table lists examples of string comparisons: <Operand1> <Operand2> RLO of the instruction 'AA' 'aa' 1 'AAA' 'a' 1 'BB' 'AA' 0 'AAA' 'AA' 0 You can also use the "Less than" instruction to compare individual characters of a string. The number of the character to be compared is specified in square brackets next to the operand name. "MyString[2]", for example, compares the second character of the "MyString" string. When time values are compared, the RLO of the instruction is "1" if the point of time at <Operand1> is less (less recent) than the point of time at <Operand2>. WinCC Basic V13.0 System Manual, 02/2014 1831 Programming the PLC 9.7 References Parameters The following table lists the parameters of the "Less than" instruction: Parameters Declaration Data type S7-1200 S7-1500 Memory area Description <Operand1> Input Integers, floating-point numbers, character strings, TIME, DATE, TOD, DTL Integers, floating-point numbers, character strings, TIME, LTIME, DATE, TOD, LTOD, DTL, DT, LDT I, Q, M, D, L, P or constant First comparison value <Operand2> Input Integers, floating-point numbers, character strings, TIME, DATE, TOD, DTL Integers, floating-point numbers, character strings, TIME, LTIME, DATE, TOD, LTOD, DTL, DT, LDT I, Q, M, D, L, P or constant Second value to compare You can select the data type of the instruction from the "<???>" drop-down list of the instruction box. For additional information on valid data types, refer to "See also". Example The following example shows how the instruction works: 7DJ,QB 7DJ,QB 7DJB9DOXH ,17 7DJ2XW 6 7DJB9DOXH The "TagOut" output is set when the following conditions are fulfilled: The operands "TagIn_1" and "TagIn_2" have signal state "1". The condition of the comparison instruction is fulfilled if "Tag_Value1" < "Tag_Value2". See also Overview of the valid data types (Page 1204) Example of detecting the fill level of a storage area (Page 1719) 1832 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References IN_RANGE: Value within range Description You can use the "Value within range" instruction to determine if the value at the VAL input is within a specific value range. You specify the limits of the value range with the MIN and MAX inputs. The "Value within range" instruction compares the value at the VAL input with the values of the MIN and MAX inputs and sends the result to the box output. If the value at the VAL input fulfills the comparison MIN <= VAL or VAL <= MAX, the box output has the signal state "1". If the comparison is not fulfilled, the box output has the signal state "0". If the box input has the signal state "0", the "Value within range" instruction is not executed. The comparison function can only execute if the values to be compared are of the same data type and the box input is interconnected. Parameters The following table shows the parameters of the "Value within range" instruction: Parameter Declaration Data type Memory area Description Box input Input BOOL I, Q, M, D, L Result of the previous logic operation MIN Input Integers, floatingpoint numbers I, Q, M, D, L or constant Low limit of the value range VAL Input Integers, floatingpoint numbers I, Q, M, D, L or constant Comparison value MAX Input Integers, floatingpoint numbers I, Q, M, D, L or constant High limit of the value range Box output Output BOOL I, Q, M, D, L Result of the comparison You can select the data type for the instruction from the "<???>" drop-down list of the instruction box. For additional information on valid data types, refer to "See also": Example The following example shows how the instruction works: 7DJ,QB 7DJ,QB 7DJB0LQ 7DJB9DOXH 7DJB0D[ WinCC Basic V13.0 System Manual, 02/2014 ,1B5$1*( 5($/ 7DJ,QB 7DJ2XW 0,1 9$/ 0$; 1833 Programming the PLC 9.7 References The "TagOut" output is set when the following conditions are fulfilled: The operands "TagIn_1" and "TagIn_2" have signal state "1". The value of the operand "Tag_Value" is within the value range that is specified by the current values of the operands "Tag_Min" and "Tag_Max" (MIN <= VAL or VAL <= MAX). The operand "TagIn_3" has the signal state "1". See also Overview of the valid data types (Page 1204) OUT_RANGE: Value outside range Description You can use the "Value outside range" instruction to determine if the value at the VAL input is outside a specific value range. You specify the limits of the value range with the MIN and MAX inputs. The "Value outside range" instruction compares the value at the VAL input with the values of the MIN and MAX inputs and sends the result to the box output. If the value at the VAL input fulfills the comparison MIN > VAL or VAL > MAX, the box output has the signal state "1". The box output also has the signal state "1" if a specified operand with the REAL data type shows an invalid value. The box output returns the signal state "0", if the value at input VAL does not satisfy the MIN > VAL or VAL > MAX condition. If the box input has the signal state "0", the "Value outside range" instruction is not executed. The comparison function can only execute if the values to be compared are of the same data type and the box input is interconnected. Parameters The following table shows the parameters of the "Value outside range" instruction: 1834 Parameter Declaration Data type Memory area Description Box input Input BOOL I, Q, M, D, L Result of the previous logic operation MIN Input Integers, floatingpoint numbers I, Q, M, D, L or constant Low limit of the value range VAL Input Integers, floatingpoint numbers I, Q, M, D, L or constant Comparison value MAX Input Integers, floatingpoint numbers I, Q, M, D, L or constant High limit of the value range Box output Output BOOL I, Q, M, D, L Result of the comparison WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References You can select the data type for the instruction from the "<???>" drop-down list of the instruction box. For additional information on valid data types, refer to "See also". Example The following example shows how the instruction works: 7DJ,QB 7DJ,QB 7DJB0LQ 7DJB9DOXH 7DJB0D[ 287B5$1*( 5($/ 7DJ,QB 7DJ2XW 0,1 9$/ 0$; The "TagOut" output is set when the following conditions are fulfilled: The operands "TagIn_1" and "TagIn_2" have signal state "1". The value of the operand "Tag_Value" is outside the value range that is specified by the values of the operands "Tag_Min" and "Tag_Max" (MIN > VAL or VAL > MAX). The operand "TagIn_3" has the signal state "1". See also Overview of the valid data types (Page 1204) ----I OK I----: Check validity Description You can use the "Check validity" instruction to check if the value of an operand (<operand>) is a valid floating-point number. The query is started in each program cycle when the signal state at the input of the instruction is "1". The output of the instruction has signal state "1" when the value of the operand is a valid floating-point number at the time of the query and the input of the instruction has signal state "1". In all other cases, the signal state at the output of the "Check validity" instruction is "0". You can use the "Check validity" instruction together with the EN mechanism. If you connect the instruction box to an EN enable input, the enable input is set only when the result of the validity query of the value is positive. You can use this function to ensure that an instruction is enabled only when the value of the specified operand is a valid floating-point number. WinCC Basic V13.0 System Manual, 02/2014 1835 Programming the PLC 9.7 References Parameters The following table shows the parameters of the "Check validity" instruction: Parameter Declaration Data type Memory area Description <Operand> Input Floating-point numbers I, Q, M, D, L Value to be queried. For additional information on valid data types, refer to "See also". Example The following example shows how the instruction works: 7DJB9DOXH 2. 7DJB9DOXH 2. 08/ 5($/ (1 (12 7DJB9DOXH ,1 7DJB9DOXH ,1 287 7DJ2XW 7DJB5HVXOW When the values of the operands "Tag_Value1" and "Tag_Value2" show valid floating-point numbers, the "Multiply" (MUL) instruction is activated and the ENO output is set. During the execution of the "Multiply" (MUL) instruction, the value of the operand "Tag_Value1" is multiplied with the value of the operand "Tag_Value2". The product of the multiplication is then stored in the operand "Tag_Result". If the instruction is executed without errors, the ENO and "TagOut" outputs are set to signal state "1". See also Overview of the valid data types (Page 1204) ----I NOT_OK I----: Check invalidity Description You can use the "Check invalidity" instruction to check if the value of an operand (<operand>) is an invalid floating-point number. The query is started in each program cycle when the signal state at the input of the instruction is "1". The output of the instruction has signal state "1" when the value of the operand is an invalid floating-point number at the time of the query and the input of the instruction has signal state "1". In all other cases, the signal state at the output of the "Check invalidity" instruction is "0". 1836 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameters The following table shows the parameters of the "Check invalidity" instruction: Parameter Declaration Data type Memory area Description <Operand> Input Floating-point numbers I, Q, M, D, L Value to be queried. For additional information on valid data types, refer to "See also". Example The following example shows how the instruction works: 029( 7DJ,QB9DOXH 127B2. 127 7DJ,QB9DOXH (1 (12 ,1 287 7DJ2XW 7DJ2XWB9DOXH When the value of operand "TagIn_Value" is an invalid floating-point number, the "Move value" (MOVE) instruction will not be executed. The "TagOut" output is reset to signal state "0". See also Overview of the valid data types (Page 1204) VARIANT instructions EQ_Type: Compare data type for EQUAL with the data type of a tag Description You can use the "Compare data type for EQUAL with the data type of a tag" instruction to query the data type of a tag to which a VARIANT points. You compare the data type of the tag (<Operand1>) to the data type of a tag (<Operand2>) that you have declared in the block interface to determine if they are "Equal". <Operand1> must have the VARIANT data type. <Operand2> can be an elementary data type or a PLC data type. If the condition of the comparison is fulfilled, the instruction returns the result of logic operation (RLO) "1". If the comparison condition is not fulfilled, the instruction returns RLO "0". The RLO of the instruction is logically combined with the RLO of the entire rung as follows: By AND, when the comparison instruction is connected in series. By OR, when the comparison instruction is connected in parallel. Specify <Operand1> at the operand placeholder above the instruction. Specify <Operand2> at the operand placeholder below the instruction. WinCC Basic V13.0 System Manual, 02/2014 1837 Programming the PLC 9.7 References Parameters The following table lists the parameters of the "Compare data type for EQUAL with the data type of a tag" instruction: Parameters Declaration Data type Memory area Description <Operand1> Input VARIANT L First operand <Operand2> Input Bit strings, integers, floating-point numbers, timers, date and time, character strings, ARRAY, PLC data types I, Q, M, D, L Second operand For additional information on valid data types, refer to "See also". Example The following example shows how the instruction works: 7DJ,QB 7DJ,QB 7DJB2SHUDQG (4B7\SH 7DJ2XW 6 7DJB2SHUDQG The "TagOut" output is set when the following conditions are fulfilled: The operands "TagIn_1" and "TagIn_2" have signal state "1". The condition of the comparison instruction is fulfilled, i.e. the "#Tag_Operand1" operand is equal to "Tag_Operand2". See also Overview of the valid data types (Page 1204) NE_Type: Compare data type for UNEQUAL with the data type of a tag Description You can use the "Compare data type for EQUAL with the data type of a tag" instruction to query the data type of a tag to which a VARIANT points. You compare the data type of the tag (<Operand1>) to the data type of a tag (<Operand2>) that you have declared in the block interface to determine if they are "Not equal". <Operand1> must have the VARIANT data type. <Operand2> can be an elementary data type or a PLC data type. If the condition of the comparison is fulfilled, the instruction returns the result of logic operation (RLO) "1". If the comparison condition is not fulfilled, the instruction returns RLO "0". The RLO of the instruction is logically combined with the RLO of the entire rung as follows: 1838 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References By AND, when the comparison instruction is connected in series. By OR, when the comparison instruction is connected in parallel. Specify <Operand1> at the operand placeholder above the instruction. Specify <Operand2> at the operand placeholder below the instruction. Parameters The following table lists the parameters of the "Compare data type for UNEQUAL with the data type of a tag" instruction: Parameters Declaration Data type Memory area Description <Operand1> Input VARIANT L First operand <Operand2> Input Bit strings, integers, floating-point numbers, timers, date and time, character strings, ARRAY, PLC data types I, Q, M, D, L Second operand For additional information on valid data types, refer to "See also". Example The following example shows how the instruction works: 7DJ,QB 7DJ,QB 7DJB2SHUDQG 1(B7\SH 7DJ2XW 6 7DJB2SHUDQG The "TagOut" output is set when the following conditions are fulfilled: The operands "TagIn_1" and "TagIn_2" have signal state "1". The condition of the comparison instruction is fulfilled, i.e. the "#Tag_Operand1" operand is not equal to "Tag_Operand2". See also Overview of the valid data types (Page 1204) EQ_ElemType: Compare element data type for EQUAL with the data type of a tag Description You can use the "Compare element data type for EQUAL with the data type of a tag" instruction to query the data type of a tag to which a VARIANT points. You compare the data type of the tag (<Operand1>) to the data type of a tag (<Operand2>) that you have declared in the block interface to determine if they are "Equal". WinCC Basic V13.0 System Manual, 02/2014 1839 Programming the PLC 9.7 References <Operand1> must have the VARIANT data type. <Operand2> can be an elementary data type or a PLC data type. If the data type of the VARIANT tag (<Operand1>) is an ARRAY, the data type of the ARRAY elements is compared. If the condition of the comparison is fulfilled, the instruction returns the result of logic operation (RLO) "1". If the comparison condition is not fulfilled, the instruction returns RLO "0". The RLO of the instruction is logically combined with the RLO of the entire rung as follows: By AND, when the comparison instruction is connected in series. By OR, when the comparison instruction is connected in parallel. Specify <Operand1> at the operand placeholder above the instruction. Specify <Operand2> at the operand placeholder below the instruction. Parameters The following table lists the parameters of the "Compare element data type for EQUAL with the data type of a tag" instruction: Parameters Declaration Data type Memory area Description <Operand1> Input VARIANT L First operand <Operand2> Input Bit strings, integers, floating-point numbers, timers, date and time, character strings, ARRAY, PLC data types I, Q, M, D, L Second operand For additional information on valid data types, refer to "See also". Example The following example shows how the instruction works: 7DJ,QB 7DJ,QB 7DJB2SHUDQG (4B(OHP7\SH 7DJ2XW 6 7DJB2SHUDQG The "TagOut" output is set when the following conditions are fulfilled: The operands "TagIn_1" and "TagIn_2" have signal state "1". The condition of the comparison instruction is fulfilled, i.e. the "#Tag_Operand1" operand is equal to "Tag_Operand2". See also Overview of the valid data types (Page 1204) 1840 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References NE_ElemType: Compare element data type for UNEQUAL with the data type of a tag Description You can use the "Compare element data type for UNEQUAL with the data type of a tag" instruction to query the data type of a tag to which a VARIANT points. You compare the data type of the tag (<Operand1>) to the data type of a tag (<Operand2>) that you have declared in the block interface to determine if they are "Not equal". <Operand1> must have the VARIANT data type. <Operand2> can be an elementary data type or a PLC data type. If the data type of the VARIANT tag (<Operand1>) is an ARRAY, the data type of the ARRAY elements is compared. If the condition of the comparison is fulfilled, the instruction returns the result of logic operation (RLO) "1". If the comparison condition is not fulfilled, the instruction returns RLO "0". The RLO of the instruction is logically combined with the RLO of the entire rung as follows: By AND, when the comparison instruction is connected in series. By OR, when the comparison instruction is connected in parallel. Specify <Operand1> at the operand placeholder above the instruction. Specify <Operand2> at the operand placeholder below the instruction. Parameters The following table lists the parameters of the "Compare element data type for UNEQUAL with the data type of a tag" instruction: Parameters Declaration Data type Memory area Description <Operand1> Input VARIANT L First operand <Operand2> Input Bit strings, integers, floating-point numbers, timers, date and time, character strings, ARRAY, PLC data types I, Q, M, D, L Second operand For additional information on valid data types, refer to "See also". Example The following example shows how the instruction works: 7DJ,QB 7DJ,QB 7DJB2SHUDQG 1(B(OHP7\SH 7DJ2XW 6 7DJB2SHUDQG The "TagOut" output is set when the following conditions are fulfilled: WinCC Basic V13.0 System Manual, 02/2014 1841 Programming the PLC 9.7 References The operands "TagIn_1" and "TagIn_2" have signal state "1". The condition of the comparison instruction is fulfilled, i.e. the "#Tag_Operand1" operand is not equal to "Tag_Operand2". See also Overview of the valid data types (Page 1204) IS_NULL: Compare for EQUALS ZERO Description You can use the instruction "Compare for EQUALS ZERO" to query whether the VARIANT does not point to an object. The <Operand> must have the VARIANT data type. Note VARIANT tag points to an ANY pointer If the VARIANT tag points to an ANY pointer, the instruction always returns the result RLO = "0" even if the ANY pointer is ZERO. Parameters The following table lists the parameters of the "Compare for EQUALS ZERO" instruction: Parameters Declaration Data type Memory area Description <Operand> Input VARIANT L Operand that is compared for EQUAL ZERO For additional information on valid data types, refer to "See also". Example The following example shows how the instruction works: 7DJ,QB 7DJ,QB 7DJB2SHUDQG ,6B18// 7DJ2XW 6 The "TagOut" output is set when the following conditions are fulfilled: 1842 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References The operands "TagIn_1" and "TagIn_2" have signal state "1". The condition of the comparison instruction is fulfilled, i.e. the "#Tag_Operand" operand does not point to an object. See also Overview of the valid data types (Page 1204) NOT_NULL: Compare for UNEQUALS ZERO Description You can use the instruction "Compare for UNEQUALS ZERO" to query whether the VARIANT points to an object. The <Operand> must have the VARIANT data type. Note VARIANT tag points to an ANY pointer If the VARIANT tag points to an ANY pointer, the instruction always returns the result RLO = "1" even if the ANY pointer is ZERO. Parameters The following table lists the parameters of the "Compare for UNEQUALS ZERO" instruction: Parameters Declaration Data type Memory area Description <Operand> Input VARIANT L Operand that is compared for NOT EQUAL ZERO For additional information on valid data types, refer to "See also". Example The following example shows how the instruction works: 7DJ,QB 7DJ,QB 7DJB2SHUDQG 127B18// 7DJ2XW 6 The "TagOut" output is set when the following conditions are fulfilled: WinCC Basic V13.0 System Manual, 02/2014 1843 Programming the PLC 9.7 References The operands "TagIn_1" and "TagIn_2" have signal state "1". The condition of the comparison instruction is fulfilled, i.e. the "#Tag_Operand" operand points to an object. See also Overview of the valid data types (Page 1204) IS_ARRAY: Check for ARRAY Description You can use the instruction "Check for ARRAY" to query whether the VARIANT points to a tag of the ARRAY data type. The <Operand> must have the VARIANT data type. Parameters The following table lists the parameters of the "Check for ARRAY" instruction: Parameters Declaration Data type Memory area Description <Operand> Input VARIANT L Operand that is query for ARRAY For additional information on valid data types, refer to "See also". Example The following example shows how the instruction works: 7DJ,QB 7DJ,QB 7DJB9$5,$17 7R$UUD\ ,6B$55$< 7DJ2XW 6 The "TagOut" output is set when the following conditions are fulfilled: The operands "TagIn_1" and "TagIn_2" have signal state "1". The condition of the comparison instruction is fulfilled, i.e. the "#Tag_VARIANTToArray" operand has the ARRAY data type. See also Overview of the valid data types (Page 1204) 1844 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Math functions CALCULATE: Calculate Description The "Calculate" instruction is used to define and execute an expression for the calculation of mathematical operations or complex logic operations depending on the selected data type. You can select the data type of the instruction from the "<???>" drop-down list of the instruction box. Depending on the data type selected, you can combine the functions of certain instructions to perform a complex calculation. The expression to be calculated is specified via a dialog you can open via the "Calculator" icon at the top of the instruction box. The expression can contain names of input parameters and the syntax of the instructions. Operand names and operand addresses cannot be specified. In its initial state, the instruction box contains at least 2 inputs (IN1 and IN2). The number of inputs can be extended. The inserted inputs are numbered in ascending order in the box. The values of the inputs are used to execute the specified expression. Not all of the defined inputs have to be used in the expression. The result of the instruction is transferred to the output OUT. Note If one of the mathematical operations fails in the expression, no result is transferred to the output OUT and the enable output ENO returns the signal state "1". If you use inputs in the expression that are not available in the box, they are inserted automatically. This requires that there are no gaps in the numbering of the inputs to be newly defined in the expression. For example, you cannot use the IN4 input in the expression unless the IN3 input has been defined. The ENO enable output has the signal state "0" if one of the following conditions is fulfilled: The EN enable input has the signal state "0". The result of the "Calculate" instruction is outside the range permitted for the data type specified at the OUT output. A floating-point number has an invalid value. An error occurred during execution of one of the instructions in the expression. The following table shows the instructions that can be executed together in the expression of the instruction "Calculate", depending on the selected data type: Data type Instruction Syntax Example Bit strings AND: AND logic operation AND IN1 AND IN2 OR IN3 OR: OR logic operation OR XOR: EXCLUSIVE OR logic operation XOR INV: Create ones complement NOT SWAP: Swap SWAP WinCC Basic V13.0 System Manual, 02/2014 1) 1845 Programming the PLC 9.7 References Data type Instruction Syntax Example Integers ADD: Add + (IN1 + IN2) * IN3; SUB: Subtract - MUL: Multiply * (ABS(IN2)) * (ABS(IN1)) DIV: Divide / MOD: Return remainder of division MOD INV: Create ones complement NOT NEG: Create twos complement -(in1) ABS: Form absolute value ABS( ) Floating-point numbers ADD: Add + ((SIN(IN2) * SIN(IN2) + (SIN(IN3) * SIN(IN3)) / IN3)); SUB: Subtract - MUL: Multiply * DIV: Divide / EXPT: Exponentiate ** ABS: Form absolute value ABS( ) SQR: Form square SQR( ) SQRT: Form square root SQRT( ) LN: Form natural logarithm LN( ) EXP: Form exponential value EXP( ) FRAC: Return fraction FRAC( ) (SQR(SIN(IN2)) + (SQR(COS(IN3)) / IN2)) SIN: Form sine value SIN( ) COS: Form cosine value COS( ) TAN: Form tangent value TAN( ) ASIN: Form arcsine value ASIN( ) ACOS: Form arcosine value ACOS( ) ATAN: Form arctangent value ATAN( ) NEG: Create twos complement -(in1) TRUNC: Truncate numerical value TRUNC( ) ROUND: Round numerical value ROUND( ) CEIL: Generate next higher integer from floatingpoint number CEIL( ) FLOOR: Generate next lower integer from floating- FLOOR( ) point number 1) Not possible for data type BYTE. Parameters The following table shows the parameters of the "Calculate" instruction: 1846 Parameters Declaration Data type Memory area Description EN Input BOOL I, Q, M, D, L Enable input ENO Output BOOL I, Q, M, D, L Enable output WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameters Declaration Data type Memory area Description IN1 Input Bit strings, integers, floatingpoint numbers I, Q, M, D, L, P or constant First available input IN2 Input Bit strings, integers, floatingpoint numbers I, Q, M, D, L, P or constant Second available input INn Input Bit strings, integers, floatingpoint numbers I, Q, M, D, L, P or constant Additionally inserted inputs OUT Output Bit strings, integers, floatingpoint numbers I, Q, M, D, L, P Output to which the end result is to be transferred. For additional information on valid data types, refer to "See also". Example The following example shows how the instruction works: &$/&8/$7( ,17 7DJB,QSXW 7DJB2XWSXW (1 (12 7DJB9DOXHB ,1 ,1,1 ,1 ,1 287 7DJB9DOXHB ,1 7DJB9DOXHB ,1 7DJB9DOXHB ,1 7DJB5HVXOW The following table shows how the instruction works using specific operand values: Parameters Operand Value IN1 Tag_Value_1 4 IN2 Tag_Value_2 4 IN3 Tag_Value_3 3 IN4 Tag_Value_4 2 OUT Tag_Result 12 If the "Tag_Input" input has the signal state"1", the "Calculate" instruction is executed. The value of operand "Tag_Value_1" is added to the value of operand "Tag_Value_2". The sum is multiplied with the value of operand "Tag_Value_3". The product is divided by the value of operand "Tag_Value_4". The quotient is transferred as end result to the operand "Tag_Result" at the OUT output of the instruction. If the instruction is executed without errors, the enable output ENO and operand "Tag_Output" are set to "1". WinCC Basic V13.0 System Manual, 02/2014 1847 Programming the PLC 9.7 References See also Using the "Calculate" instruction (Page 1420) Overview of the valid data types (Page 1204) Inserting additional inputs and outputs in LAD elements (Page 1428) Removing inputs and outputs (Page 1429) Basics of the EN/ENO mechanism (Page 1299) ADD: Add Description You can use the "Add" instruction to add the value at input IN1 and the value at input IN2 and query the sum at output OUT (OUT := IN1+IN2). In its initial state, the instruction box contains at least 2 inputs (IN1 and IN2). The number of inputs can be extended. The inserted inputs are numbered in ascending order in the box. When the instruction is executed, the values of all available input parameters are added. The sum is stored at the OUT output. The ENO enable output has the signal state "0" if one of the following conditions is fulfilled: The enable input EN has the signal state "0". The result of the instruction is outside the range permitted for the data type specified at the OUT output. A floating-point number has an invalid value. Parameters The following table shows the parameters of the "Add" instruction: Parameter Declaration Data type Memory area Description EN Input BOOL I, Q, M, D, L Enable input ENO Output BOOL I, Q, M, D, L Enable output IN1 Input Integers, floatingpoint numbers I, Q, M, D, L, P or constant First number to be added IN2 Input Integers, floatingpoint numbers I, Q, M, D, L, P or constant Second number to be added INn Input Integers, floatingpoint numbers I, Q, M, D, L, P or constant Optional input values that are added. OUT Output Integers, floatingpoint numbers I, Q, M, D, L, P Sum You can select the data type for the instruction from the "<???>" drop-down list of the instruction box. For additional information on valid data types, refer to "See also": 1848 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Example The following example shows how the instruction works: 7DJ,Q $'' ,17 (1 7DJB9DOXH ,1 7DJB9DOXH ,1 7DJ2XW 6 (12 287 7DJB5HVXOW If operand "TagIn" has the signal state "1", the "Add" instruction is executed. The value of operand "Tag_Value1" is added to the value of operand "Tag_Value2". The result of the addition is stored in operand "Tag_Result". If the instruction is executed without errors, the ENO enable output has the signal state "1" and the "TagOut" output is set. See also Overview of the valid data types (Page 1204) Removing inputs and outputs (Page 1429) Basics of the EN/ENO mechanism (Page 1299) Selecting a data type (Page 1413) Inserting additional inputs and outputs in LAD elements (Page 1428) SUB: Subtract Description You can use the "Subtract" instruction to subtract the value at input IN2 from the value at input IN1 and query the difference at output OUT (OUT := IN1-IN2). The ENO enable output has the signal state "0" if one of the following conditions is fulfilled: The EN enable input has the signal state "0". The result of the instruction is outside the range permitted for the data type specified at the OUT output. A floating-point number has an invalid value. Parameters The following table shows the parameters of the "Subtract" instruction: WinCC Basic V13.0 System Manual, 02/2014 Parameter Declaration Data type Memory area Description EN Input BOOL I, Q, M, D, L Enable input ENO Output BOOL I, Q, M, D, L Enable output IN1 Input Integers, floatingpoint numbers I, Q, M, D, L, P or constant Minuend 1849 Programming the PLC 9.7 References Parameter Declaration Data type Memory area Description IN2 Input Integers, floatingpoint numbers I, Q, M, D, L, P or constant Subtracting OUT Output Integers, floatingpoint numbers I, Q, M, D, L, P Difference You can select the data type for the instruction from the "<???>" drop-down list of the instruction box. For additional information on valid data types, refer to "See also". Example The following example shows how the instruction works: 7DJ,Q 68% ,17 (1 7DJB9DOXH ,1 7DJB9DOXH ,1 7DJ2XW 6 (12 287 7DJB5HVXOW If operand "TagIn" has the signal state "1", the "Subtract" instruction is executed. The value of operand "Tag_Value2" is subtracted from the value of operand "Tag_Value1". The result of the subtraction is stored in operand "Tag_Result". If the instruction is executed without errors, the ENO enable output has the signal state "1" and the "TagOut" output is set. See also Overview of the valid data types (Page 1204) Basics of the EN/ENO mechanism (Page 1299) Selecting a data type (Page 1413) MUL: Multiply Description You can use the "Multiply" instruction to multiply the value at input IN1 with the value at input IN2 and query the product at output OUT (OUT := IN1*IN2). The number of inputs can be expanded in the instruction box. The added inputs are numbered in ascending order in the box. When the instruction is executed, the values of all available input parameters are multiplied. The product is stored at the OUT output. The ENO enable output has the signal state "0" if one of the following conditions is fulfilled: The EN input has the signal state "0". The result is outside the range permitted for the data type specified at output OUT. A floating-point number has an invalid value. 1850 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameters The following table shows the parameters of the "Multiply" instruction: Parameter Declaration Data type Memory area Description EN Input BOOL I, Q, M, D, L Enable input ENO Output BOOL I, Q, M, D, L Enable output IN1 Input Integers, floatingpoint numbers I, Q, M, D, L, P or constant Multiplier IN2 Input Integers, floatingpoint numbers I, Q, M, D, L, P or constant Number being multiplied INn Input Integers, floatingpoint numbers I, Q, M, D, L, P or constant Optional input values that can be multiplied. OUT Output Integers, floatingpoint numbers I, Q, M, D, L, P Product You can select the data type for the instruction from the "<???>" drop-down list of the instruction box. For additional information on valid data types, refer to "See also". Example The following example shows how the instruction works: 7DJ,Q 08/ 5($/ (1 7DJB9DOXH ,1 7DJB9DOXH ,1 7DJ2XW 6 (12 287 7DJB5HVXOW If operand "TagIn" has the signal state "1", the "Multiply" instruction is executed. The value of operand "Tag_Value1" is multiplied by the value of operand "Tag_Value2". The result of the multiplication is stored in operand "Tag_Result". If the instruction is executed without errors, the ENO enable output has the signal state "1" and the "TagOut" output is set. See also Overview of the valid data types (Page 1204) Removing inputs and outputs (Page 1429) Basics of the EN/ENO mechanism (Page 1299) Selecting a data type (Page 1413) Inserting additional inputs and outputs in LAD elements (Page 1428) WinCC Basic V13.0 System Manual, 02/2014 1851 Programming the PLC 9.7 References DIV: Divide Description You can use the "Divide" instruction to divide the value at input IN1 by the value at input IN2 and query the quotient at output OUT (OUT := IN1/IN2). The ENO enable output has the signal state "0" if one of the following conditions is fulfilled: The EN enable input has the signal state "0". The result of the instruction is outside the range permitted for the data type specified at the OUT output. A floating-point number has an invalid value. Parameters The following table shows the parameters of the "Divide" instruction: Parameter Declaration Data type Memory area Description EN Input BOOL I, Q, M, D, L Enable input ENO Output BOOL I, Q, M, D, L Enable output IN1 Input Integers, floatingpoint numbers I, Q, M, D, L, P or constant Dividend IN2 Input Integers, floatingpoint numbers I, Q, M, D, L, P or constant Divisor OUT Output Integers, floatingpoint numbers I, Q, M, D, L, P Quotient value You can select the data type for the instruction from the "<???>" drop-down list of the instruction box. For additional information on valid data types, refer to "See also". Example The following example shows how the instruction works: 7DJ,Q ',9 5($/ (1 7DJB9DOXH ,1 7DJB9DOXH ,1 (12 287 7DJ2XW 6 7DJB5HVXOW If operand "TagIn" has the signal state "1", the "Divide" instruction is executed. The value of operand "Tag_Value1" is divided by the value of operand "Tag_Value2". The division result is stored in operand "Tag_Result". If the instruction is executed without errors, the ENO enable output has the signal state "1" and the "TagOut" output is set. 1852 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References See also Overview of the valid data types (Page 1204) Basics of the EN/ENO mechanism (Page 1299) Selecting a data type (Page 1413) MOD: Return remainder of division Description You can use the "Return remainder of division" instruction to divide the value at input IN1 by the value at input IN2 and query the remainder of division at output OUT. Parameters The following table shows the parameters of the "Return remainder of division" instruction: Parameter Declaration Data type Memory area Description EN Input BOOL I, Q, M, D, L Enable input ENO Output BOOL I, Q, M, D, L Enable output IN1 Input Integers I, Q, M, D, L, P or constant Dividend IN2 Input Integers I, Q, M, D, L, P or constant Divisor OUT Output Integers I, Q, M, D, L, P Remainder of division You can select the data type for the instruction from the "<???>" drop-down list of the instruction box. For additional information on valid data types, refer to "See also". Example The following example shows how the instruction works: 02' 7DJ,Q ',17 (1 7DJB9DOXH ,1 7DJB9DOXH ,1 (12 287 7DJ2XW 6 7DJB5HVXOW If operand "TagIn" has the signal state "1", the "Return remainder of division" instruction is executed. The value of operand "Tag_Value1" is divided by the value of operand "Tag_Value2". The remainder is stored in operand "Tag_Result". If the instruction is executed without errors, the ENO enable output has the signal state "1" and the "TagOut" output is set. WinCC Basic V13.0 System Manual, 02/2014 1853 Programming the PLC 9.7 References See also Overview of the valid data types (Page 1204) Basics of the EN/ENO mechanism (Page 1299) Selecting a data type (Page 1413) NEG: Create twos complement Description You can use the "Create twos complement" instruction to change the sign of the value at the IN input and query the result at the OUT output. If there is a positive value at input IN, for example, the negative equivalent of this value is sent to output OUT. The ENO enable output has the signal state "0" if one of the following conditions is fulfilled: The EN enable input has the signal state "0". The result of the instruction is outside the range permitted for the data type specified at the OUT output. A floating-point number has an invalid value. Parameters The following table shows the parameters of the "Create twos complement" instruction: Parameter Declaration Data type S7-1200 S7-1500 Memory area Description Enable input EN Input BOOL BOOL I, Q, M, D, L ENO Output BOOL BOOL I, Q, M, D, L Enable output IN Input SINT, INT, DINT, floatingpoint numbers SINT, INT, DINT, LINT, floating-point numbers I, Q, M, D, L, P or constant Input value OUT Output SINT, INT, DINT, floatingpoint numbers SINT, INT, DINT, LINT, floating-point numbers I, Q, M, D, L, P Twos complement of the input value You can select the data type for the instruction from the "<???>" drop-down list of the instruction box. For additional information on valid data types, refer to "See also". 1854 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Example The following example shows how the instruction works: 7DJ,Q 7DJ,QB9DOXH 1(* 5($/ (1 (12 ,1 287 7DJ2XW 7DJ2XWB9DOXH If operand "TagIn" has the signal state "1", the "Create twos complement" instruction is executed. The sign of the value at input "TagIn_Value" is changed and the result is provided at "TagOut_Value" output. If the instruction is executed without errors, the ENO enable output has the signal state "1" and the "TagOut" output is set. See also Overview of the valid data types (Page 1204) Basics of the EN/ENO mechanism (Page 1299) INC: Increment Description You can use the "Increment" instruction to change the value of the operand at the IN/OUT parameter to the next higher value and query the result. The "Increment" instruction is only started when the signal state at the EN enable input is "1". If no overflow error occurs during the execution, the ENO enable output also has the signal state "1". The ENO enable output has the signal state "0" if one of the following conditions is fulfilled: The EN enable input has the signal state "0". A floating-point number has an invalid value. Parameters The following table shows the parameters of the "Increment" instruction: Parameter Declaration Data type Memory area Description EN Input BOOL I, Q, M, D, L Enable input ENO Output BOOL I, Q, M, D, L Enable output IN/OUT InOut Integers I, Q, M, D, L Value to be incremented. You can select the data type for the instruction from the "<???>" drop-down list of the instruction box. For additional information on valid data types, refer to "See also". WinCC Basic V13.0 System Manual, 02/2014 1855 Programming the PLC 9.7 References Example The following example shows how the instruction works: ,1& 7DJ,QB 7DJ,QB 7DJB,Q2XW ,17 (1 (12 7DJ2XW ,1 287 If operands "TagIn_1" and "TagIn_2" have the signal state "1", the value of operand "Tag_InOut" is incremented by one and the "TagOut" output is set. See also Overview of the valid data types (Page 1204) Basics of the EN/ENO mechanism (Page 1299) DEC: Decrement Description You can use the "Decrement" instruction to change the value of the operand at the IN/OUT parameter to the next lower value and query the result. The "Decrement" instruction is only started when the signal state at the EN enable input is "1". If the range of values of the selected data type is not exceeded during processing, the ENO output also has the signal state "1". The ENO enable output has the signal state "0" if one of the following conditions is fulfilled: The EN enable input has the signal state "0". A floating-point number has an invalid value. Parameter The following table shows the parameters of the "Decrement" instruction: Parameter Declaration Data type Memory area Description EN Input BOOL I, Q, M, D, L Enable input ENO Output BOOL I, Q, M, D, L Enable output IN/OUT InOut Integers I, Q, M, D, L Value to be decremented. You can select the data type for the instruction from the "<???>" drop-down list of the instruction box. For additional information on valid data types, refer to "See also". 1856 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Example The following example shows how the instruction works: '(& 7DJ,QB 7DJ,QB 7DJB,Q2XW ,17 (1 (12 7DJ2XW ,1 287 If operands "TagIn_1" and "TagIn_2" have the signal state "1", the value of operand "Tag_InOut" is decremented by one and the "TagOut" output is set. See also Overview of the valid data types (Page 1204) Basics of the EN/ENO mechanism (Page 1299) ABS: Form absolute value Description You can use the "Form absolute value" instruction to calculate the absolute value of the value specified at input IN. The result of the instruction is sent to the OUT output and can be queried there. The ENO enable output has the signal state "0" if one of the following conditions is fulfilled: The EN enable input has the signal state "0". A floating-point number has an invalid value. Parameters The following table shows the parameters of the "Form absolute value" instruction: Parameter WinCC Basic V13.0 System Manual, 02/2014 Declaration Data type S7-1200 S7-1500 Memory area Description EN Input BOOL BOOL I, Q, M, D, L Enable input ENO Output BOOL BOOL I, Q, M, D, L Enable output IN Input SINT, INT, DINT, floatingpoint numbers SINT, INT, DINT, LINT, floating-point numbers I, Q, M, D, L, P or constant Input value OUT Output SINT, INT, DINT, floatingpoint numbers SINT, INT, DINT, LINT, floating-point numbers I, Q, M, D, L, P Absolute value of the input value 1857 Programming the PLC 9.7 References You can select the data type for the instruction from the "<???>" drop-down list of the instruction box. For additional information on valid data types, refer to "See also". Example The following example shows how the instruction works: 7DJ,Q 7DJ,QB9DOXH $%6 5($/ (1 (12 ,1 287 7DJ2XW 7DJ2XWB9DOXH The following table shows how the instruction works using specific operand values: Parameter Operand Value IN TagIn_Value -6.234 OUT TagOut_Value 6.234 If operand "TagIn" has the signal state "1", the "Form absolute value" instruction is executed. The instruction calculates the absolute value of the value at input "TagIn_Value" and sends the result to output "TagOut_Value". If the instruction is executed without errors, the "TagOut" output is set. See also Overview of the valid data types (Page 1204) Basics of the EN/ENO mechanism (Page 1299) MIN: Get minimum Description The "Get minimum" instruction compares the values at the available inputs and writes the lowest value to the OUT output. The number of inputs can be expanded at the instruction box by additional inputs. The inputs are numbered in ascending order in the box. A minimum of two and a maximum of 100 inputs must be specified for the execution of the instruction. The ENO enable output has the signal state "0" if one of the following conditions is fulfilled: Enable input EN has the signal state "0". The implicit conversion of the data types fails during execution of the instruction. A floating-point number has an invalid value. 1858 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameters The following table shows the parameters of the "Get minimum" instruction: Parameter Declaration Data type S7-1200 S7-1500 Memory area Description EN Input BOOL BOOL I, Q, M, D, L Enable input ENO Output BOOL BOOL I, Q, M, D, L Enable output IN1 Input Integers, floatingpoint numbers, TIME, TOD, DATE Integers, floating-point numbers, TIME, LTIME, TOD, LTOD, DATE, LDT I, Q, M, D, L, P or constant First input value IN2 Input Integers, floatingpoint numbers, TIME, TOD, DATE Integers, floating-point numbers, TIME, LTIME, TOD, LTOD, DATE, LDT I, Q, M, D, L, P or constant Second input value INn Input Integers, floatingpoint numbers, TIME, TOD, DATE Integers, floating-point numbers, TIME, LTIME, TOD, LTOD, DATE, LDT I, Q, M, D, L, P or constant Additionally inserted inputs whose values are to be compared OUT Output Integers, floatingpoint numbers, TIME, TOD, DATE Integers, floating-point numbers, TIME, LTIME, TOD, LTOD, DATE, LDT I, Q, M, D, L, P Result The data types TOD, LTOD, DATE, and LDT can only be used if the IEC test is not enabled. You can select the data type of the instruction from the "<???>" drop-down list of the instruction box. For additional information on valid data types, refer to "See also". Example The following example shows how the instruction works: 7DJ,QB WinCC Basic V13.0 System Manual, 02/2014 7DJ,QB 0,1 ,17 (1 (12 7DJ,QB9DOXH ,1 287 7DJ,QB9DOXH ,1 7DJ,QB9DOXH ,1 7DJ2XW 7DJ2XWB9DOXH 1859 Programming the PLC 9.7 References The following table shows how the instruction works using specific operand values: Parameter Operand Value IN1 TagIn_Value1 12222 IN2 TagIn_Value2 14444 IN3 TagIn_Value3 13333 OUT TagOut_Value 12222 If the "TagIn_1" and "TagIn_2" operands have signal state "1", the "Get minimum" instruction is executed. The instruction compares the values of the specified operands and copies the lowest value ("TagIn_Value1") to output "TagOut_Value". If the instruction is executed without errors, the "TagOut" output is set. See also Overview of the valid data types (Page 1204) Inserting additional inputs and outputs in LAD elements (Page 1428) Basics of the EN/ENO mechanism (Page 1299) MAX: Get maximum Description The "Get maximum" instruction compares the values at the available inputs and writes the highest value to the OUT output. The number of inputs can be expanded at the instruction box by additional inputs. The inputs are numbered in ascending order in the box. A minimum of two and a maximum of 100 inputs must be specified for the execution of the instruction. The ENO enable output has the signal state "0" if one of the following conditions is fulfilled: Enable input EN has the signal state "0". The implicit conversion of the data types fails during execution of the instruction. A floating-point number has an invalid value. Parameters The following table shows the parameters of the "Get maximum" instruction: Parameter 1860 Declaration Data type S7-1200 S7-1500 Memory area Description EN Input BOOL BOOL I, Q, M, D, L Enable input ENO Output BOOL BOOL I, Q, M, D, L Enable output WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameter Declaration Data type S7-1200 S7-1500 Memory area Description IN1 Input Integers, floatingpoint numbers, TIME, TOD, DATE Integers, floating-point numbers, TIME, LTIME, TOD, LTOD, DATE, LDT I, Q, M, D, L, P or constant First input value IN2 Input Integers, floatingpoint numbers, TIME, TOD, DATE Integers, floating-point numbers, TIME, LTIME, TOD, LTOD, DATE, LDT I, Q, M, D, L, P or constant Second input value INn Input Integers, floatingpoint numbers, TIME, TOD, DATE Integers, floating-point numbers, TIME, LTIME, TOD, LTOD, DATE, LDT I, Q, M, D, L, P or constant Additionally inserted inputs whose values are to be compared OUT Output Integers, floatingpoint numbers, TIME, TOD, DATE Integers, floating-point numbers, TIME, LTIME, TOD, LTOD, DATE, LDT I, Q, M, D, L, P Result The data types TOD, LTOD, DATE, and LDT can only be used if the IEC test is not enabled. You can select the data type of the instruction from the "<???>" drop-down list of the instruction box. For additional information on valid data types, refer to "See also". Example The following example shows how the instruction works: 7DJ,QB 7DJ,QB 0$; ,17 7DJ2XW (1 (12 7DJ,QB9DOXH ,1 287 7DJ,QB9DOXH ,1 7DJ,QB9DOXH ,1 7DJ2XWB9DOXH The following table shows how the instruction works using specific operand values: WinCC Basic V13.0 System Manual, 02/2014 Parameter Operand Value IN1 TagIn_Value1 12222 IN2 TagIn_Value2 14444 1861 Programming the PLC 9.7 References Parameter Operand Value IN3 TagIn_Value3 13333 OUT TagOut_Value 14444 If the "TagIn_1" and "TagIn_2" operands have signal state "1", the "Get maximum" instruction is executed. The instruction compares the values of the specified operands and copies the highest value ("TagIn_Value2") to output "TagOut_Value". If the instruction is executed without errors, the "TagOut" output is set. See also Overview of the valid data types (Page 1204) Inserting additional inputs and outputs in LAD elements (Page 1428) Removing inputs and outputs (Page 1429) Basics of the EN/ENO mechanism (Page 1299) LIMIT: Set limit value Description You can use the "Set limit value" instruction to limit the value at input IN to the values at the inputs MN and MX. If the value at the IN input meets the condition MN <= IN <= MX, it is copied to the OUT output. If the condition is not fulfilled and the input value IN is below the low limit MN, the output OUT is set to the value of the MN input. If the MX high limit is exceeded, the OUT output is set to the value of the MX input. If the value at the MN input is greater than at the MX input, the result is undefined and the enable output ENO is "0". The ENO enable output has the signal state "0" if one of the following conditions is fulfilled: Enable input EN has the signal state "0". The specified tags are not of the same data type. An operand has an invalid value. The value at the MN input is greater than the value of the MX input. Parameters The following table shows the parameters of the "Set limit value" instruction: Parameter 1862 Declaration Data type S7-1200 S7-1500 Memory area Description EN Input BOOL BOOL I, Q, M, D, L Enable input ENO Output BOOL BOOL I, Q, M, D, L Enable output WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameter Declaration Data type S7-1200 S7-1500 Memory area Description MN Input Integers, floatingpoint numbers, TIME, TOD, DATE Integers, floating-point numbers, TIME, LTIME, TOD, LTOD, DATE, LDT I, Q, M, D, L, P or constant Low limit IN Input Integers, floatingpoint numbers, TIME, TOD, DATE Integers, floating-point numbers, TIME, LTIME, TOD, LTOD, DATE, LDT I, Q, M, D, L, P or constant Input value MX Input Integers, floatingpoint numbers, TIME, TOD, DATE Integers, floating-point numbers, TIME, LTIME, TOD, LTOD, DATE, LDT I, Q, M, D, L, P or constant High limit OUT Output Integers, floatingpoint numbers, TIME, TOD, DATE Integers, floating-point numbers, TIME, LTIME, TOD, LTOD, DATE, LDT I, Q, M, D, L, P Result The data types TOD, LTOD, DATE, and LDT can only be used if the IEC test is not enabled. You can select the data type of the instruction from the "<???>" drop-down list of the instruction box. For additional information on valid data types, refer to "See also". Example The following example shows how the instruction works: 7DJ,QB 7DJ,QB 7DJB01 7DJB9DOXH 7DJB0; /,0,7 ,17 (1 (12 01 287 7DJ2XW 7DJB5HVXOW ,1 0; The following table shows how the instruction works using specific operand values: WinCC Basic V13.0 System Manual, 02/2014 Parameter Operand Value MN Tag_MN 12000 IN Tag_Value 8000 1863 Programming the PLC 9.7 References Parameter Operand Value MX Tag_MX 16000 OUT Tag_Result 12000 If operands "TagIn_1" and "TagIn_2" have the signal state "1", the "Set limit value" instruction is executed. The value of operand "Tag_Value" is compared with the values of operands "Tag_MN" and "Tag_MX". Since the value of operand "Tag_Value" is less than the low limit, the value of operand "Tag_MN" is copied to the "Tag_Result" output. If the instruction is executed without errors, the "TagOut" output is set. See also Overview of the valid data types (Page 1204) Basics of the EN/ENO mechanism (Page 1299) SQR: Form square Description You can use the "Form square" instruction to square the value at the IN input and query the result at the OUT output. The ENO enable output has the signal state "0" if one of the following conditions is fulfilled: The EN enable input has the signal state "0". The value at the IN input is not a valid floating-point number. Parameters The following table shows the parameters of the "Form square" instruction: Parameter Declaration Data type Memory area Description EN Input BOOL I, Q, M, D, L Enable input ENO Output BOOL I, Q, M, D, L Enable output IN Input Floating-point numbers I, Q, M, D, L, P or constant Input value OUT Output Floating-point numbers I, Q, M, D, L, P Square of the input value You can select the data type for the instruction from the "<???>" drop-down list of the instruction box. For additional information on valid data types, refer to "See also". 1864 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Example The following example shows how the instruction works: 7DJ,Q 7DJB9DOXH 645 5($/ (1 (12 ,1 287 7DJ2XW 7DJB5HVXOW The following table shows how the instruction works using specific operand values: Parameter Operand Value IN Tag_Value 5.0 OUT Tag_Result 25.0 If operand "TagIn" has the signal state "1", the "Form square" instruction is executed. The instruction squares the value of operand "Tag_Value" and sends the result to the "Tag_Result" output. If the instruction is executed without errors, the "TagOut" output is set. See also Overview of the valid data types (Page 1204) Basics of the EN/ENO mechanism (Page 1299) SQRT: Form square root Description You can use the "Form square root" instruction to find the square root of the value at the IN input and query the result at the OUT output. The instruction outputs a positive result if the input value is greater than zero. If input values are less than zero, the OUT output returns an invalid floating-point number. If the value at input IN is "0", then the result is also "0". The ENO enable output has the signal state "0" if one of the following conditions is fulfilled: The EN enable input has the signal state "0". The value at the IN input is not a valid floating-point number. The value at the IN input is negative. Parameters The following table shows the parameters of the "Form square root" instruction: WinCC Basic V13.0 System Manual, 02/2014 Parameter Declaration Data type Memory area Description EN Input BOOL I, Q, M, D, L Enable input ENO Output BOOL I, Q, M, D, L Enable output 1865 Programming the PLC 9.7 References Parameter Declaration Data type Memory area Description IN Input Floating-point numbers I, Q, M, D, L, P or constant Input value OUT Output Floating-point numbers I, Q, M, D, L, P Square root of the input value You can select the data type for the instruction from the "<???>" drop-down list of the instruction box. For additional information on valid data types, refer to "See also". Example The following example shows how the instruction works: 7DJ,Q 7DJB9DOXH 6457 5($/ (1 (12 ,1 287 7DJ2XW 7DJB5HVXOW The following table shows how the instruction works using specific operand values: Parameter Operand Value IN Tag_Value 25.0 OUT Tag_Result 5.0 If operand "TagIn" has the signal state "1", the "Form square root" instruction is executed. The instruction finds the square root of the value of operand "Tag_Value" and stores the result in the "Tag_Result" output. If the instruction is executed without errors, the "TagOut" output is set. See also Overview of the valid data types (Page 1204) Basics of the EN/ENO mechanism (Page 1299) LN: Form natural logarithm Description You can use the "Form natural logarithm" instruction to calculate the natural logarithm to base e (e = 2.718282) of the value at input IN. The result is sent to the OUT output and can be queried there. The instruction outputs a positive result if the input value is greater than zero. If input values are less than zero, the OUT output returns an invalid floating-point number. The ENO enable output has the signal state "0" if one of the following conditions is fulfilled: 1866 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References The enable input EN has the signal state "0". The value at the IN input is not a valid floating-point number. The value at the IN input is negative. Parameters The following table shows the parameters of the "Form natural logarithm" instruction: Parameters Declaration Data type Memory area Description EN Input BOOL I, Q, M, D, L Enable input ENO Output BOOL I, Q, M, D, L Enable output IN Input Floating-point numbers I, Q, M, D, L, P or constant Input value OUT Output Floating-point numbers I, Q, M, D, L, P Natural logarithm of the input value You can select the data type for the instruction from the "<???>" drop-down list of the instruction box. For additional information on valid data types, refer to "See also". Example The following example shows how the instruction works: 7DJ,Q 7DJB9DOXH /1 5($/ (1 (12 ,1 287 7DJ2XW 7DJB5HVXOW If operand "TagIn" has the signal state "1", the "Form natural logarithm" instruction is executed. The instruction forms the natural logarithm of the value at the "Tag_Value" input and stores the result in the "Tag_Result" output. If the instruction is executed without errors, the "TagOut" output is set. See also Overview of the valid data types (Page 1204) Basics of the EN/ENO mechanism (Page 1299) WinCC Basic V13.0 System Manual, 02/2014 1867 Programming the PLC 9.7 References EXP: Form exponential value Description You can use the "Form exponential value" instruction to calculate the exponent from the base e (e = 2.718282) and the value specified at input IN. The result is provided at output OUT and can be queried there (OUT = eIN). The ENO enable output has the signal state "0" if one of the following conditions is fulfilled: The enable input EN has the signal state "0". The value at the IN input is not a valid floating-point number. Parameters The following table shows the parameters of the "Form exponential value" instruction: Parameters Declaration Data type Memory area Description EN Input BOOL I, Q, M, D, L Enable input ENO Output BOOL I, Q, M, D, L Enable output IN Input Floating-point numbers I, Q, M, D, L, P or constant Input value OUT Output Floating-point numbers I, Q, M, D, L, P Exponential value of input value IN You can select the data type for the instruction from the "<???>" drop-down list of the instruction box. For additional information on valid data types, refer to "See also". Example The following example shows how the instruction works: 7DJ,Q 7DJB9DOXH (;3 5($/ (1 (12 ,1 287 7DJ2XW 7DJB5HVXOW If operand "TagIn" has the signal state "1", the "Form exponential value" instruction is executed. The instruction calculates the exponent from base e and the value of operand "Tag_Value" and sends the result to the "Tag_Result" output. If the instruction is executed without errors, the "TagOut" output is set. See also Overview of the valid data types (Page 1204) Basics of the EN/ENO mechanism (Page 1299) 1868 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References SIN: Form sine value Description Use the "Form sine value" instruction to calculate the sine of the angle. The size of the angle is specified in radians at the IN input. The result of the instruction is sent to the OUT output and can be queried there. The ENO enable output has the signal state "0" if one of the following conditions is fulfilled: The EN enable input has the signal state "0". The value at the IN input is not a valid floating-point number. Parameters The following table shows the parameters of the "Form sine value" instruction: Parameter Declaration Data type Memory area Description EN Input BOOL I, Q, M, D, L Enable input ENO Output BOOL I, Q, M, D, L Enable output IN Input Floating-point numbers I, Q, M, D, L, P or constant Size of angle in radians OUT Output Floating-point numbers I, Q, M, D, L, P Sine of the specified angle You can select the data type for the instruction from the "<???>" drop-down list of the instruction box. For additional information on valid data types, refer to "See also". Example The following example shows how the instruction works: 7DJ,Q 7DJB9DOXH 6,1 5($/ (1 (12 ,1 287 7DJ2XW 7DJB5HVXOW The following table shows how the instruction works using specific operand values: Parameter Operand Value IN Tag_Value +1.570796 (/2) OUT Tag_Result 1.0 If operand "TagIn" has the signal state "1", the "Form sine value" instruction is executed. The instruction calculates the sine of the angle specified at the "Tag_Value" input and stores the WinCC Basic V13.0 System Manual, 02/2014 1869 Programming the PLC 9.7 References result in the "Tag_Result" output. If the instruction is executed without errors, the "TagOut" output is set. See also Overview of the valid data types (Page 1204) Basics of the EN/ENO mechanism (Page 1299) COS: Form cosine value Description Use the "Form cosine value" instruction to calculate the cosine of the angle. The size of the angle is specified in radians at the IN input. The result of the instruction is sent to the OUT output and can be queried there. The ENO enable output has the signal state "0" if one of the following conditions is fulfilled: The EN enable input has the signal state "0". The value at the IN input is not a valid floating-point number. Parameters The following table shows the parameters of the "Form cosine value" instruction: Parameter Declaration Data type Memory area Description EN Input BOOL I, Q, M, D, L Enable input ENO Output BOOL I, Q, M, D, L Enable output IN Input Floating-point numbers I, Q, M, D, L, P or constant Size of angle in radians OUT Output Floating-point numbers I, Q, M, D, L, P Cosine of the specified angle You can select the data type for the instruction from the "<???>" drop-down list of the instruction box. For additional information on valid data types, refer to "See also". Example The following example shows how the instruction works: 7DJ,Q 7DJB9DOXH 1870 &26 5($/ (1 (12 ,1 287 7DJ2XW 7DJB5HVXOW WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References The following table shows how the instruction works using specific operand values: Parameter Operand Value IN Tag_Value +1.570796 (/2) OUT Tag_Result 0 If operand "TagIn" has the signal state "1", the "Form cosine value" instruction is executed. The instruction calculates the cosine of the angle specified at the "Tag_Value" input and stores the result in the "Tag_Result" output. If the instruction is executed without errors, the "TagOut" output is set. See also Overview of the valid data types (Page 1204) Basics of the EN/ENO mechanism (Page 1299) TAN: Form tangent value Description Use the "Form tangent value" instruction to calculate the tangent of the angle. The size of the angle is specified in radians at the IN input. The result of the instruction is sent to the OUT output and can be queried there. The ENO enable output has the signal state "0" if one of the following conditions is fulfilled: The EN enable input has the signal state "0". The value at the IN input is not a valid floating-point number. Parameters The following table shows the parameters of the "Form tangent value" instruction: Parameters Declaration Data type Memory area Description EN Input BOOL I, Q, M, D, L Enable input ENO Output BOOL I, Q, M, D, L Enable output IN Input Floating-point numbers I, Q, M, D, L, P or constant Size of angle in radians OUT Output Floating-point numbers I, Q, M, D, L, P Tangent of the specified angle You can select the data type for the instruction from the "<???>" drop-down list of the instruction box. For additional information on valid data types, refer to "See also". WinCC Basic V13.0 System Manual, 02/2014 1871 Programming the PLC 9.7 References Example The following example shows how the instruction works: 7$1 5($/ 7DJ,Q 7DJB9DOXH (1 (12 7DJ2XW ,1 287 7DJB5HVXOW The following table shows how the instruction works using specific operand values: Parameter Operand Value IN Tag_Value +3.141593 () OUT Tag_Result 0 If operand "TagIn" has the signal state "1", the "Form tangent value" instruction is executed. The instruction calculates the tangent of the angle specified at the "Tag_Value" input and stores the result in the "Tag_Result" output. If the instruction is executed without errors, the "TagOut" output is set. See also Overview of the valid data types (Page 1204) Basics of the EN/ENO mechanism (Page 1299) ASIN: Form arcsine value Description You can use the "Form arcsine value" instruction to calculate the size of the angle from the arcsine value specified at input IN, which corresponds to this value. Only valid floating-point numbers within the range -1 to +1 can be specified at the IN input. The calculated angle size is output in radians at the OUT output and can range in value from -/2 to +/2. The ENO enable output has the signal state "0" if one of the following conditions is fulfilled: The EN enable input has the signal state "0". The value at the IN input is not a valid floating-point number. The value at the IN input is outside the permitted value range (-1 to +1). 1872 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameters The following table shows the parameters of the "Form arcsine value" instruction: Parameters Declaration Data type Memory area Description EN Input BOOL I, Q, M, D, L Enable input ENO Output BOOL I, Q, M, D, L Enable output IN Input Floating-point numbers I, Q, M, D, L, P or constant Sine value OUT Output Floating-point numbers I, Q, M, D, L, P Size of angle in radians You can select the data type for the instruction from the "<???>" drop-down list of the instruction box. For additional information on valid data types, refer to "See also". Example The following example shows how the instruction works: 7DJ,Q 7DJB9DOXH $6,1 5($/ (1 (12 ,1 287 7DJ2XW 7DJB5HVXOW The following table shows how the instruction works using specific operand values: Parameters Operand Value IN Tag_Value 1.0 OUT Tag_Result +1.570796 (/2) If operand "TagIn" has the signal state "1", the "Form arcsine value" instruction is executed. The instruction calculates the size of the angle corresponding to the sine value at the "Tag_Value" input. The result of the instruction is stored in the "Tag_Result" output. If the instruction is executed without errors, the "TagOut" output is set. See also Overview of the valid data types (Page 1204) Basics of the EN/ENO mechanism (Page 1299) WinCC Basic V13.0 System Manual, 02/2014 1873 Programming the PLC 9.7 References ACOS: Form arccosine value Description You can use the "Form arccosine value" instruction to calculate the size of the angle from the cosine value specified at input IN, which corresponds to this value. Only valid floating-point numbers within the range -1 to +1 can be specified at the IN input. The calculated angle size is output in radians at the OUT output and can range in value from 0 to +. The ENO enable output has the signal state "0" if one of the following conditions is fulfilled: The EN enable input has the signal state "0". The value at the IN input is not a valid floating-point number. The value at the IN input is outside the permitted value range (-1 to +1). Parameters The following table shows the parameters of the "Form arccosine value" instruction: Parameters Declaration Data type Memory area Description EN Input BOOL I, Q, M, D, L Enable input ENO Output BOOL I, Q, M, D, L Enable output IN Input Floating-point numbers I, Q, M, D, L, P or constant Cosine value OUT Output Floating-point numbers I, Q, M, D, L, P Size of angle in radians You can select the data type for the instruction from the "<???>" drop-down list of the instruction box. For additional information on valid data types, refer to "See also". Example The following example shows how the instruction works: 7DJ,Q 7DJB9DOXH $&26 5($/ (1 (12 ,1 287 7DJ2XW 7DJB5HVXOW The following table shows how the instruction works using specific operand values: 1874 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameters Operand Value IN Tag_Value 0 OUT Tag_Result +1.570796 (/2) If operand "TagIn" has the signal state "1", the "Form arccosine value" instruction is executed. The instruction calculates the size of the angle corresponding to the cosine value at the "Tag_Value" input. The result of the instruction is stored in the "Tag_Result" output. If the instruction is executed without errors, the "TagOut" output is set. See also Overview of the valid data types (Page 1204) Basics of the EN/ENO mechanism (Page 1299) ATAN: Form arctangent value Description You can use the "Form arctangent value" instruction to calculate the size of the angle from the tangent value specified at input IN, which corresponds to this value. Only valid floating-point numbers may be specified at the IN input. The calculated angle size is output in radians at the OUT output and can range in value from -/2 to +/2. The ENO enable output has the signal state "0" if one of the following conditions is fulfilled: The EN enable input has the signal state "0". The value at the IN input is not a valid floating-point number. Parameters The following table shows the parameters of the "Form arctangent value" instruction: Parameters Declaration Data type Memory area Description EN Input BOOL I, Q, M, D, L Enable input ENO Output BOOL I, Q, M, D, L Enable output IN Input Floating-point numbers I, Q, M, D, L, P or constant Tangent value OUT Output Floating-point numbers I, Q, M, D, L, P Size of angle in radians You can select the data type for the instruction from the "<???>" drop-down list of the instruction box. For additional information on valid data types, refer to "See also". WinCC Basic V13.0 System Manual, 02/2014 1875 Programming the PLC 9.7 References Example The following example shows how the instruction works: 7DJ,Q 7DJB9DOXH $7$1 5($/ (1 (12 ,1 287 7DJ2XW 7DJB5HVXOW The following table shows how the instruction works using specific operand values: Parameters Operand Value IN Tag_Value 1.0 OUT Tag_Result +0.785398 (/4) If operand "TagIn" has the signal state"1", the "Form arctangent value" instruction is executed. The instruction calculates the size of the angle corresponding to the tangent value at the "Tag_Value" input. The result of the instruction is stored in the "Tag_Result" output. If the instruction is executed without errors, the "TagOut" output is set. See also Overview of the valid data types (Page 1204) Basics of the EN/ENO mechanism (Page 1299) FRAC: Return fraction Description You can use the "Return fraction" instruction to determine the decimal places of the value at the IN input. The result of the query is stored at the OUT output and can be queried there. If, for example, the IN input has the value 123.4567, the OUT output returns the value 0.4567. The ENO enable output has the signal state "0" if one of the following conditions is fulfilled: The EN enable input has the signal state "0". The value at input IN is not a valid floating-point number. 1876 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameters The following table shows the parameters of the "Return fraction" instruction: Parameter Declaration Data type Memory area Description EN Input BOOL I, Q, M, D, L Enable input ENO Output BOOL I, Q, M, D, L Enable output IN Input Floating-point numbers I, Q, M, D, L, P or constant Value, whose decimal places are to be determined. OUT Output Floating-point numbers I, Q, M, D, L, P Decimal places of the value at the IN input You can select the data type for the instruction from the "<???>" drop-down list of the instruction box. For additional information on valid data types, refer to "See also". Example The following example shows how the instruction works: 7DJ,QB 7DJ,QB 7DJB9DOXH )5$& 5($/ 7DJ2XW (1 (12 ,1 287 7DJB5HVXOW The following table shows how the instruction works using specific operand values: Parameter Operand Value IN Tag_Value 2.555 OUT Tag_Result 0.555 If operands "TagIn_1" and "TagIn_2" have the signal state "1", the "Return fraction" instruction is started. The decimal places from the value of operand "Tag_Value" are copied to operand "Tag_Result". If the instruction is executed without errors, the ENO output has the signal state "1" and the "TagOut" output is set. See also Overview of the valid data types (Page 1204) Basics of the EN/ENO mechanism (Page 1299) WinCC Basic V13.0 System Manual, 02/2014 1877 Programming the PLC 9.7 References EXPT: Exponentiate Description You can use the "Exponentiate" instruction to raise the value at the IN1 input to a power specified with the value at the IN2 input. The result of the instruction is provided at the OUT output and can be queried there (OUT =IN1IN2). The IN1 input can only be assigned valid floating-point numbers. Integers can also be assigned to the IN2 input. The ENO enable output has the signal state "0" if one of the following conditions is fulfilled: The EN enable input has the signal state "0". Errors occur during execution of the instruction, for example, an overflow occurs. Parameters The following table shows the parameters of the "Exponentiate" instruction: Parameter Declaration Data type Memory area Description EN Input BOOL I, Q, M, D, L Enable input ENO Output BOOL I, Q, M, D, L Enable output IN1 Input Floating-point numbers I, Q, M, D, L, P or constant Base value IN2 Input Integers, floatingpoint numbers I, Q, M, D, L, P or constant Value with which the base value is exponentiated OUT Output Floating-point numbers I, Q, M, D, L, P Result You can select the data type for the instruction from the "<???>" drop-down list of the instruction box. For additional information on valid data types, refer to "See also". Example The following example shows how the instruction works: (;37 7DJ,QB 7DJ,QB 5($/ 5($/ (1 (12 7DJB9DOXH ,1 287 7DJB9DOXH ,1 7DJ2XW 7DJB5HVXOW If operands "TagIn_1" and "TagIn_2" have the signal state "1", the "Exponentiate" instruction is started. The value of operand "Tag_Value1" is raised to a power specified with the value of operand "Tag_Value2". The result is stored in the "Tag_Result" output. If the instruction is 1878 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References executed without errors, the ENO enable output has the signal state "1" and the "TagOut" output is set. See also Overview of the valid data types (Page 1204) Basics of the EN/ENO mechanism (Page 1299) Move operations MOVE: Move value Description You use the "Move value" instruction to transfer the content of the operand at the IN input to the operand at the OUT1 output. The transfer is always made in the direction of ascending address. The ENO enable output has the signal state "0" if one of the following conditions is fulfilled: The EN enable input has the signal state "0". The data type at the IN parameter does not correspond to the specified data type at the OUT1 parameter. The following table lists the possible transfers for the S7-1200 CPU series: Source (IN) WinCC Basic V13.0 System Manual, 02/2014 Destination (OUT1) With IEC check Without IEC check BYTE BYTE, WORD, DWORD BYTE, WORD, DWORD, SINT, USINT, INT, UINT, DINT, UDINT, TIME, DATE ,TOD, CHAR WORD WORD, DWORD BYTE, WORD, DWORD, SINT, USINT, INT, UINT, DINT, UDINT, TIME, DATE, TOD, CHAR DWORD DWORD BYTE, WORD, DWORD, SINT, USINT, INT, UINT, DINT, UDINT, REAL, TIME, DATE, TOD, CHAR SINT SINT BYTE, WORD, DWORD, SINT, USINT, INT, UINT, DINT, UDINT, TIME, DATE, TOD USINT USINT, UINT, UDINT BYTE, WORD, DWORD, SINT, USINT, INT, UINT, DINT, UDINT, TIME, DATE, TOD INT INT BYTE, WORD, DWORD, SINT, USINT, INT, UINT, DINT, UDINT, TIME, DATE, TOD UINT UINT, UDINT BYTE, WORD, DWORD, SINT, USINT, INT, UINT, DINT, UDINT, TIME, DATE, TOD DINT DINT BYTE, WORD, DWORD, SINT, USINT, INT, UINT, DINT, UDINT, TIME, DATE, TOD UDINT UDINT BYTE, WORD, DWORD, SINT, USINT, INT, UINT, DINT, UDINT, TIME, DATE, TOD REAL REAL DWORD, REAL 1879 Programming the PLC 9.7 References Source (IN) Destination (OUT1) With IEC check Without IEC check LREAL LREAL LREAL TIME TIME BYTE, WORD, DWORD, SINT, USINT, INT, UINT, DINT, UDINT, TIME DATE DATE BYTE, WORD, DWORD, SINT, USINT, INT, UINT, DINT, UDINT, DATE TOD TOD BYTE, WORD, DWORD, SINT, USINT, INT, UINT, DINT, UDINT, TOD DTL DTL DTL CHAR CHAR BYTE, WORD, DWORD, CHAR, Character of a string1) Character of a string1) Character of a string Character of a string CHAR ARRAY2) ARRAY ARRAY STRUCT STRUCT STRUCT PLC data type (UDT) PLC data type (UDT) PLC data type (UDT) IEC_TIMER IEC_TIMER IEC_TIMER IEC_SCOUNTE IEC_SCOUNTER R IEC_SCOUNTER IEC_USCOUNT IEC_USCOUNTER ER IEC_USCOUNTER IEC_COUNTER IEC_COUNTER IEC_COUNTER IEC_UCOUNTE IEC_UCOUNTER R IEC_UCOUNTER IEC_DCOUNTE IEC_DCOUNTER R IEC_DCOUNTER IEC_UDCOUN TER IEC_UDCOUNTER IEC_UDCOUNTER The following table lists the possible transfers for the S7-1500 CPU series: Source (IN) 1880 Destination (OUT1) With IEC check Without IEC check BYTE BYTE, WORD, DWORD, LWORD BYTE, WORD, DWORD, LWORD, SINT, USINT, INT, UINT, DINT, UDINT, LINT, ULINT, TIME, LTIME, LDT, DATE ,TOD, LTOD, CHAR WORD WORD, DWORD, LWORD BYTE, WORD, DWORD, LWORD, SINT, USINT, INT, UINT, DINT, UDINT, LINT, ULINT, S5TIME, TIME, LTIME, LDT, DATE, TOD, LTOD, CHAR DWORD DWORD, LWORD BYTE, WORD, DWORD, LWORD, SINT, USINT, INT, UINT, DINT, UDINT, LINT, ULINT, REAL, TIME, LTIME, LDT, DATE, TOD, LTOD, CHAR LWORD LWORD BYTE, WORD, DWORD, LWORD, SINT, USINT, INT, UINT, DINT, UDINT, LINT, ULINT, LREAL, TIME, LTIME, LDT, DATE, TOD, LTOD, CHAR WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Source (IN) WinCC Basic V13.0 System Manual, 02/2014 Destination (OUT1) With IEC check Without IEC check SINT SINT BYTE, WORD, DWORD, LWORD, SINT, USINT, INT, UINT, DINT, UDINT, LINT, ULINT, TIME, LTIME, LDT, DATE, TOD, LTOD USINT USINT, UINT, UDINT, ULINT BYTE, WORD, DWORD, LWORD, SINT, USINT, INT, UINT, DINT, UDINT, LINT, ULINT, TIME, LTIME, LDT, DATE, TOD, LTOD INT INT BYTE, WORD, DWORD, LWORD, SINT, USINT, INT, UINT, DINT, UDINT, LINT, ULINT, TIME, LTIME, LDT, DATE, TOD, LTOD UINT UINT, UDINT, ULINT BYTE, WORD, DWORD, LWORD, SINT, USINT, INT, UINT, DINT, UDINT, LINT, ULINT, TIME, LTIME, LDT, DATE, TOD. LTOD DINT DINT BYTE, WORD, DWORD, LWORD, SINT, USINT, INT, UINT, DINT, UDINT, LINT, ULINT, TIME, LTIME, LDT, DATE, TOD, LTOD UDINT UDINT, ULINT BYTE, WORD, DWORD, LWORD, SINT, USINT, INT, UINT, DINT, UDINT, LINT, ULINT, TIME, LTIME, LDT, DATE, TOD, LTOD LINT LINT BYTE, WORD, DWORD, LWORD, SINT, USINT, INT, UINT, DINT, UDINT, LINT, ULINT, TIME, LTIME, LDT, DATE, TOD, LTOD ULINT ULINT BYTE, WORD, DWORD, LWORD, SINT, USINT, INT, UINT, DINT, UDINT, LINT, ULINT, TIME, LTIME, LDT, DATE, TOD, LTOD REAL REAL DWORD, REAL LREAL LREAL LWORD, LREAL S5TIME S5TIME WORD, S5TIME TIME TIME BYTE, WORD, DWORD, LWORD, SINT, USINT, INT, UINT, DINT, UDINT, LINT, ULINT, TIME LTIME LTIME BYTE, WORD, DWORD, LWORD, SINT, USINT, INT, UINT, DINT, UDINT, LINT, ULINT, LTIME DATE DATE BYTE, WORD, DWORD, LWORD, SINT, USINT, INT, UINT, DINT, UDINT, LINT, ULINT, DATE DT DT DT LDT LDT BYTE, WORD, DWORD, LWORD, SINT, USINT, INT, UINT, DINT, UDINT, LINT, ULINT, LDT TOD TOD BYTE, WORD, DWORD, LWORD, SINT, USINT, INT, UINT, DINT, UDINT, LINT, ULINT, TOD LTOD LTOD BYTE, WORD, DWORD, LWORD, SINT, USINT, INT, UINT, DINT, UDINT, LINT, ULINT, LTOD DTL DTL DTL CHAR CHAR BYTE, WORD, DWORD, LWORD, CHAR, Character of a string1) WCHAR WCHAR BYTE, WORD, DWORD, LWORD, CHAR, WCHAR, Character of a string1) Character of a string1) Character of a string CHAR, WCHAR, Character of a string 1881 Programming the PLC 9.7 References Source (IN) Destination (OUT1) With IEC check Without IEC check ARRAY2) ARRAY ARRAY STRUCT STRUCT STRUCT COUNTER COUNTER, WORD, INT WORD, DWORD, INT, UINT, DINT, UDINT TIMER TIMER, WORD, INT WORD, DWORD, INT, UINT, DINT, UDINT PLC data type (UDT) PLC data type (UDT) PLC data type (UDT) IEC_TIMER IEC_TIMER IEC_TIMER IEC_LTIMER IEC_LTIMER IEC_LTIMER IEC_SCOUNTE IEC_SCOUNTER R IEC_SCOUNTER IEC_USCOUNT IEC_USCOUNTER ER IEC_USCOUNTER IEC_COUNTER IEC_COUNTER IEC_COUNTER IEC_UCOUNTE IEC_UCOUNTER R IEC_UCOUNTER IEC_DCOUNTE IEC_DCOUNTER R IEC_DCOUNTER IEC_UDCOUN TER IEC_UDCOUNTER IEC_UDCOUNTER IEC_LCOUNTE R IEC_LCOUNTER IEC_LCOUNTER IEC_ULCOUNT IEC_ULCOUNTER ER IEC_ULCOUNTER You can also use the "Move value" instruction to transfer individual characters of a string to operands of the CHAR or WCHAR data type. The number of the character to be transferred is specified in square brackets next to the operand name. "MyString[2]", for example, transfers the second character of the "MyString" string. It is also possible to transfer from operands of the data type CHAR to the individual characters of a string. You can also replace a specific character of a string with the character of another string. 1) Transferring entire arrays (ARRAY) is possible only when the array components of the operands at input IN and at output OUT1 are of the same data type. 2) If the bit length of the data type at input IN exceeds the bit length of the data type at output OUT1, the higher-order bits of the source value are lost. If the bit length of the data type at input IN is less than the bit length of the data type at output OUT1, the higher-order bits of the destination value will be overwritten with zeros. In its initial state, the instruction box contains 1 output (OUT1). The number of outputs can be extended. The added outputs are numbered in ascending order on the box. During the execution of the instruction, the content of the operand at the input IN is transferred to all available outputs. The instruction box cannot be extended if structured data types (DTL, STRUCT, ARRAY) or characters of a string are transferred. You can also use the "Move block" (MOVE_BLK) and "Move block uninterruptible" (UMOVE_BLK) instructions to move operands of the ARRAY data type. You can move operands of the STRING data type with the instruction "Move character string" (S_MOVE). 1882 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameter The following table lists the parameters of the "Move value" instruction: Parameters Declaration Data type S7-1200 S7-1500 Memory area Description EN Input BOOL BOOL I, Q, M, D, L Enable input ENO Output BOOL BOOL I, Q, M, D, L Enable output IN Input Bit strings, integers, floating-point numbers, DATE, TIME, TOD, DTL, CHAR, STRUCT, ARRAY, IEC data types, PLC data type (UDT) Bit strings, integers, floating-point numbers, DATE, DT, LDT, S5TIME, TIME, LTIME, TOD, LTOD, DTL, CHAR, STRUCT, ARRAY, TIMER, COUNTER, IEC data types, PLC data type (UDT) I, Q, M, D, L or constant Source value OUT1 Output Bit strings, integers, floating-point numbers, DATE, TIME, TOD, DTL, CHAR, STRUCT, ARRAY, IEC data types, PLC data type (UDT) Bit strings, integers, floating-point numbers, DATE, DT, LDT, S5TIME, TIME, LTIME, TOD, LTOD, DTL, CHAR, STRUCT, ARRAY, TIMER, COUNTER, IEC data types, PLC data type (UDT) I, Q, M, D, L Operands to which in the source value is transferred. For additional information on valid data types, refer to "See also". WinCC Basic V13.0 System Manual, 02/2014 1883 Programming the PLC 9.7 References Example The following example shows how the instruction works: 7DJ,Q 7DJ,QB9DOXH 029( (1 (12 ,1 287 7DJ2XW 7DJ2XWB9DOXH The following table shows how the instruction works using specific operand values: Parameters Operand Value IN TagIn_Value 0011 1111 1010 1111 OUT1 TagOut_Value 0011 1111 1010 1111 If the operand "TagIn" has the signal state "1", the "Move value" instruction is executed. The instruction copies the contents of operand "TagIn_Value" to operand "TagOut_Value" and sets output "TagOut" to signal state "1". See also Overview of the valid data types (Page 1204) Removing inputs and outputs (Page 1429) Basics of the EN/ENO mechanism (Page 1299) MOVE_BLK: Move block (Page 1894) UMOVE_BLK: Move block uninterruptible (Page 1900) S_MOVE: Move character string (Page 2521) Inserting additional inputs and outputs in LAD elements (Page 1428) Deserialize: Deserialize Description You can use the "Deserialize" instruction to convert the sequential representation of a PLC data type (UDT) back to a PLC data type and to fill its entire contents. The memory area in which the sequential representation of a PLC data type is located must have the ARRAY of BYTE data type and be declared with standard access. Make sure that there is enough memory space prior to the conversion. 1884 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References The instruction enables you can convert multiple sequential representations of converted PLC data types back to their original state step-by-step. Note If you only want to convert back a single sequential representation of a PLC data type (UDT), you can also direct the instruction "TRCV: Receive data via communication connection". Parameters The following table lists the parameters of the "Deserialize" instruction: Parameters Declaration Data type Memory area Description EN Input BOOL I, Q, M, D, L Enable input ENO Output BOOL I, Q, M, D, L Enable output SRC_ARRA Y Input VARIANT I, Q, D, L Global data block in which the generated data stream is stored DEST_VARI ABLE InOut VARIANT I, Q, D, L Tag in which the returned converted PLC data type (UDT) is stored POS InOut DINT I, Q, M, D, L Number of bytes that the converted PLC data types use. The POS parameter is calculated zero-based. RET_VAL Output INT I, Q, M, D, L Error information For additional information on valid data types, refer to "See also". RET_VAL parameter The following table shows the meaning of the values of the RET_VAL parameter: Error code* (W#16#...) Explanation 0000 No error 80B0 The memory areas for the SRC_ARRAY and DEST_VARIABLE parameters overlap. 8136 The data block at the DEST_VARIABLE parameter is not a block with standard access. 8150 The VARIANT data type at the SRC_ARRAY parameter contains no value. 8151 Code generation error at the SRC_ARRAY parameter 8153 There is not enough free memory available at the SRC_ARRAY parameter. 8250 The VARIANT data type at the DEST_VARIABLE parameter contains no value. 8251 Code generation error at the DEST_VARIABLE parameter 8254 Invalid data type in the DEST_VARIABLE parameter. WinCC Basic V13.0 System Manual, 02/2014 1885 Programming the PLC 9.7 References Error code* (W#16#...) Explanation 8382 The value at the POS parameter is outside the limits of the array. *The error codes can be displayed as integer or hexadecimal value in the program editor. For information on toggling display formats, refer to "See also". Example The following example shows how the instruction works: Network 1: 029( 'HVHULDOL]H (1 (12 ,1 287 (12 (1 %XIIHU3RV %XIIHU)LHOG %XIIHU3RV 5(7B9$/ 65&B$55$< 326 '(67B9$5,$%/( (UURU 7DUJHW&OLHQW The "Move value" instruction copies the value "0" to the "#BufferPos" operand. The "Deserialize" instruction deserializes the sequential representation of the customer data from the "Buffer" data block and writes it to the "Target" data block. The number of bytes that show the converted customer data is stored in the "#BufferPos" operand. Network 2: 'HVHULDOL]H (1 %XIIHU)LHOG %XIIHU3RV 65&B$55$< 326 'HVHULDOL]H DUWL (12 5(7B9$/ (UURU '(67B9$5,$%/( /DEHO /DEHO %XIIHU)LHOG %XIIHU3RV 5(7B9$/ 65&B$55$< '(67B9$5,$%/( 326 'HVHULDOL]H %LOO (12 (1 675,1* /DEHO (12 (1 675,1* %XIIHU)LHOG %XIIHU3RV 5(7B9$/ 65&B$55$< 326 '(67B9$5,$%/( The "Deserialize" instruction deserializes the sequential representation of the separator sheet, which was saved with the sequential representation after the customer data, from the "Buffer" data block and writes the characters to the "#Label" operand. The characters are compared using comparison instructions "arti" and "Bill". If the comparison for "arti" = TRUE, then this is article data that has been deserialized and written to the "Target" data block. If the comparison for "Bill" = TRUE, then this is billing data that has been deserialized and written to the "Target" data block. 1886 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References The following table lists the declaration of the operands: Operand Data type Declaration DeliverPos INT In the "Input" section of the block interface BufferPos DINT In the "Temp" section of the block interface Error INT In the "Temp" section of the block interface Label STRING[4] In the "Temp" section of the block interface The following table lists the declarations of the PLC data types: Name the PLC data types Name Data type Article Number DINT Declaration STRING Colli INT Title INT First name STRING[10] Surname STRING[10] Client The following table lists the declaration of the data blocks: Name of the data blocks Name Data type Target Client "Client" (PLC data type) Article Array[0..] of "Article" (PLC data type) Bill Array[0..10] of INT Field Array[0..294] of BYTE Buffer See also Overview of the valid data types (Page 1204) Basics of the EN/ENO mechanism (Page 1299) PLC data types (Page 1248) Inserting additional inputs and outputs in LAD elements (Page 1428) Serialize: Serialize Description You can use the "Serialize" instruction to convert several PLC data types (UDT) to a sequential representation without losing parts of their structure. You can use the instruction to cache multiple structured data from your program in a buffer, which is preferably in a global data block, and send it to another CPU. The memory area in which the converted PLC data types must be stored must have the ARRAY of BYTE data type and be declared with standard access. Make sure that there is enough memory space prior to the conversion. WinCC Basic V13.0 System Manual, 02/2014 1887 Programming the PLC 9.7 References The operand at the POS parameter contains information about how many bytes the converted PLC data types occupy. Note If you want to send a single PLC data type (UDT), you can directly call the instruction "TSEND: Send data via communication connection". Parameters The following table lists the parameters of the "Serialize" instruction: Parameters Declarati on Data type Memory area Description EN Input BOOL I, Q, M, D, L Enable input ENO Output BOOL I, Q, M, D, L Enable output SRC_VARI ABLE Input VARIA NT I, Q, D, L PLC data type (UDT) that is converted to sequential representation. DEST_ARR InOut AY VARIA NT I, Q, D, L Data block in which the generated data stream is stored. POS InOut DINT I, Q, M, D, L Number of bytes that the converted PLC data types use. The POS parameter is calculated zero-based. RET_VAL Output INT I, Q, M, D, L Error information For additional information on valid data types, refer to "See also". RET_VAL parameter The following table shows the meaning of the values of the RET_VAL parameter: Error code* (W#16#...) Explanation 0000 No error 80B0 The memory areas for the SRC_VARIABLE and DEST_ARRAY parameters overlap. 8150 The VARIANT data type at the SRC_VARIABLE parameter contains no value. 8152 Code generation error at the SRC_VARIABLE parameter 8236 The data block at the DEST_ARRAY parameter is not a block with standard access. 8250 The VARIANT data type at the DEST_ARRAY parameter contains no value. 8252 Code generation error at the DEST_ARRAY parameter 8253 There is not enough free memory available at the DEST_ARRAY parameter. 8254 Invalid data type in the DEST_ARRAY parameter. 1888 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Error code* (W#16#...) Explanation 8382 The value at the POS parameter is outside the limits of the array. *The error codes can be displayed as integer or hexadecimal value in the program editor. For information on toggling display formats, refer to "See also". Example The following example shows how the instruction works: Network 1: 029( 6HULDOL]H (1 (12 ,1 287 (12 (1 %XIIHU3RV 6RXUFH&OLHQW %XIIHU3RV 5(7B9$/ 65&B9$5,$%/( '(67B$55$< 326 (UURU %XIIHU)LHOG The "Move value" instruction copies the value "0" to the "#BufferPos" operand. The "Serialize" instruction serializes the customer data from the "Source" data block and writes it in sequential representation to the "Buffer" data block. The number of bytes occupied by the sequential representation is stored in the "#BufferPos" operand. Network 2: 6B029( DUWL (1 (12 ,1 287 6HULDOL]H (1 /DEHO /DEHO %XIIHU3RV 65&B9$5,$%/( 326 (12 5(7B9$/ '(67B$55$< (UURU %XIIHU)LHOG A kind of separator sheet is inserted now to later make it easier to deserialize the sequential representation. The "Move string" instruction copies the "arti" characters to the "#Label" operand. The "Serialize" instruction writes these characters after the customer data to the "Buffer" data block. The number of bytes that the characters need in addition to the number already stored are added to the "#BufferPos" operand. Network 3: WinCC Basic V13.0 System Manual, 02/2014 1889 Programming the PLC 9.7 References 6HULDOL]H (1 6RXUFH $UWLFOH>'HOLYHU3RV@ 65&B9$5,$%/( 326 %XIIHU3RV (12 5(7B9$/ '(67B$55$< (UURU %XIIHU)LHOG The "Serialize" instruction serializes the data of a specific article, which is calculated in runtime, from the "Source" data block and writes it in sequential representation to the "Buffer" data block after the "arti" characters. The following table lists the declaration of the operands: Operand Data type Declaration DeliverPos INT In the "Input" section of the block interface BufferPos DINT In the "Temp" section of the block interface Error INT In the "Temp" section of the block interface Label STRING[4] In the "Temp" section of the block interface The following table lists the declarations of the PLC data types: Name the PLC data types Name Data type Article Number DINT Declaration STRING Colli INT Title INT First name STRING[10] Surname STRING[10] Client The following table lists the declaration of the data blocks: Name of the data blocks Name Data type Source Client "Client" (PLC data type) Article Array[0..10] of "Article" (PLC data type) Field Array[0..294] of BYTE Buffer See also Overview of the valid data types (Page 1204) Basics of the EN/ENO mechanism (Page 1299) PLC data types (Page 1248) Inserting additional inputs and outputs in LAD elements (Page 1428) 1890 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References FieldRead: Read field Description You can use the "Read field" instruction to read out a specific component from the field specified at input MEMBER and transfer its content to the tag at output VALUE. You specify the index of the field component to be read at input INDEX. Specify the first component of the field from which reading is to occur at input MEMBER. The data types of the field component at input MEMBER and the tags at output VALUE must correspond to the data type of the instruction "Read field". The ENO enable output has the signal state "0" if one of the following conditions is fulfilled: The EN enable input has the signal state "0". The field component specified at input INDEX is not defined in the field specified at output MEMBER. Errors such as an overflow occur during execution. Parameters The following table shows the parameters of the "Read field" instruction: Parameter Declaration Data type S7-1200 S7-1500 Memory area Description Enable input EN Input BOOL BOOL I, Q, M, D, L ENO Output BOOL BOOL I, Q, M, D, L Enable output INDEX Input DINT DINT I, Q, M, D, L, P or constant Index of field component whose content is read out MEMBER Input Binary numbers, integers, floating-point numbers, TIME, DATE, TOD and CHAR as components of an ARRAY tag Binary numbers, integers, floating-point numbers, timers, DATE, TOD, LTOD and CHAR as components of an ARRAY tag D, L First component of the field from which reading occurs. VALUE Output Bit strings, integers, floating-point numbers, TIME, DATE, TOD and CHAR Bit strings, integers, floating-point numbers, timers, DATE, TOD, LTOD and CHAR I, Q, M, D, L, P Operand to which the content of the field component is transferred You can select the data type for the instruction from the "<???>" drop-down list of the instruction box. WinCC Basic V13.0 System Manual, 02/2014 1891 Programming the PLC 9.7 References For additional information on valid data types, refer to "See also". Example The following example shows how the instruction works: )LHOG5HDG 5($/ (1 DBLQGH[ '%B 0DLQB)LHOG>@ ,1'(; 4 (12 9$/8( DBUHDO 0(0%(5 The following table shows how the instruction works using specific operand values: Parameters Tag Value INDEX a_index 4 MEMBER "DB_1".Main_Field[-10] First component of the "Main_Field[-10..10] of REAL" field in the "DB_1" data block VALUE a_real Component with index 4 of the "Main_Field[-10..10] of REAL" field The field component with index 4 is read from the "Main_Field[-10...10] of REAL" field and written to the "a_real" tag. The field component to be read is specified by the value at input INDEX. See also Overview of the valid data types (Page 1204) Basics of the EN/ENO mechanism (Page 1299) FieldWrite: Write field Description The "Write field" instruction is used to transfer the content of the tag at the VALUE input to a specific component of the field at the MEMBER output. You use the value at the INDEX input to specify the index of the field component that is described. At the MEMBER output, enter the first component of the field which is to be written to. The data types of the field component specified at the MEMBER output and the tags at the VALUE input have to match the data type of the "Write field" instruction. The ENO enable output has the signal state "0" if one of the following conditions is fulfilled: 1892 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References The EN enable input has the signal state "0". The field component specified at the input INDEX is not defined in the field specified at the output MEMBER. Errors such as an overflow occur during execution. Parameters The following table shows the parameters of the "Write field" instruction: Parameter Declaration Data type S7-1200 S7-1500 Memory area Description EN Input BOOL BOOL I, Q, M, D, L Enable input ENO Output BOOL BOOL I, Q, M, D, L Enable output INDEX Input DINT DINT I, Q, M, D, L, P or constant Index of the field component that is being written with the content of VALUE. VALUE Input Bit strings, integers, floating-point numbers, TIME, DATE, TOD and CHAR Bit strings, integers, floating-point numbers, timers, DATE, TOD, LTOD and CHAR I, Q, M, D, L, P or constant Operand whose content is copied. MEMBER Output Binary numbers, integers, floating-point numbers, TIME, DATE, TOD and CHAR as components of an ARRAY tag Binary numbers, integers, floating-point numbers, timers, DATE, TOD, LTOD and CHAR as components of an ARRAY tag D, L First component of the field to which the content of VALUE is written. You can select the data type for the instruction from the "<???>" drop-down list of the instruction box. For additional information on valid data types, refer to "See also". WinCC Basic V13.0 System Manual, 02/2014 1893 Programming the PLC 9.7 References Example The following example shows how the instruction works: )LHOG:ULWH 5($/ (1 DBLQGH[ ,1'(; DBUHDO 9$/8( 4 (12 0(0%(5 '%B 0DLQB)LHOG>@ The following table shows how the instruction works using specific operand values: Parameters Operand Value INDEX a_index 4 VALUE a_real 10.54 MEMBER "DB_1".Main_Field[-10] First component of the "Main_Field[-10..10] of REAL" field in the "DB_1" data block The value "10.54" of the "a_real" tag is written to the field component with index 4 of the "Main_Field[-10..10] of REAL" field. The index of the field component to which the content of the tag "a_real" is transferred is specified by the value at the input INDEX. See also Overview of the valid data types (Page 1204) Basics of the EN/ENO mechanism (Page 1299) MOVE_BLK: Move block Description You can use the "Move block" instruction to move the content of a memory area (source area) to another memory area (destination area). The number of elements to be moved to the destination area is specified at input COUNT. The width of the elements to be moved is defined by the width of the element at the IN input. The instruction can only be executed if the source area and the destination area are of the same data type. The ENO enable output has the signal state "0" if one of the following conditions is fulfilled: The EN enable input has the signal state "0". More data is copied than is made available at the IN input or OUT output. When a Array of BOOL is copied, the enable output ENO for an overflow is set to "1" until the byte limit of the ARRAY structure is exceeded. If the byte limit of the ARRAY structure is exceeded by the value at the COUNT input, the ENO enable output is reset to "0". 1894 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameters The following table lists the parameters of the "Move block" instruction: Parameter Declaration Data type S7-1200 S7-1500 Memory area Description EN Input BOOL BOOL I, Q, M, D, L Enable input ENO Output BOOL BOOL I, Q, M, D, L Enable output IN 1) Input Binary numbers, integers, floating-point numbers, TIME, DATE, CHAR, TOD Binary numbers, integers, floating-point numbers, timers, DATE, TOD, LTOD D, L The first element of the source area that is being copied COUNT Input USINT, UINT, UDINT USINT, UINT, UDINT, ULINT I, Q, M, D, L, P or constant Number of elements to be copied from the source area to the destination area. OUT 1) Output Binary numbers, integers, floating-point numbers, TIME, DATE, CHAR, TOD Binary numbers, integers, floating-point numbers, timers, DATE, TOD, LTOD D, L The first element of the destination area to which the contents of the source area are being copied 1) The specified data types can only be used as elements of an ARRAY structure. For additional information on valid data types, refer to "See also". Example The following example shows how the instruction works: 7DJ,QB 7DJ,QB DBDUUD\>@ 7DJB&RXQW 029(B%/. (1 (12 ,1 287 7DJ2XW EBDUUD\>@ &2817 The following table shows how the instruction works using specific operand values: WinCC Basic V13.0 System Manual, 02/2014 1895 Programming the PLC 9.7 References Parameter Operand Value IN a_array[2] The data type of the a_array operand is Array [0..5] of INT. It consists of six elements of data type INT. COUNT Tag_Count 3 OUT b_array[1] The data type of the b_array operand is Array [0..6] of INT. It consists of seven elements of data type INT. If operands "TagIn_1" and "TagIn_2" have the signal state "1", the "Move block" instruction is executed. Starting from the third element, the instruction selects three INT elements from the #a_array tag and copies their contents to the #b_array output tag, beginning with the second element. If the instruction is executed without errors, the ENO enable output has the signal state "1" and the "TagOut" output is set. See also Overview of the valid data types (Page 1204) Basics of the EN/ENO mechanism (Page 1299) Inserting additional inputs and outputs in LAD elements (Page 1428) MOVE_BLK_VARIANT: Move block Description You can use the "Move block" instruction to move the content of a memory area (source area) to another memory area (destination area). You can copy elements of an array to another array of the same data type. The size (number of elements) of the source and destination array may be different. You can copy several elements within an array or individual elements. If you are using the instruction, the array must not yet be known at the time the block is created, as the source and the destination are transferred using VARIANT. The counting at the parameters SRC_INDEX and DEST_INDEX always starts with the low limit "0", regardless of the later declaration of the array. If the VARIANT pointer (source or destination) is of the data type BOOL, it must be addressed absolutely and the length specified must be divisible by 8; otherwise the instruction is not executed. The ENO enable output has the signal state "0" if one of the following conditions is fulfilled: The EN enable input has the signal state "0". More data is copied than is made available. 1896 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameters The following table lists the parameters of the "Move block" instruction: Parameter Declaration Data type Memory area Description EN Input BOOL I, Q, M, D, L Enable input ENO Output BOOL I, Q, M, D, L Enable output SRC Input VARIANT (array or single element) L Source block from which to copy COUNT Input UDINT I, Q, M, D, L or constant Number of elements which are copied Set the value at the parameter COUNT to "1", if no Array is specified at the parameter SRC or the parameter DEST. SRC_INDEX Input DINT I, Q, M, D, L or constant The SRC_INDEX parameter is calculated zerobased. If an Array is specified at parameter SRC, the integer at the SRC_INDEX parameter specifies the first element within the source area from which copying is to take place. This is independent of the declared array limits. If no Array is set at the SRC parameter or only an individual element of an array is specified, assign the SRC_INDEX parameter the value "0". WinCC Basic V13.0 System Manual, 02/2014 1897 Programming the PLC 9.7 References Parameter Declaration Data type Memory area DEST_INDEX Input DINT I, Q, M, D, L or constant The DEST_INDEX parameter is calculated zerobased. If an Array is specified at the DEST parameter, the integer at the DEST_INDEX parameter specifies the first element within the destination area to which copying is to take place. This is independent of the declared array limits. Description If no Array is specified at the DEST parameter, assign the DEST_INDEX parameter the value "0". DEST Output VARIANT L Destination area into which the contents of the source block are copied. RET_VAL Output INT I, Q, M, D, L Error information: If an error occurs during the execution of the instruction, an error code is output at the RET_VAL parameter. For additional information on valid data types, refer to "See also". RET_VAL parameter The following table lists the meaning of the values of the RET_VAL parameter: Error code* Explanation (W#16#...) 1898 0000 No error 80B4 Data types do not correspond 8151 Access to the SRC parameter is not possible. 8152 The operand at the SRC parameter is not typed. 8153 Code generation error at the SRC parameter 8154 The operand at the SRC parameter has the data type BOOL. 8281 The COUNT parameter has an invalid value WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Error code* Explanation (W#16#...) 8382 The value at the SRC_INDEX parameter is outside the limits of the VARIANT. 8383 The value at the SRC_INDEX parameter is outside the high limit of the array. 8482 The value at the DEST_INDEX parameter is outside the limits of the VARIANT. 8483 The value at the DEST_INDEX parameter is outside the high limit of the array. 8534 The DEST parameter is write protected 8551 Access to the DEST parameter is not possible. 8552 The operand at the DEST parameter is not typed. 8553 Code generation error at the DEST parameter 8554 The operand at the DEST parameter has the data type BOOL. *The error codes can be displayed as integer or hexadecimal value in the program editor. For information on toggling display formats, refer to "See also". Example The following example shows how the instruction works: 7DJ,Q 6UF)LHOG 7DJB&RXQW 029(B%/.B9$5,$17 (1 (12 7DJ2XW 65& &2817 5(7B9$/ 7DJB6UFB,QGH[ 65&B,1'(; '(67 7DJB'HVWB,QGH[ '(67B,1'(; 7DJB5HVXOW 'HVW)LHOG The following table shows how the instruction works using specific operand values: WinCC Basic V13.0 System Manual, 02/2014 Parameter Operand Value SRC #SrcField The local operand #SrcField uses a UDT that was still unknown at the time when the block was programmed. (Array [0 to 10] of "MOVE_UDT" COUNT Tag_Count 2 SRC_INDEX Tag_Src_Index 3 DEST_INDEX Tag_Dest_Index 3 DEST #DestField The local operand #DestField uses a UDT that was still unknown at the time when the block was programmed. (Array [10 to 20] of "MOVE_UDT" 1899 Programming the PLC 9.7 References If the operand "TagIn" has the signal state "1", the "Move block" instruction is executed. 2 elements are copied from the source area into the destination area beginning with the fourth element of the array of UDT. The copies are inserted in the array of UDT beginning with the fourth element. If the instruction is executed without errors, the ENO enable output has the signal state "1" and the "TagOut" output is set. See also Overview of the valid data types (Page 1204) Basics of the EN/ENO mechanism (Page 1299) VariantGet: Read out VARIANT tag value (Page 1919) Inserting additional inputs and outputs in LAD elements (Page 1428) UMOVE_BLK: Move block uninterruptible Description You can use the "Move block uninterruptible" instruction to move the content of a memory area (source area) to another memory area (destination area). The number of elements to be moved to the destination area is specified with the COUNT parameter. The width of the elements to be moved is defined by the width of the element at the IN input. The instruction can only be executed if the source area and the destination area have the same data type. Note The copy operation cannot be interrupted by other operating system activities. This is why the interrupt reaction times of the CPU increase during the execution of the "Move block uninterruptible" instruction. The ENO enable output has the signal state "0" if one of the following conditions is fulfilled: The EN enable input has the signal state "0". More data is copied than is made available at the IN input or OUT output. When a Array of BOOL is copied, the enable output ENO for an overflow is set to "1" until the byte limit of the ARRAY structure is exceeded. If the byte limit of the ARRAY structure is exceeded by the value at the COUNT input, the ENO enable output is reset to "0". You can use the "Move block uninterruptible" instruction to move a maximum of 16 KB. Note the CPU-specific restrictions for this. 1900 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameters The following table shows the parameters of the "Move block uninterruptible" instruction: Parameter EN Declaration Input Data type S7-1200 S7-1500 BOOL BOOL Memory area Description I, Q, M, D, L Enable input ENO Output BOOL BOOL I, Q, M, D, L Enable output IN 1) Input Binary numbers, integers, floating-point numbers, TIME, DATE, CHAR, TOD Binary numbers, integers, floating-point numbers, timers, DATE, TOD, LTOD D, L The first element of the source area that is being copied COUNT Input USINT, UINT, UDINT USINT, UINT, UDINT, ULINT I, Q, M, D, L, P or constant Number of elements to be moved from the source area to the destination area. OUT 1) Output Binary numbers, integers, floating-point numbers, TIME, DATE, CHAR, TOD Binary numbers, integers, floating-point numbers, timers, DATE, TOD, LTOD D, L The first element of the destination area to which the contents of the source area are being copied 1) The specified data types can only be used as elements of an ARRAY structure. For additional information on valid data types, refer to "See also". Example The following example shows how the instruction works: 7DJ,QB 7DJ,QB DBDUUD\>@ 7DJB&RXQW 8029(B%/. (1 (12 ,1 287 7DJ2XW EBDUUD\>@ &2817 The following table shows how the instruction works using specific operand values: WinCC Basic V13.0 System Manual, 02/2014 1901 Programming the PLC 9.7 References Parameter Operand Value IN a_array[2] The data type of the a_array operand is Array [0..5] of INT. It consists of six elements of data type INT. COUNT Tag_Count 3 OUT b_array[1] The data type of the b_array operand is Array [0..6] of INT. It consists of seven elements of data type INT. If operands "TagIn_1" and "TagIn_2" have the signal state "1", the "Move block uninterruptible" instruction is executed. Starting from the third element, the instruction selects three INT elements from the #a_array tag and copies their contents to the #b_array output tag, beginning with the second element. The copy operation cannot be interrupted by other operating system activities. If the instruction is executed without errors, the ENO output has the signal state "1" and the "TagOut" output is set. See also Overview of the valid data types (Page 1204) Basics of the EN/ENO mechanism (Page 1299) Inserting additional inputs and outputs in LAD elements (Page 1428) FILL_BLK: Fill block Description You can use the "Fill block" instruction to fill a memory area (destination area) with the value of the IN input. The destination area is filled starting from the address specified at the OUT output. The number of repeated copy operations is specified with the COUNT parameter. When the instruction is executed, the value at the IN input is selected and copied to the destination area as often as specified by the value in the COUNT parameter. The instruction can only be executed if the source area and the destination area are of the same data type. The ENO enable output has the signal state "0" if one of the following conditions is fulfilled: The EN enable input has the signal state "0". More data is copied than is made available at the IN input or OUT output. When a Array of BOOL is copied, the enable output ENO for an overflow is set to "1" until the byte limit of the ARRAY structure is exceeded. If the byte limit of the ARRAY structure is exceeded by the value at the COUNT input, the ENO enable output is reset to "0". 1902 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameters The following table shows the parameters of the "Fill block" instruction: Parameter Declaration Data type S7-1200 S7-1500 Memory area Description EN Input BOOL BOOL I, Q, M, D, L Enable input ENO Output BOOL BOOL I, Q, M, D, L Enable output IN Input Binary numbers, integers, floating-point numbers, TIME, DATE, TOD, CHAR Binary numbers, integers, floating-point numbers, timers, DATE, CHAR, TOD, LTOD I, Q, M, D, L, P or constant Element used to fill the destination area COUNT Input USINT, UINT, UDINT USINT, UINT, UDINT, ULINT I, Q, M, D, L, P or constant Number of repeated move operations OUT 2) Output Binary numbers, integers, floating-point numbers, TIME, DATE, TOD, CHAR Binary numbers, integers, floating-point numbers, timers, DATE, CHAR, TOD, LTOD D, L Address in destination area from which filling starts. 1) 1) The specified data types can also be used as elements of an ARRAY structure. 2) The specified data types can only be used as elements of an ARRAY structure. For additional information on valid data types, refer to "See also". Example The following example shows how the instruction works: 7DJ,QB 7DJ,QB DBDUUD\>@ 7DJB&RXQW ),//B%/. (1 (12 ,1 287 7DJ2XW EBDUUD\>@ &2817 The following table shows how the instruction works using specific operand values: WinCC Basic V13.0 System Manual, 02/2014 1903 Programming the PLC 9.7 References Parameter Operand Value IN a_array[2] The data type of the a_array operand is Array [0..5] of INT. It consists of six elements of data type INT. COUNT Tag_Count 3 OUT b_array[1] The data type of the b_array operand is Array [0..6] of INT. It consists of seven elements of data type INT. If operands "TagIn_1" and "TagIn_2" have the signal state "1", the "Fill block" instruction is executed. The instruction copies the third element (#a_array[2]) of the #a_array tag three times to the #b_array output tag. If the instruction is executed without errors, the ENO and "TagOut" enable outputs are set to signal state "1". See also Overview of the valid data types (Page 1204) Basics of the EN/ENO mechanism (Page 1299) Inserting additional inputs and outputs in LAD elements (Page 1428) UFILL_BLK: Fill block uninterruptible Description You can use the "Fill block uninterruptible" instruction to fill a memory area (destination area) with the value of the IN input without interruption. The destination area is filled starting from the address specified at the OUT output. The number of repeated copy operations is specified with the COUNT parameter. When the instruction is executed, the value at the IN input is selected and copied to the destination area as often as specified by the value in the COUNT parameter. The instruction can only be executed if the source area and the destination area have the same data type. Note The copy operation cannot be interrupted by other operating system activities. This is why the alarm reaction times of the CPU increase during the execution of the "Fill block uninterruptible" instruction. The ENO enable output has the signal state "0" if one of the following conditions is fulfilled: The EN enable input has the signal state "0". More data is copied than is made available at the IN input or OUT output. When a Array of BOOL is copied, the enable output ENO for an overflow is set to "1" until the byte limit of the ARRAY structure is exceeded. If the byte limit of the ARRAY structure is exceeded by the value at the COUNT input, the ENO enable output is reset to "0". 1904 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References You can use the "Fill block uninterruptible" instruction to move a maximum of 16 KB. Note the CPU-specific restrictions for this. Parameters The following table shows the parameters of the "Fill block uninterruptible" instruction: Parameter Declaration Data type S7-1200 S7-1500 Memory area Description EN Input BOOL BOOL I, Q, M, D, L ENO Output BOOL BOOL I, Q, M, D, L Enable output IN 1) Input Binary numbers, integers, floating-point numbers, TIME, DATE, CHAR, TOD Binary numbers, integers, floating-point numbers, timers, DATE, CHAR, TOD, LTOD I, Q, M, D, L, P or constant Element used to fill the destination area. COUNT Input USINT, UINT, UDINT USINT, UINT, UDINT, ULINT I, Q, M, D, L, P or constant Number of repeated move operations OUT 2) Output Binary numbers, integers, floating-point numbers, TIME, DATE, CHAR, TOD Binary numbers, integers, floating-point numbers, timers, DATE, CHAR, TOD, LTOD D, L Address in destination area from which filling begins. 1) The specified data types can also be used as elements of an ARRAY structure. 2) The specified data types can only be used as elements of an ARRAY structure. Enable input For additional information on valid data types, refer to "See also". Example The following example shows how the instruction works: 7DJ,QB 7DJ,QB DBDUUD\>@ 7DJB&RXQW 8),//B%/. (1 (12 ,1 287 7DJ2XW EBDUUD\>@ &2817 The following table shows how the instruction works using specific operand values: WinCC Basic V13.0 System Manual, 02/2014 1905 Programming the PLC 9.7 References Parameter Operand Value IN a_array[2] The data type of the a_array operand is Array [0..5] of INT. It consists of six elements of data type INT. COUNT Tag_Count 3 OUT b_array[1] The data type of the b_array operand is Array [0..6] of INT. It consists of seven elements of data type INT. If operands "TagIn_1" and "TagIn_2" have the signal state "1", the "Fill block uninterruptible" instruction is executed. The instruction copies the third element (#a_array[2]) of the #a_array tag three times to the #b_array output tag. The copy operation cannot be interrupted by other operating system activities. If the instruction is executed without errors, the ENO and "TagOut" enable outputs are set to signal state "1". See also Overview of the valid data types (Page 1204) Basics of the EN/ENO mechanism (Page 1299) Inserting additional inputs and outputs in LAD elements (Page 1428) SWAP: Swap Description You can use the "Swap" instruction to change the order of the bytes at input IN and query the result at output OUT. The following figure shows how the bytes of an operand of the DWORD data type are swapped using the "Swap" instruction: 1906 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References ,1 287 Parameter The following table lists the parameters of the "Swap" instruction: Parameters Declaration Data type S7-1200 S7-1500 Memory area Description EN Input BOOL BOOL I, Q, M, D, L Enable input ENO Output BOOL BOOL I, Q, M, D, L Enable output IN Input WORD, DWORD WORD, DWORD, LWORD I, Q, M, D, L or, P constant Operand whose bytes are swapped. OUT Output WORD, DWORD WORD, DWORD, LWORD I, Q, M, D, L, P Result You can select the data type of the instruction from the "<???>" drop-down list of the instruction box. For additional information on valid data types, refer to "See also". Example The following example shows how the instruction works: 6:$3 :25' 7DJ,Q 7DJ,QB9DOXH WinCC Basic V13.0 System Manual, 02/2014 (1 (12 ,1 287 7DJ2XW 6 7DJ2XWB9DOXH 1907 Programming the PLC 9.7 References The following table shows how the instruction works using specific operand values: Parameter Operand Value IN TagIn_Value 0000 1111 0101 0101 OUT TagOut_Value 0101 0101 0000 1111 If operand "TagIn" has the signal state "1", the "Swap" instruction is executed. The order of the bytes is changed and stored in operand "TagOut_Value". See also Overview of the valid data types (Page 1204) Basics of the EN/ENO mechanism (Page 1299) Inserting additional inputs and outputs in LAD elements (Page 1428) ARRAY DB instructions ReadFromArrayDB: Read from array data block Description You can use the "Read from array data block" instruction to read data from an array DB and write them to a destination area. An array DB is a data block which consists of exactly one array of [data type]. The elements of the array can be UDT data type or any other elementary data type. The counting of the array always starts with the low limit "0", regardless of the later declaration of the array. The ENO enable output has the signal state "0" if one of the following conditions is fulfilled: The EN enable input has the signal state "0". If an error occurs during the execution of the instruction. Parameters The following table shows the parameters of the "Read from array data block" instruction: 1908 Parameter Declaration Data type Memory area Description EN Input BOOL I, Q, M, D, L Enable input ENO Output BOOL I, Q, M, D, L Enable output DB Input DB_ANY I, Q, M, D, L Data block that is read INDEX Input DINT I, Q, M, D, L, P or constant Element that is read WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameter Declaration Data type Memory area Description VALUE Output VARIANT L Value that is read and output RET_VAL Output INT I, Q, M, D, L, P Error information: If an error occurs during the execution of the instruction, an error code is output at the RET_VAL parameter. For additional information on valid data types, refer to "See also". RET_VAL parameter The following table shows the meaning of the values of the RET_VAL parameter: Error code* Explanation (W#16#...) 0000 No error 80B4 Data types do not correspond 80B5 Copying process was interrupted 8132 The data block does not exist or is too short 8133 The data block is located in the load memory 8134 The data block is write protected 8135 The array DB contains invalid values 8154 The data type is not correctly declared 8282 The value at the INDEX parameter is outside the limits of the array. 8350 The VARIANT data type contains no value 8352 Code generation error 8353 Code generation error *The error codes can be displayed as integer or hexadecimal value in the program editor. For information on toggling display formats, refer to "See also". Example The following example shows how the instruction works: 5HDG)URP$UUD\'% 7DJ,QB $UUD\'% $UUD\'%7+,6>@ WinCC Basic V13.0 System Manual, 02/2014 (1 (12 '% 5(7B9$/ ,1'(; 9$/8( 7DJ2XW 7DJ5HWB9DO 7DUJHW)LHOG>@ 'DWD>@ 1909 Programming the PLC 9.7 References The following table shows how the instruction works using specific operand values: Parameter Operand Value DB ArrayDB The data type of the ArrayDB operand is Array [0 to 10] of INT. INDEX ArrayDB.THIS[2] Third element of the "ArrayDB" VALUE TargetField[10].Data2[1] The data type of the TargetField operand is Array [10 to 20] of "MOVE_UDT". If the "TagIn1" operand has the signal state "1", the "Read from the ARRAY data block" instruction is executed. The third element is read from "ArrayDB" and written to the "TargetField[10].Data2[1]" operand. If the instruction is executed without errors, the ENO enable output has the signal state "1" and the "TagOut" output is set. See also Overview of the valid data types (Page 1204) Basics of the EN/ENO mechanism (Page 1299) Inserting additional inputs and outputs in LAD elements (Page 1428) WriteToArrayDB: Write to array data block Description You can use the "Write to array data block" instruction to write data to an array DB. An array DB is a data block which consists of exactly one array of [data type]. The elements of the array can be UDT data type or any other elementary data type. The counting of the array always starts with the low limit "0", regardless of the later declaration of the array. The ENO enable output has the signal state "0" if one of the following conditions is fulfilled: The EN enable input has the signal state "0". If an error occurs during the execution of the instruction. Parameters The following table shows the parameters of the "Write to array data block" instruction: 1910 Parameter Declaration Data type Memory area Description EN Input BOOL I, Q, M, D, L Enable input ENO Output BOOL I, Q, M, D, L Enable output DB Input DB_ANY I, Q, M, D, L Data block to which data is written WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameter Declaration Data type Memory area Description INDEX Input DINT I, Q, M, D, L, P or constant Element in the DB to which data is written VALUE Input VARIANT L Value to be written RET_VAL Output INT I, Q, M, D, L, P Error information: If an error occurs during the execution of the instruction, an error code is output at the RET_VAL parameter. For additional information on valid data types, refer to "See also". RET_VAL parameter The following table shows the meaning of the values of the RET_VAL parameter: Error code* Explanation (W#16#...) 0000 No error 80B4 Data types do not correspond 80B5 Copying process was interrupted 8132 The data block does not exist or is too short 8133 The data block is located in the load memory 8134 The data block is write protected 8135 The DB is not an array data block. 8282 The value at the INDEX parameter is outside the limits of the array. 8350 The VARIANT data type contains no value 8352 Code generation error 8353 Code generation error *The error codes can be displayed as integer or hexadecimal value in the program editor. For information on toggling display formats, refer to "See also". WinCC Basic V13.0 System Manual, 02/2014 1911 Programming the PLC 9.7 References Example The following example shows how the instruction works: :ULWH7R$UUD\'% 7DJ,QB $UUD\'% 7DJ2XW (1 (12 '% 5(7B9$/ $UUD\'%7+,6>@ ,1'(; 6RXUFH)LHOG>@ 'DWD>@ 9$/8( 7DJ5HWB9DO The following table shows how the instruction works using specific operand values: Parameter Operand Value DB ArrayDB The data type of the ArrayDB operand is Array [0 to 10] of INT. INDEX ArrayDB.THIS[2] Third element of the "ArrayDB" VALUE SourceField[1].Data1[6] The data type of the SourceField operand is Array [0 to 10] of "MOVE_UDT". If the "TagIn1" operand has the signal state "1", the "Write to the ARRAY data block" instruction is executed. From the "SourceField" operand, the "Data1[6]" element from the second element is written to the "ArrayDB". The third element is written to the "ArrayDB". If the instruction is executed without errors, the ENO enable output has the signal state "1" and the "TagOut" output is set. See also Overview of the valid data types (Page 1204) Basics of the EN/ENO mechanism (Page 1299) Inserting additional inputs and outputs in LAD elements (Page 1428) ReadFromArrayDBL: Read from array data block in load memory Description You can use the "Read from array data block in load memory" instruction to read data from an array DB in load memory. An array DB is a data block which consists of exactly one array of [data type]. The elements of the array can be UDT data type or any other elementary data type. The counting of the array always starts with the low limit "0", regardless of the later declaration of the array. If the array DB is marked with the "Only store in load memory" block attribute, it is only stored in load memory. The instruction is executed when a positive signal edge is detected at the REQ parameter. The BUSY parameter then has the signal state "1". The instruction is terminated if a negative 1912 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References signal edge is detected at the BUSY parameter. The DONE parameter has the signal state "1" for one program cycle and the read value is output at the VALUE parameter within this cycle. With all other program cycles, the value at the VALUE parameter is not changed. When you insert the instruction in the program, the "Call options" dialog opens in which you can specify whether the block parameters will be stored in a separate data block (single instance) or as a local tag (multi-instance) in the block interface. If you create a separate data block, you will find it in the project tree in the "Program resources" folder under "Program blocks > System blocks". For additional information on this topic, refer to "See also". Note The array DB must be located in a data block with the block property "Optimized". The ENO enable output has the signal state "0" if one of the following conditions is fulfilled: The EN enable input has the signal state "0". If an error occurs during the execution of the instruction. Parameters The following table lists the parameters of the "Read from array data block in load memory" instruction: WinCC Basic V13.0 System Manual, 02/2014 Parameter Declaration Data type Memory area Description EN Input BOOL I, Q, M, D, L Enable input ENO Output BOOL I, Q, M, D, L Enable output REQ Input BOOL I, Q, M, D, L or constant REQ = "1": Starting with the reading of the array DB DB Input DB_ANY I, Q, M, D, L Data block that is read INDEX Input DINT I, Q, M, D, L, P or constant Element that is read BUSY Output BOOL I, Q, M, D, L BUSY = "1": The array DB is still being read DONE Output BOOL I, Q, M, D, L DONE = "1": The instruction was executed successfully 1913 Programming the PLC 9.7 References Parameter Declaration Data type Memory area Description VALUE InOut VARIANT D, L Value that is read and output ERROR Output INT I, Q, M, D, L, P Error information: If an error occurs during the execution of the instruction, an error code is output at the ERROR parameter. For additional information on valid data types, refer to "See also". ERROR parameter The following table shows the meaning of the values of the ERROR parameter: Error code* Explanation (W#16#...) 0000 No error 80B4 Data types do not correspond 80B5 Copying process was interrupted 80C3 Too many concurrent calls 8132 The data block does not exist or is too short 8133 The data block is not located in the load memory 8134 The data block is write protected 8135 The DB is not an array data block. 8282 The value at the INDEX parameter is outside the limits of the array. 8350 The VARIANT data type contains no value 8352 Code generation error 8353 Code generation error *The error codes can be displayed as integer or hexadecimal value in the program editor. For information on toggling display formats, refer to "See also". You can find descriptions of the error codes triggered by the instructions "READ_DBL: Read from data block in the load memory" and "WRIT_DBL: Write to data block in the load memory" under "See also". 1914 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Example The following example shows how the instruction works: 5HDG)URP$UUD\'%/B'% 7DJ,QB 5HDG)URP$UUD\'%/ (1 7DJ5HT $UUD\'% $UUD\'%7+,6>@ 6RXUFH7DUJHW)LHOG>@ 'DWD>@ 7DJ2XW (12 5(4 %86< 7DJ%XV\ '% '21( 7DJ'RQH (5525 7DJ(UURU ,1'(; 9$/8( The following table shows how the instruction works using specific operand values: Parameters Operand Value REQ TagReq BOOL DB ArrayDB The data type of the ArrayDB operand is Array [0 to 10] of INT. INDEX ArrayDB.THIS[2] Third element of the "ArrayDB" VALUE SourceTargetField[1].Data1[6] The data type of the SourceTargetField operand is Array [0 to 10] of "MOVE_UDT". BUSY TagBusy BOOL DONE TagDone BOOL If the "TagIn1" operand has the signal state "1" and a positive edge is detected at the "TagReq"operand, the "Read from ARRAY data block in load memory" instruction is executed. The third element is read from "ArrayDB" and written to the "SourceTargetField[1].Data1[6]" operand. As soon as a negative signal edge is detected at the "TagBusy" operand, the instruction is terminated and the value at the VALUE parameter is no longer changed. If the instruction is executed without errors, the ENO enable output has the signal state "1" and the "TagOut" output is set. After the instruction has been processed, the "TagDone" operand the signal state "1". See also Overview of the valid data types (Page 1204) Basics of the EN/ENO mechanism (Page 1299) READ_DBL: Read from data block in the load memory (Page 2798) WRIT_DBL: Write to data block in the load memory (Page 2800) Inserting additional inputs and outputs in LAD elements (Page 1428) WinCC Basic V13.0 System Manual, 02/2014 1915 Programming the PLC 9.7 References WriteToArrayDBL: Write to array data block in load memory Description You can use the "Write to array data block in load memory" instruction to write data to an array DB in load memory. An array DB is a data block which consists of exactly one array of [data type]. The elements of the array can be UDT data type or any other elementary data type. The counting of the array always starts with the low limit "0", regardless of the later declaration of the array. If the array DB is marked with the "Only store in load memory" block attribute, it is only stored in load memory. The instruction is executed when a positive signal edge is detected at the REQ parameter. The BUSY parameter then has the signal state "1". If a negative signal edge is detected at the BUSY parameter, the instruction is terminated and the value at the VALUE parameter is written to the data block. The DONE parameter then has the signal state "1" for one program cycle. When you insert the instruction in the program, the "Call options" dialog opens in which you can specify whether the block parameters will be stored in a separate data block (single instance) or as a local tag (multi-instance) in the block interface. If you create a separate data block, you will find it in the project tree in the "Program resources" folder under "Program blocks > System blocks". For additional information on this topic, refer to "See also". Note The array DB must be located in a data block with the block property "Optimized". The ENO enable output has the signal state "0" if one of the following conditions is fulfilled: The EN enable input has the signal state "0". If an error occurs during the execution of the instruction. Parameters The following table lists the parameters of the "Write to array data block in load memory" instruction: 1916 Parameter Declaration Data type Memory area Description EN Input BOOL I, Q, M, D, L Enable input ENO Output BOOL I, Q, M, D, L Enable output REQ Input BOOL I, Q, M, D, L or constant REQ = "1": Start writing into the array DB DB Input DB_ANY D Data block to which data is written INDEX Input DINT I, Q, M, D, L, P or constant Element in the DB to which data is written WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameter Declaration Data type Memory area Description VALUE Input VARIANT D, L Value to be written BUSY Output BOOL I, Q, M, D, L BUSY = "1": The array DB is still being written DONE Output BOOL I, Q, M, D, L DONE = "1": The instruction was executed successfully ERROR Output INT I, Q, M, D, L, P Error information: If an error occurs during the execution of the instruction, an error code is output at the ERROR parameter. For additional information on valid data types, refer to "See also". ERROR parameter The following table shows the meaning of the values of the ERROR parameter: Error code* Explanation (W#16#...) 0000 No error 80B4 Data types do not correspond 80B5 Copying process was interrupted 80C3 Too many concurrent calls 8132 The data block does not exist or is too short 8133 The data block is not located in the load memory 8134 The data block is write protected 8135 The DB is not an array data block. 8282 The value at the INDEX parameter is outside the limits of the array. 8350 The VARIANT data type contains no value 8352 Code generation error 8353 Code generation error *The error codes can be displayed as integer or hexadecimal value in the program editor. For information on toggling display formats, refer to "See also". You can find descriptions of the error codes triggered by the instructions "READ_DBL: Read from data block in the load memory" and "WRIT_DBL: Write to data block in the load memory" under "See also". WinCC Basic V13.0 System Manual, 02/2014 1917 Programming the PLC 9.7 References Example The following example shows how the instruction works: :ULWH7R$UUD\'%/B'% :ULWH7R$UUD\'%/ 7DJ,QB (1 7DJ5HT $UUD\'% $UUD\'%7+,6>@ 6RXUFH7DUJHW)LHOG>@ 'DWD>@ 7DJ2XW (12 5(4 %86< 7DJ%XV\ '% '21( 7DJ'RQH (5525 7DJ(UURU ,1'(; 9$/8( The following table shows how the instruction works using specific operand values: Parameters Operand Value REQ TagReq BOOL DB ArrayDB The data type of the ArrayDB operand is Array [0 to 10] of INT. INDEX ArrayDB.THIS[2] Third element of the "ArrayDB" VALUE SourceTargetField[1].Data1[6] The data type of the SourceTargetField operand is Array [0 to 10] of "MOVE_UDT". BUSY TagBusy BOOL DONE TagDone BOOL If the "TagIn1" operand has the signal state "1" and a positive edge is detected at the "TagReq"operand, the "Write to ARRAY data block in load memory" instruction is executed. As soon as a negative signal edge is detected at the "TagBusy" operand, the instruction is terminated and the value at the VALUE parameter is written in the third element in the "ArrayDB". If the instruction is executed without errors, the ENO enable output has the signal state "1" and the "TagOut" output is set. After the instruction has been processed, the "TagDone" operand the signal state "1". See also Overview of the valid data types (Page 1204) Basics of the EN/ENO mechanism (Page 1299) READ_DBL: Read from data block in the load memory (Page 2798) WRIT_DBL: Write to data block in the load memory (Page 2800) Inserting additional inputs and outputs in LAD elements (Page 1428) 1918 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References VARIANT instructions VariantGet: Read out VARIANT tag value Description You can use the "Read out VARIANT tag value" instruction to read the value of the tag that points to the VARIANT at the SRC parameter, and write it to the tag at the DST parameter. The SRC parameter must have the same VARIANT data type. Any data type except for VARIANT can be specified at the DST parameter. The data type of the tag at the DST parameter must match the data type to which the VARIANT points. Note The tag to which the VARIANT at parameter SRC points must be a PLC data type. To copy structures and ARRAYs, you can use the "MOVE_BLK_VARIANT: Move block" instruction. For additional information, refer to "See also". The ENO enable output has the signal state "0" if one of the following conditions is fulfilled: The EN enable input has the signal state "0". The data types do not correspond. (No value is transferred.) Parameter The following table lists the parameters of the "Read out VARIANT tag value" instruction: Parameters Declaration Data type Memory area Description EN Input BOOL I, Q, M, D, L Enable input ENO Output BOOL I, Q, M, D, L Enable output SRC Input VARIANT L Tag to be read DST Output Bit strings, integers, floating-point numbers, timers, date and time, character strings, ARRAY I, Q, M, D, L Result of the instruction For additional information on valid data types, refer to "See also". WinCC Basic V13.0 System Manual, 02/2014 1919 Programming the PLC 9.7 References Example The following example shows how the instruction works: 7DJ,Q 7DJ,QB6RXUFH 9DULDQW*HW (1 (12 7DJ2XW 6 65& '67 7DJ2XWB'HVW If the "TagIn" operand has the signal state "1", the "Read out VARIANT tag value" instruction is executed. The value of the tag to which the VARIANT at the "#TagIn_Source" operand points, is read and written to the "TagOut_Dest" operand. See also Overview of the valid data types (Page 1204) Basics of the EN/ENO mechanism (Page 1299) VARIANT (Page 1245) MOVE_BLK_VARIANT: Move block (Page 1896) Inserting additional inputs and outputs in LAD elements (Page 1428) VariantPut: Write VARIANT tag value Description You can use the "Write VARIANT tag value" instruction to write the value of the tag at the SRC parameter and to the tag at the DST parameter to which the VARIANT points. The DST parameter must have the same VARIANT data type. Any data type except for VARIANT can be specified at the SRC parameter. The data type of the tag at the SRC parameter must match the data type to which the VARIANT points. Note The tag to which the VARIANT at parameter DST points must be a PLC data type. The ENO enable output has the signal state "0" if one of the following conditions is fulfilled: The EN enable input has the signal state "0". The data types do not correspond. (No value is transferred.) 1920 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameters The following table lists the parameters of the "Write VARIANT tag value" instruction: Parameters Declaration Data type Memory area Description EN Input BOOL I, Q, M, D, L Enable input ENO Output BOOL I, Q, M, D, L Enable output SRC Input Bit strings, integers, floating-point numbers, timers, date and time, character strings, ARRAY I, Q, M, D, L Tag to be read DST Input VARIANT L Result of the instruction For additional information on valid data types, refer to "See also". Example The following example shows how the instruction works: 7DJ,Q 9DULDQW3XW (1 7DJ,QB6RXUFH 65& 7DJ,QB'HVW '67 (12 7DJ2XW 6 If the "TagIn" operand has the signal state "1", the "Write VARIANT tag value" instruction is executed. The value of the "TagIn_Source" operand is written to the tag to which the VARIANT at the "#TagIn_Dest" operand points. See also Overview of the valid data types (Page 1204) Basics of the EN/ENO mechanism (Page 1299) VARIANT (Page 1245) Inserting additional inputs and outputs in LAD elements (Page 1428) CountOfElements: Get number of ARRAY elements Description You can use the "Get number of ARRAY elements" instruction to query how many ARRAY elements a tag pointing to an VARIANT has. WinCC Basic V13.0 System Manual, 02/2014 1921 Programming the PLC 9.7 References If it is a one-dimensional ARRAY, the difference between the high and low limit +1 is output as a result. If it is a multi-dimensional ARRAY, the product of all dimensions is output as the result. The IN parameter must have the same VARIANT data type. The ENO enable output has the signal state "0" if one of the following conditions is fulfilled: The EN enable input has the signal state "0". The VARIANT tag is not an ARRAY. (The result is "0".) If the VARIANT points to an ARRAY of BOOL, the fill elements are also included in the count. (For example, 8 is returned for an ARRAY[0..1] of BOOL) Parameters The following table lists the parameters of the "Get number of ARRAY elements" instruction: Parameters Declaration Data type Memory area Description EN Input BOOL I, Q, M, D, L Enable input ENO Output BOOL I, Q, M, D, L Enable output IN Input VARIANT L Tag to be queried RET_VAL Output UDINT I, Q, M, D, L Result of the instruction For additional information on valid data types, refer to "See also". Example The following example shows how the instruction works: 7DJ,Q &RXQW2I(OHPHQWV (1 7DJ,QB6RXUFH ,1 7DJ2XW 6 (12 5(7B9$/ 7DJ2XWB5HW9DO If the "TagIn" operand has the signal state "1", the "Get number of ARRAY elements" instruction is executed. The number of ARRAY elements of the tag to which the VARIANT at the "#TagIn_Source" operand points is read and output at the "TagOut_RetVal" operand. See also Format of array (16-bit limits) (Page 1235) Format of array (32-bit limits) (Page 1236) Overview of the valid data types (Page 1204) Basics of the EN/ENO mechanism (Page 1299) VARIANT (Page 1245) Inserting additional inputs and outputs in LAD elements (Page 1428) 1922 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Other BLKMOV: Move block Description You can use the "Move block" instruction to move the content of a memory area (source area) to another memory area (destination area). The move operation takes place in the direction of ascending addresses. You use VARIANT to define the source and destination area. Note The tags of the instruction can only be used in data blocks in which the "Optimized block access" attribute is not set. If the tag with the retentivity setting "Set in IDB" has been declared, you can also use the tags "with optimized access". The following figure shows the principle of the move operation: '%'%: $ % '%'%: & ' '%'%: ( ) '%'%: * + 0RYH 7KHPRYHWDNHVSODFHLQ WKHGLUHFWLRQRIDVFHQGLQJ DGGUHVVHV 0: $ % 0: & ' 0: ( ) 0: * + 0HPRU\DUHD Consistency of the source data and the target data Make sure that the source data remain unchanged during the execution of the "Move block" instruction. Otherwise the consistency of the target data cannot be ensured. Interruptibility There is no limit to the nesting depth. WinCC Basic V13.0 System Manual, 02/2014 1923 Programming the PLC 9.7 References Memory areas You can use the "Move block" instruction to move the following memory areas: Areas of a data block Bit memory Process image of the inputs Process image of the outputs General rules for moving The source and destination area must not overlap. If the source and destination area have different lengths, only the length of the smaller area will be moved. If the source area is less than the destination area, the entire source area will be written to the destination area. The remaining bytes of the destination area remain unchanged. If the destination area is less than the source area, the entire destination area will be written. The remaining bytes of the source area are ignored. If a block of data type BOOL is moved, the tag must be addressed absolutely and the specified length of the area must be divisible by 8, otherwise the instruction cannot be executed. Rules for moving character strings You can use the "Move block" instruction to also move source and destination areas of the STRING data type. If only the source area is STRING data type, the characters will be moved that are actually contained in the character string. Information on the actual and maximum length is also written to the destination area. If the source and destination area are each STRING data type, the current length of the character string in the destination area is set to the number of actually moved characters. If you want to move the information on the maximum and actual length of a character string, specify the areas in bytes to the SRCBLK and DSTBLK parameters. Parameters The following table lists the parameters of the "Move block" instruction: 1924 Parameter Declaration Data type Memory area Description EN Input BOOL I, Q, M, D, L Enable input ENO Output BOOL I, Q, M, D, L Enable output SRCBLK Input VARIANT L, P Specifies the memory area to be moved (source area). WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameter Declaration Data type Memory area Description RET_VAL Output INT I, Q, M, D, L, P Error information: If an error occurs during the execution of the instruction, an error code is output at the RET_VAL parameter. DSTBLK Output VARIANT L, P Specifies the memory area to which the block is to be moved (destination area). RET_VAL parameter The following table shows the meaning of the values of the RET_VAL parameter: Error code* (W#16#...) Explanation 0000 No error 8152 The WSTRING, WCHAR and BOOL data types are not supported. 8092 The source or target area is only available in the load memory. General error information See also: "GET_ERR_ID: Get error ID locally *The error codes can be displayed as integer or hexadecimal value in the program editor. For information on toggling display formats, refer to "See also". See also Overview of the valid data types (Page 1204) Basics of the EN/ENO mechanism (Page 1299) GET_ERR_ID: Get error ID locally (Page 1964) Inserting additional inputs and outputs in LAD elements (Page 1428) UBLKMOV: Move block uninterruptible Description You can use the "Move block uninterruptible" instruction to move the content of a memory area (source area) to another memory area (destination area). The move operation takes place in the direction of ascending addresses. You use VARIANT to define the source and destination area. WinCC Basic V13.0 System Manual, 02/2014 1925 Programming the PLC 9.7 References The move operation cannot be interrupted by other operating system activities. As a result the alarm reaction time of the CPU can increase during the execution of the "Move block uninterruptible" instruction. Note The tags of the instruction can only be used in data blocks in which the "Optimized block access" attribute is not set. If the tag with the retentivity setting "Set in IDB" has been declared, you can also use the tags "with optimized access". Memory areas You can use the "Move block uninterruptible" instruction to move the following memory areas: Areas of a data block Bit memory Process image of the inputs Process image of the outputs General rules for moving The source and destination area must not overlap during the execution of the "Move block uninterruptible" instruction. If the source area is less than the destination area, the entire source area will be written to the destination area. The remaining bytes of the destination area remain unchanged. If the destination area is less than the source area, the entire destination area will be written. The remaining bytes of the source area are ignored. If a source or destination area defined as a formal parameter is less than a destination or source area specified on the SRCBLK or DSTBLK parameter, no data is transferred. If a block of data type BOOL is moved, the tag must be addressed absolutely and the specified length of the area must be divisible by 8, otherwise the instruction cannot be executed. You can use the "Move block uninterruptible" instruction to move a maximum of 16 KB. Note the CPU-specific restrictions for this. Rules for moving character strings You can use the "Move block uninterruptible" instruction to also move source and destination areas of the STRING data type. If only the source area is STRING data type, the characters will be moved that are actually contained in the character string. Information on the actual and maximum length are not written in the destination area. If the source and destination area are each STRING data type, the current length of the character string in the destination area is set to the number of actually moved characters. If areas of the data type STRING are moved, you have to specify "1" as area length. 1926 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameters The following table shows the parameters of the "Move block uninterruptible" instruction: Parameter Declaration Data type Memory area Description EN Input BOOL I, Q, M, D, L Enable input ENO Output BOOL I, Q, M, D, L Enable output SRCBLK Input VARIANT L, P Specifies the memory area to be moved (source area). RET_VAL Output INT I, Q, M, D, L, P Error information: If an error occurs during the execution of the instruction, an error code is output at the RET_VAL parameter. DSTBLK Output VARIANT L, P Specifies the memory area to which the block is to be moved (destination area). RET_VAL parameter The following table shows the meaning of the values of the RET_VAL parameter: Error code* (W#16#...) Explanation 0000 No error 8152 The WSTRING, WCHAR and BOOL data types are not supported. 8091 The source area is in a data block that is not relevant for program execution. General error information See also: "GET_ERR_ID: Get error ID locally *The error codes can be displayed as integer or hexadecimal value in the program editor. For information on toggling display formats, refer to "See also". See also Overview of the valid data types (Page 1204) Basics of the EN/ENO mechanism (Page 1299) GET_ERR_ID: Get error ID locally (Page 1964) Inserting additional inputs and outputs in LAD elements (Page 1428) FILL: Fill block Description You can use the "Fill block" instruction to fill a memory area (destination area) with the content of another memory area (source area). The "Fill block" instruction moves the content of the WinCC Basic V13.0 System Manual, 02/2014 1927 Programming the PLC 9.7 References source area to the destination area until the destination area is completely written. The move operation takes place in the direction of ascending addresses. You use VARIANT to define the source and destination area. Note The tags of the instruction can only be used in data blocks in which the "Optimized block access" attribute is not set. If the tag with the retentivity setting "Set in IDB" has been declared, you can also use the tags "with optimized access". For blocks with the "Optimized block access" attribute, you can use the instruction "FILL_BLK: Fill block" instruction. The following figure shows the principle of the move operation: ),// %9$/ $ % 0: $ % 0: & ' 0: & ' 0: ( ) 0: ( ) 0: * + 0: * + 0: $ % 0: & ' 0: ( ) 0: * + 0: $ % 0: & ' 0: %/. Example: The contents of the range MW100 to MW118 are to be preassigned with the contents of the memory words MW14 to MW20. Consistency of the source data and the target data Please note that during execution of the instruction "Fill block" that the source data remain unchanged, otherwise the consistency of the target data is not ensured. Memory areas You can use the "Fill block" instruction to move the following memory areas: Areas of a data block Bit memory 1928 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Process image of the inputs Process image of the outputs General rules for moving The source and destination area must not overlap. If the destination block to be preset is not an integer multiple of the length of the input parameter BVAL, the destination block is nevertheless written up to the last byte. If the destination area to be preset is smaller than the source area, the function only copies as much data as can be written to the destination area. If the destination or source area actually present is smaller than the assigned memory area for the source or destination block (BVAL BLK parameters), no data is transferred. If the ANY pointer (source or destination) is of the data type BOOL, it must be addressed absolutely and the length specified must be divisible by 8; otherwise the instruction is not executed. If the destination block is of data type STRING, the instruction describes the entire string including the administration information. Parameters The following table shows the parameters of the "Fill block" instruction: Parameter Declaration Data type Memory area Description EN Input BOOL I, Q, M, D, L Enable input ENO Output BOOL I, Q, M, D, L Enable output BVAL Input VARIANT L, P Specification of the memory area (source area) with the content used to fill the destination area at the BLK parameter. RET_VAL Output INT I, Q, M, D, L, P Error information: If an error occurs during the execution of the instruction, an error code is output at the RET_VAL parameter. BLK Output VARIANT L, P Specification of the memory area that is filled with the content of the source area. RET_VAL parameter The following table shows the meaning of the values of the RET_VAL parameter: Error code* (W#16#...) Explanation 0000 No error 8152 The WSTRING, WCHAR and BOOL data types are not supported. WinCC Basic V13.0 System Manual, 02/2014 1929 Programming the PLC 9.7 References Error code* (W#16#...) Explanation General error information See also: "GET_ERR_ID: Get error ID locally *The error codes can be displayed as integer or hexadecimal value in the program editor. For information on toggling display formats, refer to "See also". See also Overview of the valid data types (Page 1204) Basics of the EN/ENO mechanism (Page 1299) GET_ERR_ID: Get error ID locally (Page 1964) Inserting additional inputs and outputs in LAD elements (Page 1428) Conversion operations CONVERT: Convert value Description The "Convert value" instruction reads the content of the IN parameter and converts it according to the data types selected in the instruction box. The converted value is sent to the output OUT. For information on possible conversions, refer to the "Explicit conversion" section at "See also". The ENO enable output has the signal state "0" if one of the following conditions is fulfilled: The EN enable input has the signal state "0". Errors such as an overflow occur during execution. Parameters The following table shows the parameters of the "Convert value" instruction: 1930 Parameter Declaration Data type Memory area Description EN Input BOOL I, Q, M, D, L Enable input ENO Output BOOL I, Q, M, D, L Enable output IN Input Bit strings, integers, floatingpoint numbers, CHAR, BCD16, BCD32 I, Q, M, D, L, P or constant Value to be converted. OUT Output Bit strings, integers, floatingpoint numbers, CHAR, BCD16, BCD32 I, Q, M, D, L, P Result of the conversion WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References You can select the data type for the instruction from the "<???>" drop-down list of the instruction box. Bit strings (BYTE, WORD, DWORD, LWORD) cannot be selected in the instruction box. If you specify an operand of data type BYTE, WORD, DWORD or LWORD at a parameter of the instruction, it is interpreted according to the data type of the input or output parameter. Data type BYTE is then interpreted as USINT, WORD as UINT, DWORD as UDINT, and LWORD as LINT, for example. Note For S7-1500 CPU: The data types DWORD and LWORD can be selected, if REAL or LREAL is selected as IN data type. For additional information on valid data types, refer to "See also". Example The following example shows how the instruction works: &219 7DJ,Q 7DJ,QB9DOXH ,17 WR ',17 (1 (12 ,1 287 7DJ2XW 7DJ2XWB9DOXH If operand "TagIn" has the signal state "1", the content of operand "TagIn_Value" is read and converted to an integer (32-bit). The result is stored in operand "TagOut_Value". The output "TagOut" is set to "1" if the instruction was executed without errors. See also Overview of the valid data types (Page 1204) Explicit conversion of CHAR (Page 1297) ROUND: Round numerical value Description You can use the "Round numerical value" instruction to round the value at input IN to the nearest integer. The instruction interprets the value at input IN as a floating-point number and converts this to an integer of data type DINT. If the input value is exactly between an even and odd number, the even number is selected. The result of the instruction is sent to the OUT output and can be queried there. The ENO enable output has the signal state "0" if one of the following conditions is fulfilled: WinCC Basic V13.0 System Manual, 02/2014 1931 Programming the PLC 9.7 References The enable input EN has the signal state "0". Errors such as an overflow occur during execution. Parameters The following table shows the parameters of the "Round numerical value" instruction: Parameters Declaration Data type Memory area Description EN Input BOOL I, Q, M, D, L Enable input ENO Output BOOL I, Q, M, D, L Enable output IN Input Floating-point numbers I, Q, M, D, L, P or constant Input value to be rounded. OUT Output Integers, floatingpoint numbers I, Q, M, D, L, P Result of rounding You can select the data type for the instruction from the "<???>" drop-down list of the instruction box. For additional information on valid data types, refer to "See also". Example The following example shows how the instruction works: 5281' 7DJ,Q 7DJ,QB9DOXH 5($/ WR ',17 (1 (12 ,1 287 7DJ2XW 7DJ2XWB9DOXH The following table shows how the instruction works using specific operand values: Parameter Operand Value IN TagIn_Value 1.50000000 -1.50000000 OUT TagOut_Value 2 -2 If operand "TagIn" has the signal state "1", the "Round numerical value" instruction is executed. The floating-point number at input "TagIn_Value" is rounded to the nearest even integer and sent to output "TagOut_Value". If the instruction is executed without errors, the "TagOut" output is set. See also Overview of the valid data types (Page 1204) 1932 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References CEIL: Generate next higher integer from floating-point number Description You can use the "Generate next higher integer from floating-point number" instruction to round the value at input IN to the next higher integer. The instruction interprets the value at the IN input as a floating-point number and converts this number to the next higher integer. The result of the instruction is sent to the OUT output and can be queried there. The output value can be greater than or equal to the input value. The ENO enable output has the signal state "0" if one of the following conditions is fulfilled: The enable input EN has the signal state "0". Errors such as an overflow occur during execution. Parameters The following table shows the parameters of the "Generate next higher integer from floatingpoint number" instruction: Parameters Declaration Data type Memory area Description EN Input BOOL I, Q, M, D, L Enable input ENO Output BOOL I, Q, M, D, L Enable output IN Input Floating-point numbers I, Q, M, D, L, P or constant Input value OUT Output Integers, floatingpoint numbers I, Q, M, D, L, P Result with next higher integer You can select the data type for the instruction from the "<???>" drop-down list of the instruction box. For additional information on valid data types, refer to "See also". Example The following example shows how the instruction works: &(,/ 7DJ,Q 7DJ,QB9DOXH 5($/ WR ',17 (1 (12 ,1 287 7DJ2XW 7DJ2XWB9DOXH The following table shows how the instruction works using specific operand values: WinCC Basic V13.0 System Manual, 02/2014 Parameter Operand Value IN TagIn_Value 0.50000000 -0.50000000 OUT TagOut_Value 1 0 1933 Programming the PLC 9.7 References If operand "TagIn" has the signal state "1", the "Generate next higher integer from floatingpoint number" instruction is executed. The floating-point number at the "TagIn_Value" input is rounded to the next higher integer and sent to the "TagOut_Value" output. If the instruction is executed without errors, the "TagOut" output is set. See also Overview of the valid data types (Page 1204) FLOOR: Generate next lower integer from floating-point number Description You can use the "Generate next lower integer from floating-point number" instruction to round the value at input IN to the next lower integer. The instruction interprets the value at input IN as a floating-point number and converts this to the next lower integer. The result of the instruction is sent to the OUT output and can be queried there. The output value can be less than or equal to the input value. The ENO enable output has the signal state "0" if one of the following conditions is fulfilled: The enable input EN has the signal state "0". Errors such as an overflow occur during execution. Parameters The following table shows the parameters of the "Generate next lower integer from floatingpoint number" instruction: Parameters Declaration Data type Memory area Description EN Input BOOL I, Q, M, D, L Enable input ENO Output BOOL I, Q, M, D, L Enable output IN Input Floating-point numbers I, Q, M, D, L, P or constant Input value OUT Output Integers, floatingpoint numbers I, Q, M, D, L, P Result with next lower integer You can select the data type for the instruction from the "<???>" drop-down list of the instruction box. For additional information on valid data types, refer to "See also". 1934 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Example The following example shows how the instruction works: )/225 7DJ,Q 7DJ,QB9DOXH 5($/ WR ',17 (1 (12 ,1 287 7DJ2XW 7DJ2XWB9DOXH The following table shows how the instruction works using specific operand values: Parameter Operand IN TagIn_Value 0.50000000 Value -0.50000000 OUT TagOut_Value 0 -1 If operand "TagIn" has the signal state "1", the "Generate next lower integer from floating-point number" instruction is executed. The floating-point number at input "TagIn_Value" is rounded to the next lower integer and sent to output "TagOut_Value". If the instruction is executed without errors, the "TagOut" output is set. See also Overview of the valid data types (Page 1204) TRUNC: Truncate numerical value Description You can use the "Truncate numerical value" instruction to form an integer from the value at the IN input. The value at the IN input is interpreted as a floating-point number. The instruction selects only the integer part of the floating-point number and sends this to the OUT output without decimal places. The ENO enable output has the signal state "0" if one of the following conditions is fulfilled: The EN input has the signal state "0". Errors such as an overflow occur during execution. WinCC Basic V13.0 System Manual, 02/2014 1935 Programming the PLC 9.7 References Parameters The following table shows the parameters of the "Truncate numerical value" instruction: Parameter Declaration Data type Memory area Description EN Input BOOL I, Q, M, D, L Enable input ENO Output BOOL I, Q, M, D, L Enable output IN Input Floating-point numbers I, Q, M, D, L or constant Input value OUT Output Integers, floatingpoint numbers I, Q, M, D, L Integer part of the input value You can select the data type for the instruction from the "<???>" drop-down list of the instruction box. For additional information on valid data types, refer to "See also". Example The following example shows how the instruction works: 7581& 7DJ,Q 7DJ,QB9DOXH 5($/ WR ',17 (1 (12 ,1 287 7DJ2XW 7DJ2XWB9DOXH The following table shows how the instruction works using specific operand values: Parameter Operand Value IN TagIn_Value 1.50000000 -1.50000000 OUT TagOut_Value 1 -1 If operand "TagIn" has the signal state "1", the "Truncate numerical value" instruction is executed. The integer part of the floating-point number at the "TagIn_Value" input is converted to an integer and sent to the "TagOut_Value" output. If the instruction is executed without errors, the "TagOut" output is set. See also Overview of the valid data types (Page 1204) 1936 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References SCALE_X: Scale Description You can use the "Scale" instruction to scale the value at the VALUE input by mapping it to a specified value range. When the "Scale" instruction is executed, the floating-point value at the VALUE input is scaled to the value range that was defined by the MIN and MAX parameters. The result of the scaling is an integer, which is stored in the OUT output. The following figure shows an example of how values can be scaled: 0$; 287 0,1 9$/8( The "Scale" instruction works with the following equation: OUT = [VALUE (MAX - MIN)] + MIN The ENO enable output has the signal state "0" if one of the following conditions is fulfilled: The EN enable input has the signal state "0". The value at the MIN input is greater than or equal to the value at the MAX input. The value of a specified floating-point number is outside the range of the normalized numbers according to IEEE-754. An overflow occurs. The value at the VALUE input is NaN (Not a Number = result of an invalid arithmetic operation). Note For more information on the converting of analog values, refer to the respective manual. WinCC Basic V13.0 System Manual, 02/2014 1937 Programming the PLC 9.7 References Parameters The following table shows the parameters of the "Scale" instruction: Parameter Declaration Data type Memory area Description EN Input BOOL I, Q, M, D, L Enable input ENO Output BOOL I, Q, M, D, L Enable output MIN Input Integers, floatingpoint numbers I, Q, M, D, L or constant Low limit of the value range VALUE Input Floating-point numbers I, Q, M, D, L or constant Value to be scaled. If you enter a constant, you must declare it. MAX Input Integers, floatingpoint numbers I, Q, M, D, L or constant High limit of the value range OUT Output Integers, floatingpoint numbers I, Q, M, D, L Result of scaling You can select the data type for the instruction from the "<???>" drop-down list of the instruction box. For additional information on valid data types, refer to "See also". For additional information on declaring constants, refer to "See also". Example The following example shows how the instruction works: 6&$/(B; 7DJ,Q 7DJB0,1 5($/ WR ',17 (1 (12 0,1 287 7DJB9DOXH 9$/8( 7DJB0$; 0$; 7DJ2XW 6 7DJB5HVXOW The following table shows how the instruction works using specific operand values: Parameter Operand Value MIN Tag_MIN 10 VALUE Tag_Value 0.5 MAX Tag_MAX 30 OUT Tag_Result 20 If operand "TagIn" has the signal state "1", the "Scale" instruction is executed. The value at the "Tag_Value" input is scaled to the range of values defined by the values at the "Tag_MIN" and "Tag_MAX" inputs. The result is stored in the "Tag_Result" output. If the instruction is executed without errors, the ENO enable output has the signal state "1" and the "TagOut" output is set. 1938 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References See also Overview of the valid data types (Page 1204) NORM_X: Normalize (Page 1939) Declaring global constants (Page 1320) NORM_X: Normalize Description You can use the instruction "Normalize" to normalize the value of the tag at the VALUE input by mapping it to a linear scale. You can use the MIN and MAX parameters to define the limits of a value range that is applied to the scale. The result at the OUT output is calculated and stored as a floating-point number depending on the location of the value to be normalized within this value range. If the value to be normalized is equal to the value at the MIN input, the OUT output has the value "0.0". If the value to be normalized is equal to the value at input MAX, output OUT returns the value "1.0". The following figure shows an example of how values can be normalized: 287 0,1 0$; 9$/8( The "Normalize" instruction works with the following equation: OUT = (VALUE - MIN) / (MAX - MIN) The ENO enable output has the signal state "0" if one of the following conditions is fulfilled: The EN enable input has the signal state "0". The value at the MIN input is greater than or equal to the value at the MAX input. The value of a specified floating-point number is outside the range of the normalized numbers according to IEEE-754. The value at the VALUE input is NaN (result of an invalid arithmetic operation). WinCC Basic V13.0 System Manual, 02/2014 1939 Programming the PLC 9.7 References Note For more information on the converting of analog values, refer to the respective manual. Parameter The following table shows the parameters of the "Normalize" instruction: Parameter Declaration Data type Memory area Description EN Input BOOL I, Q, M, D, L Enable input ENO Output BOOL I, Q, M, D, L Enable output MIN Input Integers, floatingpoint numbers I, Q, M, D, L or constant Low limit of the value range VALUE 1) Input Integers, floatingpoint numbers I, Q, M, D, L or constant Value to be normalized. MAX 1) Input Integers, floatingpoint numbers I, Q, M, D, L or constant High limit of the value range OUT Output Floating-point numbers I, Q, M, D, L Result of the normalization 1) 1) If you use constants in these three parameters, you only need to declare one of them. You can select the data type for the instruction from the "<???>" drop-down list of the instruction box. For additional information on valid data types, refer to "See also". For additional information on declaring constants, refer to "See also". Example The following example shows how the instruction works: 1250B; 7DJ,Q 7DJB0,1 ',17 WR 5($/ (1 (12 0,1 287 7DJB9DOXH 9$/8( 7DJB0$; 0$; 7DJ2XW 6 7DJB5HVXOW The following table shows how the instruction works using specific operand values: 1940 Parameter Operand Value MIN Tag_MIN 10 VALUE Tag_Value 20 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameter Operand Value MAX Tag_MAX 30 OUT Tag_Result 0.5 If operand "TagIn" has the signal state "1", the "Normalize" instruction is executed. The value at the "Tag_Value" input is mapped to the range of values that were defined by the values at the "Tag_MIN" and "Tag_MAX" inputs. The tag value at the "Tag_Value" input is normalized to the defined value range. The result is stored as a floating-point number in the "Tag_Result" output. If the instruction is executed without errors, the ENO enable output has the signal state "1" and the "TagOut" output is set. See also Overview of the valid data types (Page 1204) SCALE_X: Scale (Page 1937) Declaring global constants (Page 1320) Other SCALE: Scale Description Use the "Scale" instruction to convert the integer at the IN parameter into a floating-point number, which can be scaled in physical units between a low limit value and a high limit value. You can use the LO_LIM and HI_LIM parameters to specify the low limit and high limit of the value range to which the input value is scaled. The result of the instruction is output on the OUT parameter. The "Scale" instruction works with the following equation: OUT = [((FLOAT (IN) - K1)/(K2-K1)) (HI_LIM-LO_LIM)] + LO_LIM The values of the constants "K1" and "K2" are determined by the signal state on the BIPOLAR parameter. The following signal states are possible on the BIPOLAR parameter: Signal state "1": It is assumed that the value at the IN parameter is bipolar and in a value range between -27648 and 27648. In this case the "K1" constant has the value "-27648.0" and the "K2" constant the value "+27648.0". Signal state "0": It is assumed that the value at the IN parameter is unipolar and in a value range between 0 and 27648. In this case the "K1" constant has the value "0,0" and the "K2" constant the value "+27648.0". When the value at the IN parameter is greater than the value of the constant "K2", the result of the instruction is set to the value of the high limit (HI_LIM) and an error is output. When the value at the IN parameter is less than the value of the constant "K1", the result of the instruction is set to the value of the low limit value (LO_LIM) and an error is output. When the indicated low limit value is greater than the high limit value (LO_LIM > HI_LIM), the result is scaled in reverse proportion to the input value. WinCC Basic V13.0 System Manual, 02/2014 1941 Programming the PLC 9.7 References Parameter The following table shows the parameters of the "Scale" instruction: Parameter Declaration Data type Memory area Description EN Input BOOL I, Q, M, D, L Enable input ENO Output BOOL I, Q, M, D, L Enable output IN Input INT I, Q, M, D, L, P or constant Input value to be scaled. HI_LIM Input REAL I, Q, M, D, L, P or constant High limit LO_LIM Input REAL I, Q, M, D, L, P or constant Low limit BIPOLAR Input BOOL I, Q, M, D, L or constant Indicates if the value at IN parameter is to be interpreted as bipolar or unipolar. The parameter can assume the following values: 1: Bipolar 0: Unipolar OUT Output REAL I, Q, M, D, L, P Result of the instruction RET_VAL Output WORD I, Q, M, D, L, P Error information Parameter RET_VAL The following table shows the meaning of the values of the RET_VAL parameter: Error code* (W#16#...) Explanation 0000 No error 0008 The value of the IN parameter is greater than the value of the constant "K2" or less than the value of the constant "K1" General error information See also: "GET_ERR_ID: Get error ID locally *The error codes can be displayed as integer or hexadecimal value in the program editor. For information on toggling display formats, refer to "See also". 1942 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Example The following example shows how the instruction works: 6&$/( 7DJ,Q 7DJB,QSXW9DOXH (1 ,1 7DJB+LJK/LPLW +,B/,0 7DJB/RZ/LPLW /2B/,0 7DJB%LSRODU 7DJ2XW (12 5(7B9$/ 287 7DJB2XWSXW9DOXH 7DJB(UURU&RGH %,32/$5 The following table shows how the instruction works using specific operand values: Parameter Operand Value IN Tag_InputValue 22 HI_LIM Tag_HighLimit 100.0 LO_LIM Tag_LowLimit 0.0 BIPOLAR Tag_Bipolar 1 OUT Tag_OutputValue 50.03978588 RET_VAL Tag_ErrorCode W#16#0000 See also Overview of the valid data types (Page 1204) Basics of the EN/ENO mechanism (Page 1299) GET_ERR_ID: Get error ID locally (Page 1964) UNSCALE: Unscale Description The "Unscale" instruction is used to unscale the floating-point number on the IN parameter into physical units between a low limit and a high limit and convert it into an integer. You can use the LO_LIM and HI_LIM parameters to specify the low limit and high limit of the value range to which the input value is unscaled. The result of the instruction is output on the OUT parameter. The "Unscale" instruction works with the following equation: OUT = [ ((IN-LO_LIM)/(HI_LIM-LO_LIM)) (K2-K1) ] + K1 The values of the constants "K1" and "K2" are determined by the signal state on the BIPOLAR parameter. The following signal states are possible on the BIPOLAR parameter: WinCC Basic V13.0 System Manual, 02/2014 1943 Programming the PLC 9.7 References Signal state "1": It is assumed that the value at the IN parameter is bipolar and in a value range between -27648 and 27648. In this case the "K1" constant has the value "-27648.0" and the "K2" constant the value "+27648.0". Signal state "0": It is assumed that the value at the IN parameter is unipolar and in a value range between 0 and 27648. In this case the "K1" constant has the value "0.0" and the "K2" constant the value "+27648.0". When the value at the IN parameter is greater than the value of the constant "HI_LIM", the result of the instruction is set to the value of the constant (K2) and an error is output. When the value at the IN parameter is less than the value of the constant of the low limit (LO_LIM), the result of the instruction is set to the value of the constant (K1) and an error is output. Parameters The following table shows the parameters of the "Unscale" instruction: Parameter Declaration Data type Memory area Description EN Input BOOL I, Q, M, D, L Enable input ENO Input BOOL I, Q, M, D, L Enable output IN Input REAL I, Q, M, D, L, P or constant Input value to be unscaled to an integer value. HI_LIM Input REAL I, Q, M, D, L, P or constant High limit LO_LIM Input REAL I, Q, M, D, L, P or constant Low limit BIPOLAR Input BOOL I, Q, M, D, L or constant Indicates if the value at IN parameter is to be interpreted as bipolar or unipolar. The parameter can assume the following values: 1: Bipolar 0: Unipolar 1944 OUT Output INT I, Q, M, D, L, P Result of the instruction RET_VAL Output WORD I, Q, M, D, L, P Error information WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameter RET_VAL The following table shows the meaning of the values of the RET_VAL parameter: Error code* (W#16#...) Explanation 0000 No error 0008 The value of the IN parameter is greater than the value of the high limit (HI_LIM) or less than the value of the low limit (LO_LIM). General error information See also: "GET_ERR_ID: Get error ID locally *The error codes can be displayed as integer or hexadecimal value in the program editor. For information on toggling display formats, refer to "See also". Example The following example shows how the instruction works: 816&$/( 7DJ,Q 7DJB,QSXW9DOXH (1 ,1 7DJB+LJK/LPLW +,B/,0 7DJB/RZ/LPLW /2B/,0 7DJB%LSRODU 7DJ2XW (12 5(7B9$/ 287 7DJB(UURU&RGH 7DJB2XWSXW9DOXH %,32/$5 The following table shows how the instruction works using specific operand values: Parameter Operand Value IN Tag_InputValue 50.03978588 HI_LIM Tag_HighLimit 100.0 LO_LIM Tag_LowLimit 0.0 BIPOLAR Tag_Bipolar 1 OUT Tag_OutputValue 22 RET_VAL Tag_ErrorCode W#16#0000 See also Overview of the valid data types (Page 1204) Basics of the EN/ENO mechanism (Page 1299) GET_ERR_ID: Get error ID locally (Page 1964) WinCC Basic V13.0 System Manual, 02/2014 1945 Programming the PLC 9.7 References Program control operations ---( JMP ): Jump if RLO = 1 Description You can use the "Jump if RLO = 1" instruction to interrupt the linear execution of the program and resume it in another network. The destination network must be identified by a jump label (LABEL). The name of this jump label is specified in the placeholder above the instruction. The specified jump label must be in the same block in which the instruction is executed. The name you specify can only occur once in the block. Only one jumping coil is permitted within a network. If the result of logic operation (RLO) at the input of the instruction is "1", the jump to the network identified by the specified jump label is executed. The jump direction can be towards higher or lower network numbers. If the condition at the input of the instruction is not fulfilled (RLO = 0), execution of the program continues in the next network. Example The following example shows how the instruction works: 1HWZRUN 7DJ,QB &$6 -03 7DJ,QB 7DJ2XWB 5 1HWZRUN 1HWZRUN &$6 7DJ,QB 7DJ2XWB 5 If operand "TagIn_1" has the signal state "1", the "Jump if RLO = 1" instruction is executed. The linear execution of the program is interrupted and continues in Network 3, which is identified by the jump label CAS1. If the "TagIn_3" input has the signal state "1", the "TagOut_3" output is set. 1946 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References ---( JMPN ): Jump if RLO = 0 Description You can use the instruction "Jump if RLO = 0" to interrupt the linear execution of the program and resume it in another network, when the result of logic operation at the input of the instruction is "0". The destination network must be identified by a jump label (LABEL). The name of this jump label is specified in the placeholder above the instruction. The specified jump label must be in the same block in which the instruction is executed. The name you specify can only occur once in the block. Only one jumping coil is permitted within a network. If the result of logic operation (RLO) at the input of the instruction is "0", the jump to the network identified by the specified jump label is executed. The jump direction can be towards higher or lower network numbers. If the result of logic operation at the input of the instruction is "1", execution of the program continues in the next network. Example The following example shows how the instruction works: 1HWZRUN 7DJ,QB &$6 -031 7DJ,QB 7DJ2XWB 5 1HWZRUN 1HWZRUN &$6 7DJ,QB 7DJ2XWB 5 If operand "TagIn_1" has the signal state "0", the "Jump if RLO = 0" instruction is executed. The linear execution of the program is interrupted and continues in Network 3, which is identified by the jump label CAS1. If the "TagIn_3" input has the signal state "1", the "TagOut_3" output is set. See also Overview of the valid data types (Page 1204) WinCC Basic V13.0 System Manual, 02/2014 1947 Programming the PLC 9.7 References LABEL: Jump label Description You can use a jump label to identify a destination network, in which the program execution should resume when a jump is executed. The jump label and the instruction in which the jump label is specified must be located in the same block. The name of a jump label can only be assigned once in a block. You can declare up to 32 jump labels when you use a CPU S7-1200 and a maximum of 256 jump labels when you use a CPU S7-1500. Only one jump label can be placed in a network. Each jump label can jump to several locations. Example The following example shows how the instruction works: 1HWZRUN 7DJ,QB &$6 -03 7DJ,QB 7DJ2XWB 5 1HWZRUN 1HWZRUN &$6 7DJ,QB 7DJ2XWB 5 If operand "TagIn_1" has the signal state "1", the "Jump if RLO = 1" instruction is executed. The linear execution of the program is interrupted and continues in Network 3, which is identified by the jump label CAS1. If the "TagIn_3" input has the signal state "1", the "TagOut_3" output is set. See also Overview of the valid data types (Page 1204) Inserting additional inputs and outputs in LAD elements (Page 1428) Removing inputs and outputs (Page 1429) 1948 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References JMP_LIST: Define jump list Description You can use the "Define jump list" instruction to define several conditional jumps and continue the program execution in a specific network depending on the value of the K parameter. You define the jumps with jump labels (LABEL), which you specify at the outputs of the instruction box. The number of outputs can be expanded in the instruction box. You can declare up to 32 outputs when you use a CPU S7-1200 and a maximum of 99 outputs when you use a CPU S7-1500. The numbering of the outputs begins with the value "0" and continues in ascending order with each new output. Only jump labels can be specified at the outputs of the instruction. Instructions or operands cannot be specified. The value of the K parameter specifies the number of the output and thus the jump label where the program execution is to be resumed. If the value in the K parameter is greater than the number of available outputs, the program execution is resumed in the next network of the block. The "Define jump list" instruction is only executed if the signal state is "1" at the EN enable input. Parameter The following table shows the parameters of the "Define jump list" instruction: Parameters Declaration Data type Memory area Description EN Input BOOL I, Q, M, D, L Enable input K Input UINT I, Q, M, D, L or constant Specifies the number of the output and thus the jump that is to be made. DEST0 - - - First jump label DEST1 - - - Second jump label DESTn - - - Optional jump labels For additional information on valid data types, refer to "See also". WinCC Basic V13.0 System Manual, 02/2014 1949 Programming the PLC 9.7 References Example The following example shows how the instruction works: 7DJB,QSXW 7DJB9DOXH -03B/,67 (1 . '(67 /$%(/ '(67 /$%(/ '(67 /$%(/ The following table shows how the instruction works using specific operand values: Parameters Operand/Jump label Value K Tag_Value 1 Dest0 LABEL0 Jump to the network that is identified with the jump label "LABEL0". Dest1 LABEL1 Jump to the network that is identified with the jump label "LABEL1". Dest2 LABEL2 Jump to the network that is identified with the jump label "LABEL2". If operand "Tag_Input" has the signal state "1", the "Define jump list" instruction is executed. The program execution is resumed according to the value of operand "Tag_Value" in the network that is identified with the jump label "LABEL1". See also Overview of the valid data types (Page 1204) Inserting additional inputs and outputs in LAD elements (Page 1428) Removing inputs and outputs (Page 1429) SWITCH: Jump distributor Description You can use the "Jump distributor" instruction to define multiple program jumps to be executed depending on the result of one or more comparison instructions. You specify the value to be compared in the K parameter. This value is compared with the values that are provided by the various inputs. You can select the comparison method for each individual input. The availability of the various comparison instructions depends on the data type of the instruction. 1950 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References The following table shows the comparison instructions that are available depending on the selected data type: Data type S7-1200 S7-1500 Bit strings Bit strings Integers, floating-point numbers, TIME, DATE, TOD Integers, floating-point numbers, TIME, LTIME, DATE, TOD, LTOD, LDT Instruction Syntax Equal == Not equal <> Equal == Not equal <> Greater or equal >= Less or equal <= Greater than > Less than < You can select the data type of the instruction from the "<???>" drop-down list of the instruction box. If you select a comparison instruction and the data type of the instruction is not yet defined, the "<???>" drop-down list only offers the data types that are permitted for the selected comparison instruction. Execution of the instruction begins with the first comparison and runs until a comparison condition is met. If a comparison condition is met, the subsequent comparison conditions are not considered. If none of the specified comparison conditions are met, the jump at the ELSE output is executed. If no program jump is defined at the ELSE output, execution of the program continues in the next network. The number of outputs can be expanded in the instruction box. The numbering of the outputs begins with the value "0" and continues in ascending order with each new output. Specify jump labels (LABEL) at the outputs of the instruction. Instructions or operands cannot be specified at the outputs of the instruction. An input is automatically inserted for each additional output. The jump programmed at an output is executed if the comparison condition of the corresponding input is fulfilled. Parameters The following table shows the parameters of the "Jump distributor" instruction: Parameter WinCC Basic V13.0 System Manual, 02/2014 Declarati on Data type Memory area Description S7-1200 S7-1500 EN Input BOOL K Input UINT BOOL I, Q, M, D, L Enable input UINT I, Q, M, D, L or constant Specifies the value to be compared. <Comparison values> Input Bit strings, integers, floating-point numbers, TIME, DATE, TOD Bit strings, integers, floating-point numbers, TIME, LTIME, DATE, TOD, LTOD, LDT I, Q, M, D, L or constant Input value with which the value of the K parameter is compared. 1951 Programming the PLC 9.7 References Parameter Declarati on S7-1200 Data type S7-1500 Memory area Description DEST0 - - DEST1 - - - - First jump label - - Second jump label DEST(n) - - - - Optional jump labels(n = 2 to 99) ELSE - - - - Program jump that is executed when none of the comparison conditions are fulfilled. For additional information on valid data types, refer to "See also". Example The following example shows how the instruction works: 6:,7&+ 8,17 7DJB,QSXW (1 7DJB9DOXH . 7DJB9DOXHB '(67 /$%(/ 7DJB9DOXHB ! '(67 /$%(/ 7DJB9DOXHB '(67 /$%(/ (/6( /$%(/ The following table shows how the instruction works using specific operand values: 1952 Parameters Operand/Jump label Value K Tag_Value 23 == Tag_Value_1 20 > Tag_Value_2 21 < Tag_Value_3 19 Dest 0 LABEL0 Jump to jump label "LABEL0", if the value of the K parameter equals 20. Dest 1 LABEL1 Jump to jump label "LABEL1" if the value of the K parameter is greater than 21. WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameters Operand/Jump label Value Dest 2 LABEL2 Jump to jump label "LABEL2", if the value of the K parameter is less than 19. ELSE LABEL 3 Jump to jump label "LABEL3", if the none of the comparison conditions are fulfilled. If the operand "Tag_Input" changes to signal state "1", the instruction "Jump distributor" is executed. The execution of the program is continued in the network that is identified with the jump label "LABEL1". See also Overview of the valid data types (Page 1204) Inserting additional inputs and outputs in LAD elements (Page 1428) Removing inputs and outputs (Page 1429) --(RET): Return Description You can use the "Return" instruction to stop the execution of a block. The results is three types through which the block processing can be completed. Without call of the "Return" instruction The block is exited after execution of the last network. The ENO of the function call is set to the signal state "1". Call of the "Return" instruction with preceding logic operation (see example) If the left connector has the signal state "1", the block will be exited. The ENO of the function call corresponds to the operand. Call of the "Return" instruction without previous logic operation The block is exited. The ENO of the function call corresponds to the operand. Note Only one jumping coil may be used in a network ("Return", "Jump if RLO=1", "Jump if RLO=0"). If the result of logic operation (RLO) at the input of the "Return" instruction is "1", program execution is terminated in the currently called block and resumed after the call function in the calling block (for example, in the calling OB). The status (ENO) of the call function is determined by the parameter of the instruction. This can assume the following values: RLO TRUE/FALSE <Operand> WinCC Basic V13.0 System Manual, 02/2014 1953 Programming the PLC 9.7 References To set the parameter values, double-click the instruction and select the corresponding value in the drop-down list. The following table shows the status of the call function if the "Return" instruction is programmed in a network within the called block: RLO Parameter value ENO of the call function 1 RLO 1 TRUE 1 FALSE 0 <Operand> <Operand> RLO The program execution continues in the next network of the called block. 0 TRUE FALSE <Operand> If an OB is completed, another block will be selected and started or executed by the priority class system: If the program cycle OB was completed, it will be restarted. If an OB is completed that has interrupted another block (for example, an alarm OB), then the interrupted block (for example, program cycle OB) will be executed. Parameters The following table shows the parameters of the "Return" instruction: Parameter Declaration Data type Memory area Description RLO - - Is set to the signal status of the RLO. TRUE - - 1 FALSE - - 0 <Operand> Input BOOL Status of the calling function with RLO = 1: I, Q, M, D, L Signal state of the specified operand Example The following example shows how the instruction works: 7DJ,Q )$/6( 5(7 If operand "TagIn" has the signal state "1", the "Return" instruction is executed. Program execution is terminated in the called block and continues in the calling block. The ENO enable output of the call function is reset to signal state "0". 1954 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References See also Overview of the valid data types (Page 1204) Runtime control ENDIS_PW: Limit and enable password legitimation Description You use the "Limit and enable password legitimation" instruction to specify whether configured passwords may be legitimated or not for the CPU. You can prevent legitimated connections, even when the correct password is known. When you call the command and the REQ parameter has the signal state "0", only the currently set state is displayed at the output parameters. If changes are made to the input parameters, these changes are not transferred to the output parameters. If the instruction is called and REQ parameter has the signal state "1", the signal state is applied from the input parameters (F_PWD, FULL_PWD, R_PWD, HMI_PWD). FALSE means that legitimation per password is not permitted; TRUE means the password can be used. Disable or enabling of the passwords can be allowed or prohibited individually. For example, all passwords can be prohibited, except the fail-safe password. You can thus limit access options to a small user group. The output parameters (F_PWD_ON, FULL_PWD_ON, R_PWD_ON, HMI_PWD_ON) always show the current status of the password use, regardless of the REQ parameter. Non-configured passwords must have the TRUE signal state at the input and return the TRUE signal state at the output. The fail-safe password can only be configured for an F-CPU and, therefore, must always be interconnected with theTRUE signal state in a standard CPU. If the instruction return an error, the call remains without effect, i.e. the previous lock remains in force. Disabled passwords can be enabled again under the following conditions: The CPU is reset to its factory settings. The front panel of the S7-1500 CPU supports a dialog that allows you to navigate to the appropriate menu in which the passwords can be enabled again. When you call the "Limit and enable password legitimation" instruction, the input parameter of the desired password has the signal state "1". Set the operating mode switch to STOP. The restriction to password legitimation is reestablished as soon as the switch is set back to RUN. Inserting an empty memory card (transfer card or program card) into S7-1200 CPU. The transition from POWER OFF to POWER ON disables the protection in the S7-1200 CPU. The "Limit and enable password legitimation" instruction must be called again in the program (e.g. in the startup OB). WinCC Basic V13.0 System Manual, 02/2014 1955 Programming the PLC 9.7 References Note The "Limit and enable password legitimation" instruction blocks access to the HMI system, if the HMI password has not been enabled. Note Existing legitimized connections retain their access rights and you cannot use the "Limit and enable password legitimation" instruction to restrict them. Preventing accidental lockout out with an S7-1500 CPU The same setting can be made on the front panel of the S7-1500 CPU and the CPU saves the most recent setting. To prevent accidental lockout, the protection can be disabled by setting the mode selector to STOP with an S7-1500 CPU. The protection is automatically enabled again by setting mode selector to RUN without having to call the "Limit and enable password legitimation" instruction again or taking additional actions on the front panel. Preventing accidental lockout with an S7-1200 CPU The protection for POWER OFF - POWER ON is disabled because a S7-1200 CPU has no operating mode switch. As a result it is possible and advisable to use certain program sequences within your program to prevent an accidental lockout. To do this, program a time control using either a cyclic interrupt OB or a timer in the main OB (OB 1). This provides you with the option to call the "Limit and enable password legitimation" instruction again without delay in the corresponding OB (e.g. OB 1 or OB 35) after a transition from POWER OFF - POWER ON. Call the instruction in the startup OB (OB 100) in order to keep as short as possible the time window in which the application is not active and thus ensure that no restrictions exist in the password legitimation. This procedure offers you the largest possible protection against unauthorized access. If an unintended lockout occurs you can skip the call in the startup OB (for example, by querying an input parameter) and have the set time (for example 10 seconds to 1 minute), to establish a connection to the CPU before the lock becomes active again. If you have set no timer in your program code and are locked out, insert an empty transfer card or empty program card into the CPU. The empty transfer card or program card deletes the internal load memory of the CPU. You must then load the user program again from STEP 7 in the CPU. Procedure for lost passwords with an S7-1200 CPU If you have lost the password for a password-protected S7-1200 CPU, delete the passwordprotected program with an empty transfer card or program card. The empty transfer card or 1956 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References program card deletes the internal load memory of the CPU. You can then load a new user program from STEP 7 Basic in the CPU. WARNING Inserting empty transfer card When you insert a transfer card in a CPU during runtime, the CPU goes to STOP mode. If operating states are unstable, controllers may fail and thus cause the uncontrolled operation of the controlled devices. This leads to an unforeseen operation of the automation system which can cause deadly or serious injuries and/or damage to property. After you remove the transfer card the content of the transfer card is in the internal load memory. Make sure at this point that the card contains no program. WARNING Inserting empty program card When you insert a program card in a CPU during runtime, the CPU goes to STOP mode. If operating states are unstable, controllers may fail and thus cause the uncontrolled operation of the controlled devices. This leads to an unforeseen operation of the automation system which can cause deadly or serious injuries and/or damage to property. Make sure that the program card is empty. The internal load memory is copied to the empty program card. The internal load memory is empty after the removal of the formerly empty program card. You must remove the transfer card or program card before you put the CPU into RUN mode. WinCC Basic V13.0 System Manual, 02/2014 1957 Programming the PLC 9.7 References Effects of password use on the operating modes The following table shows what effects the password use by means of the "Limit and enable password legitimation" instruction has on the operating modes and the corresponding user actions. Action Password protection by means of the instruction Basic state after Not activated Operating mode switch to STOP (no restrictions) Reset memory manually (PG, switch, change of MC (Motion Control)) Reset to factory setting Basic state after POWER ON S7-1200-CPU: the lock is disabled and the instruction must be called again in the program (in the startup OB, for example). S7-1500 CPU: Enabled (if a lock was activated before POWER OFF). The option of not allowing passwords is retentive. Operating mode transition RUN/STARTUP/HOLD -> STOP (by terminating the instruction, an error or communication) or STOP -> STARTUP/RUN/HOLD Activated Passwords still cannot be used. Parameters The following table shows the parameters of the "Limit and enable password legitimation" instruction: Parameter Declaratio n Data type Memory area Description EN Input BOOL I, Q, M, D, L Enable input ENO Output BOOL I, Q, M, D, L Enable output REQ Input BOOL I, Q, M, D, L or constant When the REQ parameter has the signal state "0", the currently set signal state of the passwords is queried. F_PWD Input BOOL I, Q, M, D, L or constant Read/write access including fail-safe F_PWD = "0": Do not allow password F_PWD = "1": Allow password FULL_PW D Input BOOL I, Q, M, D, L or constant Read/write access FULL_PWD = "0": Do not allow password FULL_PWD = "1": Allow password R_PWD Input BOOL I, Q, M, D, L or constant Read access R_PWD = "0": Do not allow password R_PWD = "1": Allow password HMI_PWD Input BOOL I, Q, M, D, L or constant HMI access HMI_PWD = "0": Do not allow password HMI_PWD = "1": Allow password 1958 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameter Declaratio n Data type Memory area Description F_PWD_O N Output BOOL I, Q, M, D, L Read/write access including fail-safe F_PWD_ON = "0": Password not allowed F_PWD_ON = "1": Password allowed FULL_PW D_ON Output R_PWD_O N Output BOOL I, Q, M, D, L Read/write access status FULL_PWD_ON = "0": Password not allowed FULL_PWD_ON = "1": Password allowed BOOL I, Q, M, D, L Read-access status R_PWD_ON = "0": Password not allowed R_PWD_ON = "1": Password allowed HMI_PWD _ON Output BOOL I, Q, M, D, L HMI-access status HMI_PWD_ON = "0": Password not allowed HMI_PWD_ON = "1": Password allowed RET_VAL Output WORD I, Q, M, D, L Error information For additional information on valid data types, refer to "See also". RET_VAL parameter The following table shows the meaning of the values of the RET_VAL parameter: Error code* Explanation (W#16#...) 0000 No error 8090 The "Limit and enable password legitimation" instruction is not supported 80D0 The password for fail-safe is not configured. With standard CPUs, the signal state must be TRUE. 80D1 The read/write access is not configured 80D2 The read access is not configured 80D3 The HMI access is not configured *The error codes can be displayed as integer or hexadecimal value in the program editor. For information on toggling display formats, refer to "See also". See also Overview of the valid data types (Page 1204) Basics of the EN/ENO mechanism (Page 1299) WinCC Basic V13.0 System Manual, 02/2014 1959 Programming the PLC 9.7 References RE_TRIGR: Restart cycle monitoring time Description You can use the "Restart cycle monitoring time" instruction to restart the cycle time monitoring of the CPU. The maximum cycle time then starts over again for the duration you have set in the CPU configuration. The instruction "Restart cycle monitoring time" can be called regardless of the priority in all blocks. If the instruction is called in a block with a higher priority, such as a hardware interrupt, diagnostic error interrupt, or cyclic interrupt, the instruction is not executed and the ENO enable output is set to signal state "0". The instruction "Restart cycle monitoring time" can be called a maximum of 10 times in a program cycle. Parameter The "Restart cycle monitoring time" instruction has no parameters. See also Overview of the valid data types (Page 1204) Basics of the EN/ENO mechanism (Page 1299) STP: Exit program Description You use the "Exit program" instruction to set the CPU to STOP mode and therefore to terminate the execution of the program. The effects of changing from RUN to STOP depend on the CPU configuration. When the result of logic operation (RLO) at the input of the instruction is "1", the CPU changes to STOP mode and program execution is terminated. The signal state at the output of the instruction is not evaluated. When the RLO is "0" at the input of the instruction, then the instruction will not be executed. Parameters The "Exit program" instruction has no parameters. See also Overview of the valid data types (Page 1204) 1960 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References GET_ERROR: Get error locally Description The "Get error locally" instruction is used to query the occurrence of errors within a block. This is usually to access error. If the system reports an error during the processing of the block, detailed information is stored in the operand at the ERROR output for the first error to occur during the execution of the block since the last execution of the instruction. Only operands of the "ErrorStruct" system data type can be specified at the ERROR output. The "ErrorStruct" system data type specifies the exact structure in which the information about the error is stored. Using additional instructions, you can evaluate this structure and program an appropriate response. If several errors occur in the block, the error information about the next error to occur in the instruction is output only after the first error that occurred has been remedied. Note The ERROR output is only changed if error information is present. To set the output back to "0" after handling an error, you have the following options: Declare the tag in the "Temp" section of the block interface. Reset the tag to "0" before calling the instruction. Query the enable output ENO. The enable output ENO of the instruction "Get error locally" instruction is set only if the enable input EN returns signal state "1" and error information is present. If one of these conditions is not fulfilled, the remaining program execution is not affected by the "Get error locally" instruction. You can find an example of how you can implement the instruction in combination with other troubleshooting options under "See also". Note The "Get error locally" instruction enables local error handling within a block. If "Get error locally" is inserted in the program code of a block, any predefined system reactions are ignored if errors occur. Parameters The following table lists the parameters of the "Get error locally" instruction: WinCC Basic V13.0 System Manual, 02/2014 Parameter Declaration Data type Memory area Description ERROR Output ErrorStruct D, L Error information 1961 Programming the PLC 9.7 References Data type "ErrorStruct" The following table lists the structure of the "ErrorStruct" data type: Structure component Data type Description ERROR_ID WORD Error ID FLAGS BYTE Shows if an error occurred during a block call. 16#01: Error during a block call 16#00: No error during a block call REACTION BYTE Default reaction: 0: Ignore (write error) 1: Continue with substitute value "0" (read error) 2: Skip instruction (system error) CODE_ADDRESS BLOCK_TYPE CREF Information about the address and type of block BYTE Type of block where the error occurred: 1: OB 2: FC 3: FB CB_NUMBER UINT Number of the code block OFFSET UDINT Reference to the internal memory MODE BYTE Information about the address of an operand OPERAND_NUMBER UINT Operand number of the machine command POINTER_NUMBER_LOCATION UINT (A) Internal pointer SLOT_NUMBER_SCOPE UINT (B) Storage area in internal memory DATA_ADDRESS NREF Information about the address of an operand BYTE (C) Memory area: AREA L: 16#40 - 4E, 86, 87, 8E, 8F, C0 - CE I: 16#81 Q: 16#82 M: 16#83 DB: 16#84, 85, 8A, 8B Range violations for a directly editable tag of data type DINT: 16#04 1962 DB_NUMBER UINT (D) Number of the data block OFFSET UDINT (E) Relative address of the operand WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Structure component "ERROR_ID" The following table lists the values that can be output at the structure component "ERROR_ID": ID* (hexadecimal) ID* (decimal) Description 0 0 No error 2503 9475 Invalid pointer 2520 9504 Invalid STRING 2522 9506 Read error: Operand outside the valid range 2523 9507 Write error: Operand outside the valid range 2524 9508 Read error: Invalid operand 2525 9509 Write error: Invalid operand 2528 9512 Read error: Data alignment 2529 9513 Write error: Data alignment 252C 9516 Invalid pointer 2530 9520 Write error: Data block 2533 9523 Invalid pointer used 2538 9528 Access error: DB does not exist 2539 9529 Access error: Wrong DB used 253A 9530 Global data block does not exist 253C 9532 Faulty information or the function does not exist 253D 9533 System function does not exist 253E 9534 Faulty information or the function block does not exist 253F 9535 System block does not exist 2550 9552 Access error: DB does not exist 2551 9553 Access error: Wrong DB used 2575 9589 Error in the program nesting depth 2577 9591 The block property "Parameter passing via registers" is not selected. 2576 9590 Error in the local data distribution 25A0 9632 Internal error in TP 25A1 9633 Tag is write-protected 25A2 9634 Invalid numerical value of tag 2942 10562 Read error: Input 2943 10563 Write error: Output *The error codes can be displayed as integer or hexadecimal value in the program editor. For information on toggling display formats, refer to "See also". WinCC Basic V13.0 System Manual, 02/2014 1963 Programming the PLC 9.7 References Example The following example shows how the instruction works: 08/ $XWR 5HDO )LHOG>LQGH[@ 7DJ2XWB(QDEOHG ! 5($/ )LHOG>LQGH[@ (12 (5525 (12 ,1 287 %<7( (UURU 7DJ2XW ,1 (UURU5($&7,21 *(7B(5525 (1 (1 7DJ2XWB(QDEOHG 5 An error occurred accessing the "#Field[#index]" tag. The enable output ENO of the "Multiply" instruction and the "#TagOut_Enabled" operand have signal state "1" despite the read/access error and the multiplication is performed with the value "0.0". If this error scenario occurs, it is recommended to program the "Get error locally" instruction after the "Multiply" instruction to get the error. The error information supplied by the "Get error locally" instruction is evaluated with the comparison instruction "Equal". If the "#Error.REACTION" structure component has the value "1", this involves a read/access error and the "#TagOut_Enabled" output is reset. See also Overview of the valid data types (Page 1204) Querying and fixing errors in the program code (Page 170) GET_ERR_ID: Get error ID locally Description The "Get error ID locally" instruction is used to query the occurrence of errors within a block. This is usually to access error. If the system reports during the block processing errors within the block execution since the last execution of the instruction, the error ID of the first error that occurred in the tag is stored at the ID output. 1964 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Only operands of the WORD data type can be specified at the ID output. If several errors occur in the block, the error ID of the next error to occur in the instruction is output only after the first error that occurred has been remedied. Note The ID output is only changed if error information is present. To set the output back to "0" after handling an error, you have the following options: Declare the tag in the "Temp" section of the block interface. Reset the tag to "0" before calling the instruction. Query the enable output ENO. The enable output ENO of the instruction "Get error ID locally" instruction is set only if the enable input EN returns signal state "1" and error information is present. If one of these conditions is not fulfilled, the remaining program execution is not affected by the "Get error ID locally" instruction. You can find an example of how you can implement the instruction in combination with other troubleshooting options under "See also". Note The "Get error ID locally" instruction enables local error handling within a block. If the "Get error ID locally" instruction is inserted in the program code of a block, any predefined system reactions are ignored if errors occur. Parameters The following table lists the parameters of the "Get error ID locally" instruction: Parameter Declaration Data type Memory area Description ID Output WORD I, Q, M, D, L Error ID ID parameter The following table lists the values that can be output at the ID parameter: WinCC Basic V13.0 System Manual, 02/2014 ID* (hexadecimal) ID* (decimal) Description 0 0 No error 2503 9475 Invalid pointer 2520 9504 Invalid STRING 2522 9506 Read error: Operand outside the valid range 2523 9507 Write error: Operand outside the valid range 2524 9508 Read error: Invalid operand 2525 9509 Write error: Invalid operand 1965 Programming the PLC 9.7 References ID* (hexadecimal) ID* (decimal) Description 2528 9512 Read error: Data alignment 2529 9513 Write error: Data alignment 252C 9516 Invalid pointer 2530 9520 Write error: Data block 2533 9523 Invalid pointer used 2538 9528 Access error: DB does not exist 2539 9529 Access error: Wrong DB used 253A 9530 Global data block does not exist 253C 9532 Faulty information or the function does not exist 253D 9533 System function does not exist 253E 9534 Faulty information or the function block does not exist 253F 9535 System block does not exist 2550 9552 Access error: DB does not exist 2551 9553 Access error: Wrong DB used 2575 9589 Error in the program nesting depth 2576 9590 Error in the local data distribution 2577 9591 The block property "Parameter passing via registers" is not selected. 25A0 9632 Internal error in TP 25A1 9633 Tag is write-protected 25A2 9634 Invalid numerical value of tag 2942 10562 Read error: Input 2943 10563 Write error: Output *The error codes can be displayed as integer or hexadecimal value in the program editor. For information on toggling display formats, refer to "See also". Example The following example shows how the instruction works: 08/ $XWR 5HDO )LHOG>LQGH[@ 7DJ2XWB(QDEOHG ! 5($/ )LHOG>LQGH[@ (12 ,' 1966 ,1 287 7DJ2XW ,1 7DJ,' *(7B(55B,' (1 (1 (12 029( ,17 7DJ,' (1 (12 ,1 287 7DJ2XW WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References An error occurred accessing the "#Field[#index]" tag. The enable output ENO of the "Multiply" instruction and the "#TagOut_Enabled" operand have signal state "1" despite the read/access error and the multiplication is performed with the value "0.0". If this error scenario occurs, it is recommended to program the "Get error ID locally" instruction after the "Multiply" instruction to get the error. The error information supplied by the "Get error ID locally" instruction is evaluated with the comparison instruction "Equal". If the operand "#TagID" returns the ID 2522, this involves a read/access error and the value "100.0" is written to the "#TagOut" output. See also Overview of the valid data types (Page 1204) Querying and fixing errors in the program code (Page 170) INIT_RD: Initialize all retain data Description You can use the "Initialize all retain data" instruction to reset the retain data of all data blocks, bit memories and SIMATIC timers and counters at the same time. The instruction can only be executed within a startup OB because the execution would exceed the program cycle duration. Parameter The following table shows the parameters of the "Initialize all retain data" instruction: Parameter Declaration Data type Memory area Description EN Input BOOL I, Q, M, D, L Enable input ENO Output BOOL I, Q, M, D, L Enable output REQ Input BOOL I, Q, M, D, L, T, C or constant If the input "REQ" has the signal state "1", all retain data are reset. RET_VAL Output INT I, Q, M, D, L Error information: If an error occurs during execution of the instruction, an error code is output at the RET_VAL parameter. For additional information on valid data types, refer to "See also". WinCC Basic V13.0 System Manual, 02/2014 1967 Programming the PLC 9.7 References Parameters RET_VAL The following table shows the meaning of the values of the RET_VAL parameter: Error code* (W#16#...) Explanation 0000 No error 80B5 The instruction cannot be executed because it was not programmed within a startup OB. General error information See also: "GET_ERR_ID: Get error ID locally *The error codes can be displayed as integer or hexadecimal value in the program editor. For information on toggling display formats, refer to "See also". Example The following example shows how the instruction works: ,1,7B5' 7DJ,QB 7DJB5(4 (1 5(4 7DJ2XW (12 5(7B9$/ 7DJB5HVXOW If the operands "TagIn_1" and "Tag_REQ" have signal state "1", the instruction is executed. The retain data of all data blocks, bit memories and SIMATIC timers and counters are reset If the instruction is executed without errors, the ENO enable output has the signal state "1". See also Overview of the valid data types (Page 1204) Basics of the EN/ENO mechanism (Page 1299) GET_ERR_ID: Get error ID locally (Page 1964) WAIT: Configure time delay Description The "Configure time delay" instruction is used to halt the execution of the program for a set period of time. You indicate the period of time in microseconds on the WT parameter of the instruction. You can configure time delays of up to 32767 microseconds (s). The smallest possible delay time depends on the respective CPU and corresponds to the execution time of the "Configure time delay" instruction. The execution of the instruction can be interrupted by higher priority events. The "Configure time delay" instruction supplies no error information. 1968 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameters The following table shows the parameters of the "Configure time delay" instruction: Parameter Declaration Data type Memory area Description EN Input BOOL I, Q, M, D, L Enable input ENO Output BOOL I, Q, M, D, L Enable output WT Input INT I, Q, M, D, L, P or constant Time delay in microseconds (s) See also Overview of the valid data types (Page 1204) Basics of the EN/ENO mechanism (Page 1299) RUNTIME: Measure program runtime Description The "Measure program runtime" instruction is used to measure the runtime of the entire program, individual blocks or command sequences. If you want to measure the runtime of your entire program, call the instruction "Measure program runtime" in OB1. Measurement of the runtime is started with the first call and the output RET_VAL returns the runtime of the program after the second call. The measured runtime includes all CPU processes that can occur during the program execution, for example, interruptions caused by higher-level events or communication. The instruction "Measure program runtime" reads an internal counter of the CPU and write the value to the IN-OUT parameter MEM. The instruction calculates the current program runtime according to the internal counter frequency and writes it to output RET_VAL. If you want to measure the runtime of individual blocks or individual command sequences, you need three separate networks. Call the instruction "Measure program runtime" in an individual network within your program. You set the starting point of the runtime measurement with this first call of the instruction. Then you call the required program block or the command sequence in the next network. In another network, call the "Measure program runtime" instruction a second time and assign the same memory to the IN-OUT parameter MEM as you did during the first call of the instruction. The "Measure program runtime" instruction in the third network reads an internal CPU counter and calculates the current runtime of the program block or the command sequence according to the internal counter frequency and writes it to the output RET_VAL. WinCC Basic V13.0 System Manual, 02/2014 1969 Programming the PLC 9.7 References The Measure program runtime" instruction uses an internal high-frequency counter to calculate the time. If the counter overruns, the instruction returns values <= 0.0. Ignore these runtime values. Note The runtime of a command sequence cannot be determined exactly, because the sequence of instructions within a command sequence is changed during optimized compilation of the program. Parameter The following table lists the parameters of the "Measure program runtime" instruction: Parameter Declaration Data type Memory area Description EN Input BOOL I, Q, M, D, L Enable input ENO Output BOOL I, Q, M, D, L Enable output MEM InOut LREAL M, D, L Saves the starting point of the runtime measurement. RET_VAL Output LREAL I, Q, M, D, L Returns the measured runtime in seconds For additional information on valid data types, refer to "See also". Example The following example shows how the instruction works based on the runtime calculation of a program block: Network 1: 5817,0( 7DJ,Q 7DJ0HPRU\ (1 (12 0(0 5(7B9$/ 7DJB5HVXOW Network 2: '% %HVWBEHIRUHBGDWHB'% )% %HVWBEHIRUHBGDWH (1 (12 Network 3: 1970 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References 5817,0( 7DJ,Q (1 7DJ0HPRU\ 0(0 (12 5(7B9$/ 7DJ5HVXOWB5XQWLPH When the "TagIn1" operand in network 1 has the signal state "1", the instruction is executed. The starting point for the runtime measurement is set with the first call of the instruction and buffered as reference for the second call of the instruction in the "TagMemory" operand. The "Best_before_date" program block FB1 is called in network 2. When the FB1 program block has been executed and the "TagIn1" operand has the signal state "1", the instruction in network 3 is executed. The second call of the instruction calculates the runtime of the program block and writes the result to the output RET_VAL. See also Overview of the valid data types (Page 1204) Basics of the EN/ENO mechanism (Page 1299) Word logic operations AND: AND logic operation Description You can use the "AND logic operation" instruction to combine the value at the IN1 input and the value at the IN2 input bit-by-bit by AND logic and query the result at the OUT output. When the instruction is executed, bit 0 of the value at the IN1 input and bit 0 of the value at the IN2 input are logically ANDed. The result is stored in bit 0 of output OUT. The same logic operation is executed for all other bits of the specified values. The number of inputs can be expanded in the instruction box. The added inputs are numbered in ascending order in the box. When the instruction is executed, the values of all available input parameters are combined with AND logic (ANDed). The result is stored in the OUT output. The result bit has signal state "1" only when both of the bits in the logic operation also have signal state "1". If one of the two bits of the logic operation has signal state "0", the corresponding result bit is reset. Parameters The following table shows the parameters of the "AND logic operation" instruction: WinCC Basic V13.0 System Manual, 02/2014 Parameter Declaration Data type Memory area Description EN Input BOOL I, Q, M, D, L Enable input ENO Output BOOL I, Q, M, D, L Enable output 1971 Programming the PLC 9.7 References Parameter Declaration Data type Memory area Description IN1 Input Bit strings I, Q, M, D, L, P or constant First value for logic operation IN2 Input Bit strings I, Q, M, D, L, P or constant Second value for logic operation INn Input Bit strings I, Q, M, D, L, P or constant Other inputs whose values are logically combined. OUT Output Bit strings I, Q, M, D, L, P Result of the instruction You can select the data type for the instruction from the "<???>" drop-down list of the instruction box. For additional information on valid data types, refer to "See also". Example The following example shows how the instruction works: 7DJ,Q $1' :25' (1 7DJB9DOXH ,1 7DJB9DOXH ,1 7DJ2XW (12 287 7DJB5HVXOW The following table shows how the instruction works using specific operand values: Parameter Operand Value IN1 Tag_Value1 0101 0101 0101 0101 IN2 Tag_Value2 0000 0000 0000 1111 OUT Tag_Result 0000 0000 0000 0101 If operand "TagIn" has the signal state "1", the "AND logic operation" instruction is executed. The value of operand "Tag_Value1" and the value of operand "Tag_Value2" are ANDed. The result is mapped bit-for-bit and output in operand "Tag_Result". The ENO enable output and the "TagOut" output are set to signal state "1". See also Overview of the valid data types (Page 1204) Inserting additional inputs and outputs in LAD elements (Page 1428) Removing inputs and outputs (Page 1429) Basics of the EN/ENO mechanism (Page 1299) 1972 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References OR: OR logic operation Description You can use the "OR logic operation" instruction to combine the value at the IN1 input and the value at the IN2 input bit-by-bit by OR logic and query the result at the OUT output. When the instruction is executed, bit 0 of the value at the IN1 input and bit 0 of the value at the IN2 input are combined by OR logic operation. The result is stored in bit 0 of output OUT. The same logic operation is executed for all bits of the specified tags. The number of inputs can be expanded in the instruction box. The added inputs are numbered in ascending order in the box. When the instruction is executed, the values of all available input parameters are combined with OR logic (ORed). The result is stored in the OUT output. The result bit has signal state "1" when at least one of the two bits in the logic operation has the signal state "1". If both of the bits of the logic operation have signal state "0", the corresponding result bit is reset. Parameters The following table shows the parameters of the "OR logic operation" instruction: Parameter Declaration Data type Memory area Description EN Input BOOL I, Q, M, D, L Enable input ENO Output BOOL I, Q, M, D, L Enable output IN1 Input Bit strings I, Q, M, D, L, P or constant First value for logic operation IN2 Input Bit strings I, Q, M, D, L, P or constant Second value for logic operation INn Input Bit strings I, Q, M, D, L, P or constant Other inputs whose values are logically combined. OUT Output Bit strings I, Q, M, D, L, P Result of the instruction You can select the data type for the instruction from the "<???>" drop-down list of the instruction box. For additional information on valid data types, refer to "See also". WinCC Basic V13.0 System Manual, 02/2014 1973 Programming the PLC 9.7 References Example The following example shows how the instruction works: 7DJ,Q 25 :25' (1 7DJB9DOXH ,1 7DJB9DOXH ,1 7DJ2XW (12 287 7DJB5HVXOW The following table shows how the instruction works using specific operand values: Parameter Operand Value IN1 Tag_Value1 0101 0101 0101 0101 IN2 Tag_Value2 0000 0000 0000 1111 OUT Tag_Result 0101 0101 0101 1111 If operand "TagIn" has the signal state "1", the "OR logic operation" instruction is executed. The value of operand "Tag_Value1" and the value of operand "Tag_Value2" are ORed. The result is mapped bit-for-bit and output in operand "Tag_Result". The ENO enable output and the "TagOut" output are set to signal state "1". See also Overview of the valid data types (Page 1204) Inserting additional inputs and outputs in LAD elements (Page 1428) Removing inputs and outputs (Page 1429) Basics of the EN/ENO mechanism (Page 1299) XOR: EXCLUSIVE OR logic operation Description You can use the "EXCLUSIVE OR logic operation" instruction to combine the value at the IN1 input and the value at the IN2 input bit-by-bit by EXCLUSIVE OR logic and query the result at the OUT output. When the instruction is executed, bit 0 of the value at the IN1 input and bit 0 of the value at the IN2 input are combined by EXCLUSIVE OR logic operation. The result is stored in bit 0 of output OUT. The same logic operation is executed for all other bits of the specified value. The number of inputs can be expanded in the instruction box. The added inputs are numbered in ascending order in the box. When the instruction is executed, the values of all available input parameters are combined with EXCLUSIVE OR logic. The result is stored in the OUT output. The result bit has signal state "1" when one of the two bits in the logic operation has the signal state "1". If both of the bits of the logic operation have signal state "1" or "0", the corresponding result bit is reset. 1974 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameters The following table shows the parameters of the "EXCLUSIVE OR logic operation" instruction: Parameter Declaration Data type Memory area Description EN Input BOOL I, Q, M, D, L Enable input ENO Output BOOL I, Q, M, D, L Enable output IN1 Input Bit strings I, Q, M, D, L, P or constant First value for logic operation IN2 Input Bit strings I, Q, M, D, L, P or constant Second value for logic operation INn Input Bit strings I, Q, M, D, L, P or constant Other inputs whose values are logically combined. OUT Output Bit strings I, Q, M, D, L, P Result of the instruction You can select the data type for the instruction from the "<???>" drop-down list of the instruction box. For additional information on valid data types, refer to "See also". Example The following example shows how the instruction works: 7DJ,Q ;25 :25' (1 7DJB9DOXH ,1 7DJB9DOXH ,1 7DJ2XW (12 287 7DJB5HVXOW The following table shows how the instruction works using specific operand values: Parameter Operand Value IN1 Tag_Value1 0101 0101 0101 0101 IN2 Tag_Value2 0000 0000 0000 1111 OUT Tag_Result 0101 0101 0101 1010 If operand "TagIn" has the signal state "1", the "EXCLUSIVE OR logic operation" instruction is executed. The value of operand "Tag_Value1" and the value of operand "Tag_Value2" are combined by EXCLUSIVE OR logic. The result is mapped bit-for-bit and output in operand "Tag_Result". The ENO enable output and the "TagOut" output are set to signal state "1". See also Overview of the valid data types (Page 1204) Inserting additional inputs and outputs in LAD elements (Page 1428) WinCC Basic V13.0 System Manual, 02/2014 1975 Programming the PLC 9.7 References Removing inputs and outputs (Page 1429) Basics of the EN/ENO mechanism (Page 1299) INV: Create ones complement Description You can use the "Create ones complement" instruction to invert the signal state of the bits at the IN input. When the instruction is processed, the value at the IN input and a hexadecimal template (W#16#FFFF for 16-bit numbers or DW#16#FFFF FFFF for 32-bit numbers) are combined by EXCLUSIVE OR logic. This inverts the signal state of the individual bits that are then stored at output OUT. Parameters The following table shows the parameters of the "Create ones complement" instruction: Parameter Declaration Data type Memory area Description EN Input BOOL I, Q, M, D, L Enable input ENO Output BOOL I, Q, M, D, L Enable output IN Input Bit strings, integers I, Q, M, D, L, P or constant Input value OUT Output Bit strings, integers I, Q, M, D, L, P Ones complement of the value at input IN You can select the data type for the instruction from the "<???>" drop-down list of the instruction box. For additional information on valid data types, refer to "See also". Example The following example shows how the instruction works: ,19 :25' 7DJ,Q 7DJ,QB9DOXH (1 (12 ,1 287 7DJ2XW 7DJ2XWB9DOXH The following table shows how the instruction works using specific operand values: 1976 Parameter Operand Value IN TagIn_Value W#16#000F W#16#7E OUT TagOut_Value W#16#FFF0 W#16#81 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References If operand "TagIn" has the signal state "1", the "Create ones complement" instruction is executed. The instruction inverts the signal state of the individual bits at input TagIn_Value" and writes the result to output "TagOut_Value". The ENO enable output and the "TagOut" output are set to signal state "1". See also Overview of the valid data types (Page 1204) Basics of the EN/ENO mechanism (Page 1299) DECO: Decode Description You can use the "Decode" instruction to set a bit in the output value specified by the input value. The "Decode" instruction reads the value at the IN input and sets the bit in the output value whose bit position corresponds to the read value. The other bits in the output value are filled with zeroes. When the value at the IN input is greater than 31, a modulo 32 instruction is executed. Parameters The following table shows the parameters of the "Decode" instruction: Parameter Declaration Data type Memory area Description EN Input BOOL I, Q, M, D, L Enable input ENO Output BOOL I, Q, M, D, L Enable output IN Input UINT I, Q, M, D, L, P or constant Position of the bit in the output value which is set. OUT Output Bit strings I, Q, M, D, L, P Output value You can select the data type for the instruction from the "<???>" drop-down list of the instruction box. For additional information on valid data types, refer to "See also". WinCC Basic V13.0 System Manual, 02/2014 1977 Programming the PLC 9.7 References Example The following example shows how the instruction works: '(&2 7DJ,Q 7DJ,QB9DOXH 8,17 WR ':25' (1 (12 ,1 287 7DJ2XW 7DJ2XWB9DOXH The following figure shows how the instruction works using specific operand values: 7DJ,QB9DOXH 7DJ2XWB9DOXH If operand "TagIn" has the signal state "1", the "Decode" instruction is executed. The instruction reads bit number "3" from the value of the operand "TagIn_Value" at the input and sets the third bit to the value of the operand "TagOut_Value" at the output. If the instruction is executed without errors, the ENO enable output has the signal state "1" and the "TagOut" output is set. See also Overview of the valid data types (Page 1204) Basics of the EN/ENO mechanism (Page 1299) ENCO: Encode Description You can use the "Encode" instruction to read the bit number of the least significant bit in the input value and to send it to the OUT output. The "Encode" instruction selects the least significant bit of the value at the IN input and writes its bit number to the tag in the OUT output. Parameters The following table shows the parameters of the "Encode" instruction: 1978 Parameter Declaration Data type Memory area Description EN Input BOOL I, Q, M, D, L Enable input ENO Output BOOL I, Q, M, D, L Enable output WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameter Declaration Data type Memory area Description IN Input Bit strings I, Q, M, D, L, P or constant Input value OUT Output INT I, Q, M, D, L, P Output value You can select the data type for the instruction from the "<???>" drop-down list of the instruction box. For additional information on valid data types, refer to "See also". Example The following example shows how the instruction works: (1&2 ':25' 7DJ,Q 7DJ,QB9DOXH (1 (12 ,1 287 7DJ2XW 7DJ2XWB9DOXH The following figure shows how the instruction works using specific operand values: 7DJ,QB9DOXH 7DJ2XWB9DOXH If operand "TagIn" has the signal state "1", the "Encode" instruction is executed. The instruction selects the least significant bit at the "TagIn_Value" input and writes bit position "3" to the tag in the "TagOut_Value" output. If the instruction is executed without errors, the ENO enable output has the signal state "1" and the "TagOut" output is set. See also Overview of the valid data types (Page 1204) Basics of the EN/ENO mechanism (Page 1299) SEL: Select Description Depending on a switch (G input), the "Select" instruction selects one of the inputs, IN0 or IN1 and copies its content to the OUT output. When the G input has the signal state "0", the value at the IN0 input is moved. When the G input has the signal state "1", the value at the IN1 input is moved to the OUT output. All tags at all parameters must have the same data type. WinCC Basic V13.0 System Manual, 02/2014 1979 Programming the PLC 9.7 References Parameters The following table shows the parameters of the "Select" instruction: Parameter Declaration Data type Memory area S7-1200 S7-1500 S7-1200 S7-1500 Description EN Input BOOL BOOL I, Q, M, D, L I, Q, M, D, L Enable input ENO Output BOOL BOOL I, Q, M, D, L I, Q, M, D, L Enable output G Input BOOL BOOL I, Q, M, D, L or constant I, Q, M, D, L, T, Switch C or constant IN0 Input Bit strings, integers, floating-point numbers, TIME, TOD, CHAR, DATE Bit strings, integers, floating-point numbers, timers, TOD, LTOD, LDT, CHAR, DATE I, Q, M, D, L, P or constant I, Q, M, D, L, P or constant First input value IN1 Input Bit strings, integers, floating-point numbers, TIME, TOD, CHAR, DATE Bit strings, integers, floating-point numbers, timers, TOD, LTOD, LDT, CHAR, DATE I, Q, M, D, L, P or constant I, Q, M, D, L, P or constant Second input value OUT Output Bit strings, integers, floating-point numbers, TIME, TOD, CHAR, DATE Bit strings, integers, floating-point numbers, timers, TOD, LTOD, LDT, CHAR, DATE I, Q, M, D, L, P I, Q, M, D, L, P Result You can select the data type for the instruction from the "<???>" drop-down list of the instruction box. For additional information on valid data types, refer to "See also". Example The following example shows how the instruction works: 7DJ,Q 7DJ,QB* 1980 6(/ :25' (1 (12 * 287 7DJ,QB9DOXH ,1 7DJ,QB9DOXH ,1 7DJ2XW 7DJ2XWB9DOXH WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References The following table shows how the instruction works using specific operand values: Parameter Operand Value G TagIn_G 0 1 IN0 TagIn_Value0 W#16#0000 W#16#4C IN1 TagIn_Value1 W#16#FFFF W#16#5E OUT TagOut_Value W#16#0000 W#16#5E If operand "TagIn" has the signal state "1", the "Select" instruction is executed. Based on the signal state at the "TagIn_G" input, the value at the "TagIn_Value0" or "TagIn_Value1" input is selected and copied to the "TagOut_Value" output. If the instruction is executed without errors, enable output ENO has the signal state "1" and the "TagOut" output is set. See also Overview of the valid data types (Page 1204) Basics of the EN/ENO mechanism (Page 1299) MUX: Multiplex Description You can use the "Multiplex" instruction to copy the content of a selected input to the OUT output. The number of selectable inputs of the instruction box can be expanded. You can declare a maximum of 32 inputs. The inputs are automatically numbered in the box. Numbering starts at IN0 and continues consecutively with each new input. You use the K parameter to define the input whose content is to be copied to the OUT output. If the value of the K parameter is greater than the number of available inputs, the content of the ELSE parameter is copied to the OUT output and the ENO enable output is assigned the signal state "0". The "Multiplex" instruction can only be executed, when the tags in all inputs and in the OUT output have the same data type. The K parameter is an exception, since only integers can be specified for it. The ENO enable output is reset if one of the following conditions is fulfilled: The EN enable input has the signal state "0". The value of the K parameter is greater than the number of available inputs. Errors occurred during execution of the instruction. WinCC Basic V13.0 System Manual, 02/2014 1981 Programming the PLC 9.7 References Parameters The following table shows the parameters of the "Multiplex" instruction: Parameter Declaration Data type S7-1200 S7-1500 Memory area Description Enable input EN Input BOOL BOOL I, Q, M, D, L ENO Output BOOL BOOL I, Q, M, D, L Enable output K Input Integers Integers I, Q, M, D, L, P or constant Specifies the input whose content is to be copied. If K = 0 => Parameter IN0 If K = 1 => Parameter IN1, etc. 1982 IN0 Input Binary numbers, integers, floating-point numbers, strings, TIME, TOD, DATE Binary numbers, integers, floating-point numbers, strings, timers, TOD, LTOD, DATE, LDT I, Q, M, D, L, P or constant First input value IN1 Input Binary numbers, integers, floating-point numbers, strings, TIME, TOD, DATE Binary numbers, integers, floating-point numbers, strings, timers, TOD, LTOD, DATE, LDT I, Q, M, D, L, P or constant Second input value INn Input Binary numbers, integers, floating-point numbers, strings, TIME, TOD, DATE Binary numbers, integers, floating-point numbers, strings, timers, TOD, LTOD, DATE, LDT I, Q, M, D, L, P or constant Optional input values WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameter Declaration Data type S7-1200 S7-1500 Memory area Description Specifies the value to be copied when K > n. ELSE Input Binary numbers, integers, floating-point numbers, strings, TIME, TOD, DATE Binary numbers, integers, floating-point numbers, strings, timers, TOD, LTOD, DATE, LDT I, Q, M, D, L, P or constant OUT Output Binary numbers, integers, floating-point numbers, strings, TIME, TOD, DATE Binary numbers, integers, floating-point numbers, strings, timers, TOD, LTOD, DATE, LDT I, Q, M, D, L, P Output to which the value is to be copied. You can select the data type for the instruction from the "<???>" drop-down list of the instruction box. For additional information on valid data types, refer to "See also". Example The following example shows how the instruction works: 7DJB,QSXW 08; ':25' (1 (12 7DJB1XPEHU . 287 7DJB9DOXHB ,1 7DJB9DOXHB ,1 7DJB9DOXHB (/6( 7DJB2XWSXW 6 7DJB5HVXOW The following table shows how the instruction works using specific operand values: Parameter Operand Value K Tag_Number 1 IN0 Tag_Value_0 DW#16#00000000 IN1 Tag_Value_1 DW#16#003E4A7D ELSE Tag_Value_2 DW#16#FFFF0000 OUT Tag_Result DW#16#003E4A7D If operand "Tag_Input" has the signal state "1", the "Multiplex" instruction is executed. Depending on the value of the operand "Tag_Number", the value at input "Tag_Value_1" is copied and assigned to the operand at output "Tag_Result". If the instruction is executed without errors, the "ENO" and "Tag_Output" enable outputs are set. WinCC Basic V13.0 System Manual, 02/2014 1983 Programming the PLC 9.7 References See also Overview of the valid data types (Page 1204) Basics of the EN/ENO mechanism (Page 1299) DEMUX: Demultiplex Description You can use the "Demultiplex" instruction to copy the content of the IN input to the selected output. The number of selectable outputs can be expanded in the instruction box. The outputs are automatically numbered in the box. Numbering starts at OUT0 and continues consecutively with each new output. You use the K parameter to define the output to which the content of the IN input is to be copied. The other outputs are not changed. If the value of the parameter K is greater than the number of available outputs, then the content of input IN in the parameter ELSE and the enable output ENO will be assigned to the signal state "0". The "Demultiplex" instruction can only be executed if the tags in the IN input and in all outputs have the same data type. The K parameter is an exception, since only integers can be specified for it. The ENO enable output is reset if one of the following conditions is fulfilled: The EN enable input has the signal state "0". The value of the K parameter is greater than the number of available outputs. Errors occurred during execution of the instruction. Parameters The following table shows the parameters of the "Demultiplex" instruction: Parameter Declaration Data type S7-1200 S7-1500 Memory area Description EN Input BOOL BOOL I, Q, M, D, L Enable input ENO Output BOOL BOOL I, Q, M, D, L Enable output K Input Integers Integers I, Q, M, D, L, P or constant Specifies the output to which the input value (IN) is copied. If K = 0 => Parameter OUT0 If K = 1 => Parameter OUT1, etc. 1984 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameter Declaration Data type S7-1200 S7-1500 Memory area Description Input value IN Input Binary numbers, integers, floating-point numbers, strings, TIME, TOD, DATE Binary numbers, integers, floating-point numbers, strings, timers, TOD, LTOD, DATE, LDT I, Q, M, D, L, P or constant OUT0 Output Binary numbers, integers, floating-point numbers, strings, TIME, TOD, DATE Binary numbers, integers, floating-point numbers, strings, timers, TOD, LTOD, DATE, LDT I, Q, M, D, L, P First output OUT1 Output Binary numbers, integers, floating-point numbers, strings, TIME, TOD, DATE Binary numbers, integers, floating-point numbers, strings, timers, TOD, LTOD, DATE, LDT I, Q, M, D, L, P Second output OUTn Output Binary numbers, integers, floating-point numbers, strings, TIME, TOD, DATE Binary numbers, integers, floating-point numbers, strings, timers, TOD, LTOD, DATE, LDT I, Q, M, D, L, P Optional outputs ELSE Output Binary numbers, integers, floating-point numbers, strings, TIME, TOD, DATE Binary numbers, integers, floating-point numbers, strings, timers, TOD, LTOD, DATE, LDT I, Q, M, D, L, P Output to which the input value (IN) at K > n is copied. You can select the data type for the instruction from the "<???>" drop-down list of the instruction box. For additional information on available data types, refer to "See also". WinCC Basic V13.0 System Manual, 02/2014 1985 Programming the PLC 9.7 References Example The following example shows how the instruction works: '(08; 7DJB,QSXW 7DJB1XPEHU 7DJB9DOXH ':25' 7DJB2XWSXW 6 (1 (12 . 287 7DJB2XWSXWB ,1 287 7DJB2XWSXWB (/6( 7DJB2XWSXWB The following tables show how the instruction works using specific operand values: Table 9-24 Input values of the "Demultiplex" instruction before network execution Parameter Operand K Tag_Number 1 4 IN Tag_Value DW#16#FFFFFFFF DW#16#003E4A7D Table 9-25 Values Output values of the "Demultiplex" instruction after network execution Parameter Operand Values OUT0 Tag_Output_0 Unchanged Unchanged OUT1 Tag_Output_1 DW#16#FFFFFFFF Unchanged ELSE Tag_Output_2 Unchanged DW#16#003E4A7D If the "Tag_Input" input has the signal state"1", the "Demultiplex" instruction is executed. Depending on the value of operand "Tag_Number", the value at the IN input is copied to the corresponding output. See also Overview of the valid data types (Page 1204) Basics of the EN/ENO mechanism (Page 1299) Shift and rotate SHR: Shift right Description You can use the "Shift right" instruction to rotate the content of the operand at the input INbitby-bit to the right and query the result at the OUT output. You use the N parameter to specify the number of bit positions by which the specified value is to be shifted. When the value at the N parameter is "0", the value at the IN input is copied to the operand at the OUT output. 1986 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References When the value at the N parameter is greater than the number of available bit positions, the operand value at the IN input is shifted by the available number of bit positions to the right. In the case of unsigned values, the freed bit positions in the left area of the operand are filled with zeroes when shifting occurs. If the specified value has a sign, the free bit positions are filled with the signal state of the sign bit. The following figure show how the content of an operand of integer data type is shifted four bit positions to the right: ,1 1 287 6LJQ ELW SODFHV 7KHVHIRXUELWV DUHORVW 7KHIUHHGELWSRVLWLRQV DUHILOOHGE\WKHVLJQDOVWDWXV RIWKHVLJQELW Parameters The following table shows the parameters of the "Shift right" instruction: Parameter Declaration Data type S7-1200 S7-1500 Memory area Description EN Input BOOL BOOL I, Q, M, D, L Enable input ENO Output BOOL BOOL I, Q, M, D, L Enable output IN Input Bit strings, integers Bit strings, integers I, Q, M, D, L or constant Value to be shifted N Input USINT, UINT, UDINT USINT, UINT, UDINT, ULINT I, Q, M, D, L or constant Number of bit positions by which the value is shifted OUT Output Bit strings, integers Bit strings, integers I, Q, M, D, L Result of the instruction You can select the data type of the instruction from the "<???>" drop-down list of the instruction box. For additional information on valid data types, refer to "See also". WinCC Basic V13.0 System Manual, 02/2014 1987 Programming the PLC 9.7 References Example The following example shows how the instruction works: 6+5 :25' 7DJ,Q 7DJ,QB9DOXH 7DJB1XPEHU (1 ,1 1 (12 287 7DJ2XW 6 7DJ2XWB9DOXH The following table shows how the instruction works using specific operand values: Parameter Operand Value IN TagIn_Value 0011 1111 1010 1111 N Tag_Number 3 OUT TagOut_Value 0000 0111 1111 0101 If operand "TagIn" has the signal state "1", the "Shift right" instruction is executed. The content of operand "TagIn_Value" is shifted three bit positions to the right. The result is sent to the "TagOut_Value" output. If the instruction is executed without errors, the ENO enable output has the signal state "1" and the "TagOut" output is set. See also Overview of the valid data types (Page 1204) Basics of the EN/ENO mechanism (Page 1299) SHL: Shift left Description You can use the "Shift left" instruction to rotate the content of the operand at the IN input bitby-bit to the left and query the result at the OUT output. You use the N parameter to specify the number of bit positions by which the specified value is to be shifted. When the value at the N parameter is "0", the value at the IN input is copied to the operand at the OUT output. When the value at the N parameter is greater than the number of available bit positions, the operand value at the IN input is shifted by the available number of bit positions to the left. The bit positions in the right part of the operand freed by shifting are filled with zeros. The following figure shows how the content of an operand of the WORD data type is shifted by six bit positions to the left: 1988 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References ,1 1 287 SODFHV 7KHIUHHGELW SRVLWLRQVDUHILOOHGE\ ]HURV 7KHVHVL[ELWV DUHORVW Parameters The following table shows the parameters of the "Shift left" instruction: Parameter Declaration Data type S7-1200 S7-1500 Memory area Description EN Input BOOL BOOL I, Q, M, D, L Enable input ENO Output BOOL BOOL I, Q, M, D, L Enable output IN Input Bit strings, integers Bit strings, integers I, Q, M, D, L or constant Value to be shifted N Input USINT, UINT, UDINT USINT, UINT, UDINT, ULINT I, Q, M, D, L or constant Number of bit positions by which the value is shifted OUT Output Bit strings, integers Bit strings, integers I, Q, M, D, L Result of the instruction You can select the data type of the instruction from the "<???>" drop-down list of the instruction box. For additional information on valid data types, refer to "See also". WinCC Basic V13.0 System Manual, 02/2014 1989 Programming the PLC 9.7 References Example The following example shows how the instruction works: 6+/ :25' 7DJ,Q 7DJ,QB9DOXH 7DJB1XPEHU (1 ,1 1 (12 287 7DJ2XW 6 7DJ2XWB9DOXH The following table shows how the instruction works using specific operand values: Parameter Operand Value IN TagIn_Value 0011 1111 1010 1111 N Tag_Number 4 OUT TagOut_Value 1111 1010 1111 0000 If operand "TagIn" has the signal state "1", the "Shift left" instruction is executed. The content of operand "TagIn_Value" is shifted four bit positions to the left. The result is sent to the "TagOut_Value" output. If the instruction is executed without errors, the ENO enable output has the signal state "1" and the "TagOut" output is set. See also Overview of the valid data types (Page 1204) Basics of the EN/ENO mechanism (Page 1299) ROR: Rotate right Description You can use the "Rotate right" instruction to rotate the content of the operand at the IN input bit-by-bit to the right and query the result at the OUT output. You use the N parameter to specify the number of bit positions by which the specified value is to be rotated. The bit positions freed by rotating are filled with the bit positions that are pushed out. When the value at the N parameter is "0", the value at the IN input is copied to the operand at the OUT output. When the value at the N parameter is greater than the number of available bit positions, the operand value at the IN input is nevertheless rotated by the specified number of bit positions. The following figure shows how the content of an operand of DWORD data type is rotated three positions to the right: 1990 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References ,1 1 SODFHV 287 7KHVLJQDOVWDWXVRIWKHWKUHH VKLIWHGELWVDUHLQVHUWHGLQWR WKHIUHHGSODFHV Parameters The following table shows the parameters of the "Rotate right" instruction: Parameter Declaration Data type S7-1200 S7-1500 Memory area Description EN Input BOOL BOOL I, Q, M, D, L Enable input ENO Output BOOL BOOL I, Q, M, D, L Enable output IN Input Bit strings, integers Bit strings, integers I, Q, M, D, L or constant Value to be rotated N Input USINT, UINT, UDINT USINT, UINT, UDINT, ULINT I, Q, M, D, L or constant Number of bit positions by which the value is rotated OUT Output Bit strings, integers Bit strings, integers I, Q, M, D, L Result of the instruction You can select the data type of the instruction from the "<???>" drop-down list of the instruction box. For additional information on valid data types, refer to "See also". WinCC Basic V13.0 System Manual, 02/2014 1991 Programming the PLC 9.7 References Example The following example shows how the instruction works: 525 :25' 7DJ,Q 7DJ,QB9DOXH 7DJB1XPEHU (1 ,1 1 (12 287 7DJ2XW 6 7DJ2XWB9DOXH The following table shows how the instruction works using specific operand values: Parameter Operand Value IN TagIn_Value 0000 1111 1001 0101 N Tag_Number 5 OUT TagOut_Value 1010 1000 0111 1100 If operand "TagIn" has the signal state "1", the "Rotate right" instruction is executed. The content of operand "TagIn_Value" is rotated five bit positions to the right. The result is sent to the "TagOut_Value" output. If the instruction is executed without errors, the ENO enable output has the signal state "1" and the "TagOut" output is set. See also Overview of the valid data types (Page 1204) Basics of the EN/ENO mechanism (Page 1299) ROL: Rotate left Description You can use the "Rotate left" instruction to rotate the content of the operand at the IN input bitby-bit to the left and query the result at the OUT output. You use the N parameter to specify the number of bit positions by which the specified value is to be rotated. The bit positions freed by rotating are filled with the bit positions that are pushed out. When the value at the N parameter is "0", the value at the IN input is copied to the operand at the OUT output. When the value at the N parameter is greater than the number of available bit positions, the operand value at the IN input is nevertheless rotated by the specified number of bit positions. The following figure shows how the content of an operand of DWORD data type is rotated three positions to the left: 1992 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References ,1 1 287 SODFHV 7KHVLJQDOVWDWXVRIWKHWKUHH VKLIWHGELWVDUHLQVHUWHGLQWR WKHIUHHGSODFHV Parameters The following table shows the parameters of the "Rotate left" instruction: Parameter Declaration Data type S7-1200 S7-1500 Memory area Description EN Input BOOL BOOL I, Q, M, D, L Enable input ENO Output BOOL BOOL I, Q, M, D, L Enable output IN Input Bit strings, integers Bit strings, integers I, Q, M, D, L or constant Value to be rotated N Input USINT, UINT, UDINT USINT, UINT, UDINT, ULINT I, Q, M, D, L or constant Number of bit positions by which the value is rotated OUT Output Bit strings, integers Bit strings, integers I, Q, M, D, L Result of the instruction You can select the data type of the instruction from the "<???>" drop-down list of the instruction box. For additional information on valid data types, refer to "See also". WinCC Basic V13.0 System Manual, 02/2014 1993 Programming the PLC 9.7 References Example The following example shows how the instruction works: 52/ :25' 7DJ,Q 7DJ,QB9DOXH 7DJB1XPEHU (1 ,1 1 (12 287 7DJ2XW 6 7DJ2XWB9DOXH The following table shows how the instruction works using specific operand values: Parameter Operand Value IN TagIn_Value 1010 1000 1111 0110 N Tag_Number 5 OUT TagOut_Value 0001 1110 1101 0101 If the "TagIn" input has the signal state "1", the "Rotate left" instruction is executed. The content of operand "TagIn_Value" is rotated five bit positions to the left. The result is sent to the "TagOut_Value" output. If the instruction is executed without errors, the ENO enable output has the signal state "1" and the "TagOut" output is set. See also Overview of the valid data types (Page 1204) Basics of the EN/ENO mechanism (Page 1299) Additional instructions DRUM: Implement sequencer Description You can use the "Implement sequencer" instruction to assign the programmed values of the OUT_VAL parameter of the corresponding step to the programmed output bits (OUT1 to OUT16) and the output word (OUT_WORD). The specific step must thereby satisfy the conditions of the programmed enable mask on the S_MASK parameter while the instruction remains at this step. The instruction advances to the next step if the event for the step is true and the programmed time for the current step elapses or if the value at the JOG parameter changes from "0" to "1". The instruction is reset if the signal state on the RESET parameter changes to "1". The current step is hereby equated to the preset step (DSP). The amount of time spent on a step is determined by the product of the preset timebase (DTBP) and the preset counter value (S_PRESET) for each step. At the start of a new step, this calculated value is loaded into the DCC parameter, which contains the time remaining for the current step. If, for example the value of the DTBP parameter is "2" and the preset value for the first step is "100" (100 ms), the DCC parameter has the value "200" (200 ms). 1994 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References A step can be programmed with a timer value, an event or both. Steps that have an event bit and the timer value "0" advance to the next step as soon as the signal state of the event bit is "1". Steps that are programmed only with a timer value start the time immediately. Steps that are programmed with an event bit and a timer value greater than "0" start the time when the signal state of the event bit is "1". The event bits are initialized with a signal state of "1". When the sequencer is on the last programmed step (LST_STEP) and the time for this step has expired, the signal state on the Q parameter is set to "1"; otherwise it is set to "0". When the parameter Q is set, the instruction remains on the step until it is reset. In the configurable mask (S_MASK) you can selected the separate bits in the output word (OUT_WORD) and set or reset the output bits (OUT1 to OUT16) by means of the output values (OUT_VAL). If a bit of the configurable mask is in the signal state "1", the value OUT_VAL sets or resets the corresponding bit. If the signal state of a bit of the configurable mask is "0", the corresponding bit is left unchanged. All the bits of the configurable mask for all 16 steps are initialized with a signal state of "1". The output bit at the OUT1 parameter corresponds to the least significant bit of the output word (OUT_WORD). The output bit at the OUT16 parameter corresponds to the most significant bit of the output word (OUT_WORD). When you insert the instruction in the program, the "Call options" dialog opens in which you can specify whether the block parameters will be stored in a separate data block (single instance) or as a local tag (multi-instance) in the block interface. If you create a separate data block, you will find it in the project tree in the "Program resources" folder under "Program blocks > System blocks". For additional information on this topic, refer to "See also". Parameters The following table shows the parameters of the "Implement sequencer" instruction: WinCC Basic V13.0 System Manual, 02/2014 Parameter Declaration Data type Memory area Description EN Input BOOL I, Q, M, D, L Enable input ENO Output BOOL I, Q, M, D, L Enable output RESET Input BOOL I, Q, M, D, L or constant The signal state "1" indicates the reset condition. JOG Input BOOL I, Q, M, D, L or constant When the signal state changes from "0" to "1", the instruction advances to the next step. DRUM_EN Input BOOL I, Q, M, D, L or constant The signal state "1" causes the sequencer to advance based on the event and time criteria. LST_STEP Input BYTE I, Q, M, D, L or constant Number of the last programmed step. 1995 Programming the PLC 9.7 References Parameter Declaration Data type Memory area Description EVENT(i), Input BOOL I, Q, M, D, L or constant Event bit (i); 1 i 16 OUT(j), Initial signal state is "1". Output BOOL I, Q, M, D, L Output bit (j) Q Output BOOL I, Q, M, D, L The signal state "1" indicates that the time for the last step has elapsed. OUT_WORD Output WORD I, Q, M, D, L, P Word address to which the sequencer writes the output values. ERR_CODE Output WORD I, Q, M, D, L, P Error information JOG_HIS Static BOOL I, Q, M, D, L JOG parameter history bit EOD Static BOOL I, Q, M, D, L or constant The signal state "1" indicates that the time for the last step has elapsed. DSP Static BYTE I, Q, M, D, L, P or constant Preset step of the sequencer DSC Static BYTE I, Q, M, D, L, P or constant Current step of the sequencer DCC Static DWORD I, Q, M, D, L, P or constant Current numerical value of the sequencer DTBP Static WORD I, Q, M, D, L, P or constant Preset timebase of the sequencer PREV_TIME Static DWORD I, Q, M, D, L or constant Previous system time S_PRESET Static ARRAY of WORD I, Q, M, D, L or constant Preset count for each step [1 to 16] where 1 clock pulse = 1 ms. OUT_VAL Static ARRAY of BOOL I, Q, M, D, L or constant Output values for each step [1 to 16, 0 to 15]. S_MASK Static ARRAY of BOOL I, Q, M, D, L or constant Configurable mask for each step [1 to 16, 0 to 15]. Initial signal states are "1". 1 j 16 For additional information on valid data types, refer to "See also". 1996 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameters ERR_CODE The following table shows the meaning of the values of the ERR_CODE parameter: ERR_CODE* Explanation W#16#0000 No error W#16#000B The value at the LST_STEP parameter is less than 1 or greater than 16. W#16#000C The value at the DSC parameter is less than 1 or greater than the value of the LST_STEP parameter. W#16#000D The value at the DSP parameter is less than 1 or greater than the value of the LST_STEP parameter. *The error codes can be displayed as integer or hexadecimal value in the program editor. For information on toggling display formats, refer to "See also". See also Overview of the valid data types (Page 1204) Basics of the EN/ENO mechanism (Page 1299) DCAT: Discrete control-timer alarm Description The instruction "Discrete control-timer alarm" is used to accumulate the time from the point at which the CMD parameter issued the command to open or close. The time is accumulated until the preset time (PT) is exceeded or the information is received that the device was opened or closed (O_FB or C_FB) within the specified time. If the preset time is exceeded before the information on the opening or closing of the device is received, the corresponding alarm is activated. If the signal state of the command input changes state before the preset time, the time is restarted. When you insert the instruction in the program, the "Call options" dialog opens in which you can specify whether the block parameters will be stored in a separate data block (single instance) or as a local tag (multi-instance) in the block interface. If you create a separate data block, you will find it in the project tree in the "Program resources" folder under "Program blocks > System blocks". For additional information on this topic, refer to "See also". The "Discrete control-timer alarm" instruction has the following reactions to the input conditions: When the signal state of the CMD parameter changes from "0" to "1", the signal states of the parameters Q, CMD_HIS, ET (only if ET < PT), OA and CA are influenced as follows: - The parameters Q and CMD_HIS are set to "1". - The parameters ET, OA and CA are reset to "0". When the signal state of the parameter CMD changes from "1" to "0", the parameters Q, ET (only if ET < PT), OA, CA and CMD_HIS are reset to "0". WinCC Basic V13.0 System Manual, 02/2014 1997 Programming the PLC 9.7 References When the signal state of the parameters CMD and CMD_HIS is "1" and the parameter O_FB is set to "0", the time difference (ms) since the last execution of the instruction is added to the value at the parameter ET. If the value of the parameter ET exceeds the value of the parameter PT, the signal state on the parameter OA is set to "1". If the value of the ET parameter does not exceed the value of the parameter PT, the signal state on the parameter OA is reset to "0". The value at the parameter CMD_HIS is reset to the value of the parameter CMD. If the signal state of the CMD, CMD_HIS and O_FB parameters are set to "1" and the parameter C_FB has the value "0", the signal state of the parameter OA is set to "0". The value of the parameter ET is set to the value of the parameter PT. If the signal state of the O_FB parameter changes to "0", the alarm is set the next time the instruction is executed. The value of the parameter CMD_HIS is set to the value of the parameter CMD. If the parameters CMD, CMD_HIS and C_FB have the value "0", the time difference (ms) since the last execution of the instruction is added to the value of the parameter ET. If the value of the ET parameter exceeds the value of the parameter PT, the signal state of the parameter CA is reset to "1". If the value at the parameter PT is not exceeded, the parameter CA has the signal state "0". The value of the parameter CMD_HIS is set to the value of the parameter CMD. If the parameters CMD, CMD_HIS and O_FB have the signal state "0" and the parameter C_FB is set to "1", the parameter CA is set to "0". The value of the parameter ET is set to the value of the parameter PT. If the signal state of the C_FB parameter changes to "0", the alarm is set the next time the instruction is executed. The value of the parameter CMD_HIS is set to the value of the parameter CMD. If the parameters O_FB and C_FB simultaneously have the signal state "1", the signal states of both alarm outputs are set to "1". The "Discrete control-timer alarm" instruction returns no error information. Parameters The following table shows the parameters of the "Discrete control-timer alarm" instruction: Parameter Declaration Data type Memory area Description EN Input BOOL I, Q, M, D, L Enable input ENO Output BOOL I, Q, M, D, L Enable output CMD Input BOOL I, Q, M, D, L or constant The signal state "0" indicates a "close" command. The signal state "1" indicates the "open" command. 1998 O_FB Input BOOL I, Q, M, D, L or constant Feedback input when opening C_FB Input BOOL I, Q, M, D, L or constant Feedback input when closing Q Output BOOL I, Q, M, D, L Shows the status of the parameter CMD OA Output BOOL I, Q, M, D, L Alarm output when opening WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameter Declaration Data type Memory area Description CA Output BOOL I, Q, M, D, L Alarm output when closing ET Static DINT D, L or constant Currently elapsed time, where one clock pulse = 1 ms PT Static DINT D, L or constant Preset timer value, where one clock pulse = 1 ms PREV_TIME Static DWORD D, L or constant Previous system time CMD_HIS Static BOOL D, L or constant CMD history bit For additional information on valid data types, refer to "See also". Example In the following example the parameter CMD changes from "0" to "1". After the execution of the instruction the parameter Q is set to "1" and the two alarm outputs OA and CA have the signal state "0". The parameter CMD_HIS of the instance data block is set to the signal state "1" and the parameter ET is reset to "0". Note You can initialize static parameters in the data block. '&$7B'% '&$7 7DJ,Q (1 7DJ2XW (12 7DJB,QSXWB&0' &0' 4 7DJB2XWSXWB4 7DJB,QSXWB2B)% 2B)% 2$ 7DJB2XWSXWB2$ &B)% &$ 7DJB2XWSXWB&$ 7DJB,QSXWB&B)% The following tables show how the instruction works using specific values. Before processing In this example, the following values are used for the input and output parameters: WinCC Basic V13.0 System Manual, 02/2014 Parameter Operand Value CMD Tag_Input_CMD TRUE O_FB Tag_Input_O_FB FALSE C_FB Tag_Input_C_FB FALSE Q Tag_Output_Q FALSE OA Tag_Output_OA FALSE CA Tag_Output_CA FALSE 1999 Programming the PLC 9.7 References The following values are saved in the instance data block "DCAT_DB" of the instruction: Parameter Address Value ET DBD4 L#12 PT DBD8 L#222 CMD_HIS DBX16.0 FALSE After processing The following values are written to the output parameters after the instruction has been executed: Parameter Operand Value Q Tag_Output_Q TRUE OA Tag_Output_OA FALSE CA Tag_Output_CA FALSE The following values are saved in the instance data block "DCAT_DB" of the instruction: Parameter Address Value ET DBD4 L#0 CMD_HIS DBX16.0 TRUE See also Overview of the valid data types (Page 1204) Basics of the EN/ENO mechanism (Page 1299) MCAT: Motor control-timer alarm Description The instruction "Motor control-timer alarm" is used to accumulate the time from the point in time as of which one of the command inputs (open or close) is activated. The time is accumulated until the preset time is exceeded or the relevant feedback input indicates that the device has executed the requested operation within the specified time. If the preset time is exceeded before the feedback is received, the corresponding alarm is triggered. When you insert the instruction in the program, the "Call options" dialog opens in which you can specify whether the block parameters will be stored in a separate data block (single instance) or as a local tag (multi-instance) in the block interface. If you create a separate data block, you will find it in the project tree in the "Program resources" folder under "Program blocks > System blocks". For additional information on this topic, refer to "See also". 2000 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Execution of the "Motor control-timer alarm" instruction The following table shows the reactions of the "Motor control-timer alarm" instruction to the various input conditions: Input parameters Output parameters ET O_H IS C_H IS O_C MD C_C MD S_C MD O_F B C_F B OO CO OA CA ET O_H IS C_H IS Q Status X 1 1 X X X X X 0 0 1 1 PT 0 0 0 Alarm X X X X X X 1 1 0 0 1 1 PT 0 0 0 Alarm X X X X X 1 X X 0 0 0 0 X 0 0 1 Stop X X X 1 1 X X X 0 0 0 0 X 0 0 1 Stop X 0 X 1 0 0 X X 1 0 0 0 0 1 0 1 Start opening <PT 1 0 X 0 0 0 X 1 0 0 0 INC 1 0 1 Open X 1 0 X 0 0 1 0 0 0 0 0 PT 1 0 1 Opened >=P T 1 0 X 0 0 0 X 0 0 1 0 PT 1 0 0 Opening alarm X X 0 0 1 0 X X 0 1 0 0 0 0 1 1 Start closing <PT 0 1 0 X 0 X 0 0 1 0 0 INC 0 1 1 Close X 0 1 0 X 0 0 1 0 0 0 0 PT 0 1 1 Closed >=P T 0 1 0 X 0 X 0 0 0 0 1 PT 0 1 0 Closing alarm X 0 0 0 0 0 X X 0 0 0 0 X 0 0 1 Stopped Legend: INC Add the time difference (ms) since the last processing of the FB to ET PT PT is set to the same value as ET X Cannot be used <PT ET < PT >=PT ET >= PT If the input parameters O_HIS and C_HIS both have the signal state "1", they are immediately set to signal state "0". In this case, the last row in the table (X) mentioned above is valid. Because it is therefore no longer possible to check whether the input parameters O_HIS and C_HIS have the signal state "1", the output parameters are set as follows in this case: OO = FALSE CO = FALSE OA = FALSE CA = FALSE ET = PT Q = TRUE The "Motor control-timer alarm" instruction returns no error information. WinCC Basic V13.0 System Manual, 02/2014 2001 Programming the PLC 9.7 References Parameters The following table shows the reactions of the "Motor control-timer alarm" instruction: Parameter Declaration Data type Memory area Description EN Input BOOL I, Q, M, D, L Enable input ENO Output BOOL I, Q, M, D, L Enable output O_CMD Input BOOL I, Q, M, D, L or constant "Open" command input C_CMD Input BOOL I, Q, M, D, L or constant "Close" command input S_CMD Input BOOL I, Q, M, D, L or constant "Stop" command input O_FB Input BOOL I, Q, M, D, L or constant Feedback input when opening C_FB Input BOOL I, Q, M, D, L or constant Feedback input when closing OO Output BOOL I, Q, M, D, L "Open" output CO Output BOOL I, Q, M, D, L "Close" output OA Output BOOL I, Q, M, D, L Alarm output when opening CA Output BOOL I, Q, M, D, L Alarm output when closing Q Output BOOL I, Q, M, D, L The signal state "0" indicates an error condition. ET Static DINT D, L or constant Currently elapsed time, where one clock pulse = 1 ms PT Static DINT D, L or constant Preset timer value, where one clock pulse = 1 ms PREV_TIME Static DWORD D, L or constant Previous system time O_HIS Static BOOL D, L or constant "Open" history bit C_HIS Static BOOL D, L or constant "Close" history bit For additional information on valid data types, refer to "See also". Example The following example shows how the instruction works: Note You can initialize static parameters in the data block. 2002 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References 0&$7B'% 7DJ,Q 0&$7 (1 7DJ2XW (12 7DJB,QSXWB2B&0' 2B&0' 22 7DJB2XWSXW2SHQ &B&0' &2 7DJB2XWSXW&ORVHG 6B&0' 2$ 7DJB2XWSXWB2$ 2B)% &$ 7DJB2XWSXWB&$ &B)% 4 7DJB2XWSXWB4 7DJB,QSXWB&B&0' 7DJB,QSXWB6B&0' 7DJB,QSXWB2B)% 7DJB,QSXWB&B)% The following tables show how the instruction works using specific values. Before processing In this example, the following values are used for the input and output parameters: Parameter Operand Value O_CMD Tag_Input_O_CMD TRUE C_CMD Tag_Input_C_CMD FALSE S_CMD Tag_Input_S_CMD FALSE O_FB Tag_Input_O_FB FALSE C_FB Tag_Input_C_FB FALSE OO Tag_OutputOpen FALSE CO Tag_OutputClosed FALSE OA Tag_Output_OA FALSE CA Tag_Output_CA FALSE Q Tag_Output_Q FALSE The following values are saved in the instance data block "MCAT_DB" of the instruction: Parameter Address Value ET DBD4 L#2 PT DBD8 L#22 O_HIS DBX16.0 TRUE C_HIS DBX16.1 FALSE After processing The following values are written to the output parameters after the instruction has been executed: WinCC Basic V13.0 System Manual, 02/2014 2003 Programming the PLC 9.7 References Parameter Operand Value OO Tag_OutputOpen TRUE CO Tag_OutputClosed FALSE OA Tag_Output_OA FALSE CA Tag_Output_CA FALSE Q Tag_Output_Q TRUE The following values are saved in the instance data block "MCAT_DB" of the instruction: Parameter Address Value ET DBD4 L#0 O_HIS DBX16.0 TRUE CMD_HIS DBX16.1 FALSE See also Overview of the valid data types (Page 1204) Basics of the EN/ENO mechanism (Page 1299) IMC: Compare input bits with the bits of a mask Description The instruction "Compare input bits with the bits of a mask" is used to compare the signal state of up to 16 programmed input bits (IN_BIT0 to IN_BIT15) with the corresponding bits of a mask. Up to 16 steps with masks can be programmed. The value of the IN_BIT0 parameter is compared with the value of the mask CMP_VAL[x,0], with "x" indicating the step number. On the CMP_STEP parameter, you specify the step number of the mask that is used for the comparison. All programmed values are compared in the same manner. Unprogrammed input bits or unprogrammed bits of the mask have the default signal state FALSE. If a match is found in the comparison, the signal state of the OUT parameter is set to "1". Otherwise, the OUT parameter is set to "0". If the value of the CMP_STEP parameter is greater than 15, the instruction is not executed. An error message is output at the ERR_CODE parameter. When you insert the instruction in the program, the "Call options" dialog opens in which you can specify whether the block parameters will be stored in a separate data block (single instance) or as a local tag (multi-instance) in the block interface. If you create a separate data block, you will find it in the project tree in the "Program resources" folder under "Program blocks > System blocks". For additional information on this topic, refer to "See also". 2004 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameters The following table shows the parameters of the "Compare input bits with the bits of a mask" instruction: Paramete Declarati Data type r on Memory area Description EN Input BOOL I, Q, M, D, L Enable input ENO Output BOOL I, Q, M, D, L Enable output IN_BIT0 Input BOOL I, Q, M, D, L or constant Input bit 0 is compared with bit 0 of the mask. IN_BIT1 Input BOOL I, Q, M, D, L or constant Input bit 1 is compared with bit 1 of the mask. IN_BIT2 Input BOOL I, Q, M, D, L or constant Input bit 2 is compared with bit 2 of the mask. IN_BIT3 Input BOOL I, Q, M, D, L or constant Input bit 3 is compared with bit 3 of the mask. IN_BIT4 Input BOOL I, Q, M, D, L or constant Input bit 4 is compared with bit 4 of the mask. IN_BIT5 Input BOOL I, Q, M, D, L or constant Input bit 5 is compared with bit 5 of the mask. IN_BIT6 Input BOOL I, Q, M, D, L or constant Input bit 6 is compared with bit 6 of the mask. IN_BIT7 Input BOOL I, Q, M, D, L or constant Input bit 7 is compared with bit 7 of the mask. IN_BIT8 Input BOOL I, Q, M, D, L or constant Input bit 8 is compared with bit 8 of the mask. IN_BIT9 Input BOOL I, Q, M, D, L or constant Input bit 9 is compared with bit 9 of the mask. IN_BIT10 Input BOOL I, Q, M, D, L or constant Input bit 10 is compared with bit 10 of the mask. IN_BIT11 Input BOOL I, Q, M, D, L or constant Input bit 11 is compared with bit 11 of the mask. IN_BIT12 Input BOOL I, Q, M, D, L or constant Input bit 12 is compared with bit 12 of the mask. IN_BIT13 Input BOOL I, Q, M, D, L or constant Input bit 13 is compared with bit 13 of the mask. IN_BIT14 Input BOOL I, Q, M, D, L or constant Input bit 14 is compared with bit 14 of the mask. IN_BIT15 Input BOOL I, Q, M, D, L or constant Input bit 15 is compared with bit 15 of the mask. CMP_ST EP Input BYTE I, Q, M, D, L, P or constant The step number of the mask used for the comparison. OUT Output BOOL I, Q, M, D, L The signal state "1" indicates that a match was found. The signal state "0" indicates that a match was found. WinCC Basic V13.0 System Manual, 02/2014 2005 Programming the PLC 9.7 References Paramete Declarati Data type r on Memory area Description ERR_CO DE Output WORD I, Q, M, D, L, P Error information CMP_VA L Static ARRAY OF WORD I, Q, M, D, L or constant Comparison masks [0 to 15, 0 to 15]: The first number of the index is the step number and the second number is the bit number of the mask. For additional information on valid data types, refer to "See also". Parameters ERR_CODE The following table shows the meaning of the values of the ERR_CODE parameter: Error code* (W#16#...) Explanation 0000 No error 000A The value at the CMP_STEP parameter is greater than 15. *The error codes can be displayed as integer or hexadecimal value in the program editor. For information on toggling display formats, refer to "See also". See also Overview of the valid data types (Page 1204) Basics of the EN/ENO mechanism (Page 1299) SMC: Compare scan matrix Description The "Compare scan matrix" instruction is used to compare the signal state of up to 16 programmed input bits (IN_BIT0 to IN_BIT15) with the corresponding bits of the comparison masks for each step. Processing starts at step 1 and is continued until the last programmed step (LAST) or until a match is found. The input bit of the IN_BIT0 parameter is compared with the value of the mask CMP_VAL[x,0], with "x" indicating the step number. All programmed values are compared in the same manner. If a match is found the signal state of the OUT parameter is set to "1" and the step number with the matching mask is written in the OUT_STEP parameter. Unprogrammed input bits or unprogrammed bits of the mask have the default signal state FALSE. If more than one step has a matching mask, only the first one found is indicated in the OUT_STEP parameter. If no match is found, the signal state of the OUT parameter is set to "0". In this case the value at the OUT_STEP parameter is greater by "1" than the value of the LAST parameter. When you insert the instruction in the program, the "Call options" dialog opens in which you can specify whether the block parameters will be stored in a separate data block (single instance) or as a local tag (multi-instance) in the block interface. If you create a separate data 2006 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References block, you will find it in the project tree in the "Program resources" folder under "Program blocks > System blocks". For additional information on this topic, refer to "See also". Parameters The following table shows the parameters of the "Compare scan matrix" instruction: Paramete Declarati Data type r on Memory area Description EN Input BOOL I, Q, M, D, L Enable input ENO Output BOOL I, Q, M, D, L Enable output IN_BIT0 Input BOOL I, Q, M, D, L or constant Input bit 0 is compared with bit 0 of the mask. IN_BIT1 Input BOOL I, Q, M, D, L or constant Input bit 1 is compared with bit 1 of the mask. IN_BIT2 Input BOOL I, Q, M, D, L or constant Input bit 2 is compared with bit 2 of the mask. IN_BIT3 Input BOOL I, Q, M, D, L or constant Input bit 3 is compared with bit 3 of the mask. IN_BIT4 Input BOOL I, Q, M, D, L or constant Input bit 4 is compared with bit 4 of the mask. IN_BIT5 Input BOOL I, Q, M, D, L or constant Input bit 5 is compared with bit 5 of the mask. IN_BIT6 Input BOOL I, Q, M, D, L or constant Input bit 6 is compared with bit 6 of the mask. IN_BIT7 Input BOOL I, Q, M, D, L or constant Input bit 7 is compared with bit 7 of the mask. IN_BIT8 Input BOOL I, Q, M, D, L or constant Input bit 8 is compared with bit 8 of the mask. IN_BIT9 Input BOOL I, Q, M, D, L or constant Input bit 9 is compared with bit 9 of the mask. IN_BIT10 Input BOOL I, Q, M, D, L or constant Input bit 10 is compared with bit 10 of the mask. IN_BIT11 Input BOOL I, Q, M, D, L or constant Input bit 11 is compared with bit 11 of the mask. IN_BIT12 Input BOOL I, Q, M, D, L or constant Input bit 12 is compared with bit 12 of the mask. IN_BIT13 Input BOOL I, Q, M, D, L or constant Input bit 13 is compared with bit 13 of the mask. IN_BIT14 Input BOOL I, Q, M, D, L or constant Input bit 14 is compared with bit 14 of the mask. IN_BIT15 Input BOOL I, Q, M, D, L or constant Input bit 15 is compared with bit 15 of the mask. OUT BOOL I, Q, M, D, L The signal state "1" indicates that a match was found. Output The signal state "0" indicates that no match was found. ERR_CO DE WinCC Basic V13.0 System Manual, 02/2014 Output WORD I, Q, M, D, L, P Error information 2007 Programming the PLC 9.7 References Paramete Declarati Data type r on Memory area Description OUT_ST EP Output BYTE I, Q, M, D, L, P Contains the step number with the matching mask or the step number which is greater by "1" than the value of the LAST parameter, provided no match is found. LAST Static BYTE I, Q, M, D, L, P or constant Specifies the step number of the last step to be scanned for a matching mask. CMP_VA L Static ARRAY OF WORD I, Q, M, D, L or constant Comparison masks [0 to 15, 0 to 15]: The first number of the index is the step number and the second number is the bit number of the mask. For additional information on valid data types, refer to "See also". Parameters ERR_CODE The following table shows the meaning of the values of the ERR_CODE parameter: Error code* (W#16#...) Explanation 0000 No error 000E The value at the LAST parameter is greater than 15. *The error codes can be displayed as integer or hexadecimal value in the program editor. For information on toggling display formats, refer to "See also". See also Overview of the valid data types (Page 1204) Basics of the EN/ENO mechanism (Page 1299) LEAD_LAG: Lead and lag algorithm Description The "Lead and lag algorithm" instruction is used to process signals with an analog tag. The gain value at the GAIN parameter must be greater than zero. The result of the instruction "Lead and lag algorithm" is calculated using the following equation: 287 /*B7,0( /'B7,0(6$03/(B7 /'B7,0( ,1*$,1 35(9B287*$,1 /*B7,0(6$03/(B7 /*B7,0(6$03/(B7 /*B7,0(6$03/(B7 35(9B,1 The "Lead and lag algorithm" instruction supplies plausible results only when processing is in fixed program cycles. The same units must be specified for the LD_TIME, LG_TIME, and 2008 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References SAMPLE_T parameters. At LG_TIME > 4 + SAMPLE_T, the instruction approaches the following function: OUT = GAIN * ((1 + LD_TIME * s) / (1 + LG_TIME * s)) * IN When the value of the GAIN parameter is less than or equal to zero, the calculation is not performed and an error information is output on the ERR_CODE parameter. You can use the "Lead and lag algorithm" instruction in conjunction with loops as a compensator in dynamic feed-forward control. The instruction consists of two operations. The "Lead" operation shifts the phase of the OUT output so that the output leads the input. The "Lag" operation, on the other hand, shifts the output so that the output lags behind the input. Because the "Lag" operation is equivalent to an integration, it can be used as a noise suppressor or as a low-pass filter. The "Lead" operation is equivalent to a differentiation and can therefore be used as a high-pass filter. The two operations together (Lead and Lag) result in the output phase lagging behind the the input at lower frequencies and leading it at higher frequencies. This means that the "Lead and lag algorithm" instruction can be used as a band pass filter. When you insert the instruction in the program, the "Call options" dialog opens in which you can specify whether the block parameters will be stored in a separate data block (single instance) or as a local tag (multiple instance) in the block interface. If you create a separate data block, you will find it in the project tree in the "Program resources" folder under "Program blocks > System blocks". For additional information on this topic, refer to "See also". Parameters The following table shows the parameters of the "Lead and lag algorithm" instruction: Parameter Declaration Data type Memory area Description EN Input BOOL I, Q, M, D, L Enable input ENO Output BOOL I, Q, M, D, L Enable output IN Input REAL I, Q, M, D, L, P or constant The input value of the current sample time (cycle time) to be processed. Constants can also be specified on the IN parameter. SAMPLE_T WinCC Basic V13.0 System Manual, 02/2014 Input INT I, Q, M, D, L, P or constant Sample time Constants can also be specified on the SAMPLE_T parameter. OUT Output REAL I, Q, M, D, L Result of the instruction ERR_CODE Output WORD I, Q, M, D, L Error information LD_TIME Static REAL I, Q, M, D, L, P or constant Lead time in the same unit as sample time. 2009 Programming the PLC 9.7 References Parameter Declaration Data type Memory area Description LG_TIME Static REAL I, Q, M, D, L, P or constant Lag time in in the same unit as sample time. GAIN Static REAL I, Q, M, D, L, P or constant Gain as % / % (the ratio of the change in output to a change in input as a steady state). PREV_IN Static REAL I, Q, M, D, L, P or constant Previous input PREV_OUT Static REAL I, Q, M, D, L, P or constant Previous output For additional information on valid data types, refer to "See also". Parameter ERR_CODE The following table shows the meaning of the values of the ERR_CODE parameter: Error code* (W#16#...) Explanation 0000 No error 0009 The value at the GAIN parameter is less than or equal to zero. *The error codes can be displayed as integer or hexadecimal value in the program editor. For additional information on toggling display formats, refer to "See also". Example The following example shows how the instruction works: Note You can initialize static parameters in the data block. /($'B/$*B'% /($'B/$* 7DJ,Q 7DJB,QSXW 7DJB,QSXWB6$03/(B7 7DJ2XW (1 (12 ,1 287 6$03/(B7 (55B&2'( 7DJB2XWSXWB5HVXOW 7DJB(UURU&RGH The following table shows how the instruction works using specific operand values: Before processing In this example the following values are used for the input parameters: 2010 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameter Operand Value IN Tag_Input 2.0 SAMPLE_T Tag_InputSampleTime 10 The following values are saved in the instance data block "LEAD_LAG_DB" of the instruction: Parameter Address Value LD_TIME DBD12 2.0 LG_TIME DBD16 2.0 GAIN DBD20 1.0 PREV_IN DBD24 6.0 PREV_OUT DBD28 6.0 After processing The following values are written to the output parameters after the instruction has been executed: Parameter Operand Value OUT Tag_Output_Result 2.0 The following values are saved in the instance data block "LEAD_LAD_DB" of the instruction: Parameter Operand Value PREV_IN DBD24 2.0 PREV_OUT DBD28 2.0 See also Overview of the valid data types (Page 1204) Basics of the EN/ENO mechanism (Page 1299) SEG: Create bit pattern for seven-segment display Description The instruction "Create bit pattern for seven-segment display" is used to convert each of the four hexadecimal digits of the specified source word (IN) into an equivalent bit pattern for a seven-segment display. The result of the instruction is output in the double word on the OUT parameter. The following relation exists between the hexadecimal digits and the assignment of the 7 segments (a, b, c, d, e, f, g): WinCC Basic V13.0 System Manual, 02/2014 2011 Programming the PLC 9.7 References Input digit (Binary) 0000 0001 0010 0011 0100 0101 0110 0111 1000 1001 1010 1011 1100 1101 1110 1111 Assignment of the segments gfedcba 00111111 00000110 01011011 01001111 01100110 01101101 01111101 00000111 01111111 01100111 01110111 01111100 00111001 01011110 01111001 01110001 Display Seven-segment display (Hexadecimal) 0 1 2 3 4 5 6 7 8 9 A B C D E F D E I J H F G Parameter The following table shows the parameters of the "Create bit pattern for seven-segment display" instruction: 2012 Parameter Declaration Data type Memory area Description EN Input BOOL I, Q, M, D, L Enable input ENO Output BOOL I, Q, M, D, L Enable output IN Input WORD I, Q, M, D, L, P or constant Source word with four hexadecimal digits OUT Output DWORD I, Q, M, D, L, P Bit pattern for the seven-segment display WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Example The following example shows how the instruction works: 6(* 7DJ,Q 7DJ2XW 7DJB,QSXW (1 (12 ,1 287 7DJB2XWSXW The following table shows how the instruction works using specific operand values: Parameter Operand Value Hexadecimal Binary IN Tag_Input W#16#1234 0001 0010 0011 0100 OUT Tag_Output DW#16065B4F66 000 00110 0101 1011 0100 1111 0110 0110 Display: 1234 See also Overview of the valid data types (Page 1204) Basics of the EN/ENO mechanism (Page 1299) BCDCPL: Create tens complement Description You can use the "Create tens complement" instruction to create the tens complement of a seven-digit BCD number specified in the IN parameter. This instruction uses the following mathematical formula to calculate: 10000000 (as BCD) - 7-digit BCD value ---------------------------------------Tens complement (as BCD) Parameters The following table shows the parameters of the "Create tens complement" instruction: WinCC Basic V13.0 System Manual, 02/2014 Parameter Declaration Data type Memory area Description EN Input BOOL I, Q, M, D, L Enable input ENO Output BOOL I, Q, M, D, L Enable output 2013 Programming the PLC 9.7 References Parameter Declaration Data type Memory area Description IN Input Bit strings I, Q, M, D, L, P or constant 7-digit BCD number ERR_CODE Output DWORD I, Q, M, D, L, P Result of the instruction Example The following example shows how the instruction works: %&'&3/ 7DJ,Q 7DJ2XW (1 7DJB,QSXW ,1 (12 (55B&2'( 7DJB2XWSXW The following table shows how the instruction functions using specific values: Parameter Operand Value* IN Tag_Input DW#16#01234567 ERR_CODE Tag_Output DW#16#08765433 *The error codes can be displayed as integer or hexadecimal value in the program editor. For information on toggling display formats, refer to "See also". See also Overview of the valid data types (Page 1204) Basics of the EN/ENO mechanism (Page 1299) BITSUM: Count number of set bits Description The "Count number of set bits" instruction is used to count the number of bits of an operand that is set to the signal state "1". The operand whose bits are to be counted is specified on the IN parameter. The result of the instruction is output on the RET_VAL parameter. Parameters The following table shows the parameters of the "Count number of set bits" instruction: 2014 Parameter Declaration Data type Memory area Description EN Input BOOL I, Q, M, D, L Enable input ENO Output BOOL I, Q, M, D, L Enable output WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameter Declaration Data type Memory area Description IN Input DWORD I, Q, M, D, L, P or constant Operand whose set bits are counted RET_VAL Output INT I, Q, M, D, L, P Number of bits to be set Example The following example shows how the instruction works: %,7680 7DJ,Q 7DJ2XW (1 7DJB,QSXW ,1 (12 5(7B9$/ 7DJB2XWSXW The following table shows how the instruction functions using specific values: Parameter Operand Value* IN Tag_Input DW#16#12345678 RET_VAL Tag_Output W#16#000D (13 Bits) *The error codes can be displayed as integer or hexadecimal value in the program editor. For additional information on toggling display formats, refer to "See also". See also Overview of the valid data types (Page 1204) Basics of the EN/ENO mechanism (Page 1299) 9.7.2.2 FBD Bit logic operations &: AND logic operation Description You can use the instruction "AND logic operation" to query the signal states of two or more specified operands and evaluate them according to the AND truth table. If the signal state of all the operands is "1", then the condition is fulfilled and the instruction returns the result "1". If the signal state of one of the operands is "0", then the condition is not fulfilled and the instruction generates the result "0". WinCC Basic V13.0 System Manual, 02/2014 2015 Programming the PLC 9.7 References Parameters The following table shows the parameters of the instruction "AND logic operation": Parameter <Operand> Declaration Data type Input BOOL Memory area Description S7-1200 S7-1500 I, Q, M, D, L I, Q, M, D, L, T, C The operand indicates the bit whose signal state will be queried. Example The following example shows how the instruction works: 7DJ,QB 7DJ2XW 7DJ,QB Output "TagOut" is set, when the signal state of the operands "TagIn_1" and "TagIn_2" is "1" and reset when the state of the operands "TagIn_1" and "TagIn_2" is "0". See also AND truth table (Page 2016) Example of detecting the direction of a conveyor belt (Page 1725) Example of controlling room temperature (Page 1729) Overview of the valid data types (Page 1204) Adding additional inputs and outputs to FBD elements (Page 1469) Insert input (Page 2020) AND truth table Results of the logic operation The following table shows the results that arise from the AND logic operation of two operands: 2016 Signal state of the first operand Signal state of the second operand Result of the logic operation 1 1 1 0 1 0 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Signal state of the first operand Signal state of the second operand Result of the logic operation 1 0 0 0 0 0 See also &: AND logic operation (Page 2015) Overview of the valid data types (Page 1204) >=1: OR logic operation Description You can use the instruction "OR logic operation" to query the signal states of two or more specified operands and evaluate them according to the OR truth table. If the signal state of one of the operands is "1", then the condition is fulfilled and the instruction returns the result "1". If the signal state of all the operands is "0", then the condition is not fulfilled and the instruction generates the result "0". Parameters The following table shows the parameters of the instruction "OR logic operation": Parameter <Operand> Declaration Input Data type BOOL Memory area S7-1200 S7-1500 I, Q, M, D, L I, Q, M, D, L, T, C Description The operand indicates the bit whose signal state will be queried. Example The following example shows how the instruction works: 7DJ,QB 7DJ,QB ! 7DJ2XW Output "TagOut" is set, when the signal state of the operands "TagIn_1" or "TagIn_2" is "1". WinCC Basic V13.0 System Manual, 02/2014 2017 Programming the PLC 9.7 References See also OR truth table (Page 2018) Example of controlling a conveyor belt (Page 1724) Adding additional inputs and outputs to FBD elements (Page 1469) Overview of the valid data types (Page 1204) Insert input (Page 2020) OR truth table Results of the logic operation The following table shows the results that arise from the OR logic operation of two operands: Signal state of the first operand Signal state of the second operand Result of the logic operation 1 0 1 0 1 1 1 1 1 0 0 0 See also >=1: OR logic operation (Page 2017) Overview of the valid data types (Page 1204) X: EXCLUSIVE OR logic operation Description You can use the instruction "EXCLUSIVE OR logic operation" to query the result of a signal state query according to the EXCLUSIVE OR truth table. With an instruction "EXCLUSIVE OR logic operation", the signal state is "1" when the signal state of one of the two specified operands is "1". When more than two operands are queried, the common RLO is "1" if an odd number of the queried operands returns the result "1". 2018 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameters The following table shows the parameters of the instruction "EXCLUSIVE OR logic operation": Parameter <Operand> Declaration Data type Input BOOL Memory area S7-1200 S7-1500 I, Q, M, D, L I, Q, M, D, L, T, C Description The operand indicates the bit whose signal state will be queried. Example The following example shows how the instruction works: 7DJ,QB ; 7DJ2XW 7DJ,QB Output "TagOut" is set when the signal state of the operands "TagIn_1" and "TagIn_2" is "1". When both operands return the signal state "1" or "0", the output "TagOut" is reset. See also EXCLUSIVE OR truth table (Page 2019) Adding additional inputs and outputs to FBD elements (Page 1469) Overview of the valid data types (Page 1204) Insert input (Page 2020) EXCLUSIVE OR truth table Results of the logic operation The following table shows the results that arise from the EXCLUSIVE OR logic operation of two operands: WinCC Basic V13.0 System Manual, 02/2014 Signal state of the first operand Signal state of the second operand Result of the logic operation 1 0 1 0 1 1 1 1 0 0 0 0 2019 Programming the PLC 9.7 References The following table shows the results that arise from the EXCLUSIVE OR logic operation of three operands: Signal state of the first operand Signal state of the second operand Signal state of the third operand Result of the logic operation 1 0 0 1 0 1 1 0 0 1 0 1 1 0 1 0 0 0 1 1 1 1 0 0 1 1 1 1 0 0 0 0 See also X: EXCLUSIVE OR logic operation (Page 2018) Overview of the valid data types (Page 1204) Insert input Description The "Insert input" instruction is used to add an input to the box of one of the following instructions: "AND logic operation" "OR logic operation" "EXCLUSIVE OR logic operation" You can query the signal state of several operands by the extension of an instruction box. Parameters The following table shows the parameters of the instruction "Insert input": Parameter <Operand> 2020 Declaration Input Data type BOOL Memory area Description S7-1200 S7-1500 I, Q, M, D, L I, Q, M, D, L, T, C The operand indicates the bit whose signal state will be queried. WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Example The following example shows how the instruction works: 7DJ,QB 7DJ2XW 7DJ,QB 7DJ,QB The box of the instruction "AND logic operation" was extended by an additional input at which the signal state of the operand "TagIn_3" is queried. The output "TagOut" is set, when the signal state of the operands "TagIn_1", "TagIn_2" and "TagIn_3" returns the signal state "1". See also &: AND logic operation (Page 2015) >=1: OR logic operation (Page 2017) X: EXCLUSIVE OR logic operation (Page 2018) Overview of the valid data types (Page 1204) Invert RLO Description You use the "Invert RLO" instruction to invert the signal state of the result of logic operation (RLO). Example The following example shows how the instruction works: 7DJ,QB 7DJ,QB 7DJ,QB 7DJ,QB 7DJ,QB ! 7DJ2XW The output "TagOut" is set when the following conditions are fulfilled: The input "TagIn_1" and/or "TagIn_2" has signal state "0". The input "TagIn_3" and/or "TagIn_4" has signal state "0" or the input "TagIn_5" has signal state "1". See also Overview of the valid data types (Page 1204) WinCC Basic V13.0 System Manual, 02/2014 2021 Programming the PLC 9.7 References =: Assignment Description You can use the instruction "Assignment" to set the bit of a specified operand. If the result of logic operation (RLO) at the box input has the signal state "1", the specified operand is set to signal state "1". If the signal state at the box input is "0", the bit of the specified operand is reset to "0". The instruction does not influence the RLO. The RLO at the box input is assigned directly to the operand above the assignment box. Parameters The following table shows the parameters of the instruction "Assignment": Parameters Declaration Data type Memory area Description <Operand> Output BOOL I, Q, M, D, L Operand to which the RLO is assigned. Example The following example shows how the instruction works: 7DJ,QB 7DJ,QB ! 7DJ,QB 7DJ2XW The operand "TagOut" is set at the output of the "Assignment" instruction when one of the following conditions is fulfilled: The inputs "TagIn_1" and "TagIn_2" have the signal state "1". The signal state at the input "TagIn_3" is "0". See also Overview of the valid data types (Page 1204) Example of detecting the fill level of a storage area (Page 1726) Example of controlling room temperature (Page 1729) 2022 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References /=: Negate assignment Description The instruction "Negate assignment" inverts the result of logic operation (RLO) and assigns this to the operand above the box. If the RLO at the input of the box is "1", the binary operand is reset. If the RLO at the input of the box is "0", the operand is set to signal state "1". Parameters The following table shows the parameters of the instruction "Negate assignment": Parameters Declaration Data type Memory area Description <Operand> Output BOOL I, Q, M, D, L Operand to which the negated RLO is assigned. Example The following example shows how the instruction works: 7DJ,QB ! 7DJ,QB 7DJ2XW 7DJ,QB The operand "TagOut" is reset when the following conditions are fulfilled: The operand "TagIn_1" or "TagIn_2" has the signal state "1". The operand "TagIn_3" has the signal state "0". See also Overview of the valid data types (Page 1204) R: Reset output Description You can use the "Reset output" instruction to reset the signal state of a specified operand to "0". The instruction is only executed if the result of logic operation (RLO) at the box input is "1". If the box input has the signal state "1", the specified operand is reset to "0". If there is an RLO of "0" at the box input, the signal state of the specified operand remains unchanged. WinCC Basic V13.0 System Manual, 02/2014 2023 Programming the PLC 9.7 References Parameters The following table shows the parameters of the "Reset output" instruction: Parameters Declaration <Operand> Output Data type BOOL Memory area Description S7-1200 S7-1500 I, Q, M, D, L I, Q, M, D, L, T, C Operand that is reset if RLO = "1". Example The following example shows how the instruction works: 7DJ,QB 7DJ,QB ! 7DJ2XW 7DJ,QB 5 Operand "TagOut" is reset when one of the following conditions is fulfilled: The operands "TagIn_1" and "TagIn_2" have signal state "1". The operand "TagIn_3" has the signal state "0". See also Example of controlling a conveyor belt (Page 1724) Example of detecting the direction of a conveyor belt (Page 1725) Overview of the valid data types (Page 1204) S: Set output Description You can use the instruction "Set output" to set the signal state of a specified operand to "1". The instruction is only executed if the result of logic operation (RLO) at the box input is "1". If the box input has the signal state "1", the specified operand is set to "1". If there is an RLO of "0" at the box input, the signal state of the specified operand remains unchanged. 2024 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameters The following table shows the parameters of the instruction "Set output": Parameters Declaratio n Data type Memory area Description <Operand> Output BOOL I, Q, M, D, L Operand which is set with RLO = "1". Example The following example shows how the instruction works: 7DJ,QB 7DJ,QB ! 7DJ2XW 7DJ,QB 6 The "TagOut" operand is set when one of the following conditions is fulfilled: The operands "TagIn_1" and "TagIn_2" have signal state "1". The operand "TagIn_3" has the signal state "0". See also Overview of the valid data types (Page 1204) SET_BF: Set bit field Description You can use the instruction "Set bit field" to set multiple bits starting from a certain address. You can use the input N to define the number of bits to be set. The address of the first bit to be set is defined by (<Operand>). If the value of the N input is greater than the number of bits in a selected byte, the bits of the next byte are set. The bits remain set until they are explicitly reset, for example, by another instruction. WinCC Basic V13.0 System Manual, 02/2014 2025 Programming the PLC 9.7 References Parameters The following table shows the parameters of the instruction "Set bit field": Parameters Declaration Data type Memory area S7-1200 S7-1500 Description EN Input BOOL I, Q, M, D, L I, Q, M, D, L, T, C Enable input N Input UINT Constant Constant Number of bits to be set <Operand> Output BOOL I, Q, M I, Q, M In the case of a DB or an IDB, an element of an ARRAY[..] of BOOL In the case of a DB or an IDB, an element of an ARRAY[..] of BOOL Pointer to the first bit to be set. Example The following example shows how the instruction works: 7DJ,QB 0\'%0\%RRO$UUD\>@ 7DJ,QB 6(7B%) (1 1 If the operands "TagIn_1" and "TagIn_2" have the signal state "1", 5 bits are set starting at the address of the operand "MyDB".MyBoolArray[4]. See also Overview of the valid data types (Page 1204) RESET_BF: Reset bit field Description You can use the instruction "Reset bit field" to reset several bits starting from a certain address. You can use the value of the N input to define the number of bits to be reset. The address of the first bit to be reset is defined by (<Operand>). If the value of the input N is greater than the number of bits in a selected byte, the bits of the next byte are reset. The bits remain reset until they are explicitly set, for example, by another instruction. 2026 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameters The following table shows the parameters of the instruction "Reset bit field": Parameters Declaration Data type Memory area S7-1200 S7-1500 Description EN Input BOOL I, Q, M, D, L I, Q, M, D, L, T, C Enable input N Input UINT Constant Constant Number of bits to be reset. <Operand> Output BOOL I, Q, M I, Q, M In the case of a DB or an IDB, an element of an ARRAY[..] of BOOL In the case of a DB or an IDB, an element of an ARRAY[..] of BOOL Pointer to the first bit to be reset. Example The following example shows how the instruction works: 7DJ,QB 0\'%0\%RRO$UUD\>@ 5(6(7B%) 7DJ,QB (1 1 If the operands "TagIn_1" and "TagIn_2" have the signal state "1", 5 bits are reset starting at the address of the operand "MyDB".MyBoolArray[4]. See also Overview of the valid data types (Page 1204) SR: Set/reset flip-flop Description You can use the instruction "Set/reset flip-flop" to set or reset the bit of a specified operand based on the signal state of the inputs S and R1. If the signal state is "1" at input S and "0" at input R1, the specified operand is set to "1". If the signal state is "0" at input S and "1" at input R1, the specified operand will be reset to "0". Input R1 takes priority over input S. When the signal state is "1" on both inputs S and R1, the signal state of the specified operand is reset to "0". WinCC Basic V13.0 System Manual, 02/2014 2027 Programming the PLC 9.7 References The instruction is not executed if the signal state at the two inputs S and R1 is "0". The signal state of the operand then remains unchanged. The current signal state of the operand is transferred to output Q and can be queried there. Parameters The following table shows the parameters of the instruction "Set/reset flip-flop": Parameter Declaration Data type Memory area S7-1200 S7-1500 Description S Input BOOL I, Q, M, D, L I, Q, M, D, L, T, C Enable setting R1 Input BOOL I, Q, M, D, L I, Q, M, D, L, T, C Enable resetting <Operand> InOut BOOL I, Q, M, D, L I, Q, M, D, L Operand that is set or reset Q Output BOOL I, Q, M, D, L I, Q, M, D, L Signal state of the operand Example The following example shows how the instruction works: 7DJ65 7DJ,QB 65 6 7DJ2XW 7DJ,QB 5 4 The operands "TagSR" and "TagOut" are set when the following conditions are fulfilled: The operand "TagIn_1" has the signal state "1". The operand "TagIn_2" has the signal state "0". The operands "TagSR" and "TagOut" are reset when one of the following conditions is fulfilled: The operand "TagIn_1" has signal state "0" and the operand "TagIn_2" has signal state "1". The operands "TagIn_1" and "TagIn_2" have signal state "1". See also Overview of the valid data types (Page 1204) 2028 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References RS: Reset/set flip-flop Description You can use the instruction "Reset/set flip-flop" to reset or set the bit of a specified operand based on the signal state of the inputs R and S1. If the signal state is "1" at input R and "0" at input S1, the specified operand will be reset to "0". If the signal state is "0" at input R and "1" at input S1, the specified operand is set to "1". Input S1 takes priority over input R. When the signal state is "1" at both inputs R and S1, the signal state of the specified operand is set to "1". The instruction is not executed if the signal state at the two inputs R and S1 is "0". The signal state of the operand then remains unchanged. The current signal state of the operand is transferred to output Q and can be queried there. Parameters The following table shows the parameters of the instruction "Reset/set flip-flop": Parameter Declaration Data type Memory area S7-1200 S7-1500 Description R Input BOOL I, Q, M, D, L I, Q, M, D, L, T, C Enable resetting S1 Input BOOL I, Q, M, D, L I, Q, M, D, L, T, C Enable setting <Operand> InOut BOOL I, Q, M, D, L I, Q, M, D, L Operand that is reset or set. Q Output BOOL I, Q, M, D, L I, Q, M, D, L Signal state of the operand Example The following example shows how the instruction works: 7DJ56 7DJ,QB 56 5 7DJ2XW 7DJ,QB 6 4 The operands "TagRS" and "TagOut" are reset when the following conditions are fulfilled: The operand "TagIn_1" has the signal state "1". The operand "TagIn_2" has the signal state "0". The operands "TagRS" and "TagOut" are set when the following conditions are fulfilled: WinCC Basic V13.0 System Manual, 02/2014 2029 Programming the PLC 9.7 References The operand "TagIn_1" has signal state "0" and the operand "TagIn_2" has signal state "1". The operands "TagIn_1" and "TagIn_2" have signal state "1". See also Overview of the valid data types (Page 1204) P: Scan operand for positive signal edge Description You can use the instruction "Scan operand for positive signal edge" to determine whether there is a "0" to "1" change in the signal state of a specified operand (<Operand1>). The instruction compares the current signal state of <Operand1> with the signal state of the previous scan, which is saved in an edge memory bit (<Operand2>). If the instruction detects a change in the result of logic operation (RLO) from "0" to "1", there is a positive, rising edge. If a rising edge is detected, the output of the instruction has the signal state "1". In all other cases, the signal state at the output of the instruction is "0". Specify the operand to be queried (<Operand1>) in the operand placeholder above the instruction. Specify the edge memory bit (<Operand2>) in the operand placeholder below the instruction. Note The address of the edge memory bit must not be used more than once in the program, otherwise the memory bit is overwritten. This would influence edge evaluation and the result would no longer be unequivocal. The memory area of the edge memory bit has to be located in a DB (static area for FB) or in the bit memory area. Parameters The following table shows the parameters of the "Scan operand for positive signal edge" instruction: Parameter 2030 Declaration Data type Memory area S7-1200 S7-1500 Description <Operand1> Input BOOL I, Q, M, D, L I, Q, M, D, L, T, C Signal to be scanned <Operand2> InOut BOOL I, Q, M, D, L I, Q, M, D, L Edge memory bit in which the signal state of the previous query is saved. WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Example The following example shows how the instruction works: 7DJ,QB 3 7DJB0 7DJ2XW 7DJ,QB Output "TagOut" is set when the following conditions are fulfilled: There is a rising edge at input "TagIn_1". The signal state of the operand "TagIn_2" is "1". See also Overview of the valid data types (Page 1204) Example of detecting the direction of a conveyor belt (Page 1725) N: Scan operand for negative signal edge Description You can use the instruction "Scan operand for negative signal edge" to determine whether there is a "1" to "0" change in the signal state of a specified operand (<Operand1>). The instruction compares the current signal state of <Operand1> with the signal state of the previous scan, which is saved in an edge memory bit (<Operand2>). If the instruction detects a change in the result of logic operation (RLO) from "1" to "0", there is a negative, falling edge. If a falling edge is detected, the output of the instruction has the signal state "1". In all other cases, the signal state at the output of the instruction is "0". Specify the operand to be queried (<Operand1>) in the operand placeholder above the instruction. Specify the edge memory bit (<Operand2>) in the operand placeholder below the instruction. Note The address of the edge memory bit must not be used more than once in the program, otherwise the memory bit is overwritten. This would influence edge evaluation and the result would no longer be unequivocal. The memory area of the edge memory bit has to be located in a DB (static area for FB) or in the bit memory area. WinCC Basic V13.0 System Manual, 02/2014 2031 Programming the PLC 9.7 References Parameters The following table shows the parameters of the "Scan operand for negative signal edge" instruction: Parameter Declaration Data type Memory area S7-1200 S7-1500 Description <Operand1> Input BOOL I, Q, M, D, L I, Q, M, D, L, T, C Signal to be scanned <Operand2> InOut BOOL I, Q, M, D, L I, Q, M, D, L Edge memory bit in which the signal state of the previous query is saved. Example The following example shows how the instruction works: 7DJ,QB 1 7DJB0 7DJ2XW 7DJ,QB Output "TagOut" is set when the following conditions are fulfilled: There is a falling edge at input "TagIn_1". The signal state of the operand "TagIn_2" is "1". See also Overview of the valid data types (Page 1204) P=: Set operand on positive signal edge Description You can use the instruction "Set operand on positive signal edge" to set a specified operand (<Operand2>) when there is a "0" to "1" change in the result of logic operation (RLO). The instruction compares the current RLO with the RLO from the previous query, which is saved in the edge memory bit (<Operand1>). If the instruction detects a change in the result of logic operation (RLO) from "0" to "1", there is a positive, rising edge. When a positive edge is detected, <Operand2> is set to signal state "1" for one program cycle. In all other cases, the operand has the signal state "0". 2032 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References You specify the operand (<Operand2>) to be set in the operand placeholder above the instruction. Specify the edge memory bit (<Operand1>) in the operand placeholder below the instruction. Note The address of the edge memory bit must not be used more than once in the program, otherwise the memory bit is overwritten. This would influence edge evaluation and the result would no longer be unequivocal. The memory area of the edge memory bit has to be located in a DB (static area for FB) or in the bit memory area. Parameters The following table shows the parameters of the instruction "Set operand on positive signal edge": Parameter Declaration Data type Memory area Description <Operand2> Output BOOL I, Q, M, D, L Operand which is set when there is a positive signal edge. <Operand1> InOut BOOL I, Q, M, D, L Edge memory bit Example The following example shows the parameters of the instruction: 7DJ,QB 7DJ,QB 7DJ2XW 3 7DJB0 The "TagOut" output is set for one program cycle, when the signal state at the input of the instruction box switches from "0" to "1" (positive signal edge). In all other cases, the "TagOut" output has signal state "0". See also Overview of the valid data types (Page 1204) N=: Set operand on negative signal edge Description You can use the instruction "Set operand on negative signal edge" to set a specified operand (<Operand1>) when there is a "1" to "0" change in the result of logic operation (RLO). The instruction compares the current RLO with the RLO from the previous query, which is saved WinCC Basic V13.0 System Manual, 02/2014 2033 Programming the PLC 9.7 References in the edge memory bit (<Operand2>). If the instruction detects a change in the result of logic operation (RLO) from "1" to "0", there is a negative, falling edge. When a negative edge is detected, <Operand1> is set to signal state "1" for one program cycle. In all other cases, the operand has the signal state "0". You specify the operand (<Operand1>) to be set in the operand placeholder above the instruction. Specify the edge memory bit (<Operand2>) in the operand placeholder below the instruction. Note The address of the edge memory bit must not be used more than once in the program, otherwise the memory bit is overwritten. This would influence edge evaluation and the result would no longer be unequivocal. The memory area of the edge memory bit has to be located in a DB (static area for FB) or in the bit memory area. Parameters The following table shows the parameters of the instruction "Set operand on negative signal edge": Parameter Declaration Data type Memory area Description <Operand1> Output BOOL I, Q, M, D, L Operand which is set when there is a negative signal edge. <Operand2> InOut BOOL I, Q, M, D, L Edge memory bit Example The following example shows how the instruction works: 7DJ,QB 7DJ,QB 7DJ2XW 1 7DJB0 The operand "TagOut" is set for one program cycle if the signal state at the input of the instruction box changes from "1" to "0" (negative signal edge). In all other cases, the operand "TagOut" has the signal state "0". See also Overview of the valid data types (Page 1204) 2034 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References P_TRIG: Scan RLO for positive signal edge Description Use the instruction "Scan RLO for positive signal edge" to query a "0" to "1" change in the signal state of the result of logic operation (RLO). The instruction compares the current signal state of the RLO with the signal state of the previous query, which is saved in an edge memory bit (<Operand>). If the instruction detects a change in the result of logic operation (RLO) from "0" to "1", there is a positive, rising edge. If a rising edge is detected, the output of the instruction has the signal state "1". In all other cases, the signal state at the output of the instruction is "0". Note The address of the edge memory bit must not be used more than once in the program, otherwise the memory bit is overwritten. This would influence edge evaluation and the result would no longer be unequivocal. The memory area of the edge memory bit has to be located in a DB (static area for FB) or in the bit memory area. Parameters The following table shows the parameters of the instruction "Scan RLO for positive signal edge": Parameter Declaration Data type Memory area Description CLK Input BOOL I, Q, M, D, L Current RLO <Operand> InOut BOOL M, D Edge memory bit in which the RLO of the previous query is saved. Q Output BOOL I, Q, M, D, L Result of edge evaluation Example The following example shows how the instruction works: 7DJ,QB ! 7DJ,QB 7DJ2XW 3B75,* &/. 4 &$6 -03 7DJB0 The RLO of the preceding bit logic operation is saved in the edge memory bit "Tag_M". If a "0" to "1" change is detected in the signal state of the RLO, the program jumps to jump label CAS1. WinCC Basic V13.0 System Manual, 02/2014 2035 Programming the PLC 9.7 References See also Overview of the valid data types (Page 1204) N_TRIG: Scan RLO for negative signal edge Description Use the instruction "Scan RLO for negative signal edge" to query a "1" to "0" change in the signal state of the result of logic operation (RLO). The instruction compares the current signal state of the RLO with the signal state of the previous query saved in the edge memory bit (<Operand>). If the instruction detects a change in the result of logic operation (RLO) from "1" to "0", there is a negative, falling edge. If a falling edge is detected, the output of the instruction has the signal state "1". In all other cases, the signal state at the output of the instruction is "0". Note The address of the edge memory bit must not be used more than once in the program, otherwise the memory bit is overwritten. This would influence edge evaluation and the result would no longer be unequivocal. The memory area of the edge memory bit has to be located in a DB (static area for FB) or in the bit memory area. Parameters The following table shows the parameters of the instruction "Scan RLO for negative signal edge": Parameter Declaration Data type Memory area Description CLK Input BOOL I, Q, M, D, L Current RLO <Operand> InOut BOOL M, D Edge memory bit in which the RLO of the previous query is saved. Q Output BOOL I, Q, M, D, L Result of edge evaluation Example The following example shows how the instruction works: 7DJ,QB ! 7DJ,QB 7DJ2XW 1B75,* &/. 4 &$6 -03 7DJB0 2036 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References The RLO of the preceding bit logic operation is saved in the edge memory bit "Tag_M". If a "1" to "0" change is detected in the signal state of the RLO, the program jumps to jump label CAS1. See also Overview of the valid data types (Page 1204) R_TRIG: Set tag on positive signal edge Description You can use the "Set tag on positive signal edge" instruction to set a specified tag in the instance DB when there is a "0" to "1" change in the result of logic operation (RLO). The instruction compares the current RLO at the input CLK with the RLO from the previous query, which is saved in the specified instance DB. If the instruction detects a change in the result of logic operation (RLO) from "0" to "1", there is a positive, rising edge. If a positive edge is detected, the tag in the instance DB is set to signal state "1" and the output Q returns the signal state "1" In all other cases, the signal state at the output of the instruction is "0". When you insert the instruction in the program, the "Call options" dialog opens automatically. In this dialog you can specify whether the edge memory bit is stored in its own data block (single instance) or as a local tag (multiple instance) in the block interface. If you create a separate data block, you will find this in the project tree in the "Program resources" folder under "Program blocks > System blocks". For additional information on this topic, refer to "See also". Parameters The following table shows the parameters of the instruction "Set tag on positive signal edge": Parameter WinCC Basic V13.0 System Manual, 02/2014 Declaration Data type Memory area S7-1200 S7-1500 Description EN Input BOOL I, Q, M, D, L I, Q, M, D, L, T, C Enable input ENO Output BOOL I, Q, M, D, L I, Q, M, D, L Enable output CLK Input BOOL I, Q, M, D, L or constant I, Q, M, D, L, T, C or constant Incoming signal, the edge of which is to be queried. Q Output BOOL I, Q, M, D, L I, Q, M, D, L Result of edge evaluation 2037 Programming the PLC 9.7 References Example The following example shows how the instruction works: 7DJ,QB '% 5B75,*B'% ! 5B75,* 7DJ,QB 7DJ,Q (1 &/. 7DJ,QB 4 7DJ2XW (12 The RLO of the preceding query is saved in the instance DB "R_TRIG_DB". If a change is the signal state of the RLO from "0" to "1" is detected in the operands "TagIn_1" and "TagIn_2" or in the operand "TagIn_3", the output "TagOut" has signal state "1". See also Overview of the valid data types (Page 1204) F_TRIG: Set tag on negative signal edge Description You can use the "Set tag on negative signal edge" instruction to set a specified tag in the instance DB when there is a "1" to "0" change in the result of logic operation (RLO). The instruction compares the current RLO at the input CLK with the RLO from the previous query, which is saved in the specified instance DB. If the instruction detects a change in the result of logic operation (RLO) from "1" to "0", there is a negative, falling edge. If a negative edge is detected, the tag in the instance DB is set to signal state "1" and the output Q returns the signal state "1" In all other cases, the signal state at the output of the instruction is "0". When you insert the instruction in the program, the "Call options" dialog opens automatically. In this dialog you can specify whether the edge memory bit is stored in its own data block (single instance) or as a local tag (multiple instance) in the block interface. If you create a separate data block, you will find this in the project tree in the "Program resources" folder under "Program blocks > System blocks". For additional information on this topic, refer to "See also". Parameters The following table shows the parameters of the instruction "Set tag on negative signal edge": Parameter 2038 Declaration Data type Memory area S7-1200 S7-1500 Description EN Input BOOL I, Q, M, D, L I, Q, M, D, L, T, C Enable input ENO Output BOOL I, Q, M, D, L I, Q, M, D, L Enable output WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameter Declaration Data type Memory area S7-1200 S7-1500 Description CLK Input BOOL I, Q, M, D, L or constant I, Q, M, D, L, T, C or constant Incoming signal, the edge of which is to be queried. Q Output BOOL I, Q, M, D, L I, Q, M, D, L Result of edge evaluation Example The following example shows how the instruction works: 7DJ,QB '% )B75,*B'% ! )B75,* 7DJ,QB 7DJ,Q 7DJ,QB (1 &/. 4 7DJ2XW (12 The RLO of the preceding query is saved in the instance DB "F_TRIG_DB". If a change is the signal state of the RLO from "1" to "0" is detected in the operands "TagIn_1" and "TagIn_2" or in the operand "TagIn_3", the output "TagOut" has signal state "1". See also Overview of the valid data types (Page 1204) Timer operations IEC Timers TP: Generate pulse Description You can use the instruction "Generate pulse" to set output Q for the duration PT. The instruction is started when the result of logic operation (RLO) at input IN changes from "0" to "1" (positive signal edge). The configured time duration PT begins when the instruction starts. Output Q is set for the time duration PT, regardless of the subsequent course of the input signal (positive edge). Even when a new positive signal edge is detected, the signal state of the Q output is not affected as long as the PT duration is running. The current time value can be queried at the output ET. The time value starts at T#0s and ends when the value of the time duration PT is reached. If the configured time duration PT is reached and the signal state at input IN is "0", the ET output is reset. WinCC Basic V13.0 System Manual, 02/2014 2039 Programming the PLC 9.7 References Each call of the "Generate pulse" instruction must be assigned an IEC Timer in which the instruction data is stored. Note If the timer is not called in the program because it is skipped, for example, output ET returns a constant value as soon as the timer has expired. For S7-1200 CPU An IEC Timer is a structure of the data type IEC_TIMER or TP_TIME that you can declare as follows: Declaration of a data block of system data type IEC_TIMER (for example, "MyIEC_TIMER") Declaration as a local tag of the type TP_TIME or IEC_TIMER in the "Static" section of a block (for example, #MyIEC_TIMER) For S7-1500 CPU An IEC Timer is a structure of the data type IEC_TIMER, IEC_LTIMER, TP_TIME or TP_LTIME that you can declare as follows: Declaration of a data block of system data type IEC_TIMER or IEC_LTIMER (for example, "MyIEC_TIMER") Declaration as a local tag of the type TP_TIME, TP_LTIME, IEC_TIMER or IEC_LTIMER in the "Static" section of a block (for example, #MyIEC_TIMER) When you insert the instruction in the program, the "Call options" dialog opens in which you can specify whether the IEC Timer is stored in its own data block (single instance) or as a local tag (multiple instance) in the block interface. If you create a separate data block, you will find this in the project tree in the "Program resources" folder under "Program blocks > System blocks". For additional information on this topic, refer to "See also". The instruction data is updated both when the instruction is called and also each time the outputs Q or ET are accessed. The execution of the "Generate pulse" instruction requires a preceding logic operation. It can be placed within or at the end of the network. 2040 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameters The following table shows the parameters of the "Generate pulse" instruction: Parameter Declaration Data type Memory area S7-1200 S7-1500 S7-1200 S7-1500 Description IN Input BOOL BOOL I, Q, M, D, L I, Q, M, D, L, T, C, P Start input PT Input TIME TIME, LTIME I, Q, M, D, L or constant I, Q, M, D, L, P or constant Duration of the pulse. The value of the PT parameter must be positive. Q Output BOOL BOOL I, Q, M, D, L I, Q, M, D, L, P Pulse output ET Output TIME TIME, LTIME I, Q, M, D, L I, Q, M, D, L, P Current time value For additional information on valid data types, refer to "See also". Pulse timing diagram The following figure shows the pulse timing diagram of the "Generate pulse" instruction: ,1 4 37 37 37 (7 37 See also Overview of the valid data types (Page 1204) Example of controlling room temperature (Page 1729) WinCC Basic V13.0 System Manual, 02/2014 2041 Programming the PLC 9.7 References TON: Generate on-delay Description You can use the instruction "Generate on-delay" to delay setting of the Q output by the time configured with the PT time. The instruction is started when the result of logic operation (RLO) at input IN changes from "0" to "1" (positive signal edge). The programmed time PT begins when the instruction starts. When the duration PT expires, output Q has the signal state "1". Output Q remains set as long as the start input is still "1". When the signal state at the start input changes from "1" to "0", the Q output is reset. The timer function is started again when a new positive signal edge is detected at the start input. The current time value can be queried at the output ET. The time value starts at T#0s and ends when the value of the time duration PT is reached. The ET output is reset as soon as the signal state at the IN input changes to "0". Each call of the "Generate on-delay" instruction must be assigned an IEC Timer in which the instruction data is stored. Note If the timer is not called in the program because it is skipped, for example, output ET returns a constant value as soon as the timer has expired. For S7-1200 CPU An IEC Timer is a structure of the data type IEC_TIMER or TON_TIME that you can declare as follows: Declaration of a data block of system data type IEC_TIMER (for example, "MyIEC_TIMER") Declaration as a local tag of the type TON_TIME or IEC_TIMER in the "Static" section of a block (for example, #MyIEC_TIMER) For S7-1500 CPU An IEC Timer is a structure of the data type IEC_TIMER, IEC_LTIMER, TON_TIME or TON_LTIME that you can declare as follows: Declaration of a data block of system data type IEC_TIMER or IEC_LTIMER (for example, "MyIEC_TIMER") Declaration as a local tag of the type TON_TIME, TON_LTIME, IEC_TIMER or IEC_LTIMER in the "Static" section of a block (for example, #MyIEC_TIMER) When you insert the instruction in the program, the "Call options" dialog opens in which you can specify whether the IEC Timer is stored in its own data block (single instance) or as a local tag (multiple instance) in the block interface. If you create a separate data block, it is saved to the "Program resources" folder in the "Program blocks > System blocks" path of the project tree. For additional information on this topic, refer to "See also". The instruction data is updated both when the instruction is called and also each time the outputs Q or ET are accessed. 2042 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References The execution of the "Generate on-delay" instruction requires a preceding logic operation. It can be placed within or at the end of the network. Parameters The following table shows the parameters of the "Generate on-delay" instruction: Parameter Declaration Data type Memory area S7-1200 S7-1500 S7-1200 S7-1500 Description IN Input BOOL BOOL I, Q, M, D, L I, Q, M, D, L, T, C, P Start input PT Input TIME TIME, LTIME I, Q, M, D, L or constant I, Q, M, D, L, P or constant Duration of the on delay. The value of the PT parameter must be positive. Q Output BOOL BOOL I, Q, M, D, L I, Q, M, D, L, P Output that is set when the time PT expires. ET Output TIME TIME, LTIME I, Q, M, D, L I, Q, M, D, L, P Current time value For additional information on valid data types, refer to "See also". Pulse timing diagram The following figure shows the pulse timing diagram of the "Generate on-delay" instruction: ,1 4 37 37 (7 37 WinCC Basic V13.0 System Manual, 02/2014 2043 Programming the PLC 9.7 References See also Overview of the valid data types (Page 1204) TOF: Generate off-delay Description You can use the "Generate off-delay" instruction to delay setting of the Q output by the time configured with the PT time. The output Q is set when the result of logic operation (RLO) at input IN changes from "0" to "1" (positive signal edge). When the signal state at input IN changes back to "0" (positive signal edge), the configured time duration PT starts. Output Q remains set as long as the time duration PT is running. When the PT time duration expires, the Q output is reset. If the signal state at input IN changes to "1" before the PT time duration expires, the timer is reset. The signal state at the output Q will continue to be "1". The current time value can be queried at the output ET. The time value starts at T#0s and ends when the value of the time duration PT is reached. When the time duration PT expires, the ET output remains set to the current value until input IN changes back to "1". If input IN changes to "1" before the time duration PT has expired, the ET output is reset to the value T#0s. Each call of the "Generate off-delay" instruction must be assigned to an IEC Timer in which the instruction data is stored. Note If the timer is not called in the program because it is skipped, for example, output ET returns a constant value as soon as the timer has expired. For S7-1200 CPU An IEC Timer is a structure of the data type IEC_TIMER or TOF_TIME that you can declare as follows: Declaration of a data block of system data type IEC_TIMER (for example, "MyIEC_TIMER") Declaration as a local tag of the type TOF_TIME or IEC_TIMER in the "Static" section of a block (for example, #MyIEC_TIMER) For S7-1500 CPU An IEC Timer is a structure of the data type IEC_TIMER, IEC_LTIMER, TOF_TIME or TOF_LTIME that you can declare as follows: Declaration of a data block of system data type IEC_TIMER or IEC_LTIMER (for example, "MyIEC_TIMER") Declaration as a local tag of the type TOF_TIME, TOF_LTIME, IEC_TIMER or IEC_LTIMER in the "Static" section of a block (for example, #MyIEC_TIMER) When you insert the instruction in the program, the "Call options" dialog opens in which you can specify whether the IEC Timer is stored in its own data block (single instance) or as a local 2044 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References tag (multiple instance) in the block interface. If you create a separate data block, you will find this in the project tree in the "Program resources" folder under "Program blocks > System blocks". For additional information on this topic, refer to "See also". The instruction data is updated both when the instruction is called and also each time the outputs Q or ET are accessed. The execution of the "Generate off-delay" instruction requires a preceding logic operation. It can be placed within or at the end of the network. Parameters The following table shows the parameters of the "Generate off-delay" instruction: Parameter Declaration Data type Memory area S7-1200 S7-1500 S7-1200 S7-1500 Description IN Input BOOL BOOL I, Q, M, D, L I, Q, M, D, L, T, C, P Start input PT Input TIME TIME, LTIME I, Q, M, D, L or constant I, Q, M, D, L, P or constant Duration of the off delay The value of the PT parameter must be positive. Q Output BOOL BOOL I, Q, M, D, L I, Q, M, D, L, P Output that is reset when the timer PT expires. ET Output TIME TIME, LTIME I, Q, M, D, L I, Q, M, D, L, P Current time value For additional information on valid data types, refer to "See also". WinCC Basic V13.0 System Manual, 02/2014 2045 Programming the PLC 9.7 References Pulse timing diagram The following figure shows the pulse timing diagram of the "Generate off-delay" instruction: ,1 4 37 37 (7 37 See also Overview of the valid data types (Page 1204) TONR: Time accumulator Description The instruction "Time accumulator" is used to accumulate time values within a period set by the parameter PT. The instruction is executed and the configured time duration PT is started when the result of logic operation (RLO) at input IN changes from "0" to "1" (positive edge). While the time set at PT is running, the time values are accumulated that are recorded at signal state "1" at input IN. The accumulated time is written to output ET and can be queried there. When the current time value PT is reached, the output Q has the signal state "1". Output Q remains set at "1", even when the signal state at input IN changes to "0". The R input resets the outputs ET and Q regardless of the signal state at the start input. Each call of the "Time accumulator" instruction must be assigned to an IEC Timer in which the instruction data is stored. For S7-1200 CPU An IEC Timer is a structure of the data type IEC_TIMER or TONR_TIME that you can declare as follows: Declaration of a data block of system data type IEC_TIMER (for example, "MyIEC_TIMER") Declaration as a local tag of the type TONR_TIME or IEC_TIMER in the "Static" section of a block (for example, #MyIEC_TIMER) 2046 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References For S7-1500 CPU An IEC Timer is a structure of the data type IEC_TIMER, IEC_LTIMER, TONR_TIME or TONR_LTIME that you can declare as follows: Declaration of a data block of system data type IEC_TIMER or IEC_LTIMER (for example, "MyIEC_TIMER") Declaration as a local tag of the type TONR_TIME, TONR_LTIME, IEC_TIMER or IEC_LTIMER in the "Static" section of a block (for example, #MyIEC_TIMER) When you insert the instruction in the program, the "Call options" dialog opens in which you can specify whether the IEC Timer is stored in its own data block (single instance) or as a local tag (multiple instance) in the block interface. If you create a separate data block, you will find this in the project tree in the "Program resources" folder under "Program blocks > System blocks". For additional information on this topic, refer to "See also". The instruction data is updated both when the instruction is called and also each time the outputs Q or ET are accessed. The execution of the "Time accumulator" instruction requires a preceding logic operation. It can be placed within or at the end of the network. Parameters The following table shows the parameters of the "Time accumulator" instruction: Parameter Declaration Data type Memory area S7-1200 S7-1500 S7-1200 S7-1500 Description IN Input BOOL BOOL I, Q, M, D, L I, Q, M, D, L, T, C, P Start input R Input BOOL BOOL I, Q, M, D, L or constant I, Q, M, D, L, P or constant Reset input PT Input TIME TIME, LTIME I, Q, M, D, L or constant I, Q, M, D, L, P or constant Maximum duration of time recording. The value of the PT parameter must be positive. Q Output BOOL BOOL I, Q, M, D, L I, Q, M, D, L, P Output that is set when the time PT expires. ET Output TIME TIME, LTIME I, Q, M, D, L I, Q, M, D, L, P Current time value For additional information on valid data types, refer to "See also". WinCC Basic V13.0 System Manual, 02/2014 2047 Programming the PLC 9.7 References Pulse timing diagram The following figure shows the pulse timing diagram of the "Time accumulator" instruction: ,1 5 4 37 (7 See also Overview of the valid data types (Page 1204) TP: Start pulse timer Description Use the instruction "Start pulse timer" to start an IEC Timer with a specified duration as pulse. The IEC Timer is started when the result of logic operation (RLO) changes from "0" to "1" (positive signal edge). The IEC Timer runs for the specified time duration regardless of the subsequent course of the RLO. The expiry of the IEC Timer is also not affected by the detection of a new rising edge. As long as the IEC Timer is running, the querying of the timer status for "1" returns the signal state "1". When the IEC Timer has expired, the timer status returns the signal state "0". Note The start and the query of the IEC Timer may be on different expiry levels as each query of the outputs Q or ET updates the IEC_TIMER structure. 2048 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References For S7-1200 CPU The instruction "Start pulse timer" stores its data in a structure of the data type IEC_TIMER or TP_TIME. You can declare the structure as follows: Declaration of a data block of system data type IEC_TIMER (for example, "MyIEC_TIMER") Declaration as a local tag of the type TP_TIME or IEC_TIMER in the "Static" section of a block (for example, #MyIEC_TIMER) For S7-1500 CPU The instruction "Start pulse timer" stores its data in a structure of the data type IEC_TIMER, IEC_LTIMER, TP_TIME or TP_LTIME. You can declare the structure as follows: Declaration of a data block of system data type IEC_TIMER or IEC_LTIMER (for example, "MyIEC_TIMER") Declaration as a local tag of the type TP_TIME, TP_LTIME, IEC_TIMER or IEC_LTIMER in the "Static" section of a block (for example, #MyIEC_TIMER) The instruction data is updated both when the instruction is called and also each time the specified timer is accessed. The current timer status is saved in the structure components Q of the IEC Timer. You can query the timer status with the help of a binary logic operation. The query for Q or ET (e. g. "MyTimer".Q or "MyTimer".ET) updates the IEC_TIMER structure. The execution of the instruction "Start pulse timer" assumes a preceding logic operation. It can be placed only at the end of the network. Parameters The following table shows the parameters of the instruction "Start pulse timer": Parameters Declaration Data type S7-1200 S7-1500 Memory area Description VALUE Input TIME TIME, LTIME I, Q, M, D, L or constant Duration with which the IEC Timer runs. <IEC Timer> InOut IEC_TIMER, TP_TIME IEC_TIMER, IEC_LTIMER, TP_TIME, TP_LTIME D, L IEC Timer which is started. For additional information on valid data types, refer to "See also". WinCC Basic V13.0 System Manual, 02/2014 2049 Programming the PLC 9.7 References Example The following example shows how the instruction works: '% 0\,(&B7,0(5 7DJB,QSXW 7DJB7,0( 73 7,0( 9$/8( The instruction "Start pulse timer" is executed when the signal state of the operand "Tag_Input" changes from "0" to "1". The timer "DB1".MyIEC_TIMER is started for the time stored in the operand "TagTime". 7DJB2XWSXW '%0\,(&B 7,0(54 As long as the timer "DB1".MyIEC_TIMER is running, the timer status ("DB1".MyIEC_TIMER.Q) has signal state "1" and the operand "Tag_Output" is set. When the IEC Timer has expired, the signal state of the time status changes back to "0" and the "Tag_Output" operand is reset. See also Overview of the valid data types (Page 1204) TON: Start on-delay timer Description Use the "Start on-delay timer" instruction to start an IEC Timer with a specified duration as ondelay. The IEC Timer is started when the result of logic operation (RLO) changes from "0" to "1" (positive signal edge). The IEC Timer runs for the specified time duration. The output returns the signal state "1" if the RLO at the input of the instruction has the signal state "1". If the RLO changes to "0" before the end of the timer, the running IEC Timer is reset. The query of the timer status for "1" returns the signal state "0". The IEC Timer restarts when the next rising signal edge is detected at the input of the instruction. Note The start and the query of the IEC Timer may be on different expiry levels as each query of the outputs Q or ET updates the IEC_TIMER structure. 2050 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References For S7-1200 CPU The instruction "Start on-delay timer" stores its data in a structure of the data type IEC_TIMER or TON_TIME. You can declare the structure as follows: Declaration of a data block of system data type IEC_TIMER (for example, "MyIEC_TIMER") Declaration as a local tag of the type TON_TIME or IEC_TIMER in the "Static" section of a block (for example, #MyIEC_TIMER) For S7-1500 CPU The "Start on-delay timer" instruction stores its data in a structure of the data type IEC_TIMER, IEC_LTIMER, TON_TIME or TON_LTIME. You can declare the structure as follows: Declaration of a data block of system data type IEC_TIMER or IEC_LTIMER (for example, "MyIEC_TIMER") Declaration as a local tag of the type TON_TIME, TON_LTIME, IEC_TIMER or IEC_LTIMER in the "Static" section of a block (for example, #MyIEC_TIMER) The instruction data is updated both when the instruction is called and also each time the specified timer is accessed. The current timer status is saved in the structure components ET of the IEC Timer. You can query the timer status with the help of a binary logic operation. The query for Q or ET (e. g. "MyTimer".Q or "MyTimer".ET) updates the IEC_TIMER structure. The execution of the "Start on-delay timer" instruction assumes a preceding logic operation. It can be placed only at the end of the network. Parameters The following table shows the parameters of the instruction "Start on-delay timer": Parameters Declaration Data type S7-1200 S7-1500 Memory area Description VALUE Input TIME TIME, LTIME I, Q, M, D, L or constant Duration with which the IEC Timer runs. <IEC Timer> InOut IEC_TIMER, TON_TIME IEC_TIMER, IEC_LTIMER, TON_TIME, TON_LTIME D, L IEC Timer which is started. For additional information on valid data types, refer to "See also". WinCC Basic V13.0 System Manual, 02/2014 2051 Programming the PLC 9.7 References Example The following example shows how the instruction works: 0\,(&B7,0(5 7DJB,QSXW 7DJB7,0( 721 7,0( 9$/8( The "Start on-delay timer" instruction is executed when the signal state of the operand "Tag_Input" changes from "0" to "1". The "MyIEC_TIMER" timer is started for the time stored in the "Tag_TIME" operand. 7DJB2XWSXW 0\,(&B7,0(54 If the timer "MyIEC_TIMER" has expired and the operand "Tag_Input" has the signal state "1", querying the timer status ("MyIEC_TIMER".Q) returns signal state "1" and the "Tag_Output" operand is set. When the signal state of the operand "Tag_Input" changes to "0", the querying of the timer status returns the signal state "0" and the operand "Tag_Output" is reset. See also Overview of the valid data types (Page 1204) TOF: Start off-delay timer Description Use the "Start off-delay timer" instruction to start an IEC Timer with a specified duration as offdelay. The query of the timer status for "1" returns the signal state "0" if the result of the logic operation (RLO) at the input of the instruction has the signal state "1". When the RLO changes from "1" to "0" (negative signal edge), the IEC Timer starts with the specified time duration. The timer status remains at signal state "1" as long as the IEC Timer is running. When the timer has run out and the RLO at the input of the instruction has the signal state "0", the timer status is set to the signal state "0". If the RLO changes to "1" before the end of the timer, the running IEC Timer is reset and the timer status remain at the signal state "1". Note The start and the query of the IEC Timer may be on different expiry levels as each query of the outputs Q or ET updates the IEC_TIMER structure. 2052 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References For S7-1200 CPU The instruction "Start off-delay timer" stores its data in a structure of the data type IEC_TIMER or TOF_TIME. You can declare the structure as follows: Declaration of a data block of system data type IEC_TIMER (for example, "MyIEC_TIMER") Declaration as a local tag of the type TOF_TIME or IEC_TIMER in the "Static" section of a block (for example, #MyIEC_TIMER) For S7-1500 CPU The "Start off-delay timer" instruction stores its data in a structure of the data type IEC_TIMER, IEC_LTIMER, TOF_TIME or TOF_LTIME. You can declare the structure as follows: Declaration of a data block of system data type IEC_TIMER or IEC_LTIMER (for example, "MyIEC_TIMER") Declaration as a local tag of the type TOF_TIME, TOF_LTIME, IEC_TIMER or IEC_LTIMER in the "Static" section of a block (for example, #MyIEC_TIMER) The instruction data is updated both when the instruction is called and also each time the specified timer is accessed. The current timer status is saved in the structure components ET of the IEC Timer. You can query the timer status with the help of a binary logic operation. The query for Q or ET (e. g. "MyTimer".Q or "MyTimer".ET) updates the IEC_TIMER structure. The execution of the "Start off-delay timer" instruction assumes a preceding logic operation. It can be placed only at the end of the network. Parameters The following table shows the parameters of the instruction "Start off-delay timer": Parameters Declaration Data type S7-1200 S7-1500 Memory area Description VALUE Input TIME TIME, LTIME I, Q, M, D, L or constant Duration with which the IEC Timer runs. <IEC Timer> InOut IEC_TIMER, TOF_TIME IEC_TIMER, D, L IEC_LTIMER , TOF_TIME, TOF_LTIME IEC Timer which is started. For additional information on valid data types, refer to "See also". WinCC Basic V13.0 System Manual, 02/2014 2053 Programming the PLC 9.7 References Example The following example shows how the instruction works: 0\,(&B7,0(5 72) 7DJB,QSXW 7DJB7,0( 7,0( 9$/8( The "Start off-delay timer" instruction is executed when the signal state of the operand "Tag_Input" changes from "1" to "0". The #MyIEC_TIMER timer is started for the time stored in the operand "Tag_TIME". 7DJB2XWSXW 0\,(&B7,0(5 As long as timer #MyIEC_TIMER is running, the query of the time status (#MyIEC_TIMER.Q) returns the signal state "1" and operand "Tag_Output" is set. If the timer has expired and the operand "Tag_Input" has the signal state "0", the query of the timer status returns the signal state "0". If the signal state of the operand "Tag_Input" changes to "1" before timer #MyIEC_TIMER expires, the timer is reset. When the signal state of the operand "Tag_Input" is "1", the query of the timer status returns the signal state "1". See also Overview of the valid data types (Page 1204) TONR: Time accumulator Description You can use the "Time accumulator" instruction to record how long the signal is at the input of instruction "1". The instruction is started when the result of logic operation (RLO) changes from "0" to "1" (positive signal edge). The time is recorded as long at the RLO is "1". If the RLO changes to "0", the instruction is halted. If the RLO changes back to "1", the time recording is continued. The query of the timer status for "1" returns the signal state "1" if the recorded time exceeds the value of the specified time duration and the RLO at the input of coil is "1". The timer status and the currently expired timer can be reset to "0" using the "Reset timer" instruction. Note The start and the query of the IEC Timer may be on different expiry levels as each query of the outputs Q or ET updates the IEC_TIMER structure. 2054 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References For S7-1200 CPU The "Time accumulator" instruction stores its data in a structure of the data type IEC_TIMER or TONR_TIME. You can declare the structure as follows: Declaration of a data block of system data type IEC_TIMER (for example, "MyIEC_TIMER") Declaration as a local tag of the type TONR_TIME or IEC_TIMER in the "Static" section of a block (for example, #MyIEC_TIMER) For S7-1500 CPU The "Time accumulator" instruction stores its data in a structure of the data type IEC_TIMER, IEC_LTIMER, TONR_TIME or TONR_LTIME. You can declare the structure as follows: Declaration of a data block of system data type IEC_TIMER or IEC_LTIMER (for example, "MyIEC_TIMER") Declaration as a local tag of the type TONR_TIME, TONR_LTIME, IEC_TIMER or IEC_LTIMER in the "Static" section of a block (for example, #MyIEC_TIMER) The instruction data is updated both when the instruction is called and also each time the specified timer is accessed. The current timer status is saved in the structure components ET of the IEC Timer. You can query the timer status with the help of a binary logic operation. The query for Q or ET (e. g. "MyTimer".Q or "MyTimer".ET) updates the IEC_TIMER structure. The execution of the "Time accumulator" instruction requires a preceding logic operation. It can be placed only at the end of the network. Parameters The following table shows the parameters of the "Time accumulator" instruction: Parameters Declaration Data type S7-1200 S7-1500 Memory area Descripti on VALUE Input TIME TIME, LTIME I, Q, M, D, L or constant Duration with which the IEC Timer runs. <IEC Timer> InOut IEC_TIMER, TONR_TIME IEC_TIMER, IEC_LTIMER, TONR_TIME, TONR_LTIME D, L IEC Timer which is started. For additional information on valid data types, refer to "See also". WinCC Basic V13.0 System Manual, 02/2014 2055 Programming the PLC 9.7 References Example The following example shows how the instruction works: 0\,(&B7,0(5 7DJB,QSXW 7DJB7,0( 7215 7,0( 9$/8( The "Time accumulator" instruction is executed if there is a positive signal edge in the RLO. The time is recorded as long as the operand "Tag_Input" has the signal state "1". 7DJB2XWSXW 0\,(&B7,0(54 If the recorded time exceeds the value of the operand "Tag_TIME", then the query of the timer status ("MyIEC_TIMER".Q) will return the signal state "1" and the operand "Tag_Output" will be set. See also Overview of the valid data types (Page 1204) RT: Reset timer (Page 2056) RT: Reset timer Description You can use the "Reset timer" instruction to reset an IEC Timer to "0". You specify the IEC Timer to be reset by entering the name of the data block that contains the structure of the IEC Timer in the placeholder above the instruction. The instruction is only executed if the result of logic operation (RLO) at the box input is "1". When the instruction is executed the structure components of the IEC Timer are reset to "0" in the specified data block. If the RLO at box input is "0", the instruction is not executed. The instruction does not influence the RLO. The RLO at the box input is transferred directly to the box output. You must assign a IEC Timer declared in the program to the "Reset timer" instruction. The instruction data is updated only when the instruction is called and not each time the assigned IEC Timer is accessed. The query of the data is only identical from the call of the instruction to the next call of the instruction. 2056 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameters The following table shows the parameters of the instruction "Reset timer": Parameters Declaration <IEC Timer> Data type InOut S7-1200 S7-1500 IEC_TIMER, TP_TIME, TON_TIME, TOF_TIME, TONR_TIME IEC_TIMER, IEC_LTIMER, TP_TIME, TP_LTIME, TON_TIME, TON_LTIME, TOF_TIME, TOF_LTIME, TONR_TIME, TONR_LTIME Memory area Description D, L IEC Timer, which is reset. For additional information on valid data types, refer to "See also". Example The following example shows how the instruction works: 721B'% 721 7,0( 7DJB,QSXWB ,1 (7 7DJB37 37 4 7DJB(7 7DJB6WDWXV The "Generate on-delay" instruction executes when the signal state of the "Tag_Input_1" operand changes from "0" to "1". The IEC Timer stored in the instance data block "TON_DB" is started with the time duration that is specified by the operand "Tag_PT". 7DJB,QSXWB 721B'% 7DJB,QSXWB 57 If the operands "Tag_Input_2" and "Tag_Input_3" have the signal state "1", the "Reset timer" instruction is executed and the IEC Timer stored in the data block "TON_DB" is reset. See also Overview of the valid data types (Page 1204) WinCC Basic V13.0 System Manual, 02/2014 2057 Programming the PLC 9.7 References PT: Load time duration Description Use the "Load time duration" instruction to set the time duration of an IEC Timer. The instruction is executed in every cycle when the result of logic operation (RLO) at the input of the instruction has the signal state "1". The instruction writes the specified time duration to the structure of the specified IEC Timer. Note If the specified IEC Timer is running during the execution, the instruction overwrites the current time duration of the specified IEC Timer. As a result, the timer status of the IEC Timer can change. You must assign a IEC Timer declared in the program to the "Load time duration" instruction. The instruction data is updated when the instruction is called and each time the assigned IEC Timer is accessed. The query for Q or ET (e. g. "MyTimer".Q or "MyTimer".ET) updates the IEC_TIMER structure. Parameters The following table shows the parameters of the instruction "Load time duration": Parameters Declaration Data type S7-1200 S7-1500 Memory area Description PT Input TIME TIME, LTIME I, Q, M, D, L or constant Time duration <IEC Timer> InOut IEC_TIMER, TP_TIME, TON_TIME, TOF_TIME, TONR_TIME IEC_TIMER, IEC_LTIMER, TP_TIME, TP_LTIME, TON_TIME, TON_LTIME, TOF_TIME, TOF_LTIME, TONR_TIME, TONR_LTIME D, L IEC Timer, the duration of which is set. For additional information on valid data types, refer to "See also". 2058 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Example The following example shows how the instruction works: 721B'% 721 7,0( 7DJB,QSXWB ,1 (7 7DJB37 37 4 7DJB(7 7DJB6WDWXV The "Generate on-delay" instruction executes when the signal state of the "Tag_Input_1" operand changes from "0" to "1". The IEC Timer stored in the instance data block "TON_DB" is started with the time duration that is specified by the operand "Tag_PT". 721B'% 37 7DJB,QSXWB 7DJB37B 37 The "Load time duration" instruction is executed when the operand "Tag_Input_2" has the signal state "1". The instruction writes the time duration "Tag_PT_2" in the instance data block "TON_DB" and at the same time overwrites the value of the operand "Tag_PT" within the data block. As a result, the signal state of the timer status can change at the next query or upon access to "MyTimer".Q or "MyTimer".ET. Note The "Tag_Input_2" is executed as pulse flag in order that the time duration is loaded only throughout one program cycle. See also Overview of the valid data types (Page 1204) SIMATIC Timers S_PULSE: Assign pulse timer parameters and start Description The "Assign pulse timer parameters and start" instruction starts a programmed timer when a transition from "0" to "1" (positive signal edge) is detected in the result of logic operation (RLO) at input S. The timer expires with the programmed duration (TV) as long as the signal state at input S is "1". If the signal state at input S changes to "0" before the programmed duration expires, the timer is stopped. In this case, the signal state at output Q is "0". The duration is made up internally of a time value and a time base and is programmed at parameter TV. When the instruction is started, the programmed time value is counted down WinCC Basic V13.0 System Manual, 02/2014 2059 Programming the PLC 9.7 References to zero. The time base determines the time period of the time value. The current time value is output binary-coded at output BI and BCD-coded at output BCD. If the timer is running and the signal state at input R changes to "1", the current time value and the time base are also set to zero. If the timer is not running, the signal state "1" at the R input has no effect. The "Assign pulse timer parameters and start" instruction needs a preceding logic operation for the edge evaluation and can be placed within or at the end of the network. The instruction data is updated with each access. It can therefore happen that the query of the data at the start of the cycle returns different values than at the end of the cycle. Note In the time cell, the operating system reduces the time value in an interval specified by the time base by one unit until the value equals "0". The decrementation is performed asynchronously to the user program. The resulting timer is therefore at maximum up to one time interval shorter than the desired time base. You can find an example of how a time cell can be formed under: See also "L: Load timer value". Parameters The following table shows the parameters of the "Assign pulse timer parameters and start" instruction: Parameter Declaration Data type Memory area Description <Timer> InOut/Input TIMER T Time of the instruction The number of timers depends on the CPU. S Input BOOL I, Q, M, T, C, D, L, P Start input TV Input S5TIME, WORD I, Q, M, D, L or constant Time duration R Input BOOL I, Q, M, T, C, D, L, P or constant Reset input BI Output WORD I, Q, M, D, L, P Current time value (binary-coded) BCD Output WORD I, Q, M, D, L, P Current time value (BCD format) Q Output BOOL I, Q, M, D, L, P Status of the timer For additional information on valid data types, refer to "See also". 2060 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Pulse timing diagram The following figure shows the pulse timing diagram of the "Assign pulse timer parameters and start" instruction: W W W 5/2DWLQSXW6 5/2DWLQSXW5 7LPHUUXQQLQJ 4XHU\ 4XHU\ W SURJUDPPHGWLPH Example The following example shows how the instruction works: 7LPHUB 6B38/6( 7DJ,QB 7DJ,QB1XPEHU 6 79 %, 7DJ9DOXHB %&' 7DJ9DOXHB 7DJ2XW 7DJ,QB 5 4 "Timer_1" starts when the signal state of the "TagIn_1" operand changes from "0" to "1". The timer runs for the time value of the "TagIn_Number" operand as long as the "TagIn_1" operand has the signal state "1". If the signal state of the operand "TagIn_1" changes from "1" to "0" before the timer expires, the timer "Timer_1" is stopped. The "TagOut" operand is reset to signal state "0". WinCC Basic V13.0 System Manual, 02/2014 2061 Programming the PLC 9.7 References The "TagOut" operand has the signal state "1" as long as the timer is running and the "TagIn_1" operand has the signal state "1". When the time has expired or is reset, the "TagOut" operand is reset to "0". See also Overview of the valid data types (Page 1204) S_PEXT: Assign extended pulse timer parameters and start Description The "Assign extended pulse timer parameters and start" instruction starts a programmed timer when a transition from "0" to "1" (positive signal edge) is detected in the result of logic operation (RLO) at input S. The timer expires with the programmed duration (TV), even if the signal state at input S changes to "0". As long as the timer is running, output Q has the signal state "1". When the timer has expired, output Q is reset to "0". If the signal state at input S changes from "0" to "1" while the timer is running, the timer is restarted with the duration programmed at input TV. The duration is made up internally of a time value and a time base and is programmed at parameter TV. When the instruction is started, the programmed time value is counted down to zero. The time base determines the time period of the time value. The current time value is output binary-coded at output BI and BCD-coded at output BCD. If the timer is running and the signal state at input R changes to "1", the current time value and the time base are also set to zero. If the timer is not running, the signal state "1" at the R input has no effect. The "Assign extended pulse timer parameters and start" instruction needs a preceding logic operation for the edge evaluation and can be placed within or at the end of the network. The instruction data is updated with each access. It can therefore happen that the query of the data at the start of the cycle returns different values than at the end of the cycle. Note In the time cell, the operating system reduces the time value in an interval specified by the time base by one unit until the value equals "0". The decrementation is performed asynchronously to the user program. The resulting timer is therefore at maximum up to one time interval shorter than the desired time base. You can find an example of how a time cell can be formed under: See also "L: Load timer value". 2062 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameters The following table shows the parameters of the "Assign extended pulse timer parameters and start" instruction: Parameter Declaration Data type Memory area Description <Timer> InOut/Input TIMER T Time of the instruction The number of timers depends on the CPU. S Input BOOL I, Q, M, T, C, D, L, P Start input TV Input S5TIME, WORD I, Q, M, D, L or constant Time duration R Input BOOL I, Q, M, T, C, D, L, P or constant Reset input BI Output WORD I, Q, M, D, L, P Current time value (binary-coded) BCD Output WORD I, Q, M, D, L, P Current time value (BCD format) Q Output BOOL I, Q, M, D, L, P Status of the timer For additional information on valid data types, refer to "See also". WinCC Basic V13.0 System Manual, 02/2014 2063 Programming the PLC 9.7 References Pulse timing diagram The following figure shows the pulse timing diagram of the "Assign extended pulse timer parameters and start" instruction: W W W 5/2DWLQSXW6 5/2DWLQSXW5 7LPHUUXQQLQJ 4XHU\ 4XHU\ W SURJUDPPHGWLPH Example The following example shows how the instruction works: 7LPHUB 6B3(;7 7DJ,QB 7DJ,QB1XPEHU 6 79 %, 7DJ9DOXHB %&' 7DJ9DOXHB 7DJ2XW 7DJ,QB 5 4 "Timer_1" starts when the signal state of the "TagIn_1" operand changes from "0" to "1". The timer runs for the time value of the "TagIn_Number" operand without being affected by a negative edge at the S input. If the signal state at the "TagIn_1" operand changes from "0" to "1" before the timer expires, the timer is restarted. The "TagOut" operand has the signal state "1" as long as the timer is running. When the time has expired or is reset, the "TagOut" operand is reset to "0". 2064 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References See also Overview of the valid data types (Page 1204) S_ODT: Assign on-delay timer parameters and start Description The "Assign on-delay timer parameters and start" instruction starts a programmed timer when a transition from "0" to "1" (positive signal edge) is detected in the result of logic operation (RLO) at input S. The timer expires with the programmed duration (TV) as long as the signal state at input S is "1". If the timer expires correctly and input S still has signal state "1", output Q returns signal state "1". If the signal state at input S changes from "1" to "0" while the timer is running, the timer is stopped. In this case, output Q is reset to signal state "0". The duration is made up internally of a time value and a time base and is programmed at parameter TV. When the instruction is started, the programmed time value is counted down to zero. The time base determines the time period of the time value. The current time value is output binary-coded at output BI and BCD-coded at output BCD. If the time is running and the signal state at input R changes from "0" to "1", the current time value and the time base are also set to zero. In this case, the signal state at output Q is "0". The timer is reset if the signal state is "1" at the R input even if the timer is not running and the RLO at input S is "1". The "Assign on-delay timer parameters and start" instruction needs a preceding logic operation for the edge evaluation and can be placed within or at the end of the network. The instruction data is updated with each access. It can therefore happen that the query of the data at the start of the cycle returns different values than at the end of the cycle. Note In the time cell, the operating system reduces the time value in an interval specified by the time base by one unit until the value equals "0". The decrementation is performed asynchronously to the user program. The resulting timer is therefore at maximum up to one time interval shorter than the desired time base. You can find an example of how a time cell can be formed under: See also "L: Load timer value". WinCC Basic V13.0 System Manual, 02/2014 2065 Programming the PLC 9.7 References Parameters The following table shows the parameters of the "Assign on-delay timer parameters and start" instruction: Parameter Declaration Data type Memory area Description <Timer> InOut/Input TIMER T Time of the instruction The number of timers depends on the CPU. S Input BOOL I, Q, M, T, C, D, L, P Start input TV Input S5TIME, WORD I, Q, M, D, L or constant Time duration R Input BOOL I, Q, M, T, C, D, L, P or constant Reset input BI Output WORD I, Q, M, D, L, P Current time value (binary-coded) BCD Output WORD I, Q, M, D, L, P Current time value (BCD format) Q Output BOOL I, Q, M, D, L, P Status of the timer For additional information on valid data types, refer to "See also". 2066 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Pulse timing diagram The following figure shows the pulse timing diagram of the "Assign on-delay timer parameters and start" instruction: W W W 5/2DWLQSXW6 5/2DWLQSXW5 7LPHUUXQQLQJ 4XHU\ 4XHU\ W SURJUDPPHGWLPH Example The following example shows how the instruction works: 7LPHUB 6B2'7 7DJ,QB 7DJ,QB1XPEHU 6 79 %, 7DJ9DOXHB %&' 7DJ9DOXHB 7DJ2XW 7DJ,QB 5 4 "Timer_1" starts when the signal state of the "TagIn_1" operand changes from "0" to "1". The timer expires with the value of operand "TagIn_Number". If the timer expires and the signal state of the operand is "1", the "TagOut" operand is set to "1". If the signal state at the "TagIn_1" operand changes from "1" to "0" before the timer expires, the timer is stopped. The "TagOut" operand has the signal state "0". WinCC Basic V13.0 System Manual, 02/2014 2067 Programming the PLC 9.7 References See also Overview of the valid data types (Page 1204) S_ODTS: Assign retentive on-delay timer parameters and start Description The "Assign retentive on-delay timer parameters and start" instruction starts a programmed timer when a transition from "0" to "1" (positive signal edge) is detected in the result of logic operation (RLO) at input S. The timer expires with the programmed duration (TV), even if the signal state at input S changes to "0". If the timer expires, the "Q" output returns signal state "1" regardless of the signal state at input "S". If the signal state at input S changes from "0" to "1" while the timer is running, the timer is restarted with the duration programmed at input (TV). The duration is made up internally of a time value and a time base and is programmed at parameter TV. When the instruction is started, the programmed time value is counted down to zero. The time base determines the time period of the time value. The current time value is output binary-coded at output BI and BCD-coded at output BCD. Signal state "1" at input R resets the current time value and time base to "0" regardless of the signal state at start input S. In this case, the signal state at output Q is "0". The "Assign retentive on-delay timer parameters and start" instruction needs a preceding logic operation for the edge evaluation and can be placed within or at the end of the network. The instruction data is updated with each access. It can therefore happen that the query of the data at the start of the cycle returns different values than at the end of the cycle. Note In the time cell, the operating system reduces the time value in an interval specified by the time base by one unit until the value equals "0". The decrementation is performed asynchronously to the user program. The resulting timer is therefore at maximum up to one time interval shorter than the desired time base. You can find an example of how a time cell can be formed under: See also "L: Load timer value". 2068 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameters The following table shows the parameters of the "Assign retentive on-delay timer parameters and start" instruction: Parameter Declaration Data type Memory area Description <Timer> InOut/Input TIMER T Time of the instruction The number of timers depends on the CPU. S Input BOOL I, Q, M, T, C, D, L, P Start input TV Input S5TIME, WORD I, Q, M, D, L or constant Time duration R Input BOOL I, Q, M, T, C, D, L, P or constant Reset input BI Output WORD I, Q, M, D, L, P Current time value (binary-coded) BCD Output WORD I, Q, M, D, L, P Current time value (BCD format) Q Output BOOL I, Q, M, D, L, P Status of the timer For additional information on valid data types, refer to "See also". Pulse timing diagram The following figure shows the pulse timing diagram of the "Assign retentive on-delay timer parameters and start" instruction: W W W 5/2DWLQSXW6 5/2DWLQSXW5 7LPHUUXQQLQJ 4XHU\ 4XHU\ W SURJUDPPHGWLPH WinCC Basic V13.0 System Manual, 02/2014 2069 Programming the PLC 9.7 References Example The following example shows how the instruction works: 7LPHUB 6B2'76 7DJ,QB 7DJ,QB1XPEHU 6 79 %, 7DJ9DOXHB %&' 7DJ9DOXHB 7DJ2XW 7DJ,QB 5 4 "Timer_1" starts when the signal state of the "TagIn_1" operand changes from "0" to "1". The timer expires with the time value of the "TagIn_Number" operand, even when the signal state of the "TagIn_1" operand changes to "0". When the time expires, the "TagOut" operand is reset to "1". If the signal state at the "TagIn_1" operand changes from "0" to "1" while the timer is running, the timer is restarted. See also Overview of the valid data types (Page 1204) S_OFFDT: Assign off-delay timer parameters and start Description The "Assign off-delay timer parameters and start" instruction starts a programmed timer when a transition from "1" to "0" (negative signal edge) is detected in the result of logic operation (RLO) at input S. The timer expires with the programmed duration (TV). As long as the timer is running or input S returns signal state "1", output Q has signal state "1". If the timer expires and the signal state is "0", output Q is reset to signal state "0". If the signal state at input S changes from "0" to "1" while the timer is running, the timer is stopped. The timer is only restarted after a falling signal edge is detected at input S. The duration is made up internally of a time value and a time base and is programmed at parameter TV. When the instruction is started, the programmed time value is counted down to zero. The time base determines the time period of the time value. The current time value is output binary-coded at output BI and BCD-coded at output BCD. Signal state "1" at input R resets the current time value and time base to "0". In this case, the signal state at output Q is "0". The "Assign off-delay timer parameters and start" instruction needs a preceding logic operation for the edge evaluation and can be placed within or at the end of the network. 2070 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References The instruction data is updated with each access. It can therefore happen that the query of the data at the start of the cycle returns different values than at the end of the cycle. Note In the time cell, the operating system reduces the time value in an interval specified by the time base by one unit until the value equals "0". The decrementation is performed asynchronously to the user program. The resulting timer is therefore at maximum up to one time interval shorter than the desired time base. You can find an example of how a time cell can be formed under: See also "L: Load timer value". Parameters The following table shows the parameters of the "Assign off-delay timer parameters and start" instruction: Parameter Declaration Data type Memory area Description <Timer> InOut/Input TIMER T Time of the instruction The number of timers depends on the CPU. S Input BOOL I, Q, M, T, C, D, L, P Start input TV Input S5TIME, WORD I, Q, M, D, L or constant Time duration R Input BOOL I, Q, M, T, C, D, L, P or constant Reset input BI Output WORD I, Q, M, D, L, P Current time value (binary-coded) BCD Output WORD I, Q, M, D, L, P Current time value (BCD format) Q Output BOOL I, Q, M, D, L, P Status of the timer For additional information on valid data types, refer to "See also". WinCC Basic V13.0 System Manual, 02/2014 2071 Programming the PLC 9.7 References Pulse timing diagram The following figure shows the pulse timing diagram of the "Assign off-delay timer parameters and start" instruction: W W W W 5/2DWLQSXW6 5/2DWLQSXW5 7LPHUUXQQLQJ 4XHU\ 4XHU\ W SURJUDPPHGWLPH Example The following example shows how the instruction works: 7LPHUB 6B2))'7 7DJ,QB 7DJ,QB1XPEHU 6 79 %, 7DJ9DOXHB %&' 7DJ9DOXHB 7DJ2XW 7DJ,QB 5 4 "Timer_1" starts when the signal state of the "TagIn_1" operand changes from "1" to "0". The timer expires with the value of operand "TagIn_Number". The "TagOut" operand is set to "1" if the timer is running or the "TagIn_1" operand has the signal state "0". If the signal state at the "TagIn_1" operand changes from "0" to "1" while the timer is running, the timer is reset. See also Overview of the valid data types (Page 1204) 2072 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References SP: Start pulse timer Description The instruction "Start pulse timer" starts a programmed timer when a change from "0" to "1" (positive signal edge) is detected in the result of logic operation (RLO) at the start input. The timer runs with the specified duration as long as the RLO has the signal state "1". As long as the timer is running, the query of timer status "1" returns the signal state "1". If there is a change from "1" to "0" in the RLO before the time value has elapsed, the timer stops. In this case, the query for timer status for "1" returns the signal state "0". The duration is made up internally of a time value and a time base and is programmed at parameter TV. When the instruction is started, the programmed time value is counted down to zero. The time base determines the time period of the time value. The "Start pulse timer" instruction needs a preceding logic operation for the edge evaluation and can only be placed on the right edge of the network. Note In the time cell, the operating system reduces the time value in an interval specified by the time base by one unit until the value equals "0". The decrementation is performed asynchronously to the user program. The resulting timer is therefore at maximum up to one time interval shorter than the desired time base. You can find an example of how a time cell can be formed under: See also "L: Load timer value". Parameters The following table shows the parameters of the instruction "Start pulse timer": Parameter Declaration Data type Memory area Description <Operand> Input BOOL I, Q, M, T, C, D, L, P Start input TV Input S5TIME, WORD I, Q, M, D, L or constant Time duration <Timer> InOut/Input TIMER T Timer which is started. The number of timers depends on the CPU. For additional information on valid data types, refer to "See also". WinCC Basic V13.0 System Manual, 02/2014 2073 Programming the PLC 9.7 References Example The following example shows how the instruction works: 1HWZRUN 7LPHUB 63 7DJ,QB 7DJ,QB1XPEHU 79 1HWZRUN 7DJ2XW 7LPHUB 1HWZRUN 7LPHUB 7DJ,QB 5 "Timer_1" starts when the signal state of the "TagIn_1" operand changes from "0" to "1". The timer expires with the time value of the "TagIn_Number" operand as long as the signal state of the "TagIn_1" operand is "1". If the signal state at the "TagIn_1" operand changes from "1" to "0" before the timer expires, the timer is stopped. As long as the timer is running, the "TagOut" operand returns signal state "1". If the signal state of the "TagIn_1" operand changes from "0" to "1", the timer is reset, i.e. the timer is stopped and the current time value is set to "0". See also Overview of the valid data types (Page 1204) SE: Start extended pulse timer Description The "Start extended pulse timer" instruction starts a programmed timer when a change from "0" to "1" (positive signal edge) is detected in the result of logic operation (RLO) at the start input. The timer runs for the specified time period even when the RLO changes to signal state "0". As long as the timer is running, the query of timer status "1" returns the signal state "1". If the RLO changes from "0" to "1" while the timer is running, the timer is restarted with the programmed time period. When the timer expires, the query for timer status for "1" returns the signal state "0". The duration is made up internally of a time value and a time base and is programmed at parameter TV. When the instruction is started, the programmed time value is counted down to zero. The time base determines the time period of the time value. 2074 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References The "Start extended pulse timer" instruction needs a preceding logic operation for the edge evaluation and can only be placed on the right edge of the network. Note In the time cell, the operating system reduces the time value in an interval specified by the time base by one unit until the value equals "0". The decrementation is performed asynchronously to the user program. The resulting timer is therefore at maximum up to one time interval shorter than the desired time base. You can find an example of how a time cell can be formed under: See also "L: Load timer value". Parameters The following table shows the parameters of the instruction "Start extended pulse timer": Parameter Declaration Data type Memory area Description <Operand> Input BOOL I, Q, M, T, C, D, L, P Start input TV Input S5TIME, WORD I, Q, M, D, L or constant Time duration <Timer> InOut/Input TIMER T Timer which is started. The number of timers depends on the CPU. For additional information on valid data types, refer to "See also". WinCC Basic V13.0 System Manual, 02/2014 2075 Programming the PLC 9.7 References Example The following example shows how the instruction works: 1HWZRUN 7LPHUB 6( 7DJ,QB 7DJ,QB1XPEHU 79 1HWZRUN 7DJ2XW 7LPHUB 1HWZRUN 7LPHUB 7DJ,QB 5 "Timer_1" starts when the signal state of the "TagIn_1" operand changes from "0" to "1". The timer expires with the time value of the "TagIn_Number" operand without being affected by a negative edge at the RLO. As long as the timer is running, the "TagOut" operand returns signal state "1". If the signal state at the "TagIn_1" operand changes from "0" to "1" before the timer expires, the timer is restarted. See also Overview of the valid data types (Page 1204) SD: Start on-delay timer Description The "Start on-delay timer" instruction starts a programmed timer when a change from "0" to "1" (positive signal edge) is detected in the result of logic operation (RLO) at the start input. The timer runs for the specified period of time as long as the RLO is "1". If the timer expires and the RLO has the signal state "1", the query timer status "1" returns the signal state "1". If the RLO changes from "1" to "0" while the timer is running, the timer is stopped. In this case, querying the timer status for "1" returns the signal state "0". The duration is made up internally of a time value and a time base and is programmed at parameter TV. When the instruction is started, the programmed time value is counted down to zero. The time base determines the time period of the time value. 2076 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References The "Start on-delay timer" instruction needs a preceding logic operation for the edge evaluation and can only be placed on the right edge of the network. Note In the time cell, the operating system reduces the time value in an interval specified by the time base by one unit until the value equals "0". The decrementation is performed asynchronously to the user program. The resulting timer is therefore at maximum up to one time interval shorter than the desired time base. You can find an example of how a time cell can be formed under: See also "L: Load timer value". Parameters The following table shows the parameters of the instruction "Start on-delay timer": Parameter Declaration Data type Memory area Description <Operand> Input BOOL I, Q, M, T, C, D, L, P Start input TV Input S5TIME, WORD I, Q, M, D, L or constant Time duration <Timer> InOut/Input TIMER T Timer which is started. The number of timers depends on the CPU. For additional information on valid data types, refer to "See also". WinCC Basic V13.0 System Manual, 02/2014 2077 Programming the PLC 9.7 References Example The following example shows how the instruction works: 1HWZRUN 7LPHUB 6' 7DJ,QB 7DJ,QB1XPEHU 79 1HWZRUN 7DJ2XW 7LPHUB 1HWZRUN 7LPHUB 7DJ,QB 5 "Timer_1" starts when the signal state of the "TagIn_1" operand changes from "0" to "1". The timer expires with the value of operand "TagIn_Number". If the timer expires and the RLO has the signal state "1", the "TagOut" operand is set to "1". If the signal state at the "TagIn_1" operand changes from "1" to "0" before the timer expires, the timer is stopped. If the signal state of the "TagIn_2" operand changes to "1", "Timer_1" is reset, i.e. the timer is stopped and the current time value is set to "0". See also Overview of the valid data types (Page 1204) SS: Start retentive on-delay timer Description The "Start retentive on-delay timer" instruction starts a programmed timer when a change from "0" to "1" (positive signal edge) is detected in the result of logic operation (RLO) at the start input. The timer runs for the specified time period even when the RLO changes to signal state "0". When the timer expires, the query for timer status for "1" returns the signal state "1". When the timer expires, the timer can only be restarted if it is explicitly reset. The duration is made up internally of a time value and a time base and is programmed at parameter TV. When the instruction is started, the programmed time value is counted down to zero. The time base determines the time period of the time value. 2078 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References The "Start retentive on-delay timer" instruction needs a preceding logic operation for the edge evaluation and can only be placed on the right edge of the network. Note In the time cell, the operating system reduces the time value in an interval specified by the time base by one unit until the value equals "0". The decrementation is performed asynchronously to the user program. The resulting timer is therefore at maximum up to one time interval shorter than the desired time base. You can find an example of how a time cell can be formed under: See also "L: Load timer value". Parameters The following table shows the parameters of the instruction "Start retentive on-delay timer": Parameter Declaration Data type Memory area Description <Operand> Input BOOL I, Q, M, T, C, D, L, P Start input TV Input S5TIME, WORD I, Q, M, D, L or constant Time duration <Timer> InOut/Input TIMER T Timer which is started. The number of timers depends on the CPU. For additional information on valid data types, refer to "See also". WinCC Basic V13.0 System Manual, 02/2014 2079 Programming the PLC 9.7 References Example The following example shows how the instruction works: 1HWZRUN 7LPHUB 66 7DJ,QB 7DJ,QB1XPEHU 79 1HWZRUN 7DJ2XW 7LPHUB 1HWZRUN 7LPHUB 7DJ,QB 5 "Timer_1" starts when the signal state of the "TagIn_1" operand changes from "0" to "1". The timer expires with the value of operand "TagIn_Number". When the time expires, the "TagOut" operand is reset to "1". If the signal state at the "TagIn_1" operand changes from "0" to "1" while the timer is running, the timer is restarted. If the signal state of the "TagIn_2" operand changes to "1", "Timer_1" is reset, i.e. the timer is stopped and the current time value is set to "0". See also Overview of the valid data types (Page 1204) SF: Start off-delay timer Description The "Start off-delay timer" instruction starts a programmed timer when a change from "1" to "0" (negative signal edge) is detected in the result of logic operation (RLO) at the start input. The timer runs for the specified time period. As long as the timer is running, the query of timer status "1" returns the signal state "1". If the RLO changes from "0" to "1" while the timer is running, the timer is reset. The timer is always restarted when the RLO changes from "1" to "0". The duration is made up internally of a time value and a time base and is programmed at parameter TV. When the instruction is started, the programmed time value is counted down to zero. The time base determines the time period of the time value. 2080 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References The "Start off-delay timer" instruction needs a preceding logic operation for the edge evaluation and can only be placed on the right edge of the network. Note In the time cell, the operating system reduces the time value in an interval specified by the time base by one unit until the value equals "0". The decrementation is performed asynchronously to the user program. The resulting timer is therefore at maximum up to one time interval shorter than the desired time base. You can find an example of how a time cell can be formed under: See also "L: Load timer value". Parameters The following table shows the parameters of the instruction "Start off-delay timer": Parameter Declaration Data type Memory area Description <Operand> Input BOOL I, Q, M, T, C, D, L, P Start input TV Input S5TIME, WORD I, Q, M, D, L or constant Time duration <Timer> InOut/Input TIMER T Timer which is started. The number of timers depends on the CPU. For additional information on valid data types, refer to "See also". WinCC Basic V13.0 System Manual, 02/2014 2081 Programming the PLC 9.7 References Example The following example shows how the instruction works: 1HWZRUN 7LPHUB 6) 7DJ,QB 7DJ,QB1XPEHU 79 1HWZRUN 7DJ2XW 7LPHUB 1HWZRUN 7LPHUB 7DJ,QB 5 "Timer_1" starts when the signal state of the "TagIn_1" operand changes from "1" to "0". The timer expires with the value of operand "TagIn_Number". As long as the timer is running, the "TagOut" operand is set to "1". If the signal state at the "TagIn_1" operand changes from "1" to "0" while the timer is running, the timer is restarted. If the signal state of the "TagIn_2" operand changes to "1", "Timer_1" is reset, i.e. the timer is stopped and the current time value is set to "0". See also Overview of the valid data types (Page 1204) Counter operations IEC Counters CTU: Count up Description You can use the "Count up" instruction to increment the value at output CV. When the signal state at the CU input changes from "0" to "1" (positive signal edge), the instruction is executed and the current counter value at the CV output is incremented by one. When the instruction executes for the first time, the current counter value at the CV output is set to zero. The counter is incremented each time a positive signal edge is detected, until it reaches the high limit for 2082 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References the specified data type at output CV. When the high limit is reached, the signal state at the CU input no longer has an effect on the instruction. You can scan the counter status at the Q output. The signal state at the Q output is determined by the PV parameter. If the current counter value is greater than or equal to the value of the PV parameter, the Q output is set to signal state "1". In all other cases, the Q output has signal state "0". You can also specify a constant for the PV parameter. The value at the CV output is reset to "0" and saved to an edge memory bit when the signal state at input R changes to "1". As long as the R input has the signal state "1", the signal state at the CU input has no effect on the instruction. Note Only use a counter at a single point in the program to avoid the risk of counting errors. Each call of the "Count up" instruction must be assigned an IEC counter in which the instruction data is stored. An IEC counter is a structure with one of the following data types: For S7-1200 CPU Data block of system data type IEC_<Counter> (Shared DB) Local tag IEC_SCOUNTER / IEC_USCOUNTER CTU_SINT / CTU_USINT IEC_COUNTER / IEC_UCOUNTER CTU_INT / CTU_UINT IEC_DCOUNTER / IEC_UDCOUNTER CTU_DINT / CTU_UDINT IEC_SCOUNTER / IEC_USCOUNTER IEC_COUNTER / IEC_UCOUNTER IEC_DCOUNTER / IEC_UDCOUNTER For S7-1500 CPU Data block of system data type IEC_<Counter> (Shared DB) Local tag IEC_SCOUNTER / IEC_USCOUNTER CTU_SINT / CTU_USINT IEC_COUNTER / IEC_UCOUNTER CTU_INT / CTU_UINT IEC_DCOUNTER / IEC_UDCOUNTER CTU_DINT / CTU_UDINT IEC_LCOUNTER / IEC_ULCOUNTER CTU_LINT / CTU_ULINT IEC_SCOUNTER / IEC_USCOUNTER IEC_COUNTER / IEC_UCOUNTER IEC_DCOUNTER / IEC_UDCOUNTER IEC_LCOUNTER / IEC_ULCOUNTER You can declare an IEC counter as follows: WinCC Basic V13.0 System Manual, 02/2014 2083 Programming the PLC 9.7 References Declaration of a data block of system data type IEC_<Counter> (for example, "MyIEC_COUNTER") Declaration as a local tag of the type CTU_<Data type> or IEC_<Counter> in the "Static" section of a block (for example #MyIEC_COUNTER) When you insert the instruction in the program, the "Call options" dialog opens in which you can specify whether the IEC counter is stored in its own data block (single instance) or as a local tag (multiple instance) in the block interface. If you create a separate data block, it is saved to the "Program resources" folder in the "Program blocks > System blocks" path of the project tree. For additional information on this topic, refer to "See also". When you set up the IEC counter in a separate data block (single instance), the instance data block is created by default with "optimized block access" and the individual tags are defined as retentive. For additional information on setting retentivity in an instance data block, refer to "See also". When you set up the IEC counter as local tag (multiple instance) in a function block with "optimized block access", it is defined as retentive in the block interface. The execution of the "Count up" instruction requires a preceding logic operation. It can be placed within or at the end of the network. Parameters The following table shows the parameters of the "Count up" instruction: Parameters Declaration Data type Memory area Description S7-1200 S7-1500 I, Q, M, D, L or constant CU Input BOOL I, Q, M, D, L or constant Count input R Input BOOL I, Q, M, D, L, I, Q, M, T, C, D, Reset input P or constant L, P or constant PV Input Integers I, Q, M, D, L, I, Q, M, D, L, P P or constant or constant Value at which the output Q is set. Q Output BOOL I, Q, M, D, L I, Q, M, D, L Counter status CV Output Integers, CHAR, DATE I, Q, M, D, L, P I, Q, M, D, L, P Current counter value You can select the data type of the instruction from the "<???>" drop-down list of the instruction box. For additional information on valid data types, refer to "See also". 2084 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Example The following example shows how the instruction works: &78B'% &78 ,17 7DJ,QB &8 7DJ,QB 5 7DJB39 39 &9 7DJB&9 4 7DJ2XW When the signal state of the "TagIn_1" operand changes from "0" to "1", the "Count up" instruction executes and the current counter value of the "Tag_CV" operand is incremented by one. With each additional positive signal edge, the counter value is incremented until the high limit of the specified data type (INT = 32767) is reached. The value of the PV parameter is adopted as the limit for determining the "TagOut" output. The "TagOut" output has signal state "1" as long as the current counter value is greater than or equal to the value of the "Tag_PV" operand. In all other cases, the "TagOut" output returns the signal state "0". See also Overview of the valid data types (Page 1204) Setting retentivity in an instance data block (Page 1536) Setting the retentivity of local tags (Page 1391) CTD: Count down Description You can use the "Count down" instruction to decrement the value at output CV. When the signal state at the CD input changes from "0" to "1" (positive signal edge), the instruction is executed and the current counter value at the CV output is decremented by one. When the instruction is executed the first time, the counter value of the CV parameter is set to the value of the PV parameter. Each time a positive signal edge is detected, the counter value is decremented until it reaches the low limit of the specified data type. When the low limit is reached, the signal state at the CD input no longer has an effect on the instruction. You can scan the counter status at the Q output. If the current counter value is less than or equal to "0", the Q output is set to signal state "1". In all other cases, the Q output has signal state "0". You can also specify a constant for the PV parameter. WinCC Basic V13.0 System Manual, 02/2014 2085 Programming the PLC 9.7 References The value at the CV output is set to the value of the PV parameter and saved to a edge memory bit when the signal state at the LD input changes from "0" to "1". As long as the LD input has the signal state "1", the signal state at the CD input has no effect on the instruction. Note Only use a counter at a single point in the program to avoid the risk of counting errors. Each call of the "Count down" instruction must be assigned an IEC counter in which the instruction data is stored. An IEC counter is a structure with one of the following data types: For S7-1200 CPU Data block of system data type IEC_<Counter> (Shared DB) Local tag IEC_SCOUNTER / IEC_USCOUNTER CTD_SINT / CTD_USINT IEC_COUNTER / IEC_UCOUNTER CTD_INT / CTD_UINT IEC_DCOUNTER / IEC_UDCOUNTER CTD_DINT / CTD_UDINT IEC_SCOUNTER / IEC_USCOUNTER IEC_COUNTER / IEC_UCOUNTER IEC_DCOUNTER / IEC_UDCOUNTER For S7-1500 CPU Data block of system data type IEC_<Counter> (Shared DB) Local tag IEC_SCOUNTER / IEC_USCOUNTER CTD_SINT / CTD_USINT IEC_COUNTER / IEC_UCOUNTER CTD_INT / CTD_UINT IEC_DCOUNTER / IEC_UDCOUNTER CTD_DINT / CTD_UDINT IEC_LCOUNTER / IEC_ULCOUNTER CTD_LINT / CTD_ULINT IEC_SCOUNTER / IEC_USCOUNTER IEC_COUNTER / IEC_UCOUNTER IEC_DCOUNTER / IEC_UDCOUNTER IEC_LCOUNTER / IEC_ULCOUNTER You can declare an IEC counter as follows: Declaration of a data block of system data type IEC_<Counter> (for example, "MyIEC_COUNTER") Declaration as a local tag of the type CTD_<Data type> or IEC_<Counter> in the "Static" section of a block (for example #MyIEC_COUNTER) When you insert the instruction in the program, the "Call options" dialog opens in which you can specify whether the IEC counter is stored in its own data block (single instance) or as a local tag (multiple instance) in the block interface. If you create a separate data block, it is saved to the "Program resources" folder in the "Program blocks > System blocks" path of the project tree. For additional information on this topic, refer to "See also". 2086 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References When you set up the IEC counter in a separate data block (single instance), the instance data block is created by default with "optimized block access" and the individual tags are defined as retentive. For additional information on setting retentivity in an instance data block, refer to "See also". When you set up the IEC counter as local tag (multiple instance) in a function block with "optimized block access", it is defined as retentive in the block interface. The execution of the "Count down" instruction requires a preceding logic operation. It can be placed within or at the end of the network. Parameters The following table shows the parameters of the "Count down" instruction: Parameters Declaration Data type Memory area S7-1200 S7-1500 I, Q, M, D, L or constant Description CD Input BOOL I, Q, M, D, L or constant Count input LD Input BOOL I, Q, M, D, L, I, Q, M, T, C, D, Load input P or constant L, P or constant PV Input Integers I, Q, M, D, L, I, Q, M, D, L, P P or constant or constant Q Output BOOL I, Q, M, D, L I, Q, M, D, L Counter status CV Output Integers, CHAR, DATE I, Q, M, D, L, P I, Q, M, D, L, P Current counter value Value at which the output Q is set. You can select the data type of the instruction from the "<???>" drop-down list of the instruction box. For additional information on valid data types, refer to "See also". Example The following example shows how the instruction works: &7'B'% &7' ,17 7DJ,QB &' 7DJ,QB /' &9 7DJB&9 7DJB39 39 4 7DJ2XW When the signal state of the "TagIn_1" operand changes from "0" to "1", the "Count down" instruction executes and the value at the "Tag_CV" output is decremented by one. With each additional positive signal edge, the counter value is decremented until the low limit of the specified data type (INT = -32768) is reached. WinCC Basic V13.0 System Manual, 02/2014 2087 Programming the PLC 9.7 References The value of the PV parameter is adopted as the limit for determining the "TagOut" output. The "TagOut" output has signal state "1" as long as the current counter value is less than or equal to "0". In all other cases, the "TagOut" output returns the signal state "0". See also Overview of the valid data types (Page 1204) Setting retentivity in an instance data block (Page 1536) Setting the retentivity of local tags (Page 1391) CTUD: Count up and down Description You can use the "Count up and down" instruction to increment and decrement the counter value at the CV output. If the signal state at the CU input changes from "0" to "1" (positive signal edge), the current counter value is incremented by one and stored at the CV output. If the signal state at the CD input changes from "0" to "1" (positive signal edge), the current counter value at the CV output is decremented by one. If there is a positive signal edge at the CU and CD inputs in one program cycle, the current counter value at the CV output remains unchanged. The counter value can be incremented until it reaches the high limit of the data type specified at the CV output. When the high limit is reached, the counter value is no longer incremented on a positive signal edge. When the low limit of the specified data type is reached, the counter value is not decremented any further. When the signal state at the LD input changes to "1", the counter value at the CV output is set to the value of the PV parameter and stored in a edge memory bit. As long as the LD input has the signal state "1", the signal state at the CU and CD inputs has no effect on the instruction. The counter value is set to "0" and stored in an edge memory bit when the signal state at input R changes to "1". As long as the R input has the signal state "1", a change in the signal state of the CU, CD and LD inputs has no effect on the "Count up and down" instruction. You can scan the current status of the up counter at the QU output. If the current counter value is greater than or equal to the value of the PV parameter, the QU output is set to signal state "1". In all other cases, the QU output has signal state "0". You can also specify a constant for the PV parameter. You can scan the current status of the down counter at the QD output. If the current counter value is less than or equal to zero, the QD output is set to signal state "1". In all other cases, the QD output has signal state "0". Note Only use a counter at a single point in the program to avoid the risk of counting errors. Each call of the "Count up and down" instruction must be assigned an IEC counter in which the instruction data is stored. An IEC counter is a structure with one of the following data types: 2088 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References For S7-1200 CPU Data block of system data type IEC_<Counter> (Shared DB) Local tag IEC_SCOUNTER / IEC_USCOUNTER CTUD_SINT / CTUD_USINT IEC_COUNTER / IEC_UCOUNTER CTUD_INT / CTUD_UINT IEC_DCOUNTER / IEC_UDCOUNTER CTUD_DINT / CTUD_UDINT IEC_SCOUNTER / IEC_USCOUNTER IEC_COUNTER / IEC_UCOUNTER IEC_DCOUNTER / IEC_UDCOUNTER For S7-1500 CPU Data block of system data type IEC_<Counter> (Shared DB) Local tag IEC_SCOUNTER / IEC_USCOUNTER CTUD_SINT / CTUD_USINT IEC_COUNTER / IEC_UCOUNTER CTUD_INT / CTUD_UINT IEC_DCOUNTER / IEC_UDCOUNTER CTUD_DINT / CTUD_UDINT IEC_LCOUNTER / IEC_ULCOUNTER CTUD_LINT / CTUD_ULINT IEC_SCOUNTER / IEC_USCOUNTER IEC_COUNTER / IEC_UCOUNTER IEC_DCOUNTER / IEC_UDCOUNTER IEC_LCOUNTER / IEC_ULCOUNTER You can declare an IEC counter as follows: Declaration of a data block of system data type IEC_<Counter> (for example, "MyIEC_COUNTER") Declaration as a local tag of the type CTUD_<Data type> or IEC_<Counter> in the "Static" section of a block (for example #MyIEC_COUNTER) When you insert the instruction in the program, the "Call options" dialog opens in which you can specify whether the IEC counter is stored in its own data block (single instance) or as a local tag (multiple instance) in the block interface. If you create a separate data block, it is saved to the "Program resources" folder in the "Program blocks > System blocks" path of the project tree. For additional information on this topic, refer to "See also". When you set up the IEC counter in a separate data block (single instance), the instance data block is created by default with "optimized block access" and the individual tags are defined as retentive. For additional information on setting retentivity in an instance data block, refer to "See also". When you set up the IEC counter as local tag (multiple instance) in a function block with "optimized block access", it is defined as retentive in the block interface. The execution of the "Count up and down" instruction requires a preceding logic operation. It can be placed within or at the end of the network. WinCC Basic V13.0 System Manual, 02/2014 2089 Programming the PLC 9.7 References Parameters The following table shows the parameters of the "Count up and down" instruction: Parameter Declaration Data type Memory area S7-1200 S7-1500 Description CU Input BOOL I, Q, M, D, L or constant I, Q, M, D, L or constant Count up input CD Input BOOL I, Q, M, D, L or constant I, Q, M, D, L or constant Count down input R Input BOOL I, Q, M, D, L, I, Q, M, T, C, D, Reset input P or constant L, P or constant LD Input BOOL I, Q, M, D, L, I, Q, M, T, C, D, Load input P or constant L, P or constant PV Input Integers I, Q, M, D, L, I, Q, M, D, L, P P or constant or constant Value at which the output QU is set. QU Output BOOL I, Q, M, D, L I, Q, M, D, L Up-counter status QD Output BOOL I, Q, M, D, L I, Q, M, D, L Down-counter status CV Output Integers, CHAR, DATE I, Q, M, D, L, P I, Q, M, D, L, P Current counter value You can select the data type of the instruction from the "<???>" drop-down list of the instruction box. For additional information on valid data types, refer to "See also". Example The following example shows how the instruction works: &78'B'% &78' ,17 7DJ,QB&8 &8 7DJ,QB&' &' 7DJ,QB5 5 4' 7DJ2XWB4' 7DJ,QB/' /' &9 7DJB&9 7DJB39 39 48 7DJ2XWB48 If the signal state at the "TagIn_CU" or "TagIn_CD" input changes from "0" to "1" (positive signal edge), the "Count up and down" instruction is executed. When there is a positive signal edge at the "TagIn_CU" input, the current counter value is incremented by one and stored at the "Tag_CV" output. When there is a positive signal edge at the "TagIn_CD" input, the counter value is decremented by one and stored at the "Tag_CV" output. When there is a positive edge 2090 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References at the CU input, the counter value is incremented until it reaches the high limit (INT = 32767). If input CD has a positive signal edge, the counter value is decremented until it reaches the low limit (INT = -32768). The "TagOut_GU" output has signal state "1" as long as the current counter value is greater than or equal to the value at the "Tag_PV" input. In all other cases, the "TagOut_QU" output returns the signal state "0". The "TagOut_QD" output has signal state "1" as long as the current counter value is less than or equal to "0". In all other cases, the "TagOut_QD" output has signal state "0". See also Overview of the valid data types (Page 1204) Example of detecting the fill level of a storage area (Page 1726) Setting retentivity in an instance data block (Page 1536) Setting the retentivity of local tags (Page 1391) SIMATIC counters S_CUD: Assign parameters and count up / down Description You can use the "Assign parameters and count up / down" instruction to increment or decrement the value of a counter. If the signal state at the CU input changes from "0" to "1" (positive signal edge), the current counter value is incremented by one. If the signal state at the CD input changes from "0" to "1" (positive signal edge), the counter value is decremented by one. The current counter value is output as a hexadecimal value at output CV and BCDcoded at output CV_BCD. If there is a positive signal edge at the CU and CD inputs in one program cycle, the counter value remains unchanged. The counter value is incremented until the high limit of "999" is reached. When the high limit value is reached, the counter value is no longer incremented on a positive signal edge. When the low limit of "0" is reached, the counter value is no longer decremented. When the signal state at input S changes from "0" to "1", the counter value is set to the value of the PV parameter. If the counter is set and if RLO is "1" at the inputs CU and CD, the counter counts accordingly in the next scan cycle, even if no change in the signal edge is detected. The counter value is set to zero when the signal state at the R input changes to "1". As long as the R input has the signal state "1", processing of the signal state of the CU, CD and S inputs has no effect on the counter value. The signal state at output Q is "1" if the counter value is greater than zero. If the counter value is equal to zero, output Q has the signal state "0". Note Only use a counter at a single point in the program to avoid the risk of counting errors. WinCC Basic V13.0 System Manual, 02/2014 2091 Programming the PLC 9.7 References The "Assign parameters and count up / down" instruction needs a preceding logic operation for the edge evaluation and can be placed within or at the end of the network. Parameters The following table shows the parameters of the "Assign parameters and count up / down" instruction: Parameters Declaration Data type Memory area Description <Counter> InOut/Input COUNTER C Counter of the instruction The number of counters depends on the CPU. CU Input BOOL I, Q, M, D, L, T, C Count up input CD Input BOOL I, Q, M, D, L, T, C or constant Count down input S Input BOOL I, Q, M, D, L, T, C or constant Input for presetting counter PV Input WORD I, Q, M, D, L or constant Preset counter value (C#0 to C#999) R Input BOOL I, Q, M, D, L, T, C or constant Reset input CV Output WORD, S5TIME, DATE I, Q, M, D, L Current counter value (hexadecimal) CV_BCD Output WORD, S5TIME, DATE I, Q, M, D, L Current counter value (BCD format) Q Output BOOL I, Q, M, D, L Status of the counter For additional information on valid data types, refer to "See also". 2092 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Example The following example shows how the instruction works: &RXQWHUB 6B&8' 7DJ,QB &8 7DJ,QB &' 7DJ,QB 6 7DJ3UHVHW9DOXH 7DJ,QB 39 5 &9 7DJ9DOXHB &9B%&' 7DJ9DOXHB 7DJ2XW 4 If the signal state at the "TagIn_1" or "TagIn_2" input changes from "0" to "1" (positive signal edge), the "Assign parameters and count up / down" instruction is executed. When there is a positive signal edge at the "TagIn_1" input and the current counter value is less than "999", the counter value is incremented by one. When there is a positive signal edge at the "TagIn_2" input and the current counter value is greater than "0", the counter value is decremented by one. When the signal state at the "TagIn_3" input changes from "0" to "1", the counter value is set to the value of the "TagPresetValue" operand. The counter value is reset to "0" when the "TagIn_4" operand has signal state "1". The current counter value is hexadecimal in the "TagValue_1" operand and BCD-coded in the "TagValue_2" operand. The "TagOut" output has the signal state "1" as long as the current counter value is not equal to "0". See also Overview of the valid data types (Page 1204) S_CU: Assign parameters and count up Description You can use the "Assign parameters and count up" instruction to increment the value of a counter. If the signal state at the CU input changes from "0" to "1" (positive signal edge), the current counter value is incremented by one. The current counter value is output as a hexadecimal value at output CV and BCD-coded at output CV_BCD. The count is incremented until the limit of "999" is reached. When the limit is reached, the counter value is no longer incremented on a positive signal edge. When the signal state at input S changes from "0" to "1", the counter value is set to the value of the PV parameter. If the counter is set and if RLO at input CU is "1", the counter will count accordingly in the next scan cycle, even when no change has been detected in the signal edge. WinCC Basic V13.0 System Manual, 02/2014 2093 Programming the PLC 9.7 References The counter value is set to zero when the signal state at the R input changes to "1". As long as the R input has the signal state "1", processing of the signal state of the CU and S inputs has no effect on the counter value. The signal state at output Q is "1" if the counter value is greater than zero. If the counter value is equal to zero, output Q has the signal state "0". Note Only use a counter at a single point in the program to avoid the risk of counting errors. The "Assign parameters and count up" instruction needs a preceding logic operation for the edge evaluation and can be placed within or at the end of the network. Parameters The following table shows the parameters of the "Assign parameters and count up" instruction: Parameters Declaration Data type Memory area Description <Counter> InOut/Input COUNTER C Counter of the instruction The number of counters depends on the CPU. CU Input BOOL I, Q, M, D, L, T, C Count up input S Input BOOL I, Q, M, D, L, T, C or constant Input for presetting counter PV Input WORD I, Q, M, D, L or constant Preset counter value (C#0 to C#999) R Input BOOL I, Q, M, D, L, T, C or constant Reset input CV Output WORD, S5TIME, DATE I, Q, M, D, L Current counter value (hexadecimal) CV_BCD Output WORD, S5TIME, DATE I, Q, M, D, L Current counter value (BCD format) Q Output BOOL I, Q, M, D, L Status of the counter For additional information on valid data types, refer to "See also". 2094 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Example The following example shows how the instruction works: &RXQWHUB 6B&8 7DJ,QB &8 7DJ,QB 6 7DJ3UHVHW9DOXH 7DJ,QB 39 &9 7DJ9DOXHB &9B%&' 7DJ9DOXHB 5 7DJ2XW 4 When the signal state at the "TagIn_1" input changes from "0" to "1" (positive signal edge) and the current counter value is less than "999", the counter value is incremented by one. When the signal state at the "TagIn_2" input changes from "0" to "1", the counter value is set to the value of the "TagPresetValue" operand. The counter value is reset to "0" when the "TagIn_3" operand has signal state "1". The current counter value is hexadecimal in the "TagValue_1" operand and BCD-coded in the "TagValue_2" operand. The "TagOut" output has the signal state "1" as long as the current counter value is not equal to "0". See also Overview of the valid data types (Page 1204) S_CD: Assign parameters and count down Description You can use the "Assign parameters and count down" instruction to decrement the value of a counter. If the signal state at the CD input changes from "0" to "1" (positive signal edge), the counter value is decremented by one. The current counter value is output as a hexadecimal value at output CV and BCD-coded at output CV_BCD. The count is decremented until the low limit of "0" is reached. When the low limit is reached, the counter value is no longer decremented on a positive signal edge. When the signal state at input S changes from "0" to "1", the counter value is set to the value of the PV parameter. If the counter is set and if RLO at input CD is "1", the counter will count accordingly in the next scan cycle, even when no change has been detected in the signal edge. The counter value is set to zero when the signal state at the R input changes to "1". As long as the R input has the signal state "1", processing of the signal state of the CD and S inputs has no effect on the counter value. WinCC Basic V13.0 System Manual, 02/2014 2095 Programming the PLC 9.7 References The signal state at output Q is "1" if the counter value is greater than zero. If the counter value is equal to zero, output Q has the signal state "0". Note Only use a counter at a single point in the program to avoid the risk of counting errors. The "Assign parameters and count down" instruction needs a preceding logic operation for the edge evaluation and can be placed within or at the end of the network. Parameters The following table shows the parameters of the "Assign parameters and count down" instruction: Parameters Declaration Data type Memory area Description <Counter> InOut/Input COUNTER C Counter of the instruction The number of counters depends on the CPU. CD Input BOOL I, Q, M, D, L or constant Count down input S Input BOOL I, Q, M, D, L, T, C or constant Input for presetting counter PV Input WORD I, Q, M, D, L or constant Preset counter value (C#0 to C#999) R Input BOOL I, Q, M, D, L, T, C or constant Reset input CV Output WORD, S5TIME, DATE I, Q, M, D, L Current counter value (hexadecimal) CV_BCD Output WORD, S5TIME, DATE I, Q, M, D, L Current counter value (BCD format) Q Output BOOL I, Q, M, D, L Status of the counter For additional information on valid data types, refer to "See also". 2096 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Example The following example shows how the instruction works: &RXQWHUB 6B&' 7DJ,QB &' 7DJ,QB 6 7DJ3UHVHW9DOXH 7DJ,QB 39 5 &9 7DJ9DOXHB &9B%&' 7DJ9DOXHB 7DJ2XW 4 When the signal state at the "TagIn_1" input changes from "0" to "1" (positive signal edge) and the current counter value is greater than "0", the counter value is decremented by one. When the signal state at the "TagIn_2" input changes from "0" to "1", the counter value is set to the value of the "TagPresetValue" operand. The counter value is reset to "0" when the "TagIn_3" operand has signal state "1". The current counter value is hexadecimal in the "TagValue_1" operand and BCD-coded in the "TagValue_2" operand. The "TagOut" output has the signal state "1" as long as the current counter value is not equal to "0". See also Overview of the valid data types (Page 1204) SC: Set counter value Description You can use the "Set counter value" instruction to set the value of a counter. The instruction is executed when the result of logic operation (RLO) at the start input of the instruction changes from "0" to "1". When the instruction is executed, the counter is set to the specified counter value. The "Set counter value" instruction needs a preceding logic operation for the edge evaluation and can only be placed on the right edge of the network. WinCC Basic V13.0 System Manual, 02/2014 2097 Programming the PLC 9.7 References Parameters The following table lists the parameters of the "Set counter value" instruction: Parameters Declaration Data type Memory area Description <Operand> Input BOOL I, Q, M, T, C, D, L Start input CV Input WORD I, Q, M, D, L or constant Value with which the counter is preset in the BCD format. <Counter> InOut/Input COUNTER C (C#0 to C#999) Counter that is preset. For additional information on valid data types, refer to "See also". Example The following example shows how the instruction works: &RXQWHUB 7DJ,Q & 6& &9 the counter "Counter_1" starts with the value "100" when the signal state of the "TagIn" operand changes from "0" to "1". See also Overview of the valid data types (Page 1204) CU: Count up Description You use the "Count up" instruction to increment the value of the specified counter by the count of one on a rising edge at the start input. The count is incremented until the limit of "999" is reached. When the limit is reached, the counter value is no longer incremented on a positive signal edge. The "Count up" instruction needs a preceding logic operation for the edge evaluation and can only be placed on the right edge of the network. 2098 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameters The following table shows the parameters of the "Count up" instruction: Parameters Declaration Data type Memory area Description <Operand> Input BOOL I, Q, M, T, C, D, L Start input <Counter> InOut/Input COUNTER C Counter whose value is incremented. For additional information on valid data types, refer to "See also". Example The following example shows how the instruction works: 1HWZRUN &RXQWHUB 6& 7DJ,QB & 39 1HWZRUN &RXQWHUB 7DJ,QB &8 1HWZRUN &RXQWHUB 7DJ,QB 5 When the signal state of the operand "TagIn_1" changes from "0" to "1" (positive signal edge), the counter "Counter_1" is preset with the value "100". The value of "Counter_1" is incremented by the count of one when the signal state of the "TagIn_2" operand changes from "0" to "1". If the "TagIn_3" operand returns signal state "1", the value of "Counter_1" is reset to "0". See also Overview of the valid data types (Page 1204) WinCC Basic V13.0 System Manual, 02/2014 2099 Programming the PLC 9.7 References CD: Count down Description You use the "Count down" instruction to decrement the value of the specified counter by the count of one on a rising edge at the start input. The count is decremented until the limit of "0" is reached. When the limit is reached, the counter value is no longer changed on a positive signal edge. The "Count down" instruction needs a preceding logic operation for the edge evaluation and can only be placed on the right edge of the network. Parameters The following table shows the parameters of the "Count down" instruction: Parameters Declaration Data type Memory area Description <Operand> Input BOOL I, Q, M, T, C, D, L Start input <Counter> InOut/Input COUNTER C Counter whose value is decremented. For additional information on valid data types, refer to "See also". Example The following example shows how the instruction works: 1HWZRUN &RXQWHUB 6& 7DJ,QB & 39 1HWZRUN &RXQWHUB 7DJ,QB &' 1HWZRUN &RXQWHUB 7DJ,QB 5 When the signal state of the operand "TagIn_1" changes from "0" to "1" (positive signal edge), the counter "Counter_1" is preset with the value "100". 2100 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References The value of "Counter_1" is incremented by the count of one when the signal state of the "TagIn_2" operand changes from "0" to "1". If the "TagIn_3" operand returns signal state "1", the value of "Counter_1" is reset to "0". See also Overview of the valid data types (Page 1204) Comparator operations CMP ==: Equal Description You can use the "Equal" instruction to query whether the value at input IN1 is equal to the value at input IN2. If the condition of the comparison is fulfilled, the instruction returns the result of logic operation (RLO) "1". If the comparison condition is not fulfilled, the instruction returns RLO "0". The individual characters are compared by means of their code (for example, 'a' is greater than 'A') during the comparison of the strings. The comparison is performed from left to right. The first character to be different decides the result of the comparison. The following table lists examples of string comparisons: IN1 IN2 RLO of the instruction 'AA' 'AA' 1 'Hello World' 'HelloWorld' 0 'AA' 'aa' 0 The "Equal" instruction also compares individual characters of a string. The number of the character to be compared is specified in square brackets next to the operand name. "MyString[2]", for example, compares the second character of the "MyString" string. If IEC check is enabled, the operands to be compared must be of the same data type. If IEC check is not enabled, the width (length) of the operands must be the same. If the floating-point numbers are being compared, the operands to be compared must be of the same data type regardless of the IEC check setting. Note Comparison of floating-point numbers If you want to compare the data types REAL or LREAL, instead of the instruction "CMP ==: Equal", use the instruction "IN_RANGE: Value within range". WinCC Basic V13.0 System Manual, 02/2014 2101 Programming the PLC 9.7 References Note Comparison of the data type PORT To be able to compare the operands of the PORT data type with the "Equal" instruction, you need to select the WORD data type from the drop-down list of the instructions box. Parameters The following table lists the parameters of the "Equal" instruction: Parameter Declaration Data type S7-1200 S7-1500 Memory area Description IN1 Input Bit strings, integers, floating-point numbers, character strings, TIME, DATE, TOD, DTL Bit strings, integers, floating-point numbers, character strings, TIME, LTIME, DATE, TOD, LTOD, DTL, DT, LDT I, Q, M, D, L, P or constant First comparison value IN2 Input Bit strings, integers, floating-point numbers, character strings, TIME, DATE, TOD, DTL Bit strings, integers, floating-point numbers, character strings, TIME, LTIME, DATE, TOD, LTOD, DTL, DT, LDT I, Q, M, D, L, P or constant Second value to compare You can select the data type of the instruction from the "<???>" drop-down list of the instruction box. For additional information on valid data types, refer to "See also": Example The following example shows how the instruction works: ,17 7DJB9DOXH 7DJB9DOXH ,1 ,1 7DJ,QB 7DJ2XW 6 The "TagOut" output is set when the following conditions are fulfilled: The operand "TagIn_1" has the signal state "1". The condition of the comparison instruction is fulfilled if "Tag_Value1" = "Tag_Value2". 2102 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References See also Overview of the valid data types (Page 1204) CMP <>: Not equal Description You can use the "Not equal" instruction to query whether the value at input IN1 is not equal to the value at input IN2. If the condition of the comparison is fulfilled, the instruction returns the result of logic operation (RLO) "1". If the comparison condition is not fulfilled, the instruction returns RLO "0". The individual characters are compared by means of their code (for example, 'a' is greater than 'A') during the comparison of the strings. The comparison is performed from left to right. The first character to be different decides the result of the comparison. The following table lists examples of string comparisons: IN1 IN2 RLO of the instruction 'AA' 'aa' 1 'Hello World' 'HelloWorld' 1 'AA' 'AA' 0 The "Not equal" instruction also compares individual characters of a string. The number of the character to be compared is specified in square brackets next to the operand name. "MyString[2]", for example, compares the second character of the "MyString" string. If IEC check is enabled, the operands to be compared must be of the same data type. If IEC check is not enabled, the width (length) of the operands must be the same. If the floating-point numbers are being compared, the operands to be compared must be of the same data type regardless of the IEC check setting. Note Comparison of the data type PORT To be able to compare the operands of the PORT data type with the "Not equal" instruction, you need to select the WORD data type from the drop-down list of the instructions box. WinCC Basic V13.0 System Manual, 02/2014 2103 Programming the PLC 9.7 References Parameters The following table lists the parameters of the "Not equal" instruction: Parameters Declaration Data type S7-1200 S7-1500 Memory area Description IN1 Input Bit strings, integers, floating-point numbers, character strings, TIME, DATE, TOD, DTL Bit strings, integers, floating-point numbers, character strings, TIME, LTIME, DATE, TOD, LTOD, DTL, DT, LDT I, Q, M, D, L, P or constant First comparison value IN2 Input Bit strings, integers, floating-point numbers, character strings, TIME, DATE, TOD, DTL Bit strings, integers, floating-point numbers, character strings, TIME, LTIME, DATE, TOD, LTOD, DTL, DT, LDT I, Q, M, D, L, P or constant Second value to compare You can select the data type of the instruction from the "<???>" drop-down list of the instruction box. For additional information on valid data types, refer to "See also". Example The following example shows how the instruction works: ! ,17 7DJB9DOXH 7DJB9DOXH ,1 ,1 7DJ,QB 7DJ2XW 6 The "TagOut" output is set when the following conditions are fulfilled: The operand "TagIn_1" has the signal state "1". The condition of the comparison instruction is fulfilled if "Tag_Value1" <> "Tag_Value2". See also Overview of the valid data types (Page 1204) 2104 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References CMP >=: Greater or equal Description You can use the "Greater or equal" instruction to query whether the value at input IN1 is greater or equal to the value at input IN2. Both values to be compared must be of the same data type. If the condition of the comparison is fulfilled, the instruction returns the result of logic operation (RLO) "1". If the comparison condition is not fulfilled, the instruction returns RLO "0". The individual characters are compared by means of their code (for example, 'a' is greater than 'A') during the comparison of the strings. The comparison is performed from left to right. The first character to be different decides the result of the comparison. If the left part of the longer string is identical to the shorter string, the longer string is considered greater. The following table lists examples of string comparisons: IN1 IN2 RLO of the instruction 'BB' 'AA' 1 'AAA' 'AA' 1 'Hello World' 'Hello World' 1 'Hello World' 'HelloWorld' 0 'AA' 'aa' 0 'AAA' 'a' 0 The "Greater or equal" instruction also compares individual characters of a string. The number of the character to be compared is specified in square brackets next to the operand name. "MyString[2]", for example, compares the second character of the "MyString" string. In comparing timer values, the RLO of the instruction is "1" if the timer at input IN1 is greater (more recent) than or equal to the timer at input IN2. WinCC Basic V13.0 System Manual, 02/2014 2105 Programming the PLC 9.7 References Parameters The following table lists the parameters of the "Greater or equal" instruction: Parameters Declaration Data type S7-1200 S7-1500 Memory area Description IN1 Input Integers, floating-point numbers, character strings, TIME, DATE, TOD, DTL Integers, floating-point numbers, character strings, TIME, LTIME, DATE, TOD, LTOD, DTL, DT, LDT I, Q, M, D, L, P or constant First comparison value IN2 Input Integers, floating-point numbers, character strings, TIME, DATE, TOD, DTL Integers, floating-point numbers, character strings, TIME, LTIME, DATE, TOD, LTOD, DTL, DT, LDT I, Q, M, D, L, P or constant Second value to compare You can select the data type of the instruction from the "<???>" drop-down list of the instruction box. For additional information on valid data types, refer to "See also". Example The following example shows how the instruction works: ! ,17 7DJB9DOXH 7DJB9DOXH ,1 ,1 7DJ,QB 7DJ2XW 6 The "TagOut" output is set when the following conditions are fulfilled: The operand "TagIn_1" has the signal state "1". The condition of the comparison instruction is fulfilled if "Tag_Value1" >= "Tag_Value2". See also Overview of the valid data types (Page 1204) Example of detecting the fill level of a storage area (Page 1726) 2106 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References CMP <=: Less or equal Description You can use the "Less or equal" instruction to query whether the value at input IN1 is less or equal to the value at input IN2. Both values to be compared must be of the same data type. If the condition of the comparison is fulfilled, the instruction returns the result of logic operation (RLO) "1". If the comparison condition is not fulfilled, the instruction returns RLO "0". The individual characters are compared by means of their code (for example, 'a' is greater than 'A') during the comparison of the strings. The comparison is performed from left to right. The first character to be different decides the result of the comparison. If the left part of the longer string is identical to the shorter string, the shorter string is considered smaller. The following table lists examples of string comparisons: IN1 IN2 RLO of the instruction 'AA' 'aa' 1 'AAA' 'a' 1 'Hello World' 'Hello World' 1 'HelloWorld' 'Hello World' 0 'BB' 'AA' 0 'AAA' 'AA' 0 The "Less or equal" instruction also compares individual characters of a string. The number of the character to be compared is specified in square brackets next to the operand name. "MyString[2]", for example, compares the second character of the "MyString" string. In comparing timer values, the RLO of the instruction is "1" if the timer at input IN1 is smaller (less recent) than or equal to the timer at input IN2. WinCC Basic V13.0 System Manual, 02/2014 2107 Programming the PLC 9.7 References Parameters The following table lists the parameters of the "Less or equal" instruction: Parameters Declaration Data type S7-1200 S7-1500 Memory area Description IN1 Input Integers, floating-point numbers, character strings, TIME, DATE, TOD, DTL Integers, floating-point numbers, character strings, TIME, LTIME, DATE, TOD, LTOD, DTL, DT, LDT I, Q, M, D, L, P or constant First comparison value IN2 Input Integers, floating-point numbers, character strings, TIME, DATE, TOD, DTL Integers, floating-point numbers, character strings, TIME, LTIME, DATE, TOD, LTOD, DTL, DT, LDT I, Q, M, D, L, P or constant Second value to compare You can select the data type of the instruction from the "<???>" drop-down list of the instruction box. For additional information on valid data types, refer to "See also". Example The following example shows how the instruction works: ,17 7DJB9DOXH 7DJB9DOXH ,1 ,1 7DJ,QB 7DJ2XW 6 The "TagOut" output is set when the following conditions are fulfilled: The operand "TagIn_1" has the signal state "1". The condition of the comparison instruction is fulfilled if "Tag_Value1" <= "Tag_Value2". See also Overview of the valid data types (Page 1204) 2108 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References CMP >: Greater than Description You can use the "Greater than" instruction to query whether the value at input IN1 is greater than the value at input IN2. Both values to be compared must be of the same data type. If the condition of the comparison is fulfilled, the instruction returns the result of logic operation (RLO) "1". If the comparison condition is not fulfilled, the instruction returns RLO "0". The individual characters are compared by means of their code (for example, 'a' is greater than 'A') during the comparison of the strings. The comparison is performed from left to right. The first character to be different decides the result of the comparison. If the left part of the longer string is identical to the shorter string, the longer string is considered greater. The following table lists examples of string comparisons: IN1 IN2 RLO of the instruction 'BB' 'AA' 1 'AAA' 'AA' 1 'AA' 'aa' 0 'AAA' 'a' 0 The "Greater than" instruction also compares individual characters of a string. The number of the character to be compared is specified in square brackets next to the operand name. "MyString[2]", for example, compares the second character of the "MyString" string. In comparing timer values, the RLO of the instruction is "1" if the timer at input IN1 is greater (more recent) than the timer at input IN2. Parameters The following table lists the parameters of the "Greater than" instruction: Parameters WinCC Basic V13.0 System Manual, 02/2014 Declaration Data type S7-1200 S7-1500 Memory area Description IN1 Input Integers, floating-point numbers, character strings, TIME, DATE, TOD, DTL Integers, floating-point numbers, character strings, TIME, LTIME, DATE, TOD, LTOD, DTL, DT, LDT I, Q, M, D, L, P or constant First comparison value IN2 Input Integers, floating-point numbers, character strings, TIME, DATE, TOD, DTL Integers, floating-point numbers, character strings, TIME, LTIME, DATE, TOD, LTOD, DTL, DT, LDT I, Q, M, D, L, P or constant Second value to compare 2109 Programming the PLC 9.7 References You can select the data type of the instruction from the "<???>" drop-down list of the instruction box. For additional information on valid data types, refer to "See also". Example The following example shows how the instruction works: ! ,17 7DJB9DOXH 7DJB9DOXH ,1 ,1 7DJ,QB 7DJ2XW 6 The "TagOut" output is set when the following conditions are fulfilled: The operand "TagIn_1" has the signal state "1". The condition of the comparison instruction is fulfilled if "Tag_Value1" > "Tag_Value2". See also Overview of the valid data types (Page 1204) CMP <: Less than Description You can use the "Less than" instruction to query whether the value at input IN1 is less than the value at input IN2. Both values to be compared must be of the same data type. If the condition of the comparison is fulfilled, the instruction returns the result of logic operation (RLO) "1". If the comparison condition is not fulfilled, the instruction returns RLO "0". The individual characters are compared by means of their code (for example, 'a' is greater than 'A') during the comparison of the strings. The comparison is performed from left to right. The first character to be different decides the result of the comparison. If the left part of the longer string is identical to the shorter string, the shorter string is considered smaller. The following table lists examples of string comparisons: <Operand1> <Operand2> RLO of the instruction 'AA' 'aa' 1 'AAA' 'a' 1 'BB' 'AA' 0 'AAA' 'AA' 0 The "Less than" instruction also compares individual characters of a string. The number of the character to be compared is specified in square brackets next to the operand name. "MyString[2]", for example, compares the second character of the "MyString" string. 2110 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References In comparing timer values, the RLO of the instruction is "1" if the timer at input IN1 is less (less recent) than the timer at input IN2 . Parameters The following table lists the parameters of the "Less than" instruction: Parameters Declaration Data type S7-1200 S7-1500 Memory area Description IN1 Input Integers, floating-point numbers, character strings, TIME, DATE, TOD, DTL Integers, floating-point numbers, character strings, TIME, LTIME, DATE, TOD, LTOD, DTL, DT, LDT I, Q, M, D, L, P or constant First comparison value IN2 Input Integers, floating-point numbers, character strings, TIME, DATE, TOD, DTL Integers, floating-point numbers, character strings, TIME, LTIME, DATE, TOD, LTOD, DTL, DT, LDT I, Q, M, D, L, P or constant Second value to compare You can select the data type of the instruction from the "<???>" drop-down list of the instruction box. For additional information on valid data types, refer to "See also". Example The following example shows how the instruction works: ,17 7DJB9DOXH 7DJB9DOXH ,1 ,1 7DJ,QB 7DJ2XW 6 The "TagOut" output is set when the following conditions are fulfilled: The operand "TagIn_1" has the signal state "1". The condition of the comparison instruction is fulfilled if "Tag_Value1" < "Tag_Value2". See also Overview of the valid data types (Page 1204) Example of detecting the fill level of a storage area (Page 1726) WinCC Basic V13.0 System Manual, 02/2014 2111 Programming the PLC 9.7 References IN_RANGE: Value within range Description You can use the "Value within range" instruction to query whether of the value at input VAL is within a specific value range. You specify the limits of the value range with the MIN and MAX inputs. The "Value within range" instruction compares the value at input VAL with the values of the inputs MIN and MAX and sends the result to the box output. If the value at input VAL satisfies the comparison MIN <= VAL or VAL <=MAX, the box output has the signal state "1". If the comparison is not fulfilled, the signal state is "0" at the box output. The comparison function can only execute if the values to be compared are of the same data type. Parameters The following table shows the parameters of the "Value within range" instruction: Parameters Declaration Data type Memory area Description MIN Input Integers, floatingpoint numbers I, Q, M, D, L or constant Low limit of the value range VAL Input Integers, floatingpoint numbers I, Q, M, D, L or constant Comparison value MAX Input Integers, floatingpoint numbers I, Q, M, D, L or constant High limit of the value range Box output Output BOOL I, Q, M, D, L Result of the comparison You can select the data type of the instruction from the "<???>" drop-down list of the instruction box. For additional information on valid data types, refer to "See also": Example The following example shows how the instruction works: 7DJ,QB ! 7DJ,QB 7DJ,QB ,1B5$1*( 5($/ 7DJB0LQ 7DJB9DOXH 7DJB0D[ 0,1 9$/ 0$; 7DJ2XW Output "TagOut" is set when the following conditions are fulfilled: 2112 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References The operands "TagIn_1" or "TagIn_2" have signal state "1". The operand "TagIn_3" has the signal state "1". The value of the operand "Tag_Value" is within the value range that is specified by the current values of the operands "Tag_Min" and "Tag_Max" (MIN <= VAL or VAL <= MAX). See also Overview of the valid data types (Page 1204) OUT_RANGE: Value outside range Description You can use the "Value outside range" instruction to query whether of the value at input VAL is outside a specific value range. You specify the limits of the value range with the MIN and MAX inputs. The "Value outside range" instruction compares the value at input VAL with the values of the inputs MIN and MAX and sends the result to the box output. If the value at input VAL satisfies the comparison MIN > VAL or VAL >MAX, the box output has the signal state "1". The box output has the signal state "1" if a specified operand of data type REAL has an invalid value. The box output returns the signal state "0", if the value at input VAL does not satisfy the MIN > VAL or VAL > MAX condition. The comparison function can only execute if the values to be compared are of the same data type. Parameters The following table shows the parameters of the "Value outside range" instruction: Parameters Declaration Data type Memory area Description MIN Input Integers, floatingpoint numbers I, Q, M, D, L or constant Low limit of the value range VAL Input Integers, floatingpoint numbers I, Q, M, D, L or constant Comparison value MAX Input Integers, floatingpoint numbers I, Q, M, D, L or constant High limit of the value range Box output Output BOOL I, Q, M, D, L Result of the comparison You can select the data type of the instruction from the "<???>" drop-down list of the instruction box. For additional information on valid data types, refer to "See also". WinCC Basic V13.0 System Manual, 02/2014 2113 Programming the PLC 9.7 References Example The following example shows how the instruction works: 7DJ,QB ! 7DJ,QB 7DJ,QB 287B5$1*( 5($/ 7DJB0LQ 7DJB9DOXH 7DJB0D[ 0,1 9$/ 0$; 7DJ2XW Output "TagOut" is set when the following conditions are fulfilled: The operands "TagIn_1" and "TagIn_2" have signal state "1". The operand "TagIn_3" has the signal state "1". The value of the operand "Tag_Value" is outside the value range that is specified by the values of the operands "Tag_Min" and "Tag_Max" (MIN > VAL or VAL > MAX). See also Overview of the valid data types (Page 1204) OK: Check validity Description You can use the "Check validity" instruction to check if the value of an operand (<Operand>) is a valid floating-point number. The check is performed in every program cycle. If the operand value at the time of the query is a valid floating-point number, the output box will return the signal state"1". In all other cases, the signal state at the output of the "Check validity" instruction is "0". You can use the "Check validity" instruction together with the EN mechanism. If you connect the instruction box to an EN enable input, the enable input is set only when the result of the validity query of the value is positive. You can use this function to ensure that an instruction is enabled only when the value of the specified operand is a valid floating-point number. Parameters The following example shows how the "Check validity" instruction works: Parameters Declaration Data type Memory area Description <Operand> Input Floating-point numbers I, Q, M, D, L Value to be checked. For additional information on valid data types, refer to "See also": 2114 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Example The following example shows how the instruction works: 7DJB9DOXH 2. 7DJB9DOXH 2. 08/ 5($/ (1 7DJB9DOXH ,1 287 7DJB9DOXH ,1 (12 7DJB5HVXOW 7DJ2XW When the values of the operands "Tag_Value1" and "Tag_Value2" show valid floating-point numbers, the "Multiply" (MUL) instruction is activated and the ENO output is set. During the execution of the "Multiply" (MUL) instruction, the value of the operand "Tag_Value1" is multiplied by the value of operand "Tag_Value2". The product of the multiplication is then stored in the operand "Tag_Result". If no errors occur during the execution of the instruction, the outputs ENO and "TagOut" are set to signal state "1". See also Overview of the valid data types (Page 1204) NOT_OK: Check invalidity Description You can use the "Check invalidity" instruction to check if the value of an operand (<Operand>) is an invalid floating-point number. The check is performed in every program cycle. If the operand value at the time of the query is a valid floating-point number, then the output box will return the signal state "1". In all other cases, the signal state on the output box is "0". Parameters The following table shows the parameters of the instruction "Check invalidity": Parameters Declaration Data type Memory area Description <Operand> Input Floating-point numbers I, Q, M, D, L Value to be checked. For additional information on valid data types, refer to "See also": WinCC Basic V13.0 System Manual, 02/2014 2115 Programming the PLC 9.7 References Example The following example shows how the instruction works: 7DJ,QB9DOXH 127B2. 029( (1 287 ,1 (12 7DJ2XWB9DOXH 7DJ2XW 7DJ,QB9DOXH When the value of operand "TagIn_Value" is an invalid floating-point number, the instruction "Move value" (MOVE) is not executed. The "TagOut" output is reset to signal state "0". See also Overview of the valid data types (Page 1204) VARIANT instructions EQ_Type: Compare data type for EQUAL with the data type of a tag Description You can use the "Compare data type for EQUAL with the data type of a tag" instruction to query the data type of a tag to which a VARIANT points. You compare the data type of the tag to the data type of a tag that you have declared in the block interface to determine if they are "Equal". The IN1 parameter must have the same VARIANT data type. The IN2 parameter can be an elementary data type or a PLC data type. If the condition of the comparison is fulfilled, the instruction returns the result of logic operation (RLO) "1". If the comparison condition is not fulfilled, the instruction returns RLO "0". Parameters The following table shows the parameters of the "Compare data type for EQUAL with the data type of a tag" instruction: Parameters Declaration Data type Memory area Description IN1 Input VARIANT L First operand IN2 Input Bit strings, integers, floating-point numbers, timers, date and time, character strings, ARRAY, PLC data types I, Q, M, D, L Second operand For additional information on valid data types, refer to "See also". 2116 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Example The following example shows how the instruction works: 7DJB2SHUDQG (4B7\SH 7DJB2SHUDQG ,1 287 7DJ,Q 7DJ2XW 6 The "TagOut" output is set when the following conditions are fulfilled: The operand "TagIn" has the signal state "1". The condition of the comparison instruction is fulfilled, i.e. the "#Tag_Operand1" operand is equal to "Tag_Operand2". See also Overview of the valid data types (Page 1204) NE_Type: Compare data type for UNEQUAL with the data type of a tag Description You can use the "Compare data type for UNEQUAL with the data type of a tag" instruction to query which data type the tag to which a VARIANT points does not have. You compare the data type of the tag to the data type of a tag that you have declared in the block interface to determine if they are "Unequal". The IN1 parameter must have the same VARIANT data type. The IN2 parameter can be an elementary data type or a PLC data type. If the condition of the comparison is fulfilled, the instruction returns the result of logic operation (RLO) "1". If the comparison condition is not fulfilled, the instruction returns RLO "0". Parameters The following table shows the parameters of the "Compare data type for UNEQUAL with the data type of a tag" instruction: Parameters Declaration Data type Memory area Description IN1 Input VARIANT L First operand IN2 Input Bit strings, integers, floating-point numbers, timers, date and time, character strings, ARRAY, PLC data types I, Q, M, D, L Second operand For additional information on valid data types, refer to "See also". WinCC Basic V13.0 System Manual, 02/2014 2117 Programming the PLC 9.7 References Example The following example shows how the instruction works: 7DJB2SHUDQG 1(B7\SH 7DJB2SHUDQG ,1 287 7DJ,Q 7DJ2XW 6 The "TagOut" output is set when the following conditions are fulfilled: The operand "TagIn" has the signal state "1". The condition of the comparison instruction is fulfilled, i.e. the "#Tag_Operand1" operand is not equal to "Tag_Operand2". See also Overview of the valid data types (Page 1204) EQ_ElemType: Compare element data type for EQUAL with the data type of a tag Description You can use the "Compare element data type for EQUAL with the data type of a tag" instruction to query the data type of a tag to which a VARIANT points. You compare the data type of the tag to the data type of a tag that you have declared in the block interface to determine if they are "Equal". The IN1 parameter must have the same VARIANT data type. The IN2 parameter can be an elementary data type or a PLC data type. If the data type of the VARIANT tag is an ARRAY, the data type of the ARRAY elements is compared. If the condition of the comparison is fulfilled, the instruction returns the result of logic operation (RLO) "1". If the comparison condition is not fulfilled, the instruction returns RLO "0". Parameters The following table shows the parameters of the "Compare element data type for EQUAL with the data type of a tag" instruction: Parameters Declaration Data type Memory area Description IN1 Input VARIANT L First operand IN2 Input Bit strings, integers, floating-point numbers, timers, date and time, character strings, ARRAY, PLC data types I, Q, M, D, L Second operand For additional information on valid data types, refer to "See also". 2118 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Example The following example shows how the instruction works: 7DJB2SHUDQG (4B(OHP7\SH 7DJB2SHUDQG ,1 287 7DJ2XW 7DJ,Q 6 The "TagOut" output is set when the following conditions are fulfilled: The operand "TagIn" has the signal state "1". The condition of the comparison instruction is fulfilled, i.e. the "#Tag_Operand1" operand is equal to "Tag_Operand2". See also Overview of the valid data types (Page 1204) NE_ElemType: Compare element data type for UNEQUAL with the data type of a tag Description You can use the "Compare element data type for UNEQUAL with the data type of a tag" instruction to query which data type the tag to which a VARIANT points does not have. You compare the data type of the tag to the data type of a tag that you have declared in the block interface to determine if they are "Unequal". The IN1 parameter must have the same VARIANT data type. The IN2 parameter can be an elementary data type or a PLC data type. If the data type of the VARIANT tag is an ARRAY, the data type of the ARRAY elements is compared. If the condition of the comparison is fulfilled, the instruction returns the result of logic operation (RLO) "1". If the comparison condition is not fulfilled, the instruction returns RLO "0". Parameters The following table shows the parameters of the "Compare element data type for UNEQUAL with the data type of a tag" instruction: Parameters Declaration Data type Memory area Description IN1 Input VARIANT L First operand IN2 Input Bit strings, integers, floating-point numbers, timers, date and time, character strings, ARRAY, PLC data types I, Q, M, D, L Second operand For additional information on valid data types, refer to "See also". WinCC Basic V13.0 System Manual, 02/2014 2119 Programming the PLC 9.7 References Example The following example shows how the instruction works: 7DJB2SHUDQG 1(B(OHP7\SH 7DJB2SHUDQG ,1 7DJ2XW 7DJ,Q 6 287 The "TagOut" output is set when the following conditions are fulfilled: The operand "TagIn" has the signal state "1". The condition of the comparison instruction is fulfilled, i.e. the "#Tag_Operand1" operand is not equal to "Tag_Operand2". See also Overview of the valid data types (Page 1204) IS_NULL: Compare for EQUALS ZERO Description You can use the instruction "Compare for EQUALS ZERO" to query whether the VARIANT does not point to an object. The <Operand> must have the VARIANT data type. Note VARIANT tag points to an ANY pointer If the VARIANT tag points to an ANY pointer, the instruction always returns the result RLO = "0" even if the ANY pointer is ZERO. Parameters The following table shows the parameters of the "Compare for EQUALS ZERO" instruction: Parameters Declaration Data type Memory area Description <Operand> Input VARIANT L Operand that is compared for EQUAL ZERO For additional information on valid data types, refer to "See also". 2120 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Example The following example shows how the instruction works: 7DJB2SHUDQG ,6B18// 287 7DJB,Q 7DJ2XW 7DJB,Q The "TagOut" output is set when the following conditions are fulfilled: The operands "Tag_In1" and "Tag_In2" have signal state "1". The condition of the comparison instruction is fulfilled, i.e. the "#Tag_Operand" operand does not point to an object. See also Overview of the valid data types (Page 1204) NOT_NULL: Compare for UNEQUALS ZERO Description You can use the instruction "Compare for UNEQUALS ZERO" to query whether the VARIANT points to an object. The <Operand> must have the VARIANT data type. Note VARIANT tag points to an ANY pointer If the VARIANT tag points to an ANY pointer, the instruction always returns the result RLO = "1" even if the ANY pointer is ZERO. Parameters The following table shows the parameters of the "Compare for UNEQUALS ZERO" instruction: Parameters Declaration Data type Memory area Description <Operand> Input VARIANT L Operand that is compared for NOT EQUAL ZERO For additional information on valid data types, refer to "See also". WinCC Basic V13.0 System Manual, 02/2014 2121 Programming the PLC 9.7 References Example The following example shows how the instruction works: 7DJB2SHUDQG 127B18// 287 7DJB,Q 7DJ2XW 7DJB,Q The "TagOut" output is set when the following conditions are fulfilled: The operands "Tag_In1" and "Tag_In2" have signal state "1". The condition of the comparison instruction is fulfilled, i.e. the "#Tag_Operand" operand points to an object. See also Overview of the valid data types (Page 1204) IS_ARRAY: Check for ARRAY Description You can use the "Check for ARRAY" instruction to query whether the VARIANT points to a tag of the ARRAY data type. The <Operand> must have the VARIANT data type. Parameters The following table shows the parameters of the "Check for ARRAY" instruction: Parameters Declaration Data type Memory area Description <Operand> Input VARIANT L Operand that is queried for ARRAY For additional information on valid data types, refer to "See also". 2122 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Example The following example shows how the instruction works: 7DJB9$5,$17 7R$UUD\ ,6B$55$< 287 7DJB,Q 7DJ2XW 7DJB,Q The "TagOut" output is set when the following conditions are fulfilled: The operands "Tag_In1" and "Tag_In2" have signal state "1". The condition of the comparison instruction is fulfilled, i.e. the "#Tag_VARIANTToArray" operand has the ARRAY data type. See also Overview of the valid data types (Page 1204) Math functions CALCULATE: Calculate Description The "Calculate" instruction is used to define and execute an expression for the calculation of mathematical operations or complex logic operations depending on the selected data type. You can select the data type of the instruction from the "<???>" drop-down list of the instruction box. Depending on the selected data type, you can combine the functionality of specific instructions to execute a complex calculation. The expression to be calculated is specified via a dialog you can open via the "Calculator" icon at the top of the instruction box. The expression can contain the names of the input parameters and the syntax of the instructions. It is not permitted to specify operand names or operand addresses. In its initial state, the instruction box contains at least 2 inputs (IN1 and IN2). The number of inputs can be extended. The inserted inputs are numbered in ascending order in the box. The values of the inputs are use to execute the specified expression. Not all defined inputs have to be used in the expression. The result of the instruction is transferred to the box output OUT. Note If one of the mathematical operations fails in the expression, then no result is transferred to the OUT output and the ENO enable output has the signal state "1". WinCC Basic V13.0 System Manual, 02/2014 2123 Programming the PLC 9.7 References If, in the expression, you use inputs that are not available in the box, these inputs are automatically inserted. Provided that there are no gaps in the numbering of the inputs that are to be newly defined in the expression. You cannot, for example, use the input IN4 in the expression if the input IN3 is not defined. Enable output ENO has the signal state "0" if one of the following conditions is fulfilled: Enable input EN has the signal state "0". The result or an interim result of the "Calculate" instruction is outside the range permitted for the data type specified at output OUT. A floating-point number has an invalid value. An error occurred during the execution of one of the instructions specified in the expression. The following table shows the instructions that, depending on the selected data type, can be combined and executed in the expression of the "Calculate" instruction: Data type Instruction Syntax Example Bit strings AND: AND logic operation AND IN1 AND IN2 OR IN3 OR: OR logic operation OR XOR: EXCLUSIVE OR logic operation XOR INV: Create ones complement NOT SWAP: Swap 1) SWAP ADD: Add + (IN1 + IN2) * IN3; SUB: Subtract - MUL: Multiply * (ABS(IN2)) * (ABS(IN1)) DIV: Divide / MOD: Return remainder of division MOD INV: Create ones complement NOT NEG: Create twos complement -(in1) ABS: Form absolute value ABS( ) Integers Floating-point numbers ADD: Add 2124 + SUB: Subtract - MUL: Multiply * DIV: Divide / EXPT: Exponentiate ** ABS: Form absolute value ABS( ) SQR: Form square SQR( ) SQRT: Form square root SQRT( ) LN: Form natural logarithm LN( ) EXP: Form exponential value EXP( ) FRAC: Return fraction FRAC( ) SIN: Form sine value SIN( ) COS: Form cosine value COS( ) TAN: Form tangent value TAN( ) ASIN: Form arcsine value ASIN( ) ACOS: Form arccosine value ACOS( ) ((SIN(IN2) * SIN(IN2) + (SIN(IN3) * SIN(IN3)) / IN3)); (SQR(SIN(IN2)) + (SQR(COS(IN3)) / IN2)) WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Data type Instruction Syntax ATAN: Form arctangent value ATAN( ) NEG: Create twos complement -(in1) TRUNC: Truncate numerical value TRUNC( ) ROUND: Round numerical value ROUND( ) CEIL: Generate next higher integer from floatingpoint number CEIL( ) Example FLOOR: Generate next lower integer from floating- FLOOR( ) point number 1) Not possible for data type BYTE. Parameters The following table shows the parameters of the instruction "Calculate": Parameters Declaration Data type Memory area Description S7-1200 S7-1500 EN Input BOOL I, Q, M, D, L I, Q, M, D, L, T, C Enable input ENO Output BOOL I, Q, M, D, L I, Q, M, D, L Enable output IN1 Input Bit strings, integers, floating-point numbers I, Q, M, D, L, P or constant I, Q, M, D, L, P or constant First available input IN2 Input Bit strings, integers, floating-point numbers I, Q, M, D, L, P or constant I, Q, M, D, L, P or constant Second available input INn Input Bit strings, integers, floating-point numbers I, Q, M, D, L, P or constant I, Q, M, D, L, P or constant Additionally inserted inputs OUT Output Bit strings, integers, floating-point numbers I, Q, M, D, L, P I, Q, M, D, L, P Output to which the end result is to be transferred. For additional information on valid data types, refer to "See also". WinCC Basic V13.0 System Manual, 02/2014 2125 Programming the PLC 9.7 References Example The following example shows how the instruction works: &$/&8/$7( ,17 7DJB,QSXW (1 ,1,1 ,1 ,1 7DJB9DOXHB ,1 7DJB9DOXHB ,1 7DJB9DOXHB ,1 287 7DJB9DOXHB ,1 (12 7DJB5HVXOW 7DJB2XWSXW The following table shows how the instruction works using specific operand values: Parameters Operand Value IN1 Tag_Value_1 4 IN2 Tag_Value_2 4 IN3 Tag_Value_3 3 IN4 Tag_Value_4 2 OUT Tag_Result 12 The "Calculate" instruction is executed when input "Tag_Input" has the signal state "1". The value of operand "Tag_Value_1" is added to the value of operand "Tag_Value_2". The sum is multiplied with the value of the operand "Tag_Value_3". The product is divided by the value of the operand "Tag_Value_4". The quotient is transferred as end result to the operand "Tag_Result" at the OUT output of the instruction. If no errors occur during the execution of the individual instructions, output ENO and the operand "Tag_Output" are set to "1". See also Overview of the valid data types (Page 1204) Adding additional inputs and outputs to FBD elements (Page 1469) Removing instruction inputs and outputs (Page 1470) Basics of the EN/ENO mechanism (Page 1299) ADD: Add Description You can use the "Add" instruction to add the value at input IN1 to the value at input IN2 and query the sum at output OUT (OUT := IN1+IN2). In its initial state the instruction box contains at least 2 inputs (IN1 and IN2). The number of inputs can be extended. The inserted inputs are numbered in ascending order in the box. 2126 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References During the execution of the instruction, the values of all available input parameters are added. The sum is stored at output OUT. Enable output ENO has the signal state "0" if one of the following conditions applies: Enable input EN has the signal state "0". The result of the instruction is outside the range permitted for the data type specified at output OUT. A floating-point number has an invalid value. Parameters The following table shows the parameters of the instruction "Add": Parameters Declaration Data type Memory area S7-1200 S7-1500 Description EN Input BOOL I, Q, M, D, L I, Q, M, D, L, T, C Enable input ENO Output BOOL I, Q, M, D, L I, Q, M, D, L Enable output IN1 Input Integers, floating-point numbers I, Q, M, D, L, P or constant I, Q, M, D, L, P or constant First number to be added IN2 Input Integers, floating-point numbers I, Q, M, D, L, P or constant I, Q, M, D, L, P or constant Second number to be added INn Input Integers, floating-point numbers I, Q, M, D, L, P or constant I, Q, M, D, L, P or constant Optional input values, which are added. OUT Output Integers, floating-point numbers I, Q, M, D, L, P I, Q, M, D, L, P Sum You can select the data type of the instruction from the "<???>" drop-down list of the instruction box. For additional information on valid data types, refer to "See also": Example The following example shows how the instruction works: $'' ,17 7DJ,Q (1 7DJB9DOXH ,1 287 7DJB9DOXH ,1 (12 7DJB5HVXOW 7DJ2XW If the operand "TagIn" has the signal state "1", the "Add" instruction is executed. The value of operand "Tag_Value1" is added to the value of operand "Tag_Value2". The result of the WinCC Basic V13.0 System Manual, 02/2014 2127 Programming the PLC 9.7 References addition is stored in the operand "Tag_Result". If the instruction is executed without errors, the ENO enable output has the signal state "1" and the "TagOut" output is set. See also Overview of the valid data types (Page 1204) Removing instruction inputs and outputs (Page 1470) Basics of the EN/ENO mechanism (Page 1299) Selecting a data type (Page 1454) Adding additional inputs and outputs to FBD elements (Page 1469) SUB: Subtract Description You can use the "Subtract" instruction to subtract the value at input IN2 from the value at input IN1 and query the difference at output OUT (OUT := IN1-IN2). Enable output ENO has the signal state "0" if one of the following conditions applies: Enable input EN has the signal state "0". The result of the instruction is outside the range permitted for the data type specified at output OUT. A floating-point number has an invalid value. Parameters The following table shows the parameters of the instruction "Subtract": Parameters Declaration Data type Memory area S7-1200 S7-1500 Description EN Input BOOL I, Q, M, D, L I, Q, M, D, L, T, C Enable input ENO Output BOOL I, Q, M, D, L I, Q, M, D, L Enable output IN1 Input Integers, floating-point numbers I, Q, M, D, L, P or constant I, Q, M, D, L, P or constant Minuend IN2 Input Integers, floating-point numbers I, Q, M, D, L, P or constant I, Q, M, D, L, P or constant Subtrahend OUT Output Integers, floating-point numbers I, Q, M, D, L, P I, Q, M, D, L, P Difference You can select the data type of the instruction from the "<???>" drop-down list of the instruction box. 2128 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References For additional information on valid data types, refer to "See also". Example The following example shows how the instruction works: 68% ,17 7DJ,Q (1 7DJB9DOXH ,1 287 7DJB9DOXH ,1 (12 7DJB5HVXOW 7DJ2XW If the operand "TagIn" has the signal state "1", the "Subtract" instruction is executed. The value of operand "Tag_Value2" is subtracted from the value of operand "Tag_Value1". The result of the subtraction is stored in the operand "Tag_Result". If the instruction is executed without errors, the ENO enable output has the signal state "1" and the "TagOut" output is set. See also Overview of the valid data types (Page 1204) Basics of the EN/ENO mechanism (Page 1299) Selecting a data type (Page 1454) MUL: Multiply Description You can use the "Multiply" instruction to multiply the value at input IN1 with the value at input IN2 and query the total at output OUT (OUT := IN1*IN2). In its initial state the instruction box contains at least 2 inputs (IN1 and IN2). The number of inputs can be extended. The inserted inputs are numbered in ascending order in the box. When the instruction is executed, the values of all available input parameters are multiplied. The product is stored at the OUT output. Enable output ENO has the signal state "0" if one of the following conditions applies: Enable input EN has the signal state "0". The result is outside the range permitted for the data type specified at output OUT. A floating-point number has an invalid value. WinCC Basic V13.0 System Manual, 02/2014 2129 Programming the PLC 9.7 References Parameters The following table shows the parameters of the instruction "Multiply": Parameters Declaration Data type Memory area S7-1200 S7-1500 Description EN Input BOOL I, Q, M, D, L I, Q, M, D, L, T, C Enable input ENO Output BOOL I, Q, M, D, L I, Q, M, D, L Enable output IN1 Input Integers, floating-point numbers I, Q, M, D, L, P or constant I, Q, M, D, L, P or constant First value for multiplication IN2 Input Integers, floating-point numbers I, Q, M, D, L, P or constant I, Q, M, D, L, P or constant Second value for multiplication INn Input Integers, floating-point numbers I, Q, M, D, L, P or constant I, Q, M, D, L, P or constant Optional input values, which are multiplied. OUT Output Integers, floating-point numbers I, Q, M, D, L, P I, Q, M, D, L, P Product You can select the data type of the instruction from the "<???>" drop-down list of the instruction box. For additional information on valid data types, refer to "See also". Example The following example shows how the instruction works: 08/ 5($/ 7DJ,Q (1 7DJB9DOXH ,1 287 7DJB9DOXH ,1 (12 7DJB5HVXOW 7DJ2XW 6 If the operand "TagIn" has the signal state "1", the "Multiply" instruction is executed. The value of operand "Tag_Value1" is multiplied with the value of operand "Tag_Value2". The result of the multiplication is stored in the operand "Tag_Result". If the instruction is executed without errors, the ENO enable output has the signal state "1" and the "TagOut" output is set. See also Overview of the valid data types (Page 1204) Removing instruction inputs and outputs (Page 1470) Basics of the EN/ENO mechanism (Page 1299) 2130 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Selecting a data type (Page 1454) Adding additional inputs and outputs to FBD elements (Page 1469) DIV: Divide Description You can use the "Divide" instruction to divide the value at input IN1 by the value at input IN2 and query the quotient at output OUT (OUT := IN1/IN2). Enable output ENO has the signal state "0" if one of the following conditions applies: Enable input EN has the signal state "0". The result of the instruction is outside the range permitted for the data type specified at output OUT. A floating-point number has an invalid value. Parameters The following table shows the parameters of the instruction "Divide": Parameters Declaration Data type Memory area S7-1200 S7-1500 Description EN Input BOOL I, Q, M, D, L I, Q, M, D, L, T, C Enable input ENO Output BOOL I, Q, M, D, L I, Q, M, D, L Enable output IN1 Input Integers, floating-point numbers I, Q, M, D, L, P or constant I, Q, M, D, L, P or constant Dividend IN2 Input Integers, floating-point numbers I, Q, M, D, L, P or constant I, Q, M, D, L, P or constant Divisor OUT Output Integers, floating-point numbers I, Q, M, D, L, P I, Q, M, D, L, P Quotient value You can select the data type of the instruction from the "<???>" drop-down list of the instruction box. For additional information on valid data types, refer to "See also". WinCC Basic V13.0 System Manual, 02/2014 2131 Programming the PLC 9.7 References Example The following example shows how the instruction works: ',9 5($/ 7DJ,Q (1 7DJB9DOXH ,1 287 7DJB9DOXH ,1 (12 7DJB5HVXOW 7DJ2XW 6 If the operand "TagIn" has the signal state "1", the "Divide" instruction is executed. The value of operand "Tag_Value1" is divided by the value of operand "Tag_Value2". The result of the division is stored in the operand "Tag_Result". If the instruction is executed without errors, the ENO enable output has the signal state "1" and the "TagOut" output is set. See also Overview of the valid data types (Page 1204) Basics of the EN/ENO mechanism (Page 1299) Selecting a data type (Page 1454) MOD: Return remainder of division Description You can use the "Return remainder of division" instruction to divide the value at input IN1 by the value at input IN2 and query the quotient at output OUT. Parameters The following table shows the parameters of the instruction "Return remainder of division": Parameters Declaration Data type Memory area S7-1200 S7-1500 Description EN Input BOOL I, Q, M, D, L I, Q, M, D, L, T, C Enable input ENO Output BOOL I, Q, M, D, L I, Q, M, D, L Enable output IN1 Input Integers I, Q, M, D, L, P or constant I, Q, M, D, L, P or constant Dividend IN2 Input Integers I, Q, M, D, L, P or constant I, Q, M, D, L, P or constant Divisor OUT Output Integers I, Q, M, D, L, P I, Q, M, D, L, P Remainder of division You can select the data type of the instruction from the "<???>" drop-down list of the instruction box. 2132 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References For additional information on valid data types, refer to "See also". Example The following example shows how the instruction works: 02' ',17 7DJ,Q (1 7DJB9DOXH ,1 287 7DJB9DOXH ,1 (12 7DJB5HVXOW 7DJ2XW 6 If the operand "TagIn" has the signal state "1", the "Return remainder of division" instruction is executed. The value of operand "Tag_Value1" is divided by the value of operand "Tag_Value2". The remainder of division is stored in operand "Tag_Result". If the instruction is executed without errors, the ENO enable output has the signal state "1" and the "TagOut" output is set. See also Overview of the valid data types (Page 1204) Basics of the EN/ENO mechanism (Page 1299) Selecting a data type (Page 1454) NEG: Create twos complement Description You can use the "Create twos complement" instruction to change the sign of the value at input IN and query the result at output OUT. If there is a positive value at input IN, for example, the negative equivalent of this value is sent to output OUT. Enable output ENO has the signal state "0" if one of the following conditions applies: Enable input EN has the signal state "0". The result of the instruction is outside the range permitted for the data type specified at output OUT. A floating-point number has an invalid value. WinCC Basic V13.0 System Manual, 02/2014 2133 Programming the PLC 9.7 References Parameters The following table shows the parameters of the "Create twos complement" instruction: Parameters Declaration Data type Memory area Description S7-1200 S7-1500 S7-1200 S7-1500 EN Input BOOL BOOL I, Q, M, D, L I, Q, M, D, L, T, C Enable input ENO Output BOOL BOOL I, Q, M, D, L I, Q, M, D, L Enable output IN Input SINT, INT, DINT, Floatingpoint numbers SINT, INT, DINT, LINT, Floatingpoint numbers I, Q, M, D, L, P or constant I, Q, M, D, L, P or constant Input value OUT Output SINT, INT, DINT, Floatingpoint numbers SINT, INT, DINT, LINT, Floatingpoint numbers I, Q, M, D, L, P I, Q, M, D, L, P Twos complement of the input value You can select the data type of the instruction from the "<???>" drop-down list of the instruction box. For additional information on valid data types, refer to "See also". Example The following example shows how the instruction works: 1(* 5($/ 7DJ,Q 7DJ,QB9DOXH (1 287 ,1 (12 7DJ2XWB9DOXH 7DJ2XW If the operand "TagIn" has the signal state "1", the "Create twos complement" instruction is executed. The sign of the value at input "TagIn_Value" is changed and the result is stored at output "TagOut_Value". If the instruction is executed without errors, the ENO enable output has the signal state "1" and the "TagOut" output is set. See also Overview of the valid data types (Page 1204) Basics of the EN/ENO mechanism (Page 1299) Adding additional inputs and outputs to FBD elements (Page 1469) 2134 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References INC: Increment Description You can use the "Increment" instruction to change the value of the operand at parameter IN/ OUT to the next higher value and query the result. Enable output ENO has the signal state "0" if one of the following conditions applies: Enable input EN has the signal state "0". A floating-point number has an invalid value. Parameters The following table shows the parameters of the "Increment" instruction: Parameters Declaration Data type Memory area S7-1200 S7-1500 Description EN Input BOOL I, Q, M, D, L I, Q, M, D, L, T, C Enable input ENO Output BOOL I, Q, M, D, L I, Q, M, D, L Enable output IN/OUT InOut Integers I, Q, M, D, L I, Q, M, D, L Value to be incremented. You can select the data type of the instruction from the "<???>" drop-down list of the instruction box. For additional information on valid data types, refer to "See also". Example The following example shows how the instruction works: 7DJ,QB 7DJ,QB 7DJB,Q2XW ,1& ,17 (1 ,1287 7DJ2XW (12 If the operands TagIn_1 and TagIn_2 have the signal state "1", the value of the operand "Tag_InOut" is incremented by one and the output "TagOut" is set. See also Overview of the valid data types (Page 1204) Basics of the EN/ENO mechanism (Page 1299) Adding additional inputs and outputs to FBD elements (Page 1469) WinCC Basic V13.0 System Manual, 02/2014 2135 Programming the PLC 9.7 References DEC: Decrement Description You can use the "Decrement" instruction to change the value of the operand at parameter IN/ OUT to the next lower value and query the result. Enable output ENO has the signal state "0" if one of the following conditions applies: Enable input EN has the signal state "0". A floating-point number has an invalid value. Parameters The following table shows the parameters of the instruction "Decrement": Parameters Declaration Data type Memory area S7-1200 S7-1500 Description EN Input BOOL I, Q, M, D, L I, Q, M, D, L, T, C Enable input ENO Output BOOL I, Q, M, D, L I, Q, M, D, L Enable output IN/OUT InOut Integers I, Q, M, D, L I, Q, M, D, L Value to be decremented. You can select the data type of the instruction from the "<???>" drop-down list of the instruction box. For additional information on valid data types, refer to "See also". Example The following example shows how the instruction works: 7DJ,QB 7DJ,QB 7DJB,Q2XW '(& ,17 (1 ,1287 7DJ2XW (12 If the operands "TagIn_1" and "TagIn_2" have the signal state "1", the value of the operand "Tag_InOut" is decremented by one and the output "TagOut" is set. See also Overview of the valid data types (Page 1204) Basics of the EN/ENO mechanism (Page 1299) Adding additional inputs and outputs to FBD elements (Page 1469) 2136 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References ABS: Form absolute value Description You can use the "Form absolute value" instruction to calculate the absolute value of the value specified at input IN. The result of the instruction is provided at output OUT and can be queried there. Enable output ENO has the signal state "0" if one of the following conditions applies: Enable input EN has the signal state "0". A floating-point number has an invalid value. Parameters The following table shows the parameters of the instruction "Form absolute value": Parameters Declaration Data type Memory area S7-1200 S7-1500 S7-1200 S7-1500 Description EN Input BOOL BOOL I, Q, M, D, L I, Q, M, D, L, T, C Enable input ENO Output BOOL BOOL I, Q, M, D, L I, Q, M, D, L Enable output IN Input SINT, INT, DINT, floatingpoint numbers SINT, INT, DINT, LINT, floatingpoint numbers I, Q, M, D, L, P or constant I, Q, M, D, L, P or constant Input value OUT Output SINT, INT, DINT, floatingpoint numbers SINT, INT, DINT, LINT, floatingpoint numbers I, Q, M, D, L, P I, Q, M, D, L, P Absolute value of the input value You can select the data type of the instruction from the "<???>" drop-down list of the instruction box. For additional information on valid data types, refer to "See also". Example The following example shows how the instruction works: $%6 5($/ 7DJ,Q 7DJ,QB9DOXH (1 287 ,1 (12 7DJ2XWB9DOXH 7DJ2XW The following table shows how the instruction works using specific operand values: WinCC Basic V13.0 System Manual, 02/2014 2137 Programming the PLC 9.7 References Parameters Operand Value IN TagIn_Value -6.234 OUT TagOut_Value 6.234 If the operand "TagIn" has the signal state "1", the "Form absolute value" instruction is executed. The instruction calculates the absolute value of the value at input "TagIn_Value" and sends the result to output "TagOut_Value". If no errors occur during the execution of the instruction, the output "TagOut" is set. See also Overview of the valid data types (Page 1204) Basics of the EN/ENO mechanism (Page 1299) Adding additional inputs and outputs to FBD elements (Page 1469) MIN: Get minimum Description The "Get minimum" instruction compares the values at the available inputs and writes the lowest value to the OUT output. The number of inputs can be expanded at the instruction box by additional inputs. The inputs are numbered in ascending order in the box. In its initial state the instruction contains at least two inputs (IN1 and IN2) and no more than 100 inputs. The ENO enable output has the signal state "0" if one of the following conditions is fulfilled: Enable input EN has the signal state "0". The implicit conversion of the data types fails during execution of the instruction. A floating-point number has an invalid value. Parameters The following table shows the parameters of the "Get minimum" instruction: Parameter 2138 Declaration Data type Memory area Description S7-1200 S7-1500 S7-1200 S7-1500 EN Input BOOL BOOL I, Q, M, D, L I, Q, M, D, L, T, C Enable input ENO Output BOOL BOOL I, Q, M, D, L I, Q, M, D, L Enable output WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameter Declaration Data type Memory area S7-1200 S7-1500 S7-1200 Description S7-1500 IN1 Input Integers, floatingpoint numbers, TIME, TOD, DATE Integers, floatingpoint numbers, TIME, LTIME, TOD, LTOD, DATE, LDT I, Q, M, D, L, I, Q, M, D, L, First input P or constant P or constant value IN2 Input Integers, floatingpoint numbers, TIME, TOD, DATE Integers, floatingpoint numbers, TIME, LTIME, TOD, LTOD, DATE, LDT I, Q, M, D, L, I, Q, M, D, L, Second P or constant P or constant input value INn Input Integers, floatingpoint numbers, TIME, TOD, DATE Integers, floatingpoint numbers, TIME, LTIME, TOD, LTOD, DATE, LDT I, Q, M, D, L, I, Q, M, D, L, Additionally P or constant P or constant inserted inputs whose values are to be compared OUT Output Integers, floatingpoint numbers, TIME, TOD, DATE Integers, floatingpoint numbers, TIME, LTIME, TOD, LTOD, DATE, LDT I, Q, M, D, L, P I, Q, M, D, L, P Result The data types TOD, LTOD, DATE, and LDT can only be used if the IEC test is not enabled. You can select the data type of the instruction from the "<???>" drop-down list of the instruction box. For additional information on valid data types, refer to "See also". WinCC Basic V13.0 System Manual, 02/2014 2139 Programming the PLC 9.7 References Example The following example shows how the instruction works: 7DJ,QB 7DJ,QB 0,1 ,17 (1 7DJ,QB9DOXH ,1 7DJ,QB9DOXH ,1 287 7DJ,QB9DOXH ,1 (12 7DJ2XWB9DOXH 7DJ2XW The following table shows how the instruction works using specific operand values: Parameter Operand Value IN1 TagIn_Value1 12222 IN2 TagIn_Value2 14444 IN3 TagIn_Value3 13333 OUT TagOut_Value 12222 If the "TagIn_1" and "TagIn_2" operands have signal state "1", the "Get minimum" instruction is executed. The instruction compares the values of the specified operands and copies the lowest value ("TagIn_Value1") to output "TagOut_Value". If the instruction is executed without errors, the output "TagOut" is set. See also Overview of the valid data types (Page 1204) Removing instruction inputs and outputs (Page 1470) Basics of the EN/ENO mechanism (Page 1299) Adding additional inputs and outputs to FBD elements (Page 1469) MAX: Get maximum Description The "Get maximum" instruction compares the values at the available inputs and writes the highest value to the OUT output. The number of inputs can be expanded at the instruction box by additional inputs. The inputs are numbered in ascending order in the box. In its initial state the instruction contains at least two inputs (IN1 and IN2) and no more than 100 inputs. The ENO enable output has the signal state "0" if one of the following conditions is fulfilled: 2140 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Enable input EN has the signal state "0". The implicit conversion of the data types fails during execution of the instruction. A floating-point number has an invalid value. Parameters The following table shows the parameters of the "Get maximum" instruction: Parameter Declaration Data type Memory area S7-1200 S7-1500 S7-1200 S7-1500 Description EN Input BOOL BOOL I, Q, M, D, L I, Q, M, D, L, T, C Enable input ENO Output BOOL BOOL I, Q, M, D, L I, Q, M, D, L Enable output IN1 Input Integers, floatingpoint numbers, TIME, TOD, DATE Integers, floatingpoint numbers, TIME, LTIME, TOD, LTOD, DATE, LDT I, Q, M, D, L, I, Q, M, D, L, First input P or constant P or constant value IN2 Input Integers, floatingpoint numbers, TIME, TOD, DATE Integers, floatingpoint numbers, TIME, LTIME, TOD, LTOD, DATE, LDT I, Q, M, D, L, I, Q, M, D, L, Second P or constant P or constant input value INn Input Integers, floatingpoint numbers, TIME, TOD, DATE Integers, floatingpoint numbers, TIME, LTIME, TOD, LTOD, DATE, LDT I, Q, M, D, L, I, Q, M, D, L, Additionally P or constant P or constant inserted inputs whose values are to be compared. OUT Output Integers, floatingpoint numbers, TIME, TOD, DATE Integers, floatingpoint numbers, TIME, LTIME, TOD, LTOD, DATE, LDT I, Q, M, D, L, P I, Q, M, D, L, P Result The data types TOD, LTOD, DATE, and LDT can only be used if the IEC test is not enabled. You can select the data type of the instruction from the "<???>" drop-down list of the instruction box. For additional information on valid data types, refer to "See also". WinCC Basic V13.0 System Manual, 02/2014 2141 Programming the PLC 9.7 References Example The following example shows how the instruction works: 7DJ,QB 7DJ,QB 0$; ,17 (1 7DJ,QB9DOXH ,1 7DJ,QB9DOXH ,1 287 7DJ,QB9DOXH ,1 (12 7DJ2XWB9DOXH 7DJ2XW The following table shows how the instruction works using specific operand values: Parameter Operand Value IN1 TagIn_Value1 12222 IN2 TagIn_Value2 14444 IN3 TagIn_Value3 13333 OUT TagOut_Value 14444 If the "TagIn_1" and "TagIn_2" operands have signal state "1", the "Get maximum" instruction is executed. The instruction compares the values of the specified operands and copies the highest value ("TagIn_Value2") to output "TagOut_Value". If no errors occur during the execution of the instruction, the output "TagOut" is set. See also Overview of the valid data types (Page 1204) Removing instruction inputs and outputs (Page 1470) Basics of the EN/ENO mechanism (Page 1299) Adding additional inputs and outputs to FBD elements (Page 1469) LIMIT: Set limit value Description You can use the "Set limit value" instruction to limit the value at input IN to the values at the inputs MN and MX. If the value at the IN input meets the MN condition <= IN <= MX, it is copied to the OUT output. If the condition is not fulfilled and the input value IN is below the low limit MN, output OUT is set to the value of the input MN. If the high limit MX is exceeded, output OUT is set to the value of the input MX. If the value at input MN is greater than that at input MX, the result is undefined and the enable output ENO is "0". Enable output ENO has the signal state "0" if one of the following conditions applies: 2142 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Enable input EN has the signal state "0". The specified tags are not of the same data type. An operand has an invalid value. The value at the MN input is greater than the value at input MX. Parameters The following table shows the parameters of the "Set limit value" instruction: Parameter Declaration Data type Memory area S7-1200 S7-1500 S7-1200 S7-1500 Description EN Input BOOL BOOL I, Q, M, D, L I, Q, M, D, L, T, C Enable input ENO Output BOOL BOOL I, Q, M, D, L I, Q, M, D, L Enable output MN Input Integers, floatingpoint numbers, TIME, TOD, DATE Integers, floatingpoint numbers, TIME, LTIME, TOD, LTOD, DATE, LDT I, Q, M, D, L, I, Q, M, D, L, Low limit P or constant P or constant IN Input Integers, floatingpoint numbers, TIME, TOD, DATE Integers, floatingpoint numbers, TIME, LTIME, TOD, LTOD, DATE, LDT I, Q, M, D, L, I, Q, M, D, L, Input value P or constant P or constant MX Input Integers, floatingpoint numbers, TIME, TOD, DATE Integers, floatingpoint numbers, TIME, LTIME, TOD, LTOD, DATE, LDT I, Q, M, D, L, I, Q, M, D, L, High limit P or constant P or constant OUT Output Integers, floatingpoint numbers, TIME, TOD, DATE Integers, floatingpoint numbers, TIME, LTIME, TOD, LTOD, DATE, LDT I, Q, M, D, L, P I, Q, M, D, L, P Result The data types TOD, LTOD, DATE, and LDT can only be used if the IEC test is not enabled. You can select the data type of the instruction from the "<???>" drop-down list of the instruction box. WinCC Basic V13.0 System Manual, 02/2014 2143 Programming the PLC 9.7 References For additional information on valid data types, refer to "See also". Example The following example shows how the instruction works: /,0,7 7DJ,QB ,17 7DJ,QB 7DJB01 7DJB9DOXH 7DJB0; (1 287 01 (12 7DJB5HVXOW 7DJ2XW ,1 0; The following table shows how the instruction works using specific operand values: Parameter Operand Value MN Tag_MN 12000 IN Tag_Value 8000 MX Tag_MX 16000 OUT Tag_Result 12000 If the "TagIn_1" and "TagIn_2" operands have the signal state "1", the "Set limit value" instruction is executed. The value of operand "Tag_Value" is compared with the values of operands "Tag_MN" and "Tag_MX". Since the value at the operand "Tag_Value" is less than the low limit, the value of the operand "Tag_MN" is copied to output "Tag_Result". If the instruction is executed without errors, the output "TagOut" is set. See also Overview of the valid data types (Page 1204) Basics of the EN/ENO mechanism (Page 1299) Adding additional inputs and outputs to FBD elements (Page 1469) SQR: Form square Description You can use the "Form square" instruction to square the value at input IN and query the result at output OUT. Enable output ENO has the signal state "0" if one of the following conditions applies: Enable input EN has the signal state "0". The value at input IN is not a valid floating-point number. 2144 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameters The following table shows the parameters of the instruction "Form square": Parameters Declaration Data type Memory area S7-1200 S7-1500 Description EN Input BOOL I, Q, M, D, L I, Q, M, D, L, T, C Enable input ENO Output BOOL I, Q, M, D, L I, Q, M, D, L Enable output IN Input Floating-point numbers I, Q, M, D, L, P or constant I, Q, M, D, L, P or constant Input value OUT Output Floating-point numbers I, Q, M, D, L, P I, Q, M, D, L, P Square of the input value You can select the data type of the instruction from the "<???>" drop-down list of the instruction box. For additional information on valid data types, refer to "See also". Example The following example shows how the instruction works: 645 5($/ 7DJ,Q (1 287 ,1 (12 7DJB5HVXOW 7DJ2XW 7DJB9DOXH The following table shows how the instruction works using specific operand values: Parameters Operand Value IN Tag_Value 5.0 OUT Tag_Result 25.0 If the operand "TagIn" has the signal state "1", the "Form square" instruction is executed. The instruction squares the value of the operand "Tag_Value" and sends the result to output "Tag_Result". If no errors occur during the execution of the instruction, the output "TagOut" is set. See also Overview of the valid data types (Page 1204) Basics of the EN/ENO mechanism (Page 1299) WinCC Basic V13.0 System Manual, 02/2014 2145 Programming the PLC 9.7 References SQRT: Form square root Description You can use the "Form square root" instruction to form the square root of the value at input IN and query the result at output OUT. The instruction has a positive result if the input value is greater than zero. If input values are less than zero, output OUT returns an invalid floatingpoint number. If the value at input IN is "0", the result is also "0". Enable output ENO has the signal state "0" if one of the following conditions applies: Enable input EN has the signal state "0". The value at input IN is not a valid floating-point number. The value at input IN is negative. Parameters The following table shows the parameters of the instruction "Form square root": Parameters Declaration Data type Memory area Description S7-1200 S7-1500 I, Q, M, D, L, T, C Enable input EN Input BOOL I, Q, M, D, L ENO Output BOOL I, Q, M, D, L I, Q, M, D, L Enable output IN Input Floating-point numbers I, Q, M, D, L, P or constant I, Q, M, D, L, P or constant Input value OUT Output Floating-point numbers I, Q, M, D, L I, Q, M, D, L Square root of the input value You can select the data type of the instruction from the "<???>" drop-down list of the instruction box. For additional information on valid data types, refer to "See also". Example The following example shows how the instruction works: 6457 5($/ 7DJ,Q (1 287 ,1 (12 7DJB5HVXOW 7DJ2XW 7DJB9DOXH The following table shows how the instruction works using specific operand values: 2146 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameters Operand Value IN Tag_Value 25.0 OUT Tag_Result 5.0 If the operand "TagIn" has the signal state "1", the "Form square root" instruction is executed. The instruction calculates the square root of the operand "Tag_Value" and sends the result to output "Tag_Result". If no errors occur during the execution of the instruction, the output "TagOut" is set. See also Overview of the valid data types (Page 1204) Basics of the EN/ENO mechanism (Page 1299) LN: Form natural logarithm Description You can use the "Form natural logarithm" instruction to calculate the natural logarithm to base e (e = 2.718282) of the value at input IN. The result is sent to output OUT and can be queried there. The instruction has a positive result if the input value is greater than zero. If input values are less than zero, output OUT returns an invalid floating-point number. Enable output ENO has the signal state "0" if one of the following conditions applies: Enable input EN has the signal state "0". The value at input IN is not a valid floating-point number. The value at input IN is negative. Parameters The following table shows the parameters of the instruction "Form natural logarithm": Parameters Declaration Data type Memory area S7-1200 S7-1500 Description EN Input BOOL I, Q, M, D, L I, Q, M, D, L, T, C Enable input ENO Output BOOL I, Q, M, D, L I, Q, M, D, L Enable output IN Input Floating-point numbers I, Q, M, D, L, P or constant I, Q, M, D, L, P or constant Input value OUT Output Floating-point numbers I, Q, M, D, L, P I, Q, M, D, L, P Natural logarithm of the input value You can select the data type of the instruction from the "<???>" drop-down list of the instruction box. For additional information on valid data types, refer to "See also". WinCC Basic V13.0 System Manual, 02/2014 2147 Programming the PLC 9.7 References Example The following example shows how the instruction works: /1 5($/ 7DJ,Q (1 287 ,1 (12 7DJB5HVXOW 7DJ2XW 7DJB9DOXH If the operand "TagIn" has the signal state "1", the "Form natural logarithm" instruction is executed. The instruction forms the natural logarithm of the value at input "Tag_Value" and sends the result to output "Tag_Result". If no errors occur during the execution of the instruction, the output "TagOut" is set. See also Overview of the valid data types (Page 1204) Basics of the EN/ENO mechanism (Page 1299) EXP: Form exponential value Description You can use the "Form exponential value" instruction to calculate the exponent from the base e (e = 2.718282 and the value specified at input IN. The result is provided at output OUTand can be queried there (OUT = eIN). Enable output ENO has the signal state "0" if one of the following conditions applies: Enable input EN has the signal state "0". The value at input IN is not a valid floating-point number. Parameters The following table shows the parameters of the instruction "Form exponential value": Parameters 2148 Declaration Data type Memory area S7-1200 S7-1500 Description EN Input BOOL I, Q, M, D, L I, Q, M, D, L, T, C Enable input ENO Output BOOL I, Q, M, D, L I, Q, M, D, L Enable output IN Input Floating-point numbers I, Q, M, D, L, P or constant I, Q, M, D, L, P or constant Input value OUT Output Floating-point numbers I, Q, M, D, L, P I, Q, M, D, L, P Exponential value of the input value IN WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References You can select the data type of the instruction from the "<???>" drop-down list of the instruction box. For additional information on valid data types, refer to "See also". Example The following example shows how the instruction works: (;3 5($/ 7DJ,Q (1 287 ,1 (12 7DJB5HVXOW 7DJ2XW 7DJB9DOXH If the operand "TagIn" has the signal state "1", the "Form exponential value" instruction is executed. The instruction forms the exponent from base e and the value of the operand "Tag_Value" and sends the result to output "Tag_Result". If no errors occur during the execution of the instruction, the output "TagOut" is set. See also Overview of the valid data types (Page 1204) Basics of the EN/ENO mechanism (Page 1299) SIN: Form sine value Description You can use the "Form sine value" instruction to calculate the sine of an angle. The size of the angle is specified in the radian measure at input IN. The result of the instruction is provided at output OUT and can be queried there. Enable output ENO has the signal state "0" if one of the following conditions applies: Enable input EN has the signal state "0". The value at input IN is not a valid floating-point number. Parameters The following table shows the parameters of the instruction "Form sine value": Parameters WinCC Basic V13.0 System Manual, 02/2014 Declaration Data type Memory area S7-1200 S7-1500 Description EN Input BOOL I, Q, M, D, L I, Q, M, D, L, T, C Enable input ENO Output BOOL I, Q, M, D, L I, Q, M, D, L Enable output 2149 Programming the PLC 9.7 References Parameters Declaration Data type Memory area Description S7-1200 S7-1500 I, Q, M, D, L, P or constant IN Input Floating-point numbers I, Q, M, D, L, P or constant Size of angle in the radian measure OUT Output Floating-point numbers I, Q, M, D, L, P I, Q, M, D, L, P Sine of the specified angle You can select the data type of the instruction from the "<???>" drop-down list of the instruction box. For additional information on valid data types, refer to "See also". Example The following example shows how the instruction works: 6,1 5($/ 7DJ,Q (1 287 ,1 (12 7DJB5HVXOW 7DJ2XW 7DJB9DOXH The following table shows how the instruction works using specific operand values: Parameters Operand Value IN Tag_Value +1.570796 (/2) OUT Tag_Result 1.0 If the operand "TagIn" has the signal state "1", the "Form sine value" instruction is executed. The instruction calculates the sine of the angle specified at input "Tag_Value" and sends the result to output "Tag_Result". If no errors occur during the execution of the instruction, the output "TagOut" is set. See also Overview of the valid data types (Page 1204) Basics of the EN/ENO mechanism (Page 1299) COS: Form cosine value Description You can use the "Form cosine value" instruction to calculate the cosine of an angle. The size of the angle is specified in the radian measure at input IN. The result of the instruction is provided at output OUT and can be queried there. Enable output ENO has the signal state "0" if one of the following conditions applies: 2150 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Enable input EN has the signal state "0". The value at input IN is not a valid floating-point number. Parameters The following table shows the parameters of the instruction "Form cosine value": Parameters Declaration Data type Memory area S7-1200 S7-1500 I, Q, M, D, L, T, C Description EN Input BOOL I, Q, M, D, L Enable input ENO Output BOOL I, Q, M, D, L I, Q, M, D, L Enable output IN Input Floating-point numbers I, Q, M, D, L, P or constant I, Q, M, D, L, P or constant Size of angle in the radian measure OUT Output Floating-point numbers I, Q, M, D, L, P I, Q, M, D, L, P Cosine of the specified angle You can select the data type of the instruction from the "<???>" drop-down list of the instruction box. For additional information on valid data types, refer to "See also". Example The following example shows how the instruction works: &26 5($/ 7DJ,Q (1 287 ,1 (12 7DJB5HVXOW 7DJ2XW 7DJB9DOXH The following table shows how the instruction works using specific operand values: Parameters Operand Value IN Tag_Value +1.570796 (/2) OUT Tag_Result 0 If the operand "TagIn" has the signal state "1", the "Form cosine value" instruction is executed. The instruction calculates the cosine of the angle specified at input "Tag_Value" and sends the result to output "Tag_Result". If no errors occur during the execution of the instruction, the output "TagOut" is set. WinCC Basic V13.0 System Manual, 02/2014 2151 Programming the PLC 9.7 References See also Overview of the valid data types (Page 1204) Basics of the EN/ENO mechanism (Page 1299) TAN: Form tangent value Description You can use the "Form tangent value" instruction to calculate the tangent of an angle. The size of the angle is specified in the radian measure at input IN. The result of the instruction is provided at output OUT and can be queried there. Enable output ENO has the signal state "0" if one of the following conditions applies: Enable input EN has the signal state "0". The value at input IN is not a valid floating-point number. Parameters The following table shows the parameters of the instruction "Form tangent value": Parameters Declaration Data type Memory area S7-1200 S7-1500 Description EN Input BOOL I, Q, M, D, L I, Q, M, D, L, T, C Enable input ENO Output BOOL I, Q, M, D, L I, Q, M, D, L Enable output IN Input Floating-point numbers I, Q, M, D, L, P or constant I, Q, M, D, L, P or constant Size of angle in the radian measure OUT Output Floating-point numbers I, Q, M, D, L, P I, Q, M, D, L, P Tangent of the specified angle You can select the data type of the instruction from the "<???>" drop-down list of the instruction box. For additional information on valid data types, refer to "See also". Example The following example shows how the instruction works: 7$1 5($/ 7DJ,Q 7DJB9DOXH (1 (12 7DJ2XW ,1 287 7DJB5HVXOW The following table shows how the instruction works using specific operand values: 2152 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameters Operand Value IN Tag_Value +3.141593 () OUT Tag_Result 0 If the operand "TagIn" has the signal state "1", the "Form tangent value" instruction is executed. The instruction calculates the tangent of the angle specified at input "Tag_Value" and stores the result at output "Tag_Result". If no errors occur during the execution of the instruction, the output "TagOut" is set. See also Overview of the valid data types (Page 1204) Basics of the EN/ENO mechanism (Page 1299) ASIN: Form arcsine value Description You can use the "Form arcsine value" instruction to calculate the size of the angle from the sine value specified at input IN, which corresponds to this value. Only valid floating-point numbers within the range -1 to +1 can be specified at input IN. The calculated angle size is output in radians at output OUT and can range in value from -/2 to +/2. Enable output ENO has the signal state "0" if one of the following conditions applies: Enable input EN has the signal state "0". The value at input IN is not a valid floating-point number. The value at input IN is outside the permitted range (-1 to +1). Parameters The following table shows the parameters of the instruction "Form arcsine value": Parameters Declaration Data type Memory area S7-1200 S7-1500 Description EN Input BOOL I, Q, M, D, L I, Q, M, D, L, T, C Enable input ENO Output BOOL I, Q, M, D, L I, Q, M, D, L Enable output IN Input Floating-point numbers I, Q, M, D, L, P or constant I, Q, M, D, L, P or constant Sine value OUT Output Floating-point numbers I, Q, M, D, L, P I, Q, M, D, L, P Size of angle in the radian measure You can select the data type of the instruction from the "<???>" drop-down list of the instruction box. For additional information on valid data types, refer to "See also". WinCC Basic V13.0 System Manual, 02/2014 2153 Programming the PLC 9.7 References Example The following example shows how the instruction works: $6,1 5($/ 7DJ,Q (1 287 ,1 (12 7DJB5HVXOW 7DJ2XW 7DJB9DOXH The following table shows how the instruction works using specific operand values: Parameters Operand Value IN Tag_Value 1.0 OUT Tag_Result +1.570796 (/2) If the operand "TagIn" has the signal state "1", the "Form arcsine value" instruction is executed. The instruction calculates the size of the angle corresponding to the sine value at input "Tag_Value". The result of the instruction is stored at output "Tag_Result". If no errors occur during the execution of the instruction, the output "TagOut" is set. See also Overview of the valid data types (Page 1204) Basics of the EN/ENO mechanism (Page 1299) ACOS: Form arccosine value Description You can use the "Form arccosine value" instruction to calculate the size of the angle from the cosine value specified at input IN, which corresponds to this value. Only valid floating-point numbers within the range -1 to +1 can be specified at input IN. The calculated angle size is output in radians at output OUT and can range in value from 0 to +. Enable output ENO has the signal state "0" if one of the following conditions applies: Enable input EN has the signal state "0". The value at input IN is not a valid floating-point number. The value at input IN is outside the permitted range (-1 to +1). 2154 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameters The following table shows the parameters of the instruction "Form arccosine value": Parameters Declaration Data type Memory area S7-1200 S7-1500 Description EN Input BOOL I, Q, M, D, L I, Q, M, D, L, T, C Enable input ENO Output BOOL I, Q, M, D, L I, Q, M, D, L Enable output IN Input Floating-point numbers I, Q, M, D, L, P or constant I, Q, M, D, L, P or constant Cosine value OUT Output Floating-point numbers I, Q, M, D, L, P I, Q, M, D, L, P Size of angle in the radian measure You can select the data type of the instruction from the "<???>" drop-down list of the instruction box. For additional information on valid data types, refer to "See also". Example The following example shows how the instruction works: $&26 5($/ 7DJ,Q (1 287 ,1 (12 7DJB5HVXOW 7DJ2XW 7DJB9DOXH The following table shows how the instruction works using specific operand values: Parameters Operand Value IN Tag_Value 0 OUT Tag_Result +1.570796 (/2) If the operand "TagIn" has the signal state "1", the "Form arccosine value" instruction is executed. The instruction calculates the size of the angle corresponding to the cosine value at input "Tag_Value". The result of the instruction is stored at output "Tag_Result". If no errors occur during the execution of the instruction, the output "TagOut" is set. See also Overview of the valid data types (Page 1204) Basics of the EN/ENO mechanism (Page 1299) WinCC Basic V13.0 System Manual, 02/2014 2155 Programming the PLC 9.7 References ATAN: Form arctangent value Description You can use the "Form arctangent value" instruction to calculate the size of the angle from the tangent value specified at input IN, which corresponds to this value. Only valid floating-point numbers may be specified at input IN. The calculated angle size is output in radians at the output OUT and can range in value from -/2 to +/2. Enable output ENO has the signal state "0" if one of the following conditions applies: Enable input EN has the signal state "0". The value at input IN is not a valid floating-point number. Parameters The following table shows the parameters of the instruction "Form arctangent value": Parameters Declaration Data type Memory area S7-1200 S7-1500 Description EN Input BOOL I, Q, M, D, L I, Q, M, D, L, T, C Enable input ENO Output BOOL I, Q, M, D, L I, Q, M, D, L Enable output IN Input Floating-point numbers I, Q, M, D, L, P or constant I, Q, M, D, L, P or constant Tangent value OUT Output Floating-point numbers I, Q, M, D, L, P I, Q, M, D, L, P Size of angle in the radian measure You can select the data type of the instruction from the "<???>" drop-down list of the instruction box. For additional information on valid data types, refer to "See also". Example The following example shows how the instruction works: $7$1 5($/ 7DJ,Q (1 287 ,1 (12 7DJB5HVXOW 7DJ2XW 7DJB9DOXH The following table shows how the instruction works using specific operand values: 2156 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameters Operand Value IN Tag_Value 1.0 OUT Tag_Result +0.785398 (/4) If the operand "TagIn" has the signal state "1", the "Form arctangent value" instruction is executed. The instruction calculates the size of the angle corresponding to the tangent value at input "Tag_Value". The result of the instruction is stored at output "Tag_Result". If no errors occur during the execution of the instruction, the output "TagOut" is set. See also Overview of the valid data types (Page 1204) Basics of the EN/ENO mechanism (Page 1299) FRAC: Return fraction Description You can use the "Return fraction" instruction to determine the decimal places of the value at the IN input. The result of the query is stored at output OUT and can be queried there. If the input IN has e.g. the value 123.4567, the output OUT has the value 0.4567. Enable output ENO has the signal state "0" if one of the following conditions applies: Enable input EN has the signal state "0". Errors occur during the execution of the instruction, for example there is no valid floatingpoint number at the input. Parameters The following table shows the parameters of the "Return fraction" instruction: Parameters Declaration Data type Memory area S7-1200 S7-1500 Description EN Input BOOL I, Q, M, D, L I, Q, M, D, L, T, C Enable input ENO Output BOOL I, Q, M, D, L I, Q, M, D, L Enable output IN Input Floating-point numbers I, Q, M, D, L, P or constant I, Q, M, D, L, P or constant Input value, whose decimal places are to be determined. OUT Output Floating-point numbers I, Q, M, D, L, P I, Q, M, D, L, P Decimal places of the input value at input IN You can select the data type of the instruction from the "<???>" drop-down list of the instruction box. WinCC Basic V13.0 System Manual, 02/2014 2157 Programming the PLC 9.7 References For additional information on valid data types, refer to "See also". Example The following example shows how the instruction works: 7DJ,QB 7DJ,QB 7DJB9DOXH )5$& 5($/ (1 287 ,1 (12 7DJB5HVXOW 7DJ2XW The following table shows how the instruction works using specific operand values: Parameters Operand Value IN Tag_Value 2.555 OUT Tag_Result 0.555 If the operands "TagIn_1" and "TagIn_2" have signal state "1", the "Return fraction" instruction is executed. The decimal places from the value at the operand "Tag_Value" are copied to the operand "Tag_Result". If the instruction is executed without errors, the ENO enable output has the signal state "1" and the "TagOut" output is set. See also Overview of the valid data types (Page 1204) Basics of the EN/ENO mechanism (Page 1299) Adding additional inputs and outputs to FBD elements (Page 1469) EXPT: Exponentiate Description You can use the "Exponentiate" instruction to raise the value at the input IN1 by a power specified with the value at input IN2. The result of the instruction is stored at output OUT and can be queried there (OUT = IN1IN2). The value at input IN1 must be a valid floating-point number. Integers are also allowed for setting the input IN2. Enable output ENO has the signal state "0" if one of the following conditions applies: Enable input EN has the signal state "0". Errors occur during the instruction processing, for example, if there is an overflow. 2158 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameters The following table shows the parameters of the instruction "Exponentiate": Parameters Declaration Data type Memory area S7-1200 S7-1500 Description EN Input BOOL I, Q, M, D, L I, Q, M, D, L, T, C Enable input ENO Output BOOL I, Q, M, D, L I, Q, M, D, L Enable output IN1 Input Floating-point numbers I, Q, M, D, L, P or constant I, Q, M, D, L, P or constant Base value IN2 Input Integers, floating-point numbers I, Q, M, D, L, P or constant I, Q, M, D, L, P or constant Value with which the base value is exponentiated OUT Output Floating-point numbers I, Q, M, D, L, P I, Q, M, D, L, P Result You can select the data type of the instruction from the "<???>" drop-down list of the instruction box. For additional information on valid data types, refer to "See also". Example The following example shows how the instruction works: 7DJ,QB 7DJ,QB 5($/ (;37 5($/ (1 7DJB9DOXH ,1 287 7DJB9DOXH ,1 (12 7DJB5HVXOW 7DJ2XW If the operands "TagIn_1" and "TagIn_2" have signal state "1", the "Exponentiate" instruction is executed. The value of operand "Tag_Value1" is raised by the power of the value of the operand "Tag_Value2". The result is stored at output "Tag_Result". If the instruction is executed without errors, the ENO enable output has the signal state "1" and the "TagOut" output is set. See also Overview of the valid data types (Page 1204) Basics of the EN/ENO mechanism (Page 1299) Adding additional inputs and outputs to FBD elements (Page 1469) WinCC Basic V13.0 System Manual, 02/2014 2159 Programming the PLC 9.7 References Move operations MOVE: Move value Description You use the "Move value" instruction to transfer the content of the operand at the IN input to the operand at the OUT1 output. The transfer is always made in the direction of ascending address. The ENO enable output has the signal state "0" if one of the following conditions is fulfilled: The EN enable input has the signal state "0". The data type at the IN parameter does not correspond to the specified data type at the OUT1 parameter. The following table lists the possible transfers for the S7-1200 CPU series: Source (IN) 2160 Destination (OUT1) With IEC check Without IEC check BYTE BYTE, WORD, DWORD BYTE, WORD, DWORD, SINT, USINT, INT, UINT, DINT, UDINT, TIME, DATE ,TOD, CHAR WORD WORD, DWORD BYTE, WORD, DWORD, SINT, USINT, INT, UINT, DINT, UDINT, TIME, DATE, TOD, CHAR DWORD DWORD BYTE, WORD, DWORD, SINT, USINT, INT, UINT, DINT, UDINT, REAL, TIME, DATE, TOD, CHAR SINT SINT BYTE, WORD, DWORD, SINT, USINT, INT, UINT, DINT, UDINT, TIME, DATE, TOD USINT USINT, UINT, UDINT BYTE, WORD, DWORD, SINT, USINT, INT, UINT, DINT, UDINT, TIME, DATE, TOD INT INT BYTE, WORD, DWORD, SINT, USINT, INT, UINT, DINT, UDINT, TIME, DATE, TOD UINT UINT, UDINT BYTE, WORD, DWORD, SINT, USINT, INT, UINT, DINT, UDINT, TIME, DATE, TOD DINT DINT BYTE, WORD, DWORD, SINT, USINT, INT, UINT, DINT, UDINT, TIME, DATE, TOD UDINT UDINT BYTE, WORD, DWORD, SINT, USINT, INT, UINT, DINT, UDINT, TIME, DATE, TOD REAL REAL DWORD, REAL LREAL LREAL LREAL TIME TIME BYTE, WORD, DWORD, SINT, USINT, INT, UINT, DINT, UDINT, TIME DATE DATE BYTE, WORD, DWORD, SINT, USINT, INT, UINT, DINT, UDINT, DATE TOD TOD BYTE, WORD, DWORD, SINT, USINT, INT, UINT, DINT, UDINT, TOD DTL DTL DTL CHAR CHAR BYTE, WORD, DWORD, CHAR, Character of a string1) WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Source (IN) Destination (OUT1) With IEC check Without IEC check Character of a string1) Character of a string Character of a string CHAR ARRAY2) ARRAY ARRAY STRUCT STRUCT STRUCT PLC data type (UDT) PLC data type (UDT) PLC data type (UDT) IEC_TIMER IEC_TIMER IEC_TIMER IEC_SCOUNTE IEC_SCOUNTER R IEC_SCOUNTER IEC_USCOUNT IEC_USCOUNTER ER IEC_USCOUNTER IEC_COUNTER IEC_COUNTER IEC_COUNTER IEC_UCOUNTE IEC_UCOUNTER R IEC_UCOUNTER IEC_DCOUNTE IEC_DCOUNTER R IEC_DCOUNTER IEC_UDCOUN TER IEC_UDCOUNTER IEC_UDCOUNTER The following table lists the possible transfers for the S7-1500 CPU series: Source (IN) WinCC Basic V13.0 System Manual, 02/2014 Destination (OUT1) With IEC check Without IEC check BYTE BYTE, WORD, DWORD, LWORD BYTE, WORD, DWORD, LWORD, SINT, USINT, INT, UINT, DINT, UDINT, LINT, ULINT, TIME, LTIME, LDT, DATE ,TOD, LTOD, CHAR WORD WORD, DWORD, LWORD BYTE, WORD, DWORD, LWORD, SINT, USINT, INT, UINT, DINT, UDINT, LINT, ULINT, S5TIME, TIME, LTIME, LDT, DATE, TOD, LTOD, CHAR DWORD DWORD, LWORD BYTE, WORD, DWORD, LWORD, SINT, USINT, INT, UINT, DINT, UDINT, LINT, ULINT, REAL, TIME, LTIME, LDT, DATE, TOD, LTOD, CHAR LWORD LWORD BYTE, WORD, DWORD, LWORD, SINT, USINT, INT, UINT, DINT, UDINT, LINT, ULINT, LREAL, TIME, LTIME, LDT, DATE, TOD, LTOD, CHAR SINT SINT BYTE, WORD, DWORD, LWORD, SINT, USINT, INT, UINT, DINT, UDINT, LINT, ULINT, TIME, LTIME, LDT, DATE, TOD, LTOD USINT USINT, UINT, UDINT, ULINT BYTE, WORD, DWORD, LWORD, SINT, USINT, INT, UINT, DINT, UDINT, LINT, ULINT, TIME, LTIME, LDT, DATE, TOD, LTOD INT INT BYTE, WORD, DWORD, LWORD, SINT, USINT, INT, UINT, DINT, UDINT, LINT, ULINT, TIME, LTIME, LDT, DATE, TOD, LTOD UINT UINT, UDINT, ULINT BYTE, WORD, DWORD, LWORD, SINT, USINT, INT, UINT, DINT, UDINT, LINT, ULINT, TIME, LTIME, LDT, DATE, TOD. LTOD 2161 Programming the PLC 9.7 References Source (IN) Destination (OUT1) With IEC check Without IEC check DINT DINT BYTE, WORD, DWORD, LWORD, SINT, USINT, INT, UINT, DINT, UDINT, LINT, ULINT, TIME, LTIME, LDT, DATE, TOD, LTOD UDINT UDINT, ULINT BYTE, WORD, DWORD, LWORD, SINT, USINT, INT, UINT, DINT, UDINT, LINT, ULINT, TIME, LTIME, LDT, DATE, TOD, LTOD LINT LINT BYTE, WORD, DWORD, LWORD, SINT, USINT, INT, UINT, DINT, UDINT, LINT, ULINT, TIME, LTIME, LDT, DATE, TOD, LTOD ULINT ULINT BYTE, WORD, DWORD, LWORD, SINT, USINT, INT, UINT, DINT, UDINT, LINT, ULINT, TIME, LTIME, LDT, DATE, TOD, LTOD REAL REAL DWORD, REAL LREAL LREAL LWORD, LREAL S5TIME S5TIME WORD, S5TIME TIME TIME BYTE, WORD, DWORD, LWORD, SINT, USINT, INT, UINT, DINT, UDINT, LINT, ULINT, TIME LTIME LTIME BYTE, WORD, DWORD, LWORD, SINT, USINT, INT, UINT, DINT, UDINT, LINT, ULINT, LTIME DATE DATE BYTE, WORD, DWORD, LWORD, SINT, USINT, INT, UINT, DINT, UDINT, LINT, ULINT, DATE DT DT DT LDT LDT BYTE, WORD, DWORD, LWORD, SINT, USINT, INT, UINT, DINT, UDINT, LINT, ULINT, LDT TOD TOD BYTE, WORD, DWORD, LWORD, SINT, USINT, INT, UINT, DINT, UDINT, LINT, ULINT, TOD LTOD LTOD BYTE, WORD, DWORD, LWORD, SINT, USINT, INT, UINT, DINT, UDINT, LINT, ULINT, LTOD DTL DTL DTL CHAR CHAR BYTE, WORD, DWORD, LWORD, CHAR, Character of a string1) WCHAR WCHAR BYTE, WORD, DWORD, LWORD, CHAR, WCHAR, Character of a string1) Character of a string1) Character of a string CHAR, WCHAR, Character of a string ARRAY2) ARRAY ARRAY STRUCT STRUCT STRUCT COUNTER COUNTER, WORD, INT WORD, DWORD, INT, UINT, DINT, UDINT TIMER TIMER, WORD, INT WORD, DWORD, INT, UINT, DINT, UDINT PLC data type (UDT) PLC data type (UDT) PLC data type (UDT) IEC_TIMER IEC_TIMER IEC_TIMER IEC_LTIMER IEC_LTIMER IEC_LTIMER IEC_SCOUNTE IEC_SCOUNTER R 2162 IEC_SCOUNTER WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Source (IN) Destination (OUT1) With IEC check Without IEC check IEC_USCOUNT IEC_USCOUNTER ER IEC_USCOUNTER IEC_COUNTER IEC_COUNTER IEC_COUNTER IEC_UCOUNTE IEC_UCOUNTER R IEC_UCOUNTER IEC_DCOUNTE IEC_DCOUNTER R IEC_DCOUNTER IEC_UDCOUN TER IEC_UDCOUNTER IEC_UDCOUNTER IEC_LCOUNTE R IEC_LCOUNTER IEC_LCOUNTER IEC_ULCOUNT IEC_ULCOUNTER ER IEC_ULCOUNTER You can also use the "Move value" instruction to transfer individual characters of a string to operands of the CHAR or WCHAR data type. The number of the character to be transferred is specified in square brackets next to the operand name. "MyString[2]", for example, transfers the second character of the "MyString" string. It is also possible to transfer from operands of the data type CHAR to the individual characters of a string. You can also replace a specific character of a string with the character of another string. 1) Transferring entire arrays (ARRAY) is possible only when the array components of the operands at input IN and at output OUT1 are of the same data type. 2) If the bit length of the data type at input IN exceeds the bit length of the data type at output OUT1, the higher-order bits of the source value are lost. If the bit length of the data type at input IN is less than the bit length of the data type at output OUT1, the higher-order bits of the destination value will be overwritten with zeros. In its initial state, the instruction box contains 1 output (OUT1). The number of outputs can be extended. The added outputs are numbered in ascending order on the box. During the execution of the instruction, the content of the operand at the input IN is transferred to all available outputs. The instruction box cannot be extended if structured data types (DTL, STRUCT, ARRAY) or characters of a string are transferred. You can also use the "Move block" (MOVE_BLK) and "Move block uninterruptible" (UMOVE_BLK) instructions to move operands of the ARRAY data type. You can move operands of the STRING data type with the instruction "Move character string" (S_MOVE). Parameters The following table lists the parameters of the "Move value" instruction: Parameters WinCC Basic V13.0 System Manual, 02/2014 Declaration Data type Memory area S7-1200 S7-1500 S7-1200 S7-1500 Description EN Input BOOL BOOL I, Q, M, D, L I, Q, M, D, L, T, C Enable input ENO Output BOOL BOOL I, Q, M, D, L I, Q, M, D, L Enable output 2163 Programming the PLC 9.7 References Parameters Declaration Data type Memory area Description S7-1200 S7-1500 S7-1200 S7-1500 IN Input Bit strings, integers, floatingpoint numbers, DATE, TIME, TOD, DTL, CHAR, STRUCT, ARRAY, IEC data types, PLC data type (UDT) Bit strings, integers, floatingpoint numbers, DATE, DT, LDT, S5TIME, TIME, LTIME, TOD, LTOD, DTL, CHAR, STRUCT, ARRAY, TIMER, COUNTER, IEC data types, PLC data type (UDT) I, Q, M, D, L or constant I, Q, M, D, L or constant Element used to overwrite the destination address. OUT1 Output Bit strings, integers, floatingpoint numbers, DATE, TIME, TOD, DTL, CHAR, STRUCT, ARRAY, IEC data types, PLC data type (UDT) Bit strings, integers, floatingpoint numbers, DATE, DT, LDT, S5TIME, TIME, LTIME, TOD, LTOD, DTL, CHAR, STRUCT, ARRAY, TIMER, COUNTER, IEC data types, PLC data type (UDT) I, Q, M, D, L I, Q, M, D, L Destination address For additional information on valid data types, refer to "See also". 2164 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Example The following example shows how the instruction works: 029( 7DJ,Q (1 287 ,1 (12 7DJ2XWB9DOXH 7DJ2XW 7DJ,QB9DOXH The following table lists how the instruction works using specific operand values: Parameters Operand Value IN TagIn_Value 0011 1111 1010 1111 OUT1 TagOut_Value 0011 1111 1010 1111 If the operand "TagIn" has the signal state "1", the "Move value" instruction is executed. The instruction copies the content of the "TagIn_Value" operand to the "TagOut_Value" operand. If the instruction is executed without errors, the ENO and "TagOut" enable outputs are set to signal state "1". See also Overview of the valid data types (Page 1204) Basics of the EN/ENO mechanism (Page 1299) Removing instruction inputs and outputs (Page 1470) MOVE_BLK: Move block (Page 2175) UMOVE_BLK: Move block uninterruptible (Page 2181) S_MOVE: Move character string (Page 2521) Adding additional inputs and outputs to FBD elements (Page 1469) Deserialize: Deserialize Description You can use the "Deserialize" instruction to convert the sequential representation of a PLC data type (UDT) back to a PLC data type and to fill its entire contents. The memory area in which the sequential representation of a PLC data type is located must have the ARRAY of BYTE data type and be declared with standard access. Make sure that there is enough memory space prior to the conversion. WinCC Basic V13.0 System Manual, 02/2014 2165 Programming the PLC 9.7 References The instruction enables you to convert multiple sequential representations of converted PLC data types back to their original state step-by-step. Note If you only want to convert back a single sequential representation of a PLC data type (UDT), you can also use the instruction "TRCV: Receive data via communication connection" directly. Parameter The following table shows the parameters of the "Deserialize" instruction: Parameters Declaration Data type Memory area Description EN Input BOOL I, Q, M, D, L Enable input ENO Output BOOL I, Q, M, D, L Enable output SRC_ARRA Y Input VARIANT I, Q, D, L Global data block in which the generated data stream is stored DEST_VARI ABLE InOut VARIANT I, Q, D, L Tag in which the returned converted PLC data type (UDT) is stored POS InOut DINT I, Q, M, D, L Number of bytes that the converted PLC data types use. The POS parameter is calculated zero-based. RET_VAL Output INT I, Q, M, D, L Error information For additional information on valid data types, refer to "See also". RET_VAL parameter The following table shows the meaning of the values of the RET_VAL parameter: Error code* (W#16#...) Explanation 0000 No error 80B0 The memory areas for the SRC_ARRAY and DEST_VARIABLE parameters overlap. 8136 The data block at the DEST_VARIABLE parameter is not a block with standard access. 8150 The VARIANT data type at the SRC_ARRAY parameter contains no value. 8151 Code generation error at SRC_ARRAY parameter 8153 There is not enough free memory available at the SRC_ARRAY parameter. 8250 The VARIANT data type at the DEST_VARIABLE parameter contains no value. 8251 Code generation error at DEST_VARIABLE parameter 8254 Invalid data type at the DEST_VARIABLE parameter 2166 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Error code* (W#16#...) Explanation 8382 The value at the POS parameter is outside the limits of the array. *The error codes can be displayed as integer or hexadecimal value in the program editor. For information on toggling display formats, refer to "See also". Example The following example shows how the instruction works: Network 1: 029( 'HVHULDOL]H (1 (12 ,1 287 (12 (1 %XIIHU3RV %XIIHU)LHOG %XIIHU3RV 5(7B9$/ 65&B$55$< '(67B9$5,$%/( 326 (UURU 7DUJHW&OLHQW The "Move value" instruction moves the value "0" to the "#BufferPos" operand. The "Deserialize" instruction deserializes the sequential representation of the customer data from the "Buffer" data block and writes it to the "Target" data block. The number of bytes used by the converted customer data is stored in the "#BufferPos" operand. Network 2: 'HVHULDOL]H %XIIHU )LHOG %XIIHU3RV (12 (1 65&B$55$< 326 5(7B9$/ (UURU '(67B9$5,$%/( /DEHO 675,1* DUWL /DEHO 'HVHULDOL]H ,1 ,1 %XIIHU)LHOG %XIIHU3RV 675,1* 5HFK /DEHO (12 (1 5(7B9$/ 65&B$55$< '(67B9$5,$%/( 326 'HVHULDOL]H ,1 ,1 (1 %XIIHU)LHOG %XIIHU3RV 65&B$55$< 326 (12 5(7B9$/ '(67B9$5,$%/( The "Deserialize" instruction deserializes the sequential representation of the separator sheet, which was saved with the sequential representation after the customer data, from the "Buffer" data block and writes the characters to the "#Label" operand. The characters are compared using comparison instructions for "arti" and "Bill". If the comparison for "arti" = TRUE, these WinCC Basic V13.0 System Manual, 02/2014 2167 (UURU 7DUJHW %LOO>'HOLY Programming the PLC 9.7 References are article data that have been deserialized and written to the "Target" data block. If the comparison for "Bill" = TRUE, these are billing data that have been deserialized and written to the "Target" data block. The following table shows the declaration of the operands: Operand Data type Declaration DeliverPos INT In the "Input" section of the block interface BufferPos DINT In the "Temp" section of the block interface Error INT In the "Temp" section of the block interface Label STRING[4] In the "Temp" section of the block interface The following table lists the declarations of the PLC data types: Name of the PLC data types Name Data type Article Number DINT Declaration STRING Colli INT Title INT First name STRING[10] Surname STRING[10] Client The following table shows the declaration of the data blocks: Name of the data blocks Name Data type Target Client "Client" (PLC data type) Article Array[0..] of "Article" (PLC data type) Bill Array[0..10] of INT Field Array[0..294] of BYTE Buffer See also Overview of the valid data types (Page 1204) Basics of the EN/ENO mechanism (Page 1299) PLC data types (Page 1248) Serialize: Serialize Description You can use the "Serialize" instruction to convert several PLC data types (UDT) to a sequential representation without losing parts of their structure. You can use the instruction to temporarily save multiple structured data items from your program in a buffer, which should preferably be in a global data block, and send them to another CPU. The memory area in which the converted PLC data types are stored must have the 2168 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References ARRAY of BYTE data type and be declared with standard access. Make sure that there is enough memory space prior to the conversion. The operand at the POS parameter contains information about the number of bytes used by the converted PLC data types. Note If you want to send a single PLC data type (UDT), you can directly call the instruction "TSEND: Send data via communication connection". Parameters The following table shows the parameters of the "Serialize" instruction: Parameters Declarati on Data type Memory area Description EN Input BOOL I, Q, M, D, L Enable input ENO Output BOOL I, Q, M, D, L Enable output SRC_VARI ABLE Input VARIA NT I, Q, D, L PLC data type (UDT) that is converted to sequential representation. DEST_ARR InOut AY VARIA NT I, Q, D, L Data block in which the generated data stream is stored. POS InOut DINT I, Q, M, D, L Number of bytes that the converted PLC data types use. The POS parameter is calculated zero-based. RET_VAL Output INT I, Q, M, D, L Error information For additional information on valid data types, refer to "See also". RET_VAL parameter The following table shows the meaning of the values of the RET_VAL parameter: Error code* (W#16#...) Explanation 0000 No error 80B0 The memory areas for the SRC_VARIABLE and DEST_ARRAY parameters overlap. 8150 The VARIANT data type at the SRC_VARIABLE parameter contains no value. 8152 Code generation error at SRC_VARIABLE parameter 8236 The data block at the DEST_ARRAY parameter is not a block with standard access. 8250 The VARIANT data type at the DEST_ARRAY parameter contains no value. 8252 Code generation error at DEST_ARRAY parameter 8253 There is not enough free memory available at the DEST_ARRAY parameter. WinCC Basic V13.0 System Manual, 02/2014 2169 Programming the PLC 9.7 References Error code* (W#16#...) Explanation 8254 Invalid data type at the DEST_ARRAY parameter 8382 The value at the POS parameter is outside the limits of the array. *The error codes can be displayed as integer or hexadecimal value in the program editor. For information on toggling display formats, refer to "See also". Example The following example shows how the instruction works: Network 1: 029( 6HULDOL]H (1 (12 ,1 287 (12 (1 %XIIHU3RV 6RXUFH&OLHQW 5(7B9$/ 65&B9$5,$%/( '(67B$55$< 326 %XIIHU3RV (UURU %XIIHU)LHOG The "Move value" instruction moves the value "0" to the "#BufferPos" operand. The "Serialize" instruction serializes the customer data from the "Source" data block and writes them in sequential representation to the "Buffer" data block. The number of bytes used by the sequential representation is stored in the "#BufferPos" operand. Network 2: 6B029( DUWL (1 (12 ,1 287 6HULDOL]H (12 (1 /DEHO /DEHO %XIIHU3RV 65&B9$5,$%/( 326 5(7B9$/ '(67B$55$< (UURU %XIIHU)LHOG A kind of separator sheet is inserted now to make it easier to deserialize the sequential representation later. The "Move character string" instruction moves the "arti" characters to the "#Label" operand. The "Serialize" instruction writes these characters after the customer data to the "Buffer" data block. The number of bytes that the characters need is added to the number already stored in the "#BufferPos" operand. Network 3: 6HULDOL]H (1 6RXUFH $UWLFOH>'HOLYHU3RV@ %XIIHU3RV 65&B9$5,$%/( 326 (12 5(7B9$/ '(67B$55$< (UURU %XIIHU)LHOG The "Serialize" instruction serializes the data of a specific article, which is calculated in runtime, from the "Source" data block and writes them in sequential representation to the "Buffer" data block after the "arti" characters. 2170 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References The following table shows the declaration of the operands: Operand Data type Declaration DeliverPos INT In the "Input" section of the block interface BufferPos DINT In the "Temp" section of the block interface Error INT In the "Temp" section of the block interface Label STRING[4] In the "Temp" section of the block interface The following table lists the declarations of the PLC data types: Name of the PLC data types Name Data type Article Number DINT Declaration STRING Colli INT Title INT First name STRING[10] Surname STRING[10] Client The following table shows the declaration of the data blocks: Name of the data blocks Name Data type Source Client "Client" (PLC data type) Article Array[0..10] of "Article" (PLC data type) Field Array[0..294] of BYTE Buffer See also Overview of the valid data types (Page 1204) Basics of the EN/ENO mechanism (Page 1299) PLC data types (Page 1248) FieldRead: Read field Description You can use the "Read field" instruction to read out a specific component from the field specified in the MEMBER parameter and transfer its content to the tag in the VALUE parameter. You use the parameter INDEX to define the index of the field components that are to be read. At the parameter MEMBER you specify the first component of the field to be read. The data types of the field component at parameter MEMBER and the tags at parameter VALUE must correspond to the data type of the instruction "Read field". Enable output ENO has the signal state "0" if one of the following conditions applies: WinCC Basic V13.0 System Manual, 02/2014 2171 Programming the PLC 9.7 References Enable input EN has the signal state "0". The field component specified at the parameter INDEX is not defined in the field specified at the parameter MEMBER. Errors, such as an overflow, occur during execution. Parameters The following table shows the parameters of the instruction "Read field": Parameters Declaration Data type Memory area Description S7-1200 S7-1500 S7-1200 S7-1500 EN Input BOOL BOOL I, Q, M, D, L I, Q, M, D, L, T, C Enable input ENO Output BOOL BOOL I, Q, M, D, L I, Q, M, D, L Enable output INDEX Input DINT DINT I, Q, M, D, L, P or constant I, Q, M, D, L, P or constant Index of field components whose content is read out MEMBER Input Binary numbers, integers, floatingpoint numbers, TIME, DATE, TOD and CHAR as components of an ARRAY tag Binary numbers, integers, floatingpoint numbers, timers, DATE, TOD, LTOD and CHAR as components of an ARRAY tag D, L D, L First component of the field from which will be read VALUE Output Bit strings, integers, floatingpoint numbers, TIME, DATE, TOD and CHAR Bit strings, integers, floatingpoint numbers, timers, DATE, TOD, LTOD and CHAR I, Q, M, D, L, P I, Q, M, D, L, P Operand to which the contents of the field component are transferred. You can select the data type of the instruction from the "<???>" drop-down list of the instruction box. For additional information on valid data types, refer to "See also". 2172 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Example The following example shows how the instruction works: )LHOG5HDG 5($/ 7DJ,Q DBLQGH[ '%B 0DLQB)LHOG>@ (1 ,1'(; 0(0%(5 9$/8( (12 DBUHDO 7DJ2XW The following table shows how the instruction works using specific operand values: Parameters Tag Value INDEX a_index 4 MEMBER "DB_1".Main_Field[-10] First component of the field "Main_Field[-10..10] of REAL" in the data block "DB_1" VALUE a_real Component with Index 4 of the field "Main_Field[-10..10] of REAL" The field component with index 4 is read out from the field "Main_Field[-10...10] of REAL" and written to the tag "a_real". The field component to be read is defined by the value at the parameter INDEX. See also Overview of the valid data types (Page 1204) Basics of the EN/ENO mechanism (Page 1299) FieldWrite: Write field Description The "Write field" instruction is used to transfer the content of the tag at the VALUE input to a specific component of the field at the MEMBER output. You use the value at the INDEX input to specify the index of the field component that is described. At the MEMBER output, enter the first component of the field which is to be written to. The data types of the field component specified at the MEMBER output and the tags at the VALUE input have to match the data type of the "Write field" instruction. Enable output ENO has the signal state "0" if one of the following conditions applies: Enable input EN has the signal state "0". The field component specified at the input INDEX is not defined in the field specified at the output MEMBER. Errors, such as an overflow, occur during execution. WinCC Basic V13.0 System Manual, 02/2014 2173 Programming the PLC 9.7 References Parameters The following table shows the parameters of the instruction "Write field": Parameters Declaration Data type Memory area Description S7-1200 S7-1500 S7-1200 S7-1500 EN Input BOOL BOOL I, Q, M, D, L I, Q, M, D, L, T, C Enable input ENO Output BOOL BOOL I, Q, M, D, L I, Q, M, D, L Enable output INDEX Input DINT DINT I, Q, M, D, L, P or constant I, Q, M, D, L, P or constant Index of field component that is written with the content of VALUE VALUE Input Bit strings, integers, floatingpoint numbers, TIME, DATE, TOD and CHAR Bit strings, integers, floatingpoint numbers, timers, DATE, TOD, LTOD and CHAR I, Q, M, D, L, P or constant I, Q, M, D, L, P or constant Operand whose contents are copied MEMBER Output Binary numbers, integers, floatingpoint numbers, TIME, DATE, TOD and CHAR as components of an ARRAY tag Binary numbers, integers, floatingpoint numbers, timers, DATE, TOD, LTOD and CHAR as components of an ARRAY tag D, L D, L First component of the field to which the content of VALUE is written. You can select the data type of the instruction from the "<???>" drop-down list of the instruction box. For additional information on valid data types, refer to "See also". 2174 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Example The following example shows how the instruction works: )LHOG:ULWH 5($/ 7DJ,Q (1 DBLQGH[ ,1'(; 0(0%(5 DBUHDO 9$/8( (12 '%B 0DLQB)LHOG>@ 7DJ2XW The following table shows how the instruction works using specific operand values: Parameters Operand Value INDEX a_index 4 VALUE a_real 10.54 MEMBER "DB_1".Main_Field[-10] First component of the field "Main_Field[-10..10] of REAL" in the data block "DB_1" The value "10.54" of the "a_real" tag is written to the field component with index 4 of the "Main_Field[-10 ... 10] of REAL" field. The index of the field component to which the content of the tag "a_real" is transferred is specified by the value at the input INDEX. See also Overview of the valid data types (Page 1204) Basics of the EN/ENO mechanism (Page 1299) MOVE_BLK: Move block Description You can use the "Move block" instruction to move the content of a memory area (source area) to another memory area (destination area). The number of elements to be moved to the destination area is specified with the COUNT parameter. The width of the elements to be moved is defined by the width of the element at input IN. The instruction can only be executed if the source area and the destination area are of the same data type. The ENO enable output has the signal state "0" if one of the following conditions is fulfilled: The EN enable input has the signal state "0". More data is moved than is made available at input IN or output OUT. When a Array of BOOL is copied, the enable output ENO for an overflow is set to "1" until the byte limit of the Array structure is exceeded. If the byte limit of the Array structure is exceeded by the value at the COUNT input, the ENO enable output is reset to "0". WinCC Basic V13.0 System Manual, 02/2014 2175 Programming the PLC 9.7 References Parameters The following table lists the parameters of the "Move block" instruction: Parameter Declaration Data type Memory area Description S7-1200 S7-1500 S7-1200 S7-1500 EN Input BOOL BOOL I, Q, M, D, L I, Q, M, D, L, T, C Enable input ENO Output BOOL BOOL I, Q, M, D, L I, Q, M, D, L Enable output IN 1) Input Binary numbers, integers, floatingpoint numbers, TIME, DATE, CHAR, TOD Binary numbers, integers, floatingpoint numbers, timers, DATE, CHAR, TOD, LTOD D, L D, L The first element of the source area that is being copied COUNT Input USINT, UINT, UDINT USINT, UINT, UDINT, ULINT I, Q, M, D, L, I, Q, M, D, L, Number of P or constant P or constant elements to be copied from the source area to the destination area OUT 1) Output Binary numbers, integers, floatingpoint numbers, TIME, DATE, CHAR, TOD Binary numbers, integers, floatingpoint numbers, timers, DATE, CHAR, TOD, LTOD D, L 1) D, L The first element of the destination area to which the contents of the source area are being copied The specified data types can only be used as elements of an Array structure. For additional information on valid data types, refer to "See also". 2176 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Example The following example shows how the instruction works: 7DJ,QB 7DJ,QB DBDUUD\>@ 029(B%/. (1 ,1 287 EBDUUD\>@ 7DJ2XW 7DJB&RXQW &2817 (12 The following table shows how the instruction works using specific operand values: Parameter Operand Value IN a_array[2] The data type of the a_array operand is Array [0..5] of INT. It consists of six elements of data type INT. COUNT Tag_Count 3 OUT b_array[1] The data type of the b_array operand is Array [0..6] of INT. It consists of seven elements of data type INT. If the operands "TagIn_1" and "TagIn_2" have signal state "1", the "Move block" instruction is executed. Starting from the third element, the instruction selects three INT elements from the #a_array tag and copies their contents to the #b_array output tag, beginning with the second element. If the instruction is executed without errors, the ENO enable output has the signal state "1" and the "TagOut" output is set. See also Overview of the valid data types (Page 1204) Basics of the EN/ENO mechanism (Page 1299) MOVE_BLK_VARIANT: Move block Description You can use the "Move block" instruction to move the content of a memory area (source area) to another memory area (destination area). You can copy elements of an array to another array of the same data type. The size (number of elements) of the source and destination array may be different. You can copy several elements within an array or individual elements. If you are using the instruction, the array must not yet be known at the time the block is created, as the source and the destination are transferred using VARIANT. WinCC Basic V13.0 System Manual, 02/2014 2177 Programming the PLC 9.7 References The counting at the parameters SRC_INDEX and DEST_INDEX always starts with the low limit "0", regardless of the later declaration of the array. If the VARIANT pointer (source or destination) is of the data type BOOL, it must be addressed absolutely and the length specified must be divisible by 8; otherwise the instruction is not executed. The ENO enable output has the signal state "0" if one of the following conditions is fulfilled: The EN enable input has the signal state "0". More data is copied than is made available. Parameters The following table shows the parameters of the "Move block" instruction: Parameter Declaration Data type Memory area Description EN Input BOOL I, Q, M, D, L Enable input ENO Output BOOL I, Q, M, D, L Enable output SRC Input VARIANT (array or single element) L Source block from which to copy COUNT Input UDINT I, Q, M, D, L or constant Number of elements which are copied Set the value at the parameter COUNT to "1", if no Array is specified at the parameter SRC or the parameter DEST. 2178 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameter Declaration Data type Memory area SRC_INDEX Input DINT I, Q, M, D, L or constant The SRC_INDEX parameter is calculated zerobased. If an Array is specified at parameter SRC, the integer at the SRC_INDEX parameter specifies the first element within the source area from which copying is to take place. This is independent of the declared array limits. Description If no Array is set at the SRC parameter or only an individual element of an array is specified, assign the SRC_INDEX parameter the value "0". DEST_INDEX Input DINT I, Q, M, D, L or constant The DEST_INDEX parameter is calculated zerobased. If an Array is specified at the DEST parameter, the integer at the DEST_INDEX parameter specifies the first element within the destination area to which copying is to take place. This is independent of the declared array limits. If no Array is specified at the DEST parameter, assign the DEST_INDEX parameter the value "0". WinCC Basic V13.0 System Manual, 02/2014 2179 Programming the PLC 9.7 References Parameter Declaration Data type Memory area Description DEST Output VARIANT L Destination area into which the contents of the source block are copied. RET_VAL Output INT I, Q, M, D, L Error information: If an error occurs during the execution of the instruction, an error code is output at the RET_VAL parameter. For additional information on valid data types, refer to "See also". RET_VAL parameter The following table shows the meaning of the values of the RET_VAL parameter: Error code* Explanation (W#16#...) 0000 No error 80B4 Data types do not correspond 8151 Access to the SRC parameter is not possible. 8152 The operand at the SRC parameter is not typed. 8153 Code generation error at SRC parameter 8154 The operand at the SRC parameter has the data type BOOL. 8281 The COUNT parameter has an invalid value 8382 The value at the SRC_INDEX parameter is outside the limits of the VARIANT. 8383 The value at the SRC_INDEX parameter is outside the high limit of the array. 8482 The value at the DEST_INDEX parameter is outside the limits of the VARIANT. 8483 The value at the DEST_INDEX parameter is outside the high limit of the array. 8534 The DEST parameter is write protected 8551 Access to the DEST parameter is not possible. 8552 The operand at the DEST parameter is not typed. 8553 Code generation error at DEST parameter 8554 The operand at the DEST parameter has the data type BOOL. *The error codes can be displayed as integer or hexadecimal value in the program editor. For information on toggling display formats, refer to "See also". 2180 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Example The following example shows how the instruction works: 029(B%/.B9$5,$17 7DJ,Q 6UF)LHOG 7DJB&RXQW (1 (12 7DJ2XW 65& &2817 5(7B9$/ 7DJB6UFB,QGH[ 65&B,1'(; '(67 7DJB'HVWB,QGH[ '(67B,1'(; 7DJB5HVXOW 'HVW)LHOG The following table shows how the instruction works using specific operand values: Parameter Operand Value SRC #SrcField The local operand #SrcField uses a UDT that was still unknown at the time when the block was programmed. (Array [0 to 10] of "MOVE_UDT" COUNT Tag_Count 2 SRC_INDEX Tag_Src_Index 3 DEST_INDEX Tag_Dest_Index 3 DEST #DestField The local operand #DestField uses a UDT that was still unknown at the time when the block was programmed. (Array [10 to 20] of "MOVE_UDT" If the operand "TagIn" has the signal state "1", the "Move block" instruction is executed. 2 elements are copied from the source area into the destination area beginning with the fourth element of the array of UDT. The copies are inserted in the array of UDT beginning with the fourth element. If the instruction is executed without errors, the ENO enable output has the signal state "1" and the "TagOut" output is set. See also Overview of the valid data types (Page 1204) Basics of the EN/ENO mechanism (Page 1299) VariantGet: Read out VARIANT tag value (Page 2201) UMOVE_BLK: Move block uninterruptible Description You can use the "Move block uninterruptible" instruction to move the content of a memory area (source area) to another memory area (destination area). The number of elements to be moved WinCC Basic V13.0 System Manual, 02/2014 2181 Programming the PLC 9.7 References to the destination area is specified with the COUNT parameter. The width of the elements to be moved is defined by the width of the element at input IN. The instruction can only be executed if the source area and the destination area have the same data type. Note The move operation cannot be interrupted by other operating system activities. This is why the alarm reaction times of the CPU increase during the execution of the "Move block uninterruptible" instruction. The ENO enable output has the signal state "0" if one of the following conditions is fulfilled: The EN enable input has the signal state "0". More data is moved than is made available at input IN or output OUT. When a Array of BOOL is copied, the enable output ENO for an overflow is set to "1" until the byte limit of the Array structure is exceeded. If the byte limit of the Array structure is exceeded by the value at the COUNT input, the ENO enable output is reset to "0". You can use the "Move block uninterruptible" instruction to move a maximum of 16 KB. Note the CPU-specific restrictions for this. Parameters The following table shows the parameters of the "Move block uninterruptible" instruction: Parameter 2182 Declaration Data type Memory area Description S7-1200 S7-1500 S7-1200 S7-1500 EN Input BOOL BOOL I, Q, M, D, L I, Q, M, D, L, T, C Enable input ENO Output BOOL BOOL I, Q, M, D, L I, Q, M, D, L Enable output IN 1) Input Binary numbers, integers, floatingpoint numbers, TIME, DATE, CHAR, TOD Binary numbers, integers, floatingpoint numbers, timers, DATE, CHAR, TOD, LTOD D, L D, L The first element of the source area that is being copied COUNT Input USINT, UINT, UDINT USINT, UINT, UDINT, ULINT I, Q, M, D, L, I, Q, M, D, L, Number of P or constant P or constant elements to be copied from the source area to the destination area WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameter OUT 1) 1) Declaration Output Data type Memory area S7-1200 S7-1500 S7-1200 S7-1500 Binary numbers, integers, floatingpoint numbers, TIME, DATE, CHAR, TOD Binary numbers, integers, floatingpoint numbers, timers, DATE, CHAR, TOD, LTOD D, L D, L Description The first element of the destination area to which the contents of the source area are being copied The specified data types can only be used as elements of an array structure. For additional information on valid data types, refer to "See also". Example The following example shows how the instruction works: 7DJ,QB 7DJ,QB DBDUUD\>@ 8029(B%/. (1 ,1 287 EBDUUD\>@ 7DJ2XW 7DJB&RXQW &2817 (12 The following table shows how the instruction works using specific operand values: Parameter Operand Value IN a_array[2] The data type of the a_array operand is Array [0..5] of INT. It consists of six elements of data type INT. COUNT Tag_Count 3 OUT b_array[1] The data type of the b_array operand is Array [0..6] of INT. It consists of seven elements of data type INT. If the operands "TagIn_1" and "TagIn_2" have signal state "1", the "Move block uninterruptible" instruction is executed. Starting from the third element, the instruction selects three INT elements from the #a_array tag and copies their contents to the #b_array output tag, beginning with the second element. The move operation cannot be interrupted by other operating system activities. If the instruction is executed without errors, the ENO enable output has the signal state "1" and the "TagOut" output is set. WinCC Basic V13.0 System Manual, 02/2014 2183 Programming the PLC 9.7 References See also Overview of the valid data types (Page 1204) Basics of the EN/ENO mechanism (Page 1299) FILL_BLK: Fill block Description You can use the "Fill block" instruction to fill a memory area (destination area) with the value of input IN. The destination area is filled beginning with the address specified at the OUT output. The number of repeated move operations is specified with the COUNT parameter. When the instruction is executed, the value at the input IN is selected and moved to the destination area as often as specified by the value of the COUNT parameter. The instruction can only be executed if the source area and the destination area are of the same data type. The ENO enable output has the signal state "0" if one of the following conditions is fulfilled: The EN enable input has the signal state "0". More data is moved than is made available at input IN or output OUT. When a Array of BOOL is copied, the enable output ENO for an overflow is set to "1" until the byte limit of the Array structure is exceeded. If the byte limit of the Array structure is exceeded by the value at the COUNT input, the ENO enable output is reset to "0". Parameters The following table shows the parameters of the "Fill block" instruction: Parameter 2184 Declaration Data type Memory area Description S7-1200 S7-1500 S7-1200 S7-1500 EN Input BOOL BOOL I, Q, M, D, L I, Q, M, D, L, T, C Enable input ENO Output BOOL BOOL I, Q, M, D, L I, Q, M, D, L Enable output IN 1) Input Binary numbers, integers, floatingpoint numbers, TIME, DATE, TOD, CHAR Binary numbers, integers, floatingpoint numbers, timers, DATE, CHAR, TOD, LTOD I, Q, M, D, L, I, Q, M, D, L, Element P or constant P or constant used to fill the destination area COUNT Input USINT, UINT, UDINT USINT, UINT, UDINT, ULINT I, Q, M, D, L, I, Q, M, D, L, Number of P or constant P or constant repeated move operations WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameter OUT 2) Declaration Output Data type Memory area S7-1200 S7-1500 S7-1200 S7-1500 Binary numbers, integers, floatingpoint numbers, TIME, DATE, TOD, CHAR Binary numbers, integers, floatingpoint numbers, timers, DATE, CHAR, TOD, LTOD D, L D, L 1) The specified data types can also be used as elements of an Array structure. 2) The specified data types can only be used as elements of an Array structure. Description Address in destination area from which filling starts. For additional information on valid data types, refer to "See also". Example The following example shows how the instruction works: 7DJ,QB 7DJ,QB DBDUUD\>@ ),//B%/. (1 ,1 287 EBDUUD\>@ 7DJ2XW 7DJB&RXQW &2817 (12 The following table shows how the instruction works using specific operand values: Parameter Operand Value IN a_array[2] The data type of the a_array operand is Array [0..5] of INT. It consists of six elements of data type INT. COUNT Tag_Count 3 OUT b_array[1] The data type of the b_array operand is Array [0..6] of INT. It consists of seven elements of data type INT. If the operands "TagIn_1" and "TagIn_2" have signal state "1", the "Fill block" instruction is executed. The instruction copies the third element (#a_array[2]) of the #a_array tag three times to the #b_array output tag. If no errors occur during the execution of the instruction, the outputs ENO and "TagOut" are set to signal state "1". WinCC Basic V13.0 System Manual, 02/2014 2185 Programming the PLC 9.7 References See also Overview of the valid data types (Page 1204) Basics of the EN/ENO mechanism (Page 1299) UFILL_BLK: Fill block uninterruptible Description You can use the instruction "Fill block uninterruptible" to fill a memory area (destination area) with the value of input IN uninterruptibly. The destination area is filled beginning with the address specified at the OUT output. The number of repeated move operations is specified with the COUNT parameter. When the instruction is executed, the value at the input IN is selected and moved to the destination area as often as specified by the value of the COUNT parameter. The instruction can only be executed if the source area and the destination area have the same data type. Note The move operation cannot be interrupted by other operating system activities. This is why the alarm reaction times of the CPU increase during the execution of the "Fill block uninterruptible" instruction. The ENO enable output has the signal state "0" if one of the following conditions is fulfilled: The EN enable input has the signal state "0". More data is moved than is made available at input IN or output OUT. When a Array of BOOL is copied, the enable output ENO for an overflow is set to "1" until the byte limit of the Array structure is exceeded. If the byte limit of the Array structure is exceeded by the value at the COUNT input, the ENO enable output is reset to "0". You can use the "Fill block uninterruptible" instruction to move a maximum of 16 KB. Note the CPU-specific restrictions for this. Parameters The following table shows the parameters of the "Fill block uninterruptible" instruction: Parameter 2186 Declaration Data type Memory area Description S7-1200 S7-1500 S7-1200 S7-1500 EN Input BOOL BOOL I, Q, M, D, L I, Q, M, D, L, T, C Enable input ENO Output BOOL BOOL I, Q, M, D, L I, Q, M, D, L Enable output WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameter Declaration Data type Memory area S7-1200 S7-1500 S7-1200 Description S7-1500 IN 1) Input Binary numbers, integers, floatingpoint numbers, TIME, DATE, CHAR, TOD Binary numbers, integers, floatingpoint numbers, timers, DATE, CHAR, TOD, LTOD I, Q, M, D, L, I, Q, M, D, L, Element P or constant P or constant used to fill the destination area COUNT Input USINT, UINT, UDINT USINT, UINT, UDINT, ULINT I, Q, M, D, L, I, Q, M, D, L, Number of P or constant P or constant repeated move operations OUT 2) Output Binary numbers, integers, floatingpoint numbers, TIME, DATE, CHAR, TOD Binary numbers, integers, floatingpoint numbers, timers, DATE, CHAR, TOD, LTOD D, L D, L 1) The specified data types can also be used as elements of an Array structure. 2) The specified data types can only be used as elements of an Array structure. Address in destination area from which filling starts. For additional information on valid data types, refer to "See also". Example The following example shows how the instruction works: 7DJ,QB 7DJ,QB DBDUUD\>@ 8),//B%/. (1 ,1 287 EBDUUD\>@ 7DJ2XW 7DJB&RXQW &2817 (12 The following table shows how the instruction works using specific operand values: WinCC Basic V13.0 System Manual, 02/2014 2187 Programming the PLC 9.7 References Parameter Operand Value IN a_array[2] The data type of the a_array operand is Array [0..5] of INT. It consists of six elements of data type INT. COUNT Tag_Count 3 OUT b_array[1] The data type of the b_array operand is Array [0..6] of INT. It consists of seven elements of data type INT. If the operands "TagIn_1" and "TagIn_2" have signal state "1", the "Fill block uninterruptible" instruction is executed. The instruction copies the third element (#a_array[2]) of the #a_array tag three times to the #b_array output tag. The move operation cannot be interrupted by other operating system activities. If no errors occur during the execution of the instruction, the outputs ENO and "TagOut" are set to signal state "1". See also Overview of the valid data types (Page 1204) Basics of the EN/ENO mechanism (Page 1299) SWAP: Swap Description You can use the instruction "Swap" to change the order of the bytes within the tag at input IN and query the result at output OUT. The following figure shows how the bytes of a DWORD data type operand are swapped using the "Swap" instruction: 2188 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References ,1 287 Parameters The following table shows the parameters of the "Swap" instruction: Parameters Declaration Data type Memory area S7-1200 S7-1500 S7-1200 S7-1500 Description EN Input BOOL BOOL I, Q, M, D, L I, Q, M, D, L, T, C Enable input ENO Output BOOL BOOL I, Q, M, D, L I, Q, M, D, L Enable output IN Input WORD, DWORD WORD, DWORD, LWORD I, Q, M, D, L, P or constant I, Q, M, D, L, P or constant Operand whose bytes are swapped. OUT Output WORD, DWORD WORD, DWORD, LWORD I, Q, M, D, L, P I, Q, M, D, L, P Result You can select the data type of the instruction from the "<???>" drop-down list of the instruction box. For additional information on valid data types, refer to "See also". WinCC Basic V13.0 System Manual, 02/2014 2189 Programming the PLC 9.7 References Example The following example shows how the instruction works: 7DJ,Q 7DJ,QB9DOXH 6:$3 :25' 287 (1 7DJ2XWB9DOXH 7DJ2XW ,1 (12 6 The following table shows how the instruction works using specific operand values: Parameters Operand Value IN TagIn_Value 0000 1111 0101 0101 OUT TagOut_Value 0101 0101 0000 1111 If the operand "TagIn" has the signal state "1", the "Swap" instruction is executed. The arrangement of the bytes is changed and stored in the operand "TagOut_Value". See also Overview of the valid data types (Page 1204) Basics of the EN/ENO mechanism (Page 1299) ARRAY DB instructions ReadFromArrayDB: Read from array data block Description You can use the "Read from array data block" instruction to read data from an array DB and write them to a destination area. An array DB is a data block which consists of exactly one array of [data type]. The elements of the array can be UDT data type or any other elementary data type. The counting of the array always starts with the low limit "0", regardless of the later declaration of the array. The ENO enable output has the signal state "0" if one of the following conditions is fulfilled: The EN enable input has the signal state "0". If an error occurs during the execution of the instruction. 2190 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameters The following table shows the parameters of the "Read from array data block" instruction: Parameter Declaration Data type Memory area Description EN Input BOOL I, Q, M, D, L Enable input ENO Output BOOL I, Q, M, D, L Enable output DB Input DB_ANY I, Q, M, D, L Data block that is read INDEX Input DINT I, Q, M, D, L, P or constant Element that is read VALUE Output VARIANT L Value that is read and output RET_VAL Output INT I, Q, M, D, L, P Error information: If an error occurs during the execution of the instruction, an error code is output at the RET_VAL parameter. For additional information on valid data types, refer to "See also". Parameters RET_VAL The following table shows the meaning of the values of the RET_VAL parameter: Error code* Explanation (W#16#...) 0000 No error 80B4 Data types do not correspond 80B5 Copying process was interrupted 8132 The data block does not exist or is too short 8133 The data block is located in the load memory 8134 The data block is write protected 8135 The array DB contains invalid values 8154 The data type is not correctly declared 8282 The value at the INDEX parameter is outside the limits of the array. 8350 The VARIANT data type contains no value 8352 Code generation error 8353 Code generation error *The error codes can be displayed as integer or hexadecimal value in the program editor. For information on toggling display formats, refer to "See also". WinCC Basic V13.0 System Manual, 02/2014 2191 Programming the PLC 9.7 References Example The following example shows how the instruction works: 5HDG)URP$UUD\'% 7DJ,QB (1 $UUD\'% '% $UUD\'%7+,6>@ ,1'(; 5(7B9$/ 9$/8( (12 7DJ5HWB9DO 7DUJHW)LHOG>@ 7DJ2XW 'DWD>@ The following table shows how the instruction works using specific operand values: Parameters Operand Value DB ArrayDB The data type of the "ArrayDB" operand is Array [0 to 10] of INT. INDEX ArrayDB.THIS[2] Third element of the "ArrayDB" VALUE TargetField[10].Data2[1] The data type of the "TargetField" operand is Array [10 to 20] of "MOVE_UDT". If the "TagIn1" operand has the signal state "1", the "Read from array data block" instruction is executed. The third element is read from "ArrayDB" and written to the "TargetField[10].Data2[1]" operand. If the instruction is executed without errors, the ENO enable output has the signal state "1" and the "TagOut" output is set. See also Overview of the valid data types (Page 1204) Basics of the EN/ENO mechanism (Page 1299) WriteToArrayDB: Write to array data block Description You can use the "Write to array data block" instruction to write data to an array DB. An array DB is a data block which consists of exactly one array of [data type]. The elements of the array can be UDT data type or any other elementary data type. The counting of the array always starts with the low limit "0", regardless of the later declaration of the array. The ENO enable output has the signal state "0" if one of the following conditions is fulfilled: The EN enable input has the signal state "0". If an error occurs during the execution of the instruction. 2192 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameters The following table shows the parameters of the "Write to array data block" instruction: Parameter Declaration Data type Memory area Description EN Input BOOL I, Q, M, D, L Enable input ENO Output BOOL I, Q, M, D, L Enable output DB Input DB_ANY I, Q, M, D, L Data block to which data is written INDEX Input DINT I, Q, M, D, L, P or constant Element in the DB to which data is written VALUE Input VARIANT L Value to be written RET_VAL Output INT I, Q, M, D, L, P Error information: If an error occurs during the execution of the instruction, an error code is output at the RET_VAL parameter. For additional information on valid data types, refer to "See also". Parameters RET_VAL The following table shows the meaning of the values of the RET_VAL parameter: Error code* Explanation (W#16#...) 0000 No error 80B4 Data types do not correspond 80B5 Copying process was interrupted 8132 The data block does not exist or is too short 8133 The data block is located in the load memory 8134 The data block is write protected 8135 The DB is not an array data block. 8282 The value at the INDEX parameter is outside the limits of the array. 8350 The VARIANT data type contains no value 8352 Code generation error 8353 Code generation error *The error codes can be displayed as integer or hexadecimal value in the program editor. For information on toggling display formats, refer to "See also". WinCC Basic V13.0 System Manual, 02/2014 2193 Programming the PLC 9.7 References Example The following example shows how the instruction works: :ULWH7R$UUD\'% 7DJ,QB (1 $UUD\'% '% $UUD\'%7+,6>@ ,1'(; 5(7B9$/ 6RXUFH)LHOG>@ 'DWD>@ 9$/8( (12 7DJ5HWB9DO 7DJ2XW The following table shows how the instruction works using specific operand values: Parameters Operand Value DB ArrayDB The data type of the "ArrayDB" operand is Array [0 to 10] of INT. INDEX ArrayDB.THIS[2] Third element of the "ArrayDB" VALUE SourceField[1].Data1[6] The data type of the "SourceField" operand is Array [0 to 10] of "MOVE_UDT". If the "TagIn1" operand has the signal state "1", the "Write to the ARRAY data block" instruction is executed. From the "SourceField" operand, the "Data1[6]" element from the second element is written to the "ArrayDB". The third element is written to the "ArrayDB". If the instruction is executed without errors, the ENO enable output has the signal state "1" and the "TagOut" output is set. See also Overview of the valid data types (Page 1204) Basics of the EN/ENO mechanism (Page 1299) ReadFromArrayDBL: Read from array data block in load memory Description You can use the "Read from array data block in load memory" instruction to read data from an array DB in load memory. An array DB is a data block which consists of exactly one array of [data type]. The elements of the array can be UDT data type or any other elementary data type. The counting of the array always starts with the low limit "0", regardless of the later declaration of the array. If the array DB is marked with the "Only store in load memory" block attribute, it is only stored in load memory. The instruction is executed when a positive signal edge is detected at the REQ parameter. The BUSY parameter then has the signal state "1". The instruction is terminated if a negative signal edge is detected at the BUSY parameter. The DONE parameter has the signal state "1" 2194 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References for one program cycle and the read value is output at the VALUE parameter within this cycle. With all other program cycles, the value at the VALUE parameter is not changed. When you insert the instruction in the program, the "Call options" dialog opens in which you can specify whether the block parameters will be stored in a separate data block (single instance) or as a local tag (multiple instance) in the block interface. If you create a separate data block, it is saved to the "Program resources" folder in the "Program blocks > System blocks" path of the project tree. For additional information on this topic, refer to "See also". Note The array DB must be located in a data block with the block property "Optimized". The ENO enable output has the signal state "0" if one of the following conditions is fulfilled: The EN enable input has the signal state "0". If an error occurs during the execution of the instruction. Parameters The following table shows the parameters of the "Read from array data block in load memory" instruction: WinCC Basic V13.0 System Manual, 02/2014 Parameter Declaration Data type Memory area Description EN Input BOOL I, Q, M, D, L Enable input ENO Output BOOL I, Q, M, D, L Enable output REQ Input BOOL I, Q, M, D, L or constant REQ = "1": Starting with the reading of the array DB DB Input DB_ANY I, Q, M, D, L Data block that is read INDEX Input DINT I, Q, M, D, L, P or constant Element that is read BUSY Output BOOL I, Q, M, D, L BUSY = "1": The array DB is still being read DONE Output BOOL I, Q, M, D, L DONE = "1": The instruction was executed successfully 2195 Programming the PLC 9.7 References Parameter Declaration Data type Memory area Description VALUE InOut VARIANT D, L Value that is read and output ERROR Output INT I, Q, M, D, L, P Error information: If an error occurs during the execution of the instruction, an error code is output at the ERROR parameter. For additional information on valid data types, refer to "See also". ERROR parameter The following table shows the meaning of the values of the ERROR parameter: Error code* Explanation (W#16#...) 0000 No error 80B4 Data types do not correspond 80B5 Copying process was interrupted 80C3 Too many concurrent calls 8132 The data block does not exist or is too short 8133 The data block is not located in load memory 8134 The data block is write protected 8135 The DB is not an array data block. 8282 The value at the INDEX parameter is outside the limits of the array. 8350 The VARIANT data type contains no value 8352 Code generation error 8353 Code generation error *The error codes can be displayed as integer or hexadecimal value in the program editor. For information on toggling display formats, refer to "See also". You can find descriptions of the error codes triggered by the instructions "READ_DBL: Read from data block in load memory" and "WRIT_DBL: Write to data block in load memory" under "See also". 2196 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Example The following example shows how the instruction works: 5HDG)URP$UUD\'%/B'% 5HDG)URP$UUD\'%/ 7DJ,QB 7DJ5HT $UUD\'% $UUD\'%7+,6>@ 6RXUFH7DUJHW)LHOG>@ 'DWD>@ (1 5(4 %86< 7DJ%XV\ '% '21( 7DJ'RQH ,1'(; (5525 7DJ(UURU 9$/8( (12 7DJ2XW The following table shows how the instruction works using specific operand values: Parameters Operand Value REQ TagReq BOOL DB ArrayDB The data type of the "ArrayDB" operand is Array [0 to 10] of INT. INDEX ArrayDB.THIS[2] Third element of the "ArrayDB" VALUE SourceTargetField[1].Data1[6] The data type of the "SourceTargetField" operand is Array [0 to 10] of "MOVE_UDT". BUSY TagBusy BOOL DONE TagDone BOOL If the "TagIn1" operand has the signal state "1" and a positive edge is detected at the "TagReq"operand, the "Read from ARRAY data block in load memory" instruction is executed. The third element is read from "ArrayDB" and written to the "SourceTargetField[1].Data1[6]" operand. As soon as a negative signal edge is detected at the "TagBusy" operand, the instruction is terminated and the value at the VALUE parameter is no longer changed. If the instruction is executed without errors, the ENO enable output has the signal state "1" and the "TagOut" output is set. After the instruction has been processed, the "TagDone" operand the signal state "1". See also Overview of the valid data types (Page 1204) Basics of the EN/ENO mechanism (Page 1299) WRIT_DBL: Write to data block in the load memory (Page 2800) READ_DBL: Read from data block in the load memory (Page 2798) WinCC Basic V13.0 System Manual, 02/2014 2197 Programming the PLC 9.7 References WriteToArrayDBL: Write to array data block in load memory Description You can use the "Write to array data block in load memory" instruction to write data to an array DB in load memory. An array DB is a data block which consists of exactly one array of [data type]. The elements of the array can be UDT data type or any other elementary data type. The counting of the array always starts with the low limit "0", regardless of the later declaration of the array. If the array DB is marked with the "Only store in load memory" block attribute, it is only stored in load memory. The instruction is executed when a positive signal edge is detected at the REQ parameter. The BUSY parameter then has the signal state "1". If a negative signal edge is detected at the BUSY parameter, the instruction is terminated and the value at the VALUE parameter is written to the data block. The DONE parameter then has the signal state "1" for one program cycle. When you insert the instruction in the program, the "Call options" dialog opens in which you can specify whether the block parameters will be stored in a separate data block (single instance) or as a local tag (multiple instance) in the block interface. If you create a separate data block, it is saved to the "Program resources" folder in the "Program blocks > System blocks" path of the project tree. For additional information on this topic, refer to "See also". Note The array DB must be located in a data block with the block property "Optimized". The ENO enable output has the signal state "0" if one of the following conditions is fulfilled: The EN enable input has the signal state "0". If an error occurs during the execution of the instruction. Parameters The following table shows the parameters of the "Write to array data block in load memory" instruction: 2198 Parameter Declaration Data type Memory area Description EN Input BOOL I, Q, M, D, L Enable input ENO Output BOOL I, Q, M, D, L Enable output REQ Input BOOL I, Q, M, D, L or constant REQ = "1": Start writing to the array DB DB Input DB_ANY D Data block to which data is written INDEX Input DINT I, Q, M, D, L, P or constant Element in the DB to which data is written WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameter Declaration Data type Memory area Description VALUE Input VARIANT D, L Value to be written BUSY Output BOOL I, Q, M, D, L BUSY = "1": The array DB is still being written DONE Output BOOL I, Q, M, D, L DONE = "1": The instruction was executed successfully ERROR Output INT I, Q, M, D, L, P Error information: If an error occurs during the execution of the instruction, an error code is output at the ERROR parameter. For additional information on valid data types, refer to "See also". ERROR parameter The following table shows the meaning of the values of the ERROR parameter: Error code* Explanation (W#16#...) 0000 No error 80B4 Data types do not correspond 80B5 Copying process was interrupted 8132 The data block does not exist or is too short 8133 The data block is not located in the load memory 8134 The data block is write protected 8135 The DB is not an array data block. 8282 The value at the INDEX parameter is outside the limits of the array. 8350 The VARIANT data type contains no value 8352 Code generation error 8353 Code generation error *The error codes can be displayed as integer or hexadecimal value in the program editor. For information on toggling display formats, refer to "See also". You can find descriptions of the error codes triggered by the instructions "READ_DBL: Read from data block in load memory" and "WRIT_DBL: Write to data block in load memory" under "See also". WinCC Basic V13.0 System Manual, 02/2014 2199 Programming the PLC 9.7 References Example The following example shows how the instruction works: :ULWH7R$UUD\'%/B'% :ULWH7R$UUD\'%/ 7DJ,QB (1 7DJ5HT 5(4 %86< 7DJ%XV\ '% '21( 7DJ'RQH ,1'(; (5525 7DJ(UURU 9$/8( (12 $UUD\'% $UUD\'%7+,6>@ 6RXUFH7DUJHW)LHOG>@ 'DWD>@ 7DJ2XW The following table shows how the instruction works using specific operand values: Parameters Operand Value REQ TagReq BOOL DB ArrayDB The data type of the "ArrayDB" operand is Array [0 to 10] of INT. INDEX ArrayDB.THIS[2] Third element of the "ArrayDB" VALUE SourceTargetField[1].Data1[6] The data type of the "SourceTargetField" operand is Array [0 to 10] of "MOVE_UDT". BUSY TagBusy BOOL DONE TagDone BOOL If the "TagIn1" operand has the signal state "1" and a positive edge is detected at the "TagReq"operand, the "Write to ARRAY data block in load memory" instruction is executed. As soon as a negative signal edge is detected at the "TagBusy" operand, the instruction is terminated and the value at the VALUE parameter is written in the third element in the "ArrayDB". If the instruction is executed without errors, the ENO enable output has the signal state "1" and the "TagOut" output is set. After the instruction has been processed, the "TagDone" operand the signal state "1". See also Overview of the valid data types (Page 1204) Basics of the EN/ENO mechanism (Page 1299) WRIT_DBL: Write to data block in the load memory (Page 2800) READ_DBL: Read from data block in the load memory (Page 2798) 2200 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References VARIANT instructions VariantGet: Read out VARIANT tag value Description You can use the "Read out VARIANT tag value" instruction to read the value of the tag to which the VARIANT at the SRC parameter points and write it in the tag at the DST parameter. The SRC parameter must have the VARIANT data type. Any data type except for VARIANT can be specified at the DST parameter. The data type of the tag at the DST parameter must match the data type to which the VARIANT points. Note The tag to which the VARIANT at parameter SRC points must be a PLC data type. To copy structures and ARRAYs, you can use the "MOVE_BLK_VARIANT: Move block" instruction. For additional information, refer to "See also". The ENO enable output has the signal state "0" if one of the following conditions is fulfilled: The EN enable input has the signal state "0". The data types do not correspond. (No value is transferred.) Parameters The following table shows the parameters of the "Read out VARIANT tag value" instruction: Parameters Declaration Data type Memory area Description EN Input BOOL I, Q, M, D, L Enable input ENO Output BOOL I, Q, M, D, L Enable output SRC Input VARIANT L Tag to be read DST Output Bit strings, integers, floating-point numbers, timers, date and time, character strings, ARRAY I, Q, M, D, L Result of the instruction For additional information on valid data types, refer to "See also". WinCC Basic V13.0 System Manual, 02/2014 2201 Programming the PLC 9.7 References Example The following example shows how the instruction works: 9DULDQW*HW 7DJ,Q 7DJ,QB6RXUFH (1 (12 7DJ2XW 65& '67 7DJ2XWB'HVW If the "TagIn" operand has the signal state "1", the "Read out VARIANT tag value" instruction is executed. The value of the tag to which the VARIANT at the "#TagIn_Source" operand points is read and written to the "TagOut_Dest" operand. See also Overview of the valid data types (Page 1204) Basics of the EN/ENO mechanism (Page 1299) VARIANT (Page 1245) MOVE_BLK_VARIANT: Move block (Page 2177) VariantPut: Write VARIANT tag value Description You can use the "Write VARIANT tag value" instruction to write the value of the tag at the SRC parameter to the tag at the DST parameter to which the VARIANT points. The DST parameter must have the VARIANT data type. Any data type except for VARIANT can be specified at the SRC parameter. The data type of the tag at the SRC parameter must match the data type to which the VARIANT points. Note The tag to which the VARIANT at parameter DST points must be a PLC data type. The ENO enable output has the signal state "0" if one of the following conditions is fulfilled: The EN enable input has the signal state "0". The data types do not correspond. (No value is transferred.) 2202 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameters The following table shows the parameters of the "Write VARIANT tag value" instruction: Parameters Declaration Data type Memory area Description EN Input BOOL I, Q, M, D, L Enable input ENO Output BOOL I, Q, M, D, L Enable output SRC Input Bit strings, integers, floating-point numbers, timers, date and time, character strings, ARRAY I, Q, M, D, L Tag to be read DST Input VARIANT L Result of the instruction For additional information on valid data types, refer to "See also". Example The following example shows how the instruction works: 9DULDQW3XW 7DJ,Q (1 7DJ,QB6RXUFH 65& 7DJ,QB'HVW '67 (12 7DJ2XW If the "TagIn" operand has the signal state "1", the "Write VARIANT tag value" instruction is executed. The value of the "TagIn_Source" operand is written to the tag to which the VARIANT at the "#TagIn_Dest" operand points. See also Overview of the valid data types (Page 1204) Basics of the EN/ENO mechanism (Page 1299) VARIANT (Page 1245) CountOfElements: Get number of ARRAY elements Description You can use the "Get number of ARRAY elements" instruction to query how many ARRAY elements a tag pointing to an VARIANT has. If it is a one-dimensional ARRAY, the difference between the high and low limit +1 is output as a result. If it is a multi-dimensional ARRAY, the product of all dimensions is output as the result. The IN parameter must have the same VARIANT data type. WinCC Basic V13.0 System Manual, 02/2014 2203 Programming the PLC 9.7 References The ENO enable output has the signal state "0" if one of the following conditions is fulfilled: The EN enable input has the signal state "0". The VARIANT tag is not an ARRAY. (The result is "0".) If the VARIANT points to an ARRAY of BOOL, the fill elements are included in the count. (For example, 8 is returned for an ARRAY[0..1] of BOOL) Parameters The following table shows the parameters of the "Get number of ARRAY elements" instruction: Parameters Declaration Data type Memory area Description EN Input BOOL I, Q, M, D, L Enable input ENO Output BOOL I, Q, M, D, L Enable output IN Input VARIANT L Tag to be queried RET_VAL Output UDINT I, Q, M, D, L Result of the instruction For additional information on valid data types, refer to "See also". Example The following example shows how the instruction works: &RXQW2I(OHPHQWV 7DJ,Q 7DJ,QB6RXUFH (1 ,1 (12 5(7B9$/ 7DJ2XW 7DJ2XWB5HW9DO If the "TagIn" operand has the signal state "1", the "Get number of ARRAY elements" instruction is executed. The number of ARRAY elements of the tag to which the VARIANT at the "#TagIn_Source" operand points is read and output at the "TagOut_RetVal" operand. See also Format of array (16-bit limits) (Page 1235) Format of array (32-bit limits) (Page 1236) Overview of the valid data types (Page 1204) Basics of the EN/ENO mechanism (Page 1299) VARIANT (Page 1245) 2204 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Other BLKMOV: Move block Description You can use the "Move block" instruction to move the content of a memory area (source area) to another memory area (destination area). The move operation takes place in the direction of ascending addresses. You use VARIANT to define the source and destination area. Note The tags of the instruction can only be used in data blocks in which the "Optimized block access" attribute is not set. If the tag with the retentive setting "Set in IDB" has been declared, you can also use the tags "with optimized access". The following figure shows the principle of the move operation: '%'%: $ % '%'%: & ' '%'%: ( ) '%'%: * + 0RYH 7KHPRYHWDNHVSODFHLQ WKHGLUHFWLRQRIDVFHQGLQJ DGGUHVVHV 0: $ % 0: & ' 0: ( ) 0: * + 0HPRU\DUHD Consistency of the source data and the target data Make sure that the source data remain unchanged during the execution of the "Move block" instruction. Otherwise the consistency of the target data cannot be ensured. Interruptibility There is no limit to the nesting depth. WinCC Basic V13.0 System Manual, 02/2014 2205 Programming the PLC 9.7 References Memory areas You can use the "Move block" instruction to move the following memory areas: Areas of a data block Bit memory Process image of the inputs Process image of the outputs General rules for moving The source and destination area must not overlap. If the source and destination area have different lengths, only the length of the smaller area will be moved. If the source area is less than the destination area, the entire source area will be written to the destination area. The remaining bytes of the destination area remain unchanged. If the destination area is less than the source area, the entire destination area will be written. The remaining bytes of the source area are ignored. If a block of data type BOOL is moved, the tag must be addressed absolutely and the specified length of the area must be divisible by 8, otherwise the instruction cannot be executed. Rules for moving character strings You can use the "Move block" instruction to also move source and destination areas of the STRING data type. If only the source area is STRING data type, the characters will be moved that are actually contained in the character string. Information on the actual and maximum length is also written to the destination area. If the source and destination area are each STRING data type, the current length of the character string in the destination area is set to the number of actually moved characters. If you want to move the information on the maximum and actual length of a character string, specify the areas in bytes in the SRCBLK and DSTBLK parameters. Parameters The following table shows the parameters of the "Move block" instruction: Parameter 2206 Declaration Data type Memory area S7-1200 S7-1500 Description EN Input BOOL I, Q, M, D, L I, Q, M, D, L, T, C Enable input ENO Output BOOL I, Q, M, D, L I, Q, M, D, L Enable output SRCBLK Input VARIANT L, P L, P Specifies the memory area to be moved (source area). WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameter RET_VAL Declaration Data type Output INT Memory area S7-1200 S7-1500 I, Q, M, D, L, P I, Q, M, D, L, P Description Error information: If an error occurs during the execution of the instruction, an error code is output at the RET_VAL parameter. DSTBLK Output VARIANT L, P L, P Specifies the memory area to which the block is to be moved (destination area). RET_VAL parameter The following table shows the meaning of the values of the RET_VAL parameter: Error code* (W#16#...) Explanation 0000 No error 8152 The data types WSTRING, WCHAR and BOOL are not supported. 8092 The source or target area is only available in the load memory. General error information See also: "GET_ERR_ID: Get error ID locally *The error codes can be displayed as integer or hexadecimal value in the program editor. For information on toggling display formats, refer to "See also". See also Overview of the valid data types (Page 1204) Basics of the EN/ENO mechanism (Page 1299) GET_ERR_ID: Get error ID locally (Page 2248) UBLKMOV: Move block uninterruptible Description You can use the "Move block uninterruptible" instruction to move the content of a memory area (source area) to another memory area (destination area). The move operation takes place in the direction of ascending addresses. You use VARIANT to define the source and destination area. WinCC Basic V13.0 System Manual, 02/2014 2207 Programming the PLC 9.7 References The move operation cannot be interrupted by other operating system activities. As a result the interrupt reaction time of the CPU can increase during the execution of the "Move block uninterruptible" instruction. Note The tags of the instruction can only be used in data blocks in which the "Optimized block access" attribute is not set. If the tag with the retentive setting "Set in IDB" has been declared, you can also use the tags "with optimized access". Memory areas You can use the "Move block uninterruptible" instruction to move the following memory areas: Areas of a data block Bit memory Process image of the inputs Process image of the outputs General rules for moving The source and destination area must not overlap during the execution of the "Move block uninterruptible" instruction. If the source area is less than the destination area, the entire source area will be written to the destination area. The remaining bytes of the destination area remain unchanged. If the destination area is less than the source area, the entire destination area will be written. The remaining bytes of the source area are ignored. If a source or destination area defined as a formal parameter is less than a destination or source area specified on the SRCBLK or DSTBLK parameter, no data is transferred. If a block of data type BOOL is moved, the tag must be addressed absolutely and the specified length of the area must be divisible by 8, otherwise the instruction cannot be executed. You can use the "Move block uninterruptible" instruction to move a maximum of 16 KB. Note the CPU-specific restrictions for this. Rules for moving character strings You can use the "Move block uninterruptible" instruction to also move source and destination areas of the STRING data type. If only the source area is STRING data type, the characters will be moved that are actually contained in the character string. Information on the actual and maximum length are not written in the destination area. If the source and destination area are each STRING data type, the current length of the character string in the destination area is set to the number of actually moved characters. If areas of the data type STRING are moved, you have to specify "1" as area length. 2208 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameters The following table shows the parameters of the "Move block uninterruptible" instruction: Parameter Declaration Data type Memory area S7-1200 S7-1500 Description EN Input BOOL I, Q, M, D, L I, Q, M, D, L, T, C Enable input ENO Output BOOL I, Q, M, D, L I, Q, M, D, L Enable output SRCBLK Input VARIANT L, P L, P Specifies the memory area to be moved (source area). RET_VAL Output INT I, Q, M, D, L, P I, Q, M, D, L, P DSTBLK Output VARIANT L, P L, P Error information: If an error occurs during the execution of the instruction, an error code is output at the RET_VAL parameter. Specifies the memory area to which the block is to be moved (destination area). Parameters RET_VAL The following table shows the meaning of the values of the RET_VAL parameter: Error code (W#16#...) Explanation 0000 No error 8152 The data types WSTRING, WCHAR and BOOL are not supported. 8091 The source area is in a data block that is not relevant for program execution. General error information See also: "GET_ERR_ID: Get error ID locally *The error codes can be displayed as integer or hexadecimal value in the program editor. For information on toggling display formats, refer to "See also". See also Overview of the valid data types (Page 1204) Basics of the EN/ENO mechanism (Page 1299) GET_ERR_ID: Get error ID locally (Page 2248) WinCC Basic V13.0 System Manual, 02/2014 2209 Programming the PLC 9.7 References FILL: Fill block Description You can use the "Fill block" instruction to fill a memory area (destination area) with the content of another memory area (source area). The "Fill block" instruction moves the content of the source area to the destination area until the destination area is completely written. The move operation takes place in the direction of ascending addresses. You use VARIANT to define the source and destination area. Note The tags of the instruction can only be used in data blocks in which the "Optimized block access" attribute is not set. If the tag with the retentive setting "Set in IDB" has been declared, you can also use the tags "with optimized access". For blocks with the "Optimized block access" attribute, you can use the "FILL_BLK: Fill block" instruction. The following figure shows the principle of the move operation: ),// %9$/ $ % 0: $ % 0: & ' 0: & ' 0: ( ) 0: ( ) 0: * + 0: * + 0: $ % 0: & ' 0: ( ) 0: * + 0: $ % 0: & ' 0: %/. Consistency of the source data and the target data Note that while the instruction "Fill block" is being executed, the source data remains unchanged; otherwise the consistency of the destination data cannot be guaranteed. 2210 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Memory areas You can use the "Fill block" instruction to move the following memory areas: Areas of a data block Bit memory Process image of the inputs Process image of the outputs General rules for moving The source and destination area must not overlap. If the destination area to be preset is not an integer multiple of the length of the input parameter BVAL, the destination area is nevertheless written up to the last byte. If the destination area to be preset is smaller than the source area, the function only copies as much data as can be written to the destination area. If the destination or source area actually present is smaller than the assigned memory area for the source or destination area (BVAL, BLK parameters), no data is transferred. If the ANY pointer (source or destination) is of the data type BOOL, it must be addressed absolutely and the length specified must be divisible by 8; otherwise the instruction is not executed. If the destination area is of data type STRING, the instruction writes the entire string including the administration information. Parameters The following table shows the parameters of the "Fill block" instruction: Parameter Declaration Data type EN Input BOOL I, Q, M, D, L Memory area Description Enable input ENO Output BOOL I, Q, M, D, L Enable output BVAL Input VARIANT L, P Specification of the memory area (source area) with the content used to fill the destination area at the BLK parameter. RET_VAL Output INT I, Q, M, D, L, P Error information: If an error occurs during the execution of the instruction, an error code is output at the RET_VAL parameter. BLK WinCC Basic V13.0 System Manual, 02/2014 Output VARIANT L, P Specification of the memory area that is filled with the content of the source area. 2211 Programming the PLC 9.7 References Parameters RET_VAL The following table shows the meaning of the values of the RET_VAL parameter: Error code* (W#16#...) Explanation 0000 No error 8152 The data types WSTRING, WCHAR and BOOL are not supported. General error information See also: "GET_ERR_ID: Get error ID locally *The error codes can be displayed as integer or hexadecimal value in the program editor. For information on toggling display formats, refer to "See also". See also Overview of the valid data types (Page 1204) Basics of the EN/ENO mechanism (Page 1299) GET_ERR_ID: Get error ID locally (Page 2248) Conversion operations CONVERT: Convert value Description The "Convert value" instruction reads the content of the IN parameter and converts it according to the data types configured in the instruction box. The converted value is provided at output OUT. For information on possible conversions, refer to section "Explicit conversion" under "See also". The ENO enable output has the signal state "0" if one of the following conditions is fulfilled: The EN enable input has the signal state "0". Errors, such as an overflow, occur during execution. Parameters The following table shows the parameters of the "Convert value" instruction: 2212 Parameters Declaration Data type Memory area Description S7-1200 S7-1500 EN Input BOOL I, Q, M, D, L I, Q, M, D, L, T, C Enable input ENO Output BOOL I, Q, M, D, L I, Q, M, D, L Enable output WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameters Declaration Data type Memory area S7-1200 S7-1500 I, Q, M, D, L, P or constant Description IN Input Bit strings, integers, floating-point numbers, CHAR, BCD16, BCD32 I, Q, M, D, L, P or constant Value to be converted. OUT Output Bit strings, integers, floating-point numbers, CHAR, BCD16, BCD32 I, Q, M, D, L, P I, Q, M, D, L, P Result of the conversion You can select the data type of the instruction from the "<???>" drop-down list of the instruction box. Bit strings (BYTE, WORD, DWORD, LWORD) cannot be selected in the instruction box. If you specify an operand of data type BYTE, WORD, DWORD or LWORD at a parameter of the instruction, it is interpreted according to the data type of the input or output parameter. Data type BYTE is then interpreted as USINT, WORD as UINT, DWORD as UDINT, and LWORD as LINT, for example. Note For S7-1500 CPU: You can select the data types DWORD and LWORD if REAL or LREAL were selected as IN data type. For additional information on valid data types, refer to "See also". Example The following example shows how the instruction works: &219 ,17 WR ',17 7DJ,Q (1 287 7DJ,QB9DOXH ,1 (12 7DJ2XWB9DOXH 7DJ2XW If the operand "TagIn" has the signal state "1", the content of the operand "TagIn_Value" is read and converted to an integer (16 bits). The result is stored in the operand "TagOut_Value". The output "TagOut" is set to "1" if the instruction was executed without errors. WinCC Basic V13.0 System Manual, 02/2014 2213 Programming the PLC 9.7 References See also Overview of the valid data types (Page 1204) Basics of the EN/ENO mechanism (Page 1299) ROUND: Round numerical value Description You can use the "Round numerical value" instruction to round the value at input IN to the nearest integer. The instruction interprets the value at input IN as a floating-point number and converts this to the nearest integer. If the input value is exactly between an even and odd number, then the even number is converted. The result of the instruction is provided at output OUT and can be queried there. Enable output ENO has the signal state "0" if one of the following conditions applies: Enable input EN has the signal state "0". Errors, such as an overflow, occur during execution. Parameters The following table shows the parameters of the "Round numerical value" instruction: Parameters Declaration Data type Memory area S7-1200 S7-1500 Description EN Input BOOL I, Q, M, D, L I, Q, M, D, L, T, C Enable input ENO Output BOOL I, Q, M, D, L I, Q, M, D, L Enable output IN Input Floating-point numbers I, Q, M, D, L, P or constant I, Q, M, D, L, P or constant Input value to be rounded. OUT Output Integers, floating-point numbers I, Q, M, D, L, P I, Q, M, D, L, P Result of the rounding You can select the data type of the instruction from the "<???>" drop-down list of the instruction box. For additional information on valid data types, refer to "See also". 2214 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Example The following example shows how the instruction works: 5281' 5($/ WR ',17 7DJ,Q 7DJ,QB9DOXH (1 287 ,1 (12 7DJ2XWB9DOXH 7DJ2XW The following table shows how the instruction works using specific operand values: Parameters Operand Value IN TagIn_Value 1.50000000 -1.50000000 OUT TagOut_Value 2 -2 If the operand "TagIn" has the signal state "1", the "Round numerical value" instruction is executed. The floating-point number at input "TagIn_Value" is rounded to the nearest even integer and sent to output "TagOut_Value". If no errors occur during the execution of the instruction, the output "TagOut" is set. See also Overview of the valid data types (Page 1204) Basics of the EN/ENO mechanism (Page 1299) CEIL: Generate next higher integer from floating-point number Description You can use the "Generate next higher integer from floating-point number" instruction to round the value at input IN to the next higher integer. The instruction interprets the value at input IN as a floating-point number and converts this to the next higher integer. The result of the instruction is provided at output OUT and can be queried there. The output value can be greater than or equal to the input value. Enable output ENO has the signal state "0" if one of the following conditions applies: Enable input EN has the signal state "0". Errors, such as an overflow, occur during execution. WinCC Basic V13.0 System Manual, 02/2014 2215 Programming the PLC 9.7 References Parameters The following table shows the parameters of the instruction "Generate next higher integer from floating-point number": Parameters Declaration Data type Memory area Description S7-1200 S7-1500 EN Input BOOL I, Q, M, D, L I, Q, M, D, L, T, C Enable input ENO Output BOOL I, Q, M, D, L I, Q, M, D, L Enable output IN Input Floating-point numbers I, Q, M, D, L, P or constant I, Q, M, D, L, P or constant Input value as floating-point number OUT Output Integers, floating-point numbers I, Q, M, D, L, P I, Q, M, D, L, P Result with the next higher integer You can select the data type of the instruction from the "<???>" drop-down list of the instruction box. For additional information on valid data types, refer to "See also". Example The following example shows how the instruction works: &(,/ 5($/ 7DJ,Q 7DJ,QB9DOXH WR ',17 (1 287 ,1 (12 7DJ2XWB9DOXH 7DJ2XW The following table shows how the instruction works using specific operand values: Parameters Operand Value IN TagIn_Value 0.50000000 -0.50000000 OUT TagOut_Value 1 0 If the operand "TagIn" has the signal state "1", the instruction "Generate next higher integer from floating-point number" is executed. The floating-point number at input "TagIn_Value" is rounded to the next higher integer and sent to output "TagOut_Value". If no errors occur during the execution of the instruction, the output "TagOut" is set. See also Overview of the valid data types (Page 1204) Basics of the EN/ENO mechanism (Page 1299) 2216 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References FLOOR: Generate next lower integer from floating-point number Description You can use the "Generate next lower integer from floating-point number" instruction to round the value at input IN to the next lower integer. The instruction interprets the value at input IN as a floating-point number and converts this to the next lower integer. The result of the instruction is provided at output OUT and can be queried there. The output value can be less than or equal to the input value. Enable output ENO has the signal state "0" if one of the following conditions applies: Enable input EN has the signal state "0". Errors, such as an overflow, occur during execution. Parameters The following table shows the parameters of the instruction "Generate next lower integer from floating-point number": Parameters Declaration Data type Memory area S7-1200 S7-1500 Description EN Input BOOL I, Q, M, D, L I, Q, M, D, L, T, C Enable input ENO Output BOOL I, Q, M, D, L I, Q, M, D, L Enable output IN Input Floating-point numbers I, Q, M, D, L, P or constant I, Q, M, D, L, P or constant Input value as floating-point number OUT Output Integers, floating-point numbers I, Q, M, D, L, P I, Q, M, D, L, P Result with the next lower integer You can select the data type of the instruction from the "<???>" drop-down list of the instruction box. For additional information on valid data types, refer to "See also". Example The following example shows how the instruction works: 5($/ 7DJ,Q 7DJ,QB9DOXH )/225 WR ',17 (1 287 ,1 (12 7DJ2XWB9DOXH 7DJ2XW The following table shows how the instruction works using specific operand values: WinCC Basic V13.0 System Manual, 02/2014 2217 Programming the PLC 9.7 References Parameters Operand IN TagIn_Value 0.50000000 Value -0.50000000 OUT TagOut_Value 0 -1 If the operand "TagIn" has the signal state "1", the instruction "Generate next lower integer from floating-point number" is executed. The floating-point number at input "TagIn_Value" is rounded to the next lower integer and displayed at output "TagOut_Value". If no errors occur during the execution of the instruction, the output "TagOut" is set. See also Overview of the valid data types (Page 1204) Basics of the EN/ENO mechanism (Page 1299) TRUNC: Truncate numerical value Description You can use the "Truncate numerical value" instruction to form an integer from the value at input IN. The value at input IN is interpreted as a floating-point number. The instruction selects only the integer part of the floating-point number and sends this to output OUT without decimal places. Enable output ENO has the signal state "0" if one of the following conditions applies: Enable input EN has the signal state "0". Errors, such as an overflow, occur during execution. Parameters The following table shows the parameters of the instruction "Truncate numerical value": Parameters Declaration Data type Memory area Description EN Input BOOL I, Q, M, D, L Enable input ENO Output BOOL I, Q, M, D, L Enable output IN Input Floating-point numbers I, Q, M, D, L or constant Input value as floating-point number OUT Output Integers, floatingpoint numbers I, Q, M, D, L Result with integer part of the floatingpoint number You can select the data type of the instruction from the "<???>" drop-down list of the instruction box. For additional information on valid data types, refer to "See also". 2218 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Example The following example shows how the instruction works: 5($/ 7DJ,Q 7DJ,QB9DOXH 7581& WR ',17 (1 287 ,1 (12 7DJ2XWB9DOXH 7DJ2XW The following table shows how the instruction works using specific operand values: Parameters Operand Value IN TagIn_Value 1.50000000 -1.50000000 OUT TagOut_Value 1 -1 If the operand "TagIn" has the signal state "1", the "Truncate numerical value" instruction is executed. The integer part of the floating-point number at input "TagIn_Value" is converted to an integer and sent to output "TagOut_Value". If no errors occur during the execution of the instruction, the output "TagOut" is set. See also Overview of the valid data types (Page 1204) Basics of the EN/ENO mechanism (Page 1299) SCALE_X: Scale Description You can use the "Scale" instruction to scale the value at the VALUE input by mapping it to a specified value range. When the instruction "Scale" is executed, the floating-point value at input VALUE is scaled to the value range, which is defined by the parameters MIN and MAX. The result of the scaling is an integer, which is stored at output OUT. The following figure shows an example of how values can be scaled: WinCC Basic V13.0 System Manual, 02/2014 2219 Programming the PLC 9.7 References 0$; 287 0,1 9$/8( The "Scale" instruction works with the following equation: OUT = [VALUE (MAX - MIN)] + MIN Enable output ENO has the signal state "0" if one of the following conditions is fulfilled: Enable input EN has the signal state "0". The value at input MIN is greater than or equal to the value at input MAX. The value of a specified floating-point number is outside the range of the normalized numbers according to IEEE-754. An overflow occurs. The value at input VALUE is NaN (Not a number = result of an invalid arithmetic operation). Note For more information on the conversion of analog values, refer to the respective manual. Parameters The following table shows the parameters of the "Scale" instruction: 2220 Parameter Declaration Data type Memory area Description S7-1200 S7-1500 EN Input BOOL I, Q, M, D, L I, Q, M, D, L, T, C Enable input ENO Output BOOL I, Q, M, D, L I, Q, M, D, L Enable output MIN Input Integers, floating-point numbers I, Q, M, D, L or constant I, Q, M, D, L or constant Low limit of the value range WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameter VALUE Declaration Data type Input Floating-point numbers Memory area S7-1200 S7-1500 I, Q, M, D, L or constant I, Q, M, D, L or constant Description Value to be scaled. If you enter a constant, you must declare it. MAX Input Integers, floating-point numbers I, Q, M, D, L or constant I, Q, M, D, L or constant High limit of the value range OUT Output Integers, floating-point numbers I, Q, M, D, L I, Q, M, D, L Result of scaling You can select the data type of the instruction from the "<???>" drop-down list of the instruction box. For additional information on valid data types, refer to "See also". For additional information on declaring constants, refer to "See also". Example The following example shows how the instruction works: 6&$/(B; 5($/ 7DJ,Q 7DJB0,1 WR ',17 (1 0,1 7DJB9DOXH 9$/8( 287 7DJB0$; 0$; (12 7DJB5HVXOW 7DJ2XW 6 The following table shows how the instruction works using specific operand values: Parameter Operand Value MIN Tag_MIN 10 VALUE Tag_Value 0.5 MAX Tag_MAX 30 OUT Tag_Result 20 If the operand "TagIn" has the signal state "1", the "Scale" instruction is executed. The value at input "Tag_Value" is scaled to the range of values defined by the values at inputs "Tag_MIN" and "Tag_MAX". The result is stored at output "Tag_Result". If the instruction is executed without errors, the ENO enable output has the signal state "1" and the "TagOut" output is set. WinCC Basic V13.0 System Manual, 02/2014 2221 Programming the PLC 9.7 References See also Overview of the valid data types (Page 1204) Basics of the EN/ENO mechanism (Page 1299) NORM_X: Normalize (Page 2222) Declaring global constants (Page 1320) NORM_X: Normalize Description You can use the instruction "Normalize" to normalize the value of the tag at the VALUE input by mapping it to a linear scale. You can use the parameters MIN and MAX to define the limits of a value range that is applied to the scale. Depending on the location of the normalized value in this value range, the result at output OUT is calculated and stored as a floating-point number. If the value to be normalized is equal to the value at input MIN, output OUT returns the value "0.0". If the value to be normalized is equal to the value at input MAX, output OUT returns the value "1.0". The following figure shows an example of how values can be normalized: 287 0,1 0$; 9$/8( The "Normalize" instruction works with the following equation: OUT = (VALUE - MIN) / (MAX - MIN) Enable output ENO has the signal state "0" if one of the following conditions is fulfilled: Enable input EN has the signal state "0". The value at input MIN is greater than or equal to the value at input MAX. 2222 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References The value of a specified floating-point number is outside the range of the normalized numbers according to IEEE-754. The value at input VALUE is NaN (result of an invalid arithmetic operation). Note For more information on the conversion of analog values, refer to the respective manual. Parameters The following table shows the parameters of the instruction "Normalize": Parameters EN Declaration Data type Memory area S7-1200 S7-1500 Description Input BOOL I, Q, M, D, L I, Q, M, D, L, T, C Enable input ENO Output BOOL I, Q, M, D, L I, Q, M, D, L Enable output MIN Input Integers, floating-point numbers I, Q, M, D, L or constant I, Q, M, D, L or constant Low limit of the value range VALUE 1) Input Integers, floating-point numbers I, Q, M, D, L or constant I, Q, M, D, L or constant Value to be normalized. MAX 1) Input Integers, floating-point numbers I, Q, M, D, L or constant I, Q, M, D, L or constant High limit of the value range OUT Output Floating-point numbers I, Q, M, D, L I, Q, M, D, L Result of the normalization 1) 1) If you use constants in these three parameters, you only need to declare one of them. You can select the data type of the instruction from the "<???>" drop-down list of the instruction box. For additional information on valid data types, refer to "See also". For additional information on declaring constants, refer to "See also". WinCC Basic V13.0 System Manual, 02/2014 2223 Programming the PLC 9.7 References Example The following example shows how the instruction works: 1250B; ',17 7DJ,Q 7DJB0,1 WR 5($/ (1 0,1 7DJB9DOXH 9$/8( 287 7DJB0$; 0$; (12 7DJB5HVXOW 7DJ2XW 6 The following table shows how the instruction works using specific operand values: Parameter Operand Value MIN Tag_MIN 10 VALUE Tag_Value 20 MAX Tag_MAX 30 OUT Tag_Result 0.5 If the operand "TagIn" has the signal state "1", the "Normalize" instruction is executed. The value at input "Tag_Value" is assigned to the range of values defined by the values at inputs "Tag_MIN" and "Tag_MAX". The tag value at input "Tag_Value" is normalized corresponding to the defined value range. The result is stored as a floating-point number at output "Tag_Result". If the instruction is executed without errors, the ENO enable output has the signal state "1" and the "TagOut" output is set. See also Overview of the valid data types (Page 1204) Basics of the EN/ENO mechanism (Page 1299) SCALE_X: Scale (Page 2219) Declaring global constants (Page 1320) Other SCALE: Scale Description Use the Scale instruction to convert the integer at the IN parameter into a floating-point number, which can be scaled in physical units between a low limit value and a high limit value. You can 2224 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References use the LO_LIM and HI_LIM parameters to specify the low limit and high limit of the value range to which the input value is scaled. The result of the instruction is output at the OUT parameter. The "Scale" instruction works with the following equation: OUT = [((FLOAT (IN) - K1)/(K2-K1)) (HI_LIM-LO_LIM)] + LO_LIM The values of the constants "K1" and "K2" are determined by the signal state on the BIPOLAR parameter. The following signal states are possible on the BIPOLAR parameter: Signal state "1": It is assumed that the value at the IN parameter is bipolar and in a value range between -27648 and 27648. In this case the "K1" constant has the value "-27648.0" and the "K2" constant the value "+27648.0". Signal state "0": It is assumed that the value at the IN parameter is unipolar and in a value range between 0 and 27648. In this case the "K1" constant has the value "0.0" and the "K2" constant the value "+27648.0". When the value at the IN parameter is greater than the value of the constant "K2", the result of the instruction is set to the value of the high limit (HI_LIM) and an error is output. When the value at the IN parameter is less than the value of the constant "K1", the result of the instruction is set to the value of the low limit value (LO_LIM) and an error is output. When the indicated low limit value is greater than the high limit value (LO_LIM > HI_LIM), the result is scaled in reverse proportion to the input value. Parameters The following table shows the parameters of the "Scale" instruction: Parameter Declaration Data type Memory area S7-1200 S7-1500 Description EN Input BOOL I, Q, M, D, L I, Q, M, D, L, T, C Enable input ENO Output BOOL I, Q, M, D, L I, Q, M, D, L Enable output IN Input INT I, Q, M, D, L, P or constant I, Q, M, D, L, P or constant Input value to be scaled. HI_LIM Input REAL I, Q, M, D, L, P or constant I, Q, M, D, L, P or constant High limit LO_LIM Input REAL I, Q, M, D, L, P or constant I, Q, M, D, L, P or constant Low limit BIPOLAR Input BOOL I, Q, M, D, L or constant I, Q, M, D, L or constant Indicates if the value at IN parameter is to be interpreted as bipolar or unipolar. The parameter can assume the following values: 1: Bipolar 0: Unipolar WinCC Basic V13.0 System Manual, 02/2014 2225 Programming the PLC 9.7 References Parameter Declaration Data type Memory area S7-1200 Description S7-1500 OUT Output REAL I, Q, M, D, L, P I, Q, M, D, L, P Result of the instruction RET_VAL Output WORD I, Q, M, D, L, P I, Q, M, D, L, P Error information Parameters RET_VAL The following table shows the meaning of the values of the RET_VAL parameter: Error code* (W#16#...) Explanation 0000 No error 0008 The value of the IN parameter is greater than the value of the "K2" constant or less than the value of the "K1" constant. General error information See also: "GET_ERR_ID: Get error ID locally *The error codes can be displayed as integer or hexadecimal value in the program editor. For information on toggling display formats, refer to "See also". Example The following example shows how the instruction works: 6&$/( 7DJ,Q 7DJB,QSXW9DOXH (1 ,1 7DJB+LJK/LPLW +,B/,0 5(7B9$/ 7DJB/RZ/LPLW /2B/,0 287 7DJB2XWSXW9DOXH %,32/$5 (12 7DJ2XW 7DJB%LSRODU 7DJB(UURU&RGH The following table shows how the instruction works using specific operand values: 2226 Parameter Operand Value IN Tag_InputValue 22 HI_LIM Tag_HighLimit 100.0 LO_LIM Tag_LowLimit 0.0 BIPOLAR Tag_Bipolar 1 OUT Tag_OutputValue 50.03978588 RET_VAL Tag_ErrorCode W#16#0000 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References See also Overview of the valid data types (Page 1204) Basics of the EN/ENO mechanism (Page 1299) GET_ERR_ID: Get error ID locally (Page 2248) UNSCALE: Unscale Description The "Unscale" instruction unscales the floating-point number at the IN parameter into physical units between a low limit value and a high limit and converts them into integers. You can use the LO_LIM and HI_LIM parameters to specify the low limit and high limit of the value range to which the input value is unscaled. The result of the instruction is output at the OUT parameter. The "Unscale" instruction works with the following equation: OUT = [ ((IN-LO_LIM)/(HI_LIM-LO_LIM)) (K2-K1) ] + K1 The values of the constants "K1" and "K2" are determined by the signal state on the BIPOLAR parameter. The following signal states are possible on the BIPOLAR parameter: Signal state "1": It is assumed that the value at the IN parameter is bipolar and in a value range between -27648 and 27648. In this case the "K1" constant has the value "-27648.0" and the "K2" constant the value "+27648.0". Signal state "0": It is assumed that the value at the IN parameter is unipolar and in a value range between 0 and 27648. In this case the "K1" constant has the value "0.0" and the "K2" constant the value "+27648.0". When the value at the IN parameter is greater than the value of the constant "HI_LIM", the result of the instruction is set to the value of the constant (K2) and an error is output. When the value at the IN parameter is less than the value of the constant of the low limit (LO_LIM), the result of the instruction is set to the value of the constant (K1) and an error is output. Parameters The following table shows the parameters of the "Unscale" instruction: Parameter WinCC Basic V13.0 System Manual, 02/2014 Declaration Data type Memory area Description S7-1200 S7-1500 I, Q, M, D, L, T, C Enable input EN Input BOOL I, Q, M, D, L ENO Input BOOL I, Q, M, D, L I, Q, M, D, L Enable output IN Input REAL I, Q, M, D, L, P or constant I, Q, M, D, L, P or constant Input value to be unscaled to an integer value. HI_LIM Input REAL I, Q, M, D, L, P or constant I, Q, M, D, L, P or constant High limit 2227 Programming the PLC 9.7 References Parameter Declaration Data type Memory area S7-1200 S7-1500 Description LO_LIM Input REAL I, Q, M, D, L, P or constant I, Q, M, D, L, P or constant Low limit BIPOLAR Input BOOL I, Q, M, D, L or constant I, Q, M, D, L or constant Indicates if the value at the IN parameter is to be interpreted as bipolar or unipolar. The parameter can assume the following values: 1: Bipolar 0: Unipolar OUT Output INT I, Q, M, D, L, P I, Q, M, D, L, P Result of the instruction RET_VAL Output WORD I, Q, M, D, L, P I, Q, M, D, L, P Error information Parameters RET_VAL The following table shows the meaning of the values of the RET_VAL parameter: Error code* (W#16#...) Explanation 0000 No error 0008 The value of the IN parameter is greater than the value of the high limit (HI_LIM) or less than the value of the low limit (LO_LIM). General error information See also: "GET_ERR_ID: Get error ID locally *The error codes can be displayed as integer or hexadecimal value in the program editor. For information on toggling display formats, refer to "See also". Example The following example shows how the instruction works: 816&$/( 7DJ,Q 7DJB,QSXW9DOXH ,1 7DJB+LJK/LPLW +,B/,0 5(7B9$/ 7DJB/RZ/LPLW /2B/,0 287 7DJB2XWSXW9DOXH %,32/$5 (12 7DJ2XW 7DJB%LSRODU 2228 (1 7DJB(UURU&RGH WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References The following table shows how the instruction works using specific operand values: Parameter Operand Value IN Tag_InputValue 50.03978588 HI_LIM Tag_HighLimit 100.0 LO_LIM Tag_LowLimit 0.0 BIPOLAR Tag_Bipolar 1 OUT Tag_OutputValue 22 RET_VAL Tag_ErrorCode W#16#0000 See also Overview of the valid data types (Page 1204) Basics of the EN/ENO mechanism (Page 1299) GET_ERR_ID: Get error ID locally (Page 2248) Program control operations JMP: Jump if RLO = 1 Description You can use the "Jump if RLO = 1" instruction to interrupt the linear execution of the program and resume it in another network. The target network must be identified by a jump label (LABEL). The jump label description is entered in the placeholder above the instruction box. The specified jump label must be in the same block in which the instruction is executed. The name you specify can only occur once in the block. Only one jumping coil can occur in a network. If the result of logic operation (RLO) at the input of the instruction is "1", the jump to the network identified by the jump label is executed. The jump direction can be towards higher or lower network numbers. If the condition at the input of the instruction is not fulfilled (RLO = 0), execution of the program continues in the next network. WinCC Basic V13.0 System Manual, 02/2014 2229 Programming the PLC 9.7 References Example The following example shows how the instruction works: 1HWZRUN &$6 7DJ,QB 1HWZRUN -03 7DJ2XWB 7DJ,QB 5 1HWZRUN &$6 7DJ2XWB 7DJ,QB 5 If the operand "TagIn_1" has the signal state "1", the instruction "Jump if RLO = 1" is executed. The linear execution of the program is interrupted and continues in Network 3, which is identified by the jump label CAS1. If input "TagIn_3" has the signal state "1", output "TagOut_3" is reset. See also Overview of the valid data types (Page 1204) JMPN: Jump if RLO = 0 Description You can use the instruction "Jump if RLO = 0" to interrupt the linear execution of the program and resume it in another network, when the result of logic operation at the input of the instruction is "0". The target network must be identified by a jump label (LABEL). The jump label description is entered in the placeholder above the instruction box. The specified jump label must be in the same block in which the instruction is executed. The name you specify can only occur once in the block. Only one jumping coil can occur in a network. If the result of logic operation (RLO) at the input of the instruction is "0", the jump to the network identified by the jump label is executed. The jump direction can be towards higher or lower network numbers. If the result of the logic operation RLO at the input of the instruction is "1", execution of the program continues in the next network. 2230 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Example The following example shows how the instruction works: 1HWZRUN &$6 7DJ,QB 1HWZRUN -031 7DJ2XWB 7DJ,QB 5 1HWZRUN &$6 7DJ2XWB 7DJ,QB 5 If the operand "TagIn_1" has the signal state "0", the instruction "Jump if RLO = 0" is executed. The linear execution of the program is interrupted and continues in Network 3, which is identified by the jump label CAS1. If input "TagIn_3" has the signal state "1", output "TagOut_3" is reset. See also Overview of the valid data types (Page 1204) LABEL: Jump label Description The jump label identifies a destination network in which the execution of the program can be resumed after the execution of a jump instruction. The jump label and the instruction in which the jump label is specified must be located in the same block. The name of a jump label can only be assigned once in a block. You can declare up to 32 jump labels when you use a CPU S7-1200 and a maximum of 256 jump labels when you use a CPU S7-1500. Only one jump label can be placed in a network. Each jump label can jump to several locations. WinCC Basic V13.0 System Manual, 02/2014 2231 Programming the PLC 9.7 References Example The following example shows how the instruction works: 1HWZRUN &$6 7DJ,QB 1HWZRUN -03 7DJ2XWB 7DJ,QB 5 1HWZRUN &$6 7DJ2XWB 7DJ,QB 5 If the operand "TagIn_1" has the signal state "1", the instruction "Jump if RLO = 1" is executed. The linear execution of the program is interrupted and continues in Network 3, which is identified by the jump label CAS1. If input "TagIn_3" has the signal state "1", output "TagOut_3" is reset. See also Overview of the valid data types (Page 1204) Adding additional inputs and outputs to FBD elements (Page 1469) Removing instruction inputs and outputs (Page 1470) JMP_LIST: Define jump list Description You can use the "Define jump list" instruction to define several conditional jumps and continue the program execution in a specific network depending on the value of the K parameter. You define the jumps with jump labels (LABEL), which you specify at the outputs of the instruction box. The number of outputs can be expanded in the instruction box. You can declare up to 32 outputs when you use a CPU S7-1200 and a maximum of 99 outputs when you use a CPU S7-1500. The numbering of the outputs begins with the value "0" and is continued in ascending order with each new output. Only jump labels can be specified at the outputs of the instruction. It is not permitted to specify instructions or operands. The value of the K parameter specifies the number of the output and thus the jump label where the program execution is to be resumed. If the value in the K parameter is greater than the number of available outputs, the program execution is resumed in the next network of the block. 2232 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References The "Define jump list" instruction is only executed if the signal state is "1" at the EN enable input. Parameters The following table shows the parameters of the "Define jump list" instruction: Parameter Declaration Data type Memory area Description EN Input BOOL I, Q, M, L, D Enable input K Input UINT I, Q, M, L, D or constant Specifies the number of the output and thus the jump that is executed. DEST0 - - - First jump label DEST1 - - - Second jump label DESTn - - - Optional jump labels For additional information on valid data types, refer to "See also". Example The following example shows how the instruction works: -03B/,67 7DJB,QSXW (1 7DJB9DOXH . '(67 /$%(/ '(67 /$%(/ '(67 /$%(/ The following table shows how the instruction works using specific operand values: WinCC Basic V13.0 System Manual, 02/2014 Parameters Operand/Jump label Value K Tag_Value 1 DEST0 LABEL0 Jump to the network that is identified with the jump label "LABEL0". DEST1 LABEL1 Jump in the network that is identified with the jump label "LABEL1". DEST2 LABEL2 Jump in the network that is identified with the jump label "LABEL2". 2233 Programming the PLC 9.7 References If the operand "Tag_Input" has the signal state "1", the instruction "Define jump list" is executed. The execution of the program is continued according to the value of the operand "Tag_Value" in the network that is identified with the jump label "LABEL1". See also Overview of the valid data types (Page 1204) Adding additional inputs and outputs to FBD elements (Page 1469) Removing instruction inputs and outputs (Page 1470) SWITCH: Jump distributor Description You can use the "Jump distributor" instruction to define multiple program jumps to be executed depending on the result of one or more comparison instructions. At the parameter K, you specify the value to be compared. This value is compared with the values that the individual inputs return. You select the type of comparison for each input. The availability of various comparison instructions depends on the data type of the instruction. The following table shows the comparison instructions that are available depending on the selected data type: Data type S7-1200 S7-1500 Bit strings Bit strings Integers, floating-point numbers, TIME, DATE, TOD Integers, floating-point numbers, TIME, LTIME, DATE, TOD, LTOD, LDT Instruction Syntax Equal == Not equal <> Equal == Not equal <> Greater or equal >= Less or equal <= Greater than > Less than < You can select the data type of the instruction from the "<???>" drop-down list of the instruction box. If you select a comparison instruction and the data type of the instruction is not yet defined, then the "<???>" drop-down list will only list those data types that are permitted for the selected comparison instruction. The execution of the instruction begins with the first comparison and is executed until a comparison condition is fulfilled. When a comparison condition is fulfilled the subsequent comparison conditions are not considered. If none of the specified comparison conditions are fulfilled, the jump is executed at output ELSE. If not jump label is defined at output ELSE, the linear execution of the program is not interrupted but instead continued in the next network. In its initial state the instruction box contains at least 2 outputs (DEST0 and DEST1). The number of outputs can be extended. The numbering of the outputs begins with the value "0" and is continued in ascending order with each new output. Specify jump labels (LABEL) at the 2234 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References outputs of the instruction. It is not permitted to specify instructions or operands at the outputs of the instruction. An input is automatically inserted to each additional output. The jump programmed at an output is executed when the comparison condition of the corresponding is fulfilled. Parameters The following table shows the parameters of the instruction "Jump distributor": Parameters Declarat ion Data type S7-1200 S7-1500 Memory area Description EN Input BOOL BOOL I, Q, M, D, L Enable input K Input UINT UINT I, Q, M, D, L or constant Specifies the value to be compared. <Comparison values> Input Bit strings, integers, floatingpoint numbers, TIME, DATE, TOD Bit strings, I, Q, M, D, L or integers, constant floatingpoint numbers, TIME, LTIME, DATE, TOD, LTOD, LDT Input values with which the value of the parameter K is compared. DEST0 - - - - First jump label DEST1 - - - - Second jump label DEST(n) - - - - Optional jump labels (n = 2 to 99) ELSE - - - - Program jump which is executed if none of the comparison conditions are fulfilled. For additional information on valid data types, refer to "See also". WinCC Basic V13.0 System Manual, 02/2014 2235 Programming the PLC 9.7 References Example The following example shows how the instruction works: 6:,7&+ 8,17 7DJB,QSXW (1 7DJB9DOXH . 7DJB9DOXHB '(67 /$%(/ 7DJB9DOXHB ! '(67 /$%(/ 7DJB9DOXHB '(67 /$%(/ (/6( /$%(/ The following table shows how the instruction works using specific operand values: Parameters Operand/Jump label Value K Tag_Value 23 == Tag_Value_1 20 > Tag_Value_2 21 < Tag_Value_3 19 DEST0 LABEL0 Jump to jump label "LABEL0", if the value of parameter K is equal to 20. DEST1 LABEL1 Jump to jump label "LABEL1", if the value of parameter K is greater than 21. DEST2 LABEL2 Jump to jump label "LABEL2", if the value of parameter K is less than 19. ELSE LABEL 3 Jump to jump label "LABEL3", if none of the comparison conditions are fulfilled. If the operand "Tag_Input" changes to signal state "1", the instruction "Jump distributor" is executed. The execution of the program is continued in the network that is identified with the jump label "LABEL1". See also Overview of the valid data types (Page 1204) Adding additional inputs and outputs to FBD elements (Page 1469) Removing instruction inputs and outputs (Page 1470) 2236 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References RET: Return Description You can use the instruction "Return" to stop the execution of a block. This results in three types, in which the block processing can be completed: Without call of the "Return" instruction The block is exited after the execution of the last network. The ENO of the call function is set to the signal state "1". Call of the "Return" instruction with logic operation (see example) If the left connector has the signal state "1", then the block is exited. The ENO of the function call corresponds to the operand. Call of the "Return" instruction without logic operation The block is exited. The ENO of the function call corresponds to the operand. Note Only one jumping coil may be used in a network ("Return", "Jump if RLO = 1", "Jump if RLO = 0"). If the result of logic operation (RLO) at the input of the instruction "Return" is "1", the execution of the program is terminated in the currently called block and continued after the call function in the calling block (for example, in the calling OB). The status (ENO) of the call function is determined by the parameter of the instruction. This can assume the following values: RLO TRUE/FALSE <Operand> To set the parameter values, double-click the instruction and select the corresponding value in the drop-down list. The following table shows the status of the call function when the instruction "Return" is programmed in a network within the called block: RLO Parameter value ENO of the call function 1 RLO 1 TRUE 1 FALSE 0 <Operand> <Operand> RLO In this case, the execution of the program continues in the next network of the called block. 0 TRUE FALSE <Operand> If an OB is completed, another block is selected by the priority class system and started or reexecuted. WinCC Basic V13.0 System Manual, 02/2014 2237 Programming the PLC 9.7 References If the OB program cycle was completed, it is restarted. If an OB, which interrupted another block (e.g. an Alarm OB), is completed, then the interrupted block (e.g. OB program cycle) is executed. Parameters The following table shows the parameters of the instruction "Return": Parameters Declaration Data type Memory area Description RLO - - - Is set to the signal state of the RLO. TRUE - - - 1 FALSE - - - 0 <Operand> Input BOOL I, Q, M, D, L Signal state of the specified operand Status of the calling function when RLO = 1: Example The following example shows how the instruction works: 7DJ,QB 7DJ,QB ! )$/6( 5(7 If the operands "TagIn_1" or "TagIn_2" have signal state "1", the instruction "Return" is executed. Program execution in the called block is terminated and continues in the calling block. The enable output ENO of the call function is reset to signal state "0". See also Overview of the valid data types (Page 1204) Runtime control ENDIS_PW: Limit and enable password legitimation Description You use the "Limit and enable password legitimation" instruction to specify whether passwords configured for the CPU are legitimized or not. In this way, you can prevent legitimized connections, even if the correct password is known. 2238 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References When the instruction is called and the REQ parameter has the signal state "0", the currently set state is displayed at the output parameters. If changes have been made to the input parameters, these are not transferred to the output parameters. When the instruction is called and the REQ parameter has the signal state "1", the signal state is taken from the input parameters (F_PWD, FULL_PWD, R_PWD, HMI_PWD). FALSE means that legitimation per password is not permitted; TRUE means the password can be used. Disable or enabling of the passwords can be allowed or prohibited individually. For example, all passwords can be prohibited except the fail-safe password. You can thus limit access options to a small user group. The output parameters (F_PWD_ON, FULL_PWD_ON, R_PWD_ON, HMI_PWD_ON) always show the current status of the password use, regardless of the REQ parameter. Passwords that are not configured must have the signal state TRUE at the input and return the signal state TRUE at the output. The fail-safe password can only be configured for an FCPU and must therefore always be interconnected with the signal state TRUE in a standard CPU. If the instruction returns an error, the call has no effect and the previous lock is still in effect. Disabled passwords can be enabled again under the following conditions: The CPU is reset to its factory settings. The front panel of the S7-1500 CPU supports a dialog that allows you to navigate to the appropriate menu in which the passwords can be enabled again. When you call the "Limit and enable password legitimation" instruction, the input parameter of the desired password has the signal state "1". Set the mode selector to STOP. The restriction to password legitimation is re-established as soon as the switch is set back to RUN. Plugging an empty memory card (transfer module or program card) into an S7-1200 CPU. The transition from POWER OFF to POWER ON disables the protection in the S7-1200 CPU. The "Limit and enable password legitimation" instruction must be called once again in the program (e.g. in the startup OB). Note The "Limit and enable password legitimation" instruction blocks access from HMI systems if the HMI password has not been enabled. Note Existing legitimized connections retain their access rights and you cannot use the "Limit and enable password legitimation" instruction to restrict them. Preventing unintentional lockout on an S7-1500 CPU The settings can be made on the front panel of the CPU and the CPU saves the most recent setting. To prevent accidental lockout, the protection can be disabled by setting the mode selector to STOP with an S7-1500 CPU. The protection is automatically enabled again by setting mode WinCC Basic V13.0 System Manual, 02/2014 2239 Programming the PLC 9.7 References selector to RUN without having to call the "Limit and enable password legitimation" instruction again or taking additional actions on the front panel. Preventing unintentional lockout on an S7-1200 CPU Because the S7-1200 CPU does not have a mode switch, protection is disabled with POWER OFF - POWER ON. This means that it is possible and advisable to prevent accidental lockout with the help of specific program sequences within your program. To do so, program a time control either by means of a cyclic interrupt OB or a timer in the Main OB (OB 1). This gives you the option of calling the "Limit and enable password legitimation" instruction in the respective OB (e.g., OB 1 or OB 35) relatively quickly after a transition from POWER OFF to POWER ON and the associated disabling of the protection. Call the instruction in the startup OB (OB 100) to keep the time window in which the instruction is inactive and there are no limitations for password legitimation relatively small. This procedure will give you the best possible protection from unauthorized access. If there has been an accidental lockout, you can skip the call in the startup OB (by querying an input parameter, for example) and you have the set time (for example, 10 seconds up to 1 minute) to establish a connection to the CPU before the lock becomes active once again. If there is no timer in your program code and a lockout has occurred, insert an empty transfer card or an empty program card into the CPU. The empty transfer card or program card deletes the internal load memory of the CPU. You must then download the user program once again from STEP 7 to the CPU. Procedure for lost passwords with an S7-1200 CPU If you have lost the password for a password-protected S7-1200 CPU, delete the passwordprotected program with an empty transfer card or program card. The empty transfer card or program card deletes the internal load memory of the CPU. You can then load a new user program from STEP 7 Basic in the CPU. WARNING Inserting an empty transfer card When you insert a transfer card in a CPU during runtime, the CPU goes to STOP mode. If operating states are unstable, controllers may fail and thus cause the uncontrolled operation of the controlled devices. This leads to an unforeseen operation of the automation system which can cause deadly or serious injuries and/or damage to property. Once you have pulled the transfer card, the content of the transfer card is available in the internal load memory. Make sure that the card does not include a program at this point. 2240 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References WARNING Inserting an empty program card When you insert a program card in a CPU during runtime, the CPU goes to STOP mode. If operating states are unstable, controllers may fail and thus cause the uncontrolled operation of the controlled devices. This leads to an unforeseen operation of the automation system which can cause deadly or serious injuries and/or damage to property. Make sure that the program card is empty. The internal load memory is copied to the empty program card. Once you have pulled the previously empty program card, the internal load memory is empty. You must remove the transfer card or program card before you put the CPU into RUN mode. Effects of password use on the operating modes The following table shows what effects the password use by means of the "Limit and enable password legitimation" instruction has on the operating modes and the corresponding user actions. Action Password protection by means of the instruction Basic state after Not activated Operating mode switch to STOP (no restrictions) Reset memory manually (PG, switch, change of MC (Motion Control)) Reset to factory setting Basic state after POWER ON S7-1200 CPU: The lock is disabled and the instruction must be called once again in the program (e.g., in the startup OB). S7-1500 CPU: Enabled (if a lock was activated before POWER OFF). The option of not allowing passwords is retentive. Operating mode transition RUN/STARTUP/HOLD -> STOP (by terminating the instruction, an error or communication) or STOP -> STARTUP/RUN/HOLD Activated Passwords still cannot be used. Parameters The following table shows the parameters of the "Limit and enable password legitimation" instruction: Parameter Declaratio n Data type Memory area Description EN Input BOOL I, Q, M, D, L Enable input ENO Output BOOL I, Q, M, D, L Enable output WinCC Basic V13.0 System Manual, 02/2014 2241 Programming the PLC 9.7 References Parameter Declaratio n Data type Memory area Description REQ Input BOOL I, Q, M, D, L or constant When the REQ parameter has the signal state "0", the currently set signal state of the passwords is queried. F_PWD Input BOOL I, Q, M, D, L or constant Read/write access including fail-safe F_PWD = "0": Do not allow password F_PWD = "1": Allow password FULL_PW D Input BOOL I, Q, M, D, L or constant Read/write access FULL_PWD = "0": Do not allow password FULL_PWD = "1": Allow password R_PWD Input BOOL I, Q, M, D, L or constant Read access R_PWD = "0": Do not allow password R_PWD = "1": Allow password HMI_PWD Input BOOL I, Q, M, D, L or constant HMI access HMI_PWD = "0": Do not allow password HMI_PWD = "1": Allow password F_PWD_O Output N BOOL FULL_PW D_ON BOOL I, Q, M, D, L Read/write access including fail-safe F_PWD_ON = "0": Password not allowed F_PWD_ON = "1": Password allowed Output I, Q, M, D, L Read/write access status FULL_PWD_ON = "0": Password not allowed FULL_PWD_ON = "1": Password allowed R_PWD_ ON Output BOOL I, Q, M, D, L Read-access status R_PWD_ON = "0": Password not allowed R_PWD_ON = "1": Password allowed HMI_PWD Output _ON BOOL RET_VAL WORD I, Q, M, D, L HMI-access status HMI_PWD_ON = "0": Password not allowed HMI_PWD_ON = "1": Password allowed Output I, Q, M, D, L Error information For additional information on valid data types, refer to "See also". Parameters RET_VAL The following table shows the meaning of the values of the RET_VAL parameter: Error code* Explanation (W#16#...) 2242 0000 No error 8090 The "Limit and enable password legitimation" instruction is not supported 80D0 The password for fail-safe is not configured. The signal state must be TRUE for standard CPUs. 80D1 The read/write access is not configured 80D2 The read access is not configured WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Error code* Explanation (W#16#...) 80D3 The HMI access is not configured *The error codes can be displayed as integer or hexadecimal value in the program editor. For information on toggling display formats, refer to "See also". See also Overview of the valid data types (Page 1204) Basics of error handling (Page 1519) Principles of local error handling (Page 1521) Error output priorities (Page 1522) Enabling local error handling for a block (Page 1523) RE_TRIGR: Restart cycle monitoring time Description You can use the "Restart cycle monitoring time" instruction to restart the cycle time monitoring of the CPU. The cycle monitoring time then starts over for the duration you have set in the CPU configuration. The instruction "Restart cycle monitoring time" can be called regardless of the priority in all blocks. If the instruction is called in a block with a higher priority, such as a hardware interrupt, a diagnostics interrupt or a cyclic interrupt, the instruction is not executed and the ENO enable output is set to signal state "0". The instruction "Restart cycle monitoring time" can be called a maximum of 10 times in a program cycle. Parameters The instruction "Restart cycle monitoring time" has no parameters. See also Overview of the valid data types (Page 1204) Basics of error handling (Page 1519) Principles of local error handling (Page 1521) Error output priorities (Page 1522) Enabling local error handling for a block (Page 1523) WinCC Basic V13.0 System Manual, 02/2014 2243 Programming the PLC 9.7 References STP: Exit program Description The instruction "Exit program" instruction is used to set the CPU to STOP mode and therefore to terminate the execution of the program. The effects of changing from RUN to STOP depend on the CPU configuration. When the (RLO) at the input of the instruction is "1", the CPU changes to STOP mode and the execution of the program is terminated. The signal state at the output of the instruction is not evaluated. If the RLO at the input of the instruction is "0", then the instruction will not be executed. Parameters The instruction "Exit program" has no parameters. See also Overview of the valid data types (Page 1204) GET_ERROR: Get error locally Description The "Get error locally" instruction is used to query the occurrence of errors within a block. This is usually to access error. If the system reports an error during the processing of the block, detailed information is stored in the operand at the ERROR output for the first error to occur during the execution of the block since the last execution of the instruction. Only operands of the "ErrorStruct" system data type can be specified at the ERROR output. The "ErrorStruct" system data type specifies the exact structure in which the information about the error is stored. Using additional instructions, you can evaluate this structure and program an appropriate response. If several errors occur in the block, the error information about the next error to occur in the instruction is output only after the first error that occurred has been remedied. Note The ERROR output is only changed if error information is present. To set the output back to "0" after handling an error, you have the following options: Declare the tag in the "Temp" section of the block interface. Reset the tag to "0" before calling the instruction. Query the enable output ENO. The enable output ENO of the instruction "Get error locally" instruction is set only if the enable input EN returns signal state "1" and error information is present. If one of these conditions is 2244 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References not fulfilled, the remaining program execution is not affected by the "Get error locally" instruction. You can find an example of how you can implement the instruction in combination with other troubleshooting options under "See also". Note The "Get error locally" instruction enables local error handling within a block. If "Get error locally" is inserted in the program code of a block, any predefined system reactions are ignored if errors occur. Parameters The following table lists the parameters of the "Get error locally" instruction: Parameter Declaration Data type Memory area Description ERROR Output ErrorStruct D, L Error information Data type "ErrorStruct" The following table lists the structure of the "ErrorStruct" data type: Structure component Data type Description ERROR_ID WORD Error ID FLAGS BYTE Shows if an error occurred during a block call. 16#01: Error during a block call 16#00: No error during a block call REACTION BYTE Default reaction: 0: Ignore (write error), 1: Continue with substitute value "0" (read error), 2: Skip instruction (system error) CODE_ADDRESS BLOCK_TYPE CREF Information about the address and type of block BYTE Type of block where the error occurred: 1: OB 2: FC 3: FB CB_NUMBER UINT Number of the code block OFFSET UDINT Reference to the internal memory BYTE Information about the address of an operand MODE WinCC Basic V13.0 System Manual, 02/2014 2245 Programming the PLC 9.7 References Structure component Data type Description OPERAND_NUMBER UINT Operand number of the machine command POINTER_NUMBER_LOCATION UINT (A) Internal pointer SLOT_NUMBER_SCOPE UINT (B) Storage area in internal memory DATA_ADDRESS NREF Information about the address of an operand BYTE (C) Memory area: AREA L: 16#40 - 4E, 86, 87, 8E, 8F, C0 - CE I: 16#81 Q: 16#82 M: 16#83 DB: 16#84, 85, 8A, 8B Range violations for a directly editable tag of data type DINT: 16#04 DB_NUMBER UINT (D) Number of the data block OFFSET UDINT (E) Relative address of the operand Structure component "ERROR_ID" The following table lists the values that can be output at the structure component "ERROR_ID": 2246 ID* (hexadecimal) ID* (decimal) Description 0 0 No error 2503 9475 Invalid pointer 2520 9504 Invalid STRING 2522 9506 Read error: Operand outside the valid range 2523 9507 Write error: Operand outside the valid range 2524 9508 Read error: Invalid operand 2525 9509 Write error: Invalid operand 2528 9512 Read error: Data alignment 2529 9513 Write error: Data alignment 252C 9516 Invalid pointer 2530 9520 Write error: Data block 2533 9523 Invalid pointer used 2538 9528 Access error: DB does not exist 2539 9529 Access error: Wrong DB used 253A 9530 Global data block does not exist 253C 9532 Faulty information or the function does not exist 253D 9533 System function does not exist 253E 9534 Faulty information or the function block does not exist 253F 9535 System block does not exist 2550 9552 Access error: DB does not exist WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References ID* (hexadecimal) ID* (decimal) Description 2551 9553 Access error: Wrong DB used 2575 9589 Error in the program nesting depth 2576 9590 Error in the local data distribution 2577 9591 The block property "Parameter passing via registers" is not selected. 25A0 9632 Internal error in TP 25A1 9633 Tag is write-protected 25A2 9634 Invalid numerical value of tag 2942 10562 Read error: Input 2943 10563 Write error: Output *The error codes can be displayed as integer or hexadecimal value in the program editor. For information on toggling display formats, refer to "See also". Example The following example shows how the instruction works: ! 5HDO )LHOG>LQGH[@ ,1 ,1 08/ $XWR 5HDO (1 )LHOG>LQGH[@ ,1 287 ,1 (12 7DJ2XW 7DJ2XWB(QDEOHG *(7B(5525 (5525 (1 (UURU (12 %<7( (UURUB5($&7,21 ,1 ,1 7DJ2XWB(QDEOHG 5 An error occurred accessing the "#Field[#index]" tag. The enable output ENO of the "Multiply" instruction and the "#TagOut_Enabled" operand have signal state "1" despite the read/access error and the multiplication is performed with the value "0.0". If this error scenario occurs, it is recommended to program the "Get error locally" instruction after the "Multiply" instruction to get the error. The error information supplied by the "Get error locally" instruction is evaluated with the comparison instruction "Equal". If the "#Error.REACTION" structure component has the value "1", this involves a read/access error and the "#TagOut_Enabled" output is reset. WinCC Basic V13.0 System Manual, 02/2014 2247 Programming the PLC 9.7 References See also Overview of the valid data types (Page 1204) Basics of error handling (Page 1519) Principles of local error handling (Page 1521) Error output priorities (Page 1522) Enabling local error handling for a block (Page 1523) Querying and fixing errors in the program code (Page 170) GET_ERR_ID: Get error ID locally Description The "Get error ID locally" instruction is used to query the occurrence of errors within a block. This is usually to access error. If the system reports during the block processing errors within the block execution since the last execution of the instruction, the error ID of the first error that occurred in the tag is stored at the ID output. Only operands of the WORD data type can be specified at the ID output. If several errors occur in the block, the error ID of the next error to occur in the instruction is output only after the first error that occurred has been remedied. Note The ID output is only changed if error information is present. To set the output back to "0" after handling an error, you have the following options: Declare the tag in the "Temp" section of the block interface. Reset the tag to "0" before calling the instruction. Query the enable output ENO. The enable output ENO of the instruction "Get error ID locally" instruction is set only if the enable input EN returns signal state "1" and error information is present. If one of these conditions is not fulfilled, the remaining program execution is not affected by the "Get error ID locally" instruction. You can find an example of how you can implement the instruction in combination with other troubleshooting options under "See also". Note The "Get error ID locally" instruction enables local error handling within a block. If the "Get error ID locally" instruction is inserted in the program code of a block, any predefined system reactions are ignored if errors occur. 2248 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameters The following table lists the parameters of the "Get error ID locally" instruction: Parameter Declaration Data type Memory area Description ID Output WORD I, Q, M, D, L Error ID ID parameter The following table lists the values that can be output at the ID parameter: ID* (hexadecimal) ID* (decimal) Description 0 0 No error 2503 9475 Invalid pointer 2520 9504 Invalid STRING 2522 9506 Read error: Operand outside the valid range 2523 9507 Write error: Operand outside the valid range 2524 9508 Read error: Invalid operand 2525 9509 Write error: Invalid operand 2528 9512 Read error: Data alignment 2529 9513 Write error: Data alignment 252C 9516 Invalid pointer 2530 9520 Write error: Data block 2533 9523 Invalid pointer used 2538 9528 Access error: DB does not exist 2539 9529 Access error: Wrong DB used 253A 9530 Global data block does not exist 253C 9532 Faulty information or the function does not exist 253D 9533 System function does not exist 253E 9534 Faulty information or the function block does not exist 253F 9535 System block does not exist 2550 9552 Access error: DB does not exist 2551 9553 Access error: Wrong DB used 2575 9589 Error in the program nesting depth 2576 9590 Error in the local data distribution 2577 9591 The block property "Parameter passing via registers" is not selected. 25A0 9632 Internal error in TP 25A1 9633 Tag is write-protected 25A2 9634 Invalid numerical value of tag 2942 10562 Read error: Input 2943 10563 Write error: Output *The error codes can be displayed as integer or hexadecimal value in the program editor. For information on toggling display formats, refer to "See also". WinCC Basic V13.0 System Manual, 02/2014 2249 Programming the PLC 9.7 References Example The following example shows how the instruction works: ! 5HDO )LHOG>LQGH[@ ,1 ,1 08/ $XWR 5HDO (1 )LHOG>LQGH[@ ,1 287 ,1 (12 7DJ2XW 7DJ2XWB(QDEOHG *(7B(55B,' ,' (1 7DJ,' (12 ,17 7DJ,' ,1 ,1 029( (1 287 ,1 (12 7DJ2XW An error occurred accessing the "#Field[#index]" tag. The enable output ENO of the "Multiply" instruction and the "#TagOut_Enabled" operand have signal state "1" despite the read/access error and the multiplication is performed with the value "0.0". If this error scenario occurs, it is recommended to program the "Get error ID locally" instruction after the "Multiply" instruction to get the error. The error information supplied by the "Get error ID locally" instruction is evaluated with the comparison instruction "Equal". If the operand "#TagID" returns the ID 2522, this involves a read/access error and the value "100.0" is written to the "#TagOut" output. See also Overview of the valid data types (Page 1204) Basics of error handling (Page 1519) Principles of local error handling (Page 1521) Error output priorities (Page 1522) Enabling local error handling for a block (Page 1523) Querying and fixing errors in the program code (Page 170) 2250 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References INIT_RD: Initialize all retain data Description The "Initialize all retain data" instruction is used to reset the retentive data of all data blocks, bit memories and SIMATIC timers and counters at the same time. The instruction can only be executed within a startup OB because the execution exceeds the program cycle duration. Parameters The following table shows the parameters of the "Initialize all retain data" instruction: Parameter Declaration Data type Memory area Description EN Input BOOL I, Q, M, D, L, T, C Enable input ENO Output BOOL I, Q, M, D, L Enable output REQ Input BOOL I, Q, M, D, L, T, C or constant If the input "REQ" has the signal state "1", all retentive data are reset. RET_VAL Output INT I, Q, M, D, L Error information: If an error occurs during the execution of the instruction, an error code is output at the RET_VAL parameter. For additional information on valid data types, refer to "See also". Parameters RET_VAL The following table shows the meaning of the values of the RET_VAL parameter: Error code* (W#16#...) Explanation 0000 No error 80B5 The instruction cannot be executed because it was not programmed within a startup OB. General error information See also: "GET_ERR_ID: Get error ID locally *The error codes can be displayed as integer or hexadecimal values in the program editor. For information on toggling display formats, refer to "See also". WinCC Basic V13.0 System Manual, 02/2014 2251 Programming the PLC 9.7 References Example The following example shows how the instruction works: ,1,7B5' 7DJ,QB 7DJB5(4 (1 5(4 (12 5(7B9$/ 7DJ2XW 7DJB5HVXOW If the operands "TagIn_1" and "Tag_REQ" have signal state "1", the instruction is executed. All retentive data of all data blocks, bit memories and SIMATIC timers and counters are reset. If the instruction is executed without errors, the ENO enable output has the signal state "1". See also Overview of the valid data types (Page 1204) Basics of error handling (Page 1519) Principles of local error handling (Page 1521) Error output priorities (Page 1522) Enabling local error handling for a block (Page 1523) Basics of the EN/ENO mechanism (Page 1299) GET_ERR_ID: Get error ID locally (Page 2248) WAIT: Configure time delay Description The "Configure time delay" instruction is used to halt the execution of the program for a set period of time. You indicate the period of time in microseconds on the WT parameter of the instruction. You can configure time delays of up to 32767 microseconds (s). The smallest possible delay time depends on the respective CPU and corresponds to the execution time of the "Configure time delay" instruction. The execution of the instruction can be interrupted by higher priority events. The "Configure time delay" instruction supplies no error information. 2252 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameters The following table shows the parameters of the "Configure time delay" instruction: Parameters Declaration Data type Memory area Description EN Input BOOL I, Q, M, D, L, T, C Enable input ENO Output BOOL I, Q, M, D, L Enable output WT Input INT I, Q, M, D, L, P or constant Time delay in microseconds (s) See also Overview of the valid data types (Page 1204) Basics of the EN/ENO mechanism (Page 1299) RUNTIME: Measure program runtime Description The "Measure program runtime" instruction is used to measure the runtime of the entire program, individual blocks or command sequences. If you want to measure the runtime of your entire program, call the instruction "Measure program runtime" in OB1. Measurement of the runtime is started with the first call and the output RET_VAL returns the runtime of the program after the second call. The measured runtime includes all CPU processes that can occur during the program execution, for example, interruptions caused by higher-level events or communication. The instruction "Measure program runtime" reads an internal counter of the CPU and write the value to the IN-OUT parameter MEM. The instruction calculates the current program runtime according to the internal counter frequency and writes it to output RET_VAL. If you want to measure the runtime of individual blocks or individual command sequences, you need three separate networks. Call the instruction "Measure program runtime" in an individual network within your program. You set the starting point of the runtime measurement with this first call of the instruction. Then you call the required program block or the command sequence in the next network. In another network, call the "Measure program runtime" instruction a second time and assign the same memory to the IN-OUT parameter MEM as you did during the first call of the instruction. The "Measure program runtime" instruction in the third network reads an internal CPU counter and calculates the current runtime of the program block or the command sequence according to the internal counter frequency and writes it to the output RET_VAL. WinCC Basic V13.0 System Manual, 02/2014 2253 Programming the PLC 9.7 References The "Measure program runtime" instruction uses an internal high-frequency counter to calculate the time. If the counter overruns, the instruction returns values <= 0.0. Ignore these runtime values. Note The runtime of a command sequence cannot be determined exactly, because the sequence of instructions within a command sequence is changed during optimized compilation of the program. Parameters The following table lists the parameters of the "Measure program runtime" instruction: Parameters Declaration Data type Memory area Description EN Input BOOL I, Q, M, D, L, T, C Enable input ENO Output BOOL I, Q, M, D, L Enable output MEM InOut LREAL M, D, L Saves the starting point of the runtime measurement. RET_VAL Output LREAL I, Q, M, D, L Returns the measured runtime in seconds For additional information on valid data types, refer to "See also". Example The following example shows how the instruction works based on the runtime calculation of a program block: Network 1: 5817,0( 7DJ,Q 7DJ0HPRU\ (1 (12 0(0 5(7B9$/ 7DJ5HVXOW Network 2: '% %HVWBEHIRUHBGDWHB'% )% %HVWBEHIRUHBGDWH (1 (12 Network 3: 2254 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References 5817,0( 7DJ,Q 7DJ0HPRU\ (1 0(0 (12 5(7B9$/ 7DJ5HVXOWB5XQWLPH When the "TagIn1" operand in network 1 has the signal state "1", the instruction is executed. The starting point for the runtime measurement is set with the first call of the instruction and buffered as reference for the second call of the instruction in the "TagMemory" operand. The "Best_before_date" program block FB1 is called in network 2. When the FB1 program block has been executed and the "TagIn1" operand has the signal state "1", the instruction in network 3 is executed. The second call of the instruction calculates the runtime of the program block and writes the result to the output RET_VAL. See also Overview of the valid data types (Page 1204) Basics of error handling (Page 1519) Principles of local error handling (Page 1521) Error output priorities (Page 1522) Enabling local error handling for a block (Page 1523) Word logic operations AND: AND logic operation Description You can use the instruction "AND logic operation" to link the value at input IN1 to the value at input IN2 bit-by-bit by AND logic and query the result at the output OUT. When the instruction is executed, bit 0 of the value at input IN1 is linked by AND logic to bit 0 of the value at input IN2. The result is stored in bit 0 of output OUT. The same logic operation is executed for all other bits of the specified values. In its initial state the instruction box contains at least 2 inputs (IN1 and IN2). The number of inputs can be extended. The inserted inputs are numbered in ascending order in the box. During the execution of the instruction, the values of all available input parameters are linked by AND logic. The result is stored at output "OUT". The result bit has the signal state "1" only when both of the bits in the logic operation also have signal state "1". If one of the two bits of the logic operation has signal state "0", the corresponding result bit is reset. WinCC Basic V13.0 System Manual, 02/2014 2255 Programming the PLC 9.7 References Parameters The following table shows the parameters of the instruction "AND logic operation": Parameters Declaration Data type Memory area S7-1200 S7-1500 Description EN Input BOOL I, Q, M, D, L I, Q, M, D, L, T, C Enable input ENO Output BOOL I, Q, M, D, L I, Q, M, D, L Enable output IN1 Input Bit strings I, Q, M, D, L, P or constant I, Q, M, D, L, P or constant First value for logic operation IN2 Input Bit strings I, Q, M, D, L, P or constant I, Q, M, D, L, P or constant Second value for logic operation INn Input Bit strings I, Q, M, D, L, P or constant I, Q, M, D, L, P or constant Optional input values OUT Output Bit strings I, Q, M, D, L, P I, Q, M, D, L, P Result of the instruction You can select the data type of the instruction from the "<???>" drop-down list of the instruction box. For additional information on valid data types, refer to "See also". Example The following example shows how the instruction works: $1' :25' 7DJ,Q (1 7DJB9DOXH ,1 287 7DJB9DOXH ,1 (12 7DJB5HVXOW 7DJ2XW The following table shows how the instruction works using specific operand values: Parameters Operand Value IN1 Tag_Value1 0101 0101 0101 0101 IN2 Tag_Value2 0000 0000 0000 1111 OUT Tag_Result 0000 0000 0000 0101 If the operand "TagIn" has the signal state "1", the instruction "AND logic operation" is executed. The value of operand "Tag_Value1" is linked by AND to the value of the operand "Tag_Value2". The result is mapped bit-for-bit and sent to the operand "Tag_Result". The enable output ENO and the output "TagOut" are set to signal state "1". 2256 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References See also Overview of the valid data types (Page 1204) Adding additional inputs and outputs to FBD elements (Page 1469) Removing instruction inputs and outputs (Page 1470) Basics of the EN/ENO mechanism (Page 1299) OR: OR logic operation Description You can use the instruction "OR logic operation" to link the value at input IN1 to the value at input IN2 bit-by-bit by OR logic and query the result at the output OUT. When the instruction is executed, bit 0 of the value at input IN1 is linked by OR logic to bit 0 of the value at input IN2. The result is stored in bit 0 of output OUT. The same logic operation is executed for all bits of the specified tags. In its initial state the instruction box contains at least 2 inputs (IN1 and IN2). The number of inputs can be extended in the instruction box. The inserted inputs are numbered in ascending order in the box. During the execution of the instruction, the values of all available input parameters are linked by OR logic. The result is stored at output "OUT". The result bit has the signal state "1" when at least one of the two bits in the logic operation has the signal state "1". If both of the bits of the logic operation have signal state "0", the corresponding result bit is reset. Parameters The following table shows the parameters of the instruction "OR logic operation": Parameters Declaration Data type Memory area S7-1200 S7-1500 Description EN Input BOOL I, Q, M, D, L I, Q, M, D, L, T, C Enable input ENO Output BOOL I, Q, M, D, L I, Q, M, D, L Enable output IN1 Input Bit strings I, Q, M, D, L, P or constant I, Q, M, D, L, P or constant First value for logic operation IN2 Input Bit strings I, Q, M, D, L, P or constant I, Q, M, D, L, P or constant Second value for logic operation INn Input Bit strings I, Q, M, D, L, P or constant I, Q, M, D, L, P or constant Optional input values OUT Output Bit strings I, Q, M, D, L, P I, Q, M, D, L, P Result of the instruction You can select the data type of the instruction from the "<???>" drop-down list of the instruction box. For additional information on valid data types, refer to "See also". WinCC Basic V13.0 System Manual, 02/2014 2257 Programming the PLC 9.7 References Example The following example shows how the instruction works: 25 :25' 7DJ,Q (1 7DJB9DOXH ,1 287 7DJB9DOXH ,1 (12 7DJB5HVXOW 7DJ2XW The following table shows how the instruction works using specific operand values: Parameters Operand Value IN1 Tag_Value1 0101 0101 0101 0101 IN2 Tag_Value2 0000 0000 0000 1111 OUT Tag_Result 0101 0101 0101 1111 If the operand "TagIn" has the signal state "1", the instruction "OR logic operation" is executed. The value of operand "Tag_Value1" is linked by OR to the value of the operand "Tag_Value2". The result is mapped bit-for-bit and sent to the operand "Tag_Result". The enable output ENO and the output "TagOut" are set to signal state "1". See also Overview of the valid data types (Page 1204) Adding additional inputs and outputs to FBD elements (Page 1469) Removing instruction inputs and outputs (Page 1470) Basics of the EN/ENO mechanism (Page 1299) XOR: EXCLUSIVE OR logic operation Description You can use the instruction "EXCLUSIVE OR logic operation" to link the value at input IN1 to the value at input IN2 bit-by-bit by EXCLUSIVE OR logic and query the result at the output OUT. When the instruction is executed, bit 0 of the value at input IN1 is linked by EXCLUSIVE OR logic to bit 0 of the value at input IN2. The result is stored in bit 0 of output OUT. The same logic operation is executed for all other bits of the specified value. In its initial state the instruction box contains at least 2 inputs (IN1 and IN2). The number of inputs can be extended in the instruction box. The inserted inputs are numbered in ascending order in the box. During the execution of the instruction, the values of all available input parameters are linked by EXCLUSIVE OR logic. The result is stored at output "OUT". 2258 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References The result bit has the signal state "1" when one of the two bits in the logic operation has the signal state "1". If both of the bits of the logic operation have signal state "1" or "0", the corresponding result bit is reset. Parameters The following table shows the parameters of the instruction "EXCLUSIVE OR logic operation": Parameters Declaration Data type Memory area S7-1200 S7-1500 Description EN Input BOOL I, Q, M, D, L I, Q, M, D, L, T, C Enable input ENO Output BOOL I, Q, M, D, L I, Q, M, D, L Enable output IN1 Input Bit strings I, Q, M, D, L, P or constant I, Q, M, D, L, P or constant First value for logic operation IN2 Input Bit strings I, Q, M, D, L, P or constant I, Q, M, D, L, P or constant Second value for logic operation INn Input Bit strings I, Q, M, D, L, P or constant I, Q, M, D, L, P or constant Optional input values OUT Output Bit strings I, Q, M, D, L, P I, Q, M, D, L, P Result of the instruction You can select the data type of the instruction from the "<???>" drop-down list of the instruction box. For additional information on valid data types, refer to "See also". Example The following example shows how the instruction works: ;25 :25' 7DJ,Q (1 7DJB9DOXH ,1 287 7DJB9DOXH ,1 (12 7DJB5HVXOW 7DJ2XW The following table shows how the instruction works using specific operand values: Parameters Operand Value IN1 Tag_Value1 0101 0101 0101 0101 IN2 Tag_Value2 0000 0000 0000 1111 OUT Tag_Result 0101 0101 0101 1010 If the operand "TagIn" has the signal state "1", the instruction "EXCLUSIVE OR logic operation" is executed. The value of operand "Tag_Value1" is linked by EXCLUSIVE OR to the value of WinCC Basic V13.0 System Manual, 02/2014 2259 Programming the PLC 9.7 References the operand "Tag_Value2". The result is mapped bit-for-bit and sent to the operand "Tag_Result". The enable output ENO and the output "TagOut" are set to signal state "1". See also Overview of the valid data types (Page 1204) Adding additional inputs and outputs to FBD elements (Page 1469) Removing instruction inputs and outputs (Page 1470) Basics of the EN/ENO mechanism (Page 1299) INV: Create ones complement Description You can use the instruction "Create ones complement" to invert the signal status of the bits at input IN. When the instruction is processed, the value at input IN is linked to EXCLUSIVE OR by a hexadecimal mask (W#16#FFFF for 16-bit numbers or DW#16#FFFF FFFF for 32-bit number). This inverts the signal state of the individual bits that are then stored at output OUT. Parameters The following table shows the parameters of the instruction "Create ones complement": Parameters Declaration Data type Memory area Description S7-1200 S7-1500 I, Q, M, D, L, T, C Enable input EN Input BOOL I, Q, M, D, L ENO Output BOOL I, Q, M, D, L I, Q, M, D, L Enable output IN Input Bit strings, integers I, Q, M, D, L, P or constant I, Q, M, D, L, P or constant Input value OUT Output Bit strings, integers I, Q, M, D, L, P I, Q, M, D, L, P Ones complement of the value at input IN You can select the data type of the instruction from the "<???>" drop-down list of the instruction box. For additional information on valid data types, refer to "See also". 2260 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Example The following example shows how the instruction works: ,19 7DJ,Q 7DJ,QB9DOXH :25' (1 287 ,1 (12 7DJ2XWB9DOXH 7DJ2XW The following table shows how the instruction works using specific operand values: Parameters Operand Value IN TagIn_Value W#16#000F W#16#7E OUT TagOut_Value W#16#FFF0 W#16#81 If the operand "TagIn" has the signal state "1", the "Create ones complement" instruction is executed. The instruction inverts the signal state of the individual bits at input "TagIn_Value" and writes the result to output "TagOut_Value". The enable output ENO and the output "TagOut" are set to signal state "1". See also Overview of the valid data types (Page 1204) Basics of the EN/ENO mechanism (Page 1299) DECO: Decode Description You can use the "Decode" instruction to set a bit in the output value specified by the input value. The "Decode" instruction reads the value at the IN input and sets the bit in the output value whose bit position corresponds to the read value. The other bits in the output value are filled with zeroes. If the value at input IN is greater than 31, a modulo 32 instruction is executed. Parameters The following table shows the parameters of the "Decode" instruction: Parameters WinCC Basic V13.0 System Manual, 02/2014 Declaration Data type Memory area S7-1200 S7-1500 Description EN Input BOOL I, Q, M, D, L I, Q, M, D, L, T, C Enable input ENO Output BOOL I, Q, M, D, L I, Q, M, D, L Enable output 2261 Programming the PLC 9.7 References Parameters Declaration Data type Memory area Description S7-1200 S7-1500 I, Q, M, D, L, P or constant IN Input UINT I, Q, M, D, L, P or constant Position of the bit in the output value which is set. OUT Output Bit strings I, Q, M, D, L, P I, Q, M, D, L, P Output value You can select the data type of the instruction from the "<???>" drop-down list of the instruction box. For additional information on valid data types, refer to "See also". Example The following example shows how the instruction works: '(&2 8,17 WR ':25' 7DJ,Q (1 287 7DJ,QB9DOXH ,1 (12 7DJ2XWB9DOXH 7DJ2XW The following figure shows how the instruction works using specific operand values: 7DJ,QB9DOXH 7DJ2XWB9DOXH If the operand "TagIn" has the signal state "1", the "Decode" instruction is executed. The instruction reads bit number "3" from the value of the operand "TagIn_Value" and sets the third bit to the value of the operand "TagOut_Value". If no errors occur during the execution of the instruction, the output ENO has the signal state "1" and the output "TagOut" is set. See also Overview of the valid data types (Page 1204) Basics of the EN/ENO mechanism (Page 1299) ENCO: Encode Description The instruction "Encode" is used to read the bit number of the lowest bit in the input value and output it to the output OUT. 2262 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References The instruction "Encode" selects the least significant bit of the value at the IN input and writes its bit number to the tag in the output OUT. Parameters The following table shows the parameters of the instruction "Encode": Parameters Declaration Data type Memory area S7-1200 S7-1500 Description EN Input BOOL I, Q, M, D, L I, Q, M, D, L, T, C Enable input ENO Output BOOL I, Q, M, D, L I, Q, M, D, L Enable output IN Input Bit strings I, Q, M, D, L, P or constant I, Q, M, D, L, P or constant Input value OUT Output INT I, Q, M, D, L, P I, Q, M, D, L, P Output value You can select the data type of the instruction from the "<???>" drop-down list of the instruction box. For additional information on valid data types, refer to "See also". Example The following example shows how the instruction works: (1&2 ':25' 7DJ,Q 7DJ,QB9DOXH (1 287 7DJ2XWB9DOXH ,1 (12 7DJ2XW The following figure shows how the instruction works using specific operand values: 7DJ,QB9DOXH 7DJ2XWB9DOXH If the operand "TagIn" has the signal state "1", the "Encode" instruction is executed. The instruction selects bit position "3" as the least significant bit at input "TagIn_Value" and writes the value "3" to the tag at the output "TagOut_Value. If the instruction is executed without errors, the ENO enable output has the signal state "1" and the "TagOut" output is set. See also Overview of the valid data types (Page 1204) Basics of the EN/ENO mechanism (Page 1299) WinCC Basic V13.0 System Manual, 02/2014 2263 Programming the PLC 9.7 References SEL: Select Description Depending on the signal state at switch (input G), the "Select" instruction selects one of the inputs IN0 or IN1 and moves its content to the output OUT. When the input G has the signal state "0", the value at the input IN0 is moved. When the input G has the signal state "1", the value at the input IN1 is moved to the output OUT. The instruction can only be executed if the enable input EN has the signal state "1" and the tags at all parameters have the same data type. Parameters The following table shows the parameters of the "Select" instruction: Parameter Declaration Data type Memory area S7-1200 S7-1500 S7-1200 S7-1500 Description EN Input BOOL BOOL I, Q, M, D, L I, Q, M, D, L Enable input ENO Output BOOL BOOL I, Q, M, D, L I, Q, M, D, L Enable output G Input BOOL BOOL I, Q, M, D, L or constant I, Q, M, D, L, T, C or constant Switch IN0 Input Bit strings, integers, floating-point numbers, TIME, TOD, DATE, CHAR Bit strings, integers, floating-point numbers, timers, TOD, LTOD, DATE, CHAR I, Q, M, D, L, I, Q, M, D, L, P P or constant or constant First input value IN1 Input Bit strings, integers, floating-point numbers, TIME, TOD, DATE, CHAR Bit strings, integers, floating-point numbers, timers, TOD, LTOD, DATE, CHAR I, Q, M, D, L, I, Q, M, D, L, P P or constant or constant Second input value OUT Output Bit strings, integers, floating-point numbers, TIME, TOD, DATE, CHAR Bit strings, integers, floating-point numbers, timers, TOD, LTOD, DATE, CHAR I, Q, M, D, L, P Result I, Q, M, D, L, P You can select the data type of the instruction from the "<???>" drop-down list of the instruction box. For additional information on valid data types, refer to "See also". 2264 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Example The following example shows how the instruction works: 6(/ :25' 7DJ,Q 7DJ,QB* (1 * 7DJ,QB9DOXH ,1 (12 7DJ2XW 7DJ,QB9DOXH ,1 287 7DJ2XWB9DOXH The following table shows how the instruction works using specific operand values: Parameter Operand G TagIn_G 0 Value 1 IN0 TagIn_Value0 W#16#0000 W#16#4C IN1 TagIn_Value1 W#16#FFFF W#16#5E OUT TagOut_Value W#16#0000 W#16#5E If the operand "TagIn" has the signal state "1", the instruction "Select" is executed. Based on the signal state at the "TagIn_G" input, the value of the "TagIn_Value0" or "TagIn_Value1" input is selected and moved to the "TagOut_Value" output. If the instruction is executed without errors, the enable output ENO has the signal state "1" and the output "TagOut" is set. See also Overview of the valid data types (Page 1204) Basics of the EN/ENO mechanism (Page 1299) MUX: Multiplex Description You can use the instruction "Multiplex" to copy the content of a selected input to output OUT. In its initial state the instruction box contains at least 2 inputs (IN0 and IN1). The number of selectable inputs of the instruction box can be expanded. You can declare a maximum of 32 inputs. The inputs are numbered automatically in the box. Numbering starts at IN0 and is incremented continuously with each new input. You can use the parameter K to determine the input whose content should be copied to output OUT. If the value of the parameter K is greater than the number of available inputs, the content of the parameter ELSE is copied to output OUT and enable output ENO is assigned the signal state "0". The "Multiplex" instruction can only be executed if the tags have the same data type in all inputs and in the OUT output. The exception here is the parameter K, which can only be specified as an integer. The enable output ENO is reset if one of the following conditions applies: WinCC Basic V13.0 System Manual, 02/2014 2265 Programming the PLC 9.7 References Enable input EN has the signal state "0". The value of the parameter K is greater than the number of available inputs. Errors occurred during the execution of the instruction. Parameters The following table shows the parameters of the "Multiplex" instruction: Parameter Declaring Data type Memory area Description S7-1200 S7-1500 S7-1200 S7-1500 EN Input BOOL BOOL I, Q, M, D, L I, Q, M, D, L, T, C Enable input ENO Output BOOL BOOL I, Q, M, D, L I, Q, M, D, L Enable output K Input Integers Integers I, Q, M, D, L, P or constant I, Q, M, D, L, P or constant Specifies the input whose content is to be copied. If K = 0 => Paramet er IN0 If K = 1 => Paramet er IN1, etc. 2266 IN0 Input Binary numbers, integers, floatingpoint numbers, strings, TIME, TOD, DATE Binary numbers, integers, floatingpoint numbers, strings, timers, TOD, LTOD, DATE, LDT I, Q, M, D, L, P or constant I, Q, M, D, L, P or constant First input value IN1 Input Binary numbers, integers, floatingpoint numbers, strings, TIME, TOD, DATE Binary numbers, integers, floatingpoint numbers, strings, timers, TOD, LTOD, DATE, LDT I, Q, M, D, L, P or constant I, Q, M, D, L, P or constant Second input value WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameter Declaring Data type Memory area S7-1200 S7-1500 S7-1200 S7-1500 Description INn Input Binary numbers, integers, floatingpoint numbers, strings, TIME, TOD, DATE Binary numbers, integers, floatingpoint numbers, strings, timers, TOD, LTOD, DATE, LDT I, Q, M, D, L, P or constant I, Q, M, D, L, P or constant Optional input values ELSE Input Binary numbers, integers, floatingpoint numbers, strings, TIME, TOD, DATE Binary numbers, integers, floatingpoint numbers, strings, timers, TOD, LTOD, DATE, LDT I, Q, M, D, L, P or constant I, Q, M, D, L, P or constant Specifies the value to be copied when K > n. OUT Output Binary numbers, integers, floatingpoint numbers, strings, TIME, TOD, DATE Binary numbers, integers, floatingpoint numbers, strings, timers, TOD, LTOD, DATE, LDT I, Q, M, D, L, P I, Q, M, D, L, P Output to which the value is to be copied. You can select the data type for the instruction from the "<???>" drop-down list of the instruction box. For additional information on valid data types, refer to "See also". WinCC Basic V13.0 System Manual, 02/2014 2267 Programming the PLC 9.7 References Example The following example shows how the instruction works: 08; ':25' 7DJB,QSXW (1 287 7DJB1XPEHU . (12 7DJB9DOXHB ,1 7DJB9DOXHB ,1 7DJB9DOXHB (/6( 7DJB5HVXOW 7DJB2XWSXW 6 The following table shows how the instruction works using specific operand values: Parameter Operand K Tag_Number 1 Value IN0 Tag_ValueI_0 DW#16#00000000 IN1 Tag_Value_1 DW#16#003E4A7D ELSE Tag_Value_2 DW#16#FFFF0000 OUT Tag_Result DW#16#003E4A7D If the operand "Tag_Input" has the signal state "1", the "Multiplex" instruction is executed. Depending on the value of the operand "Tag_Number", the value at input "Tag_Value_1" is copied and assigned to the operand at output "Tag_Result". If no errors occur during the execution of the instruction, the outputs ENO and "Tag_Output" are set. See also Overview of the valid data types (Page 1204) Basics of the EN/ENO mechanism (Page 1299) DEMUX: Demultiplex Description You can use the instruction "Demultiplex" to copy the content of the input IN to a selected output. In its initial state the instruction box contains at least 2 outputs (OUT0 and OUT1). The number of selectable outputs can be extended in the instruction box. The outputs are numbered automatically in the box. Numbering starts at OUT0 and continues consecutively with each new output. You can use the parameter K to define the output to which the content of input IN will be copied. The other outputs will not be changed. If the value of the parameter K is greater than the number of available outputs, then the content of input IN in the parameter ELSE and the enable output ENO will be assigned to the signal state "0". The instruction "Demultiplex" can only be executed if the tags at the input IN and at all outputs are of the same data type. The exception here is the parameter K, which can only be specified as an integer. 2268 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References The enable output ENO is reset if one of the following conditions applies: Enable input EN has the signal state "0". The value of the parameter K is greater than the number of available outputs. Errors occurred during the execution of the instruction. Parameters The following table shows the parameters of the instruction "Demultiplex": Parameter Declaration Data type Memory area S7-1200 S7-1500 S7-1200 S7-1500 Description EN Input BOOL BOOL I, Q, M, D, L I, Q, M, D, L, T, C Enable input ENO Output BOOL BOOL I, Q, M, D, L I, Q, M, D, L Enable output K Input Integers Integers I, Q, M, D, L, P or constant I, Q, M, D, L, P or constant Specifies the output to which the input value (IN) will be copied. If K = 0 => Parameter OUT0 If K = 1 => Parameter OUT1, etc. WinCC Basic V13.0 System Manual, 02/2014 IN Input Binary numbers, integers, floatingpoint numbers, strings, TIME, TOD, DATE Binary numbers, integers, floatingpoint numbers, strings, timers, TOD, LTOD, DATE, LDT I, Q, M, D, L, P or constant I, Q, M, D, L, P or constant Input value OUT0 Output Binary numbers, integers, floatingpoint numbers, strings, TIME, TOD, DATE Binary numbers, integers, floatingpoint numbers, strings, timers, TOD, LTOD, DATE, LDT I, Q, M, D, L, P I, Q, M, D, L, P First output 2269 Programming the PLC 9.7 References Parameter Declaration Data type Memory area S7-1200 S7-1500 S7-1200 S7-1500 Description OUT1 Output Binary numbers, integers, floatingpoint numbers, strings, TIME, TOD, DATE Binary numbers, integers, floatingpoint numbers, strings, timers, TOD, LTOD, DATE, LDT I, Q, M, D, L, P I, Q, M, D, L, P Second output OUTn Output Binary numbers, integers, floatingpoint numbers, strings, TIME, TOD, DATE Binary numbers, integers, floatingpoint numbers, strings, timers, TOD, LTOD, DATE, LDT I, Q, M, D, L, P I, Q, M, D, L, P Optional outputs ELSE Output Binary numbers, integers, floatingpoint numbers, strings, TIME, TOD, DATE Binary numbers, integers, floatingpoint numbers, strings, timers, TOD, LTOD, DATE, LDT I, Q, M, D, L, P I, Q, M, D, L, P Output to which the input value (IN) at K > n is copied. You can select the data type for the instruction from the "<???>" drop-down list of the instruction box. For additional information on available data types, refer to "See also". 2270 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Example The following example shows how the instruction works: '(08; ':25' 7DJB,QSXW 7DJB1XPEHU 7DJB9DOXH (1 287 7DJB2XWSXWB . 287 7DJB2XWSXWB ,1 (/6( 7DJB2XWSXWB 7DJB2XWSXW (12 6 The following tables show how the instruction works using specific operand values: Table 9-26 Input values of the "Demultiplex" instruction before network execution Parameter Operand K Tag_Number 1 4 IN Tag_Value DW#16#FFFFFFFF DW#16#003E4A7D Table 9-27 Values Output values of the "Demultiplex" instruction after network execution Parameter Operand OUT0 Tag_Output_0 Unchanged Values Unchanged OUT1 Tag_Output_1 DW#16#FFFFFFFF Unchanged ELSE Tag_Output_2 Unchanged DW#16#003E4A7D The "Demultiplex" instruction is executed when input "Tag_Input" has the signal state "1". Depending on the value of the operand "Tag_Number", the value at input "IN" is copied to the corresponding output. See also Overview of the valid data types (Page 1204) Basics of the EN/ENO mechanism (Page 1299) Shift and rotate SHR: Shift right Description You can use the "Shift right" instruction to shift the content of the operand at the input IN bitby-bit to the right and query the result at the OUT output. The input N is used to specify the number of bit positions by which the specified value should be moved. WinCC Basic V13.0 System Manual, 02/2014 2271 Programming the PLC 9.7 References If the value at the input N is "0", the value at input IN is copied unchanged to the operand at output OUT. If the value at the input N is greater than the number of available bit positions, the operand value at input IN is shifted to the right by the available number of bit positions. The freed bit positions in the left area of the operand are filled by zeroes when values without signs are shifted. If the specified value has a sign, the free bit positions are filled with the signal state of the sign bit. The following figure show how the content of an integer data type operand is shifted four bit positions to the right: ,1 1 287 6LJQ ELW SODFHV 7KHVHIRXUELWV DUHORVW 7KHIUHHGELWSRVLWLRQVDUH ILOOHGZLWKWKHVLJQDOVWDWH RIWKHVLJQELW Parameters The following table shows the parameters of the instruction "Shift right": 2272 Parameter Declaration Data type Memory area Description S7-1200 S7-1500 S7-1200 S7-1500 EN Input BOOL BOOL I, Q, M, D, L I, Q, M, D, L, T, C Enable input ENO Output BOOL BOOL I, Q, M, D, L I, Q, M, D, L Enable output IN Input Bit strings, integers Bit strings, integers I, Q, M, D, L or constant I, Q, M, D, L or constant Value to be shifted N Input USINT, UINT, UDINT USINT, UINT, UDINT, ULINT I, Q, M, D, L or constant I, Q, M, D, L or constant Number of bit positions by which the value is shifted OUT Output Bit strings, integers Bit strings, integers I, Q, M, D, L I, Q, M, D, L Result of the instruction WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References You can select the data type for the instruction from the "<???>" drop-down list of the instruction box. For additional information on valid data types, refer to "See also". Example The following example shows how the instruction works: 6+5 :25' 7DJ,Q (1 7DJ,QB9DOXH ,1 287 7DJB1XPEHU 1 (12 7DJ2XWB9DOXH 7DJ2XW 6 The following table shows how the instruction works using specific operand values: Parameter Operand Value IN TagIn_Value 0011 1111 1010 1111 N Tag_Number 3 OUT TagOut_Value 0000 0111 1111 0101 If the operand "TagIn" has the signal state "1", the instruction "Shift right" is executed. The content of the operand "TagIn_Value" is shifted three bit positions to the right. The result is sent at output "TagOut_Value". If the instruction is executed without errors, the ENO enable output has the signal state "1" and the "TagOut" output is set. See also Overview of the valid data types (Page 1204) Basics of the EN/ENO mechanism (Page 1299) SHL: Shift left Description You can use the "Shift left" instruction to shift the content of the operand at the input IN bit-bybit to the left and query the result at the OUT output. The input N is used to specify the number of bit positions by which the specified value should be moved. If the value at the input N is "0", the value at input IN is copied unchanged to the operand at output OUT. If the value at the input N is greater than the number of available bit positions, the operand value at input IN is shifted to the left by the available number of bit positions. The bit positions in the right part of the operand freed by shifting are filled with zeros. WinCC Basic V13.0 System Manual, 02/2014 2273 Programming the PLC 9.7 References The following figure show how the content of an operand of the data type WORD is shifted six bit positions to the left: ,1 1 287 SODFHV 7KHIUHHGELWSRVLWLRQV DUHILOOHGZLWK]HURV 7KHVHVL[ELWV DUHORVW Parameters The following table shows the parameters of the instruction "Shift left": Parameter Declaration Data type Memory area Description S7-1200 S7-1500 S7-1200 S7-1500 EN Input BOOL BOOL I, Q, M, D, L I, Q, M, D, L, T, C Enable input ENO Output BOOL BOOL I, Q, M, D, L I, Q, M, D, L Enable output IN Input Bit strings, integers Bit strings, integers I, Q, M, D, L or constant I, Q, M, D, L or constant Value to be shifted. N Input USINT, UINT, UDINT USINT, UINT, UDINT, ULINT I, Q, M, D, L or constant I, Q, M, D, L or constant Number of bit positions by which the value is shifted. OUT Output Bit strings, integers Bit strings, integers I, Q, M, D, L I, Q, M, D, L Result of the instruction You can select the data type for the instruction from the "<???>" drop-down list of the instruction box. For additional information on valid data types, refer to "See also". 2274 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Example The following example shows how the instruction works: 6+/ :25' 7DJ,Q (1 7DJ,QB9DOXH ,1 287 7DJB1XPEHU 1 (12 7DJ2XWB9DOXH 7DJ2XW 6 The following table shows how the instruction works using specific operand values: Parameter Operand Value IN TagIn_Value 0011 1111 1010 1111 N Tag_Number 4 OUT TagOut_Value 1111 1010 1111 0000 If the operand "TagIn" has the signal state "1", the instruction "Shift left" is executed. The content of the operand "TagIn_Value" is shifted four bit positions to the left. The result is sent at output "TagOut_Value". If the instruction is executed without errors, the ENO enable output has the signal state "1" and the "TagOut" output is set. See also Overview of the valid data types (Page 1204) Basics of the EN/ENO mechanism (Page 1299) ROR: Rotate right Description You can use the "Rotate right" instruction to rotate the content of the operand at the input IN bit-by-bit to the right and query the result at the OUT output. The input N is used to specify the number of bit positions by which the specified value should be rotated. The bit positions freed by rotating on the left-hand side are filled true-to-position with the bit positions that are pushed out from the left-hand side. If the value at the input N is "0", the value at input IN is copied unchanged to the operand at output OUT. If the value at the parameter N is greater than the number of available bit positions, the operand value at input IN is nevertheless rotated by the specified number of bit positions. The following figure shows how the content of an operand of the data type DWORD is rotated three bit positions to the right: WinCC Basic V13.0 System Manual, 02/2014 2275 Programming the PLC 9.7 References ,1 1 SODFHV 287 7KHVLJQDOVWDWHRIWKHWKUHH VKLIWHGELWVLVLQVHUWHGLQWKH IUHHGSODFHV Parameters The following table shows the parameters of the instruction "Rotate right": Parameter Declaration Data type Memory area Description S7-1200 S7-1500 S7-1200 S7-1500 EN Input BOOL BOOL I, Q, M, D, L I, Q, M, D, L, T, C Enable input ENO Output BOOL BOOL I, Q, M, D, L I, Q, M, D, L Enable output IN Input Bit strings, integers Bit strings, integers I, Q, M, D, L or constant I, Q, M, D, L or constant Value to be rotated N Input USINT, UINT, UDINT USINT, UINT, UDINT, ULINT I, Q, M, D, L or constant I, Q, M, D, L or constant Number of bit positions by which the value is rotated OUT Output Bit strings, integers Bit strings, integers I, Q, M, D, L I, Q, M, D, L Result of the instruction You can select the data type for the instruction from the "<???>" drop-down list of the instruction box. For additional information on valid data types, refer to "See also". 2276 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Example The following example shows how the instruction works: 525 :25' 7DJ,Q (1 7DJ,QB9DOXH ,1 287 7DJB1XPEHU 1 (12 7DJ2XWB9DOXH 7DJ2XW 6 The following table shows how the instruction works using specific operand values: Parameter Operand Value IN TagIn_Value 0000 1111 1001 0101 N Tag_Number 5 OUT TagOut_Value 1010 1000 0111 1100 If the operand "TagIn" has the signal state "1", the instruction "Rotate right" is executed. The content of the operand "TagIn_Value" is rotated five bit positions to the right. The result is sent at output "TagOut_Value". If the instruction is executed without errors, the ENO enable output has the signal state "1" and the "TagOut" output is set. See also Overview of the valid data types (Page 1204) Basics of the EN/ENO mechanism (Page 1299) ROL: Rotate left Description You can use the "Rotate left" instruction to rotate the content of the operand at the input IN bitby-bit to the left and query the result at the OUT output. The input N is used to specify the number of bit positions by which the specified value should be rotated. The bit positions freed by rotating on the right-hand side are filled true-to-position with the bit positions that are pushed out from the left-hand side. If the value at the input N is "0", the value at input IN is copied to the operand at output OUT. If the value at the parameter N is greater than the number of available bit positions, the operand value at input IN is nevertheless rotated by the specified number of bit positions. The following figure shows how the content of an operand of the data type DWORD is rotated three bit positions to the left: WinCC Basic V13.0 System Manual, 02/2014 2277 Programming the PLC 9.7 References ,1 1 287 SODFHV 7KHVLJQDOVWDWHRIWKHWKUHH VKLIWHGELWVZLOOEHLQVHUWHGLQWKH IUHHSODFHV Parameters The following table shows the parameters of the instruction "Rotate left": Parameter Declaration Data type Memory area Description S7-1200 S7-1500 S7-1200 S7-1500 EN Input BOOL BOOL I, Q, M, D, L I, Q, M, D, L, T, C Enable input ENO Output BOOL BOOL I, Q, M, D, L I, Q, M, D, L Enable output IN Input Bit strings, integers Bit strings, integers I, Q, M, D, L or constant I, Q, M, D, L or constant Value to be rotated. N Input USINT, UINT, UDINT USINT, UINT, UDINT, ULINT I, Q, M, D, L or constant I, Q, M, D, L or constant Number of bit positions by which the value is rotated. OUT Output Bit strings, integers Bit strings, integers I, Q, M, D, L I, Q, M, D, L Result of the instruction You can select the data type for the instruction from the "<???>" drop-down list of the instruction box. For additional information on valid data types, refer to "See also". 2278 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Example The following example shows how the instruction works: 525 :25' 7DJ,Q (1 7DJ,QB9DOXH ,1 287 7DJB1XPEHU 1 (12 7DJ2XWB9DOXH 7DJ2XW 6 The following table shows how the instruction works using specific operand values: Parameter Operand Value IN TagIn_Value 1010 1000 1111 0110 N Tag_Number 5 OUT TagOut_Value 0001 1110 1101 0101 If input "TagIn" has the signal state "1", the instruction "Rotate left" is executed. The content of the operand "TagIn_Value" is rotated five bit positions to the left. The result is sent at output "TagOut_Value". If the instruction is executed without errors, the ENO enable output has the signal state "1" and the "TagOut" output is set. See also Overview of the valid data types (Page 1204) Basics of the EN/ENO mechanism (Page 1299) Additional instructions DRUM: Implement sequencer Description You can use the "Implement sequencer" instruction to assign the programmed values of the OUT_VAL parameter of the corresponding step to the programmed output bits (OUT1 to OUT16) and the output word (OUT_WORD). The specific step must thereby satisfy the conditions of the programmed enable mask on the S_MASK parameter while the instruction remains at this step. The instruction advances to the next step if the event for the step is true and the programmed time for the current step elapses or if the value at the JOG parameter changes from "0" to "1". The instruction is reset if the signal state on the RESET parameter changes to "1". The current step is hereby equated to the preset step (DSP). The amount of time spent on a step is determined by the product of the preset timebase (DTBP) and the preset counter value (S_PRESET) for each step. At the start of a new step, this calculated value is loaded into the DCC parameter, which contains the time remaining for the current step. If, for example the value of the DTBP parameter is "2" and the preset value for the first step is "100" (100 ms), the DCC parameter has the value "200" (200 ms). WinCC Basic V13.0 System Manual, 02/2014 2279 Programming the PLC 9.7 References A step can be programmed with a timer value, an event or both. Steps that have an event bit and the timer value "0" advance to the next step as soon as the signal state of the event bit is "1". Steps that are programmed only with a timer value start the time immediately. Steps that are programmed with an event bit and a timer value greater than "0" start the time when the signal state of the event bit is "1". The event bits are initialized with a signal state of "1". When the sequencer is on the last programmed step (LST_STEP) and the time for this step has expired, the signal state on the Q parameter is set to "1"; otherwise it is set to "0". When the Q parameter is set, the instruction remains on the step until it is reset. In the configurable mask (S_MASK), you can selected the individual bits in the output word (OUT_WORD) and set or reset the output bits (OUT1 to OUT16) by means of the output values (OUT_VAL). If a bit of the configurable mask has signal state "1", the OUT_VAL value sets or resets the corresponding bit. If the signal state of a bit of the configurable mask is "0", the corresponding bit is left unchanged. All the bits of the configurable mask for all 16 steps are initialized with a signal state of "1". The output bit at the OUT1 parameter corresponds to the least significant bit of the output word (OUT_WORD). The output bit at the OUT16 parameter corresponds to the most significant bit of the output word (OUT_WORD). When you insert the instruction in the program, the "Call options" dialog opens in which you can specify whether the block parameters will be stored in a separate data block (single instance) or as a local tag (multiple instance) in the block interface. If you create a separate data block, you will find it in the project tree in the "Program resources" folder under "Program blocks > System blocks". For additional information on this topic, refer to "See also". Parameters The following table shows the parameters of the "Implement sequencer" instruction: 2280 Parameter Declaration Data type Memory area Description EN Input BOOL I, Q, M, D, L, T, C Enable input ENO Output BOOL I, Q, M, D, L Enable output RESET Input BOOL I, Q, M, D, L or constant The signal state "1" indicates the reset condition. JOG Input BOOL I, Q, M, D, L or constant When the signal state changes from "0" to "1", the instruction advances to the next step. DRUM_EN Input BOOL I, Q, M, D, L or constant The signal state "1" causes the sequencer to advance based on the event and time criteria. LST_STEP Input BYTE I, Q, M, D, L or constant Number of the last programmed step WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameter Declaration Data type Memory area Description EVENT(i), Input BOOL I, Q, M, D, L or constant Event bit (i); 1 i 16 OUT(j), Initial signal state is "1". Output BOOL I, Q, M, D, L Output bit (j) Q Output BOOL I, Q, M, D, L The signal state "1" indicates that the time for the last step has elapsed. OUT_WORD Output WORD I, Q, M, D, L, P Word address to which the sequencer writes the output values. ERR_CODE Output WORD I, Q, M, D, L, P Error information JOG_HIS Static BOOL I, Q, M, D, L or constant JOG parameter history bit EOD Static BOOL I, Q, M, D, L or constant The signal state "1" indicates that the time for the last step has elapsed. DSP Static BYTE I, Q, M, D, L, P or constant Preset step of the sequencer DSC Static BYTE I, Q, M, D, L, P or constant Current step of the sequencer DCC Static DWORD I, Q, M, D, L, P or constant Current numerical value of the sequencer DTBP Static WORD I, Q, M, D, L, P or constant Preset timebase of the sequencer PREV_TIME Static DWORD I, Q, M, D, L or constant Previous system time S_PRESET Static ARRAY of WORD I, Q, M, D, L or constant Preset count for each step [1 to 16]; where 1 clock pulse = 1 ms. OUT_VAL Static ARRAY of BOOL I, Q, M, D, L or constant Output values for each step [1 to 16, 0 to 15]. S_MASK Static ARRAY of BOOL I, Q, M, D, L or constant Configurable mask for each step [1 to 16, 0 to 15]. Initial signal states are "1". 1 j 16 For additional information on valid data types, refer to "See also". WinCC Basic V13.0 System Manual, 02/2014 2281 Programming the PLC 9.7 References Parameters ERR_CODE The following table shows the meaning of the values of the ERR_CODE parameter: ERR_CODE* Explanation W#16#0000 No error W#16#000B The value at the LST_STEP parameter is less than 1 or greater than 16. W#16#000C The value at the DSC parameter is less than 1 or greater than the value of the LST_STEP parameter. W#16#000D The value at the DSP parameter is less than 1 or greater than the value of the LST_STEP parameter. *The error codes can be displayed as integer or hexadecimal value in the program editor. For information on toggling display formats, refer to "See also". See also Overview of the valid data types (Page 1204) Basics of the EN/ENO mechanism (Page 1299) DCAT: Discrete control-timer alarm Description The "Discrete control-timer alarm" instruction is used to accumulate the time from the point at which the CMD parameter issued the command to open or close. The time is accumulated until the preset time (PT) is exceeded or the information is received that the device was opened or closed (O_FB or C_FB) within the specified time. If the preset time is exceeded before the information on the opening or closing of the device is received, the corresponding alarm is activated. If the signal state of the command input changes state before the preset time, the time is restarted. When you insert the instruction in the program, the "Call options" dialog opens in which you can specify whether the block parameters will be stored in a separate data block (single instance) or as a local tag (multiple instance) in the block interface. If you create a separate data block, you will find it in the project tree in the "Program resources" folder under "Program blocks > System blocks". For additional information on this topic, refer to "See also". The "Discrete control-timer alarm" instruction has the following reactions to the input conditions: When the signal state of the CMD parameter changes from "0" to "1", the signal states of the parameters Q, CMD_HIS, ET (only if ET is < PT) OA and CA are influenced as follows: - The parameters Q and CMD_HIS are set to "1". - The parameters ET, OA and CA are reset to "0". When the signal state of the parameter CMD changes from "1" to "0", the parameters Q, ET (only if ET < PT), OA, CA and CMD_HIS are reset to "0". 2282 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References When the signal state of the CMD and CMD_HIS parameters is "1" and the parameter O_FB is set to "0", the time difference (ms) since the last execution of the instruction is added to the value at the parameter ET. If the value of the parameter ET exceeds the value of the parameter PT, the signal state at the parameter OA is set to "1". If the value of the ET parameter does not exceed the value of the PT parameter, the signal state at the OA parameter is reset to "0". The value at the parameter CMD_HIS is reset to the value of the parameter CMD. If the signal state of the CMD, CMD_HIS and O_FB parameters are set to "1" and the parameter C_FB has the value "0", the signal state of the parameter OA is set to "0". The value of the parameter ET is set to the value of the parameter PT. If the signal state of the O_FB parameter changes to "0", the alarm is set the next time the instruction is executed. The value of the parameter CMD_HIS is set to the value of the parameter CMD. If the CMD, CMD_HIS and C_FB parameters return signal state "0", the time difference (ms) since the last execution of the instruction is added to the value of the ET parameter. If the value of the ET parameter exceeds the value of the PT parameter, the signal state of the parameter CA is reset to "1". If the value at the parameter PT is not exceeded, the parameter CA has the signal state "0". The value of the parameter CMD_HIS is set to the value of the parameter CMD. If the parameters CMD, CMD_HIS and O_FB have the signal state "0" and the parameter C_FB is set to "1", the parameter CA is set to "0". The value of the parameter ET is set to the value of the parameter PT. If the signal state of the C_FB parameter changes to "0", the alarm is set the next time the instruction is executed. The value of the parameter CMD_HIS is set to the value of the parameter CMD. If the parameters O_FB and C_FB simultaneously have the signal state "1", the signal states of both alarm outputs are set to "1". The "Discrete control-timer alarm" instruction returns no error information. Parameters The following table shows the parameters of the "Discrete control-timer alarm" instruction: Parameter Declaration Data type Memory area Description EN Input BOOL I, Q, M, D, L, T, C Enable input ENO Output BOOL I, Q, M, D, L Enable output CMD Input BOOL I, Q, M, D, L or constant The signal state "0" indicates a "close" command. The signal state "1" indicates the "open" command. WinCC Basic V13.0 System Manual, 02/2014 O_FB Input BOOL I, Q, M, D, L or constant Feedback input when opening C_FB Input BOOL I, Q, M, D, L or constant Feedback input when closing 2283 Programming the PLC 9.7 References Parameter Declaration Data type Memory area Description Q Output BOOL I, Q, M, D, L Shows the status of the parameter CMD OA Output BOOL I, Q, M, D, L Alarm output when opening CA Output BOOL I, Q, M, D, L Alarm output when closing ET Static DINT D, L or constant Currently elapsed time, where one count = 1 ms. PT Static DINT D, L or constant Preset timer value, where one count = 1 ms. PREV_TIME Static DWORD D, L or constant Previous system time CMD_HIS Static BOOL D, L or constant CMD history bit For additional information on valid data types, refer to "See also". Example In the following example the parameter CMD changes from "0" to "1". After the execution of the instruction the parameter Q is set to "1" and the two alarm outputs OA and CA have the signal state "0". The parameter CMD_HIS of the instance data block is set to the signal state "1" and the parameter ET is reset to "0". Note You can initialize static parameters in the data block. '&$7B'% '&$7 7DJ,Q (1 4 7DJB2XWSXWB4 7DJB,QSXWB&0' &0' 2$ 7DJB2XWSXWB2$ 7DJB,QSXWB2B)% 2B)% &$ 7DJB2XWSXWB&$ 7DJB,QSXWB&B)% &B)% (12 7DJ2XW The following tables show how the instruction works using specific values. Before processing In this example, the following values are used for the input and output parameters: 2284 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameter Operand Value CMD Tag_Input_CMD TRUE O_FB Tag_Input_O_FB FALSE C_FB Tag_Input_C_FB FALSE Q Tag_Output_Q FALSE OA Tag_Output_OA FALSE CA Tag_Output_CA FALSE The following values are saved in the instance data block "DCAT_DB" of the instruction: Parameter Address Value ET DBD4 L#12 PT DBD8 L#222 CMD_HIS DBX16.0 FALSE After processing The following values are written to the output parameters after the instruction has been executed: Parameter Operand Value Q Tag_Output_Q TRUE OA Tag_Output_OA FALSE CA Tag_Output_CA FALSE The following values are saved in the instance data block "DCAT_DB" of the instruction: Parameter Address Value ET DBD4 L#0 CMD_HIS DBX16.0 TRUE See also Overview of the valid data types (Page 1204) Basics of the EN/ENO mechanism (Page 1299) MCAT: Motor control-timer alarm Description The instruction "Motor control-timer alarm" is used to accumulate the time from the point in time as of which one of the command inputs (open or close) is activated. The time is accumulated until the preset time is exceeded or the relevant feedback input indicates that the device has executed the requested operation within the specified time. If the preset time is exceeded before the feedback is received, the corresponding alarm is triggered. WinCC Basic V13.0 System Manual, 02/2014 2285 Programming the PLC 9.7 References When you insert the instruction in the program, the "Call options" dialog opens in which you can specify whether the block parameters will be stored in a separate data block (single instance) or as a local tag (multiple instance) in the block interface. If you create a separate data block, you will find it in the project tree in the "Program resources" folder under "Program blocks > System blocks". For additional information on this topic, refer to "See also". The "Motor control-timer alarm" instruction returns no error information. Execution of the "Motor control-timer alarm" instruction The following table shows the reactions of the "Motor control-timer alarm" instruction to the various input conditions: Input parameters Output parameters ET O_H IS C_H IS O_C MD C_C MD S_C MD O_F B C_F B OO CO OA CA ET O_H IS C_H IS Q Status X 1 1 X X X X X 0 0 1 1 PT 0 0 0 Alarm X X X X X X 1 1 0 0 1 1 PT 0 0 0 Alarm X X X X X 1 X X 0 0 0 0 X 0 0 1 Stop X X X 1 1 X X X 0 0 0 0 X 0 0 1 Stop X 0 X 1 0 0 X X 1 0 0 0 0 1 0 1 Start opening <PT 1 0 X 0 0 0 X 1 0 0 0 INC 1 0 1 Open X 1 0 X 0 0 1 0 0 0 0 0 PT 1 0 1 Opened >=P T 1 0 X 0 0 0 X 0 0 1 0 PT 1 0 0 Opening alarm X X 0 0 1 0 X X 0 1 0 0 0 0 1 1 Start closing <PT 0 1 0 X 0 X 0 0 1 0 0 INC 0 1 1 Close X 0 1 0 X 0 0 1 0 0 0 0 PT 0 1 1 Closed >=P T 0 1 0 X 0 X 0 0 0 0 1 PT 0 1 0 Closing alarm X 0 0 0 0 0 X X 0 0 0 0 X 0 0 1 Stopped Legend: INC Add the time difference (ms) since the last processing of the FB to ET PT PT is set to the same value as ET X Cannot be used <PT ET < PT >=PT ET >= PT If the input parameters O_HIS and C_HIS both have the signal state "1", they are immediately set to signal state "0". In this case, the last row of the above-named table (X) is valid. Because it is therefore no longer possible to check whether the input parameters O_HIS and C_HIS have the signal state "1", the output parameters are set as follows in this case: OO = FALSE CO = FALSE OA = FALSE CA = FALSE ET = PT Q = TRUE 2286 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameters The following table shows the parameters of the "Motor control-timer alarm" instruction: Parameter Declaration Data type Memory area Description EN Input BOOL I, Q, M, D, L, T, C Enable input ENO Output BOOL I, Q, M, D, L Enable output O_CMD Input BOOL I, Q, M, D, L or constant "Open" command input C_CMD Input BOOL I, Q, M, D, L or constant "Close" command input S_CMD Input BOOL I, Q, M, D, L or constant "Stop" command input O_FB Input BOOL I, Q, M, D, L or constant Feedback input when opening C_FB Input BOOL I, Q, M, D, L or constant Feedback input when closing OO Output BOOL I, Q, M, D, L "Open" output CO Output BOOL I, Q, M, D, L "Close" output OA Output BOOL I, Q, M, D, L Alarm output when opening CA Output BOOL I, Q, M, D, L Alarm output when closing Q Output BOOL I, Q, M, D, L The signal state "0" indicates an error condition. ET Static DINT D, L or constant Currently elapsed time, where one count = 1 ms PT Static DINT D, L or constant Preset timer value, where one count = 1 ms PREV_TIME Static DWORD D, L or constant Previous system time O_HIS Static BOOL D, L or constant "Open" history bit C_HIS Static BOOL D, L or constant "Close" history bit For additional information on valid data types, refer to "See also". Example The following example shows how the instruction works: Note You can initialize static parameters in the data block. WinCC Basic V13.0 System Manual, 02/2014 2287 Programming the PLC 9.7 References 0&$7B'% 0&$7 (1 22 7DJB2XWSXW2SHQ 7DJB,QSXWB2B&0' 2B&0' &2 7DJB2XWSXW&ORVHG 7DJB,QSXWB&B&0' &B&0' 2$ 7DJB2XWSXWB2$ 7DJB,QSXWB6B&0' 6B&0' &$ 7DJB2XWSXWB&$ 4 7DJB2XWSXWB4 7DJ,Q 7DJB,QSXWB2B)% 2B)% 7DJB,QSXWB&B)% &B)% (12 7DJ2XW The following tables show how the instruction works using specific values. Before processing In this example, the following values are used for the input and output parameters: Parameter Operand Value O_CMD Tag_Input_O_CMD TRUE C_CMD Tag_Input_C_CMD FALSE S_CMD Tag_Input_S_CMD FALSE O_FB Tag_Input_O_FB FALSE C_FB Tag_Input_C_FB FALSE OO Tag_OutputOpen FALSE CO Tag_OutputClosed FALSE OA Tag_Output_OA FALSE CA Tag_Output_CA FALSE Q Tag_Output_Q FALSE The following values are saved in the instance data block "MCAT_DB" of the instruction: Parameter Address Value ET DBD4 L#2 PT DBD8 L#22 O_HIS DBX16.0 TRUE C_HIS DBX16.1 FALSE After processing The following values are written to the output parameters after the instruction has been executed: 2288 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameter Operand Value OO Tag_OutputOpen TRUE CO Tag_OutputClosed FALSE OA Tag_Output_OA FALSE CA Tag_Output_CA FALSE Q Tag_Output_Q TRUE The following values are saved in the instance data block "MCAT_DB" of the instruction: Parameter Address Value ET DBD4 L#0 O_HIS DBX16.0 TRUE CMD_HIS DBX16.1 FALSE See also Overview of the valid data types (Page 1204) Basics of the EN/ENO mechanism (Page 1299) IMC: Compare input bits with the bits of a mask Description The instruction "Compare input bits with the bits of a mask" is used to compare the signal state of up to 16 programmed input bits (IN_BIT0 to IN_BIT15) with the corresponding bits of a mask. Up to 16 steps with masks can be programmed. The value of the IN_BIT0 parameter is compared with the value of the mask CMP_VAL[x,0], with "x" indicating the step number. At the CMP_STEP parameter, specify the step number of the mask that is used for the comparison. All programmed values are compared in the same manner. Unprogrammed input bits or unprogrammed bits of the mask have the default signal state FALSE. If a match is found in the comparison, the signal state of the OUT parameter is set to "1". Otherwise, the OUT parameter is set to "0". If the value of the CMP_STEP parameter is greater than 15, the instruction is not executed. An error message is output at the ERR_CODE parameter. When you insert the instruction in the program, the "Call options" dialog opens in which you can specify whether the block parameters will be stored in a separate data block (single instance) or as a local tag (multiple instance) in the block interface. If you create a separate data block, you will find it in the project tree in the "Program resources" folder under "Program blocks > System blocks". For additional information on this topic, refer to "See also". WinCC Basic V13.0 System Manual, 02/2014 2289 Programming the PLC 9.7 References Parameters The following table shows the parameters of the "Compare input bits with the bits of a mask" instruction: Parameter Declaration Data type Memory area Description EN Input BOOL I, Q, M, D, L, T, C Enable input ENO Output BOOL I, Q, M, D, L Enable output IN_BIT0 Input BOOL I, Q, M, D, L or constant Input bit 0 is compared with bit 0 of the mask. IN_BIT1 Input BOOL I, Q, M, D, L or constant Input bit 1 is compared with bit 1 of the mask. IN_BIT2 Input BOOL I, Q, M, D, L or constant Input bit 2 is compared with bit 2 of the mask. IN_BIT3 Input BOOL I, Q, M, D, L or constant Input bit 3 is compared with bit 3 of the mask. IN_BIT4 Input BOOL I, Q, M, D, L or constant Input bit 4 is compared with bit 4 of the mask. IN_BIT5 Input BOOL I, Q, M, D, L or constant Input bit 5 is compared with bit 5 of the mask. IN_BIT6 Input BOOL I, Q, M, D, L or constant Input bit 6 is compared with bit 6 of the mask. IN_BIT7 Input BOOL I, Q, M, D, L or constant Input bit 7 is compared with bit 7 of the mask. IN_BIT8 Input BOOL I, Q, M, D, L or constant Input bit 8 is compared with bit 8 of the mask. IN_BIT9 Input BOOL I, Q, M, D, L or constant Input bit 9 is compared with bit 9 of the mask. IN_BIT10 Input BOOL I, Q, M, D, L or constant Input bit 10 is compared with bit 10 of the mask. IN_BIT11 Input BOOL I, Q, M, D, L or constant Input bit 11 is compared with bit 11 of the mask. IN_BIT12 Input BOOL I, Q, M, D, L or constant Input bit 12 is compared with bit 12 of the mask. IN_BIT13 Input BOOL I, Q, M, D, L or constant Input bit 13 is compared with bit 13 of the mask. IN_BIT14 Input BOOL I, Q, M, D, L or constant Input bit 14 is compared with bit 14 of the mask. IN_BIT15 Input BOOL I, Q, M, D, L or constant Input bit 15 is compared with bit 15 of the mask. CMP_STEP Input BYTE I, Q, M, D, L, P or constant The step number of the mask used for the comparison. OUT Output BOOL I, Q, M, D, L The signal state "1" indicates that a match was found. The signal state "0" indicates that no match was found. 2290 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameter Declaration Data type Memory area Description ERR_CODE Output WORD I, Q, M, D, L, P Error information CMP_VAL Static ARRAY OF WORD I, Q, M, D, L or constant Comparison masks [0 to 15, 0 to 15]: The first number of the index is the step number and the second number is the bit number of the mask. For additional information on valid data types, refer to "See also". Parameters ERR_CODE The following table shows the meaning of the values of the ERR_CODE parameter: Error code* (W#16#...) Explanation 0000 No error 000A The value at the CMP_STEP parameter is greater than 15. *The error codes can be displayed as integer or hexadecimal value in the program editor. For information on toggling display formats, refer to "See also". See also Overview of the valid data types (Page 1204) Basics of the EN/ENO mechanism (Page 1299) SMC: Compare scan matrix Description The instruction "Compare scan matrix" is used to compare the signal state of up to 16 programmed input bits (IN_BIT0 to IN_BIT15) with the corresponding bits of the comparison masks for each step. Processing starts at step 1 and is continued until the last programmed step (LAST) or until a match is found. The input bit of the IN_BIT0 parameter is compared with the value of the mask CMP_VAL[x,0], with "x" indicating the step number. All programmed values are compared in the same manner. If a match is found, the signal state of the OUT parameter is set to "1" and the step number with the matching mask is written to the OUT_STEP parameter. Unprogrammed input bits or unprogrammed bits of the mask have the default signal state FALSE. If more than one step has a matching mask, only the first one found is indicated in the OUT_STEP parameter. If no match is found, the signal state of the OUT parameter is set to "0". In this case the value at the OUT_STEP parameter is greater by "1" than the value of the LAST parameter. When you insert the instruction in the program, the "Call options" dialog opens in which you can specify whether the block parameters will be stored in a separate data block (single instance) or as a local tag (multiple instance) in the block interface. If you create a separate data block, you will find it in the project tree in the "Program resources" folder under "Program blocks > System blocks". For additional information on this topic, refer to "See also". WinCC Basic V13.0 System Manual, 02/2014 2291 Programming the PLC 9.7 References Parameters The following table shows the parameters of the "Compare scan matrix" instruction: Parameter Declaration Data type Memory area Description EN Input BOOL I, Q, M, D, L, T, C Enable input ENO Output BOOL I, Q, M, D, L Enable output IN_BIT0 Input BOOL I, Q, M, D, L or constant Input bit 0 is compared with bit 0 of the mask. IN_BIT1 Input BOOL I, Q, M, D, L or constant Input bit 1 is compared with bit 1 of the mask. IN_BIT2 Input BOOL I, Q, M, D, L or constant Input bit 2 is compared with bit 2 of the mask. IN_BIT3 Input BOOL I, Q, M, D, L or constant Input bit 3 is compared with bit 3 of the mask. IN_BIT4 Input BOOL I, Q, M, D, L or constant Input bit 4 is compared with bit 4 of the mask. IN_BIT5 Input BOOL I, Q, M, D, L or constant Input bit 5 is compared with bit 5 of the mask. IN_BIT6 Input BOOL I, Q, M, D, L or constant Input bit 6 is compared with bit 6 of the mask. IN_BIT7 Input BOOL I, Q, M, D, L or constant Input bit 7 is compared with bit 7 of the mask. IN_BIT8 Input BOOL I, Q, M, D, L or constant Input bit 8 is compared with bit 8 of the mask. IN_BIT9 Input BOOL I, Q, M, D, L or constant Input bit 9 is compared with bit 9 of the mask. IN_BIT10 Input BOOL I, Q, M, D, L or constant Input bit 10 is compared with bit 10 of the mask. IN_BIT11 Input BOOL I, Q, M, D, L or constant Input bit 11 is compared with bit 11 of the mask. IN_BIT12 Input BOOL I, Q, M, D, L or constant Input bit 12 is compared with bit 12 of the mask. IN_BIT13 Input BOOL I, Q, M, D, L or constant Input bit 13 is compared with bit 13 of the mask. IN_BIT14 Input BOOL I, Q, M, D, L or constant Input bit 14 is compared with bit 14 of the mask. IN_BIT15 Input BOOL I, Q, M, D, L or constant Input bit 15 is compared with bit 15 of the mask. OUT Output BOOL I, Q, M, D, L The signal state "1" indicates that a match was found. The signal state "0" indicates that no match was found. ERR_CODE 2292 Output WORD I, Q, M, D, L, P Error information WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameter Declaration Data type Memory area Description OUT_STEP Output BYTE I, Q, M, D, L, P Contains the step number with the matching mask or the step number which is greater by "1" than the value of the LAST parameter, provided no match is found. LAST Static BYTE I, Q, M, D, L, P or constant Specifies the step number of the last step to be scanned for a matching mask. CMP_VAL Static ARRAY OF WORD I, Q, M, D, L or constant Comparison masks [0 to 15, 0 to 15]: The first number of the index is the step number and the second number is the bit number of the mask. For additional information on valid data types, refer to "See also". Parameters ERR_CODE The following table shows the meaning of the values of the ERR_CODE parameter: Error code* (W#16#...) Explanation 0000 No error 000E The value at the LAST parameter is greater than 15. *The error codes can be displayed as integer or hexadecimal value in the program editor. For information on toggling display formats, refer to "See also". See also Overview of the valid data types (Page 1204) Basics of the EN/ENO mechanism (Page 1299) LEAD_LAG: Lead and lag algorithm Description The "Lead and lag algorithm" instruction is used to process signals with an analog tag. The gain value at the GAIN parameter must be greater than zero. The result of the instruction "Lead and lag algorithm" is calculated using the following equation: 287 /*B7,0( /'B7,0(6$03/(B7 /'B7,0( ,1*$,1 35(9B287*$,1 /*B7,0(6$03/(B7 /*B7,0(6$03/(B7 /*B7,0(6$03/(B7 WinCC Basic V13.0 System Manual, 02/2014 35(9B,1 2293 Programming the PLC 9.7 References The "Lead and lag algorithm" instruction supplies plausible results only when processing is in fixed program cycles. The same units must be specified for the LD_TIME, LG_TIME, and SAMPLE_T parameters. At LG_TIME > 4 + SAMPLE_T, the instruction approaches the following function: OUT = GAIN * ((1 + LD_TIME * s) / (1 + LG_TIME * s)) * IN When the value of the GAIN parameter is less than or equal to zero, the calculation is not performed and an error information is output on the ERR_CODE parameter. You can use the "Lead and lag algorithm" instruction in conjunction with loops as a compensator in dynamic feed-forward control. The instruction consists of two operations. The "Lead" operation shifts the phase of the OUT output so that the output leads the input. The "Lag" operation, on the other hand, shifts the output so that the output lags behind the input. Because the "Lag" operation is equivalent to an integration, it can be used as a noise suppressor or as a low-pass filter. The "Lead" operation is equivalent to a differentiation and can therefore be used as a high-pass filter. The two instructions together (Lead and Lag) result in the output phase lagging behind the the input at lower frequencies and leading it at higher frequencies. This means that the "Lead and lag algorithm" instruction can be used as a band pass filter. When you insert the instruction in the program, the "Call options" dialog opens in which you can specify whether the block parameters will be stored in a separate data block (single instance) or as a local tag (multiple instance) in the block interface. If you create a separate data block, you will find this in the project tree in the "Program resources" folder under "Program blocks > System blocks". For additional information on this topic, refer to "See also". Parameters The following table shows the parameters of the "Lead and lag algorithm" instruction: 2294 Parameter Declaration Data type Memory area Description EN Input BOOL I, Q, M, D, L, T, C Enable input ENO Output BOOL I, Q, M, D, L Enable output IN Input REAL I, Q, M, D, L, P or constant The input value of the current sample time (cycle time) to be processed. SAMPLE_T Input INT I, Q, M, D, L, P or constant Sample time OUT Output REAL I, Q, M, D, L, P Result of the instruction ERR_CODE Output WORD I, Q, M, D, L, P Error information LD_TIME Static REAL I, Q, M, D, L, P or constant Lead time in the same unit as sample time. LG_TIME Static REAL I, Q, M, D, L, P or constant Lag time in the same unit as sample time WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameter Declaration Data type Memory area Description GAIN Static REAL I, Q, M, D, L, P or constant Gain as % / % (the ratio of the change in output to a change in input as a steady state). PREV_IN Static REAL I, Q, M, D, L, P or constant Previous input PREV_OUT Static REAL I, Q, M, D, L, P or constant Previous output For additional information on valid data types, refer to "See also". Parameters ERR_CODE The following table shows the meaning of the values of the ERR_CODE parameter: Error code* (W#16#...) Explanation 0000 No error 0009 The value at the GAIN parameter is less than or equal to zero. *The error codes can be displayed as integer or hexadecimal value in the program editor. For additional information on toggling display formats, refer to "See also". Example The following example shows how the instruction works: Note You can initialize static parameters in the data block. /($'B/$*B'% /($'B/$* 7DJ,Q 7DJB,QSXW 7DJB,QSXWB6$03/(B7 (1 ,1 6$03/(B7 287 (55B&2'( (12 7DJB2XWSXWB5HVXOW 7DJB(UURU&RGH 7DJ2XW The following table shows how the instruction works using specific operand values: Before processing In this example the following values are used for the input parameters: WinCC Basic V13.0 System Manual, 02/2014 2295 Programming the PLC 9.7 References Parameters Operand Value IN Tag_Input 2.0 SAMPLE_T Tag_InputSampleTime 10 The following values are saved in the instance data block "LEAD_LAG_DB" of the instruction: Parameters Address Value LD_TIME DBD12 2.0 LG_TIME DBD16 2.0 GAIN DBD20 1.0 PREV_IN DBD24 6.0 PREV_OUT DBD28 6.0 After processing The following values are written to the output parameters after the instruction has been executed: Parameters Operand Value OUT Tag_Output_Result 2.0 The following values are saved in the instance data block "LEAD_LAD_DB" of the instruction: Parameters Operand Value PREV_IN DBD24 2.0 PREV_OUT DBD28 2.0 See also Overview of the valid data types (Page 1204) Basics of the EN/ENO mechanism (Page 1299) SEG: Create bit pattern for seven-segment display Description The instruction "Create bit pattern for seven-segment display" is used to convert each of the four hexadecimal digits of the specified source word (IN) into an equivalent bit pattern for a seven-segment display. The result of the instruction is output in the double word on the OUT parameter. The following relation exists between the hexadecimal digits and the assignment of the 7 segments (a, b, c, d, e, f, g): 2296 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Input digit (Binary) Assignment of the segments 0000 00111111 0 0001 00000110 1 0010 01011011 2 0011 01001111 3 0100 01100110 4 0101 01101101 5 0110 01111101 6 0111 00000111 7 1000 01111111 8 1001 01100111 9 1010 01110111 A 1011 01111100 B 1100 00111001 C 1101 01011110 D 1110 01111001 E 1111 01110001 F gfedcba Display Seven-segment display (Hexadecimal) D E I J H F G Parameters The following table shows the parameters of the "Create bit pattern for seven-segment display" instruction: Parameter Declaration Data type Memory area Description EN Input BOOL I, Q, M, D, L, T, C Enable input ENO Output BOOL I, Q, M, D, L Enable output IN Input WORD I, Q, M, D, L, P or constant Source word with four hexadecimal digits OUT Output DWORD I, Q, M, D, L, P Bit pattern for the seven-segment display Example The following example shows how the instruction works: 6(* 7DJ,Q 7DJB,QSXW WinCC Basic V13.0 System Manual, 02/2014 (1 287 7DJB2XWSXW ,1 (12 7DJ2XW 2297 Programming the PLC 9.7 References The following table shows how the instruction functions using specific values: Parameters Operand Hexadecimal Binary Value IN Tag_Input W#16#1234 0001 0010 0011 0100 OUT Tag_Output DW#16065B4F66 00000110 01011011 01001111 01100110 Display: 1234 See also Overview of the valid data types (Page 1204) Basics of the EN/ENO mechanism (Page 1299) BCDCPL: Create tens complement Description You can use the "Create tens complement" instruction to create the tens complement of a seven-digit BCD number specified in the IN parameter. This instruction uses the following mathematical formula to calculate: 10000000 (as BCD) - 7-digit BCD value ---------------------------------------Tens complement (as BCD) Parameters The following table shows the parameters of the "Create tens complement" instruction: 2298 Parameter Declaration Data type Memory area Description EN Input BOOL I, Q, M, D, L, T, C Enable input ENO Output BOOL I, Q, M, D, L Enable output IN Input Bit strings I, Q, M, D, L, P or constant 7-digit BCD number ERR_CODE Output DWORD I, Q, M, D, L, P Result of the instruction WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Example The following example shows how the instruction works: %&'&3/ 7DJ,Q 7DJB,QSXW (1 (55B&2'( ,1 (12 7DJB2XWSXW 7DJ2XW The following table shows how the instruction functions using specific values: Parameter Operand Value* IN Tag_Input DW#16#01234567 ERR_CODE Tag_Output DW#16#08765433 *The error codes can be displayed as integer or hexadecimal value in the program editor. For information on toggling display formats, refer to "See also". See also Overview of the valid data types (Page 1204) Basics of the EN/ENO mechanism (Page 1299) BITSUM: Count number of set bits Description The "Count number of set bits" instruction is used to count the number of bits of an operand that is set to the signal state "1". The operand whose bits are to be counted is specified on the IN parameter. The result of the instruction is output at the RET_VAL parameter. Parameters The following table shows the parameters of the "Count number of set bits" instruction: WinCC Basic V13.0 System Manual, 02/2014 Parameter Declaration Data type Memory area Description EN Input BOOL I, Q, M, D, L, T, C Enable input ENO Output BOOL I, Q, M, D, L Enable output IN Input DWORD I, Q, M, D, L, P or constant Operand whose set bits are counted. RET_VAL Output INT I, Q, M, D, L, P Number of bits to be set 2299 Programming the PLC 9.7 References Example The following example shows how the instruction works: %,7680 7DJ,Q 7DJB,QSXW (1 ,1 5(7B9$/ (12 7DJB2XWSXW 7DJ2XW The following table shows how the instruction functions using specific values: Parameter Operand Value* IN Tag_Input DW#16#12345678 RET_VAL Tag_Output W#16#000D (13 Bits) *The error codes can be displayed as integer or hexadecimal value in the program editor. For additional information on toggling display formats, refer to "See also". See also Overview of the valid data types (Page 1204) Basics of the EN/ENO mechanism (Page 1299) 9.7.2.3 SCL Bit logic operations R_TRIG: Set tag on positive signal edge Description You can use the "Set tag on positive signal edge" instruction to set a specified tag in the instance DB when there is a "0" to "1" change in the result of logic operation (RLO). The instruction compares the current RLO at the input CLK with the RLO from the previous query, which is saved in the specified instance DB. If the instruction detects a change in the result of logic operation (RLO) from "0" to "1", there is a positive, rising edge. If a positive edge is detected, the tag in the instance DB is set to signal state "1" and the output Q returns the signal state "1" In all other cases, the signal state at the output of the instruction is "0". When you insert the instruction in the program, the "Call options" dialog opens automatically. In this dialog you can specify whether the edge memory bit is stored in its own data block (single instance) or as a local tag (multiple instance) in the block interface. If you create a separate data block, you will find it in the project tree in the "Program resources" folder under "Program blocks > System blocks". For additional information on this topic, refer to "See also". 2300 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Syntax The following syntax is used for the "Set tag on positive signal edge" instruction: SCL <Instance_DB>(CLK := <Operand>, Q => <Operand>) Parameter The following table shows the parameters of the instruction "Set tag on positive signal edge": Parameter Declaration Data type Description CLK Input BOOL Incoming signal, the edge of which is to be queried Q Output BOOL Result of edge evaluation Example The following example shows how the instruction works: SCL "R_TRIG_DB"(CLK := "TagIn", Q => "TagOut"); The RLO of the preceding query is saved in the instance DB "R_TRIG_DB". If a change in the signal state of the RLO from "0" to "1" is detected in the operand "TagIn", the output "TagOut" has signal state "1". See also Overview of the valid data types (Page 1204) Expressions (Page 1480) Operators and operator precedence (Page 1486) F_TRIG: Set tag on negative signal edge Description You can use the "Set tag on negative signal edge" instruction to set a specified tag in the instance DB when there is a "1" to "0" change in the result of logic operation (RLO). The instruction compares the current RLO at the input CLK with the RLO from the previous query, which is saved in the specified instance DB. If the instruction detects a change in the result of logic operation (RLO) from "1" to "0", there is a negative, falling edge. WinCC Basic V13.0 System Manual, 02/2014 2301 Programming the PLC 9.7 References If a negative edge is detected, the tag in the instance DB is set to signal state "1" and the output Q returns the signal state "1" In all other cases, the signal state at the output of the instruction is "0". When you insert the instruction in the program, the "Call options" dialog opens automatically. In this dialog you can specify whether the edge memory bit is stored in its own data block (single instance) or as a local tag (multiple instance) in the block interface. If you create a separate data block, you will find it in the project tree in the "Program resources" folder under "Program blocks > System blocks". For additional information on this topic, refer to "See also". Syntax The following syntax is used for the "Set tag on negative signal edge" instruction: SCL <Instance_DB>(CLK := <Operand>, Q => <Operand>) Parameter The following table shows the parameters of the instruction "Set tag on negative signal edge": Parameter Declaration Data type Description CLK Input BOOL Incoming signal, the edge of which is to be queried Q Output BOOL Result of edge evaluation Example The following example shows how the instruction works: SCL "F_TRIG_DB"(CLK := "TagIn", Q => "TagOut"); The RLO of the preceding query is saved in the instance DB "F_TRIG_DB". If a change in the signal state of the RLO from "1" to "0" is detected in the operand "TagIn", the output "TagOut" has signal state "1". See also Overview of the valid data types (Page 1204) Expressions (Page 1480) Operators and operator precedence (Page 1486) 2302 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Timer operations IEC Timers TP: Generate pulse Description You can use the "Generate pulse" instruction to set the Q parameter for the duration PT. The instruction starts when the result of logic operation (RLO) of the IN parameter changes from "0" to "1" (positive signal edge). The programmed time PT begins when the instruction starts. The Q parameter is set for the time PT, regardless of the subsequent changes in the input signal. Even when a new positive signal edge is detected, the signal state of the Q parameter is not affected as long as the time duration PT is active. The current time value can be queried in the ET parameter. The time value starts at T#0s and ends when the value of the time duration PT is reached. When the time duration PT is reached and the signal state at the IN parameter is "0", the ET parameter is reset. Note If the timer is not called in the program because it is skipped, for example, output ET returns a constant value as soon as the timer has expired. Each call of the "Generate pulse" instruction must be assigned to an IEC timer in which the instruction data is stored. For S7-1200 CPU An IEC Timer is a structure of the data type IEC_TIMER or TP_TIME that you can declare as follows: Declaration of a data block of system data type IEC_TIMER (for example, "MyIEC_TIMER") Declaration as a local tag of the TP_TIME type in the "Static" section of a block (for example, #MyTP_TIMER) For S7-1500 CPU An IEC timer is a structure of the data type IEC_TIMER, IEC_LTIMER, TP_TIME or TP_LTIME that you can declare as follows: Declaration of a data block of system data type IEC_TIMER or IEC_LTIMER (for example, "MyIEC_TIMER") Declaration as a local tag of the type TP_TIME or TP_LTIME in the "Static" section of a block (for example #MyTP_TIMER) When you insert the instruction in the program, the "Call options" dialog opens in which you can specify whether the IEC timer is stored in its own data block (single instance) or as a local tag (multiple instance) in the block interface. If you create a separate data block, you will find WinCC Basic V13.0 System Manual, 02/2014 2303 Programming the PLC 9.7 References it in the project tree in the "Program resources" folder under "Program blocks > System blocks". For additional information on this topic, refer to "See also". The instruction data is updated both when an instruction is called and also at each access to the Q or ET outputs. Syntax Use the following syntax for the "Generate pulse" instruction: Data block of system data type IEC_Timer (global DB): SCL <IEC_Timer_DB> TP(IN := <Operand>, PT := <Operand>, Q => <Operand>, ET => <Operand>) Local tag: SCL #myLocal_timer(IN := <Operand>, PT := <Operand>, Q => <Operand>, ET => <Operand>) The syntax of the instruction consists of the following parts: Parameter Declaration Data type Description S7-1200 S7-1500 IN Input BOOL BOOL Start input PT Input TIME TIME, LTIME Duration of the pulse. The value of the PT parameter must be positive. Q Output BOOL BOOL Operand that is set for the PT duration. ET Output TIME TIME, LTIME Current time value For additional information on valid data types, refer to "See also". 2304 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Pulse timing diagram The following figure shows the pulse timing diagram of the "Generate pulse" instruction: ,1 4 37 37 37 (7 37 Example The following example shows how the instruction works: SCL "TP_DB".TP(IN := "Tag_Start", PT := "Tag_PresetTime", Q => "Tag_Status", ET => "Tag_ElapsedTime"); When the signal state of the "Tag_Start" operand changes from "0" to "1", the time period programmed for the PT parameter is started and the "Tag_Status" operand is set to "1". The current time value is stored in the "Tag_ElapsedTime" operand. See also Overview of the valid data types (Page 1204) TON: Generate on-delay Description You can use the "Generate on-delay" instruction to delay the setting of the Q parameter for the programmed duration PT. The instruction starts when the result of logic operation (RLO) of the IN parameter changes from "0" to "1" (positive signal edge). The programmed time PT begins when the instruction starts. When the duration PT has expired, the Q parameter returns signal state "1". The Q parameter remains set as long as the start input is still "1". If the signal WinCC Basic V13.0 System Manual, 02/2014 2305 Programming the PLC 9.7 References state of the IN parameter changes from "1" to "0", the parameter Q will be reset. The timer function is restarted when a new positive signal edge is detected at the IN parameter. The current time value can be queried in the ET parameter. The time value starts at T#0s and ends when the value of the time duration PT is reached. The ET parameter is reset as soon as the signal state of the IN parameter changes to "0". Note If the timer is not called in the program because it is skipped, for example, output ET returns a constant value as soon as the timer has expired. Each call of the "Generate on-delay" instruction must be assigned to an IEC timer in which the instruction data is stored. For S7-1200 CPU An IEC Timer is a structure of the data type IEC_TIMER or TON_TIME that you can declare as follows: Declaration of a data block of system data type IEC_TIMER (for example, "MyIEC_TIMER") Declaration as a local tag of the TON_TIME type in the "Static" section of a block (for example, #MyTON_TIMER) For S7-1500 CPU An IEC timer is a structure of the data type IEC_TIMER, IEC_LTIMER, TON_TIME or TON_LTIME that you can declare as follows: Declaration of a data block of system data type IEC_TIMER or IEC_LTIMER (for example, "MyIEC_TIMER") Declaration as a local tag of the type TON_TIME or TON_LTIME in the "Static" section of a block (for example #MyTON_TIMER) When you insert the instruction in the program, the "Call options" dialog opens in which you can specify whether the IEC timer is stored in its own data block (single instance) or as a local tag (multiple instance) in the block interface. If you create a separate data block, you will find it in the project tree in the "Program resources" folder under "Program blocks > System blocks". For additional information on this topic, refer to "See also". The instruction data is updated both when an instruction is called and also at each access to the Q or ET outputs. Syntax Use the following syntax for the "Generate on-delay" instruction: Data block of system data type IEC_Timer (global DB): SCL <IEC_Timer_DB> TON(IN := <Operand>, PT := <Operand>, 2306 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References SCL Q => <Operand>, ET => <Operand>) Local tag: SCL #myLocal_timer(IN := <Operand>, PT := <Operand>, Q => <Operand>, ET => <Operand>) The syntax of the instruction consists of the following parts: Parameter Declaration Data type S7-1200 S7-1500 Description IN Input BOOL BOOL Start input PT Input TIME TIME, LTIME Duration of the on delay. The value of the PT parameter must be positive. Q Output BOOL BOOL Operand that is set when the timer PT expires. ET Output TIME TIME, LTIME Current time value For additional information on valid data types, refer to "See also". Pulse timing diagram The following figure shows the pulse timing diagram of the "Generate on-delay" instruction: ,1 4 37 37 (7 37 WinCC Basic V13.0 System Manual, 02/2014 2307 Programming the PLC 9.7 References Example The following example shows how the instruction works: SCL "TON_DB".TON(IN := "Tag_Start", PT := "Tag_PresetTime", Q => "Tag_Status", ET => "Tag_ElapsedTime"); When the signal state of the "Tag_Start" operand changes from "0" to "1", the time programmed for the PT parameter is started. After the end of the period the "Tag_Status" operand is set to the signal state "1". The operand Tag_Status remains set to signal state "1" as long as the operand Tag_Start has signal state "1". The current time value is stored in the operand "Tag_ElapsedTime". When the signal state at the operand "Tag_Start" changes from "1" to "0", the "Tag_Status" operand is reset. See also Overview of the valid data types (Page 1204) TOF: Generate off-delay Description You can use the "Generate off-delay" instruction to delay the resetting of the Q parameter for the programmed duration PT. The Q parameter is set when the result of logic operation (RLO) of the IN parameter changes from "0" to "1" (positive signal edge). When the signal state of the IN parameter changes back to "0", the programmed time PT starts. The Q parameter remains set as long the time duration PT is running. When the time PT expires, the Q parameter is reset. If the signal state of the IN parameter changes to "1" before the time duration PT has expired, the timer is reset. The signal state of the Q parameter remains set to "1". The current time value can be queried in the ET parameter. The time value starts at T#0s and ends when the value of the time duration PT is reached. When the time duration PT expires, the ET parameter remains set to the current value until the IN parameter changes back to "1". If the IN parameter changes to "1" before the time PT has expired, the ET parameter is reset to the value T#0s. Note If the timer is not called in the program because it is skipped, for example, output ET returns a constant value as soon as the timer has expired. Each call of the "Generate off-delay" instruction must be assigned to an IEC timer in which the instruction data is stored. 2308 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References For S7-1200 CPU An IEC Timer is a structure of the data type IEC_TIMER or TOF_TIME that you can declare as follows: Declaration of a data block of system data type IEC_TIMER (for example, "MyIEC_TIMER") Declaration as a local tag of the TOF_TIME type in the "Static" section of a block (for example, #MyTOF_TIMER) For S7-1500 CPU An IEC timer is a structure of the data type IEC_TIMER, IEC_LTIMER, TOF_TIME or TOF_LTIME that you can declare as follows: Declaration of a data block of system data type IEC_TIMER or IEC_LTIMER (for example, "MyIEC_TIMER") Declaration as a local tag of the type TOF_TIME or TOF_LTIME in the "Static" section of a block (for example #MyTOF_TIMER) When you insert the instruction in the program, the "Call options" dialog opens in which you can specify whether the IEC timer is stored in its own data block (single instance) or as a local tag (multiple instance) in the block interface. If you create a separate data block, you will find it in the project tree in the "Program resources" folder under "Program blocks > System blocks". For additional information on this topic, refer to "See also". The instruction data is updated both when an instruction is called and also at each access to the Q or ET outputs. Syntax Use the following syntax for the "Generate off-delay" instruction: Data block of system data type IEC_Timer (global DB): SCL <IEC_Timer_DB> TOF(IN := <Operand>, PT := <Operand>, Q => <Operand>, ET => <Operand>) Local tag: SCL #myLocal_timer(IN := <Operand>, PT := <Operand>, Q => <Operand>, ET => <Operand>) The syntax of the instruction consists of the following parts: WinCC Basic V13.0 System Manual, 02/2014 2309 Programming the PLC 9.7 References Parameter Declaration Data type S7-1200 S7-1500 Description IN Input BOOL BOOL Start input PT Input TIME TIME, LTIME Duration of the off delay. The value of the PT parameter must be positive. Q Output BOOL BOOL Operand that is reset when the time PT expires. ET Output TIME TIME, LTIME Current time value For additional information on valid data types, refer to "See also". Pulse timing diagram The following figure shows the pulse timing diagram of the instruction "Generate off-delay": ,1 4 37 37 (7 37 Example The following example shows how the instruction works: SCL "TOF_DB".TOF(IN := "Tag_Start", PT := "Tag_PresetTime", Q => "Tag_Status", ET => "Tag_ElapsedTime"); With a change in the signal state of the "Tag_Start" operand from "0" to "1", the "Tag_Status" operand is set. When the signal state of the "Tag_Start" operand changes from "1" to "0", the time programmed for the PT parameter is started. As long as the time is running, the 2310 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References "Tag_Status" operand remains set. When the time has expired, the "Tag_Status" operand is reset. The current time value is stored in the operand "Tag_ElapsedTime". See also Overview of the valid data types (Page 1204) TONR: Time accumulator Description The "Time accumulator" instruction is used to accumulate time values within a period set by the PT parameter. When the signal state of the IN parameter changes to "1", the instruction executes and the time duration PT starts. While the time duration PT is running, the time values that are recorded when the IN parameter has signal state "1" are accumulated. The accumulated time is output in the ET parameter and can be queried there. When the time duration PT is reached, the Q parameter has signal state "1". The Q parameter remains set to "1", even when the signal state at the IN parameter changes to "0". The R parameter resets the ET and Q parameters regardless of the signal state at the IN parameter. Each call of the "Time accumulator" instruction must be assigned to an IEC timer in which the instruction data is stored. For S7-1200 CPU An IEC Timer is a structure of the data type IEC_TIMER or TONR_TIME that you can declare as follows: Declaration of a data block of system data type IEC_TIMER (for example, "MyIEC_TIMER") Declaration as a local tag of the TONR_TIME type in the "Static" section of a block (for example, #MyTONR_TIMER) For S7-1500 CPU An IEC timer is a structure of the data type IEC_TIMER, IEC_LTIMER, TONR_TIME or TONR_LTIME that you can declare as follows: Declaration of a data block of system data type IEC_TIMER or IEC_LTIMER (for example, "MyIEC_TIMER") Declaration as a local tag of the type TONR_TIME or TONR_LTIME in the "Static" section of a block (for example #MyTONR_TIMER) When you insert the instruction in the program, the "Call options" dialog opens in which you can specify whether the IEC timer is stored in its own data block (single instance) or as a local tag (multiple instance) in the block interface. If you create a separate data block, you will find it in the project tree in the "Program resources" folder under "Program blocks > System blocks". For additional information on this topic, refer to "See also". WinCC Basic V13.0 System Manual, 02/2014 2311 Programming the PLC 9.7 References The instruction data is updated both when an instruction is called and also at each access to the Q or ET outputs. Syntax Use the following syntax for the "Time accumulator" instruction: Data block of system data type IEC_Timer (global DB): SCL <IEC_Timer_DB> TONR(IN := <Operand>, R := <Operand>, PT := <Operand>, Q => <Operand>, ET => <Operand>) Local tag: SCL #myLocal_timer(IN := <Operand>, R := <Operand>, PT := <Operand>, Q => <Operand>, ET => <Operand>) The syntax of the instruction consists of the following parts: Parameter Declaration Data type Description S7-1200 S7-1500 IN Input BOOL BOOL Start input R Input BOOL BOOL Reset of the ET and Q parameters PT Input TIME TIME, LTIME Maximum duration of time recording. The value of the PT parameter must be positive. Q Output BOOL BOOL Operand that remains set when the timer PT has expired. ET Output TIME TIME, LTIME Accumulated time For additional information on valid data types, refer to "See also". 2312 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Pulse timing diagram The following figure shows the pulse timing diagram of the "Time accumulator" instruction: ,1 5 4 37 (7 Example The following example shows how the instruction works: SCL "TONR_DB".TONR(IN := "Tag_Start", R := "Tag_Reset", PT := "Tag_PresetTime", Q => "Tag_Status", ET => "Tag_Time"); When the signal state of the "Tag_Start" operand changes from "0" to "1", the time programmed for the PT parameter is started. While the timer is running, the time values that are recorded at signal state "1" of the operand "Tag_Start" is accumulated. The accumulated times is stored in the "Tag_Time" operand. When the time value displayed at the PT parameter is reached, the "Tag_Status" operand is set to the signal state "1". The current time value is stored in the operand "Tag_Time". See also Overview of the valid data types (Page 1204) WinCC Basic V13.0 System Manual, 02/2014 2313 Programming the PLC 9.7 References RESET_TIMER: Reset timer Description You can use the "Reset timer" instruction to reset an IEC timer to "0". The structure components of the timer in the specified data block are reset to "0". The instruction does not influence the RLO. At the TIMER parameter, the "Reset timer" instruction is assigned an IEC timer declared in the program. The instruction data is updated only when the instruction is called and not each time the assigned IEC timer is accessed. Querying the data is only identical from the call of the instruction to the next call of the instruction. Syntax Use the following syntax for the "Reset timer" instruction: SCL RESET_TIMER(TIMER := <IEC timer>) Parameters The following table shows the parameters of the "Reset timer" instruction": Parameter Declaration <IEC timer> Output Data type IEC_TIMER, IEC_LTIMER, TP_TIME, TP_LTIME, TON_TIME, TON_LTIME, TOF_TIME, TOF_LTIME, TONR_TIME, TONR_LTIME Description IEC timer that is reset For more information on valid data types, refer to "See also". Example The following example shows how the instruction works: SCL IF #started = false THEN "TON_DB".TON(IN := "Tag_Start", PT := "Tag_PresetTime", Q => "Tag_Status", ET => "Tag_ElapsedTime"); #started := true; 2314 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References SCL END_IF; IF "TON_DB".ET < T#25s THEN RESET_TIMER(TIMER := "TON_DB"); #started := false; END_IF; When the tag #started has the signal state "0", the instruction "Generate on-delay" is executed when there is positive signal edge on the operand "Tag_Start". The IEC timer stored in the instance data block "TON_DB" is started with the time duration that is specified by the operand "Tag_PresetTime". The operand "Tag_Status" is set if the time duration specified by the operand "Tag_PresetTime" has expired. The parameter Q remains set as long as the operand "Tag_Start" still has the signal state "1". When the signal state of the start input changes from "1" to "0", the operand on the Q parameter is reset. If the expired time of the IEC timer "TON_DB" is less than 25s, the "Reset timer" instruction is executed and the timer stored in the "TON_DB" instance data block is reset. See also Overview of the valid data types (Page 1204) PRESET_TIMER: Load time duration Description You can use the "Load time duration" instruction to set the time for an IEC timer. The instruction is executed in every cycle when the result of logic operation (RLO) at the input of the instruction has the signal state "1". The instruction writes the specified time to the structure of the specified IEC timer. Note If the specified IEC timer is running while the instruction executes, the instruction overwrites the current time of the specified IEC timer. This can change the timer status of the IEC timer. You assign an IEC timer declared in the program to the "Load time duration" instruction. The instruction data is updated only when the instruction is called and each time the assigned IEC timer is accessed. The query on Q or ET (for example, "MyTimer".Q or "MyTimer".ET) updates the IEC_TIMER structure. Syntax Use the following syntax for the "Load time duration" instruction: SCL PRESET_TIMER(PT := <Operand>, WinCC Basic V13.0 System Manual, 02/2014 2315 Programming the PLC 9.7 References SCL TIMER := <IEC timer) Parameter The following table shows the parameters of the "Load time duration" instruction: Parameter Declaration <Time duration> Input TIME, LTIME Data type Description Duration with which the IEC timer runs. <IEC timer> Output IEC_TIMER, IEC_LTIMER, TP_TIME, TP_LTIME, TON_TIME, TON_LTIME, TOF_TIME, TOF_LTIME, TONR_TIME, TONR_LTIME IEC timer whose duration of which is set. For more information on valid data types, refer to "See also". Example The following example shows how the instruction works: SCL IF #started = false THEN "TON_DB".TON(IN := "Tag_Start", PT := "Tag_PresetTime", Q => "Tag_Status", ET => "Tag_ElapsedTime"); #started := true; #preset = true END_IF; IF "TON_DB".ET < T#10s AND #preset = true THEN PRESET_TIMER(PT := T#25s, TIMER := "TON_DB"); #preset := false; END_IF; When the tag #started has the signal state "0" and the operand "Tag_Start" has a positive signal edge, the instruction "Generate on-delay" is executed. The IEC timer stored in the instance data block "TON_DB" is started with the time duration that is specified by the operand "Tag_PresetTime". The operand "Tag_Status" is set if the time duration PT specified by the operand "Tag_PresetTime" has expired. The parameter Q remains set as long as the operand "Tag_Start" still has the signal state "1". When the signal state of the start input changes from "1" to "0", the operand on the Q parameter is reset. 2316 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References The instruction "Load time duration" is executed when the expired time of the IEC timer "TON_DB" is less than 10s and the tag #preset has the signal state "1". The instruction writes the time duration that is specified at the parameter "PT" in the instance data block "TON_DB", thereby overwriting the time value of the operand "Tag_PresetTime" within the instance data block. The signal state of the timer status may therefore change at the next query or when "TON_DB".Q or "TON_DB".ET are accessed. See also Overview of the valid data types (Page 1204) SIMATIC Timers S_PULSE: Assign pulse timer parameters and start Description The "Assign pulse timer parameters and start" instruction starts the time programmed in the T_NO parameter when a change from "0" to "1" (positive signal edge) is detected in the result of logic operation (RLO) of the S parameter. The timer runs for the programmed time (TV) as long as the signal state of the S parameter is "1". When the signal state of the S parameter changes to "0" before the programmed time has expired, the timer is stopped and the "Q" parameter is reset to "0". Internally, the time is made up of a time value and a time base and is programmed in the TV parameter. When the instruction starts, the programmed time value counts down to zero. The time base specifies the time increment by which the time value changes. The current time value is provided at the parameter BI. If the timer is running and the signal state at input R changes to "1" then the current time value and the time base are also set to zero. If the timer is not running, the signal state "1" at the R input has no effect. Parameter Q returns signal state "1" as long as the timer is running and the signal state at parameter S is "1". When the signal state of the S parameter changes to "0" before the programmed time has expired, the Q parameter returns signal state "0". If the timer is reset by parameter R or if the timer has expired then parameter Q also returns signal state "0". The instruction data is updated with each access. It is therefore possible that the query of the data at the start of the cycle returns different values from those at the end of the cycle. Note In the time cell, the operating system reduces the time value in an interval specified by the time base by one unit until the value equals "0". The decrementation is performed asynchronously to the user program. The resulting timer is therefore at maximum up to one time interval shorter than the desired time base. You can find an example of how a time cell can be formed under: See also "L: Load timer value". WinCC Basic V13.0 System Manual, 02/2014 2317 Programming the PLC 9.7 References Syntax Use the following syntax for the "Assign pulse timer parameters and start" instruction: SCL S_PULSE(T_NO := <Operand>, S := <Operand>, TV := <Operand>, R := <Operand>, Q => <Operand>, BI => <Operand>) The syntax of the instruction consists of the following parts: Parameter Declaration Data type Description T_NO Input TIMER, INT The timer that is started. S Input BOOL Start input TV Input S5TIME, WORD Preset time value R Input BOOL Reset input Q Output BOOL Status of the timer BI Output WORD Current dual-coded timer value S5TIME Current time value The number of timers depends on the CPU. Function value For additional information on valid data types, refer to "See also". 2318 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Pulse timing diagram The following figure shows the pulse timing diagram of the "Assign pulse timer parameters and start" instruction: W W W 5/2DWLQSXW6 5/2DWLQSXW5 7LPHUUXQQLQJ 4XHU\ 4XHU\ W SURJUDPPHGWLPH Example The following example shows how the instruction works: SCL "Tag_Result" := S_PULSE(T_NO := "Timer_1", S := "Tag_1", TV := "Tag_Number", R := "Tag_Reset", Q := "Tag_Status", BI := "Tag_Value"); "Timer_1" starts when the signal state of the "Tag_1" operand changes from "0" to "1". The timer counts down with the time value of the operand "Tag_Number" until operand "Tag_1" returns signal state "1". If the signal state at the S parameter changes to "0" before the programmed time has elapsed, the "Tag_Status" operand is reset to "0". If the timer is reset by the R parameter or if the timer has expired, the "Tag_Status" operand also returns signal state "0". WinCC Basic V13.0 System Manual, 02/2014 2319 Programming the PLC 9.7 References The current time value is stored both dual-coded at the "Tag_Value" operand and returned as a function value. See also Overview of the valid data types (Page 1204) S_PEXT: Assign extended pulse timer parameters and start Description The "Assign extended pulse timer parameters and start" instruction starts a programmed timer when a positive signal edge is detected at the S parameter. The timer runs for the programmed time (TV) even if the signal state at the S parameter changes to "0". As long as the timer runs, parameter Q returns the signal state "1". When the timer has expired, parameter Q is reset to "0". If the signal state at the S parameter changes from "0" to "1" while the timer is running, the timer is restarted with the time programmed in the TV parameter. Internally, the time is made up of a time value and a time base and is programmed in the TV parameter. When the instruction starts, the programmed time value counts down to zero. The time base specifies the time increment by which the time value changes. The current time value is provided at the parameter BI. If the timer is running and the signal state at parameter R changes to "1" then the current time value and the time base are also set to zero. If the timer is not running then signal state "1" at parameter R has no effect. The instruction data is updated with each access. It is therefore possible that the query of the data at the start of the cycle returns different values from those at the end of the cycle. Note In the time cell, the operating system reduces the time value in an interval specified by the time base by one unit until the value equals "0". The decrementation is performed asynchronously to the user program. The resulting timer is therefore at maximum up to one time interval shorter than the desired time base. You can find an example of how a time cell can be formed under: See also "L: Load timer value". Syntax Use the following syntax for the "Assign extended pulse timer parameters and start" instruction: SCL S_PEXT(T_NO := <Operand>, S := <Operand>, TV := <Operand>, R := <Operand>, 2320 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References SCL Q => <Operand>, BI => <Operand>) The syntax of the instruction consists of the following parts: Parameter Declaration Data type Description T_NO Input TIMER, INT The timer that is started. The number of timers depends on the CPU. S Input BOOL Start input TV Input S5TIME, WORD Preset time value R Input BOOL Reset input Q Output BOOL Status of the timer BI Output WORD Current dual-coded timer value S5TIME Current time value Function value For additional information on valid data types, refer to "See also". WinCC Basic V13.0 System Manual, 02/2014 2321 Programming the PLC 9.7 References Pulse timing diagram The following figure shows the pulse timing diagram of the "Assign extended pulse timer parameters and start" instruction: W W W W 5/2DWLQSXW6 5/2DWLQSXW5 7LPHUXQQLQJ 4XHU\ 4XHU\ W SURJUDPPHGWLPH Example The following example shows how the instruction works: SCL "Tag_Result" := S_PEXT(T_NO := "Timer_1", S := "Tag_1", TV := "Tag_Number", R := "Tag_Reset", Q := "Tag_Status", BI := "Tag_Value"); "Timer_1" starts when the signal state of the "Tag_1" operand changes from "0" to "1". As long as the timer runs, operand "Tag_Status" returns the signal state "1". When the timer has expired, operand "Tag_Status" is reset to "0". If the signal state at the S input changes from "0" to "1" while the timer is running, the timer is restarted with the time "Tag_Number". The current time value is stored both dual-coded at the "Tag_Value" operand and returned as a function value. 2322 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References See also Overview of the valid data types (Page 1204) S_ODT: Assign on-delay timer parameters and start Description The "Assign on-delay timer parameters and start" instruction starts a programmed timer as ondelay when a positive signal edge is detected at the S parameter. The timer runs for the programmed time (TV) as long as the signal state of the S parameter is "1". If the timer expires correctly and parameter S still has signal state "1" then parameter Q returns signal state "1". If the signal state at the S parameter changes from "1" to "0" while the timer is running, the timer is stopped. In this case, output Q is reset to signal state "0". Internally, the time is made up of a time value and a time base and is programmed in the TV parameter. When the instruction starts, the programmed time value counts down to zero. The time base specifies the time increment by which the time value changes. The current time value is provided at the parameter BI. If the time is running and the signal state at input R changes from "0" to "1" then the current time value and the time base are also set to zero. In this case, the signal state at parameter Q is "0". The timer is reset if the signal state at the R parameter is "1", even if the timer is not running and the result of logic operation (RLO) at the S parameter is "1". The instruction data is updated with each access. It is therefore possible that the query of the data at the start of the cycle returns different values from those at the end of the cycle. Note In the time cell, the operating system reduces the time value in an interval specified by the time base by one unit until the value equals "0". The decrementation is performed asynchronously to the user program. The resulting timer is therefore at maximum up to one time interval shorter than the desired time base. You can find an example of how a time cell can be formed under: See also "L: Load timer value". Syntax Use the following syntax for the "Assign on-delay timer parameters and start" instruction: SCL S_ODT(T_NO := <Operand>, S := <Operand>, TV := <Operand>, R := <Operand>, Q => <Operand>, BI => <Operand>) The syntax of the instruction consists of the following parts: WinCC Basic V13.0 System Manual, 02/2014 2323 Programming the PLC 9.7 References Parameter Declaration Data type Description T_NO Input TIMER, INT The timer that is started. The number of timers depends on the CPU. S Input BOOL Start input TV Input S5TIME, WORD Preset time value R Input BOOL Reset input Q Output BOOL Status of the timer BI Output WORD Current dual-coded timer value S5TIME Current time value Function value For additional information on valid data types, refer to "See also". ulse timing diagram The following figure shows the pulse timing diagram of the "Assign on-delay timer parameters and start" instruction: W W W 5/2DWLQSXW6 5/2DWLQSXW5 7LPHUUXQQLQJ 4XHU\ 4XHU\ W SURJUDPPHGWLPH Example The following example shows how the instruction works: SCL "Tag_Result" := S_ODT(T_NO := "Timer_1", 2324 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References SCL S := "Tag_1", TV := "Tag_Number", R := "Tag_Reset", Q := "Tag_Status", BI := "Tag_Value"); "Timer_1" starts when the signal state of the "Tag_1" operand changes from "0" to "1". The timer runs for the duration "Tag_Number" as long as the signal state of operand "Tag_1" is "1". If the timer expires correctly and operand "Tag_Status" has signal state "1" then operand "Tag_Status" is reset to "1". If the signal state of the "Tag_1" operand changes from "1" to "0" while the timer is running, the timer is stopped. In this case, operand "Tag_Status" returns signal state "0". The current time value is stored both dual-coded at the "Tag_Value" operand and returned as a function value. See also Overview of the valid data types (Page 1204) S_ODTS: Assign retentive on-delay timer parameters and start Description The "Assign retentive on-delay timer parameters and start" instruction starts a programmed timer when a positive signal edge is detected at the S parameter. The timer runs for the programmed time (TV) even if the signal state at the S parameter changes to "0". If the timer expires, the "Q" parameter returns signal state "1" regardless of the signal state of the "S" parameter. If the signal state at the S parameter changes from "0" to "1" while the timer is running, the timer is restarted with the programmed time TV. Internally, the time is made up of a time value and a time base and is programmed in the TV parameter. When the instruction starts, the programmed time value counts down to zero. The time base specifies the time increment by which the time value changes. The current time value is provided at the parameter BI. Signal state "1" at parameterR resets the current time value and time base to "0", independent of the signal state at parameter S. In this case, the signal state at parameter Q is "0". The instruction data is updated with each access. It is therefore possible that the query of the data at the start of the cycle returns different values from those at the end of the cycle. Note In the time cell, the operating system reduces the time value in an interval specified by the time base by one unit until the value equals "0". The decrementation is performed asynchronously to the user program. The resulting timer is therefore at maximum up to one time interval shorter than the desired time base. WinCC Basic V13.0 System Manual, 02/2014 2325 Programming the PLC 9.7 References You can find an example of how a time cell can be formed under: See also "L: Load timer value". Syntax Use the following syntax for the "Assign retentive on-delay timer parameters and start" instruction: SCL S_ODTS(T_NO := <Operand>, S := <Operand>, TV := <Operand>, R := <Operand>, Q => <Operand>, BI =><Operand>) The syntax of the instruction consists of the following parts: Parameter Declaration Data type Description T_NO Input TIMER, INT The timer that is started. S Input BOOL Start input TV Input S5TIME, WORD Preset time value R Input BOOL Reset input Q Output BOOL Status of the timer BI Output WORD Current dual-coded timer value S5TIME Current time value The number of timers depends on the CPU. Function value For additional information on valid data types, refer to "See also". 2326 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Pulse timing diagram The following figure shows the pulse timing diagram of the "Assign retentive on-delay timer parameters and start" instruction: W W W W 5/2DWLQSXW6 5/2DWLQSXW5 7LPHUUXQQLQJ 4XHU\ 4XHU\ W SURJUDPPHGWLPH Example The following example shows how the instruction works: SCL "Tag_Result" := S_ODTS(T_NO := "Timer_1", S := "Tag_1", TV := "Tag_Number", R := "Tag_Reset", Q := "Tag_Status", BI := "Tag_Value"); "Timer_1" starts when the signal state of the "Tag_1" operand changes from "0" to "1". The timer runs for the duration "Tag_Number". If the timer expires, operand "Tag_Status" returns signal state "1" independent of the signal state of operand "Tag_1". If the signal state of the "Tag_1" operand changes from "0" to "1" while the timer is running, the timer is restarted with the time "Tag_Number". The current time value is stored both dual-coded at the "Tag_Value" operand and returned as a function value. See also Overview of the valid data types (Page 1204) WinCC Basic V13.0 System Manual, 02/2014 2327 Programming the PLC 9.7 References S_OFFDT: Assign off-delay timer parameters and start Description The "Assign off-delay timer parameters and start" instruction starts a programmed timer when a negative signal edge is detected at the S parameter. The timer runs for the programmed time (TV). As long as the timer is running or parameter S returns signal state "1", then parameter Q has signal state "1". If the timer expires and the signal state is "0" then parameter Q is reset to signal state "0". If the signal state at parameter S changes from "0" to "1" while the timer is running, the timer is stopped. The timer is only restarted after a falling signal edge is detected at parameter S. Internally, the time is made up of a time value and a time base and is programmed in the TV parameter. When the instruction starts, the programmed time value counts down to zero. The time base specifies the time increment by which the time value changes. The current time value is provided at the parameter BI. Signal state "1" at parameter R resets the current time value and time base to "0". In this case, the signal state at parameter Q is "0". The instruction data is updated with each access. It is therefore possible that the query of the data at the start of the cycle returns different values from those at the end of the cycle. Note In the time cell, the operating system reduces the time value in an interval specified by the time base by one unit until the value equals "0". The decrementation is performed asynchronously to the user program. The resulting timer is therefore at maximum up to one time interval shorter than the desired time base. You can find an example of how a time cell can be formed under: See also "L: Load timer value". Syntax Use the following syntax for the "Assign off-delay timer parameters and start" instruction: SCL S_OFFDT(T_NO := <Operand>, S := <Operand>, TV := <Operand>, R := <Operand>, Q => <Operand>, BI =><Operand>) The syntax of the instruction consists of the following parts: Parameter Declaration Data type Description T_NO Input TIMER, INT The timer that is started. S Input BOOL Start input The number of timers depends on the CPU. 2328 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameter Declaration Data type Description TV Input S5TIME, WORD Preset time value R Input BOOL Reset input Q Output BOOL Status of the timer BI Output WORD Current dual-coded timer value S5TIME Current time value Function value For additional information on valid data types, refer to "See also". Pulse timing diagram The following figure shows the pulse timing diagram of the "Assign off-delay timer parameters and start" instruction: W W W W 5/2DWLQSXW6 5/2DWLQSXW5 7LPHUXQQLQJ 4XHU\ 4XHU\ W SURJUDPPHGWLPH Example The following example shows how the instruction works: SCL "Tag_Result" := S_OFFDT(T_NO := "Timer_1", S := "Tag_1", TV := "Tag_Number", R := "Tag_Reset", Q := "Tag_Status", BI := "Tag_Value"); WinCC Basic V13.0 System Manual, 02/2014 2329 Programming the PLC 9.7 References "Timer_1" starts when the signal state of the "Tag_1" operand changes from "0" to "1". The timer runs for the duration "Tag_Number". As long as the timer is running or operand "Tag_1" returns signal state "1", then operand "Tag_Status" has signal state "1". If the timer expires and the signal state of operand "Tag_1" is "0" then operand "Tag_Status" is reset to signal state "0". If the signal state of the "Tag_1" operand changes from "0" to "1" while the timer is running, the timer is reset. The timer is only restarted after a falling edge is detected at parameter S. The current time value is stored both dual-coded at the "Tag_Value" operand and returned as a function value. See also Overview of the valid data types (Page 1204) Counter operations IEC Counters CTU: Count up Description You can use the "Count up" instruction to increment the value at the CV parameter. When the signal state at the CU parameter changes from "0" to "1" (positive signal edge), the instruction is executed and the current counter value of the CV parameter is incremented by one. When the instruction is executed for the first time the current count of the CV parameter is set to zero. The counter value is incremented each time a positive signal edge is detected, until it reaches the high limit of the data type specified for the CV parameter. When the high limit is reached, the signal state of the CU parameter no longer has an effect on the instruction. You can query the count status of the Q parameter. The signal state of the Q parameter is determined by the PV parameter. When the current counter value is greater than or equal to the value of the PV parameter, the Q parameter is set to signal state "1". In all other cases, the signal state of the Q parameter is "0". You can also specify a constant for the PV parameter. The value of the CV parameter is reset to zero when the signal state at the R parameter changes to "1". As long as the R parameter has the signal state "1", the signal state of the CU parameter has no effect on the instruction. Note Only use a counter at a single location in the program to avoid counting errors. Each call of the "Count up" instruction must be assigned an IEC counter in which the instruction data is stored. An IEC counter is a structure with one of the following data types: 2330 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References For S7-1200 CPU Data block of system data type IEC_<Counter> (Shared DB) Local tag IEC_SCOUNTER / IEC_USCOUNTER CTU_SINT / CTU_USINT IEC_COUNTER / IEC_UCOUNTER CTU_INT / CTU_UINT IEC_DCOUNTER / IEC_UDCOUNTER CTU_DINT / CTU_UDINT Data block of system data type IEC_<Counter> (Shared DB) Local tag IEC_SCOUNTER / IEC_USCOUNTER CTU_SINT / CTU_USINT IEC_COUNTER / IEC_UCOUNTER CTU_INT / CTU_UINT IEC_DCOUNTER / IEC_UDCOUNTER CTU_DINT / CTU_UDINT IEC_LCOUNTER / IEC_ULCOUNTER CTU_LINT / CTU_ULINT For S7-1500 CPU You can declare an IEC counter as follows: Declaration of a data block of system data type IEC_<Counter> (for example, "MyIEC_COUNTER") Declaration as a local tag of the type CTU_<Data type> in the "Static" section of a block (for example, #MyCTU_COUNTER) When you insert the instruction in the program, the "Call options" dialog opens in which you can specify whether the IEC counter is stored in its own data block (single instance) or as a local tag (multiple instance) in the block interface. If you create a separate data block, you will find it in the project tree in the "Program resources" folder under "Program blocks > System blocks". For additional information on this topic, refer to "See also". When you set up the IEC counter in a separate data block (single instance), the instance data block is created by default with "optimized block access" and the individual tags are defined as retentive. For additional information on setting retentivity in an instance data block, refer to "See also". When you set up the IEC counter as local tag (multiple instance) in a function block with "optimized block access", it is defined as retentive in the block interface. Syntax The following syntax is used for the "Count up" instruction: Table 9-28 Data block of system data type IEC_counter (global DB) SCL <IEC_Counter_DB>.CTU(CU := <Operand>, R := <Operand>, PV := <Operand>, Q => <Operand>, CV => <Operand>) WinCC Basic V13.0 System Manual, 02/2014 2331 Programming the PLC 9.7 References Table 9-29 Local tag SCL #myLocal_counter(CU := <Operand>, R := <Operand>, PV := <Operand>, Q => <Operand>, CV => <Operand>) The syntax of the instruction consists of the following parts: Parameter Declaration Data type Description CU Input BOOL Count input R Input BOOL Reset input PV Input Integers Value at which the Q output is set Q Output BOOL Counter status CV Output Integers, CHAR, DATE Current counter value For additional information on valid data types, refer to "See also". Example The following example shows how the instruction works: SCL "IEC_COUNTER_DB".CTU(CU := "Tag_Start", R := "Tag_Reset", PV := "Tag_PresetValue", Q => "Tag_Status", CV => "Tag_CounterValue"); When the signal state at the "Tag_Start" operand changes from "0" to "1", the "Count up" instruction is executed and the current counter value of the "Tag_CounterValue" operand is incremented by one. With each additional positive signal edge, the counter value is incremented until the high limit of the specified data type (INT = 32767) is reached. The "Tag_Status" output has signal state "1" as long as the current counter value is greater than or equal to the value of the "Tag_PresetValue" operand. In all other cases, the "Tag_Status" output has signal state "0". The current counter value is stored in the "Tag_CounterValue" operand. See also Overview of the valid data types (Page 1204) Setting retentivity in an instance data block (Page 1536) Setting the retentivity of local tags (Page 1391) 2332 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References CTD: Count down Description The "Count down" instruction is used to decrement the value at the parameter CV. When the signal state at the CD parameter changes from "0" to "1" (positive signal edge), the instruction is executed and the current counter value of the CV parameter is decremented by one. When the instruction is executed the first time, the counter value of the CV parameter is set to the value of the PV parameter. Each time a positive signal edge is detected, the counter value is decremented until it reaches the low limit of the specified data type. When the low limit is reached, the signal state of the CD parameter no longer has an effect on the instruction. You can query the count status of the Q parameter. If the current counter value is less than or equal to zero, the Q parameter is set to signal state "1". In all other cases, the signal state of the Q parameter is "0". You can also specify a constant for the PV parameter. The value of the CV parameter is set to the value of the PV parameter when the signal state of the LD parameter changes to "1". As long as the LD parameter has the signal state "1", the signal state of the CD parameter has no effect on the instruction. Note Only use a counter at a single location in the program to avoid counting errors. Each call of the "Count down" instruction must be assigned an IEC counter in which the instruction data is stored. An IEC counter is a structure with one of the following data types: For S7-1200 CPU Data block of system data type IEC_<Counter> (Shared DB) Local tag IEC_SCOUNTER / IEC_USCOUNTER CTD_SINT / CTD_USINT IEC_COUNTER / IEC_UCOUNTER CTD_INT / CTD_UINT IEC_DCOUNTER / IEC_UDCOUNTER CTD_DINT / CTD_UDINT Data block of system data type IEC_<Counter> (Shared DB) Local tag IEC_SCOUNTER / IEC_USCOUNTER CTD_SINT / CTD_USINT IEC_COUNTER / IEC_UCOUNTER CTD_INT / CTD_UINT IEC_DCOUNTER / IEC_UDCOUNTER CTD_DINT / CTD_UDINT IEC_LCOUNTER / IEC_ULCOUNTER CTD_LINT / CTD_ULINT For S7-1500 CPU You can declare an IEC counter as follows: WinCC Basic V13.0 System Manual, 02/2014 2333 Programming the PLC 9.7 References Declaration of a data block of system data type IEC_<Counter> (for example, "MyIEC_COUNTER") Declaration as a local tag of the type CTD_<Data type> in the "Static" section of a block (for example, #MyCTD_COUNTER) When you insert the instruction in the program, the "Call options" dialog opens in which you can specify whether the IEC counter is stored in its own data block (single instance) or as a local tag (multiple instance) in the block interface. If you create a separate data block, you will find it in the project tree in the "Program resources" folder under "Program blocks > System blocks". For additional information on this topic, refer to "See also". When you set up the IEC counter in a separate data block (single instance), the instance data block is created by default with "optimized block access" and the individual tags are defined as retentive. For additional information on setting retentivity in an instance data block, refer to "See also". When you set up the IEC counter as local tag (multiple instance) in a function block with "optimized block access", it is defined as retentive in the block interface. Syntax The following syntax is used for the "Count down" instruction: Table 9-30 Data block of system data type IEC_counter (global DB) SCL <IEC_Counter_DB>.CTD(CD := <Operand>, LD := <Operand>, PV := <Operand>, Q => <Operand>, CV => <Operand>) Table 9-31 Local tag SCL #myLocal_counter(CD := <Operand>, LD := <Operand>, PV := <Operand>, Q => <Operand>, CV => <Operand>) The syntax of the instruction consists of the following parts: Parameter Declaration Data type Description CD Input BOOL Count input LD Input BOOL Load input PV Input Integers Value at which the Q output is set Q Output BOOL Counter status CV Output Integers, CHAR, DATE Current counter value For additional information on valid data types, refer to "See also". 2334 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Example The following example shows how the instruction works: SCL "IEC_SCOUNTER_DB".CTD(CD := "Tag_Start", LD := "Tag_Load", PV := "Tag_PresetValue", Q => "Tag_Status", CV => "Tag_CounterValue"); When the signal state at the "Tag_Start" changes from "0" to "1", the "Count down" instruction executes and the value of the "Tag_CounterValue" operand is decremented by one. With each additional positive signal edge, the counter value is decremented until it reaches the low limit of the specified data type (-128). The operand "Tag_Status" has the signal state "1" as long as the current counter value is less than or equal to zero. In all other cases, the "Tag_Status" output has signal state "0". The current counter value is stored in the "Tag_CounterValue" operand. See also Overview of the valid data types (Page 1204) Setting retentivity in an instance data block (Page 1536) Setting the retentivity of local tags (Page 1391) CTUD: Count up and down Description Use the "Count up and down" instruction to increment or decrement the counter value at the CV parameter. When the signal state at the CU parameter changes from "0" to "1" (positive signal edge), the current counter value of the CV parameter is incremented by one. When the signal state at the CD parameter changes from "0" to "1" (positive signal edge), the counter value of the CV parameter is decremented by one. If there is a positive signal edge at the CU and CD inputs in a program cycle, the current counter value of the CV parameter remains unchanged. The counter value can be incremented until it reaches the high limit of the data type specified for the CV parameter. When the high limit is reached, the counter value is no longer incremented on a positive signal edge. The counter value is no longer decremented once the low limit of the specified data type has been reached. When the signal state at the LD parameter changes to "1", the counter value of the CV parameter is set to the value of the PV parameter. As long as the LD parameter has the signal state "1", the signal state of the CU and CD parameters has no effect on the instruction. The counter value is set to zero when the signal state of the R parameter changes to "1". As long as the R parameter has signal state "1", a change in the signal state of the CU, CD and LD parameters has no effect on the "Count up and down" instruction. WinCC Basic V13.0 System Manual, 02/2014 2335 Programming the PLC 9.7 References You can query the status of the up counter at the QU parameter. When the current counter value is greater than or equal to the value of the PV parameter, the QU parameter is set to signal state "1". In all other cases, the signal state of the QU parameter is "0". You can also specify a constant for the PV parameter. You can query the status of the down counter at the QD parameter. If the current counter value is less than or equal to zero, the QD parameter is set to signal state "1". In all other cases, the signal state of the QD parameter is "0". Note Only use a counter at a single location in the program to avoid counting errors. Each call of the "Count up and down" instruction must be assigned an IEC counter in which the instruction data is stored. An IEC counter is a structure with one of the following data types: For S7-1200 CPU Data block of system data type IEC_<Counter> (Shared DB) Local tag IEC_SCOUNTER / IEC_USCOUNTER CTUD_SINT / CTUD_USINT IEC_COUNTER / IEC_UCOUNTER CTUD_INT / CTUD_UINT IEC_DCOUNTER / IEC_UDCOUNTER CTUD_DINT / CTUD_UDINT Data block of system data type IEC_<Counter> (Shared DB) Local tag IEC_SCOUNTER / IEC_USCOUNTER CTUD_SINT / CTUD_USINT IEC_COUNTER / IEC_UCOUNTER CTUD_INT / CTUD_UINT IEC_DCOUNTER / IEC_UDCOUNTER CTUD_DINT / CTUD_UDINT IEC_LCOUNTER / IEC_ULCOUNTER CTUD_LINT / CTUD_ULINT For S7-1500 CPU You can declare an IEC counter as follows: Declaration of a data block of system data type IEC_<Counter> (for example, "MyIEC_COUNTER") Declaration as a local tag of the type CTUD_<Data type> in the "Static" section of a block (for example, #MyCTUD_COUNTER) When you insert the instruction in the program, the "Call options" dialog opens in which you can specify whether the IEC counter is stored in its own data block (single instance) or as a local tag (multiple instance) in the block interface. If you create a separate data block, you will find it in the project tree in the "Program resources" folder under "Program blocks > System blocks". For additional information on this topic, refer to "See also". When you set up the IEC counter in a separate data block (single instance), the instance data block is created by default with "optimized block access" and the individual tags are defined 2336 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References as retentive. For additional information on setting retentivity in an instance data block, refer to "See also". When you set up the IEC counter as local tag (multiple instance) in a function block with "optimized block access", it is defined as retentive in the block interface. Syntax The following syntax is used for the "Count up and down" instruction: Table 9-32 Data block of system data type IEC_counter (global DB) SCL <IEC_Counter_DB>.CTUD(CU := <Operand>, CD := <Operand>, R := <Operand>, LD := <Operand>, PV := <Operand>, QU=> <Operand>, QD := <Operand>, CV => <Operand>) Table 9-33 Local tag SCL myLocal_counter(CU := <Operand>, CD := <Operand>, R := <Operand>, LD := <Operand>, PV := <Operand>, QU=> <Operand>, QD := <Operand>, CV => <Operand>) The syntax of the instruction consists of the following parts: Parameter Declaration Data type Description CU Input BOOL Count up input CD Input BOOL Count down input R Input BOOL Reset input LD Input BOOL Load input PV Input Integers Value at which the QU output is set. QU Output BOOL Status of the up counter QD Output BOOL Status of the down counter CV Output Integers, CHAR, DATE Current counter value For additional information on valid data types, refer to "See also". WinCC Basic V13.0 System Manual, 02/2014 2337 Programming the PLC 9.7 References Example The following example shows how the instruction works: SCL "IEC_COUNTER_DB".CTUD(CU := "Tag_Start1", CD := "Tag_Start2", LD := "Tag_Load", R := "Tag_Reset", PV := "Tag_PresetValue", QU => "Tag_CU_Status", QD => "Tag_CD_Status", CV => "Tag_CounterValue"); If the "Tag_Start1" operand has a positive signal edge in the signal state, the current counter value is incremented by one and stored in the "Tag_CounterValue" operand. If the "Tag_Start2" operand has a positive signal edge in the signal state, the counter value is decremented by one and is also stored in the "Tag_CounterValue" operand. The counter value is incremented on the positive signal edge of the CU parameter until it reaches the high limit of the specified data type (INT). If the CD parameter has a positive signal edge, the counter value is decremented until it reaches the low limit of the specified data type (INT). The operand "Tag_CU_Status" has the signal state "1" as long as the current counter value is greater than or equal to the value of the operand "Tag_PresetValue". In all other cases, the "Tag_CU_Status" output has signal state "0". The operand "Tag_CD_Status" has the signal state "1" as long as the current counter value is less than or equal to zero. In all other cases, the "Tag_CD_Status" output has signal state "0". See also Overview of the valid data types (Page 1204) Setting retentivity in an instance data block (Page 1536) Setting the retentivity of local tags (Page 1391) SIMATIC Counters S_CU: Assign parameters and count up Description You can use the "Assign parameters and count up" instruction to increment the value of a counter. When the signal state of the parameter CU changes from "0" to "1" (positive signal edge), the current counter value is incremented by one. The current counter value is provided at the parameter CV. The counter value is incremented until the limit of "999" is reached. When the limit value is reached, the counter value is no longer incremented on a positive signal edge. When the signal state of the parameter S changes from "0" to "1", the counter value is set to the value of the parameter PV. If the counter is set and if the result of logic operation (RLO) at the CU input is "1", the counter counts once in the next cycle, even when no signal edge change is detected. 2338 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References The counter value is set to zero when the signal state of the parameter R changes to "1". As long as the parameter R has the signal state "1", a change in the signal state of the parameters CU and S has no effect on the counter value. The signal state at parameter Q is "1" if the counter value is greater than zero. When the counter value equals zero, parameter Q returns signal state "0". Note Only use a counter at a single point in the program to avoid the risk of counting errors. Syntax The following syntax is used for the "Assign parameters and count up" instruction: SCL S_CU(C_NO := <Operand>, CU:= <Operand>, S := <Operand>, PV := <Operand>, R := <Operand>, Q => <Operand>, CV=> <Operand>) The syntax of the instruction consists of the following parts: Parameter Declaration Data type Description C_NO Input COUNTER, INT Counters The number of counters depends on the CPU. CU Input BOOL Count up input S Input BOOL Input for presetting the counter PV Input WORD Preset counter value (C#0 to C#999) in BCD format R Input BOOL Reset input Q Output BOOL Status of the counter CV Output WORD, S5TIME, DATE Current counter value Function value WORD, S5TIME, DATE Current counter value in BCD format For additional information on valid data types, refer to "See also". WinCC Basic V13.0 System Manual, 02/2014 2339 Programming the PLC 9.7 References Example The following example shows how the instruction works: SCL "Tag_Result" := S_CU(C_NO := "Counter_1", CU := "Tag_Start", S := "Tag_1", PV := "Tag_PresetValue", R := "Tag_Reset", Q => "Tag_Status", CV => "Tag_Value"); If the signal state of the "Tag_Start" parameter changes from "0" to "1" (positive signal edge) and the current counter value is less than "999", the counter value is incremented by one. If the signal state of the input "Tag_1" changes from "0" to "1", the counter value in BCD format is set to the value of the operand "Tag_PresetValue". The counter value is reset to "0" when the operand "Tag_Reset" has signal state "1". The current counter value is stored in hexadecimal form in the operand "Tag_Value". The output "Tag_Status" has the signal state "1" as long as the current counter value is not equal to "0". The current counter value is returned in the "Tag_Value" operand and as a function value. See also Overview of the valid data types (Page 1204) S_CD: Assign parameters and count down Description You can use the "Assign parameters and count down" instruction to decrement the value of a counter. When the signal state of the parameter CD changes from "0" to "1" (positive signal edge), the current counter value is decreased by one. The current counter value is provided at the parameter CV. The counter value is decreased until the low limit of "0" is reached. When the low limit value is reached, the counter value is no longer decreased on a positive signal edge. When the signal state of the parameter S changes from "0" to "1", the counter value is set to the value of the parameter PV. If the counter is set and if the result of logic operation (RLO) at the parameter CD is "1", the counter counts once in the next cycle, even when no signal edge change is detected. The counter value is set to zero when the signal state of the parameter R changes to "1". As long as the parameter R has the signal state "1", a change in the signal state of the parameters CD and S has no effect on the counter value. 2340 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References The signal state at parameter Q is "1" if the counter value is greater than zero. When the counter value equals zero, parameter Q returns signal state "0". Note Only use a counter at a single location in the program to avoid risk of counting errors. Syntax The following syntax is used for the "Assign parameters and count down" instruction: SCL S_CD(C_NO:= <Operand>, CD:= <Operand>, S:= <Operand>, PV:= <Operand>, R:= <Operand>, Q=> <Operand>, CV=> <Operand>) The syntax of the instruction consists of the following parts: Parameter Declaration Data type Description C_NO Input COUNTER, INT Counters The number of counters depends on the CPU. CD Input BOOL Count down input S Input BOOL Input for presetting the counter PV Input WORD Preset counter value (C#0 to C#999) in BCD format R Input BOOL Reset input Q Output BOOL Status of the counter CV Output WORD, S5TIME, WORD Current counter value Function value WORD, S5TIME, DATE Current counter value in BCD format For additional information on valid data types, refer to "See also". Example The following example shows how the instruction works: SCL "Tag_Result" := S_CD(C_NO := "Counter_1", WinCC Basic V13.0 System Manual, 02/2014 2341 Programming the PLC 9.7 References SCL CD := "Tag_Start", S := "Tag_1", PV := "Tag_PresetValue", R := "Tag_Reset", Q => "Tag_Status", CV => "Tag_Value"); When the signal state of the operand "Tag_Start" changes from "0" to "1" (positive signal edge) and the current counter value is greater than "0", the counter value is decreased by one. If the signal state of the operand "Tag_1" changes from "0" to "1", the counter value is set to the value of the operand "Tag_PresetValue". The counter value is reset to "0" when the operand "Tag_Reset" has signal state "1". The current counter value is stored in the operand "Tag_Value". The operand "Tag_Status" returns signal state "1" as long as the current counter value is not equal to "0". The current counter value is returned in the "Tag_Value" operand and as a function value. See also Overview of the valid data types (Page 1204) S_CUD: Assign parameters and count up / down Description You can use the "Assign parameters and count up / down" instruction to increment and decrement the value of a counter. When the signal state of the parameter CU changes from "0" to "1" (positive signal edge), the current counter value is incremented by one. When the signal state of the parameter CD changes from "0" to "1" (positive signal edge), the counter value is decreased by one. The current counter value is provided at the parameter CV. If there is a positive signal edge at the parameters CU and CD in one program cycle, the counter value remains unchanged. The counter value is incremented until the high limit value of "999" is reached. When the high limit value is reached, the counter value is no longer incremented on a positive signal edge. When the low limit value "0" is reached, the counter value is not decremented any further. When the signal state of the parameter S changes from "0" to "1", the counter value is set to the value of the parameter PV. If the counter is set and if the result of logic operation (RLO) of the parameters CU and CD is "1", the counter will count once in the next cycle, even if no signal edge change was detected. The counter value is set to zero when the signal state of the parameter R changes to "1". As long as the parameter R has the signal state "1", processing of the signal state of the parameters CU, CD and S has no effect on the counter value. 2342 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References The signal state at parameter Q is "1" if the counter value is greater than zero. When the counter value equals zero, parameter Q returns signal state "0". Note Only use a counter at a single location in the program to avoid risk of counting errors. Syntax The following syntax is used for the "Assign parameters and count up / down" instruction: SCL S_CUD(C_NO:= <Operand>, CU:= <Operand>, CD:= <Operand>, S:= <Operand>, PV:= <Operand>, R:= <Operand>, Q=> <Operand>, CV=> <Operand>) The syntax of the instruction consists of the following parts: Parameter Declaration Data type Description C_NO Input COUNTER, INT Counters The number of counters depends on the CPU. CU Input BOOL Count up input CD Input BOOL Count down input S Input BOOL Input for presetting the counter PV Input WORD Preset counter value (C#0 to C#999) in BCD format R Input BOOL Reset input Q Output BOOL Status of the counter CV Output WORD, S5TIME, DATE Current counter value (hexadecimal) Function value WORD, S5TIME, DATE Current counter value in BCD format For additional information on valid data types, refer to "See also". WinCC Basic V13.0 System Manual, 02/2014 2343 Programming the PLC 9.7 References Example The following example shows how the instruction works: SCL "Tag_Result" := S_CD(C_NO := "Counter_1", CU := "Tag_CU", CD := "Tag_CD", S := "Tag_1", PV := "Tag_PresetValue", R := "Tag_Reset", Q => "Tag_Status", CV => "Tag_Value"); When a positive signal edge is detected in the signal state of the operand "Tag_CU" and the current counter value is less than "999", the counter value is incremented by one. When a positive signal edge is detected in the signal state of the operand "Tag_CD" and the current counter value is greater than "0", the counter value is decremented by one. If the signal state of the operand "Tag_1" changes from "0" to "1", the counter value is set to the value of the operand "Tag_PresetValue". The counter value is reset to "0" when the operand "Tag_Reset" has signal state "1". The current counter value is stored in the operand "Tag_Value". The operand "Tag_Status" returns signal state "1" as long as the current counter value is not equal to "0". The current counter value is returned in the "Tag_Value" operand and as a function value. See also Overview of the valid data types (Page 1204) Comparator operations TypeOf: Query data type of a VARIANT tag Description You can use the "Check data type of a VARIANT tag" instruction to query the data type of a tag to which a VARIANT tag is pointing. You compare the data type of the tag to the data type of a tag that you have declared in the block interface to determine whether they are "Equal" or "Not equal". The operand must have the VARIANT data type. The comparison operand can be an elementary data type or a PLC data type. You can only use the "Check data type of a VARIANT tag" instruction within an IF instruction. 2344 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Syntax The following syntax is used for the "Check data type of a VARIANT tag" instruction: SCL TypeOf(<Operand>) Parameters The following table shows the parameters of the "Check data type of a VARIANT tag" instruction: Parameter Declaration Data type Description <Operand> Input VARIANT First operand For additional information on valid data types, refer to "See also". Example The following example shows how the instruction works: SCL IF TypeOf(#TagVARIANT) = TypeOf("TagBOOL") THEN ...; END_IF; If the operand to which the VARIANT "#TagVARIANT" is pointing has the BOOL data type, a specific command is to be executed. See also Overview of the valid data types (Page 1204) TypeOfElements: Check element data type of a VARIANT tag Description You can use the "Check element data type of a VARIANT tag" instruction to query the data type of a tag to which a VARIANT is pointing. You compare the data type of the tag to the data type of a tag that you have declared in the block interface to determine whether they are "Equal" or "Not equal". The operand must have the VARIANT data type. The comparison operand can be an elementary data type or a PLC data type. If the data type of the VARIANT tag is an ARRAY, the data type of the ARRAY elements is compared. WinCC Basic V13.0 System Manual, 02/2014 2345 Programming the PLC 9.7 References You can only use the "Check element data type of a VARIANT tag" instruction within an IF instruction. Syntax The following syntax is used for the "Check element data type of a VARIANT tag" instruction: SCL TypeOfElements(<Operand>) Parameter The following table shows the parameters of the "Check element data type of a VARIANT tag" instruction: Parameter Declaration Data type Description <Operand> Input VARIANT First operand For additional information on valid data types, refer to "See also". Example The following example shows how the instruction works: SCL IF TypeOfElements(#Tag_VARIANT) = TypeOf("GlobalDB".Product[1]) THEN "Tag_Result" := "GlobalDB".Product[1] * 3; END_IF; The following table shows how the instruction works using specific operand values: Operand Value #Tag_VARIANT 1.5 "GlobalDB".Product[1] 3.5 If the tag to which the VARIANT points and the ""GlobalDB".Product[1]" operand have the REAL data type, the "GlobalDB".Product[1]" operand is then multiplied by 3 and the result is written to the "Tag_Result" operand. See also Overview of the valid data types (Page 1204) 2346 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References IS_ARRAY: Check for ARRAY Description You can use the "Check for ARRAY" instruction to query whether the VARIANT points to a tag of the ARRAY data type. The <Operand> must have the VARIANT data type. You can only use the "Check for ARRAY" instruction within an IF instruction. Syntax The following syntax is used for the "Check for ARRAY" instruction: SCL IS_ARRAY(<Operand>) Parameter The following table shows the parameters of the "Check for ARRAY" instruction: Parameter Declaration Data type Description <Operand> Input VARIANT Operand that is queried for ARRAY UDINT Result of the instruction Function value For additional information on valid data types, refer to "See also". Example The following example shows how the instruction works: SCL IF IS_ARRAY(#Tag_VARIANTToArray) THEN "Tag_Result" := CountOfElements(#Tag_VARIANT); END_IF; If the tag to which the VARIANT points is an ARRAY, the number of ARRAY elements is output. See also Overview of the valid data types (Page 1204) WinCC Basic V13.0 System Manual, 02/2014 2347 Programming the PLC 9.7 References Math functions ABS: Form absolute value Description Use the "Form absolute value" instruction to calculate the absolute value of an input value and to save the result in the specified operands. Syntax Use the following syntax for the "Form absolute value" instruction: SCL ABS(<Expression>) The syntax of the instruction consists of the following parts: Parameter Declaration <Expression> Input Function value Data type Description S7-1200 S7-1500 SINT, INT, DINT, floating-point numbers SINT, INT, DINT, LINT, floatingpoint numbers Input value SINT, INT, DINT, floating-point numbers SINT, INT, DINT, LINT, floatingpoint numbers Absolute value of the input value For additional information on valid data types, refer to "See also". Example The following example shows how the instruction works: SCL "Tag_Result1" := ABS("Tag_Value"); "Tag_Result2" := ABS("Tag_Value1"*"Tag_Value2"); The absolute value of the input value is returned in the format of the input value as a function value. The following table shows how the instruction works using specific operand values: 2348 Operand Value Tag_Value -2 Tag_Result1 2 Tag_Value1 4 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Operand Value Tag_Value2 -1 Tag_Result2 4 See also Overview of the valid data types (Page 1204) Expressions (Page 1480) Operators and operator precedence (Page 1486) MIN: Get minimum Description The "Get minimum" instruction compares the values of the available inputs and returns the lowest value as the result. A minimum of two and a maximum of 32 inputs can be specified at the instruction. The result is invalid if any of the following conditions are met: The implicit conversion of the data types fails during execution of the instruction. A floating-point number has an invalid value. Syntax The following syntax is used for the "Get minimum" instruction: SCL MIN(IN1:= <Operand>, IN2 := <Operand>) WinCC Basic V13.0 System Manual, 02/2014 2349 Programming the PLC 9.7 References Parameter The following table shows the parameters of the "Get minimum" instruction: Parameter Declaration Data type Description S7-1200 S7-1500 IN1 Input Integers, floatingpoint numbers, TIME, TOD, DATE, DTL Integers, floatingpoint numbers, TIME, LTIME, TOD, LTOD, DATE, LDT, DT, DTL First input value IN2 Input Integers, floatingpoint numbers, TIME, TOD, DATE, DTL Integers, floatingpoint numbers, TIME, LTIME, TOD, LTOD, DATE, LDT, DT, DTL Second input value INn Input Integers, floatingpoint numbers, TIME, TOD, DATE, DTL Integers, floatingpoint numbers, TIME, LTIME, TOD, LTOD, DATE, LDT, DT, DTL Additionally inserted inputs whose values are to be compared Integers, floatingpoint numbers, TIME, TOD, DATE, DTL Integers, floatingpoint numbers, TIME, LTIME, TOD, LTOD, DATE, LDT, DT, DTL Result of the instruction Function value The data types TOD, LTOD, DATE, and LDT can only be used if the IEC test is not enabled. For additional information on valid data types, refer to "See also". Example The following example shows how the instruction works: SCL "Tag_Result" := MIN(IN1 := "Tag_Value1", IN2 := "Tag_Value2", IN3 := "Tag_Value3"); The following table shows how the instruction works using specific operand values: 2350 Parameter Operand Value IN1 Tag_Value1 12222 IN2 Tag_Value2 14444 IN3 Tag_Value3 13333 Function value Tag_Result 12222 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References The instruction compares the values of the available inputs and copies the lowest value ("Tag_Value1") to operand "Tag_Result". See also Overview of the valid data types (Page 1204) Expressions (Page 1480) Operators and operator precedence (Page 1486) MAX: Get maximum Description The "Get maximum" instruction compares the values of the available inputs and returns the greatest value as the result. A minimum of two and a maximum of 32 inputs can be specified at the instruction. The result is invalid if any of the following conditions are met: The implicit conversion of the data types fails during execution of the instruction. A floating-point number has an invalid value. Syntax The following syntax is used for the "Get maximum" instruction: SCL MAX(IN1:= <Operand>, IN2 := <Operand>) WinCC Basic V13.0 System Manual, 02/2014 2351 Programming the PLC 9.7 References Parameters The following table shows the parameters of the "Get maximum" instruction: Parameter Declaration Data type Description S7-1200 S7-1500 IN1 Input Integers, floatingpoint numbers, TIME, TOD, DATE, DTL Integers, floatingpoint numbers, TIME, LTIME, TOD, LTOD, DATE, LDT, DT, DTL First input value IN2 Input Integers, floatingpoint numbers, TIME, TOD, DATE, DTL Integers, floatingpoint numbers, TIME, LTIME, TOD, LTOD, DATE, LDT, DT, DTL Second input value INn Input Integers, floatingpoint numbers, TIME, TOD, DATE, DTL Integers, floatingpoint numbers, TIME, LTIME, TOD, LTOD, DATE, LDT, DT, DTL Additionally inserted inputs whose values are to be compared Integers, floatingpoint numbers, TIME, TOD, DATE, DTL Integers, floatingpoint numbers, TIME, LTIME, TOD, LTOD, DATE, LDT, DT, DTL Result of the instruction Function value The data types TOD, LTOD, DATE, and LDT can only be used if the IEC test is not enabled. For additional information on valid data types, refer to "See also". Example The following example shows how the instruction works: SCL "Tag_Result" := MAX(IN1 := "Tag_Value1", IN2 := "Tag_Value2", IN3 := "Tag_Value3"); The following table shows how the instruction works using specific operand values: 2352 Parameter Operand Value IN1 Tag_Value1 12 222 IN2 Tag_Value2 14 444 IN3 Tag_Value3 13 333 Function value Tag_Result 14 444 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References The instruction compares the values of the specified operands and copies the greatest value ("Tag_Value2") to the operand "Tag_Result". See also Overview of the valid data types (Page 1204) Expressions (Page 1480) Operators and operator precedence (Page 1486) LIMIT: Set limit value Description The "Set limit value" instruction limits the value of the parameter IN to the values of the parameters MN and MX. The value of the parameter MN may not be greater than the value of the parameter MX. If the value of the IN parameter fulfills the MN condition <=IN <= MX, it is returned as the result of the instruction. If the condition is not fulfilled and the IN input value is less than the MN low limit, the value of the MN parameter is returned as the result. If the high limit MX is exceeded, the value of the MX parameter is returned as the result. If the value of the MN input is greater than the value of the MX input, the result is undefined. The instruction is only executed if the operands of all parameters are of the same data type. Syntax The following syntax is used for the "Set limit value" instruction: SCL LIMIT(MN := <Operand>, IN := <Operand>, MX := <Operand>) The syntax of the instruction consists of the following parts: WinCC Basic V13.0 System Manual, 02/2014 2353 Programming the PLC 9.7 References Parameter Declaration Data type Description S7-1200 S7-1500 MN Input Integers, floatingpoint numbers, TIME, TOD, DATE, DTL Integers, floatingpoint numbers, TIME, LTIME, TOD, LTOD, DATE, LDT, DT, DTL Low limit IN Input Integers, floatingpoint numbers, TIME, TOD, DATE, DTL Integers, floatingpoint numbers, TIME, LTIME, TOD, LTOD, DATE, LDT, DT, DTL Input value MX Input Integers, floatingpoint numbers, TIME, TOD, DATE, DTL Integers, floatingpoint numbers, TIME, LTIME, TOD, LTOD, DATE, LDT, DT, DTL High limit Integers, floatingpoint numbers, TIME, TOD, DATE, DTL Integers, floatingpoint numbers, TIME, LTIME, TOD, LTOD, DATE, LDT, DT, DTL Result of the instruction Function value The data types TOD, LTOD, DATE, and LDT can only be used if the IEC test is not enabled. For additional information on valid data types, refer to "See also". Example The following example shows how the instruction works: SCL "Tag_Result" := LIMIT(MN := "Tag_Minimum", IN := "Tag_Value", MX := "Tag_Maximum"); The following table shows how the instruction works using specific operand values: Parameter Operand Value MN Tag_Minimum 12 000 IN Tag_Value 8 000 MX Tag_Maximum 16 000 Function value Tag_Result 12 000 The value of operand "Tag_Value" is compared with the values of operands "Tag_Minimum" and "Tag_Maximum". Because the value of the operand "Tag_Value" is less than the low limit value, the value of operand "Tag_Minimum" will be copied to operand "Tag_Result". 2354 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References See also Overview of the valid data types (Page 1204) Expressions (Page 1480) Operators and operator precedence (Page 1486) SQR: Form square Description Use the "Form square" instruction to square the input value and save the result in the specified operand. Syntax Use the following syntax for the instruction "Form square": SCL SQR(<Expression>) The syntax of the instruction consists of the following parts: Parameter Declaration Data type Description <Expression> Input Floating-point numbers Input value Floating-point numbers Square of the input value Function value For additional information on valid data types, refer to "See also". Example The following example shows how the instruction works: SCL "Tag_Result1" := SQR("Tag_Value"); "Tag_Result2" := SQR((SQR("Tag_Value1"))*"Tag_Value2); The square of the input value is returned in the operand "Tag_Result" as a function value. The following table shows how the instruction works using specific operand values: WinCC Basic V13.0 System Manual, 02/2014 Operand Value Tag_Value 2.5 Tag_Result1 6.25 Tag_Value1 6.0 Tag_Value2 2.0 Tag_Result2 5184.0 2355 Programming the PLC 9.7 References See also Overview of the valid data types (Page 1204) Expressions (Page 1480) Operators and operator precedence (Page 1486) SQRT: Form square root Description Use the "Form square root" instruction to calculate the square root of the the input value and save the result in the specified operand. The instruction has a positive result if the input value is greater than zero. If input values are less than zero, the instruction returns an invalid floatingpoint number. If the input value is "-0", the result is also "-0". Syntax Use the following syntax for the "Form square root" instruction: SCL SQRT(<Expression>) The syntax of the instruction consists of the following parts: Parameter Declaration Data type Description <Expression> Input Floating-point numbers Input value Floating-point numbers Square root of the input value Function value For additional information on valid data types, refer to "See also". Example The following example shows how the instruction works: SCL "Tag_Result1" := SQRT("Tag_Value"); "Tag_Result2" := SQRT((SQR("Tag_Value1"))+"Tag_Value2"); The square root of the input value is returned in the operand "Tag_Result" as a function value. The following table shows how the instruction works using specific operand values: 2356 Operand Value Tag_Value 4.0 Tag_Result1 2.0 Tag_Value1 3.0 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Operand Value Tag_Value2 16.0 Tag_Result2 5.0 See also Overview of the valid data types (Page 1204) Expressions (Page 1480) Operators and operator precedence (Page 1486) LN: Form natural logarithm Description You can use the "Form natural logarithm" instruction to calculate the natural logarithm to base e (e=2.718282) of the input value. The instruction has a positive result if the input value is greater than zero. If input values are less than zero, the instruction returns an invalid floatingpoint number. Syntax Use the following syntax for the "Form natural logarithm" instruction: SCL LN(<Expression>) The syntax of the instruction consists of the following parts: Parameter Declaration Data type Description <Expression> Input Floating-point numbers Input value Floating-point numbers Natural logarithm of the input value Function value For additional information on valid data types, refer to "See also". Example The following example shows how the instruction works: SCL "Tag_Result1" := LN("Tag_Value"); "Tag_Result2" := LN("Tag_Value1"+"Tag_Value2"); The result of the instruction is returned in the operand "Tag_Result" as a function value. The following table shows how the instruction works using specific operand values: WinCC Basic V13.0 System Manual, 02/2014 2357 Programming the PLC 9.7 References Operand Value Tag_Value 2.5 Tag_Result1 0.916 Tag_Value1 1.5 Tag_Value2 3.2 Tag_Result2 1.548 See also Overview of the valid data types (Page 1204) Expressions (Page 1480) Operators and operator precedence (Page 1486) EXP: Form exponential value Description The "Form exponential value" instruction calculates the exponent from the base e (e = 2.718282) and the input value and saves the result in the specified operand. Syntax The following syntax is used for the "Form exponential value" instruction: SCL EXP(<Expression>) The syntax of the instruction consists of the following parts: Parameter Declaration Data type Description <Expression> Input Floating-point numbers Input value Floating-point numbers Exponential value of the input value Function value For additional information on valid data types, refer to "See also". Example The following example shows how the instruction works: SCL "Tag_Result1" := EXP("Tag_Value"); "Tag_Result2" := EXP("Tag_Value1"/"Tag_Value2"); The result of the instruction is returned in the operand "Tag_Result" as a function value. 2358 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References The following table shows how the instruction works using specific operand values: Operand Value Tag_Value 20.5 Tag_Result1 799 902 200 Tag_Value1 15.5 Tag_Value2 30.2 Tag_Result2 1.671 See also Overview of the valid data types (Page 1204) Expressions (Page 1480) Operators and operator precedence (Page 1486) SIN: Form sine value Description Use the "Form sine value" instruction to calculate the sine of the input value. The input value must be given in the radian measure. Syntax Use the following syntax for the "Form sine value" instruction: SCL SIN(<Expression>) The syntax of the instruction consists of the following parts: Parameter Declaration Data type Description <Expression> Input Floating-point numbers Input value (size of an angle in the radian measure) Floating-point numbers Result of the instruction Function value For additional information on valid data types, refer to "See also". Example The following example shows how the instruction works: SCL "Tag_Result" := SIN("Tag_Value"); WinCC Basic V13.0 System Manual, 02/2014 2359 Programming the PLC 9.7 References The result of the instruction is returned in the "Tag_Result" operand as a function value. The following table shows how the instruction works using specific operand values: Operand Value Tag_Value +1.570796 (/2) Tag_Result 1.0 See also Overview of the valid data types (Page 1204) Expressions (Page 1480) Operators and operator precedence (Page 1486) COS: Form cosine value Description Use the "Form cosine value" instruction to calculate the cosine of the input value. The input value must be given in the radian measure. Syntax Use the following syntax for the "Form cosine value" instruction: SCL COS(<Expression>) The syntax of the instruction consists of the following parts: Parameter Declaration Data type Description <Expression> Input Floating-point numbers Input value (size of an angle in the radian measure) Floating-point numbers Result of the instruction Function value For additional information on valid data types, refer to "See also". Example The following example shows how the instruction works: SCL "Tag_Result" := COS("Tag_Value"); The result of the instruction is returned in the operand "Tag_Result" as a function value. 2360 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References The following table shows how the instruction works using specific operand values: Operand Value Tag_Value +1.570796 (/2) Tag_Result 0 See also Overview of the valid data types (Page 1204) Expressions (Page 1480) Operators and operator precedence (Page 1486) TAN: Form tangent value Description Use the "Form tangent value" instruction to calculate the sine of the input value. The input value must be given in the radian measure. Syntax Use the following syntax for the "Form tangent value" instruction: SCL TAN(<Expression>) The syntax of the instruction consists of the following parts: Parameter Declaration Data type Description <Expression> Input Floating-point numbers Input value (size of an angle in the radian measure) Floating-point numbers Result of the instruction Function value For additional information on valid data types, refer to "See also". Example The following example shows how the instruction works: SCL "Tag_Result" := TAN("Tag_Value"); The result of the instruction is returned in the operand "Tag_Result" as a function value. The following table shows how the instruction works using specific operand values: WinCC Basic V13.0 System Manual, 02/2014 2361 Programming the PLC 9.7 References Operand Value Tag_Value +3.141593 () Tag_Result 0 See also Overview of the valid data types (Page 1204) Expressions (Page 1480) Operators and operator precedence (Page 1486) ASIN: Form arcsine value Description You can use the "Form arcsine value" instruction to calculate the size of the angle from a sine value, which corresponds to this value. Only valid floating-point numbers within the range -1 to +1 can be specified as input values. The calculated angle size is given in the radian measure and can range in value from -/2 to +/2. Syntax Use the following syntax for the "Form arcsine value" instruction: SCL ASIN(<Expression>) The syntax of the instruction consists of the following parts: Parameter Declaration Data type Description <Expression> Input Floating-point numbers Sine value Floating-point numbers Size of angle in the radian measure Function value For additional information on valid data types, refer to "See also". Example The following example shows how the instruction works: SCL "Tag_Result" := ASIN("Tag_Value"); The result of the instruction is returned in the operand "Tag_Result" as a function value. The following table shows how the instruction works using specific operand values: 2362 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Operand Value Tag_Value 1.0 Tag_Result +1.570796 (/2) See also Overview of the valid data types (Page 1204) Expressions (Page 1480) Operators and operator precedence (Page 1486) ACOS: Form arccosine value Description You can use the "Form arccosine value" instruction to calculate the size of the angle from a cosine value, which corresponds to this value. Only valid floating-point numbers within the range -1 to +1 can be specified as input values. The calculated angle size is given in the radian measure and can range in value from 0 to +. Syntax Use the following syntax for the "Form arccosine value" instruction: SCL ACOS(<Expression>) The syntax of the instruction consists of the following parts: Parameter Declaration Data type Description <Expression> Input Floating-point numbers Cosine value Floating-point numbers Size of angle in the radian measure Function value For additional information on valid data types, refer to "See also". Example The following example shows how the instruction works: SCL "Tag_Result" := ACOS("Tag_Value"); The result of the instruction is returned in the "Tag_Result" operand as a function value. The following table shows how the instruction works using specific operand values: WinCC Basic V13.0 System Manual, 02/2014 2363 Programming the PLC 9.7 References Operand Value Tag_Value 0 Tag_Result +1.570796 (/2) See also Overview of the valid data types (Page 1204) Expressions (Page 1480) Operators and operator precedence (Page 1486) ATAN: Form arctangent value Description You can use the "Form arctangent value" instruction to calculate the size of the angle from a tangent value, which corresponds to this value. Only valid floating-point numbers may be specified as input values. The calculated angle size is given in the radian measure and can range in value from -/2 to +/2. Syntax Use the following syntax for the "Form arctangent value" instruction: SCL ATAN(<Expression>) The syntax of the instruction consists of the following parts: Parameter Declaration Data type Description <Expression> Input Floating-point numbers Tangent value Floating-point numbers Size of angle in the radian measure Function value For additional information on valid data types, refer to "See also". Example The following example shows how the instruction works: SCL "Tag_Result" := ATAN("Tag_Value"); The result of the instruction is returned in the operand "Tag_Result" as a function value. The following table shows how the instruction works using specific operand values: 2364 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Operand Value Tag_Value 1.0 Tag_Result +0.785398 (/4) See also Overview of the valid data types (Page 1204) Expressions (Page 1480) Operators and operator precedence (Page 1486) FRAC: Return fraction Description The result of the instruction "Return fraction" returns the decimal places of a value. Input value 123.4567, for example, returns the value 0.4567. Syntax The following syntax is used for the instruction "Return fraction": SCL FRAC(<Expression>) FRAC_<Data type>(<Expression>) The syntax of the instruction consists of the following parts: Parameter Declaration Data type Description <Expression> Input Floating-point numbers Input value Floating-point numbers Data type of the function value: _<Data type> Default: REAL You do not need to specify the data type if using the default. Any other valid data type you may use must be declared explicitly. Function value Floating-point numbers Decimal places of the input value For additional information on valid data types, refer to "See also". WinCC Basic V13.0 System Manual, 02/2014 2365 Programming the PLC 9.7 References Example The following example shows how the instruction works: SCL "Tag_Result1" := FRAC("Tag_Value"); "Tag_Result2" := FRAC_LREAL("Tag_Value"); The following table shows how the instruction works using specific operand values: Operand Value Tag_Value 2.555 -1.4421 Tag_Result1 0.555 -0.4421 See also Overview of the valid data types (Page 1204) Expressions (Page 1480) Operators and operator precedence (Page 1486) Move operations Deserialize: Deserialization Description You can use the "Deserialize" instruction to convert the sequential representation of a PLC data type (UDT) back to a PLC data type and to fill its entire contents. The memory area in which the sequential representation of a PLC data type is located must have the ARRAY of BYTE data type and be declared with standard access. Make sure that there is enough memory space prior to the conversion. The instruction enables you to convert multiple sequential representations of converted PLC data types back to their original state step-by-step. Note If you only want to convert back a single sequential representation of a PLC data type (UDT), you can also use the instruction "TRCV: Receive data via communication connection" directly. 2366 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Syntax The following syntax is used for the "Deserialize" instruction: SCL Deserialize(SRC_ARRAY := <Operand>, DEST_VARIABLE:= <Operand>, POS := <Operand>) Parameter The following table shows the parameters of the "Deserialize" instruction: Parameter Declaration Data type Description SRC_ARRAY Input VARIANT Global data block in which the generated data stream is stored DEST_VARIAB InOut LE VARIANT Tag in which the returned converted PLC data type (UDT) is stored POS DINT Number of bytes that the converted PLC data types use. The POS parameter is calculated zero-based. INT Error information InOut Function value For additional information on valid data types, refer to "See also". RET_VAL parameter The following table shows the meaning of the values of the RET_VAL parameter: Error code* (W#16#...) Explanation 0000 No error 80B0 The memory areas for the SRC_ARRAY and DEST_VARIABLE parameters overlap. 8136 The data block at the DEST_VARIABLE parameter is not a block with standard access. 8150 The VARIANT data type at the SRC_ARRAY parameter contains no value. 8151 Code generation error at SRC_ARRAY parameter 8153 There is not enough free memory available at the SRC_ARRAY parameter. 8250 The VARIANT data type at the DEST_VARIABLE parameter contains no value. 8251 Code generation error at DEST_VARIABLE parameter 8254 Invalid data type at the DEST_VARIABLE parameter 8382 The value at the POS parameter is outside the limits of the array. *The error codes can be displayed as integer or hexadecimal value in the program editor. For information on toggling display formats, refer to "See also". WinCC Basic V13.0 System Manual, 02/2014 2367 Programming the PLC 9.7 References Example The following example shows how the instruction works: SCL #Tag_RetVal := Deserialize(SRC_ARRAY := "Buffer".Field, DEST_VARIABLE := "Target".Client, POS := #BufferPos); #Tag_RetVal := Deserialize(SRC_ARRAY := "Buffer".Field, DEST_VARIABLE := #Label, POS := #BufferPos); IF #Label = 'arti' THEN #Tag_RetVal := Deserialize(SRC_ARRAY := "Buffer".Field, DEST_VARIABLE := "Target".Article[#DeliverPos], POS := #BufferPos); ELSIF #Label = 'Bill' THEN #Tag_RetVal := Deserialize(SRC_ARRAY := "Buffer".Field, DEST_VARIABLE := "Target".Bill[#DeliverPos], POS := #BufferPos); ; ELSE ; END_IF; The "Move value" instruction moves the value "0" to the "#BufferPos" operand. The "Deserialize" instruction deserializes the sequential representation of the customer data from the "Buffer" data block and writes it to the "Target" data block. The number of bytes used by the converted customer data is stored in the "#BufferPos" operand. The "Deserialize" instruction deserializes the sequential representation of the separator sheet, which was saved with the sequential representation after the customer data, from the "Buffer" data block and writes the characters to the "#Label" operand. The characters are compared using comparison instructions for "arti" and "Bill". If the comparison for "arti" = TRUE, these are article data that have been deserialized and written to the "Target" data block. If the comparison for "Bill" = TRUE, these are billing data that have been deserialized and written to the "Target" data block. The following table shows the declaration of the operands: Operand Data type Declaration DeliverPos INT In the "Input" section of the block interface BufferPos DINT In the "Temp" section of the block interface Error INT In the "Temp" section of the block interface Label STRING[4] In the "Temp" section of the block interface The following table lists the declarations of the PLC data types: 2368 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Name of the PLC data types Name Data type Article Number DINT Declaration STRING Client Colli INT Title INT First name STRING[10] Surname STRING[10] The following table shows the declaration of the data blocks: Name of the data blocks Name Data type Target Client "Client" (PLC data type) Article Array[0..] of "Article" (PLC data type) Bill Array[0..10] of INT Field Array[0..294] of BYTE Buffer See also Overview of the valid data types (Page 1204) PLC data types (Page 1248) Serialize: Serialization Description You can use the "Serialize" instruction to convert several PLC data types (UDT) to a sequential representation without losing parts of their structure. You can use the instruction to temporarily save multiple structured data items from your program in a buffer, which should preferably be in a global data block, and send them to another CPU. The memory area in which the converted PLC data types are stored must have the ARRAY of BYTE data type and be declared with standard access. Make sure that there is enough memory space prior to the conversion. The operand at the POS parameter contains information about the number of bytes used by the converted PLC data types. Note If you want to send a single PLC data type (UDT), you can directly call the instruction "TSEND: Send data via communication connection". WinCC Basic V13.0 System Manual, 02/2014 2369 Programming the PLC 9.7 References Syntax The following syntax is used for the "Serialize" instruction: SCL Serialize(SRC_VARIABLE := <Operand>, DEST_ARRAY := <Operand>, POS := <Operand>) Parameter The following table shows the parameters of the "Serialize" instruction: Parameter Declaration Data type Description SRC_VARIA BLE Input VARIAN T PLC data type (UDT) that is converted to sequential representation. DEST_ARRA Y InOut VARIAN T Data block in which the generated data stream is stored. POS InOut DINT Number of bytes that the converted PLC data types use. The POS parameter is calculated zero-based. INT Error information Function value For additional information on valid data types, refer to "See also". RET_VAL parameter The following table shows the meaning of the values of the RET_VAL parameter: Error code* (W#16#...) Explanation 0000 No error 80B0 The memory areas for the SRC_VARIABLE and DEST_ARRAY parameters overlap. 8150 The VARIANT data type at the SRC_VARIABLE parameter contains no value. 8152 Code generation error at SRC_VARIABLE parameter 8236 The data block at the DEST_ARRAY parameter is not a block with standard access. 8250 The VARIANT data type at the DEST_ARRAY parameter contains no value. 8252 Code generation error at DEST_ARRAY parameter 8253 There is not enough free memory available at the DEST_ARRAY parameter. 8254 Invalid data type at the DEST_ARRAY parameter 8382 The value at the POS parameter is outside the limits of the array. *The error codes can be displayed as integer or hexadecimal value in the program editor. For information on toggling display formats, refer to "See also". 2370 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Example The following example shows how the instruction works: SCL #Tag_RetVal := Serialize(SRC_VARIABLE := "Source".Client, DEST_ARRAY := "Buffer".Field, POS := #BufferPos); #Label := STRING_TO_WSTRING('arti'); #Tag_RetVal := Serialize(SRC_VARIABLE := #Label, DEST_ARRAY := "Buffer".Field, POS := #BufferPos); #Tag_RetVal := Serialize(SRC_VARIABLE := "Source".Article[#DeliverPos], DEST_ARRAY := "Buffer".Field, POS := #BufferPos); The "Move value" instruction moves the value "0" to the "#BufferPos" operand. The "Serialize" instruction serializes the customer data from the "Source" data block and writes them in sequential representation to the "Buffer" data block. The number of bytes used by the sequential representation is stored in the "#BufferPos" operand. A kind of separator sheet is inserted now to make it easier to deserialize the sequential representation later. The "Move character string" instruction moves the "arti" characters to the "#Label" operand. The "Serialize" instruction writes these characters after the customer data to the "Buffer" data block. The number of bytes that the characters need is added to the number already stored in the "#BufferPos" operand. The "Serialize" instruction serializes the data of a specific article, which is calculated in runtime, from the "Source" data block and writes them in sequential representation to the "Buffer" data block after the "arti" characters. The following table shows the declaration of the operands: Operand Data type Declaration DeliverPos INT In the "Input" section of the block interface BufferPos DINT In the "Temp" section of the block interface Error INT In the "Temp" section of the block interface Label STRING[4] In the "Temp" section of the block interface The following table lists the declarations of the PLC data types: Name of the PLC data types Name Data type Article Number DINT Declaration STRING Colli INT Title INT Client WinCC Basic V13.0 System Manual, 02/2014 2371 Programming the PLC 9.7 References Name of the PLC data types Name Data type First name STRING[10] Surname STRING[10] The following table shows the declaration of the data blocks: Name of the data blocks Name Data type Source Client "Client" (PLC data type) Article Array[0..10] of "Article" (PLC data type) Field Array[0..294] of BYTE Buffer See also Overview of the valid data types (Page 1204) PLC data types (Page 1248) MOVE_BLK: Move block Description The instruction "Move block" copies the contents of a memory area (source area) to another memory area (destination area). The number of elements to be copied to the destination area is specified with the COUNT parameter. The width of the elements to be moved is defined by the width of the first element in the source area. The instruction can only be executed if the source area and the destination area are of the same data type. The value of the OUT output is invalid if the following condition is met: More data is moved than is made available at the IN parameter or OUT parameter. Syntax The following syntax is used for the instruction "Move block": SCL MOVE_BLK(IN := <Operand>, COUNT := <Operand>, OUT => <Operand>) 2372 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameter The following table shows the parameters of the "Move block" instruction: Parameter Declaration Data type S7-1200 S7-1500 Description Input Binary numbers, integers, floatingpoint numbers, TIME, DATE, CHAR, TOD Binary numbers, integers, floatingpoint numbers, timers, DATE, CHAR, TOD, LTOD The first element of the source area that is being copied COUNT Input USINT, UINT, UDINT USINT, UINT, UDINT, ULINT Number of elements to be copied from the source area to the destination area OUT 1) Output Binary numbers, integers, floatingpoint numbers, TIME, DATE, CHAR, TOD Binary numbers, integers, floatingpoint numbers, timers, DATE, CHAR, TOD, LTOD The first element of the destination area to which the contents of the source area are being copied IN 1) 1) The specified data types can only be used as elements of an ARRAY structure. For more information on valid data types, refer to "See also". Example The following example shows how the instruction works: SCL MOVE_BLK(IN := #a_array[2], COUNT := "Tag_Count", OUT => #b_array[1]); The following table shows how the instruction works using specific operand values: Parameter Operand Value IN a_array[2] The data type of the a_array operand is Array [0..5] of INT. It consists of six elements of data type INT. COUNT Tag_Count 3 OUT b_array[1] The data type of the b_array operand is Array [0..6] of INT. It consists of seven elements of data type INT. Starting from the third element, the instruction selects three INT elements from the #a_array tag and copies their contents to the #b_array output tag, beginning with the second element. WinCC Basic V13.0 System Manual, 02/2014 2373 Programming the PLC 9.7 References See also Overview of the valid data types (Page 1204) MOVE_BLK_VARIANT: Move block Description The instruction "Move block" copies the contents of a memory area (source area) to another memory area (destination area). You can copy elements of an array to another array of the same data type. The size (number of elements) of the source and destination array may be different. You can copy several elements within an array or individual elements. If you are using the instruction, the array must not yet be known at the time the block is created, as the source and the destination are transferred using VARIANT. The counting at the parameters SRC_INDEX and DEST_INDEX always starts with the low limit "0", regardless of the later declaration of the array. The instruction is not executed if more data is copied than is made available. If the VARIANT pointer (source or destination) is of the data type BOOL, it must be addressed absolutely and the length specified must be divisible by 8; otherwise the instruction is not executed. Syntax The following syntax is used for the "Move block" instruction: SCL MOVE_BLK_VARIANT(SRC := <Operand>, COUNT := <Operand>, SRC_INDEX := <Operand>, DEST_INDEX := <Operand>, DEST => <Operand>) Parameter The following table shows the parameters of the "Move block" instruction: Parameter Declaration Data type Description SRC Input VARIANT (array or single element) Source block from which to copy COUNT Input UDINT Number of elements which are copied Set the value at the parameter COUNT to "1", if no Array is specified at the parameter SRC or the parameter DEST. 2374 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameter Declaration Data type Description SRC_INDEX Input DINT The SRC_INDEX parameter is calculated zero-based. If an Array is specified at parameter SRC, the integer at the SRC_INDEX parameter specifies the first element within the source area from which copying is to take place. This is independent of the declared array limits. If no Array is set at the SRC parameter or only an individual element of an array is specified, assign the SRC_INDEX parameter the value "0". DEST_INDEX Input DINT The DEST_INDEX parameter is calculated zero-based. If an Array is specified at the DEST parameter, the integer at the DEST_INDEX parameter specifies the first element within the destination area to which copying is to take place. This is independent of the declared array limits. If no Array is specified at the DEST parameter, assign the DEST_INDEX parameter the value "0". DEST Output Function value (RET_VAL) VARIANT Destination area into which the contents of the source block are copied. INT Error information For additional information on valid data types, refer to "See also". RET_VAL parameter The following table shows the meaning of the values of the RET_VAL parameter: Error code* Explanation (W#16#...) WinCC Basic V13.0 System Manual, 02/2014 0000 No error 80B4 Data types do not correspond 8151 Access to the SRC parameter is not possible. 8152 The operand at the SRC parameter is not typed. 2375 Programming the PLC 9.7 References Error code* Explanation (W#16#...) 8153 Code generation error at SRC parameter 8154 The operand at the SRC parameter has the data type BOOL. 8281 The COUNT parameter has an invalid value 8382 The value at the SRC_INDEX parameter is outside the limits of the VARIANT. 8383 The value of the SRC_INDEX parameter is outside the high limit of the array. 8482 The value at the DEST_INDEX parameter is outside the limits of the VARIANT. 8483 The value of the DEST_INDEX parameter is outside the high limit of the array. 8534 The DEST parameter is write protected 8551 Access to the DEST parameter is not possible. 8552 The operand at the DEST parameter is not typed. 8553 Code generation error at DEST parameter 8554 The operand at the DEST parameter has the data type BOOL. *The error codes can be displayed as integer or hexadecimal value in the program editor. For information on toggling display formats, refer to "See also". Example The following example shows how the instruction works: SCL "Tag_Result" := MOVE_BLK_VARIANT(SRC := #SrcField, COUNT := "Tag_Count", SRC_INDEX := "Tag_Src_Index", DEST_INDEX := "Tag_Dest_Index", DEST => #DestField); The following table shows how the instruction works using specific operand values: 2376 Parameter Operand Value SRC #SrcField The local operand #SrcField uses a UDT that was still unknown at the time when the block was programmed. (Array [0 to 10] of "MOVE_UDT" COUNT Tag_Count 2 SRC_INDEX Tag_Src_Index 3 DEST_INDEX Tag_Dest_Index 3 DEST #DestField The local operand #DestField uses a UDT that was still unknown at the time when the block was programmed. (Array [10 to 20] of "MOVE_UDT" WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References 2 elements are copied from the source area into the destination area beginning with the fourth element of the array of UDT. The copies are inserted in the array of UDT beginning with the fourth element. See also Overview of the valid data types (Page 1204) VariantGet: Read out VARIANT tag value (Page 2409) UMOVE_BLK: Move block uninterruptible Description The instruction "Move block uninterruptible" copies the contents of a memory area (source area) to another memory area (destination area) without interruption. The number of elements to be copied to the destination area is specified with the COUNT parameter. The width of the elements to be moved is defined by the width of the first element in the source area. The instruction can only be executed if the source area and the destination area have the same data type. Note The copy operation cannot be interrupted by other operating system activities. This is why the alarm reaction times of the CPU increase during the execution of the instruction "Move block uninterruptible". The value of the OUT output is invalid if the following condition is met: More data is moved than is made available at the IN parameter or OUT parameter. You can use the "Move block uninterruptible" instruction to move a maximum of 16 KB. Note the CPU-specific restrictions for this. Syntax The following syntax is used for the instruction "Move block uninterruptible": SCL UMOVE_BLK(IN := <Operand>, COUNT := <Operand>, OUT => <Operand>) WinCC Basic V13.0 System Manual, 02/2014 2377 Programming the PLC 9.7 References Parameter The following table shows the parameters of the "Move block uninterruptible" instruction: Parameter Declaration Data type Description S7-1200 S7-1500 IN 1) Input Binary numbers, integers, floatingpoint numbers, TIME, DATE, CHAR, TOD Binary numbers, integers, floatingpoint numbers, timers, DATE, CHAR, TOD, LTOD The first element of the source area that is being copied COUNT Input USINT, UINT, UDINT USINT, UINT, UDINT, ULINT Number of elements to be copied from the source area to the destination area OUT 1) Output Binary numbers, integers, floatingpoint numbers, TIME, DATE, CHAR, TOD Binary numbers, integers, floatingpoint numbers, timers, DATE, CHAR, TOD, LTOD The first element of the destination area to which the contents of the source area are being copied 1) The specified data types can only be used as elements of an ARRAY structure. For additional information on valid data types, refer to "See also". Example The following example shows how the instruction works: SCL UMOVE_BLK(IN := #a_array[2], COUNT := "Tag_Count", OUT => #b_array[1]); The following table shows how the instruction works using specific operand values: Parameter Operand Value IN a_array[2] The data type of the a_array operand is Array [0..5] of INT. It consists of six elements of data type INT. COUNT Tag_Count 3 OUT b_array[1] The data type of the b_array operand is Array [0..6] of INT. It consists of seven elements of data type INT. Starting from the third element, the instruction selects three INT elements from the #a_array tag and copies their contents to the #b_array output tag, beginning with the second element. The copy operation cannot be interrupted by other operating system activities. 2378 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References See also Overview of the valid data types (Page 1204) FILL_BLK: Fill block Description The "Fill block" instruction is used to copy the content of a memory area (source area) to a selected memory area (target area). The number of repeated copy operations is specified with the COUNT parameter. When the instruction is executed, the source area is selected and moved to the destination area as often as specified by the value of the COUNT parameter. The instruction can only be executed if the source area and the destination area are of the same data type. The value of the OUT output is invalid if the following condition is met: More data is moved than is made available at input IN or output OUT. Syntax The following syntax is used for the instruction "Fill block": SCL FILL_BLK(IN := <Operand>, COUNT := <Operand>, OUT => <Operand>) Parameter The following table shows the parameters of the "Fill block" instruction: Parameter WinCC Basic V13.0 System Manual, 02/2014 Declaration Data type S7-1200 S7-1500 Description IN 1) Input Binary numbers, integers, floatingpoint numbers, TIME, TOD, DATE, CHAR Binary numbers, integers, floatingpoint numbers, timers, DATE, CHAR, TOD, LTOD Element used to fill the destination area COUNT Input USINT, UINT, UDINT USINT, UINT, UDINT, ULINT Number of repeated copy operations 2379 Programming the PLC 9.7 References Parameter OUT 2) Declaration Data type Output Description S7-1200 S7-1500 Binary numbers, integers, floatingpoint numbers, TIME, TOD, DATE, CHAR Binary numbers, integers, floatingpoint numbers, timers, DATE, CHAR, TOD, LTOD Address in destination area from which filling starts 1) The specified data types can also be used as elements of an ARRAY structure. 2) The specified data types can only be used as elements of an ARRAY structure. For more information on valid data types, refer to "See also". Example The following example shows how the instruction works: SCL FILL_BLK(IN := #a_array[2], COUNT := "Tag_Count", OUT => #b_array[1]); The following table shows how the instruction works using specific operand values: Parameter Operand Value IN a_array[2] The data type of the a_array operand is Array [0..5] of INT. It consists of six elements of data type INT. COUNT Tag_Count 3 OUT b_array[1] The data type of the b_array operand is Array [0..6] of INT. It consists of seven elements of data type INT. The instruction copies the third element (#a_array[2]) of the #a_array tag three times to the #b_array output tag. See also Overview of the valid data types (Page 1204) UFILL_BLK: Fill block uninterruptible Description The instruction "Fill block uninterruptible" is used to copy the content of a memory area (source area) to a selected memory area (target area). The number of repeated copy operations is specified with the COUNT parameter. When the instruction is executed, the value at the IN 2380 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References input is selected and copied to the destination area as often as specified by the value in the COUNT parameter. The instruction can only be executed if the source area and the destination area have the same data type. Note The copy operation cannot be interrupted by other operating system activities. This is why the alarm reaction times of the CPU increase during the execution of the "Fill block uninterruptible" instruction. The value of the OUT output is invalid if the following condition is met: More data is moved than is made available at input IN or output OUT. You can use the "Fill block uninterruptible" instruction to move a maximum of 16 KB. Note the CPU-specific restrictions for this. Syntax The following syntax is used for the "Fill block uninterruptible" instruction: SCL UFILL_BLK(IN := <Operand>, COUNT := <Operand>, OUT => <Operand>) Parameter The following table shows the parameters of the "Fill block uninterruptible" instruction: WinCC Basic V13.0 System Manual, 02/2014 Parameter Declaration Data type S7-1200 S7-1500 IN 1) Input Binary numbers, integers, floatingpoint numbers, TIME, DATE, CHAR, TOD Binary numbers, integers, floatingpoint numbers, timers, DATE, CHAR, TOD, LTOD Element used to fill the destination area COUNT Input USINT, UINT, UDINT USINT, UINT, UDINT, ULINT Number of repeated copy operations OUT 2) Output Binary numbers, integers, floatingpoint numbers, TIME, TOD, DATE, CHAR Binary numbers, integers, floatingpoint numbers, timers, DATE, CHAR, TOD, LTOD Address in destination area from which filling starts 1) The specified data types can also be used as elements of an ARRAY structure. 2) The specified data types can only be used as elements of an ARRAY structure. Description 2381 Programming the PLC 9.7 References For additional information on valid data types, refer to "See also". Example The following example shows how the instruction works: SCL UFILL_BLK(IN := #a_array[2], COUNT := "Tag_Count", OUT => #b_array[1]); The following table shows how the instruction works using specific operand values: Parameter Operand Value IN a_array[2] The data type of the a_array operand is Array [0..5] of INT. It consists of six elements of data type INT. COUNT Tag_Count 3 OUT b_array[1] The data type of the b_array operand is Array [0..6] of INT. It consists of seven elements of data type INT. The instruction copies the third element (#a_array[2]) of the #a_array tag three times to the #b_array output tag. The copy operation cannot be interrupted by other operating system activities. See also Overview of the valid data types (Page 1204) SWAP: Swap Description You can use the "Swap" instruction to change the arrangement of the bytes of an input value and save the result in the specified operand. The following figure shows how the bytes of an operand of the DWORD data type are swapped using the "Swap" instruction: 2382 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References ,QSXWYDOXH 5HVXOW Syntax The following syntax is used for the "Swap" instruction: SCL SWAP(<Expression>) The syntax of the instruction consists of the following parts: Parameter <Expression> Declaration Input Function value Data type Description S7-1200 S7-1500 WORD, DWORD WORD, DWORD, LWORD Input value WORD, DWORD WORD, DWORD, LWORD Result of the instruction For additional information on valid data types, refer to "See also". Example The following example shows how the instruction works: SCL "Tag_Result" := SWAP("Tag_Value"); The result of the instruction is returned as a function value. The following table shows how the instruction works using specific operand values: WinCC Basic V13.0 System Manual, 02/2014 2383 Programming the PLC 9.7 References Operand Value Tag_Value 0000 1111 0101 0101 Tag_Result 0101 0101 0000 1111 See also Overview of the valid data types (Page 1204) ARRAY DB instructions ReadFromArrayDB: Read from array data block Description You can use the "Read from array data block" instruction to read data from an array DB and write them to a destination area. An array DB is a data block which consists of exactly one array of [data type]. The elements of the array can be UDT data type or any other elementary data type. The counting of the array always starts with the low limit "0", regardless of the later declaration of the array. Syntax The following syntax is used for the "Read from array data block" instruction: SCL ReadFromArrayDB(DB := <Operand>, INDEX := <Operand>, VALUE => <Operand>) Parameter The following table shows the parameters of the "Read from array data block" instruction: Parameter Declaration Data type Description DB Input DB_ANY Data block that is read INDEX Input DINT Element that is read VALUE Output VARIANT Value that is read and output INT Result of the instruction Function value (RET_VAL) For additional information on valid data types, refer to "See also". 2384 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameters RET_VAL The following table shows the meaning of the values of the RET_VAL parameter: Error code* Explanation (W#16#...) 0000 No error 80B4 Data types do not correspond 80B5 Copying process was interrupted 8132 The data block does not exist or is too short 8133 The data block is located in the load memory 8134 The data block is write protected 8135 The array DB contains invalid values 8154 The data type is not correctly declared 8282 The value at the INDEX parameter is outside the limit values of the array. 8350 The VARIANT data type contains no value 8352 Code generation error 8353 Code generation error *The error codes can be displayed as integer or hexadecimal value in the program editor. For information on toggling display formats, refer to "See also". Example The following example shows how the instruction works: SCL "TagResult" := ReadFromArrayDB(DB := "ArrayDB", INDEX := "ArrayDB"."THIS"[2], VALUE => "TargetField[10]".Data2[1]); The following table shows how the instruction works using specific operand values: Parameter Operand Value DB ArrayDB The data type of the "ArrayDB" operand is Array [0 to 10] of INT. INDEX ArrayDB."THIS"[2] Third element of the "ArrayDB" VALUE TargetField[10].Data2[1] The data type of the "TargetField" operand is Array [10 to 20] of "MOVE_UDT". The third element is read from "ArrayDB" and written to the "TargetField[10].Data2[1]" operand. See also Overview of the valid data types (Page 1204) WinCC Basic V13.0 System Manual, 02/2014 2385 Programming the PLC 9.7 References WriteToArrayDB: Write to array data block Description You can use the "Write to array data block" instruction to write data to an array DB. An array DB is a data block which consists of exactly one array of [data type]. The elements of the array can be UDT data type or any other elementary data type. The counting of the array always starts with the low limit "0", regardless of the later declaration of the array. Syntax The following syntax is used for the "Write to the ARRAY data block" instruction: SCL WriteToArrayDB(DB := <Operand>, INDEX := <Operand>, VALUE := <Operand>) Parameter The following table shows the parameters of the "Write to array data block" instruction: Parameter Declaration Data type Description DB Input DB_ANY Data block to which data is written INDEX Input DINT Element in the DB to which data is written VALUE Input VARIANT Value to be written INT Result of the instruction Function value (RET_VAL) For additional information on valid data types, refer to "See also". Parameters RET_VAL The following table shows the meaning of the values of the RET_VAL parameter: Error code* Explanation (W#16#...) 2386 0000 No error 80B4 Data types do not correspond 80B5 Copying process was interrupted 8132 The data block does not exist or is too short 8133 The data block is located in the load memory 8134 The data block is write protected 8135 The DB is not an array data block. WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Error code* Explanation (W#16#...) 8282 The value at the INDEX parameter is outside the limit values of the array. 8350 The VARIANT data type contains no value 8352 Code generation error 8353 Code generation error *The error codes can be displayed as integer or hexadecimal value in the program editor. For information on toggling display formats, refer to "See also". Example The following example shows how the instruction works: SCL "TagResult" := WriteToArrayDB(DB := "ArrayDB", INDEX := "ArrayDB"."THIS"[2], VALUE := "SourceField[1]".Data1[6]); The following table shows how the instruction works using specific operand values: Parameter Operand Value DB ArrayDB The data type of the "ArrayDB" operand is Array [0 to 10] of INT. INDEX ArrayDB."THIS"[2] Third element of the "ArrayDB" VALUE SourceField[1].Data1[6] The data type of the "SourceField" operand is Array [0 to 10] of "MOVE_UDT". From the "SourceField" operand, the "Data1[6]" element from the second element is written to the "ArrayDB". The third element is written to the "ArrayDB". See also Overview of the valid data types (Page 1204) ReadFromArrayDBL: Read from array data block in load memory Description You can use the "Read from array data block in load memory" instruction to read data from an array DB in load memory. An array DB is a data block which consists of exactly one array of [data type]. The elements of the array can be UDT data type or any other elementary data type. The counting of the array always starts with the low limit "0", regardless of the later declaration of the array. WinCC Basic V13.0 System Manual, 02/2014 2387 Programming the PLC 9.7 References If the array DB is marked with the "Only store in load memory" block attribute, it is only stored in load memory. The instruction is executed when a positive signal edge is detected at the REQ parameter. The BUSY parameter then has the signal state "1". The instruction is terminated if a negative signal edge is detected at the BUSY parameter. The DONE parameter has the signal state "1" for one program cycle and the read value is output at the VALUE parameter within this cycle. With all other program cycles, the value at the VALUE parameter is not changed. When you insert the instruction in the program, the "Call options" dialog opens in which you can specify whether the block parameters will be stored in a separate data block (single instance) or as a local tag (multiple instance) in the block interface. If you create a separate data block, you will find it in the project tree in the "Program resources" folder under "Program blocks > System blocks". For additional information on this topic, refer to "See also". Note The array DB must be located in a data block with the block property "Optimized". Syntax The following syntax is used for the "Read from array data block in load memory" instruction: SCL "Instance DB"(REQ := <Operand>, DB := <Operand>, INDEX := <Operand>, BUSY => <Operand>, DONE => <Operand>, ERROR => <Operand>, VALUE := <Operand>) Parameter The following table shows the parameters of the "Read from array data block in load memory" instruction: 2388 Parameter Declaration Data type Description REQ Input BOOL REQ = "1": Starting with the reading of the array DB DB Input DB_ANY Data block that is read INDEX Input DINT Element that is read BUSY Output BOOL BUSY = "1": The array DB is still being read DONE Output BOOL DONE = "1": The instruction was executed successfully WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameter Declaration Data type Description VALUE InOut VARIANT Value that is read and output ERROR Output INT Error information: If an error occurs during the execution of the instruction, an error code is output on the ERROR parameter. For additional information on valid data types, refer to "See also". ERROR parameter The following table shows the meaning of the values of the ERROR parameter: Error code* Explanation (W#16#...) 0000 No error 80B4 Data types do not correspond 80B5 Copying process was interrupted 80C3 Too many concurrent calls 8132 The data block does not exist or is too short 8133 The data block is not located in the load memory 8134 The data block is write protected 8135 The DB is not an array data block. 8282 The value of the INDEX parameter is outside the limits of the array. 8350 The VARIANT data type contains no value 8352 Code generation error 8353 Code generation error *The error codes can be displayed as integer or hexadecimal value in the program editor. For information on toggling display formats, refer to "See also". You can find descriptions of the error codes triggered by the instructions "READ_DBL: Read from data block in load memory" and "WRIT_DBL: Write to data block in load memory" under "See also". Example The following example shows how the instruction works: SCL "ReadFromArrayDBL_DB"(REQ := "TagReg", DB := "ArrayDB", INDEX := "ArrayDB"."THIS"[2], BUSY => "TagBusy", WinCC Basic V13.0 System Manual, 02/2014 2389 Programming the PLC 9.7 References SCL DONE => "TagDone", ERROR => "TagError", VALUE := "SourceTargetField[1]".Data1[6]); The following table shows how the instruction works using specific operand values: Parameter Operand Value REQ TagReq BOOL DB ArrayDB The data type of the "ArrayDB" operand is Array [0 to 10] of INT. INDEX ArrayDB."THIS"[2] Third element of the "ArrayDB" VALUE SourceTargetField[1].Data1[6] The data type of the "SourceTargetField" operand is Array [0 to 10] of "MOVE_UDT". BUSY TagBusy BOOL DONE TagDone BOOL If a positive edge is detected at the "TagReq" operand, the "Read from array data block in load memory" instruction is executed. The third element is read from "ArrayDB" and written to the "SourceTargetField[1].Data1[6]" operand. As soon as a negative signal edge is detected at the "TagBusy" operand, the instruction is terminated and the value at the VALUE parameter is no longer changed. After the instruction has been processed, the "TagDone" operand the signal state "1". See also Overview of the valid data types (Page 1204) READ_DBL: Read from data block in the load memory (Page 2798) WRIT_DBL: Write to data block in the load memory (Page 2800) WriteToArrayDBL: Write to array data block in load memory Description You can use the "Write to the array data block in load memory" instruction to write data to an array DB in load memory. An array DB is a data block which consists of exactly one array of [data type]. The elements of the array can be UDT data type or any other elementary data type. The counting of the array always starts with the low limit "0", regardless of the later declaration of the array. If the array DB is marked with the "Only store in load memory" block attribute, it is only stored in load memory. The instruction is executed when a positive signal edge is detected at the REQ parameter. The BUSY parameter then has the signal state "1". If a negative signal edge is detected at the BUSY parameter, the instruction is terminated and the value at the VALUE parameter is written to the data block. The DONE parameter then has the signal state "1" for one program cycle. 2390 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References When you insert the instruction in the program, the "Call options" dialog opens in which you can specify whether the block parameters will be stored in a separate data block (single instance) or as a local tag (multiple instance) in the block interface. If you create a separate data block, you will find it in the project tree in the "Program resources" folder under "Program blocks > System blocks". For additional information on this topic, refer to "See also". Note The array DB must be located in a data block with the block property "Optimized". Syntax The following syntax is used for the "Write to ARRAY data block in load memory" instruction: SCL "Instance DB"(REQ := <Operand>, DB := <Operand>, INDEX := <Operand>, VALUE := <Operand>, BUSY => <Operand>, DONE => <Operand>, ERROR => <Operand>) Parameter The following table shows the parameters of the "Write to the array data block in load memory" instruction: Parameter Declaration Data type Description REQ Input BOOL REQ = "1": Start writing to the array DB DB Input DB_ANY Data block to which data is written INDEX Input DINT Element in the DB to which data is written VALUE Input VARIANT Value to be written BUSY Output BOOL BUSY = "1": The array DB is still being written DONE Output BOOL DONE = "1": The instruction was executed successfully ERROR Output INT Error information: If an error occurs during the execution of the instruction, an error code is output on the ERROR parameter. WinCC Basic V13.0 System Manual, 02/2014 2391 Programming the PLC 9.7 References For additional information on valid data types, refer to "See also". ERROR parameter The following table shows the meaning of the values of the ERROR parameter: Error code* Explanation (W#16#...) 0000 No error 80B4 Data types do not correspond 80B5 Copying process was interrupted 80C3 Too many concurrent calls 8132 The data block does not exist or is too short 8133 The data block is not located in the load memory 8134 The data block is write protected 8135 The DB is not an array data block. 8282 The value of the INDEX parameter is outside the limits of the array. 8350 The VARIANT data type contains no value 8352 Code generation error 8353 Code generation error *The error codes can be displayed as integer or hexadecimal value in the program editor. For information on toggling display formats, refer to "See also". You can find descriptions of the error codes triggered by the instructions "READ_DBL: Read from data block in load memory" and "WRIT_DBL: Write to data block in load memory" under "See also". Example The following example shows how the instruction works: SCL "WriteToArrayDBL_DB"(REQ := "TagReg", DB := "ArrayDB", INDEX := "ArrayDB"."THIS"[2], VALUE := "SourceTargetField[1]".Data1[6], BUSY => "TagBusy", DONE => "TagDone", ERROR => "TagError"); The following table shows how the instruction works using specific operand values: 2392 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameter Operand Value REQ TagReq BOOL DB ArrayDB The data type of the "ArrayDB" operand is Array [0 to 10] of INT. INDEX ArrayDB."THIS"[2] Third element of the "ArrayDB" VALUE SourceTargetField[1].Data1[6] The data type of the "SourceTargetField" operand is Array [0 to 10] of "MOVE_UDT". BUSY TagBusy BOOL DONE TagDone BOOL If a positive edge is detected at the "TagReq" operand, the "Write to ARRAY data block in load memory" instruction is executed. As soon as a negative signal edge is detected at the "TagBusy" operand, the instruction is terminated and the value at the VALUE parameter is written in the third element in the "ArrayDB". After the instruction has been processed, the "TagDone" operand the signal state "1". See also Overview of the valid data types (Page 1204) READ_DBL: Read from data block in the load memory (Page 2798) WRIT_DBL: Write to data block in the load memory (Page 2800) Read/write access PEEK: Read memory address Description The "Read memory address" instruction is used to read a memory address from a memory area without specifying a data type. If you specify the 16#84 area at the AREA parameter for a data block, you can only access data blocks with the "Standard" block property. Syntax The following syntax is used for the "Read memory address" instruction: SCL PEEK(AREA:= <Operand>, DBNUMBER := <Operand>, BYTEOFFSET:= <Operand>) WinCC Basic V13.0 System Manual, 02/2014 2393 Programming the PLC 9.7 References SCL PEEK_<Data type>(AREA := <Operand>, DBNUMBER := <Operand>, BYTEOFFSET:= <Operand>) The syntax of the instruction consists of the following parts: Parameter Declaration Data type Description AREA Input BYTE The following areas can be selected: 16#81: Input 16#82: Output 16#83: Bit memory 16#84: DB 16#1: Peripheral input (S7-1500 only) DBNUMBER Input DINT, DB_ANY Number of the data block if AREA = DB, otherwise "0" BYTEOFFSET Input DINT Address to read from Only the 16 least significant bits are used. _<Data type> Bit strings default: BYTE Data type of the function value: You do not need to specify the data type if using the default. Any other valid data type you may use must be declared explicitly. Function value Bit strings Result of the instruction For additional information on valid data types, refer to "See also". Note If you read the memory address of the input, output or bit memory areas, you will need to set the "DBNUMBER" parameter with the value "0", as the instruction is faulty otherwise. Example The following example shows how the instruction works: SCL "Tag_Result1" := PEEK(AREA := "Tag_Area", DBNUMBER := "Tag_DBNumber", 2394 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References SCL BYTEOFFSET := "Tag_Byte"); SCL "Tag_Result2" := PEEK_WORD(AREA := "Tag_Area", DBNUMBER := "Tag_DBNumber", BYTEOFFSET := "Tag_Byte"); The following table shows how the instruction works using specific operand values: Parameter Operand Value AREA Tag_Area 16#84 DBNUMBER Tag_DBNumber 5 BYTEOFFSET Tag_Byte 20 Function value Tag_Result1 Byte value "20" Function value Tag_Result2 Word value "20" The instruction reads the value of address "20" from the "Tag_Byte" operand at data block "5" and returns the result as a function value at the "Tag_Result" operand. See also Overview of the valid data types (Page 1204) PEEK_BOOL: Read memory bit Description The "Read memory bit" instruction is used to read a memory bit from a memory area without specifying a data type. If you specify the 16#84 area at the AREA parameter for a data block, you can only access data blocks with the "Standard" block property. Note The instruction can only be used to access "Standard" memory areas. Syntax The following syntax is used for the "Read memory bit" instruction: SCL PEEK_BOOL(AREA := <Operand>, DBNumber := <Operand>, WinCC Basic V13.0 System Manual, 02/2014 2395 Programming the PLC 9.7 References SCL BYTEEOFFSET := <Operand>, BITOFFSET := <Operand>) The syntax of the instruction consists of the following parts: Parameter Declaration Data type Description AREA Input BYTE The following areas can be selected: 16#81: Input 16#82: Output 16#83: Bit memory 16#84: DB 16#1: Peripheral input (S7-1500 only) DBNUMBER Input DINT, DB_ANY Number of the data block if AREA = DB, otherwise "0" BYTEOFFSET Input DINT Address to read from Only the 16 least significant bits are used. BITOFFSET Input Function value INT Bit to be read from BOOL Result of the instruction For additional information on valid data types, refer to "See also". Note If you read the memory bit from the input, output or bit memory areas, you will need to set the "DBNUMBER" parameter with the value "0", as the instruction is faulty otherwise. Example The following example shows how the instruction works: SCL "Tag_Result" := PEEK_BOOL(AREA := "Tag_Area", DBNUMBER := "Tag_DBNumber", BYTEOFFSET := "Tag_Byte", BITOFFSET := "Tag_Bit"); The following table shows how the instruction works using specific operand values: 2396 Parameter Operand Value AREA Tag_Area 16#84 DBNUMBER Tag_DBNumber 5 BYTEOFFSET Tag_Byte 20 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameter Operand Value BITOFFSET Tag_Bit 3 Function value Tag_Result 3 The instruction reads the value of memory bit "3" from the "Tag_Bit" operand at byte "20" of data block "5" and returns the result at the "Tag_Result" operand as function value. See also Overview of the valid data types (Page 1204) POKE: Write memory address Description The "Write memory address" instruction is used to write a memory address to a memory area without specifying a data type. If you specify the 16#84 area at the AREA parameter for a data block, you can only access data blocks with the "Standard" block property. Note The instruction can only be used to access "Standard" memory areas. Syntax The following syntax is used for the "Write memory address" instruction: SCL POKE(AREA := <Operand>, DBNUMBER := <Operand>, BYTEOFFSET := <Operand>, VALUE := <Operand>) The syntax of the instruction consists of the following parts: WinCC Basic V13.0 System Manual, 02/2014 2397 Programming the PLC 9.7 References Parameter Declaration Data type Description AREA Input BYTE The following areas can be selected: 16#81: Input 16#82: Output 16#83: Bit memory 16#84: DB 16#2: Peripheral output (S7-1500 only) DBNUMBER Input DINT, DB_ANY Number of the data block if AREA = DB, otherwise "0" BYTEOFFSET Input DINT Address to be written Only the 16 least significant bits are used. VALUE Input Bit strings Value to be written For additional information on valid data types, refer to "See also". Note If you write the memory address in the input, output or bit memory areas, you will need to set the "DBNUMBER" parameter with the value "0", as the instruction is faulty otherwise. Example The following example shows how the instruction works: SCL POKE(AREA := "Tag_Area", DBNUMBER := "Tag_DBNumber", BYTEOFFSET := "Tag_Byte"), VALUE := "Tag_Value"; The following table shows how the instruction works using specific operand values: Parameter Operand Value AREA Tag_Area 16#84 DBNUMBER Tag_DBNumber 5 BYTEOFFSET Tag_Byte 20 VALUE Tag_Value 16#11 The instruction overwrites the memory address "20" in the data block "5" with value "16#11". See also Overview of the valid data types (Page 1204) 2398 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References POKE_BOOL: Write memory bit Description The "Write memory bit" instruction is used to write a memory bit to a memory area without specifying a data type. If you specify the 16#84 area at the AREA parameter for a data block, you can only access data blocks with the "Standard" block property. Note The instruction can only be used to access "Standard" memory areas. Syntax The following syntax is used for the "Write memory bit" instruction: SCL POKE_BOOL(AREA := <Operand>, DBNUMBER := <Operand>, BYTEOFFSET := <Operand>, BITOFFSET := <Operand>, VALUE := <Operand>) The syntax of the instruction consists of the following parts: Parameter Declaration Data type Description AREA Input BYTE The following areas can be selected: 16#81: Input 16#82: Output 16#83: Bit memory 16#84: DB 16#2: Peripheral output (S7-1500 only) DBNUMBER Input DINT, DB_ANY Number of the data block if AREA = DB, otherwise "0" BYTEOFFSET Input DINT Address to be written Only the 16 least significant bits are used. WinCC Basic V13.0 System Manual, 02/2014 BITOFFSET Input INT Bit to be written VALUE Input BOOL Value to be written 2399 Programming the PLC 9.7 References For additional information on valid data types, refer to "See also". Note If you write the memory bit in the input, output or bit memory areas, you need to set the "DBNUMBER" parameter with the value "0", as the instruction is faulty otherwise. Example The following example shows how the instruction works: SCL POKE_BOOL(AREA := "Tag_Area", DBNUMBER := "Tag_DBNumber", BYTEOFFSET := "Tag_Byte", BITOFFSET := "Tag_Bit", VALUE := "Tag_Value"); The following table shows how the instruction works using specific operand values: Parameter Operand Value AREA Tag_Area 16#84 DBNUMBER Tag_DBNumber 5 BYTEOFFSET Tag_Byte 20 BITOFFSET Tag_Bit 3 VALUE Tag_Value M0.0 The instruction overwrites the memory bit "3" in data block "5" in byte "20" with the value "M0.0". See also Overview of the valid data types (Page 1204) POKE_BLK: Write memory area Description The "Write memory area" instruction copies the content a memory area to a different memory area without specifying a data type. If you specify the 16#84 area at the AREA parameter for a data block, you can only access data blocks with the "Standard" block property. Note The instruction can only be used to access "Standard" memory areas. 2400 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Syntax The following syntax is used for the "Write memory area" instruction: SCL POKE_BLK(AREA_SRC:= <Operand>, DBNUMBER_SRC:= <Operand>, BYTEOFFSET_SRC:= <Operand>, AREA_DEST:= <Operand>, DBNUMBER_DEST:= <Operand>, BYTEOFFSET_DEST:= <Operand>, COUNT:= <Operand>) The syntax of the instruction consists of the following parts: Parameter Declaration Data type Description AREA_SRC Input BYTE The following areas can be selected in the source memory area: 16#81: Input 16#82: Output 16#83: Bit memory 16#84: DB DBNUMBER_SRC Input DINT, DB_ANY Number of the data block in the source memory area, if AREA = DB, otherwise "0" BYTEOFFSET_SRC Input DINT Address in the source memory area to be written Only the 16 least significant bits are used. AREA_DEST Input BYTE The following areas can be selected in the destination memory area: 16#81: Input 16#82: Output 16#83: Bit memory 16#84: DB DBNUMBER_DEST Input DINT, DB_ANY Number of the data block in the destination memory area, if AREA = DB, otherwise "0" BYTEOFFSET_DEST Input DINT Address in the destination memory area to be written Only the 16 least significant bits are used. COUNT WinCC Basic V13.0 System Manual, 02/2014 Input DINT Number of bytes which are copied 2401 Programming the PLC 9.7 References For additional information on valid data types, refer to "See also". Note If you write the memory address in the input, output or bit memory areas, you will need to set the "DBNUMBER" parameter with the value "0", as the instruction is faulty otherwise. Example The following example shows how the instruction works: SCL POKE_BLK(AREA_SRC := "Tag_Source_Area", DBNUMBER_SRC := "Tag_Source_DBNumber", BYTEOFFSET_SRC := "Tag_Source_Byte"), AREA_DEST := "Tag_Destination_Area", DBNUMBER_DEST := "Tag_Destination_DBNumber", BYTEOFFSET_DEST := "Tag_Destination_Byte", COUNT := "Tag_Count"); The following table shows how the instruction works using specific operand values: Parameter Operand Value AREA_SRC Tag_Source_Area 16#84 DBNUMBER_SRC Tag_Source_DBNumber 5 BYTEOFFSET_SRC Tag_Source_Byte 20 AREA_DEST Tag_Destination_Area 16#83 DBNUMBER_DEST Tag_Destination_DBNumber 0 BYTEOFFSET_DEST Tag_Destination_Byte 30 COUNT Tag_Count 100 The instruction writes 100 byte from data block "5" starting with address "20" in the memory area of the bit memory starting at address "30". See also Overview of the valid data types (Page 1204) READ_LITTLE: Read data in little endian format Description You use the "Read data in little endian format" instruction to read the data to a single tag in the little endian byte sequence. With the little endian format, the byte with the least significant bits is saved first, which means at the lowest memory address. The memory area that is read from must have the data type ARRAY of BYTE. 2402 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References The operand at the DEST_VARIABLE parameter must have an elementary data type. The operand at the POS parameter determines the position at which the reading starts. Note Reading tag of data type VARIANT or BOOL If you want to read a tag to which a VARIANT points, use the "Serialize" or "Deserialize" instructions. If you want to read a tag of the data type BOOL, use a "Slice access". Syntax Use the following syntax for the "Read data in little endian format" instruction: SCL READ_LITTLE(SRC_ARRAY := <Operand>, DEST_VARIABLE => <Operand>, POS := <Operand>) Parameter The following table shows the parameters of the "Read data in little endian format" instruction: Parameter Declaration Data type Description SRC_ARRAY Input ARRAY of BYTE Memory area from which is read DEST_VARIABLE Output Bit strings, integers, floatingpoint numbers, timers, LDT, TOD, LTOD, DATE, CHAR, WCHAR Read value POS InOut DINT Determines the position at which the reading starts. The POS parameter is calculated zero-based. INT Error information Function value Example The following example shows how the instruction works: SCL #TagResult := READ_LITTLE(SRC_ARRAY := #SourceField, DEST_VARIABLE => #DINTVariable, POS := #TagPos); The following table shows how the instruction works using specific operand values: WinCC Basic V13.0 System Manual, 02/2014 2403 Programming the PLC 9.7 References Parameter Operand Value SRC_ARRAY #SourceField ARRAY[0..3] of BYTE := 16#1A, 16#2B, 16#3C, 16#4D DEST_VARIABLE #DINTVariable 1295788826 16#4D3C2B1A POS #TagPos 0 => 4 The "Read data in little endian format" instruction reads the integer 1_295_788_826 from the memory area "#SourceField" and writes it to the "#DINTVariable" operand in little endian format. The data type at the DEST_VARIABLE parameter specifies how many bytes are read. The quantity 4 is saved at the "#TagPos" operand. See also Overview of the valid data types (Page 1204) Deserialize: Deserialization (Page 2366) Serialize: Serialization (Page 2369) Addressing areas of a tag with slice access (Page 1192) WRITE_LITTLE: Write data in little endian format Description You use the "Write data in little endian format" instruction to write the data of a single tag in the little endian byte sequence to a memory area. With the little endian format, the byte with the least significant bits is saved first, which means at the lowest memory address. The memory area written to must have the data type ARRAY of BYTE. The operand at the SRC_VARIABLE parameter must have an elementary data type. The operand at the POS parameter determines the position at which the writing starts. Note Writing tag of data type VARIANT or BOOL If you want to write a tag to which a VARIANT points, use the "Serialize" or "Deserialize" instructions. If you want to write a tag of the data type BOOL, use a "Slice access". Syntax Use the following syntax for the "Write data in little endian format" instruction: SCL WRITE_LITTLE(SRC_VARIABLE := <Operand>, DEST_ARRAY := <Operand>, 2404 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References SCL POS := <Operand>) Parameter The following table shows the parameters of the "Write data in little endian format" instruction: Parameter Declaration Data type Description SRC_VARIABLE Input Bit strings, integers, floatingpoint numbers, timers, LDT, TOD, LTOD, DATE, CHAR, WCHAR Tag whose data are written DEST_ARRAY InOut ARRAY of BYTE Memory area to which the data are written POS InOut DINT Determines the position at which the writing starts. The POS parameter is calculated zero-based. INT Error information Function value Example The following example shows how the instruction works: SCL #TagResult := WRITE_LITTLE(SRC_VARIABLE := #DINTVariable, DEST_ARRAY := #TargetField, POS := #TagPos); The following table shows how the instruction works using specific operand values: Parameter Operand Value SRC_VARIABLE #DINTVariable 1295788826 16#4D3C2B1A DEST_ARRAY #TargetField ARRAY[0..10] of BYTE = 16#1A, 16#2B, 16#3C, 16#4D POS #TagPos 0 => 4 The "Write data in little endian format" instruction writes the integer 1_295_788_826 from the "#DINTVariable" operand to the "#TargetField" memory area in little endian format. The data type at the SRC_VARIABLE parameter specifies how many bytes are written. The quantity 4 is saved at the "#TagPos" operand. See also Overview of the valid data types (Page 1204) Deserialize: Deserialization (Page 2366) WinCC Basic V13.0 System Manual, 02/2014 2405 Programming the PLC 9.7 References Serialize: Serialization (Page 2369) Addressing areas of a tag with slice access (Page 1192) READ_BIG: Read data in big endian format Description You use the "Read data in big endian format" instruction to read the data to a single tag in the big endian byte sequence. With the big endian format, the byte with the most significant bits is saved first, which means at the lowest memory address. The memory area that is read from must have the data type ARRAY of BYTE. The operand at the DEST_VARIABLE parameter must have an elementary data type. The operand at the POS parameter determines the position at which the reading starts. Note Reading tag of data type VARIANT or BOOL If you want to read a tag to which a VARIANT points, use the "Serialize" or "Deserialize" instructions. If you want to read a tag of the data type BOOL, use a "Slice access". Syntax Use the following syntax for the "Read data in big endian format" instruction: SCL READ_BIG(SRC_ARRAY := <Operand>, DEST_VARIABLE => <Operand>, POS := <Operand>) Parameter The following table shows the parameters of the "Read data in big endian format" instruction: Parameter Declaration Data type Description SRC_ARRAY Input ARRAY of BYTE Memory area from which is read DEST_VARIABLE Output Bit strings, integers, floatingpoint numbers, timers, LDT, TOD, LTOD, DATE, CHAR, WCHAR Read value 2406 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameter Declaration Data type Description POS InOut DINT Determines the position at which the reading starts. The POS parameter is calculated zero-based. INT Error information Function value Example The following example shows how the instruction works: SCL #TagResult := READ_BIG(SRC_ARRAY := #SourceField, DEST_VARIABLE => #DINTVariable, POS := #TagPos); The following table shows how the instruction works using specific operand values: Parameter Operand Value SRC_ARRAY #SourceField ARRAY[0..10] of BYTE := 16#1A, 16#2B, 16#3C, 16#4D DEST_VARIABLE #DINTVariable 439041101 16#1A2B3C4D POS #TagPos 0 => 4 The "Read data in big endian format" instruction reads the integer 439_041_101 from the memory area "#SourceField" and writes it to the "#DINTVariable" operand in big endian format. The data type at the DEST_VARIABLE parameter specifies how many bytes are read. The quantity 4 is saved at the "#TagPos" operand. See also Overview of the valid data types (Page 1204) Deserialize: Deserialization (Page 2366) Serialize: Serialization (Page 2369) Addressing areas of a tag with slice access (Page 1192) WRITE_BIG: Write data in big endian format Description You use the "Write data in big endian format" instruction to write the data of a single tag in the big endian byte sequence to a memory area. With the big endian format, the byte with the most significant bits is saved first, which means at the lowest memory address. The memory area written to must have the data type ARRAY of BYTE. WinCC Basic V13.0 System Manual, 02/2014 2407 Programming the PLC 9.7 References The operand at the SRC_VARIABLE parameter must have an elementary data type. The operand at the POS parameter determines the position at which the writing starts. Note Writing tag of data type VARIANT or BOOL If you want to write a tag to which a VARIANT points, use the "Serialize" or "Deserialize" instructions. If you want to write a tag of the data type BOOL, use a "Slice access". Syntax Use the following syntax for the "Write data in big endian format" instruction: SCL WRITE_BIG(SRC_VARIABLE := <Operand>, DEST_ARRAY := <Operand>, POS := <Operand>) Parameter The following table shows the parameters of the "Write data in big endian format" instruction: Parameter Declaration Data type Description SRC_VARIABLE Input Bit strings, integers, floatingpoint numbers, timers, LDT, TOD, LTOD, DATE, CHAR, WCHAR Tag whose data are written DEST_ARRAY InOut ARRAY of BYTE Memory area to which the data are written POS InOut DINT Determines the position at which the writing starts. The POS parameter is calculated zero-based. INT Error information Function value Example The following example shows how the instruction works: SCL #TagResult := WRITE_BIG(SRC_VARIABLE := #DINTVariable, DEST_ARRAY := #TargetField, POS := #TagPos); The following table shows how the instruction works using specific operand values: 2408 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameter Operand Value SRC_VARIABLE #DINTVariable 439041101 16#1A2B3C4D DEST_ARRAY #TargetField ARRAY[0..10] of BYTE = 16#1A, 16#2B, 16#3C, 16#4D POS #TagPos 0 => 4 The "Write data in big endian format" instruction writes the integer 439_041_101 from the "#DINTVariable" operand to the "#TargetField" memory area in big endian format. The data type at the SRC_VARIABLE parameter specifies how many bytes are written. The quantity 4 is saved at the "#TagPos" operand. See also Overview of the valid data types (Page 1204) Deserialize: Deserialization (Page 2366) Serialize: Serialization (Page 2369) Addressing areas of a tag with slice access (Page 1192) VARIANT instructions VariantGet: Read out VARIANT tag value Description You can use the "Read out VARIANT tag value" instruction to read the value of the tag to which the VARIANT at the SRC parameter points and write it in the tag at the DST parameter. The SRC parameter must have the VARIANT data type. Any data type except for VARIANT can be specified at the DST parameter. The data type of the tag at the DST parameter must match the data type to which the VARIANT points. Note The tag to which the VARIANT at parameter SRC points must be a PLC data type. To copy structures and ARRAYs, you can use the "MOVE_BLK_VARIANT: Move block" instruction. For additional information, refer to "See also". WinCC Basic V13.0 System Manual, 02/2014 2409 Programming the PLC 9.7 References Syntax The following syntax is used for the "Read out VARIANT tag value" instruction: SCL VariantGet(SRC := <Operand>, DST => <Operand>) Parameter The following table shows the parameters of the "Read out VARIANT tag value" instruction: Parameter Declaration Data type Description SRC Input VARIANT Tag to be read DST Output Bit strings, integers, floatingpoint numbers, timers, date and time, character strings, ARRAY, structures Result of the instruction For additional information on valid data types, refer to "See also". Example The following example shows how the instruction works: SCL VariantGet(SRC := #TagIn_Source, DST => "TagOut_Dest"); The value of the tag to which the VARIANT at the "#TagIn_Source" operand points is read and written to the "TagOut_Dest" operand. See also Overview of the valid data types (Page 1204) Basics of the EN/ENO mechanism (Page 1299) VARIANT (Page 1245) MOVE_BLK_VARIANT: Move block (Page 2374) VariantPut: Write VARIANT tag value Description You can use the "Write VARIANT tag value" instruction to write the value of the tag at the SRC parameter to the tag at the DST parameter to which the VARIANT points. 2410 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References The DST parameter must have the VARIANT data type. Any data type except for VARIANT can be specified at the SRC parameter. The data type of the tag at the SRC parameter must match the data type to which the VARIANT points. Note The tag to which the VARIANT at parameter DST points must be a PLC data type. Syntax The following syntax is used for the "Write VARIANT tag value" instruction: SCL VariantPut(SRC := <Operand>, DST := <Operand>) Parameter The following table shows the parameters of the "Write VARIANT tag value" instruction: Parameter Declaration Data type Description SRC Input Bit strings, integers, floatingpoint numbers, timers, date and time, character strings, ARRAY Tag to be read DST Input VARIANT Result of the instruction For additional information on valid data types, refer to "See also". Example The following example shows how the instruction works: SCL VariantPut(SRC := "TagIn_Source", DST => "#TagIn_Dest"); The value of the "TagIn_Source" operand is written to the tag to which the VARIANT at the "#TagIn_Dest" operand points. See also Overview of the valid data types (Page 1204) Basics of the EN/ENO mechanism (Page 1299) VARIANT (Page 1245) WinCC Basic V13.0 System Manual, 02/2014 2411 Programming the PLC 9.7 References CountOfElements: Get number of ARRAY elements Description You can use the "Get number of ARRAY elements" instruction to query how many ARRAY elements a tag to which VARIANT is pointing has. If it is a one-dimensional ARRAY, the difference between the high and low limit +1 is output as a result. If it is a multi-dimensional ARRAY, the product of all dimensions is output as the result. The <Operand> must have the VARIANT data type. The result is "0" if the VARIANT tag is not an ARRAY. If the VARIANT points to an ARRAY of BOOL, the fill elements are included in the count. (For example, 8 is returned for an ARRAY[0..1] of BOOL) Syntax The following syntax is used for the "Get number of ARRAY elements" instruction: SCL CountOfElements(<Operand>) Parameter The following table shows the parameters of the "Get number of ARRAY elements" instruction: Parameter Declaration Data type Description <Operand> Input VARIANT Tag to be queried UDINT Result of the instruction Function value For additional information on valid data types, refer to "See also". Example The following example shows how the instruction works: SCL IF IS_ARRAY(#Tag_VARIANTToArray) THEN "Tag_Result" := CountOfElements(#Tag_VARIANT); END_IF; If the tag to which the VARIANT points is an ARRAY, the number of ARRAY elements is output. 2412 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References See also Format of array (16-bit limits) (Page 1235) Format of array (32-bit limits) (Page 1236) Overview of the valid data types (Page 1204) Basics of the EN/ENO mechanism (Page 1299) VARIANT (Page 1245) Other BLKMOV: Move block Description The instruction "Move block" copies the contents of a memory area (source area) to another memory area (destination area). The move operation takes place in the direction of ascending addresses. You use VARIANT to define the source and destination areas. Note The tags of the instruction can only be used in data blocks in which the attribute "Optimized block access" is not set. If the tag with the retentive setting "Set in IDB" has been declared, you can also use the tags "with optimized access". The following figure shows the principle of the move operation: '%'%: $ % '%'%: & ' '%'%: ( ) '%'%: * + 0RYH &RS\LQJLVSHUIRUPHGLQ WKHGLUHFWLRQRIDVFHQGLQJ DGGUHVVHV 0: $ % 0: & ' 0: ( ) 0: * + 0HPRU\DUHD WinCC Basic V13.0 System Manual, 02/2014 2413 Programming the PLC 9.7 References Consistency of source data and destination data Note that while the instruction "Move block" is being executed, the source data remains unchanged; otherwise the consistency of the destination data cannot be guaranteed. Interruptibility There is no limit to the nesting depth. Memory areas The instruction "Move block" moves the following memory areas: Areas of a data block Bit memory Process image of the inputs Process image of the outputs General rules for moving The source and destination areas must not overlap. If the source and destination area have different lengths, only the length of the smaller area will be moved. If the source area is smaller than the destination area, the entire source area will be written to the destination area. The remaining bytes of the destination area remain unchanged. If the destination area is smaller than the source area, the entire destination area will be written. The remaining bytes of the source area are ignored. If a block of data type BOOL is moved, the tag must be addressed absolutely and the specified length of the area must be divisible by 8, otherwise the instruction cannot be executed. Rules for moving character strings You can use the "Move block" instruction to move source and destination areas of the STRING data type. If only the source area is of data type STRING, the characters will be moved that are actually contained in the character string. Information on the actual and maximum length is also written to the destination area. If the source and destination area are both STRING data type, the current length of the character string in the destination area is set to the number of characters actually moved. If you want to move the information on the maximum and actual length of a character string, specify the areas in bytes in the SRCBLK and DSTBLK parameters. Syntax The following syntax is used for the "Move block" instruction: SCL BLKMOV(SRCBLK:= <Operand>, DSTBLK => <Operand>) 2414 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameter The following table shows the parameters of the "Move block" instruction: Parameter Declaration Data type Description SRCBLK Input VARIANT Specifies the memory area to be moved (source area). DSTBLK Output VARIANT Specifies the memory area to which the block is to be moved (destination area). INT Error information Function value (RET_VAL) For additional information on valid data types, refer to "See also". RET_VAL parameter The following table shows the meaning of the values of the RET_VAL parameter: Error code* (W#16#...) Explanation 0000 No error 8152 The data types WSTRING, WCHAR and BOOL are not supported. 8092 The source or target area is only available in the load memory. General error information See also: "GET_ERR_ID: Get error ID locally *The error codes can be displayed as integer or hexadecimal value in the program editor. For information on toggling display formats, refer to "See also". See also Overview of the valid data types (Page 1204) GET_ERR_ID: Get error ID locally (Page 2462) UBLKMOV: Move block uninterruptible Description The instruction "Move block uninterruptible" copies the contents of a memory area (source area) to another memory area (destination area). The move operation takes place in the direction of ascending addresses. You use VARIANT to define the source and destination areas. WinCC Basic V13.0 System Manual, 02/2014 2415 Programming the PLC 9.7 References The move operation cannot be interrupted by other operating system activities. As a result the interrupt reaction time of the CPU can increase during the execution of the instruction "Move block uninterruptible". Note The tags of the instruction can only be used in data blocks in which the attribute "Optimized block access" is not set. If the tag with the retentive setting "Set in IDB" has been declared, you can also use the tags "with optimized access". Memory areas The instruction "Move block uninterruptible" copies the following memory areas: Areas of a data block Bit memory Process image of the inputs Process image of the outputs General rules for moving The source and destination area must not overlap during the execution of the instruction "Move block uninterruptible". If the source area is smaller than the destination area, the entire source area will be written to the destination area. The remaining bytes of the destination area remain unchanged. If the destination area is smaller than the source area, the entire destination area will be written. The remaining bytes of the source area are ignored. If a source or destination area defined as a formal parameter is less than a destination or source area specified at the SRCBLK or DSTBLK parameter, no data is transferred. If a block of data type BOOL is moved, the tag must be addressed absolutely and the specified length of the area must be divisible by 8, otherwise the instruction cannot be executed. You can use the "Move block uninterruptible" instruction to move a maximum of 16 KB. Note the CPU-specific restrictions for this. Rules for moving character strings The instruction "Move block uninterruptible" copies source and destination areas of the data type STRING. If only the source area is of data type STRING, the characters will be moved that are actually contained in the character string. Information on the actual and maximum length are not written in the destination area. If the source and destination area are both STRING data type, the current length of the character string in the destination area is set to the number of characters actually moved. If areas of the STRING data type are moved, specify "1" as the area length. 2416 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Syntax The following syntax is used for the "Move block uninterruptible" instruction: SCL UBLKMOV(SRCBLK:= <Operand>, DSTBLK => <Operand>) Parameter The following table shows the parameters of the "Move block uninterruptible" instruction: Parameter Declaration Data type Description SRCBLK Input VARIANT Specifies the memory area to be moved (source area). DSTBLK Output ANY Specifies the memory area to which the block is to be moved (destination area). VARIANT Error information Function value (RET_VAL) For additional information on valid data types, refer to "See also". RET_VAL parameter The following table shows the meaning of the values of the RET_VAL parameter: Error code (W#16#...) Explanation 0000 No error 8152 The data types WSTRING, WCHAR and BOOL are not supported. 8091 The source area is in a data block that is not relevant for program execution. General error information See also: "GET_ERR_ID: Get error ID locally *The error codes can be displayed as integer or hexadecimal value in the program editor. For information on toggling display formats, refer to "See also". See also Overview of the valid data types (Page 1204) GET_ERR_ID: Get error ID locally (Page 2462) WinCC Basic V13.0 System Manual, 02/2014 2417 Programming the PLC 9.7 References FILL: Fill block Description The instruction "Fill block" fills a memory area (destination area) with the content of another memory area (source area). The instruction "Fill block" moves the content of the source area to the destination area until the destination area is completely written. The move operation takes place in the direction of ascending addresses. You use VARIANT to define the source and destination areas. Note The tags of the instruction can only be used in data blocks in which the attribute "Optimized block access" is not set. If the tag with the retentive setting "Set in IDB" has been declared, you can also use the tags "with optimized access". For blocks with the "Optimized block access" attribute, you can use the "FILL_BLK: Fill block" instruction. The following figure shows the principle of the move operation: ),// %9$/ $ % 0: $ % 0: & ' 0: & ' 0: ( ) 0: ( ) 0: * + 0: * + 0: $ % 0: & ' 0: ( ) 0: * + 0: $ % 0: & ' 0: %/. Example: The contents of the range MW100 to MW118 are to be preassigned with the contents of the memory words MW14 to MW20. Consistency of source data and destination data Note that while the instruction "Fill block" is being executed, the source data remains unchanged; otherwise the consistency of the destination data cannot be guaranteed. 2418 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Memory areas The instruction "Fill block" copies the following memory areas: Areas of a data block Bit memory Process image of the inputs Process image of the outputs The instruction "Fill block" copies the following memory areas: Instructions, system data blocks Counters Timers Memory areas of the I/O area General rules for moving The source and destination areas must not overlap. If the destination area to be preset is not an integer multiple of the length of the input parameter BVAL, the destination area is nevertheless written up to the last byte. If the destination area to be preset is smaller than the source area, the function only copies as much data as can be written to the destination area. If the destination or source block actually present is smaller than the assigned memory area for the source or destination area (BVAL, BLK parameters), no data will be transferred. If the ANY pointer (source or destination) is of the data type BOOL, it must be addressed absolutely and the length specified must be divisible by 8; otherwise the instruction is not executed. If the destination area is STRING data type, the instruction writes the entire string including the administration information. Syntax The following syntax is used for the instruction "Fill block": SCL FILL(BVAL:= <Operand>, BLK => <Operand>) WinCC Basic V13.0 System Manual, 02/2014 2419 Programming the PLC 9.7 References Parameter The following table shows the parameters of the "Fill block" instruction: Parameter Declaration Data type Description BVAL Input VARIANT Specification of the memory area (source area) with whose content the destination area on the BLK parameter will be filled. BLK Output VARIANT Specification of the memory area that will be filled with the content of the source area. INT Error information Function value (RET_VAL) For additional information on valid data types, refer to "See also". BVAL Parameter When you transfer a structure as an input parameter, remember that the length of a structure is always based on an even number of bytes. The structure will need one byte of additional memory space if you declare a structure with an odd number of bytes. RET_VAL parameter The following table shows the meaning of the values of the RET_VAL parameter: Error code (W#16#...) Explanation 0000 No error 8152 The data types WSTRING, WCHAR and BOOL are not supported. General error See also: "GET_ERR_ID: Get error ID locally information *The error codes can be displayed as integer or hexadecimal value in the program editor. For information on toggling display formats, refer to "See also". See also Overview of the valid data types (Page 1204) GET_ERR_ID: Get error ID locally (Page 2462) 2420 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Conversion operations CONVERT: Convert value Description Use the "Convert value" instruction to program explicit conversions. You determine the data types to be converted in a dialogue box with opens automatically when you insert the instruction. When executed, the instruction reads the source value and converts it into the specified target value. For information on possible conversions, refer to section "Explicit conversion" under "See also". Note For S7-1500 CPU: You can select the data types DWORD and LWORD if REAL or LREAL were selected as IN data type. Syntax The following syntax is used for the "Convert value" instruction: SCL <Target_value> := <Conversion_function>(<Source_value>); The syntax of the instruction consists of the following parts: Parameter Declaration Data type Description S7-1200 S7-1500 Bit strings, integers, floatingpoint numbers, TIME, DATE, TOD, DTL, strings Bit strings, integers, floatingpoint numbers, TIME, LTIME, DATE, TOD, LTOD, DTL, strings Value to be converted. <Conversion_function > - - Function that specifies the data type to be converted . <Target_value> Bit strings, integers, floatingpoint numbers, TIME, DATE, TOD, DTL, strings Bit strings, integers, floatingpoint numbers, TIME, LTIME, DATE, TOD, LTOD, DTL, strings Result of the conversion <Source_value> Input, constant Output For additional information on valid data types, refer to "See also". WinCC Basic V13.0 System Manual, 02/2014 2421 Programming the PLC 9.7 References Example The following example shows how the instruction works: SCL "Tag_INT" := REAL_TO_INT("Tag_REAL"); The following table shows how the instruction works using specific operand values: Operand Data type Value Tag_REAL REAL 20.56 Tag_INT INT 21 During the conversion, the value of the "Tag_REAL" operand will be rounded to the nearest integer and saved in the "Tag_INT" operand. See also Overview of the valid data types (Page 1204) Operators and operator precedence (Page 1486) ROUND: Round numerical value Description The "Round numerical value" instruction is used to round the value at input IN to the nearest integer. The instruction interprets the value at input IN as a floating-point number and converts it into an integer or floating-point number. If the input value is exactly between an even and odd number, the even number is selected. Syntax The following syntax is used for the "Round numerical value" instruction: SCL ROUND(<Expression>) The syntax of the instruction consists of the following parts: Parameter Declaration Data type Description <Expression> Input Floating-point numbers Input value to be rounded. Integers, floating-point numbers Result of the rounding Function value For additional information on valid data types, refer to "See also". 2422 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Example The following example shows how the instruction works: SCL "Tag_Result" := ROUND("Tag_Value"); The result of the instruction is returned in the operand "Tag_Result" as a function value. The following table shows how the instruction works using specific operand values: Operand Value Tag_Value 1.50000000 -1.50000000 Tag_Result 2 -2 See also Overview of the valid data types (Page 1204) Operators and operator precedence (Page 1486) CEIL: Generate next higher integer from floating-point number Description Use the "Generate next higher integer from floating-point number" instruction to round the value to the nearest integer. The instruction interprets the input value as floating-point number and converts it to the next higher integer. The function value can be greater than or equal to the input value. Syntax The following syntax is used for the "Generate next higher integer from floating-point number" instruction: SCL CEIL(<Expression>) CEIL_<Data type>(<Expression>) The syntax of the instruction consists of the following parts: WinCC Basic V13.0 System Manual, 02/2014 2423 Programming the PLC 9.7 References Parameter Declaration Data type Description <Expression> Input Floating-point numbers Input value Integers, floatingpoint numbers. Default: DINT Data type of the function value: _<Data type> You do not need to specify the data type if using the default. Any other valid data type you may use must be declared explicitly. Function value Integers, floatingpoint numbers Input value rounded up For additional information on valid data types, refer to "See also". Example The following example shows how the instruction works: SCL "Tag_Result1" := CEIL("Tag_Value"); "Tag_Result2" := CEIL_REAL("Tag_Value); The following table shows how the instruction works using specific operand values: Operand Value Tag_Value 0.5 -0.5 Tag_Result1 1 0 Tag_Result2 1.0 0.0 The result of the instruction is returned in the operand "Tag_Result" as a function value. See also Overview of the valid data types (Page 1204) Expressions (Page 1480) Operators and operator precedence (Page 1486) FLOOR: Generate next lower integer from floating-point number Description Use the "Generate next lower integer from floating-point number" instruction to round the value of a floating point number to the next lower integer. The instruction interprets the input value as floating-point number and converts it to the next lower integer. The function value can be equal or less than the input value. 2424 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Syntax Use the following syntax for the "Generate next lower integer from floating-point number" instruction: SCL FLOOR(<Expression>) FLOOR_<data type>(<expression>) The syntax of the instruction consists of the following parts: Parameter Declaration Data type Description <Expression> Input Floating-point numbers Input value Integers, floatingpoint numbers. Default: DINT Data type of the function value: _<Data type> You do not need to specify the data type if using the default. Any other valid data type you may use must be declared explicitly. Function value Integers, floatingpoint numbers Input value rounded For additional information on valid data types, refer to "See also". Example The following example shows how the instruction works: SCL "Tag_Result1" := FLOOR("Tag_Value"); "Tag_Result2" := FLOOR_REAL("Tag_Value"); The following table shows how the instruction works using specific operand values: Operand Value Tag_Value 0.5 -0.5 Tag_Result1 0 -1 Tag_Result2 0.0 -1.0 The result of the instruction is returned in the operand "Tag_Result" as a function value. See also Overview of the valid data types (Page 1204) Expressions (Page 1480) Operators and operator precedence (Page 1486) WinCC Basic V13.0 System Manual, 02/2014 2425 Programming the PLC 9.7 References TRUNC: Truncate numerical value Description The "Truncate numerical value" instruction is used to generate an integer from the input value without rounding. The instruction selects only the integer part of the input value and returns this part without decimal places as the function value. Syntax The following syntax is used for the "Truncate numerical value" instruction: SCL TRUNC(<Expression>) TRUNC_<Data type>(<Expression>) The syntax of the instruction consists of the following parts: Parameter Declaration Data type Description <Expression> Input Floating-point numbers Input value Integers, floating-point numbers Default: DINT Data type of the function value: _<Data type> You do not need to specify the data type if using the default. Any other valid data type you may use must be declared explicitly. Function value Integers, floating-point numbers Integer component of the input value For additional information on valid data types, refer to "See also". Example The following example shows how the instruction works: SCL "Tag_Result1" := TRUNC("Tag_Value1"); "Tag_Result2" := TRUNC("Tag_Value2"+"Tag_Value3"); "Tag_Result3" := TRUNC_SINT("Tag_Value4"); The result of the instruction is returned in the operand "Tag_Result" as a function value. The following table shows how the instruction works using specific operand values: 2426 Operand Value Tag_Value1 -1.5 Tag_Result1 -1 Tag_Value2 2.1 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Operand Value Tag_Value3 3.2 Tag_Result2 5 Tag_Result3 2 Tag_Value4 2.4 See also Overview of the valid data types (Page 1204) Operators and operator precedence (Page 1486) SCALE_X: Scale Description Use the "Scale" instruction to scale a floating-point number by mapping it to a specific value range. You specify the value range with the MIN and MAX parameters. The result of the scaling is an integer. The following figure shows an example of how values can be scaled: 0$; 5HVXOW! 0,1 ([SUHVVLRQ! The instruction "Scale" works with the following equation: OUT = [VALUE (MAX - MIN)] + MIN Note For more information on the conversion of analog values, refer to the respective manual. WinCC Basic V13.0 System Manual, 02/2014 2427 Programming the PLC 9.7 References Syntax The following syntax is used for the "Scale" instruction: SCL SCALE_X(MIN := <Operand>, VALUE := <Operand>, MAX := <Operand>) SCALE_X_<Data type>(MIN := <Operand>, VALUE := <Operand>, MAX := <Operand>) The syntax of the instruction consists of the following parts: Parameter Declaration Data type Description MIN Input Integers, floating-point numbers Low limit of the value range VALUE Input Floating-point numbers Value to be scaled. If you enter a constant, you must declare it. MAX _<Data type> Input Integers, floating-point numbers High limit of the value range Integers, floating-point numbers Default: INT Data type of the function value: You do not need to specify the data type if using the default. Any other valid data type you may use must be declared explicitly. Function value Integers, floating-point numbers Result of scaling For additional information on valid data types, refer to "See also". For additional information on declaring constants, refer to "See also". Example The following example shows how the instruction works: SCL "Tag_Result1" := SCALE_X(MIN := "Tag_Value1", VALUE := "Tag_Real", MAX := "Tag_Value2"); "Tag_Result2" := SCALE_X_REAL(MIN := "Tag_Value1", VALUE := "Tag_Real", MAX := "Tag_Value2"); The result of the instruction is returned in the operand "Tag_Result" as a function value. 2428 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References The following table shows how the instruction works using specific operand values: Operand Value Tag_Real 0.5 Tag_Value1 10 Tag_Value2 30 Tag_Result1 20 Tag_Result2 20.0 See also Overview of the valid data types (Page 1204) Operators and operator precedence (Page 1486) Declaring global constants (Page 1320) NORM_X: Normalize Description You can use the instruction "Normalize" to normalize the value of the tag at the VALUE input by mapping it to a linear scale. You can use the MIN and MAX parameters to define the limits of a value range that is applied to the scale. Depending on the location of the normalized value in this value range, the result at output OUT is calculated and stored as a floating-point number. If the value to be normalized equals the value at input MIN, the instruction returns returns the result "0.0". If the value to be normalized equals the value at input MAX, the instruction returns returns the result "1.0". The following figure shows an example of how values can be normalized: 5HVXOW! 0,1 0$; ([SUHVVLRQ! WinCC Basic V13.0 System Manual, 02/2014 2429 Programming the PLC 9.7 References The "Normalize" instruction works with the following equation: OUT = (VALUE - MIN) / (MAX - MIN) Note For more information on the conversion of analog values, refer to the respective manual. Syntax The following syntax is used for the "Normalize" instruction: SCL NORM_X(MIN := <Operand>, VALUE := <Operand>, MAX := <Operand>) NORM_X_<Data type>(MIN := <Operand>, VALUE := <Operand>, MAX := <Operand>) The syntax of the instruction consists of the following parts: Parameter Declaration Data type Description MIN 1) Input Integers, floating-point numbers Low limit of the value range VALUE 1) Input Integers, floating-point numbers Value to be normalized. MAX 1) Input Integers, floating-point numbers High limit of the value range Floating-point numbers Default: REAL Data type of the function value: _<Data type> You do not need to specify the data type if using the default. Any other valid data type you may use must be declared explicitly. Function value 1) Floating-point numbers Result of the normalization If you use constants in these three parameters, you only need to declare one of them. For additional information on valid data types, refer to "See also". For additional information on declaring constants, refer to "See also". 2430 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Example The following example shows how the instruction works: SCL "Tag_Result1" := NORM_X(MIN := "Tag_Value1", VALUE := "Tag_InputValue", MAX := "Tag_Value2"); "Tag_Result2" := NORM_X_LREAL(MIN := "Tag_Value1", VALUE := "Tag_InputValue", MAX := "Tag_Value2"); The result of the instruction is returned in the operand "Tag_Result" as a function value. The following table shows how the instruction works using specific operand values: Operand Value Tag_InputValue 20 Tag_Value1 10 Tag_Value2 30 Tag_Result1 0.5 Tag_Result2 0.5 See also Overview of the valid data types (Page 1204) Operators and operator precedence (Page 1486) Declaring global constants (Page 1320) VARIANT instructions VARIANT_TO_DB_ANY: Convert VARIANT to DB_ANY Description The instruction "Convert VARIANT to DB_ANY" is used to read the number of the data block from a VARIANT and convert it to the data type DB_ANY. WinCC Basic V13.0 System Manual, 02/2014 2431 Programming the PLC 9.7 References Requirements If the conditions are met, the instruction is executed. If the conditions are not met, "0" is output as data block number. The output tag... homed... Conversion options VARIANT ...a data block which is an instance data block of an UDT or SDT The output tag can be converted to a data block number. VARIANT ...an Array DB The output tag can be converted to a data block number. VARIANT ...an object with an elementary data type It is not possible to convert the output tag to a database number because a data block can never comprise only one elementary data type. VARIANT ...a structure within a data block It is not possible to convert the output tags to a database number because it is only a part within the data block. Syntax The following syntax is used for the "Convert VARIANT To DB_ANY" instruction: SCL VARIANT_TO_DB_ANY(IN := <Operand>, ERR => <Operand>) Parameter The following table shows the parameters of the "Convert VARIANT to DB_ANY" instruction: Parameter Declaration Data type Description IN Input VARIANT Tag to be read ERR Output INT Error information DB_ANY Result: Number of the DB Function value For additional information on valid data types, refer to "See also". ERR parameter The following table shows the meaning of the values of the ERR parameter: Error code* Explanation (W#16#...) 2432 0000 No error 252C The VARIANT data type has the value "0" 8130 The number of the data block is "0" WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Error code* Explanation (W#16#...) 8131 The data block does not exist 8132 The data block is too short 8134 The data block is write protected 8150 The VARIANT data type has the value "0" 8154 The data type is not correctly declared *The error codes can be displayed as integer or hexadecimal value in the program editor. For information on toggling display formats, refer to "See also". Example The following example shows how the instruction works: SCL "Tag_Result" := VARIANT_TO_DB_ANY(IN := "Tag_In", ERR := "Tag_Err"); The following table shows how the instruction works using specific operand values: Parameter Operand Value IN Tag_In The data type of the Tag_In operand is VARIANT. The value is read. <Function value> Tag_Result Number of the block is output. The third element is read from "Tag_In" operand and written to the "Tag_Result" operand. See also Overview of the valid data types (Page 1204) Operators and operator precedence (Page 1486) DB_ANY_TO_VARIANT: Convert DB_ANY to VARIANT Description The instruction "Convert DB_ANY to VARIANT" is used to read the number of the data block from a DB_ANY and convert it to the data type VARIANT. WinCC Basic V13.0 System Manual, 02/2014 2433 Programming the PLC 9.7 References Requirements If the conditions are met, the instruction is executed. If the conditions are not met or the data block does not exist, the value "0" is output. All additional accesses to this value "0" fail. The output tag... homed... Conversion options DB_ANY ...a data block which is an instance data block of an UDT or SDT It is possible to convert the output tag to the VARIANT data type. DB_ANY ...a DB which is an ARRAY DB It is possible to convert the output tag to the VARIANT data type. DB_ANY ...a data block which is an instance data block of a function block or a global data block It is not possible to convert the output tags to the VARIANT data type. Syntax The following syntax is used for the "Convert DB_ANY to VARIANT" instruction: SCL DB_ANY_TO_VARIANT(IN := <Operand>, ERR => <Operand>) Parameter The following table shows the parameters of the "Convert DB_ANY to VARIANT" instruction: Parameter Declaration Data type Description IN Input DB_ANY Tag to be read ERR Output INT Error information VARIANT Result Function value For additional information on valid data types, refer to "See also". ERR parameter The following table shows the meaning of the values of the ERR parameter: Error code* Explanation (W#16#...) 2434 0000 No error 8130 The number of the data block is "0" 8131 The data block does not exist 8132 The data block is too short 8134 The data block is write protected WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Error code* Explanation (W#16#...) 8154 The data type is not correctly declared *The error codes can be displayed as integer or hexadecimal value in the program editor. For information on toggling display formats, refer to "See also". Example The following example shows how the instruction works: SCL "Tag_Result" := DB_ANY_TO_VARIANT(IN := "Tag_In", ERR := "Tag_Err"); The following table shows how the instruction works using specific operand values: Parameter Operand Value IN Tag_In The data type of the Tag_In operand is DB_ANY. The value is read. <Function value> Tag_Result Number of the block is converted and output to the VARIANT data type. The third element is read from "Tag_In" operand and written to the "Tag_Result" operand. See also Overview of the valid data types (Page 1204) Operators and operator precedence (Page 1486) Other SCALE: Scale Description The instruction "Scale" converts the integer on the parameter IN into a floating-point number, which can be scaled in physical units between a low and a high limit. You can use the LO_LIM and HI_LIM parameters to specify the low limit and high limit of the value range to which the input value is scaled. The result of the instruction is output on the OUT parameter. The instruction "Scale" works with the following equation: OUT = [((FLOAT (IN) - K1)/(K2-K1)) (HI_LIM-LO_LIM)] + LO_LIM The values of the "K1" and "K2" constants are determined by the signal state on the BIPOLAR parameter. The following signal states are possible on the BIPOLAR parameter: WinCC Basic V13.0 System Manual, 02/2014 2435 Programming the PLC 9.7 References Signal state "1": It is assumed that the value at the IN parameter is bipolar and in a value range between -27648 and 27648. In this case the "K1" constant has the value "-27648.0" and the "K2" constant the value "+27648.0". Signal state "0": It is assumed that the value at the IN parameter is unipolar and in a value range between 0 and 27648. In this case the "K1" constant has the value "0.0" and the "K2" constant the value "+27648.0". When the value at the IN parameter is greater than the value of the "K2" constant, the result of the instruction is set to the value of the high limit (HI_LIM) and an error is output. When the value at the IN parameter is less than the value of the "K1" constant, the result of the instruction is set to the value of the low limit value (LO_LIM) and an error is output. When the indicated low limit is greater than the high limit (LO_LIM >HI_LIM), the result is scaled in reverse proportion to the input value. Syntax The following syntax is used for the "Scale" instruction: SCL SCALE(IN:= <Expression>, HI_LIM := <Operand>, LO_LIM := <Operand>, BIPOLAR := <Operand>, OUT => <Operand>) The syntax of the instruction consists of the following parts: Parameter Declaration Data type Description IN Input INT Input value to be scaled. HI_LIM Input REAL High limit LO_LIM Input REAL Low limit BIPOLAR Input BOOL Indicates if the value at the IN parameter is to be interpreted as bipolar or unipolar. The parameter can assume the following values: 1: Bipolar 0: Unipolar OUT Output Function value (RET_VAL) REAL Result of the instruction WORD Error information For additional information on valid data types, refer to "See also". 2436 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References RET_VAL Parameter The following table shows the meaning of the values of the parameter RET_VAL: Error code (W#16#...) Explanation 0000 No error 0008 The value of the parameter IN is greater than 27 648 or is less than 0 (unipolar) or -27 648 (bipolar). General error See also: "GET_ERR_ID: Get error ID locally information *The error codes can be displayed as integer or hexadecimal value in the program editor. For information on toggling display formats, refer to "See also". Example The following example shows how the instruction works: "Tag_ErrorCode" := SCALE(IN := "Tag_InputValue", HI_LIM := "Tag_HighLimit" LO_LIM := "Tag_LowLimit" BIPOLAR := "Tag_Bipolar", OUT => "Tag_Result"); The error information is returned in the operand "Tag_ErrorCode" as a function value. The following table shows how the instruction works using specific operand values: Parameter Operand Value IN Tag_InputValue 22 HI_LIM Tag_HighLimit 100.0 LO_LIM Tag_LowLimit 0.0 BIPOLAR Tag_Bipolar 1 OUT Tag_Result 50.03978588 RET_VAL Tag_ErrorCode W#16#0000 See also Overview of the valid data types (Page 1204) Expressions (Page 1480) Operators and operator precedence (Page 1486) GET_ERR_ID: Get error ID locally (Page 2462) WinCC Basic V13.0 System Manual, 02/2014 2437 Programming the PLC 9.7 References UNSCALE: Unscale Description The instruction "Unscale" unscales the floating-point number on the IN parameter in physical units between a low and a high limit and converts them into an integer. You can use the LO_LIM and HI_LIM parameters to specify the low limit and high limit of the value range to which the input value is unscaled. The result of the instruction is output on the OUT parameter. The instruction "Unscale" works with the following equation: OUT = [((IN-LO_LIM)/(HI_LIM-LO_LIM)) (K2-K1)] + K1 The values of the "K1" and "K2" constants are determined by the signal state on the BIPOLAR parameter. The following signal states are possible on the BIPOLAR parameter: Signal state "1": It is assumed that the value at the IN parameter is bipolar and in a value range between -27648 and 27648. In this case the "K1" constant has the value "-27648.0" and the "K2" constant the value "+27648.0". Signal state "0": It is assumed that the value at the IN parameter is unipolar and in a value range between 0 and 27648. In this case the "K1" constant has the value "0.0" and the "K2" constant the value "+27648.0". When the value at the IN parameter is greater than the value of the "HI_LIM" constant, the result of the instruction is set to the value of the constant (K2) and an error is output. When the value at the IN parameter is less than the value of the constant of the low limit (LO_LIM), the result of the instruction is set to the value of the constant (K1) and an error is output. Syntax The following syntax is used for the instruction "Unscale": SCL UNSCALE(IN := <Expression>, HI_LIM := <Operand>, LO_LIM := <Operand>, BIPOLAR := <Operand>, OUT => <Operand>) The syntax of the instruction consists of the following parts: 2438 Parameter Declaration Data type Description IN Input REAL Input value to be unscaled to an integer value. HI_LIM Input REAL High limit LO_LIM Input REAL Low limit WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameter Declaration Data type Description BIPOLAR Input BOOL Indicates if the value at the IN parameter is to be interpreted as bipolar or unipolar. The parameter can assume the following values: 1: Bipolar 0: Unipolar OUT Output Function value (RET_VAL) INT Result of the instruction WORD Error information For additional information on valid data types, refer to "See also". RET_VAL Parameter The following table shows the meaning of the values of the parameter RET_VAL: Error code (W#16#...) Explanation 0000 No error 0008 The value of the IN parameter is greater than the value of the high limit (HI_LIM) or less than the value of the low limit (LO_LIM). General error information See also: "GET_ERR_ID: Get error ID locally *The error codes can be displayed as integer or hexadecimal value in the program editor. For information on toggling display formats, refer to "See also". Example The following example shows how the instruction works: SCL "Tag_ErrorCode" := UNSCALE(IN := "Tag_InputValue", HI_LIM := "Tag_HighLimit" LO_LIM := "Tag_LowLimit" BIPOLAR := "Tag_Bipolar", OUT => "Tag_Result"); The error information is returned in the operand "Tag_ErrorCode" as a function value. The following table shows how the instruction works using specific operand values: WinCC Basic V13.0 System Manual, 02/2014 Parameter Operand Value IN Tag_InputValue 50.03978588 HI_LIM Tag_HighLimit 100.0 LO_LIM Tag_LowLimit 0.0 BIPOLAR Tag_Bipolar 1 2439 Programming the PLC 9.7 References Parameter Operand Value OUT Tag_Result 22 RET_VAL Tag_ErrorCode W#16#0000 See also Overview of the valid data types (Page 1204) Expressions (Page 1480) Operators and operator precedence (Page 1486) GET_ERR_ID: Get error ID locally (Page 2462) Program control operations IF: Run conditionally Description The instruction "Run conditionally" branches the program flow depending on a condition. The condition is an expression with Boolean value (TRUE or FALSE). Logical expression or comparative expressions can be stated as conditions. When the instruction is executed, the stated expressions are evaluated. If the value of an expression is TRUE, the condition is fulfilled; if the value is FALSE, it is not fulfilled. Syntax Depending on the type of branch, you can program the following forms of the instruction: Branch through IF: SCL IF <Condition> THEN <Instructions> END_IF; If the condition is satisfied, the instructions programmed after the THEN are executed. If the condition is not satisfied, the execution of the program continues with the next instruction after the END_IF. Branch through IF and ELSE: SCL IF <Condition> THEN <Instructions1> ELSE <Instructions0>; END_IF; If the condition is satisfied, the instructions programmed after the THEN are executed. If the condition is not satisfied, the instructions programmed after the ELSE are executed. Then the execution of the program continues with the next instruction after the END_IF. 2440 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Branch through IF, ELSIF and ELSE: SCL IF <Condition1> THEN <Instructions1> ELSIF <Condition2> THEN <Instruction2> ELSE <Instructions0>; END_IF; If the first condition (<Condition1>) is satisfied, the instructions (<Instructions1>) after the THEN are executed. After execution of the instructions, the execution of the program continues after the END_IF. If the first condition is not satisfied, the second condition (<Condition2>) is checked. If the second condition (<Condition2>) is fulfilled, the instructions (<Instructions2>) after the THEN are executed. After execution of the instructions, the execution of the program continues after the END_IF. If none of the conditions are fulfilled, the instructions (<Instructions0>) after ELSE are executed followed by the execution of the program after END_IF. You can nest as many combinations of ELSIF and THEN as you like within the IF instruction. The programming of an ELSE branch is optional. The syntax of the IF instruction consists of the following parts: Parameter Data type Description <Condition> BOOL Expression to be evaluated <Instructions> - Instructions to be executed with satisfied condition. An exception are instructions programmed after the ELSE. These are executed if no condition within the program loop is satisfied. For additional information on valid data types, refer to "See also". Example The following example shows how the instruction works: SCL IF "Tag_1" = 1 THEN "Tag_Value" := ELSIF "Tag_2" = 1 THEN "Tag_Value" := ELSIF "Tag_3" = 1 THEN "Tag_Value" := ELSE "Tag_Value" := END_IF; 10; 20; 30; 0; The following table shows how the instruction works using specific operand values: Operand WinCC Basic V13.0 System Manual, 02/2014 Value Tag_1 1 0 0 0 Tag_2 0 1 0 0 2441 Programming the PLC 9.7 References Operand Value Tag_3 0 0 1 0 Tag_Value 10 20 30 0 See also Operators and operator precedence (Page 1486) Overview of the valid data types (Page 1204) CASE: Create multiway branch Description The instruction "Create multiway branch" executes one of several instruction sequences depending on the value of a numerical expression. The value of the expression must be an integer. When the instruction is executed, the value of the expression is compared with the values of several constants. If the value of the expression agrees with the value of a constant, the instructions programmed directly after this constant are executed. The constants can assume the following values: An integer (for example, 5) A range of integers (for example, 15..20) An enumeration consisting of integers and ranges (for example, 10, 11, 15..20) Syntax The following syntax is used for the "Create multiway branch" instruction: SCL CASE <expression> OF <Constant1>: <Instructions1> <Constant2>: <Instructions2> <ConstantX>: <InstructionsX>; // X >=3 ELSE <Instructions0>; END_CASE; The syntax of the instruction consists of the following parts: 2442 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameter Data type Description <expression> Integers Value which is compared to the programmed constant values. <Constant> Integers Constant values which form the condition for the execution of an instruction sequence. The constants can assume the following values: An integer (for example, 5) A range of integers (for example, 15..20) An enumeration consisting of integers and ranges (for example, 10, 11, 15..20) <Instruction> - Any instructions which are executed if the value of the expression agrees with the value of a constant. An exception are instructions programmed after the ELSE. These instructions are executed if the values do not agree. For additional information on valid data types, refer to "See also". If the value of the expression agrees with the value of the first constant (<Constant1>), the instructions (<Instructions1>) which are programmed directly after the first constant are executed. Program execution subsequently resumes after the END_CASE. If the value of the expression does not agree with the value of the first constant (<Constant1>), this value is compared to the value of the constant which is programmed next. In this way, the CASE instruction is executed until the values agree. If the value of the expression does not correspond to any of the programmed constant values, the instructions (<Instructions0>) which are programmed after the ELSE are executed. ELSE is an optional part of the syntax and can be omitted. The CASE instruction can also be nested by replacing an instruction block with CASE. END_CASE represents the end of the CASE instruction. Example The following example shows how the instruction works: SCL CASE "Tag_Value" OF 0 : "Tag_1" := 1; 1,3,5 : "Tag_2" :=1; 6..10 : "Tag_3" := 1; 16,17,20..25 : "Tag_4" := 1; ELSE "Tag_5" := 1; END_CASE; The following table shows how the instruction works using specific operand values: WinCC Basic V13.0 System Manual, 02/2014 2443 Programming the PLC 9.7 References Operand Values Tag_Value 0 1, 3 , 5 6, 7, 8, 9, 10 16,17, 20, 21, 22, 23, 24, 25 2 Tag_1 1 - - - - Tag_2 - 1 - - - Tag_3 - - 1 - - Tag_4 - - - 1 - Tag_5 - - - - 1 1: The operand is set to the signal state "1". -: The signal state of the operand remains unaltered. See also CONTINUE: Recheck loop condition (Page 2449) Overview of the valid data types (Page 1204) Operators and operator precedence (Page 1486) EXIT: Exit loop immediately (Page 2450) FOR: Run in counting loop Description The instruction "Run in counting loop" causes repeated execution of a program loop until a loop variable lies within a specified value range. Program loops can also be nested. Within a program loop, you can program additional program loops with other loop variables. The current continuous run of a program loop can be ended by the instruction "Recheck loop condition" (CONTINUE). The instruction "Exit loop immediately" (EXIT) ends the entire loop execution. For additional information on this topic, refer to "See also". Limits for FOR statements To program "safe" FOR statements that do not run endlessly, observe the following rules and limits: Rule FOR ii := Start TO End BY Step DO 2444 If ... ... then Note start < end end < (PMAX step) Run tag ii runs in a positive direction start > end AND step < O end > (NMAX step) Run tag ii runs in a negative direction WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Limits Different limits apply to the possible data types: Data type PMAX NMAX ii of type SINT 127 -128 ii of type INT 32767 -32768 ii of type DINT 2147483647 -2147483648 ii of type LINT 9223372036854775807 -9223372036854775808 Syntax The following syntax is used for the "Run in counting loop" instruction: SCL FOR<Run_tag> := <Start_value> TO<End_value> BY<Increment> DO<Instructions> END_FOR; Parameter The following table shows the parameters of the "Run in counting loop" instruction: Parameter Data type Description S7-1200 S7-1500 <Run tag> SINT, INT, DINT SINT, INT, DINT, LINT Operand whose value is evaluated with the loop execution. The data type of the loop variable determines the data type of the other parameters. <Start value> SINT, INT, DINT SINT, INT, DINT, LINT Expression whose value is allocated at the start of the loop execution of the loop variables. <End value> SINT, INT, DINT SINT, INT, DINT, LINT Expression whose value defines the last run of the program loop. The value of the loop variable is checked before each loop: End value not reached: The instructions according to DO are executed End value is reached: The FOR loop is executed one last time End value exceeded: The FOR loop is completed An alteration to the end value is not permitted during execution of the instruction. WinCC Basic V13.0 System Manual, 02/2014 2445 Programming the PLC 9.7 References Parameter <Increment> Data type S7-1200 S7-1500 SINT, INT, DINT SINT, INT, DINT, LINT Description Expression by whose value the loop variable is increased (positive increment) or decreased (negative increment) after each loop. Specification of the increment is optional. If no increment is given, the value of the loop variable is increased by 1 after each loop. An alteration of the increment is not permitted during execution of the instruction. <Instructions> - - Instructions which are carried out with each loop, as long as the value of the loop variable lies within the value range. The value range is defined by the start and end values. For additional information on valid data types, refer to "See also". Example The following example shows how the instruction works: SCL FOR i := 2 TO 8 BY 2 DO "a_array[i] := "Tag_Value"*"b_array[i]"; END_FOR; The operand "Tag_Value" is multiplied with the elements (2, 4, 6, 8) of the ARRAY tag "b_array". The result is read in to the elements (2, 4, 6, 8) of the ARRAY tag "a_array". See also CONTINUE: Recheck loop condition (Page 2449) EXIT: Exit loop immediately (Page 2450) Overview of the valid data types (Page 1204) Operators and operator precedence (Page 1486) WHILE: Run if condition is met Description The instruction "Run if condition is met" causes a program loop to be repeatedly executed until the implementation condition is satisfied. The condition is an expression with Boolean value (TRUE or FALSE). Logical expression or comparative expressions can be stated as conditions. When the instruction is executed, the stated expressions are evaluated. If the value of an expression is TRUE, the condition is fulfilled; if the value is FALSE, it is not fulfilled. Program loops can also be nested. Within a program loop, you can program additional program loops with other loop variables. 2446 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References The current continuous run of a program loop can be ended by the instruction "Recheck loop condition" (CONTINUE). The instruction "Exit loop immediately" (EXIT) ends the entire loop execution. For additional information on this topic, refer to "See also". Syntax The following syntax is used for the "Run if condition is met" instruction: SCL WHILE <Condition> DO <Instructions> END_WHILE; The syntax of the WHILE instruction consists of the following parts: Parameter Data type Description <Condition> BOOL Expression which is evaluated before each loop. <Instructions> - Instructions to be executed with satisfied condition. If the condition has not been satisfied, program execution continues after END_WHILE. For additional information on valid data types, refer to "See also". Example The following example shows how the instruction works: SCL WHILE "Tag_Value1" <> "Tag_Value2" DO "Tag_Result" := "Tag_Input"; END_WHILE; As long as the values of the operands "Tag_Value1" and "Tag_Value2" do not match, the value of the operand "Tag_Input" is allocated to the operand "Tag_Result". See also EXIT: Exit loop immediately (Page 2450) Operators and operator precedence (Page 1486) CONTINUE: Recheck loop condition (Page 2449) Overview of the valid data types (Page 1204) WinCC Basic V13.0 System Manual, 02/2014 2447 Programming the PLC 9.7 References REPEAT: Run if condition is not met Description The instruction "Run if condition is not met" causes a program loop to be repeatedly executed until a termination condition is met. The condition is an expression with Boolean value (TRUE or FALSE). Logical expression or comparative expressions can be stated as conditions. When the instruction is executed, the stated expressions are evaluated. If the value of an expression is TRUE, the condition is fulfilled; if the value is FALSE, it is not fulfilled. The instructions are executed once, even if the termination condition is fulfilled. Program loops can also be nested. Within a program loop, you can program additional program loops with other loop variables. The current continuous run of a program loop can be ended by the instruction "Recheck loop condition" (CONTINUE). The instruction "Exit loop immediately" (EXIT) ends the entire loop execution. For additional information on this topic, refer to "See also". Syntax The following syntax is used for the "Run if condition is not met" instruction: SCL REPEAT <Instructions> UNTIL <Condition>END_REPEAT; The syntax of the REPEAT instruction consists of the following parts: Parameter Data type Description <Instructions> - Instructions that are executed as long as the programmed condition has the value FALSE. The instructions are executed once, even if the termination condition is fulfilled. <Condition> BOOL Expression which is evaluated after each loop. If the expression has the value FALSE, the program loop is executed once again. If the expression has the value TRUE, the program loop continues after END_REPEAT. For additional information on valid data types, refer to "See also". Example The following example shows how the instruction works: SCL REPEAT "Tag_Result" := "Tag_Value"; UNTIL "Tag_Error" END_REPEAT; 2448 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References As long as the value of the operand "Tag_Error" has the signal state "0", the value of the operand "Tag_Value" is allocated to the operand "Tag_Result". See also CONTINUE: Recheck loop condition (Page 2449) EXIT: Exit loop immediately (Page 2450) Operators and operator precedence (Page 1486) Overview of the valid data types (Page 1204) CONTINUE: Recheck loop condition Description The "Recheck loop condition" instruction ends the current program run of a FOR, WHILE or REPEAT loop. After execution of the instruction, the conditions for the continuation of the program loop are evaluated again. The instruction affects the program loop which directly contains the instruction. Syntax The following syntax is used for the "Recheck loop condition" instruction: SCL CONTINUE; Example The following example shows how the instruction works: SCL FOR i := 1 TO 15 BY 2 DO IF (i < 5) THEN CONTINUE; END_IF; "DB10".Test[i] := 1; END_FOR; For additional information on valid data types, refer to "See also". If the condition i < 5 is satisfied, then the subsequent value allocation ("DB10".Test[i] := 1) will not be executed. The run variable (i) is increased by the increment of "2" and checked to see whether its current value lies in the programmed value range. If the run variable lies in the value range, the IF condition is evaluated again. WinCC Basic V13.0 System Manual, 02/2014 2449 Programming the PLC 9.7 References If the condition i < 5 is not satisfied, then the subsequent value allocation ("DB10".Test[i] := 1) will be executed and a new loop started. In this case, the run variable is also increased by the increment "2" and checked. See also Operators and operator precedence (Page 1486) EXIT: Exit loop immediately (Page 2450) Overview of the valid data types (Page 1204) EXIT: Exit loop immediately Description The instruction "Exit loop immediately" cancels the execution of a FOR, WHILE or REPEAT loop at any point regardless of conditions. The execution of the program is continued after the end of the loop (END_FOR, END_WHILE, END_REPEAT). The instruction affects the program loop which directly contains the instruction. Syntax The following syntax is used for the "Exit loop immediately" instruction: SCL EXIT; Example The following example shows how the instruction works: SCL FOR i := 15 TO 1 BY -2 DO IF (i < 5) THEN EXIT; END_IF; "DB10".Test[i] := 1; END_FOR; For additional information on valid data types, refer to "See also". If the condition i < 5 is satisfied, then the execution of the loop will be cancelled. Program execution resumes after the END_FOR. If the condition i < 5 is not satisfied, then the subsequent value allocation ("DB10".Test[i] := 1) will be executed and a new loop started. The run tag (i) is decreased by the increment of "-2" and it is checked whether its current value lies in the programmed value range. If the (i) run variable lies within the value range, the IF condition is evaluated again. 2450 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References See also Operators and operator precedence (Page 1486) CONTINUE: Recheck loop condition (Page 2449) Overview of the valid data types (Page 1204) GOTO: Jump Description Use the instruction "Jump" to resume the execution of a program at a given point marked with a jump label. The jump labels and the instruction "Jump" must be in the same block. The name of a jump label can only be assigned once within a block. Each jump label can be the target of several jump instructions. A jump from the "outside" into a program loop is not permitted, but a jump from a loop to the "outside" is possible. Syntax Use the following syntax for the "Jump" instruction: SCL GOTO <Jump label> ... <Jump label>: <Instructions> The syntax of the GOTO instruction consists of the following parts: Parameter Data type Description <jump label> - Jump label to be jumped to <Instructions> - Instructions which are executed after the jump. Example The following example shows how the instruction works: SCL CASE "Tag_Value" OF 1 : GOTO MyLABEL1; 2 : GOTO MyLABEL2; 3 : GOTO MyLABEL3; ELSE GOTO MyLABEL4; END_CASE; MyLABEL1: "Tag_1" := 1; WinCC Basic V13.0 System Manual, 02/2014 2451 Programming the PLC 9.7 References SCL MyLABEL2: "Tag_2" := 1; MyLABEL3: "Tag_3" := 1; MyLABEL4: "Tag_4" := 1; Depending on the value of the "Tag_Value" operand, the execution of the program will resume at the point identified by the corresponding jump label. If the operand "Tag_Value" has the value 2, for example, program execution will resume at the jump label "MyLABEL2". The program line identified by the jump label "MyLABEL1" will be skipped in this case. See also Operators and operator precedence (Page 1486) Overview of the valid data types (Page 1204) RETURN: Exit block Description The instruction "Exit block" exits the program execution in the currently edited block and continues in the calling block. The instruction can be omitted at the end of the block. Syntax The following syntax is used for the "Exit block" instruction: SCL RETURN; Example The following example shows how the instruction works: SCL IF "Tag_Error" <>0 THEN RETURN; END_IF; If the signal state of the "Tag_Error" operand is not zero, execution of the program ends in the block currently being processed. See also Operators and operator precedence (Page 1486) Overview of the valid data types (Page 1204) 2452 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References (*...*): Inserting a comment section Description You can use the "Insert comment section" instruction to add a comment section. The text within the parenthesis "(*...*)" is handled as a comment. Syntax The following syntax is used for the "Insert comment section" instruction: SCL (*...*) Example The following example shows how the instruction works: SCL (*This is a comment section.*) See also Operators and operator precedence (Page 1486) Overview of the valid data types (Page 1204) Runtime control ENDIS_PW: Limit and enable password legitimation Description You use the "Limit and enable password legitimation" instruction to specify whether passwords configured for the CPU are legitimized or not. In this way, you can prevent legitimized connections, even if the correct password is known. When you call the instruction and the REQ parameter has the signal state "0", the currently set state is displayed at the output parameters. If changes have been made to the input parameters, these are not transferred to the output parameters. When you call the instruction and the REQ parameter has the signal state "1", the signal state is taken from the input parameters (F_PWD, FULL_PWD, R_PWD, HMI_PWD). FALSE means that legitimation per password is not permitted; TRUE means the password can be used. Disable or enabling of the passwords can be allowed or prohibited individually. For example, all passwords can be prohibited except the fail-safe password. You can thus limit access options to a small user group. The output parameters (F_PWD_ON, FULL_PWD_ON, WinCC Basic V13.0 System Manual, 02/2014 2453 Programming the PLC 9.7 References R_PWD_ON, HMI_PWD_ON) always show the current status of the password use, regardless of the REQ parameter. Passwords that are not configured must have the signal state TRUE at the input and return the signal state TRUE at the output. The fail-safe password can only be configured for an FCPU and must therefore always be interconnected with the signal state TRUE in a standard CPU. If the instruction returns an error, the call has no effect and the previous lock is still in effect. Disabled passwords can be enabled again under the following conditions: The CPU is reset to its factory settings. The front panel of the S7-1500 CPU supports a dialog that allows you to navigate to the appropriate menu in which the passwords can be enabled again. When you call the "Limit and enable password legitimation" instruction, the input parameter of the desired password has the signal state "1". Set the mode selector to STOP. The restriction to password legitimation is re-established as soon as the switch is set back to RUN. Plugging an empty memory card (transfer module or program card) into an S7-1200 CPU. The transition from POWER OFF to POWER ON disables the protection in the S7-1200 CPU. The "Limit and enable password legitimation" instruction must be called once again in the program (e.g. in the startup OB). Note The "Limit and enable password legitimation" instruction blocks access from HMI systems if the HMI password has not been enabled. Note Existing legitimized connections retain their access rights and you cannot use the "Limit and enable password legitimation" instruction to restrict them. Preventing accidental lockout of an S7-1500 CPU The settings can be made on the front panel of the CPU and the CPU saves the most recent setting. To prevent accidental lockout, the protection can be disabled by setting the mode switch to STOP with an S7-1500 CPU. The protection is automatically enabled again by setting mode selector to RUN without having to call the "Limit and enable password legitimation" instruction again or taking additional actions on the front panel. Preventing accidental lockout of an S7-1200 CPU Because the S7-1200 CPU does not have a mode switch, protection is disabled with POWER OFF - POWER ON. This means that it is possible and advisable to prevent accidental lockout with the help of specific program sequences within your program. 2454 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References To do so, program a time control either by means of a cyclic interrupt OB or a timer in the Main OB (OB 1). This gives you the option of calling the "Limit and enable password legitimation" instruction in the respective OB (e.g., OB 1 or OB 35) relatively quickly after a transition from POWER OFF to POWER ON and the associated disabling of the protection. Call the instruction in the startup OB (OB 100) to keep the time window in which the instruction is inactive and there are no limitations for password legitimation relatively small. This procedure will give you the best possible protection from unauthorized access. If there has been an accidental lockout, you can skip the call in the startup OB (by querying an input parameter, for example) and you have the set time (for example, 10 seconds up to 1 minute) to establish a connection to the CPU before the lock becomes active once again. If there is no timer in your program code and a lockout has occurred, insert an empty transfer card or an empty program card into the CPU. The empty transfer card or program card deletes the internal load memory of the CPU. You must then download the user program once again from STEP 7 to the CPU. Procedure for lost passwords with an S7-1200 CPU If you have lost the password for a password-protected S7-1200 CPU, delete the passwordprotected program with an empty transfer card or program card. The empty transfer card or program card deletes the internal load memory of the CPU. You can then load a new user program from STEP 7 Basic in the CPU. WARNING Inserting an empty transfer card When you insert a transfer card in a CPU during runtime, the CPU goes to STOP mode. If operating states are unstable, controllers may fail and thus cause the uncontrolled operation of the controlled devices. This leads to an unforeseen operation of the automation system which can cause deadly or serious injuries and/or damage to property. Once you have pulled the transfer card, the content of the transfer card is available in the internal load memory. Make sure that the card does not include a program at this point. WARNING Inserting an empty program card When you insert a program card in a CPU during runtime, the CPU goes to STOP mode. If operating states are unstable, controllers may fail and thus cause the uncontrolled operation of the controlled devices. This leads to an unforeseen operation of the automation system which can cause deadly or serious injuries and/or damage to property. Make sure that the program card is empty. The internal load memory is copied to the empty program card. Once you have pulled the previously empty program card, the internal load memory is empty. You must remove the transfer card or program card before you put the CPU into RUN mode. WinCC Basic V13.0 System Manual, 02/2014 2455 Programming the PLC 9.7 References Effects of password use on the operating modes The following table shows what effects the password use by means of the "Limit and enable password legitimation" instruction has on the operating modes and the corresponding user actions. Action Password protection by means of the instruction Basic state after Not activated Operating mode switch to STOP (no restrictions) Reset memory manually (PG, switch, change of MC (Motion Control)) Reset to factory setting Basic state after POWER ON S7-1200 CPU: The lock is disabled and the instruction must be called once again in the program (e.g., in the startup OB). S7-1500 CPU: Enabled (if a lock was activated before POWER OFF). The option of not allowing passwords is retentive. Operating mode transition RUN/STARTUP/HOLD -> STOP (by terminating the instruction, an error or communication) or STOP -> STARTUP/RUN/HOLD Activated Passwords still cannot be used. Syntax The following syntax is used for the "Limit and enable password legitimation" instruction: SCL ENDIS_PW(REQ := <Operand>, F_PWD := <Operand>, FULL_PWD := <Operand>, R_PWD := <Operand>, HMI_PWD := <Operand>, F_PWD_ON => <Operand>, FULL_PWD_ON => <Operand>, R_PWD_ON => <Operand>, HMI_PWD_ON => <Operand>, RET_VAL => <Operand>) 2456 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameter The following table shows the parameters of the "Limit and enable password legitimation" instruction: Parameter Declaratio n Data type Memory area Description REQ Input BOOL I, Q, M, D, L When the REQ parameter has the signal state "0", the currently set signal state of the passwords is queried. F_PWD Input BOOL I, Q, M, D, L Read/write access including fail-safe F_PWD = "0": Do not allow password F_PWD = "1": Allow password FULL_PW D Input BOOL I, Q, M, D, L Read/write access FULL_PWD = "0": Do not allow password FULL_PWD = "1": Allow password R_PWD Input BOOL I, Q, M, D, L Read access R_PWD = "0": Do not allow password R_PWD = "1": Allow password HMI_PWD Input BOOL I, Q, M, D, L HMI access HMI_PWD = "0": Do not allow password HMI_PWD = "1": Allow password F_PWD_O Output N BOOL FULL_PW D_ON BOOL I, Q, M, D, L Read/write access including fail-safe F_PWD_ON = "0": Password not allowed F_PWD_ON = "1": Password allowed Output I, Q, M, D, L Read/write access status FULL_PWD_ON = "0": Password not allowed FULL_PWD_ON = "1": Password allowed R_PWD_ ON Output BOOL I, Q, M, D, L Read-access status R_PWD_ON = "0": Password not allowed R_PWD_ON = "1": Password allowed HMI_PWD Output _ON BOOL RET_VAL WORD I, Q, M, D, L HMI-access status HMI_PWD_ON = "0": Password not allowed HMI_PWD_ON = "1": Password allowed Output I, Q, M, D, L Error information For additional information on valid data types, refer to "See also". RET_VAL parameter The following table shows the meaning of the values of the RET_VAL parameter: Error code* Explanation (W#16#...) WinCC Basic V13.0 System Manual, 02/2014 0000 No error 8090 The "Limit and enable password legitimation" instruction is not supported 2457 Programming the PLC 9.7 References Error code* Explanation (W#16#...) 80D0 The password for fail-safe is not configured. The signal state must be TRUE for standard CPUs. 80D1 The read/write access is not configured 80D2 The read access is not configured 80D3 The HMI access is not configured *The error codes can be displayed as integer or hexadecimal value in the program editor. For information on toggling display formats, refer to "See also". RE_TRIGR: Restart cycle monitoring time Description The instruction "Restart cycle monitoring time" restarts the cycle monitoring of the CPU. The cycle time monitoring then restarts with the time you have set in the CPU configuration. The instruction "Restart cycle monitoring time" can be called, regardless of the priority, in all blocks. If the instruction is called in a block with a higher priority, such as a hardware interrupt, diagnostic interrupt, or cyclic interrupt, the instruction is not executed and the ENO enable output is set to signal state "0". The instruction "Restart cycle monitoring time" can be called a maximum of 10 times in a program cycle. Note If the instruction "Restart cycle monitoring time" is started more than 30 times within a LOOP instruction, the CPU switches to STOP because of a runtime error. Syntax The following syntax is used for the "Restart cycle monitoring time" instruction: SCL RE_TRIGR() STP: Exit program Description The "Exit program" instruction is used to set the CPU to STOP mode and therefore to terminate the execution of the program. The effects of changing from RUN to STOP depend on the CPU configuration. 2458 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Syntax The following syntax is used for the instruction "Exit program": SCL STP() GET_ERROR: Get error locally Description The "Get error locally" instruction is used to query the occurrence of errors within a block. This is usually to access error. If the system reports an error during the processing of the block, detailed information is generated for the first error to occur during the execution of the block since the last execution of the instruction. The error information can only be saved in operands of the "ErrorStruct" system data type. The "ErrorStruct" system data type specifies the exact structure in which the information about the error is stored. Using additional instructions, you can evaluate this structure and program an appropriate response. If several errors occur in the block, the error information about the next error to occur in the instruction is output only after the first error that occurred has been remedied. Note The <Operand> is only changed if error information is present. To set the operand back to "0" after handling the error, you have the following options: Declare the operand in the "Temp" section of the block interface. Reset the operand to "0" before calling the instruction. You can find an example of how you can implement the instruction in combination with other troubleshooting options under "See also". Note The "Get error locally" instruction enables local error handling within a block. If "Get error locally" is inserted in the program code of a block, any predefined system reactions are ignored if errors occur. Syntax The following syntax is used for the "Get error locally" instruction: SCL GET_ERROR(<Operand>) WinCC Basic V13.0 System Manual, 02/2014 2459 Programming the PLC 9.7 References Parameter The following table shows the parameters of the "Get error locally" instruction: Parameter Data type Description <Operand> ErrorStruct Information about errors that have occurred Data type "ErrorStruct" The following table shows the structure of the "ErrorStruct" data type: Structure component Data type Description ERROR_ID WORD Error ID FLAGS BYTE Shows if an error occurred during a block call. 16#01: Error during a block call 16#00: No error during a block call REACTION BYTE Default reaction: 0: Ignore (write error), 1: Continue with substitute value "0" (read error), 2: Skip instruction (system error) CODE_ADDRESS BLOCK_TYPE CREF Information about the address and type of block BYTE Type of block where the error occurred: 1: OB 2: FC 3: FB CB_NUMBER UINT Number of the code block OFFSET UDINT Reference to the internal memory MODE BYTE Information about the address of an operand OPERAND_NUMBER UINT Operand number of the machine command POINTER_NUMBER_LOCATION UINT (A) Internal pointer SLOT_NUMBER_SCOPE UINT (B) Storage area in internal memory DATA_ADDRESS NREF Information about the address of an operand 2460 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Structure component AREA Data type Description BYTE (C) Memory area: L: 16#40 - 4E, 86, 87, 8E, 8F, C0 - CE I: 16#81 Q: 16#82 M: 16#83 DB: 16#84, 85, 8A, 8B Range violations for a directly editable tag of data type DINT: 16#04 DB_NUMBER UINT (D) Number of the data block OFFSET UDINT (E) Relative address of the operand Structure component "ERROR_ID" The following table shows the values that can be output at the structure component "ERROR_ID": WinCC Basic V13.0 System Manual, 02/2014 ID* (hexadecimal) ID* (decimal) Description 0 0 No error 2503 9475 Invalid pointer 2520 9504 Invalid STRING 2522 9506 Read error: Operand outside the valid range 2523 9507 Write error: Operand outside the valid range 2524 9508 Read error: Invalid operand 2525 9509 Write error: Invalid operand 2528 9512 Read error: Data alignment 2529 9513 Write error: Data alignment 252C 9516 Invalid pointer 2530 9520 Write error: Data block 2533 9523 Invalid pointer used 2538 9528 Access error: DB does not exist 2539 9529 Access error: Wrong DB used 253A 9530 Global data block does not exist 253C 9532 Faulty information or the function does not exist 253D 9533 System function does not exist 253E 9534 Faulty information or the function block does not exist 253F 9535 System block does not exist 2550 9552 Access error: DB does not exist 2551 9553 Access error: Wrong DB used 2575 9589 Error in the program nesting depth 2576 9590 Error in the local data distribution 2577 9591 The block property "Parameter passing via registers" is not selected. 2461 Programming the PLC 9.7 References ID* (hexadecimal) ID* (decimal) Description 25A0 9632 Internal error in TP 25A1 9633 Tag is write-protected 25A2 9634 Invalid numerical value of tag 2942 10562 Read error: Input 2943 10563 Write error: Output *The error codes can be displayed as integer or hexadecimal value in the program editor. For information on toggling display formats, refer to "See also". Example The following example shows how the instruction works: SCL LABEL: #TagOut := #Field[#index] * REAL#40.5; GET_ERROR(#Error); IF #Error.REACTION = 1 THEN GOTO LABEL; ; END_IF; An error occurred accessing the "#Field[#index]" tag. The "#TagOut" operand returns the signal state "1" despite the read/access error and the multiplication is performed with the value "0.0". If this error scenario occurs, we recommend that you program the "Get error locally" instruction after the multiplication to get the error. The error information supplied by the "Get error locally" instruction is evaluated with a comparison. If the "#Error.REACTION" structure component has the value "1", there is a read/access error and the program execution begins again at the jump label LABEL. See also Querying and fixing errors in the program code (Page 170) GET_ERR_ID: Get error ID locally Description The "Get error ID locally" instruction is used to query the occurrence of errors within a block. This is usually to access error. If the system reports during the block processing errors within the block execution since the last execution of the instruction, the instruction outputs the error ID of the first error that occurred. 2462 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References The error ID can only be saved in operands of the WORD data type. If several errors occur in the block, the error ID of the next error to occur in the instruction is output only after the first error that occurred has been remedied. Note The <Operand> is only changed if error information is present. To set the operand back to "0" after handling the error, you have the following options: Declare the operand in the "Temp" section of the block interface. Reset the operand to "0" before calling the instruction. The output of the "Get error ID locally" instruction is only set if error information is present. If one of these conditions is not fulfilled, the remaining program execution is not affected by the "Get error ID locally" instruction. You can find an example of how you can implement the instruction in combination with other troubleshooting options under "See also". Note The "Get error ID locally" instruction enables local error handling within a block. If the "Get error ID locally" instruction is inserted in the program code of a block, any predefined system reactions are ignored if errors occur. Syntax The following syntax is used for the "Get error ID locally" instruction: SCL GET_ERR_ID() Parameter The following table shows the parameters of the "Get error ID locally" instruction: Parameter Data type Description Function value WORD Error ID Error ID The following table shows the values that can be output: WinCC Basic V13.0 System Manual, 02/2014 ID* (hexadecimal) ID* (decimal) Description 0 0 No error 2503 9475 Invalid pointer 2463 Programming the PLC 9.7 References ID* (hexadecimal) ID* (decimal) Description 2520 9504 Invalid STRING 2522 9506 Read error: Operand outside the valid range 2523 9507 Write error: Operand outside the valid range 2524 9508 Read error: Invalid operand 2525 9509 Write error: Invalid operand 2528 9512 Read error: Data alignment 2529 9513 Write error: Data alignment 252C 9516 Invalid pointer 2530 9520 Write error: Data block 2533 9523 Invalid pointer used 2538 9528 Access error: DB does not exist 2539 9529 Access error: Wrong DB used 253A 9530 Global data block does not exist 253C 9532 Faulty information or the function does not exist 253D 9533 System function does not exist 253E 9534 Faulty information or the function block does not exist 253F 9535 System block does not exist 2550 9552 Access error: DB does not exist 2551 9553 Access error: Wrong DB used 2575 9589 Error in the program nesting depth 2576 9590 Error in the local data distribution 2577 9591 The block property "Parameter passing via registers" is not selected. 25A0 9632 Internal error in TP 25A1 9633 Tag is write-protected 25A2 9634 Invalid numerical value of tag 2942 10562 Read error: Input 2943 10563 Write error: Output *The error codes can be displayed as integer or hexadecimal value in the program editor. For information on toggling display formats, refer to "See also". Example The following example shows how the instruction works: SCL #TagOut := #Field[#index] * REAL#40.5; #TagID := GET_ERR_ID(); IF #TagID = 16#2522 THEN MOVE_BLK(IN := #TagArrayIn[0], COUNT := 1, 2464 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References SCL OUT => #TagArrayOut[1]); END_IF; An error occurred accessing the "#Field[#index]" tag. The "#TagOut" operand returns the signal state "1" despite the read/access error and the multiplication is performed with the value "0.0". If this error scenario occurs, we recommend that you program the "Get error ID locally" instruction after the multiplication to get the error. The error ID supplied by the "Get error ID locally" instruction is evaluated with a comparison. If the "#TagID" operand returns ID 16#2522, there is a read/access error and the value "100.0" of the "#TagArrayIn[0]" operand is written to the "#TagArrayOut[1]" operand. See also Querying and fixing errors in the program code (Page 170) INIT_RD: Initialize all retain data Description The "Initialize all retain data" instruction is used to reset the retentive data of all data blocks, bit memories and SIMATIC timers and counters at the same time. The instruction can only be executed within a startup OB because the execution exceeds the program cycle duration. Syntax Use the following syntax for the "Initialize all retain data" instruction: SCL INIT_RD(REQ := <Operand> RET_VAL := <Operand>) Parameter The following table shows the parameters of the "Initialize all retain data" instruction: Parameter Declaration Data type Description REQ Input BOOL If the input "REQ" has the signal state "1", all retentive data are reset. RET_VAL Output INT Error information: If an error occurs during the execution of the instruction, an error code is output at the RET_VAL parameter. For additional information on valid data types, refer to "See also". WinCC Basic V13.0 System Manual, 02/2014 2465 Programming the PLC 9.7 References RET_VAL Parameter The following table shows the meaning of the values of the parameter RET_VAL: Error code* (W#16#...) Explanation 0000 No error 80B5 The instruction cannot be executed because it was not programmed within a startup OB. General error information See also: "GET_ERR_ID: Get error ID locally *The error codes can be displayed as integer or hexadecimal value in the program editor. For information on toggling display formats, refer to "See also". Example The following example shows how the instruction works: SCL INIT_RD(REQ := "Tag_REQ", RET_VAL := "Tag_Result"); If the operand "Tag_REQ" has the signal state "1", the instruction is executed. All retentive data of all data blocks, bit memories and SIMATIC timers and counters are reset. See also Overview of the valid data types (Page 1204) GET_ERR_ID: Get error ID locally (Page 2462) WAIT: Configure time delay Description The instruction "Configure time delay" pauses the program execution for a specific period of time. You indicate the period of time in microseconds on the WT parameter of the instruction. You can configure time delays of up to 32 767 microseconds (s). The shortest possible time delay depends on the respective CPU and corresponds to the execution time of the instruction "Configure time delay". The execution of the instruction can be interrupted by higher priority events. The instruction "Configure time delay" supplies no error information. 2466 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Syntax The following syntax is used for the instruction "Configure time delay": SCL WAIT(WT:= <Operand>) The syntax of the instruction consists of the following parts: Parameter Declaration Data type Description WT Input INT Time delay in microseconds (s) See also Overview of the valid data types (Page 1204) RUNTIME: Measure program runtime Description The "Measure program runtime" instruction is used to measure the runtime of the entire program, individual blocks or command sequences. If you want to measure the runtime of your entire program, call the instruction "Measure program runtime" in OB1. Measurement of the runtime is started with the first call and the output RET_VAL returns the runtime of the program after the second call. The measured runtime includes all CPU processes that can occur during the program execution, for example, interruptions caused by higher-level events or communication. The instruction "Measure program runtime" reads an internal counter of the CPU and writes the value to the in/out parameter. The instruction calculates the current program runtime according to the internal counter frequency and writes it to output RET_VAL. If you want to measure the runtime of individual blocks or individual command sequences, you need three separate networks. Call the instruction "Measure program runtime" in an individual network within your program. You set the starting point of the runtime measurement with this first call of the instruction. Then you call the required program block or the command sequence in the next network. In another network, call the "Measure program runtime" instruction a second time and assign the same memory to the in/out parameter as you did during the first call of the instruction. The "Measure program runtime" instruction in the third network reads an internal CPU counter and calculates the current runtime of the program block or the command sequence according to the internal counter frequency and writes it to the output RET_VAL. WinCC Basic V13.0 System Manual, 02/2014 2467 Programming the PLC 9.7 References The "Measure program runtime" instruction uses an internal high-frequency counter to calculate the time. If the counter overruns, the instruction returns values <= 0.0. Ignore these runtime values. Note The runtime of a command sequence cannot be determined exactly, because the sequence of instructions within a command sequence is changed during optimized compilation of the program. Syntax The following syntax is used for the "Measure program runtime" instruction: SCL RUNTIME(<Operand>) The syntax of the instruction consists of the following parts: Parameter Declaration Data type Description <Operand> InOut LREAL Saves the starting point of the runtime measurement. LREAL Returns the measured runtime in seconds Function value For additional information on valid data types, refer to "See also". Example The following example shows the how the instruction works based on the runtime calculation of a program block: SCL "Tag_Result" := RUNTIME("Tag_Memory"); "Best_before_date_DB" (); "Tag_Result" := RUNTIME("Tag_Memory"); The starting point for the runtime measurement is set with the first call of the instruction and buffered as reference for the second call of the instruction in the "TagMemory" operand. The "Best_before_date" program block FB1 is called. When the program block FB1 has been processed, the instruction is executed a second time. The second call of the instruction calculates the runtime of the program block and writes the result to the output "Tag_Result". 2468 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References See also Overview of the valid data types (Page 1204) Word logic operations DECO: Decode Description The instruction "Decode" sets a bit specified by the input value in the output value. The instruction "Decode" reads the value of the parameter IN and sets the bit in the output value, whose bit position corresponds to the read value. The other bits in the output value are filled with zeroes. If the value of the IN parameter is greater than 31, a modulo 32 instruction is executed. Syntax The following syntax is used for the instruction "Decode": SCL DECO(IN := <Expression>) DECO_WORD(IN := <Expression>) The syntax of the instruction consists of the following parts: Parameter Declaration Data type Description IN Input UINT Position of the bit in the output value which is set. Bit strings default: DWORD Data type of the function value: _<Data type> You do not need to specify the data type if using the default. Any other valid data type you may use must be declared explicitly. Function value Bit strings Current output value For additional information on valid data types, refer to "See also". WinCC Basic V13.0 System Manual, 02/2014 2469 Programming the PLC 9.7 References Example The following example shows how the instruction works: SCL "Tag_Result" := DECO(IN := "Tag_Value"); "Tag_Result2" := DECO_BYTE(IN := "Tag_Value2"); The following figure shows how the instruction works using specific operand values: 7DJB9DOXH 7DJB5HVXOW The instruction reads the number "3" from the value of the operand "Tag_Value" and sets the third bit to the value of the operand "Tag_Result". See also Overview of the valid data types (Page 1204) Operators and operator precedence (Page 1486) ENCO: Encode Description The instruction "Encode" reads the bit number of the lowest-value bit set in the input value and issues this as a result. Syntax The following syntax is used for the instruction "Encode": SCL ENCO(IN := <Expression>) The syntax of the instruction consists of the following parts: Parameter Declaration Data type Description IN Input Bit strings Input value INT Bit number of the bit in the input value that is read out. Function value For additional information on valid data types, refer to "See also". 2470 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Example The following example shows how the instruction works: SCL "Tag_Result" := ENCO(IN := "Tag_Value"); The following figure shows how the instruction works using specific operand values: 7DJB9DOXH 7DJB5HVXOW The instruction reads the lowest-value set bit of the operand "Tag_Value" and writes the bit position "3" in the operand "Tag_Result". See also Overview of the valid data types (Page 1204) Operators and operator precedence (Page 1486) SEL: Select Description The instruction "Select" selects one of the parameters IN0 or IN1 depending on a switch (G parameter) and issues its content as a result. When the parameter G has the signal status "0", the value at parameter IN0 is moved. When the parameter G has the signal status "1", the value at parameter IN1 is moved and returned as a function value. The instruction is only executed if the tags of all parameters have the same data type class. Syntax The following syntax is used for the instruction "Select": SCL SEL(G:= <Expression>, IN0 := <Expression>, IN1 := <Expression>) The syntax of the instruction consists of the following parts: WinCC Basic V13.0 System Manual, 02/2014 2471 Programming the PLC 9.7 References Parameter Declaration Data type S7-1200 S7-1500 Description G Input BOOL BOOL Switch IN0 Input Bit strings, integers, floating-point numbers, TIME, TOD, DATE, CHAR, DT Bit strings, integers, floating-point numbers, CHAR, timers, DATE, TOD, LTOD, DT, LDT First input value IN1 Input Bit strings, integers, floating-point numbers, TIME, TOD, DATE, CHAR, DT Bit strings, integers, floating-point numbers, CHAR, timers, DATE, TOD, LTOD, DT, LDT Second input value Bit strings, integers, floating-point numbers, TIME, TOD, DATE, CHAR, DT Bit strings, integers, floating-point numbers, CHAR, timers, DATE, TOD, LTOD, DT, LDT Result of the instruction Function value For additional information on valid data types, refer to "See also". Example The following example shows how the instruction works: SCL "Tag_Result" := SEL(G := "Tag_Value", IN0 := "Tag_0", IN1 := "Tag_1"); The result of the instruction is returned in the operand "Tag_Result" as a function value. The following table shows how the instruction works using specific operand values: Operand Value Tag_Value 0 1 Tag_0 W#16#0000 W#16#4C Tag_1 W#16#FFFF D#16#5E Tag_Result W#16#0000 D#16#5E See also Overview of the valid data types (Page 1204) Operators and operator precedence (Page 1486) 2472 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References MUX: Multiplex Description The "Multiplex" instruction copies the value of a selected input parameter and issues it. You can use the parameter K to determine the number of the input parameter whose value will be moved. Numbering starts at IN0 and is incremented continuously with each new input. You can declare a maximum of 32 inputs. If the value of the K parameter is greater than the number of inputs and the INELSE parameter is not set, the instruction function value is invalid and the ENO enable output is set to 0. Numerical data types and time data types are permitted at the inputs. All tags with assigned parameters must be of the same data type. The function value is invalid if any of the following conditions are met: The value of the parameter K is greater than the number of available inputs. Errors occurred during the execution of the instruction. Syntax The following syntax is used for the "Multiplex" instruction: SCL MUX(K := <Expression>, IN0 := <Expression>, IN1 := <Expression>, INELSE := <Expression>) Parameter The following table shows the parameters of the "Multiplex" instruction: Parameter K Declaration Input Data type S7-1200 S7-1500 Integers Integers Description Specifies the parameter whose content is to be transferred. If K = 0 => Parameter IN0 If K = 1 => Parameter IN1, etc. IN0 WinCC Basic V13.0 System Manual, 02/2014 Input Binary numbers, integers, floatingpoint numbers, strings, TOD, DATE, TIME, DT Binary numbers, integers, floatingpoint numbers, strings, TOD, LTOD, DATE, timers, DT, LDT First input value 2473 Programming the PLC 9.7 References Parameter Declaration Data type S7-1200 S7-1500 Description IN1 Input Binary numbers, integers, floatingpoint numbers, strings, TOD, DATE, TIME, DT Binary numbers, integers, floatingpoint numbers, strings, TOD, LTOD, DATE, timers, DT, LDT Second input value INn Input Binary numbers, integers, floatingpoint numbers, strings, TOD, DATE, TIME, DT Binary numbers, integers, floatingpoint numbers, strings, TOD, LTOD, DATE, timers, DT, LDT Optional input values INELSE Input Binary numbers, integers, floatingpoint numbers, strings, TOD, DATE, TIME, DT Binary numbers, integers, floatingpoint numbers, strings, TOD, LTOD, DATE, timers, DT, LDT Specifies the value to be copied when K <> n. Binary numbers, integers, floatingpoint numbers, strings, TOD, DATE, TIME, DT Binary numbers, integers, floatingpoint numbers, strings, TOD, LTOD, DATE, timers, DT, LDT Result of the instruction Function value For additional information on valid data types, refer to "See also". Example The following example shows how the instruction works: SCL "Tag_Result" := MUX(K := "Tag_Number", IN0 := "Tag_1", IN1 := "Tag_2", INELSE := "Tag_3"); The result of the instruction is returned in the operand "Tag_Result" as a function value. The following table shows how the instruction works using specific operand values: Operand 2474 Value Tag_Number 1 4 Tag_1 DW#16#00000000 DW#16#00000000 Tag_2 DW#16#003E4A7D DW#16#003E4A7D Tag_3 DW#16#FFFF0000 DW#16#FFFF0000 Tag_Result DW#16#003E4A7D DW#16#FFFF0000 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References See also Overview of the valid data types (Page 1204) Operators and operator precedence (Page 1486) DEMUX: Demultiplex Description The "Demultiplex" instruction transfers the value of the input parameter IN to a selected output parameter. The selection of the input parameter takes place independent of the parameter value K. The K parameter specifies the output parameter number to which the value of the input parameter IN is transferred. The other output parameters are not changed. Numbering starts at OUT0 and continues consecutively with each new output. You can declare a maximum of 32 output parameters. If the value of the K parameter is greater than the number of output parameters, the value of the ENO enable output is set to "0" and the value is transferred to the input parameter IN and the output parameter OUTELSE. The function value is invalid if any of the following conditions are met: The value of the K parameter is greater than the number of available outputs. Errors occurred during execution of the instruction. Syntax The following syntax is used for the instruction "Demultiplex": SCL DEMUX(K := <Expression>, IN := <Expression>, OUT0 := <Operand>, OUT1 := <Operand>, OUTELSE := <Operand>) WinCC Basic V13.0 System Manual, 02/2014 2475 Programming the PLC 9.7 References Parameter The following table shows the parameters of the instruction "Demultiplex": Parameter K Declaration Input Data type S7-1200 S7-1500 Integers Integers Description Specifies the output to which the input value (IN) will be copied. If K = 0 => Parameter OUT0 If K = 1 => Parameter OUT1, etc. IN Input Binary numbers, integers, floatingpoint numbers, strings, TIME, TOD, DATE, DT Binary numbers, integers, floatingpoint numbers, strings, timers, TOD, LTOD, DATE, DT, LDT Input value OUT0 Output Binary numbers, integers, floatingpoint numbers, strings, TIME, TOD, DATE, DT Binary numbers, integers, floatingpoint numbers, strings, timers, TOD, LTOD, DATE, DT, LDT First output OUT1 Output Binary numbers, integers, floatingpoint numbers, strings, TIME, TOD, DATE, DT Binary numbers, integers, floatingpoint numbers, strings, timers, TOD, LTOD, DATE, DT, LDT Second output OUTn Output Binary numbers, integers, floatingpoint numbers, strings, TIME, TOD, DATE, DT Binary numbers, integers, floatingpoint numbers, strings, timers, TOD, LTOD, DATE, DT, LDT Optional outputs OUTELSE Output Binary numbers, integers, floatingpoint numbers, strings, TIME, TOD, DATE, DT Binary numbers, integers, floatingpoint numbers, strings, timers, TOD, LTOD, DATE, DT, LDT Output to which the value at input IN is copied if K > n. For additional information on available data types, refer to "See also". 2476 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Example The following example shows how the instruction works: SCL DEMUX(K := "Tag_Number", IN := "Tag_Value", OUT0 := "Tag_1", OUT1 := "Tag_2", OUTELSE := "Tag_3"); The following tables show how the instruction works using specific operand values: Input values of the "Demultiplex" instruction before the network execution Parameter Operand Values K Tag_Number 2 4 IN Tag_Value DW#16#FFFFFFFF DW#16#003E4A7D Output values of the "Demultiplex" instruction after the network execution Parameter Operand Values OUT0 Tag_1 Unchanged Unchanged OUT1 Tag_2 DW#16#FFFFFFFF Unchanged OUTELSE Tag_3 Unchanged DW#16#003E4A7D See also Overview of the valid data types (Page 1204) Operators and operator precedence (Page 1486) Shift and rotate SHR: Shift right Description The "Shift right" instruction shifts the contents of the IN parameter bit-by-bit to the right and returns it as a function value. The parameter N is used to specify the number of bit positions by which the specified value should be shifted. If the value of the N parameter is "0", the value of the IN parameter is given as a result. If the value of the N parameter is greater than the number of available bit positions, then the value of the IN parameter is shifted to the right by the available number of bit positions. The bit positions that are freed by shifting in the left operand area are filled with zeros. The following figure shows how the content of an integer data type operand is shifted by four bit positions to the right: WinCC Basic V13.0 System Manual, 02/2014 2477 Programming the PLC 9.7 References ,1 1 5HVXOW! SODFHV 7KHVHIRXUELWV DUHORVW 7KHIUHHGELWSRVLWLRQV DUHILOOHGZLWK]HURV Syntax The following syntax is used for the instruction "Shift right": SCL SHR(IN := <Operand>, N := <Operand>) Parameter The following table shows the parameters of the "Shift right" instruction: Parameter Declaration Data type S7-1200 S7-1500 Description IN Input Bit strings, integers Bit strings, integers Value to be shifted N Input USINT, UINT, UDINT USINT, UINT, UDINT, ULINT Bit strings, integers Bit strings, integers Result of the instruction Function value Number of bits by which the value (IN) is shifted For more information on valid data types, refer to "See also". 2478 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Example The following example shows how the instruction works: SCL "Tag_Result" := SHR(IN := "Tag_Value", N := "Tag_Number"); The following table shows how the instruction works using specific operand values: Parameter Operand Value IN Tag_Value 0011 1111 1010 1111 N Tag_Number 3 Function value Tag_Result 0000 0111 1111 010 1 The content of the "Tag_Value" operand is shifted by three bit positions to the right. The result of the instruction is returned in the operand "Tag_Result" as a function value. See also Overview of the valid data types (Page 1204) Operators and operator precedence (Page 1486) SHL: Shift left Description The "Shift left" instruction shifts the contents of the IN parameter bit-by-bit to the left and returns it as a function value. The parameter N is used to specify the number of bit positions by which the specified value should be shifted. If the value of the N parameter is "0", the value of the IN parameter is given as a result. If the value of the N parameter is greater than the number of bit positions, the value of the IN parameter is shifted to the left by the available number of bit positions. The bit positions freed by the shift are filled with zeros in the result value. The following figure shows how the content of an operand of the WORD data type is shifted six bit positions to the left: WinCC Basic V13.0 System Manual, 02/2014 2479 Programming the PLC 9.7 References ,1 1 SRVLWLRQV 5HVXOW! 7KHELWSRVLWLRQV WKDWKDYHEHFRPHIUHH ZLOOEHILOOHGZLWK]HURHV 7KHVHVL[ELWV ZLOOEHORVW Syntax The following syntax is used for the instruction "Shift left": SCL SHL(IN := <Operand>, N := <Operand>) Parameter The following table shows the parameters of the "Shift left" instruction: Parameter Declaration Data type S7-1200 S7-1500 Description IN Input Bit strings, integers Bit strings, integers Value to be shifted N Input USINT, UINT, UDINT USINT, UINT, UDINT, ULINT Bit strings, integers Bit strings, integers Result of the instruction Function value Number of bits by which the value (IN) is shifted For more information on valid data types, refer to "See also". 2480 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Example The following example shows how the instruction works: SCL "Tag_Result" := SHL(IN := "Tag_Value", N := "Tag_Number"); The following table shows how the instruction works using specific operand values: Parameter Operand Value IN Tag_Value 0011 1111 1010 1111 N Tag_Number 4 Function value Tag_Result 1111 1010 1111 0000 The value of the "Tag_Value" operand is shifted by four bit positions to the left. The result of the instruction is returned in the operand "Tag_Result" as a function value. See also Overview of the valid data types (Page 1204) Operators and operator precedence (Page 1486) ROR: Rotate right Description The "Rotate right" instruction rotates the content of the IN parameter bit-by-bit to the right and assigns the result to the specified operand. The parameter N is used to specify the number of bit positions by which the specified value should be rotated. The bit positions freed by rotating are filled with the bit positions that are pushed out. If the value of the N parameter is "0", the value at input IN is given as a result. If the value at the N parameter is greater than the number of available bit positions, the operand value at the IN input is still rotated by the specified number of bit positions. The following figure shows how the content of an operand of the DWORD data type is rotated three bit positions to the right: WinCC Basic V13.0 System Manual, 02/2014 2481 Programming the PLC 9.7 References ,1 1 5HVXOW! SODFHV 7KHVLJQDOVWDWHRIWKHWKUHH VKLIWHGELWVLVLQVHUWHGLQWRWKH IUHHGSRVLWLRQV Syntax The following syntax is used for the instruction "Rotate right": SCL ROR(IN := <Operand>, N := <Operand>) Parameter The following table shows the parameters of the "Rotate right" instruction: Parameter Declaration Data type S7-1200 S7-1500 Description IN Input Bit strings, integers Bit strings, integers Value to be rotated N Input USINT, UINT, UDINT USINT, UINT, UDINT, ULINT Bit strings, integers Bit strings, integers Result of the instruction Function value Number of bit positions by which the value (IN) is rotated For more information on valid data types, refer to "See also". 2482 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Example The following example shows how the instruction works: SCL "Tag_Result" := ROR(IN := "Tag_Value", N := "Tag_Number"); The following table shows how the instruction works using specific operand values: Parameter Operand Value IN Tag_Value 0000 1111 1001 0101 N Tag_Number 5 Function value Tag_Result 1010 1000 0111 1100 The content of the "Tag_Value" operand is rotated by five bit positions to the right. The result of the instruction is returned in the operand "Tag_Result" as a function value. See also Overview of the valid data types (Page 1204) Operators and operator precedence (Page 1486) ROL: Rotate left Description The "Rotate left" instruction rotates the contents of the IN parameter bit-by-bit to the left and returns it as a function value. The parameter N is used to specify the number of bit positions by which the specified value should be rotated. The bit positions freed by rotating are filled with the bit positions that are pushed out. If the value of the N parameter is "0", the value at input IN is given as a result. If the value at the N parameter is greater than the number of available bit positions, the operand value at the IN input is still rotated by the specified number of bit positions. The following figure shows how the content of an operand of the DWORD data type is rotated three bit positions to the left: WinCC Basic V13.0 System Manual, 02/2014 2483 Programming the PLC 9.7 References ,1 1 5HVXOW! SRVLWLRQV 7KHVLJQDOVWDWHRIWKHWKUHH ELWVWKDWKDYHEHHQPRYHGZLOOEH DGGHGLQWKHSRVLWLRQVZKLFKKDYH EHFRPHIUHH Syntax The following syntax is used for the "Rotate left" instruction: SCL ROL(IN := <Operand>, N := <Operand>) Parameter The following table shows the parameters of the "Rotate left" instruction: Parameter Declaration Data type S7-1200 S7-1500 Description IN Input Bit strings, integers Bit strings, integers Value to be rotated N Input USINT, UINT, UDINT USINT, UINT, UDINT, ULINT Bit strings, integers Bit strings, integers Result of the instruction Function value Number of bit positions by which the value (IN) is rotated For more information on valid data types, refer to "See also". 2484 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Example The following example shows how the instruction works: SCL "Tag_Result" := ROL(IN := "Tag_Value", N := "Tag_Number"); The following table shows how the instruction works using specific operand values: Parameters Operand Value IN Tag_Value 1010 1000 1111 0110 N Tag_Number 5 Function value Tag_Result 0001 1110 1101 0101 The content of the operand "Tag_Value" is rotated five bit positions to the left. The result of the instruction is returned in the operand "Tag_Result" as a function value. See also Overview of the valid data types (Page 1204) Operators and operator precedence (Page 1486) Additional instructions DRUM: Implement sequencer Description The "Implement sequencer" instruction is used to assign the programmed values of the OUT_VAL parameter of the corresponding step to the programmed output bits (OUT1 to OUT16) and the output word (OUT_WORD). The specific step must thereby satisfy the conditions of the programmed enable mask on the S_MASK parameter while the instruction remains at this step. The instruction advances to the next step if the event for the step is true and the programmed time for the current step elapses, or if the value at the JOG parameter changes from "0" to "1". The instruction is reset if the signal state on the RESET parameter changes to "1". The current step is hereby equated to the preset step (DSP). The amount of time spent on a step is determined by the product of the preset timebase (DTBP) and the preset counter value (S_PRESET) for each step. At the start of a new step, this calculated value is loaded into the DCC parameter, which contains the time remaining for the current step. If, for example the value at the DTBP parameter is "2" and the preset value for the first step is "100" (100 ms), the DCC parameter has the value "200" (200 ms). A step can be programmed with a time value, an event, or both. Steps that have an event bit and the time value "0" advance to the next step as soon as the signal state of the event bit is "1". Steps that are programmed only with a time value start the time immediately. Steps that are programmed with an event bit and a time value greater than "0" start the time when the signal state of the event bit is "1". The event bits are initialized with a signal state of "1". WinCC Basic V13.0 System Manual, 02/2014 2485 Programming the PLC 9.7 References When the sequencer is on the last programmed step (LST_STEP) and the time for this step has expired, the signal state on the Q parameter is set to "1"; otherwise it is set to "0". When the parameter Q is set, the instruction remains on the step until it is reset. In the configurable mask (S_MASK) you can selected the separate bits in the output word (OUT_WORD) and set or reset the output bits (OUT1 to OUT16) by means of the output values (OUT_VAL). If a bit of the configurable mask is in the signal state "1", the value OUT_VAL sets or resets the corresponding bit. If the signal state of a bit of the configurable mask is "0", the corresponding bit is left unchanged. All the bits of the configurable mask for all 16 steps are initialized with a signal state of "1". The output bit on the OUT1 parameter corresponds to the least significant bit of the output word (OUT_WORD). The output bit on the OUT16 parameter corresponds to the most significant bit of the output word (OUT_WORD). When you insert the instruction in the program, the "Call options" dialog opens in which you can specify whether the block parameters will be stored in a separate data block (single instance) or as a local tag (multiple instance) in the block interface. If you create a separate data block, you will find it in the project tree in the "Program resources" folder under "Program blocks > System blocks". For more information on this topic, refer to "See also". Syntax The following syntax is used for the "Implement sequencer" instruction: SCL <Instance>RESET:= <Operand>, JOG := <Operand>, DRUM_EN := <Operand>, LST_STEP := <Operand>, EVENT1 - 16 := <Operand>, OUT1 - 16 => <Operand>, Q => <Operand>, OUT_WORD => <Operand>, ERR_CODE => <Operand>) Parameter The following table shows the parameters of the "Implement sequencer" instruction: 2486 Parameter Declaration Data type Description RESET Input BOOL A signal state of "1" indicates a reset condition. JOG Input BOOL When the signal state changes from "0" to "1", the instruction advances to the next step. WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameter Declaration Data type Description DRUM_EN Input BOOL A signal state of "1" allows the sequencer to advance based on the event and time criteria. LST_STEP Input BYTE Step number of the last step programmed. EVENT(i), Input BOOL Event bit (i); 1 i 16 OUT(j), Initial signal state is "1". Output BOOL Output bit (j) Q Output BOOL A signal state of "1" indicates that the time for the last step has elapsed. OUT_WORD Output WORD Word address to which the sequencer writes the output values. ERR_CODE Output WORD Error information JOG_HIS Static BOOL JOG parameter history bit EOD Static BOOL A signal state of "1" indicates that the time for the last step has elapsed. DSP Static BYTE Preset step of the sequencer DSC Static BYTE Current step of the sequencer DCC Static DWORD Current numerical value of the sequencer DTBP Static WORD Preset timebase of the sequencer PREV_TIME Static DWORD Previous system time S_PRESET Static ARRAY of WORD Count preset for each step [1 to 16] where 1 count = 1 ms. OUT_VAL Static ARRAY of BOOL Output values for each step [1 to 16, 0 to 15]. S_MASK Static ARRAY of BOOL Configurable mask for each step [1 to 16, 0 to 15]. Initial signal states are "1". 1 j 16 For more information on valid data types, refer to "See also". The static parameters are not visible when calling the instruction in the program. These are saved in the instance of the instruction. WinCC Basic V13.0 System Manual, 02/2014 2487 Programming the PLC 9.7 References ERR_CODE Parameter The following table shows the meaning of the values of the parameter ERR_CODE: ERR_CODE* Explanation W#16#0000 No error W#16#000B The value at the LST_STEP parameter is less than 1 or greater than 16. W#16#000C The value at the DSC parameter is less than 1 or greater than the value at the LST_STEP parameter. W#16#000D The value at the DSP parameter is less than 1 or greater than the value at the LST_STEP parameter. *The error codes can be displayed as integer or hexadecimal value in the program editor. For more information on toggling display formats, refer to "See also". See also Overview of the valid data types (Page 1204) DCAT: Discrete control-timer alarm Description The "Discrete control-timer alarm" instruction is used to accumulate the time from the point at which the CMD parameter issues the command to open or close. The time is accumulated until the preset time (PT) is exceeded or the information is received that the device was opened or closed (O_FB or C_FB) within the specified time. If the preset time is exceeded before the information on the opening or closing of the device is received, the corresponding alarm is activated. If the signal state on the command input changes state before the preset time, the time is restarted. When you insert the instruction in the program, the "Call options" dialog opens in which you can specify whether the block parameters will be stored in a separate data block (single instance) or as a local tag (multiple instance) in the block interface. If you create a separate data block, you will find it in the project tree in the "Program resources" folder under "Program blocks > System blocks". For more information on this topic, refer to "See also". The "Discrete control-timer alarm" instruction has the following reactions to the input conditions: When the signal state of the CMD parameter changes from "0" to "1", the signal states of the parameters Q, CMD_HIS, ET (only if ET < PT), OA and CA are influenced as follows: - The parameters Q and CMD_HIS are set to "1". - The parameters ET, OA and CA are reset to "0". When the signal state on the parameter CMD changes from "1" to "0", the parameters Q, ET (only if ET < PT), OA, CA and CMD_HIS are reset to "0". 2488 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References When the signal state of the parameters CMD and CMD_HIS is "1" and the parameter O_FB is set to "0", the time difference (ms) since the last execution of the instruction is added to the value at the parameter ET. If the value of the parameter ET exceeds the value of the parameter PT, the signal state on the parameter OA is set to "1". If the value of the parameter ET does not exceed the value of the parameter PT, the signal state on the parameter OA is reset to "0". The value at the parameter CMD_HIS is set to the value of the parameter CMD. If the signal state of the parameters CMD, CMD_HIS and O_FB are set to "1" and the parameter C_FB has the value "0", the signal state of the parameter OA is set to "0". The value of parameter ET is set to the value of parameter PT. If the signal state of the parameter O_FB changes to "0", the alarm is set the next time the instruction is executed. The value of parameter CMD_HIS is set to the value of parameter CMD. If the parameters CMD, CMD_HIS and C_FB have the value "0", the time difference (ms) since the last execution of the instruction is added to the value of the parameter ET. If the value of the parameter ET exceeds the value of the parameter PT, the signal state of the parameter CA is set to "1". If the value at the parameter PT is not exceeded, the parameter CA has the signal state "0". The value of parameter CMD_HIS is set to the value of parameter CMD. If the parameters CMD, CMD_HIS and O_FB have the signal state "0" and the parameter C_FB is set to "1", the parameter CA is set to "0". The value of parameter ET is set to the value of parameter PT. If the signal state of the parameter C_FB changes to "0", the alarm is set the next time the instruction is executed. The value of parameter CMD_HIS is set to the value of parameter CMD. If the parameters O_FB and C_FB simultaneously have the signal state "1", the signal states of both alarm outputs are set to "1". The "Discrete control-timer alarm" instruction has no error information. Syntax The following syntax is used for the "Discrete control-timer alarm" instruction: SCL <Instance>CMD:= <Operand>, O_FB := <Operand>, C_FB := <Operand>, Q => <Operand>, OA => <Operand>, CA => <Operand>) WinCC Basic V13.0 System Manual, 02/2014 2489 Programming the PLC 9.7 References Parameter The following table shows the parameters of the instruction: Parameter Declaration Data type Description CMD Input BOOL A signal state of "0" indicates a "close" command. A signal state of "1" indicates an "open" command. O_FB Input BOOL Feedback input when opening C_FB Input BOOL Feedback input when closing Q Output BOOL Shows the status of the parameter CMD OA Output BOOL Alarm output when opening CA Output BOOL Alarm output when closing ET Static DINT Currently elapsed time, where one count = 1 ms. PT Static DINT Preset time value, where one count = 1 ms. PREV_TIME Static DWORD Previous system time CMD_HIS Static BOOL CMD history bit For more information on valid data types, refer to "See also". The static parameters are not visible when calling the instruction in the program. These are saved in the instance of the instruction. Example In the following example the parameter CMD changes from "0" to "1". After the execution of the instruction the parameter Q is set to "1" and the two alarm outputs OA and CA have the signal state "0". The parameter CMD_HIS of the instance data block is set to the signal state "1" and the parameter ET is reset to "0". Note You can initialize static parameters in the data block. SCL "DCAT_DB"(CMD := "Tag_Input_CMD", O_FB := "Tag_Input_O_FB", C_FB := "Tag_Input_C_FB", Q => "Tag_Output_Q", OA => "Tag_Output_OA", CA => "Tag_Output_CA"); The following tables show how the instruction works using specific values: Before processing In this example the following values are used for the input and output parameters: 2490 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameter Operand Value CMD Tag_Input_CMD TRUE O_FB Tag_Input_O_FB FALSE C_FB Tag_Input_C_FB FALSE Q Tag_Output_Q FALSE OA Tag_Output_OA FALSE CA Tag_Output_CA FALSE The following values are saved in the instance data block "DCAT_DB" of the instruction: Parameter Address Value ET DBD4 L#12 PT DBD8 L#222 CMD_HIS DBX16.0 FALSE After processing The following values are written to the output parameters after the instruction has been executed: Parameter Operand Value Q Tag_Output_Q TRUE OA Tag_Output_OA FALSE CA Tag_Output_CA FALSE The following values are saved in the instance data block "DCAT_DB" of the instruction: Parameter Address Value ET DBD4 L#0 CMD_HIS DBX16.0 TRUE See also Overview of the valid data types (Page 1204) MCAT: Motor control-timer alarm Description The "Motor control-timer alarm" instruction is used to accumulate the time from the point at which one of the command inputs (opening or closing) is switched on. The time is accumulated until the preset time is exceeded or the relevant feedback input indicates that the device has executed the requested operation within the specified time. If the preset time is exceeded before the feedback is received, the corresponding alarm is triggered. When you insert the instruction in the program, the "Call options" dialog opens in which you can specify whether the block parameters will be stored in a separate data block (single WinCC Basic V13.0 System Manual, 02/2014 2491 Programming the PLC 9.7 References instance) or as a local tag (multiple instance) in the block interface. If you create a separate data block, you will find it in the project tree in the "Program resources" folder under "Program blocks > System blocks". For additional information on this topic, refer to "See also". Execution of the "Motor control-timer alarm" instruction The following table shows the reactions of the "Motor control-timer alarm" instruction to the various input conditions: Input parameters Output parameters ET O_H IS C_H IS O_C MD C_C MD S_C MD O_F B C_F B OO CO OA CA ET O_H IS C_H IS Q State X 1 1 X X X X X 0 0 1 1 PT 0 0 0 Alarm X X X X X X 1 1 0 0 1 1 PT 0 0 0 Alarm X X X X X 1 X X 0 0 0 0 X 0 0 1 Stop X X X 1 1 X X X 0 0 0 0 X 0 0 1 Stop X 0 X 1 0 0 X X 1 0 0 0 0 1 0 1 Start opening <PT 1 0 X 0 0 0 X 1 0 0 0 INC 1 0 1 Open X 1 0 X 0 0 1 0 0 0 0 0 PT 1 0 1 Opened >=P T 1 0 X 0 0 0 X 0 0 1 0 PT 1 0 0 Opening alarm X X 0 0 1 0 X X 0 1 0 0 0 0 1 1 Start closing <PT 0 1 0 X 0 X 0 0 1 0 0 INC 0 1 1 Close X 0 1 0 X 0 0 1 0 0 0 0 PT 0 1 1 Closed >=P T 0 1 0 X 0 X 0 0 0 0 1 PT 0 1 0 Closing alarm X 0 0 0 0 0 X X 0 0 0 0 X 0 0 1 Stopped Legend: INC Add the time difference (ms) since the last processing of the FB to ET PT PT is set to the same value as ET X Cannot be used <PT ET < PT >=PT ET >= PT If the input parameters O_HIS and C_HIS both have the signal state "1", they are immediately set to the signal state "0". In this case, the last row in the table (X) mentioned above is valid. Because it is therefore not possible to check whether the input parameters O_HIS and C_HIS have the signal state "1", the output parameters are set as follows in this case: OO = FALSE CO = FALSE OA = FALSE CA = FALSE ET = PT Q = TRUE 2492 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Syntax The following syntax is used for the "Motor control-timer alarm" instruction: SCL <Instance>O_CMD:= <Operand>, C_CMD := <Operand>, S_CMD := <Operand>, O_FB := <Operand>, C_FB := <Operand>, 00 => <Operand>, C0 => <Operand>, OA => <Operand>, CA => <Operand>, Q => <Operand>) Parameter The following table shows the parameters of the "Motor control-timer alarm" instruction: Parameter Declaration Data type Description O_CMD Input BOOL "Open" command input C_CMD Input BOOL "Close" command input S_CMD Input BOOL "Stop" command input O_FB Input BOOL Feedback input when opening C_FB Input BOOL Feedback input when closing OO Output BOOL "Open" output CO Output BOOL "Close" output OA Output BOOL Alarm output when opening CA Output BOOL Alarm output when closing Q Output BOOL A signal state of "0" indicates an error condition. ET Static DINT Currently elapsed time, where one count = 1 ms PT Static DINT Preset time value, where one count = 1 ms PREV_TIME Static DWORD Previous system time O_HIS Static BOOL "Open" history bit C_HIS Static BOOL "Close" history bit For additional information on valid data types, refer to "See also". The static parameters are not visible when calling the instruction in the program. These are saved in the instance of the instruction. WinCC Basic V13.0 System Manual, 02/2014 2493 Programming the PLC 9.7 References Example The following example shows how the instruction works: Note You can initialize static parameters in the data block. SCL "MCAT_DB"(O_CMD := "Tag_Iput_O_CMD", C_CMD := "Tag_Input_C_CMD", S_CMD := "Tag_Input_S_CMD", O_FB := "Tag_Input_O_FB", C_FB := "Tag_Input_C_FB", OO => "Tag_OutputOpen", CO => "Tag_OutputClosed", OA => "Tag_Output_OA", CA => "Tag_Output_CA", Q => "Tag_Output_Q"); The following tables show how the instruction works using specific values: Before processing In this example the following values are used for the input and output parameters: Parameter Operand Value O_CMD Tag_Input_O_CMD TRUE C_CMD Tag_Input_C_CMD FALSE S_CMD Tag_Input_S_CMD FALSE O_FB Tag_Input_O_FB FALSE C_FB Tag_Input_C_FB FALSE OO Tag_OutputOpen FALSE CO Tag_OutputClosed FALSE OA Tag_Output_OA FALSE CA Tag_Output_CA FALSE Q Tag_Output_Q FALSE The following values are saved in the instance data block "MCAT_DB" of the instruction: Parameter Address Value ET DBD4 L#2 PT DBD8 L#22 O_HIS DBX16.0 TRUE C_HIS DBX16.1 FALSE After processing The following values are written to the output parameters after the instruction has been executed: 2494 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameter Operand Value OO Tag_OutputOpen TRUE CO Tag_OutputClosed FALSE OA Tag_Output_OA FALSE CA Tag_Output_CA FALSE Q Tag_Output_Q TRUE The following values are saved in the instance data block "MCAT_DB" of the instruction: Parameter Address Value ET DBD4 L#0 O_HIS DBX16.0 TRUE CMD_HIS DBX16.1 FALSE See also Overview of the valid data types (Page 1204) IMC: Compare input bits with the bits of a mask Description The "Compare input bits with the bits of a mask" instruction is used to compare the signal state of up to 16 programmed input bits (IN_BIT0 to IN_BIT15) with the corresponding bit of a mask. Up to 16 steps with masks can be programmed. The value of the IN_BIT0 parameter is compared with the value of the mask CMP_VAL[x,0], with "x" indicating the step number. On the CMP_STEP parameter, you specify the step number of the mask that is used for the comparison. All programmed values are compared in the same manner. Unprogrammed input bits or unprogrammed bits of the mask have a default signal state FALSE. If a match is found in the comparison, the signal state of the OUT parameter is set to "1". Otherwise the OUT parameter is set to "0". If the value of CMP_STEP parameter is greater than 15, the instruction is not executed. An error message is output at the ERR_CODE parameter. When you insert the instruction in the program, the "Call options" dialog opens in which you can specify whether the block parameters will be stored in a separate data block (single instance) or as a local tag (multiple instance) in the block interface. If you create a separate data block, you will find it in the project tree in the "Program resources" folder under "Program blocks > System blocks". For more information on this topic, refer to "See also". Syntax The following syntax is used for the "Compare input bits with the bits of a mask" instruction: SCL <Instance>(IN_BIT0 - 15 := <Operand>, CMP_STEP := <Operand>, WinCC Basic V13.0 System Manual, 02/2014 2495 Programming the PLC 9.7 References SCL OUT => <Operand>, ERR_CODE => <Operand>) Parameters The following table shows the parameters of the "Compare input bits with the bits of a mask" instruction: Parameter Declaration Data type Description IN_BIT0 Input BOOL Input bit 0 is compared with bit 0 of the mask. IN_BIT1 Input BOOL Input bit 1 is compared with bit 1 of the mask. IN_BIT2 Input BOOL Input bit 2 is compared with bit 2 of the mask. IN_BIT3 Input BOOL Input bit 3 is compared with bit 3 of the mask. IN_BIT4 Input BOOL Input bit 4 is compared with bit 4 of the mask. IN_BIT5 Input BOOL Input bit 5 is compared with bit 5 of the mask. IN_BIT6 Input BOOL Input bit 6 is compared with bit 6 of the mask. IN_BIT7 Input BOOL Input bit 7 is compared with bit 7 of the mask. IN_BIT8 Input BOOL Input bit 8 is compared with bit 8 of the mask. IN_BIT9 Input BOOL Input bit 9 is compared with bit 9 of the mask. IN_BIT10 Input BOOL Input bit 10 is compared with bit 10 of the mask. IN_BIT11 Input BOOL Input bit 11 is compared with bit 11 of the mask. IN_BIT12 Input BOOL Input bit 12 is compared with bit 12 of the mask. IN_BIT13 Input BOOL Input bit 13 is compared with bit 13 of the mask. IN_BIT14 Input BOOL Input bit 14 is compared with bit 14 of the mask. IN_BIT15 Input BOOL Input bit 15 is compared with bit 15 of the mask. CMP_STEP Input BYTE The step number of the mask used for the comparison. OUT Output BOOL A signal state of "1" indicates that a match was found. A signal state of "0" indicates that no match was found. ERR_CODE Output WORD Error information CMP_VAL Static ARRAY OF WORD Comparison masks [0 to 15, 0 to 15]: The first number of the index is the step number and the second number is the bit number of the mask. For more information on valid data types, refer to "See also". The static parameters are not visible when calling the instruction in the program. These are saved in the instance of the instruction. 2496 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References ERR_CODE Parameter The following table shows the meaning of the values of the ERR_CODE parameter: Error code* (W#16#...) Explanation 0000 No error 000A The value at the CMP_STEP parameter is greater than 15. *The error codes can be displayed as integer or hexadecimal value in the program editor. For more information on toggling display formats, refer to "See also". See also Overview of the valid data types (Page 1204) SMC: Compare scan matrix Description You can use the "Compare scan matrix" instruction to compare the signal state of up to 16 programmed input bits (IN_BIT0 to IN_BIT15) with the corresponding bit of the comparison masks for each step. Processing starts at step 1 and is continued until the last programmed step (LAST) or until a match is found. The input bit of the IN_BIT0 parameter is compared with the value of the mask CMP_VAL[x,0], with "x" indicating the step number. All programmed values are compared in the same manner. If a match is found the signal state of the OUT parameter is set to "1" and the step number with the matching mask is written in the OUT_STEP parameter. Unprogrammed input bits or unprogrammed bits of the mask have a default signal state FALSE. If more than one step has a matching mask, only the first one found is indicated in the OUT_STEP parameter. If no match is found, the signal state of the OUT parameter is set to "0". In this case the value at the OUT_STEP parameter is greater by "1" than the value at the LAST parameter. When you insert the instruction in the program, the "Call options" dialog opens in which you can specify whether the block parameters will be stored in a separate data block (single instance) or as a local tag (multiple instance) in the block interface. If you create a separate data block, you will find it in the project tree in the "Program resources" folder under "Program blocks > System blocks". For more information on this topic, refer to "See also". Syntax The following syntax is used for the "Compare scan matrix" instruction: SCL <Instance>(IN_BIT0 - 15 := <Operand>, OUT => <Operand>, OUT_STEP => <Operand>, ERR_CODE => <Operand>) WinCC Basic V13.0 System Manual, 02/2014 2497 Programming the PLC 9.7 References Syntax The following table shows the parameters of the "Compare scan matrix" instruction: Parameter Declaration Data type Description IN_BIT0 Input BOOL Input bit 0 is compared with bit 0 of the mask. IN_BIT1 Input BOOL Input bit 1 is compared with bit 1 of the mask. IN_BIT2 Input BOOL Input bit 2 is compared with bit 2 of the mask. IN_BIT3 Input BOOL Input bit 3 is compared with bit 3 of the mask. IN_BIT4 Input BOOL Input bit 4 is compared with bit 4 of the mask. IN_BIT5 Input BOOL Input bit 5 is compared with bit 5 of the mask. IN_BIT6 Input BOOL Input bit 6 is compared with bit 6 of the mask. IN_BIT7 Input BOOL Input bit 7 is compared with bit 7 of the mask. IN_BIT8 Input BOOL Input bit 8 is compared with bit 8 of the mask. IN_BIT9 Input BOOL Input bit 9 is compared with bit 9 of the mask. IN_BIT10 Input BOOL Input bit 10 is compared with bit 10 of the mask. IN_BIT11 Input BOOL Input bit 11 is compared with bit 11 of the mask. IN_BIT12 Input BOOL Input bit 12 is compared with bit 12 of the mask. IN_BIT13 Input BOOL Input bit 13 is compared with bit 13 of the mask. IN_BIT14 Input BOOL Input bit 14 is compared with bit 14 of the mask. IN_BIT15 Input BOOL Input bit 15 is compared with bit 15 of the mask. OUT Output BOOL A signal state of "1" indicates that a match was found. A signal state of "0" indicates that no match was found. OUT_STEP Output BYTE Contains the step number with the matching mask, or the step number which is greater by "1" than the value at the LAST parameter, provided no match is found. ERR_CODE Output WORD Error information LAST Static BYTE Specifies the step number of the last step to be scanned for a matching mask. CMP_VAL Static ARRAY OF WORD Comparison masks [0 to 15, 0 to 15]: The first number of the index is the step number and the second number is the bit number of the mask. For more information on valid data types, refer to "See also". The static parameters are not visible when calling the instruction in the program. These are saved in the instance of the instruction. 2498 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References ERR_CODE Parameter The following table shows the meaning of the values of the parameter ERR_CODE: Error code* (W#16#...) Explanation 0000 No error 000E The value at the LAST parameter is greater than 15. *The error codes can be displayed as integer or hexadecimal value in the program editor. For more information on toggling display formats, refer to "See also". See also Overview of the valid data types (Page 1204) LEAD_LAG: Lead and lag algorithm Description Use the "Lead and lag algorithm" instruction to process signals with an analog tag. The gain value at the GAIN parameter must be greater than zero. The result of the "Lead and lag algorithm" instruction is calculated using the following equation: 287 /*B7,0( /'B7,0(6$03/(B7 /'B7,0( ,1*$,1 35(9B287*$,1 /*B7,0(6$03/(B7 /*B7,0(6$03/(B7 /*B7,0(6$03/(B7 35(9B,1 The instruction "Lead and lag algorithm" supplies plausible results only when processing is in fixed program cycles. The same units must be specified at the parameters LD_TIME, LG_TIME and SAMPLE_T. At LG_TIME > 4 + SAMPLE_T, the instruction approaches the following function: OUT = GAIN * ((1 + LD_TIME * s) / (1 + LG_TIME * s)) * IN When the value of the GAIN parameter is less than or equal to zero, the calculation is not performed and an error information is output on the ERR_CODE parameter. You can use the "Lead and lag algorithm" instruction in conjunction with loops as a compensator in dynamic feed-forward control. The instruction consists of two operations. The "Lead" operation shifts the phase of output OUT so that the output leads the input. The "Lag" operation, on the other hand, shifts the output so that the output lags behind the input. Because the "Lag" operation is equivalent to an integration, it can be used as a noise suppressor or as a low-pass filter. The "Lead" operation is equivalent to a differentiation and can therefore be used as a high-pass filter. The two instructions together (Lead and Lag) result in the output phase lagging behind the the input at lower frequencies and leading it at higher frequencies. This means that the "Lead and lag algorithm" instruction can be used as a band pass filter. When you insert the instruction in the program, the "Call options" dialog opens in which you can specify whether the block parameters will be stored in a separate data block (single instance) or as a local tag (multiple instance) in the block interface. If you create a separate data block, you will find it in the project tree in the "Program resources" folder under "Program blocks > System blocks". For more information on this topic, refer to "See also". WinCC Basic V13.0 System Manual, 02/2014 2499 Programming the PLC 9.7 References Syntax The following syntax is used for the "Lead and lag algorithm" instruction: SCL <Instance>(IN:= <Operand>, SAMPLE_T := <Operand>, OUT => <Operand>, ERR_CODE => <Operand>) The following table shows the parameters of the instruction: Parameter Declaration Data type Description IN Input REAL The input value of the current sample time (cycle time) to be processed. Constants can also be specified on the IN parameter. SAMPLE_T Input INT Sample time Constants can also be specified on the SAMPLE_T parameter. OUT Output REAL Result of the instruction ERR_CODE Output WORD Error information LD_TIME Static REAL Lead time in the same unit as sample time. LG_TIME Static REAL Lag time in the same unit as sample time GAIN Static REAL Gain as % / % (the ratio of the change in output to a change in input as a steady state). PREV_IN Static REAL Previous input PREV_OUT Static REAL Previous output For more information on valid data types, refer to "See also". The static parameters are not visible when calling the instruction in the program. These are saved in the instance of the instruction. 2500 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References ERR_CODE Parameter The following table shows the meaning of the values of the parameter ERR_CODE: Error code* (W#16#...) Explanation 0000 No error 0009 The value at the GAIN parameter is less than or equal to zero. *The error codes can be displayed as integer or hexadecimal value in the program editor. For more information on toggling display formats, refer to "See also". Example The following example shows how the instruction works: Note You can initialize static parameters in the data block. SCL "LEAD_LAG_DB"(IN := "Tag_Input", SAMPLE_T := "Tag_Input_SAMPLE_T", OUT => "Tag_Output_Result", ERR_CODE => "Tag_ErrorCode"); The following tables show how the instruction works using specific values: Before processing In this example the following values are used for the input parameters: Parameter Operand Value IN Tag_Input 2.0 SAMPLE_T Tag_Input_SAMPLE_T 10 The following values are saved in the instance data block "LEAD_LAG_DB" of the instruction: Parameter Address Value LD_TIME DBD12 2.0 LG_TIME DBD16 2.0 GAIN DBD20 1.0 PREV_IN DBD24 6.0 PREV_OUT DBD28 6.0 After processing The following values are written to the output parameters after the instruction has been executed: WinCC Basic V13.0 System Manual, 02/2014 2501 Programming the PLC 9.7 References Parameter Operand Value OUT Tag_Output_Result 2.0 The following values are saved in the instance data block "LEAD_LAD_DB" of the instruction: Parameter Operand Value PREV_IN DBD24 2.0 PREV_OUT DBD28 2.0 See also Overview of the valid data types (Page 1204) SEG: Create bit pattern for seven-segment display Description The "Create bit pattern for seven-segment display" instruction is used to convert each of the four hexadecimal digits of the specified source word (IN) into an equivalent bit pattern for a 7segment display. The result of the instruction is output in the double word on the OUT parameter. The following relation exists between the hexadecimal digits and the assignment of the 7 segments (a, b, c, d, e, f, g): Input digit (Binary) 2502 Assignment of the segments gfedcba Display Seven-segment display (Hexadecimal) 0000 00111111 0 0001 00000110 1 0010 01011011 2 0011 01001111 3 0100 01100110 4 0101 01101101 5 0110 01111101 6 0111 00000111 7 1000 01111111 8 1001 01100111 9 1010 01110111 A 1011 01111100 B 1100 00111001 C 1101 01011110 D 1110 01111001 E 1111 01110001 F D I E J H F G WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Syntax Use the following syntax for the "Create bit pattern for seven-segment display" instruction: SCL SEG(IN := <Operand>, OUT => <Operand>) Parameter The following table shows the parameters of the "Create bit pattern for seven-segment display" instruction: Parameter Declaration Data type Description IN Input WORD Source word with four hexadecimal digits OUT Output DWORD Bit pattern for the sevensegment display VOID Empty function value Function value Example The following example shows how the instruction works: SCL SEG(IN := "Tag_Input", OUT => "Tag_Output"); The following table shows how the instruction works using specific operand values: Parameter Operand Value Hexadecimal Binary IN Tag_Input W#16#1234 0001 0010 0011 0100 OUT Tag_Output DW16#065B4F66 00000110 01011011 01001111 01100110 Display: 1234 See also Overview of the valid data types (Page 1204) WinCC Basic V13.0 System Manual, 02/2014 2503 Programming the PLC 9.7 References BCDCPL: Create tens complement Description The "Create tens complement" instruction is used to create the tens complement of a sevendigit BCD number specified by the operand. This instruction uses the following mathematical formula to calculate: 10000000 (as BCD) - 7-digit BCD value ---------------------------------------Tens complement (as BCD) Syntax The following syntax is used for the "Create tens complement" instruction: SCL BCDCPL(<Operand>) Parameter The following table shows the parameters of the "Create tens complement" instruction: Parameter Declaration Data type Description <Operand> Input Bit strings 7-digit BCD number DWORD Result of the instruction Function value For additional information on valid data types, refer to "See also". Example The following example shows how the instruction works: SCL "Tag_Result" := BCDCPL("Tag_Input"); The following table shows how the instruction functions using specific values: Operand Value* Tag_Input DW#16#01234567 Tag_Result DW#16#08765433 *The error codes can be displayed as integer or hexadecimal value in the program editor. For information on toggling display formats, refer to "See also". 2504 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References See also Overview of the valid data types (Page 1204) BITSUM: Count number of set bits Description The "Count number of set bits" instruction is used to count the number of bits of an operand that are set to the signal state "1". Syntax The following syntax is used for the "Count number of set bits" instruction: SCL BITSUM(<Operand>) Parameter The following table shows the parameters of the "Count number of set bits" instruction: Parameter Declaration Data type Description <Operand> Input DWORD Operand whose set bits are counted INT Result of the instruction Function value Example The following example shows how the instruction works: SCL "Tag_Result" := BITSUM("Tag_Input"); The following table shows how the instruction functions using specific values: Operand Value* Tag_Input DW#16#12345678 Tag_Result W#16#000D (13 bits) *The error codes can be displayed as integer or hexadecimal value in the program editor. For more information on toggling display formats, refer to "See also". See also Overview of the valid data types (Page 1204) WinCC Basic V13.0 System Manual, 02/2014 2505 Programming the PLC 9.7 References 9.7.3 Extended instructions 9.7.3.1 Date and time-of-day T_COMP: Compare time tags Description This instruction is used to compare the contents of two tags of the data types "Timers" or "Date and time". The instruction supports comparisons of the following data types: DATE, TIME, LTIME, TOD (TIME_OF_DAY), LTOD (LTIME_OF_DAY), DT (DATE_AND_TIME), LDT (DATE_AND_LTIME), DTL, S5Time. The data types must be the same length and format to carry out the comparison. The comparison result is output at the OUT parameter as a return value. For this purpose, the parameter OUT is set to "1" if the condition used for the comparison is satisfied. The following comparison options can be used: Symbol Description EQ The return value has the signal state "1" if the time is the same at the parameter IN1 and IN2. NE The return value has the signal state "1" if the time at parameters IN1 and IN2 is not identical. GE The return value has the signal state "1" if the time at parameter IN1 is greater (more recent) than or equal to the time at parameter IN2 . LE The return value has the signal state "1" if the time at parameter IN1 is less (less recent) than or equal to the time at parameter IN2. GT The return value has the signal state "1" if the time at parameter IN1 is greater (more recent) than the time at parameter IN2. LT The return value has the signal state "1" if the time at parameter IN1 is less (less recent) than the time at parameter IN2 . Parameters The following table shows the parameters of the instruction "T_COMP": Parameter Declaration Data type Memory area Description IN1 Input DATE, TIME, LTIME, TOD, LTOD, DT, LDT, DTL I, Q, M, D, L, P or constant First value to be compared. IN2 Input DATE, TIME, LTIME, TOD, LTOD, DT, LDT, DTL I, Q, M, D, L, P or constant Second value to be compared. OUT Output BOOL I, Q, M, D, L, P Return value You can find additional information on valid data types in "Overview of the valid data types (Page 1204)". 2506 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References T_CONV: Convert times and extract Description You use the instruction "T_CONV" to convert the data type of the IN input parameter to the data type that is output at the OUT output. You select the data formats for the conversion from the instruction boxes of the input and output. Parameters The following table shows the parameters of the instruction "T_CONV". If an input and output parameter of the same data type is used, the instruction copies the corresponding value. Parameter Declaration Data type S7-1200 S7-1500 Memory area Description IN Input Integers, TIME, date and time* WORD, integers, timers, date and time* I, Q, M, D, L, P or constant Value to be converted OUT Return Integers, TIME, date and time* WORD, integers, timers, date and time* I, Q, M, D, L, P Result of the conversion * The range of supported data types depends on the CPU. Please refer to the overviews of valid data types for information on the data types supported by the S7-1200 and S7-1500 modules. You can find additional information on valid data types in "Overview of the valid data types (Page 1204)". T_ADD: Add times Description You use this instruction to add the time information in the IN1 input to the time information in the IN2 input. You can query the result in the OUToutput parameter. You can add the following formats: Addition of a time period to another time period. Example: Addition of a TIME data type to another TIME data type. Addition of a time period to a time. Example: Addition of a TIME data type to the DTL data type. The data type for the value at input parameter IN1 and output parameter OUT is defined by the selection in the instruction boxes of the input and output. You can only specify time information in TIME format in the IN2 input parameter (for S7-1500 modules also LTIME). WinCC Basic V13.0 System Manual, 02/2014 2507 Programming the PLC 9.7 References Parameters The following tables show the parameters of the "T_ADD" instruction, according to the possible conversions: Table 9-34 Parameter Addition of a time period to another time period Declaration Data type S7-1200 Memory area Description S7-1500 IN1 Input TIME TIME, LTIME I, Q, M, D, L, P or constant First number to be added IN2 Input TIME TIME, LTIME I, Q, M, D, L, P or constant Second number to be added OUT Return DINT, DWORD, TIME, TOD TIME, LTIME, I, Q, M, D, L, P Result of addition Table 9-35 The data type selection depends on the data types selected for the IN1 and IN2 input parameters. Addition of a time period to a time Parameter Declaration Data type Memory area Description IN1 Input DTL, TOD DT, TOD, LTOD, LDT, DTL I, Q, M, D, L, P or constant First number to be added IN2 Input TIME TIME, LTIME I, Q, M, D, L, P or constant Second number to be added OUT Return DINT, DWORD, TIME, TOD, UDINT, DTL DT, DTL, LDT, TOD, LTOD I, Q, M, D, L, P Result of addition S7-1200 S7-1500 The data type selection depends on the data types selected for the IN1 and IN2 input parameters. You can find additional information on valid data types in "Overview of the valid data types (Page 1204)". T_SUB: Subtract times Description You use this instruction to subtract the time information in the IN2 input parameter from the time information in the IN1 input parameter. You can query the difference in the OUT output parameter. You can subtract the following formats: Subtraction of a time period from another time period Example: Subtraction of a time period of the data type TIME from another time period of the data type TIME. The result can be output to a tag with the TIME format. Subtraction of a time period from a time Example: Subtraction of a time period of the data type TIME from a time of the data type DTL. The result can be output to a tag with the DTL format. 2508 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References You decide the formats of the values in the IN1 input parameter and the OUT output parameter by selecting the data types for the input and output parameters of the instruction. Parameters The following tables show the parameters of the "T_SUB" instruction, according to the possible conversions: Table 9-36 Parameter Subtraction of a time period from another time period Declaration Data type S7-1200 S7-1500 Memory area Description IN1 Input TIME TIME, LTIME I, Q, M, D, L, P or constant Minuend IN2 Input TIME TIME, LTIME I, Q, M, D, L, P or constant Subtrahend OUT Return DINT, DWORD, TIME, TOD, UDINT TIME, LTIME I, Q, M, D, L, P Result of subtraction Memory area Description Table 9-37 Parameter Subtraction of a time period from a time Declaration Data type S7-1200 S7-1500 IN1 Input DTL, TOD TOD, LTOD, DTL, DT, LDT I, Q, M, D, L, P or constant Minuend IN2 Input TIME TIME, LTIME I, Q, M, D, L, P or constant Subtrahend OUT Return DTL, DINT, DWORD, TIME, TOD, UDINT TOD, LTOD, DTL, DT, LDT I, Q, M, D, L, P Result of subtraction You can find additional information on valid data types in "Overview of the valid data types (Page 1204)". T_DIFF: Time difference Description You use this instruction to subtract the time information in the IN2 input parameter from the time information in the IN1 input parameter. The result is sent at output parameter OUT. If the time information at the IN2 input parameter is greater than the time information at the IN1 input parameter, the result is output as a negative value at the OUT output parameter. If the result of the subtraction is outside the TIME range, the result is set to "0" (0:00) and the enable output ENO = "0". WinCC Basic V13.0 System Manual, 02/2014 2509 Programming the PLC 9.7 References Parameters The following table shows the parameters of the "T_DIFF" instruction: Parameter Declaration Data type S7-1200 S7-1500 Memory area Description IN1 Input DTL, DATE, TOD DTL, DATE, DT, TOD, LTOD, LDT I, Q, M, D, L, P or constant Minuend IN2 Input DTL, DATE, TOD DTL, DATE, DT, TOD, LTOD, LDT I, Q, M, D, L, P or constant Subtrahend OUT Return TIME, INT TIME, LTIME, INT I, Q, M, D, L, P Difference of input parameters You can find additional information on valid data types in "Overview of the valid data types (Page 1204)". T_COMBINE: Combine times Description The instruction combines the value of a date with the value of a time and converts this into a combined date and time value. The date is output at the input parameter IN1. A value of between 1990-01-01 and 2089-12-31 must be used for the data type DATE (this is not checked). The time is input at the IN2 input value (TOD/LTOD data type). The combined data type for the date and time value is output at the OUT output value. Parameters The following table shows the parameters of the instruction "T_COMBINE": Parameter Declaration Data type Memory area Description S7-1200 S7-1500 IN1 Input DATE DATE I, Q, M, D, L, P or constant Input tag of the date IN2 Input TOD TOD, LTOD I, Q, M, D, L, P or constant Input tag of the time OUT Return DTL DT, DTL, LDT I, Q, M, D, L, P Return value of the date and time You can find additional information on valid data types under "Overview of the valid data types (Page 1204)". 2510 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Time-of-day functions WR_SYS_T: Set time-of-day Description You use this instruction to set the date and time-of-day of the CPU clock. Enter the date and time-of-day at the input parameter IN . The value must be in the following range: With DT: min. DT#1990-01-01-0:0:0, max. DT#2200-12-31-23:59:59.999 With LDT: min. LDT#1970-1-1-0:0:0.000000000, max. LDT#2200-12-31-23:59:99.999999999 With DTL: min. DTL#1970-01-01-00:00:00.0, max. DTL#2200-12-31-23:59:59.999999999 You can query whether errors have occurred during execution of the instruction in the RET_VAL output parameter. The "WR_SYS_T" instruction cannot be used to pass information about the local time zone or daylight saving time. Parameters The following table shows the parameters of the "WR_SYS_T" instruction: Parameter Declaration Data type S7-1200 S7-1500 Memory area Description IN Input DTL DT, DTL, LDT I, Q, M, D, L, P or constant * Date and time RET_VAL Return INT INT I, Q, M, D, L, P Status of the instruction * The data types DT and DTL cannot be used for the following memory areas: import, output and bit memory. For additional information on valid data types, refer to "Overview of the valid data types (Page 1204)". Parameter RET_VAL Error code* Description (W#16#....) 0000 No error 8080 Error in date 8081 Error in time 8082 Month invalid 8083 Day invalid 8084 Hour information invalid 8085 Minute information invalid 8086 Second information invalid WinCC Basic V13.0 System Manual, 02/2014 2511 Programming the PLC 9.7 References Error code* Description (W#16#....) 8087 Nanosecond information invalid 80B0 The real-time clock has failed * The error codes can be displayed as integer or hexadecimal values in the program editor. For additional information on toggling display formats, refer to "See also". RD_SYS_T: Read time-of-day Description You use this instruction to read out the current date and current time-of-day of the CPU clock. The read out dates are output at the OUT output parameter of the instruction. The provided value does not include information about the local time zone or daylight saving time. You can query whether errors have occurred during execution of the instruction in the RET_VALoutput. Parameters The following table shows the parameters of the "RD_SYS_T" instruction: Parameter Declaration Data type Memory area Description S7-1200 S7-1500 RET_VAL Return INT INT I, Q, M, D, L, P Status of the instruction OUT Output DTL DT, DTL, LDT I, Q, M, D, L, P Date and time of CPU For additional information on valid data types, refer to "Overview of the valid data types (Page 1204)". Parameter RET_VAL Error code* Description (W#16#....) 0000 No error 8081 Time value specified at the OUT parameter is outside the valid value range: With DT: min. DT#1990-01-01-0:0:0, max. DT#2200-12-31-23:59:59.999 With LDT: min. LDT#1970-1-1-0:0:0.000000000, max. LDT#2200-12-31-23:59:59.999999999 With DTL: min. DTL#1970-01-01-00:00:00.0, max. DTL#2200-12-31-23:59:59.999999999 * The error codes can be displayed as integer or hexadecimal values in the program editor. For additional information on toggling display formats, refer to "See also". 2512 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References RD_LOC_T: Read local time Description You use this instruction to read the current local time from the CPU clock and output this at the OUT output. Information on the time zone and the start of daylight saving time and standard time, which you have set in the configuration of the CPU clock, is used to output the local time. Parameter The following table shows the parameters of the "RD_LOC_T" instruction: Parameter Declaration Data type S7-1200 S7-1500 Memory area Description RET_VAL Return INT INT I, Q, M, D, L, P Status of the instruction OUT Output DTL DT, LDT, DTL I, Q, M, D, L, P Local time You can find additional information on valid data types under "Overview of the valid data types (Page 1204)". RET_VAL parameter Error code* Description (W#16#....) 0000 No error 0001 No error. Local time is output as daylight saving time. 8080 Local time cannot be read. 8081 Time value specified at the OUT parameter is outside the valid value range: With DT: min. DT#1990-01-01-0:0:0, max. DT#2089-12-31-23:59:59.999 With LDT: min. LDT#1970-1-1-0:0:0.000000000, max. LDT#2200-12-31-23:59:99.999999999 With DTL: min. DTL#1970-01-01-00:00:00.0, max. DTL#2200-12-31-23:59:59.999999999 * The error codes can be displayed as integer or hexadecimal values in the program editor. For additional information on toggling display formats, refer to "See also". WR_LOC_T: Write local time Description The instruction "WR_LOC_T" is used to set the date and time of the CPU clock. Enter the date and time-of-day as local time at the input parameter LOCTIME. The value must be in the following range: WinCC Basic V13.0 System Manual, 02/2014 2513 Programming the PLC 9.7 References With DT: min. DT#1990-01-01-00:00:00, max. DT#2089-12-31-23:59:59.999 With DTL: min. DTL#1970-01-01-00:00:00.0, max. DTL#2200-12-31-23:59:59.999999999 With LDT: min. LDT#1970-1-1-0:0:0.000000000, max. LDT#2200-12-31-23:59:59.999999999 The granularity of the time information for local time and system time is product-specific and is at least one millisecond. Input values at the LOCTIME parameter which are less than those supported by the CPU are rounded up during system time calculation. You can query whether errors have occurred during execution of the instruction in the RET_VAL output parameter. Use of WR_LOC_T during the time change to daylight savings or standard time Changeover from standard to daylight saving time In the following it is assumed that the time of the changeover is 2:00 am, and that the time is moved forward by one hour. This means there is no hour between 02:00:00:000000000 AM and 02:59:59:999999999 AM. When you specify a corresponding time for LOCTIME, the error code W#16#8089 is generated. DST is irrelevant. Changeover from daylight saving to standard time In the following it is assumed that the time of the changeover is 3:00 am, and that the time is moved back by one hour. This means there are two hours between 02:00:00:000000000 AM and 02:59:59:999999999 AM. For all times for LOCTIME that are between 02:00:00:000000000 AM and 02:59:59:999999999 AM, you therefore need to declare whether the time is before or after the time changeover. The DST parameter is used for this: - With DST=TRUE, the time is in the first of the two hours, i.e. still in daylight savings time. - With DST=FALSE, the time is in the second of the two hours, i.e. in standard time. For all times for LOCTIME that are outside the double hour, DST is irrelevant. 2514 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameters The following table shows the parameters of the "WR_LOC_T" instruction: Parameter Declaration Data type S7-1200 S7-1500 Memory area Description LOCTIME Input DTL DT, DTL, LDT D, L, P or constant Local time DST Input BOOL BOOL I, Q, M, D, L, P, T, C or constant Daylight Saving Time Is only evaluated during the "double hour" at changeover to standard time. TRUE = daylight saving time (first hour) FALSE = standard time (second hour) RET_VAL Return INT INT I, Q, M, D, L, P Error message (see "RET_VAL parameter") You can find additional information on valid data types under "Overview of the valid data types (Page 1204)". RET_VAL parameter Error code* Description (W#16#....) 0000 No error. 8080 The LOCTIME parameter has an invalid value. 8081 Time value specified at the LOCTIME parameter is outside the valid value range: With DT: min. DT#1990-01-01-00:00:00, max. DT#2089-12-31-23:59:59.999 With DTL: min. DTL#1970-01-01-00:00:00.0, max. DTL#2200-12-31-23:59:59.999999999 With LDT: min. LDT#1970-1-1-0:0:0.000000000, max. LDT#2200-12-31-23:59:59.999999999 8082** Invalid value specified for the month (byte 2 in DTL format). 8083** Invalid value specified for the day (byte 3 in DTL format). 8084** Invalid value specified for the hour (byte 5 in DTL format). 8085** Invalid value specified for the minute (byte 6 in format DTL). 8086** Invalid value specified for the second (byte 7 in DTL format). 8087** Invalid value specified for the nanosecond (byte 8 to 11 in DTL format). 8089 Time value does not exist (hour already passed upon changeover to daylight saving time). 80B0 The real-time clock has failed. * The error codes can be displayed as integer or hexadecimal values in the program editor. For additional information on toggling display formats, refer to "See also". ** Only for local time information at the LOCTIME parameter in DTL format. WinCC Basic V13.0 System Manual, 02/2014 2515 Programming the PLC 9.7 References SET_TIMEZONE: Set time zone Description Use the instruction "SET_TIMEZONE" to set the parameter for the local time zone and the daylight saving / standard time changeover. The settings which are carried out with the instruction "SET_TIMEZONE" correspond with the settings for the time-of-day in the properties of the CPU. Define the corresponding parameters in the system data type TimeTransformationRule for execution of the instruction "SET_TIMEZONE". The local time is calculated based on the system time using the settings for the time zone and the daylight saving / standard time changeover. The system time of the CPU is the UTC time. The system time is used exclusively for communication within the system. Parameters The following table shows the parameters of the "SET_TIMEZONE" instruction: Parameter Declaration Data type Memory area Description REQ Input BOOL I, Q, M, D, L, P or constant Setting the parameters which are stored at the parameter TimeZone. TimeZone Input Time Transformation Rule (Page 2517) D, L Store the parameters for the local time zone and the daylight saving / standard time changeover in the system data type TimeTransformationRule. DONE Output BOOL I, Q, M, D, L, P Status parameter: 0: Job not yet started or is still executing 1: Job completed error-free BUSY Output BOOL I, Q, M, D, L, P Status parameter: 0: Job not yet started or already completed 1: Job not yet completed. A new job cannot be started. ERROR Output BOOL I, Q, M, D, L, P Status parameter: 0: No error 1: Error occurred STATUS Output DINT, DWORD, UDINT, WORD I, Q, M, D, L, P Detailed error and status information is output at the parameter STATUS. The parameter is only set for the duration of one call. To display the status, you should therefore copy the STATUS parameter to a free data area. For additional information on valid data types, refer to "Overview of the valid data types (Page 1204)". 2516 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameter STATUS Error code* Description (W#16#....) 7000 No job processing active. 7001 Start of job processing. Parameter BUSY = 1, DONE = 0 7002 Intermediate call (REQ irrelevant): Instruction already active; BUSY has the value "1". 808x Incorrect input at the xth parameter of the system data type TimeTransformationRule. Example: Error code 8084 corresponds with an incorrect input at the 4th parameter (DaylightStartWeek). Only the values 1 to 5 are valid here. 80C3 Temporary resource error: The CPU is currently processing the maximum possible number of simultaneous block calls. "SET_TIMEZONE" cannot be executed unless at least one of the block calls is finished. * The error codes can be displayed as integer or hexadecimal values in the program editor. For additional information on toggling display formats, refer to "See also". TimeTransformationRule Description The times for changeover to daylight saving time and standard time are defined with the system data type TimeTransformationRule. The following options are available for creating the structure TimeTransformationRule: Create a new data block and select as the type TimeTransformationRule. Enter TimeTransformationRule as the Data type in an existing data block or a local interface of a function block. The structure is as follows: Name Data type TimeTransformationRule STRUCT Description Bias INT Time difference between the local time and the system time (UTC) in minutes. DaylightBias INT The time difference between standard and daylight saving time in minutes. Time specification for change to daylight saving time. The following times always refer to the local time. DaylightStartMonth USINT Month in which change is made to daylight saving time: 1 = January 2 = February 3 = March ... 12 = December WinCC Basic V13.0 System Manual, 02/2014 2517 Programming the PLC 9.7 References Name DaylightStartWeek Data type Description USINT Week in which change is made to daylight saving time. 1 = First occurrence of the weekday in the month ... 5 = Last occurrence of the weekday in the month DaylightStartWeekday USINT Weekday on which change is made to daylight saving time: 1 = Sunday DaylightStartHour USINT Hour in which change is made to daylight saving time DaylightStartMinute USINT Minute in which change is made to daylight saving time Time when change is made to standard time, the following times always refer to the local time. StandardStartMonth USINT Month in which change is made to standard time: 1 = January 2 = February 3 = March ... 12 = December StandardStartWeek USINT Week in which change is made to standard time: 1 = First occurrence of the weekday in the month ... 5 = Last occurrence of the weekday in the month StandardStartWeekday USINT Weekday on which change is made to standard time: 1 = Sunday StandardStartHour USINT Hour in which change is made to standard time StandardStartMinute USINT Minute in which change is made to standard time TimeZoneName STRING[80] Name of the time zone, for example: "(GMT+01:00) Amsterdam, Berlin, Bern, Rome, Stockholm, Vienna" SNC_RTCB: Synchronize slave clocks Definition: Synchronization of slave clocks The synchronization of clock slaves refers to the transfer of the date and time-of-day from the clock master of a bus segment to all clock slaves of this bus segment. Description You use this instruction to synchronize all slave clocks present on a bus segment independent of the assigned synchronization interval. Successful synchronization is only possible if "SNC_RTCB" is called on a CPU whose real-time clock was assigned as the master clock for at least one bus segment. 2518 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameters The following table shows the parameters of the "SNC_RTCB" instruction: Parameter Declaration Data type Memory area Description RET_VAL Output INT I, Q, M, D, L If an error occurs while the instruction is being executed, the return value contains an error code. For additional information on valid data types, refer to "Overview of the valid data types (Page 1204)". Parameter RET_VAL Error code* Explanation (W#16#...) 0000 No error occurred during synchronization. 0001 The existing clock was not assigned the master clock function for any of the bus segments. General error information See also: GET_ERR_ID: Get error ID locally (Page 1964) * The error codes can be displayed as integer or hexadecimal values in the program editor. For additional information on toggling display formats, refer to "See also". TIME_TCK: Read system time Description With the "TIME_TCK" instruction, you read the system time of the CPU. The system time is a time counter that counts from 0 to a maximum of 2147483647 ms. In case of an overflow, the system time is counted again starting with "0". The time scale and the accuracy of the system time is 1 ms. The system time is only influenced by the operating modes of the CPU. You can use the system time, for example, to measure the duration of processes by comparing the results of two "TIME_TCK" calls. The instruction does not provide any error information. The following table provides an overview of how the system time changes depending on the operating modes of the CPU. Mode System time ... Startup ... is constantly updated RUN WinCC Basic V13.0 System Manual, 02/2014 STOP ... is stopped and retains the current value Warm restart ... is deleted and restarts with "0" 2519 Programming the PLC 9.7 References Parameter The following table shows the parameters of the instruction "TIME_TCK": Parameters Declaration Data type Memory area Description RET_VAL Return TIME I, Q, M, D, L The RET_VAL parameter contains the read system time in the range from 0 to 231 -1 ms. You will find more detailed information on valid data types in "Overview of the valid data types (Page 1204)". RTM: Runtime meters Description You can use this instruction to set, start, stop, and read out a 32-bit runtime meter of your CPU. Ensure that the runtime meter can also be stopped or restarted during execution of the user program, which may render the saved values incorrect. Parameters The following table shows the parameters of the "RTM" instruction: Parameter Declaration Data type Memory area Description NR Input RTM I, Q, M, D, L or constant Number of the runtime meter Numbering starts with 0. For information on the number of runtime meters of your CPU, refer to the technical data. MODE Input BYTE I, Q, M, D, L or constant Job ID: 0: Read out (the status is then written to CQ and the current value to CV). After the runtime meter has reached (2E31) -1 hours, it stops at the highest value that can be displayed and outputs an "Overflow" error message. 1: start (at the last counter value) 2: stop 4: set (to the value specified in PV) 5: set (to the value specified in PV) and then start 6: set (to the value specified in PV) and then stop PV 2520 Input DINT I, Q, M, D, L or constant New value for the runtime meter WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameter Declaration Data type Memory area Description RET_VAL Return INT I, Q, M, D, L If an error occurs while the instruction is being executed, the return value contains an error code. CQ Output BOOL I, Q, M, D, L Status of the runtime meter (1: running) CV Output DINT I, Q, M, D, L Current value of the runtime meter For additional information on valid data types, refer to "Overview of the valid data types (Page 1204)". Parameter RET_VAL Error code Explanation (W#16#...) 0000 No error 8080 Wrong number for the runtime meter 8081 A negative value was passed to the PV parameter. 8082 Overflow of the runtime meter 8091 The MODE input parameter contains an invalid value. General error information See also: Evaluating errors with GET_ERR_ID (Page 2462) 9.7.3.2 String + Char S_MOVE: Move character string Description You can use this instruction to move the content of a string (W)STRING. The string in the IN input parameter is copied to the OUT output parameter. The tags at the input parameter IN and the output OUT must have the same data type. You can use the "MOVE_BLK" and "UMOVE_BLK" instructions to copy tags of data type ARRAY. Parameters The following table shows the parameters of the "S_MOVE" instruction: Parameters Declaration Data type S7-1200 S7-1500 Memory area Description IN Input STRING STRING, WSTRING D, L or constant Source string OUT Output STRING STRING, WSTRING D, L or constant Destination string WinCC Basic V13.0 System Manual, 02/2014 2521 Programming the PLC 9.7 References You can find additional information on valid data types under "Overview of the valid data types (Page 1204)". S_COMP: Compare character strings Description The instruction compares the contents of two tags in the STRING format and outputs the result of the comparison as a return value. The tags that are to be compared will be interconnected at the IN1 and IN2 inputs. You can only assign a symbolically defined tag for the input parameters. Use the instruction box to select the comparison condition. If the comparison condition (for example, greater than or equal to) is satisfied, the signal state is set to "1" at the output parameter OUT . The following comparison options can be used: Symbol Description EQ The return value has the signal state "1" if the string at the IN1 parameter is the same as the string at the IN2 parameter. NE The return value has the signal state "1" if the string at the IN1 parameter is not equal to the string at the IN2 parameter. GT (1) The return value has the signal state "1" if the string at the IN1 parameter is greater than the string at the IN2 parameter. LT (1) The return value has the signal state "1" if the string at the IN1 parameter is less than the string at the IN2 parameter. GE (1) The return value has the signal state "1" if the string at the IN1 parameter is greater than or equal to the string at the IN2 parameter. LE (1) The return value has the signal state "1" if the string at the IN1 parameter is less than or equal to the string at the IN2 parameter. The characters are compared by their ASCII code (for example, 'a' is greater than 'A'), starting from the left. The first character to be different decides the result of the comparison. If the first characters are the same, the longer string is greater. (1) Parameters The following table shows the parameters of the "S_COMP" instruction: Parameters Declaration Data type Memory area Description IN1 Input STRING* D, L or constant Input tag in the STRING format. IN2 Input STRING* D, L or constant Input tag in the STRING format. OUT Output BOOL I, Q, M, D, L Result of comparison * Define the maximum length of the character string if you use the data type STRING in the interface declaration for a temporary tag (you will find further information in the description of the data type). 2522 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References For additional information on valid data types, refer to "Overview of the valid data types (Page 1204)". S_CONV: Convert character string Description You use this instruction to convert the value at the IN input to the data format you have specified in the OUT output. You decide the output format of the conversion by selecting a data type for the OUT output parameter. The following conversions are possible: Conversion of a character string (STRING) to: - Numerical value (integer or floating-point number) The conversion is performed for all characters of the character string specified in the IN input parameter. Permitted characters are the digits "0" to "9", the decimal point, and the plus and minus signs. The first character of the string may be a valid number or a sign. Leading spaces and exponential notations are ignored. - A character (CHAR) The first character of the character string is transferred to the parameter OUT when a character string is converted to a character (CHAR). Conversion of a numerical value or character to a character string (STRING): - You decide the format of the numeric value to be converted by selecting a data type for the IN input. A valid tag of the STRING data type must be specified in the OUT output. The length of the character string after conversion depends on the value at the IN input. - The conversion result is saved as a string starting at the third byte. The first byte of the string records the maximum length and the second byte the actual length of the character string. Positive numeric value are output without a sign. - When you convert zero (e.g. INT_TO_STRING(0)), the string will be 6 characters long. - The first character of the character string is filled with spaces when converting to a numerical value. The number of spaces depends on the length of the numerical value. - The character is written at the first position in the character string when converting to a character (CHAR). Note Exponential notation during conversion from floating-point numbers Do not use exponential notation ("e" or "E") for the conversion from floating-point numbers with the instruction "S_CONV". Instead, use the instruction "STRG_VAL (Page 2524)" for the conversion of floating-point numbers with exponential notation. You can use the FORMAT parameter of the instruction to select exponential notation as input format. WinCC Basic V13.0 System Manual, 02/2014 2523 Programming the PLC 9.7 References Parameters The following tables show the parameters of the "S_CONV" instruction, according to the possible conversions: Table 9-38 Parameters for converting a character string to a numeric value: Parameters Declaration Data type Memory area Description IN Input STRING D, L or constant Value to be converted OUT Output CHAR, USINT, UINT, UDINT, ULINT, SINT, INT, DINT, LINT, REAL, LREAL I, Q, M, D, L Result of the conversion Table 9-39 Parameter when converting a numerical value or character to a character string: Parameter Declaration Data type Memory area IN Input CHAR, USINT, UINT, UDINT, ULINT, SINT, INT, DINT, LINT, REAL, LREAL I, Q, M, D, L or constant Value to be converted Description OUT Output STRING D, L Result of the conversion For additional information on valid data types, refer to "Overview of the valid data types (Page 1204)". STRG_VAL: Convert character string to numerical value Description The instruction "STRG_VAL" converts a character string to an integer or a floating-point number: You specify the character string to be converted in the IN input parameter. You define the format of the output value by selecting a data type for the OUT output parameter. Permitted characters for the conversion are the digits "0" to "9", the decimal point, the decimal comma, notations "E" and "e", and the plus and minus characters. The conversion can be interrupted by invalid characters. The "STRG_VAL" instruction is not supported by the SCL programming language. 2524 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameters The following table shows the parameters of the "STRG_VAL" instruction: Parameter Declaration Data type S7-1200 S7-1500 Memory area Description IN Input STRING STRING, WSTRING D, L or constant Numeric character string to be converted FORMAT Input WORD WORD I, Q, M, D, L, P or constant Output format of the characters P Input UINT UINT I, Q, M, D, L, P or constant Reference to the first character to be converted (first character = 1, the value "0" or a value > length of the string is invalid) OUT Output USINT, SINT, UINT, INT, UDINT, DINT, REAL, LREAL USINT, SINT, UINT, INT, UDINT, DINT, ULINT, LINT, REAL, LREAL I, Q, M, D, L, P Result of the conversion You can find additional information on valid data types under "Overview of the valid data types (Page 1204)". FORMAT parameter You use the FORMAT parameter to specify how the characters of a character string are to be interpreted. Exponential values can also be converted and represented with the "STRG_VAL" instruction. The following table shows the possible values of the FORMAT parameter and their meaning: Value Notation Decimal representation Decimal fraction "." (W#16#....) 0000 0001 0002 "," Exponential 0003 0004 to FFFF "." "," Invalid values P parameter The conversion starts at the character whose position you specified in the P parameter. If, for example, the value "1" is specified in the P parameter, the conversion starts at the first character of the specified character string. WinCC Basic V13.0 System Manual, 02/2014 2525 Programming the PLC 9.7 References Example The following table shows examples of the conversion of a character string to a numeric value: IN (STRING) FORMAT (W#16#....) OUT (data type) OUT (value) ENO status '123' 0000 INT/DINT 123 1 '-00456' 0000 INT/DINT -456 1 '123.45' 0000 INT/DINT 123 1 '+2345' 0000 INT/DINT 2345 1 '00123AB' 0000 INT/DINT 123 1 '123' 0000 REAL 123.0 1 '-00456' 0001 REAL -456.0 1 '+00456' 0001 REAL 456.0 1 '123.45' 0000 REAL 123.45 1 '123.45' 0001 REAL 12345.0 1 '123,45' 0000 REAL 12345.0 1 '123,45' 0001 REAL 123.45 1 '.00123AB' 0001 REAL 123.0 1 '1.23e-4' 0000 REAL 1.23 1 '1.23E-4' 0000 REAL 1.23 1 '1.23E-4' 0002 REAL 1.23E-4 1 '12,345.67' 0000 REAL 12345.67 1 '12,345.67' 0001 REAL 12.345 1 '3.4e39' 0002 REAL W#16#7F800000 1 '-3.4e39' 0002 REAL W#16#FF800000 1 '1.1754943e-38' 0002 REAL 0.0 1 '12345' -/- SINT 0 0 'A123' -/- -/- 0 0 '' -/- -/- 0 0 '++123' -/- -/- 0 0 '+-123' -/- -/- 0 0 VAL_STRG: Convert numerical value to character string Description The "VAL_STRG" instruction is used to convert a numerical value into a character string. You specify the value to be converted in the IN input parameter. You decide the format of the numeric value by selecting a data type. You query the result of the conversion in the OUT output parameter. Permitted characters for the conversion are the digits "0" to "9", the decimal point, the decimal comma, notations "E" and "e", and the plus and minus characters. The conversion can be interrupted by invalid characters. 2526 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References The "VAL_STRG" instruction is not supported by the SCL programming language. Parameters The following table shows the parameters of the "VAL_STRG" instruction: Parameter Declaration Data type S7-1200 S7-1500 Memory area Description IN Input USINT, SINT, UINT, INT, UDINT, DINT, REAL, LREAL USINT, SINT, UINT, INT, UDINT, DINT, ULINT, LINT, REAL, LREAL I, Q, M, D, L, P or constant Value to be converted SIZE Input USINT USINT I, Q, M, D, L, P or constant Number of character positions PREC Input USINT USINT I, Q, M, D, L, P or constant Number of decimal places FORMAT Input WORD WORD I, Q, M, D, L, P or constant Output format of the characters P InOut UINT UINT I, Q, M, D, L, P or constant Character starting at which the result is written. OUT Output STRING STRING, WSTRING D, L Result of the conversion You can find additional information on valid data types under "Overview of the valid data types (Page 1204)". P parameter With the P parameter, you specify the character in the string starting at which the result is written. If, for example, the value "2" is specified in the P parameter, the converted value is saved starting at the second character of the string. SIZE and P parameters Use the SIZE parameter to specify how many characters of the character string will be written. This is counted starting from the character specified in the P parameter. If the output value is shorter than the specified length, the result is written to the character string right-justified. The empty character positions are filled with blanks. FORMAT parameter Use the FORMAT parameter to specify how the numerical value is interpreted during conversion and written to the character string. You can specify only tags of the FORMAT data type in the USINT parameter. The following table shows the possible values of the FORMAT parameter and their meaning: WinCC Basic V13.0 System Manual, 02/2014 2527 Programming the PLC 9.7 References Value Notation Sign Decimal representation Decimal fraction "-" "." (W#16#....) 0000 0001 "," 0002 Exponential "." 0003 "," 0004 Decimal fraction "+" and "-" "." 0005 "," 0006 Exponential "." 0007 "," 0008 to FFFF Invalid values PREC parameter Use the PREC parameter to define the number of decimal places when converting floatingpoint numbers. A maximum precision of seven numbers is supported for numerical values of the REAL data type. If the value to be converted is an integer, you use the PREC parameter to specify the position where the decimal point will be placed. Example The following table shows examples of the conversion of numeric values to a character string. IN (value) IN (data type) P SIZE FORMAT (W#16#....) PREC OUT (STRING) ENO status 123 UINT 16 10 0000 0 xxxxxxx123 C 1 0 UINT 16 10 0000 2 xxxxxx0.00 C 1 12345678 UDINT 16 10 0000 3 x12345.678 C 1 12345678 UDINT 16 10 0001 3 x12345.678 C 1 123 INT 16 10 0004 0 xxxxxx+123 C 1 -123 INT 16 10 0004 0 xxxxxx-123 C 1 -0.00123 REAL 16 10 0004 4 xxx-0.0012 C 1 -0.00123 REAL 16 10 0006 4 -1.2300E-3 C 1 -Inf 1) REAL 16 10 -/- 4 xxxxxx-INF C 0 +Inf REAL 16 10 -/- 4 xxxxxx+INF C 0 NaN 3) REAL 16 10 -/- 4 xxxxxxxNaN C 0 12345678 UDINT 16 6 -/- 3 xxxxxxxxxx C 0 2) "x" represents blanks 1) -Inf: Floating-point number representing a negative infinite value. 2) +Inf: Floating-point number representing a positive infinite value. 3) NaN: Value returned as the result of invalid math operations. 2528 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Strg_TO_Chars: Convert character string to Array of CHAR Description Use the instruction to copy a character string (W)STRING into a structure of the data type Array of CHAR or Array of BYTE. Only ASCII characters are valid for the copy process. Specify the character string at the input parameter STRG. The characters are written to a data type Array of CHAR / BYTE at the parameter CHARS. - The number of characters in the structure Array of CHAR / BYTE should be at least the same number as were copied from the character string STRING. - If the structure Array of CHAR / BYTE contains less characters than in the character string then the characters are written up to the maximum length of the Array of CHAR / BYTE. - If the character string contains a character "$00" then the copy process is only carried out up to the corresponding position. - The number of copied characters is output at the parameter CNT. Use the parameter PCHARS to define the character in the structure after which Array of CHAR / BYTE should be written. - Example: Use the value "2" at the parameter PCHARS if writing should take place after the third character: 675,1*>@ %\WH %\WH %\WH %\WH %\WH %\WH 7 ( 6 7 7 ( 6 7 &KDU>@ &KDU>@ &KDU>@ &KDU>@ S&KDUV $UUD\>@RI&+$5 &KDU>@ &KDU>@ - The lower index limit of the array is used as the standard ("0") (e.g. CHAR[0] at an Array [0..5] of CHAR). Note Use of the instruction with S7-1200 V2.0 S7-1200 up to Version 2.0 only supports Array [0 .. n] of CHAR / BYTE. Negative index limits (e.g. Array [-3..2] of CHAR) are not permissible. This restriction is not checked by the software. WinCC Basic V13.0 System Manual, 02/2014 2529 Programming the PLC 9.7 References Parameters The following table shows the parameters of the instruction "Strg_TO_Chars": Parameter STRG Declaration Input Data type Memory area Description STRING, WSTRING D, L or constant The copy source S7-1200 S7-1500 STRING Character string with a maximum length of 254 characters. PCHARS Input DINT DINT I, Q, M, D, L, P or constant Position in the structure Array of (W)CHAR / BYTE after which the characters in the character string are written. CHARS InOut VARIANT VARIANT D, L The copy target The characters can be copied to a structure of the data type Array of (W)CHAR or Array of BYTE. CNT Output UINT UINT I, Q, M, D, L, P Number of copied characters. You can find additional information on valid data types under "Overview of the valid data types (Page 1204)". 2530 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Chars_TO_Strg: Convert Array of CHAR to character string Description Use the instruction "Chars_TO_Strg" to copy the character from a structure of a data type Array of CHAR or Array of BYTE to a character string STRING. Only ASCII characters are valid for the copy process. At the input parameter CHARS, enter the characters of the structure Array of (W)CHAR / BYTE which are to be copied to a character string. The characters are written to a data type STRING at the parameter STRG. - The number of characters in the character string STRING should be at least the same number as were copied from the field Array of CHAR. - If the character string is shorter than the number of characters in the structure Array of CHAR / BYTE, the maximum length of characters is written in the character string. - If the structure Array of CHAR / BYTE contains a character "$00" then the copy process is only carried out up to the corresponding position. Use the parameter PCHARS to define the position in the structure Array of CHAR / BYTE after which the character it to be copied. - Example: Use the value "2" at the parameter PCHARS if copying is to take place after the third character in the structure: $UUD\>@RI&+$5 &KDU>@ &KDU>@ &KDU>@ &KDU>@ 7 ( 6 7 %\WH %\WH &KDU>@ &KDU>@ %\WH %\WH S&KDUV 675,1*>@ 6 7 %\WH %\WH - The lower index limit of the array is used as the standard ("0") (e.g. CHAR[0] at Array [0..5] of CHAR). - If an index is specified at parameter PCHARS and the index is not contained in the copy source (e.g. "7" at Array [0..5] of CHAR) then the instruction is not executed. Note Use of the instruction with S7-1200 V2.0 S7-1200 up to Version 2.0 only supports Array [0 .. n] of CHAR / BYTE. Negative index limits (e.g. Array [-3..2] of CHAR) are not permissible. This restriction is not checked by the software. WinCC Basic V13.0 System Manual, 02/2014 2531 Programming the PLC 9.7 References Parameters The following table shows the parameters of the instruction "Chars_TO_Strg": Parameter CHARS Declaration Input Data type S7-1200 S7-1500 VARIANT VARIANT Memory area Description D, L The copy source Structure Array of CHAR / BYTE from which the character is copied. PCHARS Input DINT DINT I, Q, M, D, L, P or constant Position in the structure Array of (W)CHAR / Array of BYTE after which the characters are copied. CNT Output UINT UINT I, Q, M, D, L, P Number of characters to be copied. All characters were copied at "0". STRG Output STRING STRING, WSTRING D, L The copy target Character string You can find additional information on valid data types under "Overview of the valid data types (Page 1204)". MAX_LEN: Determine the length of a character string Description A tag of the STRING data type contains two lengths: the maximum length and the current length (this is the number of currently valid characters). The maximum length of the character string is specified for each tag in the STRING keyword in square brackets. The number of bytes occupied by a string is 2 greater than the maximum length. The current length represents the number of the character places actually used. The current length must be less than or equal to the maximum length. You use the "MAX_LEN" instruction to query the maximum length of the character string specified at the IN input parameter and output this information as a numerical value at the OUT output parameter. If errors occur during processing of the instruction, then an empty string will be output. Note Reading out the current length You can also use the LEN (Page 2543) instruction to read out the current length of a string. 2532 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameter The following table shows the parameters of the "MAX_LEN" instruction: Parameter Declaration Data type Memory area Description IN Input STRING D, L or constant Character string OUT Return INT I, Q, M, D, L, P Maximum number of characters You will find more detailed information on valid data types in "Overview of the valid data types (Page 1204)". Join: Join multiple strings Description The "JOIN" instruction connects multiple strings into an array. To convert multiple strings into a single one, the instruction provides the following functions: Format selection You use the first bit in the Mode parameter to select whether you want to use CSV or FSR as the format for the array. - With CSV (Comma Separated Values), the contents of the source strings are written consecutively and separated with a delimiter. Example: 1963,Miller,John,CitynameA,Roadname 1974,Jackson,Peter,CitynameB,VeryLongRoadname - With FSR (Fixed Size Records), a certain number of characters is defined for each value (each source character string). If fewer characters are required, the characters are padded with delimiters. If more characters are required, the text is truncated. Example: 1963Miller,,,,,,,John,,,,,,CitynameA,,,,Roadname,,,,,, 1974Jackson,,,,,,Peter,,,,,CitynameB,,,,VeryLongRoadna Selection of the delimiter for the source strings You can use the RecSeparator parameter to select the delimiter to be used for each string. You should select a character based on the content of the input strings at the SrcStruct parameter. If the input strings contain a comma within a string, for example, the comma should not used as a delimiter. The data type that you use for the delimiter must correspond to the destination array at the DstArray parameter in order for the delimiter to be included in what is written in the array. Selection of the delimiter for the end of all source strings You can use the third bit of the Mode parameter to specify whether an additional character should be written as a delimiter at the end of the copied characters in the destination array (DstArray parameter). Specify the character to be used as a delimiter at the EndSeparator parameter. Make sure to use a character other than the one set for the RecSeparator parameter (delimiter for individual strings). If the two delimiters are indistinguishable, you will obtain unexpected results if you reverse the conversion using the "SPLIT" instruction. WinCC Basic V13.0 System Manual, 02/2014 2533 Programming the PLC 9.7 References Selection of the source strings You specify the source strings at the SrcStruct parameter. For the data type, you can use Array of STRING or Array of WSTRING or structures which only contain the STRING or WSTRING data type. This also applies to user data types or nested structures. You can use these as long as they exclusively contain the data type STRING or WSTRING respectively. Specification of the number of joined strings If you use an Array of STRING or Array of WSTRING at the SrcStruct parameter (source string) (no nested structures), you can use the Count parameter to specify the number of source strings that have been joined to form a single string. If you use a data type other than Array of (W)STRING at the SrcStruct parameter, the Count parameter is ignored. This makes it possible to connect only a part of a large array. Selection of a destination area for writing the array You use the Array of (W)CHAR data type at the DstArray parameter. It is not possible to use the STRING or WSTRING data types here, because the length is limited to 256 characters for STRING. Index of the position in the array (DestArray target parameter) The conversion starts at this position and the instruction reads the Position parameter to determine the position at which the conversion is completed. This enables follow-up calls of the instruction for filling the array. Parameters The following table shows the parameters of the instruction "JOIN": Parameter Declaration Data type Memory area Description Mode Input DWORD I, Q, M, D, L or constant Specifies how the merger to string is performed (see Mode" parameter). RecSeparator Input VARIANT I, Q, M, D, L Delimiter for the source strings With CSV: Character that is used as a delimiter for the individual strings. With FSR: Character that is used as a fill character for the individual strings. EndSeparator Input VARIANT I, Q, M, D, L Delimiter for the end of the conversion Delimiter that is written at the end of the characters if bit 3 = 1 has been set for the Mode parameter. SrcStruct Input VARIANT I, Q, M, D, L Pointer to the source strings. Count Input UDINT I, Q, M, D, L Number of strings that were joined. The Count parameter can only be used when an Array of (W)STRING has been used at the SrcStruct parameter. DestArray InOut VARIANT I, Q, M, D, L Area in which the characters are written after the conversion. Use the Array [0 .. x] of CHAR/WCHAR data type at the DestArray parameter. You can set the length (x) of the array based on the length of the source strings at the SrcStruct parameter. 2534 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameter Declaration Data type Memory area Description Position InOut UDINT I, Q, M, D, L Index the position in the total string Ret_Val Return UINT I, Q, M, D, L Status of instruction (see table "RET_VAL parameter"). You can find additional information on valid data types under "Overview of the valid data types (Page 1204)". Mode parameter Bit Bit value "0" Bit value "1" Description 0 CSV format (Comma Separated Values) FSR format (Fixed Size Record) Selection of the format: With CSV, the source strings are separated by a delimiter in the destination array. With FSR, the source strings are written into the destination array with the fill characters defined at the RecSeparator parameter. 1 - - Irrelevant for the "JOIN" instruction. 2 - - Reserved (irrelevant for bit value) 3 Write no additional delimiters. Write character defined by the EndSeparator parameter at the end of the read characters. Select whether an additional character is to be written as a delimiter at the end of the characters in the array (DestArray parameter). 4 - - Irrelevant for the "JOIN" instruction. RET_VAL parameter Error code* Explanation (W#16#...) 0000 No error. 0001 Additional characters are ignored. 8190 Selection at the Mode parameter is not supported. 8x20 Source strings invalid. 8x50 VARIANT points to empty content. 8x52 VARIANT points to a block that has not been created with optimized access. 8x53 VARIANT points to data structure that is too short. 8x54 Invalid data type 8882 The value at the Position parameter is outside the source string. 8x84 Found additional characters. 80B4 Different data types at parameters SrcStruct (source) and DestArray (destination) or at separators (parameters RecSeparator and EndSeparator). 80B5 Buffer overflow with the instruction. The characters were not fully generated at the DestArray parameter. WinCC Basic V13.0 System Manual, 02/2014 2535 Programming the PLC 9.7 References Error code* Explanation (W#16#...) General error information See also: GET_ERR_ID: Get error ID locally (Page 1964) * Note the following for the error codes: The error codes can be displayed as integer or hexadecimal values in the program editor. For additional information on toggling display formats, refer to "See also". The "x" in the second position of the listed error codes stands for the parameter that caused the error. Example: Error code 8352 hex = error occurred at 3rd parameter (EndSeparator), see Parameter table. If the error cannot be clearly assigned to a specific parameter, "0" is output. Example: The CHAR data type is used for the delimiter (RecSeparator parameter). WCHAR is used as data type for the array at the DestArray parameter. Error code 80B4 is output in this case. Split: Splitting an array of characters into multiple strings Description The "SPLIT" instruction converts an array (Array of CHAR / WCHAR) into several separate strings (Array of STRING / WSTRING or structure). To convert the array into several strings, specify the following information: Selection of array to be read You specify the array to be read at the SrcArray parameter. Make sure that the data types used for the input and output parameters match any other parameters used. If you use an array with the CHAR data type at the SrcArray parameter, for example, you must use the CHAR data type for the delimiter (Rec/EndSeparator) and the structure must only contain strings with the STRING data type at the DestStruct parameter. Selection of the format for the array to be read You use the first bit of the Mode parameter to specify whether the array to be read has the CSV or FSR format (for a definition, see the "JOIN (Page 2533)" instruction). Delimiter used for the array to be read - If the array to be read has CSV format, specify which delimiter was used at the RecSeparator parameter. - If the array to be read has FSR format, specify which fill character was used at the RecSeparator parameter. Selection of the delimiter for the end of the total string Specify the delimiter after which the reading of the array should stop at the EndSeparator parameter. The "SPLIT" instruction stops at this position and outputs the string that has been found. It should be noted, that the EndSeparator delimiter is evaluated with higher priority than the RecSeparator delimiter. If the delimiter at the EndSeparator parameter is used in a string to be read (between two RecSeparator delimiters), all content after the EndSeparator delimiter is ignored. 2536 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Specification of the position starting at which the array is read The conversion starts at this position in the array and the instruction reads the Position parameter to determine the position at which the conversion is completed. This enables follow-up calls of the instruction for filling the various strings at the DestStruct parameter. Outputting the number of read strings If you use an Array of STRING at the DestStruct parameter, you can use the Count parameter to output the number of read strings. Only strings with content are counted. If you use a data type other than Array of STRING at the DestStruct parameter, "0" is output at the Count parameter. Parameters The following table shows the parameters of the "SPLIT" instruction: Parameter Declaration Data type Memory area Description Mode Input DWord I, Q, M, D, L or constant Specifies how the split into multiple strings is performed (see "Mode" parameter). RecSeparator Input Variant I, Q, M, D, L Delimiter or fill character With CSV: Character that was used in the array to be read to identify the individual strings. With FSR: Character that has been used as a fill character in the array to be read. EndSeparator Input Variant I, Q, M, D, L Delimiter used to define the end of the total string in the array to be read. SrcArray Input Variant I, Q, M, D, L Pointer to the array to be read (Array of CHAR/WCHAR) DestStruct InOut Variant I, Q, M, D, L Structure which includes the converted strings (Array of STRING / WSTRING). Position InOut UDInt I, Q, M, D, L Position from which the array is to be read at the SrcArray parameter. Ret_Val Return Int I, Q, M, D, L Result of instruction execution / error code (see table "Ret_Val parameter") Count Output UDInt I, Q, M, D, L Number of strings that were found. You can find additional information on valid data types under "Overview of the valid data types (Page 1204)". WinCC Basic V13.0 System Manual, 02/2014 2537 Programming the PLC 9.7 References Mode parameter Bit Bit value "0" Bit value "1" Description 0 CSV format (Comma Separated Values) FSR format (Fixed Size Record) Basic mode: Selection of CSV or FSR 1 With CSV: Additional characters are written to the following string. With CSV: Additional characters are removed. Use bit 1 to specify how you want to deal with additional characters: With FSR: Fill characters remain in string. With CSV: - If the bit is set, additional characters that do not fit in the destination string are ignored. Example: The instruction writes to a string with a length of 16 characters (STRING[16] data type). No delimiter is contained in the source after the first 16 characters. If bit 1 is set, the extra characters are ignored and the instruction continues to read the array. - If the bit is not set, the instruction stops in such a case and generates an error message at the Ret_Val parameter. With FSR: Fill characters are removed. With FSR: - - If the bit is set, the fill characters used are not written to the destination string. - If the bit is not set, the fill characters are written to the destination string. 2 - 3 Separator is retained. Separator is removed. Specification of whether the delimiter is removed at the end of the total string. 4 Leave unwritten strings (STRING) at length. Set unwritten strings (STRING) to length "0". Reserved for use in future versions. Specification of whether unused strings (STRING) at the DestStruct parameter are to be set to the length "0". RET_VAL parameter Error code* Explanation (W#16#...) 0000 No error. 0001 Additional characters are ignored. 8190 Selection at the Mode parameter is not supported. 8x20 Source strings invalid. 8x50 VARIANT points to empty content. 8x52 VARIANT points to a block that has not been created with optimized access. 8x53 VARIANT points to data structure that is too short. 8x54 Invalid data type 8882 The value at the Position parameter is outside the source string. 8x84 Found additional characters. 80B4 Different data types at parameters SrcStruct (source) and DestArray (destination) or at separators (parameters RecSeparator and EndSeparator). 80B5 Buffer overflow with the instruction. The strings were not fully generated at the DestArray parameter. 2538 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Error code* Explanation (W#16#...) General error information See also: GET_ERR_ID: Get error ID locally (Page 1964) * Note the following for the error codes: The error codes can be displayed as integer or hexadecimal values in the program editor. For additional information on toggling display formats, refer to "See also". The "x" in the second position of the listed error codes stands for the parameter that caused the error. Example: Error code 8352 hex = error occurred at 3rd parameter (EndSeparator), see Parameter table. If the error cannot be clearly assigned to a specific parameter, "0" is output. Example: The CHAR data type is used for the delimiter (RecSeparator parameter). WCHAR is used as data type for the array at the DestArray parameter. Error code 80B4 is output in this case. ATH: Convert ASCII string to hexadecimal number Description You use the instruction "ATH" to convert the ASCII character string specified at the IN input parameter into a hexadecimal number. The result of the conversion is output to the OUT output parameter. You can reference the following data types using the pointer in the IN parameter (ASCII): STRING, Array of CHAR, Array of BYTE, WSTRING, Array of WCHAR. You can reference the following data types using the pointer in the OUT parameter (hexadecimal): Bit strings, integers, STRING, Array of CHAR, Array of BYTE, WSTRING, Array of WCHAR. With the N parameter, you specify the number of ASCII characters to be converted. A maximum of 32767 valid ASCII characters can be converted. Only digits "0" to "9", upper case letters "A" to "F", and lower case letters "a" to "f" can be interpreted. All other characters are converted to zeros. Since 8 bits are required for the ASCII character and only 4 bits for the hexadecimal digit, the output word length is only half of the input word length. The ASCII characters are converted and positioned in the output in the same order as they are read in. If there is an odd number of ASCII characters, the hexadecimal number is padded with zeros in the nibble to the right of the last converted hexadecimal number. Parameters The following table shows the parameters of the "ATH" instruction: WinCC Basic V13.0 System Manual, 02/2014 Parameter Declaration Data type Memory area Description IN Input VARIANT I, Q, D, L Pointer to ASCII character string N Input INT I, Q, M, D, L or constant Number of ASCII characters to be converted RET_VAL Return WORD I, Q, M, D, L Status of the instruction OUT Output VARIANT I, Q, M, D, L Hexadecimal number 2539 Programming the PLC 9.7 References You can find additional information on valid data types in "Overview of the valid data types (Page 1204)". RET_VAL parameter Error code Description (W#16#....)* 0000 No error 0007 Invalid character. Only the following ASCII characters may be used: Digits "0" to "9", upper case letters "A" to "F", lower case letters "a" to "f". 8101 Invalid pointer in the IN parameter, e.g., because a non-existing data block is referenced. 8182 Input buffer is too small for data in the N parameter. 8120 Invalid format in the IN parameter. 8151 Non-supported data type in the IN parameter. 8401 Invalid pointer in the OUT parameter, e.g., because a non-existing data block is referenced. 8482 Output buffer is too small for data in the N parameter. 8420 Invalid format in the OUT parameter. 8451 Non-supported data type in the OUT parameter. * The error codes can be displayed as integer or hexadecimal values in the program editor. For additional information on toggling display formats, refer to "See also". ASCII characters and hexadecimal values The following table shows the ASCII characters and the corresponding hexadecimal values: 2540 ASCII character ASCII-coded hexadecimal value Hexadecimal digit "0" 30 0 "1" 31 1 "2" 32 2 "3" 33 3 "4" 34 4 "5" 35 5 "6" 36 6 "7" 37 7 "8" 38 8 "9" 39 9 "A" 41 A "B" 42 B "C" 43 C "D" 44 D "E" 45 E "F" 46 F WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Example The following table shows examples of the conversion of ASCII character strings to hexadecimal numbers: IN N OUT ENO status '0123' 4 16#0123 1 '123AFx1a23' 10 16#123AF01a23 0 HTA: Convert hexadecimal number to ASCII string Description You use the instruction "HTA" to convert the hexadecimal number specified at the IN input into an ASCII character string. The result of the conversion is stored at the address specified in the OUT parameter. You can reference the following data types using the pointer in the IN parameter (hexadecimal): Bit strings, integers, STRING, Array of CHAR, Array of BYTE, WSTRING, Array of WCHAR. You can reference the following data types using the pointer in the OUT parameter (ASCII): STRING, Array of CHAR, Array of BYTE , WSTRING, Array of WCHAR. With the N parameter, you specify the number of hexadecimal bytes to be converted. Since 8 bits are required for the ASCII character and only 4 bits for the hexadecimal digit, the output value is twice as long as the input value. Each nibble of the hexadecimal number is converted to a character while maintaining the original order. A maximum of 32767 characters can be written to the ASCII character string. The result of the conversion is represented by the digits "0" to "9" and upper-case letters "A" to "F". If the complete result of the conversion cannot be displayed in the OUT parameter, the result is will only be partially written to the parameter. Parameters The following table shows the parameters of the "HTA" instruction: Parameter Declaration Data type Memory area Description IN Input VARIANT I, Q, M, D, L Start address of the hexadecimal digits N Input INT I, Q, M, D, L or constant Number of hexadecimal bytes to be converted RET_VAL Return WORD I, Q, M, D, L Error message OUT Output VARIANT I, Q, D, L Address at which the result is stored. You can find additional information on valid data types in "Overview of the valid data types (Page 1204)". WinCC Basic V13.0 System Manual, 02/2014 2541 Programming the PLC 9.7 References RET_VAL parameter Error code* Description (W#16#....) 0000 No error 8101 Invalid pointer at the IN parameter, e.g., because a non-existing data block is referenced. 8182 Input buffer is too small for data in the N parameter. 8120 Invalid format in the IN parameter. 8151 Non-supported data type in the IN parameter. 8401 Invalid pointer in the OUT parameter, e.g., because a non-existing data block is referenced. 8482 Output buffer is too small for data in the N parameter. 8420 Invalid format in the OUT parameter. 8451 Non-supported data type in the OUT parameter. * The error codes can be displayed as integer or hexadecimal values in the program editor. For additional information on toggling display formats, refer to "See also". ASCII characters and hexadecimal values The following table shows the ASCII characters and the corresponding hexadecimal values: 2542 Hexadecimal digit ASCII-coded hexadecimal value ASCII character 0 30 "0" 1 31 "1" 2 32 "2" 3 33 "3" 4 34 "4" 5 35 "5" 6 36 "6" 7 37 "7" 8 38 "8" 9 39 "9" A 41 "A" B 42 "B" C 43 "C" D 44 "D" E 45 "E" F 46 "F" WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Example The following table shows examples of the conversion of hexadecimal numbers to ASCII character strings: IN N OUT ENO status W#16#0123 2 '0123' 1 16#123AF01023 4 '123AF010' 0 Other instructions LEN: Determine the length of a character string Description A tag of the STRING data type contains two lengths: the maximum length and the current length (this is the number of currently valid characters). The maximum length of the character string is specified for each tag in the STRING keyword in square brackets. The number of bytes occupied by a string is 2 greater than the maximum length. The current length represents the number of the character places actually used. The current length must be less than or equal to the maximum length. You use the instruction "LEN" to query the current length of the character string specified at the IN input parameter and output this information as a numerical value at the OUT output parameter. An empty string ('') has the length zero. If errors occur during processing of the instruction, then an empty string will be output. Note Reading out the maximum length You can also use the MAX_LEN (Page 2532) instruction to read out the current length of a string. Parameters The following table shows the parameters of the "LEN" instruction: Parameter Declaration Data type Memory area Description IN Input STRING D, L or constant Character string OUT Return INT, DINT, REAL, LREAL I, Q, M, D, L Number of valid characters For additional information on valid data types, refer to "Overview of the valid data types (Page 1204)". WinCC Basic V13.0 System Manual, 02/2014 2543 Programming the PLC 9.7 References CONCAT: Combine character strings Description You use the instruction "CONCAT" to combine the character string at the IN1 input parameter with the character string at the IN2 input parameter. The result is output in the OUT output parameter with the STRING format. If the resulting character string is longer than the tag specified in the OUT output parameter, then the resulting character string will be limited to the available length. If errors occur during processing of the instruction and the OUT output parameter can be written, an empty string will be output. Parameters The following table shows the parameters of the "CONCAT" instruction: Parameter Declaration Data type Memory area Description IN1 Input STRING D, L or constant Character string IN2 Input STRING D, L or constant Character string OUT Return STRING D, L Resulting character string For additional information on valid data types, refer to "Overview of the valid data types (Page 1204)". LEFT: Read the left character of a character string Description You use the instruction "LEFT" to extract a partial string beginning with the first character of the string at the IN input parameter. You specify the number of characters to be extracted in the L parameter. The extracted characters are output in the OUT output parameter with STRING format. If the number of characters to be extracted is greater than the current length of the character string, the OUT output parameter returns the input character string as a result. If the L parameter contains the value "0" or the input value is an empty string, an empty string will be returned. If the value in the L parameter is negative, an empty string will be output. If errors occur during processing of the instruction and the OUT output parameter can be written, an empty string will be output. 2544 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameters The following table shows the parameters of the "LEFT" instruction: Parameter Declaration Data type Memory area Description IN Input STRING D, L or constant Character string L Input BYTE, INT, I, Q, M, D, L or SINT, USINT constant Number of characters to be extracted OUT Return STRING Extracted partial string D, L For additional information on valid data types, refer to "Overview of the valid data types (Page 1204)". RIGHT: Read the right characters of a character string Description You use this instruction to extract the last L character in a character string in the input parameter IN. You specify the number of characters to be extracted in the L parameter. The extracted characters are output in the OUT output parameter with STRING format. If the number of characters to be extracted is greater than the current length of the character string, the OUT output parameter returns the input character string as a result. If the L parameter contains the value "0" or the input value is an empty string, an empty string will be returned. If the value in the L parameter is negative, an empty string will be output. If errors occur during processing of the instruction and the OUT output parameter can be written, an empty string will be output. Parameters The following table shows the parameters of the "RIGHT" instruction: Parameter Declaration Data type Memory area Description IN Input STRING D, L or constant Character string L Input BYTE, INT, I, Q, M, D, L or SINT, USINT constant Number of characters to be extracted OUT Return STRING Extracted partial string D, L For additional information on valid data types, refer to "Overview of the valid data types (Page 1204)". MID: Read middle characters of a character string Description You use this instruction to extract a portion of the character string in the IN input parameter. With the P parameter, you specify the position of the first character to be extracted. With the WinCC Basic V13.0 System Manual, 02/2014 2545 Programming the PLC 9.7 References L parameter, you define the length of the character string to be extracted. The extracted partial character string is output to the OUT output parameter. The following rules must be observed when executing the instruction: If the number of characters to be extracted exceeds the current length of the character string in the IN input parameter, a partial character string will be output, starting from character position P and continuing to the end of the character string. If the character position specified in the P parameter falls outside the current character string length in the IN input parameter, an empty character string will be output in the OUT output parameter. If the value of the P or L parameter equals zero or is negative, an empty character string will be output in the OUT output parameter. If errors occur during processing of the instruction and the OUT output parameter can be written, an empty string will be output. Parameters The following table shows the parameters of the "MID" instruction: Parameter Declaration Data type Memory area Description IN Input STRING D, L or constant Character string L Input BYTE, INT, SINT, USINT I, Q, M, D, L or constant Length of the string to be extracted P Input BYTE, INT, SINT, USINT I, Q, M, D, L or constant Position of the first character to be extracted (first character = 1) OUT Return STRING D, L Extracted partial string For additional information on valid data types, refer to "Overview of the valid data types (Page 1204)". DELETE: Delete characters in a character string Description You use this instruction to delete a portion of the character string in the IN input parameter. With the P parameter, you specify the position of the first character to be deleted. You specify the number of characters to be deleted in the L parameter. The remaining partial character string is output to the OUT output parameter with STRING format. The following rules must be observed when executing the instruction: If the value in the P parameter is less than or equals zero, an empty character string will be output in the OUT output parameter. If the value in the P parameter is greater than the current length of the character string in the IN input, the input character string will be returned in the OUT output parameter. 2546 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References If the value in the L parameter equals zero, the input character string will be returned in the OUT output parameter. If the number of characters to be deleted at the L parameter is greater than the length of the character string in the IN parameter, an empty character string will be output. If the value in the L parameter is negative, an empty character string will be output. If errors occur during processing of the instruction and the OUT output parameter can be written, an empty string will be output. Parameter The following table shows the parameters of the "DELETE" instruction: Parameter Declaration Data type Memory area Description IN Input STRING D, L or constant Character string L Input BYTE, INT, I, Q, M, D, L or SINT, USINT constant Number of characters to be deleted P Input BYTE, INT, I, Q, M, D, L or SINT, USINT constant Position of first character to be deleted OUT Return STRING Resulting character string D, L For additional information on valid data types, refer to "Overview of the valid data types (Page 1204)". INSERT: Insert characters in a character string Description You use this instruction to insert the character string in the IN2 input parameter to the character string in the IN1 input parameter. With the P parameter, you specify the position of the character starting at which the characters are inserted. The result is output in the OUT output parameter with the STRING format. The following rules must be observed when executing the instruction: If the value in the P parameter exceeds the current length of the character string in the IN1 input parameter, the character string of the IN2 input parameter will be appended to the character string of the IN1 input parameter. If the value at the P parameter is zero, the character string at the IN2 parameter followed by the character string at the IN1 parameter will be output in the OUT output parameter. If the value in the P parameter is negative, an empty character string will be output in the OUT output parameter. If the resulting character string is longer than the tag specified in the OUT output parameter, the resulting character string will be limited to the available length. WinCC Basic V13.0 System Manual, 02/2014 2547 Programming the PLC 9.7 References Parameter The following table shows the parameters of the "INSERT" instruction: Parameter Declaration Data type Memory area Description IN1 Input STRING D, L or constant Character string IN2 Input STRING D, L or constant String to insert P Input BYTE, INT, SINT, USINT I, Q, M, D, L or constant Insert position OUT Return STRING D, L Resulting character string For additional information on valid data types, refer to "Overview of the valid data types (Page 1204)". REPLACE: Replace characters in a character string Description You use this instruction to replace a portion of the character string in the IN1 input with the character string in the IN2 input. You specify the position of the first character to be replaced in the P parameter. You specify the number of characters to be replaced in the L parameter. The result is output in the OUT output parameter with the STRING format. The following rules must be observed when executing the instruction: If the value in the P parameter is less than or equals zero, an empty character string will be output in the OUT output parameter. If the value in the L parameter is less than zero, an empty character string will be output in the OUT output parameter. If P equals one, the character string in the IN1 input will be replaced beginning with (and including) the first character. If the value in the P parameter exceeds the current length of the character string in the IN1 input parameter, the character string of the IN2 input parameter will be appended to the character string of the IN1 input parameter. If the resulting character string is longer than the tag specified in the OUT output parameter, the resulting character string will be limited to the available length. If the value at parameter L is zero, characters are not replaced but inserted. The same conditions apply as with the instruction INSERT. See also: INSERT: Insert characters in a character string (Page 2547) 2548 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameters The following table shows the parameters of the "REPLACE" instruction: Parameter Declaration Data type Memory area Description IN1 Input STRING D, L or constant String with characters to be replaced. IN2 Input STRING D, L or constant String with characters to be inserted. L Input BYTE, INT, I, Q, M, D, L or SINT, USINT constant Number of characters to be replaced P Input BYTE, INT, I, Q, M, D, L or SINT, USINT constant Position of first character to be replaced OUT Return STRING Resulting character string D, L For additional information on valid data types, refer to "Overview of the valid data types (Page 1204)". FIND: Find characters in a character string Description You can use this instruction to search through the character string in the IN1 input parameter for a specific character or a specific sequence of characters. You specify the value to be searched for in the IN2 input parameter. The search is made from left to right. The position of the first occurrence is output in the OUT output parameter. If the search returns no match, the value "0" will be output in the OUT output parameter. If an invalid character is specified at the IN2 parameter or if an error occurs during processing, the value "0" is output at the OUT parameter. Parameters The following table shows the parameters of the "FIND" instruction: Parameter Declaration Data type S7-1200 S7-1500 Memory area Description IN1 Input STRING STRING, WSTRING D, L or constant String searched through IN2 Input STRING, CHAR STRING, WSTRING, CHAR, WCHAR D, L or constant Characters to search for INT INT I, Q, M, D, L OUT Return (For (W)CHAR also I, Q, M) Character position You can find additional information on valid data types under "Overview of the valid data types (Page 1204)". WinCC Basic V13.0 System Manual, 02/2014 2549 Programming the PLC 9.7 References Runtime information GetSymbolName: Read out a tag on the input parameter Description The "GetSymbolName" instruction is used to read the name of a tag interconnected at the parameter via the input parameter of a block. If a block is used multiple times in the project and called each time by a different tag, you can use the "GetSymbolName" instruction to evaluate the name of the calling tag. The process value of the tag is irrelevant in this case. You specify the input parameters of the block interface at the VARIABLE parameter. Use only an interface parameter for this parameter and no PLC or data block tags. You can limit the length of the read tag name using the SIZE parameter. If the name has been truncated, this is indicated by the characters "..." (Unicode character 16#2026) appears at the end of the name. Note that the "..." character itself has a length of 1. If you enter 6 as the maximum length at the SIZE parameter, for example, and read the tag name "MyPLCTag" via the block interface, the following is output: "MyPLC...". The name read is output at the OUT parameter. Parameters The following table shows the parameters of the "GetSymbolName" instruction: Parameter Declaration Data type Memory area Description VARIABLE Input PARAMETER L Input parameters of the block interface SIZE Input UINT I, Q, M, D, L Length limit for the read names OUT Return WSTRING I, Q, M, D, L Name of the tag that was read via the block interface You can find additional information on valid data types under "Overview of the valid data types (Page 1204)". GetInstanceName: Read out name of the read instance Description You can use the "GetInstanceName" instruction to read the name of the instance data block within a function block. You can specify how many characters of the instance name should be read out using the SIZE parameter. If you use the "0" value for SIZE, the entire name is read. The name of the instance data block is written to the OUT parameter. If the name of the instance data block is longer than the maximum length of WSTRING (254 characters), the name is truncated. 2550 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameters The following table shows the parameters of the "GetInstanceName" instruction: Parameter Declaration Data type Memory area Description SIZE Input DINT I, Q, M, D, L or constant Number of characters up to which the name of the instance data block is to be read OUT Output WSTRING I, Q, M, D, L Read name of the instance data block You can find additional information on valid data types under "Overview of the valid data types (Page 1204)". GetBlockName: Read out name of the block Description You can use the "GetBlockName" instruction to read the name of the block in which the instruction is called. You can specify how many characters of the block name should be read using the SIZE parameter. If you use the "0" value for SIZE, the entire name is read. The name of the block is written at the OUT parameter. If the name of the block is longer than the maximum length of WSTRING (254 characters), the name is truncated. Parameter The following table shows the parameters of the "GetBlockName" instruction: Parameter Declaration Data type Memory area Description SIZE Input UINT I, Q, M, D, L or constant Number of characters up to which the name of the instance data block is to be read. RET_VAL Output WSTRING I, Q, M, D, L Read name of the instance data block You can find additional information on valid data types under "Overview of the valid data types (Page 1204)". 9.7.3.3 Process image UPDAT_PI: Update the process image inputs Description With the instruction, you update the OB 1 process image (=process image partition 0) of the inputs or a process image partition of the inputs of the inputs defined by configuration. If you have configured repeated signaling of I/O access errors for the system-side process image update, then the selected process image will be updated constantly. WinCC Basic V13.0 System Manual, 02/2014 2551 Programming the PLC 9.7 References Otherwise, this update will only be performed if the selected process image partition is not updated by the system, in other words: If you have not assigned this process image partition to an interrupt OB or If you selected process image partition 0 and have disabled updating of the OB 1 process image partition during configuration. Note Each logical address that you have assigned to a process image partition of the inputs per configuration no longer belongs to the OB 1 process image of the inputs. When you update a process image partition with "UPDAT_PI", you must not perform a simultaneous update with the "SYNC_PI (Page 2555)" instruction. System-side updating of the OB 1 process image of the inputs and the process image partitions of inputs that you have assigned to an interrupt OB takes place independently of "UPDAT_PI" calls. Parameters The following table shows the parameters of the "UPDAT_PI"instruction: Parameter Declaration Data type Memory area Description PART Input PIP I, Q, M, D, L or constant Number of the process image partition of the inputs to be updated. Maximum value range (depending on the CPU): 0 to 31 (0 means OB 1 process image, n where 1 <= n <= 31 means process image partition n). RET_VAL Return INT I, Q, M, D, L, P Error information FLADDR Output WORD I, Q, M, D, L, P Address of the first byte to cause an error if an access error has occurred. You can find additional information on valid data types in "Overview of the valid data types (Page 1204)". RET_VAL parameter Error code* Explanation (W#16#...) 0000 No error occurred. 8090 Illegal value for PART parameter 8091 The specified process image partition was not yet defined or is not located in the permitted process image area on the CPU. 8092 The process image partition is being updated by the system and cannot be used for the PART parameter. 2552 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Error code* Explanation (W#16#...) 8093 The process image partition update is being processed in another OB. 80A0 An access error was detected when accessing the I/O. General error information See also: GET_ERR_ID: Get error ID locally (Page 1964) * The error codes can be displayed as integer or hexadecimal values in the program editor. For additional information on toggling display formats, refer to "See also". Note If you use the instruction for process image partitions of DP standard slaves for which you have defined a consistency area greater than 32 bytes, the error codes of the "DPRD_DAT (Page 2601)" instruction are also possible. UPDAT_PO: Update the process image outputs Description You use the instruction to transfer the signal states of the OB 1 process image (= process image partition 0) of the outputs or a process image partition of the outputs defined per configuration to the output modules. If you have specified a consistency range for the selected process image partition, corresponding data is transferred as consistent data to the respective I/O module. Note Each logical address you have assigned to a process image partition of the outputs during configuration no longer belongs to the OB 1 process image of the outputs. Outputs that you update with "UPDAT_PO" must not be updated simultaneously with the "SYNC_PO (Page 2556)" instruction. The OB 1 process image of the outputs and the process image partitions of the outputs that you have assigned to an interrupt OB are transferred by the system to the output modules independently of "UPDAT_PO" calls. WinCC Basic V13.0 System Manual, 02/2014 2553 Programming the PLC 9.7 References Parameters The following table shows the parameters of the "UPDAT_PO" instruction: Parameter Declaration Data type Memory area Description PART Input PIP I, Q, M, D, L or constant Number of the process image partition of the outputs to be transferred. Maximum value range (depending on the CPU): 0 to 31. (0 means OB 1 process image, n where 1 <= n <= 31 means process image partition n) RET_VAL Return INT I, Q, M, D, L, P Error information FLADDR Output WORD I, Q, M, D, L, P Address of the first byte to cause an error if an access error has occurred. You can find additional information on valid data types in "Overview of the valid data types (Page 1204)". RET_VAL parameter Error code* Explanation (W#16#...) 0000 No error occurred. 8090 Illegal value for PART parameter 8091 The specified process image partition was not yet defined or is not located in the permitted process image area on the CPU. 8092 The process image partition is being updated by the system and cannot be used for the PART parameter. 8093 The process image partition update is being processed in another OB. 80A0 An access error was detected when accessing the I/O. General error information See also: GET_ERR_ID: Get error ID locally (Page 1964) * The error codes can be displayed as integer or hexadecimal values in the program editor. For additional information on toggling display formats, refer to "See also". Note If you use the instruction for process image partitions of DP standard slaves for which you have defined a consistency area greater than 32 bytes, the error codes of the "DPWR_DAT (Page 2603)" instruction are also possible. 2554 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References SYNC_PI: Synchronize the process image inputs Description The "SYNC_PI" is used to update the process image partition of inputs in isochronous mode. A user program linked to a DP cycle or PN send cycle can use this instruction to update input data acquired in a process image partition of the inputs isochronously and consistently. Call "SYNC_PI" is interruptible and can only be called in OBs 61, 62, 63 and 64. Note A call of the "SYNC_PI" instruction in OBs 61 to 64 is only permitted if you have assigned the affected process image partition to the associated OB in the HW configuration. A process image partition that you update with "SYNC_PI" must not be updated simultaneously with the "UPDAT_PI (Page 2551)" instruction. Parameters The following table shows the parameters of the "SYNC_PI" instruction: Parameter Declaration Data type Memory area Range of values Description PART Input PIP I, Q, M, D, L or constant 1 to 31 Number of the process image partition of the inputs to be updated isochronously. RET_VAL Return INT I, Q, M, D, L, P - Error information FLADDR Output WORD I, Q, M, D, L, P Address of the first byte to cause an error if an access error has occurred. You can find additional information on valid data types in "Overview of the valid data types (Page 1204)". RET_VAL parameter Error code (W#16#...)* Explanation 0000 No error occurred. 0001 Consistency warning. The update of the process image partition was distributed over two DP or PN cycles. However, the data in one slave or IO device were consistently transferred. 8090 Illegal value on PART parameter or updating the specified process image partition of the inputs is not permitted in this OB. The process image partition of the inputs was not updated. 8091 The specified process image partition was not yet defined or is not located in the permitted process image area on the CPU. The process image partition of the inputs was not updated. 8092 The process image partition is being updated by the system and cannot be used for the PART parameter. 8093 The process image partition update is being processed in another OB. WinCC Basic V13.0 System Manual, 02/2014 2555 Programming the PLC 9.7 References Error code (W#16#...)* Explanation 80A0 During updating an access error was detected. The affected inputs were set to "0". 80A1 The update time is after the permitted access window. The process image partition of the inputs was not updated. The DP or PN cycle is too short to ensure enough time for processing the instruction. You must therefore increase the TDP (also known as T_DC), Ti and To timers. 80A2 Access error with consistency warning In the case of update of the specified process image partition an access error with simultaneous consistency warning was detected. The data of the incorrect inputs was not read by the I/O. In the process image partition of the inputs the involved inputs are set to zero. The update of the process image partition of the not involved by an access error input data was distributed over two DP and PN cycles. 80C1 The update time is before the permitted access window. The process image partition of the inputs was not updated. General error information See also: GET_ERR_ID: Get error ID locally (Page 1964) * The error codes can be displayed as integer or hexadecimal values in the program editor. For additional information on toggling display formats, refer to "See also". Note If you use the "SYNC_PI" instruction for process image partitions of DP standard slaves for which you have defined a consistency area greater than 32 bytes, the error codes of the "DPRD_DAT (Page 2601)" instruction are also possible. SYNC_PO: Synchronize the process image outputs Description The instruction "SYNC_PO" is used to update a process image partition of outputs in isochronous mode. An application program linked to a DP cycle or a PN send cycle can use this instruction for the consistent isochronous transfer of the computed output data of a process image partition from outputs to the I/O devices. 2556 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Call "SYNC_PO" is interruptible and can only be called in OBs 61, 62, 63 and 64. Note A call of the "SYNC_PO" instruction in OBs 61 to 64 is only permitted if you have assigned the affected process image partition to the associated OB in the HW configuration. A process image partition that you update with "SYNC_PO" must not be updated simultaneously with the "UPDAT_PO (Page 2553)" instruction. Parameters The following table shows the parameters of the "SYNC_PO" instruction: Parameter Declaration Data type Memory area Range of values Description PART Input PIP I, Q, M, D, L or constant 1 to 31 Number of the process image partition of the outputs to be updated isochronously. RET_VAL Return INT I, Q, M, D, P - If an error occurs while the instruction is being executed, the return value contains an error code. FLADDR Output WORD I, Q, M, D, L, P - Address of the first byte that has caused the error. You can find additional information on valid data types in "Overview of the valid data types (Page 1204)". RET_VAL parameter Error code Explanation (W#16#...)* 0000 No error occurred. 0001 Consistency warning. The update of the process image partition was distributed over two DP or PN cycles. However, the data in one slave or IO device were consistently transferred. 8090 Illegal value in PART parameter, or updating the specified process image partition of the outputs is not permitted in this OB. Outputs were not transferred to the I/O. The process image partition of the outputs remains unchanged. 8091 The specified process image partition was not yet defined or is not located in the permitted process image area on the CPU. Outputs were not transferred to the I/O. The process image partition of the outputs remains unchanged. 8092 The process image partition is being updated by the system and cannot be used for the PART parameter. 8093 The process image partition update is being processed in another OB. 80A0 In the case of update of the specified process image partition of the outputs an access error was detected. Incorrect outputs were not transferred to the I/O. During process image partition of the outputs, these outputs remain unchanged. WinCC Basic V13.0 System Manual, 02/2014 2557 Programming the PLC 9.7 References Error code Explanation (W#16#...)* 80A1 Access error with consistency warning In the case of update of the specified process image partition of the outputs an access error with simultaneous consistency warning was detected. The data of the incorrect outputs were not transferred to the I/O. During process image partition of the outputs, the involved outputs remain unchanged. The update of the process image partition of the not involved by an access error input data was distributed over two DP and PN cycles. 80A2 The update time is after the permitted access window. Outputs were not transferred to the I/O. The process image partition of the outputs remains unchanged. 80C1 The update time is before the permitted access window. Outputs were not transferred to the I/O. The process image partition of the outputs remains unchanged. General error information See also: GET_ERR_ID: Get error ID locally (Page 1964) * The error codes can be displayed as integer or hexadecimal values in the program editor. For additional information on toggling display formats, refer to "See also". Note If you use the "SYNC_PO" instruction for process image partitions of DP standard slaves for which you have defined a consistency area greater than 32 bytes, the error codes of the "DPWR_DAT (Page 2603)" instruction are also possible. 9.7.3.4 Distributed I/O RDREC: Read data record Description You use the instruction "RDREC" to read the data record with the number INDEX from the module addressed using the ID. This may be a module in a central rack or a distributed module (PROFIBUS DP or PROFINET IO). Use the parameter ID to select from which module a data record is to be read. Use only the hardware identifier of the module for the "ID" parameter. Use the INDEX parameter to select the information to be read from the module. Which data records can be read with which data record number depends on the module. For additional information, see the manual to the specific module. The data records readable via "RDREC" have a different length. Use MLEN to specify the maximum number of data record bytes you want to read. If length "0" is selected at the parameter MLEN, the complete data record is written at the parameter RECORD. The target range RECORD should have at least the length of MLEN bytes. If you read out the full data record with MLEN=0, use the maximum length of the data record for RECORD. The structure (configuration, data types and length) that you use at the parameter RECORD, also depends on which data record is read out by which module. 2558 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References The value TRUE for the output parameter VALID indicates that the data record was successfully transferred to the target range RECORD. In this case, the LEN output parameter contains the length of the read data in bytes. If an error has occurred during transfer of the data record, this is indicated by the output parameter ERROR. In this case, the output parameter STATUS contains the error information. Note The interface of the "RDREC" instruction is identical to the "RDREC" FB defined in "PROFIBUS Guideline PROFIBUS Communication and Proxy Function Blocks according to IEC 61131-3". Functional description "RDREC" is an instruction that works asynchronously, which means its execution extends over multiple calls. You start the data record transfer by calling "RDREC" with REQ= 1. The job status is displayed via the output parameter BUSY and the two central bytes of output parameter STATUS. The two central bytes of STATUS correspond to the RET_VAL output parameter of the instructions that operate asynchronously. See also: Meaning of the parameters REQ, RET_VAL and BUSY with asynchronous instructions (Page 1736). The transfer of the data record is complete when the output parameter BUSY has the value FALSE . Parameter The following table shows the parameters of the "RDREC" instruction: Parameter Declaration Data type* Memory area Description REQ Input BOOL I, Q, M, D, L, T, C or constant REQ = 1: Transfer data record ID Input HW_IO I, Q, M, L or constant Hardware identifier of the hardware module (DP/PROFINET IO) The number is assigned automatically and is stored in the properties of the module or of the interface in the hardware configuration. INDEX Input BYTE, DINT, INT, SINT, UINT, USINT, WORD I, Q, M, D, L or constant Data record number MLEN Input BYTE, UINT, USINT I, Q, M, D, L or constant Maximum length in bytes of the data record information to be read VALID Output BOOL I, Q, M, D, L New data record was received and is valid. BUSY Output BOOL I, Q, M, D, L BUSY = 1: The reading process is not yet complete. WinCC Basic V13.0 System Manual, 02/2014 2559 Programming the PLC 9.7 References Parameter Declaration Data type* Memory area Description ERROR Output BOOL I, Q, M, D, L ERROR = 1: An error occurred during the reading process. STATUS Output DWORD I, Q, M, D, L Block status or error information LEN Output UINT I, Q, M, D, L Length of the read data record information RECORD InOut VARIANT I, Q, M, D, L Target range for the data record read. * There is no implicit conversion in STL, which is why the range of valid data types may be limited. During programming in STL, please note the valid data types. These are displayed in the parameter tooltip. For additional information on valid data types, refer to "Overview of the valid data types (Page 1204)". Note If you use "RDREC" to read a data record for PROFINET IO, then negative values in the INDEX, MLEN, and LEN parameters will be interpreted as an unsigned 16-bit integer. Parameter STATUS For interpretation of the STATUS parameter, see Parameter STATUS (Page 2568). See also Basics of block access (Page 1151) WRREC: Write data record Description The instruction "WRREC" is used to transfer the RECORD data record to the component addressed using ID. This may be a module in a central rack or a distributed component (PROFIBUS DP or PROFINET IO). Use LEN to specify the length of the data record to be transmitted in bytes. The selected length of the source range RECORD should have at least the length of LEN bytes. The value TRUE at output parameter DONE indicates that the data record has been successfully transferred. If an error has occurred during transfer of the data record, this is indicated by the output parameter ERROR. In this case, the output parameter STATUS contains the error information. Note The interface of the "WRREC" instruction is identical to the "WRREC" FB defined in "PROFIBUS Guideline PROFIBUS Communication and Proxy Function Blocks according to IEC 61131-3". 2560 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Functional description "The WRREC" instruction works asynchronously, that is, its execution extends over multiple calls. You start the data record transfer by calling "WRREC" with REQ = 1. The job status is displayed via the output parameter BUSY and the two central bytes of output parameter STATUS. The two central bytes of STATUS correspond to the RET_VAL output parameter of the instructions that operate asynchronously. See also: Meaning of the parameters REQ, RET_VAL and BUSY with asynchronous instructions (Page 1736). Note that you must assign the same value to the actual parameter of RECORD for all "WRREC" calls that belong to one and the same job. The same applies to the actual parameters of LEN. The transfer of the data record is complete when the output parameter BUSY has the value FALSE. Parameter The following table shows the parameters of the instruction "WRREC": Parameter Declaration Data type Memory area Description REQ Input BOOL I, Q, M, D, L, T, C or constant REQ= 1: Transfer data record ID Input HW_IO I, Q, M, L or constant ID number of the hardware component (DP/ PROFINET IO) The number is assigned automatically and is stored in the properties of the component or of the interface in the hardware configuration. INDEX Input DINT I, Q, M, D, L or constant Data record number LEN Input BYTE, UINT, USINT I, Q, M, D, L or constant (hidden) Maximum length of the data record to be transferred in bytes DONE Output BOOL I, Q, M, D, L Data record was transferred BUSY Output BOOL I, Q, M, D, L BUSY= 1: The writing process is not yet complete. ERROR Output BOOL I, Q, M, D, L ERROR = 1: An error occurred during the writing process. STATUS Output DWORD I, Q, M, D, L Block status or error information For interpretation of the STATUS parameter, see Parameter STATUS (Page 2568). RECORD InOut WinCC Basic V13.0 System Manual, 02/2014 VARIANT I, Q, M, D, L Data record 2561 Programming the PLC 9.7 References For additional information on valid data types, refer to "Overview of the valid data types (Page 1204)". Note If you use "WRREC" to write a data record for PROFINET IO, negative values in the INDEX and LEN parameters will be interpreted as an unsigned 16-bit integer. STATUS parameter For interpretation of the STATUS parameter, see Parameter STATUS (Page 2568). GETIO: Read process image Description You use the instruction "GETIO" to consistently read out all inputs of a DP standard slave/ PROFINET IO device. The instruction "GETIO" calls the instruction "DPRD_DAT (Page 2601)". If there was no error during the data transmission, the data that have been read are entered in the target range indicated by INPUTS . The target range must have the same length that you configured for the selected component. If you read from a DP standard slave with a modular configuration or with several DP identifiers, you can only access the data of one component/DP identifier at the configured start address with a "GETIO" call. Parameter The following table shows the parameters of the instruction "GETIO": Parameter Declaration Data type ID Input HW_SUBMOD I, Q, M, D, L or constant Hardware ID of the DP standard slave / ULE PROFINET IO device. Memory area Description STATUS Output DWORD I, Q, M, D, L Contains the error information of "DPRD_DAT (Page 2601)" in the form DW#16#40xxxx00. LEN Output INT I, Q, M, D, L Amount of data read in bytes INPUTS InOut VARIANT I, Q, M, D Target range for the read data. It must have the same length as the range that you configured for the selected DP standard slave / PROFINET IO device. Only the BYTE data type is permitted. You will find more detailed information on valid data types in "Overview of the valid data types (Page 1204)". 2562 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References STATUS parameter See also: DPRD_DAT: Read consistent data of a DP standard slave (Page 2601). SETIO: Transfer process image Description You use the instruction "SETIO" to consistently transfer data from the source range defined by the parameter OUTPUTS to the addressed DP standard slave / PROFINET IO device, and, if necessary, to the process image (if you have configured the relevant address area of the DP standard slave / PROFINET IO device as a consistent range in a process image). "SETIO" calls the instruction "DPWR_DAT (Page 2603)". The source range must have the same length that you configured for the selected component. In the case of a DP standard slave / PROFINET IO device with modular configuration or with several DP identifiers, you can only access one DP identifier / component per "SETIO" call. Parameters The following table shows the parameters of the "SETIO" instruction: Parameter Declaration Data type ID Input HW_SUBMODU I, Q, M, D, L or LE constant Memory area Description Hardware ID of the DP standard slave / PROFINET IO device. STATUS Output DWORD I, Q, M, D, L Contains the error information of "DPWR_DAT (Page 2603)" in the form DW#16#40xxxx00. OUTPUTS InOut VARIANT I, Q, M, D Source range for the data to be written. It must have the same length as the range that you configured for the selected DP standard slave / PROFINET IO device. Only the BYTE data type is permitted. For additional information on valid data types, refer to "Overview of the valid data types (Page 1204)". Parameter STATUS See also: DPWR_DAT: Write consistent data of a DP standard slave (Page 2603). GETIO_PART: Read process image area Description You use the instruction "GETIO_PART" to consistently read out a related part of the inputs of an IO module. "GETIO_PART" calls the instruction "DPWR_DAT (Page 2601)". Use the ID input parameter to select the IO module by means of the hardware ID. WinCC Basic V13.0 System Manual, 02/2014 2563 Programming the PLC 9.7 References You use the OFFSET and LEN parameters to specify the portion of the process image area to be read. If the input area spanned by OFFSET and LEN is not completely covered by the module, the block returns the error code DW#16#4080B700. The length of the target range must be larger than or equal to the amount of bytes to be read: If there was no error during the data transmission, ERROR receives the value FALSE. The data that are read are written to the target range defined at the INPUTS parameter. If there was no error during the data transmission, ERROR receives the value TRUE. The STATUS parameter receives the error information from "DPRD_DAT". If the target range is greater than LEN, then the first LEN bytes of the target range will be written. ERROR receives the value FALSE. Parameters The following table shows the parameters of the "GETIO_PART" instruction: Parameter Declaration Data type Memory area ID Input HW_SUBMOD ULE I, Q, M, D, L or constant Hardware identifier of the module Description OFFSET Input INT I, Q, M, D, L or constant Number of the first byte to be read in the process image for the component (smallest possible value: 0). LEN Input INT I, Q, M, D, L or constant Number of bytes to be read. STATUS Output DWORD I, Q, M, D, L Contains the error information of "DPRD_DAT" in the form DW#16#40xxxx00, if ERROR = TRUE. ERROR Output BOOL I, Q, M, D, L Error display: ERROR = TRUE if an error occurs when "DPRD_DAT" is called. INPUTS InOut VARIANT I, Q, M, D Target range for read data: If the target range is greater than LEN, the first LEN bytes of the target range are written. For additional information on valid data types, refer to "Overview of the valid data types (Page 1204)". Parameter STATUS See "RET_VAL" parameter of the "DPRD_DAT (Page 2601)" instruction. SETIO_PART: Transfer process image area Description You can use the "SETIO_PART" instruction to consistently write data from the source area spanned by OUTPUTS to the outputs of an IO module. "SETIO_PART" calls the instruction "DPWR_DAT (Page 2603)". 2564 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Use the ID input parameter to select the IO module by means of the hardware ID. You use the OFFSET and LEN parameters to specify the portion of the process image area to be written for the components addressed by means of ID. If the output area spanned by OFFSET and LEN is not completely covered by the module, the block returns the error code DW#16#4080B700. The length of the source range must be greater than or equal to the number of bytes to be written: If there was no error during the data transmission, ERROR receives the value FALSE. If there was an error during the data transmission, ERROR receives the value TRUE, and STATUS receives the error information of "DPWR_DAT". If the source range is greater than LEN, the first LEN bytes from OUTPUTS are transferred. ERROR receives the value FALSE. Parameter The following table shows the parameters of the instruction "SETIO_PART": Parameter Declaration Data type Memory area ID Input HW_SUBMO DULE I, Q, M, D, L or constant Hardware identifier of the IO module. Description OFFSET Input INT I, Q, M, D, L or constant Number of the first byte to be written in the process image for the component (smallest possible value: 0). LEN Input INT I, Q, M, D, L or constant Number of bytes to be written. STATUS Output DWORD I, Q, M, D, L Contains the error information of "DPWR_DAT" in the form DW#16#40xxxx00, if ERROR = TRUE. ERROR Output BOOL I, Q, M, D, L Error display: ERROR = TRUE if an error occurs when "DPWR_DAT" is called. OUTPUTS InOut VARIANT I, Q, M, D Source range for the data to be written: If the source range is greater than LEN, the first LEN bytes are transferred from OUTPUTS. You will find more detailed information on valid data types in "Overview of the valid data types (Page 1204)". Parameters STATUS and ERROR See instruction "DPWR_DAT (Page 2603)". WinCC Basic V13.0 System Manual, 02/2014 2565 Programming the PLC 9.7 References RALRM: Receive interrupt Description RALRM Description The instruction receives an interrupt with all corresponding information from an I/O module (centralized configuration) or from a module of a DP slave or PROFINET IO device and supplies this information to its output parameters. The information in the output parameters contains the start information of the called OB as well as information of the interrupt source. For a central configuration, the configuration of the data structure of the target range AINFO corresponds to the data structure of PROFINET IO. Call "RALRM" only within the interrupt OB started by the CPU operating system as a result of the I/O interrupt that is to be examined. Note If you call "RALRM" in an OB whose start event is not an I/O interrupt, the instruction will provide correspondingly reduced information in its outputs. Make sure to use different instance DBs when you call "RALRM" in different OBs. If you evaluate data resulting from an "RALRM" call outside of the associated interrupt OB, you should moreover use a separate instance DB per OB start event. Note The interface of the "RALRM" instruction is identical to the "RALRM" FB defined in "PROFIBUS Guideline PROFIBUS Communication and Proxy Function Blocks according to IEC 61131-3". Calling RALRM "RALRM" can be called in three operating modes (MODE parameter). These are explained in the table below. MODE RALRM ... 0 ... shows the component that triggered the interrupt in the ID output parameter and writes TRUE in the NEW output parameter. 1 ... writes all output parameters, independent of the interrupt triggering component. 2 ... checks whether the component specified in the F_ID input parameter has triggered the interrupt. If not, NEW = FALSE If yes, NEW = TRUE and all other output parameters are written. 2566 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameters The following table shows the parameters of the "RALRM" instruction: Parameter Declaration Data type Memory area Description MODE Input INT I, Q, M, D, L or constant Mode F_ID Input HW_IO D, L or constant Hardware identifier of the module. The number is assigned automatically and is stored in the hardware configuration properties of the component or interface. MLEN Input UINT I, Q, M, D, L or constant Maximum length of the interrupt information to be received in bytes. With MLEN = 0, all data specified at the AINFO parameter are read. NEW Output BOOL I, Q, M, D, L A new interrupt was received. STATUS (Page 2568) Output DWORD I, Q, M, D, L Error code ID Output HW_IO I, Q, M, D, L Hardware identifier of the module from which the interrupt was received. LEN Output UINT I, Q, M, D, L Length of the received interrupt information TINFO (Page 2571) InOut VARIANT I, Q, M, D, L Destination area for OB start and management information AINFO (Page 2584) InOut VARIANT I, Q, M, D, L Destination area for header information and additional interrupt information For AINFO , you should provide a length of at least MLEN bytes. For additional information on valid data types, refer to "Overview of the valid data types (Page 1204)". Note If you select a target range (Page 2590)TINFO or AINFO that is too short, RALRM cannot enter the full information. WinCC Basic V13.0 System Manual, 02/2014 2567 Programming the PLC 9.7 References Parameter STATUS Description The STATUS output parameter contains error information. If it is interpreted as ARRAY[1...4] of BYTE, the error information has the following structure: Field element Name Meaning STATUS[1] Function_Num B#16#00, if no error Function ID from DPV1-PDU: In the event of an error, B#16#80 is output (in the event of an error reading a data record B#16#DE and writing a data record B#16#DF). If no DPV1 protocol element is used, then B#16#C0 will be output. STATUS[2] Error_Decode Location of the error ID STATUS[3] Error_Code_1 Error ID STATUS[4] Error_Code_2 Manufacturer-specific error ID extension Field element STATUS[2] STATUS[2] can have the following values: Error_Decode (B#16#...) Source Meaning 00 to 7F CPU No error or no warning 80 DPV1 Error according to IEC 61158-6 81 to 8F CPU B#16#8x shows an error in the xth call parameter of the instruction. FE, FF DP profile Profile-specific error Field element STATUS[3] STATUS[3] can have the following values: Error_Decode (B#16#...) Error_Code_1 (B#16#...) 00 00 70 00 reserved, reject Initial call; no active data record transfer 01 reserved, reject Initial call; data record transfer has started 02 reserved, reject Intermediate call; data record transfer already active 80 Explanation according to DVP1 Meaning No error, no warning 81 The system data type at parameter TINFO does not match the call environment of the instruction. The used system data type must match the organization block in the user program (example: for a time-delay interrupt OB you need the system data type TI_Delay). 90 2568 reserved, pass Invalid logical start address WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Error_Decode (B#16#...) Error_Code_1 (B#16#...) Explanation according to DVP1 Meaning 92 reserved, pass Illegal type for VARIANT pointer 93 reserved, pass The DP component addressed via ID or F_ID is not configured. 96 The "RALRM (Page 2566)" cannot supply the OB start information, management information, header information, or additional interrupt information. For OBs 4x, 55, 56, 57, 82 and 83, you can use the "DPNRM_DG (Page 2616)" instruction to read the current diagnostic frame of the relevant DP slave asynchronously (address information from OB start information). A0 read error Negative acknowledgment while reading the module A1 write error Negative acknowledgment when writing to the module A2 module failure DP protocol error at layer 2 (e.g., slave failure or bus problems) A3 reserved, pass PROFIBUS DP: DP protocol error with Direct-Data-LinkMapper or User-Interface/User A4 reserved, pass Communication on PBUS+ disrupted A5 reserved, pass - A7 reserved, pass DP slave or module is occupied (temporary error A8 version conflict DP slave or module reports non-compatible versions A9 feature not supported Function is not supported by DP slave or module AA to AF user specific DP slave or module reports a manufacturer-specific error in its application. Please check the documentation from the manufacturer of the DP slave or module. B0 invalid index Data record not known in module B1 write length error PROFINET IO: General CM error Illegal data record number 256 Error at length specification: With "RALRM (Page 2566)": length error in AINFO (Page 2584) With "RDREC (Page 2558)": length error in MLEN With "WRREC (Page 2560)": length error in LEN B2 invalid slot The configured slot is not assigned. B3 type conflict Actual module type does not match specified module type B4 invalid area DP slave or module reports access to an invalid area B5 state conflict DP slave or module not ready B6 access denied DP slave or module denies access B7 invalid range DP slave or module reports an invalid range for a parameter or value B8 invalid parameter DP slave or module reports an invalid parameter WinCC Basic V13.0 System Manual, 02/2014 2569 Programming the PLC 9.7 References Error_Decode (B#16#...) Error_Code_1 (B#16#...) Explanation according to DVP1 Meaning B9 invalid type DP slave or module reports an invalid type With "RDREC (Page 2558)": buffer too small (subsets cannot be read) With "WRREC (Page 2560)": buffer too small (subsets cannot be written) BA to BF user specific DP slave or module reports a manufacturer-specific error when accessing. Please check the documentation from the manufacturer of the DP slave or module. C0 read constrain conflict With "WRREC (Page 2560)": the data can only be written when the CPU is in STOP mode. Note: this means that writing by the user program is not possible. You can only write the data online with PG/PC. With "RDREC (Page 2558)": the module routes the data record, but either no data is present or the data can only be read when the CPU is in STOP mode. Note: if data can only be read when the CPU is in STOP mode, then an evaluation by the user program is not possible. In this case, you can only read the data online with PG/PC. C1 write constrain conflict The data of the previous write job on the module for the same data record have not yet been processed by the module. C2 resource busy The module is currently processing the maximum possible number of jobs for a CPU. C3 resource unavailable The required operating resources are currently occupied. C4 Internal temporary error. Job could not be executed. Repeat the job. If this error occurs often, check your installation for sources of electrical interference. C5 DP slave or module not available. C6 Data record transfer was canceled due to priority class cancellation C7 Job aborted due to warm or cold restart on the DP master C8 to CF DP slave or module reports a manufacturer-specific resource error. Please check the documentation from the manufacturer of the DP slave or module. Dx 81 user specific DP slave specific. Refer to the description of the DP slave. 00 to FF Error in the initial call parameter (with "RALRM (Page 2566)": MODE) 00 Illegal operating mode 82 00 to FF Error in the second call parameter : : : 88 00 to FF Error in the eighth call parameter (with "RALRM (Page 2566)": TINFO (Page 2571)) 01 Wrong syntax ID 23 Quantity structure exceeded or target range too small 24 Wrong range ID 2570 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Error_Decode (B#16#...) Error_Code_1 (B#16#...) Explanation according to DVP1 Meaning 32 DB/DI no. out of user range 3A DB/DI no. is NULL for area ID DB/DI or specified DB/DI does not exist 00 to FF Error in the ninth call parameter (with "RALRM (Page 2566)": AINFO (Page 2584)) 01 Wrong syntax ID 23 Quantity structure exceeded or target range too small 24 Wrong range ID 32 DB/DI no. out of user range 3A DB/DI no. is NULL for area ID DB/DI or specified DB/DI does not exist 8A 00 to FF Error in the 10th call parameter : : : 8F 00 to FF Error in the 15th call parameter FE, FF 00 to FF Profile-specific error 89 Field element STATUS[4] With DPV1 errors, the DP master passes on STATUS[4] to the CPU and the instruction. Without DPV1 error, this value is set to 0, with the following exceptions for "RDREC": STATUS[4] contains the target range length from RECORD, if MLEN > the target range length from RECORD STATUS[4]=MLEN, if the actual data record length < MLEN < the target range length from RECORD STATUS[4]=0, if STATUS[4]> 255 would have to be set In PROFINET IO, STATUS[4] has the value "0". Parameter TINFO Data structure of the destination area TINFO The data structure of the destination area TINFO contains the start information of the organization block in which "RALRM" is currently being called. The TINFO destination area can contain the start information with standard access or optimized access. The format of the start information in the TINFO destination area must always match the start information of the corresponding organization block. WinCC Basic V13.0 System Manual, 02/2014 2571 Programming the PLC 9.7 References The start information of an OB with standard access is always stored in the first 20 bytes of the "Temp" section in the block interface. Use the "TI_Classic" data structure for this. The start information of an OB with optimized access is always written to the "Input" section. Use a data structure for the specific OB type for these OBs. Changing the block access (standard/optimized) also changes the block interface. The following table provides an overview of the data structures that are used depending on the organization block at the TINFO parameter. Name of the data structure S7-1200 CPUs as of version S7-1500 CPUs as of version Data structure used for: Data structure for organization blocks with standard access TI_Classic - V1 Organization blocks without optimized block access. Data structure for organization blocks with optimized block access TI_ProgramCycle V2 V1 Cycle OB (program cycle) TI_Startup V2 V1 Startup OB (startup) TI_Delay V2 V1 Time delay interrupt TI_Cyclic V2 V1 Cyclic interrupt OB TI_HWInterrupt V2 V1 Hardware interrupt OB TI_TimeError V2 V1 Time error OB TI_DiagnosticInterrupt V2 V1 Diagnostic error interrupt OB TI_PlugPullModule V2 V1 Pull/plug of modules OB TI_StationFailure V2 V1 Rack or station failure OB TI_ProgIOAccessError V2 V1 Programming error OB I/O access error OB TI_TimeOfDay V2 V1 Time-of-day interrupt OB TI_SynchCycle - V1 Synchronous cycle interrupt OB TI_Submodule V2 V1 Status interrupt OB Update interrupt OB OB for manufacturer or profile-specific interrupt Data structure for organization blocks with standard access The following shows the TI_Classic data structure: Parameter Data type Byte TI_Classic Description Data structure for organization blocks with optimized block access. Bytes 0 to 19: Start information of the OB in which "RALRM" is currently being called.* EV_CLASS BYTE 0 Event class Example OB1: Bits 0-3: ID of the event (1 = incoming event) Bits 4-7: Event class (1 = Event class 1) 2572 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameter EV_NUM Data type Byte Description BYTE 1 Event number (depending on OB type) Example OB1 (SCAN_1): SCAN_1 = 1 for first call SCAN_1 = 3 for all additional calls PRIORITY BYTE 2 Priority class NUM BYTE 3 OB number TYP2_3 BYTE 4 Additional information TYP1 BYTE 5 Different information is stored in the BYTES "TYP2_3" and "TYPE 1" depending on the OB type used. What these are is described in the documentation for the organization blocks. Example (OB1): TYP2_3: OB1_RESERVED_1 (reserved) TYP1: OB1_RESERVED_2 (reserved) ZI1 WORD 6 to 7 Additional information Different information is stored in "ZI1" depending on the OB type used. What these are is described in the documentation for the organization blocks. Example (OB1): ZI1: OB1_PREV_CYCLE (runtime of previous cycle in ms) ZI2_3 DWORD 8 to 11 Additional information Different information is stored in "ZI2_3" depending on the OB type used. What these are is described in the documentation for the organization blocks. Example (OB1): ZI2: OB1_MIN_CYCLE (minimum cycle time (ms) since the last startup) ZI3: OB1_MAX_CYCLE (maximum cycle time (ms) since the last startup) OB_DATE_ TIME DATE_AN D_TIME (DT) 12 to 19 Date and time-of-day when the OB was called. Bytes 20 and 21: Address information WinCC Basic V13.0 System Manual, 02/2014 2573 Programming the PLC 9.7 References Parameter address Data type Byte Description WORD 20 and 21 Address information like S7-300/400 CPUs: In a central configuration, the rack number (0-31): %LW QXPEHURIWKHUDFN For a distributed configuration with PROFIBUS DP: - DP master system ID (1-31) - Station number (0-127). %LW 6WDWLRQQXPEHU '3PDVWHUV\VWHP,' In a distributed configuration with PROFINET IO: - The last two positions in the PROFINET IO system ID (0-15). To obtain the complete PROFINET IO system ID, you must add 100 (decimal) to it. - Station number (0-2047). %LW ,2V\VWHP,' 6WDWLRQQXPEHU Bytes 22 to 31: Management information slv_prfl BYTE 22 Slave profile like S7-300/400 CPUs: In a central configuration: 0 (data record 0 or data record 1) In a distributed configuration: 2574 - Bit 0 to 3: Slave type - 0000: DP (structure data record 0) - 0001: DPS7 (structure data record 0 or data record 1) - 0010: DPS7 V1 (structure data record 0 or data record 1) - 0011: DPV1 (structure according to PROFIBUS DP standard) - 0100 - 0111: Reserved - 1000: PROFINET IO (structure according to PROFINET IO standard) - from 1001: Reserved - Bit 4 to 7: Profile type (reserved) WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameter intr_type Data type Byte Description BYTE 23 Interrupt info type like S7-300/400 CPUs: In a central configuration: 0 In a distributed configuration: flags1 BYTE 24 - Bit 0 to 3: Interrupt info type - 0000: Interrupt comes from a configured remote module - 0001: Interrupt comes from a non-DPV1 slav / non IO device or a slot that is not configured - 0010: Interrupt generated in the CPU - from 0011: Reserved - Bit 4 to 7: Structure version - 0000: Initial - from 0001: Reserved Flags of the PROFIBUS DP master interface module / PROFINET IO controller interface module like S7-300/400 CPUs: In a central configuration: 0 In a distributed configuration: flags2 BYTE 25 - Bit 0 = 0: Interrupt originating from an integrated interface module (PROFINET IO or PROFIBUS DP) - Bit 0 = 1: Interrupt originating from an external interface module (PROFINET IO or PROFIBUS DP) - Bit 1 to 7: Reserved Flags of the PROFIBUS DP master interface module / PROFINET IO controller interface module like S7-300/400 CPUs: In a central configuration: 0 For a distributed configuration with PROFIBUS DP: - Bit 0: EXT_DIAG_FLAG from the diagnostics message frame, or 0 if this bit does not exist in the interrupt The bit is 1 if the DP slave is faulty. - Bit 1 to 7: Reserved In a distributed configuration with PROFINET IO: id UINT 26 and 27 - Bit 0: ARDiagnosisState or 0 if there is no information in the interrupt. The bit is 1 if the IO device is faulty. - Bit 1 to 7: Reserved Management information In a central configuration: 0 For a distributed configuration with PROFIBUS DP: PROFIBUS ID number as unique identifier of the PROFIBUS DP slave In a distributed configuration with PROFINET IO: PROFINET IO device ID number as unique identifier of the PROFINET IO device manufacture UINT r 28 and 29 Manufacturer ID (only in a distributed configuration with PROFINET IO). instance 30 and 31 Ident number of the instance (only in a distributed configuration with PROFINET IO). UINT *The start information depends on the OB used. You can find the start information of each OB type at the interface or in the documentation of the OB. WinCC Basic V13.0 System Manual, 02/2014 2575 Programming the PLC 9.7 References Data structures for organization blocks with optimized block access The data structures for organization blocks with optimized block access have the following format: Bytes 0 to 3: Format of the start information, class and number of the called OB (same structure for all data structures). Bytes 4 to 19: Optimized start information (structure depends on the OB type). The data in bytes 4 to 19 correspond to the structure and content of the corresponding OB interface. Bytes 20 to 31: In addition, the address and management information for certain OBs. The data in bytes 20 to 31 correspond to the data of 20 to 31 bytes of the TI_Classic data structure. The format of the data structures is described in the following tables. Table 9-40 Cycle OB: Data structure TI_ProgramCycle Parameter Data type Byte USINT 0 TI_ProgramCycle SI_Format Description Data structure for cycle OB Format of the start information: 16#FF: None 16#FE: Optimized start information OB_Class USINT 1 OB class (=1) OB_Nr UINT 2 OB number (1...32767). Initial_Call BOOL 4 = TRUE in the first call of this OB: Transition from STOP or HOLD to RUN After reloading Remanence Table 9-41 BOOL 5 = TRUE, if retentive data are available. Startup OB: Data structure TI_Startup Parameter Data type Byte USINT 0 TI_Startup Description Data structure for startup OB SI_Format Format of the start information: 16#FF: None 16#FE: Optimized start information OB_Class USINT 1 OB class (=100) OB_Nr UINT 2 OB number (1...32767). LostRetentive BOOL 4 =TRUE, if the contents of retentive data areas have been lost. LostRTC BOOL 5 =TRUE, if the time-of-day of the real-time clock has been lost. Table 9-42 Time delay interrupt OB: Data structurer TI_Delay Parameter Data type Byte USINT 0 TI_Delay SI_Format Description Data structure for time delay interrupt OB Format of the start information: 16#FF: None 16#FE: Optimized start information 2576 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameter Data type Byte Description OB_Class USINT 1 OB class (=20) OB_Nr UINT 2 OB number (1...32767). Sign WORD 4 User ID: Input parameter SIGN from the call of the "SRT_DINT (Page 2707)" instruction. Table 9-43 Cyclic interrupt OB: Data structure TI_Cyclic Parameter Data type Byte USINT 0 TI_Cyclic Description Data structure for cyclic interrupt OB SI_Format Format of the start information: 16#FF: None 16#FE: Optimized start information OB_Class USINT 1 OB class (=30) OB_Nr UINT 2 OB number (1...32767). Initial_Call BOOL 4 = TRUE in the first call of this OB At the transition from STOP or HOLD to RUN After reloading Event_Count Table 9-44 INT 6 Number of discarded start events since the last start of this OB. Hardware interrupt OB: Data structure TI_HWInterrupt Parameter Data type Byte USINT 0 TI_HWInterrupt SI_Format Description Data structure for hardware interrupt OB Format of the start information: 16#FF: None 16#FE: Optimized start information OB_Class USINT 1 OB class (=40) OB_Nr UINT 2 OB number (1...32767). LADDR HW_IO 4 Hardware identifier of the module that triggers the hardware interrupt. USI WORD 6 Identifier for future extensions (not user-relevant). IChannel USINT 8 Number of the channel that triggered the hardware interrupt. EventType BYTE 9 Identifier for the event type associated with the event triggering the interrupt (e.g., rising edge). You can find this ID in the description of the respective module. address WORD 20 See "address" parameter for the TI_Cassic. data structure slv_prfl BYTE 22 See "slv_prfl" parameter for the TI_Cassic data structure. intr_type BYTE 23 See "intr_type" parameter for the TI_Cassic data structure. flags1 BYTE 24 See "flags1" parameter for the TI_Cassic data structure. flags2 BYTE 25 See "flags2" parameter for the TI_Cassic data structure. id UNIT 26 See "id" parameter for the TI_Cassic data structure. manufacturer UNIT 28 See "manufacturer" parameter for the TI_Cassic data structure. instance UNIT 30 See "instance" parameter for the TI_Cassic data structure. WinCC Basic V13.0 System Manual, 02/2014 2577 Programming the PLC 9.7 References Table 9-45 Time error OB: Data structure TI_TimeError Parameter Data type Byte USINT 0 TI_TimeError Description Data structure for time error OB SI_Format Format of the start information: 16#FF: None 16#FE: Optimized start information OB_Class USINT 1 OB class (=80) OB_Nr UINT 2 OB number (1...32767). Csg_OBnr OB_ANY 4 Number of the OB that was being executed when the time error occurred. Fault_ID BYTE 7 Error code. Possible values: B#16#01: Cycle time exceeded B#16#02: The requested OB is still being processed. B#16#05: Expired time-of-day interrupt due to time jump. B#16#06: Expired time-of-day interrupt upon re-entry into RUN after HOLD. B#16#07: Overflow of the OB request buffer for the current priority class. B#16#08: Isochronous mode interrupt - time error. B#16#09: Interrupt loss due to high interrupt load B#16#0B: Technology synchronization interrupt - time error Csg_Prio Table 9-46 UNIT 8 Priority of the OB that was being executed when the time error occurred. Diagnostic interrupt OB: Data structure TI_DiagnosticInterrupt Parameter Data type Byte TI_DiagnosticInterrupt SI_Format USINT Description Data structure for diagnostic interrupt OB 0 Format of the start information: 16#FF: None 16#FE: Optimized start information OB_Class USINT 1 OB class (=82) OB_Nr UINT 2 OB number (1...32767). LADDR HW_ANY 4 Hardware identifier of the hardware object that triggered the diagnostic interrupt. IO_State WORD 6 Status of the hardware object: Bit 0: Good Bit 1: Disabled Bit 2: Maintenance required Bit 3: Maintenance demanded Bit 4: Error Bit 5: Not accessible Bit 6: Qualified Bit 7: Not available Channel UINT 8 Channel number MultiError BOOL 10 =TRUE, if there is more than one error. address WORD 20 See "address" parameter for the TI_Cassic. data structure slv_prfl BYTE 22 See "slv_prfl" parameter for the TI_Cassic data structure. intr_type BYTE 23 See "intr_type" parameter for the TI_Cassic data structure. 2578 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameter Data type Byte Description flags1 BYTE 24 See "flags1" parameter for the TI_Cassic data structure. flags2 BYTE 25 See "flags2" parameter for the TI_Cassic data structure. id UINT 26 See "id" parameter for the TI_Cassic data structure. manufacturer UINT 28 See "manufacturer" parameter for the TI_Cassic data structure. instance UINT 30 See "instance" parameter for the TI_Cassic data structure. Table 9-47 Pull/plug interrupt OB: Data structure TI_PlugPullModule Parameter Data type Byte TI_PlugPullModule SI_Format Description Data structure for pull/plug interrupt OB USINT 0 Format of the start information: 16#FF: None 16#FE: Optimized start information OB_Class USINT 1 OB class (=83) OB_Nr UINT 2 OB number (1...32767). LADDR HW_IO 4 Hardware identifier of the affected module or submodule Event_Class BYTE 6 B#16#38: (Sub)module plugged B#16#39: (Sub)module pulled or not responding Fault_ID BYTE 7 Error code The following table shows the events that cause the start of the pull/plug interrupt OB. With Event_Class = B#16#38 - (sub-)module plugged: - B#16#54: PROFINET IO submodule inserted and matches configured submodule - B#16#55: PROFINET IO submodule inserted, but does not match configured submodule - B#16#56: PROFINET IO submodule inserted; but error in module parameter assignment - B#16#57: PROFINET IO submodule or module inserted, but with a problem or maintenance - B#16#58: PROFINET IO submodule, access error corrected With Event_Class = B#16#39 - (sub-)module pulled or cannot be reached: - B#16#51: PROFINET IO module removed - B#16#54: PROFINET IO submodule removed address WORD 20 See "address" parameter for the TI_Cassic. data structure slv_prfl BYTE 22 See "slv_prfl" parameter for the TI_Cassic data structure. intr_type BYTE 23 See "intr_type" parameter for the TI_Cassic data structure. flags1 BYTE 24 See "flags1" parameter for the TI_Cassic data structure. flags2 BYTE 25 See "flags2" parameter for the TI_Cassic data structure. id UINT 26 See "id" parameter for the TI_Cassic data structure. manufacturer UINT 28 See "manufacturer" parameter for the TI_Cassic data structure. instance UINT 30 See "instance" parameter for the TI_Cassic data structure. WinCC Basic V13.0 System Manual, 02/2014 2579 Programming the PLC 9.7 References Table 9-48 Rack error OB: Data structure TI_StationFailure Parameter Data type Byte USINT 0 TI_StationFailure SI_Format Description Data structure for rack error OB Format of the start information: 16#FF: None 16#FE: Optimized start information OB_Class USINT 1 OB class (=86) OB_Nr UINT 2 OB number (1...32767). LADDR HW_Devi ce 4 Hardware identifier of the defective hardware object. Event_Class BYTE 6 B#16#38: (Sub)module plugged Fault_ID BYTE 7 Error code B#16#39: (Sub)module pulled or not responding The following table shows the events that cause the start of the pull/plug interrupt OB. With Event_Class = B#16#38 - (sub-)module plugged: - B#16#54: PROFINET IO submodule inserted and matches configured submodule - B#16#55: PROFINET IO submodule inserted, but does not match configured submodule - B#16#56: PROFINET IO submodule inserted; but error in module parameter assignment - B#16#57: PROFINET IO submodule or module inserted, but with a problem or maintenance - B#16#58: PROFINET IO submodule, access error corrected With Event_Class = B#16#39 - (sub-)module pulled or cannot be reached: - B#16#51: PROFINET IO module removed - B#16#54: PROFINET IO submodule removed address WORD 20 See "address" parameter for the TI_Cassic. data structure slv_prfl BYTE 22 See "slv_prfl" parameter for the TI_Cassic data structure. intr_type BYTE 23 See "intr_type" parameter for the TI_Cassic data structure. flags1 BYTE 24 See "flags1" parameter for the TI_Cassic data structure. flags2 BYTE 25 See "flags2" parameter for the TI_Cassic data structure. id UINT 26 See "id" parameter for the TI_Cassic data structure. manufacturer UINT 28 See "manufacturer" parameter for the TI_Cassic data structure. instance UINT 30 See "instance" parameter for the TI_Cassic data structure. Table 9-49 Programming error OB / I/O access error OB: Data structure TI_ProgIOAccessError Parameter Data type Byte TI_ProgIOAccessError SI_Format USINT Description* Data structure for programming error OB and I/O access error OB 0 Format of the start information: 16#FF: None 16#FE: Optimized start information 2580 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameter OB_Class Data type Byte Description* USINT 1 OB class: =121 for programming error OB =122 for I/O access error OB OB_Nr UINT 2 OB number (1...32767). BlockNr UINT 4 Number of the block in which the programming error occurred. Reaction USINT 6 0: Ignore error 1: Substitute bad value 2: Skip command Fault_ID BYTE 7 Error code B#16#21: BCD conversion error B#16#22: Area length error when reading B#16#23: Area length error when writing B#16#24: Range error when reading B#16#25: Range error when writing B#16#26: Error in timer no. B#16#27: Error in counter no. B#16#28: Read access to a byte, word or double word with a pointer whose bit address is not zero B#16#29: Write access to a byte, word or double word with a pointer whose bit address is not zero B#16#:30: Write access to a write-protected global DB B#16#31: Write access to a write-protected instance DB B#16#32: DB number error when accessing a global DB B#16#33: DB number error when accessing an instance DB B#16#34: Number error during FC call B#16#35: Number error during FB call B#16#42: I/O access error, reading B#16#43: I/O access error, writing B#16#3A: Access to a DB that is not loaded; the DB number is located in the permitted area B#16#3C: Access to an FC that is not loaded; the FC number is within the permissible range B#16#3D: Access to an instruction (SFC) that is not loaded; the SFC number is within the permissible range B#16#3E: Access to an FB that is not loaded; the FB number is within the permissible range B#16#3F: Access to an SFB that is not available; the SFB number is within the permissible range BlockType USINT 8 Type of block in which the error has occurred: OB: B#16#88 FC: B#16#8C FB: B#16#8E WinCC Basic V13.0 System Manual, 02/2014 2581 Programming the PLC 9.7 References Parameter Area Data type Byte Description* USINT 9 Memory area in which the incorrect access occurred: Local data: B#16#40 to 4E, 86, 87, 8E, 8F, C0 to CE Process image input: B#16#01 Process image output: B#16#02 Technology DB: B#16#04 I: B#16#81 Q: B#16#82 M: B#16#83 DB: B#16#84, 85, 8A, 8B DBNr DB_ANY 10 Csg_OBNr OB_ANY 12 DB no. if AREA = DB (global DB or instance DB) Only relevant for programming error OB. OB number: 121: Programming error OB 122: I/O access error OB Csg_Prio USINT 14 OB priority Width USINT 15 Type of access during which the error occurred: Bit: B#16#00 Byte: B#16#01 Word: B#16#02 DWord: B#16#03 LWord: B#16#04 * Only certain output values are possible depending on the OB (I/O access error OB or programming error OB) from which information is read. Table 9-50 Time-of-day interrupt OB: Data structure TI_TimeOfDay Parameter Data type Byte TI_TimeOfDay SI_Format Description Data structure for time-of-day interrupt OB USINT 0 Format of the start information: 16#FF: None 16#FE: Optimized start information OB_Class USINT 1 OB class (=10) OB_Nr UINT 2 OB number (1...32767). CaughtUp BOOL 4 =TRUE if an OB call was executed subsequently because time was adjusted ahead SecondTime BOOL 5 =TRUE if an OB was called a second time because time was adjusted back. Note: SecondTime is set only once in situations in which the time is set back. Table 9-51 Isochronous mode interrupt OB: Data structure TI_SynchCycle Parameter Data type Byte TI_SynchCycle SI_Format Description Data structure for isochronous mode interrupt OB USINT 0 Format of the start information: 16#FF: None 16#FE: Optimized start information 2582 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameter Data type Byte Description OB_Class USINT 1 OB class (=61) OB_Nr UINT 2 OB number (1...32767). Initial_Call BOOL 4 = TRUE in the first call of this OB: Transition from STOP or HOLD to RUN After reloading IO _System USINT 5 Number of the distributed I/O system triggering the interrupt Event_Count INT 6 = n: Number of lost cycles = -1: An unknown number of cycles has been lost (e.g., because cycle has changed). PIP_Input BOOL 10 =TRUE: The associated process image of the inputs is up-to-date PIP_Output BOOL 11 =TRUE: The associated process image of the outputs was transferred to the outputs in good time after the last cycle SyncCycleTim e LTIME 16 Calculated cycle time Table 9-52 Status interrupt OB / update interrupt OB for manufacturer or profile-specific interrupt: Data structure TI_Submodule Parameter Data type Byte TI_Submodule SI_Format Description Data structure for status interrupt OB / update interrupt OB for manufacturer or profile-specific interrupt USINT 0 Format of the start information: 16#FF: None 16#FE: Optimized start information OB_Class USINT 1 OB class =55 for status interrupt OB =56 for update interrupt OB =57 for manufacturer or profile-specific interrupt OB OB_Nr UINT 2 OB number (1...32767). LADDR HW_IO 4 Hardware address of the component triggering the interrupt Slot UINT 6 Slot number of the component triggering the interrupt Specifier WORD 8 Interrupt specifier from the interrupt frame address WORD 20 See "address" parameter for the TI_Cassic. data structure slv_prfl BYTE 22 See "slv_prfl" parameter for the TI_Cassic data structure. intr_type BYTE 23 See "intr_type" parameter for the TI_Cassic data structure. flags1 BYTE 24 See "flags1" parameter for the TI_Cassic data structure. flags2 BYTE 25 See "flags2" parameter for the TI_Cassic data structure. id UINT 26 See "id" parameter for the TI_Cassic data structure. manufacturer UINT 28 See "manufacturer" parameter for the TI_Cassic data structure. instance UINT 30 See "instance" parameter for the TI_Cassic data structure. WinCC Basic V13.0 System Manual, 02/2014 2583 Programming the PLC 9.7 References Parameter AINFO Data structure of the destination area AINFO with interrupts from PROFIBUS DP Byte Meaning 0 to 3 Header information, for exact description, see below 4 to 63 Additional interrupt information: data for the respective interrupt: distributed: ARRAY[0] to ARRAY[59] Structure of the header information with interrupts from PROFIBUS DP Byte Data type Meaning 0 BYTE Length of the received interrupt information in bytes 1 BYTE central: 4 to 224 distributed: 4 to 63 central: Reserved distributed: ID for the interrupt type 1: 2: 3: 4: 5: 6: 31 Diagnostics interrupt Process interrupt Pull interrupt Plug interrupt Status interrupt Update interrupt Failure of an expansion device, DP master system or DP station 32 to 126: Manufacturer-specific interrupt 2 BYTE Slot number of the component that triggered the interrupt 3 BYTE central: Reserved distributed: Specifier Bits 0 and 1: 0: No further information; 1: Incoming event, fault at slot 2: Outgoing event, fault at slot cleared 3: Outgoing event, slot still faulty 2584 Bit 2: Add_Ack Bits 3 to 7: Sequence number WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Data structure of the destination area AINFO with interrupts from PROFINET IO or central I/O devices Byte Meaning 0 to 25 Header information, for exact description, see below 26 to 1431 Additional interrupt information: Standardized diagnostic data for the respective interrupt: ARRAY[0] to ARRAY[1405] Note: The additional interrupt information may also be omitted. Structure of the header information with interrupts from PROFINET IO or central I/O devices Byte Data type Meaning 0 and 1 WORD Bits 0 to 7: Block type Bits 8 to 15: Reserved 2 and 3 WORD Block length 4 and 5 WORD Version: Bits 0 to 7: low byte Bits 8 to 15: high byte 6 and 7 WORD ID for interrupt type: 1: Diagnostics interrupt (incoming) 2: Process interrupt 3: Remove module interrupt 4: Insert module interrupt 5: Status interrupt 6: Update interrupt 7: Redundancy interrupt 8: Controlled by supervisor 9: Released by supervisor 10: Configured module not inserted 11: Return of the sub-module 12: Diagnostics interrupt (outgoing) 13: Slave-to-slave connection alarm 14: Neighborhood change alarm 15: Clock synchronization message (bus end) 16: Clock synchronization alarm (device end) 17: Network component alarm 18: Time synchronization alarm (bus end) 19 to 31: Reserved 32 to 127: Manufacturer-specific interrupt 128 to 65535: Reserved 8 to 11 DWORD API (Application Process Identifier) 12 to 13 WORD Slot number of the component triggering the interrupt (value range 0 to 65535) 14 to 15 WORD Submodule slot number of the component triggering the interrupt (value range 0 to 65535) 16 to 19 DWORD Module identification; specific information on the source of the interrupt WinCC Basic V13.0 System Manual, 02/2014 2585 Programming the PLC 9.7 References Byte Data type Meaning 20 to 23 DWORD Submodule identification; specific information on the source of the interrupt 24 to 25 WORD Interrupt specifier: Bits 0 to 10: Sequence number (value range 0 to 2047) Bit 11: Channel diagnostics: 0: No channel diagnostics available 1: Channel diagnostic information exists Bit 12: Status of manufacturer-specific diagnostics: 0: No manufacturer-specific status information available 1: Manufacturer-specific status information available Bit 13: Status of diagnostics for sub-module: 0: No status information available, all errors have been corrected 1: At least one item of channel diagnostics and/or status information is available Bit 14: Reserved Bit 15: Application relationship diagnosis state: - 0: None of the modules configured within this application relationship reports diagnostic information - 1: At least one of the modules configured in this AR is reporting diagnostic information Structure of the additional interrupt information for interrupts from PROFINET IO or central I/O The additional interrupt information for PROFINET IO depends on the format identifier. It can comprise multiple data blocks with the same or different format identifier. The following format identifiers are available: 2586 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References W#16#0000 to W#16#7FFF: Manufacturer-specific diagnostics Byte Data type Meaning 0 to 1 WORD Format identifier for the structure of the following data serving as additional interrupt information W#16#0000 to W#16#7FFF: Manufacturer-specific diagnostics 2 to n BYTE See manufacturer's manual. W#16#8000: Channel diagnostics Channel diagnostics is output in blocks of 6 bytes each. The additional interrupt information (without format identifier) is only output for disrupted channels. Byte Data type Meaning 0 to 1 WORD Format identifier for the structure of the following data serving as additional interrupt information W#16#8000: Channel diagnostics 2 to 3 WORD Channel number of the component triggering the interrupt (value range: 0 to 65535): W#16#0000 to W#16#7FFF: Channel number of the interface module/ sub-module W#16#8000: The generic substitute for the entire sub-module W#16#8001 to W#16#FFFF: Reserved 4 BYTE Bits 0 to 2: Reserved Bits 3 to 4: Type of error: 0: Reserved 1: Incoming error 2: Outgoing error 3: Outgoing error, other errors present Bits 5 to 7: Type of channel: 0: Reserved 1: Input channel 2: Output channel 3: Input/output channel WinCC Basic V13.0 System Manual, 02/2014 2587 Programming the PLC 9.7 References Byte Data type Meaning 5 BYTE Data format: B#16#00: Free data format B#16#01: Bit B#16#02: 2 bits B#16#03: 4 bits B#16#04: Byte B#16#05: Word B#16#06: Double word B#16#07: 2 double words B#16#08 to B#16#FF: Reserved 6 to 7 WORD Type of error: W#16#0000: Reserved W#16#0001: Short circuit W#16#0002: Undervoltage W#16#0003: Overvoltage W#16#0004: Overload W#16#0005: Overtemperature W#16#0006: Wire break W#16#0007: High limit exceeded W#16#0008: Low limit exceeded W#16#0009: Error W#16#000A to W#16#000F: Reserved W#16#0010 to W#16#001F: Manufacturer-specific W#16#0020 to W#16#00FF: Reserved W#16#0100 to w#16#7FFF: Manufacturer-specific W#16#8000: Device diagnostics available W#16#8001 to W#16#FFFF: Reserved Not all channels support every error type. For detailed information, refer to the description of the diagnostic data for the specific device. Note The section from "channel number" to "type of error" can occur from 0 to n times. 2588 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References W#16#8001: MULTIPLE (different types of diagnostic information are transmitted). In this case, the additional interrupt information is transmitted as blocks of variable length. Byte Data type Meaning 0 to 1 WORD Format identifier for the structure of the following data serving as additional interrupt information W#16#8001: Manufacturer-specific diagnostics and/or channel diagnostics 2 to 3 WORD Block type 4 to 5 WORD Block length 6 BYTE Version: high byte 7 BYTE Version: low byte 8 to 11 DWORD API (only if low byte of version = 1) 12 to 13 WORD Slot number 14 to 15 WORD Subslot number 16 to 17 WORD Channel number 18 to 19 WORD Channel properties 20 to 21 WORD Format identifier: W#16#0000 to W#16#7FFF: Manufacturer-specific diagnostics W#16#8000: Channel diagnostics W#16#8002: Extended channel diagnostics W#16#8003: Stepped extended channel diagnostics W#16#8004 to W#16#80FF: Reserved 22 to n BYTE Data depend on the format identifier Note The section starting from "block type" can occur from 1 to n times. W#16#8002: Extended channel diagnostics WinCC Basic V13.0 System Manual, 02/2014 Byte Meaning 0 to 1 Format identifier W#16#8002 2 to 3 Channel number 4 to 5 Channel properties 6 to 7 Error type 8 to 9 Additional error value 10 to 13 Additional error information 2589 Programming the PLC 9.7 References W#16#8003: Stepped extended channel diagnostics Byte Meaning 0 to 1 Format identifier W#16#8003 2 to 3 Channel number 4 to 5 Channel properties 6 to 7 Error type 8 to 9 Additional error value 10 to 13 Additional error information 14 to 17 Qualified channel qualifier W#16#8100: Maintenance information Byte Meaning 0 to 1 Format identifier W#16#8100 2 to 3 Block type 4 to 5 Block length 6 to 7 Block version 8 to 9 Reserved 10 to 13 Maintenance status Note You can find more detailed information about the structure of the additional alarm information in the Programming Manual SIMATIC PROFINET IO from PROFIBUS DP to PROFINET IO and the current version of IEC 61158-6-10-1. Destination area TINFO and AINFO Destination area TINFO and AINFO Depending on the respective OB in which "RALRM (Page 2566)" is called, the destination areas TINFO and AINFO are only partially written. Refer to the table below to find out which information is entered respectively. Interrupt type OB class TINFO OB start information TINFO Management information AINFO Header information AINFO Additional interrupt information Process interrupt 4x Yes Yes Yes central: No distributed: as supplied by PROFIBUS DP slave/ PROFINET IO device Status interrupt 55 Yes Yes Yes Yes Yes Update interrupt 56 Yes Yes Yes Yes Yes Manufacturer-specific interrupt 57 Yes Yes Yes Yes Yes 2590 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Interrupt type OB class TINFO OB start information TINFO Management information AINFO Header information AINFO Additional interrupt information I/O redundancy error 70 Yes Yes No No No Diagnostics interrupt 82 Yes Yes Yes central: Structure according to PROFINET IO standard distributed: as supplied by PROFIBUS DP slave/ PROFINET IO device central: No distributed: as supplied by PROFIBUS DP slave/ PROFINET IO device Insert/remove interrupt 83 Yes Yes Yes Special form of the remove module interrupt: 83 Yes Yes Yes PROFINET IO only Special form of the 83 insert module interrupt: Yes Yes Yes PROFINET IO only Controlled by supervisor Enabled by supervisor Unconfigured module inserted 83 Yes Yes Yes PROFINET IO only Rack failure/ station failure 86 Yes Yes No No Yes No No No ... all other OBs D_ACT_DP: Enable/disable DP slaves Description Use the "D_ACT_DP" instruction to specifically deactivate and reactivate configured DP slaves/ PROFINET IO devices. In addition, you can determine whether each assigned DP slave or PROFINET IO device is currently activated or deactivated. If you use the instruction to deactivate an IE/PB Link PN IO type of gateway, then all connected PROFIBUS DP slaves will also cease to function. These failures will be reported. WinCC Basic V13.0 System Manual, 02/2014 2591 Programming the PLC 9.7 References The instruction cannot be used on PROFIBUS PA field devices that are connected by a DP/ PA link to a DP master system. Note As long as one or more "D_ACT_DP" jobs are active, you cannot load a changed configuration from the programming device to the CPU (within the scope of CiR). If a changed configuration is being loaded from the programming device to the CPU during ongoing operation (CiR), the CPU will reject activation of a "D_ACT_DP" job. Several runs through the cycle control point are required to perform the disabling or enabling job. Therefore, you cannot wait for the end of such a job in a programmed loop. Functional description "D_ACT_DP" is an instruction that works asynchronously, which means its execution extends over multiple calls. You start the job by calling D_ACT_DP with REQ = 1. The output parameters RET_VAL and BUSY indicate the status of the job. See also: Meaning of the parameters REQ, RET_VAL and BUSY with asynchronous instructions (Page 1736). Application If you configure DP slaves/PROFINET IO devices in a CPU which are not actually present or not currently required, the CPU will nevertheless continue to access these DP slaves/ PROFINET IO devices at regular intervals. After the slaves are deactivated, further CPU accessing will stop. With PROFIBUS DP, the fastest possible DP bus cycle can be achieved in this manner and the corresponding error events no longer occur. Examples From a machine OEM's point of view, there are numerous device options possible in series production of machines. However, each delivered machine includes only one combination of selected options. Every one of these possible machine options is configured as a DP slave/PROFINET IO device by the manufacturer in order to create and maintain a common user program having all possible options. Use "D_ACT_DP" to deactivate all DP slaves/PROFINET IO devices not present at machine startup. A similar situation exists for machine tools having numerous tooling options available but actually using only a few of them at any given time. These tools are implemented as DP slaves/ PROFINET IO devices. With "D_ACT_DP", the user program activates the tools currently needed and deactivates those required later. Identification of a job If you have started a deactivation or activation job and you call "D_ACT_DP" again before the job is complete, the behavior of the instruction depends on whether or not the new call involves 2592 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References the same job. If the input parameter LADDR matches, then the call will be interpreted as a follow-on call. Deactivating DP slaves/PROFINET IO devices When you deactivate a DP slave/PROFINET IO device with "D_ACT_DP", its process outputs are set to the configured substitute values or to 0 (safe state). The assigned DP master/ PROFINET IO controller does not continue to address this component. Deactivated DP slaves/ PROFINET IO devices are not identified as faulty or missing by the error LEDs on the DP master/PROFINET IO controller or CPU. The process image of the inputs of deactivated DP slaves/PROFINET IO devices is updated with 0, that is, it is handled just as it is for failed DP slaves/PROFINET IO devices. If you are using your program to directly access the user data of a previously deactivated DP slave/PROFINET IO device, the I/O access error OB is called and the corresponding start event is entered in the diagnostics buffer. If you attempt to access a deactivated DP slave/ PROFINET IO device via an instruction (such as "RD_REC (Page 2596)"), you will receive the same error information in RET_VAL as for an unavailable DP slave/PROFINET IO device. Deactivating a DP slave/PROFINET IO device does not start the program error OB, even if its inputs or outputs belong to the system-side process image to be updated. Also there is no entry in the diagnostics buffer. If a DP station/PNIO station fails after you have deactivated it with "D_ACT_DP", the operating system does not detect the failure. Applies to PROFIBUS DP: If you wish to deactivate DP slaves functioning as transmitters in slave-to-slave communication, we recommend that you first deactivate the receivers (listeners) that detect which input data the transmitter is transferring to its DP master. Deactivate the transmitter only after you have performed this step. Activating DP slaves/PROFINET IO devices When you reactivate a DP slave/PROFINET IO device with "D_ACT_DP", this component is configured and assigned parameters by the associated DP master/PROFINET IO controller (as with the return of a failed DP station/PROFINET IO station). This activation is complete when the component is able to transfer user data. Activating a DP slave/PROFINET IO device does not start the program error OB, even if its inputs or outputs belong to the system-side process image to be updated. Also there is no entry in the diagnostics buffer. If you try to activate a DP slave/PROFINET IO device with "D_ACT_DP" that cannot be accessed (for example, because it was physically separated from the bus), the instruction returns the error code W#16#80A7 after expiration of the configured parameter assignment time for distributed I/O. The DP slave/PROFINET IO device is activated and the fact that the activated DP slave/PROFINET IO device cannot be accessed results in a corresponding display in the system diagnostics. WinCC Basic V13.0 System Manual, 02/2014 2593 Programming the PLC 9.7 References If the DP slave/PROFINET IO device is accessible again afterwards, this results in standard system behavior (for example, a call of the OB configured for this purpose). Note Activating a DP slave/PROFINET IO device may be time-consuming. If you wish to cancel a current activation job, start "D_ACT_DP" again with the same value for LADDR and MODE = 2. Repeat the call of "D_ACT_DP" with MODE = 2 until successful cancellation of the activation job is indicated by RET_VAL = 0. If you wish to activate DP slaves which take part in the slave-to-slave communication, we recommend that you first activate the transmitters and then the receivers (listeners). Parameters The following table shows the parameters of the "D_ACT_DP" instruction: Parameter Declaration Data type Memory area Description REQ Input BOOL I, Q, M, D, L or constant Level-triggered control parameter I, Q, M, D, L or constant Job identifier Possible values: MODE Input USINT REQ=1: Execute activation or deactivation 0: Request information on whether the addressed component is activated or deactivated (output via RET_VAL parameter) 1: Activate the DP slave/PROFINET IO device 2: Deactivate the DP slave/PROFINET IO device LADDR Input HW_DEVICE I, Q, M, D, L or constant Hardware identifier of the DP slave (HW_DPSlave)/PROFINET IO device (HW_Device) The number can be taken from the properties of the DP slave / PROFINET IO device in the Network view or from the "System constants" tab of the standard tag table. If both the identifier for the device diagnostics as well as the ID for operating state transitions are both specified there, you must use the code for the device diagnostics. RET_VAL Return INT I, Q, M, D, L If an error occurs while the instruction is being executed, the return value contains an error code. BUSY Output BOOL I, Q, M, D, L Active code: BUSY = 1: The job is still active. BUSY = 0: The job was terminated. You can find additional information on valid data types in "Overview of the valid data types (Page 1204)". 2594 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References RET_VAL parameter Error code* Explanation (W#16#...) 0000 Job completed without error. 0001 The DP slave/PROFINET IO device is active (this error code is possible only with MODE = 0.) 0002 The DP slave/PROFINET IO device is deactivated (this error code is possible only with MODE = 0.) 7000 First call with REQ=0. The job specified with LADDR is not active; BUSY has the value "0". 7001 First call with REQ=1. The job specified with LADDR was initiated. BUSY has the value "1". 7002 Intermediate call (REQ irrelevant). The activated job is still active; BUSY has the value "1". 8090 You have not configured a module with the address specified in LADDR. You operate your CPU as I-Slave and you have specified in LADDR an address of this I-Slave. 8092 The deactivation of the currently addressed DP slave/PROFINET IO device (MODE=2) cannot be canceled by being activated (MODE=1). Activate the component at a later time. 8093 No DP slave / PROFINET IO device that can be activated or deactivated is assigned to the address specified in LADDR. 8094 You have attempted to activate a device which is potential partner for a tool change port. However, another device is already activated on this tool change port at this time. The activated device will remain activated. 80A0 Error during the communication between the CPU and the IO controller. 80A1 Parameters could not be assigned for the addressed component. (This error code is only available when MODE = 1.) Note: "D_ACT_DP" returns this error information only if the activated slaves/devices of this component fails again during parameter assignment. If the parameter assignment of a single module was unsuccessful, "D_ACT_DP" returns the error information W#16#0000. 80A2 The addressed DP slave does not return an acknowledgment. (This error information is not available with PROFINET IO devices. The process is not time-monitored by PROFINET.) 80A3 The DP master/PROFINET IO controller concerned does not support this function. 80A4 The CPU does not support this function for external DP masters/PROFINET IO controller. 80A6 Slot error in the DP slave/PROFINET IO device; not all user data can be accessed (this error code is only available when MODE=1). Note: "D_ACT_DP" returns this error information only if the activated component fails again after parameter assignment and before the end of "D_ACT_DP". If only a single module is unavailable, "D_ACT_DP" returns the error information W#16#0000. 80A7 Activation of a non-accessible device. 80AA Activation with errors in the DP slave/PROFINET IO device: Differences in the configuration 80AB Activation with errors in the DP slave/PROFINET IO device: Parameter assignment error 80AC Activation with errors in the DP slave/PROFINET IO device: Maintenance required 80C1 "D_ACT_DP" has been started and is being continued with another address (this error code is possible when MODE=1 and MODE=2). 80C3 Temporary resource error: The CPU is currently processing the maximum possible activation and deactivation jobs. (This error code is available only when MODE = 1 and MODE = 2.) The CPU is busy receiving a modified configuration. Currently you can not enable/disable DP slaves/ PROFINET IO devices. 80C5 DP: Jobs not collected by the user are discarded at restart. 80C6 PROFINET: Jobs not collected by the user are discarded at restart. WinCC Basic V13.0 System Manual, 02/2014 2595 Programming the PLC 9.7 References Error code* Explanation (W#16#...) General error information See also: GET_ERR_ID: Get error ID locally (Page 1964) * The error codes can be displayed as integer or hexadecimal values in the program editor. For additional information on toggling display formats, refer to "See also". Others RD_REC: Read data record from I/O Description Use the instruction to read the data record with the number RECNUM from the addressed module. You start the read process by assigning the value "1" to the input parameter REQ during the call. If the read process could be executed immediately, the instruction returns the value "0" at the output parameter BUSY . If BUSY has the value "1", reading is not yet complete. See also: Meaning of the parameters REQ, RET_VAL and BUSY with asynchronous instructions (Page 1736). The data record read is entered in the target range spanned by the RECORD parameter, providing the data transfer was free of errors. Note When you read out a data record with a number greater than one from an FM or a CP you have purchased prior to February 1997 (below referred to as "old modules"), "RD_REC" responds differently than it does in new modules. This special situation is covered in the section "Using old S7-300 FMs and CPs with data record numbers >1" (see below). If a DPV1 slave is configured via GSD file (GSD rev. 3 and higher) and the DP interface of the DP master is set to "S7 compatible", then you may not read any data records from the I/ O modules in the user program with "RD_REC". In this case, the DP master addresses the wrong slot (configured slot + 3). Remedy: Set the interface of the DP master to "DPV1". Parameters The following table shows the parameters of the "RD_REC" instruction: Parameter Declaration Data type Memory area Description REQ Input BOOL I, Q, M, D, L or constant REQ = 1: Read request LADDR Input HW_IO I, Q, M, D, L or constant Hardware identifier of the module. RECNUM Input BYTE I, Q, M, D, L or constant Data record number (permitted values: 0 to 240) 2596 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameter Declaration Data type Memory area Description RET_VAL Return INT I, Q, M, D, L If an error occurs while the instruction is being executed, the return value contains an error code. In addition: the length of the data record actually transferred in bytes (possible values: +1 to +240), if the target range is greater than the transferred data record and if no error occurred during the transfer. BUSY Output BOOL I, Q, M, D, L BUSY = 1: The reading process is not yet complete. RECORD Output ANY I, Q, M, D, L Target range for the data record read. With asynchronous execution of "RD_REC", make sure that the actual parameters of RECORD have the same length information for all calls. Only the BYTE data type is permitted. Note: Note that for S7-300 CPUs the parameter RECORD always requires the full specification of the DB parameters (for example, P#DB13.DBX0.0 byte 100). The omission of an explicit DB number is only permitted for S7-300 CPUs and leads to an error message in the user program. For additional information on valid data types, refer to "Overview of the valid data types (Page 1204)". Parameter RECORD Note If you want to ensure that the entire data record is always read, select a target range with a length of 241 bytes. If the data transfer is without error, RET_VAL contains the actual data record length. Using old S7-300 FMs and CPs with data record numbers > 1 If you want to use the instruction "RD_REC" to read out a data record with a number greater than one from an old S7-300 FM or old S7-300 CP, remember the following points: If the target range is greater than the actual length of the required data record, no data is entered in RECORD . RET_VAL is written with W#16#80B1. If the target range is smaller than the actual length of the required data record, the CPU reads as many bytes beginning at the start of the record as are specified in the length information of RECORD and enters this number of bytes inRECORD . RET_VAL has the value "0". If the length specified in RECORD is the same as the actual length of the required data record, the CPU reads the data record and enters it in RECORD . RET_VAL is written with "0". WinCC Basic V13.0 System Manual, 02/2014 2597 Programming the PLC 9.7 References RET_VAL parameter If an error has occurred while the function was being executed, the return value contains an error code. If no error occurred during the transfer, RET_VAL contains the following: - 0, if the entire target range was filled with data from the selected data record (the data record can also be incomplete). - The length of the data record actually transferred in bytes (possible values: +1 to +240) if the target range is greater than the transferred data record. Note If the general error W#16#8745 occurs, this only indicates that access to at least one byte of the process image was blocked. The data record was read by the module correctly and written to the I/O memory area. When looking at the "real" error information (error codes W#16#8xyz) in the following table, we distinguish between two cases: Temporary errors (error codes W#16#80A2 to 80A3, 80Cx): This type of error can possibly be eliminated without user action, meaning it is helpful to call the instruction again (multiple calls, if necessary). Example of a temporary error: Resources required are currently in use (W#16#80C3). Permanent errors (error codes W#16#809x, 80A0, 80A1, 80Bx): This type of error does not correct itself. A new call of the instruction will not be successful until you have eliminated the error. Example of a permanent error: Wrong length specification in RECORD (W#16#80B1). Note If you transfer data records to a DPV1 slave with "WR_REC (Page 2600)" or if you read data records from a DPV1 slave with RD_REC and if this DPV1 slave operates in DPV1 mode, the DP master evaluates the error information it received from the slave as follows: If the error information lies within the range from W#16#8000 to W#16#80FF or W#16#F000 to W#16#FFFF, the DP master passes the error information to the instruction. If the error information is outside this range, the DP master passes the value W#16#80A2 to the instruction and suspends the slave. For a description of the error information originating from DPV1 slaves, refer to STATUS[3] Parameter STATUS (Page 2568). Parameter RET_VAL for WR_REC and RD_REC Error code* (W#16#...) Explanation Restriction 0000 No error - 7000 First call with REQ=0: No data transfer active; BUSY has the value 0. - 7001 First call with REQ=1: Data transfer started; BUSY has the value 1. Distributed I/O 2598 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Error code* (W#16#...) Explanation Restriction 7002 Intermediate call (REQ irrelevant): Data transfer already active; BUSY has the value 1. Distributed I/O 8090 Address specified at parameter ADDR is invalid. - 8092 A type other than BYTE is specified in the ANY reference. - 8093 This instruction is not permitted for the module selected by means of LADDR and IOID . - 80A0 Negative acknowledgment when reading from the module: Module was removed during the reading process or is defective With "RD_REC" only 80A1 Negative acknowledgment when writing to the module: Module was removed during the writing process or is defective With "WR_REC (Page 2600)" only 80A2 DP protocol error at layer 2 (for example, slave failure or bus problems) Distributed I/O For ET200S, data record cannot be read in DPV0 mode. 80A3 DP protocol error with user interface/user Distributed I/O 80A4 Communication on PBUS+ disrupted - 80B0 Instruction not possible for module type. - The module does not recognize the data record. Data record number 241 not permitted. With "WR_REC (Page 2600)", data records 0 and 1 are not permitted. 80B1 The length specified in parameter RECORD is incorrect. With "WR_REC (Page 2600)": Length incorrect With "RD_REC" (only when using old S7-300 FMs and S7-300 CPs): specified length > data record length With DPNRM_DG: specified length < data record length 80B2 The configured slot is not assigned. - 80B3 Actual module type does not match specified module type - 80B7 DP slave or module reports an invalid range for a parameter or value. With "RD_REC" only 80C0 With "WR_REC (Page 2600)": the data can only be written when the CPU is in STOP mode. Note: this means that writing by the user program is not possible. You can only write the data online with PG/ PC. With "WR_REC (Page 2600)" or "RD_REC" or "DPNRM_DG (Page 2616)" With "RD_REC": the module routes the data record, but either no data is present or the data can only be read when the CPU is in STOP mode. Note: if data can only be read when the CPU is in STOP mode, then an evaluation by the user program is not possible. In this case, you can only read the data online with PG/PC. With "DPNRM_DG (Page 2616)": There are no diagnostic data available. WinCC Basic V13.0 System Manual, 02/2014 2599 Programming the PLC 9.7 References Error code* (W#16#...) Explanation Restriction 80C1 The data of the previous write job on the module for the same data record have not yet been processed by the module. - 80C2 The module is currently processing the maximum possible number of jobs for a CPU. - 80C3 The required resources (memory, etc.) are currently occupied. - 80C4 Internal temporary error. Job could not be executed. - Repeat the job. If this error occurs often, check your installation for sources of electrical interference. 80C5 Distributed I/O not available. Distributed I/O 80C6 Data record transfer stopped due to priority class abort (restart or background) Distributed I/O General error information See also: GET_ERR_ID: Get error ID locally (Page 1964) - * The error codes can be displayed as integer or hexadecimal values in the program editor. For additional information on toggling display formats, refer to "See also". WR_REC: Write data record to I/O Description Use the instruction "WR_REC" to transfer the data record RECORD to the addressed module. The data to be transferred are read from the RECORD parameter during the first call. If the transfer of the data record takes longer than the duration of one call, the contents of the RECORD parameter are no longer relevant for the subsequent instruction calls (for the same job). You start the writing process by assigning the value "1" to the input parameter REQ during the call. If the writing process could be executed immediately, the instruction returns the value "0" at the output parameter BUSY. If BUSY has the value "1", writing is not yet complete. Parameters The following table shows the parameters of the instruction "WR_REC": Parameter Declaration Data type Memory area Description REQ Input BOOL I, Q, M, D, L, T, C or constant REQ = 1: Write request LADDR Input HW_IO I, Q, M, D, L or constant Hardware identifier of the module. RECNUM Input BYTE I, Q, M, D, L or constant Data record number RECORD Input VARIANT I, Q, M, D, L Data record 2600 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameter Declaration Data type Memory area Description RET_VAL Return INT I, Q, M, D, L If an error occurs while the instruction is being executed, the return value contains an error code. BUSY Output BOOL I, Q, M, D, L BUSY = 1: The writing process is not yet completed. You will find more detailed information on valid data types in "Overview of the valid data types (Page 1204)". Parameter RET_VAL See also: RD_REC: Read data record from I/O (Page 2596) Note If the general error W#16#8544 occurs, it only indicates that access to at least one byte of the I/O memory area containing the data record was denied. The data transfer was continued. DPRD_DAT: Read consistent data of a DP standard slave Description Use the instruction "DPRD_DAT" to read out consistent data from an I/O module. The instruction can be used for the central modules as well as for the DP standard slaves and PROFINET IO devices. You require "DPRD_DAT" because you can only read out a maximum of four continuous bytes using the load commands that access the I/O or the process image input table. If required, you can also read consistent data via the process image of the inputs. Refer to the related documentation to find out if your CPU supports this functionality. For additional information on consistent data of a DP standard slave/PROFINET IO device, refer to Section "Data consistency (Page 3074)". If necessary, the instruction "DPRD_DAT" can also be used for a data area of 1 byte or larger. For information on the maximum length of the data, refer to the documentation of your CPU (e.g. 64 bytes for an S7-1214). WinCC Basic V13.0 System Manual, 02/2014 2601 Programming the PLC 9.7 References Use the parameter LADDR to select the module of the DP normslave/PROFINET IO device. If an access error occurs, the error code W#16#8090 is output. Use the RECORD parameter to define the target range of the read data: - The target range has to be at least as long as the inputs of the selected module. Only the inputs are transferred, the other bytes are not considered. If you read from a DP standard slave with a modular configuration or with several DP identifiers, you can only access the data of a module of the configured hardware identifier per "DPRD_DAT" call. If you select a target range that is too small, the error code 80B1 is output at the RET_VAL parameter. - All bit strings and all integers can be used as data type. It is also possible to use these data types in a data structure of the ARRAY type . The data type STRING is not supported. If there was no error during the data transmission, the data that have been read are entered in the target range defined at the RECORD parameter. Parameters The following table shows the parameters of the instruction "DPRD_DAT": Parameter Declaration Data type Memory area Description LADDR Input HW_IO I, Q, M, L or constant Hardware ID of the module from which the data is to be read. The hardware ID can be found in the properties of the module in the device view or system constants. RET_VAL Return INT I, Q, M, D, L If an error occurs while the instruction is being executed, the return value contains an error code. RECORD Output VARIANT I, Q, M, D, L Destination area for the user data that were read. For additional information on valid data types, refer to "Overview of the valid data types (Page 1204)". RET_VAL parameter Error code* (W#16#...) Explanation 0000 No error occurred. 8090 You have not configured a module for the specified hardware identifier or You have ignored the restriction concerning the length of consistent data, or you have not specified a hardware identifier as an address at parameter LADDR . 8092 A data type other than (Array of) bit string or integer was specified at the RECORD parameter. 8093 No DP module/PROFINET IO device from which you can read consistent data exists for the hardware identifier specified in LADDR . This error code also occurs if the module addressed by means of LADDR does not have inputs. 80A0 An access error was detected when accessing the I/O. 2602 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Error code* (W#16#...) Explanation 80B1 The length of the specified target range at parameter RECORD is shorter than the configured user data length. 80C0 The data have not been read yet. General error information See also: GET_ERR_ID: Get error ID locally (Page 1964) * The error codes can be displayed as integer or hexadecimal values in the program editor. For additional information on toggling display formats, refer to "See also". See also Parameter STATUS (Page 2568) DPWR_DAT: Write consistent data of a DP standard slave Description Use the instruction "DPWR_DAT" to transfer the data at the parameters RECORD consistently to the addressed module of the central module or of the DP standard slave/PROFINET IO device and if necessary to the process image (i.e. if the affected address range of the DP standard slaves is projected as consistency range in a process image). You require "DPWR_DAT" because you can only write a maximum of four continuous bytes using the transfer commands that access the I/O or process image output. If required, you can also write consistent data via the process image outputs. Refer to the related documentation to find out if your CPU supports this functionality. Do not use both possibilities concurrently when writing consistent data: Either use "DPWR_DAT" or write via the process image output table. For additional information on consistent data of a DP standard slave/PROFINET IO device, refer to Section "Data consistency (Page 3074)". If the DP standard slave has a modular design, you can only access one module of the DP slave. CAUTION I/O access When using "DPWR_DAT", avoid accessing I/O areas that have process image partitions with OB6x connections (isochronous mode interrupts) assigned to them. If necessary, the instruction "DPRD_DAT" can also be used for a data area of 1 byte or larger. For information on the maximum length of the data, refer to the documentation of your CPU (e.g. 64 bytes for an S7-1214). WinCC Basic V13.0 System Manual, 02/2014 2603 Programming the PLC 9.7 References Use the LADDR parameter to select the DP standard slave / PROFINET IO device. If an access error occurs on the addressed module, the error code 8090 is output. Use the RECORD parameter to define the source range of the data to be written: - The source range has to be at least as long as the outputs of the selected module. Only the outputs are transferred, the other bytes are not considered. If the source range at parameter RECORD is longer than the outputs of the configured module, only the data up to the maximum length of the outputs is transferred. If the source range at parameter RECORD is shorter than the outputs of the configured module, the error code 80B1 is output. - The following data types can be used: Byte, Char, Word, LWord, DWord, Int, UInt, USInt, SInt, LInt, ULInt, DInt, UDInt. The use of these data types in a data structure of the type ARRAY or STRUCT is also permissible. - The data type STRING is not supported. The data is transferred synchronously, that is, the write process is completed when the instruction is completed. Parameters The following table shows the parameters of the instruction "DPWR_DAT": Parameter Declaration Data type Memory area Description LADDR Input HW_IO I, Q, M, L or constant Hardware ID of the module to which the data is to be written. The hardware ID can be found in the properties of the module in the device view or system constants. RECORD Input VARIANT I, Q, M, D, L Source area for the user data to be written. RET_VAL Return INT I, Q, M, D, L If an error occurs while the instruction is being executed, the return value contains an error code. For additional information on valid data types, refer to "Overview of the valid data types (Page 1204)". RET_VAL parameter Error code* (W#16#...) Explanation 0000 No error occurred. 8090 You have not configured a module for the specified hardware identifier or You have ignored the restriction concerning the length of consistent data, or you have not specified a hardware identifier at parameter LADDR . 8092 2604 A data type other than (Array of) bit string or integer was specified at the RECORD parameter. WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Error code* (W#16#...) Explanation 8093 No DP module /PROFINET IO device to which you can write consistent data exists at the HW ID specified in LADDR . This error code also occurs if the DP standard slave / PROFINET IO device addressed via LADDR does not have outputs. 80A1 Access error detected while I/O devices were being accessed. 80B1 The length of the specified source range at the RECORD parameter is shorter than the outputs of the configured DP standard slave / PROFINET IO device. 80C1 The data of the previous write job have not yet been processed by the DP standard slave / PROFINET IO device. General error information See also: GET_ERR_ID: Get error ID locally (Page 1964) * The error codes can be displayed as integer or hexadecimal values in the program editor. For additional information on toggling display formats, refer to "See also". See also Parameter STATUS (Page 2568) iDevice / iSlave RCVREC: Receive data record Description An I-device can receive a data record from a superordinate controller. The receipt takes place in the user program with the instruction "RCVREC" (receive record). The instruction has the following operating modes: Check whether the I-device has a request for a data record receipt. Make the data record available to the output parameters. Send an answer to the superordinate controller. You can determine the operating mode executed by the instruction using the input parameter MODE (see below). The I-device must be in the RUN or STARTUP mode. With MLEN, you specify the maximum number of bytes you want to receive. The selected length of the target range RECORD should have at least the length of MLEN bytes. If a data record was received (MODE=1 or MODE=2), the output parameter NEW will indicate that the data record was stored in RECORD. Note that RECORD has a sufficient length. The output parameter LEN contains the actual length of the data record received in bytes. WinCC Basic V13.0 System Manual, 02/2014 2605 Programming the PLC 9.7 References Set CODE1 and CODE2 to zero for the positive answer to the superordinate controller. If the received data record is to be rejected, enter the negative answer to the superordinate controller in Error Code 1 of the CODE1 and in Error Code 2 of the CODE2. Note If the I-device has received a request for a data record receipt, you must recognize the delivery of this request within a certain duration. After recognition, you must send an answer to the superordinate controller within this time period. Otherwise the I-device will experience a timeout error which causes the operating system of the I-device to send a negative answer to the superordinate controller. For information on the value for the time period, refer to the specifications of your CPU. The output parameter STATUS receives the error information after the occurrence of an error. Operating modes You can determine the operating mode of the instruction "RCVREC" with the input parameter MODE. This step will be explained in the following table. MODE Meaning 0 Check whether a request for a data record receipt exists If a data record from a higher-level controller exists on the I-device, the instruction will only write the output parameters NEW, SLOT, SUBSLOT, INDEX and LEN. If you call the instruction several times with MODE=0, then the output parameter will only refer to one and the same request. 1 Receiving a data record for any subslot of the I-device If a data record from a superordinate controller exists on the I-device for any subslot of the I-device, the instruction will write the output parameter and transfer the data record to the parameter RECORD. 2 Receiving a data record for a specific subslot of the I-device If a data record from a superordinate controller exists on the I-device for a specific subslot of the I-device, the instruction will write the output parameter and transfer the data record to the parameter RECORD. 3 Sending a positive answer to the superordinate controller The instruction checks the request of the superordinate controller to receive a data record, accepts the existing data record and sends a positive acknowledgment to the superordinate controller. 4 Sending a negative answer to the superordinate controller The instruction checks the request of the superordinate controller to receive a data record, rejects the existing data record and sends a negative acknowledgment to the superordinate controller. Enter the reason for the rejection in the input parameters CODE1 and CODE2. Note After the receipt of a data record (NEW=1) you must call "RCVREC" twice to ensure complete processing. You must do this in the following order: First call with MODE=1 or MODE=2 Second call with MODE=3 or MODE=4 2606 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameters The following table shows the parameters of the "RCVREC" instruction: Parameter Declaration Data type Memory area Description MODE Input INT I, Q, M, D, L or constant Mode F_ID Input HW_SUBMO DULE I, Q, M, D, L or constant Subslot in the transfer area of the I-device for the data record to be received (only relevant for MODE=2). The high word is always set to zero. MLEN Input INT* I, Q, M, D, L or constant Maximum length of the data record to be received in bytes CODE1 Input BYTE I, Q, M, D, L or constant Zero (for MODE=3) and/or Error Code 1 (forMODE=4) CODE2 Input BYTE I, Q, M, D, L or constant Zero (for MODE=3) and/or Error Code 2 (forMODE=4) NEW Output BOOL I, Q, M, D, L MODE = 0: New data record was received MODE=1 or 2: Data record was transferred to RECORD STATUS Output DWORD I, Q, M, D, L Error information SLOT Output HW_SUBMO DULE I, Q, M, D, L Identical to F_ID SUBSLOT Output HW_SUBMO DULE I, Q, M, D, L Identical to F_ID INDEX Output UINT I, Q, M, D, L Number of the data record received LEN Output UINT I, Q, M, D, L Length of the data record received RECORD InOut VARIANT I, Q, M, D, L Target range for the data record received. Note: Note that for S7-300 CPUs the parameter RECORD always requires the full specification of the DB parameters (for example, P#DB13.DBX0.0 Byte 100). The omission of an explicit DB number is not permitted for S7-300 CPUs and results in an error message in the user program. * Use the data type UINT in the STL programming language. For additional information on valid data types, refer to "Overview of the valid data types (Page 1204)". Parameter STATUS For interpretation of the parameter STATUS refer to section: Parameter STATUS (Page 2568) WinCC Basic V13.0 System Manual, 02/2014 2607 Programming the PLC 9.7 References PRVREC: Make data record available Description An I-device can receive a request from a superordinate controller to make a data record available. The I-device makes the data record available in the user program with the instruction "PRVREC" (provide record). The instruction has the following operating modes: Check whether the I-device has a request for making a data record available. Transfer the requested data record to the superordinate controller. Sending an answer to the superordinate controller. You can determine the operating mode executed by the instruction using the input parameter MODE (see below). The I-device must be in the RUN or STARTUP mode. Enter the maximum number of bytes the data record to be sent should have with LEN. The selected length of the target range RECORD should have at least the length of LEN bytes. If a request to make a data record available exists, (MODE=0), the output parameter NEW will be set to TRUE. If the request for making a data record available is accepted, write RECORD for the positive answer to the superordinate controller with the requested data record and write zero for CODE1 and CODE2. If the request for making a data record available is to be rejected, enter the negative answer to the superordinate controller in Error Code 1 of the CODE1 and in Error Code 2 of theCODE2. Note If the I-device has received a request for making a data record available, you must recognize the delivery of this request within a certain time period. After recognition, you must send an answer to the superordinate controller within this time period. Otherwise the I-device will experience a timeout error which causes the operating system of the I-device to send a negative answer to the superordinate controller. For information on the value for the time period, refer to the specifications of your CPU. The output parameter STATUS receives the error information after the occurrence of an error. 2608 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Operating modes You can determine the operating mode of the instruction "PRVREC" with the input parameter MODE. This step will be explained in the following table. MODE Meaning 0 Check whether a request for making a data record available exists If a request from a higher-level controller for making a data record available exists on the I-device, the instruction will only write the output parameters NEW, SLOT, SUBSLOT, INDEX and RLEN. If you call the instruction several times with MODE=0, then the output parameter will only refer to one and the same request. 1 Receiving a request for making a data record available for any subslot of the I-device If such a request from a superordinate controller for any subslot of the I-device exists on the I-device, the instruction will write the output parameter. 2 Receiving a request for making a data record available for a specific subslot of the I-device If such a request from a superordinate controller for a specific subslot of the I-device exists on the I-device, the instruction will write the output parameter. 3 Make the data record available and send a positive answer to the superordinate controller The instruction checks the request of the superordinate controller to make a data record available, makes the request data record available to RECORD and sends a positive acknowledgement to the superordinate controller. 4 Sending a negative answer to the superordinate controller The instruction checks the request of the superordinate controller to make a data record available, rejects this request and sends a negative acknowledgement to the superordinate controller. Enter the reason for the rejection in the input parameters CODE1 and CODE2. Note After the receipt of a request (NEW=1) you must call the instruction twice to ensure complete processing. You must do this in the following order: First call with MODE=1 or MODE=2 Second call with MODE=3 or MODE=4 Parameters The following table shows the parameters of the "PRVREC" instruction: Parameter Declaration Data type Memory area Description MODE Input INT I, Q, M, D, L or constant Mode F_ID Input HW_SUBMO DULE I, Q, M, D, L or constant Subslot in the transfer area of the I-device for the data record to be sent (only relevant for MODE=2). The high word is always set to zero. CODE1 Input BYTE I, Q, M, D, L or constant Zero (for MODE=3) and/or Error Code 1 (forMODE=4) CODE2 Input BYTE I, Q, M, D, L or constant Zero (for MODE=3) and/or Error Code 2 (forMODE=4) LEN Input UINT I, Q, M, D, L or constant Maximum length of the data record to be sent in bytes WinCC Basic V13.0 System Manual, 02/2014 2609 Programming the PLC 9.7 References Parameter Declaration Data type Memory area Description NEW Output BOOL I, Q, M, D, L The new data record was requested by the superordinate controller. STATUS Output DWORD I, Q, M, D, L Error information SLOT Output HW_SUBMO DULE I, Q, M, D, L Identical to F_ID SUBSLOT Output HW_SUBMO DULE I, Q, M, D, L Identical to F_ID INDEX Output UINT I, Q, M, D, L Number of the data record to be sent RLEN Output UINT I, Q, M, D, L Length of the data record to be sent RECORD InOut VARIANT I, Q, M, D, L Data record made available Note: Note that for S7-300 CPUs the parameter RECORD always requires the full specification of the DB parameters (for example, P#DB13.DBX0.0 Byte 100). The omission of an explicit DB number is not permitted for S7-300 CPUs and results in an error message in the user program. For additional information on valid data types, refer to "Overview of the valid data types (Page 1204)". Parameter STATUS For interpretation of the parameter STATUS refer to section: Parameter STATUS (Page 2568) PROFIBUS DPSYC_FR: Synchronize DP slaves / Freeze inputs Description You use the instruction to synchronize one or more groups of DP slaves. The function involves sending one of the control commands below, or a combination of them, to the relevant groups: SYNC (simultaneous output and freezing of output states on the DP slaves) UNSYNC (cancels the SYNC control command) FREEZE (freeze the input states on the DP slaves and read in the frozen inputs) UNFREEZE (cancels the FREEZE control command) 2610 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Before you send the control commands listed above, you must assign the DP slaves to groups per configuration. You must know which DP slave is assigned to which group, with which number and know the reactions of the various groups to SYNC/FREEZE. Note Note that the control commands SYNC and FREEZE also remain valid when you perform a warm/cold restart. Please note also that you may initiate only one SYNC/UNSYNC job or only one FREEZE/ UNFREEZE job at a time. Functional description "DPSYC_FR" works asynchronously, that is, its execution extends over multiple calls. You start the job by calling "DPSYC_FR" with REQ=1. The output parameters RET_VAL and BUSY indicate the status of the job. See also: Meaning of the parameters REQ, RET_VAL and BUSY with asynchronous instructions (Page 1736). Identification of a job If you have triggered a SYNC/FREEZE job and called "DPSYC_FR" again before the first job was completed, the response of the instruction depends on whether the new call is for the same job. If the input parameters LADDR, GROUP and MODE match, the call is interpreted as a follow-on call. Writing outputs of DP modules The writing of outputs of DP modules is triggered as follows: By transfer commands to the DP I/O By writing the process image of the outputs to the modules (by the operating system at the end of OB 1 or by calling the instruction "UPDAT_PO (Page 2553)") Calling the "DPWR_DAT (Page 2603)" instruction. In normal operation, the DP master transfers the output bytes cyclically (within the cycle of the PROFIBUS DP bus) to the outputs of the DP slaves. If you want to have certain output data (possibly distributed on several slaves) applied to the outputs to the process at exactly the same time, you can send the SYNC control command to the relevant DP master using the "DPSYC_FR" instruction. What are the effects of SYNC? With the SYNC control command, the DP slaves of the selected groups are switched to Sync mode. In other words, the DP master transfers the current output data and instructs the DP slaves involved to freeze their outputs. With the following output message frames, the DP WinCC Basic V13.0 System Manual, 02/2014 2611 Programming the PLC 9.7 References slaves enter the output data in an internal buffer and the state of the outputs remains unchanged. Following each SYNC control command, the DP slaves of the selected groups apply the output data of their internal buffer to the outputs on the process. The outputs are only updated cyclically again when you send the UNSYNC control command using the "DPSYC_FR" instruction. Note If the DP slaves of the selected group(s) are not currently connected to the network or have failed when the control command was sent, they will not be switched to SYNC mode. This information will not be communicated in the return value of the instruction. Reading input data of DP modules The input data of the DP modules are read as follows: Using load commands to the DP I/O When the process image of the inputs is updated (by the operating system at the start of OB 1 or by calling the "UPDAT_PI (Page 2551)" instruction) By calling the "DPRD_DAT (Page 2601)" instruction. In normal operation, the DP master receives this input data cyclically (within the cycle of the PROFIBUS DP bus) from its DP slaves and makes them available to the CPU. If you want to have certain input data (possibly distributed on several slaves) to be read from the process at exactly the same time, send the FREEZE control command to the relevant DP master using the "DPSYC_FR" instruction. What are the effects of FREEZE? With the FREEZE control command, the DP slaves involved are switched to Freeze mode, in other words the DP master instructs the DP slaves to freeze the current state of the inputs. It then transfers the frozen data to the input area of the CPU. Following each FREEZE control command, the DP slaves freeze the state of their inputs again. The DP master only receives the current state of the inputs cyclically again after you have sent the UNFREEZE control command with the "DPSYC_FR" instruction. Note If the DP slaves of the selected group(s) are not currently connected to the network or have failed when the control command has been sent, they will not be switched to FREEZE mode. This information will not be communicated in the return value of the instruction. 2612 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Data consistency Because the DPSYC_FR functions are asynchronous and can be interrupted by higher priority classes, you should make sure that the process images are consistent with the actual inputs and outputs of the I/O when using the "DPSYC_FR" instruction. This is guaranteed if you comply with the following consistency rules: Define suitable process image partitions for the "SYNC outputs" and the "FREEZE inputs" (only possible on the S7-400). Call the "UPDAT_PO (Page 2553)" instruction immediately before each first call of a SYNC job. Call the "UPDAT_PI (Page 2551)" instruction immediately after the respective last call of a FREEZE job. As an alternative: Use only direct I/O access for outputs involved in a SYNC job and for inputs involved in a FREEZE job. Do not write to these outputs when a SYNC job is active and do not read in these inputs when a FREEZE job is active. Use of DPWR_DAT and DPRD_DAT If you use the "DPWR_DAT (Page 2603)" instruction, it must be complete before you send a SYNC job for the outputs involved. If you use the "DPRD_DAT (Page 2601)" instruction, it must be complete before you send a FREEZE job for the inputs involved. Startup and "DPSYC_FR" The user alone must take responsibility for sending the SYNC and FREEZE control commands in the startup OBs. If you want the outputs of one or more groups to be in SYNC mode when the user program starts, you must initialize these outputs during startup and completely execute the "DPSYC_FR" instruction with the SYNC control command. If you want the inputs of one or more groups to be in FREEZE mode when the user program starts, you must execute the "DPSYC_FR" instruction with the FREEZE control command completely for these inputs during startup. Parameters The following table shows the parameters of the "DPSYC_FR" instruction: Parameter Declaration Data type Memory area Description REQ Input BOOL I, Q, M, D, L or constant Level-triggered control parameter REQ = 1: Triggering of the SYNC/FREEZE job LADDR Input HW_DPMAST I, Q, M, D, L or ER constant WinCC Basic V13.0 System Manual, 02/2014 Hardware identifier of the DP master interface The number can be taken from the properties of the DP master interface in the Network view or from the "System constants" tab of the standard tag table. 2613 Programming the PLC 9.7 References Parameter Declaration Data type Memory area Description GROUP Input BYTE I, Q, M, D, L or constant Group selection Bit 0 = 1: group 1 selected Bit 1 = 1: group 2 selected : Bit 7 = 1: group 8 selected You can select several groups per job. The value B#16#0 is invalid. MODE Input BYTE I, Q, M, D, L or constant Job ID (coding complies with EN 50 170 Volume 2, PROFIBUS) Bit 0: reserved (value 0) Bit 1: reserved (value 0) Bit 2: = 1: UNFREEZE will be executed = 0: no meaning Bit 3: = 1: FREEZE will be executed = 0: no meaning Bit 4: = 1: UNSYNC will be executed = 0: no meaning Bit 5: = 1: SYNC will be executed = 0: no meaning Bit 6: reserved (value 0) Bit 7: reserved (value 0) Possible values: with exactly one ID per job: - B#16#04 (UNFREEZE) - B#16#08 (FREEZE) - B#16#10 (UNSYNC) - B#16#20 (SYNC) with more than one ID per job: RET_VAL Return INT I, Q, M, D, L - B#16#14 (UNSYNC, UNFREEZE) - B#16#18 (UNSYNC, FREEZE) - B#16#24 (SYNC, UNFREEZE) - B#16#28 (SYNC, FREEZE) If an error occurs while the instruction is being executed, the return value contains an error code. Make sure that you evaluate RET_VAL each time the block has been executed. BUSY Output BOOL I, Q, M, D, L BUSY=1: The SYNC/FREEZE job is not yet complete. 2614 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References You can find additional information on valid data types in "Overview of the valid data types (Page 1204)". RET_VAL parameter Note If you access DPV1 slaves, error information of these slaves can be forwarded from the DP master to the instruction. For a description of this error information, refer to STATUS[3], STATUS (Page 2568) parameter. Error code* (W#16#...) Explanation 0000 Job completed without error. 7000 First call with REQ=0. The job specified with LADDR, GROUP and MODE is not active; BUSY has the value 0. 7001 First call with REQ=1. The job specified with LADDR, GROUP and MODE was triggered; BUSY has the value 1. 7002 Intermediate call (REQ irrelevant). The activated SYNC/FREEZE job is still running; BUSY has the value 1. 8090 The module selected with LADDR is not a DP master. 8093 This instruction is not permitted for the module selected with LADDR (configuration or version of the DP master). 8094 GROUP parameter is incorrect 8095 MODE parameter is incorrect 80B0 The group selected with GROUP is not configured. 80B1 The group selected with GROUP is not assigned to this CPU. 80B2 The SYNC job specified with MODE is not permitted on the group selected with GROUP. 80B3 The FREEZE job specified with MODE is not permitted on the group selected with GROUP . 80C2 Temporary shortage of resources on the DP master: The DP master is currently processing the maximum number of jobs for a CPU. 80C3 This SYNC/UNSYNC job cannot be activated at present because only one SYNC/UNSYNC job can be triggered at a time. Check your user program. 80C4 This FREEZE/UNFREEZE job cannot be activated at present because only one FREEZE/UNFREEZE job can be triggered at a time. Check your user program. 80C5 Short circuit directly at DP interface 80C6 Job aborted due to I/O disconnection by CPU 80C7 Job aborted due to warm or cold restart on the DP master General error information See also: GET_ERR_ID: Get error ID locally (Page 1964) * The error codes can be displayed as integer or hexadecimal values in the program editor. For additional information on toggling display formats, refer to "See also". WinCC Basic V13.0 System Manual, 02/2014 2615 Programming the PLC 9.7 References DPNRM_DG: Read diagnostics data from a DP slave Description You use the "DPNRM_DG" instruction to read the current diagnostic data of a DP slave in the form specified in EN 50 170 Volume 2, PROFIBUS. Refer to the following table for the basic structure of the slave diagnostic data and to the manuals of the DP slaves for further information. Byte Meaning 0 Station status 1 1 Station status 2 2 Station status 3 3 Master station number 4 Vendor ID (high byte) 5 Vendor ID (low byte) 6 ... Additional slave-specific diagnostic information The data that has been read is entered in the target range indicated by RECORD following without error data transfer. You start the read process by assigning the value "1" to the REQ input parameter when the "DPNRM_DG" instruction is called. Functional description The reading process is executed asynchronously, in other words, it can extend over several calls. The output parameters RET_VAL and BUSY indicate the status of the job. See also: Meaning of the parameters REQ, RET_VAL and BUSY with asynchronous instructions (Page 1736). Parameters The following table shows the parameters of the "DPNRM_DG" instruction: Parameter Declaration Data type Memory area Description REQ Input BOOL I, Q, M, D, L or constant REQ = 1: Read request LADDR Input HW_DPSLAVE I, Q, M, D, L or constant Configured diagnostic address of the DP slave Note: Address must be specified in hexadecimal form, for example, diagnostic address 1022 means: LADDR:=W#16#3FE. RET_VAL 2616 Return DINT, INT, LREAL, REAL I, Q, M, D, L If an error occurs while the instruction is being executed, the return value contains an error code. If no error has occurred, the length of the data actually transferred is entered in RET_VAL . WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameter Declaration Data type Memory area Description RECORD Output VARIANT I, Q, M, D, L Destination area for the diagnostic data that were read. Only the BYTE data type is permitted. The minimum length of the data record to be read or the target range is 6. The maximum length of the data record to be sent is 240. Standard slaves can provide more than 240 bytes of diagnostic data up to a maximum of 244 bytes. In this case, the first 240 bytes are transferred to the target range and the overflow bit is set in the data. BUSY Output BOOL I, Q, M, D, L BUSY = 1: The reading process is not yet complete. You can find additional information on valid data types in "Overview of the valid data types (Page 1204)". You can find information on data type conversion in the different programming languages under "Auto-Hotspot". RECORD parameter The CPU evaluates the actual length of the read diagnostic data: If the length specified for RECORD is less than the number of data bytes supplied, the data is discarded and a corresponding error code is entered in RET_VAL. is greater than or equal to the number of data bytes supplied, the data is accepted in the destination area and the actual length is entered in RET_VAL as a positive value. Note You must ensure that the actual parameters of RECORD correspond in all calls belonging to a job. A job is uniquely identified by the LADDR input parameter. Standard slaves with more than 240 bytes of diagnostic data With standard slaves on which the number of standard diagnostic data is between 241 and 244 bytes, note the following points: If the length specified for RECORD is less than 240 bytes, the data is discarded and a corresponding error code is entered in RET_VAL. If the length specified for RECORD is greater than or equal to 240 bytes, the first 240 bytes of the standard diagnostic data is transferred to the target range and the overflow bit is set in the data. WinCC Basic V13.0 System Manual, 02/2014 2617 Programming the PLC 9.7 References RET_VAL parameter If an error occurs while the function is being executed, the return value contains an error code. If no errors have occurred during data transfer, RET_VAL contains the length of the data read in bytes as a positive number. Note The amount of data read in a DP slave depends on its diagnostics status. For the evaluation of the error information of the RET_VAL parameter, refer to the following table. Error code (W#16#...) Explanation Restriction 7000 First call with REQ = 0: No data transfer active; BUSY has the value "0". - 7001 First call with REQ = 1: Data transfer triggered; BUSY has the value "1". Distributed I/O 7002 Intermediate call (REQ irrelevant): Data transfer already active; BUSY has the value "1". Distributed I/O 8090 Address specified at parameter LADDR is invalid. - 8093 This instruction is not permitted for the module selected by means of LADDR and IOID. - 80A2 DP protocol error at layer 2 (for example, slave failure or bus problems) Distributed I/O For ET200S, data record cannot be read in DPV0 mode. 80A3 DP protocol error with user interface/user Distributed I/O 80A4 Communication on PBUS+ disrupted Distributed I/O 80B0 Instruction not possible for module type. - The module does not recognize the data record. Data record number 241 not permitted. With "WR_REC (Page 2560)", data records 0 and 1 are not permitted. 80B1 The length specified in parameter RECORD is incorrect. specified length < data record length 80B2 The configured slot is not assigned. - 80B3 Actual module type does not match specified module type - 80C0 There are no diagnostic data available. - 80C1 The data of the previous write job on the module for the same data record have not yet been processed by the module. - 80C2 The module is currently processing the maximum possible number of jobs for a CPU. - 80C3 The required resources (memory, etc.) are currently occupied. - 2618 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Error code (W#16#...) Explanation Restriction 80C4 Internal temporary error. Job could not be executed. - Repeat the job. If this error occurs often, check your installation for sources of electrical interference. 80C5 Distributed I/O not available. Distributed I/O 80C6 Data record transfer stopped due to priority class abort (restart or background) Distributed I/O General error information See also: GET_ERR_ID: Get error ID locally (Page 1964) - * The error codes can be displayed as integer or hexadecimal values in the program editor. For additional information on toggling display formats, refer to "See also". DP_TOPOL: Determine topology for DP master system Description You use the instruction to trigger the topology determination for a selected DP master system. Calling the instruction will address all diagnostics repeaters on a DP master system. Note The topology can only be determined for one DP master system at a time. Topology determination is the prerequisite for the detailed display of the error location if line errors occur. After configuration and after every change to the physical configuration of a DP master system, you must repeat the topology determination with "DP_TOPOL". Changes to the physical configuration are: Changes in line lengths Adding or removing stations or components with repeater function Changing station addresses If an error is reported by a diagnostics repeater, "DP_TOPOL" writes the DPR and DPRI outputs for the duration of one "DP_TOPOL pass. If errors are reported by multiple diagnostics repeaters of the selected DP master system, "DP_TOPOL" writes DPR and DPRI with information regarding the first diagnostics repeater reporting the error. You can read out the entire diagnostic information on the programming device or using the "DPNRM_DG (Page 2616)" instruction. If no diagnostics repeater reports an error, the DPR and DPRI outputs have the value NULL. If you want to repeat a topology determination after an error occurs, you must first reset "DP_TOPOL". This is done by calling "DP_TOPOL" with REQ=0 and R=1. Functional description "DP_TOPOL" works asynchronously, that is, its execution extends over multiple calls. You start determining the bus topology by calling "DP_TOPOL" with REQ=1 . If you want to cancel the process, call "DP_TOPOL" with R=1 . WinCC Basic V13.0 System Manual, 02/2014 2619 Programming the PLC 9.7 References The output parameters RET_VAL and BUSY indicate the status of the job. See also: Meaning of the parameters REQ, RET_VAL and BUSY with asynchronous instructions (Page 1736). Note Determining the topology may take several minutes. Identification of a job The input parameter DP_ID uniquely specifies a job. If you have called "DP_TOPOL" and you call this instruction again before the topology is redetermined, the manner in which the instruction reacts depends on whether the new call involves the same job: If the DP_ID parameter matches a job that has not yet been completed, then the call is interpreted as a follow-up call and the value W#16#7002 will be entered in RET_VAL. On the other hand, if another job is involved, the CPU rejects it. Parameters The following table shows the parameters of the "DP_TOPOL" instruction: Parameter Declaration Data type Memory area Description REQ Input BOOL I, Q, M, D, L or constant REQ=1: Trigger topology determination R Input BOOL I, Q, M, D, L or constant R=1: Cancel topology determination DP_ID Input HW_IOSYST EM I, Q, M, D, L or constant DP master system ID of those master systems for which the topology will be determined RET_VAL Return INT I, Q, M, D, L If an error occurs while the instruction is being executed, the return value contains an error code. BUSY Output BOOL I, Q, M, D, L BUSY=1: Topology determination is not yet complete. DPR Output BYTE I, Q, M, D, L PROFIBUS address of the diagnostics repeater reporting the error. DPRI Output BYTE I, Q, M, D, L Measuring segment diagnostics repeater reporting the error: Bit 0 = 1: Temporary faults on segment DP2 Bit 1 = 1: Permanent faults on segment DP2 Bit 4 = 1: Temporary faults on segment DP3 Bit 5 = 1: Permanent faults on segment DP3 For additional information on valid data types, refer to "Overview of the valid data types (Page 1204)". 2620 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameter RET_VAL When looking at the "real" error information (error codes W#16#8xyz) in the following table, we distinguish between two cases: Temporary errors (error codes W#16#80A2 to 80A4, 80C3, 80C5): It is possible to eliminate this type of error without user action; in other words, it is advisable to call "DP_TOPOL" again (multiple calls, if necessary). Example of a temporary error: Resources required are currently in use (W#16#80C3). Permanent errors (error codes W#16#8082, 80B0, 80B2): This type of error does not correct itself. A new call of "DP_TOPOL" is only advisable after you have eliminated the error. Example of a permanent error: The DP master/CPU does not support this service. (W#16#80B0). Error code* Explanation (W#16#...) 0000 Job completed without error. 7000 First call with REQ=0. Topology determination is not triggered. BUSY has the value "0". 7001 First call with REQ=1. The request to execute topology determination was sent. BUSY has the value "1". 7002 Intermediate call (REQ irrelevant): Topology determination is not yet complete. BUSY has the value "1". 7010 You have attempted to cancel topology identification. But there is no running job with the specified DP_ID. BUSY has the value "0". 7011 First call with R=1. The cancellation of the topology determination was triggered. BUSY has the value "1". 7012 Intermediate call: The cancellation of the topology determination is not yet complete. BUSY has the value "1". 7013 Final call: The topology determination was cancelled. BUSY has the value "0". 8082 No DP master system is configured with the specified DP_ID. 80A2 Error during topology determination; for more detailed information, refer to output parameters DPR and DPRI. 80A3 Error during topology determination: Monitoring time has elapsed (timeout). 80A4 Communication on PBUS+ disrupted 80B0 The DP master/CPU does not support this service. 80B2 Error during topology determination: No diagnostics repeater was found at the selected DP master system. 80C3 Resources required are currently in use. Possible cause: You have initiated a second topology determination (only one topology determination is permitted at one time). 80C5 The DP master system is currently not available. General error information See also: GET_ERR_ID: Get error ID locally (Page 1964) * The error codes can be displayed as integer or hexadecimal values in the program editor. For additional information on toggling display formats, refer to "See also". WinCC Basic V13.0 System Manual, 02/2014 2621 Programming the PLC 9.7 References ASi ASI_CTRL: Controlling ASi master behavior Description of ASI_CTRL Description Using the instruction "ASI_CTRL", you can control the behavior of the AS-i master from the user program of the PLC. The instruction processes the command protocol automatically. It also enables parameter assignment on SIMATIC AS-i masters and reading out information data. The functions and operation of the command interface are detailed in the manual for the AS-i master. Both centrally inserted AS-i masters and distributed AS-i masters via PROFIBUS DP are supported. Combinations with PROFINET IO (e.g. IE/PB Link PN IO) are also possible. The schematic diagram below shows the functions of the "ASI_CTRL" instruction: 6,0$7,&VWDWLRQ $6LPDVWHU 8VHUSURJUDP 6WDUW FRPPDQG $6,B&75/ Response data 2622 Status query Read data record STATUS Command interface 5HFHLYHEXIIHU Write data record $6LPDVWHUVWDUWDGGUHVV 6HQGEXIIHU Command no. / job data Start Command processing Start of processing at the REQ parameter. The program sends the required command to the AS-i master via the instruction "RDREC". The AS-i master processes the command. The current status of the AS-i master is stored in the input area of the binary data (logical start address). The instruction "ASI_CTRL" cyclically queries and evaluates the 4 status bits. Once command processing is complete, the command job is completed with "RDREC". Depending on the command, the data field of "RDREC" may contain the response data for the command or additional status information. WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Differences in the command call between IE/ AS-i Link and DP/AS-i Links There are significant differences in how a controller exchanges commands with an AS-i master. IE/AS-i Link (PROFINET) used the data record interface. The different commands are called with either "Write data record" ("WRREC" instruction) or "Read data record" ("RDREC" instruction) by various data record numbers. DP/AS-i Links (PROFIBUS) use the command interface. All commands are called by data record number 2 with "Write data record" ("WRREC" instruction) plus "Read data record" ("RDREC" instruction). The type of command is defined by the data content in the write job. Changes compared to the instruction "ASi_3422". The instruction "ASI_CTRL" is a revised version of the instruction "ASi_3422" (S7-300/400) and provides improved functionality and compatibility. The specific changes are as follows: For writing and reading diagnostic data records, the instructions "WR_REC (Page 2600)" and "RD_REC (Page 2596)" have been replaced by the instructions "RDREC (Page 2558)" and "WRREC (Page 2560)". Their function is identical; however, they support data transfer via PROFINET IO. The block type of the instruction has been changed from a function (FC) to a function block (FB). "ASI_CTRL" has an instance data block and is multi-instance-capable. The designation of the formal parameters of "ASI_CTRL" complies with the SIMATIC system blocks. There is no STARTUP input parameter. The definition of the STATUS parameter is based on the instructions "RDREC (Page 2558)" and "WRREC (Page 2560)". The status identifiers for the parameter DONE and the new parameter BUSY have also been adjusted. Operation of the "ASI_CTRL" instruction The instruction "ASI_CTRL" is an asynchronous function block; in other words, its processing extends over multiple calls. A job is started with REQ = TRUE. The job status is displayed via the BUSY output parameters and the two central bytes of the output parameter STATUS. The BUSY parameter is set during job processing. Upon the first call, STATUS is assigned the value 00700100H. Upon all subsequent calls for this job, it is assigned the value 00700200H. When the job is complete, the result is output at the parameters DONE or ERROR. - If no errors have occurred, DONE is set. For jobs with response data from the AS-i master, this data is provided in the specified receive buffer. In such cases, the STATUS parameter also displays the volume of data supplied in bytes. For jobs without response data, the value 00000000H is entered in STATUS. - If an error occurs during job processing, ERROR is set. The content of the receive buffer is invalid in such a case. An error code is entered in the STATUS parameter for a more detailed description of the error which has occurred. WinCC Basic V13.0 System Manual, 02/2014 2623 Programming the PLC 9.7 References Number of command calls If you use the instruction "ASI_CTRL" to send commands, you may not simultaneously send other commands to the same AS-i master with "RDREC (Page 2558)" or "WRREC (Page 2560)". This also applies to multiple calls of the instruction for the same AS-i master. The instruction "ASI_CTRL" cannot be run with interruptions. Calls therefore cannot be programmed in program priority classes which interrupt each other (for example with calls in OB 1 and in OB 35). Parameter The following table shows the parameters of the instruction "ASI_CTRL": Parameter Declaration Data type Memory area REQ Input BOOL I, Q, M, D, L, constant REQ = TRUE starts a new job unless a job is already in progress. No edge evaluation takes place. Description LADDR Input WORD I, Q, M, D, L, constant Start address of the AS-i master in the S7 address space (logical base address). The start address is defined in the hardware configuration when the master is configured. SD Input VARIANT I, Q, M, D, L Send buffer The parameter refers to a memory area in which the command is to be specified (see " ASi commands (Page 2625)"). Example: P#DB101.DBX 0.0 BYTE 223 RD Input VARIANT I, Q, M, D, L Receive buffer This buffer is only relevant for commands which deliver answer data. The parameter refers to a memory area in which a command response is stored (see "ASi commands (Page 2625)"). Example: P#DB102.DBX 224.0 BYTE 221 DONE Output BOOL Q, M, D, L DONE = TRUE: Job completed without errors. BUSY Output BOOL Q, M, D, L BUSY = TRUE: Job in progress. ERROR Output BOOL Q, M, D, L ERROR = TRUE: Job aborted with error. STATUS Output DWORD M, D Job status / error code See the "STATUS parameter" description. For additional information on valid data types, refer to "Overview of the valid data types (Page 1204)". Note Parameters LADDR, SD, and RD The parameters LADDR, SD, and RD must not be changed in any block cycle when a job is in progress: they must remain constant. 2624 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References STATUS parameter The following table shows the possible STATUS displays dependent upon DONE and ERROR. DONE ERROR STATUS Meaning 0 0 00700000H First call with REQ = FALSE; no active job. 0 0 00700100H First call with REQ = TRUE; job has started. 0 0 00700200H Subsequent call (REQ irrelevant); job is still in progress. 1 0 00000000H Job completed without errors. No response data. 1 0 0000xx00H Job completed without errors. Number of xx bytes of response data. 0 1 C0818400H Data type of formal operand RD invalid. 0 1 C0818500H Error in communication with AS-i master (incorrect address configured at the LADDR parameter). 0 1 C0838100H Incorrect AS-i slave address. 0 1 C0838200H AS-i slave is not enabled (not in LAS). 0 1 C0838300H Error at the AS interface (the SD parameter may have been set too small). 0 1 C0838400H The command is not valid with the current AS-i master status. 0 1 C0838500H There is no AS-i slave with the address "0". 0 1 C0838600H The AS-i slave has invalid configuration data (I/O or ID codes). 0 1 C083A100H The AS-i slave addressed has not been found at the AS interface. 0 1 C083A200H There is no AS-i slave with the address "0". 0 1 C083A300H There is already an AS-i slave with the new address at the AS interface. 0 1 C083A400H The AS-i slave address cannot be deleted. 0 1 C083A500H The AS-i slave address cannot be set. 0 1 C083A600H The AS-i slave address cannot be permanently saved. 0 1 C083A700H Error during reading of the extended ID1 code. 0 1 C083A800H The target address is not plausible (e.g. a B slave address has been used for a standard slave). 0 1 C083B100H A length error has occurred during string transfer. 0 1 C083B200H A protocol error has occurred during string transfer. 0 1 C083F800H Unknown job number or job parameter. 0 1 C083F900H The AS-i master has detected an EEPROM error. ASi commands Description The command interface allows the controller and AS-i master to exchange parameter assignment and information data. These commands WinCC Basic V13.0 System Manual, 02/2014 2625 Programming the PLC 9.7 References provide the complete functionality of the M4 master profile of the AS-i master specifications. enable the AS-i master to be completely configured from the controller. Note AS-i commands supported Please see the manual of the relevant AS-i master for the AS-i commands supported and a detailed description. General structure of the send buffer The general structure of the send buffer for commands and job data is set out in the table below. The area for the command number must always be filled. The number of bytes for the job data can be found in the description of the command (see AS-i master documentation). "q" is the start address of the send buffer. Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0 Meaning q+0 Command number q+1 Job data q+2 Job data q + ... Job data General structure of the receive buffer The general structure of the receive buffer for the command response data is set out in the table below. The number of bytes for the response data depends on the command. Some commands do not return response data, and therefore only require the definition of a virtual receive buffer which is not filled with data. "n" is the start address of the receive buffer. Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0 Meaning 2626 n+0 Command number (echo) n+1 Response data n+2 Response data n + ... Response data WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References CAUTION Memory areas can be overwritten If the receive buffer of the "ASI_CTRL" instruction is too short, neighboring memory areas may be overwritten. The length specified in the ANY pointer of the RD parameter when the instruction "ASI_CTRL" is called is irrelevant. The required length for the receive buffer can be found in the description of the command. The following applies for command numbers 39H, 41H, 42H, 43H and 44H: The receive buffer must be 221 bytes long (bytes 0 to 220), even if the command returns less data. Depending on the command, the highest bytes in the receive buffer may be overwritten with zero values by the AS-i master. AS-i commands A selection of possible AS-i commands is set out in the table below. Name Parameter Return Coding Set_permanent_parameter (Set_Permanent_Parameter) Slave address, parameter Get_permanent_parameter (Get_Permanent_Parameter) Slave address Parameter 01 H Write_parameter (Write_Parameter) Slave address, parameter Parameter echo 02 H Read_parameter (Read_Parameter) Slave address Parameter value 03 H 00 H Store_actual_parameters (Store_Actual_Parameters) 04 H Set_configuration_data Slave address, configuration Get_configuration_data Slave address 25 H set configuration data Store_actual_configuration (Store_Actual_Configuration) 26 H 07 H Get_actual_configuration Slave address Configure_LPS LPS 29 H Set_offline_mode Mode 0AH Select_auto-program Mode 0B H Set_mode Mode 0C H Change_AS-iSlave_address (Change_AS-iSlave_Address) Address1, Address2 0D H Get_AS-iSlave_status Slave address Read_lists_and_flags WinCC Basic V13.0 System Manual, 02/2014 Actual configuration data 28 H Error record of the AS-i slave 0F H LDS, LAS, LPS, flags 30 H 2627 Programming the PLC 9.7 References Name Parameter Get_overall_configuration Return Coding Actual configuration data, current parameters, LAS, flags 39 H Set_overall_configuration Overall configuration 3A H Write_parameter_list Parameter list 3C H Read_parameter_echo_list Write_CTT2_request Slave address CTT2 string Read_version_identifier Parameter echo list 33 H CTT2 string 44 H Version string 14 H Read_AS-i_slave Slave address ID code 17 H Read_AS-i_slave_extended_ID1 Slave address Extended ID1 code 37 H Write_AS-iSlave_extended_ID1 Extended ID1 code Read_AS-iSlave_extended_ID2 Slave address Extended ID2 code 38 H Read_AS-iSlave_IO Slave address I/O configuration 18 H LPF 3E H Read_I/O_error_list Write_AS-i-slave_parameter_string Slave address, parameter string Read_AS-iSlave_parameter_string Slave address 3F H 40 H Parameter string 41 H Read_AS-iSlave_ID_string Slave address ID string 42 H Read_AS-iSlave_diagnostic_string Slave address Diagnostic string 43 H Read_AS-i_line_error_counter 4A H Read_and_clear_AS-i_line_error_counter 4B H Read_AS-iSlave_error_counter Slave address 4C H Read_and_clear_AS-iSlave_error_counter Slave address 4D H Additional command for DP/ AS-i F-Link: AS-i_status/diag_of_F_slaves Status/diagnostics of all AS-i safe slaves 51 H Note Re-initializing the AS-i master command interface Another command which is not mentioned in the table is command 77 H. This call re-initializes the command interface of the AS-i master. Any command which the AS-i master specified is currently processing will be terminated. As of version V2.1.20 of DP/AS-i LINK Advanced, command 0E H is also available. This call enables you to release and block the ground fault monitoring function for a line. 2628 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References 9.7.3.5 PROFIenergy Description of PROFIenergy PROFIenergy PROFIenergy is a manufacturer- and device-neutral profile for energy management with PROFINET. PROFIenergy enables central, coordinated device shutdown to reduce electricity consumption during breaks in production and unplanned interruptions. 3DXVH (QHUJ\FRQVXPSWLRQ 3DXVH 7LPH The PROFINET devices/power modules are switched off via special commands in the user program of the PROFINET IO controller. No additional hardware is required. The PROFINET devices interpret the PROFIenergy commands directly. PROFIenergy controller (PE controller) The PE controller is a PLC which enables/disables the idle state in lower-level devices. Individual production components and entire production lines are switched off and reactivated from the user program. Commands (e.g. "Start_Pause" and "End_Pause") are sent to the lowerlevel device using corresponding instructions (function blocks). The commands are sent via the PROFINET communication protocol. PROFIenergy entity (PE entity) The PE entity receives the PROFIenergy commands of the PE controller and executes these accordingly (for example, by returning a measured value or activating an energy saving mode). Implementation of the PE entity in a PROFIenergy-capable device is device- and manufacturerspecific. The PE entity can, for example, be executed: WinCC Basic V13.0 System Manual, 02/2014 2629 Programming the PLC 9.7 References Within the proxy of a submodule: The PE commands are valid for the addressed submodule and any existing lower-level submodules. Within the proxy of a module: The PE commands are valid for different submodules within the module. 3(FRQWUROOHU 352),1(7,2GHYLFH 3(FRQWUROOHU ,QWHUIDFHPRGXOH ,0 DV3(HQWLW\ 6XEPRGXOHDV3(HQWLW\ 3(FRPPDQG 352),1(7,2GHYLFH 3(FRPPDQG For networked submodules without a proxy function: The PE commands in this case are only valid for the respective submodule. PROFIenergy instructions Instructions for IO controller - The "PE_START_END (Page 2631)" instruction represents the simplest way to activate or deactivate the idle state of the PROFINET devices (PROFIenergy commands "Start_Pause" and "End_Pause"). This is done using a positive and negative signal edge in the instruction. - The "PE_CMD (Page 2635)" instruction allows you to transmit all PROFIenergy commands, including "Start_Pause" and "End_Pause". With other commands, you can query the current status of the PROFINET devices or the behavior during breaks, for example. - The instruction "PE_DS3_Write_ET200S (Page 2641)" is used to define the switching characteristic of up to 8 slots of ET 200S. The instruction is not a PROFIenergy instruction; however, it supplements the PROFIenergy functions for an ET 200S. Instruction for iDevices The "PE_I_DEV (Page 2665)" instruction allows you to implement PROFIenergy on iDevices as well. The instruction receives PROFIenergy commands on the iDevice and forwards these to the user program for processing. After processing the command, the user program calls the "PE_I_DEV (Page 2665)" instruction again in order to send the acknowledgement to the IO controller. For these replies, each command offers you a corresponding auxiliary block that supplies the response data to the instruction "PE_I_DEV (Page 2665)". 2630 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References PROFIenergy commands (PE commands) The PE controller transmits PE commands to the PE entity. The PE command can be either a control command to switch a PE entity to the energy-saving mode, or a command to read a status or measured value: PI commands for control PROFIenergy supports two control commands that can be executed using either the "PE_Start_End (Page 2631)" instruction or the "PE_CMD (Page 2635)" instruction: - Start_Pause: Starting a suitable energy-saving mode (PE Energy-saving mode) - End_Pause: Exiting the energy-saving mode (switch to PE_ready_to_operate mode) PI commands for reading a status or measured value Certain condition information can be read by the control system using the following status commands with the instruction "PE_CMD (Page 2635)": - PE_Identify: Read out which PE commands are supported by the PE entity. - PEM_Status: Read out the currently active mode of a PE entity (e. g. PE_ready_to_operate). - Query_Modes: Output an overview of all supported energy-saving modes, including the time and energy information - Query_Measurement: Output the measured values of a PE entity Example applications Examples for use of PROFIenergy instructions can be found in the Industry Online Support in the entry "PROFIenergy - Saving Energy with SIMATIC S7 (http:// support.automation.siemens.com/WW/view/en/41986454)". See also Service and Support (http://support.automation.siemens.com/) IO controller PE_START_END: Start and exit energy-saving mode Description The instruction "PE_START_END" is used to start and exit the energy-saving mode of a specified PE entity (e.g. ET 200S). The instruction "PE_START_END" is used in the PE controller, preferably when only field devices from which energy data does not need to be read out are connected to the corresponding PE devices. Alternatively, the instruction "PE_CMD (Page 2635)" can be used to read energy data. WinCC Basic V13.0 System Manual, 02/2014 2631 Programming the PLC 9.7 References The energy-saving modes are configured in the user program of the PE controller. On completion of the "PE_START_END" instruction, the PE entity reports its current energy-saving mode and outputs this data at parameter PE_MODE_ID. Write and read jobs of the "PE_START_END" instruction. The instruction "PE_START_END" sends a PROFIenergy command internally as a write job to the PE entity using "WRREC (Page 2560)". "PE_START_END" then waits for acknowledgment from the PE entity. The acknowledgment data record is read with the instruction "RDREC (Page 2558)" every 100 milliseconds. Until acknowledgment is received from the PE entity, the function repeats the read job for 10 seconds at intervals of 100 milliseconds. The response data of the PE entity is also read with the instruction "RDREC (Page 2558)". Below is a flowchart of the write and read jobs: 352),HQHUJ\FRQWUROOHU 352),HQHUJ\GHYLFH 3(B67$57B(1'3(B&0' 3(B,B'(9 5(4 :ULWHMRE 1(: :ULWHUHVSRQVH SRVLWLYH 5HDGMRE PV 5HDGUHVSRQVH QHJDWLYHUHVRXUFHDVVLJQHGEXV\ V 5HDGMRE V 5HDGUHVSRQVH SRVLWLYH 7LPH 2632 7LPH WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameter The following table shows the parameters of the instruction "PE_START_END": Parameter Declaration Data type Memory area Description START Input BOOL I, Q, M, D, L or constant Transmitting the PE command "Start_Pause" to the PE entity with the address set at parameter ID. END Input BOOL I, Q, M, D, L or constant Transmitting the PE command "End_Pause" to the PE entity with the address set at parameter ID. ID Input HW_ SUBMODULE I, Q, M, D, L or constant Address of the PE entity TIME I, Q, M, D, L, P or constant PAUSE_TIME Input Use the hardware ID of the head module for a PROFINET IO device. Refer to the system constants of the assigned IO controller for the hardware ID. The name of the head module is composed of the name of the IO device and the suffix [Head] (example: "IO_Device_1[Head]"). Planned pause duration. Range: T#1MS to T#24D20H31M23S647MS Start value: T#0MS VALID Output BOOL I, Q, M, D, L PE command successfully sent. BUSY Output BOOL I, Q, M, D, L PE command still being processed. ERROR Output BOOL I, Q, M, D, L Error occurred during processing. The error message is output at the STATUS parameter. STATUS Output DWORD I, Q, M, D, L, P Block status / error number (see "STATUS parameter") PE_MODE_ID Output BYTE I, Q, M, D, L, P Identification number of energy-saving mode (energy-saving level for the duration of the pause). For additional information on valid data types, refer to "Overview of the valid data types (Page 1204)". PAUSE_TIME parameter The parameter PAUSE_TIME is used to set the default duration of the energy-saving period at the PE entity. The PE entity checks whether the pause period is of sufficient length and whether it can be implemented. The minimum pause duration (Time_min_Pause) must be WinCC Basic V13.0 System Manual, 02/2014 2633 Programming the PLC 9.7 References greater than the sum of the times the device needs to switch to energy-saving mode (Time_to_Pause) and to switch back to operating mode (Time_to_Operate). 3(BUHDG\B WRBRSHUDWH 3(BHQHUJ\B VDYLQJBPRGH 6WDUWB3DXVH 7LPHBWRB3DXVH (QGB3DXVH 7LPHBPLQBOHQJWKBRIBVWD\ 7LPHBWRB2SHUDWH W 7LPHBPLQB3DXVH ET 200S checks whether the scheduled pause duration is greater than or equal to the minimum pause duration (PM-E_Pause_Min) saved on the ET 200S. This is fixed at 10 seconds. If a shorter pause is used, the power modules (PM-E) of the ET 200S will remain on. The module does not switch back on automatically at the end of the pause; it remains in OFF mode until the "END" command is sent. This prevents uncoordinated switch-on, which can cause undesired peak loads. STATUS parameter Error information is output at the STATUS output parameter. If it is interpreted as ARRAY[1...4] of BYTE, the error information has the following structure: Field element Name Meaning STATUS[1] Function_Num Cause of the error B#16#00: No error B#16#DE: Error during reading of data record B#16#DF: Error during writing of data record B#16#C0: Error message from the instruction or from the communication instructions "RDREC (Page 2558)" and "WRREC (Page 2560)" used internally. STATUS[2] Error_Decode Location of the error ID 80: DPV1 error as defined in IEC 61158-6 or application-specific FE: DP/PNIO profiles - PROFIenergy-specific error 2634 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Field element Name Meaning STATUS[3] Error_Code_1 Error ID When Error_Decode = 80: - 80: Simultaneous positive edge at the input parameters START and END. - 81: Length conflict at the CMD_PARAM and CMD_PARAM_LEN parameters. - 82-8F: Other error messages (reserved) When Error_Decode = FE: STATUS[4] Error_Code_2 - 01: "Service Request ID" invalid - 02: Incorrect "Request_Reference" - 03: "Modifier" invalid - 04: "Data Structure Identifier RQ" invalid - 05: "Data Structure Identifier RS" invalid - 06: "PE energy-saving modes" are not supported - 07: "Response" is too long (maximum transmissible length exceeded) - 08: "Count" invalid - 50: No suitable "energy mode" is available. - 51: Time value specified is not supported. - 52: "PE_Mode_ID" invalid Manufacturer-specific error ID extension Note Error messages of the instructions RDREC and WRREC The instruction "PE_START_END" uses the instructions "WRREC (Page 2560)" and "RDREC (Page 2558)" for communication. Error messages for these instructions are output in the field elements STATUS[1] to STATUS[4]. Please see the description of the corresponding STATUS (Page 2568) parameter for an explanation of the error codes of the "WRREC (Page 2560)" and "RDREC (Page 2558)" instructions. See also Description of PROFIenergy (Page 2629) PE_CMD: Start and exit energy-saving mode / Read out status information Description The instruction "PE_CMD" is used in the PE controller to start or terminate a pause in the energy-saving mode in the PE entity. Additional information and energy measurements can also be read out from a PE entity using "PE_CMD". The instruction is best used with PE controllers to which assigned PE devices are connected from which energy measurements are to be read out. If this is not the case, the instruction "PE_START_END (Page 2631)" can also be used to start and end the pauses. WinCC Basic V13.0 System Manual, 02/2014 2635 Programming the PLC 9.7 References Transfer of the PROFIenergy commands (PE commands) The instruction "PE_CMD" transfers a PROFIenergy command to a PE entity. The instruction can also be used if additional commands are to be added to the PROFIenergy profile in future. The commands which can be used with the current PROFIenergy profile are listed in the description of the CMD and CMD_MODIFIER parameters (see the "CMD and CMD_MODIFIER parameters" table). The individual PE commands which are transferred to the PE entity using the instruction are assigned defined "Service_Request_IDs". The Service_Request_IDs 01 to 05 and 16 are assigned at the CMD parameter. The two PE commands 04 (Query_Modes) and 16 (Query_Measurement) are defined in more detail with the CMD_MODIFIER parameter. Additional values are transferred at the CMD_PARA parameter for individual PE commands (see the description of the individual PE commands). The parameter CMD_PARA_LEN defines the length of the data at the parameter CMD_PARA. The commands are transferred without plausibility test. The response data of the PE entity is saved to the RESPONSE_DATA data area that is addressed by VARIANT pointer (for information about the response frame contents, refer to the description of the respective PE command). Write and read jobs of the "PE_CMD" instruction. The instruction "PE_CMD" uses "WRREC (Page 2560)" internally to transmit a PROFIenergy command as a write job to the PE entity. "PE_CMD" then waits for the acknowledgment from the PE entity. The acknowledgment data record is read with the instruction "RDREC (Page 2558)" every 100 milliseconds. Until acknowledgment is received from the PE entity, the function repeats the read job for 10 seconds at intervals of 100 milliseconds. The response data of the PE entity is also read with the instruction "RDREC (Page 2558)". Below is a flowchart of the write and read jobs: 2636 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References 352),HQHUJ\FRQWUROOHU 352),HQHUJ\GHYLFH 3(B67$57B(1'3(B&0' 3(B,B'(9 5(4 :ULWHMRE 1(: :ULWHUHVSRQVH SRVLWLYH 5HDGMRE PV 5HDGUHVSRQVH QHJDWLYHUHVRXUFHDVVLJQHGEXV\ V 5HDGMRE V 5HDGUHVSRQVH SRVLWLYH 7LPH 7LPH Parameter The following table shows the parameters of the instruction "PE_CMD": Parameter Declaration Data type Memory area Description REQ Input BOOL I, Q, M, D, L or constant Starts transferring the PE command upon a positive edge. ID Input HW_ SUBMODULE I, Q, M, D, L or constant Address of the PE entity WinCC Basic V13.0 System Manual, 02/2014 Use the hardware ID of the head module for a PROFINET IO device. Refer to the system constants of the assigned IO controller for the hardware ID. The name of the head module is composed of the name of the IO device and the suffix [Head] (example: "IO_Device_1[Head]"). 2637 Programming the PLC 9.7 References Parameter Declaration Data type Memory area Description CMD Input BYTE I, Q, M, D, L, P or constant Service-Request-ID of the PROFIenergy command in accordance with the PROFIenergy profile (see "CMD and CMD_MODIFIER parameters"). Further service request IDs are possible following extensions of the PROFIenergy profile. CMD_MODIFIER Input BYTE I, Q, M, D, L, P or constant PROFIenergy sub-command (only when CMD=3 or CMD=16, see "CMD and CMD_MODIFIER parameters") Further sub-commands are possible following extensions of the PROFIenergy profile. CMD_PARA Input VARIANT I, Q, M, D, L Parameters for the PE commands: Get mode: PE_mode_ID Get measurement values: List of Measurement_Ids The complete Service Data Request is entered. CMD_PARA_LEN Input INT I, Q, M, D, L, P or constant The actual length of the command parameters (<= length defined in CMD_PARA; is verified by the instruction). RESPONSE_DATA InOut VARIANT I, Q, M, D, L PROFIenergy information May be complete response frame including block header, depending on the command. Note: If the buffer is too small, only the number of bytes which is specified in the VARIANT pointer will be entered. VALID Output BOOL I, Q, M, D, L Command successfully sent. BUSY Output BOOL I, Q, M, D, L Command still being processed. ERROR Output BOOL I, Q, M, D, L Error occurred during processing. STATUS Output DWORD I, Q, M, D, L Block status / error number (see "STATUS parameter"): For additional information on valid data types, refer to "Overview of the valid data types (Page 1204)". Parameters CMD and CMD_MODIFIER CMD CMD_ MODIFIER PROFIenergy command Description 01 0 Start_Pause (Page 2655) Start energy-saving mode or switch to a different energysaving mode. 02 0 End_Pause (Page 2655) End energy-saving mode. 03 1 Query_Modes - List of energysaving modes (Page 2656) Output the energy-saving modes supported. 2638 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References CMD CMD_ MODIFIER PROFIenergy command Description 2 Query_Modes - Get mode (Page 2657) Output attributes of the energy-saving mode currently enabled. 04 0 PEM_Status (Page 2659) Query status of energy-saving mode. 05 0 PE_Identify (Page 2660) Read out the number and description of PE commands supported. 16 1 Query_Measurement Get_Measurement_List (Page 2661) List of measured values supported by the PE entity. 2 Query_Measurement Get_Measurement_Values (Page 2663) Output the measured values of the PE entity. STATUS parameter Error information is output at the STATUS output parameter. If it is interpreted as ARRAY[1...4] of BYTE, the error information has the following structure: Field element Name Meaning STATUS[1] Function_Num Cause of the error B#16#00: No error B#16#DE: Error during reading of data record B#16#DF: Error during writing of data record B#16#C0: Error message from the internal communication instructions "RDREC (Page 2558)" and "WRREC (Page 2560)". STATUS[2] Error_Decode Location of the error ID 80: DPV1 error as defined in IEC 61158-6 or application-specific FE: DP/PNIO profiles - PROFIenergy-specific error WinCC Basic V13.0 System Manual, 02/2014 2639 Programming the PLC 9.7 References Field element Name Meaning STATUS[3] Error_Code_1 Error ID When Error_Decode = 80: - 81: Length conflict at the CMD_PARA and CMD_PARA_LEN parameters, or maximum data record length (4095 bytes) exceeded. - 82-8F: Other error messages (reserved) When Error_Decode = FE: STATUS[4] Error_Code_2 - 01: "Service Request ID" invalid - 02: Incorrect "Request_Reference" - 03: "Modifier" invalid - 04: "Data Structure Identifier RQ" invalid - 05: "Data Structure Identifier RS" invalid - 06: "PE energy-saving modes" are not supported - 07: "Response" is too long (maximum transmissible length exceeded) - 08: "Count" invalid - 50: No suitable energy-saving mode (energy mode) is available. - 51: Time value specified is not supported. - 52: "PE_Mode_ID" invalid Manufacturer-specific error ID extension Note Error messages of the instructions RDREC and WRREC The instruction "PE_CMD" uses the instructions "WRREC (Page 2560)" and "RDREC (Page 2558)" for communication. Error messages for these instructions are output in the field elements STATUS[1] to STATUS[4]. Please see the description of the corresponding STATUS (Page 2568) parameter for an explanation of the error codes of the "WRREC (Page 2560)" and "RDREC (Page 2558)" instructions. See also Description of PROFIenergy (Page 2629) 2640 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References PE_DS3_Write_ET200S: Set power module switching behavior Description The instruction "PE_DS3_Write_ET200S" sends basic settings for power module switching behavior to the ET 200S. The switching behavior of up to 8 slots in the ET 200S (e.g. for power modules) can be defined with the instruction "PE_DS3_Write_ET200S". Note This instruction is not part of the PROIenergy profile but instead supplements SIMATICspecific functions. Parameter The following table shows the parameters of the instruction "PE_DS3_Write_ET200S": Parameter Declaration Data type Memory area Description ENABLE Input BOOL I, Q, M, D, L or constant A positive edge triggers the transfer of the data record. The data record must be transferred again after voltage OFF/ON. ID Input HW_SUBMODU LE I, Q, M, D, L or constant Address of the ET 200S The address may be taken from the hardware configuration. SLOT_NO_X Input INT I, Q, M, D, L, P or constant Slot number of switchable power module X. FUNC_X Input INT I, Q, M, D, L, P or constant Function of the module in this slot. Use the parameter FUNC_X to define the switching behavior of the PM-E (power module of the ET 200S): FALSE: - With "PAUSE_START": -No effect on PM-E -PM-E remains on - With "PAUSE_STOP": -Switches PM_E back on TRUE: - With "PAUSE_START": -Switches PM_E off - With "PAUSE_STOP": -Switches PM-E back on BUSY Output BOOL I, Q, M, D, L Transfer not yet complete. DONE Output BOOL I, Q, M, D, L Transfer completed without errors. ERROR Output BOOL I, Q, M, D, L Transfer completed with error. STATUS Output DWORD I, Q, M, D, L, P Error number (see STATUS parameter of the instruction "PE_Start_End (Page 2631)") WinCC Basic V13.0 System Manual, 02/2014 2641 Programming the PLC 9.7 References For additional information on valid data types, refer to "Overview of the valid data types (Page 1204)". See also Description of PROFIenergy (Page 2629) PE_WOL: Starting and stopping energy-saving mode via WakeOnLan Description PE_WOL Description The "PE_WOL" instruction sends the PROFIenergy commands "Start_Pause" and "End_Pause" to multiple PROFIenergy-enabled devices in the PROFINET I/O systems. Multiple PE devices can be coordinated via the instruction provided that the PE devices support the "Wake on LAN" function over a UDP connection. The "PE_WOL" instruction can only be executed on a CPU with and integrated Ethernet interface. This CPU should be able to load blocks with a size of about 400 KB. You cannot use the block with PROFINET I/O systems that are connected via an Ethernet CP. The instruction "PE_WOL" is executed asynchronously. Definition: Wake on LAN The Wake on LAN function allows data processing equipment to resume working from a state near total shutdown when a special Ethernet packet is received. For this procedure to work, the data processing equipment must have a network controller that is capable of receiving such a packet. This packet (Magic PacketTM) has a special format. It contains the MAC address of the network adapter 15 times. Selection of devices The devices are selected using the user data block at the parameter PENERGY (Type: "PE_PLUS"). The user DB represents the database for processing multiple devices. Prior to initialization of "PE_WOL", you must store at least the following information in the user DB: ID of the PROFINET I/O system Data of the connection which is used for "Wake On LAN". 2642 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Port number which is used for "Wake On LAN". For each device - Pause time (PauseTime) - Switching of the device to the PE_SLEEP_MODE (EnableSleep) You initialize the "PE_WOL" instruction with the COM_RST parameter. The jobs stored in the user DB are processed one after the other after initialization. The graphic below illustrates how the PE command "Start_Pause" is transmitted to several devices: 8VHUGDWDEORFN ,QVWDQFH'% Diag. addr. Start bit End bit 8081 8082 1 0 0 0 8081 8083 8048 ... 1 1 ... 0 0 ... 8048 3(B:2/ Diag. Adr. 8083 (1) Step 1: The bit "CmdStartPause" of the devices to be shut down is set to "1" by the user. (2) Step 2: The diagnostic addresses of the devices to be shut down (CmdStartPause = "1") are linked to the queue. (3) Step 3: The bit "CmdStartPause" is reset automatically once the jobs have been linked. (4) Step 4: The instruction "PE_WOL" processes the jobs as soon as they are linked. A PROFIenergy command "CmdStartPause" or "CmdEndPause" can be sent for all recognized devices in the PROFINET IO system via the START and END parameters. The status of the job processing as well as possible errors during processing are output by the STATUS parameter. Operation of the instruction using the user DB The operation of the instruction "PE_WOL" can only take place via the user DB. A basic procedure applies in this case: 1. Selection of the command to be executed for a device: - START_PAUSE ("CmdStartPause" in user DB) - ENDE_PAUSE ("CmdEndPause" in user DB) - UPDATE_STATUS ("CmdUpdateStatus" in user DB) 2. Setting the bit for updating ("Update" in the header of the user DB) At least one CPU cycle should pass with an "Update" = False between two updates; otherwise, edge detection cannot be guaranteed. WinCC Basic V13.0 System Manual, 02/2014 2643 Programming the PLC 9.7 References Prioritizing the PE commands The graphic below shows the chronological sequence of three possible commands. CmdStartPause CmdEndPause CmdUpdateStatus Update These are processed one after the other, regardless of whether the previous command call was successful or completed with an error. Only one command is executed if you set two commands, such as "CmdEndPause" and "CmdUpdateStatus" simultaneously. A prioritization is present within the block: The command "CmdStartPause" has the highest priority and is therefore always executed if selected. The command "CmdEndPause" has the second highest priority. The command "CmdUpdateStatus" has the lowest priority. If all three commands are set at the same time, the commands that are not executed remain preselected. In this case, the next rising edge executes the next command. Parameters The following table shows the parameters of the "PE_WOL" instruction: Parameter Declaration Data type Memory area Description COM_RST (Page 2645) Input BOOL I, Q, M, D, L Resets the block and performs a re-initialization. As long as True is set here, the initialization is started but not yet fully completed. Only the falling edge continues the initialization and switches to the normal operating mode after initialization. START (Page 2646) Input BOOL I, Q, M, D, L A rising edge performs a "CmdStartPause" PROFIenergy command for all detected devices that support this function. END (Page 2647) Input BOOL I, Q, M, D, L A rising edge performs a "CmdEndPause" PROFIenergy command for all detected devices that support this function. 2644 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameter Declaration Data type Memory area Description PENERGY (Page 2647) InOut PE_PLUS D Pointer to the user DB that contains the database for processing multiple devices. STATUS (Page 2651) Output DWORD I, Q, M, D, L Status/error number for the current status of the instruction (see "STATUS parameter"). For additional information on valid data types, refer to "Overview of the valid data types (Page 1204)". Parameter COM_RST Sequence of the initialization routine You start the initialization of the "PE_WOL" instruction with the COM_RST parameter. The following flow diagram shows the initialization routine. START Resetting the job queue Clean Queue Config Devices No. of Devices >0 Reading the configured devices of the PROFINET I/O system Yes Dev. Diag. No Order ID Determining the diagnostic addresses Reading the OrderID User DB END (Error) WinCC Basic V13.0 System Manual, 02/2014 Connection setup Setup of the WoL connection PE_Identify Identification of the supported PE commands for each device END (Initialized) 2645 Programming the PLC 9.7 References Parameter START Sequence of the CmdStartPause command The flow diagram shows the internally used functions and interaction with a device when executing the CmdStartPause command. 8VHU'% &RQWUROOHU 3(B:2/ 'HYLFH 67$57 /LVWRIGHYLFHVZLWK 'LDJ,' 3DXVHB7LPH :R/ 6WDUWB3DXVHB%LW $GGLWLRQDOLQIRUPDWLRQ LQWKH'% 7LPHBWRBRSHUDWH 7LPHBPLQB3DXVH 3(B0RGHB,' :DNHB8SB0HWKRG :DNHB8SB'DWDB/HQJW :DNHB8SB'DWD (QDEOH6OHHS <HV 1R 6OHHSPRGH VHOHFWHG" <HV 1R 'HYLFHLV SUHSDULQJ UHVSRQVH 5HVSRQVH 7LPHBWRBRSHUDWH 7LPHBPLQB3DXVH :DNHB8SB0HWKRG %DFNXSUHVSRQVH 3DXVHB7LPH ! 7LPHBPLQB 3DXVH ,QIRBVOHHSBPRGH <HV 6WDUWBVOHHSBPRGH %DFNXSUHVSRQVH 'HYLFHLQ 3(B6/((3B02'( 1R 6WDUWB3DXVH %DFNXSUHVSRQVH 4XHU\6WDWXV 'HYLFHLQDQ (1(5*<B6$9,1*B 02'( 3(0B6WDWXV 5HVSRQVH 'HYLFHLQDQ (1(5*<B6$9,1*B 02'( (1' 2646 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameter END Sequence of the CmdEndPause command The flow diagram shows the internally used functions and interaction with a device when executing the CmdEndPause command. 8VHU'% 'HYLFH &RQWUROOHU 3(B:2/ 67$57 /LVWRIGHYLFHVZLWK 'LDJ,' 3DXVHB7LPH :R/ 6WDUWB3DXVHB%LW 3(B0RGH 6OHHS0RGH <HV 0DJLF3DFNHW YLD7&20 'HIDXOW3RUW 1R (QGB3DXVH $GGLWLRQDOLQIRUPDWLRQ LQWKH'% (QGB3DXVH %DFNXSUHVSRQVH 7LPHBWRBRSHUDWH 7LPHBPLQB3DXVH 3(B0RGHB,' :DNHB8SB0HWKRG :DNHB8SB'DWDB/HQJW :DNHB8SB'DWD 'HYLFHLQ 6OHHSBPRGH :DLW772 3(0B6WDWXV 'HYLFHLQ (QHUJ\BVDYLQJBPRGH B[ 'HYLFHLQ 5HDG\BWRBRSHUDWHBP RGH %DFNXSUHVSRQVH (1' PENERGY parameter Data block at the PENERGY parameter The user DB for the "PE_WOL" PROFIenergy instruction represents a data base for processing multiple devices. The data block is usually divided into two parts. These are: WinCC Basic V13.0 System Manual, 02/2014 2647 Programming the PLC 9.7 References Header 110 bytes Device section for a maximum of 256 devices each with 100 bytes (Device). These include: - Device-specific data (Device) - PROFIenergy-specific data (PE) - Data for the job processing (Task) - User data (UserData) The data block operates with optimized access. Connection parameter "Connection" The "PE_WOL" instruction reserves a connection resource in the area of "Open User Communication". This is used as a UDP connection. The following parameters must be defined in the data block for this: Connection ID ("Connection.id" parameter) The connection ID is an integer within the range of 1 to 32. The default setting is 31. It is used to identify the communication resources allocated by the firmware, for example the send and receive buffers. The connection ID must be unique throughout the CPU. Port number that is used for the "Wake on LAN" function ("Header.PortNo" parameter) Number of the UDP port via which a "Wake On LAN" packet is sent. These port numbers are part of the communication resources, which are identified and provided by the firmware through the connection ID. The default setting for port 2189 used here is currently not assigned by IANA. The port number is transferred to the connection configuration. This affects the "Connection.local_tsap_id[1]" and "Connection.rem_tsap_id[1]" parameters. Interface ID ("Connection.local_device_id" parameter) The interface ID is also part of the connection description. This ID identifies the CPU interface to use for this connection. There are several possible valid values. However, these need to be adapted to the employed CPU and interface: - B#16#01 for ET200S CPU or WinAC RTX with Ethernet interface in subslot IF1 - B#16#02 for CPU 315(F)-2PN/DP or CPU 317(F)-2PN/DP - B#16#03 for CPU 319(F)-2PN/DP - B#16#05 for CPU 41x(F)-3PN/DP - B#16#06 for WinAC RTX with Ethernet interface in subslot IF2 - B#16#0B for WinAC RTX with Ethernet interface in subslot IF3 - B#16#0F for WinAC RTX with Ethernet interface in subslot IF4 2648 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Structure of the data block The data block has the following structure: Name Data type Offset Comment Header PE_HEADER - Header information BOOL - Signal for indicating a change in the data area. Update (1) True= indicates a change by the user. False = indicates the application of changes. Initialized BOOL - Signal indicating the completed initialization. True=Initialization finished. False= indicates that the block is not initialized. LinkUp BOOL - Indicates successful configuration of the Ethernet interface. True=interface ready for use. False=interface not yet configured. LinkDown BOOL - Indicates an unconfigured interface. True=interface is not yet configured. False=interface is currently being configured or is now configured. PROFINET_ID (1) INT - ID of the PROFINET I/O system Reserved ARRAY [1..37] OF BYTE - Reserved LastDeviceID INT - Contains the highest Device-ID in this PROFINET I/O system. PortNo (1) WORD - Port number that is used for the "Wake on LAN" function (default= 2189). Connection TCON_Param - Contains the connection configuration of the "Wake on LAN" connection. BLOCK_LENGTH UInt - Length of the structure (always B#16#40). ID CONN_OUC - Connection ID - Connection type (UDP = B#16#13) (1) CONNECTION_TYPE (1) USINT BOOL - Active connection establishment (always passive for UDP) LOCAL_DEVICE_ID (1) ACTIVE_EST USINT - Contains the interface ID (CPU dependent) LOCAL_TSAP_ID_LEN USINT - Contains the length in bytes of the own/local UDP port REM_SUBNET_ID_LEN USINT - Unused (always B#16#00) REM_STADDR_LEN (1) USINT - Contains the length of the remote IP address or B#16#00. REM_TSAP_ID_LEN (1) USINT - Contains the length in bytes of the remote UDP port. NEXT_STADDR_LEN USINT - Contains the length of the default router address (not relevant). LOCAL_TSAP_ID (1) ARRAY[1..16] OF BYTE - Contains the own/local port number. REM_SUBNET_ID (1) ARRAY[1..6] OF USINT - Unused (always B#16#00) REM_STADDR (1) ARRAY[1..6] OF USINT - Contains the remote IP address. (1) (1) (1) WinCC Basic V13.0 System Manual, 02/2014 (1) 2649 Programming the PLC 9.7 References Name Data type Offset Comment REM_TSAP_ID (1) ARRAY[1..16] OF BYTE - Contains the remote UDP port number. NEXT_STADDR (1) ARRAY[1..6] OF BYTE - irrelevant SPARE (1) WORD - ARRAY[1..256] OF PE_DEVICE - Array of devices PE_DEV - Contains data for each device DiagID HW_IO - Diagnostic address of the device. Assigned by the hardware configuration. InterfaceID WORD - Diagnostic address of the device interface. Assigned by the hardware configuration. MACAdr ARRAY[1..6] OF BYTE - Contains the MAC address of the device. IPAdr ARRAY[1..4] OF BYTE - Contains the IP address of the device. OrderID_MxLen Byte - Contains the maximum length of the OrderID. OrderId_ActLen Byte Contains the actual length of the OrderID. OrderID_Data ARRAY[1..20] OF CHAR Contains the OrderID of the device. Device Device PE ModeID PE_PE - PROFIenergy-specific data. BYTE - PE_MODE_ID according to Profienergy specification. Result BYTE - PE ErrorCode according to PROFIenergy specification. PauseTime (1) TIME - Contains the idle time in ms. TimeToPause TIME - Contains the time it takes for the device to go into Pause mode. TimeToOperate TIME - Contains the time it takes for the device to go into operating mode. MinSleepTime TIME - Contains the minimum time of the device in PE_SLEEP_MODE. SleepToOperate TIME - Contains the time it takes for the device to go from PE_SLEEP_MODE into operating mode. StatusOperate BOOL - Indicates the operating mode of the device. StatusPause BOOL - Indicates the device is in Pause mode. StatusSleep BOOL - Indicates the PE_SLEEP_MODE of the device. StatusTransitOK BOOL - Indicates the transition from one energy state to another. StatusInTransit BOOL - Indicates a current state transition. StatusTransitNOK BOOL - Indicates that the state change was not successful. StatusError BOOL - Indicates an error with the device. StatusRetryEx BOOL - Indicates an unsuccessful execution of a command. No more attempts will be made to execute this command. CmdStartPause (1) BOOL - Places a START_PAUSE command for this device in the queue. CmdEndPause (1) BOOL - Places a END_PAUSE command for this device in the queue. 2650 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Name Data type Offset Comment CmdUpdateStatus (1) BOOL - Places a PEM_STATUS command for this device in the queue. EnableSleep (1) BOOL - Allows PE_SLEEP_MODE for this device. True= device should go to PE_SLEEP_MODE if idle time is sufficient False=device may not go into PE_SLEEP_MODE. Services WORD - Shows all supported PROFIenergy services. ARRAY[1..24] OF BYTE - User-defined data PE_TASK - Job processing Cmd BYTE - Internal bits for job processing CmdJ BYTE - Internal bits for job processing TimeStart BOOL - Starts a delay time. TimeStarted BOOL - The delay time has just started. TimeDone BOOL - Shows the expiration of the delay time. Done BOOL - Indicates that this job has been completed. DelayedCmd BOOL - Indicates that a delayed command is still pending. IsV1_0 BOOL - Indicates that this device is a Spec. V1.0 device. IsWakeOnLAN BOOL - Indicates that this device is woken up by "Wake On LAN". RetryCount BYTE - Repetition counter for PE_COMMANDS Duration TIME - Contains the value for the delay in ms. StartTime TIME - Contains the start time for the delay time. MachineState INT - Contains the internal status of the job. UserData (2) Task (1) To be filled in by the user. (2) Available for use by the user. Parameter STATUS Parameter STATUS The output value at the STATUS parameter is divided into three areas: Bits 31 to 24: MESSAGE Bit 23 to 16: LOCATION Bit 15 to 0: INFORMATION You can learn the meaning of each error code for the three areas in the following tables: Table 9-53 Error code Possible values for MESSAGE Description (W#16#...) 00 No error. 50 Instruction initialized. WinCC Basic V13.0 System Manual, 02/2014 2651 Programming the PLC 9.7 References Error code Description (W#16#...) 51 Determining configuration of the PROFINET I/O system. 52 The instruction could not determine any configured devices in the PROFINET I/O system. 53 Determining the logical addresses of configured devices. 54 Reading interface information out of the devices. 55 Determining I&M data (data record 0 only) of the configured devices. 56 Configuring PROFINET interface for sending the "Wake on LAN" MagicPaketTM via UDP. 57 Determining PROFIenergy capabilities of the connected devices. 62 Invalid PROFINET I/O system ID detected. The causative number is displayed in the INFORMATION field. 70 The instruction is initiated and processing jobs. The value in the INFORMATION field contains the number of currently active jobs. 80 The instruction has lost the initialization during processing of jobs. This generally occurs when either the instance DB or the user DB has been reloaded. FF Unknown error has occurred. Table 9-54 Error code Possible values for LOCATION Description (W#16#...) 00 The instruction is either not initialized or it is idle. 70 The instruction is waiting for jobs. 71 The instruction has appended a job to the job list. 72 The instruction is preparing to send a job. 73 The instruction is sending a job to a device. 74 The instruction is waiting for a response from the device. 75 The instruction is evaluating the response of the device. 76 The instruction is removing the job from the job list. FF Unknown error has occurred. Table 9-55 Error code Possible values for INFORMATION Description (W#16#...) 0000 No additional information available and no jobs active. 0001 -00FF 1 - 255 jobs are currently being processed. 8001 Error at parameter 1 8002 Error at parameter 2 8003 Error at parameter 3 8004 Error at parameter 4 2652 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Error code Description (W#16#...) 8005 Error at parameter 5. This error is reported if there is no interconnection or an invalid interconnection to the user DB. Possible causes: The user DB is too small. The user DB is write-protected. There is no user DB in the RAM. The user DB is invalid for the employed CPU. 8100 An attempt has been made to place more than the maximum of 256 possible jobs. This is a temporary error, which is resolved by completing a few jobs. The placed jobs are not accepted and must be placed again. 8200 An attempt has been made to send an invalid or an unsupported PROFIenergy command (PE_COMMAND). 84xx A communication error has occurred. The number of the device that generated the error is output to "xx". 85xx An error has been returned from device xx. The number of the device that generated the error is output to "xx". 8600 The requested wake-up method is currently not supported. FFFF Unknown error has occurred. PROFIenergy commands Structure of the message frames Structure of the response frame in accordance with the PROFIenergy profile The table below shows the basic structure of the response frame in accordance with the PROFIenergy profile. The response frame consists of a general section (Header) and a specific section (Service Data Response). The contents of the specific section of the response frame can be found in the description of the relevant PROFIenergy command. Block definition Attributes Value Data type BlockHeader BlockType 801 hex WORD BlockLength WORD BlockVersionHigh 1 hex BYTE BlockVersionLow 0 hex BYTE WinCC Basic V13.0 System Manual, 02/2014 Description Number of bytes without consideration of the fields BlockType and BlockLength. 2653 Programming the PLC 9.7 References Block definition Attributes Value Data type Description Response Header Service_Request_ID 1hex to FF hex BYTE ID of the PI command executed. The ID of the PE command processed by the PE entity is returned in the response frame: 01: Start_Pause 02: End_Pause 03: Query_Modes 04: PEM_Status 05: PE_Identify 06 to 09: Reserved 16: Query_Measurement 11 to CF: Reserved D0 to FF: Manufacturer-specific Service Header Response Request_Reference 1hex to FF hex BYTE Unique number to identify the query/ response pair (returned by the server in the response). Status 1hex to FF hex BYTE Information whether or not the PI command was executed: 00: Reserved 01: Completed 02: Completed with error 03: Data incomplete 04 to CF: Reserved D0 to FF: Depends on the Service_Request_ID Data_Structure_ Identifier_RS 1hex to FF hex BYTE 00: Reserved 01 to FF: Data structure depends on the Service_Request_ID 0xFF - Error Service Data Response Depends on the Service-Request-ID: For the service request IDs, see the CMD and CMD_MODIFIER parameters of the instruction "PE_CMD (Page 2635)". The specific contents of the response frame can be found in the description of the PE command (see for example the "Start_Pause (Page 2655)" command). 2654 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References PI Command "Start_Pause" Description Use the PE command "Start_Pause" to start the energy-saving mode. The command Start_Pause can be used to: Switch the PE from "ready" state (PE_ready_to_operate) to an energy-saving mode (PE_energy_saving_mode). The PE entity can automatically switch between the energy-saving modes. Energy consumption can increase or decrease when you switch energy-saving mode. Calling the PI command "Start_Pause" The command "Start_Pause" is called with the instruction "PE_CMD (Page 2635)" with the following parameters: Parameter Value Description CMD 1 Call of PE command "Start_Pause". CMD_MODIFIER 0 There are no additional specifications of the command call for command "Start_Pause". CMD_PARA_LEN 4 Length of the CMD_PARA parameter of 4 bytes. CMD_PARA VARIANT VARIANT pointer to the value for "Pause_Time" (TIME). Response frame (Service Data Response) The following response frame data of the PE entity is written to the data block that is referenced at parameter RESPONSE_DATA (see instruction "PE_CMD (Page 2635)"): Attribute Value Data type Description PE_Mode_ID 1 to 255 BYTE Identification number of the energy-saving mode Reserved 0 BYTE - PI Command "End_Pause" Description The PE command "End_Pause" is used to end the energy-saving mode of the PE entity. WinCC Basic V13.0 System Manual, 02/2014 2655 Programming the PLC 9.7 References Calling the PE command "End_Pause" The command "End_Pause" is called with the instruction "PE_CMD (Page 2635)" with the following parameters: Parameter Value Description CMD 2 Call of PE command "End_Pause". CMD_MODIFIER 0 There are no additional specifications of the command call for command "End_Pause". CMD_PARA_LEN 0 Length of the CMD_PARA parameter of 0 bytes. CMD_PARA irrelevant - Response frame (Service Data Response) The following data of the PE entity response frame is written to the data block referenced at the RESPONSE_DATA parameter (see "PE_CMD (Page 2635)"): Attribute Value Data type Description Time_to_operate - DWORD Expected time it takes to switch to the "PE_ready_to_operate" mode. PI command "Query_modes" - "List_Energy_Saving_Modes" Description Use PE command "Query_modes" and sub-command (modifier) "List_Energy_Saving_Modes" to output all energy-saving modes (PE_Mode_ID) supported by the PE entity. The query result is written in the form of a response frame to the data block referenced by theRESPONSE_DATA parameter. Calling the PE command "Query_modes" - "List_Energy_Saving_Modes" The command "List_Energy_Saving_Modes" is called with the instruction "PE_CMD (Page 2635)" with the following parameters: 2656 Parameter Value Description CMD 3 Call of PE command "Query_modes". CMD_MODIFIER 1 Specification of the command call: Select the sub-command "List_Energy_Saving_Modes" to output the number and types of energy-saving modes supported. CMD_PARA_LEN 0 Length of the CMD_PARA parameter of 0 bytes. CMD_PARA irrelevant - WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Response frame (Service Data Response) The following data of the PE entity response frame is written to the data block referenced at the RESPONSE_DATA parameter (see "PE_CMD (Page 2635)"): Attribute Value Data type Description Number_of_PE_ Mode_IDs 1 BYTE The number of energy-saving modes. PE_Mode_IDs - Array [...] of BYTE Array with the IDs of the supported energysaving modes. The meaning of the individual IDs depends on the PE entity. PI command "Query_modes" - "Get_Mode" Description You use the PE command "Query_modes" and the sub-command (modifier) "Get_Mode" to output the attributes of the energy-saving mode which is currently enabled. Calling the PE command "Query_modes" - "Get_Mode" The call of the command with the instruction "PE_CMD" occurs with the following parameters: Parameter Value Description CMD 3 Call of the PE command "Query_modes" CMD_MODIFIER 2 Specification of the command call: Select the sub-command "Get_Mode" to output the status of the mode which is currently enabled. CMD_PARA_LEN 1 Length of the CMD_PARA parameter of 1 byte. CMD_PARA VARIANT VARIANT pointer to the value for PE_MODE_ID. WinCC Basic V13.0 System Manual, 02/2014 2657 Programming the PLC 9.7 References Response frame (Service Data Response) The following data of the PE entity response frame is written to the data block referenced at the RESPONSE_DATA parameter (see "PE_CMD (Page 2635)"): Attribute Value Data type Description PE_Mode_ID 0 "PE_power_off" mode BYTE ID of the energy-saving mode currently enabled. 1...254 Energy-saving mode of the PE entity (manufacturer-specific) 255 "PE_ready_to_operate" mode PE_Mode_Attributes Bit 0: BYTE = 0: Only static energy consumer and time values are available. = 1: Dynamic energy consumer and time values are available. Bit 1 to 7: Reserved Time_min_Pause 1 Time difference without date DWORD Minimum pause time for the PI mode. The minimum pause time is the sum of the values of the following attributes: Time_to_Pause Time_to_operate Time_min_length_of_stay See the description "PAUSE_TIME parameter" of the instruction "PE_START_END: Start and exit energysaving mode (Page 2631)". Time_to_Pause 1 Time difference without date DWORD Switch off time: Duration from call of energy-saving mode to start of energysaving mode (transition duration of PE_ready_to_operate to PE_energy_saving_mode). The switch-off time depends on the PE entity. Time_to_operate 1 Time difference without date DWORD Switch-on time: Duration of the transition from energy-saving mode (PE_energy_saving_mode) to ready to operate mode (PE_ready_to_operate). The PE entity calculates the duration dynamically in the output operation. Time_min_length_ of_stay 1 DWORD Minimum active period of the energysaving mode on the PE entity. Time_max_length_ of_stay 1 DWORD Maximum active period of the energysaving mode on the PE entity. Mode_Power_ Consumption 2 REAL Power consumption of the PE entity in active energy-saving mode. Unit: kW 2658 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Attribute Value Energy_ Consumption_ to_pause 2 Data type Description REAL Energy consumption of the PE entity during transition from ready-to-operate mode (PE_ready_to_operate) to energysaving mode (PE_energy_saving_mode) Unit: kWh Energy_ Consumption_ to_operate 2 REAL Energy consumption of the PE entity during transition from energy-saving mode (PE_energy_saving_mode) to ready-tooperate mode (PE_ready_to_operate) Unit: kWh 1 If the duration is infinite, 0xFFFFFFFF will be output. If the duration is zero, "0" will be output. 2 If the data for energy and power consumption is not defined by the PE entity, "0.0" will be output as the value. PI command "PEM_Status" Description The PE command "PEM_Status" is used to query the status of a PE entity energy-saving mode that is currently enabled. Calling the PE command "PEM_Status" The command "PEM_Status" is called with the instruction "PE_CMD" with the following parameters: Parameter Value Description CMD 4 Call of PE command "PEM_Status". CMD_MODIFIER 0 There are no other specifications of the command call for command "PEM_Status". CMD_PARA_LEN 0 Length of the CMD_PARA parameter of 0 bytes. CMD_PARA irrelevant - WinCC Basic V13.0 System Manual, 02/2014 2659 Programming the PLC 9.7 References Response frame (Service Data Response) The following data of the PE entity response frame is written to the data block referenced at the RESPONSE_DATA parameter (see "PE_CMD (Page 2635)"): Attribute Value Data type Description PE_Mode_ID_ Source 0 "PE_power_off" mode BYTE Mode of the PE entity before a PE command is sent. BYTE Mode of the PE entity after a PE command is executed. DWORD Switch-on time: Duration of the transition from energy-saving mode (PE_energy_saving_mode) to ready to operate mode (PE_ready_to_operate). 1 to 254 Energy-saving mode of the PE entity (manufacturer-specific) 255 "PE_ready_to_operate" mode PE_Mode_ID_ Destination 0 "PE_power_off" mode 1 to 254 Energy-saving mode of the PE entity (manufacturer-specific) 255 "PE_ready_to_operate" mode Time_to_operate Time difference without date The PE entity calculates the duration dynamically during output. Remaining_time_to_ destination Time difference without date Mode_Power_ Consumption DWORD Remaining time to switch to another mode. REAL Power consumption of the PE entity in active energy-saving mode. Unit: kW Energy_ Consumption_ to_Destination REAL Energy_ Consumption_ to_operate REAL Energy consumption for the current PI transition Unit: kWh Energy consumption of the PE entity during transition from energy-saving mode (PE_energy-saving mode) to readyto-operate mode (PE_ready_to_operate) Unit: kWh PI command "PE_Identify" Description The PE command "PE_Identify" is used to read out the number and description of PE commands supported by the PE entity. The number of specific commands supported depends on the PE entity. As PE_Identify is itself a PE command, at least three supported PE commands will be output upon a positive response: Start_Pause, End_Pause and PE_Identify. 2660 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Calling the PE command "PE_Identify" The command "PE_Identify" is called with the instruction "PE_CMD (Page 2635)" with the following parameters: Parameter Value Description CMD 5 Call of the command "PE_Identify". CMD_MODIFIER 0 There are no other specifications of the command call for command "PE_Identify". CMD_PARA_LEN 0 Length of the CMD_PARA parameter of 0 bytes. CMD_PARA irrelevant - Response frame (Service Data Response) The following data of the PE entity response frame is written to the data block referenced at the RESPONSE_DATA parameter (see "PE_CMD (Page 2635)"): Attribute Value Data type Description Count 1 6 BYTE Number of supported PROFIenergy commands Start_Pause 1 BYTE First PE command supported (Service_Request_ID) End_Pause 2 BYTE ... Query_Modes 3 BYTE ... PEM_Status 4 BYTE ... PE_Identify 5 BYTE ... Query_Measurement 16 BYTE Last PE command supported (Service_Request_ID) The number of commands supported is manufacturer-specific and depends on the PE entity used. The values given are an example of a response frame where all 6 PE commands are supported. 1 PI Command "Query_Measurement" - "Get_Measurement_list" Description Use the PE command "Query_Measurement" and sub-command (modifier) "Get_measurement_list" to query the specific measured values supported by the PE entity. The supported measured values are output as a list in the data block referenced by the RESPONSE_DATA parameter. WinCC Basic V13.0 System Manual, 02/2014 2661 Programming the PLC 9.7 References Calling the PE command "Query_Measurement" - "Get_Measurement_list" The command is called with the instruction "PE_CMD (Page 2635)" with the following parameters: Parameter Value Description CMD 16 Call of the command "Query_Measurement". CMD_MODIFIER 1 Specification of the command call: Select the sub-command "Get_Measurement_List" to output a list of supported measured values. CMD_PARA_LEN 0 Length of the CMD_PARA parameter of 0 bytes. CMD_PARA irrelevant - Response frame (Service Data Response) The following data of the PE entity response frame is written to the data block referenced at the RESPONSE_DATA parameter (see "PE_CMD (Page 2635)"): Attribute Value Data type Description Count - BYTE Number of measurement IDs reserved - BYTE Measurement_ID - WORD First supported Measurement_ID The Measurement_ID is manufacturer-specific. For more information, refer to the manual of the respective PE entity. Accuracy_Domain - BYTE See "accuracy domain" table. Accuracy_Class - BYTE See "accuracy classes" table. Range - REAL Specifies the scale end value of the measured value (only for accuracy domain 1). The attribute range uses the same unit as defined using attribute Measurement_ID (only one unit is used for each Measurement_ID). Measurement_ID - WORD Last supported Measurement_ID Accuracy_Domain - BYTE See "accuracy domain" table. Accuracy_Class - BYTE See "accuracy classes" table. Range - REAL Specifies the scale end value of the measurement value (only for accuracy domain 1). The attribute range uses the same unit as defined using attribute Measurement_ID (only one unit is used for each Measurement_ID). ... ... Accuracy domains Accuracy domain Description 0 Reserved 1 The accuracy deviation is output in percentages of the scale end value. The percentage of the possible deviation is divided into accuracy classes (see table: Accuracy classes of the accuracy domains 1 and 2). 2662 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Accuracy domain Description 2 The accuracy deviation is output in percentages of the current measurement value. The percentage of the possible deviation is divided into accuracy classes (see table: Accuracy classes of the accuracy domains 1 and 2). 3 The measuring accuracy adheres to the standard IEC 61557-12. The function performance classes for performance measurement and monitoring devices (PMD) without external sensors, and the system performance classes for PMD with external sensors, are coded as set out in the "Accuracy classes of accuracy domain 3" table. 4 The entry of the accuracy adheres to the standard EN 50470-3, chapter 8 (see also table: Accuracy classes of accuracy domain 4). Accuracy classes Table 9-56 Accuracy classes of the accuracy domains 1 and 2 Accuracy class Meaning Accuracy class Meaning Table 9-57 1 2 3 4 5 6 7 8 Reserved 0.01% 0.02% 0.05% 0.1% 0.2% 0.5% 1% 1.5% 9 10 11 12 13 14 15 >15 2% 2.5% 3% 5% 10% 20% >20% Not defined Accuracy classes of accuracy domain 3 Accuracy class Meaning Accuracy class Meaning Table 9-58 0 0 1 2 3 4 5 6 7 8 Reserved 0,02 0,05 0,1 0,2 0,5 1 1,5 2 9 10 11 12 13 14 >13 2,5 3 5 10 20 20% Not defined Accuracy classes of accuracy domain 4 Accuracy class Meaning 0 1 2 3 4 5 6 >7 Reserved 0,5 1,0 1,5 2,0 2,5 3,0 Not defined PI Command "Query_Measurement" - "Get_Measurement_values" Description Use the PE command "Query_Measurement" and sub-command (modifier) "Get_measurement_values" to output a list of measured values supported by the PE entity. The measured values are output as a list in the data block referenced by the RESPONSE_DATA parameter. WinCC Basic V13.0 System Manual, 02/2014 2663 Programming the PLC 9.7 References Calling the PE command "Query_Measurement" - "Get_Measurement_values" The command is called with the instruction "PE_CMD (Page 2635)" with the following parameters: Parameter Value Description CMD 16 Call of the command "Query_Measurement". CMD_MODIFIER 2 Specification of the command call: Select the command "Get_Measurement_Values" to output a list of supported measurement values. CMD_PARA_LEN 0 Depends on the number of measurement values. The length of the parameters results from the attribute count and the sum of the lengths of the attributes for the transferred measurement values. CMD_PARA VARIANT VARIANT pointer to data structure with list of measured values to be queried (see "CMD_PARA parameter"). Parameter CMD_PARA The structure specified with the VARIANT pointer at the CMD_PARA parameter must have the following setup: Attribute Value Data type Description Count - BYTE Number of measured values (Measurement-IDs) reserved 0 BYTE Not used Measurement_ID - WORD First measured value queried - WORD Last measured value queried ... Measurement_ID Response frame (Service Data Response) The following response frame data of the PE entity is written to the data block that is referenced at parameter RESPONSE_DATA (see "PE_CMD (Page 2635)"): Attribute Value Data type Description Count 1 - BYTE Number of measured values (Measurement-IDs) reserved 0 BYTE Not used Length_of_Structure 2 to 65535 WORD Length of the structure in bytes Measurement_Data_ Structure_ID 1 = simple value BYTE Defines the following structure. Measurement_ID 0 to 65535 WORD ID of the supported measurement value. Status_of_ Measurement_Value 1 to 3 BYTE Status of the measurement value: 1: Valid 2: Not supported 3: Invalid Transmission_Data_ Type 2664 - REAL WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Attribute Value Data type Description End_of_demand - TOD Optional time stamping with data type TimeOfDay. Length_of_Structure - WORD Length of the structure in bytes Measurement_Data_ Structure_ID - BYTE Defines the following structure. Measurement_ID - WORD ID of the supported measurement value. BYTE Status of the measurement value: ... Status_of_Measurem ent_Value 1: Valid 2: Not supported 3: Invalid Transmission_Data_ Type - REAL End_of_demand - TOD Optional time stamping with data type TimeOfDay. If the data length of the measurement values queried exceeds the size of the PDU (Protocol Data Unit) of the protocol layer, the data will not be completely transferred and only the supported measurement values will be output. 1 iDevice / iSlave PE_I_DEV: Control PROFIenergy commands in the I-Device Description The instruction "PE_I_DEV" is used to process the PROFIenergy profile in the intelligent IO device (iDevice). The functions which are executed by the firmware in standard PROFIenergycompatible IO devices, such as the ET 200S, are implemented in the iDevice by the instruction "PE_I_DEV" and the corresponding auxiliary blocks: The instruction "PE_I_DEV" is called cyclically by the user program of the iDevice and receives all PROFIenergy commands. The PROFIenergy response is generated by configuring an auxiliary block. The response in the pause is fully programmable. The response data must be provided within 10 seconds; otherwise, "State conflict 0x80B5" will occur at the STATUS parameter of the instruction in the IO controller. No specific knowledge of the PROFIenergy standard is required to use the instruction. WinCC Basic V13.0 System Manual, 02/2014 2665 Programming the PLC 9.7 References PROFIenergy auxiliary blocks (PE auxiliary blocks) The PE auxiliary blocks are used to generate the response frame. Enter the response data (in plain text) at the input parameters of the relevant block. For each PROFIenergy command, there is a corresponding auxiliary block for a positive response: - PE command "Start_Pause": PE_Start_RSP (Page 2670) - PE command "End_Pause": PE_End_RSP (Page 2672) - PE command "Query_modes" - "List_Energy_Saving_Modes": PE_List_Modes_RSP (Page 2673) - PE command "Query_modes" - "Get_Mode": PE_Get_Mode_RSP (Page 2674) - PE command "PEM_Status": PE_PEM_Status_RSP (Page 2676) - PE command "PE_Identify": PE_Identify_RSP (Page 2678) - PE command "Query_Measurement" - "Get_Measurement_list": PE_Measurement_List_RSP (Page 2679) - PE command "Query_Measurement" - "Get_Measurement_values": PE_Measurement_Value_RSP (Page 2681) Irrespective of the PROFIenergy command, there is an additional shared auxiliary block for a negative response (see PE_Error_RSP (Page 2669)). Interconnection of the auxiliary blocks The instruction "PE_I_DEV" and the auxiliary blocks are coordinated. Some of the parameters are simply interconnected. The diagram below shows which of the parameters need to be interconnected. 3(B,B'(9 3(DX[LOLDU\EORFN ,1,' ,1&0'VSHFLILF SDUDPHWHUV ,15(6(7 (YDOXDWLRQDQG UHVSRQVHE\ XVHU 287&0' 8VHU 287&0'B02',),(5 ,Q2XW&0'B3$5$ 287(5525 287,1'(; 28767$786 ,Q2XW$&7,9$7( 287(5525 8VHU 28767$786 ,19$/,' 2871(: ,Q2XW'$7$B(5525563 287&0' 287&0'B02',),(5 ,Q2XW9$/,' ,13(B,B'(9B1(: ,Q2XW'$7$B(5525563 ,1&0' ,1&0'B02',),(5 ,QWHUFRQQHFWLRQHVVHQWLDO 2666 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameters The following table shows the parameters of the instruction "PE_I_DEV": Parameter Declaration Data type Memory area Description RESET Input BOOL I, Q, M, D, L or constant Resets the instruction. ID Input HW_SUBMODU I, Q, M, D, L or LE constant Address of the iDevice The address may be taken from the hardware configuration. VALID Input BOOL I, Q, M, D, L or constant The response data for the PROFIenergy controller is ready and can be sent. CMD_PARA Output VARIANT I, Q, M, D, L Parameters for: Get mode: PE_mode_ID Get measurement values: List of Measurement_IDs (list of IDs of the tags to be read; either one tag or multiple tags may be read at any given time). Maximum length: 234 bytes DATA_ERRO RRSP InOut VARIANT I, Q, M, D, L Pointer to the data area containing the acknowledgment data for the PROFIenergy controller. This must correspond to the pointer which is also used with the auxiliary blocks. INDEX Output INT I, Q, M, D, L Data record number of the PROFIenergy record (set at 0x80A0) CMD Output INT I, Q, M, D, L Service-Request-ID of the PROFIenergy command in accordance with the PROFIenergy profile (see "CMD and CMD_MODIFIER parameters"). Further PE commands (Service-Request-IDs) are possible following extensions of the PROFIenergy profile. CMD_ MODIFIER Output INT I, Q, M, D, L PROFIenergy sub-command: Only when CMD=3 or CMD=16; see "CMD and CMD_MODIFIER parameters". For all other commands: "0". Further sub-commands are possible following extensions of the PROFIenergy profile. NEW Output BOOL I, Q, M, D, L New data available from the PROFIenergy controller. ERROR Output BOOL I, Q, M, D, L Command completed with error. STATUS Output DWORD I, Q, M, D, L Error information (see "STATUS parameter"). For additional information on valid data types, refer to "Overview of the valid data types (Page 1204)". WinCC Basic V13.0 System Manual, 02/2014 2667 Programming the PLC 9.7 References Parameters CMD and CMD_MODIFIER CMD CMD_ MODIFIER PROFIenergy command Description 01 0 Start_Pause Start energy-saving mode or switch to a different energysaving mode. 02 0 End_Pause End energy-saving mode. 03 1 Query_Modes - List energy saving Modes Output the energy-saving modes supported. 2 Query_Modes - Get Mode Output attributes of the energy-saving mode currently enabled. 04 0 PEM_Status Query status of energy-saving mode. 05 0 PE_Identify Read out the number and description of PE commands supported. 16 1 Query_Measurement Get_Measurement_List List of measured values supported by the PE entity. 2 Query_Measurement Get_Measurement_Values Output of the measured values of the PE entity. STATUS parameter Error information is output at the STATUS output parameter. If it is interpreted as ARRAY[1...4] of BYTE, the error information has the following structure: Field element Name Meaning STATUS[1] Function_Num Cause of the error B#16#00: No error B#16#DE: Error during reading of data record B#16#DF: Error during writing of data record B#16#C0: Error message from the instruction "PE_I_DEV" or from the internal communication instructions "RDREC (Page 2558)" and "WRREC (Page 2560)". STATUS[2] Error_Decode STATUS[3] Error_Code_1 Location of the error ID 80: DPV1 error as defined in IEC 61158-6 or application-specific Error ID (when Error_Decode = 80): B1: Write length error (error in write length or insufficient length information with the data type VARIANT). STATUS[4] 2668 Error_Code_2 For PROFINET errors: Output of IO controller error message If no PROFINET error has occurred, the value in STATUS[4] = "0". WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Note Error messages of the instructions RDREC and WRREC The instruction "PE_I_DEV" uses the instructions "WRREC (Page 2560)" and "RDREC (Page 2558)" for communication. Error messages for these instructions are output in the field elements STATUS[1] to STATUS[4]. Please see the description of the corresponding STATUS (Page 2568) parameter for an explanation of the error codes of the "WRREC (Page 2560)" and "RDREC (Page 2558)" instructions. See also Description of PROFIenergy (Page 2629) Auxiliary blocks of the instruction PE_I_DEV PE_Error_RSP: Generate negative answer to command Description The auxiliary block "PE_Error_RSP" (Response with failure) generates a negative response if the command requested is not supported (either in general or temporarily). Response generation does not depend on the command requested. Parameter The following table shows the parameters of the "PE_Error_RSP" auxiliary block: Parameter Declaration Data type Memory area Description PE_I_DEV_NEW Input BOOL I, Q, M, D, L or constant The parameter must be interconnected with the NEW output parameter of the "PE_I_DEV (Page 2665)" instruction. The auxiliary block is only processed if the parameter value is set to "1". ERROR_CODE Input BYTE I, Q, M, D, L or constant Error number ACTIVATE InOut BOOL I, Q, M, D, L The instruction copies the input parameters to the DATA_ERROR_RSP data area at a rising edge at input ACTIVATE. The parameter is then reset by the instruction. The parameter must be set within 10 seconds after a rising edge is detected at parameter NEW of the "PE_I_DEV (Page 2665)" instruction. WinCC Basic V13.0 System Manual, 02/2014 2669 Programming the PLC 9.7 References Parameter Declaration Data type Memory area Description VALID InOut BOOL I, Q, M, D, L The parameter must be interconnected with the VALID input of the "PE_I_DEV (Page 2665)" instruction. The auxiliary block sets the parameter as soon as the response data for the PROFIenergy controller is available and ready for transmission. DATA_ ERRORRSP InOut VARIANT D ERROR Output BOOL I, Q, M, D, L STATUS Output WORD I, Q, M, D, L Pointer on the data area in which the response data is stored. The parameter is identical to the pointer for DATA_ERRORRSP of the "PE_I_DEV (Page 2665)" instruction. The addressed data area contains the complete PROFIenergy frame. Minimum length: 244 bytes "0": No error "1": Error occurred. "0": No error "0x80B1": Error in VARIANT setting, e.g. incorrect range You can find additional information on valid data types under "Overview of the valid data types (Page 1204)". PE_Start_RSP: Generate answer to command at start of pause Description The auxiliary block "PE_Start_RSP" (Start Pause) generates the response to the PE command Start_Pause (Page 2655). The instruction returns the energy-saving mode to which the device has switched (PE_MODE_ID parameter). If the response differs depending on the length of the pause, you can return this fact in the feedback on the energy-saving mode (PE_Mode_ID = 1 for a brief pause, PE_Mode_ID = 2 for a longer pause, etc.). 2670 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameter The following table shows the parameters of the "PE_Start_RSP" auxiliary block: Parameter Declaration Data type Memory area Description PE_I_DEV_NE W Input BOOL I, Q, M, D, L or constant The parameter must be interconnected with the NEW output parameter of the "PE_I_DEV (Page 2665)" instruction. The auxiliary block is only processed if the parameter value is set to "1". CMD Input INT I, Q, M, D, L or constant Service-Request-ID of the PROFIenergy command The parameter must be interconnected with the CMD output parameter of the "PE_I_DEV (Page 2665)" instruction. PE_MODE_ID Input BYTE I, Q, M, D, L or constant PE mode that the process assumes ACTIVATE InOut BOOL I, Q, M, D, L The instruction copies the input parameters to the DATA_ERROR_RSP data area at a rising edge at input ACTIVATE. The parameter is then reset by the instruction. The parameter must be set within 10 seconds after a rising edge is detected at parameter NEW of the "PE_I_DEV (Page 2665)" instruction. VALID InOut BOOL I, Q, M, D, L The parameter must be interconnected with the VALID input of the "PE_I_DEV (Page 2665)" instruction. The auxiliary block sets the parameter as soon as the response data for the PROFIenergy controller is available and ready for transmission. DATA_ ERRORRSP InOut VARIANT D Pointer on the data area in which the response data is stored. The parameter is identical to the pointer for DATA_ERRORRSP of the "PE_I_DEV (Page 2665)" instruction. The addressed data area contains the complete PROFIenergy frame. Minimum length: 244 bytes ERROR Output BOOL I, Q, M, D, L "0": No error "1": Error occurred. STATUS Output WORD I, Q, M, D, L "0": No error "0x80B1": Error in VARIANT setting, e.g. incorrect range You can find additional information on valid data types under "Overview of the valid data types (Page 1204)". WinCC Basic V13.0 System Manual, 02/2014 2671 Programming the PLC 9.7 References PE_End_RSP: Generate answer to command at end of pause Description The auxiliary block "PE_End_RSP" generates the response to the PE command End_Pause (Page 2655). The response returned is the time required to switch from the current mode to "Ready_To_Operate" mode. Parameter The following table shows the parameters of the "PE_End_RSP" auxiliary block: Parameter Declaration Data type Memory area Description PE_I_DEV_NEW Input BOOL I, Q, M, D, L or constant The parameter must be interconnected with the NEW output parameter of the "PE_I_DEV (Page 2665)" instruction. The auxiliary block is only processed if the parameter value is set to "1". CMD Input INT I, Q, M, D, L or constant Service-Request-ID of the PROFIenergy command The parameter must be interconnected with the CMD output parameter of the "PE_I_DEV (Page 2665)" instruction. Time_to_Operate Input DWORD I, Q, M, D, L or constant Time required to switch from the current mode to "Ready_To_Operate". ACTIVATE InOut BOOL I, Q, M, D, L The instruction copies the input parameters to the DATA_ERROR_RSP data area at a rising edge at input ACTIVATE. The parameter is then reset by the instruction. The parameter must be set within 10 seconds after a rising edge is detected at parameter NEW of the "PE_I_DEV (Page 2665)" instruction. VALID InOut BOOL I, Q, M, D, L The parameter must be interconnected with the VALID input of the "PE_I_DEV (Page 2665)" instruction. The auxiliary block sets the parameter as soon as the response data for the PROFIenergy controller is available and ready for transmission. DATA_ ERRORRSP InOut VARIANT D Pointer on the data area in which the response data is stored. The parameter is identical to the pointer for DATA_ERRORRSP of the "PE_I_DEV (Page 2665)" instruction. The addressed data area contains the complete PROFIenergy frame. Minimum length: 244 bytes 2672 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameter Declaration Data type Memory area Description ERROR Output BOOL I, Q, M, D, L "0": No error "1": Error occurred. STATUS Output WORD I, Q, M, D, L "0": No error "0x80B1": Error in VARIANT setting, e.g. incorrect range You can find additional information on valid data types under "Overview of the valid data types (Page 1204)". PE_List_Modes_RSP: Generate queried energy savings modes as answer Description The auxiliary block "PE_List_Modes_RSP" generates the response to the PE command List_Energy_Saving_Modes (Page 2656). The response generated includes the number and the IDs of energy-saving modes supported. Parameter The following table shows the parameters of the "PE_List_Modes_RSP" auxiliary block: Parameter Declaration Data type Memory area Description PE_I_DEV_NEW Input BOOL I, Q, M, D, L or constant The parameter must be interconnected with the NEW output parameter of the "PE_I_DEV (Page 2665)" instruction. The auxiliary block is only processed if the parameter value is set to "1". CMD Input INT I, Q, M, D, L or constant Service-Request-ID of the PROFIenergy command The parameter must be interconnected with the CMD output parameter of the "PE_I_DEV (Page 2665)" instruction. CMD_MODIFIER Input INT I, Q, M, D, L or constant PROFIenergy sub-command (evaluated only if CMD=3, or CMD=16). The parameter must be interconnected with the CMD_MODIFIER output parameter of the "PE_I_DEV" instruction. Number_of_PE_ Mode_IDs Input BYTE I, Q, M, D, L or constant Number of energy-saving modes supported. PE_MODE_ID Input I, Q, M, D, L Points to the area in which the IDs of the energysaving modes supported (PE_Mode_ID) are stored. VARIANT Permitted values: 1 to 254 Valid range: 1 to 254. WinCC Basic V13.0 System Manual, 02/2014 2673 Programming the PLC 9.7 References Parameter Declaration Data type Memory area Description ACTIVATE InOut BOOL I, Q, M, D, L The instruction copies the input parameters to the DATA_ERROR_RSP data area at a rising edge at input ACTIVATE. The parameter is then reset by the instruction. The parameter must be set within 10 seconds after a rising edge is detected at parameter NEW of the "PE_I_DEV (Page 2665)" instruction. VALID InOut BOOL I, Q, M, D, L The parameter must be interconnected with the VALID input of the "PE_I_DEV (Page 2665)" instruction. The auxiliary block sets the parameter as soon as the response data for the PROFIenergy controller is available and ready for transmission. DATA_ ERRORRSP InOut VARIANT D ERROR Output BOOL I, Q, M, D, L STATUS Output WORD I, Q, M, D, L Pointer on the data area in which the response data is stored. The parameter is identical to the pointer for DATA_ERRORRSP of the "PE_I_DEV (Page 2665)" instruction. The addressed data area contains the complete PROFIenergy frame. Minimum length: 244 bytes "0": No error "1": Error occurred. "0": No error "0x80B1": Error in VARIANT setting, e.g. incorrect range You can find additional information on valid data types under "Overview of the valid data types (Page 1204)". PE_Get_Mode_RSP: Generate queried energy data as answer Description The auxiliary block "PE_Get_Mode_RSP" generates the response to the command Get_Mode (Page 2657). The response frame contains the time, performance, or energy data of an energy-saving mode. 2674 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameter The following table shows the parameters of the "PE_Get_Mode_RSP" auxiliary block: Parameter Declaration Data type Memory area Description PE_I_DEV_NEW Input BOOL I, Q, M, D, L or constant The parameter must be interconnected with the NEW output parameter of the "PE_I_DEV (Page 2665)" instruction. The auxiliary block is only processed if the parameter value is set to "1". CMD Input INT I, Q, M, D, L or constant Service-Request-ID of the PROFIenergy command The parameter must be interconnected with the CMD output parameter of the "PE_I_DEV (Page 2665)" instruction. CMD_MODIFIER Input INT I, Q, M, D, L or constant PROFIenergy sub-command (evaluated only if CMD=3, or CMD=16). The parameter must be interconnected with the CMD_MODIFIER output parameter of the "PE_I_DEV" instruction. PE_Mode_ID Input BYTE I, Q, M, D, L or constant ID of the energy-saving mode currently enabled. Time_min_Pause Input DWORD I, Q, M, D, L or constant Minimum pause duration for this PE energysaving mode. This is the sum of the following three parameters: Time_to_Pause Time_to_operate Time_min_length_of_stay Time_to_Pause Input DWORD I, Q, M, D, L or constant Time between the edge at the START parameter (see "PE_I_DEV (Page 2665)") and the requested PE energy-saving mode being reached. Time_to_Operate Input DWORD I, Q, M, D, L or constant Maximum switch-on time to "PE_ready_to_operate". The "Time_to_operate" parameter can be used directly for the relevant calculations. The value may be a static maximum, or be calculated dynamically by the PE entity. Time_min_Lenght_ of_stay Input DWORD I, Q, M, D, L or constant Minimum dwell time of the PE entity in this PE mode. Time_max_Lenght_o f_stay Input DWORD I, Q, M, D, L or constant Maximum dwell time of the PE entity in this PE mode. Mode_Power_ Consumption Input DWORD I, Q, M, D, L or constant Energy consumption in the current PE mode in [kW]. Energy_Consum_ to_Pause Input DWORD I, Q, M, D, L or constant Energy consumption from "PE_ready_to_operate" to the current PE mode in [kWh]. Energy_Consum_ to_operate Input DWORD I, Q, M, D, L or constant Energy consumption from the current PE mode to "PE_ready_to_operate" in [kWh]. WinCC Basic V13.0 System Manual, 02/2014 2675 Programming the PLC 9.7 References Parameter Declaration Data type Memory area Description ACTIVATE InOut BOOL I, Q, M, D, L The instruction copies the input parameters to the DATA_ERROR_RSP data area at a rising edge at input ACTIVATE. The parameter is then reset by the instruction. The parameter must be set within 10 seconds after a rising edge is detected at parameter NEW of the "PE_I_DEV (Page 2665)" instruction. VALID InOut BOOL I, Q, M, D, L The parameter must be interconnected with the VALID input of the "PE_I_DEV (Page 2665)" instruction. The auxiliary block sets the parameter as soon as the response data for the PROFIenergy controller is available and ready for transmission. DATA_ ERRORRSP InOut VARIANT D Pointer on the data area in which the response data is stored. The parameter is identical to the pointer for DATA_ERRORRSP of the "PE_I_DEV (Page 2665)" instruction. The addressed data area contains the complete PROFIenergy frame. Minimum length: 244 bytes ERROR Output BOOL I, Q, M, D, L "0": No error "1": Error occurred. STATUS Output WORD I, Q, M, D, L "0": No error "0x80B1": Error in VARIANT setting, e.g. incorrect range You can find additional information on valid data types under "Overview of the valid data types (Page 1204)". PE_PEM_Status_RSP: Generate PEM status as answer Description The auxiliary block "PE_PEM_Status_RSP" generates the response to the command PEM_Status (Page 2659). 2676 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameter The following table shows the parameters of the "PE_PEM_Status_RSP" auxiliary block: Parameter Declaration Data type Memory area Description PE_I_DEV_NEW Input BOOL I, Q, M, D, L or constant The parameter must be interconnected with the NEW output parameter of the "PE_I_DEV (Page 2665)" instruction. The auxiliary block is only processed if the parameter value is set to "1". CMD Input INT I, Q, M, D, L or constant Service-Request-ID of the PROFIenergy command The parameter must be interconnected with the CMD output parameter of the "PE_I_DEV (Page 2665)" instruction. PE_MODE_ID_ Source Input BYTE I, Q, M, D, L or constant Source and Destination for PEM_STATUS. PE_MODE_ID_ Destination Input BYTE I, Q, M, D, L or constant 0x00: PE_POWER_OFF Values: 0x01 - 0xFE: manufacturer-specific 0xFF: PE_READY_TO_OPERATE Time_to_Operate 1 Input DWORD I, Q, M, D, L or constant Maximum switch-on time to "PE_ready_to_operate". "Time_to_operate" can be used directly for the relevant calculations. The value may be a static maximum, or be calculated dynamically by the PE entity. Remaining_time_ to_destination1 Input DWORD I, Q, M, D, L or constant Optional: Time remaining until the requested PE mode. Dynamic value or static maximum value Mode_Power_ Consumption2 Input DWORD I, Q, M, D, L or constant Energy consumption in the current PE mode in [kW]. Energy_ Consumption_ to_Destination2 Input DWORD I, Q, M, D, L or constant Energy consumption in the time until the requested PE mode in [kW]. Energy_ Consumption_ to_operate2 Input DWORD I, Q, M, D, L or constant Energy consumption from the current PE mode to "PE_ready_to_operate" in [kWh]. ACTIVATE InOut BOOL I, Q, M, D, L The instruction copies the input parameters to the DATA_ERROR_RSP data area at a rising edge at input ACTIVATE. The parameter is then reset by the instruction. The parameter must be set within 10 seconds after a rising edge is detected at parameter NEW of the "PE_I_DEV (Page 2665)" instruction. VALID InOut BOOL I, Q, M, D, L The parameter must be interconnected with the VALID input of the "PE_I_DEV (Page 2665)" instruction. The auxiliary block sets the parameter as soon as the response data for the PROFIenergy controller is available and ready for transmission. WinCC Basic V13.0 System Manual, 02/2014 2677 Programming the PLC 9.7 References Parameter Declaration Data type Memory area Description DATA_ ERRORRSP InOut VARIANT D Pointer on the data area in which the response data is stored. The parameter is identical to the pointer for DATA_ERRORRSP of the "PE_I_DEV (Page 2665)" instruction. The addressed data area contains the complete PROFIenergy frame. ERROR Output BOOL I, Q, M, D, L STATUS Output WORD I, Q, M, D, L Minimum length: 244 bytes "0": No error "1": Error occurred. "0": No error "0x80B1": Error in VARIANT setting, e.g. incorrect range If the time period is unlimited, the maximum value "0xFFFFFFFF" can be specified. If the time period is "Zero", "0x00" can be used. 1 2 If no energy consumption value has been defined, "0.0" can be specified. You can find additional information on valid data types under "Overview of the valid data types (Page 1204)". PE_Identify_RSP: Generate supported PROFIenergy commands as answer Description The auxiliary block "PE_Identify_RSP" generates the response to the command PE_Identify (Page 2660). In the response to the command, specify which PROFIenergy commands are supported. Please note that PE_IDENTIFY is itself a PE command and has to be included in the response. Parameter The following table shows the parameters of the "PE_Identify_RSP" auxiliary block: Parameter Declaration Data type Memory area Description PE_I_DEV_NE W Input BOOL I, Q, M, D, L or constant The parameter must be interconnected with the NEW output parameter of the "PE_I_DEV (Page 2665)" instruction. The auxiliary block is only processed if the parameter value is set to "1". CMD Input INT I, Q, M, D, L or constant Service-Request-ID of the PROFIenergy command The parameter must be interconnected with the CMD output parameter of the "PE_I_DEV (Page 2665)" instruction. Start_Pause Input BOOL I, Q, M, D, L or constant One parameter for each of the relevant PROFIenergy commands: End_Pause Input BOOL I, Q, M, D, L or constant 0: PE command is not supported 2678 1: PE command is supported WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameter Declaration Data type Memory area Query_Modes Input BOOL I, Q, M, D, L or constant PEM_Status Input BOOL I, Q, M, D, L or constant PE_Identify Input BOOL I, Q, M, D, L or constant Query_ Measurement Input BOOL I, Q, M, D, L or constant ACTIVATE InOut BOOL I, Q, M, D, L Description The instruction copies the input parameters to the DATA_ERROR_RSP data area at a rising edge at input ACTIVATE. The parameter is then reset by the instruction. The parameter must be set within 10 seconds after a rising edge is detected at parameter NEW of the "PE_I_DEV (Page 2665)" instruction. VALID InOut BOOL I, Q, M, D, L The parameter must be interconnected with the VALID input of the "PE_I_DEV (Page 2665)" instruction. The auxiliary block sets the parameter as soon as the response data for the PROFIenergy controller is available and ready for transmission. DATA_ ERRORRSP InOut VARIANT D Pointer on the data area in which the response data is stored. The parameter is identical to the pointer for DATA_ERRORRSP of the "PE_I_DEV (Page 2665)" instruction. The addressed data area contains the complete PROFIenergy frame. Minimum length: 244 bytes ERROR Output BOOL I, Q, M, D, L STATUS Output WORD I, Q, M, D, L "0": No error "1": Error occurred. "0": No error "0x80B1": Error in VARIANT setting, e.g. incorrect range You can find additional information on valid data types under "Overview of the valid data types (Page 1204)". PE_Measurement_List_RSP: Generate list of supported measured values as answer Description The auxiliary block "PE_Measurement_List_RSP" generates the response to the command Get_measurement_list (Page 2661). In the response, specify which measured values (Measurement-IDs) are supported. WinCC Basic V13.0 System Manual, 02/2014 2679 Programming the PLC 9.7 References Parameter The following table shows the parameters of the "PE_Measurement_List_RSP" auxiliary block: Parameter Declaration Data type Memory area Description PE_I_DEV_NE W Input BOOL I, Q, M, D, L or constant The parameter must be interconnected with the NEW output parameter of the "PE_I_DEV (Page 2665)" instruction. The auxiliary block is only processed if the parameter value is set to "1". CMD Input INT I, Q, M, D, L or constant Service-Request-ID of the PROFIenergy command The parameter must be interconnected with the CMD output parameter of the "PE_I_DEV (Page 2665)" instruction. CMD_MODIFIE R Input INT I, Q, M, D, L or constant PROFIenergy sub-command (evaluated only if CMD=3, or CMD=16). The parameter must be interconnected with the CMD_MODIFIER output parameter of the "PE_I_DEV" instruction. Count Input BYTE I, Q, M, D, L or constant Number of measured values supported (measurement IDs) Measurement_ List Input VARIANT D Pointer to the array with the Measurement_IDs supported. For information on the structure of the array in accordance with the PROFIenergy profile, see: PI Command "Query_Measurement" "Get_Measurement_list" (Page 2661) ACTIVATE InOut BOOL I, Q, M, D, L The instruction copies the input parameters to the DATA_ERROR_RSP data area at a rising edge at input ACTIVATE. The parameter is then reset by the instruction. The parameter must be set within 10 seconds after a rising edge is detected at parameter NEW of the "PE_I_DEV (Page 2665)" instruction. VALID InOut BOOL I, Q, M, D, L The parameter must be interconnected with the VALID input of the "PE_I_DEV (Page 2665)" instruction. The auxiliary block sets the parameter as soon as the response data for the PROFIenergy controller is available and ready for transmission. DATA_ ERRORRSP InOut VARIANT D Pointer on the data area in which the response data is stored. The parameter is identical to the pointer for DATA_ERRORRSP of the "PE_I_DEV (Page 2665)" instruction. The addressed data area contains the complete PROFIenergy frame. Minimum length: 244 bytes 2680 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameter Declaration Data type Memory area Description ERROR Output BOOL I, Q, M, D, L "0": No error "1": Error occurred. STATUS Output WORD I, Q, M, D, L "0": No error "0x80B1": Error in VARIANT setting, e.g. incorrect range You can find additional information on valid data types under "Overview of the valid data types (Page 1204)". PE_Measurement_Value_RSP: Generate queried measured values as answer Description The auxiliary block "PE_Measurement_Value_RSP" generates the response to the command Get_measurement_values (Page 2663). In the response, return the values of the requested measurements. Parameter The following table shows the parameters of the "PE_Measurement_Value_RSP" auxiliary block: Parameter Declaration Data type Memory area Description PE_I_DEV_NE W Input BOOL I, Q, M, D, L or constant The parameter must be interconnected with the NEW output parameter of the "PE_I_DEV (Page 2665)" instruction. The auxiliary block is only processed if the parameter value is set to "1". CMD Input INT I, Q, M, D, L or constant Service-Request-ID of the PROFIenergy command The parameter must be interconnected with the CMD output parameter of the "PE_I_DEV (Page 2665)" instruction. CMD_MODIFIE R Input INT I, Q, M, D, L or constant PROFIenergy sub-command (evaluated only if CMD=3, or CMD=16). The parameter must be interconnected with the CMD_MODIFIER output parameter of the "PE_I_DEV" instruction. Count Input BYTE I, Q, M, D, L or constant Number of measured values (Measurement_Values). VARIANT D Pointer to the array with the measured values (Measurement_IDs). Measurement_V Input alues For information on the structure of the array in accordance with the PROFIenergy profile, see PI Command "Query_Measurement" "Get_Measurement_values" (Page 2663) WinCC Basic V13.0 System Manual, 02/2014 2681 Programming the PLC 9.7 References Parameter Declaration Data type Memory area Description ACTIVATE InOut BOOL I, Q, M, D, L The instruction copies the input parameters to the DATA_ERROR_RSP data area at a rising edge at input ACTIVATE. The parameter is then reset by the instruction. The parameter must be set within 10 seconds after a rising edge is detected at parameter NEW of the "PE_I_DEV (Page 2665)" instruction. VALID InOut BOOL I, Q, M, D, L The parameter must be interconnected with the VALID input of the "PE_I_DEV (Page 2665)" instruction. The auxiliary block sets the parameter as soon as the response data for the PROFIenergy controller is available and ready for transmission. DATA_ ERRORRSP InOut VARIANT D ERROR Output BOOL I, Q, M, D, L STATUS Output WORD I, Q, M, D, L Pointer on the data area in which the response data is stored. The parameter is identical to the pointer for DATA_ERRORRSP of the "PE_I_DEV (Page 2665)" instruction. The addressed data area contains the complete PROFIenergy frame. Minimum length: 244 bytes "0": No error "1": Error occurred. "0": No error "0x80B1": Error in VARIANT setting, e.g. incorrect range You can find additional information on valid data types under "Overview of the valid data types (Page 1204)". 9.7.3.6 Module parameter assignment Writing and reading data records Principle Some modules have a write-only system data area to which your program can transfer data records. This area contains data records with numbers from 0 to a maximum of 240. Not every module contains all of the data records (see following table). Modules can also have a read-only system data area in which your program can read data records. This area contains data records with numbers from 0 to a maximum of 240. Not every module contains all of the data records (see following table). Note There are modules that have both system data areas. These are physically separate areas and the only thing they have in common is their logical structure. 2682 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Write-only system data area The following table shows the structure of the write-only system data area. This table also shows how the permitted size of the individual data records and which instructions can be used to write them. Data record number Contents Size Can be written with instruction 0 Parameter - WR_DPARM (Page 2690) 1 Parameter - WR_DPARM (Page 2690) 2 to 127 User data Each 240 bytes WR_DPARM (Page 2690) 128 to 240 Parameter Each 240 bytes WR_REC (Page 2600) WR_DPARM (Page 2690) WR_REC (Page 2600) Read-only system data area The following table shows the structure of the read-only system data area. This table also shows the permitted size of the individual data records and which instructions can be used to read them. Data record Contents Size Can be read with instruction 0 Module-specific diagnostics data (set as standard for the entire system) 4 bytes RD_REC (Page 2596) 1 Channel-specific diagnostics data 4 to 220 Bytes RD_REC (Page 2596) number (incl. data record 0) 2 to 127 User data Each 240 bytes RD_REC (Page 2596) 128 to 240 Diagnostics data Each 240 bytes RD_REC (Page 2596) System resources If you start several asynchronous data record transfers one after the other with only short intervals between them, the allocation of system resources by the operating system ensures that all the jobs are executed and that they do not interfere with each other. If the limits of the system resources are reached, this is indicated in RET_VAL. You can remedy this temporary error situation by simply repeating the job. The maximum number of "simultaneously" active jobs of a single instruction type depends on the CPU. WinCC Basic V13.0 System Manual, 02/2014 2683 Programming the PLC 9.7 References RD_DPAR: Read module data record Description You use the instruction to read the data record with the number INDEX of the addressed component from the configured system data. This may be a module in a central rack or a distributed component (PROFIBUS DP or PROFINET IO). The value TRUE for the output parameter VALID indicates that the data record was successfully transferred to the target range RECORD. In this case, the LEN output parameter contains the length of the read data in bytes. If an error has occurred during transfer of the data record, this is indicated by the output parameter ERROR . In this case, the output parameter STATUS contains the error information. Functional description The "RD_DPAR" instruction works asynchronously, that is, its execution extends over multiple calls. You start the data record transfer by calling "RD_DPAR" with REQ = 1. The output parameter BUSY and bytes 2 and 3 of the output parameter STATUS show the status of the job. Bytes 2 and 3 of STATUS match the output parameter RET_VAL of the instructions that operate asynchronously. See also: Meaning of the parameters REQ, RET_VAL and BUSY with asynchronous instructions (Page 1736). The transfer of the data record is complete when the output parameter BUSY has the value FALSE. Parameter The following table shows the parameters of the instruction "RD_DPAR": Parameter Declaration Data type Memory area Description REQ Input BOOL I, Q, M, D, L or constant REQ = 1: Read request LADDR Input HW_IO I, Q, M, D, L or constant Identification number of the CPU or the interface. The number is assigned automatically and is stored in the properties of the CPU or of the interface of the hardware configuration. INDEX Input INT I, Q, M, D, L or constant Data record number RECORD InOut VARIANT I, Q, M, D, L Target range for the read data record VALID Output BOOL I, Q, M, D, L New data record was received and is valid BUSY Output BOOL I, Q, M, D, L BUSY = 1: The job is not yet completed. ERROR Output BOOL I, Q, M, D, L ERROR = 1: An error occurred during the reading process. 2684 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameter Declaration Data type Memory area Description STATUS Output DWORD I, Q, M, D, L Call ID (bytes 2 and 3) or error code Byte 1: B#16#00, if no error. Otherwise function ID from DPV1-PDU: In the case of error for data record reading B#16#DE, in the case of error for data record writing B#16#DF. If no DPV1 protocol element is used: B#16#C0. Byte 4: Manufacturer-specific error ID extension LEN Output INT I, Q, M, D, L Length of the read data record information For additional information on valid data types, refer to "Overview of the valid data types (Page 1204)". STATUS parameter Error code* Explanation Restriction 0000 No error - 7000 First call with REQ=0: No data transfer active; BUSY has the value "0". - (W#16#...) 7001 First call with REQ=1: Data transfer triggered; BUSY has the value "1". Distributed I/O 7002 Intermediate call (REQ irrelevant): Data transfer already active; BUSY has the value "1". Distributed I/O 8090 Address specified at parameter LADDR is invalid. - 8092 A data type other than (Array of) bit string or integer was specified at the RECORD parameter. - 8093 This instruction is not valid for the module selected with LADDR. - 80A1 Negative acknowledgment during sending of data record to module (module defective or unplugged during sending). - 80A2 DP protocol error at layer 2, possible hardware/interface error in DP slave. Distributed I/O 80A3 DP protocol error at user interface/user. Distributed I/O 80A4 Communication problem on com bus. Error occurs between CPU and external DP interface module 80B0 Instruction for module type not possible, or module does not recognize the data record. - 80B1 The length of the data record to be sent is incorrect. - 80B2 The configured slot is not assigned. - 80B3 Actual module type does not correspond to specified module type. - 80C1 The data of the previous write job on the module for the same data record have not yet been processed by the module. - WinCC Basic V13.0 System Manual, 02/2014 2685 Programming the PLC 9.7 References Error code* Explanation Restriction 80C2 The module is currently processing the maximum possible number of jobs for a CPU. - 80C3 The required resources (memory, etc.) are currently occupied. 80C4 Internal temporary error. Job could not be executed. (W#16#...) - Repeat the job. If this error occurs often, check your installation for sources of electrical interference. 80C5 Distributed I/O not available or deactivated. Distributed I/O 80C6 Data record transfer cancelled due to priority class abort (restart or background). Distributed I/O 80D0 There is no entry for the module. - 80D1 The data record number is not configured for the module (data record numbers > 241 are rejected). - 80D2 The module cannot be assigned parameters according to its type identifier. - 80D5 The data record is static. - General error information See also: GET_ERR_ID: Get error ID locally (Page 1964) - * The error codes can be displayed as integer or hexadecimal values in the program editor. For additional information on toggling display formats, refer to "See also". See also RD_DPARM: Read data record from configured system data (Page 2688) RD_DPARA: Read module data record asynchronously Description You use the instruction to read the data record with the number RECNUM of a selected module from the configured system data. The read data record is entered in the target range defined by the parameter RECORD . Functional description The "RD_DPARA" instruction works asynchronously, that is, its execution extends over multiple calls. You start the reading process by calling the instruction with REQ = 1. The output parameters RET_VAL and BUSY indicate the status of the job. See also: Meaning of the parameters REQ, RET_VAL and BUSY with asynchronous instructions (Page 1736). 2686 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameters The following table shows the parameters of the instruction "RD_DPARA": Parameter Declaration Data type Memory area Description REQ Input BOOL I, Q, M, D, L or constant REQ = 1: Read request LADDR Input HW_IO I, Q, M, D, L or constant Identification number of the CPU or the interface. The number is assigned automatically and is stored in the properties of the CPU or of the interface of the hardware configuration. RECNUM Input BYTE I, Q, M, D, L or constant Data record number (permitted values: 0 to 240) RET_VAL Return INT I, Q, M, D, L If an error occurs while the instruction is being executed, the return value contains an error code. If no error occurred during the transmission, the following cases are distinguished: RET_VAL contains the length of the actually read data record in bytes if the target range is larger than the read data record. RET_VAL contains "0" if the length of the read data record is equal to the length of the target range. BUSY Output BOOL I, Q, M, D, L BUSY = 1: The job is not yet completed. RECORD Output VARIANT I, Q, M, D, L Target range for the data record read. For additional information on valid data types, refer to "Overview of the valid data types (Page 1204)". RET_VAL parameter Error code* Explanation Restriction 0000 No error - 7000 First call with REQ=0: No data transfer active; BUSY has the value 0. - 7001 First call with REQ=1: Data transfer triggered; BUSY has the value "1". Distributed I/O 7002 Intermediate call (REQ irrelevant): Data transfer already active; BUSY has the value "1". Distributed I/O 8090 Specified logical base address invalid. - 8092 A data type other than (Array of) bit string or integer was specified at the RECORD parameter. - 8093 This instruction is not valid for the module selected with LADDR. - 80A1 Negative acknowledgment during sending of data record to module (module defective or unplugged during sending). - 80A2 DP protocol error at layer 2, possible hardware/interface error in DP slave. Distributed I/O (W#16#...) WinCC Basic V13.0 System Manual, 02/2014 2687 Programming the PLC 9.7 References Error code* Explanation Restriction 80A3 DP protocol error at user interface/user. Distributed I/O 80A4 Communication on PBUS+ disrupted - 80B0 Instruction for module type not possible, or module does not recognize the data record. - 80B1 The length of the data record to be sent is incorrect. With RD_DPARM (Page 2688): The target range spanned by RECORD is too short. - 80B2 The configured slot is not assigned. - 80B3 Actual module type does not correspond to specified module type. - 80C1 The data of the previous write job on the module for the same data record have not yet been processed by the module. - 80C2 The module is currently processing the maximum possible number of jobs for a CPU. - 80C3 The required resources (memory, etc.) are currently occupied. 80C4 Internal temporary error. Job could not be executed. (W#16#...) - Repeat the job. If this error occurs often, check your installation for sources of electrical interference. 80C5 Distributed I/O not available or deactivated. Distributed I/O 80C6 Data record transfer cancelled due to priority class abort (restart or background). Distributed I/O 80D0 There is no entry for the module. - 80D1 The data record number is not configured for the module (data record numbers > 241 are rejected). - 80D2 The module cannot be assigned parameters according to its type identifier. - 80D5 The data record is static. - General error information See also: GET_ERR_ID: Get error ID locally (Page 1964) - * The error codes can be displayed as integer or hexadecimal values in the program editor. For additional information on toggling display formats, refer to "See also". RD_DPARM: Read data record from configured system data Description You use instruction to read the data record with the number RECNUM of the addressed module from the configured system data. The read data record is entered into the target range spanned by the RECORD parameter. 2688 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameters The following table shows the parameters of the instruction "RD_DPARM": Parameter Declaration Data type Memory area Description IOID Input BYTE I, Q, M, D, L or constant Address area identifier: B#16#54 = Peripheral input (PI) B#16#55 = Peripheral output (PQ) If the module is a mixed module, the area identifier of the lower address must be specified. If the addresses are identical, specify B#16#54. LADDR Input HW_IO I, Q, M, D, L or constant Hardware ID of the CPU or the interface. The number is assigned automatically and is stored in the properties of the CPU or of the interface in the hardware configuration. RECNUM Input BYTE I, Q, M, D, L or constant Data record number (permitted values: 0 to 240) RET_VAL Return INT I, Q, M, D, L Length of the data record read in bytes if the read data record fits in the target range and no error occurred in the transfer. If an error occurs while the instruction is being executed, the return value contains an error code. RECORD Output VARIANT I, Q, M, D, L Target range for the data record read. For additional information on valid data types, refer to "Overview of the valid data types (Page 1204)". RET_VAL parameter Error code* Explanation Restriction 0000 No error - 7000 First call with REQ=0: No data transfer active; BUSY has the value "0". - 7001 First call with REQ=1: Data transfer triggered; BUSY has the value "1". Distributed I/O 7002 Intermediate call (REQ irrelevant): Data transfer already active; BUSY has the value "1". Distributed I/O 8090 Specified logical base address invalid. - 8092 A type other than BYTE is specified in the VARIANT reference at the RECORD parameter. - 8093 This instruction is not valid for the module selected with LADDR. - 80B1 The target range spanned by RECORD is too short. - 80C3 The required resources (memory, etc.) are currently occupied. - 80D0 There is no entry for the module. - (W#16#...) WinCC Basic V13.0 System Manual, 02/2014 2689 Programming the PLC 9.7 References Error code* Explanation Restriction 80D1 The data record number is not configured for the module (data record numbers > 241 are rejected). - 80D2 The module cannot be assigned parameters according to its type identifier. - 80D5 The data record is static. - General error information See also: GET_ERR_ID: Get error ID locally (Page 1964) - (W#16#...) * The error codes can be displayed as integer or hexadecimal values in the program editor. For additional information on toggling display formats, refer to "See also". WR_DPARM: Transfer data record Description You use the instruction "WR_DPARM" to transfer the data record with the number RECNUM from the configuration data to the addressed module. With this instruction, it is irrelevant whether the data record is static or dynamic. Parameters The following table shows the parameters of the instruction "WR_DPARM": Parameter Declaration Data type Memory area Description REQ Input BOOL I, Q, M, D, L REQ = 1: Write request LADDR Input HW_IO I, Q, M, D, L or constant Hardware ID of the CPU or of the interface. The number is assigned automatically and is stored in the properties of the CPU or of the interface in the hardware configuration. RECNUM Input BYTE I, Q, M, D, L or constant Data record number RET_VAL Return INT I, Q, M, D, L If an error occurs while the instruction is being executed, the return value contains an error code. BUSY Output BOOL I, Q, M, D, L BUSY = 1: The writing process is not yet completed. For additional information on valid data types, refer to "Overview of the valid data types (Page 1204)". 2690 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References RET_VAL parameter Error code* Explanation Restriction 0000 No error - 7000 First call with REQ=0: No data transfer active; BUSY has the value 0. - (W#16#...) 7001 First call with REQ=1: Data transfer triggered; BUSY has the value "1". Distributed I/O 7002 Intermediate call (REQ irrelevant): Data transfer already active; BUSY has the value "1". Distributed I/O 8090 Address specified at parameter LADDR is invalid. - 8093 This instruction is not valid for the module selected with LADDR. - 80A1 Negative acknowledgment during sending of data record to module (module defective or unplugged during sending). - 80A2 DP protocol error at layer 2, possible hardware/interface error in DP slave. Distributed I/O 80A3 DP protocol error at user interface/user. Distributed I/O 80A4 Communication on PBUS+ disrupted - 80B0 Instruction for module type not possible, or module does not recognize the data record. - 80B1 The length of the data record to be sent is incorrect. - 80B2 The configured slot is not assigned. - 80B3 Actual module type does not correspond to specified module type. - 80C1 The data of the previous write job on the module for the same data record have not yet been processed by the module. - 80C2 The module is currently processing the maximum possible number of jobs for a CPU. - 80C3 The required resources (memory, etc.) are currently occupied. 80C4 Internal temporary error. Job could not be executed. - Repeat the job. If this error occurs often, check your installation for sources of electrical interference. 80C5 Distributed I/O not available or deactivated. Distributed I/O 80C6 Data record transfer cancelled due to priority class abort (restart or background). Distributed I/O 80D0 There is no entry for the module. - 80D1 The data record number is not configured for the module (data record numbers > 241 are rejected). - 80D2 The module cannot be assigned parameters according to its type identifier. - 80D5 The data record is static. - WinCC Basic V13.0 System Manual, 02/2014 2691 Programming the PLC 9.7 References Error code* Explanation Restriction See also: GET_ERR_ID: Get error ID locally (Page 1964) - (W#16#...) General error information * The error codes can be displayed as integer or hexadecimal values in the program editor. For additional information on toggling display formats, refer to "See also". 9.7.3.7 Interrupts ATTACH: Attach an OB to an interrupt event Description You use the instruction "ATTACH" to assign an organization block (OB) to an event. You enter the symbolic or numeric name of the organization block in the OB_NR parameter. This will then be assigned to the event specified in the EVENT parameter. If the event in the EVENT parameter occurs following error-free execution of the "ATTACH" instruction, the organization block in the OB_NR parameter will be called and its program executed. With the ADD parameter, you specify whether previous assignments of the organization block to other events should be canceled or retained. If the ADD parameter has the value "0", the existing assignments will be replaced by the current assignment. Parameters The following table shows the parameters of the "ATTACH" instruction: Parameter Declaration Data type Memory area Description OB_NR Input OB_ATT I, Q, M, D, L or constant Organization block (numbers up to 32767 are supported.) EVENT Input EVENT_ATT D, L or constant ADD Input BOOL I, Q, M, D, L or constant Effects on previous assignments: Event, e.g., creation of a process event (failure of a hardware module; read hardware ID (16#C0xxyyzz) and query at block) ADD=0 (default): This event replaces all previous event assignments for this OB. ADD=1: This event is added to the previous event assignments for this OB. RET_VAL Return INT I, Q, M, D, L Status of the instruction For additional information on valid data types, refer to "Overview of the valid data types (Page 1204)". 2692 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameter RET_VAL Error code* Description (W#16#....) 0 No error 8090 OB does not exist 8091 OB is incorrect type 8093 Event does not exist * The error codes can be displayed as integer or hexadecimal values in the program editor. For additional information on toggling display formats, refer to "See also". DETACH: Detach an OB from an interrupt event Description You use this instruction to cancel the existing assignment of an organization block to one or more events during runtime. If you have selected a single event, the assignment of the OB to this event will be cancelled. All other currently existing assignments remain active. You can select an individual event using the drop-down list of the operand placeholder at the EVENT parameter. If you have not selected an event, all currently existing assignments of the organization block to events will be canceled. You enter the symbolic or numeric name of the organization block in the OB_NR parameter. The assignment of this organization block to the event specified in the EVENT parameter will then be canceled. Parameters The following table shows the parameters of the "DETACH" instruction: Parameters Declaration Data type Memory area Description OB_NR Input OB_ATT I, Q, M, D, L or constant Organization block (numbers up to 32767 are supported.) EVENT Input EVENT_ATT D, L or constant Event RET_VAL Return INT I, Q, M, D, L Status of the instruction For additional information on valid data types, refer to "Overview of the valid data types (Page 1204)". WinCC Basic V13.0 System Manual, 02/2014 2693 Programming the PLC 9.7 References Parameter RET_VAL Error code* Description (W#16#....) 0 No error 1 No assignment exists (warning) 8090 OB does not exist 8091 OB has incorrect type 8093 Event does not exist * The error codes can be displayed as integer or hexadecimal values in the program editor. For additional information on toggling display formats, refer to "See also". Cyclic interrupt SET_CINT: Set cyclic interrupt parameters Description You use this instruction to set the parameters for a cyclic interrupt OB. The start time for a cyclic interrupt OB is generated from the respective time interval of the OB and the phase offset. The time interval of an OB is the interval at which the OB is periodically called. For example, if the time interval is 100 s, the OB will be called every 100 s during program execution. The phase offset is a time interval by which the call of a cyclic interrupt OB is offset. You can use the phase offset to process low priority organization blocks in a precise time base. If the OB does not exist or if the time interval used is not supported, a corresponding error alarm is output in the RET_VAL parameter. A time interval in the CYCLE parameter of "0" means that the OB will not be called. Functional description If a lower priority OB and a higher priority OB are called in the same time interval, the lower priority OB will only be called once the higher priority OB has been executed. The call time for 2694 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References the lower priority OB can be offset according to the length of time to execute the higher-priority OB. 2%FDOOZLWKRXWSKDVHRIIVHW 581 W W W W W W W W 2% +LJKHUSULRULW\ 2% /RZHUSULRULW\ If a phase offset is configured for the lower priority OB and the phase offset is greater than the current execution time of the respective higher priority OB, then the block will be called in a fixed time base. 2%FDOOZLWKSKDVHRIIVHW 581 W W W W W W W 2% +LJKHUSULRULW\ W 2% /RZHUSULRULW\ 3KDVHRIIVHW Parameters The following table shows the parameters of the "SET_CINT" instruction: Parameter Declaration Data type Memory area Description OB_NR Input OB_CYCLIC I, Q, M, D, L or constant OB number (<32768) CYCLE Input UDINT I, Q, M, D, L or constant Time interval in microseconds PHASE Input UDINT I, Q, M, D, L or constant Phase offset RET_VAL Return INT I, Q, M, D, L Status of the instruction For additional information on valid data types, refer to "Overview of the valid data types (Page 1204)". WinCC Basic V13.0 System Manual, 02/2014 2695 Programming the PLC 9.7 References Parameter RET_VAL Error code* Description (W#16#....) 0 No error 8090 OB does not exist or is of the wrong type 8091 Incorrect time interval 8092 Incorrect phase offset 80B2 No event assigned to OB * The error codes can be displayed as integer or hexadecimal values in the program editor. For additional information on toggling display formats, refer to "See also". QRY_CINT: Query cyclic interrupt parameters Description You can use this instruction to query the current parameters of a cyclic interrupt OB. The cyclic interrupt OB is identified using the OB_NR parameter. The values of the queried cyclic interrupt parameters correspond to those at the time the "QRY_CINT" instruction is executed. Parameters The following table shows the parameters of the "QRY_CINT" instruction: Parameter Declaration Data type Memory area Description OB_NR Input OB_CYCLIC (INT) I, Q, M, D, L or constant OB number (<32768) or symbolic addressing via the name of the OB (e.g. OB_MyOB) CYCLE Output UDINT I, Q, M, D, L Time interval in microseconds PHASE Output UDINT I, Q, M, D, L Phase offset STATUS Output WORD I, Q, M, D, L Status of the cyclic interrupt: Bit 0 to bit 4: see parameter STATUS Other bits: Always "0" RET_VAL Return INT I, Q, M, D, L Status of the instruction For additional information on valid data types, refer to "Overview of the valid data types (Page 1204)". Parameter STATUS Bit Value Meaning 0 0 Not used (always "0"). 1 0 The cyclic interrupt is enabled. 2696 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Bit 2 Value Meaning 1 The cyclic interrupt is delayed. 0 The cyclic interrupt is not enabled or has expired. 1 The cyclic interrupt is enabled. 3 0 Not used (always "0"). 4 0 An OB with the specified number does not exist. 1 An OB with the specified number exists. Other bits Not used (always "0"). Parameter RET_VAL If an error occurs, the relevant error code will be displayed in the RET_VAL parameter and the STATUS parameter is set to "0". Error code* Description (W#16#....) 0 No error. 8090 OB does not exist or is of the wrong type 80B2 No result assigned to OB. * The error codes can be displayed as integer or hexadecimal values in the program editor. For additional information on toggling display formats, refer to "See also". Time-of-day interrupt SET_TINT: Set time-of-day interrupt Description The instruction "SET_TINT" is used to set the start data and time of the time-of-day interrupt organization blocks from the user program, without having to make settings in the hardware configuration. Enter the number of the time-of-day interrupt-OBs at the parameter OB_NR for which you would like to set the start date and the time-of-day. Use the parameter SDT and PERIOD to specify when and how often the time-of-day interrupt OB should be called: - One-time call: Enter at the parameter SDT the date and the time-of-day and use the value "0" at the parameter PERIOD. - Repeated call: Enter the date and the time-of-day of the first call at the parameter SDT. Use the parameter PERIOD to define the time interval in which subsequent calls of the OBs should take place. Observe the following when setting the start date and start time: WinCC Basic V13.0 System Manual, 02/2014 2697 Programming the PLC 9.7 References The date and the time-of-day specification at the parameter SDT refers to the system time. The seconds and milliseconds specification is ignored and set to "0" at the start time. Only the starting date days 1, 2, ... 28 are possible if you want to specify a monthly time-ofday interrupt OBs. This restriction prevents skipping the monthly call (e.g. 30-day months or in February). The setting "end of the month" (W#16#2001) can be used at the parameter PERIOD as an alternative to the 29th 30th and the 31st of the month. After setting the time-of-day interrupt with "SET_TINT" it still must be activated with the instruction "ACT_TINT". Note Additional information about time-of-day interrupt OBs Other special features for the use of time-of-day interrupt OBs can be found in the descriptions of the organization blocks of the respective CPU: For the S7-1200: Auto-Hotspot For the S7-1500: Auto-Hotspot The settings at the parameters SDT and PERIOD coincide with the settings for time-of-day interrupt in the properties of the time-of-day interrupt OBs. Parameters The following table shows the parameters of the "SET_TINT" instruction: Parameters Declaration Data type Memory area Description OB_NR Input OB_TOD I, Q, M, D, L or constant Number of the time-of-day interrupt OBs The numbers 10 to 17 are available for the time-of-day interrupt OBs. An OB number starting with 123 can also be assigned as an alternative. The OB number is displayed in the program block folder and in the system constants. SDT 2698 Input DT D, L or constant Start date and start time WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameters Declaration Data type Memory area Description PERIOD Input WORD I, Q, M, D, L or constant Execution intervals from the starting point SDT to: W#16#0000 = single execution W#16#0201 = once every minute W#16#0401 = once hourly W#16#1001 = once daily W#16#1201 = once weekly W#16#1401 = once monthly W#16#1801 = once yearly W#16#2001 = at month's end RET_VAL Return INT I, Q, M, D, L If an error occurs during execution of the instruction, the actual parameter of RET_VAL contains an error code. You can find additional information on valid data types under "Overview of the valid data types (Page 1204)". RET_VAL parameter Error code* Description (W#16#...) 0000 No error occurred. 8090 Error at the parameter OB_NR (no time-of-day interrupt OB addressed). 8091 Error at the parameter SDT (invalid date and time-of-day specification). 8092 Incorrect input at the parameter PERIOD. 80A1 The set start time is in the past. This error code only occurs at PERIOD = W#16#0000. General error information See also: GET_ERR_ID: Get error ID locally (Page 1964) * The error codes can be displayed as integer or hexadecimal values in the program editor. For additional information on toggling display formats, refer to "See also". See also ACT_TINT: Enable time-of-day interrupt (Page 2703) WinCC Basic V13.0 System Manual, 02/2014 2699 Programming the PLC 9.7 References SET_TINTL: Set time-of-day interrupt Description The instruction "SET_TINTL" is used to set the start data and time of the time-of-day interrupt organization blocks from the user program, without having to make settings in the hardware configuration. Enter the number of the time-of-day interrupt-OBs at the parameter OB_NR for which you would like to set the start date and the time-of-day. Use the parameter SDT and PERIOD to specify when and how often the time-of-day interrupt OB should be called: - One-time call: Enter at the parameter SDT the date and the time-of-day and use the value "0" at the parameter PERIOD. - Repeated call: Enter the date and the time-of-day of the first call at the parameter SDT. Use the parameter PERIOD to define the time interval in which subsequent calls of the OBs should take place. Use the parameter LOCAL to select whether the time specified at the parameter SDT refers to the local time or the system time. With the ACTIVATE parameter, you specify whether the settings made for the organization block are to be applied directly (ACTIVATE = true) or only after "ACT_TINT (Page 2703)" for the time-of-day interrupt organization block is called (ACTIVATE = false). Observe the following when setting the start date and start time: The seconds and milliseconds specification is ignored and set to "0" at the start time. Only the starting date days 1, 2, ... 28 are possible if you want to specify a monthly time-ofday interrupt OBs. This restriction prevents skipping the monthly call (e.g. 30-day months or in February). The setting "end of the month" (W#16#2001) can be used at the parameter PERIOD as an alternative to the 29th 30th and the 31st of the month. Please observe the following during the use of local time: Changeover from daylight saving to standard time: When calling time-of-day interrupt organization blocks with a start time within the second hour during changeover from daylight saving time to standard time, also use a time-delay interrupt during the first hour of the time changeover. Changeover from standard to daylight saving time: If you specify the skipped hour as the time-of-day for the daylight saving time changeover day, the error code 16#8091 will be output at a single execution (PERIOD = W#16#0000). 2700 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Note Additional information about time-of-day interrupt OBs Other special features for the use of time-of-day interrupt OBs can be found in the descriptions of the organization blocks of the respective CPU: For the S7-1200: Auto-Hotspot For the S7-1500: Auto-Hotspot The settings at the parameters SDT and PERIOD coincide with the settings for time-of-day interrupt in the properties of the time-of-day interrupt OBs. Parameters The following table shows the parameters of the "SET_TINTL" instruction: Parameters Declaration Data type Memory area Description OB_NR Input OB_TOD I, Q, M, D, L or constant Number of the time-of-day interrupt OBs The numbers 10 to 17 are available for the time-of-day interrupt OBs. An OB number starting with 123 can also be assigned as an alternative. The OB number is displayed in the program block folder and in the system constants. SDT Input DTL D, L or constant Start date and start time LOCAL Input BOOL I, Q, M, D, L or constant true: Use local time I, Q, M, D, L or constant Execution intervals from the starting point SDT to: PERIOD Input WORD false: Use system time W#16#0000 = single execution W#16#0201 = Once every minute W#16#0401 = once hourly W#16#1001 = once daily W#16#1201 = once weekly W#16#1401 = once monthly W#16#1801 = once yearly W#16#2001 = at month's end ACTIVATE Input BOOL I, Q, M, D, L or constant true: set and activate the time-of-day interrupt false: set the time-of-day interrupt and only activate at call of "ACT_TINT (Page 2703)" RET_VAL Return INT I, Q, M, D, L If an error occurs during execution of the instruction, the actual parameter of RET_VAL contains an error code. You can find additional information on valid data types under "Overview of the valid data types (Page 1204)". WinCC Basic V13.0 System Manual, 02/2014 2701 Programming the PLC 9.7 References RET_VAL parameter Error code* Description (W#16#...) 0000 No error occurred. 8090 Error at the parameter OB_NR (no time-of-day interrupt OB addressed). 8091 Error at the parameter SDT (invalid date and time-of-day specification). 8092 Incorrect input at the parameter PERIOD. 80A1 The set start time is in the past. This error code only occurs at PERIOD = W#16#0000. General error information See also: GET_ERR_ID: Get error ID locally (Page 1964) * The error codes can be displayed as integer or hexadecimal values in the program editor. For additional information on toggling display formats, refer to "See also". CAN_TINT: Cancel time-of-day interrupt Description The instruction "CAN_TINT" is used to delete the start data and start time of a specified timeof-day interrupt organization block. This deactivates the time-of-day interrupt, and the organization block is no longer called. If you want to reuse the time-of-day interrupt, the start time must be reset (instruction "SET_TINTL (Page 2700)" or "SET_TINT (Page 2697)"). Thereafter, you must reactivate the time-of-day interrupt: If you use the instruction "SET_TINT (Page 2697)" or "SET_TINTL (Page 2700)" with parameter ACTIVE=false to set the time-of-day interrupt, call "ACT_TINT (Page 2703)". By using the instruction "SET_TINTL (Page 2700)" you can also activate the time-of-day interrupt directly with the parameter ACTIVE=true. Parameters The following table shows the parameters of the instruction "CAN_TINT": Parameters Declaration Data type Memory area OB_NR Input OB_TOD I, Q, M, D, L or constant Number of the time-of-day interrupt OB, whose starting date and time-of-day are to be deleted. Description RET_VAL Return INT I, Q, M, D, L If an error occurs during execution of the instruction, the actual parameter of RET_VAL contains an error code. For additional information on valid data types, refer to "Overview of the valid data types (Page 1204)". 2702 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameter RET_VAL Error code* Description (W#16#...) 0000 No error occurred. 8090 Error at the parameter OB_NR. 80A0 No starting date/time-of-day defined for the affected time-of-day interrupt OB. General error information See also: GET_ERR_ID: Get error ID locally (Page 1964) * The error codes can be displayed as integer or hexadecimal values in the program editor. For additional information on toggling display formats, refer to "See also". ACT_TINT: Enable time-of-day interrupt Description With the instruction "ACT_TINT" you can activate a time-of-day interrupt organization block from the user program. A prerequisite for the execution of the instruction is that the starting date and time-of-day are already set for the time-of-day interrupt OB. Parameters The following table shows the parameters of the instruction "ACT_TINT": Parameters Declaration Data type Memory area Description OB_NR Input OB_TOD I, Q, M, D, L or constant Number of the time-of-day interrupt OBs The numbers 10 to 17 are available for the time-of-day interrupt OBs. An OB number starting with 123 can also be assigned as an alternative. The OB number is displayed in the program block folder and in the system constants. RET_VAL Return INT I, Q, M, D, L If an error occurs during execution of the instruction, the actual parameter of RET_VAL contains an error code. For additional information on valid data types, refer to "Overview of the valid data types (Page 1204)". Parameter RET_VAL Error code* Description (W#16#...) 0000 No error occurred. 8090 Error at the parameter OB_NR (no time-of-day interrupt OB addressed). WinCC Basic V13.0 System Manual, 02/2014 2703 Programming the PLC 9.7 References Error code* Description (W#16#...) 80A0 Start date and time-of day not set for the relevant time-of-day interrupt OB. 80A1 The activated time is in the past. The error only occurs if the time-of-day interrupt is only to be executed once. General error information See also: GET_ERR_ID: Get error ID locally (Page 1964) * The error codes can be displayed as integer or hexadecimal values in the program editor. For additional information on toggling display formats, refer to "See also". QRY_TINT: Query status of time-of-day interrupt Description You can use this instruction to display the status of a time-of-day interrupt organization block in the STATUS output parameter. Parameters The following table shows the parameters of the "QRY_TINT" instruction: Parameters Declaration Data type Memory area Description OB_NR Input OB_TOD I, Q, M, D, L or constant Number of the time-of-day interrupt OB whose status is queried The OB number is displayed in the program block folder and in the system constants. RET_VAL Return INT I, Q, M, D, L If an error occurs during execution of the instruction, the actual parameter of RET_VAL contains an error code. STATUS Output WORD I, Q, M, D, L Status of the time-of-day interrupt (see below) For additional information on valid data types, refer to "Overview of the valid data types (Page 1204)". Parameter RET_VAL Error code* Description (W#16#...) 0000 No error occurred. Exception: Status message "0" on bit 4 (no OB with this number created). 8090 Error at the parameter OB_NR. Possible causes: The value at the parameter OB_NR is not an OB number (<1 or > 32767) supported by the CPU. The OB number does not address a time-of-day interrupt OB. 2704 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Error code* Description (W#16#...) General error information See also: GET_ERR_ID: Get error ID locally (Page 1964) * The error codes can be displayed as integer or hexadecimal values in the program editor. For additional information on toggling display formats, refer to "See also". Parameter STATUS If an error occurs (see RET_VAL parameter), "0" is output in the STATUS parameter. Bit Value Meaning 0 0 In Run. 1 During startup. 0 The time-of-day interrupt is enabled. 1 The time-of-day interrupt is disabled. 0 Time-of-day interrupt is not activated or has elapsed. 1 The time-of-day interrupt is activated. 0 An OB with an OB number as specified at OB_NR parameter does not exist. 1 An OB with an OB number as specified at OB_NR parameter does exist. 0 The time-of-day interrupt is based on the system time 1 The time-of-day interrupt is based on the local time 1 2 4 6 Other Always "0" Time-delay interrupt Using time-delay interrupts Definition After you have called the "SRT_DINT (Page 2707)" instruction, the operating system generates an interrupt after the specified delay time has elapsed, in other words, the assigned time-delay interrupt OB is called. Prerequisites for the call Before a time-delay interrupt can be called by the operating system, the following conditions must be met: The time-delay interrupt OB must be started by the "SRT_DINT (Page 2707)" instruction. The time-delay interrupt OB must not be deselected during configuration. The time-delay interrupt OB must exist in the CPU. WinCC Basic V13.0 System Manual, 02/2014 2705 Programming the PLC 9.7 References Purpose of the instructions "SRT_DINT", "CAN_DINT" and "QRY_DINT" You use the instructions to Start time-delay interrupts ("SRT_DINT (Page 2707)") Cancel time-delay interrupts ("CAN_DINT (Page 2708)") Query time-delay interrupts ("QRY_DINT (Page 2708)") Effects on the time-delay interrupt The following table lists a number of different situations and explains the effect they have on a time-delay interrupt. If ... and ... Then ... A time-delay interrupt is started (by calling "SRT_DINT (Page 2707)") The time-delay interrupt has already started, The delay time is overwritten; the time-delay interrupt is started again. The time-delay interrupt OB does not exist at the time of the call, The operating system generates a priority class error (calls OB 85). If OB 85 does not exist, the CPU changes to STOP. The interrupt is started in a startup OB and the delay time elapses before the CPU changes to RUN, The call of the time-delay interrupt OB is delayed until the CPU is in RUN mode. The delay time has elapsed, A previously started timedelay interrupt OB is still being executed, The operating system generates a time error (calls OB 80). If OB 80 does not exist, the CPU changes to STOP. Response to warm restart and cold restart During a warm restart or a cold restart, all the time-delay interrupt settings made in the user program by means of instructions are cleared. Starting in a startup OB A time-delay interrupt can be started in a startup OB. Two conditions must be satisfied to call the time-delay OB: The delay time must have elapsed. The CPU must be in the RUN mode. If the delay time has elapsed and the CPU is not yet in the RUN mode, the time-delay interrupt OB call is delayed until the CPU is in RUN mode. The time-delay interrupt OB is then called before the first instruction in OB Main [OB 1] is executed. 2706 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References SRT_DINT: Start time-delay interrupt Description The instruction "SRT_DINT" is used to start a time-delay interrupt, which calls a time-delay interrupt OB after the expiry of the delay time specified at the parameter DTIME. The delay time is started when a negative edge is generated in the EN enable input. The signal state of enable input EN must be "0" during delay time countdown. If the delay time countdown is interrupted, the OB configured in the OB_NR parameter is not executed. Accuracy The maximum time between the call of the "SRT_DINT" instruction and the start of the timedelay interrupt OB is one millisecond longer than the configured delay time, provided that no interruption events delay the call. Parameters The following table shows the parameters of the instruction "SRT_DINT": Parameter Declaration Data type Memory area OB_NR Input OB_DELAY (INT) I, Q, M, D, L or constant Number of the OB to be executed after a delay time Description DTIME Input TIME I, Q, M, D, L or constant Delay time (1 to 60000 ms) You can realize longer times, for example, by using a counter in a time-delay interrupt OB. SIGN Input WORD I, Q, M, D, L or constant Identifier that appears when the timedelay interrupt OB is called in the start event information of the OB. RET_VAL Return INT I, Q, M, D, L Status of the instruction For additional information on valid data types, refer to "Overview of the valid data types (Page 1204)". Parameter RET_VAL Error code* Description (W#16#...) 0000 No error 8090 Incorrect parameter OB_NR 8091 Incorrect parameter DTIME General error information See also: GET_ERR_ID: Get error ID locally (Page 1964) * The error codes can be displayed as integer or hexadecimal values in the program editor. For additional information on toggling display formats, refer to "See also". WinCC Basic V13.0 System Manual, 02/2014 2707 Programming the PLC 9.7 References CAN_DINT: Cancel time-delay interrupt Description You use this instruction to cancel a started time-delay interrupt and, thus, also cancel the call of the time delay interrupt OB that is to be executed after the configured delay time. You specify the number of the organization block whose call is to be canceled in the OB_NR parameter. Parameters The following table shows the parameters of the "CAN_DINT" instruction: Parameter Declaration Data type Memory area Description OB_NR Input OB_DELAY (INT) I, Q, M, D, L or constant Number of the OB whose call will be canceled RET_VAL Return INT I, Q, M, D, L Status of the instruction For additional information on valid data types, refer to "Overview of the valid data types (Page 1204)". Parameter RET_VAL Error code* Description (W#16#...) 0000 No error 8090 Incorrect parameter OB_NR 80A0 Time-delay interrupt has not started. * The error codes can be displayed as integer or hexadecimal values in the program editor. For additional information on toggling display formats, refer to "See also". QRY_DINT: Query time-delay interrupt status Description The instruction "QRY_DINT" is used to query the status of the time-delay interrupt. 2708 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameters The following table shows the parameters of the instruction "QRY_DINT": Parameter Declaration Data type Memory area Description OB_NR Input OB_DELAY (INT) I, Q, M, D, L or constant Number of the OB whose status is being queried. RET_VAL Return INT I, Q, M, D, L If an error occurs during execution of the instruction, the actual parameter of RET_VAL contains an error code. The value "0" is displayed in the STATUS parameter. STATUS Output WORD I, Q, M, D, L Status of the time-delay interrupt, see following table. For additional information on valid data types, refer to "Overview of the valid data types (Page 1204)". Parameter STATUS Bit Value Meaning 0 0 Operating system in RUN 1 Operating system in startup 0 Time-delay interrupt is enabled by the operating system. 1 Time-delay interrupt is disabled. 0 Time-delay interrupt is not activated or has elapsed. 1 2 1 Time-delay interrupt is activated. 3 - - 4 0 Time-delay interrupt OB with the specified number does not exist. 1 Time-delay interrupt OB with the specified number exists. Other bits Always "0" Parameter RET_VAL Error code* Description (W#16#...) 0000 No error occurred. 8090 Incorrect information in the OB_NR parameter General error information See also: GET_ERR_ID: Get error ID locally (Page 1964) * The error codes can be displayed as integer or hexadecimal values in the program editor. For additional information on toggling display formats, refer to "See also". WinCC Basic V13.0 System Manual, 02/2014 2709 Programming the PLC 9.7 References Synchronous errors Mask synchronous error events Introduction Synchronous errors are programming and access errors. Such errors occur as a result of programming with incorrect operand areas or numbers, or incorrect addresses. Masking these synchronous errors means the following: Masked synchronous errors do not trigger an error OB call and do not lead to a programmed alternative reaction. The CPU "records" the masked errors that have occurred in an error status register. Masking is carried out by calling the "MSK_FLT (Page 2715)" instruction. Unmasking errors means canceling a previously set mask and clearing the corresponding bit in the event status register of the current priority class. Masking is canceled as follows: By calling the "DMSK_FLT (Page 2716)" instruction. Once the current priority class has been completed. If an error event occurs after it has been unmasked, then the operating system will start the associated error OB. You can use the "READ_ERR (Page 2717)" instruction to read the masked errors that have occurred. Note Regardless of masking or unmasking of the error events for the S7-1500, the error event is entered in the diagnostic buffer and the group error LED of the CPU lights up. 2710 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Handling errors in general Different actions are possible if programming and I/O area access errors occur in a user program: You can program an error OB that is called by the operating system when the corresponding error occurs. You can disable the error OB call individually for each priority class. In this case, the CPU does not change to STOP when an error of this type occurs in the particular priority class. The CPU enters the error in an error register. From this entry, however, you cannot recognize when or how often the error occurred. 6\QFKURQRXVHUURU 1R (UURUPDVNHG" <HV &DOORIDQHUURU2% &38 VZLWFKHVWR6723LIWKH HUURU2%LVQRWSURJUDP PHG %ORFNLQJWKHFDOORIDQ HUURU2% &38GRHVQRW VZLWFKWR6723ZKHQDQ HUURURFFXUV 7KHGHVLUHGUHVSRQVHWR DQHUURULVSURJUDPPHGLQ WKH2% $QHUURUHYHQWLVUHFRUGHG LQWKHHYHQWVWDWXV UHJLVWHU Synchronous errors are assigned to a particular bit pattern known as the error filter. You can find this error filter in the input and output parameters of the "MSK_FLT (Page 2715)", "DMSK_FLT (Page 2716)", and "READ_ERR (Page 2717)" instructions. Synchronous errors are divided into programming and access errors which you can mask in two error masks. The error filters are illustrated in the following figures. WinCC Basic V13.0 System Manual, 02/2014 2711 Programming the PLC 9.7 References Programming error filter The following figure shows the bit pattern of the error filter for programming errors. The error filter for the programming errors is available in the "PRGFLT_..." parameters (see below "Programming errors, Low-Word" or "Programming errors, High-Word"). %LWQR ; ; ; ; ; ; ; %&'FRQYHUVLRQHUURU $UHDOHQJWKHUURUZKHQUHDGLQJ $UHDOHQJWKHUURUZKHQZULWLQJ 5DQJHHUURUZKHQUHDGLQJ 5DQJHHUURUZKHQZULWLQJ 7LPHUQXPEHUHUURU &RXQWHUQXPEHUHUURU $OLJQPHQWHUURUZKHQUHDGLQJ $OLJQPHQWHUURUZKHQZULWLQJ %LWQR ; ; ; ; ; :ULWHHUURUGDWDEORFN :ULWHHUURULQVWDQFHGDWDEORFN %ORFNQXPEHUHUURU'% %ORFNQXPEHUHUURU', %ORFNQXPEHUHUURU)& %ORFNQXPEHUHUURU)% '%QRWORDGHG )&QRWORDGHG 6)&QRWORDGHG )%QRWORDGHG 6)%QRWORDGHG /HJHQG ; 1RWUHOHYDQW The non-relevant bits "x" are set to "0" for the input and output parameters of the instructions "MSK_FLT (Page 2715)", "DMSK_FLT (Page 2716)", "READ_ERR (Page 2717)". 2712 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Access error mask The following figure shows the bit pattern of the error mask for access errors. The error mask for access errors is located in the parameters ACCFLT_... /RZ ZRUG %LWQR ; ; ; ; ; ; ; ; ; ; ; ; ; ; ,2DFFHVVHUURUZKHQUHDGLQJ ,2DFFHVVHUURUZKHQZULWLQJ +LJK ZRUG /HJHQG %LWQR ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; 1RWUHOHYDQW Example: The following figure shows how the low word of the error mask for access errors appears with all masked errors. As input parameters for "MSK_FLT (Page 2715)" As output parameters for "MSK_FLT (Page 2715)" ,QSXW SDUDPHWHU %LWQR 0DVNHGHUURUV 2XWSXW SDUDPHWHU /HJHQG WinCC Basic V13.0 System Manual, 02/2014 %LWQR ; ; ; ; ; ; ; ; ; ; ; ; ; ; 0DVNHGHUURUV ; 1RWUHOHYDQW 1RWPDVNHG 0DVNHG 2713 Programming the PLC 9.7 References Programming error low word The following table lists the errors assigned to the low word of the error filter for programming errors. The possible causes of the errors are also listed. Error Event ID (W#16#...) Possible cause of error BCD conversion error 2521 The value to be converted is not a BCD number (e.g. 5E8). Area length error when reading 2522 An addressed operand is not located entirely within the possible operand range. Example: MW 320 should be read although the memory area is only 256 bytes long. Area length error when writing 2523 An addressed operand is not located entirely within the possible operand range. Example: A value should be written to MW 320 although the memory area is only 256 bytes long. Range error when reading 2524 An incorrect range identifier for the operand was specified during indirect, overlapping range addressing. Example: Correct: LAR1 P#E 12.0 L W[AR1, P#0.0] Incorrect: LAR1 P#12.0 L W[AR1, P#0.0] The range error is reported during this operation. Range error when writing 2525 An incorrect range identifier for the operand was specified during indirect, overlapping range addressing. Example: Correct: LAR1 P#E 12.0 T W[AR1, P#0.0] Incorrect: LAR1 P#12.0 T W[AR1, P#0.0] The range error is reported during this operation. Timer number error 2526 A non-existent timer is accessed. Example: SI T [MW 0] with MW 0 = 129; the timer 129 should be started although there are only 128 timers available. Counter number error 2527 A non-existent counter is accessed. Example: ZV Z [MW 0] with MW 0 = 600; the counter 600 is accessed although only 512 counters are available. Alignment error when reading 2528 A byte, word or double word operand with a bit address 0 is addressed. Example: Correct: LAR1 P#M12.0 L B[AR1, P#0.0] Incorrect: LAR1 P#M12.4 L B[AR1, P#0.0] Alignment error when writing 2529 A byte, word or double word operand with a bit address 0 is addressed. Example: Correct: LAR1 P#M12.0 T B[AR1, P#0.0] Incorrect: LAR1 P#M12.4 T B[AR1, P#0.0] 2714 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Programming error high word The following table lists the errors assigned to the high word of the error filter for programming errors. The possible causes of the errors are also listed. Error Event ID (W#16#...) Possible cause of error Write error data block 2530 The data block to be written to is write-protected. Write error instance data block 2531 The instance data block to be written to is write-protected. Block number error DB 2532 The number of the data block is greater than the highest permissible number. Block number error DI 2533 The number of the instance data block is greater than the highest permissible number. Block number error FC 2534 The number of a called function (FC) is greater than the highest permissible number. Block number error FB 2535 The number of a called function block (FB) is greater than the highest permissible number. DB not loaded 253A The data block is not loaded. Instruction not loaded 253C to 253F The instruction to be called is not loaded. Access error The following table contains the errors that are assigned to the error mask for access errors. The possible causes of the errors are also listed. Error Event ID (W#16#...) Possible cause of error I/O access error when reading 2942 The address in the I/O area has no assigned signal module. I/O access error when writing 2943 Access to this I/O area was not acknowledged within the specified module monitoring time (timeout). MSK_FLT: Mask synchronous error events Description You use the instruction to control the reaction of the CPU to synchronous errors. This is done by masking the respective synchronous errors (for error filters, see Mask synchronous error events (Page 2710)). When you call "MSK_FLT", you mask the synchronous errors in the current priority class. If you set individual bits of the synchronous error filter to "1" in the input parameters, other bits that were set previously retain their value of "1". You obtain new error filters that you can read out using the output parameters. The synchronous errors you have masked do not call an OB but are simply entered in an error register. You can read the error register with the "READ_ERR (Page 2717)" instruction. WinCC Basic V13.0 System Manual, 02/2014 2715 Programming the PLC 9.7 References Parameters The following table shows the parameters of the instruction "MSK_FLT": Parameter Declaration Data type Memory area PRGFLT_SET_MASK Input DWORD I, Q, M, D, L or constant Programming error to be masked Description ACCFLT_SET_MASK Input DWORD I, Q, M, D, L or constant Access error to be masked RET_VAL Return INT I, Q, M, D, L Error information PRGFLT_MASKED Output DWORD I, Q, M, D, L Masked programming errors ACCFLT_MASKED Output DWORD I, Q, M, D, L Masked access errors You will find more detailed information on valid data types in "Overview of the valid data types (Page 1204)". Parameter RET_VAL Error code* Description (W#16#...) 0000 None of the errors were already masked. 0001 At least one of the errors was already masked. Nevertheless the other errors will be masked. - General error information See also: Getting error ID locally with GetErrorID (Page 2462) * The error codes can be displayed as integer or hexadecimal values in the program editor. For additional information on toggling display formats, refer to "See also". See also Evaluating errors with output parameter RET_VAL (Page 1738) DMSK_FLT: Unmask synchronous error events Description You use the instruction to unmask the errors masked with "MSK_FLT (Page 2715)". To do this, you must set the corresponding bits of the error filter to "1" in the input parameters. With the "DMSK_FLT" call, you unmask the corresponding synchronous errors of the current priority class. At the same time, the queried entries are cleared in the error register. You can read out the new error filters using the output parameters. 2716 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameters The following table shows the parameters of the instruction "DMSK_FLT": Parameter Data type Memory area PRGFLT_RESET_ Input MASK Declaration DWORD I, Q, M, D, L or constant Programming errors to be unmasked Description ACCFLT_RESET_ MASK Input DWORD I, Q, M, D, L or constant Access errors to be unmasked RET_VAL Return INT I, Q, M, D, L Error information PRGFLT_MASKE D Output DWORD I, Q, M, D, L Still masked programming errors ACCFLT_MASKE D Output DWORD I, Q, M, D, L Still masked access errors You will find more detailed information on valid data types in "Overview of the valid data types (Page 1204)". Parameter RET_VAL Error code* (W#16#...) Description 0000 All specified errors were unmasked. 0001 At least one of the errors was not masked. Nevertheless the other errors will be unmasked. - General error information See also: GET_ERR_ID: Get error ID locally (Page 2462) * The error codes can be displayed as integer or hexadecimal values in the program editor. For additional information on toggling display formats, refer to "See also". READ_ERR: Read out event status register Description You use the instruction to read the error register. The structure of the error register corresponds to that of the programming and access error filters, which you can program as input parameters with "MSK_FLT (Page 2715)" and "DMSK_FLT (Page 2716)". In the input parameters, you enter the synchronous errors you want to read from the error register. When you call "READ_ERR", you read the required entries from the error register and at the same time clear these entries. The error register contains information that tells you which of the masked synchronous errors in the current priority class occurred at least once. If a bit is set, this means that the corresponding masked synchronous error occurred at least once. WinCC Basic V13.0 System Manual, 02/2014 2717 Programming the PLC 9.7 References Parameters The following table shows the parameters of the instruction "READ_ERR": Parameter Declaration Data type Memory area PRGFLT_QUERY Input DWORD I, Q, M, D, L or constant Query programming error Description ACCFLT_QUERY Input DWORD I, Q, M, D, L or constant Query access error RET_VAL Return INT I, Q, M, D, L Error information PRGFLT_CLR Output DWORD I, Q, M, D, L Programming errors that occurred ACCFLT_CLR Output DWORD I, Q, M, D, L Access errors that occurred You will find more detailed information on valid data types in "Overview of the valid data types (Page 1204)". Parameter RET_VAL Error code* Description (W#16#...) 0000 All queried errors are masked. 0001 At least one of the queried errors is not masked. - General error information See also: Getting error ID locally with GetErrorID (Page 2462) * The error codes can be displayed as integer or hexadecimal values in the program editor. For additional information on toggling display formats, refer to "See also". See also Evaluating errors with output parameter RET_VAL (Page 1738) Asynchronous error event DIS_IRT: Disable interrupt event Description The instruction "DIS_IRT" is used to disable the processing of new interrupts and asynchronous error events. Disabling means that if an interrupting event occurs, the operating system of the CPU reacts as follows: It neither calls an interrupt OB nor an asynchronous error OB, nor does it trigger the normal reaction if an interrupt OB or asynchronous error OB is not programmed. If you disable interrupts and asynchronous error events, this remains in effect for all priority classes. The disable can only be canceled with the "EN_IRT (Page 2720)" instruction or by a warm or a cold restart. 2718 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Whether the operating system writes interrupts and asynchronous error events to the diagnostics buffer when they occur depends on the input parameter setting you select for MODE. Note Remember that when you program the "DIS_IRT" instruction, all interrupts that occur will be discarded. Parameters The following table shows the parameters of the instruction "DIS_IRT": Parameter Declaration Data type Memory area MODE Input BYTE I, Q, M, D, L or constant Specifies which interrupts and asynchronous errors are disabled. Description OB_NR Input INT I, Q, M, D, L or constant OB number RET_VAL Return INT I, Q, M, D, L If an error occurs while the instruction is being executed, the return value contains an error code. You will find more detailed information on valid data types in "Overview of the valid data types (Page 1204)". Parameter MODE MODE (B#16#...) Meaning 00 All newly occurring interrupts and asynchronous error events are disabled. (Synchronous errors are not disabled.) Assign the value "0" to the OB_NR parameter. Entries continue to be made in the diagnostics buffer. 01 All newly occurring events belonging to a specified interrupt class are disabled. Identify the interrupt class by specifying it as follows: Time-of-day interrupts: 10 Time-delay interrupts: 20 Cyclic interrupts: 30 Process interrupts: 40 Interrupts for DPV1: 50 Multicomputing interrupt: 60 Redundancy error interrupts: 70 Asynchronous error interrupts: 80 Entries continue to be made in the diagnostics buffer. 02 All new occurrences of a specified interrupt are disabled. You designate the interrupt using the OB number. Entries continue to be made in the diagnostics buffer. WinCC Basic V13.0 System Manual, 02/2014 2719 Programming the PLC 9.7 References Parameter RET_VAL Error code* Description (W#16#...) 0000 No error occurred. 8090 The OB_NR input parameter contains an invalid value. 8091 The MODE input parameter contains an invalid value. General error information See also: GET_ERR_ID: Get error ID locally (Page 1964) * The error codes can be displayed as integer or hexadecimal values in the program editor. For additional information on toggling display formats, refer to "See also". EN_IRT: Enable interrupt event Description You use the instruction to enable the processing of new interrupts and asynchronous error events that you have previously disabled with the "DIS_IRT (Page 2718)" instruction. This means that if an interrupting event occurs, the operating system of the CPU reacts in one of the following ways: It calls an interrupt OB or asynchronous error OB. or It triggers the standard reaction if the interrupt OB or asynchronous error OB is not programmed. Parameters The following table shows the parameters of the instruction "EN_IRT": Parameter Declaration Data type Memory area Description MODE Input BYTE I, Q, M, D, L or constant Specifies which interrupts and asynchronous error events will be enabled. OB_NR Input INT I, Q, M, D, L or constant OB number RET_VAL Return INT I, Q, M, D, L If an error occurs while the instruction is being executed, the return value contains an error code. For additional information on valid data types, refer to "Overview of the valid data types (Page 1204)". 2720 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameter MODE MODE Meaning 0 All newly occurring interrupts and asynchronous error events are enabled. 1 All newly occurring events belonging to a specified interrupt class are enabled. Identify the interrupt class by specifying it as follows: Time-of-day interrupts: 10 Time-delay interrupts: 20 Cyclic interrupts: 30 Process interrupts: 40 Interrupts for DPV1: 50 Multicomputing interrupt: 60 Redundancy error interrupts: 70 Asynchronous error interrupts: 80 2 All newly occurring events of a specified interrupt are enabled. You designate the interrupt using the OB number. Parameter RET_VAL Error code* Description (W#16#...) 0000 No error occurred. 8090 The OB_NR input parameter contains an invalid value. 8091 The MODE input parameter contains an invalid value. General error information See also: GET_ERR_ID: Get error ID locally (Page 1964) * The error codes can be displayed as integer or hexadecimal values in the program editor. For additional information on toggling display formats, refer to "See also". DIS_AIRT: Delay execution of higher priority interrupts and asynchronous error events Description You use "DIS_AIRT" to delay the processing of interrupt OBs whose priority are higher than the priority of the current organization block. You can call "DIS_AIRT" multiple times in an organization block. The "DIS_AIRT" calls are counted by the operating system. Processing is delayed more and more each time "DIS_AIRT" is executed. To cancel a delay, you must execute the "EN_AIRT (Page 2722)" instruction. To cancel all delays, the number of "EN_AIRT (Page 2722)" executions must be equal to the number of "DIS_AIRT" calls. You can query the number of delays in the RET_VAL parameter of the "DIS_AIRT" instruction. If the value in the RET_VAL parameter is "0", there are no delays. WinCC Basic V13.0 System Manual, 02/2014 2721 Programming the PLC 9.7 References Parameters The following table shows the parameters of the "DIS_AIRT" instruction: Parameter Declaration Data type Memory area Description RET_VAL Return INT I, Q, M, D, L Number of delays For additional information on valid data types, refer to "Overview of the valid data types (Page 1204)". EN_AIRT: Enable execution of higher priority interrupts and asynchronous error events Description You use "EN_AIRT" to enable processing of organization blocks when interrupts occur that have been delayed by the "DIS_AIRT (Page 2721)" instruction. When "EN_AIRT" is executed, you cancel a processing delay that was registered by the operating system when "DIS_AIRT (Page 2721)" was called. To cancel all delays, the number of "EN_AIRT" executions must be equal to the number of "DIS_AIRT (Page 2721)" calls. If, for example, you have called "DIS_AIRT (Page 2721)" five times and thereby also delayed the processing five times, you must call the "EN_AIRT" instruction five times in order to cancel all five delays. You can query the number of interrupt delays that have not yet been enabled after the execution of "EN_AIRT" in the RET_VAL parameter of the "EN_AIRT" instruction. The value "0" in the RET_VAL parameter means that all delays enabled by "DIS_AIRT (Page 2721)" have been cancelled. Parameters The following table shows the parameters of the "EN_AIRT" instruction: Parameter Declaration Data type Memory area Description RET_VAL Return INT I, Q, M, D, L Number of configured delays For additional information on valid data types, refer to "Overview of the valid data types (Page 1204)". 9.7.3.8 Alarms Program_Alarm: Generate program alarm with associated values Description The instruction "Program_Alarm" monitors a signal and generates a program alarm when a signal change occurs at the SIG parameter (for definition, see also: Auto-Hotspot). An incoming program message is generated with a signal change from 0 to 1 and an outgoing program 2722 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References message is generated with a signal change from 1 to 0. The program alarm is triggered synchronously to program execution. You can append up to ten associated values to the program alarm at the parameters SD_i (0 i 10). The associated values are detected at the time of signal change at parameter SIG and assigned to the program alarm. For more information on configuring associated values, refer to the following sections: Auto-Hotspot, Auto-Hotspot. Each incoming or outgoing alarm is assigned a time stamp: The current system time of the PLC when the signal change occurs is used by default (default value at the TIMESTAMP parameter). If you wish to specify a different time stamp, you can create one at the TIMESTAMP parameter. The time value must always be specified in system time (i.e. UTC) as this is the time used for time synchronization throughout the plant. If an alarm is to be time-stamped with a local time, a conversion module, which converts the local time to system time, must be connected in series. This is the only way to make sure that the time stamp is shown properly in the alarm display. To use the current system time of the CPU, set the TIMESTAMP parameter to its default value (LDT#1970-1-1-0:0:0.0). Calling the "Program_Alarm" instruction The instruction "Program_Alarm" can only be called in a function block (FB). Once the instruction has been inserted in the FB, a multi-instance of the data type "Program_Alarm" is created in the "Static" section of the FB interfaces. You can choose any name for this multi-instance in the dialog which appears. The name of the multi-instance is also the name of the program alarm. Finally, add the parameters of the "Program_Alarm" instruction in line with your requirements (see the "Parameters" table). Configuring the program alarm The program alarm settings are displayed in the "Properties" window when you select the name of the program alarm in the "Static" section or in the network of the FB. In this window, you can select the alarm class, priority, etc. and edit the alarm text. The settings that are made here can be edited in the project tree. Go to "PLC alarms" and open the "Program alarms" tab. All existing program alarms are then displayed in the "Alarm types" table. WinCC Basic V13.0 System Manual, 02/2014 2723 Programming the PLC 9.7 References Parameters The following table shows the parameters of the "Program_Alarm" instruction: Parameter Declaration Data type Memory area Description SIG Input BOOL I, Q, M, D, L, T, C or constant The signal to be monitored. TIMESTAMP Input LDT M, D, L or constant This parameter is used to assign an alarm a time stamp, for example, from an input signal with a distributed stamp. The time value must always be specified in system time (i.e. UTC), as this is the time used for time synchronization throughout the plant. "Not assigned" means that the system time of the CPU will be used as the interrupt time stamp when a signal change occurs (default). Any system time input will be used as the interrupt time stamp when a signal change occurs. Note: If an interrupt is to be time-stamped with a local time, a conversion module must be connected in series to convert the local time to system time. This is the only way to make sure that the time stamp is shown correctly in the interrupt display. SD_i Input LREAL, REAL, DINT, INT, SINT, UDINT, UINT, USINT, DWORD, WORD, BYTE, BOOL, WSTRING, STRING, WCHAR, CHAR I, Q, M, D, L i-th associated value (0 i 10) ERROR Output BOOL I, Q, M, D, L Status parameter ERROR ERROR = TRUE indicates that an error has occurred during processing. The possible error cause is displayed at the STATUS parameter. STATUS Output WORD I, Q, M, D, L Status parameter STATUS Display of error information (see "ERROR and STATUS parameters"). You can find additional information on valid data types under "Overview of the valid data types (Page 1204)". 2724 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References ERROR and STATUS parameters The following table contains all specific error information that can be output via the ERROR and STATUS parameters. ERROR STATUS* Explanation 0 0000 No error 1 0085 "Only information" alarm type. 1 8001 Invalid static alarm information. 1 8002 No valid static alarm information. 1 8004 Maximum size of 512 bytes reached for the associated values of the alarm. 1 8005 Incoming alarm. 1 8007 Outgoing alarm, preceded by no incoming alarm. 1 8087 Deactivate static alarms. 1 8089 Length of the alarm is too large. 1 80Ax The SD_i parameter has an invalid value. 1 80C1 The CPU cannot generate any alarms at this time because initialization routines are running (this is the case after download in RUN, for example). Try again later. 1 80C2 The maximum number of alarms per time unit has been sent. Try again later. 1 80C3 All dynamic alarm instances are being used. Try again later. 1 80C4 Alarm is being output and cannot be overwritten. Try again later. * The error codes can be displayed as integer or hexadecimal values in the program editor. For additional information on toggling display formats, refer to "See also". Get_AlarmState: Output alarm status Description The "Get_AlarmState" instruction outputs the alarm status of a program alarm. The output of the alarm status always refers to a program alarm that was created using the "Program_Alarm (Page 2722)" instruction. The program alarm is selected with the Alarm input parameter. Specify the instance DB of the "Program_Alarm" instruction at the Alarm parameter. The alarm status is returned in a byte via the AlarmState output parameter. The meaning of the individual bits is shown in the following figure: WinCC Basic V13.0 System Manual, 02/2014 2725 Programming the PLC 9.7 References $6B67$7(B,1)2 9 7 7 2* 2& $* $& 6 $ODUP/RJ6WDWXV 6 ,QFRPLQJ 6 2XWJRLQJ $ODUP/RJ6WDWXV $& ,QFRPLQJZLWKDFNQRZOHGJPHQW $* 2XWJRLQJZLWKDFNQRZOHGJPHQW 2YHUIORZ VLJQDORYHUIORZ 2& 2YHUIORZRILQFRPLQJPHVVDJHV 2* 2YHUIORZRIRXWJRLQJPHVVDJHV 5HVHUYHG 6WDWXVRIPHVVDJHLQIRUPDWLRQ 9 0HVVDJHLQIRUPDWLRQLQYDOLG 9 0HVVDJHLQIRUPDWLRQYDOLG You can find more information about the possible alarm states in the section "Auto-Hotspot". The execution status of the instruction is shown with the output parameters ERROR and STATUS. Parameters The following table shows the parameters of the "Get_AlarmState" instruction: Parameter Declaration Data type Memory area Description Alarm Input ALARM_BASE D Instance of the "Program_Alarm (Page 2722)" instruction. AlarmState Output BYTE I, Q, M, D, L Status of the alarm as a bit array. ERROR Output BOOL I, Q, M, D, L Status parameter 0: No error 1: An error occurred during execution of the instruction. Detailed information is output via the STATUS parameter. STATUS Output WORD I, Q, M, D, L Status parameter The parameter is only set for the duration of one call. To display the status, you should therefore copy STATUS to a free data area. For additional information on valid data types, refer to "Overview of the valid data types (Page 1204)". 2726 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameter STATUS Error code* (W#16#...) Explanation 8001 Invalid static alarm instance. 8002 ID of the alarm is invalid. 8003 No active alarms within the message class. * The error codes can be displayed as integer or hexadecimal values in the program editor. For additional information on toggling display formats, refer to "See also". Gen_UsrMsg: Generate user diagnostic alarms Description You can use the "Gen_UsrMsg" instruction to create a message for entry into the diagnostic buffer. You can use the Mode parameter to select whether an incoming or an outgoing message is to be generated: With Mode = 0: Create an incoming message. With Mode = 1: Create an outgoing message. Regardless of whether an incoming or outgoing message is generated, the message always has the attribute "Information only". The content of the message is defined with a text list: Specify the text list you want to use with the parameter TextListID. For this purpose open the dialog "Text lists" in the project navigation. Show the column "ID" in the dialog "Text lists". Apply the ID at the parameter TextListID. Use the parameter TextID to select the text list entry you want to write in the diagnostic buffer. For this purpose select an entry from the "Text lists entries" dialog by applying a number from the columns "Range from / range to" at the parameter TextID. The same number must be used from both the "Range from" and "Range to" columns for the text list entry. Additional information about text lists can be found here: Text lists (Page 319) New associated values can be defined in the text entry and then added to the message: Associated values are defined by adding the following information in the text list entry: @<Nr. des Begleitwertes><Formatangabe>@ Use the system data type AssocValues to specify which associated value is added when generating the message. Additional information on the structure of associated values can be found here: AutoHotspot The entry in the diagnostic buffer is created synchronously. Message transmission is asynchronous. If an error occurs during the execution of an instruction, it is output via the parameter RET_VAL. WinCC Basic V13.0 System Manual, 02/2014 2727 Programming the PLC 9.7 References Parameters The following table shows the parameters of the "Gen_UsrMsg" instruction: Parameter Declaration Data type Memory area Description Mode Input UInt I, Q, M, D, L or constant Parameters for selecting the status of the message: 1: incoming message 2: outgoing message TextID Input UInt I, Q, M, D, L or constant ID of the text list entry that should be used for the message text. TextListID Input UInt I, Q, M, D, L or constant ID of the text list that contains text list entry. Ret_Val Return Int I, Q, M, D, L Error code of the instruction. AssocValues InOut VARIANT I, Q, M, D, L Pointer to the system data type AssocValues that allows you to define the associated values . You can find additional information on valid data types under "Overview of the valid data types (Page 1204)". AssocValues parameter Use the system data type AssocValues to define which associated values will be sent. A maximum of 8 associated values are possible. The structure of the system data type is created by entering the data type "AssocValues" as a data block. The associated values are selected by entering the numbers of the associated values for the parameters Value[x]. The associated value must be used in the selected text list entry (parameter TextID). Note the following: The values for TextID and TextListID are treated by the instruction as the associated values to be sent. This means that the digits "1" and "2" can not be used as a numbers for associated values. Therefore, use "3" as the first number at the parameter Value [0] and "4" at the parameter Value [1] etc. Byte Parameters Data type Start value Description 0..1 Value[1] UINT 0 First associated value of the message. 2..3 Value[2] UINT 0 Second associated value of the message. 4..5 Value[3] UINT 0 ... 6..7 Value[4] UINT 0 ... 8..9 Value[5] UINT 0 ... 10..11 Value[6] UINT 0 ... 12..13 Value[7] UINT 0 ... 14..15 Value[8] UINT 0 Eighth associated value of the message. 2728 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References RET_VAL parameter The following table contains all specific error information that can be output via the RET_VAL parameter. Error code* (W#16#...) Explanation 0000 No error 8080 Value in the Mode parameter is not supported. 80C1 Resource bottleneck due to too many parallel calls. * The error codes can be displayed as integer or hexadecimal values in the program editor. For additional information on toggling display formats, refer to "See also". 9.7.3.9 Diagnostics RD_SINFO: Read current OB start information Description You use the instruction "RD_SINFO" to read the start information of the last OB called that has not yet been completely executed, and of the last startup OB started. There is no time stamp in either case. If the call is in OB 100, OB 101 or OB 102, two identical start information messages will be returned. Parameter The following table shows the parameters of the "RD_SINFO" instruction: Parameter Declaration Data type Memory area Description RET_VAL Return INT I, Q, M, D, L Error information TOP_SI Output VARIANT D, L Start information of the current OB START_UP_SI Output VARIANT D, L Start information of the startup OB last started You will find more detailed information on valid data types in "Overview of the valid data types (Page 1204)". WinCC Basic V13.0 System Manual, 02/2014 2729 Programming the PLC 9.7 References SDTs of the TOP_SI parameter The following table shows the possible SDTs for the TOP_SI parameter: Organization blocks (OB) System data types (SDT) System data type numbers Any SI_classic 592 SI_none 593 ProgramCycleOB SI_ProgramCycle 594 TimeOfDayOB SI_TimeOfDay 595 TimeDelayOB SI_Delay 596 CyclicOB SI_Cyclic 597 ProcessEventOB SI_HWInterrupt 598 ProfileEventOB SI_Submodule 601 SynchronousCycleOB SI_SynchCycle 602 IOredundancyErrorOB SI_IORedundancyError 604 CPUredundancyErrorOB SI_CPURedundancyError 605 StatusEventOB UpdateEventOB TimeErrorOB SI_TimeError 606 DiagnosticErrorOB SI_DiagnosticInterrupt 607 PullPlugEventOB SI_PlugPullModule 608 PeripheralAccessErrorOB SI_AccessError 609 RackStationFailureOB SI_StationFailure 610 ServoOB SI_Servo 611 IpoOB SI_Ipo 612 StartupOB SI_Startup 613 ProgrammingErrorOB SI_ProgIOAccessError 614 IOaccessErrorOB SDTs of the START_UP_SI parameter The following table shows the possible SDTs for the START_UP_SI parameter: System data types (SDT) System data type numbers SI_classic 592 SI_none 593 SI_Startup 613 Structures The following tables set out the meaning of the structure elements of the individual structures: 2730 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Table 9-59 SI_classic structure Structure element Data type Description EV_CLASS BYTE Bits 0 to 3: Event ID Bits 4 to 7: Event class EV_NUM BYTE Event number PRIORITY BYTE Priority class number (Meaning of B#16#FE: OB not available or disabled or cannot be started in current operating mode) NUM BYTE OB number TYP2_3 BYTE Data ID 2_3: Identifies the information entered in ZI2_3 TYP1 BYTE Data ID 1: Identifies the information entered in ZI1 ZI1 WORD Additional information 1 ZI2_3 DWORD Additional information 2_3 Table 9-60 SI_none structure Structure element Data type Description SI_Format USINT 16#FF = No information 16#FE = Optimized start information OB_Class USINT OB class for "No information" or "Optimized start information" OB_Nr UINT OB number (1 ... 32767) Table 9-61 SI_ProgramCycle structure Structure element Data type Description SI_Format USINT 16#FF = No information 16#FE = Optimized start information OB_Class USINT := 1 OB class for "No information" or "Optimized start information" OB_Nr UINT OB number (1 ... 32767) Initial_Call BOOL For OB_Class = 1, 30, 52, 61, 65 Remanence BOOL For OB_Class = 1 Table 9-62 SI_TimeOfDay structure Structure element Data type Description SI_Format USINT 16#FF = No information 16#FE = Optimized start information OB_Class USINT := 10 OB class for "No information" or "Optimized start information" OB_Nr UINT OB number (1 ... 32767) CaughtUp BOOL For OB_Class = 10 SecondTime BOOL For OB_Class = 10 WinCC Basic V13.0 System Manual, 02/2014 2731 Programming the PLC 9.7 References Table 9-63 SI_Delay structure Structure element Data type Description SI_Format USINT 16#FF = No information 16#FE = Optimized start information OB_Class USINT := 20 OB class for "No information" or "Optimized start information" OB_Nr UINT OB number (1 ... 32767) Sign WORD For OB_Class = 20 Table 9-64 SI_Cyclic structure Structure element Data type Description SI_Format USINT 16#FF = No information OB_Class USINT := 30 OB class for "No information" or "Optimized start information" OB_Nr UINT OB number (1 ... 32767) Initial_Call BOOL For OB_Class = 1, 30, 52, 61, 65 Event_Count INT For OB_Class = 30, 51, 52, 61, 65, 91, 92 16#FE = Optimized start information Table 9-65 SI_HWInterrupt structure Structure element Data type Description SI_Format USINT 16#FF = No information OB_Class USINT := 40 OB class for "No information" or "Optimized start information" OB_Nr UINT OB number (1 ... 32767) LADDR HW_IO For OB_Class = 40, 51, 55, 56, 57, 70, 82, 83, 85, 86, 91, 92 USI WORD For OB_Class = 40 IChannel USINT For OB_Class = 40 EventType BYTE For OB_Class = 40 16#FE = Optimized start information Table 9-66 SI_Submodule structure Structure element Data type Description SI_Format USINT 16#FF = No information OB_Class USINT OB class for "No information" or "Optimized start information" OB_Nr UINT OB number (1 ... 32767) LADDR HW_IO For OB_Class = 40, 51, 55, 56, 57, 70, 82, 83, 85, 86, 91, 92 Slot UINT For OB_Class = 55, 56, 57 Specifier WORD For OB_Class = 55, 56, 57 16#FE = Optimized start information 2732 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Table 9-67 SI_SynchCycle structure Structure element Data type Description SI_Format USINT 16#FF = No information 16#FE = Optimized start information OB_Class USINT := 61 OB class for "No information" or "Optimized start information" OB_Nr UINT OB number (1 ... 32767) Initial_Call BOOL For OB_Class = 1, 30, 52, 61, 65 PIP_Input BOOL For OB_Class = 61, 91, 92 PIP_Output BOOL For OB_Class = 61, 91, 92 IO_System USINT For OB_Class = 61, 91, 92 Event_Count INT For OB_Class = 30, 51, 52, 61, 65, 91, 92 SyncCycleTime LTIME Calculated cycle time Table 9-68 SI_IORedundancyError structure Structure element Data type Description SI_Format USINT 16#FF = No information OB_Class USINT := 70 OB class for "No information" or "Optimized start information" OB_Nr UINT OB number (1 ... 32767) LADDR HW_ANY For OB_Class = 40, 51, 55, 56, 57, 70, 82, 83, 85, 86, 91, 92 Event_Class BYTE For OB_Class = 70, 83, 85, 86 Fault_ID BYTE For OB_Class = 70, 80, 83, 85, 86 16#FE = Optimized start information Table 9-69 SI_CPURedundancyError structure Structure element Data type Description SI_Format USINT 16#FF = No information 16#FE = Optimized start information OB_Class USINT := 72 OB class for "No information" or "Optimized start information" OB_Nr UINT OB number (1 ... 32767) Switch_Over BOOL For OB_Class = 72 Table 9-70 SI_TimeError structure Structure element Data type Description SI_Format USINT 16#FF = No information OB_Class USINT := 80 OB class for "No information" or "Optimized start information" OB_Nr UINT OB number (1 ... 32767) Fault_ID BYTE For OB_Class = 70, 80, 83, 85, 86 Csg_OBnr OB_ANY For OB_Class = 80 Csg_Prio UINT For OB_Class = 80 16#FE = Optimized start information WinCC Basic V13.0 System Manual, 02/2014 2733 Programming the PLC 9.7 References Table 9-71 SI_DiagnosticInterrupt structure Structure element Data type Description SI_Format USINT 16#FF = No information 16#FE = Optimized start information OB_Class USINT := 82 OB class for "No information" or "Optimized start information" OB_Nr UINT OB number (1 ... 32767) IO_State WORD For OB_Class = 82 LADDR HW_ANY For OB_Class = 40, 51, 55, 56, 57, 70, 82, 83, 85, 86, 91, 92 Channel UINT For OB_Class = 82 MultiError BOOL For OB_Class = 82 Table 9-72 SI_PlugPullModule structure Structure element Data type Description SI_Format USINT 16#FF = No information 16#FE = Optimized start information OB_Class USINT := 83 OB class for "No information" or "Optimized start information" OB_Nr UINT OB number (1 ... 32767) LADDR HW_IO For OB_Class = 40, 51, 55, 56, 57, 70, 82, 83, 85, 86, 91, 92 Event_Class BYTE For OB_Class = 70, 83, 85, 86 Fault_ID BYTE For OB_Class = 70, 80, 83, 85, 86 Table 9-73 SI_AccessError structure Structure element Data type Description SI_Format USINT 16#FF = No information 16#FE = Optimized start information OB_Class USINT := 85 OB class for "No information" or "Optimized start information" OB_Nr UINT OB number (1 ... 32767) LADDR HW_IO For OB_Class = 40, 51, 55, 56, 57, 70, 82, 83, 85, 86, 91, 92 Event_Class BYTE For OB_Class = 70, 83, 85, 86 Fault_ID BYTE For OB_Class = 70, 80, 83, 85, 86 IO_Addr UINT For OB_Class = 85 IO_LEN UINT For OB_Class = 85 Table 9-74 SI_StationFailure structure Structure element Data type Description SI_Format USINT 16#FF = No information OB_Class USINT := 86 OB class for "No information" or "Optimized start information" OB_Nr UINT OB number (1 ... 32767) LADDR HW_IO For OB_Class = 40, 51, 55, 56, 57, 70, 82, 83, 85, 86, 91, 92 Event_Class BYTE For OB_Class = 70, 83, 85, 86 Fault_ID BYTE For OB_Class = 70, 80, 83, 85, 86 16#FE = Optimized start information 2734 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Table 9-75 SI_Servo structure Structure element Data type Description SI_Format USINT 16#FF = No information 16#FE = Optimized start information OB_Class USINT := 91 OB class for "No information" or "Optimized start information" OB_Nr UINT OB number (1 ... 32767) Initial_Call BOOL For OB_Class = 1, 30, 52, 61, 65 PIP_Input BOOL For OB_Class = 61, 91, 92 PIP_Output BOOL For OB_Class = 61, 91, 92 IO_System USINT For OB_Class = 61, 91, 92 Event_Count INT For OB_Class = 30, 51, 52, 61, 65, 91, 92 Synchronous BOOL Table 9-76 SI_Ipo structure Structure element Data type Description SI_Format USINT 16#FF = No information OB_Class USINT := 92 OB class for "No information" or "Optimized start information" OB_Nr UINT OB number (1 ... 32767) Initial_Call BOOL For OB_Class = 1, 30, 52, 61, 65 PIP_Input BOOL For OB_Class = 61, 91, 92 PIP_Output BOOL For OB_Class = 61, 91, 92 IO_System USINT For OB_Class = 61, 91, 92 16#FE = Optimized start information Event_Count INT For OB_Class = 30, 51, 52, 61, 65, 91, 92 Reduction UINT For OB_Class = 92 Table 9-77 SI_Startup structure Structure element Data type Description SI_Format USINT 16#FF = No information OB_Class USINT := 100 OB class for "No information" or "Optimized start information" OB_Nr UINT OB number (1 ... 32767) LostRetentive BOOL For OB_Class = 100 LostRTC BOOL For OB_Class = 100 16#FE = Optimized start information Table 9-78 SI_ProgIOAcessError structure Structure element Data type Description SI_Format USINT 16#FF = No information OB_Class USINT OB class for "No information" or "Optimized start information" OB_Nr UINT OB number (1 ... 32767) BlockNr UINT For OB_Class = 121, 122 16#FE = Optimized start information WinCC Basic V13.0 System Manual, 02/2014 2735 Programming the PLC 9.7 References Structure element Data type Description Reaction USINT For OB_Class = 121, 122 Fault_ID BYTE For OB_Class = 121, 122 BlockType USINT For OB_Class = 121, 122 Area USINT For OB_Class = 121, 122 DBNr DB_ANY For OB_Class = 121, 122 Csg_OBNr OB_ANY For OB_Class = 121, 122 Csg_Prio USINT For OB_Class = 121, 122 Width USINT For OB_Class = 121, 122 Note The structure elements specified for the SI_classic structure are identical in content to the temporary tags of any OB created with the block property "Default". Please note, however, that temporary tags of the individual OBs can have different names and different data types. Also note that the call interface of each OB includes additional information regarding the date and the time of the OB request. Bits 4 to 7 of the EV_CLASS structure element contain the event class. The following values are possible here: 1: Start events from standard OBs 2: Start events from synchronous error OBs 3: Start events from asynchronous error OBs The PRIORITY structure element supplies the priority class belonging to the current OB. Apart from these two elements, NUM is also relevant. NUM contains the number of the current OB or the startup OB that was started last. RET_VAL parameter The following table shows the meaning of the values of the RET_VAL parameter: Error code* (W#16#...) Explanation 8080 Start information of the current OB does not correspond to the specified user-defined data type 8081 Start information of the current OB does not correspond to the specified system data type 8082 Start information of the last startup OB started does not correspond to the specified user-defined data type 8083 Start information of the last startup OB started does not correspond to the specified system data type Example OB 80 is the OB that was called last and that has not yet been completely processed and OB 100 is the start-up OB that was started last. The following table shows the assignment between the structure elements of the TOP_SI parameter of the "RD_SINFO" instruction and the associated local tags of OB 80. 2736 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References TOP_SI structure element Data type OB 80 - Associated local tag Data type EV_CLASS BYTE OB80_EV_CLASS BYTE EV_NUM BYTE OB80_FLT_ID BYTE PRIORITY BYTE OB80_PRIORITY BYTE NUM BYTE OB80_OB_NUMBR BYTE TYP2_3 BYTE OB80_RESERVED_1 BYTE TYP1 BYTE OB80_RESERVED_2 BYTE ZI1 WORD OB80_ERROR_INFO WORD ZI2_3 DWORD OB80_ERR_EV_CLASS BYTE OB80_ERR_EV_NUM BYTE OB80_OB_PRIORITY BYTE OB80_OB_NUM BYTE The following table shows the assignment between the structure elements of the START_UP_SI parameter of the "RD_SINFO" instruction and the associated local tags of OB 100. START_UP_SI structure element Data type OB 100 - Local tag Data type EV_CLASS BYTE OB100_EV_CLASS BYTE EV_NUM BYTE OB100_STRTUP BYTE PRIORITY BYTE OB100_PRIORITY BYTE NUM BYTE OB100_OB_NUMBR BYTE TYP2_3 BYTE OB100_RESERVED_1 BYTE TYP1 BYTE OB100_RESERVED_2 BYTE ZI1 WORD OB100_STOP WORD ZI2_3 DWORD OB100_STRT_INFO DWORD See also Evaluating errors with output parameter RET_VAL (Page 1738) RT_INFO: Read out runtime statistics Description Use the instruction "RT_INFO" to generate statistics on the runtime of specific organization blocks, communication or the user program. Use the MODE parameter to select which information is going to be output: WinCC Basic V13.0 System Manual, 02/2014 2737 Programming the PLC 9.7 References MODE 1 to 3 return the data on the runtime of a specific organization block whose number was specified at the OB parameter. MODE 10 and 11 return the proportions of runtime used for communication and the user program. MODE 30 to 32 return data on configured settings of the user program. All measurements are started once again when the CPU transitions from startup to RUN. Parameters The following table shows the parameters of the instruction "RT_INFO": Parameter Declaration Data type Memory area Description MODE Input UINT I, Q, M, D, L or constant Use the MODE parameter to select the information you want to read out (see table "MODE parameter"). OB Input OB_ANY I, Q, M, D, L or constant Use the OB parameter to select the OB for which you want to read out information. RET_VAL Return INT I, Q, M, D, L Error information (see " RET_VAL parameter"). INFO InOut VARIANT I, Q, M, D, L Pointer to the area to which the read data is to be written. The data type required for INFO depends on the MODE parameter (see table "MODE parameter"). You can find additional information on valid data types in "Overview of the valid data types (Page 1204)". MODE parameter The following table shows which information is returned for the values at the MODE parameter. MODE Description (decimal ) Note Value at OB parameter Data type of INFO Available as of CPU version 1 Runtime of a specific OB OB number LTIME S7-1500 V1.5 2 Maximum runtime of a specific OB The runtime information always refers to the specified OB. Processes, such as interruptions by OBs of a higher priority or communication, are not included. OB number LTIME S7-1500 V1.5 3 Minimum runtime of a specific OB LTIME S7-1500 V1.5 2738 You can use the instruction "RUNTIME" to OB measure the runtime of the entire program. number WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References MODE Description (decimal ) Note Value at OB parameter Data type of INFO Available as of CPU version 10 The percentages of MODE 10, 11 and 12 always add up to 100 (=total runtime). Not relevant UINT S7-1500 V1.5 Not relevant UINT S7-1500 V1.5 Not relevant LTIME S7-1500 V1.5 Percentage of total runtime used by higher-priority OBs The runtime of all OBs used in the user program with a higher priority than cyclical program OBs is output (ProgramCycle). These usually include all OB types except startup OBs. The CPU determines which OBs can be used and their priority. This information is included in the basic chapters on programming. 11 Percentage of total runtime used by communication The percentage of communication processes in the total runtime of the user program is output. 30 Output of the warning limit from which a time error OB is called. The warning limit is the maximum permitted number of requested but not yet completely processed requirements of an OB. 31 Output of the configured minimum cycle time for the user program Not relevant UINT S7-1500 V1.5 32 Output of the configured maximum communication load Not relevant UINT S7-1500 V1.5 RET_VAL parameter The following table shows the meaning of the values of the RET_VAL parameter: Error code* (W#16#...) Explanation 0 No error 8080 Selection for MODE parameter is not supported. 8081 Organization block selected at OB parameter does not exist in the user program. 80C3 Insufficient resources. Try to call the instruction again at a later time. 8452 Data type at INFO parameter is incorrect. Check whether the correct data type was selected depending on the MODE parameter. WinCC Basic V13.0 System Manual, 02/2014 2739 Programming the PLC 9.7 References See also Evaluating errors with output parameter RET_VAL (Page 1738) LED: Read LED status Description You can use the "LED" instruction to read out the status (e.g., "On" or "Off") of a particular module LED. With the LADDR parameter, you address the CPU or the interface. With the LED parameter, you select the module LED whose current status is to be read out using the instruction. The RET_VAL parameter outputs the status of the selected LED when the instruction is called. Depending on the LED selected, only certain status information may be displayed. For example, some LEDs have only color information. Refer to the hardware documentation of the respective module for the available status information of a particular LED. Parameters The following table shows the parameters of the "LED" instruction: Parameter Declaration Data type Memory area Description LADDR Input HW_IO I, Q, M, L or constant Identification number of the CPU or interface. The number is automatically assigned and stored in the CPU properties or the interface in the hardware configuration. LED Input UINT I, Q, M, D, L or constant Identification number of the LED: 1: STOP/RUN 2: ERROR 3: MAINT (maintenance) 4: Redundant 5: Link (green) 6: Rx/Tx (yellow) RET_VAL Return INT I, Q, M, D, L Status of LED For additional information on valid data types, refer to "Overview of the valid data types (Page 1204)". 2740 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameter RET_VAL RET_VAL Description 0 to 9 LED status: 0 = LED does not exist 1 = Permanently switched off 2 = Color 1 (e.g., for LED STOP/RUN: green) permanently ON 3 = Color 2 (e.g., for LED STOP/RUN: orange) permanently ON 4 = Color 1 flashing at 2 Hz 5 = Color 2 flashing at 2 Hz 6 = Colors 1 and 2 flashing alternately at 2 Hz 7 = LED is active, color 1 8 = LED is active, color 2 9 = LED exists, but status information not available 8091 Module addressed with the LADDR parameter does not exist. 8092 A module that does not support LEDs was addressed with the LADDR parameter. 8093 The identification number specified in the LED parameter is not defined. 80Bx The CPU specified in the LADDR parameter does not support the "LED" instruction. Get_IM_Data: Reading identification and maintenance data Description The "Get_IM_Data" instruction reads the identification and maintenance data (I&M) data from a device. Use the LADDR parameter to select the device from which you want to read the I&M via the hardware identifier. You select the data to be read via the instruction using the IM_TYPE parameter: IM_TYPE = 0: I&M 0 data The I&M 0 data are the device-specific basic information of a device and contain information such as the manufacturer ID, order number, serial number and the hardware and firmware version. Only read access is possible to the I&M 0 data. The information is also displayed in the TIA Portal with the "Online & Diagnostics" view of a device. IM_TYPE = 11: I&M 1 data from the parameter assignment data of the CPU The I&M 1 data contains a functional description of the device and the location ID, i.e. the information about how the device is designated within the plant. IM_TYPE = 12: I&M 2 data from the parameter assignment data of the CPU The I&M 2 data includes the date of installation, i.e. the information about when the device was installed in the plant. IM_TYPE = 13: I&M 3 data from the parameter assignment data of the CPU The I&M 3 data contains additional information about the installed device. The additional information is free text and can be assigned as desired. The I&M data read is written to the addressed area defined at the DATA parameter. The execution status of the read job is displayed via the BUSY, DONE, ERROR output parameters and the two middle bytes of the STATUS output parameter. WinCC Basic V13.0 System Manual, 02/2014 2741 Programming the PLC 9.7 References Definition: Identification and maintenance data (I&M) Identification and maintenance (I&M) data refers to information stored in a module, which assists you in checking the plant configuration, locating hardware changes in a plant and eliminating errors. Identification data (I data) are static information about a device that can only be read. Maintenance data (M-data) refers to plant-dependent information, such as the installation location or date. Maintenance data are created during configuration and written to the module. Parameters The following table shows the parameters of the "Get_IM_Data" instruction: Parameter Declaration Data type Memory area Description LADDR Input HW_IO I, Q, M, D, L or constant Hardware ID of the device The number is assigned automatically and is stored in the properties of the device or in the hardware configuration. IM_TYPE Input UINT I, Q, M, D, L or constant Identification and maintenance data number Possible values: 0: I&M 0 data 11: I&M 1 data from the parameter assignment data of the CPU 12: I&M 2 data from the parameter assignment data of the CPU 13: I&M 3 data from the parameter assignment data of the CPU DATA InOut VARIANT I, Q, M, D, L Area for storing the read identification and maintenance data (see DATA parameter). DONE Output BOOL I, Q, M, D, L The instruction was executed successfully. The I&M data were transferred to the DATA parameter. BUSY Output BOOL I, Q, M, D, L Status parameter 0: Execution of the instruction complete or not yet started. 1: Execution of the instruction not yet complete. ERROR Output BOOL I, Q, M, D, L Status parameter 0: No error. 1: An error occurred during execution of the instruction. Detailed information is output via the STATUS parameter. STATUS 2742 Output WORD I, Q, M, D, L Status parameter The parameter is only set for the duration of one call. To display it, you should therefore copy STATUS to a free data area. WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References You can find more information on the data types in "Overview of the valid data types (Page 1204)". DATA parameter You can use a string (STRING), an array (ARRAY of CHAR/BYTE) or a data structure (STRUCT) to store the I&M data: If you address a string (STRING data type) at the the DATA parameter, the length of the string automatically adjusts the length of the read I&M data (up to 254 characters). If you address a data structure (ARRAY of CHAR/BYTE or STRUCT) a the DATA parameter, the I&M data read are written to the individual components of the data type used. If the addressed data structure is longer than the read data, the remaining components are filled with zeros. If you crate a data structure with a STRUCT data type at the DATA parameter, use a data block without optimized block access (see category "Attributes" of the block properties). If a data type other than STRING, ARRAY of BYTE/CHAR or STRUCT is used at the DATA parameter, the STATUS parameter generates error code 8093. There is an exception for I&M 0 data (IM_TYPE parameter = 0). For I&M 0 data, the following "IuM0_data" structure can also be used at the DATA parameter: Parameter Data type Bytes Description Manufacturer_ID UINT 2 Manufacturer ID (e.g. "42" for SIEMENS) Order_ID CHAR[20] 20 Order number Serial_Number CHAR[16] 16 Serial number Hardware_Revision UNIT 2 Hardware revision Software_Revision STRUCT 4 Firmware revision Type CHAR 1 - Functional UNIT8 1 - Bugfix UNIT8 1 - Internal UINT8 1 - Revision_Counter UINT 2 Revision counter Profile_ID UNIT 2 Profile Profile_Specific_Type UNIT 2 Device class IM_Version UNIT 2 I&M version I&M_Supported UNIT 2 I&M data (I&M 0-I&M 4) supported at the device end STATUS parameter Error code* (W#16#...) Description 0 No error 7000 No job in progress. WinCC Basic V13.0 System Manual, 02/2014 2743 Programming the PLC 9.7 References Error code* (W#16#...) Description 7001 First call of the asynchronous instruction "Get_IM_Data". Execution of the instruction not yet complete (BUSY = 1, DONE = 0). 7002 Additional call of the asynchronous instruction "Get_IM_Data". Execution of the instruction not yet complete (BUSY = 1, DONE = 0). 807F Maximum of 10 parallel executions of the instances exceeded: Avoid more than 10 parallel calls of the instruction. Repeat the call at a later time, as this is a temporary error. 8091 The device addressed at the LADDR parameter does not exist. 8092 LADDR addresses a device that does not support the output of the I&M data. 8093 Data type at the DATA parameter is not supported. 80B1 The "Get_IM_Data" instruction is not supported by the CPU used. 80B2 Invalid value at the IM_TYPE parameter or the selected IM_TYPE is not supported by the CPU or the addressed device. 8752 The memory area specified at the DATA parameter is too small to store all the I&M data. The read I&M data are stored only up to the maximum length of the specified memory area. * The error codes can be displayed as integer or hexadecimal values in the program editor. For additional information on toggling display formats, refer to "See also". 2744 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References GET_NAME: Reading the name of a module Description The instruction "GET_NAME" reads the name of an IO device. The name is displayed in the network view and in the properties of the IO device: You select the IO device by using the hardware identifier of the PROFINET IO system (at the LADDR parameter) and the device number of the IO device (STATION_NR parameter). Once the instruction has been executed, the name of the IO device is written to the area addressed with the DATA parameter. The name that is read depends on the type of IO device: For a DP slave or IO device, the name of the head module is output. For an I-slave or I-device, the name of the interface module is output. The station name is output for an HMI panel. The name of the interface module is output for a PC station. The name of the Device Access Point (DAP) is displayed (name of the interface or head module) for GSD devices. The length of the name is output at the LEN parameter. If the name is longer than the area specified at the DATA parameter, only that section which corresponds to the maximum length of the addressed area will be written. WinCC Basic V13.0 System Manual, 02/2014 2745 Programming the PLC 9.7 References The maximum length for a name is 128 characters. Note Name of the CPU readout (Version 1.1) If you assign a "0" at each of the parameters LADDR and STATION_NR the instruction will output the name of the CPU. Parameters The following table shows the parameters of the "GET_NAME" instruction: Parameter Declaration Data type Memory area Description LADDR Input HW_IOSYSTEM I, Q, M, D, L or constant Hardware identifier of the PROFINET IO system. The number can be taken from the system constants or the properties of the IO system. STATION_NR Input UINT I, Q, M, D, L or constant Device number of the IO device. The device number can be applied in the Network view from the properties of the IO device under "Ethernet addresses". DATA InOut VARIANT I, Q, M, D, L Pointer to the area to which the name of the module is written. DONE Output BOOL I, Q, M, D, L The instruction was executed successfully. Name of the module transferred to the area at the DATA parameter. BUSY Output BOOL I, Q, M, D, L Status parameter 0: Execution of the instruction complete. 1: Execution of the instruction not yet complete. ERROR Output BOOL I, Q, M, D, L Status parameter 0: No error. 1: An error occurred during execution of the instruction. Detailed information is output via the STATUS parameter. LEN Output DINT I, Q, M, D, L Length of the name of the IO device (number of characters). STATUS Output WORD I, Q, M, D, L Status parameter The parameter is only set for the duration of one call. To display the status, you should therefore copy STATUS to a free data area. For additional information on valid data types, refer to "Overview of the valid data types (Page 1204)". 2746 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameter STATUS Error code* (W#16#...) Explanation 0 No error 7000 No job in progress. 7001 First call of the asynchronous instruction "GET_NAME". Execution of the instruction not yet complete (BUSY = 1, DONE = 0). 7002 Additional call of the asynchronous instruction "GET_NAME". Execution of the instruction not yet complete (BUSY = 1, DONE = 0). 8090 The LADDR input parameter contains an invalid value. Possible causes: The specified number is not a hardware identifier of a PROFINET IO system. You have not specified a number at the LADDR parameter. 8092 The value at the LADDR parameter does not address a PROFINET IO system. 8093 Instruction does not support data type at the DATA parameter. 8095 Device number (STATION_NR parameter) does not exist in the selected PROFINET IO system. 80B1 The CPU used does not support the instruction. 80C3 Temporary resource error: The CPU is currently processing the maximum possible number of simultaneous block calls. "GET_NAME" cannot be executed unless at least one of the block calls is finished. 8852 The area specified at the DATA parameter is too short for the full name of the IO device. The name will be written up to the maximum possible length. To read the full name, use a longer data area at the DATA parameter. The area must have at least as many characters as there are at the LEN parameter. * The error codes can be displayed as integer or hexadecimal values in the program editor. For additional information on toggling display formats, refer to "See also". Example The following example shows how you can read out the station name of a HMI panel. Configuration of the HMI panel: The HMI panel with the station name "HMI_IO-Device" is created in the network view and assigned to the same PROFINET IO system as the CPU. The operating mode "IO device" was activated in the properties of the hardware configuration for the HMI panel and the CPU was assigned as the IO controller. The device number "20" assigned in the properties under "Ethernet addresses". WinCC Basic V13.0 System Manual, 02/2014 2747 Programming the PLC 9.7 References Assigning parameters to the instruction "GET_NAME": The hardware ID (258) of the IO system was specified at the parameter LADDR. The device number (20) of the HMI panel was specified at the parameter STATION_NR. A tag was connected with the data type STRING of a data block at the parameter DATA. PLC tags (memory area, flags) were defined for the output parameters of the instruction. Execution of the instruction: After execution of the instruction, the name of the station of the HMI panels (HMI_IO-Device) is written into the data block at the parameter DATA. The number of characters of the name is output (13) at the parameter LEN. GetStationInfo: Read information of an IO device Description You can use the "GetStationInfo" instruction to read information of a PROFINET IO device. The instruction also enables you to read the information of an IO device located in a lowerlevel IO system (connected via CP/CM). 2748 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References The IO device is addressed via the hardware identifier of the station at the LADDR parameter. The hardware identifier is displayed in the "Devices & Networks" view in the station properties. Use the MODE parameter to select the information to be read. The instruction supports reading the IP address parameters according IPv4 in TIA V12 SP1 (MODE = 1). At the DATA parameter, specify the data area to which you want to write the read address data. Use the "IF_CONF_v4" structure to store the IP address. Enable reading of the address data using the REQ control parameter. This requires the IO device to be accessible. The execution status of the read job is displayed via the BUSY, DONE, ERROR output parameters and the STATUS output parameter. Note Address the IO device using only the hardware identifier of the station The station, the IO device and PROFINET interface have their own hardware identifier. Use only the hardware identifier of the station for the "GetStationInfo" instruction. If a PROFINET is addressed via the LADDR parameter, for example, the address data is not read and the error code 8092 is generate. To read the address data of an integrated PROFINET interface or a CM/CP in the central configuration, use the "RDREC" instruction. Parameters The following table shows the parameters of the "GetStationInfo" instruction: Parameter Declaration Data type Memory area Description REQ Input BOOL I, Q, M, D, L Control parameter Request Activates the reading of the information with REQ = "1". LADDR Input HW_DEVICE I, Q, M, D, L or constant Hardware identifier of the station of the IO device The number can be taken from the properties of the station in the Network view or from the "System constants" tab of the standard tag table. DETAIL Input HW_SUBMO I, Q, M, D, L or DULE constant The DETAIL parameter is not used. Leave the parameter unconnected. MODE Input UNIT I, Q, M, D, L or constant Selection of address data to be read D, L Pointer to the area to which the address data of the IO device is written. Use the "IF_CONF_v4" structure for MODE = 1. DATA WinCC Basic V13.0 System Manual, 02/2014 InOut VARIANT Connect the MODE parameter with "1" (read address parameter according to IPv4). 2749 Programming the PLC 9.7 References Parameter Declaration Data type Memory area Description DONE Output BOOL I, Q, M, D, L The instruction was executed successfully. The address data was transferred to the DATA parameter. BUSY Output BOOL I, Q, M, D, L Status parameter 0: Execution of the instruction complete. 1: Execution of the instruction not yet complete. ERROR Output BOOL I, Q, M, D, L Status parameter 0: No error. 1: An error occurred during execution of the instruction. Detailed information is output via the STATUS parameter. STATUS Output WORD I, Q, M, D, L Status parameter The parameter is only set for the duration of one call. To display the status, you should therefore copy STATUS to a free data area. You can find more information on the data types in "Overview of the valid data types (Page 1204)". Parameter DATA Use the "IF_CONF_v4" structure at the DATA parameter to store the address parameter according to IPv4. Byte Parameter Data type Start value Description 0 ... 1 Id UINT 30 ID of the "IF_CONF_v4" structure. 2 ... 3 Length UNIT 18 Length of data read in BYTE. 4 ... 5 Mode UNIT 0 Not relevant for the "GetStationInfo" instruction (left at "0"). - IP address of the IO device in the format IP_V4, e.g. for 192.168.3.10: 6 ... 9 InterfaceAddress ARRAY [1..4] of BYTE addr[1] = 192 addr[2] = 168 addr[3] = 3 addr[4] = 10 2750 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Byte Parameter Data type Start value Description 10 ... 13 SubnetMask ARRAY [1..4] of BYTE - Subnet mask of the IO device in the format IP_V4, e.g. for 255.255.255.0: addr[1] = 255 addr[2] = 255 addr[3] = 255 addr[4] = 0 14 ... 17 DefaultRouter ARRAY [1..4] of BYTE - IP address of the router in the format IP_V4, e.g. for 192.168.3.1: addr[1] = 192 addr[2] = 168 addr[3] = 3 addr[4] = 1 Parameter STATUS Error code* (W#16#...) Explanation 0 No error 7000 No job in progress. 7001 First call of the asynchronous instruction "GetStationInfo". Execution of the instruction not yet complete (BUSY = 1, DONE = 0). 7002 Additional call of the asynchronous instruction "GetStationInfo". Execution of the instruction not yet complete (BUSY = 1, DONE = 0). 8080 Value at the MODE parameter is not supported. 8090 The hardware identifier specified at the LADDR parameter is not configured. 8092 The LADDR parameter does not address a PROFINET IO device. 8093 Invalid data type at the DATA parameter. 80A0 Cannot read requested information. 80C0 Addressed IO device is not reachable. 80C3 The maximum number of simultaneous calls of the "GetStationInfo" instruction (10 instances) has been reached. * The error codes can be displayed as integer or hexadecimal values in the program editor. For additional information on toggling display formats, refer to "See also". DeviceStates: Read module status information in an IO system Description You use the instruction "DeviceStates" to query specific status information for all modules in an IO system, which means: Either for all IO devices in a PROFINET IO system Or for all DP slaves in a DP master system WinCC Basic V13.0 System Manual, 02/2014 2751 Programming the PLC 9.7 References The Boolean value that is output indicates the modules to which the selected status applies. You can, for example, read which IO devices are currently disabled in a PROFINET IO system. Information is also displayed as to whether the status information to be read applies to at least one of the IO devices or DP slaves. The instruction can be called in a cyclic OB as well as in an interrupt OB (e.g. OB82 - diagnostic interrupt). Parameters The following table shows the parameters of the "DeviceStates" instruction: Parameter Declaration Data type LADDR Input HW_IOSYSTEM I, Q, M, L or constant Memory area Description MODE Input UINT I, Q, M, D, L or constant Selection of status information to be read (see description below) RET_VAL Return INT I, Q, M, D, L Status of instruction (see description below) STATE InOut VARIANT I, Q, M, D, L Buffer for status of the IO devices or the DP slaves (see description below) Hardware identifier of the PROFINET IO or DP master system (see description below) You will find more detailed information on valid data types in "Overview of the valid data types (Page 1204)". Parameter LADDR You select the PROFINET IO or DP master system at the LADDR parameter by means of the hardware identifier. The hardware identifier is available: Either in the Network view of the properties of the PROFINET IO or DP master system. Or in the PLC tag table in the listed system constants with the data type HW_IOSYSTEM. Parameter MODE You use the MODE parameter to read out status information. You can read out one of the following status information items for the entire PROFINET IO or DP master system: 1: IO devices/DP slaves are configured 2: IO devices/DP slaves are faulty 3: IO devices/DP slaves are disabled 2752 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References 4: IO devices/DP slaves exist 5: IO devices/DP slaves for which a problem has occurred. For example: - Maintenance demanded or recommended - Not accessible - Not available - Error occurred Parameter STATE With the STATE parameter, the status of the IO devices/DP slaves that was selected with the MODE parameter is output. If the status selected using MODE applies to an IO device/DP slave, the following bits are set to "1" at the STATE parameter: Bit 0 = 1: Group display. The bit n of at least one IO device/DP slave was set to "1". Bit n = 1: The status selected with MODE applies to the IO device/DP slave. - With a PROFINET IO system, bit n corresponds to the device number of the respective IO device (see properties of the PROFINET interface in the device view and network view) - With a PROFIBUS DP system, bit n corresponds to the PROFIBUS address of the DP slave (see properties of the DP slave in the device view and network view) Use "BOOL" or "Array of BOOL" as data type: To only output the bit for group display of the status information, you can use the data type BOOL at the STATE parameter. To output the status information for all IO devices/DP slaves, use Array of BOOL with the following length: - With PROFINET IO system: 1024 bits - With DP master system: 128 bits Parameter RET_VAL Error code* Description (W#16#...) 0 No error 8091 Hardware identifier of the LADDR parameter does not exist. Check (for example, in the system constants) whether the value for LADDR exists in the project. 8092 LADDR does not address a PROFINET IO or DP master system. 8093 Invalid data type at the STATE parameter. 80B1 Instruction "DeviceStates" is not supported by the CPU. 80B2 The selected MODE parameter is not supported by the used CPU for the IO system specified in the LADDR parameter. WinCC Basic V13.0 System Manual, 02/2014 2753 Programming the PLC 9.7 References Error code* Description (W#16#...) 8452 The complete status information does not fit in the tag configured in the STATE parameter. * The error codes can be displayed as integer or hexadecimal values in the program editor. For additional information on toggling display formats, refer to "See also". Example - Reading the faulty stations of a PROFINET IO master system A PROFINET IO system consists of 4 IO devices with the device numbers 1, 2, 3 and 4. The IO device with number 2 is faulty. The instruction "DeviceStates" is executed for the PROFINET IO system with MODE = 2 (faulty/ not faulty). The following bits are set in the STATE parameter: Bit 0 = 1: A fault exists for at least one of the IO devices. Bit 1 = 0: IO device with device number 1 is not faulty. Bit 2 = 1: IO device with device number 2 is faulty. Bit 3 = 0: IO device with device number 3 is not faulty. Bit 4 = 0: IO device with device number 4 is not faulty. Bit 5 = 0: irrelevant Bit 6 = 0: irrelevant ... Example - Reading the faulty stations of a PROFIBUS DP master system A DP master system consists of 4 DP slaves with the PROFIBUS addresses 3, 4, 5 and 6. The DP slave with address 4 is faulty. The instruction "DeviceStates" is executed for the DP master system with MODE = 2 (faulty/ not faulty). The following bits are set in the STATE parameter: Bit 0 = 1: A fault exists for at least one of the DP slaves. Bit 1 = 0: irrelevant Bit 2 = 0: irrelevant Bit 3 = 0: DP slave with address 3 is not faulty. Bit 4 = 1: DP slave with address 4 is faulty. Bit 5 = 0: DP slave with address 5 is not faulty. Bit 6 = 0: DP slave with address 6 is not faulty. Bit 7 = 0: irrelevant Bit 8 = 0: irrelevant ... 2754 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References ModuleStates: Read module status information of a module Description You can use the "ModuleStates" instruction to read the status information of the modules of a PROFINET IO device or PROFIBUS DP slave. The Boolean value that is output indicates the modules to which the selected status applies. You can, for example, read which modules are currently disabled in a PROFINET IO device. Information is also displayed as to whether the status information to be read applies to at least one of the modules. The instruction can be called in a cyclic OB as well as in an interrupt OB (e.g. OB82 - diagnostic interrupt). Parameters The following table shows the parameters of the "ModuleStates" instruction: Parameter Declaration Data type Memory area Description LADDR Input HW_DEVICE I, Q, M, D, L or constant Hardware identifier of the station (see description below) MODE Input UINT I, Q, M, D, L or constant Selection of module status information to be read (see description below) RET_VAL Return INT I, Q, M, D, L Status of instruction (see description below) STATE InOut VARIANT I, Q, M, D, L Buffer for the module status (see description below) You will find more detailed information on valid data types in "Overview of the valid data types (Page 1204)". Parameter LADDR You select the IO device or the DP slave at the LADDR parameter by means of the hardware identifier of the station. The hardware identifier is available: Either in the network view of the properties of the IO device station or DP slave station. Or in the PLC tag table for the listed system constants with the data type HW_DEVICE (for an IO device) or with the data type HW_DPSLAVE (for a DP slave). Parameter MODE You use the MODE parameter to read out status information. One of the following status information items can be read for the modules: 1: Modules are configured 2: Modules are faulty 3: Modules are disabled WinCC Basic V13.0 System Manual, 02/2014 2755 Programming the PLC 9.7 References 4: Modules exist 5: There is a problem in the modules. For example: - Maintenance demanded or recommended - Not accessible - Not available - Error occurred Parameter STATE The STATE parameter outputs the status of the modules selected with the MODE parameter. If the status selected using MODE applies to a module, the following bits are set to "1": Bit 0 = 1: Group display. The bit n of at least one module was set to "1". Bit n = 1: The status selected with MODE applies to the module in slot n-1 (example: bit 3 = slot 2). Use "BOOL" or "Array of BOOL" as data type: To only output the bit for group display of the status information, you can use the data type BOOL at the STATE parameter. To output the status information for all modules, use Array of BOOL with a length of 128 bits. Parameter RET_VAL Error code* Description (W#16#...) 0 No error 8091 Hardware identifier of the LADDR parameter does not exist. Check (for example, in the system constants) whether the value for LADDR exists in the project. 8092 LADDR does not address an IO device or DP slave. 8093 Invalid data type at the STATE parameter. 80B1 The instruction "ModuleStates" is not supported by the CPU. 80B2 The selected MODE parameter is not supported by the used CPU for the IO device/the DP slave in the LADDR parameter. 8452 The complete status information does not fit in the tag configured in the STATE parameter. * The error codes can be displayed as integer or hexadecimal values in the program editor. For additional information on toggling display formats, refer to "See also". Example An IO device includes 4 modules in slots 1 to 4. The module in slot 2 is faulty. The instruction "ModuleStates" is executed for the IO device with MODE = 2 (faulty/not faulty). The following bits are set in the STATE parameter: 2756 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Bit 0 = 1: A fault exists for at least one module. Bit 1 = 0: Slot number 0 (used by IO device) Bit 2 = 0: Module in slot number 1 is not faulty. Bit 3 = 1: Module in slot number 2 is faulty. Bit 4 = 0: Module in slot number 3 is not faulty. Bit 5 = 0: Module in slot number 4 is not faulty. Bit 6 = 0: irrelevant Bit 7 = 0: irrelevant GEN_DIAG: Generate diagnostics information Description The "GEN_DIAG" instruction generates diagnostics information for hardware components from other manufacturers for use in TIA Portal diagnostics. The GSD(GSDL/GSDML) file supplied by the manufacturer must first be installed before the instruction can be used. The instruction generates all diagnostic events (including those for maintenance). Use the LADDR parameter to select the hardware component for which you want to generate a diagnostic event. Use the MODE parameter to specify whether the event is to be outgoing or incoming. Use the DiagEvent parameter to define the diagnostic event in the DiagnosticDetail structure. The structure is created automatically in the local interface of the block when you define a tag at the DiagEvent parameter. The diagnostics information is provided synchronously. Diagnostics information transfer and alarm output are asynchronous. NOTICE Failsafe-specific errors messages are not valid If you define failsafe-specific diagnostics information at the DiagEvent parameter, the instruction will check this information and output the error code 80A1. WinCC Basic V13.0 System Manual, 02/2014 2757 Programming the PLC 9.7 References Parameters The following table shows the parameters of the "GEN_DIAG" instruction: Parameter Declaration Data type Memory area Description LADDR Input HW_ANY I, Q, M, D, L or constant Identification number of the hardware component MODE Input UINT I, Q, M, D, L or constant Selection of incoming/outgoing information: 1: The diagnostic event specified is an incoming event 2: The diagnostic event specified is an outgoing event 3: All diagnostic events are outgoing. There are therefore no hardware component faults (green diagnostics symbol). The DiagEvent parameter is not evaluated when MODE = 3. DiagEvent InOut DiagnosticDetail L Specifies the diagnostic event (see "DiagEvent parameter"). RET_VAL Return INT Status of instruction / error message (see "RET_VAL parameter") I, Q, M, D, L You will find more detailed information on valid data types in "Overview of the valid data types (Page 1204)". DiagEvent parameter The structure DiagnosticDetail is a system data type for specifying the diagnostic event. Its structure is as follows: Parameter Data type DiagnosticDet ail Struct 2758 Description ChannelI WORD nfo Channel properties (0...7) ALID UINT Local ID of the alarm. The ID uniquely identifies the alarm. TextID UINT ID of an alarm text in a text list. Channel Number UINT Manufacturer-specific channel number (0x0000 -- 0x7FFF) Addval_0 DWORD Placeholder for additional information The value / list of values depends on the connection error. TextID2 UINT Texts for CPU response (mode, OB calls, etc.). LADDR HW_ANY Identical to the LADDR parameter. TextListI d UINT 0: No text list 0: ID of the text list WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameter Channel Direction Data type Description UINT 0000: irrelevant FFF1: Input FFF2: Output FFF3: Input/Output Addval_1 DWORD Placeholder for additional information on the channel error (depends on the GSD file). For channel error types, see also: IEC 61158 (PROFINET IO Type 10 and PROFIBUS DP Type 3). Parameter RET_VAL Error code* (W#16#...) Explanation 0 No error 8080 Value in the MODE parameter is not supported. 8090 Identification for hardware component not available at the LADDR parameter. 8091 Diagnostics information cannot be generated for the hardware component addressed at the LADDR parameter. 80A1 Content of the DiagnosticsDetail structure at the DiagEvent parameter is invalid or inconsistent. Failsafe-specific diagnostics information defined at the DiagEvent parameter (not valid). 80A4 Hardware component addressed cannot be accessed. 80C1 Insufficient resources for parallel execution. * The error codes can be displayed as integer or hexadecimal values in the program editor. For additional information on toggling display formats, refer to "See also". GET_DIAG: Read diagnostic information Description You can use the "GET_DIAG" instruction to read out the diagnostic information of a hardware object. The hardware object is selected using the parameter LADDR. With the MODE parameter, you select which diagnostic information is to be read out. Parameters The following table shows the parameters of the "GET_DIAG" instruction: Parameter Declaration Data type Memory area MODE Input UINT I, Q, M, D, L or constant Use the MODE parameter to select which diagnostic data is to be output. LADDR Input HW_ANY (WORD) I, Q, M, L or constant Hardware identifier of the device. RET_VAL Return INT I, Q, M, D, L Status of the instruction CNT_DIAG Output UINT I, Q, M, D, L Number of output diagnostic details WinCC Basic V13.0 System Manual, 02/2014 Description 2759 Programming the PLC 9.7 References Parameter Declaration Data type Memory area Description DIAG InOut VARIANT I, Q, M, D, L Diagnostic information corresponds to the selected mode, see table below DETAIL InOut VARIANT I, Q, M, D, L Diagnostics details correspond with the selected mode. Parameter is hidden (only used for MODE = 3). For additional information on valid data types, refer to "Overview of the valid data types (Page 1204)". MODE parameter Depending on the value at the MODE parameter, different diagnostic data is output at the DIAG, CNT_DIAG and DETAIL output parameters. MODE Description DIAG CNT_DIAG DETAIL 0 Output of all supported diagnostic information for a module as DWORD, where Bit X=1 indicates that mode X is supported. Bit string of the supported modes as DWORD, where Bit X=1 indicates that mode X is supported. 0 - 1 Output of the inherent status of Diagnostics status. the addressed hardware Output of the inherent status object. of the addressed hardware object in accordance with the DIS structure. 0 - 2 Output of the status of all subordinate modules of the addressed hardware object. 0 - 3* Output of the inherent status of Output of the inherent status the addressed hardware of the addressed hardware object and detailed object in accordance with information on channel the DIS structure. diagnostics. Number of module status information. Module status information in accordance with the DiagnosticDetail structure. Diagnostics status. Output in accordance with the DNN structure. * Not supported by CPU S7-1200. DIS structure With parameter MODE = 1 or = 3, the diagnostic information is output in accordance with the DIS structure. In this case, enter the system data type "DIS" as data type for the tag declaration. The following table shows the meaning of the individual parameter values. Parameter Data type Value MaintenanceState DWORD Enum 2760 Description 0 No maintenance required 1 The module or device is disabled. 2 - WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameter ComponentStateD etail Data type DWORD Value Description 3 - 4 - 5 Maintenance required 6 Maintenance demanded 7 Error 8 Status unknown / error in subordinate module 9 - 10 Inputs/outputs are not available. Bit array Status of the module sub-modules: Bit 0 to 15: Status message of the module Bit 16 to 31: Status message of the CPU 0 to 2 (enum) Additional information: Bit 0: No additional information Bit 1: Transfer not permitted 3 Bit 3 = 1: At least one channel supports qualifiers for diagnostics 4 Bit 4 = 1: Maintenance required for at least one channel or one component. 5 Bit 5 = 1: Maintenance demanded for at least one channel or one component. 6 Bit 6 = 1: Error in at least one channel or one component. 7 to 10 Reserved (always = 0) 11 to 14 Bit 11 = 1: PNIO - sub-module correct Bit 12 = 1: PNIO - replacement module Bit 13 = 1: PNIO - incorrect module Bit 14 = 1: PNIO - module disconnected 15 Reserved (always = 0) 16 to 31 Status information for modules generated by the CPU: Bit 16 = 1: Module disabled Bit 17 = 1: CiR operation active Bit 18 = 1: Input not available Bit 19 = 1: Output not available bit 20 = 1: Overflow diagnostics buffer bit 21 = 1: Diagnostics not available bit 22 - 31: Reserved (always 0) OwnState UINT WinCC Basic V13.0 System Manual, 02/2014 Enum The value of the parameter Ownstate describes the maintenance status of the module. 0 No fault 1 The module or device is disabled. 2 Maintenance required 3 Maintenance demanded 4 Error 5 The module or the device cannot be reached from the CPU (valid for modules and devices below a CPU). 6 Inputs/outputs are not available. 2761 Programming the PLC 9.7 References Parameter IOState OperatingState Data type WORD UINT Value Description 7 - Bit array I/O status of the module 0 Bit 0 = 1: No maintenance required 1 Bit 1 = 1: The module or device is disabled. 2 Bit 2 = 1: Maintenance required 3 Bit 3 = 1: Maintenance demanded 4 Bit 4 = 1: Error 5 Bit 5 = 1: The module or the device cannot be reached from the CPU (valid for modules and devices below a CPU). 6 Inputs/outputs are not available. 7 Qualifier; bit 7 = 1, if bit 0, 2, or 3 are set 8 to 15 Reserved (always = 0) Enum 0 - 1 In STOP / Firmware update 2 In STOP / reset memory 3 In STOP / self start 4 In STOP 5 Memory reset 6 In START 7 In RUN 8 - 9 In HOLD 10 - 11 - 12 Module defective 13 - 14 No power 15 CiR 16 In STOP / without ODIS 17 In 18 19 20 DNN structure With parameter MODE = 2, the diagnostic information details are output in accordance with the DNN structure. In this case, enter the system data type "DNN" as data type for the tag declaration. The following table shows the meaning of the individual parameter values. 2762 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameter Data type Value Description SubordinateState UINT Enum Status of the subordinate module (see parameter OwnState of the DIS structure) SubordinateIOState WORD Bitarray Status of the inputs and outputs of the subordinate module (see parameter IO State of the DIS structure) DNNmode WORD Bitarray Bit 0 = 0: Diagnostics enabled Bit 0 = 1: Diagnostics disabled Bit 1 to 15: Reserved DiagnosticDetail structure With parameter MODE = 3, the diagnostic information details are output in accordance with the DiagnosticDetail structure. In this case, enter the system data type "DiagnosticDetail" as data type for the tag declaration. The following table shows the meaning of the individual parameter values. Parameter Data type Description ChannelInfo WORD Channel properties (0...7) ALID UInt Identification ID of alarm TextID UNIT ID of an alarm text in a text list. ChannelNumber UINT Manufacturer-specific channel number (0x0000 -- 0x7FFF) Addval_0 DWORD Placeholder for additional information The value / list of values depends on the connection error. TextID2 UInt Texts for CPU response (mode, OB calls, etc.). LADDR HW_ANY Identical to the LADDR parameter. TextListId UInt 0: No text list 0: ID of the text list ChannelDirection UInt 000: Manufacturer-specific 001: Input 002: Output 003: Input/Output 004 - 007: Reserved AddVal_1 DWORD Placeholder for additional information on the channel error (depends on the GSD file). For channel error types, see also: IEC 61158 (PROFINET IO Type 10 and PROFIBUS DP Type 3). RET_VAL parameter Error code* Description (W#16#...) 0 No error n The data area at the DETAIL parameter is too small. Not all details of the diagnostic data can be output. WinCC Basic V13.0 System Manual, 02/2014 2763 Programming the PLC 9.7 References Error code* Description (W#16#...) 8080 Value in the MODE parameter is not supported. 8081 Type at the DIAG parameter is not supported with the selected mode (parameter MODE). 8082 Type at the DETAIL parameter is not supported by the selected mode (parameter MODE). 8090 LADDR does not exist 80C1 Insufficient resources for parallel execution. * The error codes can be displayed as integer or hexadecimal values in the program editor. For additional information on toggling display formats, refer to "See also". 9.7.3.10 Pulse CTRL_PWM: Pulse-width modulation Description You can use the "CTRL_PWM" instruction to enable and disable a pulse output supported by the CPU using the software. Enter the hardware ID of the pulse generator that you want to control with the instruction at the input PWM. The pulse output is enabled when the bit in the ENABLE input of the instruction is set. - If ENABLE has a value of TRUE the pulse generator will generate a pulse with the properties defined in the device configuration. - When the bit in the ENABLE input is reset or the CPU changes to STOP, the pulse output is disabled and no more pulses are generated. BUSY always has the value of FALSE for S7-1200 since S7-1200 activates the pulse generator if the instruction "CTRL_PWM" is executed. The ENO enable output is set only when the EN enable input has signal state "1" and no errors have occurred during execution of the instruction. Note Use of the force table for PWM and PTO Digital inputs and outputs that are used for PWM and PTO cannot be forced. Digital inputs and outputs that were assigned via device configuration cannot be controlled by either the force table or the monitoring table. Requirement A prerequisite for the correct execution of the instruction is that the specified pulse generator is activated in the hardware configuration. 2764 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Open the properties of the module in the device view. Go to "Pulse generators (PTO/PWM)", open the desired PTO/PWM and activate the function the "Activate this pulse generator" under "General". Go to "Assigning parameters" and set the Pulse options. Note Pulse output parameters are assigned exclusively in the device configuration and not using the "CTRL_PWM" instruction. Any change of parameters that is intended to have an effect on the CPU must therefore be made while the CPU is in STOP mode. Changing the duration of the pulse is an exception. Changing the pulse duration from the user program The pulse duration setting made in the dialog "Pulse options" can be changed from the user program. The value set for "Initial pulse duration" is written in the output bytes of the pulse generator. The start address and the end address are displayed in the properties of the pulse generator under "I/O-addresses". To change the pulse duration, write the desired values in the output word address specified in the device configuration. Example: A value of 500 (decimal) is used for the "Initial pulse duration". The start address of the PTO/PWM is "1000" and the end address is "1001". The binary value of "0000000111110100" (=500 decimal) is written in both of the output bytes. - Start address (AB1000): 0000_0001 (BIN) - End address (AB1001): 1111_0100 (BIN) Please note that the pulse duration always depends on the parameters set for the Pulse duration format (hundredths, thousandths, ...). Parameters The following table shows the parameters of the "CTRL_PWM" instruction: Parameters Declaration Data type Memory area Description PWM Input HW_PWM I, Q, M, D, L or constant Hardware ID of the pulse generator I, Q, M, D, L or constant The pulse output is enabled when ENABLE = TRUE and disabled when ENABLE = FALSE. ENABLE Input WinCC Basic V13.0 System Manual, 02/2014 BOOL The hardware ID can be found in the properties of the pulse generator in the Device view. The hardware IDs of the pulse generators are also listed in the system constants. 2765 Programming the PLC 9.7 References Parameters Declaration Data type Memory area Description BUSY Output BOOL I, Q, M, D, L Processing status STATUS Output WORD I, Q, M, D, L Status of the instruction (see below). For additional information on valid data types, refer to "Overview of the valid data types (Page 1204)". Parameter STATUS Error code* (W#16#...) Description 0 No errors 80A1 Hardware ID of the pulse generator is invalid. * The error codes can be displayed as integer or hexadecimal values in the program editor. For additional information on toggling display formats, refer to "See also". 9.7.3.11 Recipes and data logging Recipe functions RecipeExport: Exporting recipes Description The "RecipeExport" instruction exports the recipe data from a data block to a CSV file on the memory card of the CPU. The export is triggered by the "REQ" parameter. The BUSY parameter is set to "1" during the export. During the export, the CSV file is created in the "Recipes" folder in the main directory of the memory card. The name of the data block is used as file name of the created CSV file. If a CSV file with an identical name already exists, it must be deleted before this export. After the execution of the instruction, BUSY is reset to "0" and the completion of the operation is indicated with "1" at the DONE parameter. If an error occurs during execution, this is signaled by the parameters ERROR and STATUS. 2766 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameters The following table shows the parameters of the "RecipeExport" instruction: Parameter Declaration Data type Memory area Description REQ Input BOOL I, Q, M, D, L, T, C or constant Control parameter REQUEST: Activates the export on a rising edge. (T and C are only available in LAD and FBD with S7-1500) RECIPE_DB InOut VARIANT D Pointer to the recipe data block. For information on the structure of the data block, refer to: Structure of a recipe DB (Page 2770) DONE Output BOOL I, Q, M, D, L Status parameter 0: Job not yet started or still executing. 1: Job executed without errors. BUSY Output BOOL I, Q, M, D, L Status parameter 0: The instruction is not executed. 1: The instruction is executed. ERROR Output BOOL I, Q, M, D, L Status parameter 0: Neither warning nor error. 1: An error has occurred. STATUS supplies detailed information on the type of error. STATUS Output WORD I, Q, M, D, L Status parameter See the "STATUS" parameter table. For additional information on valid data types, refer to "Overview of the valid data types (Page 1204)". Parameter STATUS Error code* (W#16#...) Explanation 0 No error occurred 7000 No job processing active 7001 Start of job processing. Parameter BUSY = 1, DONE = 0 7002 Intermediate call (REQ irrelevant): Instruction already active; BUSY has the value "1". 8090 File name of the CSV file contains invalid characters. The file name of the CSV file is identical to the name of the data block. 8091 The data structure referenced with RECIPE_DB cannot be processed. 8092 Data structure at RECIPE_DB parameter exceeds 5000 bytes. 80B3 Insufficient memory space on the memory card or the internal load memory. 80B4 The memory card is write-protected. 80C0 CSV files is temporarily locked. WinCC Basic V13.0 System Manual, 02/2014 2767 Programming the PLC 9.7 References Error code* (W#16#...) Explanation 80C1 Data block temporarily locked. * The error codes can be displayed as integer or hexadecimal values in the program editor. For additional information on toggling display formats, refer to "See also". RecipeImport: Importing recipes Description The "RecipeImport" instruction imports the recipe data from a CSV file on the memory card into the data block at the RECIPE_DB parameter. The values in the data block are overwritten in the process. Note the following when importing the CSV file: The CSV file must be located in the "Recipes" directory of the memory card. The name of the CSV file must match the name of the data block at the RECIPE_DB parameter. The first line (header) of the CSV file contains the name of the recipe components (see also: Structure of a recipe DB (Page 2770)). The first line is ignored during import. The names of the recipe components in the CSV file and the data block are not reconciled during import. In each case the first value in each line of the CSV file is the index number of the recipe. The individual recipes are imported in the order of the index. For this, the index in the CSV file has to be in ascending order and may contain no gaps (if this is not the case, the error message 80B0 is output at the STATUS parameter. The CSV file may not contain more recipe data records than provided for in the data block. The maximum number of data records is indicated by the array limits in the data block. The import is triggered by the "REQ" parameter. The BUSY parameter is set to "1" during the import. After the execution of the instruction, BUSY is reset to "0" and the completion of the operation is indicated with "1" at the DONE parameter. If an error occurs during execution, this is signaled by the parameters ERROR and STATUS. Parameters The following table shows the parameters of the "RecipeImport" instruction: Parameter Declaration Data type Memory area Description REQ Input BOOL I, Q, M, D, L, T, C or constant Control parameter REQUEST: Activates the import on a positive edge. (T and C are only available in LAD and FBD with S7-1500) RECIPE_DB 2768 InOut VARIANT D Pointer to the recipe data block. For information on the structure of the data block, refer to: Structure of a recipe DB (Page 2770) WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameter Declaration Data type Memory area Description DONE Output BOOL I, Q, M, D, L Status parameter 0: Job not yet started or still executing. 1: Job executed without errors. BUSY Output BOOL I, Q, M, D, L Status parameter 0: The instruction is not executed. 1: The instruction is executed. ERROR Output BOOL I, Q, M, D, L Status parameter 0: Neither warning nor error. 1: An error has occurred. STATUS supplies detailed information on the type of error. STATUS Output WORD I, Q, M, D, L Status parameter See the "STATUS" parameter table. For additional information on valid data types, refer to "Overview of the valid data types (Page 1204)". Parameter STATUS Error code* (W#16#...) Explanation 0 No error occurred 7000 No job processing active 7001 Start of job processing. Parameter BUSY = 1, DONE = 0 7002 Intermediate call (REQ irrelevant): Instruction already active; BUSY has the value "1". 8090 The file name contains invalid characters. 8092 No matching CSV file found for the import. Possible cause: The name of the CSV file does not match the name of the recipe DB. 80C0 CSV file is temporarily locked. 80C1 Data block is temporarily locked. 80B0 Numbering in the index of the CSV file is not continuous, not ascending or exceeds the maximum number (array limit) in the data block. 80B1 Structure of the recipe data block and the CSV file do not match: The CSV file contains too many fields. 80B2 Structure of the recipe data block and the CSV file do not match: The CSV file contains too few fields. 80D0 +n Structure of the recipe data block and the CSV file do not match: Data type in field n does not match (n<=46). 80FF Structure of the recipe data block and the CSV file do not match: Data type in field n does not match (n>46). * The error codes can be displayed as integer or hexadecimal values in the program editor. For additional information on toggling display formats, refer to "See also". WinCC Basic V13.0 System Manual, 02/2014 2769 Programming the PLC 9.7 References Structure of a recipe DB Introduction The following sections describes the structure of a recipe DB based on a simple example. The recipe DB consists of five data records, three of which are used. The fourth and fifth data records are left free for later expansions. Each data record contains one recipe, which is made up of the recipe name and eight ingredients. product name water barley wheat hops yeast waterT mp mashT mp mashTi me QTest Pils 10 9 3 280 39 40 30 100 0 Lager 10 9 3 150 33 50 30 120 0 BlackBe er 10 9 3 410 47 60 30 90 1 Not_use d 0 0 0 0 0 0 0 0 0 Not_use d 0 0 0 0 0 0 0 0 0 Structure of the recipe data block The recipe data are implemented as follows in a global data block: The template for all recipes is the PLC data type "Beer_Recipe" with the recipe components "procutname", "water", etc. with the corresponding data types. In a global data block, the PLC data type is used as Array [1.. 5] of "Beer_Recipe". The array limits (1 to 5 in this case) indicate the maximum number of recipes that the DB may contain. The values for the recipe components are added as start value in the data block. The global DB is interconnected with the instruction via the InOut parameter RECIPE_DB. 2770 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Exporting to CSV file After the execution of the "RecipeExport (Page 2766)" instruction the data of the DB are written to a CSV file with the following structure: Recipe_DB.csv index,productname,water,barley,wheat,hops,yeast,waterTmp,mashTmp,mashTime,QTest 1,"Pils",10,9,3,280,39,40,30,100,0 2,"Lager",10,9,3,150,33,50,30,120,0 3,"BlackBeer",10,9,3,410,47,60,30,90,1 4,"Not_used",0,0,0,0,0,0,0,0,0 5,"Not_used",0,0,0,0,0,0,0,0,0 Display in Excel The CSV file can be opened in Excel to make reading and editing easier. If the commas are not recognized as separators when you open the file, use the Excel import function to output the data in structured form: Editing the CSV file The CSV file can be uploaded to the PC/programming device by means of the Web server and edited. After editing, the modified file can be reloaded in the CPU. You can use the "RecipeImport (Page 2768)" instruction to re-import the modified data from the CSV file into the data block. Note that the modified data must still be compatible with the data block. In other words: No changes may be made to the structure in the table (for example, by adding ingredients in a new column). If you add data records to the file, make sure when importing into the data block that the array limits through which you specify the maximum number of data records correspond to at least the number of data records. An index is automatically generated during export to the CSV file. If you create additional data records, add consecutive index numbers accordingly. The values in the table cells must correspond to the data types used in the data block with respect to format as well as length. - Example 1: If data type INT was used in the data block, you can only use integers in the table. - Example 2: If data type SINT was used in the data block, you can only use integers with the values -128 to +127 in the table. Always keep in mind the permitted data types and data areas as listed in the table below when you make changes in the table. WinCC Basic V13.0 System Manual, 02/2014 2771 Programming the PLC 9.7 References Format Note Floatingpoint numbers Data type LReal +9.9999999999999E +999 Always written exponentially Real +9.999999E+99 Always written exponentially Signed integers LInt +9999999999999999999 Value range for signed integers: -9223372036854775808 .. +9223372036854775807 DInt +9999999999 Value range of integers: -2147483648 to +2147483647 Int +99999 Value range of integers: -32768 to +32767 SInt +999 Value range of integers: -128 to +127 ULInt +9999999999999999999 Value range of integers: 0 to +18446744073709551615 9 UDInt +9999999999 Value range of integers: 0 to +4294967295 UInt +99999 Value range of integers: 0 to + 65535 USInt +999 Value range of integers: 0 to +255 LWord +9999999999999999999 Value range of integers: +00000000000000000000 to 9 +18446744073709551615 DWord +9999999999 Value range of integers: +0000000000 to +4294967295 Word +99999 Value range of integers: +00000 to + 65535 Byte +999 Value range of integers: +000 to +255 Bool 9 Range of values: 0 or 1 LTIME hhh:mm:ss.999 ISO format with milliseconds TIME hhh:mm:ss.999 ISO format with milliseconds S5TIME hhh:mm:ss.999 ISO format with milliseconds LDT YYYY-MM-DD hh:mm:ss. ISO format with milliseconds 999 DTL YYYY-MM-DD hh:mm:ss. ISO format with milliseconds 999 DT YYYY-MM-DD hh:mm:ss. ISO format with milliseconds 999 DATE YYYY-MM-DD ISO format LTime_Of_ Day hh:mm:ss.999_999_999 ISO format TOD hh:mm:ss.999 ISO format String "abcd" The string must be in double quotation marks. Char "a" Individual character in double quotation marks. Unsigned integers Binary numbers Date and time Character Data logging Data logging - Overview Saving process values The data logging instructions are used in the user program to save process values to data logs. Data logs can be saved on the Memory Card (MC) or in the internal load memory. The data logs are saved in CSV format (Comma Separated Value). 2772 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References The data logging instructions are used in your program to create or open a data log, to write an entry and to close the data log file. You decide by the creation of the data buffer which program values are stored in the data log during the creation of the data buffer. The data buffer is used as a memory for new data log entries. New values have to be written to the buffer before "DataLogWrite (Page 2787)" is called. During execution of the "DataLogWrite (Page 2787)" instruction, data is written from the buffer to a data log record. &38 3/& '$7$ 'DWDORJV 'RZQORDG FVY :HEVHUYHU 0HPRU\ FDUG :HEEURZVHU 'DWDORJ LQVWUXFWLRQV 3URFHVVYDOXHV Data log files can be copied to the PC as follows: If the PROFINET interface is connected to the PC, you use a Web browser to access the data logs via the Web server. The CPU can be in RUN or STOP mode for this. If the CPU is in "RUN" mode, the program continues running while the Web server is transferring data. If there is a memory card in the CPU, you can remove this card and insert it into a standard slot for SD (Secure Digital) cards or MMC (MultiMediaCard) cards on a PC or programming device. Use File Manager to transfer the data log files from the memory card to the PC. The CPU goes to "STOP" when you remove the memory card. Properties of the data log Writing of the data records of a data log is carried out in accordance with the principle of a ring buffer. New data records are added until the maximum number of data records is reached (RECORD parameter). The next data record then overwrites the "oldest" data record of the data log. If you want to prevent data records from being overwritten, use the "DataLogNewFile (Page 2792)" instruction to create a new data log file based on the current data log. New data records are then written into the new data log. WinCC Basic V13.0 System Manual, 02/2014 2773 Programming the PLC 9.7 References Creating data logs With the "DataLogCreate (Page 2775)" instruction, you can create a new data log file in the ""\DataLogs" directory of the load memory. The name assigned at the NAME parameter is the designation for the data log and is also used the file name for the CSV file. The file is stored in the directory "DataLogs". The block parameter DATA specifies the data buffer for the new data log object and the columns and data types in the data log. The columns and data types of a data record in the data log are generated by the elements in the structure declaration or the array declaration of this data buffer. Each element of a structure or of an array corresponds to a column in a line in the data log. You can use the HEADER block parameter to assign a header text in the header to each column. The "DataLogCreate (Page 2775)" instruction returns an ID. This ID is used by the other data logging instructions as a reference for the created data log. Opening data logs You use the instruction "DataLogOpen" (S7-1200 and S7-1500) to open an existing data log on the memory card. A data log must be open before you can write new data records to it. Data log opens automatically when you execute the instructions "DataLogCreate (Page 2775)" and "DataLogNewFile (Page 2792)". Up to 10 data logs can be open simultaneously. You can select the data log to be opened using the ID or name of the data log. If you specify the ID and the name of the data log in the ID and NAME parameters, respectively, the data log will be identified based on the ID. The data log name will not be compared. If you select the data log using the NAME parameter and no ID is specified, the ID will be displayed in the ID parameter when the data log is opened. If you select the data log using the ID parameter and no name is specified, the name will be displayed in the NAME parameter when the data log is opened. You use the MODE parameter to specify whether the data records of the data log are to be deleted upon opening. Writing to data logs A data log must be open ("DataLogOpen (Page 2782)" instruction) before a data record can be written to a data log. The "DataLogWrite (Page 2787)" instruction writes a data record to the data log. Closing data logs You use the "DataLogClose (Page 2789)" instruction to close an open data log. You select the data log using the ID parameter. The data log is closed automatically when the CPU switches to STOP and upon restart. 2774 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Deleting data logs You use the instruction "DataLogDelete (Page 2791)" (S7-1500) to delete a data log file from the memory card. The data log and the data records it contains can only be deleted if the log was created with the instruction "DataLogCreate (Page 2775)". Select the data log to be deleted using the NAME and ID parameters. The ID parameter is evaluated first. If there is a data log with the relevant ID, the NAME parameter will not be evaluated. If the value "0" is used at the ID parameter, a value with the data type STRING must be used at the NAME parameter. Clearing data logs You use the instruction "DataLogClear (Page 2785)" (S7-1500) to delete all the data records in an existing data log. The instruction does not delete the optional header of the CSV file (see the description of the HEADER parameter of the instruction "DataLogCreate (Page 2775)"). You use the ID parameter to select the data log whose data records are to be deleted. Before you can delete data records, the data log must be open. New file for data logs You use the instruction "DataLogNewFile (Page 2792)" (S7-1200) or "DataLogTypedNewFile (Page 2794)" (S7-1500) to create a new data log with the same properties as an existing data log. This allows you to retain the contents of an existing data log. When called, the instruction creates a new data log on the memory card or in the internal load memory with the name defined at the NAME parameter. You use the ID parameter to specify the ID of the old data log whose properties you want to apply to the new data log. The ID of the new data log is then output via the ID parameter. You specify the file size of the new data log with the RECORDS parameter of the instruction. You can run a consistency check for "DataLogTypedNewFile (Page 2794)" (S7-1500). DataLogCreate: Create data log Description With the "DataLogCreate" instruction you create a data log. The data log is saved on the memory card or in the internal load memory in the directory "\DataLogs". The amount of data that can be stored in a data log is dependent on the available space on the memory card or the storage space in the internal load memory of the CPU. You specify the maximum number of data records that can be stored in a data log in the RECORDS parameter. If the specified maximum number of data records in the data log is reached, the oldest data record will be overwritten. To avoid overwriting of existing data records, use the "DataLogNewFile (Page 2792)" instruction. The instruction can be used to create a new data log with the same structure when the number specified at the RECORDS parameter is reached (return value 1 at the STATUS parameter of the "DataLogWrite (Page 2787)" instruction). The data records are then saved in the new data log. WinCC Basic V13.0 System Manual, 02/2014 2775 Programming the PLC 9.7 References You can specify the name for the data log in the NAME parameter. The data log is created in CSV (Comma Separated Value) format. With the HEADER parameter, you can create an (optional) header for the data log. Once the data log is created, it is opened automatically. This means that data can be written. Parameters The following table shows the parameters of the "DataLogCreate" instruction: Parameter Declaration Data type Memory area Description REQ Input BOOL I, Q, M, L, D, T, C or constant Execution of the instruction (T and C are only available in LAD and FBD with S7-1500) RECORDS FORMAT Input Input UDInt UInt The data log is created with a rising edge at the parameter REQ. I, Q, M, L, D or constant Maximum number of data records in the data log I, Q, M, L, D or constant Data format: If the instruction "DataLogWrite (Page 2787)" writes more records than specified in this parameter, the oldest record is overwritten. 0: Internal (not supported) 1: CSV (Comma separated values) TIMESTAMP Input UInt I, Q, M, L, D or constant Time stamp: 0: No time stamp 1: Date and time The extra columns in the header are automatically added if time-stamping is activated. NAME Input VARIANT L, D Name of the data log The specified name is also used as a file name for the csv file. The restrictions for Windows file names apply when assigning the name. The following characters must not be used: "\", "/", ":", "*", "?", "<", ">", "|", "space" ID InOut DWORD I, Q, M, L, D Object ID of the data log (only output) The ID of the data log is required for further data logging instructions to address the created data log. HEADER InOut VARIANT L, D Header of the data log (optional) The parameter is hidden after the instruction is added. The header is written as the first line in the CSV file. DATA 2776 InOut VARIANT L, D Pointer to the data structure that is to be written as data record when executing the instruction "DataLogWrite (Page 2787)". WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameter Declaration Data type Memory area Description DONE Output BOOL I, Q, M, L, D Status parameter: 0: Processing not yet complete. 1: Processing of instruction finished successfully. BUSY Output BOOL I, Q, M, L, D Status parameter: 0: Processing of the instruction has not started, completed, or canceled. 1: Processing of the instruction is in progress. ERROR Output BOOL I, Q, M, L, D Status parameter: 0: No error. 1: An error occurred during execution of the instruction. Detailed information is output via the STATUS parameter. STATUS Output WORD I, Q, M, L, D Detailed status information: Detailed error and status information is output at the parameter STATUS. The parameter is only set for the duration of one call. To display the status, you should therefore copy the STATUS parameter to a free data area. You can find additional information on valid data types under "Overview of the valid data types (Page 1204)". HEADER parameter The HEADER parameter is a VARIANT pointer to a data block that defines a header for the CSV file (header). The header is always the first line in the CSV file representation. When creating a header, remember that the individual columns must be separated by a comma (S7-1200) or a semicolon (S7-1500). A STRING, Array of BYTE, or Array of CHAR data type can be used for the individual column names. A longer character string is possible with the Array [...] of type data type than with the STRING data type. When the STRING data type is used, the length is limited to 254 bytes. If no header is to be created, do not specify a value in the HEADER parameter. DATA parameter The DATA parameter is a VARIANT pointer to a structure or an array in a data block. An element of a structure or an array corresponds to a column in the data log with a specific data type. Note the following when creating the data block: WinCC Basic V13.0 System Manual, 02/2014 2777 Programming the PLC 9.7 References The number of columns must correspond to the number of columns defined in the HEADER parameter. Each element of the structure or the array corresponds to a column entry in the CSV file. Therefore, no nesting structures (STRUCT in STRUCT) may be used when using the data type STRUCT. The data structure can contain up to 256 elements. If there are more than 256 elements, error code 8C52 is output at the STATUS parameter. The tags of the data block can be set as retentive or non-retentive tags. However, the retentivity setting must be the same for all tags of the data block. STATUS (S7-1200) parameter Error code* Description (W#16#...) 0 No errors. 7000 No job processing active. 7001 Start of job processing. Parameter BUSY = 1, DONE = 0 7002 Intermediate call (REQ irrelevant): Instruction already active; BUSY has the value "1". 8070 Complete internal instance memory is assigned. 8090 Invalid file name (see description of the NAME parameter). 8093 Data log already exists. 8097 File length exceeds the file system limit. 80B3 Insufficient memory space on the memory card. 80B4 The memory card is write-protected. 80C1 Too many data logs are open. 80C3 Resources are not sufficient. Possible causes: Multiple calling of instructions with different parameters. More than 10 data logs open simultaneously. At least one data log must be closed in order to continue because the instruction "DataLogCreate" automatically opens the the log that is being created. 8453 Invalid format selection. 8553 Invalid time stamp. 8B51 Invalid data type at HEADER parameter. 8C20 String with length specification other than 254 used. 8C51 Invalid data type at DATA parameter. 8C52 Structure at the parameter DATA contains more than 256 elements. * The error codes can be displayed as integer or hexadecimal values in the program editor. For additional information on toggling display formats, refer to "See also". 2778 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References STATUS (S7-1500) parameter Error code* Description (W#16#...) 0 No errors. 7000 No job processing active. 7001 Start of job processing. Parameter BUSY = 1, DONE = 0 8070 Complete internal instance memory is assigned. 8090 Invalid file name (see description of the NAME parameter). 8091 "NAME" parameter is not a string. 8093 Data log already exists. 8097 File length exceeds the file system limit. 80B3 Insufficient memory space on the memory card. 80B4 The memory card is write-protected. 80C0 Access currently not possible. 80C1 Too many data logs are open. 80C3 Resources are not sufficient. Possible causes: Multiple calling of instructions with different parameters. More than 10 data logs open simultaneously. At least one data log must be closed in order to continue because the instruction "DataLogCreate" automatically opens the the log that is being created. 8253 The RECORDS parameter has an invalid value. 8353 Invalid format selection. 8453 Invalid time stamp. 8B51 Invalid data type at HEADER parameter. 8C51 Invalid data type at DATA parameter. 8C52 Structure at the parameter DATA contains more than 256 elements. * The error codes can be displayed as integer or hexadecimal values in the program editor. For additional information on toggling display formats, refer to "See also". Example In the following example, a simple data log is created with a time stamp and three process values. Tags in the global data block The values for the input parameters of the data log are stored in the global data block "DataLogDB": DataLogName (String): The tag contains the name of the data log which is also used as the file name for the CSV file. DataLogID (DInt): The ID of the data log is written in this tag when the instruction is called. - The ID is automatically assigned by the instruction. - Use the tag "DataLogID" in other DataLog instructions in order to address this data log. WinCC Basic V13.0 System Manual, 02/2014 2779 Programming the PLC 9.7 References MyHeader (String): This tag contains the header of the DataLog, i.e. the column headings for the process values. A semicolon is used as a delimiter for the columns when using a S7-1500. MyData (Struct): This tag contains the three process values that are written in the data log. Each time a record is written (instruction "DataLogWrite (Page 2787)") the current values are written in a new record. Calling the "DataLogCreate" instruction The instruction is called with the following input parameters: REQ (BOOL): With REQ = "1" the data log is created. RECORD (3): A maximum of three data records can be written in the data log. Thereafter, the oldest data record is overwritten. FORMAT (1): The data log is created as a CSV file. TIMESTAMP (1): Activated. Two additional columns are automatically created (date and time) for the data log. The current time stamp is written in the data record each time "DataLogWrite (Page 2787)" is executed. NAME (VARIANT): Pointer to the tag "DataLogName" in the data block "DataLogDB". ID (VARIANT): Pointer to the tag "DataLogID" in the data block "DataLogDB". HEADER (VARIANT): Pointer to the tag "MyHeader" in the data block "DataLogDB". DATA (VARIANT): Pointer to the tag "MyData" in the data block "DataLogDB". 2780 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Readout of the data log via the web server You can readout the created data log with the web server: Activate the web server in the properties of the CPU. The authorization "...to read files" must be activated for the web server in order to readout the data log. You can access the web server via the Internet browser by entering the IP address of the CPU as a URL. Under "Filebrowser" the directory "\DataLogs" was automatically created which contains the data log. The DataLog only contains one entry "//END" if the instruction "DataLogWrite (Page 2787)" has still not been executed. The first data record is written after the initial execution of "DataLogWrite (Page 2787)". See also Data logging - Overview (Page 2772) WinCC Basic V13.0 System Manual, 02/2014 2781 Programming the PLC 9.7 References DataLogOpen: Open data log DataLogOpen: Open data log Description You use the "DataLogOpen" instruction to open an existing data log on the memory card. A data log must be open before you can write new data records to it. Data log opens automatically when you execute the instructions "DataLogCreate (Page 2775)" and "DataLogNewFile (Page 2792)". Up to 10 data logs can be open simultaneously. You can select the data log to be opened using the ID or name of the data log. If you specify the ID and the name of the data log in the ID and NAME parameters, respectively, the data log will be identified based on the ID. The data log name will not be compared. If you select the data log using the NAME parameter and no ID is specified, the ID will be displayed in the ID parameter when the data log is opened. If you select the data log using the ID parameter and no name is specified, the name will be displayed in the NAME parameter when the data log is opened. You use the MODE parameter to specify whether the data records of the data log are to be deleted upon opening. Parameters The following table shows the parameters of the "DataLogOpen" instruction: Parameter Declaration Data type Memory area Description REQ Input BOOL I, Q, M, L, D or constant Execution of the instruction upon a rising edge. MODE Input UInt I, Q, M, L, D or constant Mode for opening the data log: MODE= "0" Data records of the data log are retained MODE= "1" Data records of the data log are deleted, but the header is retained NAME Input VARIANT L, D (File) name of the data log. ID InOut DWORD I, Q, M, L, D Object ID of the data log. DONE Output BOOL I, Q, M, L, D Instruction was executed successfully. BUSY Output BOOL I, Q, M, L, D Execution of instruction not yet complete. 2782 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameter Declaration Data type Memory area Description ERROR Output BOOL I, Q, M, L, D 0: No error. 1: An error occurred during execution of the instruction. Detailed information is output via the STATUS parameter. STATUS Output WORD I, Q, M, L, D Status parameter The parameter is only set for the duration of one call. To display the status, you should therefore copy the STATUS parameter to a free data area. For additional information on valid data types, refer to "Overview of the valid data types (Page 1204)". Parameter STATUS Error code* (W#16#...) Description 0 No errors. 2 Warning: Data log file has already been opened by this application. 7000 No job processing active. 7001 Start of job processing. Parameter BUSY = 1, DONE = 0 7002 Intermediate call (REQ irrelevant): Instruction already active; BUSY has the value "1". 8070 Complete internal instance memory is assigned. 8090 There are inconsistencies between the data log definition and existing data log data. 8091 A data type other than String was used at the NAME parameter. 8092 Data log does not exist. 80B4 The memory card is write-protected. 80C0 The data log file is locked. * The error codes can be displayed as integer or hexadecimal values in the program editor. For additional information on toggling display formats, refer to "See also". See also Data logging - Overview (Page 2772) DataLogOpen: Open data log Description You use the "DataLogOpen" instruction to open an existing data log on the memory card. A data log must be open to write new data records to it. Data log opens automatically when you execute the instructions "DataLogCreate (Page 2775)" and "DataLogNewFile (Page 2792)". WinCC Basic V13.0 System Manual, 02/2014 2783 Programming the PLC 9.7 References Up to 10 data logs can be open simultaneously. You can select the data log to be opened using the ID or name of the data log. If you specify the ID and the name of the data log in the ID and NAME parameters, respectively, the data log will be identified based on the ID. The data log name will not be compared. If you select the data log using the NAME parameter and no ID is specified, the ID will be displayed in the ID parameter when the data log is opened. If you select the data log using the ID parameter and no name is specified, the name will be displayed in the NAME parameter when the data log is opened. You use the MODE parameter to specify whether the data records of the data log are to be deleted upon opening. The parameter DATA enables a consistency check between the data log to be opened and the definition of the data log of the instruction "DataLogCreate (Page 2775)". The consistency check can only be executed if the data log was created with the instruction "DataLogCreate (Page 2775)": If you are using the same pointer at the DATA parameter as at the DATA parameter of the "DataLogCreate (Page 2775)" instruction, a check is performed to determine whether the data types match. If the data types do not match, the error code W#16#80A0 is output at the STATUS parameter. If the data log to be opened was not created with "DataLogCreate (Page 2775)", a consistency check is not possible. In this case, enter the value "NULL" in the DATA parameter. Parameters The following table shows the parameters of the "DataLogOpen" instruction: Parameter Declaration Data type Memory area Description REQ Input BOOL I, Q, M, L, D, T, C or constant Execution of the instruction upon a rising edge. (T and C are only available in LAD and FBD with S7-1500) MODE Input UInt I, Q, M, L, D or constant Mode for opening the data log: MODE= "0" Data records of the data log are retained MODE= "1" Data records of the data log are deleted, but the header is retained NAME Input VARIANT L, D (File) name of the data log. ID InOut DWORD I, Q, M, L, D Object ID of the data log. DATA InOut VARIANT L, D With consistency check: Pointer to the data area at the DATA parameter of the "DataLogCreate (Page 2775)" instruction. DONE Output BOOL I, Q, M, L, D Instruction was executed successfully. BUSY Output BOOL I, Q, M, L, D Execution of instruction not yet complete. 2784 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameter Declaration Data type Memory area Description ERROR Output BOOL I, Q, M, L, D 0: No error. 1: An error occurred during execution of the instruction. Detailed information is output via the STATUS parameter. STATUS Output WORD I, Q, M, L, D Status parameter The parameter is only set for the duration of one call. To display the status, you should therefore copy the STATUS parameter to a free data area. For additional information on valid data types, refer to "Overview of the valid data types (Page 1204)". Parameter STATUS Error code* (W#16#...) Description 0 No errors. 2 Warning: Data log file has already been opened by this application. 7000 No job processing active. 7001 Start of job processing. Parameter BUSY = 1, DONE = 0 7002 Intermediate call (REQ irrelevant): Instruction already active; BUSY has the value "1". 8070 Complete internal instance memory is assigned. 8090 There are inconsistencies between the data log definition and existing data log data. 8091 A data type other than String was used at the NAME parameter. 8092 Data log does not exist. 80A0 Data types inconsistent. The data log at the ID parameter uses different data types than specified in the DATA parameter. 80B4 The memory card is write-protected. 80C1 Too many files open. * The error codes can be displayed as integer or hexadecimal values in the program editor. For additional information on toggling display formats, refer to "See also". See also Data logging - Overview (Page 2772) DataLogClear: Empty data log Description The "DataLogClear" instruction deletes all data records in an existing data log. The instruction does not delete the optional header of the CSV file (see the description of the HEADER parameter of the instruction "DataLogCreate (Page 2775)"). WinCC Basic V13.0 System Manual, 02/2014 2785 Programming the PLC 9.7 References You use the ID parameter to select the data log whose data records are to be deleted. Requirement Before you can delete data records, the data log must be open (see "DataLogOpen (Page 2782) instruction"). Parameters The following table shows the parameters of the "DataLogClear" instruction: Parameter Declaration Data type Memory area Description REQ Input BOOL I, Q, M, L, D, T, C or constant Execution of the instruction upon a rising edge. (T and C are only available in LAD and FBD with S7-1500) ID InOut DWORD I, Q, M, D, L Object ID of the data log DONE Output BOOL I, Q, M, D, L Instruction was executed successfully. BUSY Output BOOL I, Q, M, D, L Execution of the instruction not yet complete. ERROR Output BOOL I, Q, M, D, L 0: No error. 1: An error occurred during execution of the instruction. Detailed information is output at the STATUS parameter. STATUS Output WORD I, Q, M, D, L Status parameter The parameter is only set for the duration of one call. To display the status, you should therefore copy the STATUS parameter to a free data area. For additional information on valid data types, refer to "Overview of the valid data types (Page 1204)". Parameter STATUS Error code* (W#16#...) Explanation 0000 No error. 7000 No job processing active. 7001 Start of job processing. Parameter BUSY = 1, DONE = 0 7002 Intermediate call (REQ irrelevant): Instruction already active; BUSY has the value "1". 8080 The data log file selected with the ID parameter cannot be processed with the "DataLogClear" instruction. 8092 Data log does not exist. 80B0 Data log is not open. 2786 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Error code* (W#16#...) Explanation 80B4 The memory card is write-protected. * The error codes can be displayed as integer or hexadecimal values in the program editor. For additional information on toggling display formats, refer to "See also". See also Data logging - Overview (Page 2772) DataLogWrite: Write data log Description The instruction "DataLogWrite" is used to write a data record to an existing data log. The ID parameter is used to select the data log to which the data record is to be written. To create a new data record, the data log must be open. The instruction creates a new data record in the format that was specified in the DATA parameter when the data log was created. Before calling the "DataLogWrite" instruction, transfer the data to the tag that you interconnected at the DATA parameter of the "DataLogCreate" instruction. When the "DataLogWrite" instruction is executed, the transferred data is copied to the data log. NOTICE Data log data loss when the power supply to the CPU is interrupted If the power supply is interrupted during execution of the "DataLogWrite" instruction, the data record to be transferred is lost. Parameters The following table shows the parameters of the "DataLogWrite" instruction: Parameter Declaration Data type Memory area Description REQ Input BOOL I, Q, M, L, D, T, C or constant Execution of the instruction upon a rising edge. (T and C are only available in LAD and FBD with S7-1500) ID InOut DWORD I, Q, M, L, D Object ID of the data log DONE Output BOOL I, Q, M, L, D Instruction was executed successfully. BUSY Output BOOL I, Q, M, L, D Execution of the instruction not yet complete. WinCC Basic V13.0 System Manual, 02/2014 2787 Programming the PLC 9.7 References Parameter Declaration Data type Memory area Description ERROR Output BOOL I, Q, M, L, D 0: No error. 1: An error occurred during execution of the instruction. Detailed information is output via the STATUS parameter. STATUS Output WORD I, Q, M, L, D Status parameter The parameter is only set for the duration of one call. To display the status, you should therefore copy the STATUS parameter to a free data area. For additional information on valid data types, refer to "Overview of the valid data types (Page 1204)". Parameter STATUS (S7-1200) Error code* Description (W#16#...) 0 No errors 0001 Last possible data record created at the end of the file. Creating another data record will overwrite an older data record. 7000 No job processing active. 7001 Start of job processing. Parameter BUSY = 1, DONE = 0 7002 Intermediate call (REQ irrelevant): Instruction already active; BUSY has the value "1". 8070 Complete internal instance memory is assigned. 8092 Data log does not exist. 80B0 Data log is not open. 80B3 Insufficient memory space on the memory card. 80B4 The memory card is write-protected. 80C0 Data log is locked. * The error codes can be displayed as integer or hexadecimal values in the program editor. For additional information on toggling display formats, refer to "See also". Parameter STATUS (S7-1500) Error code* Description (W#16#...) 0 No errors 0001 Last possible data record created at the end of the file. Creating another data record will overwrite an older data record. 7000 No job processing active. 7001 Start of job processing. Parameter BUSY = 1, DONE = 0 8070 Complete internal instance memory is assigned. 8092 Data log does not exist. 2788 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Error code* Description (W#16#...) 80B0 Data log is not open. 80B3 Insufficient memory space on the memory card. 80B4 The memory card is write-protected. 80C0 Data log is locked. * The error codes can be displayed as integer or hexadecimal values in the program editor. For additional information on toggling display formats, refer to "See also". See also Data logging - Overview (Page 2772) DataLogClose: Close data log Description You use the "DataLogClose" instruction to close an open data log. You select the data log using the ID parameter. Note Closing data logs automatically The data log is closed automatically when the CPU goes to STOP or if there is a restart. Parameters The following table shows the parameters of the "DataLogClose" instruction: Parameters Declaration Data type Memory area Description REQ Input BOOL I, Q, M, L, D, T, C or constant Execute function on a rising edge. (T and C are only available in LAD and FBD with S7-1500) ID InOut DWORD I, Q, M, L, D Object ID of the data log DONE Output BOOL I, Q, M, L, D Instruction was executed successfully. BUSY Output BOOL I, Q, M, L, D Execution of the instruction not yet complete. WinCC Basic V13.0 System Manual, 02/2014 2789 Programming the PLC 9.7 References Parameters Declaration Data type Memory area Description ERROR Output BOOL I, Q, M, L, D 0: No error. 1: An error occurred during execution of the instruction. Detailed information is output via the STATUS parameter. STATUS Output WORD I, Q, M, L, D Status parameter The parameter is only set for the duration of one call. To display the status, you should therefore copy the STATUS parameter to a free data area. You can find additional information on valid data types under "Overview of the valid data types (Page 1204)". STATUS (S7-1200) parameter Error code* Description (W#16#...) 0 No errors 1 Data log is not open 7000 No job processing active. 7001 Start of job processing. Parameter BUSY = 1, DONE = 0 7002 Intermediate call (REQ irrelevant): Instruction already active; BUSY has the value "1". 8092 Data log does not exist. * The error codes can be displayed as integer or hexadecimal values in the program editor. For additional information on toggling display formats, refer to "See also". STATUS (S7-1500) parameter Error code* Description (W#16#...) 0 No errors 1 Data log is not open 7000 No job processing active. 7001 Start of job processing. Parameter BUSY = 1, DONE = 0 8070 Complete internal instance memory is assigned. 8092 Data log does not exist. 80B4 The memory card is write-protected. 80C0 Access currently not possible. * The error codes can be displayed as integer or hexadecimal values in the program editor. For additional information on toggling display formats, refer to "See also". 2790 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References DataLogDelete: Delete data log Description You use the "DataLogDelete" instruction to delete a data log file from the memory card. The data log and the data records it contains can only be deleted if it was created with the "DataLogCreate" or "DataLogNewFile" instruction. Parameters The following table shows the parameters of the "DataLogDelete" instruction: Parameter Declaration Data type Memory area Description REQ Input BOOL I, Q, M, L, D, T, C or constant Execution of the instruction upon a rising edge. (T and C are only available in LAD and FBD with S7-1500) NAME Input VARIANT L, D File name of the data log DELFILE Input BOOL I, Q, M, D, L 0: Data log is retained. 1: Data log is deleted. Detailed information is output at the STATUS parameter. ID InOut DWORD I, Q, M, D, L Object ID of the data log DONE Output BOOL I, Q, M, D, L Instruction was executed successfully. BUSY Output BOOL I, Q, M, D, L Deletion of the data log is not yet complete. ERROR Output BOOL I, Q, M, D, L 0: No error. 1: An error occurred during execution of the instruction. Detailed information is output at the STATUS parameter. STATUS Output WORD I, Q, M, D, L Status parameter The parameter is only set for the duration of one call. To display the status, you should therefore copy the STATUS parameter to a free data area. You can find additional information on valid data types under "Overview of the valid data types (Page 1204)". NAME and ID parameters Select the data log to be deleted using the NAME and ID parameters. The ID parameter is evaluated first. If there is a data log with the relevant ID, the NAME parameter will not be evaluated. If the value "0" is used at the ID parameter, a value with the data type STRING must be used at the NAME parameter. WinCC Basic V13.0 System Manual, 02/2014 2791 Programming the PLC 9.7 References RET_VAL parameter Error code* (W#16#...) Explanation 0 No error. 7000 No job processing active. 7001 Start of job processing. Parameter BUSY = 1, DONE = 0 7002 Intermediate call (REQ irrelevant): Instruction already active; BUSY has the value "1". 8091 A data type other than STRING is being used at the NAME parameter. 8092 Data log does not exist. 80A2 Write error 80B4 The memory card is write-protected. * The error codes can be displayed as integer or hexadecimal values in the program editor. For additional information on toggling display formats, refer to "See also". See also DataLogCreate: Create data log (Page 2775) DataLogNewFile: Data log in new file DataLogNewFile: Data log in new file Description You use the "DataLogNewFile" instruction to create a new data log with the same properties as an existing data log. This allows the contents of an existing data log to be retained. When called, the instruction creates a new data log on the memory card or in the internal load memory with the name defined at the NAME parameter. You use the ID parameter to specify the ID of the old data log whose properties you want to apply to the new data log. The ID of the new data log is then output via the ID parameter. You specify the file size of the new data log with the RECORDS parameter of the instruction. Once the new data log is created, it is opened automatically. This means that data can be written. 2792 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameters The following table shows the parameters of the "DataLogNewFile" instruction: Parameters Declaration Data type Memory area Description REQ Input BOOL I, Q, M, L, D or constant Execution of the instruction upon a rising edge. RECORDS Input UDInt I, Q, M, L, D or constant Number of data records in the data log. NAME Input VARIANT L, D File name of the new data log. ID InOut DWORD I, Q, M, L, D Object ID of the data log In: ID of the existing data log Out: ID of the new data log DONE Output BOOL I, Q, M, L, D Instruction was executed successfully. BUSY Output BOOL I, Q, M, L, D Execution of the instruction not yet complete. ERROR Output BOOL I, Q, M, L, D 0: No error. 1: An error occurred during execution of the instruction. Detailed information is output via the STATUS parameter. STATUS Output WORD I, Q, M, L, D Status parameter The parameter is only set for the duration of one call. To display the status, you should therefore copy the STATUS parameter to a free data area. For additional information on valid data types, refer to "Overview of the valid data types (Page 1204)". Parameter STATUS Error code* Description (W#16#...) 0 No errors. 7000 No job processing active. 7001 Start of job processing. Parameter BUSY = 1, DONE = 0 7002 Intermediate call (REQ irrelevant): Instruction already active; BUSY has the value "1". 8070 Complete internal instance memory is assigned. 8090 Invalid file name. 8091 Path does not exist. 8092 Source data log does not exist. 8093 New data log already exists. 8097 File length exceeds the file system limit. 80B3 Load memory not sufficient. 80B4 The memory card is write-protected. WinCC Basic V13.0 System Manual, 02/2014 2793 Programming the PLC 9.7 References Error code* Description (W#16#...) 80C1 Too many files open. * The error codes can be displayed as integer or hexadecimal values in the program editor. For additional information on toggling display formats, refer to "See also". DataLogNewFile: Data log in new file Description You use the "DataLogNewFile" instruction to create a new data log with the same properties as an existing data log. This allows the contents of an existing data log to be retained. When called, the instruction creates a new data log on the memory card or in the internal load memory with the name defined at the NAME parameter. You use the ID parameter to specify the ID of the old data log whose properties you want to apply to the new data log. The ID of the new data log is then output via the ID parameter. You specify the file size of the new data log with the RECORDS parameter of the instruction. The parameter DATA enables a consistency check between the new data log to be created and the definition of the data log of the instruction "DataLogCreate (Page 2775)". The consistency check can only be executed if the data log was created with the instruction "DataLogCreate (Page 2775)": If you are using the same pointer at the DATA parameter as at the DATA parameter of the "DataLogCreate (Page 2775)" instruction, a check is performed to determine whether the data types match. If the data types do not match, the error code W#16#80A0 is output at the STATUS parameter. If the data log to be opened was not created with "DataLogCreate (Page 2775)", a consistency check is not possible. In this case, enter the value "NULL" in the DATA parameter. Once the new data log is created, it is opened automatically. This means that data can be written. Parameters The following table shows the parameters of the "DataLogNewFile" instruction: Parameter Declaration Data type Memory area Description REQ Input BOOL I, Q, M, L, D, T, C or constant Execution of the instruction upon a rising edge. (T and C are only available in LAD and FBD with S7-1500) RECORDS Input UDInt I, Q, M, L, D or constant Number of data records in the data log. NAME Input VARIANT L, D File name of the new data log. 2794 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameter Declaration Data type Memory area Description ID InOut DWORD I, Q, M, L, D Object ID of the data log In: ID of the existing data log Out: ID of the new data log DATA InOut VARIANT L, D Data type for consistency check DONE Output BOOL I, Q, M, L, D Instruction was executed successfully. BUSY Output BOOL I, Q, M, L, D Execution of the instruction not yet complete. ERROR Output BOOL I, Q, M, L, D 0: No error. 1: An error occurred during execution of the instruction. Detailed information is output via the STATUS parameter. STATUS Output WORD I, Q, M, L, D Status parameter The parameter is only set for the duration of one call. To display the status, you should therefore copy the STATUS parameter to a free data area. You can find additional information on valid data types under "Overview of the valid data types (Page 1204)". STATUS parameter Error code* Description (W#16#...) 0 No errors. 7000 No job processing active. 7001 Start of job processing. Parameter BUSY = 1, DONE = 0 7002 Intermediate call (REQ irrelevant): Instruction already active; BUSY has the value "1". 8070 Complete internal instance memory is assigned. 8090 Invalid file name. Data types inconsistent. The data log at the ID parameter uses different data types than specified in the DATA parameter. 8091 Path does not exist. 8092 Source data log does not exist. 8093 New data log already exists. 8097 File length exceeds the file system limit. 80B3 Load memory not sufficient. 80B4 The memory card is write-protected. 80C0 Access currently not possible. 80C1 Too many files open. * The error codes can be displayed as integer or hexadecimal values in the program editor. For additional information on toggling display formats, refer to "See also". WinCC Basic V13.0 System Manual, 02/2014 2795 Programming the PLC 9.7 References 9.7.3.12 Data block functions CREATE_DB: Create data block Description The instruction "CREATE_DB" is used to create a new data block in the load and/or work memory. The instruction "CREATE_DB" does not change the checksum of the user program. Number of the data block The data block created is assigned a number from the range defined at the LOW_LIMIT (low limit) and UP_LIMIT (high limit) parameters. "CREATE_DB" assigns the smallest possible number from the specified range to the DB. You cannot assign the numbers of the DBs already contained in the user program. To create a DB with a specific number, enter the same number for the high and low limit of the range to be specified. If a DB with the same number already exists in the work memory and/ or load memory, or if the DB exists as a copied version, the instruction will be terminated and an error message will be generated at the RET_VAL parameter. Start values of the data block Using the SRCBLK parameter, you can define start values for the DB to be created. The SRCBLK parameter is a pointer to a DB or a DB area from which you apply the start values. The DB addressed at the SRCBLK parameter must have been generated with standard access ("Optimized block access" attribute disabled). If the area specified at the SRCBLK parameter is larger than the DB generated, the values up to the length of the DB generated will be applied as start values. If the area specified at the SRCBLK parameter is smaller than the DB generated, the remaining values will be filled with "0". To ensure data consistency, you must not change this data area while "CREATE_DB" is being executed (which means as long as the BUSY parameter has the value TRUE). Parameters The following table shows the parameters of the "CREATE_DB" instruction: Parameter Declarati on Data type Memory area Description REQ Input BOOL I, Q, M, D, L or constant REQ= 1: Request to create the DB LOW_LIMIT Input UINT I, Q, M, D, L or constant Low limit of the area ### used by "CREATE_DB" to assign a number to your DB 60000) UP_LIMIT UINT I, Q, M, D, L or constant High limit of the area ### used by "CREATE_DB" to assign a number to your DB (largest possible DB number: 60999) 2796 Input WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameter Declarati on Data type Memory area Description COUNT Input UDINT I, Q, M, D, L or constant The count value specifies the number of bytes which you want to reserve for the DB generated. The number of bytes must be an even number. The maximum length is 65534 bytes. ATTRIB Input BYTE I, Q, M, D, L or constant The first 4 bits of the byte at the ATTRIB parameter define the properties of the data block: Bit 0 = 0: DB only in the work memory Bit 0 = 1: DB only in the load memory Bit 1 = 0: DB is not write-protected. Bit 1 = 1: DB is write-protected Bit 2 = 0: DB is retentive (only for DBs generated in the load memory) Bit 2 = 1: DB is not retentive Bit 3= 0: DB generated either in load or in work memory Bit 3= 1: DB generated both in load and in work memory To ensure compatibility with STEP7 V5.x, bits 1 and 3 must be used in combination: Bit 0 Bit 3 DB generation 0 0 In work memory only 1 0 In load memory only 0 1 Work and load memory 1 1 Work and load memory Bit 4 = 0 - No start values specified (input values at the SRCBLK parameter will be ignored). Bit 4 = 1 - Specify start values (values correspond to the DB addressed by the SRCBLK parameter). SRCBLK Input VARIAN T D Pointer to the data block whose values will be used to initialize the data block to be generated. RET_VAL Return INT I, Q, M, D, L Error information BUSY Output BOOL I, Q, M, D, L BUSY= 1: The process is not yet complete. DB_NUM Output DB_DY I, Q, M, D, L N (UINT) Number of the DB created. For additional information on valid data types, refer to "Overview of the valid data types (Page 1204)". Parameter RET_VAL Error code* (W#16#...) Description 0000 No error 0081 The target range is greater than the source range. The complete source range is written to the target range. The remaining bytes of the target range are filled with 0. 7000 First call with REQ = 0: No data transfer active; BUSY has the value "0". 7001 First call with REQ = 1: Data transfer triggered; BUSY has the value "1". WinCC Basic V13.0 System Manual, 02/2014 2797 Programming the PLC 9.7 References Error code* (W#16#...) Description 7002 Intermediate call (REQ irrelevant): Data transfer already active; BUSY has the value "1". 8081 The source range is larger than the target range. The complete target range is written. The remaining bytes of the source range are ignored. 8092 The "Create data block" function is currently unavailable because The "Compress user memory" function is currently active. The maximum number of blocks on your CPU has already been reached. 8093 No data block or a data block that is not in the work memory is specified for the SRCBLK parameter. 8094 A not yet supported attribute was specified for the ATTRIBparameter. 80A1 DB number error: The number is "0" Low limit > high limit 80A2 DB length error: The length is "0" The length is an odd number The length is greater than permitted by the CPU 80A3 The data block at the SRCBLK parameter was not created with standard access. 80B1 There is no DB number free. 80B2 Not enough work memory. 80B4 The memory card is write-protected. 80BB Not enough load memory. 80C0 The destination is currently being processed by another instruction or a communication function. 80C1 A DB with this DB number is currently being deleted. 80C3 The maximum number of simultaneously active "CREATE_DB" instructions has already been reached. * The error codes can be displayed as integer or hexadecimal values in the program editor. For additional information on toggling display formats, refer to "See also". READ_DBL: Read from data block in the load memory Description With the instruction you copy a DB or an area of a DB in load memory (Micro Memory Card) to the data area of a destination DB. The destination DB must be relevant for execution; that is, it must not be created with the attribute UNLINKED. The content of the load memory is not changed during the copy process. To ensure data consistency, you must not change the target range while "READ_DBL" is being executed (i.e., as long as the BUSY parameter has the value TRUE). The following restrictions apply to the SRCBLK and DSTBLK parameters (source and destination blocks): 2798 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References You must be able to divide the length of the VARIANT pointer by eight. For a VARIANT pointer of type STRING, the length must be equal to 1. The source and destination block must have been created with the same block access, i.e. both must use either the access type "Optimized" or "Standard". Note ""READ_DBL" is processed asynchronously. Therefore, it is not suitable for frequent (or cyclical) reading of tags in the load memory. Once started, a job is always completed. If the maximum number of simultaneously active "READ_DBL" instructions is reached and you call "READ_DBL" once again at this time in a priority class having higher priority, error code W#16#80C3 will be returned. Consequently it does not make sense to restart the high-priority job right away. Functional description The "READ_DBL" instruction works asynchronously, that is, its execution extends over multiple calls. You start the job by calling "READ_DBL" with REQ = 1. The output parameters RET_VAL and BUSY indicate the status of the job. See also: Meaning of the parameters REQ, RET_VAL and BUSY with asynchronous instructions (Page 1736) Parameters The following table shows the parameters of the "READ_DBL" instruction: Parameter Declaration Data type Memory area Description REQ Input BOOL I, Q, M, D, L or constant REQ = 1: Read request SRCBLK Input VARIANT D Pointer to data block in the load memory that is to be read from RET_VAL Return INT I, Q, M, D, L Error information BUSY Output BOOL I, Q, M, D, L BUSY = 1: The reading process is not yet complete. DSTBLK Output VARIANT D Pointer to the data block in the work memory that is to be written to For additional information on valid data types, refer to "Overview of the valid data types (Page 1204)". WinCC Basic V13.0 System Manual, 02/2014 2799 Programming the PLC 9.7 References Parameter RET_VAL Error code* Description (W#16#...) 0000 No error 0081 The target range is greater than the source range. The source range is written completely to the target range; the remaining bytes of the target range will not be changed. 7000 First call with REQ = 0: No data transfer active; BUSY has the value "0". 7001 First call with REQ=1: Data transfer triggered; BUSY has the value "1". 7002 Intermediate call (REQ irrelevant): Data transfer already active; BUSY has the value "1". 8081 The source range is larger than the target range. The complete target range is written. The remaining bytes of the source range are ignored. 8082 Destination DB type different from source DB type (optimized/standard access). 8093 No data block or a data block that is not in the work memory is specified for the DSTBLK parameter. 80B1 No data block is specified for the SRCBLK parameter, or the data block specified there is not a load memory object. 80B4 DB with F-attribute must not be read. 80C3 The maximum number of simultaneously active "READ_DBL" instructions has already been reached. 80C0 The destination DB is currently being processed by another instruction or a communication function. * The error codes can be displayed as integer or hexadecimal values in the program editor. For additional information on toggling display formats, refer to "See also". See also GET_ERR_ID: Get error ID locally (Page 2462) WRIT_DBL: Write to data block in the load memory Description The instruction "WRIT_DBL" is used to transfer the contents of a DB or a DB area from the work memory to a DB or a DB area in the load memory (Micro Memory Card). The source DB must be relevant for execution, which means it must not be created with the attribute UNLINKED. To ensure data consistency, it is not permitted to change the source range while "WRIT_DBL" is being executed (i.e., as long as the BUSY parameter has the value TRUE). The following restrictions apply to the SRCBLK and DSTBLK parameters (source and destination blocks): For a VARIANT pointer of type BOOL, the length must be divisible by 8. For a VARIANT pointer of type STRING, the length must be equal to 1. 2800 The source and destination block must have been created with the same block access, i.e. both must use either the access type "Optimized" or "Standard - compatible with S7-300/400". WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References The "WRIT_DBL" instruction does not change the checksum of the user program if you write a DB that was created using an instruction. However, when a loaded DB is written, the first entry in this DB changes the checksum of the user program. Note "WRIT_DBL" is not suitable for frequent (or cyclical) writing of tags in the load memory. This is because the Micro Memory Card technology limits the number of write accesses that can be made to a Micro Memory Card. Functional description The "WRIT_DBL" instruction works asynchronously, that is, its execution extends over multiple calls. You start the job by calling "WRIT_DBL" with REQ=1. The output parameters RET_VAL and BUSY indicate the status of the job. See also: Meaning of the parameters REQ, RET_VAL and BUSY with asynchronous instructions (Page 1736). Parameters The following table shows the parameters of the instruction "WRIT_DBL": Parameter Declaration Data type Memory area Description REQ Input BOOL I, Q, M, D, L or constant REQ = 1: Write request SRCBLK Input VARIANT D Pointer to the DB in the work memory that is to be read from RET_VAL Return INT I, Q, M, D, L Error information BUSY Output BOOL I, Q, M, D, L BUSY = 1: The writing process is not yet completed. DSTBLK Output VARIANT D Pointer to the data block in the load memory that is to be written to You will find more detailed information on valid data types in "Overview of the valid data types (Page 1204)". Parameter RET_VAL Error code* Description (W#16#...) 0000 No error 0081 The target range is greater than the source range. The source range is written completely to the target range; the remaining bytes of the target range will not be changed. 7000 First call with REQ = 0: No data transfer active; BUSY has the value "0". 7001 First call with REQ = 1: Data transfer triggered; BUSY has the value "1". WinCC Basic V13.0 System Manual, 02/2014 2801 Programming the PLC 9.7 References Error code* Description (W#16#...) 7002 Intermediate call (REQ irrelevant): Data transfer already active; BUSY has the value "1". 8081 The source range is larger than the target range. The complete target range is written. The remaining bytes of the source range are ignored. 8082 Destination DB type different from source DB type (optimized/non-optimized access). 8092 Incorrect operating mode: While "WRIT_DBL" was active, the CPU went into STOP mode. This error code is supplied at the next transition to RUN. Call "WRIT_DBL" again. 8093 No data block or a data block that is not in the work memory is specified for the SRCBLK parameter. 80B1 No data block has been specified for the DSTBLK parameter, or the data block specified there is not a load memory object. 80B4 DB with F-attribute must not be read. The memory card is write-protected. 80BB Insufficient load memory available. 80C3 The maximum number of simultaneously active "WRIT_DBL" instructions has already been reached. 80C0 The destination DB is currently being processed by another instruction or a communication function. General error codes See also: GET_ERR_ID: Get error ID locally (Page 1964) * The error codes can be displayed as integer or hexadecimal values in the program editor. For additional information on toggling display formats, refer to "See also". ATTR_DB: Read data block attribute Description You use the instruction "ATTR_DB" to obtain information about a data block (DB) located in the work memory of the CPU. The instruction determines the attributes set at the ATTRIB parameter for the DB selected. The length cannot be read out for data blocks with optimized access, the DB_LENGH parameter contains the length "0" for DBs with optimized access. Data blocks for Motion Control cannot be read out with the "ATTR_DB" instruction. The error code 80B2 is output for this. Parameters The following table shows the parameters of the "ATTR_DB" instruction: Parameter Declaration Data type Memory area Description REQ Input BOOL I, Q, M, D, L or constant REQ = 1: Read request for block attributes DB_NUMBE R Input DB_ANY (UINT) I, Q, M, D, L or constant Number of the DB to be tested RET_VAL Output INT I, Q, M, D, L Error information UDINT I, Q, M, D, L Number of data bytes which the selected DB contains. DB_LENGTH Output 2802 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameter Declaration Data type Memory area Description ATTRIB Output BYTE I, Q, M, D, L DB properties: Bit 0*= 0: LINKED - The DB only exists in the work memory Bit 0*= 1: UNLINKED - The DB only exists in the load memory Bit 1 = 0: READ_ONLY - The DB is not writeprotected. Bit 1 = 1: READ_ONLY - The DB is write-protected. Bit 2 = 0: RETAIN - The DB is retentive. Bit 2 = 1: NON_RETAIN - The DB is not retentive. Bit 3*= 0: The DB exists either in the load or the work memory Bit 3*= 1: The DB is generated in both the load and the work memory * The relationship between bit 0 and bit 3 is explained in the parameters of the instruction "CREATE_DB: Create data block (Page 2796)". You will find more detailed information on valid data types in "Overview of the valid data types (Page 1204)". Parameter RET_VAL Error code* (W#16#...) Explanation 0000 No error occurred. 80A1 Error in input parameter DB_NUMBER: the actual parameter selected Is "0" Is greater than the maximum permitted DB number for the CPU used. 80B1 The DB with the specified number does not exist on the CPU. 80B2 Data blocks of Motion Control technology objects cannot be read out with the "ATTR_DB" instruction. * The error codes can be displayed as integer or hexadecimal values in the program editor. For additional information on toggling display formats, refer to "See also". DELETE_DB: Delete data block Description You use the instruction "DELETE_DB" to delete a data block (DB) that was created from the user program by calling the instruction "CREATE_DB (Page 2796)". If the data block was not created with "CREATE_DB", the error code W#16#80B5 is output at the RET_VAL parameter. The DB to be deleted may not be located in the current or in a lower priority class. Otherwise, the CPU starts OB 121 when the "DELETE_DB" instruction is called. If OB 121 is not present, the CPU switches to STOP mode. The instruction "DELETE_DB" can be interrupted by higher WinCC Basic V13.0 System Manual, 02/2014 2803 Programming the PLC 9.7 References priority classes. If the instruction is called again there, then this second call will be aborted and W#16#8091 will be entered in RET_VAL . Parameters The following table shows the parameters of the "DELETE_DB" instruction: Parameter Declaration Data type Memory area Description REQ Input BOOL I, Q, M, D, L or constant REQ =1: Request to delete the DB with the number in parameter DB_NUMBER DB_NUMBER Input UINT I, Q, M, D, L or constant Number of the DB to be deleted RET_VAL Output INT I, Q, M, D, L Error information (see "RET_VAL parameter") BUSY Output BOOL I, Q, M, D, L BUSY= 1: The process is not yet complete. You will find more detailed information on valid data types in "Overview of the valid data types (Page 1204)". Parameter RET_VAL Error code* (W#16#...) Explanation 0000 No error occurred. 8091 "DELETE_DB" calls were nested and the maximum nesting level of the CPU used was exceeded. 8092 The instruction can currently not be executed because: The "Compress user memory" function is currently active. You are copying the DB to be deleted from the CPU to an offline project. 80A1 Error in input parameter DB_NUMBER: The value at the parameter is "0". The value at the parameter is greater than the maximum permitted DB number for the CPU used. 80B1 The DB with the specified number does not exist on the CPU. 80B4 The DB cannot be deleted because the memory card of the CPU is write-protected. 80B5 The DB was not created using "CREATE_DB". 80BB Not enough load memory. 80C1 The "Delete a DB" function cannot be executed at this time due to a temporary resource bottleneck. General error information See also: GET_ERR_ID: Get error ID locally (Page 1964) * The error codes can be displayed as integer or hexadecimal values in the program editor. For additional information on toggling display formats, refer to "See also". 2804 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References 9.7.3.13 Addressing Instructions for address conversion Description There are different options for addressing a module (IO address, hardware identifier, slot). You can convert the address data with the following instructions: GEO2LOG: Determine hardware identifier from slot (Page 2806) LOG2GEO: Determine slot from hardware identifier (Page 2808) LOG2MOD: Determine the hardware identifier from addressing of STEP 7 V5.5 SPx (Page 2809) IO2MOD: Determine hardware identifier from an IO address (Page 2810) RD_ADDR: Determine IO addresses from the hardware identifier (Page 2811) The following instructions are supported in addition for migrated projects: GEO_LOG: Determine hardware identifier from slot (Page 2813) LOG_GEO: Determine slot from hardware identifier (Page 2814) RD_LGADR: Determine IO addresses from the hardware identifier (Page 2816) GADR_LGC: Determine hardware identifier from slot and offset in the user data address area (Page 2817) LGC_GADR: Determine slot from hardware identifier (Page 2818) WinCC Basic V13.0 System Manual, 02/2014 2805 Programming the PLC 9.7 References Type of address conversion The figure below shows which instruction runs which address conversion. 1DPH 7\SH *(2/2* 6)& /2**(2 6)& /2*02' 6)& ,202' 6)& 5'B$''5 6)& *(2B/2* )& /2*B*(2 )& 5'B/*$'5 )& *$'5B/*& )& /*&B*$'5 )& ,2DGGUHVV HV +DUGZDUHLGHQWLILHU 6ORW GEO2LOG: Determine hardware identifier from slot Description You use the "GEO2LOG" instruction to determine hardware identifier based on slot information that you define using the system data type GEOADDR. Depending on the type of hardware you define at the parameter HWTYPE the following information is evaluated from the other parameters GEOADDR: With HWTYPE = 1 (PROFINET IO system): - Only IOSYSTEM is evaluated. The other parameters of GEOADDR are not taken into consideration. - The hardware identifier of the PROFINET IO system is output. With HWTYPE = 2 (PROFINET IO device): - IOSYSTEM and STATION are evaluated. The other parameters of GEOADDR are not taken into consideration. - The hardware identifier of the PROFINET IO device is output. With HWTYPE = 3 (rack): - Only IOSYSTEM and STATION are evaluated. The other parameters of GEOADDR are not taken into consideration. - The hardware identifier of the rack is output. 2806 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References With HWTYPE = 4 (module): - IOSYSTEM, STATION and SLOT are evaluated. The SUBSLOT parameter of GEOADDR is not taken into consideration. - The hardware identifier of the module is output. With HWTYPE = 5 (submodule): - All parameters of GEOADDR are evaluated. - The hardware identifier of the submodule is output. The AREA parameter of the GEOADDR system data type is not evaluated. Parameter The following table shows the parameters of the "GEO2LOG" instruction: Parameter Declaration Data type Memory area Description GEOADDR Input VARIANT D, L Pointer to the structure of the GEOADDR system data type. The system data type contains the slot information from which the hardware ID is determined. See also: System data type GEOADDR (Page 2812) RET_VAL Return INT I, Q, M, D, L Output of error information. LADDR Output HW_ANY I, Q, M, D, L Hardware identifier of the assembly or the module. The number is automatically assigned and is stored in the properties in the hardware configuration. For additional information on valid data types, refer to "Overview of the valid data types (Page 1204)". Parameter RET_VAL Error code* (W#16#...) Explanation 0 No error occurred. 8091 Invalid value for in GEOADDR for HWTYPE. 8094 Invalid value for in GEOADDR for IOSYSTEM. 8095 Invalid value for in GEOADDR for STATION. 8096 Invalid value for in GEOADDR for SLOT. 8097 Invalid value for in GEOADDR for SUBSLOT. * The error codes can be displayed as integer or hexadecimal values in the program editor. For additional information on toggling display formats, refer to "See also". WinCC Basic V13.0 System Manual, 02/2014 2807 Programming the PLC 9.7 References See also Instructions for address conversion (Page 2805) LOG2GEO: Determine slot from hardware identifier Description You use the "LOG2GEO" instruction to determine the module slot belonging to a hardware identifier. Parameters The following table shows the parameters of the "LOG2GEO" instruction: Parameter Declaration Data type Memory area Description LADDR Input HW_ANY I, Q, M, D, L or constant Hardware identifier of the module whose slot you want to find. The hardware ID is assigned automatically and is stored in the properties of the module in the hardware configuration and the system constants. RET_VAL Output INT I, Q, M, D, L Output of error information. GEOADDR InOut VARIANT D Pointer to the GEOADDR system data type. The slot information is written in the system data type GEOADDR. See also: System data type GEOADDR (Page 2812) You will find more detailed information on valid data types in "Overview of the valid data types (Page 1204)". Parameter RET_VAL Error code* (W#16#...) Explanation 0 No error occurred. 8090 The address specified at the LADDR parameter is invalid. * The error codes can be displayed as integer or hexadecimal values in the program editor. For additional information on toggling display formats, refer to "See also". 2808 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References LOG2MOD: Determine the hardware identifier from addressing of STEP 7 V5.5 SPx Description You use the "LOG2MOD" instruction to determine the hardware identifier for an IO (sub)module from the addressing of STEP 7 5.5 SPx (IO data address or diagnostic address). The hardware identifier is used at the LADDR input parameter for addressing of various instructions. You can convert the addressing parameters from STEP 7 5.5 SPx by calling "LOG2MOD" beforehand. Parameter The following table shows the parameters of the "LOG2MOD" instruction: Parameter Declaration Data type Memory area Description IOID Input BYTE I, Q, M, D, L or constant Identifier of the address area as in STEP 7 5.5 SPx: B#16#00: Bit15 of ADDR specifies whether an input (Bit15=0) or output address (Bit15=1) exists. B#16#54= Peripheral input (PI) B#16#55= Peripheral output (PQ) ADDR Input WORD I, Q, M, D, L or constant Logical address of the IO data of the module as offset (corresponding addressing in STEP 7 5.5 SPx) or diagnostic address. RET_VAL Return INT I, Q, M, D, L Error code of the instruction. HWID Output HW_IO I, Q, M, D, L Determined hardware identifier (logical address) of the IO (sub)module. You will find more detailed information on valid data types in "Overview of the valid data types (Page 1204)". RET_VAL parameter Error code* (W#16#...) Explanation 0 No error occurred. 8093 Specified address is not used by any hardware components. Specified value at IOID parameter is invalid. * The error codes can be displayed as integer or hexadecimal values in the program editor. For additional information on toggling display formats, refer to "See also". WinCC Basic V13.0 System Manual, 02/2014 2809 Programming the PLC 9.7 References IO2MOD: Determine hardware identifier from an IO address Description The "IO2MOD" instruction determines the hardware identifier of the module from an IO address (I, Q, PI, PQ) of a (sub)module. Enter the IO address at the ADDR parameter. If a series of IO addresses is used at this parameter, only the first address is evaluated to determine the hardware identifier. If the first address is correctly specified, the length for the address specification at the ADDR is of no significance. If an address area is used that encompasses several modules or non-used addresses, the hardware identifier of the first module can also be determined. If no IO address of a sub(module) is specified at the ADDR parameter, the error code 8090 is output at the RET_VAL parameter. Note Input of IO address in SCL You cannot program using the IO access ID "%QWx:P" in SCL. In this case, use the symbolic tag name or the absolute address in the process image. Parameters The following table shows the parameters of the "IO2MOD" instruction: Parameter Declaration Data type Memory area Description ADDR Input VARIANT I, Q, M, D, L IO address (I, Q, PI, PQ) within a (sub)module. Make sure that slice access is not used for the parameter ADDR. If this is the case, incorrect values are output at the LADDR parameter. RET_VAL Return INT I, Q, M, D, L Error code of the instruction. LADDR Output HW_IO I, Q, M, D, L Determined hardware identifier (logical address) of the IO (sub)module. For additional information on valid data types, refer to "Overview of the valid data types (Page 1204)". RET_VAL parameter Error code* (W#16#...) Explanation 0 No error occurred. 8090 IO address specified at ADDR parameter is not used by any hardware component. * The error codes can be displayed as integer or hexadecimal values in the program editor. For additional information on toggling display formats, refer to "See also". 2810 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References RD_ADDR: Determine IO addresses from the hardware identifier Description The "RD_ADDR" instruction determines the length and the start address of the inputs or outputs based on the hardware identifier of a sub(module). Use the LADDR parameter to select the input or output module based on the hardware identifier. The following output parameters are used depending on whether it is an input module or output module: - In the case of an input module the determined values are output at the PIADDR and PICOUNT parameters. - In the case of an output module the determined values are output at the PQADDR and PQCOUNT parameters. The PIADDR and PQADDR parameters each contain the start address of the I/O addresses of the module. The PICOUNT and PQCOUNT parameters each contain the number of bytes of the inputs our outputs (1 byte for 8 inputs/outputs, 2 bytes for 16 inputs/outputs). Note Addressing packed modules If packed modules (not the first module of the packed module group) are addressed, the displayed data deviates from the hardware configuration. "0" is returned for PIADDR or PQADDR and PICOUNT or PQCOUNT. RET_VAL does not indicate an error (16#0000). Parameters The following table shows the parameters of the "RD_ADDR" instruction: Parameter Declaration Data type Memory area Description LADDR Input HW_IO I, Q, M, D, L or constant Hardware identifier of the (sub)module. RET_VAL Return INT I, Q, M, D, L Error code of the instruction. PIADDR Output UDINT I, Q, M, D, L Start address of the input module. PICOUNT Output UINT I, Q, M, D, L Number of bytes of the inputs. PQADDR Output UDINT I, Q, M, D, L Start address of the output module. PQCOUNT Output UINT I, Q, M, D, L Number of bytes of the outputs. You will find more detailed information on valid data types in "Overview of the valid data types (Page 1204)". WinCC Basic V13.0 System Manual, 02/2014 2811 Programming the PLC 9.7 References Parameter RET_VAL Error code* (W#16#...) Explanation 0 No error occurred. 8090 Hardware identifier of the module at the LADDR parameter is invalid. * The error codes can be displayed as integer or hexadecimal values in the program editor. For additional information on toggling display formats, refer to "See also". System data type GEOADDR Geographical address The system data type GEOADDR contains the geographical address of a module, i.e. the slot information. Geographical address for PROFINET IO For PROFINET IO the geographical address was composed of the ID of the PROFINET IO system, the device number, the slot number and the submodule (if a sub-module is used). Geographical address for PROFIBUS DP For PROFIBUS DP, the geographical address consists of the ID of the DP master system, the station number and the slot number. The slot information of the modules can be found in the hardware configuration of each module. System data type GEOADDR The structure GEOADDR is automatically created if you enter "GEOADDR" as the data type in a data block. The system data type GEOADDR has the following structure: Parameter name Data type GEOADDR STRUCT HWTYPE UINT Description Hardware type: 1: IO system (PROFINET/PROFIBUS) 2: IO device/DP slave 3: Rack 4: Module 5: Submodule If a hardware type is not supported by the instruction, a HWTYPE "0" is output. AREA UINT Area ID: 0 = CPU 1 = PROFINET IO 2 = PROFIBUS DP 3 = AS-i IOSYSTEM 2812 UINT PROFINET IO system (0=central unit in the rack) WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameter name STATION Data type Description UINT Number of the rack if area identifier AREA = 0 (central module). Station number if area identifier AREA > 0. SLOT UINT Slot number SUBSLOT UINT Number of the submodule. This parameter has the value "0" if no submodule is available or can be plugged. Other GEO_LOG: Determine hardware identifier from slot Description The corresponding module slot of a signal module is known. Use the "GEO_LOG" instruction to determine the corresponding hardware identifier of the module from this. Parameters The following table shows the parameters of the instruction "GEO_LOG": Parameter Declaration Data type Memory area Description MASTER Input INT I, Q, M, D, L or constant Area ID: 0, if the slot is located in a centralized configuration. 1 to 32: DP master system ID of the associated field device if the slot is located in a field device on PROFIBUS 100 to 115: PROFINET IO system ID of the associated field device if the slot is located in a field device on PROFINET STATION Input INT I, Q, M, D, L or constant If MASTER = 0: Number of the rack If MASTER > 0: Station number of the field device SLOT Input INT I, Q, M, D, L or constant Slot number SUBSLOT Input INT I, Q, M, D, L or constant The parameter SUBSLOT is not evaluated by the instruction. RET_VAL Return INT I, Q, M, D, L Error information LADDR Output HW_IO I, Q, M, D, L Hardware identifier of the module You will find more detailed information on valid data types in "Overview of the valid data types (Page 1204)". WinCC Basic V13.0 System Manual, 02/2014 2813 Programming the PLC 9.7 References Parameter RET_VAL Error code* Explanation (W#16#...) 0000 No error occurred. 8094 No subnet was configured with the specified SUBNETID . 8095 Illegal value for STATION parameter 8096 Illegal value for SLOT parameter General error information See also: GET_ERR_ID: Get error ID locally (Page 1964) * The error codes can be displayed as integer or hexadecimal values in the program editor. For additional information on toggling display formats, refer to "See also". See also Instructions for address conversion (Page 2805) LOG_GEO: Determine slot from hardware identifier Description You use the "LOG_GEO" instruction to determine the module slot belonging to a hardware identifier. Parameters The following table shows the parameters of the instruction "LOG_GEO": Parameter Declaration Data type Memory area Description LADDR Input HW_IO I, Q, M, D, L or constant Hardware identifier of the module for which the slot is to be determined. RET_VAL Return INT I, Q, M, D, L Error information AREA Output INT I, Q, M, D, L Area ID: indicates how the remaining output parameters are to be interpreted: 0: central device 2: PROFIBUS DP / PROFINET IO 2814 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameter Declaration Data type Memory area Description MASTER Output INT I, Q, M, D, L With AREA = 0: 0: If the slot is located in one of the racks (central device). With AREA = 2: 1 to 32: DP master system ID of the associated field device if the slot is located in a field device on PROFIBUS 100 to 115: PROFINET IO system ID of the associated field device if the slot is located in a field device on PROFINET STATION Output INT I, Q, M, D, L With MASTER = 0: Number of the rack With MASTER > 0: Station number of the field device SLOT Output INT I, Q, M, D, L Slot number SUBSLOT Output INT I, Q, M, D, L The SUBSLOT parameter is not output by the instruction (always "0"). OFFSET Output INT I, Q, M, D, L The OFFSET parameter is not output by the instruction (always "0"). You will find more detailed information on valid data types in "Overview of the valid data types (Page 1204)". Parameter RET_VAL Error code* (W#16#...) Explanation 0000 No error occurred. 8090 Specified logical address invalid General error information See also: GET_ERR_ID: Get error ID locally (Page 1964) * The error codes can be displayed as integer or hexadecimal values in the program editor. For additional information on toggling display formats, refer to "See also". See also Instructions for address conversion (Page 2805) WinCC Basic V13.0 System Manual, 02/2014 2815 Programming the PLC 9.7 References RD_LGADR: Determine IO addresses from the hardware identifier Description Based on the hardware identifier, you can determine the logical addresses of a module, a central submodule or a submodule for PNIO with the "RD_LGADR" instruction. You can specify the hardware ID of the submodule at the LADDR parameter. The addresses are written to the PEADDR and PAADDR parameters is ascending order. - For an input module, only the PEADDR parameter is written. For an output module, the PAADDR parameter is written. - An Array of WORD is used to store the addresses in each case. The number of addresses is output at the PECOUNT parameter (for an input module) and PACOUNT parameter (for an output module). Parameters The following table shows the parameters of the instruction "RD_LGADR": Parameter Declaration Data type Memory area IOID Input BYTE I, Q, M, D, L or constant Address area identifier: Description B#16#54 = Peripheral input (PI) B#16#55 = Peripheral output (PQ) LADDR Input HW_ANY I, Q, M, D, L or constant Hardware identifier of the module or the submodule. RET_VAL Return INT I, Q, M, D, L Error information PEADDR Output ANY I, Q, M, D, L Field for the PI addresses with the Array of WORD data type PECOUNT Output INT I, Q, M, D, L Number of returned PI addresses PAADDR Output ANY I, Q, M, D, L Field for the PQ addresses with the Array of WORD data type PACOUNT Output INT I, Q, M, D, L Number of returned PQ addresses You can find additional information on valid data types under "Overview of the valid data types (Page 1204)". RET_VAL parameter Error code Explanation (W#16#...) 0000 No error occurred. 8090 Specified logical address invalid or illegal value for the IOID parameter. 80A0 Error in the output parameter PEADDR: The data type of the array elements is not WORD. 2816 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Error code Explanation (W#16#...) 80A1 Error in the output parameter PAADDR: The data type of the array elements is not WORD. 80A2 Error in the output parameter PEADDR: The specified array could not accommodate all the logical addresses. 80A3 Error in the output parameter PAADDR: The specified array could not accommodate all the logical addresses. General error information See also: GET_ERR_ID: Get error ID locally (Page 1964) See also Instructions for address conversion (Page 2805) GADR_LGC: Determine hardware identifier from slot and offset in the user data address area Description You use the "GADR_LGC" instruction to determine the hardware identifier of a signal module. The hardware identifier is determined from the module slot and the offset in the user data address area of the module. If you use the "GADR_LGC" instruction on power modules or modules with packed addresses (ET 200S), then the diagnostics address will be returned. Parameters The following table shows the parameters of the instruction "GADR_LGC": Parameter Declaration Data type Memory area Description SUBNETID Input BYTE I, Q, M, D, L or constant Area ID: 0: If the slot is located in the central module 1 to 32: DP master system ID of the corresponding distributed I/O system if the slot is in a distributed I/O device. 100 to 115: PROFINET IO system ID of the associated field device if the slot is located in a field device on PROFINET RACK Input WORD I, Q, M, D, L or constant Number of the rack, if area identifier is 0 Device number of the distributed I/O device if the area identifier > 0 SLOT Input WORD I, Q, M, D, L or constant Slot no. SUBSLOT Input BYTE I, Q, M, D, L or constant Sub-module slot (if no sub-module can be inserted, 0 must be entered here) WinCC Basic V13.0 System Manual, 02/2014 2817 Programming the PLC 9.7 References Parameter Declaration Data type Memory area SUBADDR Input WORD I, Q, M, D, L or constant Offset in the user data address area of the module Description RET_VAL Return INT I, Q, M, D, L Error information IOID Output BYTE I, Q, M, D, L The IOID output parameter is not written (always "0"). LADDR Output HW_MODUL E I, Q, M, D, L Hardware identifier of the module You will find more detailed information on valid data types in "Overview of the valid data types (Page 1204)". Parameter RET_VAL Error code* Explanation (W#16#...) 0000 No error occurred. 8093 Illegal value for SUBNETID parameter 8094 No subnet was configured with the specified SUBNETID . 8095 Illegal value for RACK parameter. 8096 Illegal value for SLOT parameter. 8097 Illegal value for SUBSLOT parameter. 8098 Illegal value for SUBADDR parameter. 8099 The slot is not configured. 809A The sub-address of the selected slot is not configured (only possible with central I/O for CPU and IM). General error information See also: GET_ERR_ID: Get error ID locally (Page 1964) * The error codes can be displayed as integer or hexadecimal values in the program editor. For additional information on toggling display formats, refer to "See also". See also Instructions for address conversion (Page 2805) LGC_GADR: Determine slot from hardware identifier Description You use the "LGC_GADR" instruction to determine the module slot belonging to a hardware identifier. Note The "LGC_GADR" instruction cannot be used on a module with packed addresses (ET 200S). 2818 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameters The following table shows the parameters of the instruction "LGC_GADR": Parameter Declaration Data type Memory area IOID Input BYTE I, Q, M, D, L or constant Is not evaluated. Description LADDR Input HW_MODUL E I, Q, M, D, L or constant Hardware identifier of the module RET_VAL Return INT I, Q, M, D, L Error information AREA Output BYTE I, Q, M, D, L Area ID: indicates how the remaining output parameters are to be interpreted: 0: Central module 2: PROFIBUS DP RACK Output WORD I, Q, M, D, L Rack number: With central module AREA= 0): - Rack number For PROFIBUS DP (AREA=2): SLOT Output WORD I, Q, M, D, L - Low byte: Station number - High byte: DP master system ID Slot number: With central module AREA= 0): - Slot number For PROFIBUS DP (AREA=2): - SUBADDR Output WORD I, Q, M, D, L Slot no. in the station Is not output (always "0"). You will find more detailed information on valid data types in "Overview of the valid data types (Page 1204)". Parameter RET_VAL Error code* Explanation (W#16#...) 0000 No error occurred. 8090 Specified logical address invalid or illegal value for the IOID parameter. 8093 This instruction is not permitted for the module selected by the parameters IOID and LADDR . General error information See also: GET_ERR_ID: Get error ID locally (Page 1964) * The error codes can be displayed as integer or hexadecimal values in the program editor. For additional information on toggling display formats, refer to "See also". See also Instructions for address conversion (Page 2805) WinCC Basic V13.0 System Manual, 02/2014 2819 Programming the PLC 9.7 References 9.7.4 Technology 9.7.4.1 S7-1200 Motion Control S7-1200 Motion Control V4 MC_Power MC_Power: Enable, disable axis V4 Description The Motion Control instruction "MC_Power" enables or disables an axis. Requirements The positioning axis technology object has been configured correctly. There is no pending enable-inhibiting error. Override response Execution of "MC_Power" cannot be aborted by a Motion Control command. Disabling the axis (input parameter "Enable" = FALSE) aborts all Motion Control commands for the associated technology object in accordance with the selected "StopMode". Parameters Parameter Declaration Data type Default value Description Axis INPUT TO_Axis - Axis technology object Enable INPUT BOOL FALSE TRUE The axis is enabled. FALSE All current jobs are interrupted in accordance with the "StopMode" configured. The axis is stopped and disabled. StopMode INPUT INT 0 0 Emergency stop If a request to disable the axis is pending, the axis brakes at the configured emergency stop deceleration. The axis is disabled after reaching standstill. 1 Immediate stop If a request to disable the axis is pending, this axis is disabled without deceleration. The pulse output is stopped immediately. 2820 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameter Declaration Data type Default value Description 2 Emergency stop with jerk control If a request to disable the axis is pending, the axis brakes at the configured emergency stop deceleration. If the jerk control is activated, the configured jerk is taken into account. The axis is disabled after reaching standstill. Status OUTPUT BOOL FALSE Status of axis enable FALSE The axis is disabled. The axis does not execute Motion Control commands and does not accept any new commands (exception: MC_Reset command). The axis is not homed. Upon disabling, the status does not change to FALSE until the axis reaches a standstill. TRUE The axis is enabled. The axis is ready to execute Motion Control commands. Upon axis enabling, the status does not change to TRUE until the signal "Drive ready" is pending. If the "Drive ready" drive interface was not configured in the axis configuration, the status changes to TRUE immediately. Busy OUTPUT BOOL FALSE TRUE "MC_Power" is active. Error OUTPUT BOOL FALSE TRUE An error occurred in Motion Control instruction "MC_Power" or in the associated technology object. The cause of the error can be found in parameters "ErrorID" and "ErrorInfo". ErrorID OUTPUT WORD 16#0000 Error ID (Page 4436) for parameter "Error" ErrorInfo OUTPUT WORD 16#0000 Error info ID (Page 4436) for parameter "ErrorID" Note If the axis is switched off due to an error, it will be enabled again automatically after the error has been eliminated and acknowledged. This requires that the input parameter "Enable" has retained the value TRUE during this process. Enabling an axis with configured drive interface To enable the axis, follow these steps: 1. Check the requirements indicated above. 2. Initialize input parameter "StopMode" with the desired value. Set the input parameter "Enable" to TRUE. The enable output for "Drive enabled" changes to TRUE to enable the power to the drive. The CPU waits for the "Drive ready" signal of the drive. When the "Drive ready" signal is available at the configured ready input of the CPU, the axis is enabled. Output parameter "Status" and tag of technology object <Axis name>.StatusBits.Enable indicate the value TRUE. WinCC Basic V13.0 System Manual, 02/2014 2821 Programming the PLC 9.7 References Enabling an axis without configured drive interface To enable the axis, follow these steps: 1. Check the requirements indicated above. 2. Initialize input parameter "StopMode" with the desired value. Set the input parameter "Enable" to TRUE. The axis is enabled. The output parameter "Status" and the tag of the technology object <Axis name>.StatusBits.Enable indicate the value TRUE. Disabling an axis To disable an axis, you can follow the steps described below: 1. Bring the axis to a standstill. You can identify when the axis is at a standstill in the tag of the technology object <Axis name>.StatusBits.StandStill. 2. Set input parameter "Enable" to FALSE after standstill is reached. 3. If output parameters "Busy" and "Status" and tag of technology object <Axis name>.StatusBits.Enable indicate the value FALSE, disabling of the axis is complete. See also Overview of the Motion Control statements (Page 4400) List of ErrorIDs and ErrorInfos (technology objects as of V4) (Page 4436) MC_Power: Function chart V4 (Page 2823) MC_Reset: Acknowledge fault V4 (Page 2824) MC_Home: Home axes, set reference point V4 (Page 2826) MC_Halt: Halt axes V4 (Page 2829) MC_MoveAbsolute: Absolute positioning of axes V4 (Page 2832) MC_MoveRelative: Relative positioning of axes V4 (Page 2835) MC_MoveVelocity: Move axes at preset rotational speed V4 (Page 2839) MC_MoveJog: Move axes in jog mode V4 (Page 2843) MC_ChangeDynamic: Change dynamic settings of axis V4 (Page 2848) MC_CommandTable: Run axis commands as motion sequence V4 (Page 2846) MC_ReadParam: Continuously read motion data of a positioning axis V4 (Page 2850) MC_WriteParam: Write tag of positioning axis V4 (Page 2852) S7-1200 Motion Control V1...3 (Page 2853) 2822 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References MC_Power: Function chart V4 Function chart $[LVB (QDB )% )% 0&B3RZHU 0&B5HVHW $[LV (QDEOH 6WRS0RGH 6WDWXV %XV\ (UURU (UURU,' (UURU,QIR )% 6WDWXVB %XV\B (UURUB $[LVB ([HB $[LV ([HFXWH 'RQH %XV\ (UURU (UURU,' (UURU,QIR 'RQHB %XV\B (QDB W 6WDWXVB W W ([HB W 'RQHB W %XV\B W 'ULYH(QDEOHG W 'ULYH5HDG\ W %XV\B (UURUB )% 'ULYH,QWHUIDFH W An axis is enabled and then disabled again. When the drive has signaled "Drive ready" back to the CPU, the successful enable can be read out via "Status_1". Following an axis enable, an error has occurred that caused the axis to be disabled. The error is eliminated and acknowledged with "MC_Reset". The axis is then enabled again. See also MC_Power: Enable, disable axis V4 (Page 2820) WinCC Basic V13.0 System Manual, 02/2014 2823 Programming the PLC 9.7 References MC_Reset MC_Reset: Acknowledge fault V4 Description Motion Control instruction "MC_Reset" can be used to acknowledge "Operating error with axis stop" and "Configuration error". The errors that require acknowledgement can be found in the "List of ErrorIDs and ErrorInfos" under "Remedy". The axis configuration can be downloaded to the work memory after a download in RUN operating mode. Requirements The positioning axis technology object has been configured correctly. The cause of a pending configuration error requiring acknowledgement has been eliminated (for example, acceleration in positioning axis technology object has been changed to a valid value). Override response The MC_Reset command cannot be aborted by any other Motion Control command. The new MC_Reset command does not abort any other active Motion Control commands. Parameters Parameter Declaration Data type Default value Description Axis INPUT TO_Axis - Axis technology object Execute INPUT BOOL FALSE Start of the command with a positive edge Restart INPUT BOOL FALSE TRUE Download the axis configuration from the load memory to the work memory. The command can only be executed when the axis is disabled. Refer to the notes on Download to the CPU (Page 4378). FALSE Acknowledges pending errors Done OUTPUT BOOL FALSE TRUE Error has been acknowledged. Busy OUTPUT BOOL FALSE TRUE The command is being executed. Error OUTPUT BOOL FALSE TRUE An error occurred during execution of the command. The cause of the error can be found in parameters "ErrorID" and "ErrorInfo". ErrorID OUTPUT WORD 16#0000 Error ID (Page 4436) for parameter "Error" ErrorInfo OUTPUT WORD 16#0000 Error info ID (Page 4436) for parameter "ErrorID" 2824 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Acknowledging an error requiring acknowledgement with MC_Reset To acknowledge an error, follow these steps: 1. Check the requirements indicated above. 2. Start the acknowledgement of the error with a rising edge at input parameter "Execute". 3. If output parameter "Done" indicates the value TRUE and tag of technology object <Axis name>.StatusBits.Error the value FALSE, the error has been acknowledged. See also Overview of the Motion Control statements (Page 4400) List of ErrorIDs and ErrorInfos (technology objects as of V4) (Page 4436) Download to CPU (Page 4378) MC_Power: Enable, disable axis V4 (Page 2820) MC_Home: Home axes, set reference point V4 (Page 2826) MC_Halt: Halt axes V4 (Page 2829) MC_MoveAbsolute: Absolute positioning of axes V4 (Page 2832) MC_MoveRelative: Relative positioning of axes V4 (Page 2835) MC_MoveVelocity: Move axes at preset rotational speed V4 (Page 2839) MC_MoveJog: Move axes in jog mode V4 (Page 2843) MC_CommandTable: Run axis commands as motion sequence V4 (Page 2846) MC_ChangeDynamic: Change dynamic settings of axis V4 (Page 2848) MC_ReadParam: Continuously read motion data of a positioning axis V4 (Page 2850) MC_WriteParam: Write tag of positioning axis V4 (Page 2852) S7-1200 Motion Control V1...3 (Page 2853) WinCC Basic V13.0 System Manual, 02/2014 2825 Programming the PLC 9.7 References MC_Home MC_Home: Home axes, set reference point V4 Description Motion Control instruction "MC_Home" is used to match the axis coordinates to the real, physical drive position. Homing is required for absolute positioning of the axis. The following types of homing can be executed: Active homing (Mode = 3) The homing procedure is executed automatically. Passive homing (Mode = 2) During passive homing, the "MC_Home" Motion Control instruction does not carry out any homing motion. The traversing motion required for this must be implemented by the user via other Motion Control instructions. When the homing switch is detected, the axis is homed. Direct homing absolute (Mode = 0) The current axis position is set to the value of parameter "Position". Direct homing relative (Mode = 1) The current axis position is offset by the value of parameter "Position". Requirements The positioning axis technology object has been configured correctly. The axis is enabled. No MC_CommandTable command may be active upon start with Mode = 0, 1, or 2. Override response The override response depends on the selected mode: Mode = 0, 1 The MC_Home command cannot be aborted by any other Motion Control command. The MC_Home command does not abort any active Motion Control commands. Positionrelated motion commands are resumed after homing according to the new homing position (value at input parameter: "Position"). Mode = 2 The MC_Home command can be aborted by the following Motion Control commands: MC_Home command Mode = 2, 3 The new MC_Home command aborts the following active Motion Control command: MC_Home command Mode = 2 Position-related motion commands are resumed after homing according to the new homing position (value at input parameter: "Position"). 2826 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Mode = 3 The MC_Home command can be aborted by the following Motion Control commands: MC_Home command Mode = 3 MC_Halt command MC_MoveAbsolute command MC_MoveRelative command MC_MoveVelocity command MC_MoveJog command MC_CommandTable command The new MC_Home command aborts the following active Motion Control commands: MC_Home command Mode = 2, 3 MC_Halt command MC_MoveAbsolute command MC_MoveRelative command MC_MoveVelocity command MC_MoveJog command MC_CommandTable command Parameters Parameter Declaration Data type Default value Description Axis INPUT TO_Axis - Axis technology object Execute INPUT BOOL FALSE Start of the command with a positive edge Position INPUT REAL 0.0 Mode = 0, 2, and 3 Absolute position of axis after completion of the homing operation Mode = 1 Correction value for the current axis position Limit values: -1.0e12 Position 1.0e12 Mode INPUT INT 0 Homing mode 0 Direct homing (absolute) New axis position is the position value of parameter "Position". 1 Direct homing (relative) New axis position is the current axis position + position value of parameter "Position". WinCC Basic V13.0 System Manual, 02/2014 2827 Programming the PLC 9.7 References Parameter Declaration Data type Default value Description 2 Passive homing Homing according to the axis configuration. Following homing, the value of parameter "Position" is set as the new axis position. 3 Active homing Homing procedure in accordance with the axis configuration. Following homing, the value of parameter "Position" is set as the new axis position. Done OUTPUT BOOL FALSE TRUE Command completed Busy OUTPUT BOOL FALSE TRUE The command is being executed. CommandAborted OUTPUT BOOL FALSE TRUE During execution the command was aborted by another command. Error OUTPUT BOOL FALSE TRUE An error occurred during execution of the command. The cause of the error can be found in parameters "ErrorID" and "ErrorInfo". ErrorID OUTPUT WORD 16#0000 Error ID (Page 4436) for parameter "Error" ErrorInfo OUTPUT WORD 16#0000 Error info ID (Page 4436) for parameter "ErrorID" Note Axis homing is lost under the following conditions: Disabling of axis by the "MC_Power" Motion Control instruction Changeover between automatic mode and manual control Upon start of active homing. After successful completion of the homing operation, axis homing is again available. After POWER OFF -> POWER ON of the CPU After CPU restart (RUN-STOP -> STOP-RUN) Homing an axis To home the axis, follow these stops: 1. Check the requirements indicated above. 2. Initialize the necessary input parameters with values, and start the homing operation with a rising edge at input parameter "Execute" 3. If output parameter "Done" and technology object tag <Axis name>.StatusBits.HomingDone indicate the value TRUE, homing is complete. See also Overview of the Motion Control statements (Page 4400) List of ErrorIDs and ErrorInfos (technology objects as of V4) (Page 4436) 2828 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References MC_Power: Enable, disable axis V4 (Page 2820) MC_Reset: Acknowledge fault V4 (Page 2824) MC_Halt: Halt axes V4 (Page 2829) MC_MoveAbsolute: Absolute positioning of axes V4 (Page 2832) MC_MoveRelative: Relative positioning of axes V4 (Page 2835) MC_MoveVelocity: Move axes at preset rotational speed V4 (Page 2839) MC_MoveJog: Move axes in jog mode V4 (Page 2843) MC_CommandTable: Run axis commands as motion sequence V4 (Page 2846) MC_ChangeDynamic: Change dynamic settings of axis V4 (Page 2848) MC_ReadParam: Continuously read motion data of a positioning axis V4 (Page 2850) MC_WriteParam: Write tag of positioning axis V4 (Page 2852) S7-1200 Motion Control V1...3 (Page 2853) MC_Halt MC_Halt: Halt axes V4 Description The "MC_Halt" Motion Control instruction stops all movements and brings the axis to a standstill with the configured deceleration. The standstill position is not defined. Requirements The positioning axis technology object has been configured correctly. The axis is enabled. Override response The MC_Halt command can be aborted by the following Motion Control commands: MC_Home command Mode = 3 MC_Halt command MC_MoveAbsolute command MC_MoveRelative command MC_MoveVelocity command MC_MoveJog command MC_CommandTable command The new MC_Halt command aborts the following active Motion Control commands: WinCC Basic V13.0 System Manual, 02/2014 2829 Programming the PLC 9.7 References MC_Home command Mode = 3 MC_Halt command MC_MoveAbsolute command MC_MoveRelative command MC_MoveVelocity command MC_MoveJog command MC_CommandTable command Parameters Parameter Declaration Data type Default value Description Axis INPUT TO_SpeedAxis - Axis technology object Execute INPUT BOOL FALSE Start of the command with a positive edge Done OUTPUT BOOL FALSE TRUE Zero velocity reached Busy OUTPUT BOOL FALSE TRUE The command is being executed. CommandAborted OUTPUT BOOL FALSE TRUE During execution the command was aborted by another command. Error OUTPUT BOOL FALSE TRUE An error occurred during execution of the command. The cause of the error can be found in parameters "ErrorID" and "ErrorInfo". ErrorID OUTPUT WORD 16#0000 Error ID (Page 4436) for parameter "Error" ErrorInfo OUTPUT WORD 16#0000 Error info ID (Page 4436) for parameter "ErrorID" See also Overview of the Motion Control statements (Page 4400) List of ErrorIDs and ErrorInfos (technology objects as of V4) (Page 4436) MC_Halt: Function chart V4 (Page 2831) MC_Power: Enable, disable axis V4 (Page 2820) MC_Reset: Acknowledge fault V4 (Page 2824) MC_Home: Home axes, set reference point V4 (Page 2826) MC_MoveAbsolute: Absolute positioning of axes V4 (Page 2832) MC_MoveRelative: Relative positioning of axes V4 (Page 2835) MC_MoveVelocity: Move axes at preset rotational speed V4 (Page 2839) MC_MoveJog: Move axes in jog mode V4 (Page 2843) MC_CommandTable: Run axis commands as motion sequence V4 (Page 2846) MC_ChangeDynamic: Change dynamic settings of axis V4 (Page 2848) MC_ReadParam: Continuously read motion data of a positioning axis V4 (Page 2850) 2830 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References MC_WriteParam: Write tag of positioning axis V4 (Page 2852) S7-1200 Motion Control V1...3 (Page 2853) MC_Halt: Function chart V4 Function chart $[LVB ([HB )% )% 0&B0RYH9HORFLW\ 0&B+DOW $[LV ,Q9HORFLW\ ([HFXWH %XV\ 9HORFLW\ &RPPDQG$ERUWHG (UURU 'LUHFWLRQ (UURU,' &XUUHQW (UURU,QIR ,Q9HOB %XV\B $ERUWB $[LVB ([HB $[LV ([HFXWH 'RQH %XV\ &RPPDQG$ERUWHG (UURU (UURU,' (UURU,QIR 'RQHB %XV\B $ERUWB )% ([HB ,Q9HOB W %XV\B W $ERUWB W W )% ([HB 'RQHB W %XV\B W $ERUWB W W 9HORFLW\ $[LVB W The following values were configured in the configuration window Dynamics > General: Acceleration: 10.0 Deceleration: 5.0 WinCC Basic V13.0 System Manual, 02/2014 2831 Programming the PLC 9.7 References The axis is braked by an MC_Halt command until it comes to a standstill. The axis standstill is signaled via "Done_2". While an MC_Halt command is braking the axis, this command is aborted by another motion command. The abort is signaled via "Abort_2". See also MC_Halt: Halt axes V4 (Page 2829) MC_MoveAbsolute MC_MoveAbsolute: Absolute positioning of axes V4 Description The "MC_MoveAbsolute" Motion Control instruction starts an axis positioning motion to move it to an absolute position. Requirements The positioning axis technology object has been configured correctly. The axis is enabled. The axis is homed. Override response The MC_MoveAbsolute command can be aborted by the following Motion Control commands: MC_Home command Mode = 3 MC_Halt command MC_MoveAbsolute command MC_MoveRelative command MC_MoveVelocity command MC_MoveJog command MC_CommandTable command The new MC_MoveAbsolute command aborts the following active Motion Control commands: MC_Home command Mode = 3 MC_Halt command MC_MoveAbsolute command MC_MoveRelative command MC_MoveVelocity command 2832 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References MC_MoveJog command MC_CommandTable command Parameters Parameter Declaration Data type Default value Description Axis INPUT TO_Positioning Axis - Axis technology object Execute INPUT BOOL FALSE Start of the command with a positive edge Position INPUT REAL 0.0 Absolute target position Limit values: -1.0e12 Position 1.0e12 Velocity INPUT REAL 10.0 Velocity of axis This velocity is not always reached on account of the configured acceleration and deceleration and the target position to be approached. Limit values: Start/stop velocity Velocity maximum velocity Done OUTPUT BOOL FALSE TRUE Absolute target position reached Busy OUTPUT BOOL FALSE TRUE The command is being executed. CommandAborted OUTPUT BOOL FALSE TRUE During execution the command was aborted by another command. Error OUTPUT BOOL FALSE TRUE An error occurred during execution of the command. The cause of the error can be found in parameters "ErrorID" and "ErrorInfo". ErrorID OUTPUT WORD 16#0000 Error ID (Page 4436) for parameter "Error" ErrorInfo OUTPUT WORD 16#0000 Error info ID (Page 4436) for parameter "ErrorID" See also Overview of the Motion Control statements (Page 4400) List of ErrorIDs and ErrorInfos (technology objects as of V4) (Page 4436) MC_MoveAbsolute: Function chart V4 (Page 2834) MC_Power: Enable, disable axis V4 (Page 2820) MC_Reset: Acknowledge fault V4 (Page 2824) MC_Home: Home axes, set reference point V4 (Page 2826) MC_Halt: Halt axes V4 (Page 2829) MC_MoveRelative: Relative positioning of axes V4 (Page 2835) MC_MoveVelocity: Move axes at preset rotational speed V4 (Page 2839) MC_MoveJog: Move axes in jog mode V4 (Page 2843) MC_CommandTable: Run axis commands as motion sequence V4 (Page 2846) WinCC Basic V13.0 System Manual, 02/2014 2833 Programming the PLC 9.7 References MC_ChangeDynamic: Change dynamic settings of axis V4 (Page 2848) MC_ReadParam: Continuously read motion data of a positioning axis V4 (Page 2850) MC_WriteParam: Write tag of positioning axis V4 (Page 2852) S7-1200 Motion Control V1...3 (Page 2853) MC_MoveAbsolute: Function chart V4 Function chart )% )% 0&B0RYH$EVROXWH 0&B0RYH$EVROXWH $[LVB ([HB $[LV ([HFXWH 3RVLWLRQ 9HORFLW\ 'RQH %XV\ &RPPDQG$ERUWHG (UURU (UURU,' (UURU,QIR )% ([HB 'RQHB %XV\B $ERUWB )% ([HB 'RQHB %XV\B 'RQHB %XV\B $ERUWB $[LVB ([HB $[LV ([HFXWH 3RVLWLRQ 9HORFLW\ 'RQH %XV\ &RPPDQG$ERUWHG (UURU (UURU,' (UURU,QIR 'RQHB %XV\B W W W W W W W 9HORFLW\ $[LVB W 3RVLWLRQ $[LVB 2834 W WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References The following values were configured in the configuration window Dynamics > General: Acceleration: 10.0 Deceleration: 10.0 An axis is moved to absolute position 1000.0 with an MC_MoveAbsolute command. When the axis reaches the target position, this is signaled via "Done_1". When "Done_1" = TRUE, another MC_MoveAbsolute command, with target position 1500.0, is started. Because of the response times (e.g., cycle time of user program, etc.), the axis comes to a standstill briefly (see zoomed-in detail). When the axis reaches the new target position, this is signaled via "Done_2". An active MC_MoveAbsolute command is aborted by another MC_MoveAbsolute command. The abort is signaled via "Abort_1". The axis is then moved at the new velocity to the new target position 1500.0. When the new target position is reached, this is signaled via "Done_2". See also MC_MoveAbsolute: Absolute positioning of axes V4 (Page 2832) MC_MoveRelative MC_MoveRelative: Relative positioning of axes V4 Description The "MC_MoveRelative" Motion Control instruction starts a positioning motion relative to the start position. Requirements The positioning axis technology object has been configured correctly. The axis is enabled. Override response The MC_MoveRelative command can be aborted by the following Motion Control commands: MC_Home command Mode = 3 MC_Halt command MC_MoveAbsolute command MC_MoveRelative command MC_MoveVelocity command MC_MoveJog command MC_CommandTable command The new MC_MoveRelative command aborts the following active Motion Control commands: WinCC Basic V13.0 System Manual, 02/2014 2835 Programming the PLC 9.7 References MC_Home command Mode = 3 MC_Halt command MC_MoveAbsolute command MC_MoveRelative command MC_MoveVelocity command MC_MoveJog command MC_CommandTable command Parameters Parameter Declaration Data type Default value Description Axis INPUT TO_Positioning Axis - Axis technology object Execute INPUT BOOL FALSE Start of the command with a positive edge Distance INPUT REAL 0.0 Travel distance for the positioning operation Limit values: -1.0e12 Distance 1.0e12 Velocity INPUT REAL 10.0 Velocity of axis This velocity is not always reached on account of the configured acceleration and deceleration and the distance to be traveled. Limit values: Start/stop velocity Velocity maximum velocity Done OUTPUT BOOL FALSE TRUE Target position reached Busy OUTPUT BOOL FALSE TRUE The command is being executed. CommandAborted OUTPUT BOOL FALSE TRUE During execution the command was aborted by another command. Error OUTPUT BOOL FALSE TRUE An error occurred during execution of the command. The cause of the error can be found in parameters "ErrorID" and "ErrorInfo". ErrorID OUTPUT WORD 16#0000 Error ID (Page 4436) for parameter "Error" ErrorInfo OUTPUT WORD 16#0000 Error info ID (Page 4436) for parameter "ErrorID" See also Overview of the Motion Control statements (Page 4400) List of ErrorIDs and ErrorInfos (technology objects as of V4) (Page 4436) MC_MoveRelative: Function chart V4 (Page 2838) MC_Power: Enable, disable axis V4 (Page 2820) MC_Reset: Acknowledge fault V4 (Page 2824) MC_Home: Home axes, set reference point V4 (Page 2826) 2836 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References MC_Halt: Halt axes V4 (Page 2829) MC_MoveAbsolute: Absolute positioning of axes V4 (Page 2832) MC_MoveVelocity: Move axes at preset rotational speed V4 (Page 2839) MC_MoveJog: Move axes in jog mode V4 (Page 2843) MC_CommandTable: Run axis commands as motion sequence V4 (Page 2846) MC_ChangeDynamic: Change dynamic settings of axis V4 (Page 2848) MC_ReadParam: Continuously read motion data of a positioning axis V4 (Page 2850) MC_WriteParam: Write tag of positioning axis V4 (Page 2852) S7-1200 Motion Control V1...3 (Page 2853) WinCC Basic V13.0 System Manual, 02/2014 2837 Programming the PLC 9.7 References MC_MoveRelative: Function chart V4 Function chart )% )% 0&B0RYH5HODWLYH $[LV ([HFXWH 'LVWDQFH 9HORFLW\ $[LVB ([HB 0&B0RYH5HODWLYH 'RQH %XV\ &RPPDQG$ERUWHG (UURU (UURU,' (UURU,QIR 'RQHB %XV\B $ERUWB $[LVB ([HB $[LV ([HFXWH 'LVWDQFH 9HORFLW\ 'RQH %XV\ &RPPDQG$ERUWHG (UURU (UURU,' (UURU,QIR 'RQHB %XV\B )% ([HB W %XV\B W 'RQHB W $ERUWB W )% ([HB W %XV\B 'RQHB 9HORFLW\ $[LVB W W 3RVLWLRQ $[LVB W W The following values were configured in the configuration window Dynamics > General: Acceleration: 10.0 Deceleration: 10.0 2838 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References The axis is moved by an MC_MoveRelative command by the distance ("Distance") 1000.0. When the axis reaches the target position, this is signaled via "Done_1". When "Done_1" = TRUE, another MC_MoveRelative command, with travel distance 500.0, is started. Because of the response times (e.g., cycle time of user program, etc.), the axis comes to a standstill briefly (see zoomed-in detail). When the axis reaches the new target position, this is signaled via "Done_2". An active MC_MoveRelative command is aborted by another MC_MoveRelative command. The abort is signaled via "Abort_1". The axis is then moved at the new velocity by the new distance ("Distance") 500.0. When the new target position is reached, this is signaled via "Done_2". See also MC_MoveRelative: Relative positioning of axes V4 (Page 2835) MC_MoveVelocity MC_MoveVelocity: Move axes at preset rotational speed V4 Description The Motion Control instruction "MC_MoveVelocity" moves the axis constantly at the specified velocity. Requirements The positioning axis technology object has been configured correctly. The axis is enabled. Override response MC_MoveVelocity can be aborted by the following Motion Control commands: MC_Home command Mode = 3 MC_Halt command MC_MoveAbsolute command MC_MoveRelative command MC_MoveVelocity command MC_MoveJog command MC_CommandTable command The new MC_MoveVelocity command aborts the following active Motion Control commands: MC_Home command Mode = 3 MC_Halt command MC_MoveAbsolute command MC_MoveRelative command WinCC Basic V13.0 System Manual, 02/2014 2839 Programming the PLC 9.7 References MC_MoveVelocity command MC_MoveJog command MC_CommandTable command Parameters Parameter Declaration Data type Default value Description Axis INPUT TO_SpeedAxis - Axis technology object Execute INPUT BOOL FALSE Start of the command with a positive edge Velocity INPUT REAL 10.0 Velocity specification for axis motion Limit values: Start/stop velocity |Velocity maximum velocity (Velocity = 0.0 is permitted) Direction INPUT INT 0 Direction specification 0 Direction of rotation corresponds to the sign of the value in parameter "Velocity" 1 Positive direction of rotation (The sign of the value in parameter "Velocity" is ignored) 2 Negative direction of rotation (The sign of the value in parameter "Velocity" is ignored) Current INPUT BOOL FALSE Maintain current velocity FALSE "Maintain current velocity" is deactivated. The values of parameters "Velocity" and "Direction" are used. TRUE "Maintain current velocity" is activated. The values in parameters "Velocity" and "Direction" are not taken into account. When the axis resumes motion at the current velocity, the "InVelocity" parameter returns the value TRUE. InVelocity OUTPUT BOOL FALSE TRUE "Current" = FALSE: The velocity specified in parameter "Velocity" was reached. "Current" = TRUE: The axis travels at the current velocity at the start time. Busy OUTPUT BOOL FALSE TRUE The command is being executed. CommandAborted OUTPUT BOOL FALSE TRUE During execution the command was aborted by another command. Error OUTPUT BOOL FALSE TRUE An error occurred during execution of the command. The cause of the error can be found in parameters "ErrorID" and "ErrorInfo". ErrorID OUTPUT WORD 16#0000 Error ID (Page 4436) for parameter "Error" ErrorInfo OUTPUT WORD 16#0000 Error info ID (Page 4436) for parameter "ErrorID" 2840 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Note PLCopen Version 2.0 The Motion Control instruction "MC_MoveVelocity" is compatible to PLCopen Version 2.0 as of V4. The "InVelocity" and "Busy" parameters show their status regardless of the "Execute" parameter until the command is overridden or stopped by an error. For more information, refer to the section " Tracking active commands (Page 4410). Behavior with zero setpoint velocity (Velocity = 0.0) An MC_MoveVelocity command with "Velocity" = 0.0 (such as an MC_Halt command) aborts active motion commands and stops the axis with the configured deceleration. When the axis comes to a standstill, output parameter "InVelocity" indicates TRUE for at least one program cycle. "Busy" indicates the value TRUE during the deceleration process and changes to FALSE together with "InVelocity". If parameter "Execute" = TRUE is set, "InVelocity" and "Busy" are latched. When the "MC_MoveVelocity" command is started, status bit "SpeedCommand" is set in the technology object. Status bit "ConstantVelocity" is set upon axis standstill. Both bits are adapted to the new situation when a new motion command is started. See also Overview of the Motion Control statements (Page 4400) List of ErrorIDs and ErrorInfos (technology objects as of V4) (Page 4436) MC_MoveVelocity: Function chart V4 (Page 2842) MC_Power: Enable, disable axis V4 (Page 2820) MC_Reset: Acknowledge fault V4 (Page 2824) MC_Home: Home axes, set reference point V4 (Page 2826) MC_Halt: Halt axes V4 (Page 2829) MC_MoveAbsolute: Absolute positioning of axes V4 (Page 2832) MC_MoveRelative: Relative positioning of axes V4 (Page 2835) MC_MoveJog: Move axes in jog mode V4 (Page 2843) MC_CommandTable: Run axis commands as motion sequence V4 (Page 2846) MC_ChangeDynamic: Change dynamic settings of axis V4 (Page 2848) MC_ReadParam: Continuously read motion data of a positioning axis V4 (Page 2850) MC_WriteParam: Write tag of positioning axis V4 (Page 2852) S7-1200 Motion Control V1...3 (Page 2853) WinCC Basic V13.0 System Manual, 02/2014 2841 Programming the PLC 9.7 References MC_MoveVelocity: Function chart V4 Function chart )% )% 0&B0RYH9HORFLW\ 0&B0RYH9HORFLW\ $[LV ,Q9HORFLW\ ([HFXWH %XV\ 9HORFLW\ &RPPDQG$ERUWHG (UURU 'LUHFWLRQ (UURU,' &XUUHQW (UURU,QIR $[LVB ([HB ,Q9HOB %XV\B $ERUWB $[LVB ([HB $[LV ,Q9HORFLW\ ([HFXWH %XV\ 9HORFLW\ &RPPDQG$ERUWHG (UURU 'LUHFWLRQ (UURU,' &XUUHQW (UURU,QIR ,Q9HOB %XV\B )% ([HB W %XV\B ,Q9HOB W W $ERUWB W )% ([HB %XV\B W W ,Q9HOB W 9HORFLW\ $[LVB W The following values were configured in the configuration window Dynamics > General: Acceleration: 10.0 Deceleration: 10.0 An active MC_MoveVelocity command signals via "InVel_1" that its target velocity has been reached. It is then aborted by another MC_MoveVelocity command. The abort is signaled via "Abort_1". When the new target velocity 15.0 is reached, this is signaled via "InVel_2". The axis then continues moving at the new constant velocity. An active MC_MoveVelocity command is aborted by another MC_MoveVelocity command prior to reaching its target velocity. The abort is signaled via "Abort_1". When the new target velocity 15.0 is reached, this is signaled via "InVel_2". The axis then continues moving at the new constant velocity. 2842 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References See also MC_MoveVelocity: Move axes at preset rotational speed V4 (Page 2839) MC_MoveJog MC_MoveJog: Move axes in jog mode V4 Description Motion control instruction "MC_MoveJog" moves the axis constantly at the specified velocity in jog mode. You use this Motion Control instruction, for example, for testing and commissioning purposes. Requirements The positioning axis technology object has been configured correctly. The axis is enabled. Override response The MC_MoveJog command can be aborted by the following Motion Control commands: MC_Home command Mode = 3 MC_Halt command MC_MoveAbsolute command MC_MoveRelative command MC_MoveVelocity command MC_MoveJog command MC_CommandTable command The new MC_MoveJog command aborts the following active Motion Control commands: MC_Home command Mode = 3 MC_Halt command MC_MoveAbsolute command MC_MoveRelative command MC_MoveVelocity command MC_MoveJog command MC_CommandTable command WinCC Basic V13.0 System Manual, 02/2014 2843 Programming the PLC 9.7 References Parameters Parameter Declaration Data type Default value Description Axis INPUT TO_SpeedAxis - Axis technology object JogForward INPUT BOOL FALSE As long as the parameter is TRUE, the axis moves in the positive direction at the velocity specified in parameter "Velocity". JogBackward INPUT BOOL FALSE As long as the parameter is TRUE, the axis moves in the negative direction at the velocity specified in parameter "Velocity". If both parameters are simultaneously TRUE, the axis stops with the configured deceleration. An error is indicated in parameters "Error", "ErrorID", and "ErrorInfo". Velocity INPUT REAL 10.0 Preset velocity for jog mode Limit values: Start/stop velocity velocity maximum velocity InVelocity OUTPUT BOOL FALSE TRUE The velocity specified in parameter "Velocity" was reached. Busy OUTPUT BOOL FALSE TRUE The command is being executed. CommandAborted OUTPUT BOOL FALSE TRUE During execution the command was aborted by another command. Error OUTPUT BOOL FALSE TRUE An error occurred during execution of the command. The cause of the error can be found in parameters "ErrorID" and "ErrorInfo". ErrorID OUTPUT WORD 16#0000 Error ID (Page 4436) for parameter "Error" ErrorInfo OUTPUT WORD 16#0000 Error info ID (Page 4436) for parameter "ErrorID" See also Overview of the Motion Control statements (Page 4400) List of ErrorIDs and ErrorInfos (technology objects as of V4) (Page 4436) MC_MoveJog: Function chart V4 (Page 2845) MC_Power: Enable, disable axis V4 (Page 2820) MC_Reset: Acknowledge fault V4 (Page 2824) MC_Home: Home axes, set reference point V4 (Page 2826) MC_Halt: Halt axes V4 (Page 2829) MC_MoveAbsolute: Absolute positioning of axes V4 (Page 2832) MC_MoveRelative: Relative positioning of axes V4 (Page 2835) MC_MoveVelocity: Move axes at preset rotational speed V4 (Page 2839) MC_CommandTable: Run axis commands as motion sequence V4 (Page 2846) MC_ChangeDynamic: Change dynamic settings of axis V4 (Page 2848) MC_ReadParam: Continuously read motion data of a positioning axis V4 (Page 2850) 2844 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References MC_WriteParam: Write tag of positioning axis V4 (Page 2852) S7-1200 Motion Control V1...3 (Page 2853) MC_MoveJog: Function chart V4 Function chart )% 0&B0RYH-RJ $[LVB -RJB) -RJB% $[LV ,Q9HORFLW\ -RJ)RUZDUG %XV\ -RJ%DFNZDUG &RPPDQG$ERUWHG (UURU 9HORFLW\ (UURU,' (UURU,QIR ,Q9HOB %XV\B )% -RJB) W -RJB% W ,Q9HOB %XV\B W W 9HORFLW\ $[LVB W The following values were configured in the configuration window Dynamics > General: Acceleration: 10.0 Deceleration: 5.0 The axis is moved in the positive direction in jog mode via "Jog_F". When the target velocity 50.0 is reached, this is signaled via "InVel_1". After "Jog_F" is reset, the axis is braked to a standstill. The axis is moved in the negative direction in jog mode via "Jog_B". When the target velocity -50.0 is reached, this is signaled via "InVel_1". When "Jog_B" is set, the value at parameter "Velocity" changes to 25.0. "InVel_1" is reset and the axis is braked. When the new target velocity -25.0 is reached, this is signaled via "InVel_1". After "Jog_B" is reset, the axis is braked to a standstill. WinCC Basic V13.0 System Manual, 02/2014 2845 Programming the PLC 9.7 References See also MC_MoveJog: Move axes in jog mode V4 (Page 2843) MC_CommandTable MC_CommandTable: Run axis commands as motion sequence V4 Description The Motion Control instruction "MC_CommandTable" combines multiple individual axis control commands in one movement sequence. Requirements The positioning axis technology object has been inserted and correctly configured. The command table technology object has been inserted and correctly configured. The axis is enabled. Override response The MC_CommandTable command can be aborted by the following Motion Control commands: MC_Home command Mode = 3 MC_Halt command MC_MoveAbsolute command MC_MoveRelative command MC_MoveVelocity command MC_MoveJog command MC_CommandTable command The new MC_CommandTable command aborts the following active Motion Control commands: MC_Home command Mode = 3 MC_Halt command MC_MoveAbsolute command MC_MoveRelative command MC_MoveVelocity command MC_MoveJog command MC_CommandTable command The active Motion Control command is cancelled by the start of the first "Positioning Relative", "Positioning Absolute", "Velocity set point" or "Halt" command. 2846 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameters Parameter Declaration Data type Default value Description Axis INPUT TO_SpeedAxis - Axis technology object CommandTab INPUT le TO_CommandT able - Command table technology object Execute INPUT BOOL FALSE Command table start with positive edge StartStep INPUT INT 1 Defines the step at which the execution of the command table should begin Limit values: 1 StartStep EndStep EndStep INPUT INT 32 Defines the step up to which the execution of command table should take place Limit values: StartStep EndStep 32 Done OUTPUT BOOL FALSE TRUE Command table has been successfully executed Busy OUTPU BOOL FALSE TRUE The command table is being executed. CommandAb orted OUTPUT BOOL FALSE TRUE The command table was cancelled by another command. Error OUTPUT BOOL FALSE TRUE An error occurred during execution of the command table. The cause of the error can be found in parameters "ErrorID" and "ErrorInfo". ErrorID OUTPUT WORD 16#0000 Error ID (Page 4436) for parameter "Error" ErrorInfo OUTPUT WORD 16#0000 Error info ID (Page 4436) for parameter "ErrorID" CurrentStep OUTPUT INT 0 Step in command table currently being executed StepCode OUTPUT WORD 16#0000 User-defined numerical value / bit pattern of the step currently being executed See also Overview of the Motion Control statements (Page 4400) List of ErrorIDs and ErrorInfos (technology objects as of V4) (Page 4436) MC_Power: Enable, disable axis V4 (Page 2820) MC_Reset: Acknowledge fault V4 (Page 2824) MC_Home: Home axes, set reference point V4 (Page 2826) MC_Halt: Halt axes V4 (Page 2829) MC_MoveAbsolute: Absolute positioning of axes V4 (Page 2832) MC_MoveRelative: Relative positioning of axes V4 (Page 2835) MC_MoveVelocity: Move axes at preset rotational speed V4 (Page 2839) MC_MoveJog: Move axes in jog mode V4 (Page 2843) MC_ChangeDynamic: Change dynamic settings of axis V4 (Page 2848) MC_ReadParam: Continuously read motion data of a positioning axis V4 (Page 2850) WinCC Basic V13.0 System Manual, 02/2014 2847 Programming the PLC 9.7 References MC_WriteParam: Write tag of positioning axis V4 (Page 2852) S7-1200 Motion Control V1...3 (Page 2853) MC_ChangeDynamic MC_ChangeDynamic: Change dynamic settings of axis V4 Description Motion Control instruction "MC_ChangeDynamic" allows you to change the following settings of the axis: Change the ramp-up time (acceleration) value Change the ramp-down time (deceleration) value Change the emergency stop ramp-down time (emergency stop deceleration) value Change the smoothing time (jerk) value For the effectiveness of the change, refer to the description of the tag (Page 4446). Requirements The positioning axis technology object has been configured correctly. Override response A MC_ChangeDynamic command cannot be aborted by any other Motion Control command. A new MC_ChangeDynamic command does not abort any active Motion Control commands. Parameters Parameter Declaration Data type Default value Description Axis INPUT TO_SpeedAxis - Axis technology object Execute INPUT BOOL FALSE Start of the command with a positive edge ChangeRa mpUp INPUT BOOL FALSE TRUE RampUpTi me INPUT REAL 5.00 Time (in seconds) to accelerate axis from standstill to configured maximum velocity without jerk limit. Change ramp-up time in line with input parameter "RampUpTime" The change will influence the tag <Axis name>. Config.DynamicDefaults.Acceleration. For the effectiveness of the change, refer to the description of this tag. ChangeRa mpDown 2848 INPUT BOOL FALSE TRUE Change ramp-down time to correspond to input parameter "RampDownTime" WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameter Declaration RampDown INPUT Time Data type Default value Description REAL 5.00 Time (in seconds) to decelerate axis from the configured maximum velocity to standstill without jerk limiter. The change will influence the tag <Axis name>. Config.DynamicDefaults.Deceleration . For the effectiveness of the change, refer to the description of this tag. ChangeEm ergency INPUT BOOL FALSE TRUE Change emergency stop ramp-down time in line with input parameter "EmergencyRampTime" Emergency RampTime INPUT REAL 2.00 Time (in seconds) to decelerate the axis from configured maximum velocity to standstill without jerk limiter in emergency stop mode. The change will influence the tag <Axis name>. Config.DynamicDefaults.EmergencyDeceleration . For the effectiveness of the change, refer to the description of this tag. ChangeJer kTime INPUT BOOL FALSE TRUE Change smoothing time according to the input parameter "JerkTime" JerkTime INPUT REAL 0.25 Smoothing time (in seconds) used for the axis acceleration and deceleration ramps The change will influence the tag <Axis name>. Config.DynamicDefaults.Jerk . For the effectiveness of the change, refer to the description of this tag. Done OUTPUT BOOL FALSE TRUE The changed values have been written to the technology data block. The description of the tags will show when the change becomes effective. Error OUTPUT BOOL FALSE TRUE An error occurred during execution of the command. The cause of the error can be found in parameters "ErrorID" and "ErrorInfo". ErrorID OUTPUT WORD 16#0000 Error ID (Page 4436) for parameter "Error" ErrorInfo OUTPUT WORD 16#0000 Error info ID (Page 4436) for parameter "ErrorID" Note At the input parameters "RampUpTime", "RampDownTime", "EmergencyRampTime" and "JerkTime", values can be entered which exceed the admissible limits of the resulting parameters: "Acceleration", "Deceleration", "Emergency stop deceleration" and "Jerk". Ensure that your inputs are within the valid range, taking into consideration the equations and limits in section "Dynamic (Page 4345)". See also Overview of the Motion Control statements (Page 4400) List of ErrorIDs and ErrorInfos (technology objects as of V4) (Page 4436) Changing the configuration of dynamics in the user program (Page 4351) Changing the homing configuration in the user program (Page 4358) Tags of the positioning axis technology object as of V4 (Page 4446) MC_Power: Enable, disable axis V4 (Page 2820) WinCC Basic V13.0 System Manual, 02/2014 2849 Programming the PLC 9.7 References MC_Reset: Acknowledge fault V4 (Page 2824) MC_Home: Home axes, set reference point V4 (Page 2826) MC_Halt: Halt axes V4 (Page 2829) MC_MoveAbsolute: Absolute positioning of axes V4 (Page 2832) MC_MoveRelative: Relative positioning of axes V4 (Page 2835) MC_MoveVelocity: Move axes at preset rotational speed V4 (Page 2839) MC_MoveJog: Move axes in jog mode V4 (Page 2843) MC_CommandTable: Run axis commands as motion sequence V4 (Page 2846) MC_ReadParam: Continuously read motion data of a positioning axis V4 (Page 2850) MC_WriteParam: Write tag of positioning axis V4 (Page 2852) S7-1200 Motion Control V1...3 (Page 2853) MC_ReadParam MC_ReadParam: Continuously read motion data of a positioning axis V4 Description Motion Control instruction "MC_ReadParam" enables continuous reading of motion data of an axis. The current value of the corresponding tag is determined at the start of the command. The following motion data can be read: Current position of the axis Current velocity of the axis Current distance of axis from target position Target position of the axis Requirements The positioning axis technology object has been configured correctly. Override response A MC_ReadParam command cannot be aborted by any other Motion Control command. A new MC_ReadParam command does not abort any active Motion Control commands. 2850 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameters Parameter Declaration Data type Default value Description Enable INPUT BOOL FALSE TRUE Read the tag specified with the "Parameter" and store the value in the destination address specified with "Value". FALSE Do not update assigned motion data Parameter INPUT VARIANT (REAL) - VARIANT pointer to the value to be read. The following tags are permitted: <Axis name>.Position <Axis name>.Velocity <Axis name>.StatusPositioning.Distance <Axis name>.StatusPositioning.TargetPosition Value INOUT VARIANT (REAL) - VARIANT pointer to the target tag or destination address to which the read value is to be written. Valid OUTPUT BOOL FALSE TRUE Busy OUTPUT BOOL FALSE TRUE The command is being executed. Error OUTPUT BOOL FALSE TRUE An error occurred during execution of the command. The cause of the error can be found in parameters "ErrorID" and "ErrorInfo". ErrorID OUTPUT WORD 16#0000 Error ID (Page 4436) for parameter "Error" ErrorInfo OUTPUT WORD 16#0000 Error info ID (Page 4436) for parameter "ErrorID" The read value is valid. FALSE The read value is invalid. See also Overview of the Motion Control statements (Page 4400) List of ErrorIDs and ErrorInfos (technology objects as of V4) (Page 4436) S7-1200 Motion Control V1...3 (Page 2853) MC_Power: Enable, disable axis V4 (Page 2820) MC_Reset: Acknowledge fault V4 (Page 2824) MC_Home: Home axes, set reference point V4 (Page 2826) MC_Halt: Halt axes V4 (Page 2829) MC_MoveAbsolute: Absolute positioning of axes V4 (Page 2832) MC_MoveRelative: Relative positioning of axes V4 (Page 2835) MC_MoveVelocity: Move axes at preset rotational speed V4 (Page 2839) MC_MoveJog: Move axes in jog mode V4 (Page 2843) MC_CommandTable: Run axis commands as motion sequence V4 (Page 2846) MC_ChangeDynamic: Change dynamic settings of axis V4 (Page 2848) MC_WriteParam: Write tag of positioning axis V4 (Page 2852) WinCC Basic V13.0 System Manual, 02/2014 2851 Programming the PLC 9.7 References MC_WriteParam MC_WriteParam: Write tag of positioning axis V4 Description Motion Control instruction "MC_WriteParam" enables the writing of tags of the positioning axis technology object in the user program. In contrast to the value assignment of the tags in the user program, "MC_WriteParam" can also change values of read-only tags. You can learn about the tags, the conditions under which they can be written and the time at which they take effect in the description of the technology object tags (Page 4446). Requirements The positioning axis technology object has been configured correctly. To write tags that are read-only in the user program, the axis must be disabled. Override response A MC_WriteParam command cannot be aborted by any other Motion Control command. A new MC_WriteParam command does not abort any active Motion Control commands. Parameters Parameter Declaration Data type Default value Description Parameter INPUT VARIANT (BOOL, INT, DINT, REAL) - VARIANT pointer to the technology object tag (Page 4446) positioning axis (destination address) to be written Value INPUT VARIANT (BOOL, INT, DINT, REAL) - VARIANT pointer to the value to be written (source address) Execute INPUT BOOL FALSE Start of the command with a positive edge Done OUTPUT BOOL FALSE TRUE Value was written Busy OUTPUT BOOL FALSE TRUE The command is being executed. Error OUTPUT BOOL FALSE TRUE An error occurred during execution of the command. The cause of the error can be found in parameters "ErrorID" and "ErrorInfo". ErrorID OUTPUT WORD 16#0000 Error ID (Page 4436) for parameter "Error" ErrorInfo OUTPUT WORD 16#0000 Error info ID (Page 4436) for parameter "ErrorID" 2852 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References See also Overview of the Motion Control statements (Page 4400) List of ErrorIDs and ErrorInfos (technology objects as of V4) (Page 4436) Tags of the positioning axis technology object as of V4 (Page 4446) S7-1200 Motion Control V1...3 (Page 2853) MC_Power: Enable, disable axis V4 (Page 2820) MC_Reset: Acknowledge fault V4 (Page 2824) MC_Home: Home axes, set reference point V4 (Page 2826) MC_Halt: Halt axes V4 (Page 2829) MC_MoveAbsolute: Absolute positioning of axes V4 (Page 2832) MC_MoveRelative: Relative positioning of axes V4 (Page 2835) MC_MoveVelocity: Move axes at preset rotational speed V4 (Page 2839) MC_MoveJog: Move axes in jog mode V4 (Page 2843) MC_CommandTable: Run axis commands as motion sequence V4 (Page 2846) MC_ChangeDynamic: Change dynamic settings of axis V4 (Page 2848) MC_ReadParam: Continuously read motion data of a positioning axis V4 (Page 2850) S7-1200 Motion Control V1...3 MC_Power MC_Power: Enable, disable axis V1...3 Description The Motion Control instruction "MC_Power" enables or disables an axis. Requirements The axis technology object has been configured correctly. There is no pending enable-inhibiting error. Override response Execution of "MC_Power" cannot be aborted by a Motion Control command. Disabling the axis (input parameter "Enable" = FALSE) aborts all Motion Control commands for the associated technology object in accordance with the selected "StopMode". WinCC Basic V13.0 System Manual, 02/2014 2853 Programming the PLC 9.7 References Parameters Parameter Declaration Data type Default value Description Axis INPUT TO_Axis_1 - Axis technology object Enable INPUT BOOL FALSE TRUE Motion Control attempts to enable the axis. FALSE All current jobs are interrupted in accordance with the "StopMode" configured. The axis is stopped and disabled. StopMode INPUT INT 0 0 Emergency stop If a request to disable the axis is pending, the axis brakes at the configured emergency stop deceleration. The axis is disabled after reaching standstill. 1 Immediate stop If a request to disable the axis is pending, this axis is disabled without deceleration. The pulse output is stopped immediately. 2 Emergency stop with jerk control If a request to disable the axis is pending, the axis brakes at the configured emergency stop deceleration. If the jerk control is activated, the configured jerk is taken into account. The axis is disabled after reaching standstill. Status OUTPUT BOOL FALSE Status of axis enable FALSE The axis is disabled. The axis does not execute Motion Control commands and does not accept any new commands (exception: MC_Reset command). The axis is not homed. Upon disabling, the status does not change to FALSE until the axis reaches a standstill. TRUE The axis is enabled. The axis is ready to execute Motion Control commands. Upon axis enabling, the status does not change to TRUE until the signal "Drive ready" is pending. If the "Drive ready" drive interface was not configured in the axis configuration, the status changes to TRUE immediately. Busy OUTPUT BOOL FALSE TRUE "MC_Power" is active. Error OUTPUT BOOL FALSE TRUE An error occurred in Motion Control instruction "MC_Power" or in the associated technology object. The cause of the error can be found in parameters "ErrorID" and "ErrorInfo". ErrorID OUTPUT WORD 16#0000 Error ID (Page 4481) for parameter "Error" ErrorInfo OUTPUT WORD 16#0000 Error info ID (Page 4481) for parameter "ErrorID" 2854 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Note If the axis is switched off due to an error, it will be enabled again automatically after the error has been eliminated and acknowledged. This requires that the input parameter "Enable" has retained the value TRUE during this process. Enabling an axis with configured drive interface To enable the axis, follow these steps: 1. Check the requirements indicated above. 2. Initialize input parameter "StopMode" with the desired value. Set the input parameter "Enable" to TRUE. The enable output for "Drive enabled" changes to TRUE to enable the power to the drive. The CPU waits for the "Drive ready" signal of the drive. When the "Drive ready" signal is available at the configured Ready input of the CPU, the axis is enabled. The output parameter "Status" and the tag of the technology object <Axis name>.StatusBits.Enable indicate the value TRUE. Enabling an axis without configured drive interface To enable the axis, follow these steps: 1. Check the requirements indicated above. 2. Initialize input parameter "StopMode" with the desired value. Set the input parameter "Enable" to TRUE. The axis is enabled. The output parameter "Status" and the tag of the technology object <Axis name>.StatusBits.Enable indicate the value TRUE. Disabling an axis To disable an axis, you can follow the steps described below: 1. Bring the axis to a standstill. You can identify when the axis is at a standstill in the tag of the technology object <Axis name>.StatusBits.StandStill. 2. Set input parameter "Enable" to FALSE after standstill is reached. 3. If output parameters "Busy" and "Status" and the tag of technology object <Axis name>.StatusBits.Enable indicate the value FALSE, disabling of the axis is complete. See also Overview of the Motion Control statements (Page 4400) S7-1200 Motion Control V4 (Page 2820) ErrorIDs and ErrorInfos (Page 4481) MC_Power: Function chart V1...3 (Page 2856) MC_Reset: Acknowledge fault V1...3 (Page 2857) WinCC Basic V13.0 System Manual, 02/2014 2855 Programming the PLC 9.7 References MC_Home: Home axes, set reference point V1...3 (Page 2859) MC_Halt: Halt axes V1...3 (Page 2862) MC_MoveAbsolute: Absolute positioning of axes V1...3 (Page 2865) MC_MoveRelative: Relative positioning of axes V1...3 (Page 2868) MC_MoveVelocity: Move axes at preset rotational speed V1...3 (Page 2871) MC_MoveJog: Move axes in jog mode V1...3 (Page 2875) MC_CommandTable: Run axis commands as motion sequence V2...3 (Page 2878) MC_ChangeDynamic: Change dynamic settings of axis V2...3 (Page 2880) MC_Power: Function chart V1...3 Function chart $[LVB (QDB )% )% 0&B3RZHU 0&B5HVHW $[LV (QDEOH 6WRS0RGH 6WDWXV %XV\ (UURU (UURU,' (UURU,QIR )% 6WDWXVB %XV\B (UURUB $[LVB ([HB $[LV ([HFXWH 'RQH %XV\ (UURU (UURU,' (UURU,QIR 'RQHB %XV\B (QDB W 6WDWXVB W W ([HB W 'RQHB W %XV\B W 'ULYH(QDEOHG W 'ULYH5HDG\ W %XV\B (UURUB )% 'ULYH,QWHUIDFH 2856 W WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References An axis is enabled and then disabled again. When the drive has signaled "Drive ready" back to the CPU, the successful enable can be read out via "Status_1". Following an axis enable, an error has occurred that caused the axis to be disabled. The error is eliminated and acknowledged with "MC_Reset". The axis is then enabled again. See also MC_Power: Enable, disable axis V1...3 (Page 2853) MC_Reset MC_Reset: Acknowledge fault V1...3 Description Motion Control instruction "MC_Reset" can be used to acknowledge "Operating error with axis stop" and "Configuration error". The errors that require acknowledgement can be found in the "List of ErrorIDs and ErrorInfos" under "Remedy". From version V3.0, the axis configuration can be downloaded to the work memory in RUN operating mode. Requirements The axis technology object has been configured correctly. The cause of a pending configuration error requiring acknowledgement has been eliminated (for example, acceleration in positioning axis technology object has been changed to a valid value). Override response The MC_Reset command cannot be aborted by any other Motion Control command. The new MC_Reset command does not abort any other active Motion Control commands. Parameters Parameter Declaration Data type Default value Description Axis INPUT TO_Axis_1 - Axis technology object Execute INPUT BOOL FALSE Start of the command with a positive edge Restart INPUT BOOL FALSE (From version V3.0) TRUE Download the axis configuration from the load memory to the work memory. The command can only be executed when the axis is disabled. Refer to the notes on Download to the CPU (Page 4378). WinCC Basic V13.0 System Manual, 02/2014 2857 Programming the PLC 9.7 References Parameter Declaration Data type Default value Description FALSE Acknowledges pending errors Done OUTPUT BOOL FALSE TRUE Error has been acknowledged. Busy OUTPUT BOOL FALSE TRUE The command is being executed. Error OUTPUT BOOL FALSE TRUE An error occurred during execution of the command. The cause of the error can be found in parameters "ErrorID" and "ErrorInfo". ErrorID OUTPUT WORD 16#0000 Error ID (Page 4481) for parameter "Error" ErrorInfo OUTPUT WORD 16#0000 Error info ID (Page 4481) for parameter "ErrorID" Acknowledging an error requiring acknowledgement with MC_Reset To acknowledge an error, follow these steps: 1. Check the requirements indicated above. 2. Start the acknowledgement of the error with a rising edge at input parameter "Execute". 3. If output parameter "Done" indicates the value TRUE and tag of technology object <Axis name>.StatusBits.Error the value FALSE, the error has been acknowledged. See also Overview of the Motion Control statements (Page 4400) S7-1200 Motion Control V4 (Page 2820) ErrorIDs and ErrorInfos (Page 4481) Download to CPU (Page 4378) MC_Power: Enable, disable axis V1...3 (Page 2853) MC_Home: Home axes, set reference point V1...3 (Page 2859) MC_Halt: Halt axes V1...3 (Page 2862) MC_MoveAbsolute: Absolute positioning of axes V1...3 (Page 2865) MC_MoveRelative: Relative positioning of axes V1...3 (Page 2868) MC_MoveVelocity: Move axes at preset rotational speed V1...3 (Page 2871) MC_MoveJog: Move axes in jog mode V1...3 (Page 2875) MC_CommandTable: Run axis commands as motion sequence V2...3 (Page 2878) MC_ChangeDynamic: Change dynamic settings of axis V2...3 (Page 2880) 2858 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References MC_Home MC_Home: Home axes, set reference point V1...3 Description Motion Control instruction "MC_Home" is used to match the axis coordinates to the real, physical drive position. Homing is required for absolute positioning of the axis. The following types of homing can be executed: Active homing (Mode = 3) The homing procedure is executed automatically. Passive homing (Mode = 2) During passive homing, the "MC_Home" Motion Control instruction does not carry out any homing motion. The traversing motion required for this must be implemented by the user via other Motion Control instructions. When the homing switch is detected, the axis is homed. Direct homing absolute (Mode = 0) The current axis position is set to the value of parameter "Position". Direct homing relative (Mode = 1) The current axis position is offset by the value of parameter "Position". Requirements The axis technology object has been configured correctly. The axis is enabled. No MC_CommandTable command may be active upon start with Mode = 0, 1, or 2. Override response The override response depends on the selected mode: Mode = 0, 1 The MC_Home command cannot be aborted by any other Motion Control command. The MC_Home command does not abort any active Motion Control commands. Positionrelated motion commands are resumed after homing according to the new homing position (value at input parameter: "Position"). Mode = 2 The MC_Home command can be aborted by the following Motion Control commands: MC_Home command Mode = 2, 3 The new MC_Home command aborts the following active Motion Control command: MC_Home command Mode = 2 Position-related motion commands are resumed after homing according to the new homing position (value at input parameter: "Position"). WinCC Basic V13.0 System Manual, 02/2014 2859 Programming the PLC 9.7 References Mode = 3 The MC_Home command can be aborted by the following Motion Control commands: MC_Home command Mode = 3 MC_Halt command MC_MoveAbsolute command MC_MoveRelative command MC_MoveVelocity command MC_MoveJog command MC_CommandTable command The new MC_Home command aborts the following active Motion Control commands: MC_Home command Mode = 2, 3 MC_Halt command MC_MoveAbsolute command MC_MoveRelative command MC_MoveVelocity command MC_MoveJog command MC_CommandTable command Parameters Parameter Declaration Data type Default value Description Axis INPUT TO_Axis_1 - Axis technology object Execute INPUT BOOL FALSE Start of the command with a positive edge Position INPUT REAL 0.0 Mode = 0, 2, and 3 Absolute position of axis after completion of the homing operation Mode = 1 Correction value for the current axis position Limit values: -1.0e12 Position 1.0e12 Mode INPUT INT 0 Homing mode 0 Direct homing absolute New axis position is the position value of parameter "Position". 1 Direct homing relative New axis position is the current axis position + position value of parameter "Position". 2860 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameter Declaration Data type Default value Description 2 Passive homing Homing according to the axis configuration. Following homing, the value of parameter "Position" is set as the new axis position. 3 Active homing Homing procedure in accordance with the axis configuration. Following homing, the value of parameter "Position" is set as the new axis position. Done OUTPUT BOOL FALSE TRUE Command completed Busy OUTPUT BOOL FALSE TRUE The command is being executed. CommandAborted OUTPUT BOOL FALSE TRUE During execution the command was aborted by another command. Error OUTPUT BOOL FALSE TRUE An error occurred during execution of the command. The cause of the error can be found in parameters "ErrorID" and "ErrorInfo". ErrorID OUTPUT WORD 16#0000 Error ID (Page 4481) for parameter "Error" ErrorInfo OUTPUT WORD 16#0000 Error info ID (Page 4481) for parameter "ErrorID" Note Axis homing is lost under the following conditions: Disabling of axis by the "MC_Power" Motion Control instruction Changeover between automatic mode and manual control Upon start of active homing. After successful completion of the homing operation, axis homing is again available. After POWER OFF -> POWER ON of the CPU After CPU restart (RUN-STOP -> STOP-RUN) Homing an axis To home the axis, follow these stops: 1. Check the requirements indicated above. 2. Initialize the necessary input parameters with values, and start the homing operation with a rising edge at input parameter "Execute" 3. If output parameter "Done" and technology object tag <Axis name>.StatusBits.HomingDone indicate the value TRUE, homing is complete. See also Overview of the Motion Control statements (Page 4400) S7-1200 Motion Control V4 (Page 2820) WinCC Basic V13.0 System Manual, 02/2014 2861 Programming the PLC 9.7 References ErrorIDs and ErrorInfos (Page 4481) MC_Power: Enable, disable axis V1...3 (Page 2853) MC_Reset: Acknowledge fault V1...3 (Page 2857) MC_Halt: Halt axes V1...3 (Page 2862) MC_MoveAbsolute: Absolute positioning of axes V1...3 (Page 2865) MC_MoveRelative: Relative positioning of axes V1...3 (Page 2868) MC_MoveVelocity: Move axes at preset rotational speed V1...3 (Page 2871) MC_MoveJog: Move axes in jog mode V1...3 (Page 2875) MC_CommandTable: Run axis commands as motion sequence V2...3 (Page 2878) MC_ChangeDynamic: Change dynamic settings of axis V2...3 (Page 2880) MC_Halt MC_Halt: Halt axes V1...3 Description The "MC_Halt" Motion Control instruction stops all movements and brings the axis to a standstill with the configured deceleration. The standstill position is not defined. Requirements The axis technology object has been configured correctly. The axis is enabled. Override response The MC_Halt command can be aborted by the following Motion Control commands: MC_Home command Mode = 3 MC_Halt command MC_MoveAbsolute command MC_MoveRelative command MC_MoveVelocity command MC_MoveJog command MC_CommandTable command The new MC_Halt command aborts the following active Motion Control commands: MC_Home command Mode = 3 MC_Halt command 2862 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References MC_MoveAbsolute command MC_MoveRelative command MC_MoveVelocity command MC_MoveJog command MC_CommandTable command Parameters Parameter Declaration Data type Default value Description Axis INPUT TO_Axis_1 - Axis technology object Execute INPUT BOOL FALSE Start of the command with a positive edge Done OUTPUT BOOL FALSE TRUE Zero velocity reached Busy OUTPUT BOOL FALSE TRUE The command is being executed. CommandAborted OUTPUT BOOL FALSE TRUE During execution the command was aborted by another command. Error OUTPUT BOOL FALSE TRUE An error occurred during execution of the command. The cause of the error can be found in parameters "ErrorID" and "ErrorInfo". ErrorID OUTPUT WORD 16#0000 Error ID (Page 4481) for parameter "Error" ErrorInfo OUTPUT WORD 16#0000 Error info ID (Page 4481) for parameter "ErrorID" See also Overview of the Motion Control statements (Page 4400) S7-1200 Motion Control V4 (Page 2820) ErrorIDs and ErrorInfos (Page 4481) MC_Halt: Function chart V1...3 (Page 2864) MC_Power: Enable, disable axis V1...3 (Page 2853) MC_Reset: Acknowledge fault V1...3 (Page 2857) MC_Home: Home axes, set reference point V1...3 (Page 2859) MC_MoveAbsolute: Absolute positioning of axes V1...3 (Page 2865) MC_MoveRelative: Relative positioning of axes V1...3 (Page 2868) MC_MoveVelocity: Move axes at preset rotational speed V1...3 (Page 2871) MC_MoveJog: Move axes in jog mode V1...3 (Page 2875) MC_CommandTable: Run axis commands as motion sequence V2...3 (Page 2878) MC_ChangeDynamic: Change dynamic settings of axis V2...3 (Page 2880) WinCC Basic V13.0 System Manual, 02/2014 2863 Programming the PLC 9.7 References MC_Halt: Function chart V1...3 Function chart )% )% 0&B0RYH9HORFLW\ $[LVB ([HB $[LV ,Q9HORFLW\ ([HFXWH %XV\ 9HORFLW\ &RPPDQG$ERUWHG (UURU 'LUHFWLRQ (UURU,' &XUUHQW (UURU,QIR 0&B+DOW ,Q9HOB %XV\B $ERUWB $[LVB ([HB $[LV ([HFXWH 'RQH %XV\ &RPPDQG$ERUWHG (UURU (UURU,' (UURU,QIR 'RQHB %XV\B $ERUWB )% ([HB ,Q9HOB W %XV\B W $ERUWB W W )% ([HB 'RQHB W %XV\B W $ERUWB W W 9HORFLW\ $[LVB W The following values were configured in the configuration window Dynamics > General: Acceleration: 10.0 Deceleration: 5.0 The axis is braked by an MC_Halt command until it comes to a standstill. The axis standstill is signaled via "Done_2". While an MC_Halt command is braking the axis, this command is aborted by another motion command. The abort is signaled via "Abort_2". 2864 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References See also MC_Halt: Halt axes V1...3 (Page 2862) MC_MoveAbsolute MC_MoveAbsolute: Absolute positioning of axes V1...3 Description The "MC_MoveAbsolute" Motion Control instruction starts an axis positioning motion to move it to an absolute position. Requirements The axis technology object has been configured correctly. The axis is enabled. The axis is homed. Override response The MC_MoveAbsolute command can be aborted by the following Motion Control commands: MC_Home command Mode = 3 MC_Halt command MC_MoveAbsolute command MC_MoveRelative command MC_MoveVelocity command MC_MoveJog command MC_CommandTable command The new MC_MoveAbsolute command aborts the following active Motion Control commands: MC_Home command Mode = 3 MC_Halt command MC_MoveAbsolute command MC_MoveRelative command MC_MoveVelocity command MC_MoveJog command MC_CommandTable command WinCC Basic V13.0 System Manual, 02/2014 2865 Programming the PLC 9.7 References Parameters Parameter Declaration Data type Default value Description Axis INPUT TO_Axis_1 - Axis technology object Execute INPUT BOOL FALSE Start of the command with a positive edge Position INPUT REAL 0.0 Absolute target position Limit values: -1.0e12 Position 1.0e12 Velocity INPUT REAL 10.0 Velocity of axis This velocity is not always reached on account of the configured acceleration and deceleration and the target position to be approached. Limit values: Start/stop velocity Velocity maximum velocity Done OUTPUT BOOL FALSE TRUE Absolute target position reached Busy OUTPUT BOOL FALSE TRUE The command is being executed. CommandAborted OUTPUT BOOL FALSE TRUE During execution the command was aborted by another command. Error OUTPUT BOOL FALSE TRUE An error occurred during execution of the command. The cause of the error can be found in parameters "ErrorID" and "ErrorInfo". ErrorID OUTPUT WORD 16#0000 Error ID (Page 4481) for parameter "Error" ErrorInfo OUTPUT WORD 16#0000 Error info ID (Page 4481) for parameter "ErrorID" See also Overview of the Motion Control statements (Page 4400) S7-1200 Motion Control V4 (Page 2820) ErrorIDs and ErrorInfos (Page 4481) MC_MoveAbsolute: Function chart V1...3 (Page 2867) MC_Power: Enable, disable axis V1...3 (Page 2853) MC_Reset: Acknowledge fault V1...3 (Page 2857) MC_Home: Home axes, set reference point V1...3 (Page 2859) MC_Halt: Halt axes V1...3 (Page 2862) MC_MoveRelative: Relative positioning of axes V1...3 (Page 2868) MC_MoveVelocity: Move axes at preset rotational speed V1...3 (Page 2871) MC_MoveJog: Move axes in jog mode V1...3 (Page 2875) MC_CommandTable: Run axis commands as motion sequence V2...3 (Page 2878) MC_ChangeDynamic: Change dynamic settings of axis V2...3 (Page 2880) 2866 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References MC_MoveAbsolute: Function chart V1...3 Function chart )% )% 0&B0RYH$EVROXWH 0&B0RYH$EVROXWH $[LVB ([HB $[LV ([HFXWH 3RVLWLRQ 9HORFLW\ 'RQH %XV\ &RPPDQG$ERUWHG (UURU (UURU,' (UURU,QIR )% ([HB 'RQHB %XV\B $ERUWB )% ([HB 'RQHB %XV\B 'RQHB %XV\B $ERUWB $[LVB ([HB $[LV ([HFXWH 3RVLWLRQ 9HORFLW\ 'RQH %XV\ &RPPDQG$ERUWHG (UURU (UURU,' (UURU,QIR 'RQHB %XV\B W W W W W W W 9HORFLW\ $[LVB W 3RVLWLRQ $[LVB W The following values were configured in the configuration window Dynamics > General: Acceleration: 10.0 Deceleration: 10.0 WinCC Basic V13.0 System Manual, 02/2014 2867 Programming the PLC 9.7 References An axis is moved to absolute position 1000.0 with an MC_MoveAbsolute command. When the axis reaches the target position, this is signaled via "Done_1". When "Done_1" = TRUE, another MC_MoveAbsolute command, with target position 1500.0, is started. Because of the response times (e.g., cycle time of user program, etc.), the axis comes to a standstill briefly (see zoomed-in detail). When the axis reaches the new target position, this is signaled via "Done_2". An active MC_MoveAbsolute command is aborted by another MC_MoveAbsolute command. The abort is signaled via "Abort_1". The axis is then moved at the new velocity to the new target position 1500.0. When the new target position is reached, this is signaled via "Done_2". See also MC_MoveAbsolute: Absolute positioning of axes V1...3 (Page 2865) MC_MoveRelative MC_MoveRelative: Relative positioning of axes V1...3 Description The "MC_MoveRelative" Motion Control instruction starts a positioning motion relative to the start position. Requirements The axis technology object has been configured correctly. The axis is enabled. Override response The MC_MoveRelative command can be aborted by the following Motion Control commands: MC_Home command Mode = 3 MC_Halt command MC_MoveAbsolute command MC_MoveRelative command MC_MoveVelocity command MC_MoveJog command MC_CommandTable command The new MC_MoveRelative command aborts the following active Motion Control commands: MC_Home command Mode = 3 MC_Halt command MC_MoveAbsolute command MC_MoveRelative command 2868 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References MC_MoveVelocity command MC_MoveJog command MC_CommandTable command Parameters Parameter Declaration Data type Default value Description Axis INPUT TO_Axis_1 - Axis technology object Execute INPUT BOOL FALSE Start of the command with a positive edge Distance INPUT REAL 0.0 Travel distance for the positioning operation Limit values: -1.0e12 Distance 1.0e12 Velocity INPUT REAL 10.0 Velocity of axis This velocity is not always reached on account of the configured acceleration and deceleration and the distance to be traveled. Limit values: Start/stop velocity Velocity maximum velocity Done OUTPUT BOOL FALSE TRUE Target position reached Busy OUTPUT BOOL FALSE TRUE The command is being executed. CommandAborted OUTPUT BOOL FALSE TRUE During execution the command was aborted by another command. Error OUTPUT BOOL FALSE TRUE An error occurred during execution of the command. The cause of the error can be found in parameters "ErrorID" and "ErrorInfo". ErrorID OUTPUT WORD 16#0000 Error ID (Page 4481) for parameter "Error" ErrorInfo OUTPUT WORD 16#0000 Error info ID (Page 4481) for parameter "ErrorID" See also Overview of the Motion Control statements (Page 4400) S7-1200 Motion Control V4 (Page 2820) ErrorIDs and ErrorInfos (Page 4481) MC_MoveRelative: Function chart V1...3 (Page 2870) MC_Power: Enable, disable axis V1...3 (Page 2853) MC_Reset: Acknowledge fault V1...3 (Page 2857) MC_Home: Home axes, set reference point V1...3 (Page 2859) MC_Halt: Halt axes V1...3 (Page 2862) MC_MoveAbsolute: Absolute positioning of axes V1...3 (Page 2865) MC_MoveVelocity: Move axes at preset rotational speed V1...3 (Page 2871) MC_MoveJog: Move axes in jog mode V1...3 (Page 2875) WinCC Basic V13.0 System Manual, 02/2014 2869 Programming the PLC 9.7 References MC_CommandTable: Run axis commands as motion sequence V2...3 (Page 2878) MC_ChangeDynamic: Change dynamic settings of axis V2...3 (Page 2880) MC_MoveRelative: Function chart V1...3 Function chart )% )% 0&B0RYH5HODWLYH 0&B0RYH5HODWLYH $[LV ([HFXWH 'LVWDQFH 9HORFLW\ $[LVB ([HB 'RQH %XV\ &RPPDQG$ERUWHG (UURU (UURU,' (UURU,QIR 'RQHB %XV\B $ERUWB $[LVB ([HB $[LV ([HFXWH 'LVWDQFH 9HORFLW\ 'RQH %XV\ &RPPDQG$ERUWHG (UURU (UURU,' (UURU,QIR 'RQHB %XV\B )% ([HB W %XV\B W 'RQHB W $ERUWB )% ([HB W W %XV\B 'RQHB 9HORFLW\ $[LVB W W 3RVLWLRQ $[LVB W W The following values were configured in the configuration window Dynamics > General: 2870 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Acceleration: 10.0 Deceleration: 10.0 The axis is moved by an MC_MoveRelative command by the distance ("Distance") 1000.0. When the axis reaches the target position, this is signaled via "Done_1". When "Done_1" = TRUE, another MC_MoveRelative command, with travel distance 500.0, is started. Because of the response times (e.g., cycle time of user program, etc.), the axis comes to a standstill briefly (see zoomed-in detail). When the axis reaches the new target position, this is signaled via "Done_2". An active MC_MoveRelative command is aborted by another MC_MoveRelative command. The abort is signaled via "Abort_1". The axis is then moved at the new velocity by the new distance ("Distance") 500.0. When the new target position is reached, this is signaled via "Done_2". See also MC_MoveRelative: Relative positioning of axes V1...3 (Page 2868) MC_MoveVelocity MC_MoveVelocity: Move axes at preset rotational speed V1...3 Description Motion control instruction "MC_MoveVelocity" moves the axis constantly at the specified velocity. Requirements The axis technology object has been configured correctly. The axis is enabled. Override response MC_MoveVelocity can be aborted by the following Motion Control commands: MC_Home command Mode = 3 MC_Halt command MC_MoveAbsolute command MC_MoveRelative command MC_MoveVelocity command MC_MoveJog command MC_CommandTable command The new MC_MoveVelocity command aborts the following active Motion Control commands: MC_Home command Mode = 3 MC_Halt command WinCC Basic V13.0 System Manual, 02/2014 2871 Programming the PLC 9.7 References MC_MoveAbsolute command MC_MoveRelative command MC_MoveVelocity command MC_MoveJog command MC_CommandTable command Parameters Parameter Declaration Data type Default value Description Axis INPUT TO_Axis_1 - Axis technology object Execute INPUT BOOL FALSE Start of the command with a positive edge Velocity INPUT REAL 10.0 Velocity specification for axis motion Limit values: Start/stop velocity |Velocity maximum velocity (Velocity = 0.0 is permitted) Direction INPUT INT 0 Direction specification 0 Direction of rotation corresponds to the sign of the value in parameter "Velocity" 1 Positive direction of rotation (The sign of the value in parameter "Velocity" is ignored) 2 Negative direction of rotation (The sign of the value in parameter "Velocity" is ignored) Current INPUT BOOL FALSE Maintain current velocity FALSE "Maintain current velocity" is deactivated. The values of parameters "Velocity" and "Direction" are used. TRUE "Maintain current velocity" is activated. The values in parameters "Velocity" and "Direction" are not taken into account. When the axis resumes motion at the current velocity, the "InVelocity" parameter returns the value TRUE. InVelocity OUTPUT BOOL FALSE TRUE "Current" = FALSE: The velocity specified in parameter "Velocity" was reached. "Current" = TRUE: The axis travels at the current velocity at the start time. Busy OUTPUT BOOL FALSE TRUE The command is being executed. CommandAborted OUTPUT BOOL FALSE TRUE During execution the command was aborted by another command. 2872 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameter Declaration Data type Default value Description Error OUTPUT BOOL FALSE TRUE ErrorID OUTPUT WORD 16#0000 Error ID (Page 4481) for parameter "Error" ErrorInfo OUTPUT WORD 16#0000 Error info ID (Page 4481) for parameter "ErrorID" An error occurred during execution of the command. The cause of the error can be found in parameters "ErrorID" and "ErrorInfo". Behavior with zero setpoint velocity (Velocity = 0.0) An MC_MoveVelocity command with "Velocity" = 0.0 (such as an MC_Halt command) aborts active motion commands and stops the axis with the configured deceleration. When the axis comes to a standstill, output parameter "InVelocity" indicates TRUE for at least one program cycle. "Busy" indicates the value TRUE during the deceleration process and changes to FALSE together with "InVelocity". If parameter "Execute" = TRUE is set, "InVelocity" and "Busy" are latched. When the "MC_MoveVelocity" command is started, status bit "SpeedCommand" is set in the technology object. Status bit "ConstantVelocity" is set upon axis standstill. Both bits are adapted to the new situation when a new motion command is started. See also Overview of the Motion Control statements (Page 4400) S7-1200 Motion Control V4 (Page 2820) ErrorIDs and ErrorInfos (Page 4481) MC_MoveVelocity: Function chart V1...3 (Page 2874) MC_Power: Enable, disable axis V1...3 (Page 2853) MC_Reset: Acknowledge fault V1...3 (Page 2857) MC_Home: Home axes, set reference point V1...3 (Page 2859) MC_Halt: Halt axes V1...3 (Page 2862) MC_MoveAbsolute: Absolute positioning of axes V1...3 (Page 2865) MC_MoveRelative: Relative positioning of axes V1...3 (Page 2868) MC_MoveJog: Move axes in jog mode V1...3 (Page 2875) MC_CommandTable: Run axis commands as motion sequence V2...3 (Page 2878) MC_ChangeDynamic: Change dynamic settings of axis V2...3 (Page 2880) WinCC Basic V13.0 System Manual, 02/2014 2873 Programming the PLC 9.7 References MC_MoveVelocity: Function chart V1...3 Function chart )% )% 0&B0RYH9HORFLW\ 0&B0RYH9HORFLW\ $[LV ,Q9HORFLW\ ([HFXWH %XV\ 9HORFLW\ &RPPDQG$ERUWHG (UURU 'LUHFWLRQ (UURU,' &XUUHQW (UURU,QIR $[LVB ([HB ,Q9HOB %XV\B $ERUWB $[LVB ([HB $[LV ,Q9HORFLW\ ([HFXWH %XV\ 9HORFLW\ &RPPDQG$ERUWHG (UURU 'LUHFWLRQ (UURU,' &XUUHQW (UURU,QIR ,Q9HOB %XV\B )% ([HB W %XV\B ,Q9HOB W W $ERUWB W )% ([HB %XV\B W W ,Q9HOB W 9HORFLW\ $[LVB W The following values were configured in the configuration window Dynamics > General: Acceleration: 10.0 Deceleration: 10.0 An active MC_MoveVelocity command signals via "InVel_1" that its target velocity has been reached. It is then aborted by another MC_MoveVelocity command. The abort is signaled via "Abort_1". When the new target velocity 15.0 is reached, this is signaled via "InVel_2". The axis then continues moving at the new constant velocity. An active MC_MoveVelocity command is aborted by another MC_MoveVelocity command prior to reaching its target velocity. The abort is signaled via "Abort_1". When the new target velocity 15.0 is reached, this is signaled via "InVel_2". The axis then continues moving at the new constant velocity. 2874 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References See also MC_MoveVelocity: Move axes at preset rotational speed V1...3 (Page 2871) MC_MoveJog MC_MoveJog: Move axes in jog mode V1...3 Description Motion control instruction "MC_MoveJog" moves the axis constantly at the specified velocity in jog mode. You use this Motion Control instruction, for example, for testing and commissioning purposes. Requirements The axis technology object has been configured correctly. The axis is enabled. Override response The MC_MoveJog command can be aborted by the following Motion Control commands: MC_Home command Mode = 3 MC_Halt command MC_MoveAbsolute command MC_MoveRelative command MC_MoveVelocity command MC_MoveJog command MC_CommandTable command The new MC_MoveJog command aborts the following active Motion Control commands: MC_Home command Mode = 3 MC_Halt command MC_MoveAbsolute command MC_MoveRelative command MC_MoveVelocity command MC_MoveJog command MC_CommandTable command WinCC Basic V13.0 System Manual, 02/2014 2875 Programming the PLC 9.7 References Parameters Parameter Declaration Data type Default value Description Axis INPUT TO_Axis_1 - Axis technology object JogForward INPUT BOOL FALSE As long as the parameter is TRUE, the axis moves in the positive direction at the velocity specified in parameter "Velocity". JogBackward INPUT BOOL FALSE As long as the parameter is TRUE, the axis moves in the negative direction at the velocity specified in parameter "Velocity". If both parameters are simultaneously TRUE, the axis stops with the configured deceleration. An error is indicated in parameters "Error", "ErrorID", and "ErrorInfo". Velocity INPUT REAL 10.0 Preset velocity for jog mode Limit values, instruction version V1.0: Start/stop velocity |Velocity maximum velocity Limits, instruction version V2.0: Start/stop velocity velocity maximum velocity InVelocity OUTPUT BOOL FALSE TRUE The velocity specified in parameter "Velocity" was reached. Busy OUTPUT BOOL FALSE TRUE The command is being executed. CommandAborted OUTPUT BOOL FALSE TRUE During execution the command was aborted by another command. Error OUTPUT BOOL FALSE TRUE An error occurred during execution of the command. The cause of the error can be found in parameters "ErrorID" and "ErrorInfo". ErrorID OUTPUT WORD 16#0000 Error ID (Page 4481) for parameter "Error" ErrorInfo OUTPUT WORD 16#0000 Error info ID (Page 4481) for parameter "ErrorID" See also Overview of the Motion Control statements (Page 4400) S7-1200 Motion Control V4 (Page 2820) ErrorIDs and ErrorInfos (Page 4481) MC_MoveJog: Function chart V1...3 (Page 2877) MC_Power: Enable, disable axis V1...3 (Page 2853) MC_Reset: Acknowledge fault V1...3 (Page 2857) MC_Home: Home axes, set reference point V1...3 (Page 2859) MC_Halt: Halt axes V1...3 (Page 2862) MC_MoveAbsolute: Absolute positioning of axes V1...3 (Page 2865) MC_MoveRelative: Relative positioning of axes V1...3 (Page 2868) MC_MoveVelocity: Move axes at preset rotational speed V1...3 (Page 2871) 2876 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References MC_CommandTable: Run axis commands as motion sequence V2...3 (Page 2878) MC_ChangeDynamic: Change dynamic settings of axis V2...3 (Page 2880) MC_MoveJog: Function chart V1...3 Function chart )% 0&B0RYH-RJ $[LVB -RJB) -RJB% $[LV ,Q9HORFLW\ -RJ)RUZDUG %XV\ -RJ%DFNZDUG &RPPDQG$ERUWHG (UURU 9HORFLW\ (UURU,' (UURU,QIR ,Q9HOB %XV\B )% -RJB) W -RJB% W ,Q9HOB %XV\B W W 9HORFLW\ $[LVB W The following values were configured in the configuration window Dynamics > General: Acceleration: 10.0 Deceleration: 5.0 The axis is moved in the positive direction in jog mode via "Jog_F". When the target velocity 50.0 is reached, this is signaled via "InVelo_1". After " Jog_F" is reset, the axis brakes again until it comes to a standstill. The axis is moved in the negative direction in jog mode via "Jog_B". When the target velocity 50.0 is reached, this is signaled via "InVelo_1". After " Jog_B" is reset, the axis brakes again until it comes to a standstill. WinCC Basic V13.0 System Manual, 02/2014 2877 Programming the PLC 9.7 References See also MC_MoveJog: Move axes in jog mode V1...3 (Page 2875) MC_CommandTable MC_CommandTable: Run axis commands as motion sequence V2...3 Description The Motion Control instruction "MC_CommandTable" combines multiple individual axis control commands in one movement sequence. Requirements The axis technology object has been inserted in V2 and correctly configured. The command table technology object has been inserted and correctly configured. The axis is enabled. Override response The MC_CommandTable command can be aborted by the following Motion Control commands: MC_Home command Mode = 3 MC_Halt command MC_MoveAbsolute command MC_MoveRelative command MC_MoveVelocity command MC_MoveJog command MC_CommandTable command The new MC_CommandTable command aborts the following active Motion Control commands: MC_Home command Mode = 3 MC_Halt command MC_MoveAbsolute command MC_MoveRelative command MC_MoveVelocity command MC_MoveJog command MC_CommandTable command The active Motion Control command is cancelled by the start of the first "Positioning Relative", "Positioning Absolute", "Velocity set point" or "Halt" command. 2878 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameters Parameter Declaration Data type Default value Description Axis INPUT TO_Axis_1 - Axis technology object CommandTab INPUT le TO_CommandT able_1 - Command table technology object Execute INPUT BOOL FALSE Command table start with positive edge StartStep INPUT INT 1 Defines the step at which the execution of the command table should begin Limit values: 1 StartStep EndStep EndStep INPUT INT 32 Defines the step up to which the execution of command table should take place Limit values: StartStep EndStep 32 Done OUTPUT BOOL FALSE TRUE Command table has been successfully executed Busy OUTPU BOOL FALSE TRUE The command table is being executed. CommandAb orted OUTPUT BOOL FALSE TRUE The command table was cancelled by another command. Error OUTPUT BOOL FALSE TRUE An error occurred during execution of the command table. The cause of the error can be found in parameters "ErrorID" and "ErrorInfo". ErrorID OUTPUT WORD 16#0000 Error ID (Page 4481) for parameter "Error" ErrorInfo OUTPUT WORD 16#0000 Error info ID (Page 4481) for parameter "ErrorID" CurrentStep OUTPUT INT 0 Step in command table currently being executed StepCode OUTPUT WORD 16#0000 User-defined numerical value / bit pattern of the step currently being executed See also Overview of the Motion Control statements (Page 4400) S7-1200 Motion Control V4 (Page 2820) ErrorIDs and ErrorInfos (Page 4481) MC_Power: Enable, disable axis V1...3 (Page 2853) MC_Reset: Acknowledge fault V1...3 (Page 2857) MC_Home: Home axes, set reference point V1...3 (Page 2859) MC_Halt: Halt axes V1...3 (Page 2862) MC_MoveAbsolute: Absolute positioning of axes V1...3 (Page 2865) MC_MoveRelative: Relative positioning of axes V1...3 (Page 2868) MC_MoveVelocity: Move axes at preset rotational speed V1...3 (Page 2871) MC_MoveJog: Move axes in jog mode V1...3 (Page 2875) MC_ChangeDynamic: Change dynamic settings of axis V2...3 (Page 2880) WinCC Basic V13.0 System Manual, 02/2014 2879 Programming the PLC 9.7 References MC_ChangeDynamic MC_ChangeDynamic: Change dynamic settings of axis V2...3 Description Motion Control instruction "MC_ChangeDynamic" allows you to change the following settings of the axis: Change the ramp-up time (acceleration) value Change the ramp-down time (deceleration) value Change the emergency stop ramp-down time (emergency stop deceleration) value Change the smoothing time (jerk) value For the effectiveness of the change, refer to the description of the tag (Page 4494). Requirements The axis technology object has been inserted in Version V2. The axis technology object has been configured correctly. Override response A MC_ChangeDynamic command cannot be aborted by any other Motion Control command. A new MC_ChangeDynamic command does not abort any active Motion Control commands. Parameters Parameter Declaration Data type Default value Description Axis INPUT TO_Axis_1 - Axis technology object Execute INPUT BOOL FALSE Start of the command with a positive edge ChangeRa mpUp INPUT BOOL FALSE TRUE RampUpTi me INPUT REAL 5.00 Time (in seconds) to accelerate axis from standstill to configured maximum velocity without jerk limit. Change ramp-up time in line with input parameter "RampUpTime" The change will influence the tag <Axis name>. Config.DynamicDefaults.Acceleration. For the effectiveness of the change, refer to the description of this tag. ChangeRa mpDown INPUT BOOL FALSE TRUE Change ramp-down time in line with input parameter "RampDownTime" RampDown INPUT Time REAL 5.00 Time (in seconds) to decelerate axis from the configured maximum velocity to standstill without jerk limiter. The change will influence the tag <Axis name>. Config.DynamicDefaults.Deceleration . For the effectiveness of the change, refer to the description of this tag. 2880 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameter Declaration Data type Default value Description ChangeEm ergency INPUT BOOL FALSE TRUE Emergency RampTime INPUT REAL 2.00 Time (in seconds) to decelerate the axis from configured maximum velocity to standstill without jerk limiter in emergency stop mode. Change emergency stop ramp-down time in line with input parameter "EmergencyRampTime" The change will influence the tag <Axis name>. Config.DynamicDefaults.EmergencyDeceleration . For the effectiveness of the change, refer to the description of this tag. ChangeJer kTime INPUT BOOL FALSE TRUE Change smoothing time according to the input parameter "JerkTime" JerkTime INPUT REAL 0.25 Smoothing time (in seconds) used for the axis acceleration and deceleration ramps The change will influence the tag <Axis name>. Config.DynamicDefaults.Jerk . For the effectiveness of the change, refer to the description of this tag. Done OUTPUT BOOL FALSE TRUE The changed values have been written to the technology data block. The description of the tags will show when the change becomes effective. Error OUTPUT BOOL FALSE TRUE An error occurred during execution of the command. The cause of the error can be found in parameters "ErrorID" and "ErrorInfo". ErrorID OUTPUT WORD 16#0000 Error ID (Page 4481) for parameter "Error" ErrorInfo OUTPUT WORD 16#0000 Error info ID (Page 4481) for parameter "ErrorID" Note At the input parameters "RampUpTime", "RampDownTime", "EmergencyRampTime" and "JerkTime", values can be entered which exceed the admissible limits of the resulting parameters: "Acceleration", "Deceleration", "Emergency stop deceleration" and "Jerk". Please note the equations and limits in "Axis technology object" -> "Configuring the technology object" -> "Dynamics" and ensure that the values you input are within the valid range. See also Overview of the Motion Control statements (Page 4400) S7-1200 Motion Control V4 (Page 2820) ErrorIDs and ErrorInfos (Page 4481) Tag of the axis technology object V1...3 (Page 4494) MC_Power: Enable, disable axis V1...3 (Page 2853) MC_Reset: Acknowledge fault V1...3 (Page 2857) MC_Home: Home axes, set reference point V1...3 (Page 2859) MC_Halt: Halt axes V1...3 (Page 2862) WinCC Basic V13.0 System Manual, 02/2014 2881 Programming the PLC 9.7 References MC_MoveAbsolute: Absolute positioning of axes V1...3 (Page 2865) MC_MoveRelative: Relative positioning of axes V1...3 (Page 2868) MC_MoveVelocity: Move axes at preset rotational speed V1...3 (Page 2871) MC_MoveJog: Move axes in jog mode V1...3 (Page 2875) MC_CommandTable: Run axis commands as motion sequence V2...3 (Page 2878) 9.7.4.2 High-speed counters CTRL_HSC: Control high-speed counters Parameter Parameter Declaration Data type Memory area Description EN INPUT BOOL I, Q, M, D, L, T, C Enable input ENO OUTPUT BOOL I, Q, M, D, L Enable output HSC INPUT HW_HSC I, Q, M or constant Hardware address of the high-speed counter (HW-ID) DIR INPUT BOOL I, Q, M, D, L or constant Enables the new count direction (see NEW_DIR) CV INPUT BOOL I, Q, M, D, L or constant Enables the new count value (see NEW_CV) RV INPUT BOOL I, Q, M, D, L or constant Enables the new reference value (see NEW_RV) PERIOD INPUT BOOL I, Q, M, D, L or constant Enables the new period of a frequency measurement (see NEW_PERIOD) NEW_DIR INPUT INT I, Q, M, D, L or constant Count direction loaded when DIR = TRUE. NEW_CV INPUT DINT I, Q, M, D, L or constant Count value loaded when CV = TRUE. NEW_RV INPUT DINT I, Q, M, D, L or constant Reference value loaded when RV = TRUE. INT I, Q, M, D, L or constant Period of the frequency measurement loaded when PERIOD = TRUE. NEW_PERIOD INPUT 2882 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameter Declaration Data type Memory area Description BUSY OUTPUT BOOL I, Q, M, D, L Processing status STATUS OUTPUT WORD I, Q, M, D, L Status of the operation Description With the "Control high-speed counter" instruction, you can make parameter settings and control the high-speed counters supported by the CPU by loading new values into the counter. Execution of the instruction requires that the high-speed counter to be controlled is enabled. You cannot execute multiple "Control high-speed counter" instructions simultaneously in the program for a given high-speed counter. You can load the following parameter values into a high-speed counter using the "Control highspeed counter" instruction: Count direction (NEW_DIR): The count direction defines whether a high-speed counter counts up or down. The count direction is defined by the following values at the NEW_DIR input: 1 = up, -1 = down. A change to the count direction with the "Control high-speed counter" instruction is only possible when direction control is set in the parameters by the program. The count direction specified at the NEW_DIR input is loaded into a high-speed counter when the bit at the DIR input is set. Count value (NEW_CV): The count value is the initial value at which a high-speed counter starts counting. The count value can be in the range -2147483648 to 2147483647. The count value specified at the NEW_CV input is loaded into a high-speed counter when the bit at the CV input is set. Reference value (NEW_RV): You can compare the reference value with the current counter value to trigger an alarm. Similar to the counter value, the reference value can be in the range -2147483648 to 2147483647. The reference value specified at the NEW_RV input is loaded into a high-speed counter when the bit at the RV input is set. Period of the frequency measurement (NEW_PERIOD): The period of the frequency measurement is specified by the following values at the NEW_PERIOD input: 10 = 0.01s, 100 = 0.1s, 1000 = 1s. The time period can be updated if the "Measure frequency" function for the specified highspeed counter is configured. The time period specified at the NEW_PERIOD input is loaded into a high-speed counter when the bit at the PERIOD input is set. The "Control high-speed counter" instruction is only executed if the signal state at the EN input is "1". As long as the operation is executing, the bit at the BUSY output is set. Once the operation has executed completely, the bit at the BUSY output is reset. The ENO enable output is set only when the EN enable input has signal state "1" and no errors occur during execution of the operation. When inserting the "Control high-speed counter" instruction, an instance data block is created in which the operation data is saved. WinCC Basic V13.0 System Manual, 02/2014 2883 Programming the PLC 9.7 References Parameter STATUS At the STATUS output, you can query whether errors occurred during execution of the "Control high-speed counter" instruction. The following table shows the meaning of the values output at the STATUS output: 2884 Error code (hexadecimal) Description 0 No error 80A1 Hardware identifier of the high-speed counter invalid 80B1 Count direction (NEW_DIR) invalid 80B2 Count value (NEW_CV) invalid 80B3 Reference value (NEW_RV) invalid 80B4 Period of the frequency measurement (NEW_PERIOD) invalid 80C0 Multiple access to the high-speed counter 80D0 The high-speed counter (HSC) is not enabled in the CPU hardware configuration. WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References 9.7.4.3 PID Control PID_Compact New features of PID_Compact PID_Compact V2.2 Use with S7-1200 As of PID_Compact V2.2, the instruction with V2 functionality can also be used on S7-1200 with firmware version 4.0 or higher. PID_Compact V2.0 Reaction to error The reaction to error has been completely overhauled. PID_Compact now reacts in a more fault-tolerant manner in the default setting. This reaction is set when copying PID_Compact V1.X from an S7-1200 CPU to an S7-1500 CPU. NOTICE Your system may be damaged. If you use the default setting, PID_Compact remains in automatic mode when the process value limits are exceeded. This may damage your system. It is essential to configure how your controlled system reacts in the event of an error to protect your system from damage. The Error parameter indicates if an error is pending. When the error is no longer pending, Error = FALSE. The ErrorBits parameter shows which errors have occurred. Use ErrorAck to acknowledge the errors and warnings without restarting the controller or clearing the integral action. Switching operating modes no longer clears errors that are no longer pending. You can configure the reaction to error with SetSubstituteOutput and ActivateRecoverMode. Substitute output value You can configure a substitute output value that is to be output if an error occurs. Switching the operating mode You specify the operating mode at the Mode in/out parameter and use a rising edge at ModeActivate to start the operating mode. The sRet.i_Mode tag has been omitted. Multi-instance capability You can call up PID_Compact as multi-instance DB. No technology object is created in this case and no parameter assignment interface or commissioning interface is available. You must assign parameters for PID_Compact directly in the multi-instance DB and commission it via a watch table. Startup characteristics The operating mode specified at the Mode parameter is also started on a falling edge at Reset and during a CPU cold restart, if RunModeByStartup = TRUE. WinCC Basic V13.0 System Manual, 02/2014 2885 Programming the PLC 9.7 References ENO characteristics ENO is set depending on the operating mode. If State = 0, then ENO = FALSE. If State 0, then ENO = TRUE. Setpoint value specification during tuning You configure the permitted fluctuation of the setpoint during tuning at the CancelTuningLevel tag. Value range for output value limits The value 0.0 no longer has to fall within the output value limits. Pre-assigning the integral action Using the tags IntegralResetMode and OverwriteInitialOutputValue, you can determine the pre-assignment of the integral action when switching from "Inactive" operating mode to "Automatic mode". Switching a disturbance variable on You can switch a disturbance variable on at the Disturbance parameter. Default value of PID parameters The following default settings have been changed: - Proportional action weighting (PWeighting) from 0.0 to 1.0 - Derivative action weighting (DWeighting) from 0.0 to 1.0 - Coefficient for derivative delay (TdFiltRatio) from 0.0 to 0.2 Renaming tags The static tags have been given new names that are compatible with PID_3Step. PID_Compact V1.2 Manual mode on CPU startup If ManualEnable = TRUE when the CPU starts, PID_Compact starts in manual mode. A rising edge at ManualEnable is not necessary. Pretuning If the CPU is switched off during pretuning, pretuning starts again when the CPU is switched back on. PID_Compact V1.1 Manual mode on CPU startup When the CPU starts up, PID_Compact only switches to manual mode with a rising edge at ManualEnable. Without rising edge, PID_Compact starts in the last operating mode in which ManualEnable was FALSE. Reaction to reset A rising edge at Reset resets the errors and warnings and clears the integral action. A falling edge at Reset triggers a switchover to the most recently active operating mode. Default of process value high limit The default value of r_Pv_Hlm has been changed to 120.0. 2886 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Monitoring the sampling time - An error is no longer output when the current sampling time is >= 1.5 x current mean value or when the current sampling time is <= 0.5 x current mean value. The sampling time may deviate much more in automatic mode. - PID_Compact is compatible with FW, V2.0 or higher. Access to tags The following tags can now be used in the user program. - i_Event_SUT - i_Event_TIR - r_Ctrl_Ioutv Troubleshooting PID_Compact now outputs the correct pulses when the shortest ON time is not equal to the shortest OFF time. Compatibility with CPU and FW The following table shows which version of PID_Compact can be used on which CPU. CPU FW PID_Compact S7-1200 V4.x V2.2 V1.2 S7-1200 V3.X V1.2 S7-1200 V2.X S7-1200 V1.X V1.0 S7-1500 V1.1 V2.2 V1.1 V1.2 V1.1 V2.1 V2.0 S7-1500 V1.0 V2.0 PID_Compact V2 Description of PID_Compact V2 Description The PID_Compact instruction provides a PID controller with integrated tuning for actuators with proportional action. The following operating modes are possible: WinCC Basic V13.0 System Manual, 02/2014 2887 Programming the PLC 9.7 References Inactive Pretuning Fine tuning Automatic mode Manual mode Substitute output value with error monitoring For a more detailed description of the operating modes, see the State parameter. PID algorithm PID_Compact is a PIDT1 controller with anti-windup and weighting of the proportional and derivative actions. The PID algorithm operates according to the following equation: 1 y = Kp [ (b * w - x) + T * s (w - x) + I 2888 TD * s a * TD * s + 1 (c * w - x) Symbol Description y Output value of the PID algorithm Kp Proportional gain s Laplace operator b Proportional action weighting w Setpoint x Process value ] TI Integral action time TD Derivative action time a Derivative delay coefficient (derivative delay T1 = a x TD) c Derivative action weighting WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Block diagram of PID_Compact ,QSXWB3(5 &53B,1 ,QSXW3HU2Q 6FDOH ,QSXW:DUQLQJB/ ,QSXW 6HWSRLQW ,QSXW:DUQLQJB+ 39B$/50 3,'7 $QWL:LQGXS /LPLW ,QYHUW&RQWURO ,19 2XWSXW 'LVWXUEDQFH 6WDWH &53B287 /LPLW 0DQXDO9DOXH 2XWSXWB3(5 3:0 2XWSXWB3:0 Block diagram of PIDT1 with anti-windup 6HWSRLQW Z E $QWL:LQGXS /,0,7 , .3 \ F 6FDOHG,QSXW [ WinCC Basic V13.0 System Manual, 02/2014 '7 2889 Programming the PLC 9.7 References Call PID_Compact is called in the constant time scale of a cycle interrupt OB. If you call PID_Compact as a multi-instance DB, no technology object is created. No parameter assignment interface or commissioning interface is available. You must assign parameters for PID_Compact directly in the multi-instance DB and commission it via a watch table. Download to device The actual values of retentive variables are only updated when you download PID_Compact completely. Downloading technology objects to device (Page 4223) Startup When the CPU starts up, PID_Compact starts in the operating mode that is saved in the Mode in/out parameter. To switch to "Inactive" operating mode during startup, set RunModeByStartup = FALSE. Reaction to error In automatic mode and during commissioning, the reaction to error depends on the SetSubstituteOutput and ActivateRecoverMode variables. In manual mode, the reaction is independent of SetSubstituteOutput and ActivateRecoverMode. If ActivateRecoverMode = TRUE, the reaction additionally depends on the error that occurred. SetSubstituteOu tput ActivateReco verMode Configuration editor > output value > Set Output to Reaction Not relevant FALSE Zero (inactive) Switch to "Inactive" mode (State = 0) The value 0.0 0 is transferred to the actuator. FALSE TRUE Current output value while error is pending Switch to "Substitute output value with error monitoring" mode (State = 5) The current output value is transferred to the actuator while the error is pending. TRUE TRUE Substitute output value while error is pending Switch to "Substitute output value with error monitoring" mode (State = 5) The value at SubstituteOutput is transferred to the actuator while the error is pending. In manual mode, PID_Compact uses ManualValue as output value, unless ManualValue is invalid. If ManualValue is invalid, SubstituteOutput is used. If ManualValue and SubstituteOutput are invalid, Config.OutputLowerLimit is used. The Error parameter indicates if an error is pending. When the error is no longer pending, Error = FALSE. The ErrorBits parameter shows which errors have occurred. ErrorBits is reset by a rising edge at Reset or ErrorAck. 2890 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References PID_Compact V2 mode of operation Monitoring process value limits You specify the high limit and low limit of the process value in the Config.InputUpperLimit and Config.InputLowerLimit tags. If the process value is outside these limits, an error occurs (ErrorBits = 0001h). You specify a high and low warning limit of the process value in the Config.InputUpperWarning and Config.InputLowerWarning tags. If the process value is outside these warning limits, a warning occurs (Warning = 0040h), and the InputWarning_H or InputWarning_L output parameter changes to TRUE. Limiting the setpoint You specify a high limit and low limit of the setpoint in the Config.SetpointUpperLimit and Config.SetpointLowerLimit tags. PID_Compact automatically limits the setpoint to the process value limits. You can limit the setpoint to a smaller range. PID_Compact checks whether this range falls within the process value limits. If the setpoint is outside these limits, the high or low limit is used as the setpoint, and output parameter SetpointLimit_H or SetpointLimit_L is set to TRUE. The setpoint is limited in all operating modes. Limiting the output value You specify a high limit and low limit of the output value in the Config.OutputUpperLimit and Config.OutputLowerLimit tags. Output, ManualValue, and SubstituteOutput are limited to these values. The output value limits must match the control logic. The valid output value limit values depend on the Output used. Output -100.0 to 100.0% Output_PER -100.0 to 100.0% Output_PWM 0.0 to 100.0% Rule: OutputUpperLimit > OutputLowerLimit Substitute output value In the event of an error, PID_Compact can output a substitute output value that you define at the tag SubstituteOutput. The substitute output value must be within the output value limits. Monitoring signal validity The values of the following parameters are monitored for validity when used: Setpoint Input WinCC Basic V13.0 System Manual, 02/2014 2891 Programming the PLC 9.7 References Input_PER Disturbance ManualValue SubstituteOutput Output Output_PER Output_PWM Monitoring of the sampling time PID_Compact Ideally, the sampling time is equivalent to the cycle time of the calling OB. The PID_Compact instruction measures the time interval between two calls. This is the current sampling time. On every switchover of operating mode and during the initial startup, the mean value is formed from the first 10 sampling times. Too great a difference between the current sampling time and this mean value triggers an error (Error = 0800h). The error occurs during tuning if: New mean value >= 1.1 x old mean value New mean value <= 0.9 x old mean value The error occurs in automatic mode if: New mean value >= 1.5 x old mean value New mean value <= 0.5 x old mean value If you deactivate the sampling time monitoring (CycleTime.EnMonitoring = FALSE), you can also call PID_Compact in OB1. You must then accept a lower control quality due to the deviating sampling time. Sampling time of the PID algorithm The controlled system needs a certain amount of time to respond to changes in the output value. It is therefore not advisable to calculate the output value in every cycle. The sampling time of the PID algorithm represents the time between two calculations of the output value. It is calculated during tuning and rounded to a multiple of the cycle time. All other functions of PID_Compact are executed at every call. If you use Output_PWM, the accuracy of the output signal is determined by the ratio of the PID algorithm sampling time to the cycle time of the OB. The cycle time should be at least 10 times the PID algorithm sampling time. Control logic An increase of the output value is generally intended to cause an increase in the process value. This is referred to as a normal control logic. For cooling and discharge control systems, it may be necessary to invert the control logic. PID_Compact does not work with negative proportional gain. If InvertControl = TRUE, an increasing control deviation causes a reduction in the output value. The control logic is also taken into account during pretuning and fine tuning. 2892 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Input parameters of PID_Compact V2 Table 9-79 Parameter Data type Default Description Setpoint REAL 0.0 Setpoint of the PID controller in automatic mode Input REAL 0.0 A tag of the user program is used as the source of the process value. If you are using the Input parameter, then Config.InputPerOn = FALSE must be set. Input_PER INT 0 An analog input is used as the source of the process value. If you are using the Input_PER parameter, then Config.InputPerOn = TRUE must be set. Disturbance REAL 0.0 Disturbance variable or precontrol value ManualEnable BOOL FALSE A FALSE -> TRUE edge activates "manual mode", while State = 4, Mode remain unchanged. As long as ManualEnable = TRUE, you cannot change the operating mode via a rising edge at ModeActivate or use the commissioning dialog. A TRUE -> FALSE edge activates the operating mode that is specified by Mode. We recommend that you change the operating mode using ModeActivate only. ManualValue REAL 0.0 Manual value This value is used as the output value in manual mode. Values from Config.OutputLowerLimit to Config.OutputUpperLimit are permitted. ErrorAck BOOL FALSE FALSE -> TRUE edge ErrorBits and Warning are reset. Reset BOOL FALSE Restarts the controller. FALSE -> TRUE edge - Switch to "Inactive" mode - ErrorBits and Warnings are reset. - Integral action is cleared (PID parameters are retained) As long as Reset = TRUE, PID_Compact remains in "Inactive" mode (State = 0). TRUE -> FALSE edge PID_Compact switches to the operating mode that is saved in the Mode parameter. ModeActivate WinCC Basic V13.0 System Manual, 02/2014 BOOL FALSE FALSE -> TRUE edge PID_Compact switches to the operating mode that is saved in the Mode parameter. 2893 Programming the PLC 9.7 References Output parameters of PID_Compact V2 Table 9-80 Parameter Data type Default Description ScaledInput REAL 0.0 Scaled process value The "Output", "Output_PER", and "Output_PWM" outputs can be used concurrently. Output REAL 0.0 Output value in REAL format Output_PER INT 0 Analog output value Output_PWM BOOL FALSE Pulse-width-modulated output value The output value is formed by by variable On and Off times. SetpointLimit_H BOOL FALSE If SetpointLimit_H = TRUE, the absolute setpoint high limit is reached (Setpoint Config.SetpointUpperLimit). SetpointLimit_L BOOL FALSE InputWarning_H BOOL FALSE If InputWarning_H = TRUE, the process value has reached or exceeded the warning high limit. InputWarning_L BOOL FALSE If InputWarning_L = TRUE, the process value has reached or fallen below the warning low limit. State INT 0 The State parameter (Page 2904) shows the current operating mode of the PID controller. You can change the operating mode using the input parameter Mode and a rising edge at ModeActivate. The setpoint is limited to Config.SetpointUpperLimit . If SetpointLimit_L = TRUE, the absolute setpoint low limit has been reached (Setpoint Config.SetpointLowerLimit). The setpoint is limited to Config.SetpointLowerLimit . State = 0: Inactive State = 1: Pretuning State = 2: Fine tuning State = 3: Automatic mode State = 4: Manual mode State = 5: Substitute output value with error monitoring Error BOOL FALSE If Error = TRUE, at least one error message is pending in this cycle. ErrorBits DWORD DW#16#0 The ErrorBits parameter (Page 2908) shows which error messages are pending. ErrorBits is retentive and is reset upon a rising edge at Reset or ErrorAck. 2894 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References In/out parameters of PID_Compact V2 Table 9-81 Parameter Data type Default Description Mode INT 4 At Mode, specify the operating mode to which PID_Compact is to switch. Options are: Mode = 0: Inactive Mode = 1: Pretuning Mode = 2: Fine tuning Mode = 3: Automatic mode Mode = 4: Manual mode The operating mode is activated by: Rising edge at ModeActivate Falling edge at Reset Falling edge at ManualEnable Cold restart of CPU if RunModeByStartup = TRUE Mode is retentive. A detailed description of the operating modes can be found in Parameters State and Mode V2 (Page 2904). See also Parameters State and Mode V2 (Page 2904) WinCC Basic V13.0 System Manual, 02/2014 2895 Programming the PLC 9.7 References Static tags of PID_Compact V2 You must not change variables that are not listed. These are used for internal purposes only. Table 9-82 Tag Data type Default Description IntegralResetMode INT 1 The tag IntegralResetMode determines how PIDCtrl.IntegralSum is pre-assigned when switching from "Inactive" operating mode to "Automatic mode". This setting only works for one cycle. Options are: IntegralResetMode = 0: Smoothing The value of IntegralSum is pre-assigned so that the switchover is bumpless. IntegralResetMode = 1: Deleting The value of IntegralSum is deleted. Any control deviation will cause a jump change of the output value. IntegralResetMode = 2: Holding The value of IntegralSum is not changed. You can define a new value using the user program. IntegralResetMode = 3: Pre-assigning The value of IntegralSum is automatically preassigned so that Output is calculated with reference to the value OverwriteInitialOutputValue. This setting is useful, for example, for an override controller. OverwriteInitialOutputValue REAL 0.0 If IntegralResetMode = 3, the value of IntegralSum is automatically pre-assigned so that Output = OverwriteInitialOutputValue in the next cycle. RunModeByStartup BOOL TRUE Activate operating mode at Mode parameter after CPU restart If RunModeByStartup = TRUE, PID_Compact starts in the operating mode saved in the Mode parameter after CPU startup. If RunModeByStartup = FALSE, PID_Compact remains in "Inactive" mode after CPU startup. LoadBackUp BOOL FALSE If LoadBackUp = TRUE, the last set of PID parameters is reloaded. The set was saved prior to the last tuning. LoadBackUp is automatically set back to FALSE. PhysicalUnit INT 0 Unit of measurement of the process value and setpoint, e.g., C, or F. PhysicalQuantity INT 0 Physical quantity of the process value and setpoint, e.g., temperature. ActivateRecoverMode BOOL TRUE The Tag ActivateRecoverMode V2 (Page 2910) determines the reaction to error. Warning DWORD 0 Tag Warning V2 (Page 2912) shows the warnings since Reset = TRUE or ErrorAck =TRUE. Warning is retentive. Progress REAL 0.0 Progress of tuning as a percentage (0.0 - 100.0) 2896 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Tag Data type Default Description CurrentSetpoint REAL 0.0 CurrentSetpoint always displays the current setpoint. This value is frozen during tuning. CancelTuningLevel REAL 10.0 Permissible fluctuation of setpoint during tuning. Tuning is not canceled until: Setpoint > CurrentSetpoint + CancelTuningLevel or Setpoint < CurrentSetpoint - CancelTuningLevel SubstituteOutput REAL 0.0 Substitute output value When the following conditions are met, the substitute output value is used: An error has occurred in automatic mode. SetSubstituteOutput = TRUE ActivateRecoverMode = TRUE SetSubstituteOutput BOOL TRUE If SetSubstituteOutput = TRUE and ActivateRecoverMode = TRUE, the substitute output value configured is output as long as an error is pending. If SetSubstituteOutput = FALSE and ActivateRecoverMode = TRUE, the actuator remains at the current output value as long as an error is pending. If ActivateRecoverMode = FALSE, SetSubstituteOutput is not effective. If SubstituteOutput is invalid (ErrorBits = 20000h), the substitute output value cannot be output. Config.InputPerOn BOOL TRUE If InputPerOn = TRUE, the Input_PER parameter is used. If InputPerOn = FALSE, the Input parameter is used. Config.InvertControl BOOL FALSE Invert control logic If InvertControl = TRUE, an increasing control deviation causes a reduction in the output value. Config.InputUpperLimit REAL 120.0 High limit of the process value Input and Input_PER are monitored to ensure adherence to this limit. At the I/O input, the process value can be a maximum of 18% higher than the standard range (overrange). This pre-assignment ensures that an error is no longer signaled due to a violation of the "Process value high limit". Only a wire-break and a short-circuit are recognized and PID_Compact reacts according to the configured reaction to error. InputUpperLimit > InputLowerLimit Config.InputLowerLimit REAL 0.0 Low limit of the process value Input and Input_PER are monitored to ensure adherence to this limit. InputLowerLimit < InputUpperLimit WinCC Basic V13.0 System Manual, 02/2014 2897 Programming the PLC 9.7 References Tag Data type Default Config.InputUpperWarning REAL 3.402822e+38 Warning high limit of the process value Description If you set InputUpperWarning outside the process value limits, the configured absolute process value high limit is used as the warning high limit. If you configure InputUpperWarning within the process value limits, this value is used as the warning high limit. InputUpperWarning > InputLowerWarning InputUpperWarning InputUpperLimit Config.InputLowerWarning REAL -3.402822e +38 Warning low limit of the process value If you set InputLowerWarning outside the process value limits, the configured absolute process value low limit is used as the warning low limit. If you configure InputLowerWarning within the process value limits, this value is used as the warning low limit. InputLowerWarning < InputUpperWarning InputLowerWarning InputLowerLimit Config.OutputUpperLimit REAL 100.0 High limit of output value For details, see OutputLowerLimit OutputUpperLimit > OutputLowerLimit Config.OutputLowerLimit REAL 0.0 Low limit of output value For Output and Output_PER, the range of values from -100.0 to +100.0, including zero, is valid. At -100.0, Output_PER = -27648; at +100.0, Output_PER = 27648. For Output_PWM, the value range 0.0 to +100.0 applies. The output value limits must match the control logic. OutputLowerLimit < OutputUpperLimit Config.SetpointUpperLimit REAL 3.402822e+38 High limit of setpoint If you configure SetpointUpperLimit outside the process value limits, the configured absolute process value high limit is used as the setpoint high limit. If you configure SetpointUpperLimit within the process value limits, this value is used as the setpoint high limit. Config.SetpointLowerLimit REAL -3.402822e +38 Low limit of the setpoint If you set SetpointLowerLimit outside the process value limits, the configured process value absolute low limit is used as the setpoint low limit. If you set SetpointLowerLimit within the process value limits, this value is used as the setpoint low limit. Config.MinimumOnTime REAL 0.0 The minimum ON time of the pulse width modulation in seconds is rounded to MinimumOnTime = nxCycleTime.Value Config.MinimumOffTime REAL 0.0 The minimum OFF time of the pulse width modulation in seconds is rounded to MinimumOffTime = nxCycleTime.Value 2898 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Tag Data type Default Description Config.InputScaling.UpperPointIn REAL 27648.0 Scaling Input_PER high Input_PER is converted to percent based on the two value pairs UpperPointOut, UpperPointIn and LowerPointOut, LowerPointIn. Config.InputScaling.LowerPointIn REAL 0.0 Scaling Input_PER low Input_PER is converted to percent based on the two value pairs UpperPointOut, UpperPointIn and LowerPointOut, LowerPointIn. Config.InputScaling.UpperPointOut REAL 100.0 Scaled high process value Input_PER is converted to percent based on the two value pairs UpperPointOut, UpperPointIn and LowerPointOut, LowerPointIn. Config.InputScaling.LowerPointOut REAL 0.0 Scaled low process value Input_PER is converted to percent based on the two value pairs UpperPointOut, UpperPointIn and LowerPointOut, LowerPointIn. CycleTime.StartEstimation BOOL TRUE If CycleTime.StartEstimation = TRUE, the automatic determination of the cycle time is started. CycleTime.StartEstimation = FALSE once measurement is complete. CycleTime.EnEstimation BOOL TRUE If CycleTime.EnEstimation = TRUE, the PID_Compact sampling time is calculated. If CycleTime.EnEstimation = FALSE, the PID_Compact sampling time is not calculated and you need to correct the configuration of CycleTime.Value manually. CycleTime.EnMonitoring BOOL TRUE If CycleTime.EnMonitoring = FALSE, the PID_Compact sampling time is not monitored. If it is not possible to execute PID_Compact within the sampling time, no error (ErrorBits=0800h) is output and PID_Compact does not switch to "Inactive" mode. CycleTime.Value REAL 0.1 PID_Compact sampling time in seconds CycleTime.Value is determined automatically and is usually equivalent to the cycle time of the calling OB. CtrlParamsBackUp.Gain REAL 1.0 Saved proportional gain You can reload values from the CtrlParamsBackUp structure with LoadBackUp = TRUE. CtrlParamsBackUp.Ti REAL 20.0 Saved integral action time [s] CtrlParamsBackUp.Td REAL 0.0 Saved derivative action time [s] CtrlParamsBackUp.TdFiltRatio REAL 0.2 Saved derivative delay coefficient CtrlParamsBackUp.PWeighting REAL 1.0 Saved proportional action weighting factor CtrlParamsBackUp.DWeighting REAL 1.0 Saved derivative action weighting factor CtrlParamsBackUp.Cycle REAL 1.0 Saved sampling time of PID algorithm WinCC Basic V13.0 System Manual, 02/2014 2899 Programming the PLC 9.7 References Tag Data type PIDSelfTune.SUT.CalculateParams BOOL Default Description FALSE The properties of the controlled system are saved during tuning. If SUT.CalculateParams = TRUE, the parameters for pretuning are recalculated according to these properties. This enables you to change the parameter calculation method without having to repeat controller tuning. SUT.CalculateParams is set to FALSE after the calculation. PIDSelfTune.SUT.TuneRule INT 0 Methods used to calculate parameters during pretuning: SUT.TuneRule = 0: PID according to Chien, Hrones and Reswick SUT.TuneRule = 1: PI according to Chien, Hrones and Reswick PIDSelfTune.SUT.State INT 0 The SUT.State tag indicates the current phase of pretuning: State = 0: Initialize pretuning State = 100: Calculate standard deviation State = 200: Determine point of inflection State = 9900: Pretuning successful State = 1: Pretuning not successful PIDSelfTune.TIR.RunIn BOOL FALSE With the RunIn tag, you can specify that fine tuning can also be performed without pretuning. RunIn = FALSE Pretuning is started when fine tuning is started from inactive or manual mode. If the requirements for pretuning are not met, PID_Compact reacts as when RunIn = TRUE. If fine tuning is started from automatic mode, the system uses the existing PID parameters to control to the setpoint. Only then will fine tuning start. If pretuning is not possible, PID_Compact switches to the mode from which tuning was started. RunIn = TRUE The pretuning is skipped. PID_Compact tries to reach the setpoint with minimum or maximum output value. This can produce increased overshoot. Fine tuning then starts automatically. RunIn is set to FALSE after fine tuning. PIDSelfTune.TIR.CalculateParams BOOL FALSE The properties of the controlled system are saved during tuning. If TIR.CalculateParams = TRUE, the parameters for fine tuning are recalculated according to these properties. This enables you to change the parameter calculation method without having to repeat controller tuning. TIR.CalculateParams is set to FALSE after the calculation. 2900 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Tag Data type Default Description PIDSelfTune.TIR.TuneRule INT 0 Methods used to calculate parameters during fine tuning: TIR.TuneRule = 0: PID automatic TIR.TuneRule = 1: PID rapid TIR.TuneRule = 2: PID slow TIR.TuneRule = 3: Ziegler-Nichols PID TIR.TuneRule = 4: Ziegler-Nichols PI TIR.TuneRule = 5: Ziegler-Nichols P PIDSelfTune.TIR.State INT 0 The TIR.State tag indicates the current phase of fine tuning: State = -100 Fine tuning is not possible. Pretuning will be performed first. State = 0: Initialize fine tuning State = 200: Calculate standard deviation State = 300: Attempt to reach the setpoint State = 400: Attempt to reach the setpoint with existing PID parameters (if pretuning was successful) State = 500: Determine oscillation and calculate parameters State = 9900: Fine tuning successful State = 1: Fine tuning not successful PIDCtrl.IntegralSum REAL 0.0 Current integral action Retain.CtrlParams.Gain REAL 1.0 Active proportional gain To invert the control logic, use the Config.InvertControl tag. Negative values at Gain also invert the control logic. We recommend you use only InvertControl to set the control logic. The control logic is also inverted if InvertControl = TRUE and Gain < 0.0. Gain is retentive. Retain.CtrlParams.Ti REAL 20.0 CtrlParams.Ti > 0.0: Active integral action time CtrlParams.Ti = 0.0: Integral action is deactivated Ti is retentive. Retain.CtrlParams.Td REAL 0.0 CtrlParams.Td > 0.0: Active derivative action time CtrlParams.Td = 0.0: Derivative action is deactivated Td is retentive. WinCC Basic V13.0 System Manual, 02/2014 2901 Programming the PLC 9.7 References Tag Data type Default Description Retain.CtrlParams.TdFiltRatio REAL 0.2 Active derivative delay coefficient The derivative delay coefficient delays the effect of the derivative action. Derivative delay = derivative action time x derivative delay coefficient 0.0: Derivative action is effective for one cycle only and therefore almost not effective. 0.5: This value has proved useful in practice for controlled systems with one dominant time constant. > 1.0: The greater the coefficient, the longer the effect of the derivative action is delayed. TdFiltRatio is retentive. Retain.CtrlParams.PWeighting REAL 1.0 Active proportional action weighting The proportional action may weaken with changes to the setpoint. Values from 0.0 to 1.0 are applicable. 1.0: Proportional action for setpoint change is fully effective 0.0: Proportional action for setpoint change is not effective The proportional action is always fully effective when the process value is changed. PWeighting is retentive. Retain.CtrlParams.DWeighting REAL 1.0 Active derivative action weighting The derivative action may weaken with changes to the setpoint. Values from 0.0 to 1.0 are applicable. 1.0: Derivative action is fully effective upon setpoint change 0.0: Derivative action is not effective upon setpoint change The derivative action is always fully effective when the process value is changed. DWeighting is retentive. Retain.CtrlParams.Cycle REAL 1.0 Active sampling time of the PID algorithm CtrlParams.Cycle is calculated during tuning and rounded to an integer multiple of CycleTime.Value. Cycle is retentive. Note Change the tags listed in this table in "Inactive" mode to prevent malfunction of the PID controller. 2902 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References See also Tag ActivateRecoverMode V2 (Page 2910) Tag Warning V2 (Page 2912) Downloading technology objects to device (Page 4223) Changing the PID_Compact V2 interface The following table shows what has changed in the PID_Compact instruction interface. PID_Compact V1 PID_Compact V2 Change Input_PER Input_PER Data type from Word to Int Disturbance New ErrorAck New ModeActivate New Output_PER Output_PER Data type from Word to Int Error ErrorBits Renamed Error New Mode New RunModeByStartup Function sb_RunModeByStartup IntegralResetMode OverwriteInitialOutputValue New SetSubstituteOutput New CancelTuningLevel New SubstituteOutput New The following table shows which variables have been renamed. WinCC Basic V13.0 System Manual, 02/2014 PID_Compact V1.x PID_Compact V2 sb_GetCycleTime CycleTime.StartEstimation sb_EnCyclEstimation CycleTime.EnEstimation sb_EnCyclMonitoring CycleTime.EnMonitoring sb_RunModeByStartup RunModeByStartup si_Unit PhysicalUnit si_Type PhysicalQuantity sd_Warning Warning sBackUp.r_Gain CtrlParamsBackUp.Gain sBackUp.r_Ti CtrlParamsBackUp.Ti sBackUp.r_Td CtrlParamsBackUp.Td sBackUp.r_A CtrlParamsBackUp.TdFiltRatio sBackUp.r_B CtrlParamsBackUp.PWeighting sBackUp.r_C CtrlParamsBackUp.DWeighting sBackUp.r_Cycle CtrlParamsBackUp.Cycle 2903 Programming the PLC 9.7 References PID_Compact V1.x PID_Compact V2 sPid_Calc.r_Cycle CycleTime.Value sPid_Calc.b_RunIn PIDSelfTune.TIR.RunIn sPid_Calc.b_CalcParamSUT PIDSelfTune.SUT.CalculateParams sPid_Calc.b_CalcParamTIR PIDSelfTune.TIR.CalculateParams sPid_Calc.i_CtrlTypeSUT PIDSelfTune.SUT.TuneRule sPid_Calc.i_CtrlTypeTIR PIDSelfTune.TIR.TuneRule sPid_Calc.r_Progress Progress sPid_Cmpt.r_Sp_Hlm Config.SetpointUpperLimit sPid_Cmpt.r_Sp_Llm Config.SetpointLowerLimit sPid_Cmpt.r_Pv_Norm_IN_1 Config.InputScaling.LowerPointIn sPid_Cmpt.r_Pv_Norm_IN_2 Config.InputScaling.UpperPointIn sPid_Cmpt.r_Pv_Norm_OUT_1 Config.InputScaling.LowerPointOut sPid_Cmpt.r_Pv_Norm_OUT_2 Config.InputScaling.UpperPointOut sPid_Cmpt.r_Lmn_Hlm Config.OutputUpperLimit sPid_Cmpt.r_Lmn_Llm Config.OutputLowerLimit sPid_Cmpt.b_Input_PER_On Config.InputPerOn sPid_Cmpt.b_LoadBackUp LoadBackUp sPid_Cmpt.b_InvCtrl Config.InvertControl sPid_Cmpt.r_Lmn_Pwm_PPTm Config.MinimumOnTime sPid_Cmpt.r_Lmn_Pwm_PBTm Config.MinimumOffTime sPid_Cmpt.r_Pv_Hlm Config.InputUpperLimit sPid_Cmpt.r_Pv_Llm Config.InputLowerLimit sPid_Cmpt.r_Pv_HWrn Config.InputUpperWarning sPid_Cmpt.r_Pv_LWrn Config.InputLowerWarning sParamCalc.i_Event_SUT PIDSelfTune.SUT.State sParamCalc.i_Event_TIR PIDSelfTune.TIR.State sRet.i_Mode sRet.i_Mode has been omitted. The operating mode is changed using Mode and ModeActivate. sRet.r_Ctrl_Gain Retain.CtrlParams.Gain sRet.r_Ctrl_Ti Retain.CtrlParams.Ti sRet.r_Ctrl_Td Retain.CtrlParams.Td sRet.r_Ctrl_A Retain.CtrlParams.TdFiltRatio sRet.r_Ctrl_B Retain.CtrlParams.PWeighting sRet.r_Ctrl_C Retain.CtrlParams.DWeighting sRet.r_Ctrl_Cycle Retain.CtrlParams.Cycle Parameters State and Mode V2 Correlation of the parameters The State parameter shows the current operating mode of the PID controller. You cannot change the State parameter. 2904 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References With a rising edge at ModeActivate, PID_Compact switches to the operating mode saved in the Mode in-out parameter. When the CPU is switched on or switches from Stop to RUN mode, PID_Compact starts in the operating mode that is saved in the Mode parameter. To leave PID_Compact in "Inactive" mode, set RunModeByStartup = FALSE. Meaning of values State / Mode Description of operating mode 0 Inactive In "Inactive" operating mode, the output value 0.0 is always output, regardless of Config.OutputUpperLimit and Config.OutputLowerLimit. Pulse width modulation is off. 1 Pretuning The pretuning determines the process response to a jump change of the output value and searches for the point of inflection. The PID parameters are calculated from the maximum rate of rise and dead time of the controlled system. You obtain the best PID parameters when you perform pretuning and fine tuning. Pretuning requirements: Inactive (State = 0), manual mode (State = 4), or automatic mode (State = 3) ManualEnable = FALSE Reset = FALSE The process value must not be too close to the setpoint. |Setpoint - Input| > 0.3 * | Config.InputUpperLimit - Config.InputLowerLimit| and |Setpoint - Input| > 0.5 * |Setpoint| The setpoint and the process value lie within the configured limits. The more stable the process value is, the easier it is to calculate the PID parameters and the more precise the result will be. Noise on the process value can be tolerated as long as the rate of rise of the process value is significantly higher compared to the noise. The setpoint is frozen in the CurrentSetpoint tag. Tuning is canceled when: Setpoint > CurrentSetpoint + CancelTuningLevel or Setpoint < CurrentSetpoint - CancelTuningLevel Before the PID parameters are recalculated, they are backed up and can be reactivated with LoadBackUp. The controller switches to automatic mode following successful pretuning. If pretuning is unsuccessful, the switchover of the operating mode is dependent on ActivateRecoverMode. The phase of pretuning is indicated with PIDSelfTune.SUT.State. WinCC Basic V13.0 System Manual, 02/2014 2905 Programming the PLC 9.7 References State / Mode Description of operating mode 2 Fine tuning Fine tuning generates a constant, limited oscillation of the process value. The PID parameters are recalculated based on the amplitude and frequency of this oscillation. PID parameters from fine tuning usually have better master control and disturbance characteristics than PID parameters from pretuning. You obtain the best PID parameters when you perform pretuning and fine tuning. PID_Compact automatically attempts to generate an oscillation greater than the noise of the process value. Fine tuning is only minimally influenced by the stability of the process value. The setpoint is frozen in the CurrentSetpoint tag. Tuning is canceled when: Setpoint > CurrentSetpoint + CancelTuningLevel or Setpoint < CurrentSetpoint - CancelTuningLevel Before the PID parameters are recalculated, they are backed up and can be reactivated with LoadBackUp. Requirements for fine tuning: No disturbances are expected. The setpoint and the process value lie within the configured limits. ManualEnable = FALSE Reset = FALSE Automatic (State = 3), inactive (State = 0) or manual (State = 4) mode Fine tuning proceeds as follows when started from: Automatic mode (State = 3) Start fine tuning from automatic mode if you wish to improve the existing PID parameters through tuning. PID_Compact controls the system using the existing PID parameters until the control loop has stabilized and the requirements for fine tuning have been met. Only then will fine tuning start. Inactive (State = 0) or manual mode (State = 4) If the requirements for pretuning are met, pretuning is started. The determined PID parameters will be used for control until the control loop has stabilized and the requirements for fine tuning have been met. If the process value for pretuning is already too near the setpoint or PIDSelfTune.TIR.RunIn = TRUE, an attempt is made to reach the setpoint with the minimum or maximum output value. This can produce increased overshoot. Only then will fine tuning start. The controller switches to automatic mode following successful fine tuning. If fine tuning is unsuccessful, the switchover of the operating mode is dependent on ActivateRecoverMode. The "Fine tuning" phase is indicated with PIDSelfTune.TIR.State. 3 Automatic mode In automatic mode, PID_Compact corrects the controlled system in accordance with the parameters specified. The controller switches to automatic mode if one the following requirements is fulfilled: Pretuning successfully completed Fine tuning successfully completed Changing of the Mode in-out parameter to the value 3 and a rising edge at ModeActivate. The switchover from automatic mode to manual mode is only bumpless if carried out in the commissioning editor. The ActivateRecoverMode tag is taken into consideration in automatic mode. 2906 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References State / Mode Description of operating mode 4 Manual mode In manual mode, you specify a manual output value in the ManualValue parameter. You can also activate this operating mode using ManualEnable = TRUE. We recommend that you change the operating mode using Mode and ModeActivate only. The switchover from manual mode to automatic mode is bumpless. Manual mode is also possible when an error is pending. 5 Substitute output value with error monitoring The control algorithm is deactivated. The SetSubstituteOutput tag determines which output value is output in this operating mode. SetSubstituteOutput = FALSE: Last valid output value SetSubstituteOutput = TRUE: Substitute output value You cannot activate this operating mode using Mode = 5. In the event of an error, it is activated instead of "Inactive" operating mode if all the following conditions are met: Automatic mode (Mode = 3) ActivateRecoverMode = TRUE One or more errors have occurred in which ActivateRecoverMode is effective. As soon as the errors are no longer pending, PID_Compact switches back to automatic mode. ENO characteristics If State = 0, then ENO = FALSE. If State 0, then ENO = TRUE. Automatic switchover of operating mode during commissioning Automatic mode is activated following successful pretuning or fine tuning. The following table shows how Mode and State change during successful pretuning. Cycle no. Mode State Action 0 4 4 Set Mode = 1 1 1 4 Set ModeActivate = TRUE 1 4 1 Value of State is saved in Mode parameter Pretuning is started n 4 1 Pretuning successfully completed n 3 3 Automatic mode is started PID_Compact automatically switches the operating mode in the event of an error. The following table shows how Mode and State change during pretuning with errors. WinCC Basic V13.0 System Manual, 02/2014 Cycle no. Mode State Action 0 4 4 Set Mode = 1 1 1 4 Set ModeActivate = TRUE 2907 Programming the PLC 9.7 References Cycle no. Mode State Action 1 4 1 Value of State is saved in Mode parameter Pretuning is started n 4 1 Pretuning canceled n 4 4 Manual mode is started If ActivateRecoverMode = TRUE, the operating mode that is saved in the Mode parameter is activated. At the start of pretuning or fine tuning, PID_Compact has saved the value of State in the Mode in/out parameter. PID_Compact therefore switches to the operating mode from which tuning was started. If ActivateRecoverMode = FALSE, the system switches to "Inactive" operating mode. See also Output parameters of PID_Compact V2 (Page 2894) Parameter ErrorBits V2 If several errors are pending simultaneously, the values of the ErrorBits are displayed with binary addition. The display of ErrorBits = 0003h, for example, indicates that the errors 0001h and 0002h are pending simultaneously. In manual mode, PID_Compact uses ManualValue as output value. The exception is Errorbits = 10000h. ErrorBits (DW#16#...) Description 0000 There is no error. 0001 The "Input" parameter is outside the process value limits. Input > Config.InputUpperLimit or Input < Config.InputLowerLimit If automatic mode was active before the error occurred and ActivateRecoverMode = TRUE, PID_Compact remains in automatic mode. If pretuning or fine tuning mode was active before the error occurred and ActivateRecoverMode = TRUE, PID_Compact switches to the operating mode that is saved in the Mode parameter. 0002 Invalid value at "Input_PER" parameter. Check whether an error is pending at the analog input. If automatic mode was active before the error occurred and ActivateRecoverMode = TRUE, PID_Compact outputs the configured substitute output value. As soon as the error is no longer pending, PID_Compact switches back to automatic mode. If pretuning or fine tuning mode was active before the error occurred and ActivateRecoverMode = TRUE, PID_Compact switches to the operating mode that is saved in the Mode parameter. 0004 Error during fine tuning. Oscillation of the process value could not be maintained. If ActivateRecoverMode = TRUE before the error occurred, PID_Compact cancels the tuning and switches to the operating mode that is saved in the Mode parameter. 0008 Error at start of pretuning. The process value is too close to the setpoint. Start fine tuning. If ActivateRecoverMode = TRUE before the error occurred, PID_Compact cancels the tuning and switches to the operating mode that is saved in the Mode parameter. 2908 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References ErrorBits (DW#16#...) Description 0010 The setpoint was changed during tuning. You can set the permitted fluctuation of the setpoint at the CancelTuningLevel tag. If ActivateRecoverMode = TRUE before the error occurred, PID_Compact cancels the tuning and switches to the operating mode that is saved in the Mode parameter. 0020 Pretuning is not permitted during fine tuning. If ActivateRecoverMode = TRUE before the error occurred, PID_Compact remains in fine tuning mode. 0080 Error during pretuning. Incorrect configuration of output value limits. Check whether the limits of the output value are configured correctly and match the control logic. If ActivateRecoverMode = TRUE before the error occurred, PID_Compact cancels the tuning and switches to the operating mode that is saved in the Mode parameter. 0100 Error during fine tuning resulted in invalid parameters. If ActivateRecoverMode = TRUE before the error occurred, PID_Compact cancels the tuning and switches to the operating mode that is saved in the Mode parameter. 0200 Invalid value at "Input" parameter: Value has an invalid number format. If automatic mode was active before the error occurred and ActivateRecoverMode = TRUE, PID_Compact outputs the configured substitute output value. As soon as the error is no longer pending, PID_Compact switches back to automatic mode. If pretuning or fine tuning mode was active before the error occurred and ActivateRecoverMode = TRUE, PID_Compact switches to the operating mode that is saved in the Mode parameter. 0400 Calculation of output value failed. Check the PID parameters. If automatic mode was active before the error occurred and ActivateRecoverMode = TRUE, PID_Compact outputs the configured substitute output value. As soon as the error is no longer pending, PID_Compact switches back to automatic mode. If pretuning or fine tuning mode was active before the error occurred and ActivateRecoverMode = TRUE, PID_Compact switches to the operating mode that is saved in the Mode parameter. 0800 Sampling time error: PID_Compact is not called within the sampling time of the cyclic interrupt OB. If automatic mode was active before the error occurred and ActivateRecoverMode = TRUE, PID_Compact remains in automatic mode. If pretuning or fine tuning mode was active before the error occurred and ActivateRecoverMode = TRUE, PID_Compact switches to the operating mode that is saved in the Mode parameter. 1000 Invalid value at "Setpoint" parameter: Value has an invalid number format. If automatic mode was active before the error occurred and ActivateRecoverMode = TRUE, PID_Compact outputs the configured substitute output value. As soon as the error is no longer pending, PID_Compact switches back to automatic mode. If pretuning or fine tuning mode was active before the error occurred and ActivateRecoverMode = TRUE, PID_Compact switches to the operating mode that is saved in the Mode parameter. 10000 Invalid value at ManualValue parameter. Value has an invalid number format. If ActivateRecoverMode = TRUE before an error occurred, PID_Compact uses SubstituteOutput as the output value. As soon as you specify a valid value in ManualValue, PID_Compact uses it as the output value. WinCC Basic V13.0 System Manual, 02/2014 2909 Programming the PLC 9.7 References ErrorBits (DW#16#...) Description 20000 Invalid value at SubstituteOutput tag. Value has an invalid number format. PID_Compact uses the output value low limit as the output value. If automatic mode was active before the error occurred, ActivateRecoverMode = TRUE, and the error is no longer pending, PID_Compact switches back to automatic mode. 40000 Invalid value at Disturbance parameter. Value has an invalid number format. If automatic mode was active and ActivateRecoverMode = TRUE before the error occurred, Disturbance is set to zero. PID_Compact remains in automatic mode. If pretuning or fine tuning mode was active and ActivateRecoverMode = TRUE before the error occurred, PID_Compact switches to the operating mode saved in the Mode parameter. If Disturbance in the current phase has no effect on the output value, tuning is not be canceled. Tag ActivateRecoverMode V2 The ActivateRecoverMode tag determines the reaction to error. The Error parameter indicates if an error is pending. When the error is no longer pending, Error = FALSE. The ErrorBits parameter shows which errors have occurred. Automatic mode NOTICE Your system may be damaged. If ActivateRecoverMode = TRUE, PID_Compact remains in automatic mode even if there is an error and the process limit values are exceeded. This may damage your system. It is essential to configure how your controlled system reacts in the event of an error to protect your system from damage. 2910 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References ActivateRecover Description Mode FALSE PID_Compact automatically switches to "Inactive" mode in the event of an error. The controller is only activated by a falling edge at Reset or a rising edge at ModeActivate. TRUE If errors occur frequently in automatic mode, this setting has a negative effect on the control response, because PID_Compact switches between the calculated output value and the substitute output value at each error. In this case, check the ErrorBits parameter and eliminate the cause of the error. If one or more of the following errors occur, PID_Compact stays in automatic mode: 0001h: The "Input" parameter is outside the process value limits. 0800h: Sampling time error 40000h: Invalid value at parameter Disturbance. If one or more of the following errors occur, PID_Compact switches to "Substitute output value with error monitoring" mode: 0002h: Invalid value at Input_PER parameter. 0200h: Invalid value at Input parameter. 0400h: Calculation of output value failed. 1000h: Invalid value at Setpoint parameter. If the following error occurs, PID_Compact switches to "Substitute output value with error monitoring" mode and moves the actuator to Config.OutputLowerLimit: 20000h: Invalid value at SubstituteOutput tag. Value has an invalid number format. This characteristics are independent of SetSubstituteOutput. As soon as the errors are no longer pending, PID_Compact switches back to automatic mode. Pretuning and fine tuning ActivateRecover Description Mode FALSE PID_Compact automatically switches to "Inactive" mode in the event of an error. The controller is only activated by a falling edge at Reset or a rising edge at ModeActivate. TRUE If the following error occurs, PID_Compact remains in the active mode: 0020h: Pretuning is not permitted during fine tuning. The following errors are ignored: 10000h: Invalid value at ManualValue parameter. 20000h: Invalid value at SubstituteOutput tag. When any other error occurs, PID_Compact cancels the tuning and switches to the mode from which tuning was started. Manual mode ActivateRecoverMode is not effective in manual mode. WinCC Basic V13.0 System Manual, 02/2014 2911 Programming the PLC 9.7 References Tag Warning V2 If several warnings are pending simultaneously, the values of the Warning tag are displayed with binary addition. The display of warning 0003h, for example, indicates that the warnings 0001h and 0002h are pending simultaneously. Warning Description (DW#16#....) 0000 No warning pending. 0001 The point of inflection was not found during pretuning. 0004 The setpoint was limited to the configured limits. 0008 Not all the necessary controlled system properties were defined for the selected method of calculation. Instead, the PID parameters were calculated using the TIR.TuneRule = 3 method. 0010 The operating mode could not be changed because Reset = TRUE or ManualEnable = TRUE. 0020 The cycle time of the calling OB limits the sampling time of the PID algorithm. Improve results by using shorter OB cycle times. 0040 The process value exceeded one of its warning limits. 0080 Invalid value at Mode. The operating mode is not switched. 0100 The manual value was limited to the limits of the controller output. 0200 The specified rule for tuning is not supported. No PID parameters are calculated. 1000 The substitute output value cannot be reached because it is outside the output value limits. The following warnings are deleted as soon as the cause is eliminated: 0001h 0004h 0008h 0040h 0100h All other warnings are cleared with a rising edge at Reset or ErrorAck. PID_Compact V1 Description of PID_Compact V1 Description The PID_Compact instruction provides a PID controller with integrated tuning for automatic and manual mode. Call PID_Compact is called in the constant interval of the cycle time of the calling OB (preferably in a cyclic interrupt OB). 2912 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Download to device The actual values of retentive tags are only updated when you download PID_Compact completely. Downloading technology objects to device (Page 4223) Startup At the startup of the CPU, PID_Compact starts in the operating mode that was last active. To retain PID_ Compact in "Inactive" mode, set sb_RunModeByStartup = FALSE. Monitoring of the sampling time PID_Compact Ideally, the sampling time is equivalent to the cycle time of the calling OB. The PID_Compact instruction measures the time interval between two calls. This is the current sampling time. On every switchover of operating mode and during the initial startup, the mean value is formed from the first 10 sampling times. If the current sampling time deviates too much from this mean value, Error = 0800 hex occurs and PID_Compact switches to "Inactive" mode. PID_Compact, Version 1.1 or higher is set to "Inactive" mode during controller tuning under the following conditions: New mean value >= 1.1 x old mean value New mean value <= 0.9 x old mean value In automatic mode, PID_Compact, Version 1.1 or higher, is set to "Inactive" mode under the following conditions: New mean value >= 1.5 x old mean value New mean value <= 0.5 x old mean value During controller tuning and in automatic mode, PID_Compact 1.0 is set to "Inactive" operating mode under the following conditions: New mean value >= 1.1 x old mean value New mean value <= 0.9 x old mean value Current sampling time >= 1.5 x current mean value Current sampling time <= 0.5 x current mean value Sampling time of the PID algorithm The controlled system needs a certain amount of time to respond to changes in the output value. It is therefore not advisable to calculate the output value in every cycle. The sampling time of the PID algorithm represents the time between two calculations of the output value. It is calculated during tuning and rounded to a multiple of the cycle time. All other functions of PID_Compact are executed at every call. WinCC Basic V13.0 System Manual, 02/2014 2913 Programming the PLC 9.7 References PID algorithm PID_Compact is a PIDT1 controller with anti-windup and weighting of the proportional and derivative actions. The following equation is used to calculate the output value. 1 [ (b * w - x) + T * s y = Kp (w - x) + I TD * s a * TD * s + 1 (c * w - x) Symbol Description y Output value Kp Proportional gain s Laplace operator b Proportional action weighting w Setpoint x Process value TI Integral action time a Derivative delay coefficient (T1 = a x TD) ] Derivative action time c Derivative action weighting Block diagram of PID_Compact ,QSXWB3(5 &53B,1 6FDOH EB,QSXWB3(5B2Q ,QSXW:DUQLQJB+ ,QSXW:DUQLQJB/ ,QSXW 6HWSRLQW 39B$/50 3,'7 $QWL:LQGXS /LPLW ,19 EB,QY&WUO 2XWSXW 0DQXDO(QDEOH 0DQXDO9DOXH /LPLW &53B287 3:0 2914 2XWSXWB3(5 2XWSXWB3:0 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Block diagram of PIDT1 with anti-windup E 6HWSRLQW Z $QWL:LQGXS /,0,7 , .3 \ F 6FDOHG,QSXW [ '7 Reaction to error If errors occur, they are output in parameter Error, and PID_Compact changes to "Inactive" mode. Reset the errors using the Reset parameter. Control logic An increase of the output value is generally intended to cause an increase in the process value. This is referred to as a normal control logic. For cooling and discharge control systems, it may be necessary to invert the control logic. PID_Compact does not work with negative proportional gain. If InvertControl = TRUE, an increasing control deviation causes a reduction in the output value. The control logic is also taken into account during pretuning and fine tuning. See also Controller type (Page 4262) Input parameters of PID_Compact V1 Table 9-83 Parameter Data type Default Description Setpoint REAL 0.0 Setpoint of the PID controller in automatic mode Input REAL 0.0 A variable of the user program is used as source for the process value. If you are using parameter Input, then sPid_Cmpt.b_Input_PER_On = FALSE must be set. WinCC Basic V13.0 System Manual, 02/2014 2915 Programming the PLC 9.7 References Parameter Data type Default Description Input_PER WORD W#16#0 Analog input as the source of the process value If you are using parameter Input_PER, then sPid_Cmpt.b_Input_PER_On = TRUE must be set. ManualEnable BOOL FALSE A FALSE -> TRUE edge selects "Manual mode", while State = 4, sRet.i_Mode remains unchanged. A TRUE -> FALSE edge selects the most recently active operating mode, State =sRet.i_Mode A change of sRet.i_Mode will not take effect during ManualEnable = TRUE. The change of sRet.i_Mode will only be considered upon a TRUE -> FALSE edge at ManualEnable . PID_Compact V1.2 und PID_Compact V1.0 If at start of the CPU ManualEnable = TRUE, PID_Compact starts in manual mode. A rising edge (FALSE > TRUE) at ManualEnable is not necessary. PID_Compact V1.1 At the start of the CPU, PID_Compact only switches to manual mode with a rising edge (FALSE->TRUE) at ManualEnable . Without rising edge, PID_Compact starts in the last operating mode in which ManualEnable was FALSE. ManualValue REAL 0.0 Manual value This value is used as the output value in manual mode. Reset BOOL FALSE The Reset parameter (Page 2925) restarts the controller. Output parameters of PID_Compact V1 Table 9-84 Parameter Data type Default Description ScaledInput REAL 0.0 Output of the scaled process value Outputs "Output", "Output_PER", and "Output_PWM" can be used concurrently. Output REAL 0.0 Output value in REAL format Output_PER WORD W#16#0 Analog output value Output_PWM BOOL FALSE Pulse-width-modulated output value SetpointLimit_H BOOL FALSE The output value is formed by minimum On and Off times. If SetpointLimit_H = TRUE, the setpoint absolute high limit is reached. The setpoint in the CPU is limited to the configured setpoint absolute high limit. The configured process value absolute high limit is the default for the setpoint high limit. If you set sPid_Cmpt.r_Sp_Hlm to a value within the process value limits, this value is used as the setpoint high limit. SetpointLimit_L BOOL FALSE If SetpointLimit_L = TRUE, the setpoint absolute low limit has been reached. In the CPU, the setpoint is limited to the configured setpoint absolute low limit. The configured process value absolute low limit is the default setting for the setpoint low limit. If you set sPid_Cmpt.r_Sp_Llm to a value within the process value limits, this value is used as the setpoint low limit. 2916 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameter Data type Default Description InputWarning_H BOOL FALSE If InputWarning_H = TRUE, the process value has reached or exceeded the warning high limit. InputWarning_L BOOL FALSE If InputWarning_L = TRUE, the process value has reached or fallen below the warning low limit. State INT 0 The State parameter (Page 2922) shows the current operating mode of the PID controller. To change the operating mode, use variable sRet.i_Mode. State = 0: Inactive State = 1: pretuning State = 2: fine tuning State = 3: Automatic mode State = 4: Manual mode Error DWORD W#16#0 The Error parameter (Page 2925) indicates the error messages. Error = 0000: No error pending. Static tags of PID_Compact V1 You must not change tags that are not listed. These are used for internal purposes only. Table 9-85 Tag Data type Default Description sb_GetCycleTime BOOL TRUE If sb_GetCycleTime = TRUE, the automatic determination of the cycle time is started. CycleTime.StartEstimation = FALSE once measurement is complete. sb_EnCyclEstimation BOOL TRUE If sb_EnCyclEstimation = TRUE, the sampling time PID_Compact is calculated. sb_EnCyclMonitoring BOOL TRUE If sb_EnCyclMonitoring = FALSE, the sampling time PID_Compact is not monitored. If it is not possible to execute PID_Compact within the sampling time, an 0800 error is not output and PID_Compact does not change to "Inactive" mode. sb_RunModeByStartup BOOL TRUE Activate Mode after CPU restart If sb_RunModeByStartup = FALSE, the controller will remain inactive after a CPU startup. After a CPU startup and if sb_RunModeByStartup = TRUE, the controller will return to the most recently active operating mode. si_Unit INT 0 Unit of measurement of the process value and setpoint, e.g., C, or F. si_Type INT 0 Physical quantity of the process value and setpoint, e.g., temperature. sd_Warning DWORD DW#16#0 Variable sd_warning (Page 2927) displays the warnings generated since the reset, or since the last change of the operating mode. WinCC Basic V13.0 System Manual, 02/2014 2917 Programming the PLC 9.7 References Tag Data type Default Description sBackUp.r_Gain REAL 1.0 Saved proportional gain You can reload values from the sBackUp structure with sPid_Cmpt.b_LoadBackUp = TRUE. sBackUp.r_Ti REAL 20.0 Saved integral action time [s] sBackUp.r_Td REAL 0.0 Saved derivative action time [s] sBackUp.r_A REAL 0.0 Saved derivative delay coefficient sBackUp.r_B REAL 0.0 Saved proportional action weighting factor sBackUp.r_C REAL 0.0 Saved derivative action weighting factor sBackUp.r_Cycle REAL 1.0 Saved sampling time of PID algorithm sPid_Calc.r_Cycle REAL 0.1 Sampling time of the PID_Compact instruction r_Cycle is determined automatically and usually equivalent to the cycle time of the calling OB. sPid_Calc.b_RunIn BOOL FALSE b_RunIn = FALSE Pretuning is started when fine tuning is started from inactive or manual mode. If the requirements for pretuning are not met, PID_Compact reacts like b_RunIn = TRUE. If fine tuning is started from automatic mode, the system uses the existing PID parameters to control to the setpoint. Only then will fine tuning start. If pretuning is not possible, PID_Compact will change to "Inactive" mode. b_RunIn = TRUE The pretuning is skipped. PID_3Compact tries to reach the setpoint with minimum or maximum output value. This can produce increased overshoot. Fine tuning then starts automatically. b_RunIn is set to FALSE after fine tuning. sPid_Calc.b_CalcParamSUT BOOL FALSE The parameters for pretuning will be recalculated if b_CalcParamSUT = TRUE. This enables you to change the parameter calculation method without having to repeat controller tuning. b_CalcParamSUT will be set to FALSE after calculation. sPid_Calc.b_CalcParamTIR BOOL FALSE The parameters for fine tuning will be recalculated if b_CalcParamTIR = TRUE. This enables you to change the parameter calculation method without having to repeat controller tuning. b_CalcParamTIR will be set to FALSE after calculation. sPid_Calc.i_CtrlTypeSUT INT 0 Methods used to calculate parameters during pretuning: i_CtrlTypeSUT = 0: PID according to Chien, Hrones and Reswick i_CtrlTypeSUT = 1: PI according to Chien, Hrones and Reswick 2918 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Tag Data type Default Description sPid_Calc.i_CtrlTypeTIR INT 0 Methods used to calculate parameters during fine tuning: i_CtrlTypeTIR = 0: PID automatic i_CtrlTypeTIR = 1: PID rapid i_CtrlTypeTIR = 2: PID slow i_CtrlTypeTIR = 3: Ziegler-Nichols PID i_CtrlTypeTIR = 4: Ziegler-Nichols PI i_CtrlTypeTIR = 5: Ziegler-Nichols P sPid_Calc.r_Progress REAL 0.0 Progress of tuning as a percentage (0.0 - 100.0) sPid_Cmpt.r_Sp_Hlm REAL +3.402822e +38 High limit of setpoint If you set sPid_Cmpt.r_Sp_Hlm outside the process value limits, the configured process value absolute high limit is used as the setpoint high limit. If you set sPid_Cmpt.r_Sp_Hlm within the process value limits, this value is used as the setpoint high limit. sPid_Cmpt.r_Sp_Llm REAL -3.402822e +38 Low limit of the setpoint If you set sPid_Cmpt.r_Sp_Llm outside the process value limits, the configured process value absolute low limit is used as the setpoint low limit. If you set sPid_Cmpt.r_Sp_Llm within the process value limits, this value is used as the setpoint low limit. sPid_Cmpt.r_Pv_Norm_IN_1 REAL 0.0 Scaling Input_PER low Input_PER is converted to percent based on the two value pairs r_Pv_Norm_OUT_1, r_Pv_Norm_IN_1 and r_Pv_Norm_OUT_2, r_Pv_Norm_IN_2 from the sPid_Cmpt structure. sPid_Cmpt.r_Pv_Norm_IN_2 REAL 27648.0 Scaling Input_PER high Input_PER is converted to percent based on the two value pairs r_Pv_Norm_OUT_1, r_Pv_Norm_IN_1 and r_Pv_Norm_OUT_2, r_Pv_Norm_IN_2 from the sPid_Cmpt structure. sPid_Cmpt.r_Pv_Norm_OUT_1 REAL 0.0 Scaled low process value Input_PER is converted to percent based on the two value pairs r_Pv_Norm_OUT_1, r_Pv_Norm_IN_1 and r_Pv_Norm_OUT_2, r_Pv_Norm_IN_2 from the sPid_Cmpt structure. sPid_Cmpt.r_Pv_Norm_OUT_2 REAL 100.0 Scaled high process value Input_PER is converted to percent based on the two value pairs r_Pv_Norm_OUT_1, r_Pv_Norm_IN_1 and r_Pv_Norm_OUT_2, r_Pv_Norm_IN_2 from the sPid_Cmpt structure. sPid_Cmpt.r_Lmn_Hlm REAL 100.0 Output value high limit for output parameter "Output" sPid_Cmpt.r_Lmn_Llm REAL 0.0 Low output value limit for output parameter "Output" sPid_Cmpt.b_Input_PER_On BOOL TRUE If b_Input_PER_On = TRUE, then parameter Input_PER is used. If b_Input_PER_On = FALSE, then parameter Input is used. WinCC Basic V13.0 System Manual, 02/2014 2919 Programming the PLC 9.7 References Tag Data type Default Description sPid_Cmpt.b_LoadBackUp BOOL FALSE Activate the back-up parameter set. If an optimization has failed, you can reactivate the previous PID parameters by setting this bit. sPid_Cmpt.b_InvCtrl BOOL FALSE Invert control logic With b_InvCtrl = TRUE, a rising control deviation reduces the output value. sPid_Cmpt.r_Lmn_Pwm_PPTm REAL 0.0 The minimum ON time of the pulse width modulation in seconds is rounded to r_Lmn_Pwm_PPTm = r_Cycle or r_Lmn_Pwm_PPTm = n*r_Cycle sPid_Cmpt.r_Lmn_Pwm_PBTm REAL 0.0 The minimum OFF time of the pulse width modulation in seconds is rounded to r_Lmn_Pwm_PBTm = r_Cycle or r_Lmn_Pwm_PBTm = n*r_Cycle sPid_Cmpt.r_Pv_Hlm REAL 120.0 High limit of the process value At the I/O input, the process value can be a maximum of 18% higher than the standard range (overrange). An error is no longer reported for a violation of the "Process value high limit". Only a wire-break and a short-circuit are recognized and the PID_Compact switches to "Inactive" mode. r_Pv_Hlm > r_Pv_Llm sPid_Cmpt.r_Pv_Llm REAL 0.0 Low limit of the process value r_Pv_Llm < r_Pv_Hlm sPid_Cmpt.r_Pv_HWrn REAL +3.402822e +38 Warning high limit of the process value If you set r_Pv_HWrn outside the process value limits, the configured process value absolute high limit is used as the warning high limit. If you set r_Pv_HWrn within the process value limits, this value is used as the warning high limit. r_Pv_HWrn > r_Pv_LWrn r_Pv_HWrn r_Pv_Hlm sPid_Cmpt.r_Pv_LWrn REAL -3.402822e +38 Warning low limit of the process value If you set r_Pv_LWrn outside the process value limits, the configured process value absolute low limit is used as the warning low limit. If you set r_Pv_LWrn within the process value limits, this value is used as the warning low limit. r_Pv_LWrn < r_Pv_HWrn r_Pv_LWrn r_Pv_LWrn sParamCalc.i_Event_SUT INT 0 Variable i_Event_SUT (Page 2928) indicates the current phase of "pretuning": sParamCalc.i_Event_TIR INT 0 Variable i_Event_TIR (Page 2928) indicates the current phase of "fine tuning": 2920 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Tag Data type Default Description sRet.i_Mode INT 0 The operating mode is changed edge-triggered. The following operating mode is enabled on a change to i_Mode = 0: "Inactive" (controller stop) i_Mode = 1: "Pretuning" mode i_Mode = 2: "Fine tuning" mode i_Mode = 3: "Automatic mode" i_Mode = 4: "Manual mode" i_Mode is retentive. sRet.r_Ctrl_Gain REAL 1.0 sRet.r_Ctrl_Ti REAL 20.0 Active proportional gain Gain is retentive. r_Ctrl_Ti > 0.0: active integral action time r_Ctrl_Ti = 0.0: Integral action is disabled r_Ctrl_Ti is retentive. sRet.r_Ctrl_Td REAL 0.0 r_Ctrl_Td > 0.0: Active derivative action time r_Ctrl_Td = 0.0: Derivative action is disabled r_Ctrl_Td is retentive. sRet.r_Ctrl_A REAL 0.0 Active derivative delay coefficient r_Ctrl_A is retentive. sRet.r_Ctrl_B REAL 0.0 Active proportional action weighting r_Ctrl_B is retentive. sRet.r_Ctrl_C REAL 0.0 Active derivative action weighting r_Ctrl_C is retentive. sRet.r_Ctrl_Cycle REAL 1.0 Active sampling time of the PID algorithm r_Ctrl_Cycle is calculated during controller tuning and rounded to an integer multiple of r_Cycle. r_Ctrl_Cycle is retentive. Note Change the tags listed in this table in "Inactive" mode to prevent malfunction of the PID controller. The "Inactive" mode is forced by setting variable "sRet.i_Mode" to "0". See also Downloading technology objects to device (Page 4223) WinCC Basic V13.0 System Manual, 02/2014 2921 Programming the PLC 9.7 References Parameters State and sRet.i_Mode V1 Correlation of the parameters The State parameter indicates the current operating mode of the PID controller. You cannot modify the State parameter. You need to modify the sRet.i_Mode tag to change the operating mode. This also applies when the value for the new operating mode is already in sRet.i_Mode. First set sRet.i_Mode = 0 and then sRet.i_Mode = 3. Provided the current operating mode of the controller supports this change, State is set to the value of sRet.i_Mode. When PID_Compact automatically switches the operating mode, the following applies: State ! = sRet.i_Mode. Examples: Successful pretuning State = 3 and sRet.i_Mode = 1 Error State = 0 and sRet.i_Mode remains at the same value, e.g sRet.i_Mode = 3 ManualEnalbe = TRUE State = 4 and sRet.i_Mode remain at the previous value, for example, sRet.i_Mode = 3 Note You wish to repeat successful fine tuning without exiting automatic mode with i_Mode = 0. Setting sRet.i_Mode to an invalid value such as 9999 for one cycle has no effect on State. Set Mode = 2 in the next cycle. You can generate a change to sRet.i_Mode without first switching to "inactive" mode. 2922 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Meaning of values State / sRet.i_Mode Description of the operating mode 0 Inactive The controller is switched off. The controller was in "inactive" mode before pretuning was performed. The PID controller will change to "inactive" mode when running if an error occurs or if the "Deactivate controller" icon is clicked in the commissioning window. 1 Pretuning The pretuning determines the process response to a jump of the output value and searches for the point of inflection. The optimized PID parameters are calculated as a function of the maximum rate of rise and dead time of the controlled system. Pretuning requirements: The controller is in inactive mode or manual mode ManualEnable = FALSE The process value must not be too close to the setpoint. |Setpoint - Input| > 0.3 * |sPid_Cmpt.r_Pv_Hlm - sPid_Cmpt.r_Pv_Llm| and |Setpoint - Input| > 0.5 * |Setpoint| The setpoint may not be changed during pretuning. The higher the stability of the process value, the easier it is to calculate the PID parameters and increase precision of the result. Noise on the process value can be tolerated as long as the rate of rise of the process value is significantly higher compared to the noise. PID parameters are backed up before they are recalculated and can be reactivated with sPid_Cmpt.b_LoadBackUp. There is a change to automatic mode following successful pretuning and to "inactive" mode following unsuccessful pretuning. The phase of pretuning is indicated with Tag i_Event_SUT V1 (Page 2928). WinCC Basic V13.0 System Manual, 02/2014 2923 Programming the PLC 9.7 References State / sRet.i_Mode Description of the operating mode 2 Fine tuning Fine tuning generates a constant, limited oscillation of the process value. The PID parameters are optimized based on the amplitude and frequency of this oscillation. The differences between the process response during pretuning and fine tuning are analyzed. All PID parameters are recalculated on the basis of the findings. PID parameters from fine tuning usually have better master control and disturbance behavior than PID parameters from pretuning. PID_Compact automatically attempts to generate an oscillation greater than the noise of the process value. Fine tuning is only minimally influenced by the stability of the process value. PID parameters are backed up before they are recalculated and can be reactivated with sPid_Cmpt.b_LoadBackUp. Requirements for fine tuning: No disturbances are expected. The setpoint and the process value lie within the configured limits. The setpoint may not be changed during fine tuning. ManualEnable = FALSE Automatic (State = 3), inactive (State = 0) or manual (State = 4) mode Fine tuning proceeds as follows when started in: Automatic mode (State = 3) Start fine tuning in automatic mode if you wish to improve the existing PID parameters using controller tuning. PID_Comact will regulate using the existing PID parameters until the control loop has stabilized and the requirements for fine tuning have been met. Only then will fine tuning start. Inactive (State = 0) or manual (State = 4) mode If the requirements for pretuning are met, pretuning is started. The PID parameters established will be used for adjustment until the control loop has stabilized and the requirements for fine tuning have been met. Only then will fine tuning start. If pretuning is not possible, PID_Compact will change to "Inactive" mode. An attempt is made to reach the setpoint with a minimum or maximum output value if the process value for pretuning is already too near the setpoint or sPid_Calc.b_RunIn = TRUE. This can produce increased overshoot. The controller will change to "automatic mode" after successfully completed "fine tuning" and to "inactive" mode if "fine tuning" has not been successfully completed. The "Fine tuning" phase is indicated with Tag i_Event_TIR V1 (Page 2928). 3 Automatic mode In automatic mode, PID_Compact corrects the controlled system in accordance with the parameters specified. The controller changes to automatic mode if one the following conditions is fulfilled: Pretuning successfully completed Fine tuning successfully completed Change of variable sRet.i_Mode to the value 3. After CPU startup or change from Stop to RUN mode, PID_Compact will start in the most recently active operating mode. To retain PID_Compact in "Inactive" mode, set sb_RunModeByStartup = FALSE. 4 Manual mode In manual mode, you specify a manual output value in the ManualValue parameter. This operating mode is enabled if sRet.i_Mode = 4, or at the rising edge on ManualEnable. If ManualEnable changes to TRUE, only State will change. sRet.i_Mode will retain its current value. PID_Compact will return to the previous operating mode upon a falling edge at ManualEnable. The change to automatic mode is bumpless. 2924 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References See also Output parameters of PID_Compact V1 (Page 2916) Pretuning (Page 4272) Fine tuning (Page 4274) "Manual" mode (Page 4275) Tag i_Event_SUT V1 (Page 2928) Tag i_Event_TIR V1 (Page 2928) Parameter Error V1 If several errors are pending simultaneously, the values of the error codes are displayed with binary addition. The display of error code 0003, for example, indicates that the errors 0001 and 0002 are pending simultaneously. Error (DW#16#...) Description 0000 There is no error. 0001 The "Input" parameter is outside the process value limits. Input > sPid_Cmpt.r_Pv_Hlm or Input < sPid_Cmpt.r_Pv_Llm You cannot move the actuator again until you eliminate the error. 0002 Invalid value at "Input_PER" parameter. Check whether an error is pending at the analog input. 0004 Error during fine tuning. Oscillation of the process value could not be maintained. 0008 Error at start of pretuning. The process value is too close to the setpoint. Start fine tuning. 0010 The setpoint was changed during tuning. 0020 Pretuning is not permitted in automatic mode or during fine tuning. 0080 Incorrect configuration of output value limits. Check whether the limits of the output value are configured correctly and match the control logic. 0100 Error during tuning resulted in invalid parameters. 0200 Invalid value at "Input" parameter: Value has an invalid number format. 0400 Calculation of output value failed. Check the PID parameters. 0800 Sampling time error: PID_Compact is not called within the sampling time of the cyclic interrupt OB. 1000 Invalid value at "Setpoint" parameter: Value has an invalid number format. See also Output parameters of PID_Compact V1 (Page 2916) Parameter Reset V1 The response to Reset = TRUE depends on the version of the PID_Compact instruction. WinCC Basic V13.0 System Manual, 02/2014 2925 Programming the PLC 9.7 References Reset response PID_Compact V.1.1 or higher A rising edge at Reset resets the errors and warnings and clears the integral action. A falling edge at Reset triggers a change to the most recently active operating mode. 5HVHW W PV LB0RGH W PV 6WDWH 2926 W PV Activation Error Reset WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Reset response PID_Compact V.1.0 A rising edge at Reset resets the errors and warnings and clears the integral action. The controller is not reactivated until the next edge at i_Mode. 5HVHW W PV LB0RGH W PV 6WDWH W PV Activation Error Reset Tag sd_warning V1 If several warnings are pending, the values of variable sd_warning are displayed by means of binary addition. The display of warning 0003, for example, indicates that the warnings 0001 and 0002 are also pending. sd_warning Description (DW#16#....) 0000 No warning pending. 0001 The point of inflection was not found during pretuning. 0002 Oscillation increased during fine tuning. 0004 The setpoint was outside the set limits. 0008 Not all the necessary controlled system properties were defined for the selected method of calculation. The PID parameters were instead calculated using the "i_CtrlTypeTIR = 3" method. 0010 The operating mode could not be changed because ManualEnable = TRUE. 0020 The cycle time of the calling OB limits the sampling time of the PID algorithm. Improve results by using shorter OB cycle times. 0040 The process value exceeded one of its warning limits. WinCC Basic V13.0 System Manual, 02/2014 2927 Programming the PLC 9.7 References The following warnings are deleted as soon as the cause is dealt with: 0004 0020 0040 All other warnings are cleared with a rising edge at Reset. Tag i_Event_SUT V1 i_Event_SUT Name 0 SUT_INIT Description Initialize pretuning 100 SUT_STDABW Calculate the standard deviation 200 SUT_GET_POI Find the point of inflection 9900 SUT_IO 1 SUT_NIO Pretuning successful Pretuning not successful See also Static tags of PID_Compact V1 (Page 2917) Parameters State and sRet.i_Mode V1 (Page 2922) Tag i_Event_TIR V1 i_Event_TIR Name -100 TIR_FIRST_SUT 0 TIR_INIT Description Fine tuning is not possible. Pretuning will be executed first. Initialize fine tuning 200 TIR_STDABW Calculate the standard deviation 300 TIR_RUN_IN Attempt to reach the setpoint 400 TIR_CTRLN Attempt to reach the setpoint with the existing PID parameters (if pretuning has been successful) 500 TIR_OSZIL 9900 TIR_IO 1 TIR_NIO Determine oscillation and calculate parameters Fine tuning successful Fine tuning not successful See also Static tags of PID_Compact V1 (Page 2917) Parameters State and sRet.i_Mode V1 (Page 2922) 2928 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References PID_3Step New features of PID_3Step PID_3Step V2.2 Use with S7-1200 As of PID_3Step V2.2, the instruction with V2 functionality can also be used on S7-1200 with firmware version 4.0 or higher. PID_3Step V2.0 Reaction to error The reaction to ActivateRecoverMode = TRUE has been completely overhauled. PID_3Step reacts in a more fault tolerant manner in the default setting. NOTICE Your system may be damaged. If you use the default setting, PID_3Step remains in automatic mode even if the process value limits are exceeded. This may damage your system. It is essential to configure how your controlled system reacts in the event of an error to protect your system from damage. You use the ErrorAck input parameter to acknowledge the errors and warnings without restarting the controller or clearing the integral action. Switching operating modes does not acknowledge errors that are no longer pending. Switching the operating mode You specify the operating mode at the Mode in/out parameter and use a rising edge at ModeActivate to start the operating mode. The Retain.Mode tag has been omitted. The transition time measurement can no longer be started with GetTransitTime.Start, but only with Mode = 6 and a rising edge at ModeActivate. Multi-instance capability You can call up PID_3Step as multi-instance DB. No technology object is created in this case and no parameter assignment interface or commissioning interface is available. You must assign parameters for PID_3Step directly in the multi-instance DB and commission it via a watch table. Startup characteristics The operating mode specified at the Mode parameter is also started on a falling edge at Reset and during a CPU cold restart, if RunModeByStartup = TRUE. ENO characteristics ENO is set depending on the operating mode. If State = 0, then ENO = FALSE. If State 0, then ENO = TRUE. WinCC Basic V13.0 System Manual, 02/2014 2929 Programming the PLC 9.7 References Manual mode The Manual_UP and Manual_DN input parameters no longer function as edge-triggered parameters. Edge-triggered manual mode continues to be possible using the ManualUpInternal and ManualDnInternal tags. In "Manual mode without endstop signals" (Mode = 10), the endstop signals Actuator_H and Actuator_L are ignored even though they are activated. Default value of PID parameters The following default settings have been changed: - Proportional action weighting (PWeighting) from 0.0 to 1.0 - Derivative action weighting (DWeighting) from 0.0 to 1.0 - Coefficient for derivative delay (TdFiltRatio) from 0.0 to 0.2 Limiting of motor transition time You configure the maximum percentage of the motor transition time that the actuator will travel in one direction in the Config.VirtualActuatorLimit tag. Setpoint value specification during tuning You configure the permitted fluctuation of the setpoint during tuning at the CancelTuningLevel tag. Switching a disturbance variable on You can switch a disturbance variable on at the Disturbance parameter. Troubleshooting If the endstop signals are not activated (ActuatorEndStopOn = FALSE), ScaledFeedback is determined without Actuator_H or Actuator_L. PID_3Step V1.1 Manual mode on CPU startup If ManualEnable = TRUE when the CPU starts, PID_3Step starts in manual mode. A rising edge at ManualEnable is not necessary. Reaction to error The ActivateRecoverMode tag is no longer effective in manual mode. Troubleshooting The Progress tag is reset following successful tuning or transition time measurement. Compatibility with CPU and FW The following table shows which version of PID_3Step can be used on which CPU. CPU FW PID_3Step S7-1200 V4.X V2.2 V1.1 S7-1200 V3.X S7-1200 V2.X V1.1 V1.0 V1.1 V1.0 2930 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References CPU FW PID_3Step S7-1200 V1.X - S7-1500 V1.1 V2.2 V2.1 V2.0 S7-1500 V1.0 V2.0 PID_3Step V2 Description of PID_3Step V2 Description You use the PID_3Step instruction to configure a PID controller with self tuning for valves or actuators with integrating behavior. The following operating modes are possible: Inactive Pretuning Fine tuning Automatic mode Manual mode Approach substitute output value Transition time measurement Error monitoring Approach substitute output value with error monitoring Manual mode without endstop signals For a more detailed description of the operating modes, see the State parameter. WinCC Basic V13.0 System Manual, 02/2014 2931 Programming the PLC 9.7 References PID algorithm PID_3Step is a PIDT1 controller with anti-windup and weighting of the proportional and derivative actions. The PID algorithm operates according to the following equation: 1 [ y = K p * s * (b * w - x) + Symbol 2932 TI * s (w - x) + TD * s a * TD * s + 1 (c * w - x) ] Description y Output value of the PID algorithm Kp Proportional gain s Laplace operator b Proportional action weighting w Setpoint x Process value TI Integral action time TD Derivative action time a Derivative delay coefficient (derivative delay T1 = a x TD) c Derivative action weighting WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Block diagram without position feedback ,QSXW:DUQLQJB+ 39B$/50 ,QSXW:DUQLQJB/ ,QSXW3HU2Q &53B,1 ,QSXWB3(5 $QWL:LQGXS 6FDOH ,QSXW )DF 3,'7 $QWL:LQGXS ,QW Y /LPLW 6HWSRLQW ' 'LVWXUEDQFH 2XWSXW3HU2Q 2XWSXW3HU2Q /LPLW 0DQXDO(QDEOH 0DQXDO9DOXH )$& 5RFB/LP 2XWSXW8SSHU/LPLW 2XWSXW/RZHU/LPLW 6WDWH 0DQXDOB'1 &53B287 0DQXDOB83 2XWSXWB3(5 $GHDGB% 6WDWH 0DQXDO83,QWHUQDO 7KU6WS 0DQXDO'1,QWHUQDO 0DQXDOB83 3XOVH2XW 6WDWH 2XWSXWB83 2XWSXWB'1 0DQXDOB'1 6WDWH WinCC Basic V13.0 System Manual, 02/2014 2933 Programming the PLC 9.7 References Block diagram with position feedback ,QSXW:DUQLQJB+ 39B$/50 ,QSXW3HU2Q ,QSXWB3(5 &53B,1 ,QSXW:DUQLQJB/ 6FDOH $QWL:LQGXS ,QSXW ,QW 3,'7 $QWL:LQGXS 6HWSRLQW )DF /LPLW /LPLW 6WDWH 9 ' 'LVWXUEDQFH 0DQXDO9DOXH )HHGEDFN3HU2Q )HHGEDFNB3(5 &53B,1 6FDOH )HHGEDFN 0DQXDOB83 2XWSXW8SSHU/LPLW 2XWSXW/RZHU/LPLW $GHDGB% &53B287 2XWSXWB3(5 0DQXDOB83 6WDWH 0DQXDO83,QWHUQDO 7KU6WS 6WDWH 0DQXDOB'1 2XWSXW3HU2Q 0DQXDO'1,QWHUQDO 6WDWH 3XOVH2XW 2XWSXWB83 2XWSXWB'1 0DQXDOB'1 6WDWH 2934 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Block diagram of PIDT1 with anti-windup E 6HWSRLQW Z '7 F ' . 3 \ 'HDGB% 7L , 6FDOHG,QSXW [ )DF7W $QWL:LQGXS Call PID_3Step is called in the constant time scale of a cycle interrupt OB. If you call PID_3Step as a multi-instance DB, no technology object is created. No parameter assignment interface or commissioning interface is available. You must assign parameters for PID_3Step directly in the multi-instance DB and commission it via a watch table. Download to device The actual values of retentive tags are only updated when you download PID_3Step completely. Downloading technology objects to device (Page 4223) Startup When the CPU starts up, PID_3Step starts in the operating mode that is saved in the Mode in/ out parameter. To leave PID_3Step in "Inactive" mode, set RunModeByStartup = FALSE. Reaction to error In automatic mode and during commissioning, the reaction to error depends on the ErrorBehaviour and ActivateRecoverMode tags. In manual mode, the reaction is independent WinCC Basic V13.0 System Manual, 02/2014 2935 Programming the PLC 9.7 References of ErrorBehaviour and ActivateRecoverMode. If ActivateRecoverMode = TRUE, the reaction additionally depends on the error that occurred. ErrorBeha viour ActivateRecov Configuration editor erMode > actuator setting > Set Output to Reaction FALSE FALSE Switch to "Inactive" mode (State = 0) Current output value The actuator remains in the current position. FALSE TRUE Current output value while error is pending Switch to "Error monitoring" mode (State = 7) The actuator remains in the current position while the error is pending. TRUE FALSE Substitute output value Switch to "Approach substitute output value" mode (State = 5) The actuator moves to the configured substitute output value. Switch to "Inactive" mode (State = 0) The actuator remains in the current position. TRUE TRUE Substitute output value while error is pending Switch to "Approach substitute output value with error monitoring" mode (State = 8) The actuator moves to the configured substitute output value. Switch to "Error monitoring" mode (State = 7) In manual mode, PID_3Step uses ManualValue as output value, unless the following errors occur: 2000h: Invalid value at Feedback_PER parameter. 4000h: Invalid value at Feedback parameter. 8000h: Error during digital position feedback. You can only change the position of the actuator with Manual_UP and Manual_DN, not with ManualValue. The Error parameter indicates whether an error has occurred in this cycle. The ErrorBits parameter shows which errors have occurred. ErrorBits is reset by a rising edge at Reset or ErrorAck. See also Parameters State and Mode V2 (Page 2952) Parameter ErrorBits V2 (Page 2957) Configuring PID_3Step V2 (Page 4277) 2936 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Mode of operation of PID_3Step V2 Monitoring process value limits You specify the high limit and low limit of the process value in the Config.InputUpperLimit and Config.InputLowerLimit variables. If the process value is outside these limits, an error occurs (ErrorBits = 0001h). You specify a high and low warning limit of the process value in the Config.InputUpperWarning and Config.InputLowerWarning variables. If the process value is outside these warning limits, a warning occurs (Warning = 0040h), and the InputWarning_H or InputWarning_L output parameter changes to TRUE. Limiting the setpoint You specify a high limit and low limit of the setpoint in the Config.SetpointUpperLimit and Config.SetpointLowerLimit variables. PID_3Step automatically limits the setpoint to the process value limits. You can limit the setpoint to a smaller range. PID_3Step checks whether this range falls within the process value limits. If the setpoint is outside these limits, the high or low limit is used as the setpoint, and output parameter SetpointLimit_H or SetpointLimit_L is set to TRUE. The setpoint is limited in all operating modes. Limiting the output value You specify a high limit and low limit of the output value in the Config.OutputUpperLimit and Config.OutputLowerLimit variables. The output value limits must be within "Low endstop" and "High endstop". High endstop: Config.FeedbackScaling.UpperPointOut Low endstop: Config.FeedbackScaling.LowerPointOut Rule: UpperPointOut OutputUpperLimit > OutputLowerLimit LowerPointOut The valid values for "High endstop" and "Low endstop" depend upon: FeedbackOn FeedbackPerOn OutputPerOn WinCC Basic V13.0 System Manual, 02/2014 OutputPerOn FeedbackOn FeedbackPerOn LowerPointOut UpperPointOut FALSE FALSE FALSE Cannot be set (0.0%) Cannot be set (100.0%) FALSE TRUE FALSE -100.0% or 0.0% 0.0% or +100.0% FALSE TRUE TRUE -100.0% or 0.0% 0.0% or +100.0% TRUE FALSE FALSE Cannot be set (0.0%) Cannot be set (100.0%) TRUE TRUE FALSE -100.0% or 0.0% 0.0% or +100.0% TRUE TRUE TRUE -100.0% or 0.0% 0.0% or +100.0% 2937 Programming the PLC 9.7 References If OutputPerOn = FALSE and FeedbackOn = FALSE, you cannot limit the output value. Output_UP and Output_DN are then reset at Actuator_H = TRUE or Actuator_L = TRUE. If endstop signals are also not present, Output_UP and Output_DN are reset after a travel time of Config.VirtualActuatorLimit x Retain.TransitTime/100. The output value is 27648 at 100% and -27648 at -100%. PID_3Step must be able to close the valve completely. Substitute output value If an error has occurred, PID_3Step can output a substitute output value and move the actuator to a safe position that is specified in the SavePosition tag. The substitute output value must be within the output value limits. Monitoring signal validity The values of the following parameters are monitored for validity when used: Setpoint Input Input_PER Input_PER Feedback Feedback_PER Disturbance ManualValue SavePosition Output_PER Monitoring the PID_3Step sampling time Ideally, the sampling time is equivalent to the cycle time of the calling OB. The PID_3Step instruction measures the time interval between two calls. This is the current sampling time. On every switchover of operating mode and during the initial startup, the mean value is formed from the first 10 sampling times. Too great a difference between the current sampling time and this mean value triggers an error (ErrorBits = 0800h). The error occurs during tuning if: New mean value >= 1.1 x old mean value New mean value <= 0.9 x old mean value The error occurs in automatic mode if: New mean value >= 1.5 x old mean value New mean value <= 0.5 x old mean value 2938 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References If you deactivate the sampling time monitoring (CycleTime.EnMonitoring = FALSE), you can also call PID_3Step in OB1. You must then accept a lower control quality due to the deviating sampling time. Sampling time of the PID algorithm The controlled system needs a certain amount of time to respond to changes in the output value. It is therefore not advisable to calculate the output value in every cycle. The sampling time of the PID algorithm represents the time between two calculations of the output value. It is calculated during tuning and rounded to a multiple of the cycle time. All other functions of PID_3Step are executed at every call. Measuring the motor transition time The motor transition time is the time in seconds the motor requires to move the actuator from the closed to the opened state. The actuator is moved in one direction for a maximum time of Config.VirtualActuatorLimit x Retain.TransitTime/100. PID_3Step requires the motor transition time to be as accurate as possible for good controller results. The data in the actuator documentation contains average values for this type of actuator. The value for the specific actuator used may differ. You can measure the motor transition time during commissioning. The output value limits are not taken into consideration during the motor transition time measurement. The actuator can travel to the high or the low endstop. Control logic An increase of the output value is generally intended to cause an increase in the process value. This is referred to as a normal control logic. For cooling and discharge control systems, it may be necessary to invert the control logic. PID_3Step does not work with negative proportional gain. If InvertControl = TRUE, an increasing control deviation causes a reduction in the output value. The control logic is also taken into account during pretuning and fine tuning. See also Configuring PID_3Step V1 (Page 4294) Changing the PID_3Step V2 interface The following table shows what has changed in the PID_3Step instruction interface. PID_3Step V1 PID_3Step V2 Change Input_PER Input_PER Data type from Word to Int Feedback_PER Feedback_PER Data type from Word to Int Disturbance New Manual_UP Manual_UP Function Manual_DN Manual_DN Function ErrorAck New WinCC Basic V13.0 System Manual, 02/2014 2939 Programming the PLC 9.7 References PID_3Step V1 PID_3Step V2 Change ModeActivate New Output_PER Data type from Word to Int ManualUPInternal New ManualDNInternal New CancelTuningLevel New VirtualActuatorLImit New Config.Loadbackup Loadbackup Renamed Config.TransitTime Retain.TransitTime Renamed and retentivity added Output_PER GetTransitTime.Start Replaced by Mode and ModeActivate SUT.CalculateSUTPara ms SUT.CalculateParams Renamed SUT.TuneRuleSUT SUT.TuneRule Renamed TIR.CalculateTIRParams TIR.CalculateParams Renamed TIR.TuneRuleTIR TIR.TuneRule Renamed Retain.Mode Mode Function Declaration of static for in-out parameters Input parameters of PID_3Step V2 Table 9-86 Parameter Data type Default Description Setpoint REAL 0.0 Setpoint of the PID controller in automatic mode Input REAL 0.0 A tag of the user program is used as the source of the process value. If you are using the Input parameter, then Config.InputPerOn = FALSE must be set. Input_PER INT 0 An analog input is used as the source of the process value. If you are using the Input_PER parameter, then Config.InputPerOn = TRUE must be set. Actuator_H BOOL FALSE Digital position feedback of the valve for the high endstop If Actuator_H = TRUE, the valve is at the high endstop and is no longer moved towards this direction. Actuator_L BOOL FALSE Digital position feedback of the valve for the low endstop If Actuator_L = TRUE, the valve is at the low endstop and is no longer moved towards this direction. Feedback REAL 0.0 Position feedback of the valve If you are using the Feedback parameter, then Config.FeedbackPerOn = FALSE must be set. 2940 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameter Data type Default Description Feedback_PER INT 0 Analog position feedback of a valve If you are using the Feedback_PER parameter, then Config.FeedbackPerOn = TRUE must be set. Feedback_PER is scaled based on the tags: Config.FeedbackScaling.LowerPointIn Config.FeedbackScaling.UpperPointIn Config.FeedbackScaling.LowerPointOut Config.FeedbackScaling.UpperPointOut Disturbance REAL 0.0 Disturbance tag or precontrol value ManualEnable BOOL FALSE A FALSE -> TRUE edge activates "manual mode", while State = 4, Mode remain unchanged. As long as ManualEnable = TRUE, you cannot change the operating mode via a rising edge at ModeActivate or use the commissioning dialog. A TRUE -> FALSE edge activates the operating mode that is specified by Mode. We recommend that you change the operating mode using ModeActivate only. ManualValue REAL 0.0 In manual mode, the absolute position of the valve is specified. ManualValue is only evaluated if you are using Output_PER, or if position feedback is available. Manual_UP BOOL FALSE Manual_UP = TRUE The valve is opened even if you are using Output_PER or a position feedback. The valve is no longer moved if the high endstop has been reached. See also Config.VirtualActuatorLimit Manual_UP = FALSE If you are using Output_PER or a position feedback, the valve is moved to ManualValue. Otherwise, the valve is no longer moved. If Manual_UP and Manual_DN are set to TRUE simultaneously, the valve is not moved. Manual_DN BOOL FALSE Manual_DN = TRUE The valve is closed even if you are using Output_PER or a position feedback. The valve is no longer moved if the low endstop has been reached. See also Config.VirtualActuatorLimit Manual_DN = FALSE If you are using Output_PER or a position feedback, the valve is moved to ManualValue. Otherwise, the valve is no longer moved. ErrorAck WinCC Basic V13.0 System Manual, 02/2014 BOOL FALSE FALSE -> TRUE edge ErrorBits and Warning are reset. 2941 Programming the PLC 9.7 References Parameter Data type Default Description Reset BOOL FALSE Restarts the controller. FALSE -> TRUE edge - Switch to "Inactive" mode - ErrorBits and Warning are reset. - Integral action is cleared (PID parameters are retained) As long as Reset = TRUE, PID_3Step remains in "Inactive" mode (State = 0). TRUE -> FALSE edge PID_3Step switches to the operating mode that is saved in the Mode parameter. ModeActivate BOOL FALSE FALSE -> TRUE edge PID_3Step switches to the operating mode that is saved in the Mode parameter. Output parameters of PID_3Step V2 Table 9-87 Parameter Data type Default Description ScaledInput REAL 0.0 Scaled process value ScaledFeedback REAL 0.0 Scaled position feedback For an actuator without position feedback, the position of the actuator indicated by ScaledFeedback is very imprecise. ScaledFeedback may only be used for rough estimation of the current position in this case. Output_UP BOOL FALSE Digital output value for opening the valve If Config.OutputPerOn = FALSE, the Output_UP parameter is used. Output_DN BOOL FALSE Digital output value for closing the valve If Config.OutputPerOn = FALSE, the Output_DN parameter is used. Output_PER INT 0 SetpointLimit_H BOOL FALSE SetpointLimit_L BOOL FALSE Analog output value If Config.OutputPerOn = TRUE, Output_PER is used. If SetpointLimit_H = TRUE, the absolute setpoint high limit is reached (Setpoint Config.SetpointUpperLimit). The setpoint is limited to Config.SetpointUpperLimit . If SetpointLimit_L = TRUE, the absolute setpoint low limit has been reached (Setpoint Config.SetpointLowerLimit). The setpoint is limited to Config.SetpointLowerLimit . InputWarning_H BOOL FALSE If InputWarning_H = TRUE, the process value has reached or exceeded the warning high limit. InputWarning_L BOOL FALSE If InputWarning_L = TRUE, the process value has reached or fallen below the warning low limit. 2942 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameter Data type Default Description State INT 0 The State parameter (Page 2952) shows the current operating mode of the PID controller. You can change the operating mode using the input parameter Mode and a rising edge at ModeActivate. State = 0: Inactive State = 1: Pretuning State = 2: Fine tuning State = 3: Automatic mode State = 4: Manual mode State = 5: Approach substitute output value State = 6: Transition time measurement State = 7: Error monitoring State = 8: Approach substitute output value with error monitoring State = 10: Manual mode without end stop signals Error BOOL FALSE If Error = TRUE, at least one error message is pending in this cycle. ErrorBits DWORD DW#16#0 The ErrorBits parameter (Page 2957) shows which error messages are pending. ErrorBits is retentive and is reset upon a rising edge at Reset or ErrorAck. See also Parameters State and Mode V2 (Page 2952) Parameter ErrorBits V2 (Page 2957) WinCC Basic V13.0 System Manual, 02/2014 2943 Programming the PLC 9.7 References In-out parameters of PID_3Step V2 Table 9-88 Parameter Data type Default Description Mode INT 4 At the Mode parameter, you specify the operating mode to which PID_3Step is to switch. Options are: Mode = 0: Inactive Mode = 1: Pretuning Mode = 2: Fine tuning Mode = 3: Automatic mode Mode = 4: Manual mode Mode = 6: Transition time measurement Mode = 10: Manual mode without endstop signals The operating mode is activated by: Rising edge at ModeActivate Falling edge at Reset Falling edge at ManualEnable Cold restart of CPU if RunModeByStartup = TRUE Mode is retentive. A detailed description of the operating modes can be found in Parameters State and Mode V2 (Page 2952). Static tags of PID_3Step V2 You must not change tags that are not listed. These are used for internal purposes only. Tag Data type Default Description ManualUpInternal BOOL FALSE In manual mode, each rising edge opens the valve by 5% of the total control range or for the duration of the minimum motor transition time. ManualUpInternal is only evaluated if you are not using Output_PER or a position feedback. This tag is used in the commissioning dialog. ManualDnInternal BOOL FALSE In manual mode, every rising edge closes the valve by 5% of the total control range or for the duration of the minimum motor transition time. ManualDnInternal is only evaluated if you are not using Output_PER or position feedback. This tag is used in the commissioning dialog. ActivateRecoverMode BOOL TRUE The ActivateRecoverMode V2 (Page 2960) tag determines the reaction to error. RunModeByStartup BOOL TRUE Activate operating mode at Mode parameter after CPU restart If RunModeByStartup = TRUE, PID_3Step starts in the operating mode saved in the Mode parameter after CPU startup. If RunModeByStartup = FALSE, PID_3Step remains in "Inactive" mode after CPU startup. LoadBackUp 2944 BOOL FALSE If LoadBackUp = TRUE, the last set of PID parameters is reloaded. The set was saved prior to the last tuning. LoadBackUp is automatically set back to FALSE. WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Tag Data type Default Description PhysicalUnit INT 0 Unit of measurement of the process value and setpoint, e.g., C, or F. PhysicalQuantity INT 0 Physical quantity of the process value and setpoint, e.g., temperature ErrorBehaviour BOOL FALSE If ErrorBehaviour = FALSE and an error has occurred, the valve stays at its current position and the controller switches directly to "Inactive" or "Error monitoring" mode. If ErrorBehaviour = TRUE and an error occurs, the actuator moves to the substitute output value and only then switches to "Inactive" or "Error monitoring" mode. If the following errors occur, you can no longer move the valve to a configured substitute output value. 2000h: Invalid value at Feedback_PER parameter. 4000h: Invalid value at Feedback parameter. 8000h: Error during digital position feedback. 20000h: Invalid value at SavePosition tag. Warning DWORD DW#16# 0 The Warning tag (Page 2952) shows the warnings since Reset = TRUE or ErrorAck =TRUE. Warning is retentive. Cyclic warnings (for example, process value warning) are shown until the cause of the warning is removed. They are automatically deleted once their cause has gone. Non-cyclic warnings (for example, point of inflection not found) remain and are deleted like errors. SavePosition REAL 0.0 Substitute output value If ErrorBehaviour = TRUE, the actuator is moved to a position that is safe for the plant when an error occurs. As soon as the substitute output value has been reached, PID_3Step switches the operating mode according to ActivateRecoverMode. CurrentSetpoint REAL 0.0 Currently active setpoint. This value is frozen at the start of tuning. CancelTuningLevel REAL 10.0 Permissible fluctuation of setpoint during tuning. Tuning is not canceled until: Setpoint > CurrentSetpoint + CancelTuningLevel or Setpoint < CurrentSetpoint - CancelTuningLevel Progress REAL 0.0 Progress of tuning as a percentage (0.0 - 100.0) Config.InputPerOn BOOL TRUE If InputPerOn = TRUE, the Input_PER parameter is used. If InputPerOn = FALSE, the Input parameter is used. Config.OutputPerOn BOOL FALSE If OutputPerOn = TRUE, the Output_PER parameter is used. If OutputPerOn = FALSE, the Ouput_UP and Output_DN parameters are used. Config.InvertControl BOOL FALSE Invert control logic If InvertControl = TRUE, an increasing control deviation causes a reduction in the output value. Config.FeedbackOn BOOL FALSE If FeedbackOn = FALSE, a position feedback is simulated. Position feedback is generally activated when FeedbackOn = TRUE. WinCC Basic V13.0 System Manual, 02/2014 2945 Programming the PLC 9.7 References Tag Data type Default Description Config.FeedbackPerOn BOOL FeedbackPerOn is only effective when FeedbackOn = TRUE. FALSE If FeedbackPerOn = TRUE, the analog input is used for the position feedback (Feedback_PER parameter). If FeedbackPerOn = FALSE, the Feedback parameter is used for the position feedback. Config.ActuatorEndStopOn BOOL FALSE If ActuatorEndStopOn = TRUE, the digital position feedback Actuator_L and Actuator_H are taken into consideration. Config.InputUpperLimit REAL 120.0 High limit of the process value Input and Input_PER are monitored to ensure adherence to this limit. At the I/O input, the process value can be a maximum of 18% higher than the standard range (overrange). An error is no longer signaled due to a violation of the "Process value high limit". Only a wire-break and a short-circuit are recognized and PID_3Step reacts according to the configured reaction to error. InputUpperLimit > InputLowerLimit Config.InputLowerLimit REAL 0.0 Low limit of the process value InputLowerLimit < InputUpperLimit Config.InputUpperWarning REAL +3.40282 Warning high limit of the process value 2e+38 If you set InputUpperWarning outside the process value limits, the configured absolute process value high limit is used as the warning high limit. If you configure InputUpperWarning within the process value limits, this value is used as the warning high limit. InputUpperWarning > InputLowerWarning InputUpperWarning InputUpperLimit Config.InputLowerWarning REAL -3.40282 2e+38 Warning low limit of the process value If you set InputLowerWarning outside the process value limits, the configured absolute process value low limit is used as the warning low limit. If you configure InputLowerWarning within the process value limits, this value is used as the warning low limit. InputLowerWarning < InputUpperWarning InputLowerWarning InputLowerLimit Config.OutputUpperLimit REAL 100.0 High limit of output value For details, see OutputLowerLimit Config.OutputLowerLimit REAL 0.0 Low limit of output value If OutputPerOn = TRUE or FeedbackOn = TRUE, the range of values from -100% to +100%, including zero, is valid. At -100%, Output = -27648; at +100% Output = 27648 If OutputPerOn = FALSE, the range of values from 0% to 100% is valid. The valve is completely closed at 0% and completely opened at 100%. Config.SetpointUpperLimit REAL +3.40282 High limit of setpoint 2e+38 If you set SetpointUpperLimit outside the process value limits, the configured absolute process value high limit is preassigned as the setpoint high limit. If you configure SetpointUpperLimit within the process value limits, this value is used as the setpoint high limit. 2946 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Tag Data type Default Config.SetpointLowerLimit REAL Description Low limit of the setpoint 3.402822 If you set SetpointLowerLimit outside the process value limits, the e+38 configured absolute process value low limit is preassigned as the setpoint low limit. If you set SetpointLowerLimit within the process value limits, this value is used as the setpoint low limit. Config.MinimumOnTime REAL 0.0 Minimum ON time Minimum time in seconds for which the servo drive must be switched on. Config.MinimumOffTime REAL 0.0 Minimum OFF time Minimum time in seconds for which the servo drive must be switched off. Config.VirtualActuatorLimit REAL 150.0 If all the following conditions have been satisfied, the actuator is moved in one direction for the maximum period of VirtualActuatorLimit x Retain.TransitTime/100 and the warning 2000h is output: Config.OutputPerOn = FALSE Config.ActuatorEndStopOn = FALSE Config.FeedbackOn = FALSE If Config.OutputPerOn = FALSE and Config.ActuatorEndStopOn = TRUE or Config.FeedbackOn = TRUE, only the warning 2000h is output. If Config.OutputPerOn = TRUE, VirtualActuatorLimit is not taken into consideration. Config.InputScaling.UpperPoi ntIn REAL Config.InputScaling.LowerPoi ntIn REAL Config.InputScaling.UpperPoi ntOut REAL Config.InputScaling.LowerPoi ntOut REAL 27648.0 Input_PER is converted to a percentage based on the two value pairs UpperPointOut, UpperPointIn and LowerPointOut, LowerPointIn of the InputScaling structure. 0.0 Scaling Input_PER low Input_PER is converted to a percentage based on the two value pairs UpperPointOut, UpperPointIn and LowerPointOut, LowerPointIn of the InputScaling structure. 100.0 Scaled high process value Input_PER is converted to a percentage based on the two value pairs UpperPointOut, UpperPointIn and LowerPointOut, LowerPointIn of the InputScaling structure. 0.0 Scaled low process value Input_PER is converted to a percentage based on the two value pairs UpperPointOut, UpperPointIn and LowerPointOut, LowerPointIn of the InputScaling structure. Config.FeedbackScaling.Uppe REAL rPointIn 27648.0 Config.FeedbackScaling.Lowe REAL rPointIn 0.0 WinCC Basic V13.0 System Manual, 02/2014 Scaling Input_PER high Scaling Feedback_PER high Feedback_PER is converted to a percentage based on the two value pairs UpperPointOut, UpperPointIn and LowerPointOut, LowerPointIn of the FeedbackScaling structure. Scaling Feedback_PER low Feedback_PER is converted to a percentage based on the two value pairs UpperPointOut, UpperPointIn and LowerPointOut, LowerPointIn of the FeedbackScaling structure. 2947 Programming the PLC 9.7 References Tag Data type Default Config.FeedbackScaling.Uppe REAL rPointOut 100.0 Config.FeedbackScaling.Lowe REAL rPointOut 0.0 GetTransitTime.InvertDirectio n FALSE BOOL Description High endstop Feedback_PER is converted to a percentage based on the two value pairs UpperPointOut, UpperPointIn and LowerPointOut, LowerPointIn of the FeedbackScaling structure. Low endstop Feedback_PER is converted to a percentage based on the two value pairs UpperPointOut, UpperPointIn and LowerPointOut, LowerPointIn of the FeedbackScaling structure. If InvertDirection = FALSE, the valve is fully opened, closed, and then reopened in order to determine the valve transition time. If InvertDirection = TRUE, the valve is fully closed, opened, and then closed again. GetTransitTime.SelectFeedba ck BOOL FALSE If SelectFeedback = TRUE, then Feedback_PER, or Feedback is taken into consideration in the transition time measurement. If SelectFeedback = FALSE, then Actuator_H and Actuator_L are taken into consideration in the transition time measurement. GetTransitTime.State INT 0 Current phase of the transition time measurement State = 0: Inactive State = 1: Open valve completely State = 2: Close valve completely State = 3: Move valve to target position (NewOutput) State = 4: Transition time measurement successfully completed State = 5: Transition time measurement canceled GetTransitTime.NewOutput REAL 0.0 Target position for transition time measurement with position feedback The target position must be between "High endstop" and "Low endstop". The difference between NewOutput and ScaledFeedback must be at least 50% of the permissible control range. CycleTime.StartEstimation BOOL TRUE CycleTime.EnEstimation BOOL TRUE If StartEstimation = TRUE, the measurement of the PID_3Step sampling time is started. CycleTime.StartEstimation = FALSE once measurement is complete. If EnEstimation = TRUE, the PID_3Step sampling time is calculated. If CycleTime.EnEstimation = FALSE, the PID_3Step sampling time is not calculated and you need to correct the configuration of CycleTime.Value manually. CycleTime.EnMonitoring BOOL TRUE If EnMonitoring = TRUE, the PID_3Step sampling time is monitored. If it is not possible to execute PID_3Step within the sampling time, the error 0800h is output and the operating mode is switched. ActivateRecoverMode and ErrorBehaviour determine which operating mode is switched to. If EnMonitoring = FALSE, the PID_3Step sampling time is not monitored, the error 0800h is not output, and the operating mode is not switched. CycleTime.Value REAL 0.1 PID_3Step sampling time in seconds CycleTime.Value is determined automatically and is usually equivalent to the cycle time of the calling OB. 2948 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Tag Data type Default CtrlParamsBackUp.SetByUser BOOL FALSE Description Saved value of Retain.CtrlParams.SetByUser You can reload values from the CtrlParamsBackUp structure with LoadBackUp = TRUE. CtrlParamsBackUp.Gain REAL 1.0 Saved proportional gain CtrlParamsBackUp.Ti REAL 20.0 Saved integral action time in seconds CtrlParamsBackUp.Td REAL 0.0 Saved derivative action time in seconds CtrlParamsBackUp.TdFiltRati o REAL 0.2 Saved derivative delay coefficient CtrlParamsBackUp.PWeightin g REAL 1.0 Saved proportional action weighting CtrlParamsBackUp.DWeightin REAL g 1.0 Saved derivative action weighting CtrlParamsBackUp.Cycle REAL 1.0 Saved sampling time of PID algorithm in seconds CtrlParamsBackUp.InputDead REAL Band 0.0 Saved deadband width of the control deviation PIDSelfTune.SUT.CalculateP arams BOOL FALSE The properties of the controlled system are saved during tuning. If CalculateParams = TRUE, the PID parameters are recalculated on the basis of these properties. The PID parameters are calculated using the method set in TuneRule. CalculateParams is set to FALSE following calculation. PIDSelfTune.SUT.TuneRule INT 1 Methods used to calculate parameters during pretuning: SUT.TuneRule = 0: PID rapid I SUT.TuneRule = 1: PID slow I SUT.TuneRule = 2: Chien, Hrones and Reswick PID SUT.TuneRule = 3: Chien, Hrones, Reswick PI SUT.TuneRule = 4: PID rapid II SUT.TuneRule = 5: PID slow II PIDSelfTune.SUT.State INT 0 The SUT.State tag indicates the current phase of pretuning: State = 0: Initialize pretuning State = 50: Determine start position without position feedback State = 100: Calculate standard deviation State = 200: Determine point of inflection State = 300: Determine rise time State = 9900: Pretuning successful State = 1: Pretuning not successful WinCC Basic V13.0 System Manual, 02/2014 2949 Programming the PLC 9.7 References Tag Data type Default Description PIDSelfTune.TIR.RunIn BOOL With the RunIn tag, you can specify that fine tuning can also be performed without pretuning. FALSE RunIn = FALSE Pretuning is started when fine tuning is started from inactive or manual mode. If fine tuning is started from automatic mode, the system uses the existing PID parameters to control to the setpoint. Only then will fine tuning start. If pretuning is not possible, PID_3Step switches to the mode from which tuning was started. RunIn = TRUE The pretuning is skipped. PID_3Step attempts to reach the setpoint with the minimum or maximum output value. This can produce increased overshoot. Only then will fine tuning start. RunIn is set to FALSE after fine tuning. PIDSelfTune.TIR.CalculatePar BOOL ams FALSE The properties of the controlled system are saved during tuning. If CalculateParams = TRUE, the PID parameters are recalculated on the basis of these properties. The PID parameters are calculated using the method set in TuneRule. CalculateParams is set to FALSE following calculation. PIDSelfTune.TIR.TuneRule 0 Methods used to calculate parameters during fine tuning: INT TIR.TuneRule = 0: PID automatic TIR.TuneRule = 1: PID rapid TIR.TuneRule = 2: PID slow TIR.TuneRule = 3: Ziegler-Nichols PID TIR.TuneRule = 4: Ziegler-Nichols PI TIR.TuneRule = 5: Ziegler-Nichols P PIDSelfTune.TIR.State INT 0 The TIR.State tag indicates the current phase of fine tuning: State = -100 Fine tuning is not possible. Pretuning will be performed first. State = 0: Initialize fine tuning State = 200: Calculate standard deviation State = 300: Attempt to reach the setpoint with the maximum or minimum output value State = 400: Attempt to reach the setpoint with existing PID parameters (if pretuning was successful) State = 500: Determine oscillation and calculate parameters State = 9900: Fine tuning successful State = 1: Fine tuning not successful Retain.TransitTime REAL 30.0 Motor transition time in seconds Time in seconds the actuating drive requires to move the valve from the closed to the opened state. TransitTime is retentive. 2950 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Tag Data type Default Description Retain.CtrlParams.SetByUser BOOL If SetByUser = FALSE, the PID parameters are determined automatically and PID_3Step operates with a deadband at the output value. The deadband width is calculated during tuning on the basis of the standard deviation of the output value and saved in Retain.CtrlParams.OutputDeadBand. FALSE If SetByUser = TRUE, the PID parameters are entered manually and PID_3 Step operates without a deadband at the output value. Retain.CtrlParams.OutputDeadBand = 0.0 SetByUser is retentive. Retain.CtrlParams.Gain REAL 1.0 Active proportional gain To invert the control logic, use the Config.InvertControl tag. Negative values at Gain also invert the control logic. We recommend you use only InvertControl to set the control logic. The control logic is also inverted if InvertControl = TRUE and Gain < 0.0. Gain is retentive. Retain.CtrlParams.Ti REAL 20.0 Ti > 0.0: Active integral action time in seconds Ti = 0.0: Integral action is deactivated Ti is retentive. Retain.CtrlParams.Td REAL 0.0 Td > 0.0: Active derivative action time in seconds Td = 0.0: Derivative action is deactivated Td is retentive. Retain.CtrlParams.TdFiltRatio REAL 0.2 Active derivative delay coefficient The derivative delay coefficient delays the effect of the derivative action. Derivative delay = derivative action time x derivative delay coefficient 0.0: Derivative action is effective for one cycle only and therefore almost not effective. 0.5: This value has proved useful in practice for controlled systems with one dominant time constant. > 1.0: The greater the coefficient, the longer the effect of the derivative action is delayed. TdFiltRatio is retentive. Retain.CtrlParams.PWeighting REAL 1.0 Active proportional action weighting The proportional action may weaken with changes to the setpoint. Values from 0.0 to 1.0 are applicable. 1.0: Proportional action for setpoint change is fully effective 0.0: Proportional action for setpoint change is not effective The proportional action is always fully effective when the process value is changed. PWeighting is retentive. WinCC Basic V13.0 System Manual, 02/2014 2951 Programming the PLC 9.7 References Tag Data type Default Description Retain.CtrlParams.DWeightin g REAL Active derivative action weighting 1.0 The derivative action may weaken with changes to the setpoint. Values from 0.0 to 1.0 are applicable. 1.0: Derivative action is fully effective upon setpoint change 0.0: Derivative action is not effective upon setpoint change The derivative action is always fully effective when the process value is changed. DWeighting is retentive. Retain.CtrlParams.Cycle REAL 1.0 Active sampling time of PID algorithm in seconds, rounded to an integer multiple of the cycle time of the calling OB. Cycle is retentive. Retain.CtrlParams.InputDead Band REAL 0.0 Deadband width of the control deviation InputDeadBand is retentive. Note Change the tags listed in this table in "Inactive" mode to prevent malfunction of the PID controller. See also Parameters State and Mode V2 (Page 2952) Tag ActivateRecoverMode V2 (Page 2960) Downloading technology objects to device (Page 4223) Parameters State and Mode V2 Correlation of the parameters The State parameter shows the current operating mode of the PID controller. You cannot change the State parameter. With a rising edge at ModeActivate, PID_3Step switches to the operating mode saved in the Mode in-out parameter. When the CPU is switched on or switches from Stop to RUN mode, PID_3Step starts in the operating mode that is saved in the Mode parameter. To leave PID_3Step in "Inactive" mode, set RunModeByStartup = FALSE. 2952 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Meaning of values State Description of operating mode 0 Inactive The controller is switched off and no longer changes the valve position. 1 Pretuning The pretuning determines the process response to a pulse of the output value and searches for the point of inflection. The PID parameters are calculated from the maximum rate of rise and dead time of the controlled system. You obtain the best PID parameters when you perform pretuning and fine tuning. Pretuning requirements: The motor transition time has been configured or measured. Inactive (State = 0), manual mode (State = 4), or automatic mode (State = 3) ManualEnable = FALSE Reset = FALSE The setpoint and the process value lie within the configured limits. The more stable the process value is, the easier it is to calculate the PID parameters and the more precise the result will be. Noise on the process value can be tolerated as long as the rate of rise of the process value is significantly higher as compared to the noise. This is most likely the case in operating modes "Inactive" and "manual mode". The setpoint is frozen in the CurrentSetpoint tag. Tuning is canceled when: Setpoint > CurrentSetpoint + CancelTuningLevel or Setpoint < CurrentSetpoint - CancelTuningLevel Before the PID parameters are recalculated, they are backed up and can be reactivated with LoadBackUp. The controller switches to automatic mode following successful pretuning. If pretuning is unsuccessful, the switchover of operating mode is dependent on ActivateRecoverMode and ErrorBehaviour. The pretuning phase is indicated with the SUT.State tag. WinCC Basic V13.0 System Manual, 02/2014 2953 Programming the PLC 9.7 References State Description of operating mode 2 Fine tuning Fine tuning generates a constant, limited oscillation of the process value. The PID parameters are recalculated based on the amplitude and frequency of this oscillation. PID parameters from fine tuning usually have better master control and disturbance characteristics than PID parameters from pretuning. You obtain the best PID parameters when you perform pretuning and fine tuning. PID_3Step automatically attempts to generate an oscillation greater than the noise of the process value. Fine tuning is only minimally influenced by the stability of the process value. The setpoint is frozen in the CurrentSetpoint tag. Tuning is canceled when: Setpoint > CurrentSetpoint + CancelTuningLevel or Setpoint < CurrentSetpoint - CancelTuningLevel The PID parameters are backed up before fine tuning. They can be reactivated with LoadBackUp. Requirements for fine tuning: The motor transition time has been configured or measured. The setpoint and the process value lie within the configured limits. ManualEnable = FALSE Reset = FALSE Automatic (State = 3), inactive (State = 0) or manual (State = 4) mode Fine tuning proceeds as follows when started from: Automatic mode (State = 3) Start fine tuning from automatic mode if you wish to improve the existing PID parameters through tuning. PID_3Step controls the system using the existing PID parameters until the control loop has stabilized and the requirements for fine tuning have been met. Only then will fine tuning start. Inactive (State = 0) or manual mode (State = 4) If the requirements for pretuning are met, pretuning is started. The determined PID parameters will be used for control until the control loop has stabilized and the requirements for fine tuning have been met. If PIDSelfTune.TIR.RunIn = TRUE, pretuning is skipped and an attempt is made to reach the setpoint with the minimum or maximum output value. This can produce increased overshoot. Fine tuning then starts automatically. The controller switches to automatic mode following successful fine tuning. If fine tuning is unsuccessful, the switchover of operating mode is dependent on ActivateRecoverMode and ErrorBehaviour. The fine tuning phase is indicated with the TIR.State tag. 3 Automatic mode In automatic mode, PID_3Step controls the controlled system in accordance with the parameters specified. The controller switches to automatic mode if one the following requirements is fulfilled: Pretuning successfully completed Fine tuning successfully completed Changing of the Mode in-out parameter to the value 3 and a rising edge at ModeActivate. The switchover from automatic mode to manual mode is only bumpless if carried out in the commissioning editor. The ActivateRecoverMode tag is taken into consideration in automatic mode. 2954 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References State Description of operating mode 4 Manual mode In manual mode, you specify manual output values in the Manual_UP and Manual_DN parameters or ManualValue parameter. Whether or not the actuator can be moved to the output value in the event of an error is described in the ErrorBits parameter. You can also activate this operating mode using ManualEnable = TRUE. We recommend that you change the operating mode using Mode and ModeActivate only. The switchover from manual mode to automatic mode is bumpless. Manual mode is also possible when an error is pending. 5 Approach substitute output value This operating mode is activated in the event of an error, if Errorbehaviour = TRUE and ActivateRecoverMode = FALSE.. PID_3Step moves the actuator to the substitute output value and then switches to "Inactive" mode. 6 Transition time measurement The time that the motor needs to completely open the valve from the closed condition is determined. This operating mode is activated when Mode = 6 and ModeActivate = TRUE is set. If endstop signals are used to measure the transition time, the valve will be opened completely from its current position, closed completely, and opened completely again. If GetTransitTime.InvertDirection = TRUE, this behavior is inverted. If position feedback is used to measure the transition time, the actuator will be moved from its current position to a target position. The output value limits are not taken into consideration during the transition time measurement. The actuator can travel to the high or the low endstop. 7 Error monitoring The control algorithm is switched off and no longer changes the valve position. This operating mode is activated instead of "Inactive" mode in the event of an error. All the following conditions must be met: Automatic mode (Mode = 3) Errorbehaviour = FALSE ActivateRecoverMode = TRUE One or more errors have occurred in which ActivateRecoverMode (Page 2960) is effective. As soon as the errors are no longer pending, PID_3Step switches back to automatic mode. 8 Approach substitute output value with error monitoring This operating mode is activated instead of "approach substitute output value" mode when an error occurs. PID_3Step moves the actuator to the substitute output value and then switches to "error monitoring" mode. All the following conditions must be met: Automatic mode (Mode = 3) Errorbehaviour = TRUE ActivateRecoverMode = TRUE One or more errors have occurred in which ActivateRecoverMode (Page 2960) is effective. As soon as the errors are no longer pending, PID_3Step switches back to automatic mode. 10 Manual mode without endstop signals The endstop signals are not taken into consideration, even though Config.ActuatorEndStopOn = TRUE. The output value limits are not taken into consideration. Otherwise, PID_3Step behaves the same as in manual mode. WinCC Basic V13.0 System Manual, 02/2014 2955 Programming the PLC 9.7 References ENO characteristics If State = 0, then ENO = FALSE. If State 0, then ENO = TRUE. Automatic switchover of operating mode during commissioning Automatic mode is activated following successful pretuning or fine tuning. The following table shows how Mode and State change during successful pretuning. Cycle no. Mode State Action 0 4 4 Set Mode = 1 1 1 4 Set ModeActivate = TRUE 1 4 1 Value of State is saved in Mode parameter Pretuning is started n 4 1 Pretuning successfully completed n 3 3 Automatic mode is started PID_3Step automatically switches the operating mode in the event of an error. The following table shows how Mode and State change during pretuning with errors. Cycle no. Mode State Action 0 4 4 Set Mode = 1 1 1 4 Set ModeActivate = TRUE 1 4 1 Value of State is saved in Mode parameter Pretuning is started n 4 1 Pretuning canceled n 4 4 Manual mode is started If ActivateRecoverMode = TRUE, the operating mode that is saved in the Mode parameter is activated. At the start of transition time measurement, pretuning, or fine tuning, PID_3Step saved the value of State in the Mode in/out parameter. PID_3Step therefore switches to the operating mode from which transition time measurement or tuning was started. If ActivateRecoverMode = FALSE, "Inactive" or "Approach substitute output value" mode is activated. Automatic switchover of operating mode after transition time measurement If ActivateRecoverMode = TRUE, the operating mode that is saved in the Mode parameter is activated after successful transition time measurement. If ActivateRecoverMode = FALSE, the system switches to "Inactive" operating mode after successful transition time measurement. 2956 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Automatic switchover of operating mode in automatic mode PID_3Step automatically switches the operating mode in the event of an error. The following diagram illustrates the influence of ErrorBehaviour and ActivateRecoverMode on this switchover of operating mode. ,QDFWLYH (UURUPRQLWRULQJ (UURU%HKDYLRXU )$/6( $FWLYDWH5HFRYHU0RGH )$/6( (UURU%HKDYLRXU )$/6( $FWLYDWH5HFRYHU0RGH 758( $XWRPDWLFPRGH (UURU%HKDYLRXU 758( $FWLYDWH5HFRYHU0RGH )$/6( (UURU%HKDYLRXU 758( $FWLYDWH5HFRYHU0RGH 758( $SSURDFKVXEVWLWXWHRXWSXWYDOXH $SSURDFKVXEVWLWXWHRXWSXWYDOXH ZLWKHUURUPRQLWRULQJ Automatic switchover of operating mode in the event of an error Automatic switchover of operating mode once the current operation has been completed. Automatic switchover of operating mode when error is no longer pending. See also Tag ActivateRecoverMode V2 (Page 2960) Parameter ErrorBits V2 (Page 2957) Parameter ErrorBits V2 If several errors are pending simultaneously, the values of the ErrorBits are displayed with binary addition. The display of ErrorBits = 0003h, for example, indicates that the errors 0001h and 0002h are pending simultaneously. If there is a position feedback, PID_3Step uses ManualValue as output value in manual mode. The exception is Errorbits = 10000h. WinCC Basic V13.0 System Manual, 02/2014 2957 Programming the PLC 9.7 References ErrorBits Description (DW#16#...) 0000 There is no error. 0001 The "Input" parameter is outside the process value limits. Input > Config.InputUpperLimit or Input < Config.InputLowerLimit If automatic mode was active before the error occurred and ActivateRecoverMode = TRUE, PID_3Step remains in automatic mode. If pretuning, fine tuning, or transition time measurement mode and ActivateRecoverMode = TRUE were active before the error occurred, PID_3Step switches to the operating mode that is saved in the Mode parameter. 0002 Invalid value at "Input_PER" parameter. Check whether an error is pending at the analog input. If automatic mode was active before the error occurred and ActivateRecoverMode = TRUE, PID_3Step switches to "Approach substitute output value with error monitoring" or "Error monitoring" mode. As soon as the error is no longer pending, PID_3Step switches back to automatic mode. If pretuning, fine tuning, or transition time measurement mode and ActivateRecoverMode = TRUE were active before the error occurred, PID_3Step switches to the operating mode that is saved in the Mode parameter. 0004 Error during fine tuning. Oscillation of the process value could not be maintained. If ActivateRecoverMode = TRUE before the error occurred, PID_3Step cancels the tuning and switches to the operating mode that is saved in the Mode parameter. 0010 The setpoint was changed during tuning. You can set the permitted fluctuation of the setpoint at the CancelTuningLevel tag. If ActivateRecoverMode = TRUE before the error occurred, PID_3Step cancels the tuning and switches to the operating mode that is saved in the Mode parameter. 0020 Pretuning is not permitted during fine tuning. If ActivateRecoverMode = TRUE before the error occurred, PID_3Step remains in fine tuning mode. 0080 Error during pretuning. Incorrect configuration of output value limits. Check whether the limits of the output value are configured correctly and match the control logic. If ActivateRecoverMode = TRUE before the error occurred, PID_3Step cancels the tuning and switches to the operating mode that is saved in the Mode parameter. 0100 Error during fine tuning resulted in invalid parameters. If ActivateRecoverMode = TRUE before the error occurred, PID_3Step cancels the tuning and switches to the operating mode that is saved in the Mode parameter. 0200 Invalid value at "Input" parameter: Value has an invalid number format. If automatic mode was active before the error occurred and ActivateRecoverMode = TRUE, PID_3Step switches to "Approach substitute output value with error monitoring" or "Error monitoring" mode. As soon as the error is no longer pending, PID_3Step switches back to automatic mode. If pretuning, fine tuning, or transition time measurement mode and ActivateRecoverMode = TRUE were active before the error occurred, PID_3Step switches to the operating mode that is saved in the Mode parameter. 0400 Calculation of output value failed. Check the PID parameters. If automatic mode was active before the error occurred and ActivateRecoverMode = TRUE, PID_3Step switches to "Approach substitute output value with error monitoring" or "Error monitoring" mode. As soon as the error is no longer pending, PID_3Step switches back to automatic mode. If pretuning, fine tuning, or transition time measurement mode and ActivateRecoverMode = TRUE were active before the error occurred, PID_3Step switches to the operating mode that is saved in the Mode parameter. 2958 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References ErrorBits Description (DW#16#...) 0800 Sampling time error: PID_3Step is not called within the sampling time of the cyclic interrupt OB. If automatic mode was active before the error occurred and ActivateRecoverMode = TRUE, PID_3Step remains in automatic mode. If pretuning, fine tuning, or transition time measurement mode and ActivateRecoverMode = TRUE were active before the error occurred, PID_3Step switches to the operating mode that is saved in the Mode parameter. 1000 Invalid value at "Setpoint" parameter: Value has an invalid number format. If automatic mode was active before the error occurred and ActivateRecoverMode = TRUE, PID_3Step switches to "Approach substitute output value with error monitoring" or "Error monitoring" mode. As soon as the error is no longer pending, PID_3Step switches back to automatic mode. If pretuning, fine tuning, or transition time measurement mode and ActivateRecoverMode = TRUE were active before the error occurred, PID_3Step switches to the operating mode that is saved in the Mode parameter. 2000 Invalid value at Feedback_PER parameter. Check whether an error is pending at the analog input. The actuator cannot be moved to the substitute output value and remains in its current position. In manual mode, you can change the position of the actuator only with Manual_UP and Manual_DN, and not with ManualValue. If automatic mode was active before the error occurred, ActivateRecoverMode = TRUE, and the error is no longer pending, PID_3Step switches back to automatic mode. If pretuning, fine tuning, or transition time measurement mode and ActivateRecoverMode = TRUE were active before the error occurred, PID_3Step switches to the operating mode that is saved in the Mode parameter. 4000 Invalid value at Feedback parameter. Value has an invalid number format. The actuator cannot be moved to the substitute output value and remains in its current position. In manual mode, you can change the position of the actuator only with Manual_UP and Manual_DN, and not with ManualValue. If automatic mode was active before the error occurred, ActivateRecoverMode = TRUE, and the error is no longer pending, PID_3Step switches back to automatic mode. If pretuning, fine tuning, or transition time measurement mode and ActivateRecoverMode = TRUE were active before the error occurred, PID_3Step switches to the operating mode that is saved in the Mode parameter. 8000 Error during digital position feedback. Actuator_H = TRUE and Actuator_L = TRUE. The actuator cannot be moved to the substitute output value and remains in its current position. Manual mode is not possible in this state. In order to move the actuator from this state, you must deactivate the "Actuator endstop" (Config.ActuatorEndStopOn = FALSE) or switch to manual mode without endstop signals (Mode = 10). If automatic mode was active before the error occurred, ActivateRecoverMode = TRUE, and the error is no longer pending, PID_3Step switches back to automatic mode. If pretuning, fine tuning, or transition time measurement mode and ActivateRecoverMode = TRUE were active before the error occurred, PID_3Step switches to the operating mode that is saved in the Mode parameter. 10000 Invalid value at ManualValue parameter. Value has an invalid number format. The actuator cannot be moved to the manual value and remains in its current position. Specify a valid value in ManualValue or move the actuator in manual mode with Manual_UP and Manual_DN. WinCC Basic V13.0 System Manual, 02/2014 2959 Programming the PLC 9.7 References ErrorBits Description (DW#16#...) 20000 Invalid value at SavePosition tag. Value has an invalid number format. The actuator cannot be moved to the substitute output value and remains in its current position. 40000 Invalid value at Disturbance parameter. Value has an invalid number format. If automatic mode was active and ActivateRecoverMode = TRUE before the error occurred, Disturbance is set to zero. PID_3Step remains in automatic mode. If pretuning or fine tuning mode was active and ActivateRecoverMode = TRUE before the error occurred, PID_3Step switches to the operating mode saved in the Mode parameter. If Disturbance in the current phase has no effect on the output value, tuning is not be canceled. The error has no effect during transition time measurement. Tag ActivateRecoverMode V2 The ActivateRecoverMode tag determines the reaction to error. The Error parameter indicates if an error is pending. When the error is no longer pending, Error = FALSE. The ErrorBits parameter shows which errors have occurred. NOTICE Your system may be damaged. If ActivateRecoverMode = TRUE, PID_3Step remains in automatic mode even if the process limit values are exceeded. This may damage your system. It is essential to configure how your controlled system reacts in the event of an error to protect your system from damage. 2960 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Automatic mode ActivateRecover Description Mode FALSE In the event of an error, PID_3Step switches to "Inactive" or "Approach substitute output value" mode. The controller is only activated by a falling edge at Reset or a rising edge at ModeActivate. TRUE If errors occur frequently in automatic mode, this setting has a negative effect on the control response, because PID_3Step switches between the calculated output value and the substitute output value at each error. In this case, check the ErrorBits parameter and eliminate the cause of the error. If one or more of the following errors occur, PID_3Step stays in automatic mode: 0001h: The "Input" parameter is outside the process value limits. 0800h: Sampling time error 40000h: Invalid value at Disturbance parameter. If one or more of the following errors occur, PID_3Step switches to "Approach substitute output value with error monitoring" or "Error monitoring" mode: 0002h: Invalid value at Input_PER parameter. 0200h: Invalid value at Input parameter. 0400h: Calculation of output value failed. 1000h: Invalid value at Setpoint parameter. If one or more of the following errors occur, PID_3Step can no longer move the actuator: 2000h: Invalid value at Feedback_PER parameter. 4000h: Invalid value at Feedback parameter. 8000h: Error during digital position feedback. 20000h: Invalid value at SavePosition tag. Value has an invalid number format. The characteristics are independent of ErrorBehaviour. As soon as the errors are no longer pending, PID_3Step switches back to automatic mode. Pretuning, fine tuning, and transition time measurement ActivateRecover Description Mode FALSE In the event of an error, PID_3Step switches to "Inactive" or "Approach substitute output value" mode. The controller is only activated by a falling edge at Reset or a rising edge at ModeActivate. The controller changes to "Inactive" mode after successful transition time measurement. TRUE If the following error occurs, PID_3Step remains in the active mode: 0020h: Pretuning is not permitted during fine tuning. The following errors are ignored: 10000h: Invalid value at ManualValue parameter. 20000h: Invalid value at SavePosition tag. When any other error occurs, PID_3Step cancels the tuning and switches to the mode from which tuning was started. Manual mode ActivateRecoverMode is not effective in manual mode. WinCC Basic V13.0 System Manual, 02/2014 2961 Programming the PLC 9.7 References See also Static tags of PID_3Step V2 (Page 2944) Parameters State and Mode V2 (Page 2952) Tag Warning V2 If several warnings are pending simultaneously, their values are displayed with binary addition. The display of warning 0005h, for example, indicates that the warnings 0001h and 0004h are pending simultaneously. Warning Description (DW#16#...) 0000 No warning pending. 0001 The point of inflection was not found during pretuning. 0004 The setpoint was limited to the configured limits. 0008 Not all the necessary controlled system properties were defined for the selected method of calculation. Instead, the PID parameters were calculated using the TIR.TuneRule = 3 method. 0010 The operating mode could not be changed because Reset = TRUE or ManualEnable = TRUE. 0020 The cycle time of the calling OB limits the sampling time of the PID algorithm. Improve results by using shorter OB cycle times. 0040 The process value exceeded one of its warning limits. 0080 Invalid value at Mode. The operating mode is not switched. 0100 The manual value was limited to the limits of the controller output. 0200 The specified rule for tuning is not supported. No PID parameters are calculated. 0400 The transition time cannot be measured because the actuator settings do not match the selected measuring method. 0800 The difference between the current position and the new output value is too small for transition time measurement. This can produce incorrect results. The difference between the current output value and new output value must be at least 50% of the entire control range. 1000 The substitute output value cannot be reached because it is outside the output value limits. 2000 The actuator was moved in one direction for longer than Config.VirtualActuatorLimit x Retain.TransitTime. Check whether the actuator has reached an endstop signal. The following warnings are deleted as soon as the cause is eliminated: 0001h 0004h 0008h 0040h 0100h 2000h All other warnings are cleared with a rising edge at Reset or ErrorAck. 2962 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References PID_3Step V1 Description PID_3Step V1 Description You use the PID_3Step instruction to configure a PID controller with self tuning for valves or actuators with integrating behavior. The following operating modes are possible: Inactive Pretuning Fine tuning Automatic mode Manual mode Approach substitute output value Transition time measurement Approach substitute output value with error monitoring Error monitoring For a more detailed description of the operating modes, see the State parameter. WinCC Basic V13.0 System Manual, 02/2014 2963 Programming the PLC 9.7 References PID algorithm PID_3Step is a PIDT1 controller with anti-windup and weighting of the proportional and derivative actions. The following equation is used to calculate the output value. 1 [ y = K p * s * (b * w - x) + Symbol 2964 TI * s (w - x) + TD * s a * TD * s + 1 (c * w - x) ] Description y Output value Kp Proportional gain s Laplace operator b Proportional action weighting w Setpoint x Process value TI Integral action time a Derivative delay coefficient (T1 = a x TD) TD Derivative action time c Derivative action weighting WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Block diagram without position feedback ,QSXW:DUQLQJB+ 39B$/50 ,QSXW:DUQLQJB/ ,QSXW3HU2Q ,QSXWB3(5 &53B,1 )DF ,QSXW 6HWSRLQW $QWL:LQGXS 6FDOH ,QW 3,'7 $QWL:LQGXS Y /LPLW 2XWSXW3HU2Q 0DQXDO(QDEOH 0DQXDO9DOXH )$& 5RFB/LP 2XWSXW3HU2Q &53B287 /LPLW 2XWSXWB3(5 $GHDGB% 0DQXDO(QDEOH 0DQXDOB83 7KU6WS 0DQXDOB'1 2XWSXWB83 3XOVH2XW 2XWSXWB'1 WinCC Basic V13.0 System Manual, 02/2014 2965 Programming the PLC 9.7 References Block diagram with position feedback 39B$/50 ,QSXW:DUQLQJB+ ,QSXW:DUQLQJB/ ,QSXW3HU2Q ,QSXWB3(5 ,QW ,QSXW 6HWSRLQW $QWL:LQGXS 6FDOH &53B,1 /LPLW 3,'7 $QWL:LQGXS )DF /LPLW ; 0DQXDO(QDEOH 9 0DQXDO9DOXH )HHGEDFN3HU2Q )HHGEDFNB3(5 6FDOH &53B,1 )HHGEDFN 2XWSXW3HU2Q &53B287 0DQXDO(QDEOH 0DQXDOB83 $GHDGB% 2XWSXWB3(5 7KU6WS 0DQXDOB'1 3XOVH2XW 2XWSXWB83 2XWSXWB'1 2966 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Block diagram of PIDT1 with anti-windup E 6HWSRLQW Z '7 F ' . 3 \ 'HDGB% , 7L 6FDOHG,QSXW [ )DF7W $QWL:LQGXS Call PID_3Step is called in a constant time interval of the cycle time of the calling OB (preferably in a cyclic interrupt OB). Download to device The actual values of retentive tags are only updated when you download PID_3Step completely. Downloading technology objects to device (Page 4223) Startup At the startup of the CPU, PID_3Step starts in the operating mode that was last active. To leave PID_3Step in "Inactive" mode, set RunModeByStartup = FALSE. Reaction to error If errors occur, these are output in the Error parameter. You configure the reaction of PID_3Step using the ErrorBehaviour and ActivateRecoverMode tags. WinCC Basic V13.0 System Manual, 02/2014 ErrorBeha viour ActivateRecov Actuator setting configuration Reaction erMode Set Output to 0 FALSE Current output value Switch to "Inactive" mode (Mode = 0) 0 TRUE Current output value while error is pending Switch to "Error monitoring" mode (Mode = 7) 2967 Programming the PLC 9.7 References ErrorBeha viour ActivateRecov Actuator setting configuration Reaction erMode Set Output to 1 FALSE Substitute output value Switch to "Approach substitute output value" mode (Mode = 5) Switch to "Inactive" mode (Mode = 0) 1 TRUE Substitute output value while error is pending Switch to "Approach substitute output value with error monitoring" mode (Mode = 8) Switch to "Error monitoring" mode (Mode = 7) The ErrorBits parameter shows which errors have occurred. See also Parameter State and Retain.Mode V1 (Page 2980) Parameter ErrorBits V1 (Page 2987) Configuring PID_3Step V1 (Page 4294) Operating principle PID_3Step V1 Monitoring process value limits You specify the high limit and low limit of the process value in the Config.InputUpperLimit and Config.InputLowerLimit tags. If the process value is outside these limits, an error occurs (ErrorBits = 0001hex). You specify a high and low warning limit of the process value in the Config.InputUpperWarning and Config.InputLowerWarning tags. If the process value is outside these warning limits, a warning occurs (Warnings = 0040hex), and the InputWarning_H or InputWarning_L output parameter changes to TRUE. Limiting the setpoint You specify a high limit and low limit of the setpoint in the Config.SetpointUpperLimit and Config.SetpointLowerLimit tags. PID_3Step automatically limits the setpoint to the process value limits. You can limit the setpoint to a smaller range. PID_3Step checks whether this range falls within the process value limits. If the setpoint is outside these limits, the high or low limit is used as the setpoint, and output parameter SetpointLimit_H or SetpointLimit_L is set to TRUE. The setpoint is limited in all operating modes. 2968 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Limiting the output value You specify a high limit and low limit of the output value in the Config.OutputUpperLimit and Config.OutputLowerLimit tags. The output value limits must be within "Low endstop" and "High endstop". High endstop: Config.FeedbackScaling.UpperPointOut Low endstop: Config.FeedbackScaling.LowerPointOut Rule: UpperPointOut OutputUpperLimit > OutputLowerLimit LowerPointOut The valid values for "High endstop" and "Low endstop" depend upon: FeedbackOn FeedbackPerOn OutputPerOn OutputPerOn FeedbackOn FeedbackPerOn LowerPointOut UpperPointOut FALSE FALSE FALSE Cannot be set (0.0%) Cannot be set (100.0%) FALSE TRUE FALSE -100.0% or 0.0% 0.0% or +100.0% FALSE TRUE TRUE -100.0% or 0.0% 0.0% or +100.0% TRUE FALSE FALSE Cannot be set (100.0%) Cannot be set (100.0%) TRUE TRUE FALSE -100.0% or 0.0% 0.0% or +100.0% TRUE TRUE TRUE -100.0% or 0.0% 0.0% or +100.0% If OutputPerOn = FALSE and FeedbackOn = FALSE, you cannot limit the output value. The digital outputs are reset with Actuator_H = TRUE or Actuator_L = TRUE, or after a travel time amounting to 110% of the motor transition time. The output value is 27648 at 100% and -27648 at -100%. PID_3Step must be able to close the valve completely. Therefore, zero must be included in the output value limits. Substitute output value If an error has occurred, PID_3Step can output a substitute output value and move the actuator to a safe position that is specified in the SavePosition tag. The substitute output value must be within the output value limits. Monitoring signal validity The values of the following parameters are monitored for validity: Setpoint Input Input_PER Feedback Feedback_PER Output WinCC Basic V13.0 System Manual, 02/2014 2969 Programming the PLC 9.7 References Monitoring the PID_3Step sampling time Ideally, the sampling time is equivalent to the cycle time of the calling OB. The PID_3Step instruction measures the time interval between two calls. This is the current sampling time. On every switchover of operating mode and during the initial startup, the mean value is formed from the first 10 sampling times. Too great a difference between the current sampling time and this mean value triggers an error (ErrorBits = 0800 hex). PID_3Step is set to "Inactive" mode during tuning under the following conditions: New mean value >= 1.1 x old mean value New mean value <= 0.9 x old mean value In automatic mode, PID_3Step is set to "Inactive" mode under the following conditions: New mean value >= 1.5 x old mean value New mean value <= 0.5 x old mean value Sampling time of the PID algorithm The controlled system needs a certain amount of time to respond to changes in the output value. It is therefore not advisable to calculate the output value in every cycle. The sampling time of the PID algorithm represents the time between two calculations of the output value. It is calculated during tuning and rounded to a multiple of the cycle time. All other functions of PID_3Step are executed at every call. Measuring the motor transition time The motor transition time is the time in seconds the motor requires to move the actuator from the closed to the opened state. The maximum time that the actuator is moved in one direction is 110% of the motor transition time. PID_3Step requires the motor transition time to be as accurate as possible for good controller results. The data in the actuator documentation contains average values for this type of actuator. The value for the specific actuator used may differ. You can measure the motor transition time during commissioning. The output value limits are not taken into consideration during the motor transition time measurement. The actuator can travel to the high or the low endstop. Control logic An increase of the output value is generally intended to cause an increase in the process value. This is referred to as a normal control logic. For cooling and discharge control systems, it may be necessary to invert the control logic. PID_3Step does not work with negative proportional gain. If InvertControl = TRUE, an increasing control deviation causes a reduction in the output value. The control logic is also taken into account during pretuning and fine tuning. See also Configuring PID_3Step V1 (Page 4294) 2970 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References PID_3Step V1 input parameters Table 9-89 Parameters Data type Default Description Setpoint REAL 0.0 Setpoint of the PID controller in automatic mode Input REAL 0.0 A variable of the user program is used as source for the process value. If you are using parameter Input, then Config.InputPerOn = FALSE must be set. Input_PER WORD W#16#0 An analog input is used as source for the process value. If you are using parameter Input_PER, then Config.InputPerOn = TRUE must be set. Actuator_H BOOL FALSE Digital position feedback of the valve for the high endstop If Actuator_H = TRUE, the valve is at the high endstop and is no longer moved towards this direction. Actuator_L BOOL FALSE Digital position feedback of the valve for the low endstop If Actuator_L = TRUE, the valve is at the low endstop and is no longer moved towards this direction. Feedback REAL 0.0 Position feedback of the valve If you are using parameter Feedback, then Config.FeedbackPerOn = FALSE must be set. Feedback_PER WORD W#16#0 Analog feedback of the valve position If you are using parameter Feedback_PER, then Config.FeedbackPerOn = TRUE must be set. Feedback_PER is scaled based on the variables: Config.FeedbackScaling.LowerPointIn Config.FeedbackScaling.UpperPointIn Config.FeedbackScaling.LowerPointOut Config.FeedbackScaling.UpperPointOut ManualEnable BOOL FALSE A FALSE -> TRUE edge selects "Manual mode", while State = 4, Retain.Mode remains unchanged. A TRUE -> FALSE edge selects the most recently active operating mode A change of Retain.Mode will not take effect during ManualEnable = TRUE. The change of Retain.Mode will only be considered upon a TRUE -> FALSE edge at ManualEnable . PID_3Step V1.1If at start of the CPU ManualEnable = TRUE, PID_3Step starts in manual mode. A rising edge (FALSE > TRUE) at ManualEnable is not necessary. PID_3Step V1.0 At the start of the CPU, PID_3Step only switches to manual mode with a rising edge (FALSE->TRUE) at ManualEnable . Without rising edge, PID_3Step starts in the last operating mode in which ManualEnable was FALSE. ManualValue WinCC Basic V13.0 System Manual, 02/2014 REAL 0.0 In manual mode, you specify the absolute position of the valve. ManualValue will only be evaluated if you are using OutputPer, or if position feedback is available. 2971 Programming the PLC 9.7 References Parameters Data type Default Description Manual_UP BOOL FALSE In manual mode, every rising edge opens the valve by 5% of the total control range, or for the duration of the minimum motor transition time. Manual_UP is evaluated only if you are not using Output_PER and there is no position feedback available. Manual_DN BOOL FALSE In manual mode, every rising edge closes the valve by 5% of the total control range, or for the duration of the minimum motor transition time. Manual_DN is evaluated only if you are not using Output_PER and there is no position feedback available. Reset BOOL FALSE Restarts the controller. FALSE -> TRUE edge - Change to "Inactive" mode - Intermediate controller values are reset (PID parameters are retained) TRUE -> FALSE edge Change in most recent active mode PID_3Step V1 output parameters Table 9-90 Parameter Data type Default Description ScaledInput REAL 0.0 Scaled process value ScaledFeedback REAL 0.0 Scaled position feedback For an actuator without position feedback, the position of the actuator indicated by ScaledFeedback is very imprecise. ScaledFeedback may only be used for rough estimation of the current position in this case. Output_UP BOOL FALSE Digital output value for opening the valve If Config.OutputPerOn = FALSE, the Output_UP parameter is used. Output_DN BOOL FALSE Digital output value for closing the valve If Config.OutputPerOn = FALSE, the Output_DN parameter is used. Output_PER WORD W#16#0 SetpointLimit_H BOOL FALSE Analog output value If Config.OutputPerOn = TRUE, Output_PER is used. If SetpointLimit_H = TRUE, the absolute setpoint high limit is reached. In the CPU, the setpoint is limited to the configured absolute setpoint high limit. The configured absolute process value high limit is the default for the setpoint high limit. If you configure Config.SetpointUpperLimit to a value within the process value limits, this value is used as the setpoint high limit. SetpointLimit_L BOOL FALSE If SetpointLimit_L = TRUE, the absolute setpoint low limit has been reached. In the CPU, the setpoint is limited to the configured absolute setpoint low limit. The configured absolute process value low limit is the default setting for the setpoint low limit. If you configure Config.SetpointLowerLimit to a value within the process value limits, this value is used as the setpoint low limit. 2972 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameter Data type Default Description InputWarning_H BOOL FALSE If InputWarning_H = TRUE, the process value has reached or exceeded the warning high limit. InputWarning_L BOOL FALSE If InputWarning_L = TRUE, the process value has reached or fallen below the warning low limit. State INT 0 The State parameter (Page 2980) shows the current operating mode of the PID controller. You change the operating mode with the Retain.Mode tag. State = 0: Inactive State = 1: Pretuning State = 2: Fine tuning State = 3: Automatic mode State = 4: Manual mode State = 5: Approach substitute output value State = 6: Transition time measurement State = 7: Error monitoring State = 8: Approach substitute output value with error monitoring Error BOOL FALSE If Error = TRUE, at least one error message is pending. ErrorBits DWORD DW#16#0 The ErrorBits parameter (Page 2987) indicates the error messages. See also Parameter State and Retain.Mode V1 (Page 2980) Parameter ErrorBits V1 (Page 2987) PID_3Step V1 static tags You must not change tags that are not listed. These are used for internal purposes only. Table 9-91 Tag Data type Default Description ActivateRecoverMode BOOL TRUE The ActivateRecoverMode tag (Page 2988) determines the reaction to error. RunModeByStartup BOOL TRUE Activate Mode after CPU restart If RunModeByStartup = TRUE, the controller returns to the last active operating mode after a CPU restart. If RunModeByStartup = FALSE, the controller remains inactive after a CPU restart. PhysicalUnit INT 0 Unit of measurement of the process value and setpoint, e.g., C, or F. PhysicalQuantity INT 0 Physical quantity of the process value and setpoint, e.g., temperature. WinCC Basic V13.0 System Manual, 02/2014 2973 Programming the PLC 9.7 References Tag Data type Default Description ErrorBehaviour INT If ErrorBehaviour = 0 and an error has occurred, the valve stays at its current position and the controller switches directly to "Inactive" or "Error monitoring" mode. 0 If ErrorBehaviour = 1 and an error occurs, the actuator moves to the substitute output value and only then switches to "Inactive" or "Error monitoring" mode. If the following errors occur, you can no longer move the valve to a configured substitute output value. 2000h: Invalid value at Feedback_PER parameter. 4000h: Invalid value at Feedback parameter. 8000h: Error during digital position feedback. Warning DWORD DW#16# 0 The Warning tag (Page 2980) displays the warnings generated since a Reset or since the last switchover of operating mode. Cyclic warnings (for example, process value warning) are shown until the cause of the warning is removed. They are automatically deleted once their cause has gone. Non-cyclic warnings (for example, point of inflection not found) remain and are deleted like errors. SavePosition REAL 0.0 Substitute output value If ErrorBehaviour = 1 and an error occurs, the actuator moves to a safe position for the plant and only then switches to "Inactive" mode. CurrentSetpoint REAL 0.0 Currently active setpoint. This value is frozen at the start of tuning. Progress REAL 0.0 Progress of tuning as a percentage (0.0 - 100.0) Config.InputPerOn BOOL TRUE If InputPerOn = TRUE, the Input_PER parameter is used. If InputPerOn = FALSE, the Input parameter is used. Config.OutputPerOn BOOL FALSE If OutputPerOn = TRUE, the Output_PER parameter is used. If OutputPerOn = FALSE, the Ouput_UP and Output_DN parameters are used. Config.LoadBackUp BOOL FALSE If LoadBackUp = TRUE, the last set of PID parameters is reloaded. This set was saved prior to the last tuning operation. LoadBackUp is automatically reset to FALSE. Config.InvertControl BOOL FALSE Invert control logic If InvertControl = TRUE, an increasing control deviation causes a reduction in the output value. Config.FeedbackOn BOOL FALSE If FeedbackOn = FALSE, a position feedback is simulated. Position feedback is generally activated when FeedbackOn = TRUE. Config.FeedbackPerOn BOOL FALSE FeedbackPerOn is only effective when FeedbackOn = TRUE. If FeedbackPerOn = TRUE, the analog input is used for the position feedback (Feedback_PER parameter). If FeedbackPerOn = FALSE, the Feedback parameter is used for the position feedback. Config.ActuatorEndStopOn 2974 BOOL FALSE If ActuatorEndStopOn = TRUE, the digital position feedback Actuator_L and Actuator_H are taken into consideration. WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Tag Data type Default Description Config.InputUpperLimit REAL High limit of the process value 120.0 At the I/O input, the process value can be a maximum of 18% higher than the standard range (overrange). An error is no longer signaled due to a violation of the "Process value high limit". Only a wire-break and a short-circuit are recognized and PID_3Step reacts according to the configured reaction to error. InputUpperLimit > InputLowerLimit Config.InputLowerLimit REAL 0.0 Low limit of the process value Config.InputUpperWarning REAL +3.40282 Warning high limit of the process value 2e+38 If you set InputUpperWarning outside the process value limits, the configured absolute process value high limit is used as the warning high limit. InputLowerLimit < InputUpperLimit If you configure InputUpperWarning within the process value limits, this value is used as the warning high limit. InputUpperWarning > InputLowerWarning InputUpperWarning InputUpperLimit Config.InputLowerWarning REAL -3.40282 2e+38 Warning low limit of the process value If you set InputLowerWarning outside the process value limits, the configured absolute process value low limit is used as the warning low limit. If you configure InputLowerWarning within the process value limits, this value is used as the warning low limit. InputLowerWarning < InputUpperWarning InputLowerWarning InputLowerLimit Config.OutputUpperLimit REAL 100.0 High limit of output value For details, see OutputLowerLimit Config.OutputLowerLimit REAL 0.0 Low limit of output value If OutputPerOn = TRUE or FeedbackOn = TRUE, the range of values from -100% to +100%, including zero, is valid. At -100%, Output = -27648; at +100%, Output = 27648 If OutputPerOn = FALSE, the range of values from 0% to 100% is valid. The valve is completely closed at 0% and completely opened at 100%. Config.SetpointUpperLimit REAL +3.40282 High limit of setpoint 2e+38 If you set SetpointUpperLimit outside the process value limits, the configured absolute process value high limit is preassigned as the setpoint high limit. If you configure SetpointUpperLimit within the process value limits, this value is used as the setpoint high limit. Config.SetpointLowerLimit REAL Low limit of the setpoint 3.402822 If you set SetpointLowerLimit outside the process value limits, the e+38 configured absolute process value low limit is preassigned as the setpoint low limit. If you set SetpointLowerLimit within the process value limits, this value is used as the setpoint low limit. WinCC Basic V13.0 System Manual, 02/2014 2975 Programming the PLC 9.7 References Tag Data type Default Description Config.MinimumOnTime REAL Minimum ON time 0.0 Minimum time in seconds for which the servo drive must be switched on. Config.MinimumOffTime REAL 0.0 Minimum OFF time Minimum time in seconds for which the servo drive must be switched off. Config.TransitTime REAL 30.0 Motor transition time Time in seconds the actuating drive requires to move the valve from the closed to the opened state. Config.InputScaling.UpperPoi ntIn REAL Config.InputScaling.LowerPoi ntIn REAL Config.InputScaling.UpperPoi ntOut REAL Config.InputScaling.LowerPoi ntOut REAL 27648.0 Scaling Input_PER high Input_PER is converted to a percentage based on the two value pairs UpperPointOut, UpperPointIn and LowerPointOut, LowerPointIn of the InputScaling structure. 0.0 Scaling Input_PER low Input_PER is converted to a percentage based on the two value pairs UpperPointOut, UpperPointIn and LowerPointOut, LowerPointIn of the InputScaling structure. 100.0 Scaled high process value Input_PER is converted to a percentage based on the two value pairs UpperPointOut, UpperPointIn and LowerPointOut, LowerPointIn of the InputScaling structure. 0.0 Scaled low process value Input_PER is converted to a percentage based on the two value pairs UpperPointOut, UpperPointIn and LowerPointOut, LowerPointIn of the InputScaling structure. Config.FeedbackScaling.Uppe REAL rPointIn 27648.0 Config.FeedbackScaling.Lowe REAL rPointIn 0.0 Config.FeedbackScaling.Uppe REAL rPointOut 100.0 Config.FeedbackScaling.Lowe REAL rPointOut 0.0 GetTransitTime.InvertDirectio n FALSE BOOL Scaling Feedback_PER high Feedback_PER is converted to a percentage based on the two value pairs UpperPointOut, UpperPointIn and LowerPointOut, LowerPointIn of the FeedbackScaling structure. Scaling Feedback_PER low Feedback_PER is converted to a percentage based on the two value pairs UpperPointOut, UpperPointIn and LowerPointOut, LowerPointIn of the FeedbackScaling structure. High endstop Feedback_PER is converted to a percentage based on the two value pairs UpperPointOut, UpperPointIn and LowerPointOut, LowerPointIn of the FeedbackScaling structure. Low endstop Feedback_PER is converted to a percentage based on the two value pairs UpperPointOut, UpperPointIn and LowerPointOut, LowerPointIn of the FeedbackScaling structure. If InvertDirection = FALSE, the valve is fully opened, closed, and then reopened in order to determine the valve transition time. If InvertDirection = TRUE, the valve is fully closed, opened, and then closed again. 2976 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Tag Data type Default Description GetTransitTime.SelectFeedba ck BOOL If SelectFeedback = TRUE, then Feedback_PER, or Feedback is taken into consideration in the transition time measurement. FALSE If SelectFeedback = FALSE, then Actuator_H and Actuator_L are taken into consideration in the transition time measurement. GetTransitTime.Start BOOL FALSE If Start = TRUE, the transition time measurement is started. GetTransitTime.State INT 0 Current phase of the transition time measurement State = 0: Inactive State = 1: Open valve completely State = 2: Close valve completely State = 3: Move valve to target position (NewOutput) State = 4: Transition time measurement successfully completed State = 5: Transition time measurement canceled GetTransitTime.NewOutput REAL 0.0 Target position for transition time measurement with position feedback The target position must be between "High endstop" and "Low endstop". The difference between NewOutput and ScaledFeedback must be at least 50% of the permissible control range. CycleTime.StartEstimation BOOL TRUE If StartEstimation = TRUE, the measurement of the PID_3Step sampling time is started. CycleTime.StartEstimation = FALSE once measurement is complete. CycleTime.EnEstimation BOOL TRUE If EnEstimation = TRUE, the PID_3Step sampling time is calculated. CycleTime.EnMonitoring BOOL TRUE If EnMonitoring = TRUE, the PID_3Step sampling time is monitored. If it is not possible to execute PID_3Step within the sampling time, the error 0800h is output and the operating mode is switched. ActivateRecoverMode and ErrorBehaviour determine which operating mode is switched to. If EnMonitoring = FALSE, the PID_3Step sampling time is not monitored, the error 0800h is not output, and the operating mode is not switched. CycleTime.Value REAL 0.1 PID_3Step sampling time in seconds CycleTime.Value is determined automatically and is usually equivalent to the cycle time of the calling OB. CtrlParamsBackUp.SetByUser BOOL FALSE Saved value of Retain.CtrlParams.SetByUser. You can reload values from the CtrlParamsBackUp structure with Config.LoadBackUp = TRUE. CtrlParamsBackUp.Gain REAL 1.0 Saved proportional gain CtrlParamsBackUp.Ti REAL 20.0 Saved integral action time CtrlParamsBackUp.Td REAL 0.0 Saved derivative action time CtrlParamsBackUp.TdFiltRati o REAL 0.0 Saved derivative delay coefficient CtrlParamsBackUp.PWeightin g REAL 0.0 Saved proportional action weighting CtrlParamsBackUp.DWeightin REAL g 0.0 Saved derivative action weighting CtrlParamsBackUp.Cycle REAL 1.0 Saved sampling time of PID algorithm CtrlParamsBackUp.InputDead REAL Band 0.0 Saved dead band width of the control deviation WinCC Basic V13.0 System Manual, 02/2014 2977 Programming the PLC 9.7 References Tag Data type Default Description PIDSelfTune.SUT.CalculateS UTParams BOOL FALSE The properties of the controlled system are saved during tuning. If CalculateSUTParams = TRUE, the PID parameters are recalculated on the basis of these properties. The PID parameters are calculated using the method set in TuneRuleSUT. CalculateSUTParams is set to FALSE following calculation. PIDSelfTune.SUT.TuneRuleS UT INT 1 Methods used to calculate parameters during pretuning: TuneRuleSUT = 0: PID rapid I TuneRuleSUT = 1: PID slow I TuneRuleSUT = 2: Chien, Hrones and Reswick PID TuneRuleSUT = 3TuneRuleSUT = 3: Chien, Hrones, Reswick PI TuneRuleSUT = 4: PID rapid II TuneRuleSUT = 5: PID slow II PIDSelfTune.SUT.State INT 0 The SUT.State tag indicates the current phase of pretuning: PIDSelfTune.TIR.RunIn BOOL FALSE RunIn = FALSE Pretuning is started when fine tuning is started from inactive or manual mode. If fine tuning is started from automatic mode, the system uses the existing PID parameters to control to the setpoint. Only then will fine tuning start. If pretuning is not possible, PID_3Step switches to "Inactive" mode. RunIn = TRUE The pretuning is skipped. PID_3Step attempts to reach the setpoint with the minimum or maximum output value. This can produce increased overshoot. Only then will fine tuning start. RunIn is set to FALSE after fine tuning. PIDSelfTune.TIR.CalculateTI RParams BOOL FALSE The properties of the controlled system are saved during tuning. If CalculateTIRParams = TRUE, the PID parameters are recalculated on the basis of these properties. The PID parameters are calculated using the method set in TuneRuleTIR. CalculateTIRParams is set to FALSE following calculation. PIDSelfTune.TIR.TuneRuleTI R INT 0 Methods used to calculate parameters during fine tuning: TuneRuleTIR = 0: PID automatic TuneRuleTIR = 1: PID rapid TuneRuleTIR = 2: PID slow TuneRuleTIR = 3: Ziegler-Nichols PID TuneRuleTIR = 4: Ziegler-Nichols PI TuneRuleTIR = 5: Ziegler-Nichols P PIDSelfTune.TIR.State 2978 INT 0 The TIR.State tag indicates the current phase of "fine tuning": WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Tag Data type Default Description Retain.Mode INT A change to the value of Retain.Mode initiates a switch to another operating mode. 0 The following operating mode is enabled upon a change of Mode to: Mode = 0: Inactive Mode = 1: Pretuning Mode = 2: Fine tuning Mode = 3: Automatic mode Mode = 4: Manual mode Mode = 5: Approach substitute output value Mode = 6: Transition time measurement Mode = 7Mode = 7: Error monitoring Mode = 8: Approach substitute output value with error monitoring Mode is retentive. Retain.CtrlParams.SetByUser BOOL FALSE If SetByUser = FALSE, the PID parameters are determined automatically and PID_3Step operates with a dead band at the output value. The dead band width is calculated during tuning on the basis of the standard deviation of the output value and saved in Retain.CtrlParams.OutputDeadBand. If SetByUser = TRUE, the PID parameters are entered manually and PID_3 Step operates without a dead band at the output value. Retain.CtrlParams.OutputDeadBand = 0.0 SetByUser is retentive. Retain.CtrlParams.Gain REAL 1.0 Retain.CtrlParams.Ti REAL 20.0 Active proportional gain Gain is retentive. Ti > 0.0: Active integral action time Ti = 0.0: Integral action is deactivated Ti is retentive. Retain.CtrlParams.Td REAL 0.0 Td > 0.0: Active derivative action time Td = 0.0: Derivative action is deactivated Td is retentive. Retain.CtrlParams.TdFiltRatio REAL 0.0 Active derivative delay coefficient TdFiltRatio is retentive. Retain.CtrlParams.PWeighting REAL 0.0 Active proportional action weighting PWeighting is retentive. Retain.CtrlParams.DWeightin g REAL Retain.CtrlParams.Cycle REAL 0.0 Active derivative action weighting DWeighting is retentive. 1.0 Active sampling time of PID algorithm in seconds, rounded to an integer multiple of the cycle time of the calling OB. Cycle is retentive. Retain.CtrlParams.InputDead Band WinCC Basic V13.0 System Manual, 02/2014 REAL 0.0 Dead band width of the control deviation InputDeadBand is retentive. 2979 Programming the PLC 9.7 References Note Change the tags listed in this table in "Inactive" mode to prevent malfunction of the PID controller. "Inactive" mode is forced by setting the "Retain.Mode" tag to "0". See also Parameter State and Retain.Mode V1 (Page 2980) Tag ActivateRecoverMode V1 (Page 2988) Downloading technology objects to device (Page 4223) Parameter State and Retain.Mode V1 Correlation of the parameters The State parameter shows the current operating mode of the PID controller. You cannot change the State parameter. To switch from one operating mode to another, you must change the Retain.Mode tag. This also applies when the value for the new operating mode is already in Retain.Mode. For example, set Retain.Mode = 0 first and then Retain.Mode = 3. Provided the current operating mode of the controller permits this switchover, State will be set to the value of Retain.Mode. When PID_3Step automatically switches from one operating mode to another, the following applies: State != Retain.Mode. Examples: After successful pretuning State = 3 and Retain.Mode = 1 In the event of an error State = 0 and Retain.Mode remain at the previous value, for example, Retain.Mode = 3 ManualEnalbe = TRUE State = 4 and Retain.Mode remain at the previous value, e.g., Retain.Mode = 3 Note You want, for example, to repeat successful fine tuning without exiting automatic mode with Mode = 0. Setting Retain.Mode to an invalid value such as 9999 for one cycle has no effect on State. Set Mode = 2 in the next cycle. In this way, you can generate a change to Retain.Mode without first switching to "Inactive" mode. 2980 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Meaning of values State / Description Retain.Mode 0 Inactive The controller is switched off and no longer changes the valve position. 1 Pretuning The pretuning determines the process response to a pulse of the output value and searches for the point of inflection. The optimized PID parameters are calculated as a function of the maximum rate of rise and dead time of the controlled system. Pretuning requirements: State = 0 or State = 4 ManualEnable = FALSE The motor transition time has been configured or measured. The setpoint and the process value lie within the configured limits. The more stable the process value is, the easier it is to calculate the PID parameters and the more precise the result will be. Noise on the process value can be tolerated as long as the rate of rise of the process value is significantly higher as compared to the noise. Before the PID parameters are recalculated, they are backed up and can be reactivated with Config.LoadBackUp. The setpoint is frozen in the CurrentSetpoint tag. The controller switches to automatic mode following successful pretuning and to "Inactive" mode following unsuccessful pretuning. The pretuning phase is indicated with the SUT.State tag. WinCC Basic V13.0 System Manual, 02/2014 2981 Programming the PLC 9.7 References State / Description Retain.Mode 2 Fine tuning Fine tuning generates a constant, limited oscillation of the process value. The PID parameters are tuned based on the amplitude and frequency of this oscillation. The differences between the process response during pretuning and fine tuning are analyzed. All PID parameters are recalculated from the results. PID parameters from fine tuning usually have better master control and disturbance characteristics than PID parameters from pretuning. PID_3Step automatically attempts to generate an oscillation greater than the noise of the process value. Fine tuning is only minimally influenced by the stability of the process value. The PID parameters are backed up before fine tuning. They can be reactivated with Config.LoadBackUp. The setpoint is frozen in the CurrentSetpoint tag. Requirements for fine tuning: The motor transition time has been configured or measured. The setpoint and the process value lie within the configured limits. ManualEnable = FALSE Automatic (State = 3), inactive (State = 0) or manual (State = 4) mode Fine tuning proceeds as follows when started from: Automatic mode (State = 3) Start fine tuning from automatic mode if you wish to improve the existing PID parameters through tuning. PID_3Step controls the system using the existing PID parameters until the control loop has stabilized and the requirements for fine tuning have been met. Only then will fine tuning start. Inactive (State = 0) or manual mode (State = 4) Pretuning is always started first. The determined PID parameters will be used for control until the control loop has stabilized and the requirements for fine tuning have been met. If PIDSelfTune.TIR.RunIn = TRUE, pretuning is skipped and an attempt is made to reach the setpoint with the minimum or maximum output value. This can produce increased overshoot. Fine tuning then starts automatically. The controller switches to automatic mode following successful fine tuning. If fine tuning was not successful, the controller switches to "Inactive" mode. The fine tuning phase is indicated with the TIR.State tag. 3 Automatic mode In automatic mode, PID_3Step controls the controlled system in accordance with the parameters specified. The controller switches to automatic mode if one the following requirements is fulfilled: Pretuning successfully completed Fine tuning successfully completed Changing the Retain.Mode tag to the value 3. When the CPU is switched on or switches from Stop to RUN mode, PID_3Step starts in the most recently active operating mode. To leave PID_3Step in "Inactive" mode, set RunModeByStartup = FALSE. The ActivateRecoverMode tag is taken into consideration in automatic mode. 2982 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References State / Description Retain.Mode 4 Manual mode In manual mode, you specify manual output values in the Manual_UP and Manual_DN parameters or ManualValue parameter. Whether or not the actuator can be moved to the output value in the event of an error is described in the ErrorBits parameter. This operating mode is enabled if Retain.Mode = 4, or on a rising edge at ManualEnable. If ManualEnable changes to TRUE, only State changes. Retain.Mode retains its current value. On a falling edge at ManualEnable, PID_3Step returns to the previous operating mode. The switchover to automatic mode is bumpless. PID_3Step V1.1 Manual mode is always possible in the event of an error. PID_3Step V1.0 Manual mode is dependent on the ActivateRecoverMode tag in the event of an error. 5 Approach substitute output value This operating mode is activated in the event of an error or when Reset = TRUE if Errorbehaviour = 1 and ActivateRecoverMode = FALSE.. PID_3Step moves the actuator to the substitute output value and then switches to "Inactive" mode. 6 Transition time measurement The time that the motor needs to completely open the valve from the closed condition is determined. This operating mode is activated when GetTransitTime.Start = TRUE is set. If endstop signals are used to measure the transition time, the valve will be opened completely from its current position, closed completely, and opened completely again. If GetTransitTime.InvertDirection = TRUE, this behavior is inverted. If position feedback is used to measure the transition time, the actuator will be moved from its current position to a target position. The output value limits are not taken into consideration during the transition time measurement. The actuator can travel to the high or the low endstop. 7 Error monitoring The control algorithm is switched off and no longer changes the valve position. This operating mode is activated instead of "Inactive" mode in the event of an error. All the following conditions must be met: Mode = 3 (automatic mode) Errorbehaviour = 0 ActivateRecoverMode = TRUE One or more errors have occurred in which ActivateRecoverMode (Page 2988) is effective. As soon as the errors are no longer pending, PID_3Step switches back to automatic mode. 8 Approach substitute output value with error monitoring This operating mode is activated instead of "Approach substitute output value" mode in the event of an error. PID_3Step moves the actuator to the substitute output value and then switches to "Error monitoring" mode. All the following conditions must be met: Mode = 3 (automatic mode) Errorbehaviour = 1 ActivateRecoverMode = TRUE One or more errors have occurred in which ActivateRecoverMode (Page 2988) is effective. As soon as the errors are no longer pending, PID_3Step switches back to automatic mode. WinCC Basic V13.0 System Manual, 02/2014 2983 Programming the PLC 9.7 References Automatic switchover of operating mode during commissioning PID_3Step automatically switches the operating mode in the event of an error. The following diagram illustrates the influence of ErrorBehaviour on the switchover of operating mode from transition time measurement, pretuning, and fine tuning modes. ,QDFWLYH (UURU%HKDYLRXU 7UDQVLWLRQWLPHPHDVXUHPHQW (UURU%HKDYLRXU (UURU%HKDYLRXU (UURU%HKDYLRXU 3UHWXQLQJ )LQHWXQLQJ (UURU%HKDYLRXU (UURU%HKDYLRXU $XWRPDWLFPRGH $SSURDFKVXEVWLWXWHRXWSXWYDOXH Automatic switchover of operating mode in the event of an error 2984 Automatic switchover of operating mode once the current operation has been completed. WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Automatic switchover of operating mode in automatic mode (PID_3Step V1.1) PID_3Step automatically switches the operating mode in the event of an error. The following diagram illustrates the influence of ErrorBehaviour and ActivateRecoverMode on this switchover of operating mode. ,QDFWLYH (UURUPRQLWRULQJ (UURU%HKDYLRXU $FWLYDWH5HFRYHU0RGH )$/6( (UURU%HKDYLRXU $FWLYDWH5HFRYHU0RGH 758( $XWRPDWLFPRGH (UURU%HKDYLRXU $FWLYDWH5HFRYHU0RGH )$/6( (UURU%HKDYLRXU $FWLYDWH5HFRYHU0RGH 758( $SSURDFKVXEVWLWXWHRXWSXWYDOXH $SSURDFKVXEVWLWXWHRXWSXWYDOXH ZLWKHUURUPRQLWRULQJ Automatic switchover of operating mode in the event of an error Automatic switchover of operating mode once the current operation has been completed. WinCC Basic V13.0 System Manual, 02/2014 2985 Programming the PLC 9.7 References Automatic switchover of operating mode in automatic and manual modes (PID_3Step V1.0) PID_3Step automatically switches the operating mode in the event of an error. The following diagram illustrates the influence of ErrorBehaviour and ActivateRecoverMode on this switchover of operating mode. ,QDFWLYH (UURU%HKDYLRXU $FWLYDWH5HFRYHU0RGH )$/6( (UURUPRQLWRULQJ (UURU%HKDYLRXU $FWLYDWH5HFRYHU0RGH )$/6( (UURU%HKDYLRXU $FWLYDWH5HFRYHU0RGH 758( $XWRPDWLFPRGH 0DQXDOPRGH $FWLYDWH5HFRYHU0RGH 758( (UURU%HKDYLRXU $FWLYDWH5HFRYHU0RGH )$/6( (UURU%HKDYLRXU $FWLYDWH5HFRYHU0RGH )$/6( (UURU%HKDYLRXU $FWLYDWH5HFRYHU0RGH 758( $SSURDFKVXEVWLWXWHRXWSXWYDOXH $SSURDFKVXEVWLWXWHRXWSXWYDOXH ZLWKHUURUPRQLWRULQJ Automatic switchover of operating mode in the event of an error Automatic switchover of operating mode once the current operation has been completed. Automatic switchover of operating mode when error is no longer pending. See also Tag ActivateRecoverMode V1 (Page 2988) Parameter ErrorBits V1 (Page 2987) 2986 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameter ErrorBits V1 If several errors are pending simultaneously, the values of the error codes are displayed with binary addition. The display of error code 0003, for example, indicates that the errors 0001 and 0002 are pending simultaneously. ErrorBits Description (DW#16#...) 0000 There is no error. 0001 The "Input" parameter is outside the process value limits. Input > Config.InputUpperLimit or Input < Config.InputLowerLimit If ActivateRecoverMode = TRUE and ErrorBehaviour = 1, the actuator moves to the substitute output value. If ActivateRecoverMode = TRUE and ErrorBehaviour = 0, the actuator stops in its current position. If ActivateRecoverMode = FALSE, the actuator stops in its current position. PID_3Step V1.1 You can move the actuator in manual mode. PID_3Step V1.0 Manual mode is not possible in this state. You cannot move the actuator again until you eliminate the error. 0002 Invalid value at "Input_PER" parameter. Check whether an error is pending at the analog input. If automatic mode was active before the error occurred, ActivateRecoverMode = TRUE, and the error is no longer pending, PID_3Step switches back to automatic mode. 0004 Error during fine tuning. Oscillation of the process value could not be maintained. 0020 Pretuning is not permitted in automatic mode or during fine tuning. 0080 Error during pretuning. Incorrect configuration of output value limits. Check whether the limits of the output value are configured correctly and match the control logic. 0100 Error during fine tuning resulted in invalid parameters. 0200 Invalid value at "Input" parameter: Value has an invalid number format. If automatic mode was active before the error occurred, ActivateRecoverMode = TRUE, and the error is no longer pending, PID_3Step switches back to automatic mode. 0400 Calculation of output value failed. Check the PID parameters. 0800 Sampling time error: PID_3Step is not called within the sampling time of the cyclic interrupt OB. If automatic mode was active before the error occurred, ActivateRecoverMode = TRUE, and the error is no longer pending, PID_3Step switches back to automatic mode. 1000 Invalid value at "Setpoint" parameter: Value has an invalid number format. If automatic mode was active before the error occurred, ActivateRecoverMode = TRUE, and the error is no longer pending, PID_3Step switches back to automatic mode. 2000 Invalid value at Feedback_PER parameter. Check whether an error is pending at the analog input. The actuator cannot be moved to the substitute output value and remains in its current position. Manual mode is not possible in this state. You must deactivate position feedback (Config. FeedbackOn = FALSE) to move the actuator from this state. If automatic mode was active before the error occurred, ActivateRecoverMode = TRUE, and the error is no longer pending, PID_3Step switches back to automatic mode. WinCC Basic V13.0 System Manual, 02/2014 2987 Programming the PLC 9.7 References ErrorBits Description (DW#16#...) 4000 Invalid value at Feedback parameter. Value has an invalid number format. The actuator cannot be moved to the substitute output value and remains in its current position. Manual mode is not possible in this state. You must deactivate position feedback (Config. FeedbackOn = FALSE) to move the actuator from this state. If automatic mode was active before the error occurred, ActivateRecoverMode = TRUE, and the error is no longer pending, PID_3Step switches back to automatic mode. 8000 Error during digital position feedback. Actuator_H = TRUE and Actuator_L = TRUE. The actuator cannot be moved to the substitute output value and remains in its current position. Manual mode is not possible in this state. In order to move the actuator from this state, you must deactivate the "Actuator endstop" (Config.ActuatorEndStopOn = FALSE). If automatic mode was active before the error occurred, ActivateRecoverMode = TRUE, and the error is no longer pending, PID_3Step switches back to automatic mode. Parameter Reset V1 A rising edge at Reset resets the errors and warnings and clears the integral action. A falling edge at Reset triggers a change to the most recently active operating mode. 5HVHW W PV 0RGH W PV 6WDWH W PV Activation Error Reset Tag ActivateRecoverMode V1 The effect of the ActivateRecoverMode variable depends on the version of the PID_3Step. 2988 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Behavior in version 1.1 The ActivateRecoverMode variable determines the behavior in the event of an error in automatic mode. ActivateRecoverMode is not effective during pretuning, fine tuning and transition time measurement. ActivateRecover Description Mode FALSE In the event of an error, PID_3Step switches to "Inactive" or "Approach substitute output value" operating mode. The controller is activated by a reset or a change in Retain.Mode. TRUE If errors occur frequently in automatic mode, this setting has a negative effect on the control response. In this case, check the ErrorBits parameter and eliminate the cause of the error. If one or more errors occur, PID_3Step switches to "Approach substitute output value with error monitoring" or "Error monitoring" mode: 0002h: Invalid value at parameter Input_PER. 0200h: Invalid value at parameter Input. 0800h: Sampling time error 1000h: Invalid value at parameter Setpoint. 2000h: Invalid value at parameter Feedback_PER. 4000h: Invalid value at parameter Feedback. 8000h: Error in digital position feedback. With errors 2000h, 4000h and 8000h, PID_3Step cannot approach the configured substitute output value. As soon as the errors are no longer pending, PID_3Step switches back to automatic mode. WinCC Basic V13.0 System Manual, 02/2014 2989 Programming the PLC 9.7 References Behavior in version 1.0 The ActivateRecoverMode variable determines the behavior in the event of an error in automatic and manual mode. ActivateRecoverMode is not effective during pretuning, fine tuning and transition time measurement. ActivateRecover Description Mode FALSE In the event of an error, PID_3Step switches to "Inactive" or "Approach substitute output value" operating mode. The controller is activated by a reset or a change in Retain.Mode. TRUE Errors in automatic mode If errors occur frequently in automatic mode, this setting has a negative effect on the control response. In this case, check the ErrorBits parameter and eliminate the cause of the error. If one or more errors occur, PID_3Step switches to "Approach substitute output value with error monitoring" or "Error monitoring" mode: 0002h: Invalid value at parameter Input_PER. 0200h: Invalid value at parameter Input. 0800h: Sampling time error 1000h: Invalid value at parameter Setpoint. 2000h: Invalid value at parameter Feedback_PER. 4000h: Invalid value at parameter Feedback. 8000h: Error in digital position feedback. With errors 2000h, 4000h and 8000h, PID_3Step cannot approach the configured substitute output value. As soon as the errors are no longer pending, PID_3Step switches back to automatic mode. Errors in manual mode If one or more of the following errors occur, PID_3Step stays in manual mode: 0002h: Invalid value at parameter Input_PER. 0200h: Invalid value at parameter Input. 0800h: Sampling time error 1000h: Invalid value at parameter Setpoint. 2000h: Invalid value at parameter Feedback_PER. 4000h: Invalid value at parameter Feedback. 8000h: Error in digital position feedback. With errors 2000h, 4000h and 8000h, you cannot move the valve to a suitable position. See also PID_3Step V1 static tags (Page 2973) Parameter State and Retain.Mode V1 (Page 2980) 2990 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Tag Warning V1 If several warnings are pending simultaneously, their values are displayed with binary addition. The display of warning 0003, for example, indicates that the warnings 0001 and 0002 are pending simultaneously. Warning Description (DW#16#...) 0000 No warning pending. 0001 The point of inflection was not found during pretuning. 0002 Oscillation increased during fine tuning. 0004 The setpoint was limited to the configured limits. 0008 Not all the necessary controlled system properties were defined for the selected method of calculation. The PID parameters were instead calculated using the TuneRuleTIR = 3 method. 0010 The operating mode could not be changed because ManualEnable = TRUE. 0020 The cycle time of the calling OB limits the sampling time of the PID algorithm. Improve results by using shorter OB cycle times. 0040 The process value exceeded one of its warning limits. 0080 Invalid value at Retain.Mode. The operating mode is not switched. 0100 The manual value was limited to the limits of the controller output. 0200 The rule used for tuning produces an incorrect result, or is not supported. 0400 Method selected for transition time measurement not suitable for actuator. The transition time cannot be measured because the actuator settings do not match the selected measuring method. 0800 The difference between the current position and the new output value is too small for transition time measurement. This can produce incorrect results. The difference between the current output value and new output value must be at least 50% of the entire control range. 1000 The substitute output value cannot be reached because it is outside the output value limits. The following warnings are deleted as soon as the cause is eliminated: 0004 0020 0040 0100 All other warnings are cleared with a rising edge at Reset. Tag SUT.State V1 SUT.Stat e Name 0 SUT_INIT 50 SUT_TPDN Description Initialize pretuning Determine start position without position feedback 100 SUT_STDABW Calculate the standard deviation 200 SUT_GET_POI Find the point of inflection WinCC Basic V13.0 System Manual, 02/2014 2991 Programming the PLC 9.7 References SUT.Stat e Name Description 300 SUT_GET_RISETM 9900 SUT_IO Determine the rise time Pretuning successful 1 SUT_NIO Pretuning not successful Tag TIR.State V1 TIR.State Name Description -100 TIR_FIRST_SUT 0 TIR_INIT Fine tuning is not possible. Pretuning will be executed first. Initialize fine tuning 200 TIR_STDABW Calculate the standard deviation 300 TIR_RUN_IN Attempt to reach the setpoint with the maximum or minimum output value 400 TIR_CTRLN Attempt to reach the setpoint with the existing PID parameters (if pretuning has been successful) 500 TIR_OSZIL 9900 TIR_IO Determine oscillation and calculate parameters Fine tuning successful 1 TIR_NIO Fine tuning not successful 9.7.5 Communication 9.7.5.1 Communications processor Point-to-point PORT_CFG: Configure communication parameters dynamically Description The instruction "PORT_CFG" allows dynamic configuration of communications parameters for a point-to-point communications port. You set up the original static configuration of the port in the hardware configuration. You can change this configuration by executing the "PORT_CFG" instruction. You can also use this function to save created blocks in libraries and to avoid configuration in the hardware configuration when you reuse it. With "PORT_CFG" you can influence the following communications parameter settings: Parity Baud rate Number of bits per character 2992 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Number of stop bits Type and properties of flow control The changes made by the "PORT_CFG" instruction are not stored permanently on the target system. You can transfer serial data via the electrical connections RS-232 (half and full duplex) and RS-485 (half duplex). Parameters The following table shows the parameters of the "PORT_CFG" instruction: Parameter Declaration Data type Memory area Description REQ Input BOOL I, Q, M, D, L or constant Activates the configuration change on a rising edge PORT Input PORT I, Q, M, D, L or constant Identification of the communication port (HW-ID) PROTOCOL Input UINT I, Q, M, D, L or constant Transmission protocol: 0: Point-to-point communication protocol 1..n: Future definition for specific transmission protocols BAUD Input UINT I, Q, M, D, L or constant Baud rate of the port: 1: 300 baud 2: 600 baud 3: 1200 baud 4: 2400 baud 5: 4800 baud 6: 9600 baud (default) 7: 19200 baud 8: 38400 baud 9: 57600 baud 10: 76800 baud 11: 115200 baud PARITY Input UINT I, Q, M, D, L or constant Parity of the port: 1: No parity (default) 2: Even parity 3: Odd parity 4: Mark parity 5: Space parity DATABITS Input UINT I, Q, M, D, L or constant Bits per character: 1: 8 bits per character (default) 2: 7 bits per character STOPBITS Input UINT I, Q, M, D, L or constant Number of stop bits: 1: 1 stop bit (default) 2: 2 stop bits WinCC Basic V13.0 System Manual, 02/2014 2993 Programming the PLC 9.7 References Parameter Declaration Data type Memory area Description FLOWCTRL Input UINT I, Q, M, D, L or constant Data flow control: 1: None (default) 2: XON/XOFF 3: Hardware flow control (RTS always activated) 4: Hardware flow control (RTS can be deactivated during transmission) XONCHAR Input CHAR I, Q, M, D, L or constant Indicates the character used as XON character. The character DC1 (11H) is set as default. XOFFCHAR Input CHAR I, Q, M, D, L or constant Indicates the character used as XOFF character. The character DC3 (13H) is set as default. WAITTIME Input UINT I, Q, M, D, L or constant Specifies the wait time for XON or CTS after the start of the transmission. The specified value must be greater than 0. 2000 milliseconds are set as default. DONE Output BOOL I, Q, M, D, L Status parameter with the following values: 0: Job not yet started or is still executing 1: Job executed without errors ERROR Output BOOL I, Q, M, D, L Status parameter with the following values: 0: No error 1: Error occurred STATUS Output WORD I, Q, M, D, L Status of the instruction You will find more detailed information on valid data types in "Overview of the valid data types (Page 1204)". STATUS parameter Error code* Description (W#16#...) 80A0 The specified protocol is invalid. 80A1 The specified baud rate is invalid. 80A2 The specified parity rate is invalid. 80A3 The specified number of bits per character is invalid. 80A4 The specified number of stop bits is invalid. 80A5 The specified type of flow control is invalid. 80A6 Incorrect value at the WAITTIME parameter When the data flow control is enabled, the value at the WAITTIME parameter must be greater than zero. 80A7 Invalid values at XONCHAR and XOFFCHAR parameters. * The error codes can be displayed as integer or hexadecimal values in the program editor. For additional information on toggling display formats, refer to "See also". You will find more detailed information on general error codes of the communication instructions in: "General status information of the communications blocks (Page 3009)". 2994 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References SEND_CFG: Configure serial transmission parameters dynamically Description The instruction "SEND_CFG" allows dynamic configuration of serial transmission parameters for a point-to-point communications port. All the messages waiting for transfer are discarded after execution of SEND_CFG. You set up the original static configuration of the port in the hardware configuration. You can change this configuration by executing the "SEND_CFG" instruction. You can also use this function to save created blocks in libraries and to avoid configuration in the hardware configuration when you reuse it. With "SEND_CFG" you can influence the following transmission parameter settings: Time between the activation of RTS (Request to Send) and the start of the transmission Time between the end of transmission and the deactivation of RTS Define bit times for breaks The changes made by the "SEND_CFG" instruction are not stored permanently on the target system. You can transfer serial data via the electrical connections RS-232 (half and full duplex) and RS-485 (half duplex). Parameters The following table shows the parameters of the "SEND_CFG" instruction: Parameter Declaration Data type Memory area Description REQ Input BOOL I, Q, M, D, L or constant Activates the configuration change on a rising edge PORT Input PORT I, Q, M, D, L or constant Identification of the communication port (HW-ID) RTSONDLY Input UINT I, Q, M, D, L or constant The time that should elapse after activating RTS until the start of transmission. Valid values for this parameter are as follows: 0 (default) 0 to 65535 ms in steps of 1 ms This parameter does not apply to RS-485 modules. RTSOFFDLY Input UINT I, Q, M, D, L or constant Time that should elapse after the end of transmission until deactivation of RTS. Valid values for this parameter are as follows: 0 (default) 0 to 65535 ms in steps of 1 ms This parameter does not apply to RS-485 modules. BREAK Input UINT I, Q, M, D, L or constant Specifies the bit times for a break, which are sent at the start of the message. 12 bit times are set as default. A maximum of 25000 bit times can be specified. WinCC Basic V13.0 System Manual, 02/2014 2995 Programming the PLC 9.7 References Parameter Declaration Data type Memory area Description IDLELINE Input UINT I, Q, M, D, L or constant Specifies the bit times for idle line after the break at the start of the message. 12 bit times are set as default. A maximum of 25000 bit times can be specified. DONE Output BOOL I, Q, M, D, L Status parameter with the following values: 0: Job not yet started or is still executing 1: Job executed without errors ERROR Output BOOL I, Q, M, D, L Status parameter with the following values: 0: No error 1: Error occurred STATUS Output WORD I, Q, M, D, L Status of the instruction You will find more detailed information on valid data types in "Overview of the valid data types (Page 1204)". STATUS parameter Error code* Description (W#16#...) 80B0 The configuration of a transmission interruption is not permitted. 80B1 The specified break time exceeds the permitted maximum of 25000 bit times. 80B2 The specified time for idle line exceeds the permitted maximum of 25000 bit times. * The error codes can be displayed as integer or hexadecimal values in the program editor. For additional information on toggling display formats, refer to "See also". You will find more detailed information on general error codes of the communication instructions in: "General status information of the communications blocks (Page 3009)". RCV_CFG: Configure serial receive parameters dynamically Description The instruction "RCV_CFG" allows dynamic configuration of serial receive parameters for a point-to-point communications port. You can use this instruction to configure the conditions that specify the start and end of the message to be transmitted. The receipt of messages that correspond to these conditions can be enabled by the "RCV_PTP (Page 3005)" instruction. You set up the original static configuration of the port in the properties of the hardware configuration. Execute the "RCV_CFG" instruction in your program to change the configuration. You can also use this function to save created blocks in libraries and to avoid configuration in the hardware configuration when you reuse it. The changes made by the "RCV_CFG" instruction are not stored permanently on the target system. All the messages waiting for transfer are discarded after execution of the "RCV_CFG" instruction. 2996 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameters The following table shows the parameters of the "RCV_CFG" instruction: Parameter Declaration Data type Memory area Description REQ Input BOOL I, Q, M, D, L or constant Activates the configuration change on a rising edge. PORT Input PORT I, Q, M, D, L or constant Identification of the communication port (HW-ID) CONDITIONS Input CONDITIONS D, L Data structure defining the conditions for start and end of data transmission. DONE Output BOOL I, Q, M, D, L Status parameter with the following values: 0: Job not yet started or is still executing 1: Job executed without errors ERROR Output BOOL I, Q, M, D, L Status parameter with the following values: 0: No error 1: Error occurred. STATUS Output WORD I, Q, M, D, L Status of the instruction You will find more detailed information on valid data types in "Overview of the valid data types (Page 1204)". Data type CONDITIONS You can use the CONDITIONS structure to define the start and end conditions for the message transmission. The structure CONDITIONS is included in the instance DB of the "RCV_CFG" instruction. Use the structure CONDITIONS to define the start and end conditions when the transmission of a message is complete and when the next message transfer is to start: You define the start conditions for the data transfer in the START structure. You define the end conditions for the data transfer in the END structure. You can define one or more start and end conditions for this. If you specify multiple start or end conditions these are linked by an OR logic instruction. The following table shows the "CONDITIONS" structure: WinCC Basic V13.0 System Manual, 02/2014 2997 Programming the PLC 9.7 References Parameters Data type Description START STRUCT Start conditions UINT Specifies the start condition (details, see below). STARTCOND The start condition can be specified as a 16-bit hexadecimal value. Possible values for the start condition are: 1: Start character 2: Any character (default) 4: Line break 8: Idle line 16: Character string 1 32: Character string 2 64: Character string 3 128: Character string 4 Multiple start conditions can also be defined at the STARTCOND parameter. The total from the values of the individual conditions is specified for this. If, for example, you want to define "Idle line" OR "Character string 1" OR "Character string 4" as start condition, the value "152" must be specified. IDLETIME UINT Specifies the maximum idle time of the line before receipt is started. Valid values for this parameter are as follows: 40 bit times (default) 0 to 2500 bit times STARTCHAR BYTE Specifies the start character. This setting is only enabled when the configured start condition is "Start character". Valid values for this parameter are as follows: 02 (STX): Default setting B#16#00 to B#16#FF SEQ[1].CTL BYTE Character string 1: Control sequence for each character You can use the bit position of the character to define which characters of the character string will be considered or ignored. To evaluate the characters, the corresponding bits have to be set. Bit 0: 1 character Bit 1: 2 characters Bit 2: 3 characters Bit 3: 4 characters Bit 4: 5 characters A character is ignored when the corresponding bit is reset. SEQ[1].STR END 2998 CHAR[5] Character string 1: Start character (5 characters) SEQ[2].CTL BYTE Character string 2: Ignore/compare control sequence for each character SEQ[2].STR CHAR[5] Character string 2: Start character (5 characters) SEQ[3].CTL BYTE Character string 3: Ignore/compare control sequence for each character SEQ[3].STR CHAR[5] Character string 3: Start character (5 characters) SEQ[4].CTL BYTE Character string 4: Ignore/compare control sequence for each character SEQ[4].STR CHAR[5] Character string 4: Start character (5 characters) STRUCT End conditions WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameters ENDCOND Data type Description UINT Specifies the end condition (details, see below). The end condition can be specified as a 16-bit hexadecimal value. Possible values for the end condition are: 1: Reply timeout 2: Message timeout 4: Timeout within the character string 8: Maximum length 16: N+LEN+M; the information on the message length in integrated in the message and will be evaluated. 32: Character string 1 Multiple end conditions can also be defined at the ENDCOND parameter. The total from the values of the individual end conditions is specified for this. If, for example, you want to define the end condition "Maximum length" OR "Sequence 1", the value "40" must be specified. MAXLEN UINT Specifies the maximum number of characters in a message. Valid values* for this parameter are as follows: 1 character (default) 0 to 1024 characters This setting is only enabled if the "Maximum length" end condition is set at the ENDCOND parameter. N UINT Offset of the length field in the message Valid values for this parameter are as follows: 0 characters (default) 0 to 1024 characters This setting is only enabled if the "N+LEN+M" end condition is set at the ENDCOND parameter. LENGTHSIZE UINT Size of the length field in bytes Valid values* for this parameter are as follows: 0 bytes (default) 1 byte 2 bytes 4 bytes This setting is only enabled if the "N+LEN+M" end condition is set at the ENDCOND parameter. LENGTHM UINT Specifies the number of end characters that follow the length field but are not contained in the length of the message. Valid values for this parameter are as follows: 0 characters (default) 0 to 255 characters This setting is only enabled if the "N+LEN+M" end condition is set at the ENDCOND parameter. WinCC Basic V13.0 System Manual, 02/2014 2999 Programming the PLC 9.7 References Parameters RCVTIME Data type Description UINT Specifies the maximum duration for the receipt of the first character of a message. Valid values for this parameter are as follows: 200 ms (default) 0 to 65535 ms in steps of 1 ms This setting is only enabled if the "Reply timeout" end condition is set at the ENDCOND parameter. MSGTIME UINT Specifies the maximum duration of the receipt of a message. Valid values for this parameter are as follows: 200 ms (default) 0 to 65535 ms in steps of 1 ms This setting is only enabled if the "Message timeout" end condition is set at the ENDCOND parameter. CHARGAP UINT Specifies the time interval between received consecutive characters. Valid values for this parameter are as follows: 12 bit times (default) 0 to 2500 bit times This setting is only enabled if the "Timeout within the character string" end condition is set at the ENDCOND parameter. SEQ.CTL BYTE Character string: Control sequence for each character You can use the bit position of the character to define which characters of the character string will be considered or ignored. To evaluate the characters, the corresponding bits have to be set. Bit 0: 1 character Bit 1: 2 characters Bit 2: 3 characters Bit 3: 4 characters Bit 4: 5 characters A character is ignored when the corresponding bit is reset. SEQ.STR CHAR[5] Character string: Start character (5 characters) * These value ranges also apply to the corresponding hardware settings for specifying the end of message. Start conditions for the message receipt (STARTCOND parameter) The start of the message is recognized by the receiver if a configured start condition applies. The following conditions can be defined as start conditions for message receipt: Start character: The start of a message is recognized when a certain character occurs. This character is stored as first character of the message. All characters received before the start character are rejected. Any character: Any character can define the start of a message. This character is stored as first character of the message. Line break: The start of a message is recognized if the received data stream is interrupted for longer than one character length. 3000 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Idle line: The start of a message is recognized when the send transmission line is in the idle state for a certain time (specified in bit times) followed by renewed transmission of characters. Character string (sequence): The start of a message is recognized when a specified character sequence occurs in the data stream. You can specify up to four character sequences with up to five characters each. Example: A received hexadecimal message includes the following characters: "68 10 aa 68 bb 10 aa 16". The configured start character sequences are listed in the following table. Start character sequences will be evaluated once the first character 68H has been received successfully. After the fourth character has been received successfully (the second 68H), the start condition "1" has been met. Once the start conditions have been met, evaluation of the end conditions will start. Processing of the start character sequence can end due to different errors in parity, framing or time intervals between characters. These errors will prevent reception of the message, because the start condition has not been met. Start condition First character First character +1 First character +2 First character +3 First character +4 1 68H xx xx 68H xx 2 10H aaH xx xx xx 3 dcH aaH xx xx xx 4 e5H xx xx xx xx End conditions for the message receipt (ENDCOND parameter) The start of a message is recognized by the receiver if a configured end condition applies. The following conditions can be defined as end conditions for message receipt: Reply timeout: The receipt of messages will end when the specified maximum duration for the receipt of a character is exceeded. The maximum duration is defined at the RCVTIME parameter. The defined time starts to run down as soon at the last transmission is completed and the RCV_PTP instruction enables the receipt of the message. If no character was received within the defined time (RCVTIME), the RCV_PTP instruction reports an error. Message timeout: The receipt of messages will end when the specified maximum duration for the receipt of a message is exceeded. The maximum duration is defined at the MSGTIME parameter. The defined time starts to run down as soon as the first character of the message is received. Timeout within the character string: The receipt of messages will end when the time interval between the receipt of two consecutive characters is longer than the value at the CHARGAP parameter. Maximum length: The receipt of messages will end when the length of the message defined at the MAXLEN parameter is exceeded. WinCC Basic V13.0 System Manual, 02/2014 3001 Programming the PLC 9.7 References Reading message length (N+LEN+M): The receipt of messages will end when a certain message length is reached. This length is calculated by the values of the following parameters: - N: Position of the character in the message from which the length field begins. - LENGTHSIZE: Size of the length field in bytes - LENGTHM: Number of end characters that follow the length field. These characters are not taken into account in the evaluation of the message length. Character string: The receipt of messages will end when a defined character sequence is received. The character string can contain a maximum of five characters. For each character of the character string, you can use the bit position to define if this will be considered or ignored in the evaluation. STATUS parameter Error code* Description (W#16#...) 80C0 Error in start condition 80C1 Error in end condition No end condition defined 80C2 Receive interrupt enabled 80C3 A value that is equal to 0 or greater than 4132 was entered at the MAXLEN parameter while the "Maximum length" end condition was set. 80C4 A value that is greater than 4131 was entered at the N parameter while the "N+LEN+M" end condition was set. 80C5 A value that is equal to 0 or invalid was entered at the LENGTHSIZE parameter while the "N+LEN+M" end condition was set. 80C6 A value that is greater than 255 was entered at the LENGTHM parameter while the "N+LEN+M" end condition was set. 80C7 A message length greater than 4132 was calculated while the "N+LEN+M" end condition was set. 80C8 A value that is equal to 0 was entered at the RCVTIME parameter while the "Reply timeout" end condition was set. 80C9 A value that is equal to 0 or greater than 2500 was entered at the CHARGAP parameter while the "Timeout within a character string" end condition was set. 80CA A value that is equal to 0 or greater than 2500 was entered at the IDLETIME parameter while the "Idle line" start condition was set. 80CB All characters of the character string are marked as "Don't care" even though "Character string" is set as the end condition. 80CC All characters of the character string are marked as "Don't care" even though "Character string" is set as the start condition. * The error codes can be displayed as integer or hexadecimal values in the program editor. For additional information on toggling display formats, refer to "See also". You will find more detailed information on general error codes of the communication instructions in: "General status information of the communications blocks (Page 3009)". 3002 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References SEND_PTP: Transmit send buffer data Description You use the "SEND_PTP" instruction to start the transmission of data. The "SEND_PTP" instruction does not execute the actual transmission of the data. The data of the send buffer is transmitted to the relevant point-to-point communication module (CM). The CM executes the actual transmission. Parameters The following table shows the parameters of the "SEND_PTP" instruction: Parameter Declaration Data type Memory area Description REQ Input BOOL I, Q, M, D, L or constant Enables the requested transmission on a rising edge of this enable input. The content of buffer is transmitted to the point-to-point communication module (CM). PORT Input PORT I, Q, M, D, L or constant Identification of the communication port (HW-ID) BUFFER Input VARIANT I, Q, M, D, L or constant Pointer to the start address of the send buffer. Boolean values or Array of BOOL are not supported. LENGTH Input UINT I, Q, M, D, L or constant Length of the send buffer PTRCL Input BOOL I, Q, M, D, L or constant This parameter selects the buffer for normal point-topoint communication or for specific Siemens protocols implemented in the connected CM. FALSE = point-to-point operations controlled by the user program (only valid option) DONE Output BOOL I, Q, M, D, L Status parameter with the following values: 0: Job not yet started or is still executing 1: Job executed without errors ERROR Output BOOL I, Q, M, D, L Status parameter with the following values: 0: No error 1: Error occurred STATUS Output WORD I, Q, M, D, L Status of the instruction You will find more detailed information on valid data types in "Overview of the valid data types (Page 1204)". STATUS parameter Error code* Description (W#16#...) 7000 The send operation is not active. 7001 The send operation is processing the first call. 7002 The send operation is processing subsequent calls (queries following the first call). WinCC Basic V13.0 System Manual, 02/2014 3003 Programming the PLC 9.7 References Error code* Description (W#16#...) 8080 The identifier entered for the communications port number is invalid. 8088 The length of the LENGHT parameter does not correspond to the length of data to be sent. See also: Parameters LENGHT and BUFFER. 80D0 A new send request was received while a transmission was taking place. 80D1 The transmission was interrupted because the CTS signal was not confirmed within the specified wait time. 80D2 The send request was interrupted because the communications partner (DCE) signaled that it was not willing to receive (DSR). 80D3 The send request was interrupted because the maximum size of the waiting loop was exceeded (more than 1024 Byte). * The error codes can be displayed as integer or hexadecimal values in the program editor. For additional information on toggling display formats, refer to "See also". You will find more detailed information on general error codes of the communication instructions in: "General status information of the communications blocks (Page 3009)". Parameters LENGTH and BUFFER The minimum data size that can be sent by the "PTP_SEND" instruction is one byte. The parameter BUFFER defines the size of the data to be sent. You can use neither the BOOL nor the Array of BOOL data type for the BUFFER parameter. LENGTH parameter BUFFER parameter Description LENGTH = 0 Not used The complete data is sent as defined by the BUFFER parameter. If LENGTH = 0, you do not need to specify the number of bytes transferred. LENGTH > 0 Elementary data type The LENGTH value must contain the byte count of this data type. Otherwise, data is not transferred and error 8088 is output. STRUCT The LENGTH value can contain a byte count that is smaller than the complete byte length of the structure. In this case, only the first LENGTH bytes are transferred. ARRAY The LENGTH value can contain a byte count that is smaller than the complete byte length of the field. In this case, only the field elements that fit completely in the LENGTH bytes are transferred. The LENGTH value must be a multiple of the byte count of the data elements. Otherwise, STATUS = 8088, ERROR = 1, and no data is transferred. STRING The complete memory arrangement of the character sequence format will be transmitted as well as the information about maximum length of the character string and the actual length of the character string. The LENGTH value must contain bytes for maximum length, actual length, and the characters of the character string. With the data type STRING, all lengths and characters have the size of one byte. If a character string is used for the BUFFER parameter, the LENGTH value must also contain two bytes for the two length fields. 3004 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References RCV_PTP: Enable receive messages Description With the RCV_PTP instruction you enable receipt of a sent message. Each message must be enabled individually. The sent data is only available in the receive area when the message has been acknowledged by the relevant communications partner. Parameters The following table shows the parameters of the "RCV_PTP" instruction: Parameter Declaration Data type Memory area Description EN_R Input BOOL I, Q, M, D, L or constant Enables receipt on a rising edge PORT Input PORT I, Q, M, D, L or constant Identification of the communication port (HW-ID) BUFFER Input VARIANT I, Q, M, D, L or constant Points to the start address of the receive buffer. Do not use a tag of the type STRING in the receive buffer. NDR Output BOOL I, Q, M, D, L Status parameter with the following values: 0: Job not yet started or is still executing 1: Job executed without errors ERROR Output BOOL I, Q, M, D, L Status parameter with the following values: 0: No error 1: Error occurred STATUS Output WORD I, Q, M, D, L Status of the instruction LENGTH Output UINT I, Q, M, D, L Length of the message in the receive buffer You will find more detailed information on valid data types in "Overview of the valid data types (Page 1204)". STATUS parameter Error code* Description (W#16#....) 80E0 Receipt of messages was terminated because the receive buffer is full. 80E1 Receipt of messages was terminated as a result of a parity error. 80E2 Receipt of messages was terminated as a result of a framing error. 80E3 Receipt of messages was terminated as a result of an overflow error. 80E4 Receipt of messages was terminated because the calculated message length (N+LEN+M) exceeds the size of the receive buffer. 8080 The identifier entered for the communications port number is invalid. 8088 A data type STRING is referenced via the BUFFER parameter. 0094 Receipt of messages was terminated because the maximum character length was received. 0095 Receipt of messages was terminated as a result of a timeout. WinCC Basic V13.0 System Manual, 02/2014 3005 Programming the PLC 9.7 References Error code* Description (W#16#....) 0096 Receipt of messages was terminated because of a timeout within the character string. 0097 Receipt of messages was terminated as a result of a reply timeout. 0098 Receipt of messages was terminated because the "N+LEN+M" length condition has been satisfied. 0099 Receipt of messages was terminated because the character string defined as the end condition was received. * The error codes can be displayed as integer or hexadecimal values in the program editor. For additional information on toggling display formats, refer to "See also". You will find more detailed information on general error codes of the communication instructions in: "General status information of the communications blocks (Page 3009)". RCV_RST: Delete receive buffer Description With the "RCV_RST" instruction, you delete the receive buffer of a communications partner. Parameters The following table shows the parameters of the "RCV_RST" instruction: Parameter Declaration Data type Memory area Description REQ Input BOOL I, Q, M, D, L or constant Enables deleting of the receive buffer on a rising edge PORT Input PORT I, Q, M, D, L or constant Identification of the communication port (HW-ID) DONE Output BOOL I, Q, M, D, L Status parameter with the following values: 0: Job not yet started or is still executing 1: Job executed without errors ERROR Output BOOL I, Q, M, D, L Status parameter with the following values: 0: No error 1: Error occurred STATUS Output WORD I, Q, M, D, L Status of the instruction You will find more detailed information on general error codes of the communication instructions in: "General status information of the communications blocks (Page 3009)". You will find more detailed information on valid data types in "Overview of the valid data types (Page 1204)". 3006 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References SGN_GET: Query RS-232 signals Description With the "SGN_GET" instruction, you query the current state of several signals of an RS-232 communications module. Parameters The following table shows the parameters of the "SGN_GET" instruction: Parameter Declaration Data type Memory area Description REQ Input BOOL I, Q, M, D, L or constant Enables the query on a rising edge PORT Input PORT I, Q, M, D, L or constant Identification of the communication port (HW-ID) NDR Output BOOL I, Q, M, D, L Is set for one cycle if new data are ready for sending and the instruction was executed errorfree. DTR Output BOOL I, Q, M, D, L Data terminal ready, module ready DSR Output BOOL I, Q, M, D, L Data set ready, communications partner ready RTS Output BOOL I, Q, M, D, L Send request, module ready to send CTS Output BOOL I, Q, M, D, L Clear to send, communications partner can receive data (reaction to RTS = ON of the module). DCD Output BOOL I, Q, M, D, L Data carrier detect, received signal level RING Output BOOL I, Q, M, D, L Ring display, display of an incoming call ERROR Output BOOL I, Q, M, D, L Status parameter with the following values: 0: No error 1: Error occurred STATUS Output WORD I, Q, M, D, L Status of the instruction You will find more detailed information on valid data types in "Overview of the valid data types (Page 1204)". STATUS parameter Error code* Description (W#16#....) 80F0 The communication module is an RS-485 module and no signals are available. * The error codes can be displayed as integer or hexadecimal values in the program editor. For additional information on toggling display formats, refer to "See also". You will find more detailed information on general error codes of the communication instructions in: "General status information of the communications blocks (Page 3009)". WinCC Basic V13.0 System Manual, 02/2014 3007 Programming the PLC 9.7 References SGN_SET: Set RS-232 signals Description With the "SGN_SET" instruction, you set the status of the output signals of an RS-232 communications module. Parameters The following table shows the parameters of the "SGN_SET" instruction: Parameter Declaration Data type Memory area Description REQ Input BOOL I, Q, M, D, L or constant Activates the action on a rising edge Initial value: FALSE PORT Input PORT I, Q, M, D, L or constant Identification of the communication port (HW-ID) SIGNAL Input BYTE I, Q, M, D, L or constant Specifies the signals to be set: Initial value: FALSE Set 01H = RTS Set 02H = DTR Set 04H = DSR Initial value: FALSE RTS DTR DSR Input Input Input BOOL BOOL BOOL I, Q, M, D, L or constant Send request, module ready to send I, Q, M, D, L or constant Data terminal ready, module ready I, Q, M, D, L or constant Data set ready (applies only to interfaces of the DCE type) Initial value: FALSE Initial value: FALSE Initial value: FALSE DONE Output BOOL I, Q, M, D, L Status parameter with the following values: 0: Job not yet started or is still executing 1: Job executed without errors Initial value: FALSE ERROR Output BOOL I, Q, M, D, L Status parameter with the following values: 0: No error 1: Error occurred Initial value: FALSE STATUS Output WORD I, Q, M, D, L Status of the instruction Initial value: 0 You will find more detailed information on valid data types in "Overview of the valid data types (Page 1204)". 3008 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References STATUS parameter Error code* (W#16#...) Description 80F0 The communication module is an RS-485 module and no signals are available. 80F1 No signals are settable because H/W flow control is enabled. 80F2 The DSR signal cannot be set because the module is a DTE device. 80F3 The DTR signal cannot be set because the module is a DCE device. * The error codes can be displayed as integer or hexadecimal values in the program editor. For additional information on toggling display formats, refer to "See also". You will find more detailed information on general error codes of the communication instructions in: "General status information of the communications blocks (Page 3009)". General status information of the communications blocks General information on execution status of the communications blocks The following table shows which general information can be output at the STATUS parameter of the communications blocks: Error code* Description (W#16#....) 8070 All internal instance memory is in use 8080 The identifier entered for the communications port is invalid 8081 Timeout, module error, internal error 8085 Error specifying the length at the LENGHT parameter. The specified length is "0" or greater than the maximum permitted value. 8090 Message length invalid, module invalid, message invalid 8091 Incorrect version in parameterization message 8092 Invalid record length in parameterization message * The error codes can be displayed as integer or hexadecimal values in the program editor. For additional information on toggling display formats, refer to "See also". USS Overview of USS instructions Introduction The USS instructions control the operation of drives that support the universal serial interface (USS). With the USS instructions, you can communicate with more than one drive via an RS-485 connection. WinCC Basic V13.0 System Manual, 02/2014 3009 Programming the PLC 9.7 References To do this, you require a CM 1241 RS-485 communications module or a CB 1241 RS-485 communications board. Up to three CM 1241 RS-485 modules and one CB 1241 RS-485 board can be installed in an S7-1200 CPU. Each RS-485 port can operate up to sixteen drives. The USS protocol uses a master/slave network for communication via a serial bus. The master uses an address parameter to send a message to a selected slave. A slave itself can never send without previously receiving a request. Direct exchange of messages between slaves is not possible. USS communication works in half duplex mode. The following figure shows an example of a USS network diagram: &0 56PRGXOHV 6&38 866GULYHVQHWZRUN 866GULYHVQHWZRUN Requirements for using the USS protocol General requirements for setting up a drive The use of 4 PKW words must be set up for the drives. The drives can be configured for 2, 4, 6 or 8 PZD words. The number of PZD words in the drive must correspond to the PZD_LEN input of the "USS_DRIVE (Page 3015)" instruction of the drive. The baud rate of all drives must match the baud rate of the BAUD input parameter of the "USS_PORT (Page 3014)" instruction. The drive must be set up for remote control. USS must be specified for the desired frequency value on the COM connection of the drive. 3010 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References 1 to 16 must be set as the drive address. This address must correspond to the address of the DRIVE input parameter of the "USS_DRIVE (Page 3015)" instruction. To control the direction of the drive, the polarity of the drive desired value must be set up. The RS-485 network must be connected correctly. Definition: PKW / PZD area The PKW area relates to the handling of the parameter-identifier-value interface. The PKW interface is not a physical interface but describes a mechanism that controls the exchange of parameters between two communications partners, in other words, reading and writing parameter values, parameter descriptions and corresponding texts and the handling of parameter changes due to spontaneous messages. All the tasks handled via the PKW interface are essentially tasks for operator control and monitoring, service and diagnostics. The PZD area includes the signals required for automation: - Control word(s), and setpoint(s) from the master to the slave - Status word(s), and actual value(s) from the slave to the master. Both areas together result in the user data field. This is transferred by the master to the slave as a job frame or by the slave to the master as a reply frame. Description Each communication module CM 1241 RS485 supports a maximum of 16 drives. A single instance data block contains temporary memory and buffer functions for all drives in the USS WinCC Basic V13.0 System Manual, 02/2014 3011 Programming the PLC 9.7 References network that are connected to a PtP communications module you installed. The USS instructions for these drives have shared access to the information in this data block. 866B3257 7KHGDWDEORFN866B'59B'%LVD EXIIHUWKDW\RXFDQRQO\DFFHVV LQGLUHFWO\YLDWKH866RSHUDWLRQV 866B'59B'% 866B'% 866B'59B'% 5HVHUYHGIRU 373 &20GDWD E\WHV 'ULYHGDWD 866B'59B'% 866B'59 '5,9( &056 RGHU &%56 7KHFRPPXQLFDWLRQV PRGXOHVXSSRUWVXSWR GULYHV(QWHUWR DVWKHER[LQSXWIRUWKH GULYHSDUDPHWHU 866B530 '5,9( 'ULYH 'ULYH 866B:30 '5,9( All drives (max. 16) that are connected to an RS485 port are part of the same USS network. All drives that are connected to a different RS485 port are part of a different USS network. As the S7-1200 supports up to three CM 1241 RS485 modules, you can set up up to three USS networks, each having a maximum of 16 drives, thus a total of 48 USS drives are supported. Each USS network is managed via a unique data block (three data blocks are required for three USS networks with three CM 1241 RS485 modules). All instructions that belong to a USS network must share this data block. This includes all "USS_DRIVE (Page 3015)", "USS_PORT (Page 3014)", "USS_RPM (Page 3017)", and "USS_WPM (Page 3019)" instructions for controlling all drives in a USS network. 3012 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References The instruction "USS_DRIVE (Page 3015)" is a function block (FB). When you insert the instruction "USS_DRIVE" in the editor, the "Call options" dialog will ask you to assign a DB to the instruction. - If this is the first "USS_DRIVE" instruction in this program for this USS network, you can accept the default DB assignment (or, if necessary, change the name) and the new DB will be created. - If, however, this is not the first "USS_DRIVE" instruction for this network, you must select the DB that was previously assigned to this USS network in the drop-down list in the "Call options" dialog. All "USS_PORT (Page 3014), USS_RPM (Page 3017)", and "USS_WPM (Page 3019)" instructions are functions (FCs). When you insert these FCs in the editor, no DB is assigned. Instead, you have to assign the DB in question to the USS_DB input of these instructions (double-click on the parameter field and then on the icon to display the available DBs). The instruction "USS_PORT (Page 3014)" controls communication between the CPU and the drives via the PtP communications module. Whenever this instruction is called, communication with a drive is processed. Your program must call this function quickly enough so that the drives do not report a timeout. The instruction can be called from the main program or any interrupt OB. The function block "USS_DRIVE (Page 3015)" gives your program access to a specified drive in the USS network. Its inputs and outputs correspond to the states and operating functions of the drive. If there are 16 drives in the network, "USS_DRIVE" must be called at least 16 times in your program, i.e., once for each drive. How quickly these blocks are called depends on the required speed for controlling drive functions. You can only call the instruction "USS_DRIVE" from the main program OB. CAUTION Call "USS_DRIVE", "USS_RPM", "USS_WPM" only from the main program OB. The instruction "USS_PORT" can be called from any OB, it is usually called from a time-delay interrupt OB. If the instruction "USS_PORT" is interrupted during execution, this may result in unexpected errors. The "USS_RPM" and "USS_WPM" instructions are used to read and write the operating parameters of the drive. These parameters control the internal mode of operation of the drive. A definition of these parameters can be found in the drive manual. Your program may also contain any number of these instructions; however only one read or write request can be active for a drive. You may only call the instructions "USS_RPM" and "USS_WPM" from the main program OB. Calculating the time for communication with the drive Communication with the drive is runs asynchronous to the cycle of the S7-1200. The S7-1200 runs through several cycles before communication with a drive is completed. The interval of "USS_PORT" is the time required for a drive transaction. The following table shows the minimum intervals for "USS_PORT" for each baud rate. Calling the "USS_PORT" more frequently than the "USS_PORT" interval will not increase the number of transactions. The timeout interval of the drive is the period of time available to a transaction if 3 attempts WinCC Basic V13.0 System Manual, 02/2014 3013 Programming the PLC 9.7 References are required to complete the transaction due to communications errors. By default, up to 2 further attempts are made for each transaction with the USS protocol. Baud rate Calculated minimum interval for calling USS_PORT (ms) Drive message interval timeout per drive (ms) 1200 790 2370 2400 405 1215 4800 212.5 638 9600 116.3 349 19200 68.2 205 38400 44.1 133 57600 36.1 109 115200 28.1 85 USS_PORT: Edit communication via USS network Description The "USS_PORT" instruction handles communication over the USS network. In the program, use one "USS_PORT" instruction per PtP communications port to control the transmission to or from one drive. All USS instructions that are assigned to one USS network and one PtP communications port must use the same instance data block. Call Your program must execute the "USS_PORT" instruction often enough to prevent timeouts in the drive. You should therefore call the "USS_PORT" instruction from a cyclic interrupt OB to prevent drive timeouts and keep the most recent USS data updates available for "USS_DRIVE (Page 3015)" calls. Parameters The following table shows the parameters of the "USS_PORT" instruction: Parameter Declaration Data type Memory area Description PORT Input PORT D, L or constant PtP communications port identifier Constant that can be referenced within the "Constants" tab of the default tag table. BAUD Input DINT USS_DB InOut USS_BASE D 3014 I, Q, M, D, L or constant Baud rate for USS communication. Reference to the instance DB of the "USS_DRIVE (Page 3015)" instruction. WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameter Declaration Data type Memory area Description ERROR Output BOOL I, Q, M, D, L ERROR is set to TRUE if an error occurs. A corresponding error code will be output at the STATUS output. STATUS (Page 3020) Output WORD I, Q, M, D, L Status value of the request. It indicates the result of the cycle or initialization. Additional information is available in the "USS_Extended_Error (Page 3020)" tag for some status codes. You will find more detailed information on valid data types in "Overview of the valid data types (Page 1204)". USS_DRIVE: Swap data with drive Description The "USS_DRIVE" instruction exchanges data with the drive by creating request messages and interpreting the drive response messages. A separate instruction must be used for each drive, but all USS instructions assigned to one USS network and one PtP communications module must use the same instance data block. You must create the DB name when you place the first "USS_DRIVE" instruction. Then reuse this DB that was created when the initial instruction was inserted. When the "USS_DRIVE" instruction is executed the first time, the drive indicated by the USS address (parameter DRIVE) is initialized in the instance DB. After this initialization, subsequent "USS_PORT (Page 3014)" instructions can start communication with the drive at this drive number. Changing the drive number requires a PLC STOP to RUN mode transition that initializes the instance DB. Input parameters are configured in the USS send buffer, and outputs are read from a "previous" valid response buffer if any exists. There is no data transmission during execution of the "USS_DRIVE" instruction. Communication with the drives takes place when "USS_PORT (Page 3014)" is executed. "USS_DRIVE" only configures the messages to be sent and interprets data received in a previous request. You can control the drive direction of rotation using either the DIR (BOOL) input or using the sign (positive or negative) at the SPEED_SP (REAL) input. The following table explains how these inputs work together to determine the drive direction, assuming the motor is wired for forward rotation. SPEED_SP DIR Direction of rotation of drive Value > 0 0 Reverse Value > 0 1 Forward Value < 0 0 Forward Value < 0 1 Reverse Parameters Expand the box to display all the parameters by clicking the bottom of the box. The parameter connections that are grayed are optional and do not need to be assigned. WinCC Basic V13.0 System Manual, 02/2014 3015 Programming the PLC 9.7 References The following table shows the parameters of the "USS_DRIVE" instruction: Parameter Declaration Data type Memory area Description RUN Input BOOL I, Q, M, D, L or constant Drive start bit: If this parameter has the value TRUE, this input enables the drive to run at the preset speed. OFF2 Input BOOL I, Q, M, D, L or constant "Electrical stop" bit: If this parameter has the value FALSE, this bit cause the drive to coast to a stop without braking. OFF3 Input BOOL I, Q, M, D, L or constant Fast stop bit - If this parameter has the value FALSE, this bit causes a fast stop by braking the drive. F_ACK Input BOOL I, Q, M, D, L or constant Fault acknowledge bit - This bit resets the fault bit on a drive. This bit is set after the fault is cleared to indicate to the drive that it no longer needs to indicate the previous fault. DIR Input BOOL I, Q, M, D, L or constant Drive direction control - This bit is set to indicate that the direction is forward (when SPEED_SP is positive). DRIVE Input USINT I, Q, M, D, L or constant Drive address: This input is the address of the USS drive. The valid range is drive 1 to drive 16. PZD_LEN Input USINT I, Q, M, D, L or constant Word length - This is the number of words of PZD data. Valid values are 2, 4, 6, or 8 words. The default is 2. SPEED_SP Input REAL I, Q, M, D, L or constant Speed setpoint - This is the speed of the drive as a percentage of configured frequency. A positive value specifies forward direction (when DIR has the value TRUE). CTRL3 Input WORD I, Q, M, D, L or constant Control word 3 - A value written to a user-configurable parameter on the drive. The user must configure this on the drive. Optional parameter CTRL4 Input WORD I, Q, M, D, L or constant Control word 4 - A value written to a user-configurable parameter on the drive. The user must configure this on the drive. Optional parameter CTRL5 Input WORD I, Q, M, D, L or constant Control word 5 - A value written to a user-configurable parameter on the drive. The user must configure this on the drive. Optional parameter CTRL6 Input WORD I, Q, M, D, L or constant Control word 6 - A value written to a user-configurable parameter on the drive. The user must configure this on the drive. CTRL7 Input WORD I, Q, M, D, L or constant Control word 7 - A value written to a user-configurable parameter on the drive. The user must configure this on the drive. Optional parameter CTRL8 Input WORD I, Q, M, D, L or constant Control word 8 - A value written to a user-configurable parameter on the drive. The user must configure this on the drive. Optional parameter NDR Output BOOL I, Q, M, D, L New data ready - If this parameter has the value TRUE, the bit indicates that the output contains data from a new communication request. 3016 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameter Declaration Data type Memory area Description ERROR Output BOOL I, Q, M, D, L Error occurred - If this parameter has the value TRUE, this indicates that an error has occurred and the STATUS output is valid. All other outputs are set to zero on an error. Communication errors are only reported at the ERROR and STATUS outputs of the "USS_PORT" instruction. STATUS (Page 3020) Output WORD I, Q, M, D, L Status value of the request. It indicates the result of the cycle. This is not a status word returned from the drive. RUN_EN Output BOOL I, Q, M, D, L Run enabled - This bit indicates whether the drive is running. D_DIR Output BOOL I, Q, M, D, L Drive direction - This bit indicates whether the drive is running forward. INHIBIT Output BOOL I, Q, M, D, L Drive inhibited - This bit indicates the state of the inhibit bit on the drive. FAULT Output BOOL I, Q, M, D, L Drive fault - This bit indicates that the drive has registered a fault. The user must eliminate the fault and then set the F_ACK bit to clear this bit. SPEED Output REAL I, Q, M, D, L Drive current speed (scaled value of drive status word 2) - The value of the speed of the drive as a percentage of configured speed. STATUS1 Output WORD I, Q, M, D, L Drive status word 1 - This value contains fixed status bits of a drive. STATUS3 Output WORD I, Q, M, D, L Drive status word 3 - This value contains a userconfigurable status word on the drive. STATUS4 Output WORD I, Q, M, D, L Drive status word 4 - This value contains a userconfigurable status word on the drive. STATUS5 Output WORD I, Q, M, D, L Drive status word 5 - This value contains a userconfigurable status word on the drive. STATUS6 Output WORD I, Q, M, D, L Drive status word 6 - This value contains a userconfigurable status word on the drive. STATUS7 Output WORD I, Q, M, D, L Drive status word 7 - This value contains a userconfigurable status word on the drive. STATUS8 Output WORD I, Q, M, D, L Drive status word 8 - This value contains a userconfigurable status word on the drive. You will find more detailed information on valid data types in "Overview of the valid data types (Page 1204)". USS_RPM: Readout parameters from the drive Description The "USS_RPM" instruction reads a parameter from the drive. All USS functions that are assigned to one USS network and one PtP communications module must use the same instance data block. "USS_RPM" must be called from the main program OB. WinCC Basic V13.0 System Manual, 02/2014 3017 Programming the PLC 9.7 References Parameter The following table shows the parameters of the "USS_RPM" instruction: Parameter Declaration Data type Memory area Description REQ Input BOOL I, Q, M, D, L Send request: If this parameter has the value TRUE, it indicates that a new read request is desired. This is ignored if the request for this parameter is already pending. DRIVE Input USINT I, Q, M, D, L or constant Drive address: This input is the address of the USS drive. The valid range is drive 1 to drive 16. PARAM Input UINT I, Q, M, D, L or constant Parameter number: This input specifies which drive parameter is written. The range of this parameter is 0 to 2047. See your drive manual for details on how to access any parameters above this range. INDEX Input UINT I, Q, M, D, L or constant Parameter index: This input specifies which drive parameter index is to be written. This is a 16-bit value where the least significant byte is the actual index value with a range of (0 to 255). The most significant byte may also be used by the drive and is drivespecific. See your drive manual for additional information. USS_DB InOut USS_BASE D Reference to the instance DB that is created and initialized when a "USS_DRIVE" instruction is inserted in your program. DONE Output BOOL If this parameter has the value TRUE, it indicates that the VALUE output holds the previously requested read parameter value. I, Q, M, D, L This bit is set when the "USS_DRIVE" instruction recognizes the read response from the drive. This bit is reset when either: you request the response data via another "USS_RPM" poll or the second of the next two calls of "USS_DRIVE (Page 3015)" is executed ERROR Output BOOL I, Q, M, D, L Error occurred - If this parameter has the value TRUE, this indicates that an error has occurred and the STATUS output is valid. All other outputs are set to zero on an error. Communication errors are only reported at the ERROR and STATUS outputs of the "USS_PORT (Page 3014)" instruction. STATUS (Page 3020) Output WORD I, Q, M, D, L This is the status value of the request. It indicates the result of the read request. Additional information is available in the "USS_Extended_Error (Page 3020)" tag for some status codes. VALUE Output VARIANT I, Q, M, D, L This is the value of the parameter that was read and is valid only when the DONE bit has the value TRUE. You will find more detailed information on valid data types in "Overview of the valid data types (Page 1204)". 3018 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References USS_WPM: Change parameters in the drive Description The "USS_WPM" instruction modifies a parameter in the drive. All USS functions that are assigned to one USS network and one PtP communications module must use the same instance data block. "USS_WPM" must be called from the main program OB. Note EEPROM write operations Beware of overusing the EEPROM write operation. Minimize the number of EEPROM write operations to extend the EEPROM life. Parameter The following table shows the parameters of the "USS_WPM" instruction: Parameter Declaration Data type Memory area Description REQ Input BOOL I, Q, M, D, L Send request: If this parameter has the value TRUE, it indicates that a new write request is desired. This is ignored if the request for this parameter is already pending. DRIVE Input USINT I, Q, M, D, L or constant Drive address: This input is the address of the USS drive. The valid range is drive 1 to drive 16. PARAM Input UINT I, Q, M, D, L or constant Parameter number: This input specifies which drive parameter is written. The range of this parameter is 0 to 2047. See your drive manual for details on how to access any parameters above this range. INDEX Input UINT I, Q, M, D, L or constant Parameter index: This input specifies which drive parameter index is to be written. This is a 16-bit value where the least significant byte is the actual index value with a range of (0 to 255). The most significant byte may also be used by the drive and is drive-specific. See your drive manual for additional information. EEPROM Input BOOL I, Q, M, D, L or constant Store to drive EEPROM: If this parameter has the value TRUE, values written to the drive parameter will be stored in the drive EEPROM. If this parameter has the value FALSE, the value written is only temporarily saved and will be lost the next time the drive is switched on. VALUE Input VARIANT I, Q, M, D, L or constant The value of the parameter that is to be written. It must be valid on the transition of REQ. USS_DB InOut USS_BASE D WinCC Basic V13.0 System Manual, 02/2014 This is a reference to the instance DB that is created and initialized when a "USS_DRIVE (Page 3015)" instruction is inserted in your program. 3019 Programming the PLC 9.7 References Parameter Declaration Data type Memory area Description DONE Output BOOL I, Q, M, D, L If this parameter has the value TRUE, the VALUE input was written to the drive. This bit is set when the "USS_DRIVE (Page 3015)" instruction recognizes the write response from the drive. This bit is reset when either: You request the drive's confirmation that the write operation has been completed via another "USS_WPM" query or when the second of the next two calls of "USS_DRIVE (Page 3015)" is executed. ERROR Output BOOL I, Q, M, D, L Error occurred: If this parameter has the value TRUE, this indicates that an error has occurred and the STATUS output is valid. All other outputs are set to zero on an error. Communication errors are only reported at the ERROR and STATUS outputs of the "USS_PORT (Page 3014)" instruction. STATUS (Page 3020) Output WORD I, Q, M, D, L This is the status value of the request. It indicates the result of the write request. Additional information is available in the "USS_Extended_Error (Page 3020)" tag for some status codes. You will find more detailed information on valid data types in "Overview of the valid data types (Page 1204)". Parameter STATUS of USS instructions STATUS parameter The following table contains the status codes of the USS operation that are output at the STATUS output of the USS instructions: STATUS* (W#16#....) Description 0000 No error 8180 The length of the drive response did not match the characters received from the drive. The drive number where the error occurred is returned in the "USS_Extended_Error" tag. See the extended error description below this table. 8181 The parameter VALUE is not of the data type WORD, REAL, or DWORD 8182 User supplied a parameter value of the type word and received a DWORD or REAL from the drive in the response 8183 User supplied a parameter value of the type DWORD or REAL and received a word from the drive in the response 8184 Response telegram from drive had a bad checksum. The drive number where the error occurred is returned in the "USS_Extended_Error" tag. See the extended error description below this table. 8185 Illegal drive address (valid drive address range: 1-16) 8186 Speed set point out of valid range (valid speed SP range: -200% to 200%) 8187 Wrong drive number responded to the request sent. The drive number where the error occurred is returned in the "USS_Extended_Error" tag. See the extended error description below this table. 8188 Illegal PZD word length specified (valid range = 2, 4, 6 or 8 words) 3020 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References STATUS* (W#16#....) Description 8189 Illegal baud rate was specified 818A Parameter request channel is in use by another request for this drive 818B Drive has not responded to requests and retries. The drive number where the error occurred is returned in the "USS_Extended_Error" tag. See the extended error description below this table. 818C Drive returned an extended error on a parameter request operation. See the extended error description below this table. 818D Drive returned an invalid access error on a parameter request operation. See your drive manual for information of why parameter access may be limited 818E Drive has not been initialized: This error code is output at "USS_RPM (Page 3017)" or "USS_WPM (Page 3019)" if the "USS_DRIVE (Page 3015)" instruction has not been called at least once for this drive. This prevents the initialization of the first cycle of "USS_DRIVE (Page 3015)" from overwriting a pending parameter read or write request since it initializes the drive as a new entry. To eliminate this error, call the "USS_DRIVE (Page 3015)" instruction for this drive. 80Ax-80Fx Specific errors returned from PtP (Point-to-Point) communication instructions called by the USS library: These error code values are not modified by the USS library and are defined in the PtP instruction descriptions. * The error codes can be displayed as integer or hexadecimal values in the program editor. For additional information on toggling display formats, refer to "See also". USS_Extended_Error - USS drive extended error codes USS drives support read and write access to a drive's internal parameters. This feature allows distributed control and configuration of the drive. Drive parameter access operations can fail due to errors such as values out of range or invalid requests in a drive's current mode. The drive generates an error code that is output in the "USS_Extended_Error" variable in the instance DB of the "USS_DRIVE (Page 3015)" instruction. This error code value is only valid for the last execution of the "USS_RPM (Page 3017)" or "USS_WPM (Page 3019)" instruction. The drive error code is put into the "USS_Extended_Error" tag when the value of STATUS is hexadecimal 818C. The error code of "USS_Extended_Error" depends on the drive variant. See the drive's manual for a description of the extended error codes for read and write parameter operations. MODBUS (RTU) MB_COMM_LOAD: Configure port on the PtP module for Modbus RTU Description The "MB_COMM_LOAD" instruction configures a port for communication using the Modbus RTU protocol. The following hardware can be used for this: Up to three point-to-point modules (PtP) CM 1241 RS485 or CM 1241 RS232 A communications board CB 1241 RS485 in addition to this After configuration of the port, you communicate over Modbus by executing the "MB_SLAVE" or "MB_MASTER" instruction. WinCC Basic V13.0 System Manual, 02/2014 3021 Programming the PLC 9.7 References Call "MB_COMM_LOAD" must be called once to configure the port for the Modbus RTU protocol. On completion of the configuration, the port can be used by the "MB_MASTER (Page 3025)" and "MB_SLAVE (Page 3032)" instructions. "MB_COMM_LOAD" only needs to be called again if one of the communication parameters has to be modified. Each "MB_COMM_LOAD" call deletes the communications buffer. To avoid data loss during communication, you should not call the instruction unnecessarily. One instance of "MB_COMM_LOAD" must be used to configure the port of each communication module that is used for Modbus communication. You assign a unique "MB_COMM_LOAD" instance data block for each port that you use. The S7-1200 CPU is limited to three communication modules. An instance data block is assigned when you insert the "MB_MASTER (Page 3025)" or "MB_SLAVE (Page 3032)" instruction. This instance data block is referenced when you specify the MB_DB parameter on the "MB_COMM_LOAD" instruction. Parameters The following table shows the parameters of the instruction "MB_COMM_LOAD": Parameter Declaration Data type Memory area Description REQ Input BOOL I, Q, M, D, L Execution of the instruction upon a rising edge. PORT Input PORT I, Q, M, D, L or constant ID of the communications port: I, Q, M, D, L or constant Baud rate selection: BAUD Input UDINT After you have inserted the communications module in the device configuration, the port ID appears in the drop-down list at the PORT box connection. This constant can also be referenced within the "Constants" tab of the tag table. 300, 600, 1200, 2400, 4800, 9600, 19200, 38400, 57600, 76800, 115200 All other values are invalid. PARITY Input UINT I, Q, M, D, L or constant Parity selection: 0 - None 1 - Odd 2 - Even FLOW_CTRL Input UINT I, Q, M, D, L or constant Flow control selection: 0 - (default) No flow control 1 - Hardware flow control with RTS always ON (does not apply to RS485 ports) 2 - Hardware flow control with RTS switched 3022 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameter Declaration Data type Memory area Description RTS_ON_DLY Input UINT I, Q, M, D, L or constant RTS on-delay selection: 0 - (default) No delay of RTS active until the first character of the message is transmitted. 1 to 65535 - Delay in milliseconds of "RTS active" until the first character of the message is transmitted (does not apply to RS-485 ports). RTS delays must be applied independent of the FLOW_CTRL selection. RTS_OFF_DLY Input UINT I, Q, M, D, L or constant RTS off-delay selection: 0 - (default) No delay after the last character transmitted until "RTS inactive" 1 to 65535 - Delay in milliseconds after the last character transmitted until "RTS inactive" (does not apply to RS-485 ports). RTS delays must be applied independent of the FLOW_CTRL selection. RESP_TO Input UINT I, Q, M, D, L or constant Response timeout: Time in milliseconds allowed by "MB_MASTER (Page 3025)" for the slave to respond. If the slave does not respond in this time, "MB_MASTER (Page 3025)" repeats the request or terminates the request with an error if the specified number of retries has been sent. 5 ms to 65535 ms (default = 1000 ms). MB_DB Input MB_BASE D A reference to the instance data block of the "MB_MASTER (Page 3025)" or "MB_SLAVE (Page 3032)" instructions. After you insert "MB_SLAVE (Page 3032)" or "MB_MASTER (Page 3025)" in your program, the DB identifier appears in the drop-down list at the MB_DB box connection. DONE Output BOOL I, Q, M, D, L Execution of instruction completed without error. ERROR Output BOOL I, Q, M, D, L Error: 0 - No error detected 1 - Indicates that an error was detected. An error code is output in the STATUS parameter. STATUS Output WORD I, Q, M, D, L Port configuration error code For additional information on valid data types, refer to "Overview of the valid data types (Page 1204)". Parameter STATUS Error code* (W#16#...) Description 0000 No error 8180 Invalid value for the port ID (wrong address for the communications module). WinCC Basic V13.0 System Manual, 02/2014 3023 Programming the PLC 9.7 References Error code* (W#16#...) Description 8181 Invalid baud rate value. 8182 Invalid parity value. 8183 Invalid flow control value. 8184 Invalid value for the timeout of the response (the time before which a timeout is reported must be at least 25 ms). 8185 Incorrect pointer in the MB_DB parameter to the instance DB of the "MB_MASTER (Page 3025)" or "MB_SLAVE (Page 3032)" instruction. * The error codes can be displayed as integer or hexadecimal values in the program editor. For additional information on toggling display formats, refer to "See also". MB_COMM_LOAD data block tags The table below shows the public static tags in the instance DB of MB_COMM_LOAD that you can use in your program. Table 9-92 Static tags in the instance DB Tag Data type Default Description ICHAR_GAP WORD 0 Delay for the character spacing between characters. This parameter is specified in milliseconds and is used to increase the anticipated period between the received characters. The corresponding number of bit times for this parameter is added to the Modbus standard value of 35 bit times (3.5 character times). RETRIES WORD 2 The number of repeated attempts by the master before the error code 0x80C8 is returned for "No response". MODE USINT 0 Mode Permitted modes are: 0 = Full duplex (RS232) 1 = Full duplex (RS422) four-wire mode (point-to-point) 2 = Full duplex (RS422) four-wire mode (multipoint master) 3 = Full duplex (RS422) four-wire mode (multipoint slave) 4 = Half duplex (RS485) two-wire mode LINE_PRE USINT 0 Receive line initial state Permitted defaults are: 0 = "No" default 1 = Signal R(A)=5V, signal R(B)=0 V (break detection): No break detection is possible with this default. Can only be selected with: "Full duplex (RS422) four-wire mode (point-topoint connection)" and "Full duplex (RS422) four-wire mode (multipoint slave)". 2 = Signal R(A)=0 V, signal R(B)=5 V: This default corresponds to the at-rest state (no send process is active). No break detection is possible with this default. CABLEBREAK USINT 0 Activate cable break detection: 0 - not activated 1 - activated 3024 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References MB_MASTER: Communicate via the PtP port as Modbus master Description of MB_MASTER Description The "MB_MASTER" instruction allows your program to communicate as a Modbus master using a port on a point-to-point module (CM) or a communications board (CB). You can access data in one or more Modbus slave devices. Before the "MB_MASTER" instruction can communicate with a port, "MB_COMM_LOAD (Page 3021)" must first execute. An instance DB is created when you insert the "MB_MASTER" instruction in your program. You specify this instance DB in the MB_DB input parameter of the "MB_COMM_LOAD (Page 3021)" instruction. Rules for Modbus master communication A port used for Modbus master requests cannot be used for "MB_SLAVE". A port can be used for one or more "MB_MASTER" calls if the same instance DB is used. The Modbus instructions do not use communication interrupt events to control the communication process. Your program must poll the "MB_MASTER" instruction for completed send and receive operations. Calling the instruction: - Call the "MB_MASTER" instruction if possible in a cyclic program OB. The instruction can only be called in a time delay or cyclic interrupt OB. - Do not call more than one "MB_MASTER" instruction in organization blocks with different priority classes. If a "MB_MASTER" instruction executes "preemptively" from a higher priority class, the instruction may execute incorrectly. - Do not call the "MB_MASTER" instruction in a startup, diagnostics or time error OB. After a transfer has started, the EN parameter (LAD/FBD) must remain set to the value "1" until the DONE or ERROR output parameter is set to "1" by the instruction. A renewed call by the REQ parameter while the instruction is executing causes an error. After the instruction executes, the bit in the REQ parameter remains set for the time specified by the BLOCKED_PROC_TIMEOUT parameter in the instance DB. If "MB_MASTER" sends a request to a slave, make sure that "MB_MASTER" continues to execute until the response from the slave arrives. WinCC Basic V13.0 System Manual, 02/2014 3025 Programming the PLC 9.7 References Parameters The following table shows the parameters of the "MB_MASTER" instruction: Parameters Declaration Data type Memory area Description REQ (Page 3028) Input BOOL I, Q, M, D, L Request input: 0 - No request 1 - Request to transmit data to Modbus slave(s) MB_ADDR Input UINT I, Q, M, D, L or constant Modbus RTU station address: Default address range: 0 to 247 Extended address range: 0 to 65535 The value "0" is reserved for broadcasting a message to all Modbus slaves. Modbus function codes 05, 06, 15, and 16 are the only function codes supported for broadcast. MODE (Page 3028) Input USINT I, Q, M, D, L or constant Mode selection: Specifies the type of request: Read, write, or diagnostics: Refer to the Modbus functions table for details. DATA_ADDR (Page 3028) Input UDINT I, Q, M, D, L or constant Starting address in the slave: Specifies the starting address of the data to be accessed in the Modbus slave. You will find the valid addresses in the Modbus functions table. DATA_LEN Input UINT I, Q, M, D, L or constant Data length: Specifies the number of bits or words to be accessed in this request. You will find the valid lengths in the Modbus functions table. DATA_PTR (Page 3029) Input VARIANT M, D Points to the DB or bit memory address of the CPU for the data to be written or read. For a DB, this must be created with the "Standard - compatible with S7-300/400" access type. DONE Output BOOL I, Q, M, D, L 0: Transaction not completed BUSY Output BOOL I, Q, M, D, L ERROR Output BOOL I, Q, M, D, L 1: Transaction completed without error 0: No "MB_MASTER" transaction in progress 1: "MB_MASTER" transaction in progress 0: No error 1: Error, the error code is indicated by the STATUS parameter STATUS Output WORD I, Q, M, D, L Execution condition code You will find more detailed information on valid data types in "Overview of the valid data types (Page 1204)". 3026 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References STATUS parameter Table 9-93 Error code* Communications and configuration error messages of the instruction Description (W#16#....) 0000 No error 80C8 Slave timeout. Check the baud rate, parity and the connectors on the slave. 80D1 The receiver issued a flow control request to suspend an active transmission and never re-enabled the transmission within the wait time. This error is also generated during hardware flow control if the recipient does not detect CTS within the wait time. 80D2 The send request was aborted because no DSR signal is received from the DCE. 80E0 The message was terminated because the receive buffer is full. 80E1 The message was terminated as a result of a parity error. 80E2 The message was terminated as a result of a framing error. 80E3 The message was terminated as a result of an overrun error. 80E4 The message was terminated as a result of the specified length exceeding the total buffer size. 8180 Invalid value for the port ID. 8186 Invalid Modbus station address 8188 The MODE parameter has an invalid value for a broadcast call. 8189 Invalid data address value. 818A Invalid data length value. 818B Invalid pointer to the local data source/destination: Size not correct 818C The DATA_PTR parameter has an invalid pointer. Use a pointer to a bit memory area or a DB with the "Standard - compatible with S7-300/400" access type. 8200 Port is busy processing a send request * The error codes can be displayed as integer or hexadecimal values in the program editor. For additional information on toggling display formats, refer to "See also". Table 9-94 Error code* Error messages of the Modbus protocol Response code of slave Description (W#16#....) 8380 - CRC error 8381 01 Function code not supported 8382 03 Data length error 8383 02 Error in the data address or address outside the valid range of DATA_PTR 8384 > 03 Data value error 8385 03 Data diagnostic code value not supported (function code 08) 8386 - Function code of the response does not match the function code of the query. 8387 - Response from wrong slave WinCC Basic V13.0 System Manual, 02/2014 3027 Programming the PLC 9.7 References Error code* Response code of slave Description (W#16#....) 8388 - The response of the slave to a write call is not correct. The data sent by the slave does not match the query from the master. * The error codes can be displayed as integer or hexadecimal values in the program editor. For additional information on toggling display formats, refer to "See also". Parameter REQ Description REQ = FALSE: No request REQ = TRUE: Request to transmit data to Modbus slave(s) You can control this input by means of a level-controlled or edge-controlled contact. A state machine is started every time this input is activated to ensure that another instruction "MB_MASTER" that uses the same instance DB can only issue a request when the current request has been processed. All other input states are recorded and saved internally for the current request until the reply has been received or an error has been detected. If the same instance of "MB_MASTER" is executed again with REQ input = 1 before the current request is completely processed, no subsequent transfers are made. However, if the request has been processed, a new request is issued at the time when "MB_MASTER" is executed again with REQ input = 1. DATA_ADDR and MODE parameters Description You specify the start address for data access to the Modbus slave using the DATA_ADDR parameter. With the MODE parameter and the Modbus address, you specify the function code to be transferred to the Modbus slave. The following table shows the relationship between the MODE parameter, the function code and Modbus address range. MODE Modbus function Data length Operation and data Modbus address 0 01 1 to 2000 Read output bits: 1 to 9999 1 to 1992 0 02 1 to 2000 1 to 1992 0 03 04 3028 (1) 1 to 125 1 to 124 1 to (1992 or 2000) bits per query Read input bits: (1) 1 to 125 1 to 124 0 (1) (1) 10001 to 19999 1 to (1992 or 2000) bits per query Read holding register: 40001 to 49999 or 1 to (124 or 125) WORD per query 400001 to 465535 Read input WORD: 30001 to 39999 1 to (124 or 125) WORD per query WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References MODE Modbus function Data length Operation and data Modbus address 1 05 1 Writing an output bit: 1 to 9999 1 06 1 1 15 2 to 1968 One bit per query 2 to 1960 1 16 2 to 123 2 11 15 16 11 40001 to 49999 or 1 WORD per query 400001 to 465535 Writing multiple output bits: 1 to 9999 2 to (1960 or 1968) bits per query Writing multiple holding registers: 40001 to 49999 or 2 to (122 or 123) WORD per query 400001 to 465535 1 to 1968 Writing one or more output bits: 1 to 9999 2 to 1960 (1) 1 to (1960 or 1968) bits per query 1 to 123 Writing one or more holding registers: 40001 to 49999 or 2 to 122 (1) 1 to (122 or 123) WORD per query 400001 to 465535 0 Reading out the communications status word of the slaves and the event counter: - 2 to 122 2 (1) Writing a holding register: (1) The status word indicates execution of the instruction (0: is not executing; 0xFFFF: is executing). The event counter is incremented each time a message is transferred successfully. The DATA_ADDR and DATA_LEN parameters of the "MB_MASTER" instruction are ignored with this function. 80 08 1 Checking the slave status by reading the error code (0x0000): - 1 WORD per query 81 08 1 Resetting the event counter of the slave with the diagnostics code 0x000A: - 1 WORD per query 3 to 10, 12 to 79, 82 to 2555 Reserved - For the "Extended address range", the maximum data length is reduced by one byte or one WORD depending on which data type is used for the function. (1) Parameter DATA_PTR Description The DATA_PTR parameter is a pointer to a data block or bit memory from which the data should be written or read. If you use a data block, create a global data block with the "Standard - compatible with S7-300/400" access type. WinCC Basic V13.0 System Manual, 02/2014 3029 Programming the PLC 9.7 References Data block structures for the DATA_PTR parameter These data types are valid for reading of words of Modbus addresses 30001 to 39999, 40001 to 49999, and 400001 to 465536 and also for writing of words to Modbus addresses 40001 to 49999 and 400001 to 465536. - Standard array of WORD, UINT, or INT data types (see below). - Named WORD, UINT, or INT structure where each element has a unique name and 16 bit data type. - Named complex structure where each element has a unique name and 16 bit or 32 bit data type. For reading and writing of bits of Modbus addresses 00001 to 09999 and 10001 to 19999. - Standard array of Boolean data types. - Named Boolean structure of uniquely named Boolean variables. Although not required, it is recommended that each "MB_MASTER" instruction has its own separate memory area in a global data block. The reason for this recommendation is that there is a greater possibility of data corruption if multiple "MB_MASTER" instructions are reading and writing the same area of a global data block. The memory areas for DATA_PTR do not need to be in the same global data block. You can create one data block with multiple areas for Modbus read operations, one data block for Modbus write operations, or one data block for each slave station. Instance DB of the "MB_MASTER" instruction Static variables of the instance DB The following table describes the static variables of the instance DB of the instruction that you can use in the user program. Variable Data type Description MB_STATE UINT Internal status of the Modbus instruction BLOCKED_ PROC_TIMEOUT REAL Time between completion of the instruction call and resetting the ACTIVE bit in the instance DB. The time buffer is used to avoid execution of the instruction being terminated before a job has been sent completely. The default time is 500 ms. EXTENDED_ ADDRESSING BOOL Configuring addressing: 0: Default address area (1 byte) 1: Extended address area (2 bytes) For additional information, refer to the section EXTENDED_ADDRESSING: Instance DB of the "MB_SLAVE" instruction (Page 3035) 3030 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Sample program for a Modbus master Networks (LAD) Network 1: Initialize parameters of the RS-485 module only once during the first cycle. Network 2: Read 100 words from the holding register of the slave. Network 3: This is an optional network that displays the values of the first 3 words as soon as the read operation has executed. Network 4: Write 64 bits to the process image output, starting at slave address Q2.0. WinCC Basic V13.0 System Manual, 02/2014 3031 Programming the PLC 9.7 References MB_SLAVE: Communicate via the PtP port as Modbus slave Description of MB_SLAVE Description The "MB_SLAVE" instruction allows your program to communicate as a Modbus slave using a port on a point-to-point module (PtP) or a communications board (CB). A Modbus RTU master can issue a request and then your program responds via "MB_SLAVE" execution. You must assign a unique instance data block when you insert the "MB_SLAVE" instruction in your program. This instance data block is used when you specify it at the MB_DB parameter of the "MB_COMM_LOAD (Page 3021)" instruction. Modbus communication function codes (1, 2, 4, 5, and 15) can read and write bits and words directly in the process image input and process image output in the target system. The following table shows the mapping of Modbus addresses to the process image in the CPU. Modbus functions of "MB_SLAVE" S7-1200 Codes Function Data area Address range Data area CPU address 01 Read bits Output 1 to 02 Read bits Input 10001 to 8192 Process image output Q0.0 to Q1023.7 18192 Process image input I0.0 to I1023.7 04 Read words Input 30001 to 30512 Process image input IW0 to IW1022 05 Write bit Output 15 Write bits Output 1 to 8192 Process image output Q0.0 to Q1023.7 1 to 8192 Process image output Q0.0 to Q1023.7 Modbus communication function codes (function codes 3, 6, 16) use a separate holding register. To do this, you can use bit memory or a data block with the "Standard - compatible with S7-300/400" access type. You specify the type of the holding register using the MB_HOLD_REG parameter of the MB_SLAVE instruction. The following table shows the mapping of the Modbus holding register to the DB address of MB_HOLD_REG in the target system. 3032 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Modbus functions of "MB_SLAVE" Codes 03 06 16 Function Data area Read words Write word Write words S7-1200 Address range Address in the DB Bit memory address (WORD number) (BYTE number) (BYTE number) MW0 to CPU limit Holding register 40001 to 49999 or DW0 to DW19998 or 400001 to 465535 DW0 to DW131068 Holding register 40001 to 49999 or DW0 to DW19998 or 400001 to 465535 DW0 to DW131068 Holding register 40001 to 49999 or DW0 to DW19998 or 400001 to 465535 DW0 to DW131068 The table below shows the supported Modbus diagnostic functions. S7-1200 "MB_SLAVE" Modbus diagnostic functions Codes Subfunction Description 08 0000H Return query data echo test: The "MB_SLAVE" instruction returns the echo of a received data word to a Modbus master. 08 000AH Clear communication event counter: The "MB_SLAVE" instruction clears the communication event counter that is used for Modbus function 11. 11 - Get communication event counter: The "MB_SLAVE" instruction uses an internal communication event counter for recording the number of successful Modbus read and write requests that are sent to the Modbus slave. The counter is not incremented on any Function 8, Function 11, or broadcast requests. It is also not incremented on any requests that result in a communication error (for example, parity or CRC errors). The "MB_SLAVE" instruction supports broadcast write requests from Modbus masters as long as the requests include access to valid addresses. Regardless of the validity of a request, "MB_SLAVE" gives no response to a Modbus master as the result of a broadcast request. Rules of Modbus slave communication "MB_COMM_LOAD" must be executed to configure a port, before the "MB_SLAVE" instruction can communicate with this port. If a port is to respond as a slave to a Modbus master, then that port cannot be used by "MB_MASTER (Page 3025)". Only one instance of "MB_SLAVE" can be used with a given port. The Modbus instructions do not use communication interrupt events to control the communication process. Your program must control the communication process by polling the "MB_SLAVE" instruction for completed send and receive operations. The "MB_SLAVE" instruction must be executed periodically at a rate that allows it to make a timely response to incoming requests from a Modbus master. It is therefore advisable to call the instruction in a cyclic program OB. Calling the "MB_SLAVE" instruction in an interrupt OB is possible but not advisable since it can lead to long delays in execution. WinCC Basic V13.0 System Manual, 02/2014 3033 Programming the PLC 9.7 References Frequency of execution of "MB_SLAVE" The "MB_SLAVE" instruction must be executed periodically to receive each request from the Modbus master and to respond as required. The frequency of execution of "MB_SLAVE" is dependent upon the specified response timeout period of the Modbus master. This is illustrated in the following diagram. $'5 )& 'DWD 5HVSRQVH WLPHRXWSHULRG &5& 0DVWHUVHQGV 6WDUW &5& LQWHUYDO FKDUDFWHUWLPHV $'5 6ODYHVHQGV 5HVSRQVH GHOD\WLPH $'5 )& 'DWD 6WDUW &5& LQWHUYDO The response timeout period is the amount of time a Modbus master waits for the start of a response from a Modbus slave. This time period is not defined by the Modbus protocol, but rather by a parameter of each Modbus master. The frequency of execution (time between one execution and the next execution) of "MB_SLAVE" must be based on the particular parameters of your Modbus master. As a minimum, you should execute "MB_SLAVE" twice within the response timeout period of the Modbus master. Parameters The following table shows the parameters of the "MB_SLAVE" instruction: Parameter Declaration Data type Memory area Description MB_ADDR Input USINT I, Q, M, D, L or constant Station address of the Modbus slave (address range: 0 to 255) MB_HOLD_REG Input VARIANT D Pointer to the Modbus holding register DB. The DB must be created with the "Standard - compatible with S7-300/400" access type. NDR Output BOOL I, Q, M, D, L New data ready: 0: No new data 1: Indicates that new data has been written by the Modbus master DR Output BOOL I, Q, M, D, L Read data: 0: No data read 1: Indicates that data has been read by the Modbus master ERROR Output BOOL I, Q, M, D, L 0: No error detected 1: Error, a corresponding error code is output in the STATUS STATUS Output WORD I, Q, M, D, L Error code You will find more detailed information on valid data types in "Overview of the valid data types (Page 1204)". 3034 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References STATUS parameter STATUS* (W#16#....) Description 80C8 The specified response timeout (refer to RCVTIME or MSGTIME) is "0". 80D1 The receiver issued a flow control request to suspend an active transmission and never re-enabled the transmission within the wait time. This error is also generated during hardware flow control if the recipient does not detect CTS within the wait time. 80D2 The send request was aborted because no DSR signal is received from the DCE. 80E0 The message was terminated because the receive buffer is full 80E1 The message was terminated as a result of a parity error 80E2 The message was terminated as a result of a message frame error 80E3 The message was terminated as a result of a overrun error 80E4 The message was terminated as a result of the specified length exceeding the total buffer size 8180 Invalid value for the port ID. 8186 Invalid Modbus station address 8187 Invalid pointer to MB_HOLD_REG-DB 818C Pointer to a type safe DB type MB_HOLD_REG (must be a Classic DB type) Response code sent to Modbus master (B#16#...) 8380 No response CRC error 8381 01 Function code not supported or not supported in a broadcast 8382 03 Data length error 8383 02 Error in the data address or address outside the valid range of MB_HOLD_REG 8384 03 Data value error 8385 03 Data diagnostic code value not supported (function code 08) * The error codes can be displayed as integer or hexadecimal values in the program editor. For additional information on toggling display formats, refer to "See also". Instance DB of the "MB_SLAVE" instruction Static variables of the instance DB The following table describes the static variables of the instance DB of the instruction that you can use in the user program. Your program can write values to the HR_Start_Offset and Extended_Addressing variables and control the Modbus slave operations. The other variables can be read to monitor the Modbus status. Variable Data type Description HR_Start_Offset WORD Start address of the Modbus holding register (default = " 0") Extended_ Addressing BOOL Configuring addressing: 0: Default address area (1 byte) 1: Extended address area (2 bytes) WinCC Basic V13.0 System Manual, 02/2014 3035 Programming the PLC 9.7 References Variable Data type Description Request_Count WORD Total number of queries received by the slave Slave_Message_ Count WORD Number of queries sent to this specific slave Bad_CRC_Count WORD Number of received queries with CRC errors Broadcast_Count WORD Number of received broadcast queries Exception_Count WORD Number of Modbus-specific errors that require the return of an exception Success_Count WORD The number of requests received for this specific slave without protocol errors HR_Start_Offset The addresses of the Modbus holding register start at 40001 or 400001. These addresses correspond to the start address of the holding register in the target system memory. Using the HR_Start_Offset variable, you can set the offset to a different start address. Example: A holding register starts at MW 100 and has a length of 100 WORD. With an offset of 20 in the HR_Start_Offset parameter, the holding register begins at address 40021 instead of 40001. Each address below 40021 and above 400119 causes an addressing error. HR_Start_Offset = 0 HR_Start_Offset = 20 Modbus word address S7-1200 byte address Modbus word address S7-1200 byte address Minimum 40001 MW100 40021 MW100 Maximum 40099 MW198 40119 MW198 Extended_Addressing To address the Modbus slave, a single byte (default address range) or a double byte (extended address range) can be configured. Extended addressing is used to address more than 247 devices in a single network. If you decide on extended addressing, you can address a maximum of 64,000 addresses. Below, you will see a frame of Modbus function 1 as an example. Table 9-95 Slave address with one byte (byte 0) Function 1 Byte 0 Byte 1 Byte 2 Byte 3 Request Slave address F code Valid response Slave address F code Length Error response Slave address 0x81 E code 3036 Start address Byte 4 Byte 5 Length of the coils Coil data WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Table 9-96 Slave address with two bytes (byte 0 and byte 1) Function 1 Byte 0 Byte 1 Byte 2 Byte 3 Byte 4 Request Slave address F code Valid response Slave address F code Length Start address Error response Slave address 0x81 F code Byte 5 Byte 6 Length of the coils Coil data Sample program for a Modbus slave Networks (LAD) Network 1: Initialize parameters of the RS-485 module only once during the first cycle. Network 2: Check the requests of the Modbus master in every cycle. 100 words starting at MW1000 are configured for the Modbus holding register. WinCC Basic V13.0 System Manual, 02/2014 3037 Programming the PLC 9.7 References MODBUS (TCP) MODBUS (TCP) (S7-1200) MB_CLIENT: Communicating via PROFINET as a Modbus TCP client Description of MB_CLIENT Description The "MB_CLIENT" instruction communicates as a Modbus TCP client via the PROFINET connection of the S7-1200 CPU. To use the instruction, you do not require any additional hardware module. With the "MB_CLIENT" instruction, you establish a connection between the client and the server, send requests and receive responses and control connection termination of the Modbus TCP server. Parameters The following table shows the parameters of the "MB_CLIENT" instruction: Parameter Declaration Data type Description REQ (Page 3040) Input BOOL Communication request with the Modbus TCP server The REQ parameter is level-controlled. This means that as long as the input is set (REQ=true), the instruction sends communication requests. The instance DB for other clients is blocked with the communications request. Changes to the input parameters will not become effective until the server has responded or an error message has been output. If the parameter REQ is set again during an ongoing Modbus request, no additional transmission takes place afterwards. DISCONNECT (Page 3040) Input BOOL With this parameter, you control the establishment and termination of the connection to the Modbus server: 0: Establish a communications connection to the specified IP address and port number. 1: Disconnect the communication connection. No other function is executed during connection termination. The value 7003 is output at the STATUS parameter after successful connection termination. The request is sent immediately if the REQ parameter is set during connection establishment. CONNECT_ID Input UINT Unique ID to identify the connection. Each instance of the instructions "MB_CLIENT" and "MB_SERVER (Page 3045)" must be assigned a unique connection ID. IP_OCTET_1 Input USINT 1. Octet of the IP address* of the Modbus TCP server. IP_OCTET_2 Input USINT 2. Octet of the IP address* of the Modbus TCP server. 3038 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameter Declaration Data type Description IP_OCTET_3 Input USINT 3. Octet of the IP address* of the Modbus TCP server. IP_OCTET_4 Input USINT 4. Octet of the IP address* of the Modbus TCP server. IP_PORT Input UINT IP port number of the server to which the client establishes the connection and communicates using the TCP/IP protocol (default value: 502). MB_MODE (Page 3041) Input USINT Selects the mode of the request (read, write or diagnostics). MB_DATA_ADDR (Page 3041) Input UDINT Start address of the data accessed by the "MB_CLIENT" instruction. DATA_LEN Input UINT Data length: Number of bits or words for the data access (see "MB_MODE and MB_DATA_ADDR parameters" - data length). MB_DATA_PTR (Page 3042) InOut VARIANT Pointer to the Modbus data register: The register is a buffer for the data received from the Modbus server or to be sent to the Modbus server. The pointer must reference a global data block with standard access. The number of bits addressed must be divisible by 8. DONE Out BOOL The bit at output parameter DONE is set to "1" as soon as the last job is completed without errors. BUSY Out BOOL 0: No "MB_CLIENT " job in progress ERROR Out BOOL 1: "MB_ CLIENT " job in progress 0: No error 1: Error occurred. The cause of error is indicated by the STATUS parameter. STATUS (Page 3043) Out WORD Error code of the instruction. * 8-bit long component of the 32-bit IPv4 IP address of the Modbus TCP server. For additional information on valid data types, refer to "Overview of the valid data types (Page 1204)". Note Consistent input data during an "MB_CLIENT" call When a Modbus client calls a Modbus instruction, the status of the input parameters is stored internally and then compared at the next call. The comparison is used to determine whether this particular call initialized the current request. Several "MB_CLIENT" calls can be executed if you use a common instance DB. The values of the input parameters must not be changed while an "MB_CLIENT" instance is being executed. If the input parameters are changed during execution, "MB_CLIENT" cannot be used to check whether or not the instance is currently being executed. Multiple client connections A Modbus TCP client can support several TCP connections and the maximum number of connections depends on the CPU being used. The total number of connections of one CPU, including those of the Modbus TCP clients and server must not exceed the maximum number of supported connections. Modbus TCP connections can also be shared by client and/or server connections. WinCC Basic V13.0 System Manual, 02/2014 3039 Programming the PLC 9.7 References With individual client connections, remember the following rules: Each "MB_CLIENT" connection must use a unique instance DB. For each "MB_CLIENT" connection, a unique server IP address must be specified. Each "MB_CLIENT" connection requires a unique connection ID. The relevant individual connection ID must be used for each individual instance DB of the instruction. The connection ID and instance DB belong together in pairs and must be unique for each connection. Unique numbers for the IP port may or may not be required depending on the server configuration. Static tags of the instruction The following table describes the editable static tags of the instance data block of the "MB_CLIENT" instruction. Tag Start value Description Blocked_Proc_Timeo REAL ut Data type 3.0 Wait time in seconds before the static tag ACTIVE is reset if there is a blocked Modbus instance. This can, for example, occur if a client request is output and the execution of the client function aborts before the request was fully executed. The maximum wait time is 55 seconds. MB_Transaction_ID WORD 1 Transaction ID of the Modbus TCP protocol. The start value of "1" should only be changed if the Modbus TCP server requires a different value. MB_Unit_ID BYTE 255 Unit ID of the Modbus protocol. The tag corresponds to the slave address of the Modbus RTU protocol. Change this value only if the Modbus TCP server can be used as a gateway and is controlled by the application program within the Modbus server. RCV_TIMEOUT REAL 2.0 Time interval in seconds in which the "MB_CLIENT" instruction waits for a response from the server. Connected BOOL 0 Indicates whether the connection to the assigned client has been established or not: 1 = connected, 0 = not connected. See also MB_CLIENT example 1: Send several requests via a TCP connection (Page 3051) MB_CLIENT example 2: Send multiple requests via several TCP connections (Page 3052) MB_CLIENT example 3: Coordinate several requests (Page 3053) REQ and DISCONNECT parameters Description If no instance of the "MB_CLIENT" instruction is executing and if the value of the DISCONNECT parameter is "0", a new job executes if REQ=1. If there is not yet a connection, this is established during execution. 3040 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References If the same instance of the "MB_CLIENT" instruction executes again (DISCONNECT = 0 and REQ = 1), before the active job was executed, this is not executed on completion of the active job. A new job can only be started on completion of the active job (REQ = 1). You can monitor the status of execution with the DONE parameter. You can use this to monitor the status of execution if the "MB_CLIENT" instruction is executed sequentially. See also Description of MB_CLIENT (Page 3038) MB_MODE and MB_DATA_ADDR parameters Description Instead of a function code, the "MB_CLIENT" instruction uses the MB_MODE parameter. The MB_DATA_ADDR parameter is used to specify the Modbus start address of the data you want to access. The combination of the parameters MB_MODE and MB_DATA_ADDRdefines the function code used in the current Modbus message. The following table shows the relationship between the MB_MODE parameter, the Modbus function and the address space. MB_MODE Modbus function Data length Function and data type MB_DATA_ADDR 0 01 1 to 2000 Read output bits: 1 to 9999 1 to 2000 bits per call 0 02 1 to 2000 Read input bits: 10001 to 19999 1 to 2000 bits per call 0 03 1 to 125 Read holding register: 40001 to 49999 1 to 125 WORD per call 0 04 1 to 125 Read input words: 30001 to 39999 1 to 125 WORD per call 1 05 1 Write an output bit: 1 to 9999 1 06 1 1 15 2 to 1968 1 16 2 to 123 Write several holding registers: 2 to 123 WORD per call 40001 to 49999 2 15 1 to 1968 Write one or more output bits: 1 to 9999 One bit per call Write a holding register: 40001 to 49999 1 WORD per call Write multiple output bits: 1 to 9999 2 to 1968 bits per call 1 to 1968 bits per call 2 16 1 to 123 Write one or more holding registers: 40001 to 49999 1 to 123 WORD per call WinCC Basic V13.0 System Manual, 02/2014 3041 Programming the PLC 9.7 References MB_MODE Modbus function Data length Function and data type MB_DATA_ADDR 11 11 0 Read status word and event counter of server communication: - The status word reflects the the processing status (0 - not processing, 0xFFFF - processing). The event counter is incremented each time a message is sent successfully. The MB_DATA_ADDR and MB_DATA_LEN parameters of the "MB_CLIENT" instruction are not evaluated when this function executes. 80 08 1 Check the server status with the error code 0x0000 (return loop test - the server sends the request back): - 1 WORD per call 81 08 1 Reset the event counter of the server with the error code 0x000A: 1 WORD per call 3 to 10, 12 to 79, 82 to 255 Reserved See also Description of MB_CLIENT (Page 3038) MB_DATA_PTR parameter Description The MB_DATA_PTR parameter is a pointer to a data buffer for storing the data read from or written to the Modbus server. As the data buffer, you can use a global data block or a memory area (M). For a buffer in the memory area (M), use a pointer in the ANY format as follows: "P#bit address" "data type" "length" (example: P#M1000.0 WORD 500). The MB_DATA_PTR parameter uses a communications buffer: For the communication functions of the "MB_CLIENT" instruction: - Reading and writing of 1 bit of data of the Modbus server addresses 00001 to 09999 and 10001 to 19999. - Reading of 16-bit WORD data of the Modbus server addresses 30001 to 39999 and 40001 to 49999. - Writing 16-bit WORD data of the Modbus server addresses 40001 to 49999. During data transmission (length: bit or WORD) from or to the global DB or the memory area (M) that you assigned with the MB_DATA_PTR parameter. 3042 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References If you use a data block for the buffer in the MB_DATA_PTR parameter, you will need to assign data types to the DB elements. Use the 1-bit data type BOOL for a Modbus bit address Use a 16-bit data type such as WORD, UINT, INT or REAL for a Modbus WORD address. Use a 32-bit data type (double word) such as DWORD, DINT or REAL for two Modbus WORD addresses. With MB_DATA_PTR, you can also access complex DB elements such as: - Standard arrays - Structures with unique element names - Complex structures with unique naming of the elements and data type lengths of 16 or 32 bits. The data areas for the MB_DATA_PTR parameter can also be in different global data blocks (or in different memory areas). You can, for example, use a data block for the the read jobs and another one for the write jobs or a separate data block for each "MB_CLIENT" station. See also Description of MB_CLIENT (Page 3038) Parameter STATUS Parameter STATUS (general status information) STATUS* (W#16#) Description 0000 Instruction executed without errors. 0001 Connection established. 0003 Connection terminated. 7000 No call active (REQ=0). 7001 First call with REQ=1: Processing started; BUSY has the value 1. 7002 Intermediate call (REQ irrelevant). Processing already active; BUSY has the value 1. 7003 Connection is being terminated. 7004 Connection established and monitored. No job processing active. 7005 Data was sent. 7006 Data was received. 80BB Invalid value at ACTIVE_EST parameter (identifier for the type of connection establishment, see T_CON_PARAM): Only passive connection establishment permitted for server (ACTIVE_EST = FALSE). Only active connection establishment permitted for client (ACTIVE_EST = TRUE). WinCC Basic V13.0 System Manual, 02/2014 3043 Programming the PLC 9.7 References STATUS* (W#16#) Description 8380 Received Modbus frame has incorrect format or too few bytes were received. * The error codes can be displayed as integer or hexadecimal values in the program editor. For additional information on toggling display formats, refer to "See also". Parameter STATUS (protocol error) STATUS* (W#16#) Code of the response to the Modbus client (B#16#) Description 8381 01 Function code is not supported. 8382 03 Error in data length. 8383 02 Error in the data address or access outside the address area of MB_DATA_PTR (Page 3042). 8384 03 Error in data value. 8385 03 Error codes of diagnostics not supported (function code 08). * The error codes can be displayed as integer or hexadecimal values in the program editor. For additional information on toggling display formats, refer to "See also". Parameter STATUS (parameter error) In addition to the errors listed in the following table, errors are also possible with the "MB_CLIENT" instruction caused by the communications instructions ("TCON", "TDISCON", "TSEND" and "TRCV"). STATUS* (W#16#) Description 80C8 No response of the server in the defined period. Check the connection to the Modbus server. This error is only reported on completion of the configured repeated attempts. If the "MB_CLIENT" instruction does not receive an answer with the originally transferred transaction ID (MB_TRANSACTION_ID tag) within the defined period, this error code is output. 8188 The MB_MODE parameter has an invalid value. 8189 Invalid addressing of data at the MB_DATA_ADDR parameter. 818A Invalid data length at the MB_DATA_LEN parameter. 818B The MB_DATA_PTR parameter has an invalid pointer. You should also check the values of the MB_DATA_ADDR (Page 3041) and MB_DATA_LEN parameters. 818C The MB_DATA_PTR (Page 3042) pointer references an an optimized data block. Either use a data block with standard access or a memory area Timeout at parameter BLOCKED_PROC_TIMEOUT (see static tags of instruction). The limit of 55 seconds has been exceeded. 818D The transaction ID (MB_TRANSACTION_ID tag) does not correspond to the one sent originally (see static tags of instruction). 8200 A further Modbus request is currently being processed via the port. Another instance of MB_CLIENT with the same connection parameters is processing an existing Modbus request. 8380 3044 Received block of transferred Modbus data is not well-formed or too few bytes were received. WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References STATUS* (W#16#) Description 8386 Received function code does not match the one sent originally. 8387 The assigned connection ID is different from that used for previous requests. Only one connection ID can be used for each instance DB of the "MB_CLIENT" instruction. The error code is also output when the ID of the Modbus TCP protocol received by the server is not "0". 8388 The Modbus server sent a different data length than was requested. This error occurs only when using the Modbus functions 15 or 16. * The error codes can be displayed as integer or hexadecimal values in the program editor. For additional information on toggling display formats, refer to "See also". Note Error codes of internally used communications instructions. With the "MB_CLIENT" instruction, in addition to the errors listed in the tables, errors caused by the communication instructions ("TCON", "TDISCON", "TSEND" and "TRCV") used by the instruction can occur. The error codes are assigned via the instance data block of the "MB_CLIENT" instruction. The error codes are displayed for the respective instruction under STATUS in the Static section. The meaning of the error codes is available in the documentation of the corresponding communications instruction. See also Description of MB_CLIENT (Page 3038) MB_HOLD_REG parameter (Page 3049) MB_SERVER: Communicating via PROFINET as a Modbus TCP server Description of MB_SERVER Description The "MB_SERVER" instruction communicates as a Modbus TCP server via the PROFINET connection of the S7-1200 CPU. To use the instruction, you do not require any additional WinCC Basic V13.0 System Manual, 02/2014 3045 Programming the PLC 9.7 References hardware module. The "MB_SERVER" instruction processes connection requests of a Modbus TCP client, receives requests from Modbus functions and sends responses. NOTICE Safety instruction Note that each client on the network has access to the data of the Modbus instructions. Although the data block for the Modbus holding register cannot be addressed directly by the client, it is possible to indirectly access the data via the offset addresses. The option is available to restrict access to an IP address to prevent unauthorized read and write operations. Note, however, that the shared address can also be used for unauthorized access. Parameters The following table shows the parameters of the "MB_SERVER" instruction: Parameter Declaration Data type Description DISCONNECT Input BOOL The instruction "MB_SERVER" enters into a passive connection with a partner module, which means the server responds to a TCP connection request from each requesting IP address. You can use this parameter to control when a connection request is accepted: 0: A passive connection is established when there is no communications connection. 1: Initialization of the connection termination. If the input is set, no other operations are executed. The value 7003 is output at the STATUS parameter after successful connection termination. CONNECT_ID Input UINT The parameter uniquely identifies a connection within the CPU. Each individual instance of the instructions "MB_CLIENT (Page 3038)" and "MB_SERVER" must have a unique CONNECT_ID parameter. IP_PORT Input UINT Start value = 502. The number of IP ports defines which IP port is monitored for connection requests of the Modbus client. The following TCP port numbers must not be used for the passive connection of the "MB_SERVER" instruction: 20, 21, 25, 80, 102, 123, 5001, 34962, 34963 and 34964. MB_HOLD_REG (Page 3049) InOut VARIANT Pointer to the Modbus holding register of the "MB_SERVER" instruction: Use a global data block with standard access as holding register. The holding register contains the values that may be accessed by a Modbus client using the Modbus functions 3 (read), 6 (write) and 16 (read). NDR Output BOOL "New Data Ready": 0: No new data 1: New data written by the Modbus client written DR Output BOOL "Data Read": 0: No data read 1: Data read by the Modbus client 3046 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameter Declaration Data type Description ERROR Output BOOL If an error occurs during the call of the "MB_SERVER" instruction, the output of the ERROR parameter is set to TRUE. Detailed information about the cause of the problem is indicated by the STATUS parameter. STATUS (Page 3050) Output WORD Error code of the instruction. For additional information on valid data types, refer to "Overview of the valid data types (Page 1204)". Mapping of Modbus addresses to the process image The "MB_SERVER" instruction allows incoming Modbus functions (1, 2, 4, 5 and 15) direct read and write access to the process image input and output of the S7-1200 CPU (use of the data types BOOL and WORD). For the data transfer of the function codes 3, 6 and 16, the holding register (MB_HOLD_REG parameter) must be defined longer than one byte. The following table shows the mapping of the Modbus addresses to the process image of the CPU. Modbus function S7-1200 Code Function Data area Data area CPU address 01 Read: Bits Output 1 Address space to 8192 Process image output Q0.0 to Q1023.7 02 Read: Bits Input 10001 to 18192 Process image input I0.0 to I1023.7 04 Read: WORD Input 30001 to 30512 Process image input IW0 to IW1022 05 Write: Bits Output 1 to 8192 Process image output Q0.0 to Q1023.7 15 Write: Bits Output 1 to 8192 Process image output Q0.0 to Q1023.7 Incoming Modbus messages with the function codes 3, 6 and 16 write to or read from the Modbus holding registers (you specify the holding registers with the MB_HOLD_REG parameter). Multiple server connections You can create multiple Server connections. This allows a single CPU to establish connections to more than one Modbus TCP client at the same time. A Modbus TCP server can support several TCP connections and the maximum number of connections depends on the CPU being used. The total number of connections of one CPU, including those of the Modbus TCP clients and server must not exceed the maximum number of supported connections. Modbus TCP connections can also be shared by client and/or server connections. In the case of Server connections, remember the following rules: Each "MB_SERVER" connection must use a unique instance DB. Each "MB_SERVER" connection must be created with a unique IP port number. Only one connection is supported for each port. WinCC Basic V13.0 System Manual, 02/2014 3047 Programming the PLC 9.7 References Each "MB_SERVER" connection must use a unique connection ID. The relevant individual connection ID must be used for each individual instance DB of the instruction. The connection ID and instance DB belong together in pairs and must be unique for each connection. For each connection, the "MB_SERVER" instruction must be called individually. Modbus diagnostics functions The table below contains a description of the Modbus diagnostics functions. Code Subfunction Description 08 0x0000 Echo test: The "MB_SERVER" instruction receives a data word and returns this unchanged to the Modbus master. 08 0x000A Reset event counter: The "MB_SERVER" instruction resets the event counter for communication that is used for Modbus function 11. 11 - Fetch event counter of the communication: The "MB_SERVER" instruction uses an internal event counter for communication to record the number of successfully executed read and write requests sent to the Modbus server. The event counter is not incremented by the functions 8, 11 or broadcast requests. The same applies to requests that result in a communications error (for example parity errors or CRC errors). The broadcast function is not available for Modbus TCP because only one client/server connection can exist at any one time. Static tags of the instruction The following table describes the static tags of the instance data block of the "MB_SERVER" instruction used in the program. You can write the HR_Start_Offset tag. You can read the other tags to monitor the Modbus status. Tag Data type Start value Description HR_Start_Offset WORD 0 Assign the start address of the Modbus holding register. Request_Count WORD 0 Total number of requests received by the server. Server_Message_Co WORD unt 0 Total number of received messages for the relevant Server. Xmt_Rcv_Count WORD 0 Counter for detecting the number of transfers during which an error occurred. The counter is also incremented if an invalid Modbus message is received. Exception_Count WORD 0 Counter for detecting the number of errors specifically for Modbus cause an exception. Success_Count WORD 0 Counter for detecting the number of requests that contain no error in the transferred protocol. Connected BOOL 0 Indicates whether the connection to the assigned client has been established or not: 1 = connected, 0 = not connected. 3048 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Example: Addressing via static tag HR_Start_Offset The addresses of the Modbus holding register start at 40001. These addresses correspond to the address space of the CPU memory area for the holding register. You can also define the HR_Start_Offset tag so that the Modbus holding register has a start address other than 40001. Example: The holding register begins at MW100, and has a length of 100 WORD. An offset value in the HR_Start_Offset parameter means that the start address of the holding register is moved from 40001 to 40021. Whenever the holding register is addressed below the address 40021 and above the address 40119, this causes an error. HR_Start_Offset Address Minimum Maximum 0 Modbus address (WORD) 40001 40099 S7-1200 address MW100 MW298 Modbus address (WORD) 40021 40119 S7-1200 address MW100 MW298 20 See also MB_SERVER example: Multiple TCP connections (Page 3054) MB_HOLD_REG parameter Description The MB_HOLD_REG parameter is a pointer to a data buffer for storing the data read from or written to the Modbus server. As the data buffer, you can use a global data block or a memory area (M). As pointer to a buffer in the memory area (M), use the ANY format as follows: "P#bit address" "data type" "length" (example: P#M1000.0 WORD 500). The following table shows examples of mapping Modbus addresses to the holding register for the Modbus functions 3 (read WORD), 6 (write WORD) and 16 (write several WORD). The upper limit for the number of addresses in the data block is decided by the maximum work memory of the CPU. If you use a memory area, the upper limit for the addresses is decided by the size of the memory area of the CPU. Modbus addresses WinCC Basic V13.0 System Manual, 02/2014 MB_HOLD_REG parameter - examples P#M100.0 WORD 5 P#DB10.DBx0.0 WORD 5 "Recipe".ingredient 40001 MW100 DB10.DBW0 "Recipe".ingredient[1] 40002 MW102 DB10.DBW2 "Recipe".ingredient[2] 40003 MW104 DB10.DBW4 "Recipe".ingredient[3] 40004 MW106 DB10.DBW6 "Recipe".ingredient[4] 40005 MW108 DB10.DBW8 "Recipe".ingredient[5] 3049 Programming the PLC 9.7 References See also Description of MB_SERVER (Page 3045) Parameter STATUS Parameter STATUS (general status information) STATUS* (W#16#) Description 0000 Instruction executed without errors. 0001 Connection established. 0003 Connection terminated. 7000 No call active (REQ=0). 7001 First call with REQ=1: Processing started; BUSY has the value 1. 7002 Intermediate call (REQ irrelevant). Processing already active; BUSY has the value 1. 7003 Connection is being terminated. 7004 Connection established and monitored. No job processing active. 7005 Data was sent. 7006 Data was received. 80BB Invalid value at ACTIVE_EST parameter (identifier for the type of connection establishment, see T_CON_PARAM): Only passive connection establishment permitted for server (ACTIVE_EST = FALSE). Only active connection establishment permitted for client (ACTIVE_EST = TRUE). 8380 Received Modbus frame has incorrect format or too few bytes were received. * The error codes can be displayed as integer or hexadecimal values in the program editor. For additional information on toggling display formats, refer to "See also". Parameter STATUS (parameter error) STATUS* (W#16#) Code of the response to the Modbus server (B#16#) Description 8187 No response The MB_HOLD_REG parameter has an invalid pointer. Data area is too small. 818C No response The MB_HOLD_REG parameter references an an optimized data block. Either use a data block with standard access or a memory area 8381 01 Function code is not supported. 8382 03 Error in data length 8383 02 Error in data address or access outside the address area of the holding register (MB_HOLD_REG (Page 3049) parameter). 8384 03 Error in data value Error due to timeout of execution (more than 55 seconds). 3050 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References STATUS* (W#16#) Code of the response to the Modbus server (B#16#) Description 8385 03 Value of the diagnostic code is not supported (only with function code 08). * The error codes can be displayed as integer or hexadecimal values in the program editor. For additional information on toggling display formats, refer to "See also". Note Error codes of internally used communications instructions. With the "MB_SERVER" instruction, in addition to the errors listed in the tables, errors caused by the communication instructions ("TCON", "TDISCON", "TSEND" and "TRCV") used by the instruction can occur. The error codes are assigned via the instance data block of the "MB_SERVER" instruction. The error codes are displayed for the respective instruction under STATUS in the Static section. The meaning of the error codes is available in the documentation of the corresponding communications instruction. See also Description of MB_SERVER (Page 3045) Examples MB_CLIENT example 1: Send several requests via a TCP connection Description Several requests of the Modbus Client can be sent via a TCP connection. To do this, use the same instance DB, the same connection ID and the same port number. Only one client can be active at any one time. After processing of a client has been completed, the next client is processed. The order of execution must be defined in the program. In the following sample program, the value of the STATUS output parameter is also copied. WinCC Basic V13.0 System Manual, 02/2014 3051 Programming the PLC 9.7 References Network 1: Modbus function 1 - 16 read output bits Network 2: Modbus function 2 - 32 read input bits MB_CLIENT example 2: Send multiple requests via several TCP connections Description Requests from the Modbus client can be sent via different TCP connections. If you require this, use a different instance DB and a different connection ID. Use a different port number, if the connections are to the same Modbus server. If the connections are to different Modbus servers, you can freely assign the port number. 3052 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Network 1: Modbus function 4 - read input (WORD) Network 2: Modbus function 3 - read holding register (WORD) MB_CLIENT example 3: Coordinate several requests Description Make sure that the individual Modbus requests are executed. You control coordination of requests with the program. The following example demonstrates how the output parameters of the first and second client request can be used to coordinate execution of the instructions. WinCC Basic V13.0 System Manual, 02/2014 3053 Programming the PLC 9.7 References Network 1: Modbus function 3 - read holding register (WORD) Network 2: Modbus function 3 - read holding register (WORD) MB_SERVER example: Multiple TCP connections Description You can use several Modbus TCP server connections. To do this, the "MB_SERVER" instruction must be called independently for each connection. Every connection requires the following: An independent instance data block of the instruction A unique connection ID A separate IP port (on the S7-1200, only one connection is permitted per IP port) 3054 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References To optimize the performance "MB_SERVER" should be executed once per program cycle for each connection. Network 1: Connection #1 with associated IP port connection ID and instance DB Network 2: Connection #1 with associated IP port connection ID and instance DB MODBUS (TCP) (S7-1200, S7-1500) MB_CLIENT: Communicating via PROFINET as a Modbus TCP client Description of MB_CLIENT Description The "MB_CLIENT" instruction communicates as a Modbus TCP client via the PROFINET connection. With the "MB_CLIENT" instruction, you establish a connection between the client and the server, send Modbus requests and receive responses and control connection termination of the Modbus TCP client. The "MB_CLIENT" instruction V3.0 can be used for the S7-1500 as well as for the S7-1200 version 4.0 or higher. The connection can take place via the local interface of the CPU or CM/ CP. To use the instruction, you do not require an additional hardware module. WinCC Basic V13.0 System Manual, 02/2014 3055 Programming the PLC 9.7 References Multiple client connections A Modbus TCP client can support several TCP connections and the maximum number of connections depends on the CPU being used. The total number of connections of one CPU, including those of the Modbus TCP clients and server must not exceed the maximum number of supported connections. Modbus TCP connections can also be shared by "MB_CLIENT" and/ or "MB_SERVER" instances. With individual client connections, remember the following rules: Each "MB_CLIENT" connection must use a unique instance DB. For each "MB_CLIENT" connection, a unique server IP address must be specified. Each "MB_CLIENT" connection requires a unique connection ID. The relevant individual connection ID must be used for each individual instance DB of the instruction. The connection ID and instance DB belong together in pairs and must be unique for each connection. Unique numbers for the IP port may or may not be required depending on the server configuration. Parameters The following table shows the parameters of the "MB_CLIENT" instruction: Parameter Declaration Data type Description REQ (Page 3058) Input BOOL Communication request with the Modbus TCP server The REQ parameter is level-controlled. This means that as long as the input is set (REQ=true), the instruction sends communication requests. The instance DB for other clients is blocked with the communications request. Changes to the input parameters will not become effective until the server has responded or an error message has been output. If the parameter REQ is set again during an ongoing Modbus request, no additional transmission takes place afterwards. DISCONNECT (Page 3058) Input BOOL With this parameter, you control the establishment and termination of the connection to the Modbus server: 0: Establish communications connection to the connection partner configured at the CONNECT parameter (see CONNECT parameter). 1: Disconnect the communication connection. No other function is executed during connection termination. The value 0003 is output at the STATUS parameter after successful connection termination. The Modbus request is sent immediately if the REQ parameter is set during connection establishment. MB_MODE (Page 3058) Input USINT Selects the mode of the Modbus request (read, write or diagnostics). MB_DATA_ADDR (Page 3058) Input UDINT Start address of the data accessed by the "MB_CLIENT" instruction. 3056 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameter Declaration Data type Description MB_DATA_LEN Input UINT Data length: Number of bits or words for the data access (see "MB_MODE and MB_DATA_ADDR parameters" - data length). MB_DATA_PTR (Page 3060) InOut VARIANT Pointer to the Modbus data register: The register is a buffer for the data received from the Modbus server or to be sent to the Modbus server. The pointer must reference a global data block with optimized access. CONNECT (Page 3061) InOut VARIANT The number of bits addressed must be divisible by 8. Pointer to the structure of the connection description The following structures (system data types) can be used: TCON_IP_v4: Includes all address parameters required for establishing a programmed connection. When using TCON_IP_v4, the connection is established when calling the instruction "MB_SERVER". TCON_Configured: Includes the address parameters of a configured connection. When using TCON_Configured, an existing connection is used that was created by the CPU after download of the hardware configuration. DONE Out BOOL The bit at output parameter DONE is set to "1" as soon as the last job is completed without errors. BUSY Out BOOL 0: No Modbus request in progress 1: Modbus request being processed The output parameter BUSY is not set during connection establishment and termination. ERROR Out BOOL 0: No error 1: Error occurred. The cause of error is indicated by the STATUS parameter. STATUS (Page 3063) Out WORD Detailed status information of the instruction. For additional information on valid data types, refer to "Overview of the valid data types (Page 1204)". Note Consistent input data during an "MB_CLIENT" call When a Modbus client instruction is called, the status of the input parameters is stored internally and then compared at the next call. The comparison is used to determine whether this particular call initialized the current request. Several "MB_CLIENT" calls can be executed if you use a common instance DB. The values of the input parameters must not be changed while an "MB_CLIENT" instance is being executed. If the input parameters are changed during execution, "MB_CLIENT" cannot be used to check whether or not the instance is currently being executed. WinCC Basic V13.0 System Manual, 02/2014 3057 Programming the PLC 9.7 References Static tags of the instruction The following table describes the editable static tags of the instance data block of the "MB_CLIENT" instruction. Tag Start value Description Blocked_Proc_Timeo REAL ut Data type 3.0 Wait time in seconds before the static tag ACTIVE is reset if there is a blocked Modbus instance. This can, for example, occur if a client request is output and the execution of the client function aborts before the request was fully executed. The maximum wait time is 55 seconds. MB_Transaction_ID WORD 1 Transaction ID of the Modbus TCP protocol. The start value of "1" should only be changed if the Modbus TCP server requires a different value. MB_Unit_ID BYTE 255 Unit ID of the Modbus protocol. The tag corresponds to the slave address of the Modbus RTU protocol. Change this value only if the Modbus TCP server can be used as a gateway and is controlled by the application program within the Modbus server. RCV_TIMEOUT REAL 2.0 Time interval in seconds in which the "MB_CLIENT" instruction waits for a response from the server. Connected BOOL 0 Indicates whether the connection to the assigned server has been established or not: 1 = connected, 0 = not connected. REQ and DISCONNECT parameters Description If no instance of the "MB_CLIENT" instruction is executing and if the value of the DISCONNECT parameter is "0", a new job executes if REQ=1. If there is not yet a connection, this is established during execution. If the same instance of the "MB_CLIENT" instruction executes again (DISCONNECT = 0 and REQ = 1), before the active job was executed, this is not executed on completion of the active job. A new job can only be started on completion of the active job (REQ = 1). The status of the execution is output by the output parameters. You can use it to monitor the execution status when the "MB_CLIENT" instruction is executed sequentially. MB_MODE and MB_DATA_ADDR parameters Description Instead of a function code, the "MB_CLIENT" instruction uses the MB_MODE parameter. The MB_DATA_ADDR parameter is used to specify the Modbus start address of the data you want to access. The combination of the parameters MB_MODE, MB_DATA_ADDR and MB_DATA_LEN defines the function code used in the current Modbus message. For example: 3058 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Function code 5 - MB_MODE=1 - MB_DATA_ADDR=1 - MB_DATA_LEN=1 Function code 15 - MB_MODE=1 - MB_DATA_ADDR=1 - MB_DATA_LEN=2 The following table shows the relationship between the input parameters of the "MB_CLIENT" instruction and the Modbus function. MB_MODE MB_DATA_A DDR MB_DATA_L EN Modbus function 0 Start address: Data length 01 1 to 9999 (bits) per call: Read input bits: Start address: Data length 02 10001 to 1 (bits) per call: Read input bits: Start address: Data length (WORD) per 40001 to call: 49999 Read holding register: 1 to 2000 0 9999 0 400001 to 465535 0 1 to 2000 03 Function and data type 1 to 2000 1 to 2000 0 to 9998 0 to 65534 1 to 125 1 to 125 Start address: Data length 30001 to 3 (WORD) per call: 9999 04 Read input words: 0 to 9998 1 to 125 1 Start address: Data length 05 (bits) per call: 1 to 9999 Writing an output bit: Start address: Data length (WORD) per 40001 to call: 49999 Write a holding register: 1 1 400001 to 465535 1 06 0 to 9998 0 to 65524 1 1 Start address: Data length 15 1 to 9999 (bits) per call: Write multiple output bits: Start address: Data length (WORD) per 40001 to call: 49999 Write multiple holding registers: 2 to 1968 1 0 to 9998 400001 to 465534 WinCC Basic V13.0 System Manual, 02/2014 2 to 123 16 0 to 9998 0 to 9998 0 to 65534 2 to 123 3059 Programming the PLC 9.7 References MB_MODE MB_DATA_A DDR MB_DATA_L EN Modbus function 2 Start address: Data length 15 (bits) per call: 1 to 9999 Write one or more output bits: Start address: Data length (WORD) per 40001 to call: 49999 Write one or more holding registers: 1 to 1968 2 400001 to 465535 11 80 16 0 to 65534 1 to 123 1 to 123 The MB_DATA_ADDR and MB_DATA_LEN parameters are not evaluated when this function is executed. 11 - 08 - 0 to 9998 0 to 9998 Data length (WORD) per call: Data length (WORD) per call: Read status word and event counter of the server: The status word reflects the the processing status (0 - not processing, 0xFFFF - processing). The event counter is incremented when the Modbus request was executed successfully. If an error occurred during execution of a Modbus function, a message is sent by the server but the event counter is not incremented. Check the server status with the diagnostic code 0x0000 (return loop test - the server sends the request back): 1 WORD per call 1 81 Function and data type 08 1 3 to 10, 12 to 79, 82 to 255 Reset the event counter of the server with the diagnostic code 0x000A: 1 WORD per call Reserved MB_DATA_PTR parameter Description The MB_DATA_PTR parameter is a pointer to a data buffer for storing the data read from or written to the Modbus server. As the data buffer, you can use a global data block or a memory area (M). For a buffer in the memory area (M), use a pointer in the ANY format as follows: "P#bit address" "data type" "length" (example: P#M1000.0 WORD 500). The MB_DATA_PTR parameter uses a communications buffer: The communications buffer is used: 3060 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References For the communication functions of the "MB_CLIENT" instruction: - Reading and writing of 1 bit of data of the Modbus server addresses 00001 to 09999 and 10001 to 19999. - Reading of 16-bit WORD data of the Modbus server addresses 30001 to 39999 and 40001 to 49999. - Writing of 16-bit WORD data of the Modbus server addresses 40001 to 49999. During data transmission (length: bit or WORD) from or to the global DB or the memory area (M) that you assigned with the MB_DATA_PTR parameter. If you use a data block for the buffer in the MB_DATA_PTR parameter, you will need to assign data types to the DB elements. Use the 1-bit data type BOOL for a Modbus bit address Use a 16-bit data type such as WORD, UINT, INT or REAL for a Modbus WORD address. Use a 32-bit data type (double word) such as DWORD, DINT or REAL for two Modbus WORD addresses. With MB_DATA_PTR, you can also access complex DB elements such as: - Standard arrays - Structures with unique element names - Complex structures with unique naming of the elements and data type lengths of 16 or 32 bits. The data areas for the MB_DATA_PTR parameter can also be in different global data blocks (or in different memory areas). You can, for example, use a data block for the the read jobs and another one for the write jobs or a separate data block for each "MB_CLIENT" station. CONNECT parameter Connection descriptions at CONNECT parameter Two different connection descriptions can be used for the "MB_CLIENT" instruction: Programmed connections with the structure TCON_IP_v4 The connection parameters are stored in the TCON_IP_v4 structure and the connection is set up with the call of the instruction "MB_CLIENT". Configured connections with the structure TCON_Configured The configured connection has already been established by the CPU. Use the structure TCON_Configured to specify which existing connection is to be used for the instruction. Each instance of the instruction "MB_CLIENT" requires a unique connection. Create a separate structure TCON_IP_v4 or TCON_Configured for each instance of the instruction to describe the connection. WinCC Basic V13.0 System Manual, 02/2014 3061 Programming the PLC 9.7 References Connection description for programmed connections Use the following structure for connection description to TCON_IP_v4 for programmed connections at the CONNECT parameter: Make sure that only connections of the type TCP are specified in the TCON_IP_v4 structure. The connection may not use the following TCP port numbers: 20, 21, 25, 80, 102, 123, 5001, 34962, 34963 and 34964. Parameter Data type Start value Description 0 ... 1 InterfaceID Byte HW_ANY - Hardware identifier of the local interface (value range: 0 to 65535). 2 ... 3 ID CONN_OUC - Reference to this connection (value range: 1 to 4095). The parameter uniquely identifies a connection within the CPU. Each individual instance of the instruction "MB_CLIENT" must use a unique ID. 4 ConnectionType BYTE 11 Connection type Select 11 (decimal) for TCP. Other connection types are not permitted. If another connection type (e.g. UDP) is used, a corresponding error message is output at the STATUS parameter of the instruction. 5 ActiveEstablished BOOL TRUE ID for the manner in which the connection is established Select TRUE for active connection establishment. 6 ... 9 RemoteAddress ARRAY [1..4] of BYTE - IP address of the connection partner (Modbus server), for example, for 192.168.0.1: addr[1] = 192 addr[2] = 168 addr[3] = 0 addr[4] = 1 10 ... 11 RemotePort UINT 502 Port number of the remote connection partner (value range: 1 to 49151). Use the IP port number of the server to which the client establishes the connection and communicates using the TCP/ IP protocol (default value: 502). 12 ... 13 LocalPort UINT 0 Port number of the local connection partner: Port numbers: 1 to 49151 Any port: "0" 3062 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Note Migration of the instruction "MB_CLIENT" version 2.1 The parameters CONNECT_ID, IP_PORT and IP_OCTET_x are mapped in version 3.0 of the "MB_CLIENT" instruction in the TCON_IP_v4 structure: The parameter CONNECT_ID of the "MB_CLIENT" V2.1 instruction corresponds to the ID parameter of TCON_IP_v4. The parameter IP_PORT of the "MB_CLIENT" V2.1 instruction corresponds to the RemotePort parameter of TCON_IP_v4. The four parameters IP_OCTET_x of the "MB_CLIENT" V2.1 instruction correspond to the array of the RemoteAddress parameter of TCON_IP_v4. Connection description for configured connections For programmed connections at the CONNECT parameter, use the following structure for connection description to TCON_Configured. Make sure that only connections of the type TCP are specified in the TCON_Configured structure. The connection may not use the following TCP port numbers: 20, 21, 25, 80, 102, 123, 5001, 34962, 34963 and 34964. Byte Parameter Data type Start value Description 0 ... 1 InterfaceId HW_ANY - Hardware identifier of the local interface (value range: 0 to 65535). 2 ... 3 ID CONN_OUC - Reference to this connection (value range: 1 to 4095). Enter the connection ID of the existing connection. 4 ConnectionType BYTE 0 Connection type Select 254 (decimal) for a configured connection. Parameter STATUS Parameter STATUS (general status information) STATUS* (W#16#) Description 0000 Instruction executed without errors. 0001 Connection established. 0003 Connection terminated. 7000 No call active and no connection established (REQ=0). 7001 Connection establishment triggered. 7002 Intermediate call. Connection is being established. 7003 Connection is being terminated. WinCC Basic V13.0 System Manual, 02/2014 3063 Programming the PLC 9.7 References STATUS* (W#16#) Description 7004 Connection established and monitored. No job processing active. 7005 Data is being sent. 7006 Data is being received. 80BB Invalid value at ActiveEstablished parameter (identifier for the type of connection establishment, see CONNECT parameter (Page 3061)): Only passive connection establishment permitted for server (ActiveEstablished = FALSE). Only active connection establishment permitted for client (ActiveEstablished = TRUE). 8380 Received Modbus frame has incorrect format or too few bytes were received. * The status codes can be displayed as integer or hexadecimal values in the program editor. For additional information on toggling display formats, refer to "See also". Parameter STATUS (protocol error) STATUS* (W#16#) Error code in the error message from MB_SERVER (B#16#) Description 8381 01 Function code is not supported. 8382 03 Error in data length: Invalid length specification in received Modbus frame. The length of the Modbus frame in the frame header does not match the number of received bytes. The number of bytes does not match the number of actually transmitted bytes (only functions 1-4). The received start address does not match the one sent originally (functions 5, 6, 15, 16). The number of words does not match the number of actually transmitted words (only functions 15 and 16). 8383 02 Error reading or writing data or access outside the address area of MB_DATA_PTR (Page 3060). The error can occur locally as well as with the instruction "MB_SERVER". 8384 03 Error in data value: Error in data value for function 5 (error on server). A different data value was received than was originally sent by the client (functions 5 and 6) (local error). Invalid exception code received. 8385 03 Diagnostic code is not supported (function code 08). The error can occur locally as well as on the server. 8386 - Received function code does not match the one sent originally. 8387 - The assigned connection ID is different from that used for previous requests. Only one connection ID can be used for each instance DB of the "MB_CLIENT" instruction. The error code is also output when the protocol ID of the Modbus TCP frame received by the server is not "0". 3064 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References STATUS* (W#16#) Error code in the error message from MB_SERVER (B#16#) Description 8388 15 or 16 The Modbus server sent a different data length than was requested. This error occurs only when using the Modbus functions 15 or 16. * The status codes can be displayed as integer or hexadecimal values in the program editor. For additional information on toggling display formats, refer to "See also". Parameter STATUS (parameter error) STATUS* (W#16#) Description 80B6 Invalid connection type, only TCP connections are supported. 80C8 No response of the server in the defined period. Check the connection to the Modbus server. This error is only reported on completion of the configured repeated attempts. If the "MB_CLIENT" instruction does not receive an answer with the originally transferred transaction ID (see static MB_TRANSACTION_ID tag) within the defined period, this error code is output. 8188 The MB_MODE parameter has an invalid value. 8189 Invalid addressing of data at the MB_DATA_ADDR parameter. 818A Invalid data length at the MB_DATA_LEN parameter. 818B The MB_DATA_PTR parameter has an invalid pointer. You should also check the values of the MB_DATA_ADDR (Page 3060) and MB_DATA_LEN parameters. 818C Timeout at parameter BLOCKED_PROC_TIMEOUT or RCV_TIMEOUT (see static tags of instruction). The limit of 55 seconds has been exceeded. 818D The transaction ID (MB_TRANSACTION_ID tag) does not correspond to the one sent originally (see static tags of instruction). 8200 A different Modbus request is currently being processed via the port. Another instance of MB_CLIENT with the same connection parameters is processing an existing Modbus request. * The status codes can be displayed as integer or hexadecimal values in the program editor. For additional information on toggling display formats, refer to "See also". Note Error codes of internally used communications instructions With the "MB_CLIENT" instruction, in addition to the errors listed in the tables, errors caused by the communication instructions ("TCON", "TDISCON", "TSEND", "TRCV", "T_DIAG" and "TRESET") used by the instruction can occur. The error codes are assigned via the instance data block of the "MB_CLIENT" instruction. The error codes are displayed for the respective instruction under STATUS in the "Static" section. The meaning of the error codes is available in the documentation of the corresponding communications instruction. WinCC Basic V13.0 System Manual, 02/2014 3065 Programming the PLC 9.7 References See also GET_ERR_ID: Get error ID locally (Page 1964) MB_SERVER: Communicating via PROFINET as a Modbus TCP server Description of MB_SERVER Description The "MB_SERVER" instruction communicates as Modbus TCP server via a PROFINET connection. The "MB_SERVER" instruction processes connection requests of a Modbus TCP client, receives and processes Modbus requests and sends responses. The "MB_SERVER" instruction V3.0 can be used for the S7-1500 as well as for the S7-1200 version 4.0 or higher. The connection can take place via the local interface of the CPU or CM/ CP. To use the instruction, you do not require an additional hardware module. NOTICE Safety instruction Note that each client on the network has access to the data of the Modbus instructions. Although the data block for the Modbus holding register cannot be addressed directly by the client, it is possible to indirectly access the data via the offset addresses. The option is available to restrict access to an IP address to prevent unauthorized read and write operations. Note, however, that the shared address can also be used for unauthorized access. Multiple server connections You can create multiple Server connections. This allows a single CPU to accept connections from multiple Modbus TCP clients at the same time. A Modbus TCP server can support several TCP connections and the maximum number of connections depends on the CPU being used. The total number of connections of one CPU, including those of the Modbus TCP clients and server must not exceed the maximum number of supported connections. Modbus TCP connections can also be shared by "MB_CLIENT" and/or "MB_SERVER" instances. In the case of Server connections, remember the following rules: 3066 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Each "MB_SERVER" connection must use a unique instance DB. Each "MB_SERVER" connection must use a unique connection ID. The relevant individual connection ID must be used for each individual instance DB of the instruction. The connection ID and instance DB belong together in pairs and must be unique for each connection. For each connection, the "MB_SERVER" instruction must be called individually. Parameters The following table shows the parameters of the "MB_SERVER" instruction: Parameter Declaration Data type Description DISCONNECT Input BOOL The "MB_SERVER" instruction is used to enter into a passive connection with a partner module. The server responds to a connection request from the IP address which is entered in the SDT "TCON_IP_v4" in the CONNECT parameter. You can use this parameter to control when a connection request is accepted: 0: A passive connection is established when there is no communications connection. 1: Initialization of the connection termination. If the input is set, no other operations are executed. The value 0003 is output at the STATUS parameter after successful connection termination. MB_HOLD_REG (Page 3070) InOut VARIANT Pointer to the Modbus holding register of the "MB_SERVER" instruction The holding register contains the values that may be accessed by a Modbus client using the Modbus functions 3 (read), 6 (write) and 16 (read). As the holding register, use either a global data block with optimized access or the memory area of the bit memories. CONNECT (Page 3070) InOut VARIANT Pointer to the structure of the connection description The following structures (SDTs) can be used: TCON_IP_v4: Includes all address parameters required for establishing a programmed connection. The default address is 0.0.0.0 (any IP address), but you can enter a specific IP address so that the server only responds to requests from this address. When using TCON_IP_v4, the connection is established when calling the instruction "MB_SERVER". TCON_Configured: Includes the address parameters of a configured connection. When using TCON_Configured, the connection is established by the CPU after download of the hardware configuration. NDR Output BOOL "New Data Ready": 0: No new data 1: New data written by the Modbus client written DR Output BOOL "Data Read": 0: No data read 1: Data read by the Modbus client WinCC Basic V13.0 System Manual, 02/2014 3067 Programming the PLC 9.7 References Parameter Declaration Data type Description ERROR Output BOOL If an error occurs during the call of the "MB_SERVER" instruction, the output of the ERROR parameter is set to "1". Detailed information about the cause of the problem is indicated by the STATUS parameter. STATUS (Page 3072) Output WORD Detailed status information of the instruction. You will find more detailed information on valid data types in "Overview of the valid data types (Page 1204)". Static tags of the instruction The following table describes the static tags of the instance data block of the "MB_SERVER" instruction used in the program. You can write the HR_Start_Offset tag. You can read the other tags to monitor the Modbus status. Tag Data type Start value Description HR_Start_Offset WORD 0 Assign the start address of the Modbus holding register. Request_Count WORD 0 Total number of requests received by the server. Server_Message_Co WORD unt 0 Total number of received messages for the relevant Server. Xmt_Rcv_Count WORD 0 Counter for detecting the number of transfers during which an error occurred. The counter is only incremented when an invalid Modbus request is received. Exception_Count WORD 0 Counters for detecting the number of errors specifically for Modbus which cause an error message to "MB_CLIENT". Success_Count WORD 0 Event counter for detecting the number of requests that were successfully executed by the server. Connected BOOL 0 Indicates whether the connection to the assigned client has been established or not: 1 = connected, 0 = not connected. Mapping of Modbus addresses to the process image The "MB_SERVER" instruction allows incoming Modbus functions (1, 2, 4, 5 and 15) direct read and write access to the process image inputs and outputs of the CPU (use of the data types BOOL and WORD). For the data transfer of the function codes 3, 6 and 16, the holding register (MB_HOLD_REG parameter) must be defined longer than one byte. The following table shows the mapping of the Modbus addresses to the process image of the CPU. Modbus function S7-1500, S7-1200 V4.0 Function code Function Data area 01 Read: Bits Output 1 to 02 Read: Bits Input 1 04 Read: WORD Input 1 3068 Address space Data area CPU address 9999 Process image output Q0.0 to Q1249.6 to 19999 Process image input I0.0 to I1249.6 to 39999 Process image input IW0 to IW19996 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Modbus function S7-1500, S7-1200 V4.0 05 Write: Bits Output 1 to 9999 Process image output Q0.0 to Q1249.6 15 Write: Bits Output 1 to 9999 Process image output Q0.0 to Q1249.6 Incoming Modbus requests with the function codes 3, 6, 16 and 23 write to or read from the Modbus holding register (you specify the holding register with the MB_HOLD_REG parameter). Example: Addressing via static tag HR_Start_Offset The addresses of the Modbus holding register start at 40001. These addresses correspond to the address space of the CPU memory area for the holding register. You can also define the HR_Start_Offset tag so that the Modbus holding register has a start address other than 40001. Example: The holding register begins at MW100, and has a length of 100 WORD. An offset value in the HR_Start_Offset parameter means that the start address of the holding register is moved from 40001 to 40021. Whenever the holding register is addressed below the address 40021 and above the address 40120, this causes an error. HR_Start_Offset Address Minimum Maximum 0 Modbus address (WORD) 40001 40100 CPU address MW100 MW298 Modbus address (WORD) 40021 40120 CPU address MW100 MW298 20 Modbus diagnostics functions The table below contains a description of the Modbus diagnostics functions. Function code Diagnostic code Description 08 0x0000 Echo test: The "MB_SERVER" instruction receives a data word and returns this unchanged to the Modbus client. 08 0x000A Reset event counter: The "MB_SERVER" instruction resets the following event counters: "Success_Count", "Xmt_Rcv_Count", "Exception_Count", "Server_Message_Co" and "Request_Count". 11 - Fetch event counter of the communication: The "MB_SERVER" instruction uses an internal event counter for communication to record the number of successfully executed read and write requests sent to the Modbus server. The event counter is not incremented with the functions 8 or 11. The same holds true for requests that cause a communications error, for example, if a protocol error has occurred (e.g., the function code in the received Modbus request is not supported). WinCC Basic V13.0 System Manual, 02/2014 3069 Programming the PLC 9.7 References MB_HOLD_REG parameter Description The MB_HOLD_REG parameter is a pointer to a data buffer for storing the data read from or written to the Modbus server. You can use a global data block or a bit memory (M) as memory area. The high limit for the number of addresses in the data block (D) is determined by the maximum work memory of the CPU. The high limit for the number of bit memories (M) is determined by the size of the CPU memory area. The following table shows examples of mapping Modbus addresses to the holding register for the Modbus functions 3 (read WORD), 6 (write WORD), 16 (write several WORD) and 23 (write and read several words). Modbus addresses MB_HOLD_REG parameter - examples 40001 MW100 DB10.DBW0 "Recipe".ingredient[1] 40002 MW102 DB10.DBW2 "Recipe".ingredient[2] 40003 MW104 DB10.DBW4 "Recipe".ingredient[3] 40004 MW106 DB10.DBW6 "Recipe".ingredient[4] 40005 MW108 DB10.DBW8 "Recipe".ingredient[5] CONNECT parameter Connection descriptions at CONNECT parameter Two different connection descriptions can be used for the "MB_SERVER" instruction: Programmed connections with the structure TCON_IP_v4 The connection parameters are stored in the TCON_IP_v4 structure and the connection is set up with the call of the instruction "MB_SERVER". Configured connections with the structure TCON_Configured The configured connection has already been established by the CPU. Use the structure TCON_Configured to specify which existing connection is to be used for the instruction. Each instance of the instruction "MB_SERVER" requires a unique connection. Create a separate structure TCON_IP_v4 or TCON_Configured for each instance of the instruction to describe the connection. 3070 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Connection description for programmed connections For programmed connections at the CONNECT parameter, use the following structure for connection description to TCON_IP_v4. Make sure that only connections of the type TCP are specified in the TCON_IP_v4 structure. The connection may not use the following TCP port numbers: 20, 21, 25, 80, 102, 123, 5001, 34962, 34963 and 34964. Byte Parameter Data type Start value Description 0 ... 1 InterfaceID HW_ANY - Hardware identifier of the local interface (value range: 0 to 65535). 2 ... 3 ID CONN_OUC - Reference to this connection (value range: 1 to 4095). The parameter uniquely identifies a connection within the CPU. Each individual instance of the instruction "MB_SERVER" must use a unique ID. 4 ConnectionType BYTE 11 Connection type Select 11 (decimal) for TCP. Other connection types are not permitted. If another connection type (e.g. UDP) is used, a corresponding error message is output at the STATUS parameter of the instruction. 5 ActiveEstablished BOOL FALSE ID for the manner in which the connection is established Select FALSE for passive connection establishment. 6 ... 9 RemoteAddress ARRAY [1..4] of BYTE 0.0.0.0 IP address of the connection partner, for example, for 192.168.0.1: addr[1] = 192 addr[2] = 168 addr[3] = 0 addr[4] = 1 If the instruction "MB_SERVER" is to accept connection requests from any connection partner, use "0.0.0.0" as IP address. 10 ... 11 RemotePort UINT 0 Port number of the remote connection partner (value range: 1 to 49151). If the instruction "MB_SERVER" is to accept connection requests from any remote partner, use "0" as port number. 12 ... 13 LocalPort UINT 502 Port number of the local connection partner (value range: 1 to 49151). The number of the IP port defines which IP port is monitored for connection requests of the Modbus client. The following TCP port numbers must not be used for the passive connection of the "MB_SERVER" instruction: 20, 21, 25, 80, 102, 123, 5001, 34962, 34963 and 34964. WinCC Basic V13.0 System Manual, 02/2014 3071 Programming the PLC 9.7 References Note Migration of the instruction "MB_SERVER" version 2.1 The parameters CONNECT_ID and IP_PORT are mapped in version 3.0 of the "MB_SERVER" instruction in the TCON_IP_v4 structure: The parameter CONNECT_ID of the "MB_SERVER" V2.1 instruction corresponds to the ID parameter of TCON_IP_v4. The parameter IP_PORT of the "MB_SERVER" V2.1 instruction corresponds to the LocalPort parameter of TCON_IP_v4. Connection description for configured connections For configured connections at the CONNECT parameter, use the following structure for connection description to TCON_Configured. Make sure that only connections of the type TCP are specified in the TCON_Configured structure. The connection may not use the following TCP port numbers: 20, 21, 25, 80, 102, 123, 5001, 34962, 34963 and 34964. Byte Parameter Data type Start value Description 0 ... 1 InterfaceID HW_ANY - Hardware identifier of the local interface (value range: 0 to 65535). 2 ... 3 ID CONN_OUC - Reference to this connection (value range: 1 to 4095). 4 BYTE - Enter the connection ID of the existing connection. ConnectionType Connection type Select 254 (decimal) for a configured connection. Parameter STATUS Parameter STATUS (general status information) STATUS* (W#16#) Description 0000 Instruction executed without errors. 0001 Connection established. 0003 Connection terminated. 7000 No call active (REQ=0). 7001 First call. Connection establishment triggered. 7002 Intermediate call. Connection is being established. 7003 Connection is being terminated. 7005 Data is being sent. 7006 Data is being received. 3072 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References STATUS* (W#16#) Description 80BB Invalid value at ActiveEstablished parameter (identifier for the type of connection establishment, see CONNECT parameter (Page 3070)): Only passive connection establishment permitted for server (active_established = FALSE). Only active connection establishment permitted for client (active_established = TRUE). 8380 Received Modbus frame has incorrect format or too few bytes were received. * The status codes can be displayed as integer or hexadecimal values in the program editor. For additional information on toggling display formats, refer to "See also". Parameter STATUS (parameter error) STATUS* (W#16#) Error code in the error message from "MB_SERVER" (B#16#) Description 8187 No response The MB_HOLD_REG parameter has an invalid pointer. Data area is too small. 8381 01 Function code is not supported. 8382 03 Error in data length: Invalid length specification in received Modbus frame The frame length entered in the header of the Modbus frame does not match the number of actually received bytes. The number of bytes entered in the header of the Modbus frame does not match the number of actually received bytes (functions 15 and 16). 8383 02 Error in data address or access outside the address area of the holding register (MB_HOLD_REG (Page 3070) parameter). 8384 03 Invalid data value (function 5). 8385 03 Diagnostic code is not supported (only with function code 08). * The status codes can be displayed as integer or hexadecimal values in the program editor. For additional information on toggling display formats, refer to "See also". Note Error codes of internally used communications instructions With the "MB_SERVER" instruction, in addition to the errors listed in the tables, errors caused by the communication instructions ("TCON", "TDISCON", "TSEND", "TRCV", "T_DIAG" and "T_RESET") used by the instruction can occur. The error codes are assigned via the instance data block of the "MB_SERVER" instruction. The error codes are displayed for the respective instruction under STATUS in the "Static" section. The meaning of the error codes is available in the documentation of the corresponding communications instruction. See also GET_ERR_ID: Get error ID locally (Page 1964) WinCC Basic V13.0 System Manual, 02/2014 3073 Programming the PLC 9.7 References 9.7.5.2 S7 communication Data consistency Definition A data block which cannot be modified by concurrent processes is called consistent data area. A data block which is larger than the consistent data area can thus be falsified as a whole during transmission. This means that a data block which belongs together and which is larger than consistent data area can consist in part of new and of old consistent data at the same time. Example An inconsistency can occur when an instruction for communication is interrupted, for example, by a hardware interrupt OB with higher priority. If the user program in this OB now changes the data that has already been partly processed by the instruction, the transferred data originates: In part from the time before the hardware interrupt was processed And in part from the time after the hardware interrupt was processed This means that these data are inconsistent (not coherent). Ensuring data consistency If the communication process can be interrupted by an interrupt OB, you must ensure that the data is transferred consistently. Make sure that only an image of the data and not the data to be transferred is not changed directly by the interrupt OB. Copy the image of the data to the transfer area of the communication instruction prior to the next data transfer. If the user program contains a communication instruction that accesses common data, access to this data area can be coordinated, for example, by means of the DONE parameter. The data consistency of the communication areas which are transferred locally with a communication instruction can therefore be ensured in the user program. In the case of S7 communication instructions "PUT (Page 3081)"/"GET (Page 3078)", the size of the consistent data areas must already be taken into consideration during programming or configuration, because a communication block is not available in the user program of the target device (server) to synchronize communication data to the user program. 3074 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References For the S7-300 and C7-300 (exception: CPU 318-2 DP) the communication data are copied consistently into the user memory in blocks of 32 bytes in the cycle control point of the operating system. Data consistency is not guaranteed for larger data areas. If a defined data consistency is required, the communication data in the user program may not exceed 32 bytes (maximum of 8 bytes, depending on the version). In the S7-400 and S7-1500, on the other hand, the communication data in 462-byte blocks is not processed at the cycle control point, but in fixed time slices during the program cycle. The consistency of a tag is ensured by the system. These communication areas can then be accessed consistently using the "PUT (Page 3081)" / "GET (Page 3078)" instructions or when reading/writing tags, for example by an OP or an OS. Note Additional information on data consistency is provided in the description of the specific instructions. Effect on interrupt reaction times The interrupt reaction times of the CPU are slightly extended by copying the data. The greater the quantity of data which must be transferred with absolute consistency, the longer the interrupt reaction time of a system. Common parameters of instructions for S7 communication Classification The parameters of the instructions for S7 communication can be divided into the following five categories according to their functions: 1. Control parameters are used to activate an instruction. 2. Addressing parameters are used to address the remote communication partner. 3. Send parameters point to the data areas that are to be sent to the remote partner. 4. Receive parameters point to the data areas where the data received from remote partners will be entered. 5. Status parameters are used to monitor whether the instruction has completed its task without error or for the analysis of any errors that have occurred. Control parameter Data exchange will only be activated if the appropriate control parameters have a defined value (for example, are set) when the instruction is called or when the value has undergone a specific change since the previous call (for example, a positive edge). WinCC Basic V13.0 System Manual, 02/2014 3075 Programming the PLC 9.7 References Addressing parameters Parameter Description ID Reference to the local connection description (specified by the configuration of the connection). R_ID With the R_ID parameter, you specify that a send and a receive instruction belong together: The R_ID parameter must match in the instruction at the sending end and the instruction at the receiving end. This allows the communication of several instruction pairs via the same logic connection. R_ID must be specified in the form DW#16#wxyzWXYZ. The instruction pairs of a logical connection specified in R_ID must be unique for this connection. Note Addressing parameters ID and R_ID You can reassign the addressing parameters ID and R_ID during runtime. The new parameters are validated with each new job after the previous job has been closed. You can use the following options to reduce the number of instance DBs and therefore the work memory required: 1. With tag IDs, you can use several connections via one data instance block. 2. With tag R_IDs, you can define several pairs of sending and receiving instructions for one job with a single instance. 3. You can combine cases 1 and 2. Please note that the new parameters are valid after the last job is executed. When you activate the sending operation, the R_ID parameter in the instruction at the sending end must match its counterpart at the receiving end. Status parameter With the status parameters, you monitor whether the instruction has completed its task correctly or whether it is still active. The status parameters also indicate errors. Note The status parameters are valid for one cycle only, namely from the first command following the call until the next call. As a result, you must evaluate these parameters after each instruction cycle. 3076 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Send and receive parameters For communication instructions configured at both ends The number of the SD_i and RD_i parameters used must match at the send and receive end. The data types of the SD_i and RD_i parameters that belong together must match at the send and receive end. The amount of data to be sent according to the SD_i parameter must not exceed the range made available by the corresponding RD_i (does not apply to "BSEND (Page 3086)" / "BRCV (Page 3089)"). The RD_i parameters must (with exception of "BSEND"/"BRCV") have the identical data size. If you do not keep to the rules above, this is indicated by ERROR = 1 and STATUS = 4. Note Supplying the send and receive parameters With the VARIANT data type, send and receive parameters must always be supplied any time a communication instruction is called. It is not possible, for example, to supply the send parameters of the communication instructions at startup and to only trigger the send job in cyclic operation. User data size With the "USEND (Page 3083)", "URCV (Page 3085)", "GET (Page 3078)" and "PUT (Page 3081)" instructions, the amount of data to be transferred must not exceed a defined user data size. The maximum user data size depends on: The instruction used The communication partner. The guaranteed minimum size of the user data for an instruction with 1-4 tags is listed in the following table: Instruction Partner: S7-300 Partner: S7-400 Partner: S7-1200 Partner: S7-1500 PUT / GET 160 bytes 400 bytes 160 bytes 880 bytes USEND / URCV 160 bytes 440 bytes - 920 bytes BSEND / BRCV 32768/65534 bytes 65534 bytes - 65534 bytes with standard access 65535 bytes with optimized access Further information on the user data size can be found in the technical data of the respective CPU. WinCC Basic V13.0 System Manual, 02/2014 3077 Programming the PLC 9.7 References Exact user data size If the user data size specified above is insufficient you can determine the maximum byte length of the user data as follows: First read the data block size valid for communication from the following table: Local CPU Remote CPU Data block size in bytes S7-1200 Any 240 S7-1500 S7-300 240 S7-400 480 S7-1200 240 S7-1500 960 Use this value in the following table to read the maximum possible user data length in bytes as total of the parameters used. It applies for even lengths of the areas SD_i, RD_i, and ADDR_i. For each range of uneven length the maximum possible user data length is reduced by one byte. Number of SD_i, RD_i, ADDR_i parameters used Data block size Instruction 1 2 3 4 240 (S7-300) PUT/GET/ USEND 160 - - - 240 (S7-300 via integrated interface) PUT 212 - - - GET 222 - - - USEND 212 - - - PUT 212 196 180 164 GET 222 218 214 210 USEND 212 - - - PUT 452 436 420 404 GET 462 458 454 450 USEND 452 448 444 440 PUT 212 196 180 164 GET 222 218 214 210 PUT 932 916 900 884 GET 942 938 934 930 USEND 932 928 924 920 240 (S7-400) 480 (S7-400) 240 (S7-1200) 960 (S7-1500) GET: Read data from a remote CPU Description With the instruction "GET", you can read data from a remote CPU. 3078 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References The instruction is started on a positive edge at control input REQ: The relevant pointers to the areas to be read out (ADDR_i) are then sent to the partner CPU. The partner CPU can be in RUN or STOP mode. The partner CPU returns the data: - If the reply exceeds the maximum user data length, this is displayed with error code "2" at the STATUS parameter. - The received data is copied to the configured receive areas (RD_i) at the next call. Completion of this action is indicated by the status parameter NDR having the value "1". Reading can only be activated again after the previous reading process has been completed. Errors and warnings are output via ERROR and STATUS if access problems occurred while the data was being read or if the data type check results in an error. Changes in the data areas addressed on the partner CPU are not registered by the "GET" instruction. Requirements for using the instruction The "Permit access with PUT/GET communication from remote partner" function was activated in the properties of the partner CPU under "Protection". The blocks which you access with the "GET" instruction were created with the access type "standard". Make sure that the areas defined with the parameters ADDR_i and SD_i match in terms of number, length and data type. The area to be read (ADDR_i parameter) cannot be larger than the area for data storage (RD_i parameter). Parameters The following table shows the parameters of the "GET" instruction: Parameter Declaration Data type Memory area Description REQ Input BOOL I, Q, M, D, L or constant Control parameter request, activates the data exchange on a positive edge. ID Input WORD I, Q, M, D, L or constant Addressing parameters for specifying the connection to the partner CPU. NDR Output BOOL I, Q, M, D, L Status parameter NDR: 0: Job not yet started or still running. 1: Job successfully completed. ERROR Output BOOL I, Q, M, D, L Status parameters ERROR and STATUS, error code: ERROR=0 STATUS has the value: - WinCC Basic V13.0 System Manual, 02/2014 0000H: Neither warning nor error 3079 Programming the PLC 9.7 References Parameter Declaration Data type Memory area STATUS Output WORD I, Q, M, D, L Description - <> 0000H: Warning, STATUS supplies detailed information. ERROR=1 An error has occurred. STATUS supplies detailed information on the type of error. ADDR_1 InOut REMOTE ADDR_2 InOut REMOTE ADDR_3 InOut REMOTE ADDR_4 InOut REMOTE RD_1 InOut VARIANT RD_2 InOut VARIANT RD_3 InOut VARIANT RD_4 InOut VARIANT I, Q, M, D Pointers to the areas on the partner CPU that are to be read. When the REMOTE pointer accesses a DB, the DB must always be specified. Example: P#DB10.DBX5.0 Byte 10. I, Q, M, D, L Pointers to the areas on the local CPU in which the read data is entered. For additional information on valid data types, refer to "Overview of the valid data types (Page 1204)". Parameters ERROR and STATUS The following table contains all specific error information for the "GET" instruction that can be output via the ERROR and STATUS parameters. ERROR STATUS (decimal) Explanation 0 11 Warning: New job not active because the previous job is still busy. 0 25 Communication has started. The job is being processed. 1 1 Communication problems, for example Connection description not loaded (local or remote) Connection interrupted (for example: cable, CPU off, CP in STOP mode) Connection to partner not yet established 1 2 Negative acknowledgment from the partner device. The function cannot be executed. Response from the remote station exceeds the maximum user data length (see: Common parameters of instructions for S7 communication (Page 3075)). Access protection is activated on the partner CPU. Deactivate access protection in the CPU settings. 1 4 Error in the pointers to the data storage RD_i: Data types of the parameters RD_i and ADDR_i are not compatible with each other. The length of the area RD_i is smaller than the length of the data of the ADDR_i parameter that is to be read. 1 8 Access error on the partner CPU. 1 10 Access to the local user memory not possible (for example, access to a deleted DB). 1 20 Maximum number of parallel jobs exceeded. The job is currently being processed in a priority class with low priority (first call). 3080 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Note Data consistency Data is received consistently if you read the part of the receive area RD_i currently being used completely before initiating another job. PUT: Write data to a remote CPU Description You can write data to a remote CPU with the instruction "PUT". The instruction is started on a positive edge at control input REQ: The pointers to the areas to be written (ADDR_i) and the data (SD_i) are then sent to the partner CPU. The partner CPU can be in RUN or STOP mode. The data to be sent is copied from the configured send areas ((SD_i). The partner CPU saves the sent data under the addresses supplied with the data and returns an execution acknowledgment. If no errors occur, this is indicated at the next instruction call with status parameter DONE = "1". The writing process can only be activated again after the last job is complete. Errors and warnings are output via ERROR and STATUS if access problems occurred while the data was being written or if the execution check results in an error. Requirements for using the instruction The "Permit access with PUT/GET communication from remote partner" function was activated in the properties of the partner CPU under "Protection". The blocks which you access with the "PUT" instruction were created with the access type "standard". Make sure that the areas defined with the parameters ADDR_i and SD_i match in terms of number, length and data type. The area to be written (ADDR_i parameter) must be as large as the send area (SD_i parameter). Parameters The following table shows the parameters of the "PUT" instruction: Parameter Declaration Data type Memory area Description REQ Input BOOL I, Q, M, D, L or constant Control parameter request, activates the data exchange on a positive edge. ID Input WORD I, Q, M, D, L or constant Addressing parameters for specifying the connection to the partner CPU. WinCC Basic V13.0 System Manual, 02/2014 3081 Programming the PLC 9.7 References Parameter Declaration Data type Memory area Description DONE Output BOOL I, Q, M, D, L Status parameter DONE: 0: Job not yet started or still executing 1: Job executed without errors. ERROR Output BOOL I, Q, M, D, L Status parameters ERROR and STATUS, error code: STATUS Output WORD I, Q, M, D, L ERROR=0 STATUS has the value: - 0000H: Neither warning nor error - <> 0000H: Warning, STATUS supplies detailed information. ERROR=1 An error has occurred. STATUS supplies detailed information on the type of error. ADDR_1 InOut REMOTE ADDR_2 InOut REMOTE ADDR_3 InOut REMOTE ADDR_4 InOut REMOTE I, Q, M, D Pointers to the areas on the partner CPU to which the data will be written. When the REMOTE pointer accesses a DB, the DB must always be specified. Example: P#DB10.DBX5.0 Byte 10. When transferring data structures (e.g., Struct) the data type CHAR must be used at the ADDR_i parameters. SD_1 InOut VARIANT SD_2 InOut VARIANT SD_3 InOut VARIANT SD_4 InOut VARIANT I, Q, M, D, L Pointers to the areas on the local CPU which contain the data to be sent. Only the data types BOOL, BYTE, CHAR, WORD, INT, DWORD, DINT, REAL are permitted. When transferring data structures (e.g., Struct) the data type CHAR must be used at the SD_i parameters. For additional information on valid data types, refer to "Overview of the valid data types (Page 1204)". Parameters ERROR and STATUS The following table contains all specific error information for the "PUT" instruction that can be output via the ERROR and STATUS parameters. ERROR STATUS (decimal) Explanation 0 11 Warning: New job not active because the previous job is still busy. 0 25 Communication has started. The job is being processed. 1 1 Communication problems, for example Connection description not loaded (local or remote). Connection interrupted (for example, cable, CPU off, CP in STOP mode). Connection to partner not yet established. 3082 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References ERROR STATUS (decimal) Explanation 1 2 Negative acknowledgment of partner CPU. The function cannot be executed. 1 4 Error in the pointers to the data storage: Access on the partner CPU was not granted. Activate the access in the CPU settings. Data types of the parameters SD_i and ADDR_i are not compatible with each other. The length of the area SD_i is greater than the length of the data of the ADDR_i parameter that is to be written. Not possible to access SD_i. Maximum user data size exceeded. Number of the parameters SD_i and ADDR_i does not match. 1 8 Access error with the partner CPU (e.g. DB not loaded or write-protected). 1 10 Access to the local user memory not possible (for example, access to a deleted DB). 1 20 Maximum number of parallel jobs exceeded. The job is currently being processed in a priority class with low priority (first call). Data consistency When a send operation is activated (positive edge at REQ), the data to be sent from the send area SD_i is copied from the user program. After the block call, you can write to these areas without corrupting the current send data. Note The send operation is only complete when the DONE status parameter has the value "1". Other USEND: Send data uncoordinated Description The "USEND" instruction sends data to a remote partner instruction of type "URCV (Page 3085)". The sending process is carried out without coordination with the partner instruction. This means that the data transfer is carried out without acknowledgment by the partner instruction. When a send operation is activated (positive edge at REQ), the data to be sent from the send areas SD_i are copied from the user program. After the instruction call, you can write to these send areas again without corrupting the current send data. Successful completion of the send operation is indicated by the value of the DONE status parameter being set to "1". WinCC Basic V13.0 System Manual, 02/2014 3083 Programming the PLC 9.7 References Parameters The following table shows the parameters of the "USEND" instruction: Parameter Declaration Data type Memory area Description REQ Input BOOL I, Q, M, D, L or constant Control parameter request, activates the data exchange on a positive edge. ID Input CONN_PRG I, Q, M, D, L, P or constant Addressing parameters for specifying the connection to the partner CPU. R_ID Input CONN_R_ID I, Q, M, D, L or constant Addressing parameter R_ID for defining the instruction pairs "USEND" and "URCV". See also: Common parameters of instructions for S7 communication (Page 3075) DONE Output BOOL I, Q, M, D, L Status parameter 0: Job not yet started or still executing. 1: Job executed without errors. ERROR Output BOOL I, Q, M, D, L Status parameter 0: Neither warning nor error. 1: An error has occurred. STATUS supplies detailed information on the type of error. STATUS Output WORD I, Q, M, D, L Status parameter See "ERROR and STATUS parameters" table. SD_i (1 i 4) InOut VARIANT I, Q, M, D Pointer on the i-th send area. Only the BOOL data types are permitted (not permitted: bit array), BYTE, CHAR, WORD, INT, DWORD, DINT, REAL or STRUCT. The maximum user data size for SD_i parameters depends on the partner CPU ("URCV" instruction) and on the number of parameters used. Additional information is available in: Common parameters of instructions for S7 communication (Page 3075) For additional information on valid data types, refer to "Overview of the valid data types (Page 1204)". Parameters ERROR and STATUS ERROR STATUS (decimal) Explanation 0 11 Warning: New job not active because the previous job is still busy. 0 25 Communication has started. The job is being processed. 1 1 Communication problem has occurred. Possible causes: Connection description not loaded (local or remote) Connection interrupted (for example: cable, CPU off, CP in STOP mode) Connection to partner not yet established 3084 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References ERROR STATUS (decimal) Explanation 1 4 Errors in the send area pointers SD_i relating to the data length or the data type. 1 10 Access to the local user memory not possible (for example, access to a deleted DB). 1 18 Value at R_ID parameter already exists in the connection specified at the ID parameter (R_ID value must be unique for the connection). 1 20 Maximum number of parallel jobs exceeded. Maximum user data length was exceeded. The job is currently being processed in a priority class with lower priority (first call). URCV: Receive data uncoordinated Description The "URCV" instruction receives data asynchronously from a remote partner instruction of type "USEND (Page 3083)" and copies this data into the configured receive areas. The instruction is ready to receive if there is a logical 1 at the EN_R input. An active job can be canceled with EN_R=0. The receive data areas are referenced by the parameters RD_1 to RD_4. Make sure that the areas defined by the parameters RD_i / RD_1 and SD_i / SD_1 (with the associated partner instruction "USEND (Page 3083)") match in terms of number and length. Successful completion of the copy operation is indicated when the value of the NDR status parameter is set to logical "1". Once the status parameter NDR has changed to "1", there will be new receive data in your receive areas (RD_i). A new block call may cause these data to be overwritten with new receive data. If you want to prevent this, call "URCV" (for example, during cyclic block processing) with the value 0 at EN_R until you have finished processing the received data. Parameters The following table shows the parameters of the "URCV" instruction: Parameter Declaration Data type Memory area Description EN_R Input BOOL I, Q, M, D, L or constant Control parameter enabled to receive, signals ready to receive if the input is set. ID Input CONN_PR G I, Q, M, D, L, P or constant Addressing parameters for specifying the connection to the partner CPU. R_ID Input CONN_R_I D I, Q, M, D, L or constant Addressing parameter for defining the instruction pairs "USEND" and "URCV". See also: Common parameters of instructions for S7 communication (Page 3075) NDR Output BOOL I, Q, M, D, L Status parameter 0: Job not yet started or still running. 1: Job successfully completed. WinCC Basic V13.0 System Manual, 02/2014 3085 Programming the PLC 9.7 References Parameter Declaration Data type Memory area Description ERROR Output BOOL I, Q, M, D, L Status parameter 0: Neither warning nor error 1: An error has occurred. STATUS supplies detailed information on the type of error. STATUS Output WORD I, Q, M, D, L Status parameter See "ERROR and STATUS parameters" table. RD_i (1 i 4) InOut VARIANT I, Q, M, D Pointer to the i-th receive area: Only the BOOL data types are permitted (not permitted: bit array), BYTE, CHAR, WORD, INT, DWORD, DINT, REAL or STRUCT. Additional information is available in: Common parameters of instructions for S7 communication (Page 3075) For additional information on valid data types, refer to "Overview of the valid data types (Page 1204)". Parameters ERROR and STATUS ERROR STATUS Explanation (decimal) 0 9 Warning: older received data were overwritten by newer received data. 0 11 Warning: The received data is already being processed in a priority class with lower priority (error can occur when copying data to the receive area). 0 25 Communication has started. The job is being processed. 1 1 Communication problem has occurred. Possible causes: Connection description not loaded (local or remote) Connection interrupted (for example: cable, CPU off, CP in STOP mode) Connection to partner not yet established 1 4 Errors in the receive area pointers RD_i relating to the data length or the data type. 1 10 Access to the local user memory not possible (for example, access to a deleted DB). 1 18 Value at R_ID parameter already exists in the connection specified at the ID parameter (R_ID value must be unique for the connection). 1 19 The associated "USEND (Page 3083)" instruction sends data faster than it can be copied to the receive areas by "URCV". 1 20 Maximum number of parallel jobs exceeded. The job is currently being processed in a priority class with lower priority (first call). BSEND: Send data in segments Description The "BSEND" instruction sends data to a remote partner instruction of type "BRCV (Page 3089)". With this type of data transfer, more data can be transported between the communication partners than is possible with all other communication instructions for 3086 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References configured S7 connections. In each case, the maximum data volume amounts to 65534 bytes (standard access) or 65535 bytes (optimized access) for the integrated interface and for SIMATIC Net CP. Functional description You specify the instruction pair "BSEND" and "BRCV" with the input parameter R_ID. The R_ID parameter must be identical in the related instructions. The send job is activated after the instruction is called and a positive edge is detected at control input REQ. After the call, "BSEND" is not processed in the background, which means the data can only be read within the user program. The data area to be transmitted is segmented. Each segment is sent individually to the partner. Each segment is acknowledged by the partner after the application of this segment by "BRCV (Page 3089)". If the data is segmented, "BSEND" must be called multiple times until all segments have been transferred. The data area of the data to be sent is specified by SD_1. To ensure data consistency, you may only write to the part of the currently used sending area SD_1 after the current send operation is complete. This is the case when the value of the status parameter DONE changes to "1". The length of the send data is specified by LEN based on the job. With LEN = "0", all data addressed with the SD_1 parameter is sent. If there is a positive edge at control input R, the current sending process is canceled. Due to the asynchronous data transfer, a new data transfer can only be initiated if the previous data has been fetched by a partner instruction call. When the data has been collected, the status parameter "NDR" is set in the partner instruction "BRCV". Note Migration of S7-400 user programs An S7-400 CPU interprets the parameter SD_1 as pointer and not as data area. With S7-1500, LEN may not exceed the area of SD1. This was permitted with S7-400. Recommendation: Use the maximum size for the LEN parameter (65534 bytes for the integrated interface) as size of the data area at the SD_1 parameter. Parameters The following table shows the parameters of the "BSEND" instruction: Parameter Declaration Data type Memory area Description REQ Input BOOL I, Q, M, D, L or constant Control parameter request, activates the data exchange at a positive edge R Input BOOL I, Q, M, D, L or constant Control parameter reset, activates an abort of the current data exchange at a positive edge WinCC Basic V13.0 System Manual, 02/2014 3087 Programming the PLC 9.7 References Parameter Declaration Data type Memory area Description ID Input CONN_PR G I, Q, M, D, L, P or constant Addressing parameters for specifying the connection to the partner CPU. R_ID Input CONN_R_I D I, Q, M, D, L or constant Addressing parameter for defining the instruction pairs "BSEND" and "BRCV (Page 3089)". See also: Common parameters of instructions for S7 communication (Page 3075) SD_1 InOut VARIANT I, Q, M, D Pointer to send area LEN InOut WORD I, Q, M, D, L Length of the block of data to be sent in bytes. DONE Output BOOL I, Q, M, D, L With LEN = "0", all data is sent by SD_1. Status parameter 0: Job not yet started or still executing. 1: Job executed without errors. ERROR Output BOOL I, Q, M, D, L Status parameter 0: Neither warning nor error. 1: An error has occurred. STATUS supplies detailed information on the type of error. STATUS Output WORD I, Q, M, D, L Status parameter See "ERROR and STATUS parameters" table. For additional information on valid data types, refer to "Overview of the valid data types (Page 1204)". Parameters ERROR and STATUS The following table contains all specific error information for "BSEND" that can be output via the ERROR and STATUS parameters. ERROR STATUS (decimal) Explanation 0 11 Warning: New job not active because the previous job is still busy. 0 25 Communication has started. The job is being processed. 1 1 Communication problem has occurred. Possible causes: Connection description not loaded (local or remote) Connection interrupted (for example: cable, CPU off, CP in STOP mode) Connection to partner not yet established 1 2 Negative acknowledgment of partner instruction. The instruction cannot be executed. 1 3 R_ID is unknown on the connection specified by the ID or the receive block has not yet been called. 1 4 Error in the data length or data type in the send area pointer SD_1. Value for LEN is greater than area SD_1. 1 5 Reset request was executed. 1 6 Partner instruction is in DISABLED status (EN_R has the value "0"). Also check the input parameters of "BRCV (Page 3089)" for consistency with "BSEND". 1 7 "BRCV (Page 3089)" partner instruction not called since the last data transfer. 3088 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References ERROR STATUS (decimal) Explanation 1 8 Access to remote object in the user memory was rejected: The destination area for the associated "BRCV (Page 3089)" is too small. ERROR = 1, STATUS = 4 or ERROR = 1, STATUS = 10 reported at the output parameters of "BRCV (Page 3089)". 1 10 Access to the local user memory not possible (for example, access to a deleted DB). 1 18 R_ID already exists in the connection. 1 20 Maximum number of parallel jobs exceeded. The job is currently being processed in a priority class with lower priority (first call). BRCV: Receive data in segments Description The "BRCV" instruction receives data from a remote partner instruction of type "BSEND (Page 3086)". The R_ID parameter must be identical in the related instructions. The instruction is ready to receive data (STATUS = 25) after it is called with the value "1" at control input EN_R. An active job can be canceled with EN_R=0. The maximum receive area is specified by RD_1. Data will be received consistently if you fully evaluate the part of the RD_1 receive area currently in use before calling the block again with value 1 at control input EN_R. After each received data segment, an acknowledgment is sent to the partner instruction. If there are multiple segments it will be necessary to call "BRCV" several times until all of the segments have been received. Asynchronous data receipt is indicated by STATUS = 17. The amount of data currently received is indicated at the parameter LEN. The RD_1 parameter must remain constant during the operation. Value "1" at the NDR status parameter indicates that all data segments have been received without error. The received data remains unchanged until the next call with EN_R=1. Parameters The following table shows the parameters of the "BRCV" instruction: Parameter Declaration Data type Memory area Description EN_R Input BOOL I, Q, M, D, L or constant Control parameter enabled to receive, signals ready to receive if the input is set. ID Input CONN_PRG I, Q, M, D, L, P or constant Addressing parameters for specifying the connection to the partner CPU. R_ID Input CONN_R_ID I, Q, M, D, L or constant Addressing parameter for defining the instruction pairs "BSEND (Page 3086)" and "BRCV". See also: Common parameters of instructions for S7 communication (Page 3075) RD_1 InOut VARIANT I, Q, M, D Pointer to the receive area. LEN InOut WORD I, Q, M, D, L Length of the data already received in bytes. WinCC Basic V13.0 System Manual, 02/2014 3089 Programming the PLC 9.7 References Parameter Declaration Data type Memory area Description NDR Output BOOL I, Q, M, D, L Status parameter 0: Job not yet started or still running. 1: Job successfully completed. ERROR Output BOOL I, Q, M, D, L Status parameter 0: Neither warning nor error 1: An error has occurred. STATUS supplies detailed information on the type of error. STATUS Output WORD I, Q, M, D, L Status parameter See "ERROR and STATUS parameters" table. For additional information on valid data types, refer to "Overview of the valid data types (Page 1204)". Parameters ERROR and STATUS The following table contains all specific error information for "BRCV" that can be output via the ERROR and STATUS parameters. ERROR STATUS (decimal) Explanation 0 17 Warning: Instruction receives data asynchronously. The LEN parameter shows the amount of data already received in bytes. 0 25 Communication has started. The job is being processed. 1 1 Communication problem has occurred. Possible causes: Connection description not loaded (local or remote) Connection interrupted (for example: cable, CPU off, CP in STOP mode) Connection to partner not yet established 1 2 Function cannot be executed (protocol error) 1 4 Error in the receive area pointer RD_1 relating to the data length or data type. The block of data sent is longer than the receive area. 1 5 Reset request received, incomplete transfer. 1 8 Access error in associated "BSEND (Page 3086)": After the last valid data segment has been sent, ERROR = 1 and STATUS = 4 or ERROR = 1 and STATUS = 10 is reported. 1 10 Access to the local user memory not possible (for example, access to a deleted DB). 1 18 Value at R_ID parameter already exists in the connection specified at the ID parameter (R_ID value must be unique for the connection). 1 20 Maximum number of parallel jobs exceeded. The job is currently being processed in a priority class with lower priority (first call). 3090 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References 9.7.5.3 Open User Communication TSEND_C: Send data via Ethernet TSEND_C: Send data via Ethernet Description The "TSEND_C" instruction sets up and establishes a TCP or ISO-on-TCP communication connection. Once the connection has been set up and established, it is automatically maintained and monitored by the CPU. The connection description specified at the CONNECT parameter is used to set up the communication connection. The instruction is executed asynchronously and has the following functions: A communication connection is set up and established: The communication connection is set up and established with CONT=1. Once the connection is successfully established, the DONE parameter is set to "1" for one cycle. An existing connection is terminated and the connection which has been set up is removed when the CPU goes into STOP mode. To set up and establish the connection again, you must execute "TSEND_C" again. For information on the number of possible communication connections, refer to the technical specifications for your CPU. Sending data via an existing communication connection: You specify the send area with the DATA parameter. This includes the address and the length of the data to be sent. Do not use a data area with the data type BOOL or Array of BOOL at the DATA parameter. If you use purely symbolic values at the DATA parameter, the LEN parameter must have the value "0". The send job is executed when a rising edge is detected at the REQ parameter. With the LEN parameter, you specify the maximum number of bytes sent with a send job. When sending data (rising edge at the REQ parameter), the CONT parameter must have the value "1" in order to establish or maintain a connection. The data to be sent must not be edited until the send job is completed. If the send job executes successfully, the DONE parameter is set to "1". Signal state "1" at the DONE parameter is not confirmation that the data sent has already been read by the communication partner. Terminating the communication connection: The communication connection is terminated when the CONT parameter is set to "0" even if an ongoing data transmission is not complete yet. This does not apply if you are using an already configured connection for "TSEND_C". When setting the COM_RST parameter to "1", the currently established connection or a current data transmission can be reset at any time. This terminates the existing communication connection and a new connection is established. If data is being transferred when it executes again, this can lead to a loss of data. To enable "TSEND_C" again after the execution (DONE = 1), call the instruction once with REQ = 0. WinCC Basic V13.0 System Manual, 02/2014 3091 Programming the PLC 9.7 References Parameters The following table shows the parameters of the "TSEND_C" instruction: Parameter Declaration Data type Memory area Description REQ Input BOOL I, Q, M, D, L Starts the send job on a rising edge. CONT Input BOOL I, Q, M, D, L Controls the communication connection: 0: Disconnect the communication connection 1: Establish and maintain the communication connection When sending data (rising edge at the REQ parameter), the CONT parameter must have the value TRUE in order to establish or maintain a connection. LEN Input UINT I, Q, M, D, L or constant Maximum number of bytes to be sent with the job. If you use purely symbolic values at the DATA parameter, the LEN parameter must have the value "0". CONNECT InOut TCON_Param D Pointer to the connection description See also: Auto-Hotspot DATA InOut VARIANT I, Q, M, D, L Pointer to the send area containing the address and the length of the data to be sent. COM_RST InOut BOOL I, Q, M, D, L Restarts the instruction: 0: Irrelevant 1: Complete restart of the instruction causing an existing connection to be terminated and a new connection to be established. DONE Output BOOL I, Q, M, D, L Status parameter with the following values: 0: Job not yet started or still in progress 1: Job completed without error BUSY Output BOOL I, Q, M, D, L Status parameter with the following values: 0: Job not yet started or already completed 1: Job not yet completed. A new job cannot be started. ERROR Output BOOL I, Q, M, D, L Status parameter with the following values: 0: No error 1: Error occurred STATUS Output WORD I, Q, M, D, L Status of the instruction You can find additional information on valid data types under "Overview of the valid data types (Page 1204)". BUSY, DONE and ERROR parameters You can check the status of the job with the BUSY, DONE, ERROR and STATUS parameters. The BUSY parameter indicates the processing status. With the DONE parameter, you can check whether or not a job executed successfully. The ERROR parameter is set when errors occurred during execution of "TSEND_C". The error information is output at the STATUS parameter. 3092 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References The following table shows the relationship between the BUSY, DONE and ERROR parameters: BUSY DONE ERROR Description 1 - - The job is being processed. 0 1 0 The job was completed successfully. 0 0 1 The job ended with an error. The cause of the error is specified in the STATUS parameter. 0 0 0 No new job was assigned. ERROR and STATUS parameters ERROR STATUS* Description (W#16#...) 0 0000 Job completed without error. 0 0001 The connection establishment is complete. 0 0003 The connection termination is complete. 0 7000 No job processing active. 0 7001 Start execution of the job Establish connection Wait for connection partner 0 7002 Data was sent. 0 7003 Connection is being terminated. 0 7004 Connection established and monitored, no job processing active. 1 80A0 Group error for error codes 80A1 and 80A2. 1 80A1 Connection or port already being used by user. Communication error: - The specified connection has not yet been established. - The specified connection is being terminated. Transfer via this connection is not possible. - The interface is being re-initialized. 1 80A2 Local or remote port is being used by the system. 1 80A3 Attempt being made to terminate a non-existent connection. 1 80A4 IP address of the remote endpoint of the connection is invalid, in other words, it matches the IP address of the local partner. 1 80A7 Communication error: You called the instruction with COM_RST = 1 before the send job was complete. 1 80AA A connection is currently being established with the same connection ID by another block. Repeat the job with a new rising edge at the REQ parameter. 1 80B2 The CONNECT parameter points to a data block that was generated with the attribute "Only store in load memory". 1 80B3 Inconsistent parameter assignment: Group error for error codes 80A0 to 80A2, 80A4, 80B4 to 80B9. 1 80B4 You have violated one or both of the following conditions for passive connection establishment (active_est = FALSE) when using the ISO-on-TCP protocol variant (connection_type = B#16#12): "local_tsap_id_len >= B#16#02", and/or "local_tsap_id[1] = B#16#E0". 1 80B5 Only passive connection establishment is permitted for connection type 13 = UDP. WinCC Basic V13.0 System Manual, 02/2014 3093 Programming the PLC 9.7 References ERROR STATUS* Description (W#16#...) 1 80B6 Parameter assignment error in the connection_type parameter of the data block for connection description. 1 80B7 Error in one of the following parameters of the data block for connection description: block_length, local_tsap_id_len, rem_subnet_id_len, rem_staddr_len, rem_tsap_id_len, next_staddr_len. 1 8085 The LEN parameter is larger than the highest permitted value. 1 8086 The ID parameter within the CONNECT parameter is outside the permitted range. 1 8087 Maximum number of connections reached; no additional connection possible. 1 8088 The value at the LEN parameter does not correspond to the receive area set at the DATA parameter. 1 8089 The CONNECT parameter does not point to a data block. 1 8091 Maximum nesting depth exceeded. 1 809A The CONNECT parameter points to a field that does not correspond to the length of the connection description. 1 809B The ID of the local device in the connection description does not correspond to the CPU. 1 80C3 All connection resources are in use. A block with this ID is already being processed in a different priority group. 1 80C4 Temporary communication error: The connection cannot be established at this time. The interface is receiving new parameters or the connection is being established. The configured connection is currently being removed by a "TDISCON" instruction. The connection used is being terminated by a call with COM_RST= 1. 1 80C6 Remote network error. Remote partner cannot be reached. 1 8722 Parameter CONNECT: The source area is invalid. The area does not exist in the DB. 1 873A Parameter CONNECT: Access to the connection description is not possible (for example, DB does not exist). 1 877F Parameter CONNECT: Internal error. 1 8822 Parameter DATA: Invalid source area, the area does not exist in the DB. 1 8824 Parameter DATA: Area error in the VARIANT pointer. 1 8832 Parameter DATA: The DB number is too high. 1 883A Parameter CONNECT: Access to specified connection data not possible (e.g. because the DB does not exist). 1 887F Parameter DATA: Internal error, e.g. invalid VARIANT reference. 1 893A Parameter DATA: Access to send area not possible (e.g. because the DB does not exist). * The error codes can be displayed as integer or hexadecimal values in the program editor. For additional information on toggling display formats, refer to "See also". 3094 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Note Error messages of the instructions "TCON", "TSEND", "T_DIAG" and "TDISCON" Internally, the "TSEND_C" instruction uses the instructions "TCON (Page 3124)", "TSEND (Page 3137)", "T_DIAG (Page 3157)", "T_RESET (Page 3156)" and "TDISCON (Page 3132)". The error messages of these instructions can also be output at the STATUS parameter. The meaning of the error codes is described in the corresponding instructions. In the event of identical error codes for internally used instructions with different meanings, the instance data block of "TSEND_C" can be used to determine which instruction output the error. TSEND_C: Send data via Ethernet Description The "TSEND_C" instruction sets up and establishes a communications connection. Once the connection has been set up and established, it is automatically maintained and monitored by the CPU. The instruction is executed asynchronously and has the following functions: Setting up and establishing a communication connection Sending data via an existing communication connection Terminating or resetting the communication connection Internally, the instruction "TSEND_C" uses the communication instructions TCON", "TSEND", "T_DIAG", "T_RESET" and "TDISCON". Setting up and establishing a communication connection The communication connection is set up and established with CONT=1. For information on the number of possible communication connections, refer to the technical specifications for your CPU. The connection description specified at the CONNECT parameter is used to set up the communication connection. The following connection types can be used: Programmed connections (structure of connection via "TCON"): - TCP / UDP: Connection description via the TCON_IP_v4 system data type - ISO-on-TCP: Connection description via the TCON_IP_RFC system data type - ISO: Connection description via the TCON_ISOnative system data type (for CP1543-1 only) Configured connections - Specify an existing connection in the TCON_Configured system data type. An existing connection is terminated and the connection which has been set up is removed when the CPU goes into STOP mode. To set up and establish the connection again, you must execute "TSEND_C" again. WinCC Basic V13.0 System Manual, 02/2014 3095 Programming the PLC 9.7 References Sending data via an existing communication connection The send job is executed when a rising edge is detected at the REQ parameter. As described above, the communication connection is established first. You specify the send area with the DATA parameter. This includes the address and the length of the data to be sent. Do not use a data area with the data type BOOL or Array of BOOL at the DATA parameter. With the LEN parameter, you specify the maximum number of bytes sent with a send job. If you use a send area with optimized access at the DATA parameter, the LEN parameter must have the value "0". The data to be sent must not be edited until the send job is completed. Terminating and resetting the communication connection The communication connection is terminated when the CONT parameter is set to "0" even if an ongoing data transmission is not complete yet. This does not apply if you are using a configured connection for "TSEND_C". The connection can be reset at any time by setting the parameter COM_RST to "1". This terminates the existing communication connection and a new connection is established. If data is being transferred at this time, this can lead to data loss. Parameters The following table shows the parameters of the "TSEND_C" instruction: Parameter Declaration Data type Memory area Description REQ Input BOOL I, Q, M, D, L, T, C or constant Starts the send job on a rising edge. CONT Input BOOL I, Q, M, D, L Controls the communication connection: 0: Disconnect the communication connection. 1: Establish and maintain the communication connection. LEN 3096 Input UDINT I, Q, M, D, L or constant Optional parameter (hidden) Maximum number of bytes to be sent with the job. If you use a send area with optimized access at the DATA parameter, the value "0" must be used at the LEN parameter. WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameter Declaration Data type Memory area Description CONNECT InOut VARIANT D Pointer to the structure of the connection description: Programmed connection: - For TCP, use the TCON_IP_v4 system data type For description, refer to:Auto-Hotspot - For ISO-on-TCP, use the TCON_IP_RFC system data type For description, refer to: Auto-Hotspot - For ISO, use the TCON_ISOnative system data type (only for CP1543-1) For description, refer to instruction "TCON (Page 3127)". Configured connection: - For existing connections, use the TCON_Configured system data type For a description see "System data type for configured connections" below DATA InOut VARIANT I, Q, M, D, L Pointer to the send area containing the address and the length of the data to be sent. ADDR InOut VARIANT D Optional parameter (hidden) Pointer to the address of the recipient. COM_RST InOut BOOL I, Q, M, D, L Optional parameter (hidden) Resets the connection: 0: Irrelevant 1: The existing connection is reset. The COM_RST parameter is reset after evaluation by the "TSEND_C" instruction and should not, therefore, be interconnected statically. DONE Output BOOL I, Q, M, D, L Status parameter with the following values: 0: Send job not yet started or still in progress. 1: Send job executed without error. This state is only displayed for one cycle. The output parameter DONE is set if an intermediate step was completed successfully during processing (connection establishment, sending, connection termination) and if the execution of "TSEND_C" was completed successfully. BUSY Output BOOL I, Q, M, D, L Status parameter with the following values: 0: Send job not yet started or already completed. 1: Send job not yet completed. A new send job cannot be started. WinCC Basic V13.0 System Manual, 02/2014 3097 Programming the PLC 9.7 References Parameter Declaration Data type Memory area Description ERROR Output BOOL I, Q, M, D, L Status parameter with the following values: 0: No error 1: Error occurred during connection establishment, data transmission or connection termination. The output parameter ERROR can be set due to an error in the "TSEND_C" instruction or the communication instructions used internally. STATUS Output WORD I, Q, M, D, L Status of instruction (see the "ERROR and STATUS" parameters" description). You can find additional information on valid data types under "Overview of the valid data types (Page 1204)". REQ, CONT and COM_RST parameters The parameter CONT controls the connection establishment of the "TSEND_C" instruction regardless of the REQ parameter. The behavior of the CONT parameter partially depends on whether a programmed or a configured connection is used: With CONT = "0": No data is sent (regardless of whether a programmed or a configured connection is used). When changing CONT = "0" to "1": - With a programmed connection, it is established with "TCON". - With a configured connection, it is checked with "T_DIAG". With CONT = "1": - As long as no data is sent (REQ="0"), the connection is checked with "T_DIAG". - If the internally used communication instructions signal that no connection end point exists, the connection is automatically reestablished with "TCON". When changing CONT = "1" to "0": - With a programmed connection, it is terminated with "TDISCON". - With a configured connection, it is reset with "T_RESET". The parameter COM_RST resets the connection when changing from "0" to "1": If a connection is established, it is reset with "T_RESET" (regardless of whether a programmed or configured connection is used). If no connection is established, the setting of the parameter has no effect. The REQ and COM_RST parameters only have an effect if CONT has been set to "1". The following table shows the relationship between the REQ, CONT and COM_RST parameters: 3098 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References REQ CONT COM_ RST Status of the instruction Description irreleva nt 0 irreleva nt Not yet executed No job active (STATUS = 7000). irreleva nt 0 irreleva nt Initialization Connection is being terminated. The instruction is being reset. irreleva nt 0>1 irreleva nt Connection establishment Connection is being established. Data is not being transferred yet. 0 1 0 Connection established The connection is established and is monitored with the instruction "T_DIAG". irreleva nt 1 0>1 Connection established The connection is interrupted by "T_RESET" briefly and reset. 0>1 1 0 Connection established Instruction starts sending. irreleva nt 1 0>1 Data is being sent Data transmission is interrupted. The connection is being reset. System data type for configured connections For configured connections at the CONNECT parameter, use the following structure for connection description to TCON_Configured: Byte Parameter Data type Start value Description 0 ... 1 InterfaceID HW_ANY - Hardware identifier of the local interface (value range: 0 to 65535). 2 ... 3 ID CONN_OUC - Reference to the connection (value range: 1 to 4095). Enter the connection ID of the existing connection. 4 ConnectionType BYTE - Connection type Select 254 (decimal) for a configured connection. BUSY, DONE and ERROR parameters You can check the status of the job with the BUSY, DONE, ERROR and STATUS parameters. The BUSY parameter indicates the processing status. With the DONE parameter, you can check whether or not a send job executed successfully. The ERROR parameter is set when errors occurred during execution of "TSEND_C". The error information is output at the STATUS parameter. The following table shows the relationship between the BUSY, DONE and ERROR parameters: DONE BUSY ERROR Description 0 0 0 The instruction has not been executed yet (no rising edge at REQ parameter). 0 1 0 The instruction is being executed and calls the internally used communication instructions. WinCC Basic V13.0 System Manual, 02/2014 3099 Programming the PLC 9.7 References DONE BUSY ERROR Description 1 0 0 The send job was completed successfully. "0000" is output at the STATUS parameter. DONE = "1" is only displayed for one cycle. 0 0 1 The execution of the instruction or an intermediate step during processing was terminated with an error. If there is a subsequent error due to an internally used communication instruction, the error that occurred first during processing is displayed. This state is only displayed for one cycle. ERROR and STATUS parameters ERROR STATUS* Description (W#16#...) 0 0000 Send job was executed without error. 0 0001 Communication connection established. 0 0003 Communication connection closed. 0 7000 No active send job execution; no communication connection established. 0 7001 Initial call for establishing a connection. 0 7002 Second call for establishing a connection 0 7003 Communication connection is being terminated. 0 7004 Communication connection has been established and is being monitored. No send job execution active. 0 7005 Data transmission in progress. 1 80A1 Connection or port already being used by user. Communication error: - The specified connection has not yet been established. - The specified connection is being terminated. Transfer via this connection is not possible. - The interface is being re-initialized. 1 80A3 The nested "T_DIAG" instruction has reported that the connection has closed. 1 80A4 IP address of the remote endpoint of the connection is invalid or it matches the IP address of the local partner. 1 80A7 Communication error: You called the instruction with COM_RST = 1 before the send job was complete. 1 80AA A connection is currently being established with the same connection ID by another block. Repeat the job with a new rising edge at the REQ parameter. 1 80B4 You have violated one or both of the following conditions for passive connection establishment (active_est = FALSE) when using the ISO-on-TCP protocol variant (connection_type = B#16#12): local_tsap_id_len >= B#16#02 local_tsap_id[1] = B#16#E0 1 80B5 Only passive connection establishment is permitted for connection type 13 = UDP. 1 80B6 Parameter assignment error in the connection_type parameter of the data block for connection description. 1 80B7 Error in one of the following parameters of the data block for connection description: block_length, local_tsap_id_len, rem_subnet_id_len, rem_staddr_len, rem_tsap_id_len, next_staddr_len. 3100 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References ERROR STATUS* Description (W#16#...) 1 8085 The LEN parameter is larger than the highest permitted value. 1 8086 The ID parameter within the CONNECT parameter is outside the permitted range. 1 8087 Maximum number of connections reached; no additional connection possible. 1 8088 The value at the LEN parameter does not correspond to the receive area set at the DATA parameter. 1 8089 The CONNECT parameter does not point to a data block. 1 8091 Maximum nesting depth exceeded. 1 809A The CONNECT parameter points to a field that does not correspond to the length of the connection description. 1 809B InterfaceID is invalid. It is either zero or it does not point to a local CPU interface or a CP. 1 80C3 All connection resources are in use. 1 80C4 A block with this ID is already being processed in a different priority group. Temporary communication error: The connection cannot be established at this time. The interface is receiving new parameters or the connection is being established. The configured connection is currently being removed by a "TDISCON (Page 3132)" instruction. The connection used is being terminated by a call with COM_RST = 1. 1 80C6 Remote network error. Remote partner cannot be reached. 1 8722 Parameter CONNECT: The source area is invalid. The area does not exist in the DB. 1 873A Parameter CONNECT: Access to the connection description is not possible (for example, because the DB is not available). 1 877F Parameter CONNECT: Internal error. 1 8822 Parameter DATA: Invalid source area, the area does not exist in the DB. 1 8824 Parameter DATA: Area error in the VARIANT pointer. 1 8832 Parameter DATA: The DB number is too high. 1 883A Parameter CONNECT: Access to specified connection data not possible (e.g. because the DB does not exist). 1 887F Parameter DATA: Internal error, e.g. invalid VARIANT reference. 1 893A Parameter DATA: Access to send area not possible (e.g. because the DB does not exist). * The error codes can be displayed as integer or hexadecimal values in the program editor. For additional information on toggling display formats, refer to "See also". Note Error messages of the instructions "TCON", "TSEND", "T_DIAG", "T_RESET" and "TDISCON" Internally, the "TSEND_C" instruction uses the instructions "TCON (Page 3127)", "TSEND (Page 3137)", "T_DIAG (Page 3157)", "T_RESET (Page 3156)" and "TDISCON (Page 3132)". The error messages of these instructions can also be output at the STATUS parameter. The meaning of the error codes is described in the corresponding instructions. In the event of identical error codes for internally used instructions with different meanings, the instance data block of "TSEND_C" can be used to determine which instruction output the error. WinCC Basic V13.0 System Manual, 02/2014 3101 Programming the PLC 9.7 References TRCV_C: Receive data via Ethernet TRCV_C: Receive data via Ethernet Description The "TRCV_C" instruction is executed asynchronously and has the following functions: 1. Setting up and establishing a communication connection: "TRCV_C" sets up and establishes a TCP or ISO-on-TCP communication connection. Once the connection has been set up and established, it is automatically maintained and monitored by the CPU. The connection description specified at the CONNECT parameter is used to set up the communication connection. To establish a connection, the CONT parameter must be set to the value "1". Once the connection is successfully established, the DONE parameter is set to "1". An existing connection is terminated and the connection which has been set up is removed when the CPU goes into STOP mode. To set up and establish the connection again, you must execute "TRCV_C" again. For information on the number of possible communication connections, refer to the technical specifications for your CPU. 2. Receiving data via an existing communication connection: If the EN_R parameter is set to the value "1", receipt of data is enabled. When receiving data (rising edge at the EN_R parameter), the CONT parameter must have the value TRUE in order to establish or maintain a connection. The received data is entered in a receive area. You specify the length of the receive area either with the LEN parameter (if LEN <> 0) or with the length information of the DATA parameter (if LEN = 0) in accordance with the protocol variant used. If you use purely symbolic values at the DATA parameter, the LEN parameter must have the value "0". After data has been received successfully, the signal state at the DONE parameter is "1". If errors occur in the data transfer, the DONE parameter is set to "0". 3. Terminating the communication connection: The communication connection is terminated immediately when the CONT parameter is set to "0". TRCV_C is executed again when the COM_RST parameter is set. This terminates the existing communication connection and a new connection is established. If data is being received when it executes again, this can lead to a loss of data. 3102 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Receive modes of TRCV_C The following table shows how the received data is entered in the receive area. Protocol variant Availability of data in the receive area connection_type parameter of the connection description LEN parameter TCP The data is immediately available. Hexadecimal value: B#16#11 0 (Ad-hoc mode) Integer value: 17 TCP (Receipt of data with specified length) ISO on TCP (Message-oriented data transfer) The data is available as soon as the data length specified at the LEN parameter has been fully received. Hexadecimal value: B#16#11 The data is available as soon as the data length specified at the LEN parameter has been fully received. Hexadecimal value: B#16#12 1 to 8192 Integer value: 17 Integer value: 18 1 to 1452, if a CP is used. 1 to 8192, if no CP is used. TCP (Ad-hoc mode) The ad-hoc mode is only available with the TCP protocol variant. You use the ad-hoc mode to receive data with dynamic length with the "TRCV" instruction. You set ad-hoc mode by assigning the value "0" to the LEN parameter. All data types can be used for data blocks with standard access when you use ad-hoc mode. Only ARRAY of BYTE or data types with a length of 8 bits can be used for data blocks with optimized access (e.g., CHAR, USINT, SINT, etc.). The data length actually received is output at the RCVD_LEN parameter. TCP (Receipt of data with specified length) You use the value of the LEN parameter to specify the length for the data receipt. The data receipt is not complete until the length of data specified at the LEN parameter has been completely received. Only then is the data available in the receive area (DATA parameter). The actually received data length in bytes at the RCVD_LEN parameter corresponds to the data length at the LEN parameter after receipt. ISO on TCP (Message-oriented data transfer) Complete message blocks are sent via a connection with the protocol variant ISO on TCP; these are recognized as such by the recipient. When using ISO on TCP, "TRCV_C" signals data receipt as soon as the message block has been completely received. The receive area is defined by the LEN and DATA parameters. If the receive buffer (DATA parameter) is too small for the sent data, "TRCV_C" signals an error. The actually received data length in bytes at the RCVD_LEN parameter corresponds to the data length at the LEN parameter after receipt. WinCC Basic V13.0 System Manual, 02/2014 3103 Programming the PLC 9.7 References Parameters The following table shows the parameters of the "TRCV_C" instruction: Parameter Declaration Data type Memory area Description EN_R Input BOOL I, Q, M, D, L Receive enable CONT Input BOOL I, Q, M, D, L Controls the communication connection: 0: Disconnect the communication connection 1: Establish and maintain the communication connection When receiving data (rising edge at the EN_R parameter), the CONT parameter must have the value TRUE in order to establish or maintain a connection. LEN Input UINT I, Q, M, D, L or constant Maximum length of the data to be received. If you use purely symbolic values at the DATA parameter, the LEN parameter must have the value "0". CONNECT InOut TCON_Param D Pointer to the connection description DATA InOut VARIANT I, Q, M, D, L Pointer to the receive area COM_RST InOut BOOL I, Q, M, D, L Restarts the instruction: See also: Auto-Hotspot 0: Irrelevant 1: Complete restart of the instruction causing an existing connection to be terminated DONE Output BOOL I, Q, M, D, L Status parameter with the following values: 0: Job not yet started or still in progress 1: Job completed without error BUSY Output BOOL I, Q, M, D, L Status parameter with the following values: 0: Job not yet started or already completed 1: Job not yet completed. A new job cannot be started ERROR Output BOOL I, Q, M, D, L Status parameter ERROR: 0: No error 1: Error occurred STATUS Output WORD I, Q, M, D, L Status of the instruction RCVD_LEN Output UDINT I, Q, M, D, L Amount of data actually received in bytes You can find additional information on valid data types under "Overview of the valid data types (Page 1204)". BUSY, DONE and ERROR parameters You can check the status of the job with the BUSY, DONE, ERROR and STATUS parameters. The BUSY parameter indicates the processing status. With the DONE parameter, you can check whether or not a job executed successfully. The ERROR parameter is set when errors occurred during execution of "TRCV_C". The error information is output at the STATUS parameter. 3104 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References The following table shows the relationship between the BUSY, DONE and ERROR parameters: BUSY DONE ERROR Description 1 - - The job is being processed. 0 1 0 The job was completed successfully. 0 0 1 The job ended with an error. The cause of the error is output at the STATUS parameter. 0 0 0 No new job was assigned. ERROR and STATUS parameters ERROR STATUS* Description (W#16#...) 0 0000 Job completed without error. 0 0001 The connection establishment is complete. 0 0003 The connection termination is complete. 0 7000 No job processing active. 0 7001 Start execution of the job Establish connection Wait for connection partner 0 7002 Data is being received. 0 7003 Connection is being terminated. 0 7004 Connection established and monitored 0 7006 1 8085 No job processing active Data is currently being received. The LEN parameter is larger than the highest permitted value. The value at the LEN or DATA parameter was changed after the first call. 1 8086 The ID parameter is outside the permitted range. 1 8087 Maximum number of connections reached; no additional connection possible 1 8088 The value at the LEN parameter does not correspond to the receive area set at the DATA parameter. 1 8089 The CONNECT parameter does not point to a data block. 1 8091 Maximum nesting depth exceeded. 1 809A The CONNECT parameter points to a field that does not correspond to the length of the connection description. 1 809B The ID of the local device (local_device_id) in the connection description does not correspond to the CPU. 1 80A0 Group error for error codes W#16#80A1 and W#16#80A2. 1 80A1 Connection or port already being used by user. Communication error: 1 80A2 WinCC Basic V13.0 System Manual, 02/2014 - The specified connection has not yet been established. - The specified connection is being terminated. Transfer via this connection is not possible. - The interface is being re-initialized. Local or remote port is being used by the system. 3105 Programming the PLC 9.7 References ERROR STATUS* Description (W#16#...) 1 80A3 Attempt being made to re-establish an existing connection. Attempt being made to terminate a non-existent connection. 1 80A4 IP address of the remote endpoint of the connection is invalid, in other words, it matches the IP address of the local partner. 1 80A7 Communication error: You called the instruction with COM_RST = 1 before the send job was complete. 1 80B2 The CONNECT parameter points to a data block that was generated with the attribute "Only store in load memory". 1 80B3 Inconsistent parameter assignment: Group error for error codes W#16#80A0 to W#16#80A2, W#16#80A4, W#16#80B4 to W#16#80B9. 1 80B4 You have violated one or both of the following conditions for passive connection establishment (active_est = FALSE) when using the ISO-on-TCP protocol variant (connection_type = B#16#12): "local_tsap_id_len >= B#16#02", and/or "local_tsap_id[1] = B#16#E0". 1 80B5 Only passive connection establishment is permitted for connection type 13 = UDP. 1 80B6 Parameter assignment error in the connection_type parameter of the data block for connection description. 1 80B7 Error in one of the following parameters of the data block for connection description: block_length, local_tsap_id_len, rem_subnet_id_len, rem_staddr_len, rem_tsap_id_len, next_staddr_len. 1 80C3 All connection resources are in use. A block with this ID is already being processed in a different priority group. 1 80C4 Temporary communication error: The connection cannot be established at this time. The interface is receiving new parameters or the connection is being established. The configured connection is currently being removed by a "TDISCON" instruction. The connection used is being terminated by a call with COM_RST= 1. 1 80C6 The remote partner cannot be reached (network error). 1 8722 Error in the CONNECT parameter: Invalid source area (area not declared in data block). 1 873A Error in the CONNECT parameter: Access to connection description is not possible (no access to data block). 1 877F Error in the CONNECT parameter: Internal error 1 8922 Parameter DATA: Invalid target area; the area does not exist in the DB. 1 8924 Parameter DATA: Area error in the VARIANT pointer. 1 8932 Parameter DATA: The DB number is too high. 1 893A Parameter CONNECT: Access to specified connection data not possible (e.g. because the DB does not exist). 1 897F Parameter DATA: Internal error, e.g. invalid VARIANT reference. 1 8A3A Parameter DATA: No access to the data area, for example because the data block does not exist. * The error codes can be displayed as integer or hexadecimal values in the program editor. For additional information on toggling display formats, refer to "See also". 3106 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Note Error messages of the instructions "TCON", "TRCV" and "TDISCON" Internally, the TRV_C instruction uses the "TCON (Page 3124)", "TRCV (Page 3140)" and "TDISCON (Page 3132)" instructions. The error messages of these instructions are contained in the respective descriptions. TRCV_C: Receive data via Ethernet Description The "TRCV_C" instruction is executed asynchronously and implements the following functions in sequence: Setting up and establishing a communication connection Receiving data via an existing communication connection Terminating or resetting the communication connection Internally, the instruction "TRCV_C" uses the communication instructions TCON", "TRCV", "T_DIAG", "T_RESET" and "TDISCON". Setting up and establishing a communication connection The communication connection is set up and established with CONT=1. For information on the number of possible communication connections, refer to the technical specifications for your CPU. The connection description specified at the CONNECT parameter is used to set up the communication connection. The following connection types can be used: Programmed connections (structure of connection via "TCON"): - TCP / UDP: Connection description via the TCON_IP_v4 system data type - ISO-on-TCP: Connection description via the TCON_IP_RFC system data type - ISO: Connection description via the TCON_ISOnative system data type (for CP1543-1 only) Configured connections - Specify an existing connection in the TCON_Configured system data type. An existing connection is terminated and the connection which has been set up is removed when the CPU goes into STOP mode. To set up and establish the connection again, you must execute "TRCV_C" again. Receiving data via an existing communication connection Receipt of data is enabled when the EN_R parameter is set to the value "1". The received data is entered in a receive area. You specify the length of the receive area either with the LEN parameter (if LEN <> 0) or with the length information of the DATA parameter (if LEN = 0), WinCC Basic V13.0 System Manual, 02/2014 3107 Programming the PLC 9.7 References depending on the protocol variant being used. If you use purely symbolic values at the DATA parameter, the LEN parameter must have the value "0". Receive modes of TRCV_C: TCP (Ad-hoc mode) The ad-hoc mode is only available with the TCP protocol variant. You use the ad-hoc mode to receive data with dynamic length with the "TRCV_C" instruction. You set ad-hoc mode by assigning the value "1" to the ADHOC parameter. All data types can be used for data blocks with standard access when you use ad-hoc mode. Only ARRAY of BYTE or data types with a length of 8 bits can be used for data blocks with optimized access (e.g., CHAR, USINT, SINT, etc.). The data length actually received is output at the RCVD_LEN parameter. TCP (Receipt of data with specified length) Assign the value "0" to the ADHOC parameter for receipt of data with specified length. If ad-hoc mode is disabled, the data receipt is not complete until the length of data specified at the LEN parameter has been completely received. Only then is the data available in the receive area (DATA parameter). The actually received data length in bytes at the RCVD_LEN parameter corresponds to the data length at the LEN parameter after receipt. ISO on TCP (Message-oriented data transfer) Complete message blocks are sent via a connection with the protocol variant ISO on TCP; these are recognized as such by the recipient. The receive area is defined by the LEN and DATA parameters. If the receive buffer (DATA parameter) is too small for the sent data, "TRCV_C" signals an error. The actually received data length in bytes at the RCVD_LEN parameter corresponds to the data length at the LEN parameter after receipt. The following table shows how the received data is entered in the receive area. Protocol variant Availability of data in the receive area connection_type parameter of the connection description LEN parameter TCP The data is immediately available. Hexadecimal value: B#16#11 Integer value: 17 1 up to maximum length (depending on the CPU) The data is available as soon as the data length specified at the LEN parameter has been fully received. Hexadecimal value: B#16#11 1 to 8192 The data is available as soon as the data length specified at the LEN parameter has been fully received. Hexadecimal value: B#16#12 (Ad-hoc mode) TCP (Receipt of data with specified length) ISO on TCP (Message-oriented data transfer) Integer value: 17 1 to 8192 Integer value: 18 Terminating the communication connection The communication connection is terminated when the CONT parameter is set to "0" even if an ongoing data transmission is not complete yet. This does not apply if you are using a configured connection, however. The connection can be reset at any time by setting the parameter COM_RST to "1". This terminates the existing communication connection and a new connection is established. If data is being transferred at this time, this can lead to data loss. 3108 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameters The following table shows the parameters of the "TRCV_C" instruction: Parameter Declaration Data type Memory area Description EN_R Input BOOL I, Q, M, D, L, T, C or constant Receive enable CONT Input BOOL I, Q, M, D, L Controls the communication connection: 0: Disconnect the communication connection. 1: Establish communication connection and maintain after receipt of data. LEN Input UDINT I, Q, M, D, L or constant Maximum length of the data to be received. If you use a receive area with optimized access at the DATA parameter, the value "0" must be used at the LEN parameter. ADHOC Input BOOL I, Q, M, D, L or constant Optional parameter (hidden) D Pointer to the connection description CONNECT InOut VARIANT Use ad-hoc mode for the TCP protocol variant. Programmed connection: - For TCP or UDP, use the structure TCON_IP_v4 For description, refer to:Auto-Hotspot - For ISO-on-TCP, use the structure TCON_IP_RFC For description, refer to: Auto-Hotspot - For ISO, use the structure TCON_ISOnative (only for CP1543-1) For description, refer to instruction "TCON (Page 3127)": "Structure of the connection description according to TCON_ISOnative" Configured connection: - For existing connections, use the TCON_Configured system data type. For a description, see "System data type for configured connections" below. DATA InOut VARIANT I, Q, M, D, L Pointer to the receive area. ADDR InOut VARIANT D Optional parameter (hidden) Pointer to the address of the sender with connection type UDP. COM_RST InOut BOOL I, Q, M, D, L Optional parameter (hidden) Resets the connection: 0: Irrelevant 1: The existing connection is reset. The COM_RST parameter is reset after evaluation by the "TRCV_C" instruction and should not, therefore, be interconnected statically. WinCC Basic V13.0 System Manual, 02/2014 3109 Programming the PLC 9.7 References Parameter Declaration Data type Memory area Description DONE Output BOOL I, Q, M, D, L Status parameter with the following values: 0: Receipt not yet started or still in progress. 1: Receipt executed without error. This state is only displayed for one cycle. The output parameter DONE is set if an intermediate step was completed successfully during processing (connection establishment, receipt, connection termination) and if the execution of "TRCV_C" was completed successfully. BUSY Output BOOL I, Q, M, D, L Status parameter with the following values: 0: Receipt not yet started or already completed. 1: Receipt not yet completed. A new send job cannot be started. ERROR Output BOOL I, Q, M, D, L Status parameter with the following values: 0: No error 1: Error occurred during connection establishment, data receipt or connection termination. The output parameter ERROR can be set due to an error in the "TRCV_C" instruction or the communication instructions used internally. STATUS Output WORD I, Q, M, D, L Status of the instruction RCVD_LEN Output UDINT I, Q, M, D, L Amount of data actually received in bytes You can find additional information on valid data types under "Overview of the valid data types (Page 1204)". EN_R, CONT and COM_RST parameters The parameter CONT controls the connection establishment of the "TRCV_C" instruction regardless of the EN_R parameter. The behavior of the CONT parameter partially depends on whether a programmed or a configured connection is used: With CONT = "0": No data is received (regardless of whether a programmed or a configured connection is used). When changing CONT = "0" to "1": - With a programmed connection, it is established with "TCON". - With a configured connection, it is checked with "T_DIAG". With CONT = "1": - As long as no data is received (EN_R="0"), the connection is checked with "T_DIAG". - If the internally used communication instructions signal that no connection end point exists, the connection is automatically reestablished with "TCON". When changing CONT = "1" to "0": - With a programmed connection, it is terminated with "TDISCON". - With a configured connection, it is reset with "T_RESET". 3110 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References The parameter COM_RST resets the connection when changing from "0" to "1": If a connection is established, it is reset with "T_RESET" (regardless of whether a programmed or configured connection is used). If no connection is established, the setting of the parameter has no effect. The EN_R and COM_RST parameters only have an effect if CONT has been set to "1". The following table shows the relationship between the EN_R, CONT and COM_RST parameters: EN_R CONT COM_ RST Status of the instruction Description irreleva nt 0 irreleva nt Not yet executed No job active (STATUS = 7000). irreleva nt 0 irreleva nt Initialization Connection is being terminated. The instruction is being reset. irreleva nt 0>1 irreleva nt Connection establishment Connection is being established. Data is not being transferred yet. 0 1 0 Connection established The connection is established and is monitored with the instruction "T_DIAG". irreleva nt 1 0>1 Connection established The connection is interrupted by "T_RESET" briefly and reset. 0>1 1 0 Connection established Instruction starts receiving. irreleva nt 1 0>1 Data is being received Data transmission is interrupted. The connection is being reset. System data type for configured connections For configured connections at the CONNECT parameter, use the following structure for connection description to TCON_Configured: Byte Parameter Data type Start value Description 0 ... 1 InterfaceID HW_ANY - Hardware identifier of the local interface (value range: 0 to 65535). 2 ... 3 ID CONN_OUC - Reference to the connection (value range: 1 to 4095). Enter the connection ID of the existing connection. 4 ConnectionType BYTE - Connection type Select 254 (decimal) for a configured connection. BUSY, DONE and ERROR parameters You can check the status of the job with the BUSY, DONE, ERROR and STATUS parameters. The BUSY parameter indicates the processing status. With the DONE parameter, you can check whether or not a job executed successfully. The ERROR parameter is set when errors occurred during execution of "TRCV_C". The error information is output at the STATUS parameter. The following table shows the relationship between the BUSY, DONE and ERROR parameters: WinCC Basic V13.0 System Manual, 02/2014 3111 Programming the PLC 9.7 References DONE BUSY ERROR Description 0 0 0 The instruction has not been executed yet (no rising edge at EN_R parameter). 0 1 0 The instruction is being executed and calls the internally used communication instructions. 1 0 0 The receipt has been completed successfully. "0000" is output at the STATUS parameter. DONE = "1" is only displayed for one cycle. 0 0 1 The execution of the instruction or an intermediate step during processing was terminated with an error. If there is a subsequent error due to an internally used communication instruction, the error that occurred first during processing is displayed. This state is only displayed for one cycle. ERROR and STATUS parameters ERROR STATUS Description (W#16#...) 0 0000 Receive job executed without error. 0 0001 Communication connection established. 0 0003 Communication connection closed. 0 7000 No job processing active. 0 7001 Initial call for establishing a connection. 0 7002 Second call for establishing a connection. 0 7003 Communication connection is being terminated. 0 7004 Communication connection has been established and is being monitored. No receive job processing active. 0 7006 Data is currently being received. 1 8085 The LEN parameter is larger than the highest permitted value. The value at the LEN or DATA parameter was changed after the first call. 1 8086 The ID parameter is outside the permitted range. 1 8087 Maximum number of connections reached; no additional connection possible 1 8088 The value at the LEN parameter does not correspond to the receive area set at the DATA parameter. 1 8089 The CONNECT parameter does not point to a data block. 1 8091 Maximum nesting depth exceeded. 1 809A The CONNECT parameter points to a field that does not correspond to the length of the connection description. 1 809B InterfaceID is invalid. It is either zero or it does not point to a local CPU interface or a CP. 1 80A1 Connection or port already being used by user. Communication error: - The specified connection has not yet been established. - The specified connection is being terminated. Transfer via this connection is not possible. - The interface is being re-initialized. 1 80A3 The nested "T_DIAG" instruction has reported that the connection has closed. 1 80A4 IP address of the remote endpoint of the connection is invalid or it matches the IP address of the local partner. 1 80A7 Communication error: You called the instruction with COM_RST = 1 before the send job was complete. 3112 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References ERROR STATUS Description (W#16#...) 1 80B4 You have violated one or both of the following conditions for passive connection establishment (active_est = FALSE) when using the ISO-on-TCP protocol variant (connection_type = B#16#12): "local_tsap_id_len >= B#16#02", and/or "local_tsap_id[1] = B#16#E0". 1 80B5 Only passive connection establishment is permitted for connection type 13 = UDP. 1 80B6 Parameter assignment error in the connection_type parameter of the data block for connection description. 1 80B7 Error in one of the following parameters of the data block for connection description: block_length, local_tsap_id_len, rem_subnet_id_len, rem_staddr_len, rem_tsap_id_len, next_staddr_len. 1 80C3 All connection resources are in use. 1 80C4 A block with this ID is already being processed in a different priority group. Temporary communication error: The connection cannot be established at this time. The interface is receiving new parameters or the connection is being established. The configured connection is currently being removed by a "TDISCON" instruction. The connection used is being terminated by a call with COM_RST = 1. 1 80C6 The remote partner cannot be reached (network error). 1 8722 Error in the CONNECT parameter: Invalid source area (area not declared in data block). 1 873A Error in the CONNECT parameter: Access to connection description is not possible (no access to data block). 1 877F Error in the CONNECT parameter: Internal error 1 8922 Parameter DATA: Invalid target area; the area does not exist in the DB. 1 8924 Parameter DATA: Area error in the VARIANT pointer. 1 8932 Parameter DATA: The DB number is too high. 1 893A Parameter CONNECT: Access to specified connection data not possible (e.g. because the DB does not exist). 1 897F Parameter DATA: Internal error, e.g. invalid VARIANT reference. 1 8A3A Parameter DATA: No access to the data area, for example because the data block does not exist. Note Error messages of the instructions "TCON", "TRCV" and "TDISCON" Internally, the TRV_C instruction uses the "TCON (Page 3127)", "TRCV (Page 3140)" and "TDISCON (Page 3132)" instructions. The error messages of these instructions are contained in the respective descriptions. See also TSEND_C: Send data via Ethernet (Page 3095) WinCC Basic V13.0 System Manual, 02/2014 3113 Programming the PLC 9.7 References TMAIL_C: Transfer email Description of TMAIL_C Description You use the instruction "TMAIL_C" to send an e-mail via the Ethernet interface of the S7-1500 CPU or S7-1200 V4.0, a communication module (CM), or of a communication processor (CP). The instruction can only be used once the hardware has been configured and if the network infrastructure allows for a communication connection to the mail server. You define the content of the e-mail, and the connection data, using the following parameters: You define the recipient addresses with the parameters TO_S and CC. You define the content of the e-mail with the parameters SUBJECT and TEXT. You can define an attachment using VARIANT pointers at the ATTACHMENT and ATTACHMENT_NAME parameters. The connection data is defined, and addressing and authentication for the mail server executed, using the system data type Tmail_v4, Tmail_v6 or Tmail_FQDN at the MAIL_ADDR_PARAM parameter. - If you are using the interface of the S7-1500 CPU, the system data type Tmail_v4 must be used. In this case, the e-mail can only be sent via SMTP. - Any of the system data types can be used if you are using the interface of a CM/CP. The e-mail can then also be sent via SMTPS. You start the sending of an e-mail with an edge change from "0" to "1" for the REQ parameter. The job status is indicated by the output parameters "BUSY", "DONE", "ERROR" and "STATUS". You cannot send an SMS directly with the "TMAIL_C" instruction. Whether or not the e-mail can be forwarded by the mail server as an SMS depends on your telecommunications provider. Operation of the instruction The "TMAIL_C" instruction works asynchronously, which means its execution extends over multiple calls. You must specify an instance when you call the instruction "TMAIL_C". In the following cases, the connection to the mail server will be lost: If the CPU switches to STOP while "TMAIL_C" is active. If communication problems occur at the Industrial Ethernet bus. 3114 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References In this case, the transfer of the e-mail will be interrupted and it will not reach its recipient. The connection is also canceled once the instruction has been successfully executed and the email sent. NOTICE Changing user programs You can change the parts of your user program that directly affect calls of "TMAIL_C" only: The CPU is in "STOP" mode. No e-mail is being sent (REQ = 0 and BUSY = 0). This relates, in particular, to deleting and replacing program blocks that contain "TMAIL_C" calls or calls for the instance of "TMAIL_C". Ignoring this restriction can tie up connection resources. The automation system can change to an undefined status with the TCP/IP communication functions via Industrial Ethernet. A warm or cold restart of the CPU is required after the changes are transferred. Data consistency The TO_S, CC, SUBJECT, TEXT, ATTACHMENT and MAIL_ADDR_PARAM parameters are applied by the "TMAIL_C" instruction while it is running, which means that they may only be changed after the job has been completed (BUSY = 0). SMTP authentication Authentication refers here to a procedure for verifying identity, for example, with a password query. If you are using the S7-1500 CPU interface, the instruction "TMAIL_C" supports the SMTP authentication procedure AUTH-LOGIN which is required by most mail servers. For information about the authentication procedure of your mail server, please refer to your mail server manual or the website of your Internet service provider. Before you can use the AUTH-LOGIN authentication procedure, the "TMAIL_C" instruction requires the user name with which it is to log on to the mail server. This user name corresponds to the user name with which you set up a mail account on your mail server. It is transferred via the UserName parameter to the structure at parameter MAIL_ADDR_PARAM. If no user name is specified at the MAIL_ADDR_PARAM parameter, the AUTH-LOGIN authentication procedure is not used. The e-mail is then sent without authentication. To log on, the "TMAIL_C" instruction also requires the associated password. This password corresponds to the password you specified when you set up your mail account. It is transferred via the PassWord parameter to the structure at parameter MAIL_ADDR_PARAM. WinCC Basic V13.0 System Manual, 02/2014 3115 Programming the PLC 9.7 References Parameters The following table shows the parameters of the "TMAIL_C" instruction: Parameter Declaratio n Data type Memory area Description REQ Input BOOL I, Q, M, D, L, T, C or constant Control parameter REQUEST: Activates the sending of an e-mail upon a rising edge. TO_S (Page 3117) Input STRING D, L or constant Recipient addresses STRING with a maximum length of 240 characters (bytes). For the e-mail address format, see the example in the parameter description. CC (Page 3117) Input STRING D, L or constant CC recipient addresses (optional) STRING with a maximum length of 240 characters (bytes). Same e-mail address format as for the TO_S parameter. If an empty string is assigned here, the e-mail is not sent to a CC recipient. SUBJECT TEXT Input Input ATTACHMEN T Input ATTACHMEN T_NAME Input MAIL_ADDR_ PARAM (Page 3118) Input DONE (Page 3120) Output STRING STRING D, L or constant Subject of the e-mail D, L or constant Text of the e-mail (optional) VARIANT D STRING with a maximum length of 240 characters (bytes). STRING with a maximum length of 240 characters (bytes). If an empty string is assigned at this parameter, the e-mail is sent without text. E-mail attachment (optional) Reference to a byte/word/double word field (ArrayOfByte, ArrayOfWord or ArrayOfDWord) with a maximum length of 64 bytes. If no value is assigned, the e-mail is sent without an attachment. STRING D, L or constant VARIANT D E-mail attachment name (optional) Reference to a character string with a maximum length of 50 characters (bytes) to define the file name of the attachment. If an empty string is assigned at this parameter, the e-mail attachment will be sent with the file name "attachment.bin". Connection parameter and address of the email server To define the connection parameters, use the structure Tmail_v4, Tmail_v6 or Tmail_FQDN (see parameter description). BOOL I, Q, M, D, L Status parameter DONE = 0: Job not yet started or still executing. DONE = 1: Job was executed without errors. 3116 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameter Declaratio n Data type Memory area Description BUSY (Page 3120) Output BOOL I, Q, M, D, L Status parameter BUSY=0: The processing of "TMAIL_C" was stopped. BUSY = 1: E-mail transmission is not yet complete. ERROR (Page 3120) Output BOOL I, Q, M, D, L Status parameter ERROR = 0: No error has occurred. ERROR = 1: An error occurred during processing. STATUS supplies detailed information on the type of error. STATUS (Page 3121) Output WORD I, Q, M, D, L Status parameter Return value or error information of the "TMAIL_C" instruction (see parameter description). You can find additional information on valid data types under "Overview of the valid data types (Page 1204)". Note Optional parameters The optional parameters CC, TEXT, and ATTACHMENT are only sent with the e-mail if the corresponding parameters contain a string of length > 0. TO_S and CC parameters Description The TO_S and CC parameters are strings, for example, with the following content: <wenna@mydomain.com>, <ruby@mydomain.com> <admin@mydomain.com>, <judy@mydomain.com> Note the following rules when entering the parameters: A space and an opening pointed bracket "<" must be entered before each address. A closing pointed bracket ">" must be entered after each address. A comma must be entered between the addresses in TO and CC. For runtime and memory space reasons, the "TMAIL_C" instruction does not perform a syntax check of parameter TO_S or CC. WinCC Basic V13.0 System Manual, 02/2014 3117 Programming the PLC 9.7 References MAIL_ADDR_PARAM parameter Description At the MAIL_ADDR_PARAM parameter, you define the connection for sending the e-mail in the structure Tmail_v4, Tmail_v6 or Tmail_FQDN, and save the e-mail server address and login details. The structure you use at the MAIL_ADDR_PARAM parameter depends on the format in which the e-mail server is to be addressed: Tmail_v4: Addressing by IP address (IPv4). Tmail_v6: Addressing by IP address (IPv6). Tmail_FQDN: Addressing by fully qualified domain name (FQDN). Which structure you can use depends on the interface addressed at the InterfaceId parameter: If you want to use the "TMAIL_C" instruction with the internal interface, the structure Tmail_v4 must be used at the MAIL_ADDR_PARAM parameter. If you are using a communication processor (CP) or communication module (CM), you can use all three addressing options (IPv4, IPv6 and FQDN). Table 9-97 Tmail_v4: Addressing the mail server by IP address (IPv4) Parameter Data type Tmail_v4 Struct Description InterfaceId LADDR Hardware identifier of the interface ID CONN_OUC Connection ID ConnectionType BYTE Connection type. Select 16#20 as the connection type for IPv4. ActiveEstablished BOOL Status bit. Set to "1" once the connection is established. CertIndex BYTE =0: SMTP used (Simple Mail Transfer Protocol). SMTP must be used if the e-mail is being sent via the interface of an S7-1500 CPU. 0: SMTPS used to secure the connection before it is established (with CPs/CMs). You use the CertIndex parameter to specify the certificate to be used (see "Project navigation" > "Global security settings" > "Certificate manager"). WatchDogTime TIME Execution watchdog. Use this parameter to define the maximum execution time for the send operation. Note: Connection establishment can take longer (approx. one minute) if the connection is slow. When you specify the WATCH_DOG_TIME parameter, remember to allow for the time required to establish the connection. The connection is terminated once the specified time has elapsed. MailServerAddress IP_v4 IP address of the mail server. IPv4 in the following format: XXX.XXX.XXX.XXX (decimal). Example: 192.142.131.237. UserName 3118 STRING[254] Mail server login name WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameter Data type Description PassWord STRING[254] Mail server password From EMAIL_ADDR E-mail sender address, which is defined using the following two STRING parameters. For example: "myname@mymailserver.com". LocalPartPlusAtSi STRING[64] gn Local part of sender address, including @ sign. Example: "myname@". FullQualifiedDom ainName Fully Qualified Domain Name ( FQDN for short) of the mail server. Example: "mymailserver.com". Table 9-98 STRING[254] Tmail_v6: Addressing the mail server by IP address (IPv6) Parameter Data type Tmail_v6 Struct InterfaceId Description LADDR Hardware identifier of the interface ID CONN_OUC Connection ID ConnectionType BYTE Connection type. Select 16#21 as the connection type for IPv6. ActiveEstablished BOOL Status bit. Set to "1" once the connection is established. CertIndex BYTE =0: SMTP used (Simple Mail Transfer Protocol). SMTP must be used if the e-mail is being sent via the interface of an S7-1500 CPU. 0: SMTPS used to secure the connection before it is established (with CPs/CMs). You use the CertIndex parameter to specify the certificate to be used (see "Project navigation" > "Global security settings" > "Certificate manager"). WatchDogTime TIME Execution watchdog. Use this parameter to define the maximum execution time for the send operation. Note: Connection establishment can take longer (approx. one minute) if the connection is slow. When you specify the WATCH_DOG_TIME parameter, remember to allow for the time required to establish the connection. The connection is terminated once the specified time has elapsed. MailServerAddress IP_v6 IP address of the mail server (IPv6) in the following format: XXXX.XXXX.XXXX.XXXX.XXXX.XXXX.XXXX.XXXX (hexadecimal). The address is divided into 8 blocks of 2 bytes each (16 bytes in total). Example: 2001:db8:1f11:08d3:290:27ff:0370:2093 WinCC Basic V13.0 System Manual, 02/2014 UserName STRING[254] Mail server login name PassWord STRING[254] Mail server password From EMAIL_ADDR E-mail sender address, which is defined using the following two STRING parameters. For example: "myname@mymailserver.com". LocalPartPlusAtSi STRING[64] gn Local part of sender address, including @ sign. Example: "myname@". FullQualifiedDom ainName Fully Qualified Domain Name ( FQDN for short) of the mail server. Example: "mymailserver.com". STRING[254] 3119 Programming the PLC 9.7 References Table 9-99 Tmail_FQDN: Addressing the mail server by FQDN Parameter Data type Tmail_v6 Struct Description Tmail_FQDN LADDR Hardware identifier of the interface ID CONN_OUC Connection ID ConnectionType BYTE Connection type. Select 16#22 as the connection type for FQDN. ActiveEstablished BOOL Status bit. Set to "1" once the connection is established. CertIndex BYTE =0: SMTP used (Simple Mail Transfer Protocol). SMTP must be used if the e-mail is being sent via the interface of an S7-1500 CPU. 0: SMTPS used to secure the connection before it is established (with CPs/CMs). You use the CertIndex parameter to specify the certificate to be used (see "Project navigation" > "Global security settings" > "Certificate manager"). WatchDogTime TIME Execution watchdog. Use this parameter to define the maximum execution time for the send operation. Note: Connection establishment can take longer (approx. one minute) if the connection is slow. When you specify the WATCH_DOG_TIME parameter, remember to allow for the time required to establish the connection. The connection is terminated once the specified time has elapsed. MailServerAddress STRING[254] FQDN (Fully Qualified Domain Name) of the mail server. The mail server is addressed using the fully qualified domain name. Example: "www.mymailserver.com.". UserName STRING[254] Mail server login name PassWord STRING[254] Mail server password From Struct E-mail sender address, which is defined using the following two STRING parameters. For example: "myname@mymailserver.com". LocalPartPlusAtSi STRING[64] gn Local part of sender address, including @ sign. Example: "myname@". FullQualifiedDom ainName Fully Qualified Domain Name ( FQDN for short) of the mail server. Example: "mymailserver.com". STRING[254] DONE, BUSY and ERROR parameters Description The output parameters DONE, BUSY and ERROR are each displayed for only one cycle if the status of the BUSY output parameter changes from "1" to "0". The following table shows the relationship between DONE, BUSY, and ERROR. Using this table, you can determine the current status of the instruction "TMAIL_C and when the sending of the e-mail is complete. 3120 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References DONE BUSY ERRO R Description 0 1 0 The job is being processed. 1 0 0 Job successfully completed. 0 0 1 The job ended with an error. The cause of the error can be found in the STATUS (Page 3121) parameter. 0 0 0 The "TMAIL_C" instruction was not assigned a (new) job. STATUS parameter Description The following table shows the return values of "TMAIL_C" at the STATUS parameter: Return value Explanation Notes STATUS* (W#16#...): 0000 The processing of "TMAIL_C" was completed without errors. Error-free completion of "TMAIL_C" does not mean that the e-mail sent will necessarily arrive. Incorrectly entering the recipient addresses does not generate a status error of the "TMAIL_C" instruction. In this case, there is no guarantee that the e-mail will be sent to other recipients, even if these were entered correctly. WinCC Basic V13.0 System Manual, 02/2014 7001 "TMAIL_C" is active (BUSY = 1). First call: Job triggered. 7002 "TMAIL_C" is active (BUSY = 1). Intermediate call: Job already active. 8xxx The processing of "TMAIL_C" was completed with an error code of the communication instructions called internally. For detailed information, please refer to the STATUS parameter descriptions for the "TCON (Page 3127)", "TDISCON (Page 3132)", "TSEND (Page 3137)" and "TRCV (Page 3140)" communication instructions. 8010 Error during connection establishment You will find further information on evaluation in the SFB_STATUS parameter of the instance data block. The error code displayed at the SFB_STATUS parameter is explained in the STATUS parameter description for the "TCON (Page 3127)" instruction. 8011 Error sending the data You will find further information on evaluation in the SFB_STATUS parameter of the instance data block. The error code displayed at the SFB_STATUS parameter is explained in the STATUS parameter description for the "TSEND (Page 3137)" instruction. 3121 Programming the PLC 9.7 References Return value Explanation Notes STATUS* (W#16#...): 3122 8012 Error receiving the data You will find further information on evaluation in the SFB_STATUS parameter of the instance data block. The error code displayed at the SFB_STATUS parameter is explained in the STATUS parameter description for the "TRCV (Page 3140)" instruction. 8013 Error during connection establishment You will find further information on evaluation in the SFB_STATUS parameter of the instance data block. The error code displayed at the SFB_STATUS parameter is explained in the STATUS parameter description for the TCON (Page 3127)" and "TDISCON (Page 3132)" instructions. 8014 Establishment of a connection is not possible. You may have entered an incorrect mail server IP address (MailServerAddress (Page 3118)) or too short a time span (WatchDogTime (Page 3118)) for connection establishment. It is also possible that the CPU has no connection to the network or that the CPU configuration is incorrect. 8015 Incorrect data type for MAIL_ADDR_PARAM The only valid data types are the system data types (structures) Tmail_v4, Tmail_v6 and TMail_FQDN. 8016 Incorrect data type for the ATTACHMENT parameter The only valid data types are ArrayOfByte, ArrayOfWord and ArrayOfDWord. 8017 Incorrect data length for the ATTACHMENT parameter Data length must be <= 65534 bytes. 8401 No channels available. Possible cause: There is already an e-mail connection via the CP. A second connection cannot be established in parallel. Specific error for CP 1543 8403 A TCP/IP connection to the mail server was not possible. Specific error for CP 1543 8405 Server has denied login request. Specific error for CP 1543 8406 SMTP client has detected an internal SSL error or a problem with the certificate structure. Specific error for CP 1543 8407 Request to use SSL denied. Specific error for CP 1543 8408 Client unable to identify socket for establishing a TCP/IP connection to the mail server. Specific error for CP 1543 8409 Writing via the connection not Specific error for CP 1543 possible. Possible cause: The communication partner has reset the connection or the connection has been lost. WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Return value Explanation Notes STATUS* (W#16#...): 8410 Reading via the connection not Specific error for CP 1543 possible. Possible cause: The communication partner has reset the connection or the connection has been lost. 8411 E-mail could not be sent. Cause: Insufficient memory space to execute the send operation. Specific error for CP 1543 8412 DNS server configured was unable to resolve the specified domain name. Specific error for CP 1543 8413 An internal error in the DNS subsystem prevented domain name resolution. Specific error for CP 1543 8414 Empty character string entered as domain name. Specific error for CP 1543 8415 An internal error has occurred in the Specific error for CP 1543 cURL module. Execution was stopped. 8416 An internal error has occurred in the SMTP module. Execution was stopped. Specific error for CP 1543 8417 Request to SMTP on a channel already in use or invalid channel ID. Execution was stopped. Specific error for CP 1543 8418 E-mail send job aborted. Possible causes: Execution time exceeded (WatchDogTime parameter) or CP transition from start to stop. Specific error for CP 1543 8419 Channel interrupted and cannot be used before the connection is closed. Specific error for CP 1543 8420 Server certificate string could not be verified with CP root certificate. Specific error for CP 1543 8421 Internal error occurred. Execution was stopped. Specific error for CP 1543 82xx, 84xx, or 85xx The error message originates from the mail server and corresponds, except for the "8", to the error number of the SMTP protocol. You will find more detailed information on the SMTP error code and other error codes in the SMTP protocol on the Internet or in the error documentation of the mail server. You can also view the most recent error message from the mail server in your instance DB in the BUFFER1 parameter. You will find the last data sent by the "TMAIL_C" instruction under DATEN in the instance DB. The following lines list several error codes that can occur. WinCC Basic V13.0 System Manual, 02/2014 8450 Action not executed: Mailbox not available/cannot be reached Try again later. 8451 Action aborted: Local processing error Try again later. 3123 Programming the PLC 9.7 References Return value Explanation Notes STATUS* (W#16#...): 8500 Syntax error: Error not recognized. This also includes the error when a command string is too long. This can also occur when the e-mail server does not support the LOGIN authentication procedure. Check the parameters of "TMAIL_C". Try to send an e-mail without authentication. To do this, replace the content of the UserName parameter with an empty string. If no user name is specified, the LOGIN authentication procedure is not used. 8501 Syntax error: Incorrect input at a parameter Possible cause: Incorrect address at the TO_S or CC parameter (see also: TO_S and CC parameters (Page 3117)). 8502 Command unknown or not implemented Check your entries, in particular the FROM parameter. It may be incomplete and you may have forgotten the "@" or "." (see also: TO_S and CC parameters (Page 3117)). 8504 Command parameters not implemented Check your entries, in particular the FROM parameter. It may be incomplete and you may have forgotten the "@" or "." (see also: TO_S and CC parameters (Page 3117)). 8535 SMTP authentication incomplete You have possibly entered an incorrect user name or incorrect password. 8550 Mail server cannot be reached. You have no access rights. You may have entered an incorrect user name or password, or the mail server may not support your login. Another cause of error could be a mistake in the domain name after the "@" or a missing "." at the TO_S, CC and FROM parameters (see also: TO_S and CC parameters (Page 3117)). 8552 Action aborted: Assigned memory size has been exceeded Try again later. 8554 Transfer failed Try again later. * The error codes can be displayed as integer or hexadecimal values in the program editor. For additional information on toggling display formats, refer to "See also". Other TCON: Establishing a communication connection TCON: Establish communication connection Description You use the "TCON" instruction to set up and establish a communication connection. Once the connection has been set up and established, it is automatically maintained and monitored by the CPU. "TCON" is executed asynchronously. The connection data specified for the CONNECT and ID parameters are used to set up the communication connection. To establish the connection, a rising edge must be detected at the 3124 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References REQ parameter. Once the connection is successfully established, the DONE parameter is set to "1". Number of possible connections For information on the number of possible communication connections, refer to the technical specifications for your CPU. Connection with TCP and ISO-on-TCP Both communication partners call the "TCON" instruction to set up and establish the communication connection. During parameter assignment, you specify which partner is the active communication end point and which is the passive one. If the connection aborts, for example due to a line break or due to the remote communication partner, the active partner attempts to reestablish the configured connection. You do not have to call "TCON" again. This applies only if "TCON" has been executed successfully once (DONE = 1). An existing connection is terminated and the connection set up is removed when the "TDISCON (Page 3132)" instruction is executed or when the CPU changes to STOP mode. To set up and establish the connection again, you will need to execute "TCON" again. Parameters The following table shows the parameters of the "TCON" instruction: Parameter Declaration Data type REQ Input BOOL I, Q, M, D, L or constant Starts the job to establish the connection specified in the ID upon a rising edge. ID Input CONN_OUC I, Q, M, D, L or constant Reference to the assigned connection. D Pointer to the connection description CONNECT InOut TCON_Param Memory area Description Range of values: W#16#0001 to W#16#0FFF See also: Auto-Hotspot DONE Output BOOL I, Q, M, D, L Status parameter with the following values: 0: Job not yet started or still in progress 1: Job completed without error BUSY Output BOOL I, Q, M, D, L Status parameter with the following values: 0: Job not yet started or already completed 1: Job not yet completed. A new job cannot be started ERROR Output BOOL I, Q, M, D, L Status parameter ERROR: 0: No error 1: Error occurred STATUS Output WORD I, Q, M, D, L Status of the instruction You can find additional information on valid data types under "Overview of the valid data types (Page 1204)". WinCC Basic V13.0 System Manual, 02/2014 3125 Programming the PLC 9.7 References BUSY, DONE and ERROR parameters You can check the status of the job with the BUSY, DONE, ERROR and STATUS parameters. The BUSY parameter indicates the processing status. You use the DONE parameter to check whether or not a job has been executed successfully. The ERROR parameter is set when errors occurred during execution of "TCON". The error information is output at the STATUS parameter. The following table shows the relationship between the BUSY, DONE and ERROR parameters: BUSY DONE ERROR Description 1 0 0 The job is being processed. 0 1 0 The job was completed successfully. 0 0 1 The job ended with an error. The cause of the error is output at the STATUS parameter. 0 0 0 No new job was assigned. ERROR and STATUS parameters ERROR STATUS* (W#16#...) Explanation 0 0000 Connection successfully established. 0 7000 No job processing active 0 7001 Start job execution, establish connection. 0 7002 Connection is being established (REQ irrelevant). 1 8085 Connection ID (ID parameter) is already being used by a configured connection. 1 8086 The ID parameter is outside the valid range. 1 8087 Maximum number of connections reached; no additional connection possible 1 8089 The CONNECT parameter does not point to a data block. 1 809A The CONNECT parameter points to a field that does not correspond to the length of the connection description. 1 809B The element InterfaceId within the TCON_xxx structure does not reference a hardware identifier of a CPU or CM/CP interface or has the value "0". 1 80A0 Group error for error codes W#16#80A1 and W#16#80A2. 1 80A2 Local or remote port is being used by the system. 1 80A3 Attempt being made to re-establish an existing connection. 1 80A4 IP address of the remote endpoint of the connection is invalid, in other words, it matches the IP address of the local partner. 1 80A5 Connection ID is already in use. 1 80A7 Communication error: You executed "TDISCON (Page 3132)" before "TCON" had completed. 1 80B2 The CONNECT parameter points to a data block that was generated with the attribute "Only store in load memory". 3126 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References ERROR STATUS* (W#16#...) Explanation 1 80B4 You have violated one or more of the following conditions for passive connection establishment with the ISO-on-TCP protocol variant (connection_type = B#16#12): local_tsap_id_len >= B#16#02 local_tsap_id[1] = B#16#E0 With local_tsap_id_len >= B#16#03, local_tsap_id[1] is an ASCII character. local_tsap_id[1] is an ASCII character and local_tsap_id_len >= B#16#03. 1 80B5 Only passive connection establishment is permitted for connection type 13 = UDP. 1 80B6 Parameter assignment error at the connection_type parameter of the SDT TCON_Param. 1 80B7 Error in one of the following parameters of the data block for connection description: block_length, local_tsap_id_len, rem_subnet_id_len, rem_staddr_len, rem_tsap_id_len, next_staddr_len. 1 80B8 Connection description of the structure element ID and the block parameter ID are not identical. 1 80C3 All connection resources are in use. 1 80C4 Temporary communication error: The connection cannot be established at this time. The interface is currently receiving new parameters. The configured connection is currently being removed by a "TDISCON (Page 3132)" instruction. * The error codes can be displayed as integer or hexadecimal values in the program editor. For additional information on toggling display formats, refer to "See also". TCON: Establish communication connection Description You use the "TCON" instruction to set up and establish a communication connection. Once the connection has been set up and established, it is automatically maintained and monitored by the CPU. "TCON" is executed asynchronously. The connection data specified for the CONNECT and ID parameters are used to set up the communication connection. At the CONNECT parameter, if possible, only use the predefined structures as created by the connection parameter assignment in the Inspector window of the program editor. If the CONNECT parameter is not interconnected with a structure listed in the parameter table or if the structure includes an error, the error code 8089 is output at the STATUS parameter. To establish the connection, a rising edge must be detected at the REQ parameter. Once the connection is successfully established, the DONE parameter is set to "1". The instruction "TCON" V3.0 can also be used with CPU S7-1200, Version 4.0 or later. Number of possible connections For information on the number of possible communication connections, refer to the technical specifications for your CPU. WinCC Basic V13.0 System Manual, 02/2014 3127 Programming the PLC 9.7 References Connection with TCP and ISO-on-TCP Both communication partners call the "TCON" instruction to set up and establish the communication connection. During parameter assignment, you specify which partner is the active communication end point and which is the passive one. If the connection aborts, for example due to a line break or due to the remote communication partner, the active partner attempts to reestablish the configured connection. You do not have to call "TCON" again. This applies only if "TCON" has been executed successfully once (DONE = 1). An existing connection is terminated and the connection set up is removed when the "TDISCON (Page 3132)" instruction is executed or when the CPU changes to STOP mode. To set up and establish the connection again, you will need to execute "TCON" again. Parameters The following table shows the parameters of the "TCON" instruction: Parameter Declaration Data type Memory area Description REQ Input BOOL I, Q, M, D, L or constant Starts the job to establish the connection specified on a rising edge. ID Input CONN_OUC I, Q, M, D, L or constant Reference to the assigned connection. D Pointer to the connection description CONNECT InOut VARIANT Range of values: W#16#0001 to W#16#0FFF For TCP or UDP, use the structure TCON_IP_v4 For description, refer to: Auto-Hotspot For ISO-on-TCP, use the structure TCON_IP_RFC For description, refer to: Auto-Hotspot For ISO, use the structure TCON_ISOnative (only for CP1543-1) For description, refer to: "Structure of the connection description according to TCON_ISOnative" DONE Output BOOL I, Q, M, D, L Status parameter with the following values: 0: Job not yet started or still in progress 1: Job completed without error BUSY Output BOOL I, Q, M, D, L Status parameter with the following values: 0: Job not yet started or already completed 1: Job not yet completed. A new job cannot be started ERROR Output BOOL I, Q, M, D, L Status parameter ERROR: 0: No error 1: Error occurred STATUS Output WORD I, Q, M, D, L Status of the instruction You can find additional information on valid data types under "Overview of the valid data types (Page 1204)". 3128 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References BUSY, DONE and ERROR parameters You can check the status of the job with the BUSY, DONE, ERROR and STATUS parameters. The BUSY parameter indicates the processing status. You use the DONE parameter to check whether or not a job has been executed successfully. The ERROR parameter is set when errors occurred during execution of "TCON". The error information is output at the STATUS parameter. The instruction "TCON" generates an error message in version 3.0 if an active connection establishment to a remote partner fails. Create a rising edge at the REQ parameter to establish a connection once again. The following table shows the relationship between the BUSY, DONE and ERROR parameters: BUSY DONE ERROR Description 1 0 0 The job is being processed. 0 1 0 The job was completed successfully. 0 0 1 The job ended with an error. The cause of the error is output at the STATUS parameter. 0 0 0 No new job was assigned. Structure of the connection description according to TCON_ISOnative A connection description DB with a structure according to TCON_ISOnative is used to assign the communication connection parameters for ISO. The fixed data structure of the TCON_ISOnative contains all parameters that are required to establish the connection. Byte Parameter Data type Start value Description 0... 1 InterfaceId HW_ANY 64 Hardware identifier of the local interface (value range: 0 to 65535). 2... 3 ID CONN_OUC 1 Reference to this connection (unique ID in the value range: 1 to 4095). 4 ConnectionType BYTE 16#16 Connection type: ISO 5 ActiveEstablished BOOL TRUE ID for the manner in which the connection is established: FALSE: Passive connection establishment TRUE: Active connection establishment 8... 13 RemoteMacAddress ARRAY [1..6] of BYTE - MAC address of the partner end point, for example, for 00-74-41-FD-AE-84: MacAddr[1] = 00 MacAddr[2] = 74 MacAddr[3] = 41 MacAddr[4] = FD MacAddr[5] = AE MacAddr[6] = 84 WinCC Basic V13.0 System Manual, 02/2014 3129 Programming the PLC 9.7 References Byte Parameter Data type Start value Description 14 .. LocalMacAddress . 19 ARRAY [1..6] of BYTE - MAC address of the local end point, for example, for 00-74-41-FD-AE-84: MacAddr[1] = 00 MacAddr[2] = 74 MacAddr[3] = 41 MacAddr[4] = FD MacAddr[5] = AE MacAddr[6] = 84 20 .. RemoteTSelector . 53 Struct - TSelector of the remote connection partner: Bytes 20 to 21 = TSelLength Bytes 22 to 53: = TSel[1-32] TSelLength UINT - Value range from 0 to 32 TSel ARRAY [1..32] of BYTE - Value range in each case 0 to 255 in bytes Struct - TSelector of the remote connection partner: 54 .. LocalTSelector . 87 Bytes 20 to 21 = TSelLength Bytes 22 to 53: = TSel[1-32] TSelLength UINT TSel ARRAY [1..32] of BYTE - Value range in each case 0 to 255 in bytes UINT - Duration until connection attempt is repeated in seconds. 90 .. DataRetransmitionTim . 91 e UINT 100 ms Duration until data transfer is repeated in milliseconds. 92 .. MaxRetransmitionCou . 93 nt UINT - Maximum number of repetitions. 94 .. InactivityTime . 95 UINT - in seconds 96 .. WindowTime . 97 UINT 88 ... 89 CrRetransmitionTime Value range from 0 to 32 in seconds ERROR and STATUS parameters ERROR STATUS* (W#16#...) Explanation 0 0000 Connection successfully established. 0 7000 No job processing active 0 7001 Start job execution, establish connection. 0 7002 Connection is being established (REQ irrelevant). 1 8085 Connection ID (ID parameter) is already being used by a configured connection. 1 8086 The ID parameter is outside the valid range. 1 8087 Maximum number of connections reached; no additional connection possible 1 8089 The CONNECT parameter does not point to a connection description or the connection description was created manually. 3130 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References ERROR STATUS* (W#16#...) Explanation 1 809A The structure at the CONNECT parameter is not supported or the length is invalid. 1 809B The element InterfaceId within the TCON_xxx structure does not reference a hardware identifier of a CPU or CM/CP interface or has the value "0". 1 80A2 Local or remote port is being used by the system. The following ports are reserved locally: 20, 21, 80, 102, 135, 161, 162, 443, 34962, 34963, 34964 as well as the area 49152 to 65535. 1 80A3 ID is used by a connection created by the user program, which uses the same connection description at the CONNECT parameter. 1 80A4 IP address of the remote endpoint of the connection is invalid or it corresponds to the IP address of the local partner. 1 80A7 Communication error: You executed "TDISCON (Page 3132)" before "TCON" had completed. 1 80B4 Only with TCON_IP_RFC: The local T selector was not specified or the first byte does not contain the value 0x0E (only with a length of T selector = 2) or the local T selector starts with "SIMATIC-". 1 80B5 Only passive connection establishment is permitted for connection type 13 = UDP (parameter ActiveEstablished of the structure TCON_IP_v4 / TCON_PARAM has the value TRUE). 1 80B6 Parameter assignment error in the ConnectionType parameter of the data block for connection description. Only valid with TCON_IP_v4: 0x11, 0x0B and 0x13. Only valid with TCON_IP_RFC: 0x0C and 0x12 1 80B7 With TCON_IP_v4: TCP (active connection establishment): Remote port is "0". TCP (passive connection establishment): Local port is "0". UDP: Local port is "0". With TCON_IP_RFC: Local (LocalTSelector) or remote (RemoteTSelector) T selector was specified with a length of more than 32 bytes. For TSelLength of the T selector (local or remote), a length greater than 32 was entered. Error in the length of the IP address of the specific connection partner. 1 80B8 Parameter ID in the local connection description (structure at CONNECT parameter) and parameter ID of the instruction are different. 1 80C3 All connection resources are in use. 1 80C4 Temporary communication error: The connection cannot be established at this time. The interface is currently receiving new parameters. The configured connection is currently being removed by a "TDISCON (Page 3132)" instruction. 1 80C5 The connection partner refuses to establish the connection, has terminated the connection or actively ended it. 1 80C6 The connection partner cannot be reached (network error). 1 80C7 Execution timeout. 1 80C8 Value at the ID parameter is already being used by a connection that was created using the user program. The connection uses the identical ID, but different connection settings at the parameter CONNECT. 1 80C9 Validation of the connection partner failed. The connection partner that wants to establish the connection does not match the defined partner of the structure at the CONNECT parameter. WinCC Basic V13.0 System Manual, 02/2014 3131 Programming the PLC 9.7 References ERROR STATUS* (W#16#...) Explanation 1 80CE The IP address of the local interface is 0.0.0.0. * The error codes can be displayed as integer or hexadecimal values in the program editor. For additional information on toggling display formats, refer to "See also". TDISCON: Terminate communication connection Description The "TDISCON" instruction terminates a communications connection from the CPU to a connection partner. Functional description "The TDISCON" instruction works asynchronously, which means its job processing extends over multiple calls. You start the job for terminating a connection by calling the "TDISCON" instruction with REQ = 1. After "TDISCON" has been successfully executed, the ID specified for "TCON" is no longer valid and cannot be used for sending or receiving. The job status is indicated by the output parameters BUSY and STATUS. Here, STATUS corresponds to the output parameter RET_VAL of the asynchronous instructions (see also: Meaning of the parameters REQ, RET_VAL and BUSY with asynchronous instructions (Page 1736)). The following table shows the relationship between BUSY, DONE and ERROR. Using this table, you can recognize the current status of "TDISCON" or when the establishment of the connection is completed. BUSY DONE ERROR Description 1 0 0 The job is being processed. 0 1 0 Job successfully completed. 0 0 1 The job ended with an error. The cause of the error can be found in the STATUS parameter. 0 0 0 The instruction was not assigned a (new) job. 3132 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameters The following table shows the parameters of the instruction "TDISCON": Parameter Declaration Data type Memory area S7-1200 S7-1500 I, Q, M, D, L or constant REQ Input BOOL I, Q, M, D, L or constant ID Input CONN_OU C (WORD) D, L or constant I, Q, M, D, L or constant Description Control parameter REQUEST starts the job for terminating the connection specified by ID. The job starts on a rising edge. Reference to the connection to be terminated (connection ID) Range of values: W#16#0001 to W#16#0FFF DONE Output BOOL I, Q, M, D, L I, Q, M, D, L Status parameter: 0: Job not yet started or still executing. 1: Job executed without errors BUSY Output BOOL I, Q, M, D, L I, Q, M, D, L Status parameter: BUSY = 1: The job is not yet completed. BUSY = 0: The job is completed or has not started yet. ERROR Output BOOL I, Q, M, D, L I, Q, M, D, L Status parameter: ERROR=0: No error. ERROR=1: Error occurred during processing. STATUS supplies detailed information on the type of error STATUS Output WORD I, Q, M, D, L I, Q, M, D, L Status parameter: Error information (see "Parameters ERROR and STATUS") You will find more detailed information on valid data types in "Overview of the valid data types (Page 1204)". Parameters ERROR and STATUS ERROR STATUS* (W#16#...) Explanation 0 0000 Connection terminated successfully. 0 7000 No job processing active. 0 7001 Start of job processing, connection being terminated. 0 7002 Intermediate call (REQ irrelevant), connection being terminated. 1 8086 The ID parameter is not in the permitted value range. 1 80A3 Attempt is being made to terminate a non-existent connection or the connection is already terminated. WinCC Basic V13.0 System Manual, 02/2014 3133 Programming the PLC 9.7 References ERROR STATUS* (W#16#...) Explanation 1 80C4 Temporary communication error: New parameters are being assigned to the interface or the connection is currently being established. * The error codes can be displayed as integer or hexadecimal values in the program editor. For additional information on toggling display formats, refer to "See also". TSEND: Send data via communication connection TSEND: Send data via communication connection Description The following description of the "TSEND" instruction is valid for the CPU S7-1200 to version 3.0. You use the "TSEND" instruction to send data over an existing communication connection. "TSEND" is executed asynchronously. You specify the send area with the DATA parameter. This includes the address and the length of the data to be sent. All data types except BOOL and Array of BOOL can be used for the data to be sent. The send job is executed when a rising edge is detected at the REQ parameter. With the LEN parameter, you specify the maximum number of bytes sent with a send job. When data is transferred with TCP (streaming protocol), the "TSEND" instruction provides no information about the length of the data sent to "TRCV (Page 3140)". When data is transferred with ISO-on-TCP (message-oriented protocol), the length of the data sent is communicated to "TRCV (Page 3140)". The amount of data sent with "TSEND" as packet must also be received again at the receiving end ("TRCV (Page 3140)"): - If the receive buffer is too small for the sent data, an error occurs at the receiving end. - If the receive buffer is sufficiently large, "TRCV" returns with DONE=1 as soon as the data packet is received. The data to be sent must not be edited until the send job is completed. If the send job executes successfully, the DONE parameter is set to "1". Signal state "1" at the DONE parameter is not confirmation that the data sent has already been read by the communication partner. Parameters The following table shows the parameters of the "TSEND" instruction: Parameter Declaration Data type Memory area Description REQ Input BOOL I, Q, M, D, L or constant Starts the send job on a rising edge. ID Input CONN_OUC I, Q, M, D, L or constant Reference to the connection established with "TCON". Range of values: W#16#0001 to W#16#0FFF 3134 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameter Declaration Data type Memory area Description LEN Input UINT I, Q, M, D, L or constant Maximum number of bytes to be sent with the job. DATA InOut VARIANT I, Q, M, D Pointer to the send area containing the address and the length of the data to be sent. The address references: The process image of the inputs The process image of the outputs A bit memory A data block DONE Output BOOL I, Q, M, D, L Status parameter with the following values: 0: Job not yet started or still in progress 1: Job completed without error BUSY Output BOOL I, Q, M, D, L Status parameter with the following values: 0: Job not yet started or already completed 1: Job not yet completed. A new job cannot be started. ERROR Output BOOL I, Q, M, D, L Status parameter with the following values: 0: No error 1: Error occurred STATUS Output WORD I, Q, M, D, L Status of the instruction You can find additional information on valid data types under "Overview of the valid data types (Page 1204)". LEN and DATA parameters With LEN = 0 , all the data specified with the DATA parameter is sent. If the number of bytes at the LEN parameter is larger than the length of the data to be sent that was defined with the DATA parameter, the error code 8088 is output at the STATUS parameter (see description of the STATUS parameter below). If a structure (Struct) is referenced via the DATA parameter, LEN can be shorter than the structure. In this case, only the data up to the length of the LEN parameter is transferred. With data types STRING and WSTRING, all data is transferred if the parameter LEN = 0. When LEN > 0, the length must be at least the maximum number of bytes plus two additional bytes which contain the length information. You can find more detailed information on the structure of the data types in: "Overview of the valid data types (Page 1204)". The maximum number of bytes that can be transmitted is 65534. When you use structured tags from optimized DBs, the address of the structured tag should be interconnected at the DATA parameter and the parameter LEN = 0. This guarantees type-safe transmission of the entire structure if the same structure is used at the receiving end. WinCC Basic V13.0 System Manual, 02/2014 3135 Programming the PLC 9.7 References BUSY, DONE and ERROR parameters You can check the status of the job with the BUSY, DONE, ERROR and STATUS parameters. The BUSY parameter indicates the processing status. With the DONE parameter, you can check whether or not a job executed successfully. The ERROR parameter is set when errors occurred during execution of "TSEND". The error information is output at the STATUS parameter. The following table shows the relationship between the BUSY, DONE and ERROR parameters: BUSY DONE ERROR Description 1 0 0 The job is being processed. 0 1 0 The job was completed successfully. 0 0 1 The job ended with an error. The cause of the error is specified in the STATUS parameter. 0 0 0 No new job was assigned. Note Because "TSEND" is executed asynchronously, you must keep the data in the send area consistent until the DONE parameter or the ERROR parameter changes to the value "1". ERROR and STATUS parameters ERROR STATUS* (W#16#...) Description 0 0000 Send job completed without error. 0 7000 No job processing active. 0 7001 Start of job execution, data is being sent. When processing this job, the operating system accesses the data in the DATA send area. 0 7002 Job executing (REQ irrelevant). When processing this job, the operating system accesses the data in the DATA send area. 1 8085 The LEN parameter is greater than the highest permitted value (65536). DATA and LEN parameters both have the value "0". 1 8086 The ID parameter is outside the permitted address range (1..0xFFF). 1 8088 The LEN parameter is greater than the area specified in DATA. 1 80A1 Communication error: The specified connection has not yet been established. The specified connection is being terminated. Transfer via this connection is not possible. The interface is being re-initialized. 1 80B3 The protocol variant (ConnectionType parameter in the connection description) is set to UDP. Use the instruction "TUSEND" with a UDP connection. 1 80C3 A block with this ID is already being processed in a different priority group. Internal lack of resources. 3136 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References ERROR STATUS* (W#16#...) Description 1 80C4 Temporary communication error: The connection cannot be established to the partner at this time. The interface is receiving new parameter settings or the connection is being established. 1 80C5 Connection terminated by the communication partner. 1 80C6 Network error. Communication partner cannot be reached. 1 80C7 Execution timeout. * The error codes can be displayed as integer or hexadecimal values in the program editor. For additional information on toggling display formats, refer to "See also". TSEND: Send data via communication connection Description The following description of the "TSEND" instruction is valid for the CPU S7-1500 and S7-1200 V4.0. You use the "TSEND" instruction to send data over an existing communication connection. "TSEND" is executed asynchronously. You specify the send area with the DATA parameter. This includes the address and the length of the data to be sent. All data types except BOOL and Array of BOOL can be used for the data to be sent. The send job is executed when a rising edge is detected at the REQ parameter. With the LEN parameter, you specify the maximum number of bytes sent with a send job. When data is transferred with TCP (streaming protocol), the "TSEND" instruction provides no information about the length of the data sent to "TRCV (Page 3140)". When data is transferred with ISO-on-TCP (message-oriented protocol), the length of the data sent is communicated to "TRCV (Page 3140)". The amount of data sent with "TSEND" as packet must also be received again at the receiving end ("TRCV (Page 3140)"): - If the receive buffer is too small for the sent data, an error occurs at the receiving end. - If the receive buffer is sufficiently large, "TRCV" returns with DONE=1 as soon as the data packet is received. The data to be sent must not be edited until the send job is completed. If the send job executes successfully, the DONE parameter is set to "1". Signal state "1" at the DONE parameter is not confirmation that the data sent has already been read by the communication partner. WinCC Basic V13.0 System Manual, 02/2014 3137 Programming the PLC 9.7 References Parameters The following table shows the parameters of the "TSEND" instruction: Parameter Declaration Data type Memory area Description REQ Input BOOL I, Q, M, D, L or constant Starts the send job on a rising edge. ID Input CONN_OUC I, Q, M, D, L or constant Reference to the connection established with "TCON". Range of values: W#16#0001 to W#16#0FFF LEN Input UDINT I, Q, M, D, L or constant Maximum number of bytes to be sent with the job. DATA InOut VARIANT I, Q, M, D Pointer to the send area containing the address and the length of the data to be sent. The address references: The process image of the inputs The process image of the outputs A bit memory A data block DONE Output BOOL I, Q, M, D, L Status parameter with the following values: 0: Job not yet started or still in progress 1: Job completed without error BUSY Output BOOL I, Q, M, D, L Status parameter with the following values: 0: Job not yet started or already completed 1: Job not yet completed. A new job cannot be started. ERROR Output BOOL I, Q, M, D, L Status parameter with the following values: 0: No error 1: Error occurred STATUS Output WORD I, Q, M, D, L Status of the instruction You can find additional information on valid data types under "Overview of the valid data types (Page 1204)". LEN and DATA parameters With LEN = 0 , all the data specified with the DATA parameter is sent. If the number of bytes at the LEN parameter is larger than the length of the data to be sent that was defined with the DATA parameter, the error code 8088 is output at the STATUS parameter (see description of the STATUS parameter below). If a structure (Struct) is referenced via the DATA parameter, LEN can be shorter than the structure. In this case, only the data up to the length of the LEN parameter is transferred. With data types STRING and WSTRING, all data is transferred if the parameter LEN = 0. When LEN > 0, the length must be at least the maximum number of bytes plus two additional bytes which contain the length information. You can find more detailed information on the structure of the data types in: "Overview of the valid data types (Page 1204)". 3138 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References The maximum number of bytes that can be transmitted depends on the device. When you use structured tags from optimized DBs, the address of the structured tag should be interconnected at the DATA parameter and the parameter LEN = 0. This guarantees type-safe transmission of the entire structure if the same structure is used at the receiving end. BUSY, DONE and ERROR parameters You can check the status of the job with the BUSY, DONE, ERROR and STATUS parameters. The BUSY parameter indicates the processing status. With the DONE parameter, you can check whether or not a job executed successfully. The ERROR parameter is set when errors occurred during execution of "TSEND". The error information is output at the STATUS parameter. The following table shows the relationship between the BUSY, DONE and ERROR parameters: BUSY DONE ERROR Description 1 0 0 The job is being processed. 0 1 0 The job was completed successfully. 0 0 1 The job ended with an error. The cause of the error is specified in the STATUS parameter. 0 0 0 No new job was assigned. Note Because "TSEND" is executed asynchronously, you must keep the data in the send area consistent until the DONE parameter or the ERROR parameter changes to the value "1". ERROR and STATUS parameters ERROR STATUS* (W#16#...) Description 0 0000 Send job completed without error. 0 7000 No job processing active. 0 7001 Start of job execution, data is being sent. 0 7002 1 8085 1 8086 The ID parameter is outside the permitted address range (1..0xFFF). 1 8088 The LEN parameter is greater than the area specified in DATA. 1 80A1 Communication error: When processing this job, the operating system accesses the data in the DATA send area. Job executing (REQ irrelevant). When processing this job, the operating system accesses the data in the DATA send area. The LEN parameter is greater than the highest permitted value (65536). DATA and LEN parameters both have the value "0". The specified connection has not yet been established. The specified connection is being terminated. Transfer via this connection is not possible. The interface is being re-initialized. WinCC Basic V13.0 System Manual, 02/2014 3139 Programming the PLC 9.7 References ERROR STATUS* (W#16#...) Description 1 80B3 The protocol variant (ConnectionType parameter in the connection description) is set to UDP. Use the instruction "TUSEND" with a UDP connection. 1 80C3 A block with this ID is already being processed in a different priority group. Internal lack of resources. 1 80C4 Temporary communication error: The connection cannot be established to the partner at this time. The interface is receiving new parameter settings or the connection is being established. 1 80C5 Connection terminated by the communication partner. 1 80C6 Network error. Communication partner cannot be reached. 1 80C7 Execution timeout. * The error codes can be displayed as integer or hexadecimal values in the program editor. For additional information on toggling display formats, refer to "See also". TRCV: Receive data via communication connection TRCV: Receive data via communication connection Description The following description of the "TRCV" instruction is valid for the CPU S7-1200 up to version 3.0. You use the "TRCV" instruction to receive data over an existing communication connection. "TRCV" is executed asynchronously. Receipt of data is enabled when the EN_R parameter is set to the value "1". The received data is entered in a receive area. You specify the length of the receive area either with the LEN parameter (if LEN <> 0) or with the length information of the DATA parameter (if LEN = 0), depending on the protocol variant being used. While data is being received, you cannot make changes to the DATA parameter or the defined receive area to ensure consistency of the received data. After successful receipt of data, the NDR parameter is set to the value "1". You can query the amount of data actually received at the RCVD_LEN parameter. 3140 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Receive modes of "TRCV" The following table shows how the received data is entered in the receive area. Protocol variant Availability of data in the receive area connection_type* parameter of the connection description LEN parameter TCP The data is immediately available. Hexadecimal value: B#16#11 0 (Ad-hoc mode) Integer value: 17 TCP (Receipt of data with specified length) ISO on TCP (Message-oriented data transfer) The data is available as soon as the data length specified at the LEN parameter has been fully received. Hexadecimal value: B#16#11 1 to 8192 The data is available as soon as the data length specified at the LEN parameter has been fully received. Hexadecimal value: B#16#12 1 to 1452, if a CP is used. Integer value: 18 1 to 8192, if no CP is used. Integer value: 17 * See "Auto-Hotspot". TCP (Ad-hoc mode) The ad-hoc mode is only available with the TCP protocol variant. You use the ad-hoc mode to receive data with dynamic length with the "TRCV" instruction. You set ad-hoc mode by assigning the value "0" to the LEN parameter. All data types can be used for data blocks with standard access when you use ad-hoc mode. Only ARRAY of BYTE or data types with a length of 8 bits can be used for data blocks with optimized access (e.g., CHAR, USINT, SINT, etc.). When ad-hoc mode is active, receipt of data is already signaled after a received byte at the NDR parameter. TCP (Receipt of data with specified length) For receipt of data with a specified length, enter the length of the data at the LEN parameter. The data receipt is not complete until the length of data specified at the LEN parameter has been completely received. Only then is the data available in the receive area (DATA parameter). The receipt of data is signaled by the NDR output parameter. The actually received data length in bytes at the RCVD_LEN parameter corresponds to the data length at the LEN parameter after receipt. ISO on TCP (Message-oriented data transfer) Complete message blocks are sent via a connection with the protocol variant ISO on TCP; these are recognized as such by the recipient. When using ISO on TCP, "TRCV" signals data receipt as soon as the message block has been completely received. The receive area is defined by the LEN and DATA parameters. If the receive buffer (DATA parameter) is too small for the sent data, "TRCV" signals an error. The successful receipt of data is signaled by the NDR output parameter. The actually received data length in bytes at the RCVD_LEN parameter corresponds to the data length at the LEN parameter after receipt. WinCC Basic V13.0 System Manual, 02/2014 3141 Programming the PLC 9.7 References Parameters The following table shows the parameters of the "TRCV" instruction: Parameter Declaration Data type Memory area Description EN_R Input BOOL I, Q, M, D, L or constant Receive enable ID Input CONN_OUC I, Q, M, D, L or constant Reference to the connection established with "TCON (Page 3124)". Range of values: W#16#0001 (1) to W#16#0FFF (4095) LEN Input UDINT I, Q, M, D, L or constant Length of the receive area in bytes (hidden). If you use a memory area with optimized access at the DATA parameter, the LEN parameter must have the value "0". DATA InOut VARIANT I, Q, M, D Pointer to the receive area NDR Output BOOL I, Q, M, D, L Status parameter (New Data Received): 0: Job not yet started or still in progress 1: Job completed without error BUSY Output BOOL I, Q, M, D, L Status parameter: 0: Job not yet started or already completed 1: Job not yet completed. A new job cannot be started ERROR Output BOOL I, Q, M, D, L Status parameter: 0: No error. 1: An error occurred during execution of the instruction. Detailed information is output via the STATUS parameter. STATUS Output WORD I, Q, M, D, L RCVD_LEN Output UDINT I, Q, M, D, L Status parameter: Output of status and error information. Amount of data actually received in bytes You can find additional information on valid data types under "Overview of the valid data types (Page 1204)". LEN, DATA and RCVD_LEN parameters If LEN = 0, the received data is saved in the receive area specified at the DATA parameter. The number of bytes received is indicated at the RCVD_LEN parameter. If the length specified at the LEN parameter is greater than the length of the data received at the DATA parameter, the error code 8088 is output at the STATUS parameter (see description of the STATUS) parameter in the following. If a structure (Struct) is referenced via the DATA parameter, LEN can be shorter than the structure. In this case, only the data up to the length of the LEN parameter is transferred. If the DATA parameter references a data block with optimized access, the LEN parameter must be set to "0". 3142 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References If a STRING data type is referenced via the DATA parameter, the length specified at the LEN parameter must be 0 or >=2 (LEN = 1 is not permitted). If a WSTRING data type is referenced via the DATA parameter, the length specified at the LEN parameter must be 0 or >=5. BUSY, NDR and ERROR parameters You can check the status of the job with the BUSY, NDR, ERROR and STATUS parameters. The BUSY parameter indicates the processing status. With the NDR parameter, you can check whether or not a job executed successfully. The ERROR parameter is set when errors occurred during execution of TRCV. The error information is output at the STATUS parameter. The following table shows the relationship between the BUSY, NDR and ERROR parameters: BUSY NDR ERROR Description 1 - - The job is being processed. 0 1 0 The job was completed successfully. 0 0 1 The job ended with an error. The cause of the error is output at the STATUS parameter. 0 0 0 No new job was assigned. Note Because "TRCV" is executed asynchronously, the data in the receive area is only consistent when the NDR parameter is set to the value "1". ERROR and STATUS parameters ERROR STATUS* Explanation (W#16#...) 0 0000 Job completed successfully. The current length of the received data is output at the RCVD_LEN parameter. 0 7000 Block not ready to receive. 0 7001 Block is ready to receive, receive job was activated. 0 7002 Interim call, the receive job is executing. Note: While the job is being processed, data is written to the receive area. Access to the receive area during this time may provide inconsistent data. 1 8085 The LEN parameter is larger than the highest permitted value. The value of the LEN or DATA parameter was changed after the first call. Both LEN parameters and the DATA parameter have the value "0" or LEN is longer than the maximum permitted value (65536). 1 8086 The ID parameter is outside the permitted address range (1 .. 0x0FFF). 1 8088 Receive area is too small. The value at the LEN parameter is larger than the receive area set at the DATA parameter. WinCC Basic V13.0 System Manual, 02/2014 3143 Programming the PLC 9.7 References ERROR STATUS* Explanation (W#16#...) 1 80A1 Communication error: The specified connection has not yet been established. The specified connection is being terminated. Receive job over this connection is not possible. The connection is being re-initialized. 1 80B3 The protocol variant (connection_type parameter in the connection description) is set to UDP. Use the instruction "TURCV" with a UDP connection. 1 80C3 A block with this ID is already being processed in a different priority group. Internal lack of resources. 1 80C4 Temporary communication error: The connection cannot be established to the partner at this time. The interface is receiving new parameter settings or the connection is being established. 1 80C5 The remote partner has terminated the connection. 1 80C6 The remote partner cannot be reached (network error). 1 80C7 Execution timeout. 1 80C9 The length of the receive area is smaller than the length of the sent data. * The error codes can be displayed as integer or hexadecimal values in the program editor. For additional information on toggling display formats, refer to "See also". TRCV: Receive data via communication connection Description The following description of the "TRCV" instruction is valid for the CPU S7-1500 and S7-1200 V4.0. You use the "TRCV" instruction to receive data over an existing communication connection. "TRCV" is executed asynchronously. Receipt of data is enabled when the EN_R parameter is set to the value "1". The received data is entered in a receive area. You specify the length of the receive area either with the LEN parameter (if LEN <> 0) or with the length information of the DATA parameter (if LEN = 0), depending on the protocol variant being used. While data is being received, you cannot make changes to the DATA parameter or the defined receive area to ensure consistency of the received data. After successful receipt of data, the NDR parameter is set to the value "1". You can query the amount of data actually received at the RCVD_LEN parameter. 3144 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Receive modes of "TRCV" The following table shows how the received data is entered in the receive area. Protocol variant ADHOC parameter Availability of data in the receive area connection_type parameter of the connection description LEN parameter TCP 1 (ad-hoc activated) The data is immediately available. Hexadecimal value: B#16#11 1 up to maximum length (depending on the CPU) (Ad-hoc mode) Integer value: 17 TCP (Receipt of data with specified length) ISO on TCP 0 (ad-hoc deactivated) - (Message-oriented data transfer) The data is available as soon as the data length specified at the LEN parameter has been fully received. Hexadecimal value: B#16#11 1 to 8192 The data is available as soon as the data length specified at the LEN parameter has been fully received. Hexadecimal value: B#16#12 1 to 1452, if a CP is used. Integer value: 18 1 to 8192, if no CP is used. Integer value: 17 TCP (Ad-hoc mode) The ad-hoc mode is only available with the TCP protocol variant. You use the ad-hoc mode to receive data with dynamic length with the "TRCV" instruction. You set ad-hoc mode by assigning the value "1" to the ADHOC parameter. All data types can be used for data blocks with standard access when you use ad-hoc mode. Only ARRAY of BYTE or data types with a length of 8 bits can be used for data blocks with optimized access (e.g., CHAR, USINT, SINT, etc.). When ad-hoc mode is active, receipt of data is already signaled after a received byte at the NDR parameter. TCP (Receipt of data with specified length) Assign the value "0" to the ADHOC parameter for receipt of data with specified length. If adhoc mode is disabled, the data receipt is not complete until the length of data specified at the LEN parameter has been completely received. Only then is the data available in the receive area (DATA parameter). The successful receipt of data is signaled by the NDR output parameter. The actually received data length in bytes at the RCVD_LEN parameter corresponds to the data length at the LEN parameter after receipt. ISO on TCP (Message-oriented data transfer) Complete message blocks are sent via a connection with the protocol variant ISO on TCP; these are recognized as such by the recipient. When using ISO on TCP, "TRCV" signals data receipt as soon as the message block has been completely received. The receive area is defined by the LEN and DATA parameters. If the receive buffer (DATA parameter) is too small for the sent data, "TRCV" signals an error. The successful receipt of data is signaled by the NDR output parameter. The actually received data length in bytes at the RCVD_LEN parameter corresponds to the data length at the LEN parameter after receipt. WinCC Basic V13.0 System Manual, 02/2014 3145 Programming the PLC 9.7 References Parameters The following table shows the parameters of the "TRCV" instruction: Parameter Declaration Data type Memory area Description EN_R Input BOOL I, Q, M, D, L or constant Receive enable ID Input CONN_OUC I, Q, M, D, L or constant Reference to the connection established with "TCON". Range of values: W#16#0001 to W#16#0FFF LEN Input UDINT I, Q, M, D, L or constant Length of the receive area in bytes (hidden). If you use a receive area with optimized access at the DATA parameter, the LEN parameter must have the value "0". ADHOC Input BOOL I, Q, M, D, L or constant Use ad-hoc mode for the TCP protocol variant (hidden). DATA InOut VARIANT I, Q, M, D Pointer to the receive area NDR Output BOOL I, Q, M, D, L Status parameter (New Data Received): 0: Job not yet started or still in progress 1: New data received BUSY Output BOOL I, Q, M, D, L Status parameter with the following values: 0: Job not yet started or already completed 1: Job not yet completed. A new job cannot be started ERROR Output BOOL I, Q, M, D, L Status parameter ERROR: 0: No error 1: Error occurred STATUS Output WORD I, Q, M, D, L Status of the instruction RCVD_LEN Output UDINT I, Q, M, D, L Amount of data actually received in bytes You can find additional information on valid data types under "Overview of the valid data types (Page 1204)". LEN, DATA and RCVD_LEN parameters If LEN = 0, the received data is saved in the receive area specified at the DATA parameter. The number of bytes received is indicated at the RCVD_LEN parameter. If the length specified at the LEN parameter is greater than the length of the data received at the DATA parameter, the error code 8088 is output at the STATUS parameter (see description of the STATUS) parameter in the following. If a structure (Struct) is referenced via the DATA parameter, LEN can be shorter than the structure. In this case, only the data up to the length of the LEN parameter is transferred. If the DATA parameter references a data block with optimized access, the LEN parameter must be set to "0". If the length of the data does not match for elementary data types, the data will not be received and the error code 8088 is output at the STATUS parameter. 3146 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References If a STRING data type is referenced via the DATA parameter, the length specified at the LEN parameter must be 0 or >=2 (LEN = 1 is not permitted). If a WSTRING data type is referenced via the DATA parameter, the length specified at the LEN parameter must be 0 or >=5. BUSY, NDR and ERROR parameters You can check the status of the job with the BUSY, NDR, ERROR and STATUS parameters. The BUSY parameter indicates the processing status. With the NDR parameter, you can check whether or not a job executed successfully. The ERROR parameter is set when errors occurred during execution of TRCV. The error information is output at the STATUS parameter. The following table shows the relationship between the BUSY, NDR and ERROR parameters: BUSY NDR ERROR Description 1 - - The job is being processed. 0 1 0 The job was completed successfully. 0 0 1 The job ended with an error. The cause of the error is output at the STATUS parameter. 0 0 0 No new job was assigned. Note Because "TRCV" is executed asynchronously, the data in the receive area is only consistent when the NDR parameter is set to the value "1". ERROR and STATUS parameters ERROR STATUS* Explanation (W#16#...) 0 0000 Job completed successfully. The current length of the received data is output at the RCVD_LEN parameter. 0 7000 Block not ready to receive. 0 7001 Block is ready to receive, receive job was activated. 0 7002 Interim call, the receive job is executing. Note: While the job is being processed, data is written to the receive area. Access to the receive area during this time may provide inconsistent data. 1 8085 The LEN parameter is larger than the highest permitted value. The value of the LEN or DATA parameter was changed after the first call. Both LEN parameters and the DATA parameter have the value "0" or LEN is longer than the maximum permitted value (65536). 1 8086 The ID parameter is outside the permitted value range (1 .. 0x0FFF). 1 8088 Receive area is too small. The value at the LEN parameter is larger than the receive area set at the DATA parameter. WinCC Basic V13.0 System Manual, 02/2014 3147 Programming the PLC 9.7 References ERROR STATUS* Explanation (W#16#...) 1 80A1 Communication error: The specified connection has not yet been established. The specified connection is being terminated. Receive job over this connection is not possible. The connection is being re-initialized. 1 80B3 The protocol variant (connection_type parameter in the connection description) is set to UDP. Use the instruction "TURCV" with a UDP connection. 1 80C3 A block with this ID is already being processed in a different priority group. Internal lack of resources. 1 80C4 Temporary communication error: The connection cannot be established to the partner at this time. The interface is receiving new parameter settings or the connection is being established. 1 80C5 The remote partner has terminated the connection. 1 80C6 The remote partner cannot be reached (network error). 1 80C7 Execution timeout. 1 80C9 The length of the receive area is smaller than the length of the sent data. * The error codes can be displayed as integer or hexadecimal values in the program editor. For additional information on toggling display formats, refer to "See also". See also TRCV: Receive data via communication connection (Page 3140) TCON: Establish communication connection (Page 3127) Structure of the address information for the remote partner with UDP Overview When using a UDP connection, the address information for the remote partner is stored in the system data type TADDR_Param: By using the instruction "TUSEND (Page 3150)" the address information of the recipient is assigned to the parameter ADDR via TADDR_Param. The stored address data of the remote partner are read from the system data type by the instruction. By using the instruction "TURCV (Page 3153)" the address of the sender is received at the parameter ADDR via TADDR_Param. The address data is written by the instruction in the system data type. Structure of the address information according to TADDR_Param The system data type TADDR_Param contains the address information of the remote partner and consists of the IP address and the port number. The system data type TADDR_Param has the following structure: 3148 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Byte Parameter Data type Start value Description 0 to 3 rem_ip_addr ARRAY [1..4] of USINT B#16#00 ... IP address of the remote partner, e.g. 192.168.002.003: rem_ip_addr[1] = B#16#C0 (192) rem_ip_addr[2] = B#16#A8 (168) rem_ip_addr[3] = B#16#02 (002) rem_ip_addr[4] = B#16#03 (003) The IP address can be taken from the Devices & networks view in the interface properties of the remote partner. As an alternative these are also displayed in the properties of the UDP connection under Address details. 4 to 5 rem_port_nr UINT B#16#00 ... Remote port-number (possible values see: Auto-Hotspot): rem_port_nr[1] = high byte of the port no. in hexadecimal notation rem_port_nr[2] = low byte of port no. in hexadecimal notation The port number can be taken from the Devices & networks view in the UDP connection properties. The port number is indicated under Address details as a decimal value. Example: Port number = 2000 (decimal) / W#16#07D0 (hexadecimal) rem_port_nr[1] = 07 (high byte) rem_port_nr[2] = D0 (low byte) 6 to 7 reserved WORD B#16#00 ... Not used. Leave the value "0" at this parameter. Creating TADDR_Param in a data block You have the following options for creating TADDR_Param: Create a new data block and select TADDR_Param as type in the dialog "Add new data block". Open an existing data block create a new tag and enter in the column Data type TADDR_Param. A data block can contain several system data types TADDR_Param. WinCC Basic V13.0 System Manual, 02/2014 3149 Programming the PLC 9.7 References TUSEND: Send data via Ethernet (UDP) Description The "TUSEND" instruction sends data to the remote partner addressed by the ADDR parameter using UDP. WARNING Data transfer via UDP Data transferred via UDP to RFC 768 to the remote partner are sent without acknowledgement and are therefore unsecured. This means the data can be lost without any indication at the block. Note For sequential send operations to different partners, you only need to adjust the ADDR parameter when calling "TUSEND". You do not need to call the "TCON (Page 3124)" and "TDISCON (Page 3132)" instructions again. The UDP port must be set up at the specific remote partner in order for this partner to receive data. Functional description "The TUSEND" instruction works asynchronously, which means its job processing extends over multiple calls. Create a rising edge at the REQ parameter to establish a connection once again. The output parameters BUSY, DONE, ERROR and STATUS indicate the status of the job. See also: Meaning of the parameters REQ, RET_VAL and BUSY with asynchronous instructions (Page 1736). The following table shows the relationship between BUSY, DONE and ERROR. Using this table, you can determine the current status of "TUSEND" or when the send process is concluded. BUSY DONE ERROR Description TRUE FALSE FALSE The job is being processed. FALSE TRUE FALSE Job successfully completed. FALSE FALSE TRUE The job ended with an error. The cause of the error can be found in the STATUS parameter. FALSE FALSE FALSE The instruction was not assigned a (new) job. Note Due to the asynchronous operation of "TUSEND", make sure the data in the send area remains consistent until the DONE parameter or the ERROR parameter has the value TRUE. 3150 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameters The following table shows the parameters of the "TUSEND" instruction: Parameters Declaration Data type Memory area Description REQ Input BOOL I, Q, M, D, L or constant Control parameter REQUEST starts the send job on a rising edge. The data is transferred from the area specified by DATA and LEN. ID Input CONN_OU C I, Q, M, D, L or constant Reference to the associated connection between the user program and the communication layer of the operating system. ID must be identical to the associated parameter ID in the local connection description with the instruction "TCON". LEN Input UINT I, Q, M, D, L or constant Number of bytes to be sent with the job DONE Output BOOL I, Q, M, D, L Status parameter DONE: Range of values: W#16#0001 to W#16#0FFF Range of values: 1 to 1472 0: Job not yet started or still executing. 1: Job executed without errors. This value is only displayed for one cycle. BUSY Output BOOL I, Q, M, D, L ERROR Output BOOL I, Q, M, D, L BUSY = 1: The job is not yet completed. A new job cannot be triggered. BUSY = 0: The job is completed. Status parameter ERROR: ERROR=1: An error has occurred during processing, STATUS supplies detailed information on the type of error. STATUS Output WORD I, Q, M, D, L Status parameter STATUS: Error information DATA InOut VARIANT I, Q, M, D Send area, contains address and length The address refers to: The process image of the inputs The process image of the outputs A bit memory A data block ADDR InOut VARIANT D Pointer to the system data type TADDR_Param. Store the address information of the remote partner (IP address and port number) in a data block with the system data type TADDR_Param. See also: Structure of the address information for the remote partner with UDP (Page 3148) You can find additional information on valid data types under "Overview of the valid data types (Page 1204)". WinCC Basic V13.0 System Manual, 02/2014 3151 Programming the PLC 9.7 References ERROR and STATUS parameters ERROR STATUS* Explanation (W#16#...) 0 0000 Send job completed without error 0 7000 No job processing active 0 7001 Start of job processing, data being sent Note: During this processing phase, the operating system accesses the data in the DATA send area. 0 7002 Intermediate call (REQ irrelevant), job is being processed Note: During this processing phase, the operating system accesses the data in the DATA send area. 1 8085 The LEN parameter has the value "0" or is greater than the highest permitted value. 1 8086 The ID parameter is not in the permitted value range. 0 8088 The LEN parameter is greater than the memory area specified in DATA. 1 8089 The ADDR parameter does not point to a data block with the TADDR_Param structure. 1 80A1 Communication error: The specified connection between user program and communication layer of the operating system has not yet been established. The specified connection between the user program and the communication layer of the operating system is currently being terminated. Transmission over this connection is not possible. The interface is being reinitialized. 1 80A4 IP address (at the ADDR parameter) of the remote connection end point is invalid; it may correspond to the local partner's own IP address. 1 80B3 The protocol variant (connection_type parameter in the connection description) is not set to UDP. Please use "TSEND (Page 3137)". 1 80B7 1 80C3 ADDR parameter: Invalid information for port no. The length of the structure referenced by the parameter ADDR is not 8 bytes. A block with this ID is already being processed in a different priority class. Internal lack of resources. 1 80C4 Temporary communication error: The connection between the user program and the communication layer of the operating system cannot be established at this time. New parameter settings are being assigned to the interface. 1 80C5 The remote partner has terminated the connection. 1 80C6 The remote partner cannot be reached (network error). 1 80C7 Execution timeout. - General error informatio n See also: GET_ERR_ID: Get error ID locally (Page 1964) * The error codes can be displayed as integer or hexadecimal values in the program editor. For additional information on toggling display formats, refer to "See also". 3152 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References TURCV: Receive data via Ethernet (UDP) Description The "TURCV" instruction receives data via UDP. After successful completion of "TURCV", the ADDR parameter will show you the address of the remote partner (the sender). WARNING Unsecured data transfer Data transferred via UDP to RFC 768 to the remote partner are sent without acknowledgement and are therefore unsecured. This means the data can be lost without any indication at the block. Functional description "The TURCV" instruction works asynchronously, which means its job processing extends over multiple calls. You start the receive job by calling "TURCV" with EN_R = 1. The output parameters BUSY, DONE, ERROR and STATUS indicate the status of the job. See also: Meaning of the parameters REQ, RET_VAL and BUSY with asynchronous instructions (Page 1736). The following table shows the relationship between BUSY, NDR and ERROR. Using this table, you can determine the current status of TURCV or when the receive process is concluded. BUSY NDR ERROR Description TRUE FALSE FALSE The job is being processed. FALSE TRUE FALSE Job successfully completed. New data was received. FALSE FALSE TRUE The job ended with an error. The cause of the error can be found in the STATUS parameter. FALSE FALSE FALSE The instruction was not assigned a (new) job. Note Due to the asynchronous operation of "TURCV", the data in the receive area is only consistent when the NDR parameter has the value TRUE. WinCC Basic V13.0 System Manual, 02/2014 3153 Programming the PLC 9.7 References Parameters The following table shows the parameters of the "TURCV" instruction: Parameters Declaration Data type Memory area Description EN_R Input BOOL I, Q, M, D, L or constant Control parameter enabled to receive When EN_R = 1, "TURCV" is ready to receive. The receive job is being processed. ID Input WORD I, Q, M, D, L or constant Reference to the associated connection between the user program and the communication layer of the operating system. ID must be identical to the corresponding parameter ID in the local connection description. Value range: W#16#0001 to W#16#0FFF LEN Input UINT I, Q, M, D, L or constant Length of the receive area in bytes: 0 (recommended) or 1 to 1472 NDR Output BOOL I, Q, M, D, L Status parameter NDR: NDR = 0: Job not yet started or still running NDR = 1: Job successfully completed ERROR Output BOOL I, Q, M, D, L Status parameter ERROR: ERROR=1: Error occurred during processing. STATUS supplies detailed information on the type of error BUSY Output BOOL I, Q, M, D, L BUSY = 1: The job is not yet completed. A new job cannot be triggered. STATUS Output WORD I, Q, M, D, L Status parameter STATUS: Error information RCVD_LEN Output UINT I, Q, M, D, L Amount of data actually received in bytes DATA InOut VARIANT I, Q, M, D, L Receive area BUSY = 0: The job is completed. The address references: The process image of the inputs The process image of the outputs A bit memory A data block ADDR InOut VARIANT D Pointer to the system data type TADDR_Param. The address information of the remote partner (IP address and port number) is written in a data block with the system data type TADDR_Param. See also: Structure of the address information for the remote partner with UDP (Page 3148) You can find additional information on valid data types under "Overview of the valid data types (Page 1204)". 3154 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References ERROR and STATUS parameters ERROR STATUS* (W#16#...) Explanation 0 0000 New data was accepted. The current length of the received data is shown in RCVD_LEN. 0 7000 Block not ready to receive 0 7001 Block is ready to receive, receive job was activated 0 7002 Intermediate call, receive job being processed Note: During this processing phase, "TURCV" writes data to the receive area. For this reason, an error could result in inconsistent data in the receive area. 1 8085 The LEN parameter is greater than the largest permitted value, or you changed the value of the LEN or DATA parameter since the first call 1 8086 The ID parameter is not in the permitted value range 1 8088 Receive area is too small 1 8089 The ADDR parameter does not point to a data block with the TADDR_Param structure. 1 80A1 Communication error: Value in LEN is higher than the receive area specified by DATA The specified connection between user program and communication layer of the operating system has not yet been established. The specified connection between the user program and the communication layer of the operating system is currently being terminated. A receive job over this connection is not possible. New parameter settings are being assigned to the interface. 1 80B3 The protocol variant (connection_type parameter in the connection description) is not set to UDP. Please use "TRCV (Page 3140)". 1 80B7 The length at ADDR parameter does not correspond to 8 bytes. 1 80C3 A block with this ID is already being processed in a different priority class. 1 80C4 Temporary communication error: New parameter settings are being assigned to the interface. 1 80C5 The remote partner has terminated the connection. 1 80C7 Execution timeout. 1 80C9 With RFC1006 / UDP: The received data is longer than expected (size of receive buffer exceeded). - General error information See also: GET_ERR_ID: Get error ID locally (Page 1964) Internal lack of resources. * The error codes can be displayed as integer or hexadecimal values in the program editor. For additional information on toggling display formats, refer to "See also". See also TCON: Establish communication connection (Page 3124) TDISCON: Terminate communication connection (Page 3132) WinCC Basic V13.0 System Manual, 02/2014 3155 Programming the PLC 9.7 References T_RESET: Resetting the connection Description The "T_RESET" instruction terminates and then reestablishes an existing connection. The local end points of the connection are retained. They are generated automatically: If a connection has been configured and loaded to the CPU. If a connection has been generated by the user program, for example, by calling the instruction "TCON (Page 3124)". The instruction "T_RESET" can be executed for all connection types (TCP, UDP, ISO-on-TCP, etc.). It does not matter whether the local interface of the CPU or the interface of a CM/CP was used for the connection. Once the instruction "T_RESET" has been called using the REQ parameter, the connection specified with the ID parameter is terminated and, if necessary, the data send and receive buffer cleared. Canceling the connection also cancels any data transfer in progress. There is therefore a risk of losing data if data transfer is in progress. The CPU defined as the active connection partner will then automatically attempt to restore the interrupted communication connection. You therefore do not need to call the "TCON (Page 3124)" instruction to reestablish the communication connection. The output parameters DONE, BUSY and STATUS indicate the status of the job. Parameters The following table shows the parameters of the "T_RESET" instruction: Parameter Declaration Data type Memory area Description REQ Input BOOL I, Q, M, D, L or constant Control parameter REQUEST starts the job for terminating the connection specified by ID. The job starts on a rising edge. ID Input CONN_OUC I, Q, M, D, L or constant Reference to the connection to the passive partner ID being interrupted must be identical to the corresponding parameter ID in the local connection description. DONE Output BOOL I, Q, M, D, L Range of values: W#16#0001 to W#16#0FFF Status parameter DONE 0: Job not yet started or still executing. 1: Job executed without errors BUSY Output BOOL I, Q, M, D, L Status parameter BUSY 0: Job is complete. 1: The job is not yet completed. 3156 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameter Declaration Data type Memory area Description ERROR Output BOOL I, Q, M, D, L Status parameter ERROR 0: No error occurred. 1: Error occurred during processing. The STATUS parameter supplies detailed information on the type of error STATUS Output WORD I, Q, M, D, L Status parameter STATUS Error information (see "STATUS parameter" table). You will find more detailed information on valid data types in "Overview of the valid data types (Page 1204)". Parameter STATUS STATUS* (W#16#...) Explanation 0000 No error. 0001 Connection has not been established. 7001 Connection termination launched. 7002 Connection being terminated. 8081 Unknown connection specified at the ID parameter. * The error codes can be displayed as integer or hexadecimal values in the program editor. For additional information on toggling display formats, refer to "See also". T_DIAG: Checking the connection Description You use the "T_DIAG" instruction to check the status of a connection and read further information on the local end point of this connection. The connection is referenced by the ID parameter. You can read both connection end points configured in the connection editor and programmed connection end points (e.g. with the "TCON" instruction). Temporary connection end points (for example end points created when you connect to an engineering station) cannot be diagnosed, as no connection ID is generated in this process. The connection information read is stored in a structure referenced by the RESULT parameter. The output parameter STATUS indicates whether it was possible to read the connection information. The connection information in the structure at the RESULT parameter is only valid if the "T_DIAG" instruction has been completed with STATUS = W#16#0000 and ERROR = FALSE. Connection information cannot be evaluated if an error occurs. WinCC Basic V13.0 System Manual, 02/2014 3157 Programming the PLC 9.7 References Possible connection information Two different structures can be used to read the connection information at the RESULT parameter: The "TDiag_Status" structure only contains the most important information about a connection end point, for example the protocol used, the connection status and the number of data bytes sent or received. The structure "TDiag_StatusExt" supplies not just the most important information, but also the number of connection attempts, the reason for a connection abort, etc. The structure and parameters of the two structures are described below (see the "TDIAG_Status and TDIAG_StatusExt structures" table). Parameters The following table shows the parameters of the "T_DIAG" instruction: Parameter Declaration Data type Memory area Description REQ Input BOOL I, Q, M, D, L or constant Starts the instruction to check the connection specified in the ID parameter when there is a positive edge. ID Input CONN_OUC (WORD) L, D or constant Reference to the assigned connection. Range of values: W#16#0001 to W#16#0FFF RESULT InOut VARIANT D Pointer to the structure in which the connection information is stored. The structure TDiag_Status or TDiag_StatusExt can be used at the RESULT parameter (for a description, see the "TDIAG_Status and TDIAG_StatusExt structures" table). DONE Output BOOL I, Q, M, D, L Status parameter: 0: Instruction not yet started or still in progress. 1: Instruction executed without errors. BUSY Output BOOL I, Q, M, D, L Status parameter: 0: Instruction not yet started or already completed. 1: Instruction not yet completed. A new job cannot be started. ERROR Output BOOL I, Q, M, D, L Status parameter: 0: No error. 1: Error occurred. STATUS Output WORD I, Q, M, D, L Status of the instruction You will find more detailed information on valid data types in "Overview of the valid data types (Page 1204)". 3158 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameters BUSY, DONE and ERROR You can check the status of "T_DIAG" instruction execution with the BUSY, DONE, ERROR and STATUS parameters. The BUSY parameter indicates the processing status. You use the DONE parameter to check whether or not an instruction has been executed successfully. The ERROR parameter is set if errors occur during execution of "T_DIAG". The following table shows the relationship between the BUSY, DONE and ERROR parameters: BUSY DONE ERRO Description R 1 - - The instruction is being processed. 0 1 0 The instruction has been executed successfully. The data in the structure referenced by RESULT are only valid if this is the case. 0 0 1 Instruction completed with an error. The cause of the error is output at the STATUS parameter. 0 0 0 No new instruction has been assigned. Parameter STATUS The following table shows the meaning of the values at the STATUS parameter: STATU Explanation S* (W#16#. ..) 0000 The instruction "T_DIAG" has been executed successfully. The data in the structure referenced at the RESULT parameter can be evaluated. 7000 No instruction processing active. 7001 Instruction processing launched. 7002 Connection information is being read (REQ parameter irrelevant). 8086 The value at the ID parameter is outside the valid range (W#16#0001 ... W#16#0FFF). 8089 The RESULT parameter points to an invalid data type (structures TDIAG_Status and TDIAG_StatusExt only). 80A3 The ID parameter references a connection end point which does not exist. With programmed connections, this error can also occur after the "TDISCON" instruction is called. 80C4 Internal error. Access to the connection end point is temporarily unavailable. * The error codes can be displayed as integer or hexadecimal values in the program editor. For additional information on toggling display formats, refer to "See also". Structures TDIAG_Status and TDIAG_StatusExt The table below details the form of the TDIAG_Status and TDIAG_StatusExt structures: From the InterfaceID to the ReceivedBytes parameter, the "TDIAG_StatusExt" and "TDIAG_Status" structures are identical. The structure TDIAG_StatusExt also includes the parameters ConnTrials to LastDisconnTimeStamp. The value of each element is only valid if the instruction has been executed without errors. If an error occurs, the content of the parameters will not change. WinCC Basic V13.0 System Manual, 02/2014 3159 Programming the PLC 9.7 References Name Data type Description The following parameters are in both the TDIAG_Status and the TDIAG_StatusExt structure: InterfaceID HW_ANY Interface ID (LADDR) of the CPU or the CM/CP. ID CONN_OU ID of the connection diagnosed. Following a successful call, the value of this element is C identical to the parameter ID of the "T_DIAG" instruction. ConnectionType BYTE Protocol type used for connection: 0x01: Not used. ... 0x0B: TCP protocol (IP_v4) 0x0C: ISO-on-TCP protocol (RFC1006) 0x0D: TCP protocol (DNS) 0x0E: Dial-in protocol 0x0F: WDC protocol 0x10: SMTP protocol 0x11: TCP protocol 0x12: TCP and ISO-on-TCP protocol (RFC1006) 0x13: UDP protocol 0x14: Reserved 0x15: PROFIBUS bus access protocol (FDL) 0x16: ISO 8073 transport protocol (ISO native) ... 0x20: SMTP or SMTPS protocol - based on IPv4 0x21: SMTP or SMTPS protocol - based on IPv6 0x22: SMTP or SMTPS protocol - based on FQDN (Fully Qualified Domain Name) ... 0x70: S7 connection Other: Reserved ActiveEstablished BOOL State BYTE FALSE: Locally, the passive connection end point TRUE: Locally, the active connection end point Current status of the connection end point 0x00: Not used. 0x01: Connection terminated. Temporary status, for example, after the "T_RESET" instruction is called. The system then automatically attempts to reestablish the connection. 0x02: The active connection end point is attempting to establish a connection to the remote communication partner. 0x03: The passive connection end point is waiting for establishment of the connection to the remote communication partner. 0x04: Connection established. 0x05: The connection is being terminated. This may be because the "T_RESET" or "T_DISCON" instruction has been called. Other possible reasons are protocol errors and line breaks. 0x06..0xFF: Not used. 3160 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Name Data type Description Kind BYTE Mode of the connection end point: 0x00: Not used. 0x01: Configured, static connection which has been configured and loaded to the CPU. 0x02: Configured, dynamic connection which has been configured and loaded to the CPU (not currently supported). 0x03: Programmed connection generated in the user program with the instruction "TCON". A call of the instruction "TDISCON" or a transition to CPU STOP status has destroyed the connection end point. 0x04: Temporary, dynamic connection established by the engineering station (ES) or operator station (OS), for example. (this connection type cannot currently by diagnosed as there is no ID). 0x05..0xFF: Not used. SentBytes UDINT Number of data bytes sent. ReceivedBytes UDINT Number of data bytes received. The following parameters only occur in the TDiag_StatusExt structure: ConnTrials UDINT ConnTrialsSucces s UDINT LastConnErrReas on UDINT Number of connection attempts. Once a connection has been established, ConnTrials has the value 0. If this element is not equal to 0, there are connection problems. Note: With a passive connection end point, this value is never greater than 1. Number of successful connection attempts. This element is never reset during the life cycle of a connection end point, and returns to 0 after reaching 0xFFFF FFFF. Note: This parameter is 1 if there has never been a problem in this connection. Error ID output during the last connection attempt with errors (the error messages are identical to those at the LastDisconnReason parameter): 0x4F01: Remote connection end point cannot be reached (this error usually occurs during connection establishment). 0x4F02: Connection terminated locally. 0x4F03: Connection terminated by remote communication partner. 0x4F04: Connection terminated by a protocol error. 0x4F05: Connection terminated by a network problem detected locally. 0x4F06: Connection terminated by a network problem detected remotely. 0x4F07: Connected terminated due to timeout in protocol. 0x4F08: Incorrect parameter assignment: Connection to be established to local partner's own address. 0x4F09: Connection temporarily reset by a call of the instruction "T_RESET". 0x4F0A: Insufficient connection resources available (quantity exceeded) 0x4F0B: Internal error: Incorrect addressing parameters 0x4F0C: Internal CPU communication error 0x4F0D: Internal AS communication error between CPU and CM/CP 0x4F0E: The local TCP/UDP port (or RFC1006-T selector) specified is already in use. LastConnErrTime Stamp LDT WinCC Basic V13.0 System Manual, 02/2014 Time of the last connection attempt with errors. 3161 Programming the PLC 9.7 References Name Data type Description LastDisconnReas on UDINT Error ID which led to the last connection termination (the error messages are identical to those at the LastConnErrReason parameter): 0x4F01: Remote connection end point cannot be reached (this error usually occurs during connection establishment). 0x4F02: Connection terminated locally. 0x4F03: Connection terminated by remote communication partner. 0x4F04: Connection terminated by a protocol error. 0x4F05: Connection terminated by a network problem detected locally. 0x4F06: Connection terminated by a network problem detected remotely. 0x4F07: Connected terminated due to timeout in protocol. 0x4F08: Incorrect parameter assignment: Connection to be established to local partner's own address. 0x4F09: Connection temporarily reset by a call of the instruction "T_RESET". 0x4F0A: Insufficient connection resources available (quantity exceeded) 0x4F0B: Internal error: Incorrect addressing parameters 0x4F0C: Internal CPU communication error 0x4F0D: Internal AS communication error between CPU and CM/CP 0x4F0E: The local TCP/UDP port (or RFC1006-T selector) specified is already in use. LastDisconnTime Stamp LDT Time of the last connection termination. T_CONFIG: Configure interface Description T_CONFIG Description The "T_CONFIG" instruction is used for the program-controlled configuration of the integrated PROFINET interfaces of the CPU or the interface of a CP/CM. You can change the Ethernet address of the PROFINET device name from the user program via the instruction. The existing configuration data is overwritten. You can make the following changes via the instruction "T_CONFIG": Settings for the IP protocol - IP address - Subnet mask - Router address Settings for PROFINET - Assignment of the PROFINET device name 3162 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References The settings correspond with the configuration options under "IP protocol" and "PROFINET" in the dialog "Ethernet addresses". This is displayed in the view "devices & networks" under the properties of the PROFINET interface. WARNING Restart of CPU after execution of the "T_CONFIG" instruction The CPU is restarted after you have executed the instruction to change an IP parameter. The CPU goes to STOP mode, a warm restart is carried out and the CPU starts up again (RUN mode). Make sure that the control process is in a secure operating mode after the CPU has been restarted following execution of the instruction. Uncontrolled operation can result in serious material damage or personal injury due to malfunctions or programming errors, for example. Non-retentive data could be lost. Requirement In order to use the instruction must be explicitly specified in the hardware configuration that the assignment of IP address parameters and device name must be made by the user program. For this purpose open the properties of the PROFINET interface in the device view. Activate the following options in the dialog "Ethernet addresses": - In order to change the IP address parameters with "T_CONFIG": Select the setting "Set IP address using a different method" under "IP protocol". - In order to change the PROFINET device name with "T_CONFIG": Select the setting "Set PROFINET device name using a different method" under "PROFINET". The configuration data must be stored in the following system data types and assigned at the parameter CONF_DATA (Page 3166): - Store the IP address, subnet mask, and the router address in the system data type IF_CONF_V4. - Store the device name in the system type IF_CONF_NOS. Observe the restrictions that exist for assigning the name of the device (see parameter CONF_DATA (Page 3166)). Functional description The "T_CONFIG" instruction works asynchronously, which means its execution extends over multiple calls. The configuration process is started by calling "T_CONFIG" with REQ = 1. Only one job can be active at any time. The block is edge triggered which means that after BUSY= FALSE the block must be re-called with REQ=FALSE to enable the instance. WinCC Basic V13.0 System Manual, 02/2014 3163 Programming the PLC 9.7 References Parameters The following table shows the parameters of the "T_CONFIG" instruction: Parameter Declaration Data type Memory area Description REQ Input BOOL I, Q, M, D, L or constant Calling the instruction with REQ = 1 starts processing of the instruction. INTERFACE Input HW_INTERFA CE I, Q, M, D, L or constant Hardware identifier of the interface The hardware ID is displayed in the properties of the interface in the device view, and in the system constants of the PLC tags. CONF_DATA (Page 3166) Input VARIANT D, L Pointer to the parent structure that contains the system data types IF_CONF_HEADER, IF_CONF_V4 and IF_CONF_NOS (see description of the parameters CONF_DATA). DONE (Page 3170) Output BOOL I, Q, M, D, L Status parameter: 0: Processing not yet complete. 1: Processing of instruction finished successfully. BUSY (Page 3170) Output ERROR (Page 3170) Output BOOL I, Q, M, D, L Status parameter: 0: Processing of the instruction has not started, completed or canceled yet. 1: Processing of instruction is in progress BOOL I, Q, M, D, L Status parameter: 0: No error 1: Error STATUS (Page 3170) Output ERR_LOC (Page 3170) Output DWORD I, Q, M, D, L Detailed status information: Detailed error and status information in the form of an error code are output at the parameter STATUS. DWORD I, Q, M, D, L Error location: 0: Error during execution of the instruction or when assigning parameters. > 0: Errors in the structure or content of the configuration data at the parameter CONF_DATA. For additional information on valid data types, refer to "Overview of the valid data types (Page 1204)". Example In the following example the device name of an IO device is changed with the instruction "T_CONFIG". Call of instruction The execution of the instruction is started with REQ=1. The hardware ID of the PROFINET interface is specified at the parameter Interface. The structure "StructConfigData" is referenced at the parameter CONF_DATA. The structure was created in the global data block "DataBlock". 3164 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameters CONF_DATA The structure "StructConfigData" at the parameter CONF_DATA contains the following information: In the Header (IF_CONF_HEADER). SubfieldCount = 1: Indicates that only one additional structure (nos) is used below. In the structure "nos" (system data type IF_CONF_NOS) - Lenght = 11: Information on overall length of the structure NOS (5 bytes for the device name "myplc" + 6 bytes for the parameters Id, Length and Mode) Note: Instead of an absolute length, you can use the default start value (Lenght = 0) for a dynamic length. - Mode = 1: Permanent change of the device name in "myplc". - NOS[1] ... NOS[5]: Device name (1 character / byte) WinCC Basic V13.0 System Manual, 02/2014 3165 Programming the PLC 9.7 References See also Evaluating errors with output parameter RET_VAL (Page 1738) Parameter CONF_DATA Structure of the configuration data The configuration data at the parameter CONF_DATA can be stored in a global data block or in the section "Static" of the block interface. The configuration data must be stored according to the following structure: Name Data type Description ConfData Struct Parent structure that is assigned at the parameter CONF_DATA. Header IF_CONF_HEAD The header is used to define the number of these system data types. The system data ER type IF_CONF_HEADER must always be included. IPData IF_CONF_V4 The IP address, subnet mask and router address are stored in this system data type. Only create IF_CONF_V4 if you also want to change the Ethernet address with "T_CONFIG". NoS IF_CONF_NOS The PROFINET device names are stored in this system data type. Only create IF_CONF_NOS if you also want to change the device names with "T_CONFIG". The system data types IF_CONF_HEADER, IF_CONF_V4 and IF_CONF_NOS are created by entering the name of the system data type in the column "data type" of the data block or the block interface. The name for the system data types can be freely assigned. 3166 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References System data type IF_CONF_Header Use the system data type IF_CONF_Header to specify the number of system data types IF_CONF_V4 and IF_CONF_NOS that are used during the execution of "T_CONFIG". Byte Parameter Data type Start value Description 0 ... 1 FieldType UINT 0 Field type: Must always have the value "0". 2 ... 3 FieldId UINT 0 Error ID: Must always have the value "0". 4 ... 5 SubfieldCount UINT 0 Number of system data types IF_CONF_V4 and IF_CONF_NOS: 1: Only one of the system data types is used. 2: Both system data types are used System data type IF_CONF_V4 The IP address, subnet mask and router address are defined with the system data type IF_CONF_V4. Byte Parameter Data type Start value Description 0 ... 1 Id UINT 30 System data type ID The start value of this parameter may not be changed. 2 ... 3 Length UINT 18 Length of the system data type IF_CONF_V4 The start value must be used for the length specification since the parameters of IF_CONF_V4 have a fixed length and structure. 4 ... 5 Mode UINT 0 Validity of addressing: 1: Permanent validity of the configuration data 2: Temporary validity of the configuration data including the deletion of existing permanent configuration data 6 ... 9 InterfaceAddress IP_V4 * 0.0.0.0 IP address 10 ... 12 SubnetMask IP_V4 * 0.0.0.0 Subnet mask 14 ... 16 DefaultRouter IP_V4 * 0.0.0.0 Router address * The data type IP_V4 is a structure of 4 BYTE, which includes the respective address of the respective parameter (e.g. at parameter SubnetMask the four-digit address of the subnet mask of the IP protocol). WinCC Basic V13.0 System Manual, 02/2014 3167 Programming the PLC 9.7 References Subfield IF_CONF_NOS Use the subfield IF_CONF_NOS to specify the station name to be assigned during execution of the instruction "T_CONFIG". Byte Parameter Data type Start value Description 0 ... 1 Id UINT 40 System data type ID The start value of this parameter may not be changed. 2 ... 3 Length UINT 246 Length of the system data type IF_CONF_NOS in bytes. For an absolute length, the value for the Lenght parameter consists of: - 6 bytes for the parameter Id, Length and Mode. - up to 240 bytes for the device name (parameter NOS). Example: An overall length of 10 is the result for the device name "plc1" with a length of 4 characters (=4 bytes). Use the default start value 246 at the Lenght parameter for a dynamic length. Make sure that you enter the value "0" after the name (see description for NOS parameter). 3168 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Byte Parameter Data type Start value Description 4 ... 5 Mode UINT 0 Validity of the device name change: 1: Permanent validity of the device name. 2: Temporary validity of the device name. 6 ... 244 NOS ARRAY [1...240] of Byte 0 Device name (Name of Station) You must occupy the ARRAY from the first byte. The station name is deleted if "0" is assigned as the first byte. The minimum length for the name is 2 bytes. The maximum length for a name is 240 bytes. If the device name is shorter than specified at the parameter Length then a zero byte (16#0 hex) must be entered after the actual station name (according to IEC 61185-6-10). Otherwise NOS will be rejected and the instruction "T_CONFIG" outputs the error codeDW#16#C0809400 at the parameter STATUS. If the device name is longer than specified at the parameter Length then the device name will only be written up to to specified length. The following restrictions apply for the device name: The name must be specified in ASCII code. Only lowercase letters, numbers, hyphen or dots may be used for the name. - The name may not begin or end with a hyphen. - The name may not begin with numbers. - The name may not have the form n.n.n.n (n = 0, ... 999). - The name may not begin with the string "portxyz" or "port-xyz-abcde" (a, b, c, d, e, x, y, z = 0, ... 9). A name component between two points may be up to 63 characters long. No special characters such as umlauts, brackets, underscore, slash, blank etc. The error code C080_9400 is output at the parameter STATUS if an invalid character is used. WinCC Basic V13.0 System Manual, 02/2014 3169 Programming the PLC 9.7 References DONE, BUSY and ERROR parameters Description The following table shows the relationship between BUSY, DONE and ERROR. Using this table, you can determine the current status of the instruction and when the transfer of configuration data is concluded. BUSY DONE ERROR Description TRUE FALSE FALSE The job is being processed. FALSE TRUE FALSE Job successfully completed. FALSE FALSE TRUE The job ended with an error. The cause of the error can be found in the parameter STATUS (Page 3170). FALSE FALSE FALSE The instruction was not assigned a (new) job. Parameter STATUS and ERR_LOC Description The status and error messages of the instruction "T_CONFIG" are output at the parameters STATUS and ERR_LOC. The cause of the error is output at the parameter STATUS. The location of the error that occurred is output at the parameter ERR_LOC. The following options are available here: - 16#0000_0000: Error when calling the instruction (e.g. errors when assigning parameters to the instruction or in communication with the PROFINET interface). - 16#0001_0000: Error with the configuration data in the parameters of the system data type IF_CONF_HEADER. - 16#0001_0001: Error with the configuration data in the parameters of the system types IF_CONF_V4 or IF_CONF_NOS. The following table shows the possible values for the parameters STATUS and ERR_LOC: STATUS* ERR_LOC* Explanation 0000_0000 0000_0000 Order processing completed without errors. 0070_0000 0000_0000 No job processing active. 0070_0100 0000_0000 Start of the order processing. 0070_0200 0000_0000 Intermediate call (REQ irrelevant). C08x_yy00 0000_0000 General error information. See also: GET_ERR_ID: Get error ID locally (Page 1964) C080_8000 0000_0000 Error at call of the instruction: C080_8100 0000_0000 The hardware ID at the parameter Interface is invalid. Error at call of the instruction: The hardware ID at the parameter Interface does not address a PROFINET interface. 3170 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References STATUS* ERR_LOC* Explanation C080_8700 0000_0000 Error at call of the instruction: Incorrect length of the data block at the parameter CONF_DATA. C080_8800 0001_0000 Error in the system data type IF_CONF_HEADER: The parameter FieldType has an invalid value. Use the value "0" for FieldType. C080_8900 0001_0000 Error in the system data type IF_CONF_HEADER: The parameter FieldId has an invalid value or was used several times. Use the value "0" for FieldId. C080_8A00 0001_0000 Error in the system data type IF_CONF_HEADER: Incorrect number at the parameter SubfieldCount. Enter the correct number of system data types IF_CONF_V4 and IF_CONF_NOS in use. C080_8B00 0001_0001 Error in the system data type IF_CONF_V4 or IF_CONF_NOS: C080_8C00 0001_0001 Error in the system data type IF_CONF_V4 or IF_CONF_NOS: C080_8D00 0001_0001 The parameter Id has an invalid value. Use "30" and IF_CONF_NOS "40" for IF_CONF_V4. Incorrect data type system used, wrong order or multiple use of a system data type. Error in the system data type IF_CONF_V4 or IF_CONF_NOS: The parameter Length has an incorrect or invalid value. C080_8E00 0001_0001 Error in the system data type IF_CONF_V4 or IF_CONF_NOS: The parameter Mode has an incorrect or invalid value. Only the values "1" (permanent) or "2" (temporary) are valid. C080_9000 0001_0001 Error in the system data type IF_CONF_V4 or IF_CONF_NOS: Configuration data cannot be applied. Possible cause: The setting "Set IP address on device" or "Set PROFINET device name on device" was not selected in the hardware configuration. C080_9400 0001_0001 C080_9500 0001_0001 C080_C200 0000_0000 Error in the system data type IF_CONF_V4 or IF_CONF_NOS: A parameter value is undefined or invalid. Error in the system data type IF_CONF_V4 or IF_CONF_NOS: The values of two parameters are inconsistent. Error at call of the instruction: The configuration data can not be transferred. Possible cause: The PROFINET interface is not accessible. C080_C300 0000_0000 C080_C400 0000_0000 C080_D200 0000_0000 Error at call of the instruction: Insufficient resources (e.g., multiple calling of "T_CONFIG" with different parameters). Error at call of the instruction: Temporary communication error. Time indication for change to daylight saving time. Error at call of the instruction: Call not possible. Instruction is not supported by the selected PROFINET interface. * The error codes can be displayed as integer or hexadecimal values in the program editor. For additional information on toggling display formats, refer to "See also". WinCC Basic V13.0 System Manual, 02/2014 3171 Programming the PLC 9.7 References 9.7.5.4 Web server WWW: Synchronizing user-defined web pages Description The instruction WWW initializes the web server of the CPU or synchronizes user-defined web pages with the user program in the CPU. User-defined web pages together with the web server make it possible for the CPU to access freely designed web pages of the CPU with a web browser. Use script instructions (such as Javascript) and HTML code in user-defined web pages to transfer data via a web browser for further processing to the CPU and to display data from the operand area of the CPU in the web browser. Call the WWW instruction in the user program for synchronization of the user program and the web server as well as initialization. Initialization User-defined web pages are "packaged" in data blocks for processing by the CPU. You will have to generate appropriate data blocks from the source files (HTML files, screens, Javascript files, ...) during configuration. The Web Control DB has a special role (default: DB 333). It contains status and control information as well as links to additional data blocks with coded web pages. The data blocks with coded web pages are called fragment DBs. When the data block is downloaded into the CPU, the CPU does not "know" that user-defined web pages are coded inside it. The instruction "WWW" in the startup OB, for example, will inform the CPU which DB is the Web Control DB. The user-defined web pages can be accessed via a web browser after this initialization. Synchronization If you want the user program to interact with the user-defined web pages, then the instruction WWW must be used in the cyclical program part. Examples of interaction between user program and web page: Check received data Assemble and send back data to the web browser making the request In this case it must be possible to evaluate the current status information and the web server must receive control information, such as release of a web page requested by a web browser. 3172 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameter The following table shows the parameters of the instruction "WWW": Parameter Declaration Data type CTRL_DB Input DB_WWW D Memory area Data block that describes the user-defined web pages (Web Control DB) RET_VAL Output INT Error information I, Q, M, D, L Description For additional information on valid data types, refer to Overview of the valid data types (Page 1204). Parameter RET_VAL Error code Explanation (W#16#...) 0000 No error occurred. There are no web page requests that have to be released by the user program. 00xy x: indicates whether an error has occurred during initialization of the Web Control DB (CTRL_DB): x=0: No errors occurred. x=1: Error occurred. The error is coded in the byte "CTRL_DB.last_error" of the Web Control DB, see description of Web Control DB. y: Number of the pending request. Several requests are possible (e. g. requests "0" and "1" are pending: y="3". y="1": Request "0" y="2": Request "1" y="4": Request "2" y="8": Request "3" 803A The specified Web Control DB does not exist on the CPU. 8081 Incorrect version or incorrect format of the Web Control DB 80C1 There are no resources to initialize the web application. See also Overview of the valid data types (Page 1204) WinCC Basic V13.0 System Manual, 02/2014 3173 Programming the PLC 9.7 References 9.7.5.5 TeleService TM_MAIL: Transfer email Description of TM_MAIL Description The "TM_MAIL" instruction works asynchronously, in other words, its execution extends over multiple calls. You must specify an instance when you call the instruction "TM_MAIL". The attribute "retentive" may not be set in the instance. This attribute ensures that the instance is initialized when the CPU switches from STOP to RUN and that a new e-mail send job can be triggered afterwards. You start the sending of an e-mail with an edge change from "0" to "1" for the REQ parameter. The job status is indicated by the output parameters BUSY , "DONE", "ERROR", "STATUS" and "SFC_STATUS". "SFC_STATUS" corresponds in this case to the "STATUS" output parameter of the called communication blocks. The output parameters DONE, ERROR, STATUS, and SFC_STATUS are each displayed for only one cycle if the status of the BUSY output parameter changes from "1" to "0". The following table shows the relationship between BUSY, DONE, and ERROR. Using this table, you can determine the current status of the instruction "TM_MAILand when the sending of the e-mail is complete. DONE BUSY ERROR Description 0 1 0 The job is being processed. 1 0 0 Job successfully completed. 0 0 1 The job ended with an error. The cause of the error can be found in the STATUS and SFC_STATUS parameters. 0 0 0 The "TM_MAIL" instruction was not assigned a (new) job. If the CPU changes to STOP mode while "TM_MAIL" is active, the communication connection to the mail server aborts. The communication connection to the mail server will also be lost if 3174 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References communication problems occur on the Industrial Ethernet bus. In this case, the transfer of the e-mail will be interrupted and it will not reach its recipient. NOTICE Changing user programs You can change the parts of your user program that directly affect calls of "TM_MAIL" only: when the CPU is in "STOP" mode or when no mail is being sent (REQ = 0 and BUSY = 0). This relates, in particular, to deleting and replacing program blocks that contain "TM_MAIL" calls or calls for the instance of "TM_MAIL". Ignoring this restriction can tie up connection resources. The automation system can change to an undefined status for the TPC/IP communication functions via Industrial Ethernet. A warm or cold restart of the CPU is required after the changes are transferred. Data consistency The ADDR_MAIL_SERVER input parameter of the instruction is taken from the "TM_MAIL" instruction again each time the sending of an e-mail is triggered. If a change is made during operation, the "new" value only becomes effective once an e-mail is triggered again. In contrast, the WATCH_DOG_TIME, TO_S, CC, FROM, SUBJECT, TEXT, ATTACHMENT, and, if applicable, USERNAME and PASSWORD parameters are taken from the "TM_MAIL" instruction while it is running, which means that they may only be changed after the job is complete (BUSY = 0) Setting the parameters of the TS Adapter IE On the TS Adapter IE, you need to specify parameters for outgoing calls in such a way as to enable the TS Adapter IE to establish a connection to the dial-up server of your service provider. If you set "When required" for connection establishment, the connection will only be established when an e-mail needs to be sent. Connection establishment can take longer (approx. one minute) for an analog modem connection. When you specify the WATCH_DOG_TIME parameter, remember to allow for the time required to establish the connection. WinCC Basic V13.0 System Manual, 02/2014 3175 Programming the PLC 9.7 References Parameters The following table shows the parameters of the "TM_MAIL" instruction: Parameter Declaration Data type Memory area Description REQ Input BOOL I, Q, M, D, L or constant Control parameter REQUEST: Activates the sending of an e-mail on a rising edge. ID Input CONN_OU C (Word) D, L or constant Reference to the connection to be established. See ID parameter of the TCON (Page 3124), TDISCON (Page 3132), TSEND (Page 3137), and TRCV (Page 3140) instructions. A number that is not used for any additional instances of this instruction in the user program must be entered here. TO_S (Page 3178) Input STRING D Input parameter for receiver addresses: CC (Page 3178) Input STRING with a maximum length of 240 characters (see example call). STRING D Input parameter for CC recipient addresses (optional): STRING with a maximum length of 240 characters (see example call). If an empty string is assigned here, the e-mail is not sent to a CC recipient. SUBJECT Input STRING D TEXT Input STRING D Input parameter for subject of the e-mail: STRING with a maximum length of 240 characters. Input parameter for text of the e-mail (optional): Reference to a data string with a maximum length of 240 characters. If an empty string is assigned at this parameter, the e-mail is sent without text. ATTACHMENT Input VARIANT I, Q, M, D, L Input parameter for e-mail attachment (optional): Reference to a byte/word/double word field with a maximum length of 65534 bytes. If no value is assigned, the e-mail is sent without an attachment. DONE Output BOOL I, Q, M, D, L DONE = 0: Job not yet started or still executing. DONE = 1: Job was executed without errors. BUSY Output BOOL I, Q, M, D, L BUSY = 1: E-mail transmission is not yet complete. BUSY=0: The processing of "TM_MAIL" was stopped. ERROR Output BOOL I, Q, M, D, L ERROR=1: An error occurred during processing. STATUS and SFC_STATUS supply detailed information about the type of error. STATUS (Page 3179) Output WORD I, Q, M, D, L Output/status parameter STATUS: 3176 Return value or error information of the "TM_MAIL" instruction. WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Parameter Declaration Data type Memory area Description ADDR_MAIL_S ERVER Static* DWORD I, Q, M, D, L IP address input parameter of the mail server: Specify as a data word in HEX format, for example: IP address = 192.168.0.200. ADDR_MAIL_SERVER = DW#16#C0A800C8, where: 192 = 16#C0, 168 =16#A8 0 = 16#00 and 200 = 16#C8. WATCH_DOG_ TIME Static* USERNAME Static* TIME I, Q, M, D, L Input parameter for max. period of time: The "TM_MAIL" instruction should establish a connection within the period specified by WATCH_DOG_TIME. The block is exited with an error if this period is exceeded. The time before the block is exited and the error is output can exceed the WATCH_DOG_TIME because connection termination also takes a certain amount of time. To begin with, you should set a period of 2 minutes. If you have an ISDN telephone connection, a significantly shorter period can be selected. STRING D Input parameter for user name: STRING with a maximum length of 180 characters. A user name is an absolute requirement for authentication. PASSWORD Static* STRING D Input parameter for password: STRING with a maximum length of 180 characters. A password is an absolute requirement for authentication. FROM (Page 3178) Static* SFC_STATUS (Page 3179) Static* STRING D Input parameter for sender address: STRING with a maximum length of 240 characters (see example call). WORD I, Q, M, D, L Output/status parameter "SFC_STATUS": Error information of the called communication blocks. *The values of the parameter are not modified at every call of the instruction "TM_MAIL". The values are in the static parameters of the instance and are only written once at the first call of the instruction. You will find more detailed information on valid data types in "Overview of the valid data types (Page 1204)". Note Optional parameters The optional parameters CC, TEXT, and ATTACHMENT are only sent with the e-mail if the corresponding parameters contain a string of length > 0. WinCC Basic V13.0 System Manual, 02/2014 3177 Programming the PLC 9.7 References SMTP authentication Authentication refers here to a procedure for ensuring an identity, for example, by a password query. The "TM_MAIL" instruction supports the SMTP authentication procedure AUTH-LOGIN that is requested by most mail servers. For information about the authentication procedure of your mail server, please refer to your mail server manual or the website of your Internet service provider. To use the AUTH-LOGIN authentication procedure, the "TM_MAIL" instruction requires the user name with which it can log onto the mail server. This user name corresponds to the user name with which you set up a mail account on your mail server. It is made available to the "TM_MAIL" instruction in the USERNAME parameter. To log on, the "TM_MAIL" instruction also requires the associated password. This password corresponds to the password you specified when you set up your mail account. It is made available to the "TM_MAIL" instruction in the PASSWORD parameter. The user name and the password are each transferred to the mail server unencrypted (BASE64-coded). If no user name is specified in the DB, the AUTH-LOGIN authentication procedure is not used. The e-mail is then sent without authentication. Parameters TO_S, CC, and FROM Description The TO_S, CC, and FROM parameters are strings with, for example, the following content: TO: <wenna@mydomain.com>, <ruby@mydomain.com>, CC: <admin@mydomain.com>, <judy@mydomain.com>, FROM: <admin@mydomain.com> Note the following rules when entering the parameters: The "TO:", "CC:", and "FROM:" characters must be entered. A space and an opening pointed bracket "<" must be entered before each address. A closing pointed bracket ">" must be entered after each address. A comma must be entered after each address in TO and CC. Only one e-mail may be entered in FROM, and there must not be a comma at the end of this address Because of runtime and memory space, the "TM_MAIL" instruction does not perform any syntax check of the parameters TO_S, CC and FROM. 3178 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References STATUS and SFB_STATUS parameters Description The return values of the "TM_MAIL" instruction can be classified as follows: W#16#0000: "TM_MAIL" was completed successfully W#16#7xxx: Status of "TM_MAIL" W#16#8xxx: An error was reported during the internal call of a communication block or from the mail server. The following table shows the return values of "TM_MAIL" except for error codes of the internally called communication blocks. Return value Return value STATUS* SFB_STATUS (W#16#...): (W#16#...): 0000 - 7001 Explanation Notes The processing of "TM_MAIL" was completed without error. A without error completion of "TM_MAIL" does not mean that the sent e-mail will necessarily arrive (see below - note on point 1) "TM_MAIL" is active (BUSY = 1). Initial call; job has started 7002 7002 "TM_MAIL" is active (BUSY = 1). Intermediate call; job already active 8xxx xxxx The processing of "TM_MAIL" was completed with an error code of the internally called communication instructions. For detailed information on the evaluation of the SFB_STATUS parameter, refer to the descriptions of the STATUS parameter of the communication instructions. 8010 xxxx Error during connection establishment. For further information on the evaluation of the SFB_STATUS parameter, refer to the descriptions of the STATUS parameter of the "TCON (Page 3124)" instruction. 8011 xxxx Error sending the data. For further information on the evaluation of SFB_STATUS, refer to the descriptions of the STATUS parameter of the "TSEND (Page 3137)" instruction. 8012 xxxx Error receiving the data. For further information on the evaluation of SFB_STATUS, refer to the descriptions of the STATUS parameter of the "TRCV (Page 3140)" instruction. 8013 xxxx Error during connection establishment. For further information on the evaluation of SFB_STATUS, refer to the descriptions of the STATUS parameter of the "TCON (Page 3124)" and "TDISCON (Page 3132)" instructions. WinCC Basic V13.0 System Manual, 02/2014 3179 Programming the PLC 9.7 References Return value Return value STATUS* SFB_STATUS Explanation Notes (W#16#...): (W#16#...): 8014 - Establishment of a connection is not possible. You have possibly entered an incorrect mail server IP address (ADDR_MAIL_SERVER) or a time span that is too short (WATCH_DOG_TIME) to establish the connection. It is also possible that the CPU has no connection to the network or that the CPU configuration is incorrect. 8016 - Error copying the attachment - 82xx, 84xx, or 85xx - The error message originates from the mail server and corresponds, except for the "8", to the error number of the SMTP protocol. See point 2 in the note. The following columns list several error codes that can occur: 8450 - Action not executed: Mailbox not available/ not reachable. Try again later. 8451 - Action aborted: Local processing error Try again later. 8500 - Syntax error: Error not recognized. This also includes the error when a command string is too long. This can also be occur when the email server does not support the LOGIN authentication procedure. Check the parameters of "TM_MAIL". Try to send an e-mail without authentication. To do this, replace the USERNAME parameter with an empty string. 8501 - Syntax error: Parameter or argument incorrect You have possibly entered an incorrect address in TO_S or CC. 8502 - Command unknown or not implemented. Check your entries, in particular the FROM parameter. This is possibly incomplete and you have forgotten "@" or ".". 8535 - SMTP authentication incomplete. You have possibly entered an incorrect user name or incorrect password. 8550 - Mail server cannot be reached, you have no access rights. You have possibly entered an incorrect user name or password, or the mail server does not support your LOGIN. Another cause of error could be an incorrect entry of the domain name after the "@" in TO_S or CC. 8552 - Action aborted: Assigned memory size has been exceeded Try again later. 8554 - Transmission failed. Try again later. * The error codes can be displayed as integer or hexadecimal values in the program editor. For additional information on toggling display formats, refer to "See also". 3180 WinCC Basic V13.0 System Manual, 02/2014 Programming the PLC 9.7 References Note Status error 1. An incorrect entry of the recipient addresses does not generate a status error of the "TM_MAIL" instruction. In this case, there is no guarantee that the e-mail will be sent to other recipients, even if these were entered correctly. 2. You can find more detailed information on the SMTP error code and other error codes in SMTP protocol on the Internet or in the error documentation of the mail server. You can also view the most recent message from the mail server in your instance DB in the BUFFER1 parameter. If you look under "Data", you will find the data most recently sent by the "TM_MAIL" instruction. WinCC Basic V13.0 System Manual, 02/2014 3181 10 Visualize processes 10.1 Creating screens 10.1.1 Basics 10.1.1.1 Screen basics Introduction In WinCC you create screens that an operator can use to control and monitor machines and plants. When you create your screens, the object templates included support you in visualizing processes, creating images of your plant, and defining process values. Application example The figure shows a screen that was created in WinCC. With the help of this screen, the operator can operate and monitor the mixing station of a fruit juice manufacturing system. Fruit juice base is supplied from various tanks to a mixing unit. The screen indicates the fill level of the tanks. 7DQNV 0L[HU Screen design Insert an object you need to represent a process into your screen. Configure the object to correspond to the requirements of your process. A screen may consist of static and dynamic elements. WinCC Basic V13.0 System Manual, 02/2014 3183 Visualize processes 10.1 Creating screens Static elements such as text or graphic objects do not change their status in runtime. The tank labels (W, K, Z, A) shown in this example of a mixing unit are static elements. Dynamic elements change their status based on the process. Visual current process values as follows: - From the memory of the PLC - From the memory of the HMI device in the form of alphanumeric displays, trends and bars. Input fields on the HMI device are also considered dynamic objects. The fill level values of the tanks in our example of a mixing plant are dynamic objects. Process values and operator inputs are exchanged between the controller and the HMI device via tags. Screen properties The screen layout is determined by the features of the HMI device you are configuring. It corresponds with the layout of the user interface of this device. The screen properties such as the screen resolution, fonts and colors are also determined by the characteristics of the selected HMI device. If the set HMI device has function keys, the screen shows these function keys. A function key is a key on the HMI device. You can assign one or several functions in WinCC. These functions are triggered when the operator presses the relevant key on the HMI device. A function key can be assigned global or local functions. Global function keys always trigger the same action, regardless of the currently displayed screen. Function keys with local assignment trigger different actions, based on the currently displayed screen on the operator station. This assignment applies only to the screen in which you have defined the function key. Opening screens In order for the operator to be able to call a screen in runtime, you must integrate each configured screen in the operating process. You have various options of configuring these functions: You use the "Screen" editor to configure buttons and function keys for opening other screens. You use the "Global Screen" editor to configure globally assigned function keys. 10.1.1.2 Device-specific functional scope of screens Introduction The functions of an HMI device determine the display of the device in WinCC and the scope of functions of the editors. The following screen properties are determined by the functions of the selected HMI device: 3184 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.1 Creating screens Device layout Screen resolution Number of colors Fonts Objects available Device layout The device layout of a screen forms the image of the HMI device in your configuration. The device layout of the screen shows all the function keys available on the HMI device, for example. Screen resolution The screen resolution is determined by the different display dimensions of the various operator panels. You can only change the screen resolution if you configure the "WinCC Runtime Advanced" or "WinCC Runtime Professional" HMI device. Number of colors You can assign colors to the screen objects. The number of possible colors is determined by the color depth and specific colors supported on the selected HMI device. Fonts You can customize the appearance of the texts in all the screen objects that contain static or dynamic text. How to highlight individual texts in a screen. Select the font, font style and size, and set additional effects such as underscoring, for example. WinCC Basic V13.0 System Manual, 02/2014 3185 Visualize processes 10.1 Creating screens The settings for the text markups such as font style and effects always refer to the entire text of a screen object. That is, you can display the complete title in bold format, but not its individual characters or words, for example. Objects available Some of the screen objects can not be configured globally for all HMI devices. These screen objects are not displayed in the "Tools" task card. For a KTP 1000 touch panel unit you can not configure a slider, for example. 10.1.1.3 Basics Task cards Introduction The following task cards are available in the "Screens" editor: Tools: Display and operating objects Animations: Templates for dynamic configuration Layout: Aid for customizing the display Libraries: Administration of the project library and of the global libraries Note WinCC Basic The "Animations" task card is not available in WinCC Basic. Tools The "Tools" task card contains objects in different panes: Basic objects Elements Controls User controls (optional) Graphics You paste objects from the palettes into your screens by drag&drop or a double click. The objects available for selection are determined by the features of the HMI device you are configuring. The following icons are used to change the display mode: 3186 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.1 Creating screens Icon Meaning Displays the objects as a list. Displays the objects as a graphic. Animations The "Animations" task card contains the possible dynamizations of a screen object in the palettes. You paste the animations to a screen object by drag&drop or a double click from the "Movements", "Display" and "Tag Binding" palettes. Layout The "Layout" task card contains the following panes for displaying objects and elements: Layers: Serves to manage screen object layers The layers are displayed in a tree view and contain information about the active layer and the visibility of all layers. Grid: You specify whether you want to align the objects to a grid or to other objects and set the grid size for a grid. Objects out of range: Objects that lie outside the visible area are displayed with name, position and type. Libraries The "Libraries" task card show the following libraries in separate panes: Project library: The project library is stored together with the project. Global library: The global library is stored in a separate file in the specified path on your configuration PC. Move view Introduction To display only a section of the entire screen in the work area, use the editor: icon of the "Screens" Requirement A screen is open. The view shows only a screen section. WinCC Basic V13.0 System Manual, 02/2014 3187 Visualize processes 10.1 Creating screens Procedure To move the view: 1. Click the icon at the bottom right corner of the work area and press the left mouse button. A miniature view of the full screen is shown. An orange frame shows the currently selected area. 2. Hold down the mouse button and drag the frame to the desired area. Note The screen is scrolled when you drag a screen object from the visible to a currently hidden section. Zooming the view Introduction To view a small screen section in closer detail, use the zoom tool to magnify the screen in the working area. The maximum zoom amounts to 800%. You can zoom with the toolbar in the work area or with the "Layout > Zoom" task card. There are different ways to increase the screen, for example, with the zoom factor or by adapting the work area to the height of the screen. Requirement The screen is opened. Procedure Proceed as follows to zoom a view with the selection frame: 1. Click the toolbar button. 2. Use the mouse to draw a selection frame in the screen. After you have released the mouse button, the section enclosed by the selection frame is zoomed to fit the complete work area. Alternatively, use the slider in the lower right-hand corner of the screen. Result The selected screen section is magnified. 3188 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.1 Creating screens 10.1.1.4 Working with screens Steps Steps To create screens, you need to take the following initial steps: Plan the structure of the process visualization: Number of screens and their layout Example: Subprocesses are visualized in separate screens, and merged in a master screen. Define your screen navigation control strategies. Adapt the templates and the global screen. You define objects centrally and assign function keys for example. Create the screens. Use the following options of efficient screen creation: - Working with libraries - Working with layers - Working with faceplates Creating a new screen Introduction Create screens to display processes in your system. Requirement The project has been created. The Inspector window is open. WinCC Basic V13.0 System Manual, 02/2014 3189 Visualize processes 10.1 Creating screens Procedure 1. Double-click "Screens > Add New Screen" in the project navigation. The screen is generated in the project and appears in your view. The screen properties are shown in the Inspector window. 2. Enter a meaningful name for the screen. 3. Configure the screen properties in the Inspector window: - Specify whether and on which template the screen is based. - Set the "Background Color" and the "Screen Number." - Specify a documenting text under "Tooltip". - Specify the layers to be displayed under "Layers" in the engineering system. - Select dynamic screen update under "Animations." - Select "Events" to define which functions you want to execute in Runtime when you call and exit the screen or at other events. Note Not all HMI devices support the "Visibility" animation. Result You created the screen in your project. You can now paste objects and control elements from the "Tools" task card and assign function keys in further work steps. Managing Screens Introduction You can move screens within a project to other groups, or copy, rename, and delete them. Moving screens in a group 1. Select the "Screens" folder in the project tree. 2. Select the "Add group" command from the shortcut menu. A folder called "Group_x" is inserted. 3. Select the screen in the project tree. 4. Drag-and-drop the screen to the required group. The screen is moved into this group. Copy screen 1. Select the screen in the project tree. 2. Select the "Copy" command in the shortcut menu to copy the screen to the clipboard. 3190 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.1 Creating screens 3. In the project tree, select the screen insert position. 4. Select "Paste" from the shortcut menu to insert the screen. A copy of the screen is inserted. A consecutive number is appended to the name of the original in the copy. Alternatively, press <Ctrl> while you drag the screen to the required position. Note If you copy a screen with interconnected template for several devices and projects, the template will also be copied. Any existing matching template is not used. This holds particularly true when you copy the screens with drag-and-drop. Rename screen 1. Select the screen in the project tree. 2. Select "Rename" from the shortcut menu. 3. Type in a new name. 4. Press <Enter>. As an option, use the <F2> function key to rename the screen. Delete screen 1. Select the screen in the project tree. 2. Select "Delete" from the shortcut menu. The screen and all its objects are deleted from the current project. Defining the start screen of the project Introduction The start screen is the initial screen opened at the start of project in Runtime. You can define a different start screen for each one of the HMI devices. Beginning at this start screen, the operator calls the other screens. Requirement The project contains the screen you want to use as the start screen. WinCC Basic V13.0 System Manual, 02/2014 3191 Visualize processes 10.1 Creating screens Procedure 1. Double-click "Runtime settings > General" in the project tree. 2. Select the desired screen as "Start screen". Alternatively select a screen in the project tree and select "Use as start screen" in the shortcut menu. Result The start screen opens on the HMI at the start of Runtime. 10.1.1.5 Working with Templates Basics on working with templates Introduction Configure the objects in a template which are to be displayed in all screens based on this template. Note the following rules: 3192 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.1 Creating screens A screen must not be based on a template. A screen is only based on one template. You can create several templates for one device. A template cannot be based on another template. Objects for a template You determine functions and objects in the template which are to apply for all screens based on this template: Assignment of function keys: You also assign the function keys in the template for HMI devices with function keys. This assignment overwrites a possible global assignment. Permanent window: Some devices support a permanent window for all screens in the top area of the screen. In contrast to the template, the permanent window occupies an area of the screen for itself alone. Operator controls: You can paste all screen objects which you also use for a screen into a template. Application examples You want to assign the ActivateScreen" function to a function key in the template. The operator uses this key to switch to another screen in runtime. This configuration applies to all screens that are based on this template. A graphic with your company logo can be added to the template. The logo appears on all screens that are based on this template. Note If an object from the template has the same position as an object in the screen, the template object is covered. See also Creating a new template (Page 3195) Managing templates (Page 3196) Global screen (Page 3193) Using a template in the screen (Page 3197) Global screen Introduction You define global elements for all screens of an HMI device independently of the used template. WinCC Basic V13.0 System Manual, 02/2014 3193 Visualize processes 10.1 Creating screens Function keys For HMI devices with function keys you assign the function keys globally in the "Global Screen" editor. This global assignment applies for all screens of the HMI device. Proceed as follows to assign function keys locally in screens or templates: 1. Click the function key in your screens or templates. 2. Deactivate "Properties > Properties > General > Use Global Assignment" in the inspection window. Indicator and control objects for alarms The "Alarm window" and "Alarm indicator" objects that are available as global objects are configured within the "Global screen" editor. The "Alarm window" and "Alarm indicator" are always shown in the foreground. For Comfort Panels you also have the possibility of configuring a "System diagnostic view" in the global screen. Note If you have configured a permanent window in a template, do not position the alarm window and alarm indicator in the area of the permanent window. Otherwise, the alarm window and the alarm indicator will not be displayed in Runtime. The permanent window is not visible in the "Global screen" editor. 3194 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.1 Creating screens Order of configuration of screens The following order applies for the configuration: The global screen comes before screens and templates Screens come before templates 7HPSODWH 6FUHHQ 6FUHHQ *OREDOVFUHHQ 6\VWHP /D\HU /D\HU /D\HU The system layer is not configurable. This contains input dialog boxes alarms from the operating system the direct keys for touch panels See also Basics on working with templates (Page 3192) Creating a new template Introduction In a template, you can centrally modify objects and function keys. 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. Note HMI device dependency Function keys are not available on all HMI devices. WinCC Basic V13.0 System Manual, 02/2014 3195 Visualize processes 10.1 Creating screens Requirement The project has been created. The Inspector window is open. Procedure 1. Select "Screen management > Templates" in the project tree and then double-click "Add new template". The template is created in the project, and appears in your view. The properties of the template are displayed in the Inspector window. 2. Define the name of the template under "Properties > Properties > General" in the Inspector window. 3. Specify the layers in the engineering system that are displayed under "Properties >Properties >Layers" in the Inspector window. 4. Add the necessary objects from the "Tools" task card. 5. Configure the function keys. Result The template is created in your project. See also Basics on working with templates (Page 3192) Managing templates Introduction You can move, copy, rename, and delete templates within a project in the Project window. Moving a template into a group 1. Select the templates in the project navigation "Screen management > Templates". 2. Select "Add group" in the shortcut menu. A folder called "Group_x" is inserted. 3. Select the template in the project navigation. 4. Drag-and-drop the template to the required group. The template is moved to this group. 3196 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.1 Creating screens Copying templates 1. Select the template in the project navigation. 2. Select "Copy" in the shortcut menu. 3. Select the position in the project navigation where you want to paste the template. 4. Select "Paste" from the shortcut menu to insert the template. A unique name is assigned automatically to the copy. Alternatively, you can hold down the <Ctrl> key, and drag the template into position. Deleting a template 1. In the project navigation, select the template to be deleted. 2. Select "Delete" in the shortcut menu. The template, and all its objects are deleted from the current project. Assigning a template to a screen 1. In the project navigation, select the screen to which you want to assign the template. 2. In the Inspector window, select "Properties > Properties > General". 3. Select the desired template under "Template." The selected template and all the objects contained in it are assigned to the screen. See also Basics on working with templates (Page 3192) Using a template in the screen Introduction You use a template in the screen. All the objects configured in the template are also available in the screen. Requirement A template has been created. A screen has been created. WinCC Basic V13.0 System Manual, 02/2014 3197 Visualize processes 10.1 Creating screens Procedure Proceed as follows to use a template in a screen: 1. Double click a screen in the project tree. The screen opens in the work area. 2. Open "Properties > Properties > General" in the inspector window. 3. Select a template that is to be applied to the screen under "Template". Show template in screen When you edit a screen, you can show an existing template in the screen. Proceed as follows to show a template in the screen: 1. Activate "Extras > Settings > Visualization > Show template in screens" in the menu. Result The screen is based on the selected template. All objects which you have configured in the template are available in the screen. The template is displayed in the screen. See also Basics on working with templates (Page 3192) 10.1.1.6 Working with styles Basics on working with styles Introduction The style editor is a global editor. You define a uniform appearance for display and operating elements in the style editor. In this way, you harmonize the display of objects in Runtime. The style editor offers predefined styles. You can choose one of the predefined styles or create your own style. You use the style editor independently of devices and projects. Views in the style editor Objects are grouped in the style editor according to their main visual features. The following groups are available: Buttons, lines, and polygon-based objects Text-based objects Trend-based objects, such as trend view Graphic or value-based objects, such as value table. 3198 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.1 Creating screens Displaying predefined styles Introduction In the "Style" editor, you see predefined styles and create your own styles for representing display and operating objects in Runtime. Open "Styles" editor 1. Double-click "Common data" in the project navigation. 2. Click the "Styles" editor. The editor opens. Note Style editor in the project navigation The style editor is only visible in the project navigation if a device that supports styles, e.g., Comfort Panels, is created in the project. 3. The standard styles are displayed in the work area of the "Style" editor: WinCC Light WinCC Dark WinCC Fresh WinCC Wireframe. Result The settings for the groups and individual objects are displayed in the work area. You will assign predefined styles or define your own styles in the next steps. Predefined styles are write-protected and cannot be changed. Managing styles Deleting a style You can delete styles that you have defined yourself. 1. Open the "Common data" folder in the project navigation. 2. Open the "Style" editor. 3. Select the style in the work area that you want to delete. Note You cannot delete the predefined styles of WinCC. 4. Select the "Delete" command in the shortcut menu. WinCC Basic V13.0 System Manual, 02/2014 3199 Visualize processes 10.1 Creating screens The style is deleted. Editing a style You can edit styles that you have defined yourself. 1. Open the project library. 2. Select the released version of the style that you want to change. 3. Select "Edit type" in the shortcut menu. A new version "in progress" is created. 4. Make the required changes in the Inspector window. 5. Select the "Release version" command from the shortcut menu of the edited version to put the changes into effect. The changes made take effect. Determining a standard style for a project A project can be assigned a standard style to achieve a visual conformity of all display objects in the project. 1. Open the "Common data" folder in the project navigation. 2. Open the "Style" editor. 3. Activate a style in the work area. The activated style is used as standard style in the project. When you add a device to the project, this device uses the standard style. Changing the style for a specific device Within a project, you change the style for a specific device. 1. Open the "Runtime settings" editor of the HMI device. 2. Select a device style under "General". The selected style is applied to the device. If the device style is not assigned, the device uses the standard style of the project. 10.1.2 Working with objects 10.1.2.1 Overview of objects Introduction Objects are graphics elements which you use to design the screens of your project. 3200 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.1 Creating screens The "Tools" task card contains all objects that can be used for the HMI device. Display the Task Card with menu command "View" by activating the "Task Card" option. The toolbox contains various palettes, depending on the currently active editor. If the "Screens" editor is open, the toolbox contains the following palettes: "Basic objects" The basic objects include basic graphic objects such as "Line", "Circle", "Text field" or "Graphic view". "Elements" The elements include basic control elements, e.g. "I/O field", "Button" or "Gauge". "Controls" The controls provide advanced functions. They also represent process operations dynamically, for example Trend view and Recipe view. "Graphics" Graphics are broken down into subjects in the form of a directory tree structure. The various folders contain the following graphic illustrations: - Machine and plant areas - Measuring equipment - Control elements - Flags - Buildings You can create links to your own graphic folders. The external graphics are located in these folders and subfolders. They are displayed in the toolbox and incorporated into the project using links. "Libraries" task card In addition to the display and operating elements, the library objects are available. They are located within the palettes of the "Libraries" task card. A library contains preconfigured objects such as graphics of pipes, pumps, or preconfigured buttons. You can also integrate multiple instances of library objects into your project without having to reconfigure them. The WinCC software package includes libraries, e.g. "HMI Buttons & Switches". You can also store customized objects, and faceplates in user libraries. Faceplates are objects that you create from existing screen objects, and for which you define the configurable properties. Note HMI device dependency Some of the toolbox objects are either available with restricted functionality, or not at all. This depends on the HMI device you are configuring. Unavailable properties of an object are displayed as deactivated, and cannot be selected. WinCC Basic V13.0 System Manual, 02/2014 3201 Visualize processes 10.1 Creating screens Basic objects Icon Object Instructions "Line" - "Ellipse" - "Circle" - "Rectangle" - "Text field" One or more lines of text. The font and layout are adjustable. "Graphic view" Displays graphics from external graphic programs, and inserts OLE objects. The following graphic formats can be used: "*.emf", "*.wmf", "*.dib", "*.bmp", "*.jpg", "*.jpeg", "*.gif" and "*.tif". Elements Icon Object Instructions "I/O field" Outputs the values of a tag, and/or writes values to a tag. You can define limits for the tag values shown in the I/O field. To hide the operator input in runtime, configure "Hidden input". "Button" Executes a function list, or a script as configured. "Symbolic I/O field" Outputs the values of a tag, and/or writes values to a tag. A text from a text list is displayed in relation to the tag value. "Graphic I/O field" Outputs the values of a tag, and/or writes values to a tag. A graphic from a graphics list is displayed in relation to the tag value. "Date/time field" Outputs the system date and time, or the time and date from a tag. This allows the operator to enter new values. The display format is adjustable. "Bar" The bar represents a value from the PLC in the form of a scaled bar graph. "Switch" Toggles between two defined states. You can label a switch with text, or a graphic. Controls Icon Object Description "Alarm view" Shows currently pending alarms or alarm events from the alarm buffer or alarm log. "Trend view" Represents multiple curves with values from the PLC, or from a log. "User view" Allows an administrator to administer users on the HMI device. It also allows an operator without administrator rights to change his password. 3202 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.1 Creating screens Icon Object Description "Recipe view" Displays data records, and allows them to be edited. "System diagnostics view" Provides an overview of all devices capable of diagnostics. Displays errors in the plant. See also Inserting an object (Page 3204) Positioning an object (Page 3207) Resizing an object (Page 3208) Selecting multiple objects (Page 3210) Aligning objects (Page 3212) Moving an object forward or backward (Page 3213) Show objects outside the screen area (Page 3214) Rotating objects (Page 3215) Flipping objects (Page 3217) Inserting multiple objects of the same type (stamping tool) (Page 3228) Repositioning and resizing multiple objects (Page 3230) External graphics (Page 3230) Managing external graphics (Page 3231) Storing an external image in the graphics library. (Page 3233) Basics on groups (Page 3235) Overview of keyboard access (Page 3242) Example: Inserting and configuring a rectangle (Page 3244) Objects for Basic Panels (Page 3297) 10.1.2.2 Options for Editing Objects Introduction Objects are graphics elements which you use to design the screens of your project. You have the following options for editing objects: Copying, pasting or deleting objects using the shortcut menu If you copy an object in a screen and the screen already includes an object of the same name, the name of the object is changed. Maintaining the standard size of the objects you are inserting or customizing their size on insertion. WinCC Basic V13.0 System Manual, 02/2014 3203 Visualize processes 10.1 Creating screens Moving an object in front of or behind other objects Rotating objects Mirroring objects Defining the tab sequence for objects Stamping: Inserting several objects of the same type Selecting several objects simultaneously Repositioning and resizing multiple objects You can assign external graphics to objects, e.g. in the Graphic View. You can view only the images you have previously stored in the graphic browser of your WinCC project. You can save graphics in the graphic browser: - Via drag & drop from the "Graphics" object group to the working area - As graphic files in the following formats: *.bmp, *.dib, *.ico, *.emf, *.wmf, *.gif, *.tif, *.jpeg or *.jpg - As an OLE object You either create a new OLE object or save an existing graphic file as an OLE object. To save an OLE object, an OLE-compatible graphics program must be installed on the configuration computer. See also Overview of objects (Page 3200) 10.1.2.3 Inserting an object Introduction In the "Screens" or "Reports" editor, insert the objects to the "Toolbox" task card. Use the mouse to drag the objects into the work area. You either keep the objects in their original size, or scale them up or down when you paste them. In addition, you can copy or move objects via the clipboard from one editor to another, for example to transfer a screen object to a report. Alternatively, you can also use the mouse instead of the clipboard for copying and moving: Copying: <Ctrl + Drag&Drop> Moving: Drag&drop Note Basic Panels The "Reports" editor is not available for Basic Panels. 3204 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.1 Creating screens Requirement The "Tools" task card is open. Inserting objects in their standard size 1. In the "Toolbox" task card, select the desired graphic object or the desired graphic in the WinCC graphics folder. When you move the cursor across the work area, it turns into a crosshair with an appended object icon. 2. Click the location in the work area where you want to insert the object or graphic. The object is inserted with its standard size at the desired position in the work area. Alternatively, double-click the object in the "Toolbox" task card. Copying an object 1. Select the desired object. 2. Select "Copy" in the shortcut menu. 3. Click the desired location and select "Paste" in the shortcut menu. WinCC inserts a copy of the object at the desired location. You can only change the properties that are appropriate for the relevant context. Example: In the "Screens" editor, you can set for I/O fields and the mode for input and output. In the "Reports" editor, the mode is set to "Output". Original and copy are not interconnected and are configured independently from one another. Inserting lines 1. Select the desired graphic object in the "Tools" task card. 2. Click on a location in the work area. A line in the standard size is inserted. Inserting a polygon or polyline 1. Select the desired object "Polyline" or "Polygon" in the "Tools" task card. 2. Click on a location in the work area. This fixes the starting point of the object. 3. Click another location in the work area. A corner point is set. 4. For every additional corner point, click on the corresponding location in the work area. 5. Double-click on a location in the work area. The last corner point is set. This fixes all the points of the polygon or polyline. Note Basic Panels The "Polyline" and "Polygon" objects are not available for Basic Panels. WinCC Basic V13.0 System Manual, 02/2014 3205 Visualize processes 10.1 Creating screens Note If you want to insert several objects of the same type, use the "Stamp" function. This avoids having to reselect the object in the "Tools" task card every time before inserting it. To do so, select the icon in the toolbar of the "Tools" task card. See also Overview of objects (Page 3200) 10.1.2.4 Deleting an Object Introduction You can delete objects individually or with a multiple selection. Requirement You have opened the work area containing at least one object. Procedure 1. Select the object that you want to delete. To delete multiple objects, keep the <Shift> key pressed and select the objects to be deleted one after the other. Alternatively, drag and maximize an area around the desired objects with the mouse. 2. Select "Delete" from the shortcut menu. Result The selected objects are deleted. See also Overview of objects (Page 3200) 3206 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.1 Creating screens 10.1.2.5 Positioning an object Introduction When you select an object, it is enclosed by a rectangle with resizing handles. This rectangle is the rectangle which surrounds the object. The position of an object is defined by the coordinates of the top left corner of the rectangle surrounding the object. Note If the position is outside the work area the object is not displayed in Runtime. Position and align You have the possibility of having a grid displayed in the work area. You have three options for easier positioning of objects: "Snap to grid" When you resposition objects, they are automatically snapped and pasted to the grid. If you hold down the <Alt> key, the object is no longer snapped to the grid. "Snap to objects" When you reposition objects, they are displayed with help lines. You can use other objects for orientation during positioning. "None": You position the objects in any position. You activate and deactivate the grid and options as follows: In the "Options > Settings > Visualization > Screens" menu In the "Layout > Grid" task card Requirement You have opened the work area containing at least one object. Procedure 1. Select the object you want to move. The selected object is framed by a rectangle with resizing handles. 2. Left-click the object and keep the mouse button pressed. WinCC Basic V13.0 System Manual, 02/2014 3207 Visualize processes 10.1 Creating screens 3. Move the mouse pointer onto the new position. The contour of the object moves with the mouse and displays the new position for the object. The object initially remains at its original position. 4. Now release the mouse button. The object is moved into the position indicated by the contour of the selection rectangle. Alternative procedure 1. In the Inspector window, select "Properties > Properties > Layout". 2. Enter the X and Y values for the position under "Position & Size". Result The object appears at its new position. See also Overview of objects (Page 3200) 10.1.2.6 Resizing an object Introduction When you select an object, it is enclosed by a rectangle with handles. You have the following options of resizing an object: Drag the handles using the mouse. Modify the "Size" property in the Inspector window. Requirement You have opened the work area containing at least one object. 3208 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.1 Creating screens Procedure 1. Select the object you want to resize. The selection rectangle appears. The following figure shows a selected object: 2. Drag a resizing contact of the rectangle to a new position. The size of the object changes. - The size of the object is aligned to the grid pattern, provided the "Snap to grid" function is set. - Press <ALT> to disable this function while you drag the object. In order to scale the object proportionally, keep the <Shift> key pressed while changing the size with the mouse. Alternative procedure 1. In the Inspector window, select "Properties > Properties > Layout". 2. Enter the size of the object under "Position & Size". Harmonizing the object size 1. Select the objects. 2. Now, click one of the following buttons: or or The size of the selected objects is matched to each other. The following screen shows how the selected objects are adapted to the height of the reference object: WinCC Basic V13.0 System Manual, 02/2014 3209 Visualize processes 10.1 Creating screens Icon Description Aligns the selected objects to the width of the reference object. Aligns the selected objects to the height of the reference object. Aligns the selected objects to the width and height of the reference object. Result The object now appears with its new size. See also Overview of objects (Page 3200) 10.1.2.7 Selecting multiple objects Introduction Select all objects you want to align with each other or to change global properties. This procedure is called "multiple selection." The Inspector window shows all the properties of the selected objects. You now have several options of selecting multiple objects: Draw a selection frame around the objects. Hold down the <Shift> key, and click the required objects. Selection frame of a multiple selection The selection frame surrounds all objects of a multiple selection. The selection frame is comparable with the rectangle that surrounds an individual object. The selection frame is not visible. When you have made your multiple selection, the following frame is displayed: The reference object is indicated by the rectangle around it. The other selected objects are indicated by a dashed-line frame. 3210 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.1 Creating screens Specifying a reference object The reference object is the object upon which the other objects are oriented. The reference object is framed by a rectangle with handles. The following figure shows a reference object with two other selected objects: You have the following options to specify the reference object: Select the objects via multiple selection. The object selected first is then the reference object. Draw a selection frame around the objects. The reference object compiled automatically. If you wish to specify a different object within the selection as the reference object, click on the desired object. This action does not cancel your multiple selection. Requirement You have opened the work area containing at least two objects. Selecting multiple objects with a selection frame 1. Position the mouse pointer in the work area close to one of the objects to be selected. 2. Hold down the mouse button, and draw a selection frame around the objects to be selected. Or: 1. Hold down the <Shift> key. 2. Click the relevant objects, working in succession. All the selected objects are identified by frames. The object selected first is identified as reference object. Note To remove an object from the multiple selection, press <SHIFT>, hold it down and then click the relevant object once again. Result Multiple objects are selected. One of those is identified as the reference object. You can now perform the following steps: Changing the object properties of all the objects Resizing all the objects by the same ratio, by dragging the selection frame to increase or reduce the size WinCC Basic V13.0 System Manual, 02/2014 3211 Visualize processes 10.1 Creating screens Moving all the objects in one group Aligning the objects to the reference object See also Overview of objects (Page 3200) 10.1.2.8 Aligning objects Procedure 1. Select the objects via multiple selection. 2. Specify an object as the reference object. 3. Select the desired command in the toolbar or the shortcut menu - see table below. The selected objects will be aligned. Aligning objects flush The selected objects will be aligned flush to the reference object. Icon Description Aligns the selected objects to the left edge of the reference object. Aligns the selected objects to the vertical center axis of the reference object. Aligns the selected objects to the right edge of the reference object. Aligns the selected objects to the upper edge of the reference object. Aligns the selected objects to the horizontal center axis of the reference object. Aligns the selected objects to the lower edge of the reference object. Centers the selected objects to the center points of the reference object. Centers the selected objects vertically in the screen. Snap to object When you reposition objects, they are displayed with help lines. You can use other objects for orientation during positioning. If you are working with the keyboard, press the Alt key. When you move the selected object with the arrow keys, the next anchor point is displayed. 3212 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.1 Creating screens Distributing objects evenly You need at least three selected objects. A reference object is not required. 1. Select the objects. 2. Click one of the buttons "Distribute horizontally equal" or "Distribute vertically equal". The selected objects are distributed at equal distances. The following screen shows how you align the vertical spacing of the selected objects: Icon Description Aligns the horizontal distance between the objects. The position of the objects on the extreme left and right side remains unchanged. All other objects are distributed evenly between them. Aligns the vertical distance between the objects. The position of the objects at the extreme top and bottom (right and left) remains unchanged. All other objects are distributed evenly between them. See also Overview of objects (Page 3200) 10.1.2.9 Moving an object forward or backward Introduction You can use the "Order" functions in the shortcut menu of a selected object or in the toolbar to move a selected object in front of or behind other objects within an object layer. Note ActiveX controls are always positioned in front of an object layer (.NET property). Requirement You have opened a screen which contains a layer with multiple objects. WinCC Basic V13.0 System Manual, 02/2014 3213 Visualize processes 10.1 Creating screens Procedure 1. Select the object you want to move forward or backward. 2. Select the "Sort" command and one of the following commands from the shortcut menu: Icon Description Moves the selected object before all the other objects of the same layer Moves the selected object to the lowest position in the same layer Moves the selected object up by one position Moves the selected object down by one position Alternative procedure 1. Open the "Layers" palette of the "Layout" task card. 2. Navigate to the required object. 3. Hold down the mouse button, and drag the object in the tree topology to the required position in the layer. 4. Now release the mouse button. Result The object is moved up or down. See also Overview of objects (Page 3200) 10.1.2.10 Show objects outside the screen area Introduction If you assign objects to positions that are outside the configurable area, these objects will be hidden. The functions of the "Objects outside the visible area" palette in the "Layout" task card are used to move these objects back into the screen. Requirement You have opened a screen which contains objects that are outside the configurable area. The "Layout" task card is open. 3214 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.1 Creating screens Procedure 1. Open the "Layout > Objects outside the area" task card. This displays a list of objects that are outside the configurable area. 2. Select the the object which you want to move back into the screen from the list. 3. Select "Move to screen" in the object shortcut menu. Alternatively open the "Layout > Layer" task card. Objects outside the area are indicated by the icon. If you click this icon, the object is moved back into the screen. Result The objects are moved to the configurable area. See also Overview of objects (Page 3200) 10.1.2.11 Rotating objects Introduction You can rotate a suitable object clockwise or counterclockwise around its center axis in steps of 90. Note Not all the objects can be rotated. Some objects that can be rotated in screens cannot be rotated in reports. You can also rotate multiple objects using the multiple selection function. Certain WinCC objects such as buttons cannot be rotated. The alignment of elements in an object will change in a rotated object. The following figure shows how a rectangle and an ellipse behave under the different commands for rotating an object: WinCC Basic V13.0 System Manual, 02/2014 3215 Visualize processes 10.1 Creating screens rWRWKHULJKW rWRWKHOHIW rWRWKHULJKW [rWRWKHULJKW Requirement You have opened the work area containing at least one object. Procedure 1. Select the object that you want to rotate. 2. Click one of the following toolbar icons: , to rotate the object clockwise around its center point. The angle of rotation is 90. , to rotate the object counterclockwise around its center point. The angle of rotation is 90. , to rotate the object clockwise by 180. Result The object is shown at its new angle. See also Overview of objects (Page 3200) Ellipse (Page 3303) 3216 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.1 Creating screens 10.1.2.12 Flipping objects Introduction You can flip an object along its vertical or horizontal center axis. The alignment of elements in an object will change when you flip an object. The following figure shows how a rectangle and an ellipse behave under the different commands for flipping an object. KRUL]RQWDO YHUWLFDO KRUL]RQWDOYHUWLFDO Requirement You have opened a screen which contains at least one object. Procedure 1. Select the object that you want to flip. 2. Click the "Flip" command in the shortcut menu and select one of the options displayed: - , to flip the selected object along its vertical center axis. - , to flip the selected object along its horizontal center axis. Result The object is shown at its flipped position. See also Overview of objects (Page 3200) Ellipse (Page 3303) 10.1.2.13 Designing an object Introduction You design the border and background of an object. WinCC Basic V13.0 System Manual, 02/2014 3217 Visualize processes 10.1 Creating screens Requirements A line has been created in a screen. Procedure 1. Select the line on your screen. 2. In the Inspector window, select "Properties > Properties > Appearance": 3. Select "Dash" as the style. 4. To display the dashed line in two colors, select the line width "1". 5. Select the setting "Arrow" in the "Line ends" area. Result The line is displayed in two colors as a dashed line. The end of the line is an arrow. 10.1.2.14 Designing the fill pattern Introduction WinCC lets you design the background color and the fill pattern of an object. The design options change in the Inspector window depending on object for which you are making the filling pattern. For certain objects, you can not only define the color, but also a transparent background or a background with a color gradient. Note Device-specific nature of the properties The fill style that is available depends on the object and the HMI device used. Requirement The object has been created and selected. 3218 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.1 Creating screens Designing the background color of an object 1. In the Inspector window, select "Properties > Properties > Appearance". 2. Select a color for the background of the object, for example, yellow. The object is filled with the selected color. WinCC Basic V13.0 System Manual, 02/2014 3219 Visualize processes 10.1 Creating screens Designing the fill pattern of an object 1. In the Inspector window, select "Properties > Properties > Appearance". 2. To define a transparent background for the object, select transparent. You can find information about designing a fill pattern with a color gradient in the section Defining color gradients (Page 3226). The object is shown as transparent. 3220 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.1 Creating screens You can optionally set the fill pattern in the Inspector window under "Properties > Properties > Fill Pattern". See also Defining color gradients (Page 3226) 10.1.2.15 Formatting graphics in an object Introduction WinCC lets you insert graphics into some objects and format them. You can change the size, orientation and distances of a graphic to the object border. You change the properties of the graphic in the Inspector window of the relevant object. Requirement The selected object is in graphic mode. The selected object contains at least one graphic. Resizing a graphic 1. In the Inspector window, select "Properties > Properties > Layout". 2. Select "No stretching of picture" or "Stretch picture". The contained graphic is displayed in its original size or stretched to the size of the object. Note To adjust the object size to the contained graphic, select "Fit object to contents". Aligning a graphic horizontally and vertically 1. In the Inspector window, select "Properties > Properties > Layout". 2. To determine the horizontal position of the graphic, select "Right", for example. 3. To determine the vertical position of the graphic, select "Top", for example. The graphic is then shown at the top right of the object. WinCC Basic V13.0 System Manual, 02/2014 3221 Visualize processes 10.1 Creating screens Defining the distance from the object border 1. In the Inspector window, select "Properties > Properties > Layout". 2. Enter the value for the distance to the object border, for example, "20" for the top border. The graphic is shown with a distance of 20 pixels to the top border of the object. Icon Description Sets the distance from the left border of the object. Sets the distance from the right border of the object. Sets the distance from the top border of the object. Sets the distance from the bottom border of the object. See also Button (Page 3321) Switch (Page 3320) 10.1.2.16 Formatting text in an object Introduction Some objects, for example, the I/O field, support text within the object. You have several options to align text. 3222 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.1 Creating screens Configuring the distance from the object border 1. In the Inspector window, select "Properties > Properties > Layout". 2. Enter the value "5" for the left border, for example. The text is aligned five pixels from the left border of the object. Aligning the text position 1. In the Inspector window, select "Properties > Properties > Text format". 2. Select the horizontal alignment, for example, centered. 3. Select the vertical alignment, for example, top. The text is shown at the top center in the object. Defining the text orientation 1. In the Inspector window, select "Properties > Properties > Text format". 2. Select the orientation of the text, for example, vertical, right. The text flow is shown from bottom to top. 10.1.2.17 Designing table-based objects Introduction WinCC offers various properties for designing display and operating objects. You change the properties of table-based objects in the Inspector window of the relevant object. Designing colors Select the colors for font, selections and areas under "Properties > Properties > Appearance". 7DEOHKHDGHU )RUHJURXQGFRORU $OWHUQDWLYHFRORU Figure 10-1 Selecting table properties Designing the border of the table header 1. In the Inspector window, open "Properties > Properties > Table header border". 2. Select "Solid", for example, as the style. WinCC Basic V13.0 System Manual, 02/2014 3223 Visualize processes 10.1 Creating screens 3. Select 5, for example, as the "Width". 4. Select red, for example, as a foreground color. The border of the table header is shown with a red border and width of 5 pixels. With "Solid" border style, only the foreground color is visible. Colors and color gradient in the table header 1. Select the table-based object in the screen. 2. In the Inspector window, open "Properties > Properties > Table header fill pattern". 3. Select the fill pattern, for example "Horizontal gradient". 4. Select a background color, for example, blue, under "Gradient". 5. Activate "Gradient 1". 6. Select a color for "Gradient 1", for example, white. 7. Select a "Width" for the color gradient, for example, 12. 8. Activate Gradient 2. 9. Select a color for Gradient 2, for example, yellow. 10.Select a "Width" for the color gradient, for example, 10 The table header is displayed with a color gradient. See also Designing a border (Page 3224) 10.1.2.18 Designing a border Introduction WinCC offers various properties for designing display and operating objects. The I/O field example below shows the possible settings for designing borders. You change the appearance in the Inspector window of the relevant object. Designing a border 1. Open "Properties > Properties > Appearance". 2. Select the width of the border, e.g. "5". 3. Select the style of the border, e.g. double line. 4. Select the foreground color. 5. Select the background color. 3224 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.1 Creating screens &RORU )RUHJURXQGFRORU %DFNJURXQGFRORU :LGWK &RUQHUUDGLXV Figure 10-2 "Double line" border style Border style The figure below shows a border in "3D style". The figure below shows a border in "Solid" style. Note Device-specific nature of the properties The border style that is available depends on the object and the HMI device used. WinCC Basic V13.0 System Manual, 02/2014 3225 Visualize processes 10.1 Creating screens See also Designing table-based objects (Page 3223) 10.1.2.19 Defining color gradients Introduction For the objects in WinCC, color gradients can be specified as background for various surfaces. Change the category in the Inspector window, depending on which surface you fill with a color gradient. The procedure remains the same. The following section describes how to configure the color gradient of buttons. Horizontal color gradient with two colors 1. Select an object with buttons, for example, a button. 2. In the Inspector window, select "Properties > Properties > Fill Pattern". 3. Select "Fill Pattern > Horizontal gradient". 4. Select a background color for the vertical color gradient, for example, orange. 5. Activate "Gradient 1". 6. Select a "Color" for Gradient 1, for example, red. 7. Select a "Width" for Gradient 1, for example, "10". The background of the button is displayed in orange. For the horizontal color gradient, Gradient 1 is shown from the left border. Gradient 1 is 10 pixels wide. Vertical color gradient with three colors 1. Select a button in the screen. 2. In the Inspector window, select "Properties > Properties > Fill Pattern". 3. Select the "Vertical gradient" background. 4. Select a background color under "Gradient", for example, orange. 5. Activate "Gradient 1". 6. Select a color for "Gradient 1", for example, red. 7. Select a "Width" for the color gradient, for example, 8. 8. Activate Gradient 2. 3226 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.1 Creating screens 9. Select a color for Gradient 2, for example, yellow. 10.Select a "Width" for the color gradient, for example, 10. Color Gradient 1 Background color Color Gradient 2 For the vertical color gradient, Gradient 1 is shown from top to bottom. Gradient 1 is 8 pixels wide. The background of the button is displayed in orange. Gradient 2 is shown at the bottom border. Gradient 2 is 10 pixels wide. 10.1.2.20 Applying predefined styles Introduction You can assign predefined styles to objects and faceplates in Runtime. You can change the background color of the display and operating elements using predefined styles. In this way, you harmonize the display in Runtime. Requirement The "Tools" task card is open. Setting predefined styles 1. Select the object that you want to insert in the "Toolbox" task card. 2. Select one of the following options in the "Toolbox" task card: - "Default" to use the default style - "Dark" to use the dark color scheme - "Light" to use the light color scheme - "Use device design" to use the settings from the current device design WinCC Basic V13.0 System Manual, 02/2014 3227 Visualize processes 10.1 Creating screens 3. Insert the required object in the work area. The object is displayed in the selected style. 4. The objects are created in the selected style as long as the style remains activated in the toolbar. To return to the default style, select the "Default" option in the toolbar. See also Working with styles (Page 3198) 10.1.2.21 Inserting multiple objects of the same type (stamping tool) Introduction WinCC offers the possibility to "stamp" several objects of the same type directly one after the other, i.e. paste without having to reselect the object every time. In addition you have the possibility of multiplying an object that has already been inserted. Requirement The "Tools" task card is open. Inserting several objects of one type 1. Select the object that you want to insert in the "Tools" task card. 2. Click the icon in the toolbar of the "Tools" task card. The "Stamp" function is activated. 3. To insert the object with its standard size, click the relevant insertion position in the work area. To insert the object with another size, position the mouse pointer at the desired location in the work area. Press the left mouse button and drag the object to the required size. The object is inserted in the work area as soon as you release the mouse button. 4. Repeat step 3 to insert further objects of the same type. 5. Click the icon again. The "Stamp" function is deactivated. Note You can copy existing objects using the drag-and-drop +<CTRL> function. The existing object is not moved in this case. You paste a copy of this object into the new position instead. 3228 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.1 Creating screens Inserting and multiplying an object 1. Insert the desired object from the "Tools" task card. 2. Press the <Ctrl> key and position the cursor on one of the handles displayed in the figure shown below. 0XOWLSOLFDWLRQ LQKRUL]RQWDO GLUHFWLRQ 0XOWLSOLFDWLRQ LQYHUWLFDO GLUHFWLRQ 0XOWLSOLFDWLRQ LQYHUWLFDODQG KRUL]RQWDO GLUHFWLRQ 3. Drag the handles to the right and/or down while keeping the left mouse button pressed. 4. The object is multiplied depending on available space if you keep moving the cursor. Result You have pasted and stamped an object in a screen. See also Overview of objects (Page 3200) WinCC Basic V13.0 System Manual, 02/2014 3229 Visualize processes 10.1 Creating screens 10.1.2.22 Repositioning and resizing multiple objects Possible modifications After you have selected multiple objects, you edit them: Shift using the mouse - To change the absolute position of the marked objects, position the mouse pointer over an object, and shift the multiple selection with the mouse button pressed. - To resize all the objects by the same ratio, grab the resizing handles of the reference object. Move over the work area with the icons of the toolbar - Change the position of the marked objects with respect to each other - Align the height and width of the marked objects Moving with the shortcut menu commands of the work area - Change the position of the marked objects with respect to each other - Align the height and width of the marked objects See also Overview of objects (Page 3200) 10.1.2.23 External graphics Introduction You can use graphics created with an external graphic program in WinCC. To use these graphics you store them in the graphic browser of the WinCC project. You can save graphics in the graphic browser: When you drag-and-drop graphics objects from the "Graphics" pane into the work area, these are stored automatically in the graphic browser. The graphic names are numbered in the order of their creation, for example, "Graphic_1." Use the <F2> function key to rename the graphic. As a graphic file with the following formats: *.bmp, *.ico, *.emf, *.wmf, *.gif, *.tif, *.png, *.jpeg or *.jpg As an OLE object that is embedded in WinCC and is linked to an external graphic editor. In the case of an OLE link, you open the external graphic editor from WinCC. The linked object is edited using the graphic editor. An OLE link only works if the external graphic editor is installed on your PC, and supports OLE. 3230 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.1 Creating screens Use of graphics from the graphic browser Graphics from the graphic browser are used in your screens: In a Graphic view In a graphics list As labeling for a button/function key Transparent graphics In WinCC you also use graphics with a transparent background. When a graphic with a transparent background is inserted into a graphic object of WinCC, the transparency is replaced by the background color specified for the graphic object. The selected background color is linked firmly with the graphic. If you use the graphic in another graphic object of WinCC, this object is displayed with the same background color as the graphic object that was configured first. If you want to use the graphic with different background colors, include this graphic in the graphic browser again under a different name. The additional background color is configured when the graphic is used at the corresponding graphic object of WinCC. Managing graphics An extensive collection of graphics, icons and symbols is installed with WinCC, for example: In the Toolbox window of the "Graphic" pane the graphic objects are structured by topic in the "WinCC graphics folder." The link to the WinCC graphics folder cannot be removed, edited or renamed. The "Graphics" pane is also used to manage the external graphics. The following possibilities are available: Creating links to graphics folders The external graphic objects in this folder, and in the subfolders, are displayed in the toolbox and are thus integrated in the project. Editing folder links You open the program required for editing of the external graphic in WinCC. See also Overview of objects (Page 3200) 10.1.2.24 Managing external graphics Introduction External graphics that you want to use in WinCC are managed in the "Screens" editor by using the "Tools" task card in the "Graphics" pane. WinCC Basic V13.0 System Manual, 02/2014 3231 Visualize processes 10.1 Creating screens Requirement The "Screens" editor is open. The "Tools" task card is open. The graphics are available. The graphics have the following formats: *.bmp, *.ico, *.emf, *.wmf, *.gif, *.tif, *.jpeg or *.jpg Creating a folder link 1. Click "My graphics folder." 2. Select "Link" in the shortcut menu. The "Create link to folder" dialog is opened. The dialog suggests a name for the folder link. 3. Edit the name as required. Select the path containing the graphic objects. 4. Click "OK" to confirm your input. The new folder link is added to the "Graphics" object group. The external graphics that are located in the target folder and in sub-folders are displayed in the toolbox. Editing folder links 1. Select the folder link to edit. 2. Select the "Edit link..." command from the shortcut menu. The "Create link to folder" dialog is opened. 3. Edit the name and path of the folder link as required. 4. Click "OK" to confirm your input. Renaming the folder link 1. Select the folder link to rename. 2. Select "Rename" from the shortcut menu. 3. Assign a name to the new folder link. Removing a folder link 1. Select the folder link you want to delete. 2. Select "Remove" in the shortcut menu. Edit external graphics 1. Select the graphic you want to edit. 2. Select the "Edit graphic" command from the shortcut menu. This opens the screen editor associated with the graphic object file. 3232 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.1 Creating screens Editing graphics folders from WinCC 1. Select the graphic you want to edit. 2. Select the "Open parent folder" command from the shortcut menu. The Windows Explorer opens. See also Overview of objects (Page 3200) 10.1.2.25 Storing an external image in the graphics library. 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 A screen has been created. A Graphic View is inserted in the screen. The Inspector window of the Graphic view is open. To store an external graphic in the image browser: A graphic is available. To store an OLE object in the browser: An OLE-compatible graphics program is installed on your configuration computer. Save graphics file 1. Open the Windows Explorer. 2. Select the graphic that you want to store. 3. Drag-and-drop the graphic into the graphic browser. Creating and saving a new graphic as an OLE object 1. Select the Graphic view on your screen. 2. In the Inspector window, select "Properties > Properties > General": 3. Open the graphic selection list. 4. Click WinCC Basic V13.0 System Manual, 02/2014 . 3233 Visualize processes 10.1 Creating screens 5. 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. From the "Insert object" dialog box, select "New" and an object type. The settings in "Settings > "OLE settings" determine which object types are shown. 7. Click "OK." The associated graphic program is opened. When you are finished creating graphics, end the graphic programming software with "File > Close" or "File > Close & return to WinCC." The graphic will be stored in the graphic programming software standard format and added to the graphic browser. Inserting created graphics in WinCC Note A new graphic object created as OLE object may not be directly accepted in WinCC when you save it to an external graphics program. 1. Reopen the dialog for inserting a graphic. 2. From the "Insert object" dialog box, select "Create from file." 3. Click the "Browse" button. 4. Navigate to the created graphic and select it. Saving an existing graphic object as an OLE object 1. In the Inspector window, select "Properties > Properties > General": 2. Open the graphic selection list. 3. Click . 4. 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. 5. From the "Insert object" dialog box, select "Create from file." 3234 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.1 Creating screens 6. Click the "Browse" button. 7. Use the dialog to help you navigate to the folder in which the graphic file is saved. Note To import graphics files, note the following size restrictions: *.bmp, *.tif, *.emf, *.wmf 4 MB *.jpg, *.jpeg, *.ico, *.gif "*1 MB Result The image file is now stored in your image browser. It is shown in a screen with a Graphic view , or is added as a list element in an image list. You can double-click OLE objects in your library to open them for editing in the corresponding graphic editor. When you have finished editing graphics, end the graphic programming software with "File > Close" or "File > Close & return to WinCC." The changes are applied to WinCC. See also Overview of objects (Page 3200) 10.1.2.26 Working with object groups Basics on groups Introduction Groups are several objects that are grouped together with the "Group" function. You edit a group in the same way as any other object. Overview WinCC offers the following methods for editing multiple objects: Multiple selection Creating object groups Editing mode To edit an individual object in a group, select the object in the "Layout > Layers" task card. Alternatively select "Group > Edit group" in the object group's shortcut menu. WinCC Basic V13.0 System Manual, 02/2014 3235 Visualize processes 10.1 Creating screens Hierarchical groups You add further objects or groups to extend a group. The group is enlarged by the new objects and is structured hierarchically in main and sub-groups. Such hierarchical groups must be broken up in stages. You also break up the group in the same order in which you grouped the objects or groups. It takes exactly the same number of steps to break up these hierarchical groups as it did to create them. Rectangle surrounding the object Only one surrounding rectangle is now displayed for the whole group. The surrounding rectangles of all objects are displayed for a multiple selection on the other hand. Layers All objects of a group are located in the same layer. See also Overview of objects (Page 3200) Creating object groups Introduction The "Group" command combines multiple objects to form a group. You can change the size and position of the group. The following rules apply: The system automatically adapts the position coordinates of the grouped objects when you reposition the group. The relative position of the grouped objects to the group is not affected. The system automatically adapts the height and width of the grouped objects in proportion to a change of the group size. To change the size of the group proportionately, hold down the <Shift> key and drag the rectangle around the object until has the required size. Note To create a hierarchical group, organize the individual groups like objects. Requirement You have opened a screen which contains at least two objects. Creating object groups 1. Select all the objects you want to organize in a group. 2. Select the command "Group > Group" from the shortcut menu. 3236 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.1 Creating screens The objects of the group are displayed with a rectangle around the objects. Grouping objects within a group 1. Select the group you want to edit. 2. Select the command "Group > Edit group" from the shortcut menu. The group that you are editing is highlighted by a red frame. 3. Select the objects of a group that you want to combine into a subgroup. 4. Select the command "Group > Group" from the shortcut menu. A subgroup with the objects is created. Adding objects into an existing group 1. Select the group to which you want to add objects. 2. Press the <Shift> key and select the object you want to add to the group. 3. Select the "Group > Add to group" command from the shortcut menu. The object is added to this group. Alternative procedure You can also edit groups in the "Layout" task card. Using drag-and-drop you can also easily edit nested groups in the "Layers" pane. Result The selected objects are combined in a group. The multiple selection rectangle becomes the rectangle surroundings the objects in the group. The handles are shown only for the group. The group in in the active layer. Ungroup Introduction Select the "Ungroup" command to split a group into the original object fractions. Requirement You have opened a screen that contains a group. Ungroup 1. Select the group. 2. Select the "Group > Ungroup" command from the shortcut menu. WinCC Basic V13.0 System Manual, 02/2014 3237 Visualize processes 10.1 Creating screens Ungrouping a group within a group 1. Select the higher-level group. 2. Select the command "Group > Edit group" from the shortcut menu. The group that you are editing is highlighted by a red frame. 3. Select the lower-level group. 4. Select the "Group > Ungroup" command from the shortcut menu. Result The lower-level group is ungrouped. The objects are assigned to the next higher group. Alternative procedure You can also edit groups in the "Layout" task card. Using drag-and-drop you can also easily edit nested groups in the "Layers" pane. Adding objects to a group Introduction The "Add objects to group" command is used to add objects to a group, without ungrouping it first. Requirements A screen with one group and at least one other object is opened. Procedure 1. Select the group. 2. Press the <Shift> key and select the object you want to add to the group. 3. Select the "Group > Add to group" command from the shortcut menu. Result The group consists of the original objects, and the newly-added objects. The added objects are arranged at the front of the group. Alternative procedure You can also edit groups in the "Layout" task card. Using drag&drop you can also easily edit hierarchical groups in the "Layers" palette. 3238 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.1 Creating screens Removing Objects from the Group Introduction You use the "Remove objects from group" command to remove individual objects from a group, without ungrouping it first. You do not have to remove the object from the group to edit an object in a group. You can edit the objects of a group individually. Requirement You have opened a screen that contains a group. Removing objects from a group To remove an object from a group: 1. Select the group. 2. Select the command "Group > Edit group" from the shortcut menu. The group you want to edit is highlighted by a red frame. 3. Select all objects in the group that you want to remove from the group. 4. Select the "Group > Remove from group" command from the shortcut menu. The objects are removed from the group. Note If there are only two objects in the group, the menu command "Remove from group" is not available. Deleting objects from a group To remove an object from the group, and from the screen: 1. Select the group. 2. Select the command "Group > Edit group" from the shortcut menu. The group you want to edit is highlighted by a red frame. 3. Select the objects in the group that you want to delete. 4. Select "Delete" from the shortcut menu. Note If there are only two objects in the group, the menu command "Delete" is not available. WinCC Basic V13.0 System Manual, 02/2014 3239 Visualize processes 10.1 Creating screens Alternative procedure You can also edit groups in the "Layout" task card. Using drag-and-drop you can also easily edit nested groups in the "Layers" pane. Editing an Object in a Group Introduction You can edit the objects of a group individually. Requirement You have opened a screen that contains a group. Editing grouped objects 1. Select the group. The properties of the group are displayed in the Inspector window. 2. Change the position and size of the grouped objects in "Properties > Properties >Layout." 3. Change the name of the group in "Properties > Properties > Miscellaneous." 3240 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.1 Creating screens Modifying the properties of an object within a group 1. Select the group. 2. Select the object whose properties you want to change in the Inspector window. The properties of the object are displayed. 3. Change the object properties. Note The dynamization of properties for all objects of the group which have these properties is not possible in a group. You can only dynamize the properties of the objects associated with a group for each object itself. Result Although you have edited the object, it is still an element of the group. These changes do not affect the other objects of the group. WinCC Basic V13.0 System Manual, 02/2014 3241 Visualize processes 10.1 Creating screens 10.1.2.27 Configuring the keyboard access Overview of keyboard access Introduction For keyboard units without a mouse, the operator activates control objects using the <Tab> key. You can set up keyboard input to make the process easier to run, and to make sure that the operator enters all the necessary values. If you are using the keyboard, use the <Tab> key to activate the objects in a certain order, and to enter the necessary values. For HMI devices without key, you can simulate the <Tab> key by configuring the "SimulateSystemKey" system function to a function key. Operator authorizations and operator control enables If you configure an object for operator input with the <Tab> key, the object must have both an operator authorization, and an operator control enable. Editing the tab sequence The tab sequence is determined automatically when the control objects are created. The numbers of the tab sequence are assigned in the sequence in which the libraries are created. It makes sense to change the tab sequence in the following cases: The operator changes directly to a specific control object. The screen requires a specific sequence Change to the tab sequence mode to change the tab sequence. In this mode, the tab sequence number is displayed at the top left of the control objects. The tab sequence numbers of hidden objects are also shown. The distribution of these numbers is edited using the mouse. Note Other functions are not available in the tab sequence mode. See also Example: Inserting and configuring a rectangle (Page 3244) Overview of objects (Page 3200) Defining the Operator Authorization and Operator Control Enable for an Object Introduction If you configure an object for operator input with the <Tab> key, the object must have both an operator authorization, and an operator control enable. 3242 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.1 Creating screens Requirement You have opened a screen which contains at least one object. Procedure 1. Select the object. 2. Select "Properties > Properties > Security" in the Inspector window. 3. Select the operator authorization under "Authorization." 4. Activate the authorization to operate. Result The operator can use the <Tab> key in Runtime to select the object. See also Example: Inserting and configuring a rectangle (Page 3244) Setting the tab sequence order Introduction All operable objects can be reached in runtime with the <Tab> key. You use the "Tab sequence" command to define the order in which the operator can activate objects in runtime. Note You cannot reach objects with the "Output" or "Two states" mode in runtime with the <Tab> key. You can operate the screen in runtime: Using the <Tab> key Using the mouse Using a configured hotkey Requirement The active screen contains operable objects. No object is selected. The objects have been enabled for use in runtime, and have operator authorization. WinCC Basic V13.0 System Manual, 02/2014 3243 Visualize processes 10.1 Creating screens Procedure 1. Select "Edit tab sequence" in the "Edit" menu. Tab sequence mode is activated. The tab sequence number is displayed for all objects that can be used. The tab sequence number is also displayed for hidden objects. 2. Use edit the tab sequence mode, click the accessible objects in the order in which you want them to be activated using <Tab> in runtime. The following figure shows how the tab sequence is defined in the screen. In runtime, the <Tab> key first activates the alarm view (number 1), then the I/O field (number 2), and then the button (number 3): 3. To exclude a screen object from the tab sequence, press the key combination <Shift+Ctrl> and click on the desired object. The tab sequence number is no longer displayed in the screen object. The screen object is now excluded from the tab sequence. The remaining tab sequence numbers are automatically decreased by 1. 4. To reenter an excluded screen object in the tab sequence, repeat step 3. The screen object entered as the first object in the tab sequence. Result The operator selects the objects in the specified order in Runtime with the <Tab> key. See also Example: Inserting and configuring a rectangle (Page 3244) 10.1.2.28 Examples Example: Inserting and configuring a rectangle Task In this example, you insert a rectangle in a screen. You can configure the following properties: Name = "MyRectangle" Position = (20, 20) Size = (100,100) 3244 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.1 Creating screens Color = red Black frame 2 pixels wide Principle The rectangle is a closed object which can be filled with a color or pattern. The height and width of a rectangle can be adjusted to allow its horizontal and vertical alignment. Overview Carry out the following steps in order to create a rectangle: Inserting a rectangle Configuring a rectangle See also Basics on groups (Page 3235) Overview of objects (Page 3200) Example: Inserting a rectangle Task In this example, you insert and rename a rectangle. Do not use the special characters ?, ", /, \, *, <, > for the name. Requirement A screen is open. The Inspector window is open. The "Tools" task card is open. WinCC Basic V13.0 System Manual, 02/2014 3245 Visualize processes 10.1 Creating screens Procedure 1. Click the "Basic objects" palette in the "Tools" task card. 2. Drag the "Rectangle" object into the screen. 3. In the Inspector window, select "Properties > Properties > Miscellaneous". 4. Type in the new name "MyRectangle". Result The rectangle is now inserted and named "MyRectangle". The rectangle has the default properties of the "rectangle" object. Example: Configuring a rectangle Task In this example you configure a rectangle: Color = red Black frame 2 pixels wide Position = (20, 20) Size = (100,100) Changing the color of the rectangle To change the color of the rectangle: 1. Select the rectangle. 2. Define the background color in "Properties > Properties > Appearance > Background > Color" in the Inspector window. 3. Select "Solid" as the fill pattern. 4. Define the color for the border in "Properties > Properties > Appearance > Border > Color" in the Inspector window. 5. Enter the value "2" for "width". 6. Select "Solid" as the "Style". Interim result The rectangle is red and has a black frame with a width of two pixels. 3246 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.1 Creating screens Repositioning and resizing the rectangle To change the position and size of the rectangle: 1. Select the rectangle. 2. In the Inspector window, select "Properties > Properties > Layout". 3. Set "20" for the both the X and Y coordinates under "Position & Size". 4. Set "100" for the height and for the width. Result The rectangle is positioned at the coordinates (20, 20), and has a width and height of 100 pixels. WinCC Basic V13.0 System Manual, 02/2014 3247 Visualize processes 10.1 Creating screens 10.1.3 Working with text lists and graphics lists 10.1.3.1 Working with text lists Basics on text lists Introduction Texts are assigned to the values of a tag in a text list. Assign the text list to a symbolic I/O field for example in the configuration. This supplies the text to be displayed to the object. The text lists are created in the ""Text List" editor. You configure the interface between the text list and a tag at the object that uses the text list. The selection of objects that can have a text list assigned depends on the Runtime. Application The text list is used, for example, to display a drop-down list in a symbolic I/O field. If the symbolic I/O field is a display field, the associated texts will differ according to the value of the configured tags. If the symbolic I/O field is an input field, the configured tag assumes the associated value when the operator selects the corresponding text in Runtime. Note Display of tag values without text The display of tag values to which no text has been assigned depends on the Runtime: The display and operating object remains empty. Three asterisks *** are displayed. Multilingual texts You can configure multiple languages for the texts in a text list. The texts will then be displayed in the set language in Runtime. To this purpose you set the languages in the Project window under "Language support > Project languages." Configuration steps The following steps are necessary to display texts in a symbolic I/O field for example: 1. Creating the text list 2. Assignment of the texts to values or value ranges of a text list 3. Assignment of a text list in the display object, e.g. the symbolic I/O field 3248 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.1 Creating screens Creating a text list Introduction The text list allows you to assign specific texts to values and to output these in Runtime, for example in a symbolic I/O field. The type of symbolic I/O field can be specified, for example as a pure input field. The following types of list are available: Value/Range Bit Bit Number Procedure 1. Double-click "Text and graphics lists" in the project window. 2. Open the "Text lists" tab. 3. Click "Add" in the "Text lists" table. The Inspector window of the text list is open. 4. Assign a name to the text list that indicates its function. 5. Select the text list type under "Selection": - Value/Range: Text from the text list is displayed when the tag has a value that lies within the specified range. - Bit (0,1): A text from the text list is displayed when the tag has the value 0. A different text from the text list is displayed when the tag has the value 1. - Bit number (0-31): Text from the text list is displayed when the tag has the value of the assigned bit number. 6. Enter a comment for the text list. Note You must not use semicolons in the texts in a text list. The semicolon is a control character and is automatically deleted from a text. WinCC Basic V13.0 System Manual, 02/2014 3249 Visualize processes 10.1 Creating screens Result A text list is created. Assigning texts and values to a range text list Introduction For each area text list you specify which texts are displayed at which value range. Requirement The "Text and graphics list" editor is open. The "Text lists" tab is open. An area text list has been created and selected. 3250 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.1 Creating screens Procedure 1. Click "Add" in the "Text list entries" table. The Inspector window for this list entry opens. 2. Select the setting "Range" in "Properties > Properties > General > Value" in the Inspector window. - Enter the value "1" for "Min" for example. - Enter the value "20" for "Max" for example. - For "Text", enter the text that is displayed in Runtime if the tag is within the specified value range. Note Use a maximum of 255 characters and no semicolons for the text. 3. Click "Add" in the "Text list entries" table. A second list entry is created. 4. Select the setting "Range" in "Properties > Properties > General > Value" in the Inspector window. - Enter the value "21" for "Min" for example. - Enter the value "40" for "Max" for example. - For "Text", enter the text that is displayed in Runtime when the tag is within the specified value range. 5. If required, activate the "default entry". The entered text is always displayed when the tag has an undefined value. Only one default entry is possible per list. Result An area text list is created. Texts have been assigned to the possible value ranges. WinCC Basic V13.0 System Manual, 02/2014 3251 Visualize processes 10.1 Creating screens Assigning texts and values to a bit text list Introduction For each text list, you specify which text is displayed at which bit value. Requirement The "Text and graphics list" editor is open. The "Text lists" tab is open. A bit text list has been created and selected. Procedure 1. Click "Add" in the "Text list entries" table. The Inspector window for this list entry opens. 2. Select the setting "Single value" in "Properties > Properties > General > Value" in the Inspector window. - Enter "0" for "Value." - Enter the text which is displayed in Runtime under "Text" if the bit tag is set to "0". Note Use a maximum of 255 characters and no semicolons for the text. 3. Click "Add" in the "Text list entries" table. A second list entry is created. 4. Select the setting "Single value" in "Properties > Properties > General > Value" in the Inspector window. - Enter "1" under "Value." - Enter the text which is to be displayed in Runtime under "Text" if the bit tag is set to "1". 3252 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.1 Creating screens Result A bit text list is created. Texts that appear in Runtime are assigned to the possible values "0" and "1". Assigning texts and values to a bit number text list Introduction For each bit number text list you specify which texts are displayed at which bit number. Requirement The "Text and graphics list" editor is open. The "Text lists" tab is open. A bit number text list has been created and selected. Procedure 1. Click "Add" in the "Text list entries" table. The Inspector window for this list entry opens. 2. Select the setting "Single value" in "Properties > Properties > General > Value" in the Inspector window. - Enter "10", for example, for "Value". - Under "Text", enter the text that is displayed in Runtime when the tag has the value "10". Note Use a maximum of 255 characters and no semicolons for the text. WinCC Basic V13.0 System Manual, 02/2014 3253 Visualize processes 10.1 Creating screens 3. If required, activate the "default entry". The entered text is always displayed when the tag has an undefined value. Only one default entry is possible per list. 4. Create further list entries for additional bit numbers of the same text list. Result A bit number text list is created. Texts that appear in Runtime are assigned to the specified bit numbers. Configuring objects with a text list Introduction The output value and value application for text lists are specified in the display and operating object that displays the texts of the text list in Runtime. The properties of these objects are configured as required. Requirement A text list is created. You have created a tag. The "Screens" editor is open. A screen with a symbolic I/O field is open. The object is edited. 3254 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.1 Creating screens Procedure 1. Select the text list which you want to have displayed in Runtime in "Properties > Properties > General > Text list" in the Inspection window. 2. Select the setting "Output" as the "Mode". Note Runtime dependency Different field types are available for a symbolic I/O field depending on the Runtime. 3. Select the tag the value of which determines the display in the symbolic I/O field as "Tag". Result The defined texts of the text list are displayed in the symbolic I/O field in Runtime when the tag has the specified value. 10.1.3.2 Working with graphics lists Basic principles of graphics lists Introduction The possible values of a tag are assigned to specific graphics in a graphics list. During configuration, you can create a graphics list for a button or a graphic I/O field. This supplies the graphics to be displayed to the object. The graphics lists are created with the "Text and graphics list" editor. You configure the interface between the graphics list and a tag at the object that uses the graphics list. The availability of the graphics list is determined by the HMI device used. WinCC Basic V13.0 System Manual, 02/2014 3255 Visualize processes 10.1 Creating screens Application You can configure the graphics list for the following situations: Drop-down list with a graphic I/O field State-specific graphic for a button The graphics in a graphics list can be configured as multilingual. The graphics will then be displayed in the set language in runtime. Graphic sources Graphics can be added to the graphics list from the following sources: By selecting from a graphic browser By selecting an existing file You can use the following file types: *.bmp, *.ico, *.emf, *.wmf, *.gif, *.tiff, *.png, *.jpeg and *.jpg. By creating a new file Function If the graphic I/O field is a display field, the associated graphics will differ according to the value of the configured tags. If the graphic I/O field is an input field, the configured tag assumes the associated value when the operator selects a graphic in runtime. Configuration steps The following tasks are required to display graphics, for example, in a graphic I/O field: 1. Creating the graphics list 2. Assignment of the graphics to values or value ranges of a graphics list 3. Assigning a graphics list in the display object, for example the graphic I/O field Creating a graphics list Introduction The graphics list allows you to assign specific graphics to variable values and to output these in a graphic IO field in Runtime. You can specify the type of graphic I/O field, for example as a pure output field. 3256 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.1 Creating screens Procedure 1. Double-click "Text and graphics lists" in the project window. 2. Open the "Graphics lists" tab. 3. Click "Add" in the "Graphics lists" table. The Inspector window of the graphics list will open up. 4. Assign a name to the graphics list that indicates its function. 5. Select the graphics list type "Bit number (0 - 31)" for example under "Select". 6. Enter a comment for the graphics list. Result A graphics list of the type "Range (0 - 31)" is created. Assigning a graphic and values to a range graphics list Introduction For each area graphics list you specify which graphics are displayed at which value range. WinCC Basic V13.0 System Manual, 02/2014 3257 Visualize processes 10.1 Creating screens Requirement The "Text and graphics list" editor is open. The "Graphics list" tab is open. An area graphics list has been created and selected. 3258 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.1 Creating screens Procedure 1. Click "Add" in the "Graphics list entries" table. The Inspector window for this list entry opens. 2. Select the settings "Range" in "Properties > Properties > General > Value" in the Inspector window: - Enter the value "1" for "Min" for example. - Enter the value "20" for "Max" for example. - Select a graphic that is displayed in Runtime when the tag is within the specified value range. Note As an alternative to the drop-down menu, you can insert graphics from libraries or from your file system: 1. Select a graphic in the library or in your file system. 2. Drag-and-drop the graphic into the "Graphics list entries > Graphic" table. 3. Click "Add" in the "Graphics list entries" table. A further list entry is created. WinCC Basic V13.0 System Manual, 02/2014 3259 Visualize processes 10.1 Creating screens 4. Select the settings "Single value" in "Properties > Properties > General > Value" in the Inspector window: - Enter the value "21" for example. - Select a graphic which is displayed in Runtime if the bit "21" is set in the tag. 5. If required, activate the "default entry". The graphic is always displayed when the tag has an undefined value. Only one default entry is possible per list. Result An area graphics list is created. Graphics that appear in Runtime are assigned to the possible values. Assigning graphics and values to a bit graphics list Introduction For each graphics list you specify which graphic is displayed at which bit value. Requirement The "Text and graphics list" editor is open. The "Graphics list" tab is opened. A bit graphics list has been created and selected. 3260 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.1 Creating screens Procedure 1. Click "Add" in the "Graphics list entries" table. The Inspector window for this list entry opens. 2. Select the settings "Single value" in the inspector window "Properties > Properties > General > Value": - Enter "0" as the value. - Select a graphic which is displayed in Runtime if the bit "0" is set in the tag. Note As an alternative to the drop-down menu, you can insert graphics from libraries or from your file system: 1. Select a graphic in the library or in your file system. 2. Drag-and-drop the graphic into the "Graphics list entries > Graphic" table. 3. Click "Add" in the "Graphics list entries" table. A new list entry is created. 4. Select "Properties > Properties > General > Value > Single value": in the Inspector window. - Enter "1" as the value. - Select a graphic which is displayed in Runtime if the bit "1" is set in the tag. Result A bit graphics list is created. Graphics that appear in Runtime are assigned to the values "0" and "1". WinCC Basic V13.0 System Manual, 02/2014 3261 Visualize processes 10.1 Creating screens Assigning graphics and values to a bit number graphics list Introduction For each bit number graphics list you specify which graphics are displayed at which bit number. Requirement The "Text and graphics list" editor is open. The "Graphics list" tab is open. A bit number graphics list has been created and selected. 3262 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.1 Creating screens Procedure 1. Click "Add" in the "Graphics list entries" table. The Inspector window for this list entry opens. 2. Select the settings "Single value" in "Properties > Properties > General > Value" in the Inspector window: - Enter the value "0" for example. - Select a graphic which is displayed in Runtime if the bit "0" is set in the tag. Note As an alternative to the drop-down menu, you can insert graphics from libraries or from your file system: 1. Select a graphic in the library or in your file system. 2. Drag-and-drop the graphic into the "Graphics list entries > Graphic" table. 3. If required, activate the "default entry". The graphic is always displayed when the tag has an undefined value. Only one default entry is possible per list. 4. Create further list entries for additional bit numbers of the same graphics list. Result A bit number graphics list is created. Graphics that appear in Runtime are assigned to the specified bit numbers. WinCC Basic V13.0 System Manual, 02/2014 3263 Visualize processes 10.1 Creating screens Configuring objects with a graphics list Introduction The output value and value application for graphics list are specified in the display and operating object that displays the graphics of the graphics list in Runtime. The properties of these objects are configured as required. Requirement A graphics list is created. The values have been defined. Graphics have been assigned to the values. You have created a tag. The "Screens" editor is open. A screen with a graphics I/O field is open. The object is edited. Procedure 1. Select the graphics list the graphics of which you want to have displayed in Runtime in "Properties > Properties > General > Graphics list" in the inspector window. 2. Select the setting "Input/Output" as the "Mode". Note Runtime dependency Different field types are available for a graphic I/O field depending on the Runtime. 3. As "Tag", select the tag whose values are defined by the display in the graphic I/O field. Result The defined graphics of the graphics list are displayed in the graphic I/O field in Runtime when the tag has the specified value. 10.1.4 Dynamizing screens 10.1.4.1 Basics on dynamization Dynamizing objects In WinCC you dynamize objects to map your system and show processes on HMI devices. 3264 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.1 Creating screens You implement dynamizations by Animations Tags System functions One example is the mapping of a tank, the liquid level of which rises or falls in relation to a process value. The options for dynamization depend on the object involved. When you copy an object, its dynamization functions are included. See also Dynamization in the inspector window (Page 3265) Configuring a new animation (Page 3267) Basic on events (Page 3276) 10.1.4.2 Dynamization in the inspector window Introduction Basically, you can dynamize all the screen objects which you have configured in a screen. Which dynamization possibilities and which events are available depends on the device and the selected object. Animations WinCC helps you to implement dynamization using predefined animations. If you want to animate an object, first configure the desired animation in the object's inspector window. Then adapt the animation to the requirements of your project. The selection of the supported animations depends on the HMI device and the selected object. You choose between the following types of animation: Layout: Appearance, visibility Movements: direct, diagonal, horizontal and vertical movement Variable binding You can configure the "Variable binding" type of animation several times for one object. You configure animations in the "Properties > Animations" inspector window. WinCC Basic V13.0 System Manual, 02/2014 3265 Visualize processes 10.1 Creating screens Events Operable objects also react to events, such as a mouse click. You configure a function list with system functions on an event. The system functions are processed as a reaction to the triggered event. You configure events in the "Properties > Events" inspector window. 3266 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.1 Creating screens You will find further information in "Working with function lists". See also Basics on dynamization (Page 3264) 10.1.4.3 Dynamization with animations Configuring a new animation Introduction Use predefined animations to dynamize screen objects. Requirement You have opened a screen which contains at least one dynamic object. The Inspector window is open. The toolbox window is displayed. WinCC Basic V13.0 System Manual, 02/2014 3267 Visualize processes 10.1 Creating screens Procedure in the inspector window 1. In the Inspector window, select "Properties > Animations". 2. Select the animation you want to use. 3. Click the button. Procedure in the "Animations" task card. 1. Open the object group containing the required animation in the "Animations" task card. 2. Drag the animation onto the object that you want to make dynamic. Alternatively you select the object in the screen and double click the desired animation in the "Animation" task card. Result The animation appears in the Inspector window of the object. You configure the animation in the following steps. In the animations overview the green arrow indicates which animation is already configured. The configured animation opens in the inspector window when you click the green arrow. See also Dynamizing the visibility of an object (Page 3273) Basics on dynamization (Page 3264) 3268 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.1 Creating screens Dynamize appearance of an object Introduction The appearance of a screen object is controlled by changing the value of a tag in runtime. When the tag adopts a certain value, the screen object changes its color or flashing characteristics according to the configuration. Type Areas or single values of the tag are observed in Runtime depending on the selection. The appearance of the object changes according to the configuration. Requirement A screen is open. A dynamic object is contained and selected in the screen. The Inspector window is open. The toolbox window is displayed. Procedure 1. In the Inspector window, select "Properties > Animations". The animations available for the selected object are displayed. 2. Select the animation "Appearance" and click the The parameters of the animation are displayed. button. 3. Select a tag in "Tag > Name". 4. Select "Type > Range" for example. 5. Click "Add" in the table. 6. Enter the tag interval "0 - 20" in the "Range" column for example. 7. For "Foreground color" and "Background color", select the color the object is to acquire in Runtime when the tag reaches the interval. WinCC Basic V13.0 System Manual, 02/2014 3269 Visualize processes 10.1 Creating screens 8. Select a flashing mode for the object from the "Flashing" list. 9. Repeat steps 5 to 8 to create another tag interval, e.g. "21 - 60". Result In Runtime, the flashing response, and color of the object change dynamically according to the process value returned in the tag. Configuring movement Introduction You can configure dynamic objects in such a way that they move on a certain track. The movement is controlled via tags. The object moves every time the tag is updated. You can only program one type of movement for each object. Requirement You have created a tag. You have opened a screen which contains at least one dynamic object. The Inspector window is open. The toolbox window is displayed. 3270 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.1 Creating screens Procedure 1. Select the screen object you want to control dynamically. The object properties are displayed in the Inspector window. 2. In the Inspector window, select "Properties > Animations". The animations available for the selected object are displayed. 3. Select "Horizontal movement" and click the button. The parameters of the animation are displayed. A transparent copy of the object is shown in the work area, which is connected to the source object by means of an arrow. 4. Select a tag for control of movement. 5. Move the object copy to the relevant destination. The system automatically enters the pixel values of the final position in the Inspector window. 6. Customize the range of values for the tag as required. Result In Runtime, the object moves in response to every change in value of the tag that is used to control the movement. The direction of movement corresponds to the configured type of movement "horizontal". Note You configure vertical and diagonal movements similar to horizontal movements WinCC Basic V13.0 System Manual, 02/2014 3271 Visualize processes 10.1 Creating screens Configuring direct movement Introduction The object is moved respectively in x direction and y direction with "Direct movement". Two tags define the number of pixels by which the object moves from its original static start position. Requirement Two tags are set up. You have opened a screen which contains at least one dynamic object. The Inspector window is open. The toolbox window is displayed. Configuring "Direct movement" 1. Select the screen object you want to control dynamically. The object properties are displayed in the Inspector window. 2. In the Inspector window, select "Properties > Animations". 3. Select "Direct movement" and click the button. The parameters of the animation are displayed. 4. Select a tag for the X position with which the movement in x direction is controlled. 5. Select a tag for the Y position with which the movement in y direction is controlled. Result In Runtime, the object moves in response to every change in value of the tag that is used to control the movement. 3272 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.1 Creating screens Dynamizing the visibility of an object Introduction Dynamization of the "Visibility" property allows you to output an alarm to your screen, which is triggered when the tag value exceeds a critical range, for example. The alarm is cleared when the tag value returns to the non-critical range. The "Simple recipe view" and "Simple alarm view" objects are always visible. Requirement You have created a tag. You have opened a screen containing an object that you want to show or hide in Runtime. The Inspector window is open. Procedure 1. Select the screen object you want to control dynamically. The object properties are displayed in the Inspector window. 2. In the Inspector window, select "Properties > Animations". The animations available for the selected object are displayed. 3. Select "Visibility" and click the button. The parameters of the animation are displayed. 4. Select a tag. 5. Activate "Range". 6. Select, for example, "from 20" and "to 40" 7. Activate "Visible". WinCC Basic V13.0 System Manual, 02/2014 3273 Visualize processes 10.1 Creating screens Result The screen object is shown or hidden in Runtime depending on the tag value. If the tag value matches the configured range between 20 and 40, the screen object is shown. If the tag value is outside the configured range, the screen object is hidden. See also Configuring a new animation (Page 3267) Animations of object groups Applying animations to object groups The inspector window shows all objects of a group and their possible animations. The animation types which are supported by all objects in the group are also listed separately. If you configure an animation for an object group, this animation will apply to all individual objects that support this animation. 3274 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.1 Creating screens Application example The "horizontal movement" animation is configured for the object of an object group. The "direct movement" animation is configured for the whole object group. Only the animation of the object group i.e. "direct movement" is executed in Runtime. This also applies for object groups within object groups. Only the animation of the group on the top layer is listed. Animations for object groups and for multiple selection Changing animations for multiple objects For a multiple selection, the animations that are configured for the reference object appear in the Inspector window. You can change the animations as usual. The changes will apply to all the objects in the multiple selection that support the configured animation. This means that even objects for which you have not yet configured an animation will have the reference object's animation. Application example Select a button, and a circle at the same time. The button is the reference object. The "Appearance" animation is already configured for the button, so it appears in the Inspector window of the multiple selection. When you activate "Properties > Animations >Appearance > Flashing" in the inspector window, the settings of the "Appearance" animation apply for the button and for the circle. Configuring new animations for multiple objects If you configure a new animation for the objects of a multiple selection, this animation will apply to all selected objects that support the configured animation. If the new animation replaces an existing animation, a security prompt appears. Application example You select a circle, and a rectangle. The "Diagonal movement" animation is already configured for the circle. You configure the "Horizontal movement" animation for the multiple selection. This animation applies to the rectangle since no animation of the Movement type is yet configured for it. For the circle, you are asked to confirm that you want to replace the existing "Diagonal movement" animation with the new "Horizontal movement" animation. WinCC Basic V13.0 System Manual, 02/2014 3275 Visualize processes 10.1 Creating screens 10.1.4.4 Dynamize with system functions Basic on events Introduction Screen objects react to events. You configure a function list with system functions on the events of an object. Events Which events and system functions are available depends on the object used. If the operator activates a screen object for example, the configured system function is executed. You can find additional information under "Basics on the function list (Page 3498)". See also Basics on dynamization (Page 3264) Example: Configuring a button for language switching (Page 3277) Configure system function on the "Click" event (Page 3276) Configure system function on the "Click" event Introduction You configure a function list on an object event. The linked system function is executed when the event occurs in runtime. Requirements A screen is open. A button has been created in the screen. The inspector window is open. Procedure 1. Select the button. 2. Click "Properties> Events" in the Inspector window. 3. Select the "Click" event. 4. Click "Add function" in the table. 5. Select the "ShowAlarmWindow" system function. 3276 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.1 Creating screens Result The alarm window opens in the screen if the operator clicks the button in runtime. See also Basic on events (Page 3276) 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 and the "Switch" setting. 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 Basic on events (Page 3276) Button (Page 3321) WinCC Basic V13.0 System Manual, 02/2014 3277 Visualize processes 10.1 Creating screens 10.1.5 Working with function keys 10.1.5.1 Working with function keys Introduction The function key is a physical key on your HMI device and its functions can be configured. A function list can be configured for the events "Key pressed" and "Release key". A function key can be assigned global or local functions. Note Availability for specific HMI devices Function keys are not available on all HMI devices. Global function keys Global function keys always trigger the same action, regardless of the displayed screen. Global function keys are configured in the "Global Screen" editor. The global assignment applies for all the screens of the set HMI device. Global function keys reduce programming considerably, because there is no need to assign these global keys to each individual screen. Local function keys in screens Local function keys in screens can trigger a different action in each screen. This assignment applies only to the screen in which you have defined the function key. Within a screen, a function key has only one function assignment, either a global or local one. The project planner specifies which assignment has priority. Note If a screen with local function keys is overlapped by an alarm view or an alarm window, then the function keys are still active in runtime. This may happen in particular on HMI devices with a small display. Local function keys in templates Local functions keys that are assigned in templates are valid for all the screens based on this template. They can trigger a different action in every screen. Function keys for templates are assigned in the template of the "Screens" editor. Within a template, a function key has only one function assignment, either a global or local one. The project planner specifies which assignment has priority. 3278 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.1 Creating screens Hotkey assignment You can assign hotkeys, such as buttons, to control objects. The available hotkeys depend on the HMI device. Note The function key has a local or global action assigned to it. If the function key also has a hotkey assigned to it, then the hotkey function will be executed in Runtime. Graphics When a function key is placed directly next to the display, you can assign a graphic to it to make the function of the function key more clear. Display of assignment Table 10-1 Function key The following table shows which symbols display the assignment of the function keys: Description Not assigned Global assignment Assigned locally in the template Local assignment Local assignment (local assignment of the template overwrites global assignment) Local assignment (local assignment overwrites global assignment) Local assignment (local assignment overwrites local assignment of the template) Local assignment (local assignment overwrites local assignment of the template, which already overwrites global assignment) Assigning buttons with screen navigation WinCC Basic V13.0 System Manual, 02/2014 3279 Visualize processes 10.1 Creating screens Note Basic Panels The "Screen Navigation" editor is not available for Basic Panels. 10.1.5.2 Assigning function keys globally Introduction You define the global assignment of a function key in the "Global Screen" editor. The global assignment applies to all screens of the set HMI device. Note Availability for specific HMI devices Function keys are not available on all HMI devices. Requirement You have opened the project. The Inspector window is open. 3280 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.1 Creating screens Procedure Proceed as follows to assign a screen-based function to a function key: 1. To open the "Global Screen" editor, double-click "Global Screen" in the "Screen management" group of the Project window. 2. Select the desired function key. The properties of the function key are shown in the Inspector window. 3. Under "General", configure a graphic and an operator authorization for the function key. 4. Configure a function list for the required event under "Events". Result If a local assignment does not overwrite the global assignment, the assignment of the function key changes in all the screens of the set HMI device in accordance with your entry. WinCC Basic V13.0 System Manual, 02/2014 3281 Visualize processes 10.1 Creating screens 10.1.5.3 Local assignment of function keys Introduction Function keys are assigned globally and locally. A local assignment of the function keys is only valid for the screen or the template in which it was defined. The following local function keys are available: Local function keys of a screen Different functions are assigned to the function key for each screen. This assignment applies only to the screen in which you have defined the function key. Local function keys of a template You assign the function keys in a template. The assignment applies to all the screens that are based on this template and are not overwritten by a local assignment in a screen. A local assignment overwrites the global assignment of a function key. Note Availability for specific HMI devices Function keys are not available on all HMI devices. Using existing assignments The option for using existing assignments is referred to as follows in the Inspector window: In a template: "Use global assignment" In a screen: - Screen based on a template: "Use local template" - Screen not based on a template: "Use global assignment" The "Use local template" option includes the use of the local assignment in the template and the global assignment. Requirement You have opened the screen or the template in which you want to assign a function key locally. The Inspector window is open. 3282 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.1 Creating screens Procedure Proceed as follows: 1. Select the desired function key in the screen or in the template. The properties of the function key are shown in the Inspector window. 2. Click "General" in the Inspector window. 3. Disable the "Use local template" or "Use global assignment" option. 4. Under "General", configure a graphic and an operator authorization for the function key. 5. Configure a function list for the required event under "Events". Result The function key is assigned the configured function in the screen or in the template. 10.1.5.4 Assigning a function key to a function Introduction A function key can have two states: Pressed: Defined by the "Key pressed" event. Released: Defined by the "Release key" event. WinCC Basic V13.0 System Manual, 02/2014 3283 Visualize processes 10.1 Creating screens Both of these events are configured in the Inspector window of the function key. You can assign any event a function list which contains system functions or scripts. Execution of this function list is event-driven in runtime. Note Availability for specific HMI devices Function keys are not available on all HMI devices. Note Basic Panels Scripts are not available for Basic Panels. Requirement To assign the function key a global function: The "Global Screen" editor is open. To assign the function key a local function: The screen in which you want to assign a function key is open. If you want to assign a function key locally in a template: The template in which you want to assign a function key is open. The Inspector window is open. Procedure Proceed as follows: 1. Select the function key you want to define. The properties of the function key are shown in the Inspector window. 2. Configure the function list for the desired result in the Inspector window under "Properties" in the "General" group. Result The function list is executed in runtime when the operator presses or releases the function key. 10.1.5.5 Assigning operator authorization for a function key Introduction In WinCC you can assign an operator authorization for a function key in runtime. This allows you to restrict access to the function keys to specific persons or operator groups when you 3284 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.1 Creating screens configure your project. Only authorized personnel can then change important parameters and settings in runtime. You configure access protection in order to avoid operator errors and increase plant or machine security. Note Availability for specific HMI devices Function keys are not available on all HMI devices. Requirement The user groups have been defined. To protect a global function key: The "Global Screen" editor is open. If you want to protect a local function key of a screen or of a template: The screen or the template which contains the function key is open. The Inspector window is open. Procedure Proceed as follows: 1. Select the relevant function key. The properties of the function key are shown in the Inspector window. 2. Click "General" in the Inspector window. 3. In the "Authorization" list, select the user group you want to allow runtime access to the function key. WinCC Basic V13.0 System Manual, 02/2014 3285 Visualize processes 10.1 Creating screens Result The operator authorization is configured. 10.1.5.6 Assigning a function key to a graphic Introduction In order to make the function of a key more clear, you can insert a graphic in the screen alongside the function key. Graphics can only be assigned to function keys that border the screen margin of the HMI device. Note Availability for specific HMI devices Function keys are not available on all HMI devices. Requirement To assign a graphic to a global function key: The "Global Screen" editor is open. If you want to assign a graphic to a local function key in a screen or template: The screen or the template that contains the corresponding function key is open. The Inspector window is open. You have created the graphic for the function key. 3286 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.1 Creating screens Procedure Proceed as follows: 1. Select the relevant function key. The properties of the function key are shown in the Inspector window. 2. Click "General" in the Inspector window. WinCC Basic V13.0 System Manual, 02/2014 3287 Visualize processes 10.1 Creating screens 3. Click in the "Graphic" area of the list. The graphic browser of your WinCC project appears. The pane on the left side shows the external graphics which are stored in the browser. The pane on the right side shows you a preview of the graphic you have selected in the browser. Using the and icons, you can display the collection either in form of thumbnails or as a list. In order to open and edit OLE objects with the associated graphics program, double-click on the object. 4. In the browser click the desired graphic or store the relevant graphic in the graphic browser. The graphic preview is shown in the right pane. 5. Click "Select" to add the graphic to the screen. Click "Clear" to remove the graphic from the screen. Result The graphic is displayed next to the function key. 10.1.5.7 Configuring LED tags Requirements An HMI device with key operation has been created. You have created an LED tag. Procedure 1. Create a new screen. 2. Click an F-key of the HMI device. 3288 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.1 Creating screens 3. In the Inspector window, click "Properties > Properties > General". 4. Select a tag under "LED tag" in the "General > Settings" area. 5. Under "Bit" enter the correct bit number. The correct bit number depends on the HMI device and the input and output assignments on the HMI device. Assignment of inputs and outputs The exact assignment of inputs and outputs can be found under: PROFINET IO direct keys: Auto-Hotspot PROFIBUS DP direct keys: Auto-Hotspot WinCC Basic V13.0 System Manual, 02/2014 3289 Visualize processes 10.1 Creating screens 10.1.5.8 Example: Using function keys for screen navigation Task In this example you create a local function key in a screen. When the operator presses this function key, a screen change to a predefined screen is triggered, for example "Boiler 2". Note Availability for specific HMI devices Function keys are not available on all HMI devices. Requirement The screen in which you want to assign the function key is open. You have created the "Boiler 2" screen. The Inspector window is open. Procedure Proceed as follows to use the "ActivateScreen" function: 1. Select the desired function key. The properties of the function key are shown in the Inspector window. 2. Click "General." 3. To overwrite a global assignment, disable the "Use local template" option. 4. Click "Key pressed" under "Events". 3290 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.1 Creating screens 5. Select the "ActivateScreen" system function from the list. The "ActivateScreen" function appears in the "Function list" dialog box, including the "Screen name" and "Object number" parameters. 6. Select the "Boiler 2" screen from the "Screen name" list. Result The operator changes to the "Boiler 2" screen in runtime by pressing the selected function key. 10.1.6 Working with layers 10.1.6.1 Basics on working with layers Layers Use layers in order to achieve differentiated editing of the objects in a screen. A screen consists of 32 layers that you can give any names. If you assign objects to the layers, you thereby define WinCC Basic V13.0 System Manual, 02/2014 3291 Visualize processes 10.1 Creating screens the screen depth. Objects of layer 0 are located at the screen background, while objects of layer 31 are located in the foreground. The objects of a single layer are also arranged hierarchically. When you create a screen, the object inserted first is located at the rear within the layer. Each further object is placed one position towards the front. You can shift objects forwards and backwards within a layer. Principle of the layer technique Always one layer of the 32 layers is active. New objects you add to the screen are always assigned to the active layer. The number of the active level is displayed in the inspector window of the screen and in the "Layout > Layers" task card. When you open a screen, all 32 layers of the screen are displayed. You can hide all the layers except for the active layer in the inspector window of the screen and in the "Layout > Layers" task card. You then explicitly edit objects of the active layer. In the tree view of the "Layers" palette in the "Layout" task card, you administer layers and objects with drag-and-drop and the context menu. Application examples Use layers, for example, in the following cases: To hide the labeling of objects when editing, To hide objects, e.g. alarm windows, while configuring other objects 10.1.6.2 Moving objects between layers Introduction By default, a new object is inserted on the active layer. You can, however, assign an object to another layer at a later time. 3292 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.1 Creating screens Requirement A screen with an object is open. The Inspector window is open. Procedure 1. Select the object in the screen. The object properties are displayed in the Inspector window. 2. Enter the layer to which you want to move the object in "Properties > Properties > Miscellaneous > Layer" in the Inspector window. Alternatively, select the object from the "Layout" task card and drag it to the required layer. Changing the order of objects 1. Select the object in the screen. The object properties are displayed in the Inspector window. 2. To move the object to the front or back, select the "Order" > "Move backward" or "Move forward" command from the shortcut menu. Alternatively, use the or button in the toolbar. Result The object is assigned to the selected layer, and positioned at the top of the layer. 10.1.6.3 Setting the active layer Introduction The screen objects are always assigned to one of the 32 layers. There is always an active layer in the screen. New objects you add to the screen are always assigned to the active layer. The number of the active layer is indicated in the "Layer" toolbar. The active layer is indicated by the icon in the "Layout > Layers" task card. Layer 0 is the active layer when you start programming. You can activate a different layer during configuration, if necessary. Requirement You have opened a screen which contains at least one object. The Inspector window of the active screen is open. Procedure 1. Click "Properties > Properties > Layers" in the Inspector window of the current screen. 2. Enter the layer number in "Settings > Active layer". WinCC Basic V13.0 System Manual, 02/2014 3293 Visualize processes 10.1 Creating screens Alternative procedure 1. Select "Layout > Layers" in the "Layout" task card. 2. Select the "Set to active" command from the shortcut menu of a layer. Result The layer with the specified number is now active. 10.1.6.4 Show and hide layers Introduction You can show or hide the layers of a screen as required. You specify the layers that are shown in the Engineering System. When you open a screen, all the layers are always shown. Requirement The screen is opened. The "Layout" task card is open. 3294 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.1 Creating screens Procedure 1. Select the layer that you want to hide or show in the "Layout > Layers" task card. 2. Click one of the icons next to the corresponding layer: - A shown layer is hidden - A hidden layer is shown Note The active layer cannot be hidden. Alternative procedure 1. Click in an area of the screen that does not contain an object. The screen properties are shown in the Inspector window. 2. In the Inspector window, select "Properties > Properties > Layers": 3. In the list, disable the levels you wish to hide. If you activate "All ES layers" for a layer, the objects in this layer will be shown in the Engineering System. Result The layers are shown according to your settings. 10.1.6.5 Renaming layers Introduction When you create a screen, the 32 layers are numbered consecutively by default. To improve clarity, you can rename the layers to suit your requirements. WinCC Basic V13.0 System Manual, 02/2014 3295 Visualize processes 10.1 Creating screens Requirement The screen is opened. Procedure 1. Click in an area of the screen that does not contain an object. The screen properties are shown in the Inspector window. 2. In the Inspector window, select "Properties > Properties > Layers". 3. Enter the new layer name. Result The layer is displayed with the new name. 3296 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.1 Creating screens 10.1.7 Display and operating objects 10.1.7.1 Device-Specific Nature of the Objects Objects for Basic Panels Availability of display and operating objects for Basic Panels Only the objects which can be used for the device you are configuring will be shown in the object window. The following table shows the availability of indicator and operating objects for the Basic Panels. Overview KP300 Basic KTP400 Basic KTP700 Basic KP400 Basic KTP600 Basic KTP900 Basic KTP1000 Basic TP1500 Basic Bar Yes Yes Yes User view Yes Yes Yes1) Date/time field Yes Yes Yes I/O field Yes Yes Yes Ellipse Yes Yes Yes Graphic view Yes Yes Yes Graphic I/O field Yes Yes Yes Help indicator Yes No No Circle Yes Yes Yes Trend view Yes Yes Yes1) Line Yes Yes Yes Alarm view Yes Yes Yes1) Alarm indicator Yes Yes Yes Rectangle Yes Yes Yes Recipe view Yes Yes Yes1) Button Yes Yes Yes Switch Yes Yes Yes Symbolic I/O field Yes Yes Yes System diagnostics view Yes Yes Yes1) Text field Yes Yes Yes Alarm window 1) The objects are displayed on the panels as table-based objects. WinCC Basic V13.0 System Manual, 02/2014 3297 Visualize processes 10.1 Creating screens See also Overview of objects (Page 3200) 10.1.7.2 Objects Bar Application The tags are displayed graphically using the "Bar" object. The bar graph can be labeled with a scale of values. Layout In the Inspector window, you customize the settings for the position, shape, style, color, and font types of the object. You can adapt the following properties in particular: Color transition: Specifies the change in color display when limit values are exceeded. Displaying the limit lines / limit markers: Shows the configured limit as a line or marker. Define bar segments: Defines the gradations on the bar scale. Define scale gradation: Defines the subdivisions, scale markings and intervals of a bar scale. Color transition You define how the color change is represented in "Properties > Properties > Appearance" in the Inspector window. Color transition Description "Segmented" If a particular limit was reached, the bar changes color segment by segment. With segment by segment representation, you visualize, for example, which limits are exceeded by the displayed value. "Entire bar" If a particular limit was reached, the entire bar changes color. Displaying limit lines and limit markers You display the configured limit in the bar as a line or marking in Runtime using the "Lines" and "Markings" property: 1. In the Inspector window, select "Properties > Properties > Appearance": 2. Activate "Lines" and "Markings". 3298 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.1 Creating screens Define bar segments Use the "Subdivisions" property to define the number of segments into which the bar is divided by the main gradations on the scale. Use the "Interval" property to divide the distance between the main gradations. The value appears as the difference in value between two adjacent main gradations: 1. In the Inspector window, select "Properties > Properties > Scales": 2. Activate "Show scale." 3. Select the corresponding value for "Settings > Subdivisions". 4. Select the corresponding value for "Settings > Marks label". 5. Select the corresponding value for "Large interval > Interval". See also Device-Specific Nature of the Objects (Page 3297) User view Application The "User view" object is used to set up and administer users and authorizations. Note Do not use the user view in a group. WinCC Basic V13.0 System Manual, 02/2014 3299 Visualize processes 10.1 Creating screens Layout In the Inspector window, you customize the position, shape, style, color and font types of the object. You can adapt the following properties in particular: Number of lines: Specifies the maximum number of visible entries. Number of lines The number of lines in the user view displayed in Runtime is specified in the Inspector window. The setting for the number of lines is only effective if the property "Fit object to contents" is active. 1. In the Inspector window, select "Properties > Properties > View". 2. Enter an integer value under "Number of lines". 3. In the Inspector window, activate "Properties > Properties > Layout". 4. Activate "Fit object to contents". See also Device-Specific Nature of the Objects (Page 3297) Simple user view (Page 4158) Configuring a user view (Page 3480) Date/time field Use The "Date/time field" object shows the system time and the system date. The appearance of the "Date/time field" depends on the language set on the HMI device. Layout In the Inspector window, you customize the position, style, colors and font types of the object. You can adapt the following properties in particular: Display system time: Specifies that the system time is displayed. Include tag: Specifies that the time of the connected tag is displayed. Long date/time format: This setting defines the format displayed for the data and time. 3300 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.1 Creating screens Display system time The time displayed in the "Date/time field" on the HMI device is specified in the inspector window. 1. In the Inspector window, select "Properties > Properties > General". 2. Activate "Format > System time". Using tags The time of the interconnected tag is displayed in the date/time field. 1. In the Inspector window, select "Properties > Properties > General". 2. In the "Format" area, select a tag with the "DateTime" data type, e.g. an internal tag. Long date/time format Visualization of the date and time is specified in the "Format" area under "General" in the inspector window. Option Description "Enabled" Date and time are displayed in full, e.g. "Sunday, December 31, 2000 10:59:59 AM" "Disabled" Date and time are displayed in short form, e.g. "12/31/2000 10:59:59 AM" See also Device-Specific Nature of the Objects (Page 3297) I/O field Application The "I/O field" object is used to enter and display process values. WinCC Basic V13.0 System Manual, 02/2014 3301 Visualize processes 10.1 Creating screens Layout In the Inspector window, you customize the position, shape, style, color and font types of the object. You can adapt the following properties in particular: Mode: Specifies the response of the object in Runtime. Display format: Specifies the display format in the I/O field for input and output of values. Hidden input: Specifies whether the input value is displayed normally or encrypted during input. Note Reports In reports, I/O fields only output data. "Output" mode is preset. Properties for configuring input are not available, e.g. "hidden input". Mode The response of the I/O field is specified in the Inspector window in "Properties > Properties > General > Type". Mode Description "Input" Values can only be input into the I/O field in runtime. "Input/output" Values can be input and output in the I/O field in runtime. "Output" The I/O field is used for the output of values only. Layout The "display format" for the input and output of values is specified in "Properties > Properties > General > Format" in the Inspector window. Layout 3302 "Binary" Input and output of values in binary form "Date" Input and output of date information. The format depends on the language setting on the HMI device. "Date/time" Input and output of date and time information. The format depends on the language setting on the HMI device. "Decimal" Input and output of values in decimal form "Hexadecimal" Input and output of values in hexadecimal form "Time" Input and output of times. The format depends on the language setting on the HMI device. "Character string" Input and output of character strings. WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.1 Creating screens Note Data formats Not all data formats are available for selection for Runtime Professional. Hidden input In Runtime the input can be displayed normally or encrypted, for example for hidden input of a password. A "*" is displayed for every character during hidden input. The data format of the value entered cannot be recognized. 1. In the Inspector window, select "Properties > Properties > Response": 2. Activate "Hidden input". Avoid overlaps in output fields If several I/O fields are configured as output fields with a transparent background in a screen, these I/O fields may overlap. The transparent part of the one field covers the digits of the other field. This may cause display problems in Runtime. In order to avoid such overlaps, set the margins of the I/O fields to zero in the object properties under "Properties > Properties > Appearance". Activate "Properties > Properties > Layout > Fit object to contents." Limits Under "Properties > Properties > Limits" in the Inspector window, set the colors for the values that violate the high or low limits. You define the limits via the properties of a tag. In Runtime Professional, you can also define the limit range for the entry in the I/O field via "Properties > Properties > Limits". See also Device-Specific Nature of the Objects (Page 3297) Ellipse Application The "Ellipse" is an enclosed object that can be filled with a color or pattern. WinCC Basic V13.0 System Manual, 02/2014 3303 Visualize processes 10.1 Creating screens Layout In the Inspector window you can customize the settings for the object position, geometry, style, frame and color. You can adapt the following properties in particular: Horizontal radius: Specifies the horizontal radius of the elliptical object. Vertical radius: Specifies the vertical radius of the elliptical object. Horizontal radius The horizontal radius of the "Ellipse" object is specified in the Inspector window. The value is entered in pixels. 1. In the Inspector window, select "Properties > Properties > Layout". 2. Enter a value between 0 and 2500 under "Horizontal." Vertical radius The vertical radius of the "Ellipse" object is specified in the Inspector window. The value is entered in pixels. 1. In the Inspector window, select "Properties > Properties > Layout". 2. Enter a value between 0 and 2500 at "Vertical." See also Device-Specific Nature of the Objects (Page 3297) Rotating objects (Page 3215) Flipping objects (Page 3217) Designing a border (Page 3224) Graphic view Application The "Graphic view" object is used to display graphics. 3304 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.1 Creating screens Layout In the Inspector window, you customize the position, shape, style, color and font types of the object. You can adapt the following properties in particular: Graphic: Specifies the graphic file that is displayed in the object. Stretch graphic: Specifies the automatic size stretching for objects with graphics. Transparent color: Specify whether or not the transparent color is used for the graphic. Inserting graphics The following graphic format is used in the "Graphic view" object: *.bmp, *.tif, *.png, *.ico, *.emf, *.wmf, *.gif, *.jpg or *.jpeg. You may also use graphics as OLE objects in the Graphic view . 1. In the Inspector window, select "Properties > Properties > General": 2. Select the graphic that you wish to insert. The graphic preview is shown in the right pane. 3. Click "Apply" to insert the graphic in the Graphic view . Stretch graphic Whether a graphic displayed in a Graphic view is stretched to the size of the Graphic view in runtime is specified in the Inspector window. 1. Click "Properties > Properties > Layout" in the inspector window. 2. Select the required size adjustment for the graphic. Transparent color This property defines whether the transparent color is used for the graphic to be displayed. 1. Click "Properties > Properties > Appearance" in the inspector window: 2. Activate "Background > Transparent". 3. Select a transparent color. Note When using bitmaps in WinCC screens the "Transparent color" setting demands a high character performance in the layout on the panel. Visualization performance is enhanced by disabling the "Transparent" setting in the properties of the relevant display object. This restriction applies in particular when bitmaps are used as background image. Note Basic Panels The "Transparent" property is not available for Basic Panels. WinCC Basic V13.0 System Manual, 02/2014 3305 Visualize processes 10.1 Creating screens See also Device-Specific Nature of the Objects (Page 3297) Storing an external image in the graphics library. (Page 3233) Options for Editing Objects (Page 3203) Objects for Basic Panels (Page 3297) Graphic I/O field Application The "Graphic I/O field" object can be used to configure a list for display and selection of graphic files. Layout In the Inspector window, you customize the position, shape, style, color and font types of the object. You can adapt the following properties in particular: Mode: Specifies the response of the object in Runtime. Scroll bar type: Specifies the graphic layout of the scroll bar. Note Basic Panels The scroll bar is not available for Basic Panels. Note Reports Graphic I/O fields output exclusively graphics in reports. "Output" mode is preset. Properties for configuring the selection of graphics are not available, e.g. "scroll bar". Mode The response of the "Graphic I/O field" object is specified under "Properties > Properties > General > Type > Mode" in the Inspector window. 3306 Mode Description "Input" The "Graphic I/O field" object is only used to select graphics. "Input/output" The "Graphic I/O field" object is used to select and display graphics. WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.1 Creating screens Mode Description "Output" The "Graphic I/O field" object is used to display graphics only. "Two states" The "Graphic I/O field" object is only used to display graphics and can have a maximum of two states. You use no graphics list but insert one graphic each for the "ON" and "OFF" state. Stretch graphic Whether a graphic displayed in a graphic I/O field is stretched to the size of the view in runtime is specified in the Inspector window. 1. In the Inspector window, select "Properties > Properties > Layout". 2. Select the required size adjustment for the graphic. Scroll bar type The response for the graphic representation of the scroll bar is specified under "Properties > Properties > Appearance > Scroll Bar > Type" in the Inspector window. Type Description "Permanent" The scroll bar is always visible. "No scrollbar" The scroll bar is not visible. "Visible after clicking" The scroll bar is made visible by a mouse click. See also Device-Specific Nature of the Objects (Page 3297) Symbolic I/O field (Page 3323) Help indicator Application The object "help indicator" is available for the HMI devices OP 73 and KP300 Basic. If a a tooltip exists for the selected object, the help indicator is displayed during runtime. If a tooltip was configured for the opened screen, the help indicator always remains visible. You configure the object "help indicator" exclusively in the global screen. WinCC Basic V13.0 System Manual, 02/2014 3307 Visualize processes 10.1 Creating screens Layout You can adapt the following properties in the Inspector window: Position: Determines the position of the object "Help indicator." Position You can use this property to set the position of the object "Help indicator." 1. Select the object "Help indicator" in the template. 2. In the Inspector window, select "Properties > Properties > Layout". 3. Enter a value for X and Y. You can also use the cursor keys to position the selected object. If you have configured a screen object at this position, the visible help indicator covers the screen object. The help indicator is covered only by incoming system alarms and dialogs. See also Device-Specific Nature of the Objects (Page 3297) Circle Application The "Circle" object is a closed object which can be filled with a color or pattern. Layout In the Inspector window you can customize the settings for the object position, geometry, style, frame and color. You can adapt the following properties in particular: Radius: Specifies the size of the circle. Radius The radius of the "Circle" object is specified in the Inspector window. The value is entered in pixels. 1. In the Inspector window, select "Properties > Properties > Layout". 2. Enter a value between 0 and 2500 in the "Radius" area. See also Device-Specific Nature of the Objects (Page 3297) 3308 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.1 Creating screens Trend view Application The trend view is meant for the graphical representation of tag values from the current process or from a log in form of trends. Layout In the Inspector window, you customize the position, geometry, style, color, and font types of the object. You can adapt the following properties in particular: Display value table, ruler and grid: Specifies whether a value table, a ruler or a grid is displayed in addition to the coordinate system to improve legibility. Toolbars: Defines the display of the control elements. Display value table, ruler and grid For improved legibility a value table, a ruler and a grid can be displayed in Runtime. 1. Activate "Properties > Properties > Appearance > Show ruler". 2. Activate "Properties > Properties > Table > Show table". 3. Activate "Properties > Properties > Table > Show grid". WinCC Basic V13.0 System Manual, 02/2014 3309 Visualize processes 10.1 Creating screens Toolbars The layout of the control elements is defined in the "Properties > Properties > Toolbar" inspector window. Note Basic Panels As archiving is not possible for Basic Panels, the control elements are not available. Toolbar button Brief description Description "Go to start" Scrolls back to the beginning of the trend recording. The start values with which the trend recording started are displayed. "Zoom in" Zooms out of the displayed time section "Zoom out" Zooms into the displayed time section. "Ruler backward" Moves the ruler back. "Ruler forward" Moves the ruler forward. "Backward" Scrolls back one display width. "Forward" Scrolls forward one display width. "Ruler" Shows or hides the ruler. The ruler displays the Xvalue associated with a Y-value. "Start/stop" Stops trend recording or continues trend recording. Configuration behavior Displaying column headers The layout of the table in the trend view depends on the view settings in the Control Panel. Depending on the setting, the column headers may be truncated. This setting is found under "Display > Appearance" in the control panel. To display column headers correctly, set the display in "Windows and buttons" to "Windows Classic" style. This behavior only occurs during configuration. The column headers are displayed correctly in Runtime. Consistency test If warnings or errors are displayed in the output window during a consistency check in connection with trend views, clicking "Go to Error/Tag" on the shortcut menu will not always take you to the exact error position. In some cases only the trend view is shown as cause of error. 3310 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.1 Creating screens Adding, configuring, and removing trends The trends of the trend view are managed in the Inspector window under "Properties > Properties > Trend". You can copy trends between different trend views. See also Device-Specific Nature of the Objects (Page 3297) Configuring trend displays for values from the PLC (Page 3369) Touch and key operation (Page 4152) Overview (Page 4151) Line Application The "Line" object is an open object. The line length and gradient slope are defined by the height and width of the rectangle enclosing the object. Layout In the Inspector window, you customize the settings for the object position, shape, style, and color. You can adapt the following properties in particular: Line style Line start and end Line style The representation of the line is specified under "Properties > Properties > Appearance" in the Inspector window. The line is shown without interruption if you select "Solid", for example. Note The line styles available depend on the selected HMI device. Line start and end The start and end points of the line are specified under "Properties > Properties > Appearance > Line ends" in the Inspector window. WinCC Basic V13.0 System Manual, 02/2014 3311 Visualize processes 10.1 Creating screens Use arrow point, for example, as start and end point. The available start and end points depend on the device. See also Device-Specific Nature of the Objects (Page 3297) Alarm view Application Alarms are indicated in the Alarm view or in the Alarm window of the HMI device. The following screen contains a simple alarm view: Layout In the Inspector window, you customize the position, geometry, style, color and font types of the object. Note The fonts available for selection depend on the fonts you have configured in the Runtime settings under "Language & font" and the fonts supported by your HMI device. You can adapt the following properties in particular: 3312 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.1 Creating screens Control elements: Defines the operator controls of the alarm display. Alarm classes: This setting defines which alarm classes are displayed in the alarm view. Columns: Specifies the displayed columns in runtime. Note If you have different alarm classes output, these will be initially sorted into alarm classes in runtime, and then by when the alarm occurred. Control elements The control elements that can be used to control the alarm display in runtime are specified in the Inspector window under "Display > Settings". The following table shows the control elements in the alarm view, and what they do: Button Function "Info text" Displays info text for an alarm. "Acknowledge" Acknowledges an alarm. "Loop-In-Alarm" If a screen change is configured, the display switches to a screen containing information about the alarm. Select alarm classes 1. Click "Properties" in the Inspector window. 2. Under "Alarm classes" activate the alarm classes to be displayed in the alarm view in runtime . Define columns Define the columns to be displayed in the alarm view in runtime in the Inspector window. 1. In the Inspector window, click "Properties > Columns". 2. Activate the columns that are to be displayed in runtime under "Columns". Displaying column headers The layout of the alarm view is dependent on the view settings in the control panel. Depending on the setting, the column headers may be truncated. This setting is found under "Display > Layout tab" in the control panel. To display column headers correctly, set the display in "Windows and buttons" to "Windows Classic" style. WinCC Basic V13.0 System Manual, 02/2014 3313 Visualize processes 10.1 Creating screens This behavior only occurs during configuration. The column headers are displayed correctly in runtime. Note In the engineering system you can dynamically control the visibility of an object, for example, in the "Animations" group of the Inspector window. In runtime, the "Simple alarm view" does not support animations. If you have configured an animation and, for example, wish to perform a consistency check of the project, then an error alarm is issued in the Output window. See also Device-Specific Nature of the Objects (Page 3297) Alarm window (Page 3314) Alarm indicator (Page 3317) Configuring an alarm view (Page 3395) Alarm window Use Alarms are indicated in the Alarm view or in the Alarm window of the HMI device. The layout and operation of the Alarm window are similar to that of the Alarm view. The Alarm window has the following characteristics that are the same as in the Alarm view: Alarm window Alarm line: The alarm line is not available on Basic Panels. The Alarm window is configured in the "Global screen" editor. The alarm window is not assigned to any screen. Depending on the configuration the alarm window is opened when an alarm that belongs to a specific alarm class is active. Depending on the configuration, it is not closed until the alarm is acknowledged. 3314 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.1 Creating screens Note In the engineering system you dynamize, for example, the visibility of an object in "Properties > Animations" in the Inspector window. In runtime, the "Simple alarm window" object does not support animations. If you have configured an animation and, for example, wish to perform a consistency check of the project, then an error alarm is issued in the Output window. Layout In the Inspector window, you customize the position, geometry, style, color and font types of the object. You configure the Alarm window in the same way as the Alarm view. In addition you adapt the following properties: Fixed alarm window: Specifies that the Alarm window retains the focus after a screen change. Window: You define the operator input and response of the Alarm window in runtime. Note If you have different alarm classes output, these will be initially sorted into alarm classes in runtime, and then by when the alarm occurred. Operator controls The control elements that can be used to control the alarm view in runtime are specified in the Inspector window under "Properties >Display > Settings". The following table shows the control elements in the Alarm window, and what they do: Button Function "Tooltip" Displays a tooltip for an alarm. "Acknowledge" Acknowledges an alarm. "Loop-In-Alarm" If a screen change is configured, the display switches to a screen containing information about the alarm. Access protection in Runtime Configure access protection under "Properties > Properties > Security" in the Inspector window of the alarm view. If a logged-on user has the required authorization, he can acknowledge and edit alarms using the operator controls in the alarm view. If the logged-in user does not have WinCC Basic V13.0 System Manual, 02/2014 3315 Visualize processes 10.1 Creating screens the required authorization, or if no user is logged in, clicking the "Acknowledge" or "Edit" buttons or double-clicking an alarm line opens the login dialog box. Note Basic Panels Access protection is not available for Basic Panels. Activating the focus of the Alarm window Select the following option so that the Alarm window does not lose the focus after a screen change: 1. In the Inspector window, select "Properties > Properties > Mode". 2. Enable "Label". Window Define the response of the Alarm window under "Properties > Properties > Mode > Window" in the Inspector window. The following table shows the possible properties: Option Function Automatic display The Alarm window is automatically displayed when a system alarm occurs, for example. Closable The window closes again after a set time has elapsed. You define the display duration in the alarm settings. Modal The Alarm window is linked to a confirmation, such as: Alarm must be acknowledged. If the modal alarm window has the focus, the buttons in the screen behind it cannot be used. The functions configured on a function key are carried out. Sizeable You can change the size of the Alarm window in runtime. See also Device-Specific Nature of the Objects (Page 3297) Alarm view (Page 3312) Configuring an alarm window (Page 3396) 3316 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.1 Creating screens Alarm indicator Application The alarm indicator is a graphic symbol that shows current errors or errors that need to be acknowledged, depending on the configuration. The alarm indicator is configured in the "Global screen" editor. The following figure shows an alarm indicator: Alarm indicator OP 73 A "simple" alarm indicator is available for the HMI OP 73. The following diagram shows the alarm indicator for the OP 73 HMI devices: The "simple" alarm indicator shows alarms to be acknowledged or alarms which have already been acknowledged and have not yet gone. Only the position can be defined for the "simple" alarm indicator. The alarm indicator is displayed on the device at the selected position. If you have configured a screen object at this position, the visible alarm indicator covers the screen object. The alarm indicator is covered by system dialogs, such as the login dialog, Help dialog, and alarm windows. Layout In the Inspector window, you customize the position, shape, style, color and font types of the object. You can adapt the following properties in particular: Alarm classes: Establishes the alarm classes where the alarm indicator is displayed. Operator control in Runtime: Defines the operator actions in Runtime that cause the Alarm window to open. Alarm classes You define which alarm classes are shown with an alarm indicator in "General > Alarm classes" in the Inspector window. Alarm classes, such as "Warnings" or "Errors". Define operator control in Runtime 1. Select the alarm indicator in the screen. 2. Click "Events > Click" or "Click when flashing" in the Inspector window. 3. The "function list" opens. Click the first line of the function list. The list of system functions, and scripts available in the project opens. WinCC Basic V13.0 System Manual, 02/2014 3317 Visualize processes 10.1 Creating screens 4. Select the "ShowAlarmWindow". system function under "Alarms." 5. Under "object name" select the name of the Alarm window from the selection list. Under "Layout", define whether the Alarm window should be visible, hidden, or should toggle between the two states. See also Device-Specific Nature of the Objects (Page 3297) Alarm view (Page 3312) Configuring an alarm indicator (Page 3397) Rectangle Application The "Rectangle" is a closed object which you can fill with a color. Layout In the Inspector window, you customize the position, shape, style, color and font types of the object. You can adapt the following properties in particular: Corner radius: Specifies the horizontal and vertical distance between the corner of the rectangle and the start point of a rounded corner. Corner radius The corners of the "Rectangle" object can be rounded to suit your requirements. When the properties "X" and "Y" are set to the 100 % value, the rectangle is displayed as an ellipse. As soon as one of the properties has the value 0%, a normal rectangle without a rounded corner is shown. 1. Click "Properties > Properties > Layout" in the inspector window. 2. Enter a value for "X" in the "Corner radius" area. The input value is the percentage proportion of half the width of the rectangle. 3. Enter a value for "Y" in the "Corner radius" area. The input value is the percentage proportion of half the height of the rectangle. 3318 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.1 Creating screens See also Device-Specific Nature of the Objects (Page 3297) Rotating objects (Page 3215) Flipping objects (Page 3217) Recipe view Application The "Recipe view" object is used to display and modify recipes. Layout In the Inspector window, you customize the position, geometry, style, color and font types of the object. You can adapt the following properties in particular: Toolbar: Specifies the menu commands of the recipe view. Toolbar The menu items with which the recipe view is operated in Runtime are configured under "Properties > Properties > Toolbar" in the Inspector window. WinCC Basic V13.0 System Manual, 02/2014 Menu command Description "Tooltip" Calls up the configured tooltip for the selected recipe. "New record" Creates a new recipe record in the recipe. "Delete record" Deletes the selected record. "Saving" Saves the modified record with its current name. "Save as" Saves the modified record with a new name. "Write to PLC" Sends the current value to the PLC. "Read from PLC" Reads the current value from the PLC. 3319 Visualize processes 10.1 Creating screens Menu command Description "Rename" Specifies that the "Rename" button is shown. "Forward" Specifies that the menu buttons are visible. "Back" Specifies that the "Back" button is shown. See also Device-Specific Nature of the Objects (Page 3297) Simple recipe view (Page 3441) Displaying recipes (Page 3436) Configuring the simple recipe view (Page 3452) Description of the simple recipe view (Page 3455) Switch Application The "Switch" object is used to configure a switch that is used to switch between two predefined states in runtime. The current state of the "Switch" object can be visualized with either a label or a graphic. The following figure shows a "Switch" type switch. 3320 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.1 Creating screens Layout In the Inspector window, you customize the position, shape, style, color and font types of the object. In particular, you can customize the following property: Type: Defines the graphic representation of the object. Type Button visualization is specified at "Properties > Properties > General >Type" in the Inspector window. Type Description "Switch" The two states of the "Switch" are displayed in the form of a switch. The position of the switch indicates the current state. The state is changed in runtime by sliding the switch. You specify the direction of movement of the switch in "Switch orientation" with this type. "Switch with text" The switch is shown as a button. The current state is visualized with a label. In runtime click on the button to actuate the switch. "Switch with graphic" The switch is shown as a button. The current state is visualized with a graphic. In runtime click on the button to actuate the switch. Note Basic Panels The "Switch" type is not available for Basic Panels. See also Device-Specific Nature of the Objects (Page 3297) Overview of objects (Page 3200) Button Application The "Button" object allows you to configure an object that the operator can use in runtime to execute any configurable function. WinCC Basic V13.0 System Manual, 02/2014 3321 Visualize processes 10.1 Creating screens Layout In the Inspector window, you customize the position, shape, style, color and font types of the object. You can adapt the following properties in particular: Mode: Defines the graphic representation of the object. Text / Graphic: Defines whether the Graphic view is static or dynamic. Define hotkey: Defines a key, or shortcut that the operator can use to actuate the button. Note You can only define a hotkey for HMI devices with keys. Mode The button display is defined in "Properties > Properties > General >Mode" in the Inspector window. Mode Description "Invisible" The button is not visible in runtime. "Text" The button is displayed with text. This text explains the function of the button. "Graphic" The button is displayed with a graphic. This graphics represents the function of the button. Depending on the device, further options are available. Text / Graphic The "Mode" property settings are used to define whether the display is static or dynamic. The display is defined in "Properties > Properties > General >Text" or "Graphic" in the Inspector window. You can, for example, select the following options for the "Graphic" or "Text" type. Type Option Description "Graphic" "Graphic" Use "Graphic when button is "not pressed"" to specify a graphic displayed in the button for the "OFF" state. Use "Graphic when button is "pressed"" to specify a graphic for the "ON" state. "Text" "Graphics list" The graphic in the button depends on the state. The corresponding entry from the graphics list is displayed depending on the state. "Text" Use "Text when button is "not pressed"" to specify the text displayed in the button for the "OFF" state. Use "Text when button is "pressed"" to specify text for the "ON" state. "Text list" 3322 The text in the button depends on the state. The entry from the text list corresponding to the state is displayed. WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.1 Creating screens Define hotkey In the Inspector window, a key or key combination is defined that the operator can use to control the button in runtime. 1. In the Inspector window, select "Properties > Properties > General". 2. Select a key or key combination from the selection list in the "Hotkey" area. See also Device-Specific Nature of the Objects (Page 3297) Example: Configuring a button for language switching (Page 3277) Example: Configuring a button with logon dialog box (Page 3487) Example: Configuring a button with access protection (Page 3491) Symbolic I/O field Application The "Symbolic I/O field" object can be used to configure a selection list for input and output of texts in runtime. Layout In the Inspector window, you customize the position, shape, style, color and font types of the object. You can adapt the following properties in particular: Mode: Specifies the response of the object in runtime. Text list: Specifies the text list that is linked to the object. Button for selection list: Specifies that the object has a button to open the selection list. Note Reports In reports, symbolic I/O fields only output data. "Output" mode is preset. Properties for configuring the selection of graphics are not available, e.g. "button for selection list". WinCC Basic V13.0 System Manual, 02/2014 3323 Visualize processes 10.1 Creating screens Mode The response of the symbolic I/O field is specified in the Inspector window in "Properties > Properties > General > Type". Mode Description "Output" The symbolic I/O field is used to output values. "Input" The symbolic I/O field is used to input values. "Input/output" The symbolic I/O field is used for the input and output of values. "Two states" The symbolic I/O field is used only to output values and has a maximum of two states. The field switches between two predefined texts. This is used, for example, to visualize the two states of a valve: closed or open. Note The behavior possible for the symbolic I/O field depends on the Runtime. Text list In the Inspector window, you specify which text list is linked to the symbolic I/O field. 1. In the Inspector window, select "Properties > Properties > General". 2. Under "Contents" open the selection list for "Text list". 3. Select a text list. Button for selection list The "Button for selection list" property is used to display a button for opening the selection list. 1. Select "Properties > Properties > Layout" in the Inspector window. 2. Activate "Response > Button for selection list". Note Basic Panels The "Button for selection list" option is not available for Basic Panels. See also Device-Specific Nature of the Objects (Page 3297) Graphic I/O field (Page 3306) 3324 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.1 Creating screens System diagnostics view Introduction The system diagnostics view offers you an overview of all the available devices in your plant. You navigate directly to the cause of the error and to the relevant device. You have access to all diagnostics-capable devices which you have configured in the "Devices & networks" editor. Use The system diagnostics view enables you to achieve the maximum level of detail of the diagnostics data. A precise diagnosis is possible, as all the available data is displayed. You have the system status of the entire plant at one glance. Three different views are available in the system diagnostics view. Device view Diagnostic buffer view Detail view Device view The device view of the system diagnostics view shows all the available connections in tabular form. Double-clicking a connection opens the detail view. The device view is only displayed if more than one connection has been created in the "Devices & Networks" editor. Diagnostic buffer view In the diagnostic buffer view, the current data from the diagnostic buffer is displayed. Detail view The detail view shows detailed information on the selected connection. You cannot sort error texts in the detail view. The detail view is only available if there is an integrated connection to an S7 1200 or S7 1500. WinCC Basic V13.0 System Manual, 02/2014 3325 Visualize processes 10.1 Creating screens Layout You change the settings for the position, geometry, style, color, and font of the object in the Inspector window. You can adapt the following properties in particular: Lines per entry: Specifies the number of lines that are shown for an entry. Configuring the system diagnostics view 1. Drag-and-drop the system diagnostics view from the toolbox. 2. In the Inspector window, select "Properties > Layout". 3. Enter a number under "Lines per entry", i.e. 5. 4. Select an authorization for operation in "Properties > Properties > Security". See also System diagnostics views (Page 3430) Text field Application The "Text field" is a closed object which you can fill with a color. Layout In the Inspector window, you customize the position, shape, style, color and font types of the object. You can adapt the following properties in particular: Text: Specifies the text for the text field. Size of text field: Defines whether the size of the object is adapted to the space required by the largest list entry. Text Specify the text for the text field in the Inspector window. 1. In the Inspector window, select "Properties > Properties > General". 2. Enter a text. For texts over several lines you can set a line break by pressing the key combination <Shift + Enter>. 3326 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.1 Creating screens Size of text field In the Inspector window, you can define whether the size of the object is adapted to the space required by the largest list entry. 1. In the Inspector window, select "Properties > Properties > Layout". 2. Activate "Resize > Fit to contents". See also Device-Specific Nature of the Objects (Page 3297) 10.1.8 Configuring screen navigation 10.1.8.1 Basics for screen navigation Types of navigation for the screen change For a production process consisting of multiple subprocesses, you will configure multiple screens. You have the following options to enable the operator to switch from one screen to the next in Runtime: Assign buttons to screen changes Configuring screen changes at local function keys Procedure Before you create a screen change, define the plant structure and derive from it the screen changes that you want to configure. Create the start screen under "Runtime Settings > General > Start screen". See also Assign button with screen change (Page 3328) WinCC Basic V13.0 System Manual, 02/2014 3327 Visualize processes 10.1 Creating screens 10.1.8.2 Assign button with screen change Introduction Configure a button in the screen to switch between the screens on the HMI device during operation. Note If you have set the "Visibility" of animations to "Hidden" in the Inspector window of a screen, this screen cannot be called up in Runtime. Requirements You have created the project. You have created the "Screen_2" screen. "Screen_1" is created. Procedure 1. Double-click "Screen_1" in the project navigation. The screen is displayed in the work area. 2. Move "Screen_2" from the project tree to the open screen by drag&drop. A button with the name "Screen_1" is inserted. 3. In the Inspector window, select "Properties > Events > Click". The "ActivateScreen" system function is displayed in the "Function list". 4. At the "Object number" attribute, define, if required, the tab sequence number of the object on which the focus is to be set after a screen change. You can also specify a tag that contains the object number. 3328 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.1 Creating screens Alternative procedure 1. Move a button from the "Tools" task card to "Screen2" by drag&drop. 2. In the Inspector window, select "Properties > Events > Click". 3. Select the "ActivateScreen" system function. 4. Select "Screen_2" for the "Screen number". Result The operator goes to "Screen_1 with the button in Runtime. If you have specified an object number, the object with this object number has the focus following a screen change. See also Basics for screen navigation (Page 3327) 10.1.8.3 Assign screen change to function key Introduction Configure a screen change function key in the screen to switch between the screens on the HMI device during operation. Note If you have set the "Visibility" of animations to "Hidden" in the inspector window of a screen, this screen cannot be called up in Runtime. Requirements You have created a project. You have created the "Screen_2" screen. You have created the "Screen_1" screen. Procedure 1. Double click "Screen_1" in the project tree. The screen is displayed in the work area. 2. Move "Screen_2" from the project tree to a function key, e.g. "F2". The configured function key displays a yellow triangle. 3. Click "Properties > Events > Press key" in the inspector window. The "ActivateScreen" system function is displayed. WinCC Basic V13.0 System Manual, 02/2014 3329 Visualize processes 10.2 Working with Tags Result The operator goes to the specified "Screen_2" with function key "F2" in Runtime. 10.2 Working with Tags 10.2.1 Basics 10.2.1.1 Basics of tags Introduction Process values are forwarded in runtime using tags. Process values are data which is stored in the memory of one of the connected automation systems. They represent the status of a plant in the form of temperatures, fill levels or switching states, for example. Define external tags for processing the process values in WinCC. WinCC works with two types of tag: External tags Internal tags The external tags form the link between WinCC and the automation systems. The values of external tags correspond to the process values from the memory of an automation system. The value of an external tag is determined by reading the process value from the memory of the automation system. It is also possible to rewrite a process value in the memory of the automation system. ([WHUQDOWDJ 3URFHVVYDOXH :LQ&& $XWRPDWLRQV\VWHP Internal tags do not have a process link and only convey values within the WinCC. Tag values are only available while Runtime is running. Tags in WinCC For external tags, the properties of the tag are used to define the connection that the WinCC uses to communicate with the automation system and form of data exchange. Tags that are not supplied with values by the process - the internal tags - are not connected to the automation system. In the tag's "Connection" property, this is identified by the "Internal tag" entry. 3330 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.2 Working with Tags You can create tags in different tag tables for greater clarity. You then directly access the individual tag tables in the "HMI tags" node in the project tree. The tags from all tag tables can be displayed with the help of the table "Show all tags". See also Overview of HMI tag tables (Page 3331) Internal tags (Page 3336) External tags (Page 3332) Addressing external tags (Page 3334) Creating external tags (Page 3337) Basics on arrays (Page 3364) Cycle basics (Page 3367) 10.2.1.2 Overview of HMI tag tables Introduction HMI tag tables contain the definitions of the HMI tags that apply across all devices. A tag table is created automatically for each HMI device created in the project. In the project tree there is an "HMI tags" folder for each HMI device. The following tables can be contained in this folder: Standard tag table User-defined tag tables All tags The following tables are also available in an HMI tag table: Discrete alarms Analog alarms With the help of these tables you configure alarms for the currently selected HMI tag. In the project tree you can create additional tag tables in the HMI tags folder and use these to sort and group tags and constants. You can move tags to a different tag table using a dragand-drop operation or with the help of the "Tag table" field. You activate the "Tag table" field using the shortcut menu of the column headings. Standard tag table There is one standard tag table for each HMI device of the project. It cannot be deleted, renamed or moved. The standard tag table contains HMI tags and, depending on the HMI device, also system tags. You can declare all HMI tags in the standard tag table, or create additional user-defined tag tables as you want. WinCC Basic V13.0 System Manual, 02/2014 3331 Visualize processes 10.2 Working with Tags User-defined tag tables You can create multiple user-defined tag tables for each HMI device in order to group tags according to your requirements. You can rename, gather into groups, or delete user-defined tag tables. To group tag tables, create additional subfolders in the HMI tags folder. All tags The "All tags" table shows an overview of all HMI tags and system tags of the HMI device in question. This table cannot be deleted, renamed or moved. Discrete alarms table In the "Discrete alarms" table, you configure discrete alarms to the HMI tag selected in the HMI tag table. When you configure a discrete alarm, multiple selection in the HMI tag table is not possible. You configure the discrete alarms for each HMI tag separately. Analog alarms table In the "Analog alarms" table, you configure analog alarms to the HMI tag selected in the HMI tag table. When you configure an analog alarm, multiple selection in the HMI tag table is not possible. You configure the analog alarms for each HMI tag separately. See also Basics of tags (Page 3330) 10.2.1.3 External tags Introduction External tags allow communication (data exchange) between the components of an automation system, for example, between an HMI device and a PLC. Principle An external tag is the image of a defined memory location in the PLC. You have read and write access to this storage location from both the HMI device and from the PLC. Since external tags are the image of a storage location in the PLC, the applicable data types depend on the PLC which is connected to the HMI device. If you write a PLC control program in STEP 7, the PLC tags created in the control program will be added to the PLC tag table. If you want to connect an external tag to a PLC tag, access the PLC tags directly via the PLC tag table and connect them to the external tag. 3332 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.2 Working with Tags Data types All the data types which are available at the connected PLC are available at an external tag in WinCC. Information about data types which are available for connection to other PLCs can be found in the documentation about the respective communication drivers. See "Basics of communication (Page 3595)" for additional information. Note As well as external tags, area pointers are also available for communication between the HMI device and PLC. You can set up and enable the area indicators in the "Connections" editor. Synchronization with PLC tags A variety of options for synchronizing external tags with the PLC tags are available in the Runtime settings under "Settings for tags". When you perform synchronization, you have the option of automatically applying the tag names of the PLC to external tags and reconnecting the existing tags. The generated tag name is derived from the position of the data value in the hierarchical structure of the data block. Update of tag values For external tags, the current tag values are transmitted in runtime via the communication connection between WinCC and the connected automation systems and then saved in the runtime memory. Next, the tag value will be updated to the set cycle time. For use in the runtime project, WinCC accesses tag values in the runtime memory that were read from the PLC at the previous cycle time. As a result, the value in the PLC can already change whilst the value from the runtime memory is being processed. Note PLC array elements in conjunction with S7-1200 or S7-1500 The index of the PLC array elements can begin with any number. In WinCC, indexing always starts with 0. A PLC tag "Array [1..3] of Int", for example, is mapped to "Array [0..2] of Int" in WinCC. When you access an array in a script, pay attention to the correct indexing. See also Addressing external tags (Page 3334) Basics of communication (Page 3595) Basics of tags (Page 3330) WinCC Basic V13.0 System Manual, 02/2014 3333 Visualize processes 10.2 Working with Tags 10.2.1.4 Addressing external tags Introduction The options for addressing external tags depend on the type of connection between WinCC and the PLC in question. A distinction must be made between the following connection types: Integrated connection Connections of devices which are within a project and were created with the "Devices & Networks" editor are referred to as integrated connections. Non-integrated connection Connections of devices which were created with the "Connections" editor are referred to as non-integrated connections. It is not necessary that all of the devices be within a single project. The connection type can also be recognized by its icon. Integrated connection Non-integrated connection You can find additional information in the section "Basics of communication (Page 3595)". Addressing with integrated connections An integrated connection offers the advantage that you can address a tag both symbolically and absolutely. For symbolic addressing, you select the PLC tag via its name and connect it to the HMI tag. The valid data type for the HMI tag is automatically selected by the system. You have to distinguish between the following cases when you address elements in data blocks: Symbolic addressing of data blocks with optimized access and standard access: During the symbolic addressing of a data block with optimized access and standard access, the address of an element in the data block is dynamically assigned and is automatically adopted in the HMI tag in the event of a change. You do not need to compile the connected data block or the WinCC project for this step. For data blocks with optimized access, only symbolic addressing is available. For symbolic addressing of elements in a data block, you only need to recompile and reload the WinCC project in case of the following changes: If the name or the data type of the linked data block element or global PLC tag has changed. If the name or the data type of the higher level structure node of a linked element in the data block element or global PLC tag has changed. If the name of the connected data block has changed. Symbolic addressing is currently available with the following PLCs: SIMATIC S7 1200 SIMATIC S7 1500 Symbolic addressing is also available if you have an integrated link. 3334 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.2 Working with Tags Note Symbolic addressing is not possible if you are using the "Date/Time" area pointer. You can also use absolute addressing with an integrated connection. You have to use absolute addressing for PLC tags from a SIMATIC S7 300/400 PLC. If you have connected an HMI tag with a PLC tag and the address of the PLC tag changes, you only have to recompile the control program to update the new address in WinCC. Then you recompile the WinCC project and load it onto the HMI device. In WinCC, symbolic addressing is the default method. To change the default setting, select the menu command "Options > Settings". Select "Visualization > Tags" in the "Settings" dialog. If required, disable the "Symbolic access" option. The availability of an integrated connection depends on the PLC used. The following table shows the availability: PLC Integrated connection Comments S7 300/400 Yes The linking of tags is not checked in Runtime. If the tag address changes in the PLC and the HMI device is not compiled again and loaded, the change is not registered in runtime. S7 1200 Yes A validity check of the tag connection is performed in runtime during symbolic addressing. If an address is changed in the PLC, the change is registered and an error message is issued. In the case of absolute addressing, the following behavior applies to the S7 300/400. S7 1500 Yes A validity check of the tag connection is performed in runtime during symbolic addressing. If an address is changed in the PLC, the change is registered and an error message is issued. In the case of absolute addressing, the following behavior applies to the S7 300/400. Create an integrated connection in the "Devices & Networks" editor. If the PLC is contained in the project and integrated connections are supported, you can then also have the connection created automatically. To do this, when configuring the HMI tag, simply select an existing PLC tag to which you want to connect the HMI tag. The integrated connection is then automatically created by the system. Addressing with non-integrated connections In the case of a project with a non-integrated connection, you always configure a tag connection with absolute addressing. Select the valid data type yourself. If the address of a PLC tag changes in a project with a non-integrated connection during the course of the project, you also have to make the change in WinCC. The tag connection cannot be checked for validity in Runtime, an error message is not issued. A non-integrated connection is available for all supported PLCs. WinCC Basic V13.0 System Manual, 02/2014 3335 Visualize processes 10.2 Working with Tags Symbolic addressing is not available in a non-integrated connection. With a non-integrated connection, the control program does not need to be part of the WinCC project. You can perform the configuration of the PLC and the WinCC project independently of each other. For configuration in WinCC, only the addresses used in the PLC and their function have to be known. See also External tags (Page 3332) Basics of tags (Page 3330) Basics of communication (Page 3595) 10.2.1.5 Internal tags Introduction Internal tags do not have any connection to the PLC. Internal tags transport values within the HMI device. Tag values are only available while Runtime is running. Principle Internal tags are stored in the memory of the HMI device. Therefore, only this HMI device has read and write access to the internal tags. You can create internal tags to perform local calculations, for example. You can use the HMI data types for internal tags. The following HMI data types are available: 3336 HMI data type Data format Array One-dimensional array Bool Binary tag DateTime Date/time format DInt Signed 32-bit value Int Signed 16-bit value LReal Floating-point number 64-bit IEEE 754 Real Floating-point number 32-bit IEEE 754 SInt Signed 8-bit value UDInt Unsigned 32-bit value UInt Unsigned 16-bit value USInt Unsigned 8-bit value WString Text tag, 16-bit character set WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.2 Working with Tags See also Basics of tags (Page 3330) 10.2.2 Working with tags 10.2.2.1 Creating tags Creating external tags Introduction You can access an address in the PLC via a PLC tag using an external tag. The following options are available for addressing: Symbolic addressing Absolute Addressing You can find further details on symbolic addressing in section "Addressing external tags (Page 3334)". If possible, use symbolic addressing when configuring a tag. You create tags either in the standard tag table or in a tag table you defined yourself. Requirement You have opened the project. A connection to the PLC is configured. The Inspector window is open. Procedure To create an external tag, proceed as follows: 1. Open the "HMI tags" folder in the project tree and double-click the standard tag table. The tag table open. Alternatively, create a new tag table and then open it. 2. In the "Name" column, double-click "Add" in the tag table. A new tag is created. 3. Select the "Properties > Properties >General" category in the Inspector window and, if required, enter a unique tag name in the "Name" field. The tag name must be unique throughout the device. 4. If required, select the "Display name" field to enter a name to be displayed in Runtime. The name to be displayed is language-specific and can be translated for the required Runtime languages. The display name is available for Basic Panels, Panels and Runtime Advanced. WinCC Basic V13.0 System Manual, 02/2014 3337 Visualize processes 10.2 Working with Tags 5. Select the connection to the required PLC in the "Connection" box. If the connection you require is not displayed, you must first create the connection to the PLC. You create the connection to a SIMATIC S7 PLC in the "Devices & Networks" editor. You create the connection to external PLCs in the "Connections" editor. If the project contains the PLC and supports integrated connections, you can also have the connection created automatically. To do this, when configuring the HMI tag, simply select an existing PLC tag to which you want to connect the HMI tag. The integrated connection is then automatically created by the system. 6. If you are working with an integrated connection, click the button in the "PLC tag" field and select an already created PLC tag in the object list. Click the button to confirm the selection. 7. If you are working with a non-integrated connection, enter the address from the PLC in the "Address" field. The "PLC tag" field remains empty. 8. Configure the other properties of the tag in the inspector window. You can also configure all tag properties directly in the tag table. To view hidden columns, activate the column titles using the shortcut menu. You can also create new tags alternatively directly at the application point, e.g. on an I/O field. To do this, click the button in the object list. You then configure the new tag in the Inspector window. Result An external tag has been created and linked to a PLC tag or an address in the PLC. Alternative procedure You can also create external HMI tags by dragging and dropping data block elements or global PLC tags in an HMI tag table. 3338 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.2 Working with Tags See also Creating internal tags (Page 3339) Creating multiple tags (Page 3340) Editing a Tag (Page 3341) Tag limits (Page 3347) Basics of tags (Page 3330) Addressing external tags (Page 3334) Creating internal tags Introduction You must at least set the name and data type for internal tags. Select the "Internal tag" item, rather than a connection to a PLC. For documentation purposes, it is a good idea to enter a comment for every tag. Requirement You have opened the project. Procedure 1. Open the "HMI tags" folder in the project tree and double-click the entry "Standard tag table". The tag table opens. Alternatively, create and then open a new tag table. 2. Double-click "Add" in the "Name" column of the tag table. A new tag is created. 3. If the Inspector window is not open, select the "Inspector window" option in the "View" menu. 4. Select the "Properties > Properties >General" category in the Inspector window and, if required, enter a unique tag name in the "Name" field. This tag name must be unique throughout the project. 5. If required, select the "Display name" field to enter a name to be displayed in Runtime. The name to be displayed is language-specific and can be translated for the required Runtime languages. The display name is available for Basic Panels, Panels and Runtime Advanced. 6. Select "Internal tag" as the connection in the "Connection" field. 7. Select the required data type in the "Data type" field. 8. In the "Length" field, you must specify the maximum number of characters to be stored in the tag according to the selected data type. The length is automatically defined by the data type for numerical tags. 9. As an option, you can enter a comment regarding the use of the tag. To do so, click "Properties > Properties > Comment" in the Inspector window and enter a text. You can also configure all tag properties directly in the tag table. To view hidden columns, activate the column titles using the shortcut menu. WinCC Basic V13.0 System Manual, 02/2014 3339 Visualize processes 10.2 Working with Tags You can also create new tags alternatively directly at the application point, e.g. on an I/O field. Click the button in the object list. You can then configure the new tag in the Properties window that opens. Result An internal tag is created. You can now use this in your project. In additional steps you can configure the tag, for example, by setting the start value and limits. See also Creating external tags (Page 3337) Creating multiple tags Introduction In a tag table, you create additional identical tags by automatically filling the rows of the table below a tag. The tag names are incremented automatically when filling in automatically. You can also use the auto fill function to fill table cells below a tag with a single tag property and thus modify the corresponding tags. If you apply the automatic filling in to already filled cells of a tab table, you will be asked whether you want to overwrite the cells or insert new tags. If you do not want to overwrite already configured tags, activate insert mode. Activate insert mode by keeping the <Ctrl> key pressed during insertion. Already existing entries in the tag table are moved down if insert mode is activated. Requirement You have opened the project. A tag table is open. The tag which is to serve as a template for other tags is configured. 3340 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.2 Working with Tags Procedure 1. If you want to create new tags, mark in the "Name" column the tag that should be used as a template for the new tags. If you want to copy a property of a tag to the tags below it, select the cell which contains this property. The selected cell will be highlighted in color and a small blue square will appear in its bottom right corner. If you move the mouse over this square, the cursor will change to a black cross. 2. Hold down the mouse button and drag this square over the cells below that you wish to fill automatically. The marking will be extended to cover this area. 3. Now release the mouse button. All of the marked cells will be filled automatically. New tags will be created in all empty cells in the marked area. Result Depending on which cells were selected, the function may automatically fill individual properties or create new tags. See also Creating external tags (Page 3337) 10.2.2.2 Editing tags Editing a Tag Introduction You can always rename, copy or delete tags. When a tag is renamed, the new name must be unique for the whole device. If you use the "Copy" command to copy a tag to the clipboard, the objects and references linked to the tag are copied as well. If you use the "Insert" command to add a tag to another device, the tag will be added without the connected references. Only the object name of the reference will be inserted. If a reference of the same name and valid properties exists in the target system, the existing reference will then be connected to the copied tag. If you copy a tag, the alarms linked to the tag are copied as well. If you add the copied tag to another device, the tag is added together with the linked alarms. WinCC Basic V13.0 System Manual, 02/2014 3341 Visualize processes 10.2 Working with Tags Requirement The tag which you wish to rename, copy or delete must exist. The tag table is open. Renaming tags 1. In the "Name" field, select the tag in the tag table. 2. Select "Rename" from the shortcut menu. 3. Type in a new name. The tag appears under its new name. Copying tags 1. Select one or more tags in the tag table or in the Detail window. 2. Select "Copy" from the shortcut menu. 3. Click on the point at which you want to insert the tag. For example, click another tag table in the same device or the tag table in a second device. 4. Select the "Insert" or "Extended insert" command from the shortcut menu. The tag is inserted as described above. Deleting a tag 1. Select one or more tags in the tag table. 2. Select the "Cross-reference" command from the "Tools" menu. In the "Cross-reference" editor, check to see where the tags are used. In this manner, you can see what impact the deletion of the tag will have on your project. 3. Select "Delete" in the pop-up menu of the tag. All marked tags will be deleted. Export and import of tags WinCC gives you the option to export and import tags. With Export and Import, you have the option to export tags from one project and import them into another project. There is also the option to create larger numbers of tags outside of WinCC, edit them and subsequently import into any WinCC project. See Importing and exporting tags (Page 4029) for additional information. See also Changing the tag configuration (Page 3343) Configuring multiple tags simultaneously (Page 3343) Using multiple tags simultaneously in a screen (Page 3344) Synchronizing tags (Page 3346) 3342 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.2 Working with Tags Creating external tags (Page 3337) Importing and exporting tags (Page 4029) Changing the tag configuration Introduction You can modify tags at any time to adapt them to changed requirements in the project. Changing the tag configuration if you want to change the configuration of a tag, open the tag table in which the tag is contained. Open the "Show all tags" tag table alternatively. In the tag tables, you can perform such tasks as comparing and adjusting the properties of multiple tags or sorting the tags by their properties. Change the properties either directly in the table or in the inspector window. If you change a tag property and this change causes a conflict with another property, it will be highlighted in color to draw your attention to this fact. This could happen, for example, if you connect the tag to another PLC which does not support this data type. See also Editing a Tag (Page 3341) Configuring multiple tags simultaneously Introduction In WinCC, you can assign the same properties to multiple tags in a single operation. This facilitates efficient programming. Requirement You created the tags you want to configure. The tag table is open. The Inspector window is open. Procedure 1. In the tag table, select all the tags that you want to configure at the same time. If the selected property is identical for all the tags, the setting for this property will appear in the Inspector window. The associated field will remain blank otherwise. 2. You can define the shared properties in the Inspector window or directly in the tag table. WinCC Basic V13.0 System Manual, 02/2014 3343 Visualize processes 10.2 Working with Tags if you change a property commonly on several tags, only this one property is changed. The other properties of the tag remain unchanged. Result All marked tags will be reconfigured. To edit tag properties which differ from one tag to the other, simply clear the multiple selection. See also Editing a Tag (Page 3341) Using multiple tags simultaneously in a screen Introduction In WinCC, you can create multiple I/O fields that are linked with tags in one screen in a single operation. This facilitates efficient programming. Requirement Several tags are set up. A screen is open. 3344 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.2 Working with Tags Procedure 1. In the project tree, select the required tag table under "HMI tags". 2. Select the detail view at the bottom of the project tree. The detail view shows the tags that exist in the selected tag group. 3. Mark the tags in the detail window. 4. Drag the tags to the screen. For each tag, this creates an I/O field that is connected to the tag. Note When you move a PLC tag from the detail window to the work area by drag&drop, a network and a connection are created additionally in the "Devices & Networks" editor. See also Editing a Tag (Page 3341) WinCC Basic V13.0 System Manual, 02/2014 3345 Visualize processes 10.2 Working with Tags Synchronizing tags Introduction To synchronize the PLC and HMI tags, WinCC offers the following options: Synchronizing tags with or without name matching between PLC and WinCC The following options are available for this: Link tags with addresses in the PLC This procedure is suitable, for example, if changes were made to the connection between the HMI device and the PLC and the tag connections were lost. The function can also be used if you have configured the control program and HMI project separately. Requirement External HMI tags have been created. PLC tags have been created. An HMI connection to a PLC in the project has been established. Procedure To synchronize HMI tags with PLC tags, follow these steps: 1. In the project tree, select the directory that contains the tags in question. 2. Select "Connect HMI tags to matching PLC tags" from the shortcut menu. A dialog opens. 3. Select the option you want to use. If you want to synchronize the tags without name matching, disable "Replace WinCC tag name with PLC tag name". If you want to connect HMI tags new with absolute access, select "Data type and absolute address match". 4. Confirm with "Synchronize". The system searches for a suitable PLC tag according to the selected option. 3346 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.2 Working with Tags Result The external HMI tags are synchronized with the PLC tags. If you have selected the option "Data type and absolute address match", the tag connection is established as soon as a suitable PLC tag is found. If you have selected a different option, the WinCC tags are updated accordingly and the PLC tag names are applied in WinCC. See also Editing a Tag (Page 3341) 10.2.2.3 Configuring tags Tag limits Introduction You can restrict the value range with limits for numerical tags. Principle You can specify a value range defined by a high and low limit for numerical tags. If the process value violates the value range, you trigger a function list. If the operator enters a value for the tag that is outside the configured value range, the input is rejected. The value is not accepted. Note You enter the text of the analog alarms for limit violations in the "Analog alarms" editor. Application example Use the limit to warn the operator in good time when the value of a tag enters a critical range, for example. See also Applying linear scaling to a tag (Page 3353) Defining the start value of a tag (Page 3350) Defining the acquisition cycle for a tag (Page 3357) Defining Limits for a Tag (Page 3348) Start value of a tag (Page 3349) WinCC Basic V13.0 System Manual, 02/2014 3347 Visualize processes 10.2 Working with Tags Updating the tag value in Runtime (Page 3350) Linear scaling of a tag (Page 3351) Connecting a tag to another PLC (Page 3353) Indirect addressing of tags (Page 3354) Addressing tags indirectly (Page 3355) Using tags to trigger functions (Page 3356) Address multiplexing (Page 3358) Configuring address multiplexing with absolute addressing (Page 3359) Configuring address multiplexing with symbolic addressing (Page 3361) Creating external tags (Page 3337) Defining Limits for a Tag Introduction For numerical tags, you can specify a value range by defining a low and high limit. Additionally, you configure the system to process a function list whenever a tag value drops below or exceeds its configured value range. Requirement You created the tag for which you want to set limits. The Inspector window with the properties for this tag is open. Procedure To define limits of a tag, follow these steps: 1. In the Inspector window select "Properties > Properties > Limits." If you want to define one of the limits as a constant value, select "Constant" using the button. Enter a number in the relevant field. If you want to define one of the limits as a tag value, select "HMI tag" using the button. Use the object list to define the tag for the limit. 2. To set an additional limit value for the tag, repeat step 1 with the appropriate settings. Alternative procedure You can also configure the high and low limit directly in the tag table. To view hidden columns, activate the column titles using the shortcut menu. 3348 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.2 Working with Tags Configuring a function list You can configure a function list for exceeding the value range as follows: 1. If you want to start a function list when the value drops below the value range, click "Properties > Events > Minimum violated" in the Inspector window. Create a function list in this dialog. 2. If you want to start a function list when the value exceeds the value range, click "Properties > Events > Maximum violated" in the Inspector window. Create a function list in this dialog. Result You have set a value range defined by a high and low limit for the selected tag. If the value range is exceeded or undershot, a function list is carried out. See also Tag limits (Page 3347) Start value of a tag Value of a tag at start of Runtime You can configure a start value for numeric tags and tags for date/time values. The tag will be preset to this value when Runtime starts. In this way, you can ensure that the tag has a defined status when Runtime starts. For external tags, the start value will be displayed on the HMI device until it is overwritten by the PLC or by input. If no start value was configured, the tag contains the value "0" when starting Runtime. In WinCC Runtime Professional you can enter a tag value in place of the start value on a tag with the "String" data type. The tag value is saved in the "Project texts" editor and is multilingual. After the text has been translated, it is displayed in Runtime as a language-dependent start value. Application example You can assign a default value to an I/O field. Enter the desired default value as start value for the tag that is linked to the I/O field. See also Defining the start value of a tag (Page 3350) Tag limits (Page 3347) WinCC Basic V13.0 System Manual, 02/2014 3349 Visualize processes 10.2 Working with Tags Defining the start value of a tag Introduction In WinCC you can configure a start value for a numeric tag and a tag for date/time values which this adopts at Runtime start. Requirement You have created the tag for which you want to define a start value. The Inspector window with the tag properties is open. Procedure To configure a start value, proceed as follows: 1. In the Inspector window select "Properties > Properties > Values." 2. Enter the desired "Start value." Alternative procedure You can also configure the start value directly in the tag table. To view hidden columns, activate the column titles using the shortcut menu. Result The start value you selected for the tag is transferred to the project. See also Tag limits (Page 3347) Start value of a tag (Page 3349) Updating the tag value in Runtime Introduction Tags contain process values which change while Runtime is running. Value changes are handled differently at internal and external tags. Principle When Runtime starts, the value of a tag is equal to its start value. Tag values change in Runtime. In Runtime, you have the following options for changing the value of a tag: 3350 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.2 Working with Tags A value change in an external tag in the PLC. By input, for example, in an I/O field. By running a system function, such as "SetValue." Updating the Value of External Tags The value of an external tag is updated as follows: Cyclic in operation If you select the "Cyclic in operation" acquisition mode, the tag is updated in runtime as long as it is displayed in a screen. The acquisition cycle determines the update cycle for tag value updates on the HMI device. Cyclic acquisition is based on the selected scan cycle time. Cyclic continuous If you select the "Cyclic continuous" acquisition mode, the tag will be updated continuously in Runtime, even if it is not in the currently-open screen. This setting is activated for tags that are configured to trigger a function list when their value changes, for example. Only use the "Cyclic continuous" setting for tags that must truly be updated. Frequent read operations increase communication load. On demand If you select the "On demand" acquisition mode, the tag is not updated cyclically. It will only be updated on request, for example, by using the "Update Tag" system function. See also Tag limits (Page 3347) Linear scaling of a tag Introduction Numeric data types can be processed with linear scaling. The process values in the PLC for an external tag can be mapped onto a specific value range in the project. WinCC Basic V13.0 System Manual, 02/2014 3351 Visualize processes 10.2 Working with Tags Principle To apply linear scaling to a tag, you must specify one value range on the HMI device and one on the PLC. The value ranges will be mapped to each other linearly. 3/& ,QFKHV FP +0,GHYLFH As soon as data from the HMI device is written to an external tag, it will be automatically mapped to the value range of the PLC. As soon as data from the HMI device is read from the external tag, a corresponding transformation will be performed in the other direction. Note You can also use the system functions "LinearScaling" and "InvertLinearScaling" to automatically convert process values. Application example The user enters length dimensions in centimeters but the PLC is expecting inches. The entered values are automatically converted before they are forwarded to the controller. Using linear scaling, the value range [0 to 100] on the PLC can be mapped onto the value range [0 to 254] on the HMI device. See also Tag limits (Page 3347) 3352 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.2 Working with Tags Applying linear scaling to a tag Introduction To apply linear scaling to a tag, you must specify one value range on the HMI device and one on the PLC. The value ranges will be mapped to each other linearly. Requirement The external tag to which linear scaling is to be applied must exist. The Inspector window with the properties for this tag is open. Procedure To apply linear scaling to a tag, follow these steps: 1. In the Inspector window select "Properties > Properties > Linear scaling." 2. Click on "Enable" to switch on linear scaling. Using this option, you can temporarily switch off linear scaling for testing purposes, for example. Settings which were made earlier for linear scaling remain unchanged. 3. In the "PLC" area, enter the start and end values of the value range to be applied to the process values on the PLC. 4. In the "HMI device" area, enter the end and start values of the value range to be applied to the process values on the HMI device. Result In Runtime the data will be automatically mapped from one value range to the other. Note You can also use the "LinearScaling" and "InvertLinearScaling" system functions to automatically convert process values. See also Tag limits (Page 3347) Connecting a tag to another PLC Introduction In WinCC, you can change the PLC connection of a tag at any time. This is needed when you change the configuration of your plant, for example. WinCC Basic V13.0 System Manual, 02/2014 3353 Visualize processes 10.2 Working with Tags Depending on the PLC selected, you may need to modify the configuration of the tag. The tag properties which must be changed will be highlighted in color. Requirement The external tag, whose connection you wish to change, must already exist. The connection to the PLC must already exist. The Properties window for this tag is open. Procedure To change the PLC connection of a tag, proceed as follows: 1. In the Inspector window select "Properties > Properties > General." 2. Select the new connection in the "Connection" field. The tag properties that you must change will be highlighted in color in the tag table and in the Inspector window. 3. Change all highlighted properties of the tag to suit the requirements of the new PLC. Result The external tag is connected to the new PLC. See also Tag limits (Page 3347) Indirect addressing of tags Principle In multiplexes, a type of indirect addressing, the tag used is first determined at runtime. A list of tags is defined for the multiplex tag. The relevant tag is selected from the list of tags in runtime. The selection of the tag depends on the value of the index tag. In Runtime, the system first reads the value of the index tag. Then the tag which is specified in the corresponding place in the tag list is accessed. Application example Using indirect addressing, you could configure the following scenario: The operator selects one of several machines from a selection list. Depending on the operator's selection, data from the selected machine will be displayed in an output field. To configure such a scenario, configure the index tag for a symbolic I/O field. Configure the multiplex tag at an I/O field. Configure the tag list of the multiplex tag to reflect the structure of the selection list. 3354 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.2 Working with Tags If the operator selects another machine, the value of the index tag will change. The selection field then displays the content of the tag that is pointed to in the tag list in the multiplex tag by the new index value. See also Tag limits (Page 3347) Addressing tags indirectly Introduction With indirect addressing, the tag used is first determined at runtime. Instead of a single tag, a list of tags is defined. The list entries consist of an index value and the name of the tag to be used. Using an index tag, you can control which entry in the tag list will be accessed. Requirement The tag which you wish to address indirectly must already exist. The index tag must exist. The tags which will be contained in the tag list must already exist. The Inspector window with the tag properties is open. Procedure To address tags indirectly, proceed as follows: 1. In the Inspector window select "Properties > Properties > Multiplexing". 2. Select the "Multiplexing" option to activate indirect addressing. Using this option, you can temporarily switch off indirect addressing for testing purposes, for example. Settings which were made earlier for indirect addressing remain unchanged. 3. Select an "Index tag" or define a new tag using the object list. 4. Click the first entry in the "Tags" column in the tag list. 5. Select a tag as a list entry or define a new tag using the object list. The entry in the "Index" column will be generated automatically. 6. Repeat step 5 for all tags that you wish to add to the tag list. 7. If necessary, you can use drag-and-drop to change the order of the entries in the list. Result In runtime, the system will dynamically access the tag in the tag list which has the same index value as the value currently in the index tag. WinCC Basic V13.0 System Manual, 02/2014 3355 Visualize processes 10.2 Working with Tags See also Tag limits (Page 3347) Using tags to trigger functions Introduction You can use the values of variables as the triggering event for an action in runtime. To start an action in Runtime, configure a function list for a tag. Include one or more system functions in the function list. The function list is processed when the configured event occurs. The following events are available for a tag: Change in value of the tag Function list processing is triggered by each change in the value of the variable. If the tag contains arrays, the function list is processed whenever an element of the array changes. Violation of the tag's high limit The function list is processed when the high limit is violated. Violation of the tag's low limit The function list is processed when the low limit is violated. Requirement The tag whose value you wish to use as an event already exists. The Inspector window with the properties for this tag is open. Procedure To configure a tag with a function list, proceed as follows: 1. Under "Properties > Events >" in the Inspector window, select the event for which you want to create a function list. The function list associated with the selected event is shown. 2. Click "<Add function>". The second table column contains a selection button. 3. Click the selection button and select a system function. 4. Define the parameter values. Result The function list is processed when the configured event occurs in Runtime. See also Tag limits (Page 3347) 3356 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.2 Working with Tags Defining the acquisition cycle for a tag Introduction The value of an external tag can be changed in Runtime by the PLC to which the tag is linked. To ensure that the HMI device is informed of any changes in tag values by the PLC, the values must be updated on the HMI. The value is updated at regular intervals while the tag is displayed in the process screen or is logged. The interval for regular updates is set with the acquisition cycle. The update can also be made continuous. Requirement You have created the tag for which you want to define an acquisition cycle. The Inspector window with the tag properties is open. Procedure To configure an acquisition cycle for a tag, follow these steps: 1. In the Inspector window select "Properties > Properties > General." 2. If you want to update the tag at regular intervals as long as it is being displayed on the screen or logged, select "Cyclic in operation" as the acquisition mode. Or: If you want to update the tag at regular intervals even though it is not being displayed on the screen or logged, select "Cyclic continuous" as the acquisition mode. The "Cyclic continuous" setting is selected for a tag, for example, that has a function list configured for a change of its value and that is not directly visible in a screen. 3. Select the required cycle time in the "Acquisition cycle" field or define a new acquisition cycle using the object list. Alternatively, you can configure the acquisition cycle directly in the work area of the tag table. To view hidden columns, activate the column titles using the shortcut menu. Note Only use the "Cyclic continuous" acquisition mode for tags that really have to be continuously updated. Frequent read operations generate a heavy communication load. Result The configured tag is updated in Runtime with the selected acquisition cycle. See also Tag limits (Page 3347) WinCC Basic V13.0 System Manual, 02/2014 3357 Visualize processes 10.2 Working with Tags Address multiplexing Introduction Using address multiplexing, you can use a single tag to access a multitude of memory locations within the PLC's address range. You read and write to the addresses without defining a tag for each individual address. Multiplexing with absolute addressing When using multiplexing with absolute addressing, you configure tags as placeholders for the address in the PLC to be addressed. If you want to access, for example, an address of the format "%DBx.DBWy", the expression for multiplexing is as follows: "%DB[HMITag1].DBW[HMITag2]" In Runtime, you supply the tag "HMITag1" with the required value for the data block you want to address. In Runtime, you supply the tag "HMITag2" with the required address from the data block. Tags are supplied with values, for example, with the help of values from the PLC or via a script. Multiplexing with absolute addresses is supported for the following PLCs and communication drivers. SIMATIC S7-300/400 SIMATIC S7-1200 SIMATIC S7-1500 Multiplexing with absolute addresses is not available for data blocks with optimized access. Multiplexing with symbolic addressing When multiplexing with symbolic addressing, you access an array element of an array tag in a data block of the connected PLC by means of a multiplex tag and an index tag. The multiplex tag contains the symbolic address of the data block which you want to access. The symbolic address also contains the index tag via which you access the index of the array tag. If you want to access, for example, the array tag "Arraytag_1" in the data block "Datablock_1", the expression for symbolic addressing is as follows: "Datablock_1.Arraytag_1["HMITag_1"] You control the access to the index of the array elements with the HMI-Variable "HMITag_1". In Runtime, you supply the tag with the index of the array element that you want to access. Multiplexing with symbolic addressing is only available if the following components support symbolic addressing: the HMI device PLC Communication driver 3358 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.2 Working with Tags Symbolic addressing is supported by communication drivers: SIMATIC S7-1200 SIMATIC S7-1500 See also Tag limits (Page 3347) Configuring address multiplexing with absolute addressing Introduction When using address multiplexing, you can efficiently access different addresses in the PLC with the help of a small number of tags. Instead of the absolute address in the PLC, you use tags in order to be able to change the address in Runtime. Requirement The tag for address multiplexing is created and connected to the PLC. The Properties window for this tag is open. Procedure 1. Select the tag for address multiplexing in the tag table, and select "Properties > Properties > General" in the Inspector window. The general properties of the tag are displayed. 2. Select the "Int" data type for this example. 3. Select the access type "Absolute addressing". WinCC Basic V13.0 System Manual, 02/2014 3359 Visualize processes 10.2 Working with Tags 4. Click the selection button in the "Address" field. The address dialog opens. 5. Click the selection button in the "DB number" field and select the entry "HMI tag". 6. In the "DB number" field, click the button and select a tag for the DB number in the object list. Or create a new tag with the help of the object list. Accept the tag by clicking the button. 7. Repeat steps 3 and 4 for the "Address" field and configure a further tag for calling the address area in the data block. 3360 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.2 Working with Tags The selection options in the Address dialog depend on the selected data type of the multiplex tag. The Address dialog offers only address settings that can be configured with the selected data type. Result In runtime, the multiplex tag is used to access the memory location corresponding to the address currently found in the tag. You control access to the data block with the tag in the DB number field. You control access to the address in the selected data block with the tag in the "Address" field. Note The value in the memory location will only be read at the next update cycle for the addressed tag. If, for example, you use a multiplex tag in a script, do not attempt to access contents of the memory location directly after changing it. See also Tag limits (Page 3347) Configuring address multiplexing with symbolic addressing Introduction When using address multiplexing, you can efficiently access different addresses in the PLC with the help of a small number of tags. Instead of the symbolic address in the PLC, you use tags in order to be able to change the address in Runtime. Requirement The tag for address multiplexing is created. The Properties window for this tag is open. A data block with an array tag is created in the connected PLC. The data block was compiled. WinCC Basic V13.0 System Manual, 02/2014 3361 Visualize processes 10.2 Working with Tags Procedure 1. Select the tag for address multiplexing in the tag table, and select "Properties > Properties > General" in the Inspector window. The general properties of the tag are displayed. 2. Select the connection to the PLC via the "Connection" field. 3. Select the access type "Symbolic addressing". 3362 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.2 Working with Tags 4. Navigate to the data block of the PLC via the "PLC tag" field and select an array element of the array tag. 5. Click the selection button in the "Address" field. The address dialog opens. 6. Click the selection button in the "Index tag" field and select the entry "HMI tag". 7. In the "Index tag" field, click the button and select a tag for the array index in the object list. Or create a new tag with the help of the object list. Accept the tag by clicking the button. Result In Runtime, the array element whose index value is contained in the index tag is accessed. WinCC Basic V13.0 System Manual, 02/2014 3363 Visualize processes 10.2 Working with Tags See also Tag limits (Page 3347) 10.2.3 Working with arrays 10.2.3.1 Basics on arrays Definition Array data of a uniform data type is successively arranged and is addressed within the address space to allow access to these data by means of an index. The individual array elements are addressed by means of an integer index. The properties of each array element are the same and are configured at the array tag in a data block of the PLC program. Advantages You can configure multiple array elements with the same properties at one time using a single array tag. You can then use each array element as any other tag in your configuration. Restrictions The following restrictions apply to the use of arrays: Not all HMI devices support array tags. An array may contain only one dimension. The lower index of an array must begin with "0". Application examples Array tags can be used in the following situations: To group process values in profile trends: You map process values to trends which are acquired at different points in time, for example. To access specific values which are grouped in trends: You output all values of the profile trend by stepping up the index tag, for example. 3364 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.2 Working with Tags To configure discrete alarms with successive bit number. To save the complete machine data records in a recipe. License rule for runtime An array tag is counted in WinCC Runtime as one PowerTag, regardless of the number of array elements. Special features WARNING Increased system load and performance losses Read or write access to a single array element always includes read or write access to all array elements of the array tag. Transfer of the data of large arrays from and to the PLC usually takes longer compared to the transfer of a basic data type. This may cause communication overload and disruption as a result. Example: An array tag which consists of 100 array elements of data type "Real" was configured. If an array element with a length of four bytes changes, 100 x 4 bytes are written to the PLC. CAUTION Data inconsistency at array tags If the value of a single element must be changed in an array tag, the whole array is read, changed and rewritten as a complete array. Changes carried out in the meantime to other array elements in the PLC are overwritten during rewriting. You should always prevent the HMI device and the PLC from concurrently writing values to the same array tag. Use synchronous transfer of recipe data records to synchronize an array tag with the PLC. See also Creating array tags (Page 3366) Examples of arrays (Page 3367) Basics of tags (Page 3330) WinCC Basic V13.0 System Manual, 02/2014 3365 Visualize processes 10.2 Working with Tags 10.2.3.2 Creating array tags Introduction Create an array tag to configure a large number of tags of the same data type. The array elements are saved to a consecutive address space. You can create an array tag as an internal tag or as an external tag. If you want to create an array tag as an external tag, first configure an array tag in a data block of the connected PLC. You then connect the array tag to an HMI tag. Requirement The HMI tag table is open. Procedure To create an array tag, follow these steps: 1. Double click <Add> in the "Name" column of the HMI tag table. A new HMI tag is created. 2. Click in the Data type column and select the "Array" data type. 3. Click in the data type column. The dialog box for configuring the array is opened. 4. Select the desired data type for the array tag in the "Date type" field. 5. Define the number of array elements in the "Array limits" field. The lower limit must begin with "0". 6. Click . The settings for the array are saved. 7. Save the project. 3366 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.2 Working with Tags Result An array tag is created. The properties of the array elements are inherited from the parent array tag. See also Basics on arrays (Page 3364) 10.2.3.3 Examples of arrays Introduction Array tags combine a number of tags, e.g. 100 array elements. You use array tags as complete arrays in the following places: In the "Alarms" editor In the "Recipes" editor For address multiplexing In the trend view You use individual array elements everywhere in the configuration like HMI tags. Examples You can configure an array tag with the corresponding number of array elements to handle multiple tags of the same data type. The individual array elements can be accessed indirectly by means of a multiplex index tag, for example. Use these index tags to operate and monitor the array elements. See also Basics on arrays (Page 3364) 10.2.4 Working with cycles 10.2.4.1 Cycle basics Introduction Cycles are used to control actions that regularly occur in runtime. Common applications are the acquisition cycle and the update cycle. WinCC Basic V13.0 System Manual, 02/2014 3367 Visualize processes 10.2 Working with Tags Principle In Runtime, actions that are performed regularly are controlled by cycles. Typical applications for cycles: Acquisition of external tags The acquisition cycle determines when the HMI device will read the process value of an external tag from the PLC. Set the acquisition cycle to suit the rate of change of the process values. The temperature of an oven, for example, changes much more slowly than the speed of an electrical drive. Do not set the acquisition cycle too low, since this will unnecessarily increase the communication load of the process. The smallest possible value for the cycle depends on the HMI device that will be used in your project. For most HMIs, this value is 100 ms. The values of all other cycles are always an integer multiple of the smallest value. Application example You can use cycles for the following tasks: To regularly update a tag. To draw attention to maintenance intervals. See also Basics of tags (Page 3330) 10.2.5 Displaying tags 10.2.5.1 Outputting tag values in screens Introduction In runtime you can output tag values in the screens of the operator device in the form of a trend. A trend is a graphic representation of the values that a tag takes during runtime. Use the "Trend display" graphic object to represent it. Process values for the trend display are loaded by the PLC from the ongoing process. The values to be displayed are determined individually within a fixed, configurable cycle. Cyclically-triggered trends are suitable for representing continuous curves, such as the changes in the operating temperature of a motor. Displayed values You will need to configure a trend view in a screen so that tag values are displayed on the HMI device. When configuring the trend view, specify which tag values are to be displayed. You can control the updating of the trend display by defining the cycle time. 3368 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.2 Working with Tags 10.2.5.2 Configuring trend displays for values from the PLC Introduction You use a trend view to graphically represent values that a tag assumes during the process. Requirement A screen is open. The Inspector window with the trend view properties is open. Procedure To configure a trend view, follow these steps: 1. Add the "Trend view" object from the toolbox in the "Control" group to the screen. 2. Select the "Trend" category from the "Properties" group in the Inspector window and doubleclick "<Add>" in the "Name" column. 3. Assign a name to the trend in the "Name" column. 4. In the "Style" column, use the selection button to open the "Style" dialog and select the style of the line. 5. Select the number of trend values in the "Trend values" column. WinCC Basic V13.0 System Manual, 02/2014 3369 Visualize processes 10.3 Working with alarms 6. In the "Settings" column, use the selection button to open the "Data source" dialog and select the tags to supply the trend with values. Specify the cycle for reading the tags from the PLC. 7. You can make other settings in the dialogs of the Inspector window. For example, you can select the "Display table" option in the "Table" category to display a value table beneath the trend view. Note If you hold down the <CTRL> key and double-click the trend view, the trend view is activated. You set the column width and the position of the columns in the table header of the values table in active mode. In order to activate the trend view the zoom factor has to be set to 100 %. Result In runtime, the values of the selected tags are displayed in the configured trend view. 10.3 Working with alarms 10.3.1 Basics 10.3.1.1 Alarm system in WinCC Introduction The alarm system allows you to display and record operating states and faults on the HMI device that are present or occur in a plant. An alarm may have the following content: N Time o. 5 3370 Date 12:50:24 24.02. :590 2007 Alarm text Status Alarm class Boiler pressure above high limit. Incoming Outgoing Warning: Color Red WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.3 Working with alarms Alarm system in WinCC The alarm system processes a variety of alarm types. The alarm procedures can be broken down into system-defined alarms and user-defined alarms: User-defined alarms are used to monitor the plant process. System-defined alarms monitor the HMI device. The detected alarm events are displayed on the HMI device. Targeted access to the alarms combined with supplementary information about individual alarms ensures that faults are localized and cleared quickly. This reduces stoppages or even prevents them altogether. The following figure shows the alarm system structure: 6\VWHPGHILQHGDODUPV +0,GHYLFH 1RQH &RQILJXUDWLRQ LQ:LQ&& 10.3.1.2 6\VWHPDODUPV 8VHUGHILQHGDODUPV +0,GHYLFH $QDORJDODUP 'LVFUHWHDODUP Alarm types Overview of the alarm types Introduction The alarm types serve various purposes for monitoring the plant. The alarms from the individual alarm types are configured and triggered in different ways. WinCC Basic V13.0 System Manual, 02/2014 3371 Visualize processes 10.3 Working with alarms Select the relevant tab in the "HMI alarms" editor to configure alarms based on the individual alarm types. Alarm types in WinCC WinCC supports the following alarm types: User-defined alarms Analog alarms - Analog alarms are used to monitor limit violations. Discrete alarms - Discrete alarms are used to monitor states. System-defined alarms System events - System events belong to the HMI device and are imported into the project. - System events monitor the HMI device. System-defined alarms System alarms Examples for alarms "An online connection to the PLC is established." Description A system alarm indicates the status of the system, plus communication errors between the HMI device and system. Under "Runtime settings > Alarms" you specify how long a system alarm is shown on the HMI device. Support The reference contains a list of the possible system events, along with the cause and possible remedies. If you contact online support because of a system alarm on the HMI device, you will need the alarm number and tags used in the system alarm. 3372 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.3 Working with alarms User-defined alarms Analog alarms Description Analog alarms signal limit violations during the process. Example The speed of the mixer in a fruit juice mixing plant must not be too high or too low. You can configure analog alarms to monitor the speed of the mixer. If the high or low limit for the speed of the mixer is violated, an alarm is output on the HMI device containing the following alarm text, for example: "Mixer speed is too low". Discrete alarms Description Discrete alarms indicate a status in the current process. Example A fruit juice mixing plant consists of several tanks containing the ingredients. To ensure the correct mixing ratio of water, fruit concentrate, sugar, and flavoring, the valves in the intakes open and close at the right moment. This operation should be monitored. You configure a suitable discrete alarm for all the valve states. If a valve on one of the four tanks opens or closes, an alarm is displayed, such as "Water valve closed". The operator can thus monitor whether the plant is producing correctly. 10.3.1.3 Alarm states Introduction An alarm assumes various alarm states in Runtime. The user analyzes and reports on the process execution with reference to the alarm states. WinCC Basic V13.0 System Manual, 02/2014 3373 Visualize processes 10.3 Working with alarms Description Every alarm has an alarm status. The alarm states are made up of the following events: Incoming The condition for triggering an alarm is satisfied. The alarm is displayed, such as "Boiler pressure too high." Outgoing The condition for triggering an alarm is no longer satisfied. The alarm is no longer displayed as the boiler was vented. Acknowledge The operator acknowledges the alarm. Alarms without acknowledgment The following table shows the alarm states for alarms that do not have to be acknowledged: Status Description Incoming The condition for an alarm is satisfied. Outgoing The condition for an alarm is no longer satisfied. Alarms with acknowledgment The following table shows the alarm states for alarms that have to be acknowledged: Status Description Incoming The condition for an alarm is satisfied Outgoing, not acknowledged The condition for an alarm is no longer satisfied. The operator has not acknowledged the alarm. Outgoing, subsequently acknowledged The condition for an alarm is no longer satisfied. The operator has acknowledged the alarm after this time. Incoming, acknowledged The condition for an alarm is satisfied. The operator has acknowledged the alarm. Outgoing, acknowledged first The condition for an alarm is no longer satisfied. The operator acknowledged the alarm while the condition was still satisfied. If necessary, the HMI device shows you each time one of these states occurs. Note The display text for alarm states depends on the language and configuration. 3374 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.3 Working with alarms 10.3.1.4 Alarm classes Basics on alarm classes Introduction Many alarms occur in a plant. These are all of different importance. You can assign the alarms of your project to alarm classes to clearly show the user which of the alarms are most important. Description The alarm class defines how an alarm is displayed. The alarm class specifies if and how the user has to acknowledge alarms of this alarm class. A new alarm class with mandatory acknowledgment is generated in WinCC. Note The choice of display modes for alarm classes depends on the options on your HMI device. Examples of how to use alarm classes The alarm "Speed of fan 1 in upper tolerance range" has alarm class "Warnings". The alarm is displayed with a white background. The alarm does not have to be acknowledged. The alarm "Speed of fan 2 has exceeded upper warning range" is assigned to the "Errors" alarm class. The alarm is displayed with a red background and flashes at high frequency in runtime. The alarm is displayed until the user acknowledges it. Using alarm classes Use the following alarm classes to define the acknowledgment model and display of alarms for your project: Predefined alarm classes You cannot delete predefined alarm classes and edit them only to a limited extent. Predefined alarm classes have been created for each HMI device under "HMI alarms > Alarm classes". Custom alarm classes You can create new alarm classes under "HMI alarms > Alarm classes", configure how you want the alarms to be displayed, and define an acknowledgment model for alarms of this alarm class. The possible number of custom alarm classes depends on which runtime is used in your project. See also Creating alarm classes (Page 3381) WinCC Basic V13.0 System Manual, 02/2014 3375 Visualize processes 10.3 Working with alarms Predefined alarm classes Predefined alarm classes The following alarm classes already created in WinCC for every HMI device: Alarm classes for user-defined alarms "Warnings" The "Warnings" alarm class is intended to show regular states and routines in the process. Users do not acknowledge alarms from this alarm class. "Errors" The "Errors" alarm class is intended to show critical or dangerous states or limit violations in the process. The user must acknowledge alarms from this alarm class. Alarm class for system-defined alarms "System" The "System" alarm class contains alarms that display states of the HMI device and the PLCs. See also Creating alarm classes (Page 3381) 10.3.1.5 Acknowledgment Acknowledging alarms Introduction To make sure that an alarm was registered by the plant operator, configure this alarm so that it is displayed until acknowledged by the operator. Alarms that display critical or hazardous states in the process have to be acknowledged. Description Acknowledging an alarm changes the alarm status from "Incoming" to "Acknowledged". When the operator acknowledges an alarm, the operator confirms that he or she has processed the status that triggered the alarm. 3376 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.3 Working with alarms Triggering acknowledgment of an alarm In Runtime, you trigger alarm acknowledgments in various ways: Acknowledgement by the authorized user at the HMI device Automatic acknowledgment by the system without operator action, e.g. by means of - Tags - PLC - System functions in function lists Acknowledging alarms that belong together To make the alarm system clearer and easier to use in Runtime, you can configure an alarm group. You can acknowledge all alarms belonging to this alarm group in a single pass. Acknowledgment by the PLC Discrete alarms will be automatically acknowledged by the PLC, if necessary. The acknowledgment is triggered by a bit in the "Acknowledgment tag PLC". You define the bit and tag at the configuration stage. Acknowledgment of an alarm on the HMI device In Runtime, the user acknowledges an alarm in one of the following ways, depending on the configuration: Using the acknowledgment button <ACK> on the HMI device Using the button in the alarm view Using configured function keys or buttons in screens Note Acknowledgment button <ACK> on the HMI device To ensure that critical alarms are processed only by authorized users, protect the "ACK" button on the HMI devices, including the operating controls and display objects of the alarms. Use the appropriate operator authorization for this. Note HMI device dependency The acknowledgement key <ACK> is not available on all HMI devices. WinCC Basic V13.0 System Manual, 02/2014 3377 Visualize processes 10.3 Working with alarms Acknowledgment model Overview You define the acknowledgment model for an alarm class. Alarms that are assigned to this alarm class will be acknowledged on the basis of this acknowledgment model. The following acknowledgment model is used in WinCC: Alarm without acknowledgment This alarm comes and goes without having to be acknowledged. There is no visible response from the system. Alarm with simple acknowledgment This alarm must be acknowledged as soon as the event that triggers the alarm occurs. The alarm remains pending until it is acknowledged. 10.3.1.6 Alarm groups Introduction Many alarms from different areas and processes occur in a plant. You can compile associated alarms into alarm groups. Alarm groups You can use the alarm groups to monitor the parts of the plant and to acknowledge the associated alarms together as required. Alarm groups can contain alarms from different alarm classes. You only assign alarms that require acknowledgment to alarm groups. Using alarm groups It is a good idea to compile alarm groups for alarms such as the following: Alarms that are caused by the same fault. Alarms of the same type Alarms from a machine unit, such as "Fault in drive XY" Alarms from an associated part of the process, such as "Fault in cooling water supply" Display in Runtime In Runtime, the "Alarm group" column displays the number of the alarm group to which the alarm belongs. 3378 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.3 Working with alarms 10.3.1.7 Alarm number Assigning alarm numbers The system assigns unique alarm numbers within an alarm type. Note When adapting alarm numbers, observe the uniqueness of the alarm number within an alarm type. 10.3.2 Working with alarms 10.3.2.1 Alarm components and properties Overview You configure the components of alarms in WinCC. The following table shows the basic components of alarms: Alarm Alarm class number Time Date of day Warni 1 ng 11:09 :14 06.08.2 IO 007 Maximum speed reached 2 Syste m 11:25 :58 06.08.2 I 007 Switch to "Online" mode 0 110001 Alarm status Alarm text Alarm Tooltip Trigger tag Limit value This alarm is ... speed_1 27 This alarm is ... PLCVariable_1 - group 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) 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. WinCC Basic V13.0 System Manual, 02/2014 3379 Visualize processes 10.3 Working with alarms 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. 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. 3380 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.3 Working with alarms 10.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. 3. 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. 4. 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. 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. WinCC Basic V13.0 System Manual, 02/2014 3381 Visualize processes 10.3 Working with alarms 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 emails. 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. 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. 3382 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.3 Working with alarms Requirement You have created a project. The "HMI alarms" editor is open. The Inspector window is open. Creating a new alarm group 1. Click the "Alarm Groups" tab. The existing alarm groups are displayed. 2. In the work area of the table, double-click "<Add>" in the first free row. A new alarm group is created. 3. You can overwrite the proposed "Name". Result An alarm group is created. For the group acknowledgment of alarms in Runtime, assign the associated alarms that require acknowledgment to an alarm group. Configuring discrete alarms Introduction Discrete alarms triggered by the PLC indicate status changes in a plant. They indicate the opened or closed state of a valve, for example. The following sections describes the configuration procedures in the "HMI alarms" editor. You can also configure discrete alarms in the "HMI tags" editor. Requirements The "HMI alarms" editor is open. The Inspector window is open. You have created the required alarm classes and alarm groups. Procedure To configure a discrete alarm, proceed as follows: 1. Open the "Discrete alarms" tab. 2. To create a new discrete alarm, double-click in the work area on "<Add>". A new discrete alarm is created. WinCC Basic V13.0 System Manual, 02/2014 3383 Visualize processes 10.3 Working with alarms 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. - When you select a PLC tag, use the data types "Int" or "Word". The input and output area of a PLC tag is unsuitable as trigger. - 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. Note 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. Additional settings for discrete alarms 3384 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.3 Working with alarms Creating a tooltip To configure a tooltip for the alarm, follow these steps: Enter your text under "Properties > Properties > Tooltip". Configuring event-driven tasks To configure event-driven tasks, such as a loop-in alarm, follow these steps: 1. Select the discrete alarm. 2. Select "Properties > Events" in the Inspector window and configure a new function list for the relevant event. See also Configuring loop-in alarm (Page 3389) Configuring analog alarms Introduction Analog alarms indicate limit violations. For example, if the speed of a motor drops below a certain value, an analog alarm is triggered. Requirements The "HMI alarms" editor is open. The Inspector window is open. You have created the required alarm classes and alarm groups. Procedure To configure an analog alarm, proceed as follows: 1. Click the "Analog alarms" tab. 2. To create a new analog alarm, double-click in the table on "<Add>". A new analog alarm is created. WinCC Basic V13.0 System Manual, 02/2014 3385 Visualize processes 10.3 Working with alarms 3. To configure the alarm, select "Properties > Properties >General" in the Inspector window: - Enter an alarm text as event text. Format the text character-for-character using the shortcut menu. Using the shortcut menu, you can insert output fields for HMI tags, or text from text lists. - You can renumber the alarm. - Select the alarm class and the alarm group, if necessary. 4. Configure the tag that triggers the alarm under "Properties > Properties > Trigger > Settings". Do not use trigger tags for anything else. Configure limit values for an analog alarm 1. In the Inspector window, click the button under "Properties > Properties > Trigger > Limit > Value". - To use a constant as limit value, select "Constant". Enter the required limit value. - To use a tag as limit value, select "HMI tag". The button is shown. Use this button to select the tag you want to use. Note If the tag included in the selection does not yet exist, 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. 3386 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.3 Working with alarms 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. Creating a tooltip To configure a tooltip for the alarm, follow these steps: Select "Properties > Properties > Tooltip" in the Inspector window and enter your text. Configuring event-driven tasks To configure event-driven tasks, such as a loop-in alarm, follow these steps: 1. Select the analog alarm. 2. Select "Properties > Events" in the Inspector window and configure a new function list for the relevant event. See also Configuring loop-in alarm (Page 3389) WinCC Basic V13.0 System Manual, 02/2014 3387 Visualize processes 10.3 Working with alarms Adding an output field to alarm text Introduction In WinCC, you can insert output fields into the alarm text which display the content of tags. Requirements The "HMI alarms" editor is open. The alarm is selected. Output of a tag value in the alarm text To insert an output field for a tag value in the alarm text, proceed as follows: 1. Place the cursor onto the required position in the event text. 2. Select "Insert tag output field" in the shortcut menu. 3. Open the object list under "Tag" and select a tag. You can also create the tag in the object list. 4. Under "Format", specify the length of the output field and the format for tag value output in the alarm text. Configure an output field of sufficient size. Otherwise, the tag content is not output to the full extent in the alarm. 5. Click to save your entries. WinCC inserts a placeholder for the output field into the alarm text: "<tag: n, [tag name]>" whereby n = text string length. 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. 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. 3388 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.3 Working with alarms Formatting alarm text Requirement 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". Note It is not possible to underline tags and text list entries. Result The selected characters are displayed in Runtime with the selected formatting. Removing format settings To remove all text formats, proceed as follows: 1. In the Inspector window, select the characters whose formatting you want to remove in the alarm text. 2. Select "Delete formatting characters" from the shortcut menu. Result The selected characters are displayed in unformatted notation in Runtime. Configuring loop-in alarm Introduction A Loop-In-Alarm is configured in order to change to a screen containing relevant information on an alarm received. WinCC Basic V13.0 System Manual, 02/2014 3389 Visualize processes 10.3 Working with alarms Requirement 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 a button with the following system functions: "EditAlarm" for HMI devices with keys "AlarmViewEditAlarm" for HMI devices without keys The system functions trigger the "Loop-In-Alarm" event. The alarm line has no buttons. Result If you click on the "Loop-In-Alarm" button of the alarm view in Runtime, a screen is opened with information on the selected alarm. See also Configuring analog alarms (Page 3385) Configuring discrete alarms (Page 3383) 3390 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.3 Working with alarms Alarms in the "HMI tags" Editor Configuring discrete alarms in the "HMI tags" editor 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. - When you select a PLC tag, use the data types "Int" or "Word". The input and output area of a PLC tag is unsuitable as trigger. 3. Select the tag at the top of the work area. 4. Click on "<Add>" in the table on the "Discrete alarms" tab at the bottom of the work area. A new discrete alarm is created for the tag. If you have selected the incorrect data type, the tag will be marked in the discrete alarm. 5. Configure the discrete alarm in the Inspector window: - Enter the alarm text under "Properties > Properties > General > Alarm text". You can also insert output fields into the alarm text. - Select an alarm class. - Select the trigger bit of the tag that triggers the discrete alarm under "Properties > Trigger". 6. You can create additional discrete alarms to monitor the tags. Note A tag is monitored using only one alarm type. You should therefore create either analog alarms or discrete alarms for a tag. WinCC Basic V13.0 System Manual, 02/2014 3391 Visualize processes 10.3 Working with alarms Result The configured discrete alarms are created in the "HMI tags" editor and displayed in the "HMI alarms" and "HMI tags" editors. Configuring analog alarms in the "HMI tags" editor Introduction In WinCC, create the discrete and analog alarms, including the trigger tags, in the "HMI tags" editor. You can also edit the alarms as in the "HMI alarms" editor. You can create up to two range values for a tag. You monitor these limits with analog alarms. Requirements The "HMI tags" editor is open. Procedure To configure an analog alarm in the "HMI tags" editor, proceed as follows: 1. To create a tag, click on "<Add>" in the table at the top of the work area. A new tag is created. 2. Configure an internal or external tag as required. 3. In the Inspector window, configure the range values of the tags under "Properties > Properties > Range": - Select whether to use a "Constant" or an "HMI tag" as limit value for your range values. The object list opens when you select "HMI tag". Select the tag you want to use. 3392 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.3 Working with alarms 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. 10.3.2.3 Configuring alarm output 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. 2. Configure acknowledgment In the "Screens" editor, you can set the operator action that will trigger the acknowledgment. WinCC Basic V13.0 System Manual, 02/2014 3393 Visualize processes 10.3 Working with alarms Additional configuration tasks Additional tasks may be necessary for configuring alarm views, depending on the requirements of your project: 1. Setting up authorizations To make sure only authorized operators process the alarms, assign authorizations for the alarm view and the function keys of the HMI device. 2. Configuring the filtering of the alarm view You configure the filtering of the alarms in Runtime in the "Screens" editor. You can also configure alarm views that only display selected alarms. 3. Configure operator input alarms Configure the operator input alarms on the operator controls of the HMI device in the "Screens" editor. A preconfigured operator input alarm is output for an operator action. An operator input is, e.g. the acknowledgment of an alarm. Displaying alarms Options for displaying alarms on the HMI device WinCC offers the following options for displaying alarms on the HMI device: Alarm view The alarm view is configured in a screen. More than one alarm can be displayed simultaneously, depending on the configured size. You can configure multiple alarm views with different contents. Alarm window The Alarm window is configured in the "Global screen" editor. The alarm window can display multiple alarms at the same time, depending on the configured size. The alarm window is not assigned to any screen. Depending on the configuration, the alarm window is opened when an alarm of a specific alarm class is pending. Based on the configuration, it is not closed until the alarm is acknowledged. 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. 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. 3394 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.3 Working with alarms 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 "Errors" ! "System" $ "Warnings" <No symbol> Configuring an alarm view 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. 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". 3. In the table, activate the alarm classes to be displayed in the alarm view. WinCC Basic V13.0 System Manual, 02/2014 3395 Visualize processes 10.3 Working with alarms 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. Result Alarms of various alarm classes are output in the alarm view during runtime. See also Alarm view (Page 3312) Configuring an alarm window Introduction The alarm window displays current alarms. The alarm window is configured in the "Global screen" editor. The alarm window is not assigned to any screen. Depending on the configuration the alarm window is opened when an alarm that belongs to a specific alarm class is active. Depending on the configuration, it is not closed until the alarm is acknowledged. 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. 3396 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.3 Working with alarms 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 Alarm window (Page 3314) 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. WinCC Basic V13.0 System Manual, 02/2014 3397 Visualize processes 10.3 Working with alarms 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. See also Alarm indicator (Page 3317) 3398 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.3 Working with alarms 10.3.2.4 Acknowledging alarms Configuring alarm acknowledgment by means of alarm class Introduction To configure an alarm with alarm acknowledgment, assign it to an alarm class with the "Alarm with single acknowledgment" acknowledgment model. Requirement The "HMI alarms" editor is open. The required alarm class has been created. The required alarm has been created. 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: WinCC Basic V13.0 System Manual, 02/2014 3399 Visualize processes 10.3 Working with alarms Configuring a button to acknowledge an alarm Acknowledgment of a Discrete Alarm by the PLC Requirements 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. 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". 3400 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.3 Working with alarms Acknowledging alarms in an alarm group The various acknowledgment options have the following effect in alarm groups: Operator acknowledges the alarm You acknowledge the alarm of an alarm group, for example, using the <ACK> acknowledgment key or a function key. All alarms of the alarm group are acknowledged. The PLC acknowledges the alarm The alarm of an alarm group is acknowledged by setting a bit in the tag. Only the alarm to be acknowledged is acknowledged. 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 The HMI device 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. WinCC Basic V13.0 System Manual, 02/2014 3401 Visualize processes 10.3 Working with alarms 10.3.3 Operating alarms in Runtime 10.3.3.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 acknowledgement. "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. 3402 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.3 Working with alarms 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 The alarm window is not assigned to any screen. Depending on the configuration the alarm window is opened when an alarm that belongs to a specific alarm class is active. 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 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 is not yet deactivated. The number indicates the number of queued alarms. 10.3.3.2 Simple alarm view, simple 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 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. WinCC Basic V13.0 System Manual, 02/2014 3403 Visualize processes 10.3 Working with alarms 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: Icon 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 3404 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.3 Working with alarms 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 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. 10.3.3.3 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 has not gone out yet. The displayed number indicates the number of queued alarms. Operation Depending on the configuration, when operating the alarm indicator an alarm window is opened. The alarm indicator can only be operated with the touch screen. WinCC Basic V13.0 System Manual, 02/2014 3405 Visualize processes 10.3 Working with alarms 10.3.3.4 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 the option "Acknowledgment by the PLC". 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. Requirement An alarm is displayed on the HMI device. Procedure To acknowledge an alarm, proceed as follows: 1. Select the alarm. 2. Click on the button. 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. 3406 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.3 Working with alarms 10.3.4 Reference 10.3.4.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. The table shows all the system functions available for displaying and editing alarms. 10.3.4.2 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. 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. ShowAlarmWindow Hides or shows the alarm window on the HMI device. System events Basics on system events System events System events on the HMI device provide information about internal states of the HMI device and PLC. The following overview illustrates when a system event occurs and how to eliminate the cause of error. Note HMI device dependency Some of the system events described in this section apply to the individual HMI devices based on their scope of functions. WinCC Basic V13.0 System Manual, 02/2014 3407 Visualize processes 10.3 Working with alarms 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. 30000 - Alarms errors when using system functions Meaning of the system events All system events that can be displayed are listed below. The system events are divided into different ranges. Table 10-2 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: 3408 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.3 Working with alarms Table 10-3 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 10-4 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. -- 70000 - Win32 function alarms Meaning of the system events All system events that can be displayed are listed below. Table 10-5 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. Check the time which is to be set. The error alarm only appears in connection with area Using Windows NT/XP: Users running WinCC Runtime pointer "Date/time PLC". Possible causes: must be granted the right to set the system time of the An invalid time was transferred in the job mailbox. operating system. 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. WinCC Basic V13.0 System Manual, 02/2014 3409 Visualize processes 10.3 Working with alarms Number Effect/causes Remedy 70012 Error when executing the function "StopRuntime" with the "Runtime and operating system" option. Windows and WinCC Runtime are not closed. The error was possibly generated because other programs cannot be closed. Close all programs currently running. Then close Windows. 70013 The system time could not be modified because an invalid value was entered. Incorrect separators may have been used. Check the time which is to be set. 70014 The system time could not be modified. Possible causes: 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. An invalid time was transferred. The Windows user has no right to modify the system time. Windows rejects the setting request. 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. Check the screen number in the function or job with the screen numbers configured. Assign the number to a screen if necessary. Or: The screen is blocked. Check the details for the screen call and whether the screen is blocked for specific users. Or: Screen call has not been executed correctly. 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. -- 3410 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.3 Working with alarms Number Effect/causes Remedy 70028 The files from the RAM have been copied in the Flash memory. The files from the RAM have been copied in the Flash memory. Following a restart, these saved files are copied back to the RAM file system. -- 70029 Backup of the RAM file system has failed. No backup copy of the RAM file system has been made. Check the settings in the "Control Panel > OP" dialog and save the RAM file system using the "Save Files" button in the "Persistent Storage" tab. 70030 The parameters configured for the system function Compare the parameters configured for the system are faulty. function with the parameters configured for the PLCs The connection to the new PLC was not established. and correct them as necessary. 70031 The PLC configured in the system function is not an Compare the S7 PLC name parameter configured for S7 PLC. the system function with the parameters configured for The connection to the new PLC was not established. 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. 70033 An e-mail cannot be sent because a TCP/IP Check the network connection to the SMTP server and connection to the SMTP server no longer exists. re-establish it if necessary. 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. 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: 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. -- WinCC Basic V13.0 System Manual, 02/2014 Check the number of the tab sequence and correct it if necessary. 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" 3411 Visualize processes 10.3 Working with alarms Number Effect/causes Remedy 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. 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. The system function was not calculated. 70044 An error occurred while sending the e-mails. The e- Check the SMTP settings and the error message in the mails were not sent. 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. 110000 - Offline function alarms Meaning of the system events All system events that can be displayed are listed below. Table 10-6 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: 3412 the project ID entered on the PLC. the project ID entered in WinCC. WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.3 Working with alarms 120000 - Trend alarms Meaning of the system alarms All system alarms that can be displayed are listed below. Table 10-7 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. 140000 - Connection alarms: Connection + device Meaning of the system events All system events that can be displayed are listed below. Table 10-8 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. Check the connection and 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 address for the HMI device. Check the connection and whether the PLC is switched on. Check the parameters set in the "Set PG/PC interface" dialog of the Control Panel. 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.). WinCC Basic V13.0 System Manual, 02/2014 3413 Visualize processes 10.3 Working with alarms 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 database: 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 parameters set in the "Set PG/PC interface" dialog of the Control Panel. Restart the system. 140008 An incorrect baud rate prevents tag updates or write operations. The following parameters could not be written to the registry database: 0: General error 1: Wrong version 2: Profile cannot be written to the registry database. 3: The subnet type cannot be written to the registry database. 4: The Target Rotation Time cannot be written to the registry database. 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 Initialization error (e.g. if WinCC Runtime was closed in Task Manager). Or: Another application (e.g. STEP 7) 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. 3414 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.3 Working with alarms 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 Mismatch of the PLC and project (FWX file) versions. The 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. 140021 Setup of the connection to the PLC failed. Incorrect configuration of the "Access password" for the connection to the PLC. Select the "Access password" area in the "Connections" editor to check the password entered for the connection to the PLC. Assign the correct password. The "Password" for the connection to the PLC is assigned in the "Security" area of the PLC properties. 140022 140025 Setup of the connection to the PLC failed. Incorrect configuration of the access password for the connection to the PLC. Select the "Access password" area in the "Connections" editor to check the password entered for the connection to the PLC. Setup of the connection to the PLC failed. Enable the access password in the PLC display. The "Password" for the connection to the PLC is assigned in the "Security" area of the PLC properties. The access password of the PLC is disabled in the PLC display. 180000 - General alarms Meaning of the system events All system events that can be displayed are listed below. Table 10-9 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: Reinstall WinCC Runtime. "TouchInputPC.exe" was not registered due to faulty Setup. WinCC Basic V13.0 System Manual, 02/2014 3415 Visualize processes 10.3 Working with alarms 190000 - Tag alarms Meaning of the system events All system events that can be displayed are listed below. Table 10-10 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: Observe the configured or current tag limits. Value input System function Script 190009 An attempt was made to assign this tag a value that Observe the range of values for the data type of the tags. 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. 190010 190011 The rate at which values are written to the tag is too high (e.g. initiated in a script loop). Values will be lost because buffer capacity is limited to 100 operations. 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". Possible cause 1: The value entered could not be written to the configured PLC tag because the high or low limit was exceeded. Note that the value entered must be within the range of values of the control tag. The system discarded the entry and restored the original value. Possible cause 2: The connection to the PLC was interrupted. 3416 Check the connection to the PLC. WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.3 Working with alarms Number Effect/causes Remedy 190012 It is not possible to convert a value from a source format to a target format, for example: Check the range of values, or the data type of the tag. 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. 190013 You entered a string that exceeds the tag length. The string is truncated automatically to a valid length. Always enter strings that do not exceed the valid tag length. 190100 - Area pointer alarms 190100 - Area pointer alarms Number Effect/causes Remedy 190100 The area pointer is not updated because the address configured for this pointer does not exist. Type 1 Warnings 2 Errors 3 PLC acknowledgment 4 HMI device acknowledgment 5 LED image 6 Trend request 7 Trend transfer 1 8 Trend transfer 2 No.: Consecutive number displayed in WinCC ES. Check the configuration. 190101 The area pointer is not updated because it is not possible to map the PLC type to the area pointer type. Parameter type and no.: see alarm 190100 -- 190102 The area pointer is updated after the cause of the last error state has been eliminated (recovery of normal operation). Parameter type and no.: See alarm 190100. -- WinCC Basic V13.0 System Manual, 02/2014 3417 Visualize processes 10.3 Working with alarms 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 Change the address or set the address in the PLC at an to the address configured in the PLC is not possible. 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: Ensure that the cable is plugged in and the PLC is operational. Restart the system if the system alarm persists. The cable is defective. The PLC does not respond, is defective, etc. System overload 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. 3418 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.3 Working with alarms 220000 - WinCC communication driver alarms 220000 - WinCC communication driver alarms Number Effect/causes Remedy 220001 The tag is not downloaded because write access to data type Bool/Bit is not supported by the sublevel communication driver/HMI device. Change the configuration. 220002 The tag is not downloaded because write access to data type Byte is not supported by the sublevel communication driver/HMI device. Change the configuration. 220003 The communication driver cannot be loaded as it is possibly not installed. Install the driver by reinstalling WinCC Runtime. 220004 Communication is down and no update data is transferred because the cable is not connected or defective etc. Check the connection. 220005 Communication is up. -- 220006 The connection between the specified PLC and the specified port is active. -- 220007 The connection to the specified PLC is interrupted at the specified port. Check the following: Is the cable plugged in? Is the PLC OK? Is the right port being used? Is your configuration OK (port parameters, protocol settings, PLC address)? Restart the system if the system event persists. 220008 The communication driver cannot access or open the specified port. This port might be in use by another application, or a port that does not exist on the target device is being used. Close all applications that access the port and restart the computer. Use another port that exists in the system. No communication with the PLC. WinCC Basic V13.0 System Manual, 02/2014 3419 Visualize processes 10.3 Working with alarms 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. Enter a practical value, or delete a user that is no longer required. Possible causes: The range of values is exceeded. You entered invalid characters The valid maximum number of users has been exceeded. 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. -- 3420 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.3 Working with alarms 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 On 503 Service unavailable error: Check whether WinCC Runtime is running on the server and whether the HTTP channel is supported. 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. 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. WinCC Basic V13.0 System Manual, 02/2014 3421 Visualize processes 10.3 Working with alarms 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. -- 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 "Administrator" 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. 260012 The password entries in the "Change Password" You have to log on to the system again. Then enter dialog and in the confirmation field do not match. the identical password twice to be able to change the The password is not changed. User will be password. logged off. 3422 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.3 Working with alarms Number Effect/causes Remedy 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 comprises at least three characters. 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. Check the connection to the SIMATIC Logon Server and its configuration; for example: 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. 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. 1. Port number 2. IP address 3. Server name 4. Functional transfer cable Or use a local user. Log in again and choose a different password. Check the password rules on the SIMATIC Logon Server. The old password remains and the user is logged off. 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. Wait until the logon operation is complete. The logon dialog is not opened. The user action is not executed. 260035 The last attempt to change the password was not completed. A user action or a logon dialog can therefore not be called. Wait until the procedure is complete. The logon dialog is not opened. The user action is not executed. 260036 There are insufficient licenses on the SIMATIC Logon Sever. The logon is not authorized. WinCC Basic V13.0 System Manual, 02/2014 Check the licensing on the SIMATIC Logon Server. 3423 Visualize processes 10.3 Working with alarms Number Effect/causes Remedy 260037 There is no license on the SIMATIC Logon Sever. A logon is not possible. Check the licensing on the SIMATIC Logon Server. It is not possible to log on via the SIMATIC Logon Server, only via a local user. 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. 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. Check connection to the domain and its configuration in the Runtime security settings editor. Or use a local user. Try again. If necessary, check the password data on the SIMATIC Logon Server. The new user is not logged in. If a different user was logged on before, then this user is logged off. 260044 It was not possible to log the user on to the SIMATIC Logon Server as his account is blocked. Check the user data on the SIMATIC Logon Server. The new user is not logged in. If a different user was logged on before, then this user is logged off. 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. -- 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. 3424 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.3 Working with alarms Number Effect/causes Remedy 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. 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. WinCC Basic V13.0 System Manual, 02/2014 3425 Visualize processes 10.3 Working with alarms Number Effect/causes Remedy 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 The following remedies are available: under a data record number that already exists. Check the source for the number (constant or tag The operation is not executed. 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? 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. --- 3426 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.3 Working with alarms Number Effect/causes Remedy 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. 290027 Unable to connect to the PLC at present. As a Check the connection to the PLC. 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. 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. -- 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. -- WinCC Basic V13.0 System Manual, 02/2014 Set the mailbox status to zero. 3427 Visualize processes 10.3 Working with alarms Number Effect/causes Remedy 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). 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 Enter a value within the recipe tag limits. value that exceeds the high limit of the recipe tag. The entry is discarded. 3428 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.3 Working with alarms Number Effect/causes Remedy 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. Download the project to the device again, including the recipes (the corresponding check box in the download dialog must be check marked). 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. 10.3.5 Configuring system diagnostics 10.3.5.1 System diagnostics basics Introduction Using system diagnostics, you can display the messages from the diagnostic buffer of all integrated connections. System diagnostics view The system diagnostics display is an operating and display object that you use in a screen. You navigate directly to the cause of the error and the associated connection. You have access to all integrated connections that you have configured in the "Devices & networks" editor. WinCC Basic V13.0 System Manual, 02/2014 3429 Visualize processes 10.3 Working with alarms 10.3.5.2 System diagnostics views Introduction Three different views are available in the simple system diagnostic view. Device view Diagnostic buffer view Detail view Device view The device view is only displayed if more than one integrated connection has been configured. The device view shows all available connections in a table. Double-clicking a connection opens the diagnostic buffer view. Diagnostic buffer view The diagnostic buffer view shows the current data from the diagnostic buffer. To update the diagnostic buffer view, you click 3430 . WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.3 Working with alarms Detail view The detail view gives detailed information about the selected connection and any pending errors. Check whether the data is correct in the detail view. Note Contents of the detail view The contents of the detail view are only available for integrated connections with S7 1200 and S7 1500 PLCs. Navigation buttons Button Key Function Enter key In the device view: Opens the diagnostic buffer view of the selected device. In the diagnostic buffer view: Opens the detail view. Esc key In the diagnostic buffer view: Opens the device view. In the detail view: Opens the diagnostic buffer view. Configured function key, e.g. F1. WinCC Basic V13.0 System Manual, 02/2014 Updates the diagnostic buffer view. 3431 Visualize processes 10.3 Working with alarms See also System diagnostics view (Page 3325) Configuring the system diagnostic view (Page 3432) 10.3.5.3 Configuring the system diagnostic view Introduction For an overview of all integrated connections, you insert a system diagnostics view in your project. Requirements A PLC has been created. A Basic Panel has been created. An integrated connection has been created in the "Devices & Networks" editor. 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. In the Inspector window, select "Properties > Layout". 3. Enter a number under "Lines per entry", i.e. 5. Result The system diagnostics view has been added to the screen. To obtain the latest alarms, update the diagnostic buffer. See also System diagnostics views (Page 3430) 3432 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.4 Working with recipes 10.4 Working with recipes 10.4.1 Basics 10.4.1.1 Definition and applications Introduction Related data, e.g. machine parameter assignments or production data, are combined in recipes. 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 in the configuration. A recipe contains recipe data records. These differ in terms of their values, but not their structure. Recipes are saved on the HMI device. A recipe data record is always transferred completely and in a single pass between the HMI device and the PLC. Note Restrictions in the import/export It is not possible to export or import the recipes for Basic Panels. Complete recipe data but not individual recipe data records can be exported and imported with ProSave to the CSV format and transmitted to the HMI device. Runtime is stopped in the meantime. 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. WinCC Basic V13.0 System Manual, 02/2014 3433 Visualize processes 10.4 Working with recipes 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. 10.4.1.2 Examples for using recipes Recipes are used in the manufacturing industry and mechanical engineering, for example. The following recipes show typical applications which you can implement with the recipe function of WinCC: Machine parameter assignment One field of application for recipes is the assignment of machine parameters in the manufacturing industry: A machine cuts wooden boards to a certain size and drills holes. The guide rails and drill have to be moved to new positions according to the board size. The required position data are stored as data records in a recipe. You reassign the machine parameters using "Teach in" mode if, for example, a new board size is to be processed. You transfer the new position data directly from the PLC to the HMI device and save it as a new data record. Batch production Batch production in the food processing industry represents another field of application for recipes: A filling station in a fruit juice plant produces juice, nectar, and fruit drinks in a variety of flavors. The ingredients are always the same, differing only in their mixing ratios. Each flavor corresponds to a recipe. Each mixing ratio corresponds to a data record. All of the required data for a mixing ratio can be transferred to the machine control at the touch of a button. 10.4.1.3 Structure of recipes 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: 3434 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.4 Working with recipes In a soft drinks production plant, a recipe is needed for different flavors. Drink variants include fruit juice drink, juice and nectar. Recipe The recipe contains all the recipe data records for the different drink variants. -XLFH :DWHU 6XJDU )ODYRU &RQFHQWUDWH 5 30 23 80 5HFLSHGDWDUHFRUG 1HFWDU :DWHU 6XJDU )ODYRU &RQFHQWUDWH 15 35 20 70 5HFLSHHOHPHQW 5HFLSH 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. WinCC Basic V13.0 System Manual, 02/2014 3435 Visualize processes 10.4 Working with recipes 10.4.1.4 Displaying recipes Introduction You need to configure the recipe view to display recipes. You can change the values of a recipe in the recipe view and thereby influence the manufacturing process or a machine. Recipe view The recipe view is an off-the-shelf WinCC display and operator control 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. -XLFH %HYHUDJH 1HFWDU 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. 10.4.1.5 Flow of data for recipes 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 recipe data. 3436 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.4 Working with recipes Overview of the flow of data The following figure illustrates the flow of data in recipes: +0,GHYLFH 5HFLSHPHPRU\ 5HFLSHYLHZ 5HFLSH 5HFLSH 5HFLSH 5HFLSHQ 5HFLSHWDJ 3/& To transfer recipe data records to the PLC, use the "To PLC" button in the recipe view or an operator control with the system function "RecipeViewSetDataRecordToPLC". Data are exchanged with the PLC by recipe tags. On Basic Panels you cannot use recipe tags outside a recipe, e.g. not in I/O fields. 10.4.1.6 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. WinCC Basic V13.0 System Manual, 02/2014 3437 Visualize processes 10.4 Working with recipes 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. 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" 10.4.2 Elements and basic settings 10.4.2.1 "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. 3438 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.4 Working with recipes 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. 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: WinCC Basic V13.0 System Manual, 02/2014 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. 3439 Visualize processes 10.4 Working with recipes Setting Description 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. Note 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". 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. 3440 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. WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.4 Working with recipes 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 10.4.3 Displaying and editing recipes in Runtime 10.4.3.1 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. WinCC Basic V13.0 System Manual, 02/2014 3441 Visualize processes 10.4 Working with recipes -XLFH %HYHUDJH 1HFWDU Display of values Note 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 3319) 10.4.3.2 Behavior 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. 3442 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.4 Working with recipes Display after import of recipe data Note 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 Note 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. 10.4.4 Configuring recipes 10.4.4.1 General configuration procedure Carry out the following configuration steps when you create a new recipe: Step Description 1 Define the structure of the recipe. 2 Create tags according to the recipe structure. Assign process names to these tags. 3 WinCC Basic V13.0 System Manual, 02/2014 Create the recipe. 3443 Visualize processes 10.4 Working with recipes Step Description 4 Enter the required properties for the recipe: Language-dependent view name of the recipe "Coordinated transfer of data records" option Not for Basic Panels: Recipe storage location "Synchronize recipe view and recipe tags" option "Manual transfer of individual modified values (teach-in mode)" option 5 Create the recipe elements and enter the required properties: Language-dependent view name of the recipe elements Tag binding of the recipe elements Standard values and decimal places (power of ten) for the recipe elements 6 Create the recipe data records. Enter the language-specific display names for the recipe data records. 7 Configure a screen with recipe view or a recipe screen. Note 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. Note 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). 10.4.4.2 Creating and Editing Recipes Creating a new recipe Introduction To create a complete recipe, start by creating a new recipe, assign the corresponding recipe elements and then define the associated values in a recipe data record. Requirement The tags for the recipe have been created. The "Recipes" editor is open. 3444 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.4 Working with recipes Create recipe Create a recipe as follows: 1. Click "Add" in the first free row of the table in the "Recipes" editor. The new recipe is created and displayed on a line. 2. Enter a descriptive name for the recipe under "Name" in the "General" area. This name identifies the recipe unambiguously within the project. 3. Select "Display name" to enter the language-specific name to be displayed in runtime. 4. Select a recipe number in "Number". The number identifies the recipe unambiguously within the HMI device. The recipe is automatically assigned a version that indicates the date and time of the last change. As an alternative, you can enter specific information relating to the recipe. 5. Specify the storage location for recipe data records in "Data medium". The options offered depend on the specific HMI device used. Note 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. WinCC Basic V13.0 System Manual, 02/2014 3445 Visualize processes 10.4 Working with recipes 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". Note Basic Panels and OP77A, TP177A (Portrait) Because the recipe tags cannot be additionally used in I/O fields in screens for Basic Panels, the "Synchronize recipe view and recipe tags" is not available; you will also not be able to use the "Manual transfer of individual modified values (teach-in mode)" option. 8. Deactivate "Manual transfer of individual modified values (teach-in mode)" to specify that the recipe tags are automatically transferred to the PLC when editing the I/O fields. 9. Activate "Coordinated transfer of data records" to monitor the transfer of recipe data in Runtime using area pointers. 10.Select the appropriate connection to the PLC for coordinated transfer under "Synchronize with". Create recipe element To create recipe elements, proceed as follows: 1. Click the "Elements" tab. 2. Click "Add" in the first free line of the table editor. A new recipe element is created. 3. Enter a descriptive name for the element under "Name". The name identifies the element uniquely within the recipe. 4. Enter a language-specific display name for the element under "Display name". The display name appears in the recipe view, for example, in runtime. 3446 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.4 Working with recipes 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. WinCC Basic V13.0 System Manual, 02/2014 3447 Visualize processes 10.4 Working with recipes 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. 3448 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.4 Working with recipes 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 Note 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. WinCC Basic V13.0 System Manual, 02/2014 3449 Visualize processes 10.4 Working with recipes 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. 3450 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.4 Working with recipes 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. WinCC Basic V13.0 System Manual, 02/2014 3451 Visualize processes 10.4 Working with recipes 10.4.4.3 Configuring the display of recipes Configuring the simple recipe view Requirement The recipe has been created. The "Screens" editor is open. The screen has been created and opened. NOTICE 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". 3452 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.4 Working with recipes 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". WinCC Basic V13.0 System Manual, 02/2014 3453 Visualize processes 10.4 Working with recipes 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. Deactivation of the editing mode in "Properties > Properties > General" has no impact on the toolbar icons. The buttons you activated in "Properties > Toolbar" can still be used even if editing mode is disabled. 3454 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.4 Working with recipes 10.4.5 Using recipes in Runtime 10.4.5.1 Using the 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: -XLFH %HYHUDJH 1HFWDU 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. Button WinCC Basic V13.0 System Manual, 02/2014 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. 3455 Visualize processes 10.4 Working with recipes Button Key Function <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 3456 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. WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.4 Working with recipes 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. WinCC Basic V13.0 System Manual, 02/2014 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. 3457 Visualize processes 10.4 Working with recipes 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 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. 3458 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.4 Working with recipes 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. 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. WinCC Basic V13.0 System Manual, 02/2014 3459 Visualize processes 10.4 Working with recipes 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. 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. 3460 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.4 Working with recipes 10.4.6 Example 10.4.6.1 Example of creating a recipe Task In this example, you create three recipes for a fruit juice mixing machine. The fruit juice mixing machine produces drinks with "orange", "apple" and "tropical" flavors. You create a recipe for each flavor. Each recipe contains a recipe data record for the following mixing ratios: Beverage Nectar Juice Settings The settings relate to an HMI device which is connected to a SIMATIC S7-300 or SIMATIC S7-400. In this example, you will need the following tags, recipes, recipe entries and recipe data records: Tags: Name PLC connection Address Type Liter water Yes DB 120, DBW 0 Integer Liter concentrate Yes DB 120, DBW 4 Integer Kilo sugar Yes DB 120, DBW 8 Integer Gram flavoring Yes DB 120, DBW 12 Integer Recipes: 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: WinCC Basic V13.0 System Manual, 02/2014 3461 Visualize processes 10.4 Working with recipes 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. 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. 3462 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.5 Configuring user administration 10.5 Configuring user administration 10.5.1 Field of application of the user administration Principle The access protection controls access to data and functions in Runtime. This feature protects your applications against unauthorized operation. Safety-related operations are already limited to specific user groups when a project is being created. To this purpose you set up users and user groups that you equip with characteristic access rights, so-called authorizations. You then configure the authorizations required for operation of safety-related objects. Operators only have access, for example, to specific operator controls. Commissioners, for example, have unlimited access in Runtime. Definition You administer users, user groups and authorizations centrally in the user administration of WinCC. You transfer users and user groups together with the project to the HMI device. The users and passwords are managed on the HMI device in the User view. Application example You configure the "Service" authorization so that only service technicians have access to the configuration parameters. You assign the authorization to the "Service technician" user group. This allows all members of this group to set the protected configuration parameters. NOTICE Access protection does not protect against incorrect operations. It is your job to ensure that only authorized personnel with appropriate training will design, commission, operate and maintain plants and machines. Access protection is not suitable for defining work routines and monitoring their observance. 10.5.2 Form of the user administration Introduction In case of a project in manufacturing engineering, the environment at the equipment manufacturer has to be differentiated from the environment at the end customer as plant operator. The equipment manufacturer allows users, for example Mr. Foreman, a specific access within the application or HMI device. However, a user Foreman does not exist at the end customer. The machine manufacturer cannot know the end users and the tasks they have to perform for configuration. The final users are usually set after commissioning at the end customer. WinCC Basic V13.0 System Manual, 02/2014 3463 Visualize processes 10.5 Configuring user administration :LQ&&:RUNEHQFK $GPLQLVWUDWRU &RQILJXUDWLRQ 8VHUJURXS 6HUYLFH7HFKQLFLDQ $XWKRUL]DWLRQV 0LOOHU (GLWUHFLSHGDWDUHFRUGV &KDQJHV\VWHPSDUDPHWHUV 6PLWKJURXS /RJSURFHVVYDOXHV )RUHPDQ 0U)RUHPDQ 3URJUDP 2SHUDWRU FRQWUROV %ORFN 3URFHVV YDOXHV 6\VWHP 5HFLSH SDUDPHWHUV /RJJLQJ Principle To minimize the work required for management, authorizations are assigned via user groups and not directly to individual users. A user group assembles configured authorizations according to common jobs. For example, all permissions required for a service job are collected in a "Service technician" group. When you create a user who should be responsible for servicing, you simply assign him to the "Service technician" group. The user view enables user administration in Runtime. Use user view to create, delete and assign an authorization to users in Runtime. The user administration separates the administration of the users from the configuration of the authorizations. This ensures flexibility at the access protection. Defaults can be set for the user administration during the configuration phase in the Engineering System. 10.5.3 Basics 10.5.3.1 Users Introduction You can create users in the "Users" tab of the "User administration" editor and assign them to user groups. The "Users" tab is part of the user administration in WinCC. 3464 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.5 Configuring user administration Open To open the "Users" tab, double-click "User administration" in the project window. Work area The users are managed in the work area: You create or delete users. You assign users to user groups. Note You can assign a user to exactly one user group. Inspector window When you select a user, you can change the password in the "General" group. Under "Automatic logoff" you can specify if the user is to be automatically logged off by the HMI device when there is no operator activity after the specified time. 10.5.3.2 Users work area Introduction The "Users" work area lists the users and user groups in table form. You administrate the users and assign them to a user group. Principle The work area consists of the "Users" and "Groups" tables. WinCC Basic V13.0 System Manual, 02/2014 3465 Visualize processes 10.5 Configuring user administration The "Users" table shows the existing users. When you select a user in this table, the "Groups" table shows the user group to which the user belongs. Note For the user "Administrator", the default password is "administrator". For security reasons, you should change the password of this user. 10.5.3.3 User groups Introduction You can create users and authorizations in the "User groups" tab of the "User Administration" editor. The "User groups" tab is part of the user administration in WinCC. Open Double-click the "User administration" in the project window. Open the "User groups" tab. Work area The user groups and authorizations are managed in the work area: You create new user groups and authorizations or delete them. You assign the authorizations to the user groups. Inspector window When a user group or an authorization is selected, you can edit the name in the "General" group. You can also enter a brief description in the "Comment" group. 10.5.3.4 User groups work area Introduction The "User groups" work area shows a table of the groups and their authorizations. You administer the user groups and assign authorizations to them. 3466 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.5 Configuring user administration Principle The work area consists of the "Groups" and "Authorizations" tables. The "Groups" table shows the existing user groups. When you select a user group in this table, the "Active" column of the "Authorizations" table shows the authorizations which were assigned to the user group. The number of the user group and of the authorization is assigned by the user administration. The designations and descriptions are assigned by you. The number of predefined authorizations are fixed. Authorizations that you create can be freely edited. Ensure that the assigned numbers are unique. 10.5.3.5 Settings for the user administration Introduction In the "Runtime settings > User administration" editor, configure the security settings for users and their passwords in runtime. Open Double-click the "Runtime settings" editor in the project window. Click "User administration". WinCC Basic V13.0 System Manual, 02/2014 3467 Visualize processes 10.5 Configuring user administration Work area You carry out the settings for the validity of passwords in runtime in the work area. You determine the complexity of the password, for example. Effects in Runtime The security settings have the following effects in runtime, depending on the configuration. "General" group - "Enable limit for logon attempts" check box selected The number entered in the "Number of incorrect logon attempts" box defines the number of logon attempts a user is allowed before being assigned to the "Unauthorized" group. "Enable limit for logon attempts" check box not selected The user has an unlimited number of logon attempts in runtime. - "Number of incorrect logon attempts" field If you enter "4" in the field, for example, and the fourth logon attempt fails, the user is automatically assigned to the "Unauthorized" group. You can specify 1 to 9 attempts. - "Logon only with password" check box When the check box is selected, the user will be authenticated by the password. The user name is not required. To match users to passwords, you cannot configure passwords more than once. "Hierarchy level" group - "Group-specific rights for user administration" check box When this check box is selected, administrators only manage users whose group number is less than or equal to their own. For example, an administrator whose group number is 5 can only manage users whose group number is less than or equal to 5. This means that the administrator can assign users only to groups with a group number less than or equal to 5. 3468 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.5 Configuring user administration "Password" group - "Enable password aging" checkbox selected The password expires after the number of days set in the "Validity of the password (days)" field. The "Password aging" column is selected in the "User groups" editor. This enables you to specify group-by-group, if the passwords should expire or if the password generations should be saved. Passwords never expire for groups for which password aging is not enabled. - "Prewarning time (days)" field The user is informed that the password will expire the specified number of days before the password expires. - "Password generations" field If the user changes the password, the new password must be different from the specified number of previous passwords. The number of password generations ranges from 1 to 5. "Password complexity" group - "Must include special characters" check box selected The user must enter a password containing at least one special character at any position. - "Must include number" check box selected The user must enter a password containing at least one number at any position. - "Minimum password length" field The user must enter a password with a minimum length, as specified in the "Minimum password length" field. The minimum length of the password is 3 characters. 10.5.4 Setting up the user administration 10.5.4.1 Basics on user administration Principle This section addresses four target groups. The topics are organized correspondingly. The target groups serve as examples for different groups of persons who use the user administration. 1. Administrator OEM 2. Administrator RT 3. Planners 4. Operator As Administrator OEM you create the user groups, users and authorizations for Runtime in the Engineering System of, for example, an equipment manufacturer. As Administrator RT you administer users in Runtime by means of the "User view." WinCC Basic V13.0 System Manual, 02/2014 3469 Visualize processes 10.5 Configuring user administration As the project engineer you assign the authorizations to the user groups in the Engineering System. In addition, you configure the authorizations for objects. As Operator you log on in runtime. You can only access a protected object if you have the required authorization. Note The Administrator RT target group already exists in the Runtime user administration as the predefined user group "Administrator group." For a better understanding the predefined user groups and authorizations are not used below. 10.5.4.2 Administering users for Runtime Creating an authorization Introduction You create an authorization and assign it to one or more user groups. Requirements The "User groups" work area is open. Procedure 1. Double-click "Add" in the "Authorizations" table. 2. Enter "Stop runtime" as the name of the authorization. 3. Enter a brief description as the "Comment". Creating a user group Introduction User groups are created so that you do not have to assign an authorization to every single user. You create a user group, assign authorizations and then assign users to it. Note The name of the user group has to be unique within the project. Otherwise the input is not accepted. 3470 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.5 Configuring user administration Note Using SIMATIC Logon Ensure that the names of the user groups in Windows and WinCC are identical. Requirements The "User groups" work area is open. Procedure 1. Double-click "Add" in the "Groups" table. 2. Enter "Operators" as the "Name" of the user group. 3. Change the "Number" of the user group as required. 4. Enter "Display name" of the "Operators" user group. 5. Enter a brief description as the "Comment". In runtime, the user view shows the display name of the user group. The display name of the user group depends on the language. You can specify the name in several languages and switch between languages in runtime. See also Assigning an authorization (Page 3471) Creating users (Page 3472) Assigning a user to a user group (Page 3473) Managing user groups (Page 3475) User administration (Page 3474) Assigning an authorization Introduction When you allocate an authorization to a user group, all assigned users have this authorization. Requirements A "Stop runtime" authorization has been created. An "Operators" user group has been created. The "User groups" work area is open. WinCC Basic V13.0 System Manual, 02/2014 3471 Visualize processes 10.5 Configuring user administration Procedure 1. Click on the "Operators" user group in the "Groups" table. The "Authorizations" table shows all authorizations. 2. Enable the "Stop runtime" authorization in the "Authorizations" table. Note The "Stop runtime" authorization is only a designation and does not have any relation to the function "StopRuntime". You have to establish this relation yourself. To do so, configure the "StopRuntime" system functions at a button and select "Stop runtime" as the "Authorization". See also Creating a user group (Page 3470) Creating users Introduction You create a user so that users can log on with their user names in runtime after loading to the device. As an alternative, you can create and change users by means of the "User view" in Runtime. In order for a created user to have authorizations you have to assign him to a user group and allocate authorizations to the user group. The logon is successful when the user name entered during the logon matches a user in Runtime. In addition, the entered password must agree with the stored password of the user. Note Note that the entry is case-sensitive. Requirements The "Users" work area is open. 3472 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.5 Configuring user administration Procedure 1. Double-click "Add" in the "Users" table. 2. Enter "Foreman" as the user name. Note The user name must be unique within the project. Otherwise the input is not accepted. Note Do not use special characters such as / " $ % ? when you enter a user name and a password. ' &. 3. Click the button in the "Password" column. A dialog box for entering the password is displayed. 4. Enter the password of the user. 5. To confirm the password enter it a second time in the lower field. 6. Close the dialog box using the icon. 7. If a user is to be logged off after a specific time period, activate "Automatic logoff". 8. Click in the "Logoff time" column. The preset value for "Logoff time" is 5 minutes. 9. Enter a brief description as the "Comment". See also Creating a user group (Page 3470) Assigning a user to a user group Introduction When you assign a user to a user group, the user has the authorizations of the user group. Note You have to assign a user to exactly one user group. The assignment is checked during the consistency check and generation of the project. Requirements The user "Foreman" has been created. An "Operators" user group has been created. The "Users" work area is open. WinCC Basic V13.0 System Manual, 02/2014 3473 Visualize processes 10.5 Configuring user administration Procedure 1. Click on the "Foreman" user in the "Users" table. The "Groups" table shows all user groups. 2. Activate the "Operators" user group in the "Groups" table. See also Creating a user group (Page 3470) User administration Introduction In the work area, you can administer users and assign them to user groups. Requirements The "Users" work area is open. Changing the user name 1. In the "Users" table, double-click the field in the "Name" column to change the user name. 2. Change the user name. 3. Confirm your entry with <Return>. Alternatively, select the user in the work area. Change the user name under "Properties > Properties > General" in the Inspector window. Changing the password of the user 1. Click the button in the "Password" column of the "Users" table. A dialog for entering the password opens. 2. In the "Enter password" field, enter the new password. 3. Reenter the new password in the "Confirm password" field. 4. Confirm your entry with <Return>. Alternatively, select the user in the work area. Change the password under "Properties > Properties > General" in the Inspector window. Displaying invisible columns 1. Position the mouse cursor on the title of the "Users" table. 2. Right-click to open the shortcut menu and enable the display of the "Logoff time" column, for example. 3474 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.5 Configuring user administration Changing the logoff time of the user 1. In the "Users" area, double-click on the field in the "Logoff time" column to change the logoff time. 2. Change the logoff time. 3. Confirm your entry with <Return>. Alternatively, select the user in the work area. Change the logoff time under "Properties > Properties > Automatic logoff" in the Inspector window. Deleting a user 1. Select the line of the user to be deleted. 2. Open the shortcut menu with the right mouse button and select the "Delete" command. Note Predefined users cannot be deleted. See also Creating a user group (Page 3470) Managing user groups Introduction In the workplace you administer user groups and assign authorizations for use in runtime. Requirements The "User groups" work area is open. Changing the name of the user group 1. In the "Groups" table, double-click the field in the "Name" column to change the name of the user group. 2. Change the name of the user group. 3. Confirm your entry with <Return>. Alternatively, select the user group in the work area. Change the name under "Properties > Properties > General" in the Inspector window. Note Predefined user groups cannot be deleted. WinCC Basic V13.0 System Manual, 02/2014 3475 Visualize processes 10.5 Configuring user administration Displaying invisible columns 1. Position the mouse cursor on the title of the "Users" table. 2. Right-click to open the shortcut menu and enable the display of the "Display name" column, for example. Changing the displayed name of the user group 1. In the "Groups" table, double-click the field in the "Display name" column to change the display name of the user group. 2. Change the displayed name of the user group. 3. Confirm your entry with <Return>. Alternatively, select the user group in the work area. Change the display name under "Properties > Properties > General" in the Inspector window. Deleting a user group 1. Mark the line of the user group to be deleted. 2. Open the shortcut menu with the right mouse button and select the "Delete" command. Note Predefined user groups cannot be deleted. Changing the name of the authorization 1. In the "Authorizations" table, double-click the field in the "Name" column to change the name of the authorization. 2. Change the name of the authorization. 3. Confirm your entry with <Return>. Alternatively, select the authorization in the work area. Change the name under "Properties > Properties > General" in the Inspector window. Deleting authorizations 1. Mark the line of the authorization to be deleted. 2. Open the shortcut menu with the right mouse button and select the "Delete" command. Note Predefined authorizations cannot be deleted. See also Creating a user group (Page 3470) 3476 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.5 Configuring user administration 10.5.4.3 Managing users in Runtime Users in Runtime Principle You create users and user groups and assign authorizations to them. You configure objects with authorizations. After download to the HMI device, all objects which were configured with an authorization are protected against unauthorized access in Runtime. User view When you configure a user view in the Engineering System, you administer users in this user view following download to the HMI device. NOTICE Changes in the user view are effective immediately in Runtime. Changes in runtime are not updated in the engineering system. When downloading the user administration to the HMI device, all changes in the user view are overwritten after a security prompt and based on the settings. Users who have a "User administration" authorization have unlimited access to the user view. This allows them to administer all users. Any other user has only limited access to the user view for self administration. User view Purpose You configure a user view in the engineering system to also administer the users in Runtime. Structure The user view shows the following in each line: The user The corresponding user group. If no user is logged on, the user view is empty. The content of the individual fields is displayed after logon. WinCC Basic V13.0 System Manual, 02/2014 3477 Visualize processes 10.5 Configuring user administration User view of an administrator When an administrator is logged on, the user view shows all the users. The administrator changes the user name and the password. The administrator creates new users and assigns them to an existing user group. User view of a user When no administrator is logged on, the user view shows only the logged-on user. Users can change their own passwords. 3478 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.5 Configuring user administration User view Purpose You configure a user view in the engineering system to also administer the users in Runtime. Structure The user view shows the following in each line: The user The encrypted password The corresponding user group The logoff time If no user is logged on, the user view is empty. The content of the individual fields is displayed after logon. User view of an administrator When an administrator is logged on, the user view shows all the users. The administrator changes the user name and the password. The administrator creates new users and assigns them to an existing user group. User view of a user WinCC Basic V13.0 System Manual, 02/2014 3479 Visualize processes 10.5 Configuring user administration When no administrator is logged on, the user view shows only the logged-on user. Users can change their own passwords and logoff time. Configuring a user view Introduction You configure a user view in the Engineering System to also administer users in Runtime. Requirements A screen has been created. Procedure 1. Select the "User view" object from the "Controls" category in the toolbox. 2. Drag-and-drop the "User view" object into the screen. 3. Click on "Properties > Properties" in the Inspector window. 4. Specify the appearance of the "User view". 5. You can, for example, select " "Display mode > Fit to size > Fit object to contents". Result You have created a user view in the screen. Creating users Introduction You create a user so that users can log on under their user name in runtime. As an alternative, you can create users in the engineering system and download them to the HMI device. The logon is successful only when the user name entered during the logon matches a user in runtime. In addition, the password entered at logon has to match that of the user. Note Note that the entry is case-sensitive. 3480 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.5 Configuring user administration Note Do not use special characters such as / " $ % ? when you enter a user name and a password. ' &. You assign the user to a user group. The user then has the authorizations of the user group. Note Runtime users must be assigned to a user group. The user group is created in the engineering system. The designation of the user group is language-dependent. Requirements The user view is open. A "Group 2" user group has been created. Procedure 1. Click "<New User>" in the user view. A dialog opens. 2. Enter "Foreman" as the user name. 3. Press the <Return> button. 4. Click "Password." 5. Enter the password of the user. 6. Press the <Return> button. The password is hidden. 7. Click in the "Group" column. 8. Select "Group 2" as the "Group". 9. Press the <Return> button. 10.Click in the "Logoff time" column. 11.Enter the time after which the user is logged off automatically. WinCC Basic V13.0 System Manual, 02/2014 3481 Visualize processes 10.5 Configuring user administration Managing users in the user view Introduction If you have configured a user view in the engineering system, the users and user groups can be managed in runtime. NOTICE Changes in the user view are effective immediately in runtime. Changes in runtime are not updated in the engineering system. When downloading the user administration to the HMI device, all changes in the user view are overwritten after a security prompt and based on the settings. Requirements Runtime is enabled. A complex user view has been created. The screen with the user view is open. You have the default "User administration" authorization. Note If you do not have a "User administration" authorization, you can only change your own password and your logoff time. Changing the user name 1. Enter a new user name in the "Users" column in the user display. 2. Confirm your entry with <Return>. Note The user can then no longer log on with his previous password in runtime. If you delete the name and press <Return>, the user is deleted. 3482 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.5 Configuring user administration Changing the password of the user Availability of complex user display in selected devices only. 1. Enter a new password in the "Password" column in the user display. 2. Confirm your entry with <Return>. Note The user can then no longer log on with his previous password in runtime. If you delete the password in the complex user view and press <Return>, the user will be deleted. Changing the logoff time of the user 1. Enter a new logoff time in the "Logoff time" column in the user display. 2. Confirm your entry with <Return>. Deleting a user 1. Click the name of the user to be deleted. 2. Delete the name. 3. Press the <Return> button. Note The user can no longer log on in runtime. Assigning a user to a different user group 1. Activate the user group field for the corresponding user. 2. Select a user group. 3. Confirm your selection with <Return>. Unlocking users Unlock locked out users The check box "Activate limit for login attempts" is activated in the "Runtime settings > User administration". The number 3 is entered in the field "Number of invalid login attempts". If users have three failed attempts at login, e.g. by entering an incorrect password, they are assigned to the "Unauthorized" group. The user loses all authorizations. The user can still log on, but no longer has any authorizations. Only a user with administrator rights re-assigns the unauthorized user to a user group. WinCC Basic V13.0 System Manual, 02/2014 3483 Visualize processes 10.5 Configuring user administration Logging on as a user Introduction As a rule you log-on as a user by means of a special button. The logon dialog box is displayed to this purpose. The logon dialog box is displayed by default during access to a protected object if No user is logged on in runtime. The logged-on user does not have the required authorization. Note The system always opens the logon dialog on the OP 73, OP 77A, TP 177A and Basic Panels HMI devices when you press an access-protected button: Requirements Under "Runtime settings > User administration" the - "Enable limit for logon attempts" check box has been selected. - The number 3 is entered in the field "Number of incorrect login attempts". The "ShowLogonDialog" system function is configured on a button called "Logon". Procedure 1. Click the "Logon" button. The logon dialog box is displayed. 2. Enter your user name as it was specified in the user administration, for example "Foreman". If someone has logged on before you, the name of the user will be displayed. 3. Enter the corresponding password. The input is concealed. 4. Click "OK" to close the dialog box. 3484 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.5 Configuring user administration Logon was successful If you have entered the user name "Foreman" and the entered password corresponds with the stored password, you are logged on as the user "Foreman" in runtime. You have the authorizations of the user "Foreman". When the user "Foreman" accesses a protected object such as the "Logging" button, access to this protected object will only be authorized if the user "Foreman" has the required authorization. The programmed function is executed immediately. If you do not have the required authorization after the successful log-on, a corresponding error message is displayed. However, you remain logged on in runtime. Logon was unsuccessful An error message is displayed. In order to maintain security, you or the user logged-on before you no longer has any authorizations. However, access to unprotected objects remains possible. The user view does not, however, show any entries. The user view and the authorizations change after the next successful log-on. If the third login attempt has failed, the user will be assigned to the "Unauthorized" group. For this reason, do not configure a user group with this display name. If the "Log off" function is called up or the logoff time of the user has expired, the user is logged off. 10.5.4.4 Configuring access protection Access protection Introduction You configure an authorization at an object in order to protect it against access. All logged-on users who have this authorization can then access the object. If a user does not have authorization to operate an object, the logon dialog is displayed automatically. Note Several system functions are available under "User administration" so that user, password, and user group can be edited, for example, in the PLC. Configuring authorization (Basic,Advanced; Professional) Introduction You configure the "Stop runtime" authorization on a button. Then only those users who have the appropriate authorization have access to this button, for example all the users of the "Operators" user group. WinCC Basic V13.0 System Manual, 02/2014 3485 Visualize processes 10.5 Configuring user administration This ensures that access to the command button is protected. If a logged-on user who belongs to the "Operators" user group and has the required authorizations clicks the button, runtime is stopped. An example describes in detail how to configure a command button with access protection. Requirements The "Operators" user group has been created. The "Stop runtime" authorization has been created. A screen has been created and opened. The screen contains a button. Procedure 1. Click the button in the screen. 2. Click "Properties > Properties > Security" in the Inspector window. 3. Select "Stop runtime" as the "Authorization". 4. In the Inspector window, select "Properties > Events > Click". 5. Select a system function from the function list, for example, "StopRuntime". Note The "Enable" and "Disable" events are only used to detect whether an object was selected or deselected. The events do not, however, trigger a password prompt. Do not use the "Enable"or "Disable" event if you want to configure access protection at the function call of the object. 10.5.5 Reference 10.5.5.1 Objects with access protection Introduction The following objects can be configured with an authorization: Date/time field I/O field Graphic I/O field Recipe view Switch 3486 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.5 Configuring user administration Button Symbolic I/O field System diagnostic view 10.5.5.2 Default user groups and authorizations Principle The predefined user groups and authorizations have the following numbers: User group Number "Administrator group" 1 "Users" 2 Authorization Number "User administration" 1 "Monitor" 2 "Operate" 3 10.5.6 Examples 10.5.6.1 Example: Configuring a button with logon dialog box Task In the following example, you configure the function "ShowLogonDialog" for a button. A different user can then log on in runtime when the shift changes, for example. In the process the user previously logged on is logged off. Note In runtime the logon dialog box is not displayed by default until you access a protected object. Either no user is logged on or the logged-on user does not have the required authorization. Requirements A screen has been created. A button has been created in the screen. WinCC Basic V13.0 System Manual, 02/2014 3487 Visualize processes 10.5 Configuring user administration Procedure 1. Click the button in the screen. 2. Click "Properties > Events > Release" in the Inspector window. 3. Click the entry "Add function" in the "Function list" table. 4. Select the system function "ShowLogonDialog" from the "User administration" group. Result If the user clicks on the button in runtime, the function "ShowLogonDialog" is called up. When the function "ShowLogonDialog" is called up, the logon dialog box is displayed. The user logs on with his user name and password. 10.5.6.2 Example: Logging the logon and logoff events Task In the following example, you configure the function "TraceUserChange" to the event "User change". Principle The "TraceUserChange" function is called when a user logs on or off. When a function is called up, a system message with information about the corresponding user is output. This system message can be archived. When archiving, the system message is provided with a date stamp and time stamp. This ensures that you can track which user was logged on at the HMI device at which time and for how long. 3488 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.5 Configuring user administration Requirements You have created an HMI device with Runtime Advanced. The Inspector window is open. Procedure 1. Double-click the "Scheduler" in the Project view. 2. Double-click "Add" in the table of the tasks. 3. Enter "Logon-Protocol" as the "Name". 4. Select "User change" as the "Trigger". 5. Open "Properties > Events" in the Inspector window. 6. Click the entry "Add function" in the "Function list" table. 7. Select the "TraceUserChange" system function. Result A system message is output when a user logs on or logs off. 10.5.6.3 Example of user management Example: Structure of user management Task In the following example you set up a user administration for different users and user groups. The example orientates itself to a typical requirement profile from manufacturing engineering. Principle Completely different groups of persons are involved in a plant or project. Each group of persons protects its respective data and functions against access by others. For this purpose, users are created and assigned to a user group. You can reproduce different views through user groups. Example: Organizational view: Commissioners, Operators, Shift I, Shift II Technological view: Axis control, Tool changers, Plant North, Plant South The following example orientates itself to the organizational view. Every user group has characteristic requirements regarding access protection: A user group has operating authorizations for specific application cases. A programmer changes, for example, recipe data records. WinCC Basic V13.0 System Manual, 02/2014 3489 Visualize processes 10.5 Configuring user administration In the example the users Miller, Group Smith and Foreman are created and assigned to different user groups. Ms. Miller works as a programmer in the engineering system. The Group Smith are commissioners. Mr. Foreman is an operator. Requirements A new project has been created. The "User administration" editor is open. Procedures overview Working with user administration has the following procedure in the example: 1. Creating authorizations The planner specifies which authorizations are required for access protection. 2. Configuring authorizations: The planner specifies which objects may be operated and which functions may be executed. 3. Creating user groups and allocating authorizations: The administrator creates the user groups together with the planner. The planner uses the authorizations to specify who may operate objects and change parameters. 4. Creating users and assigning them to a user group: The administrator administers the users. Result The aim is the following structure of the user administration of users, user groups and authorizations: Users Miller Smith Foreman User groups Authorizations Roles Changing recipe records Changing system parameters Changing process parameters Administrator group X X X Managing x Programmer X Commissioning engineers X Operators x X X The user "Foreman" who belongs to the "Operators" user group has access to the configured "To Recipe view" button. Note Alternatively, you can create several users as operators with different operating authorizations, for example, Operator Level 1, Operator Level 2. 3490 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.5 Configuring user administration Example: Creating and configuring authorizations Task The following example shows you how to create the authorizations Procedure 1. Open the "User groups" work area. 2. Double-click "Add" in the "Authorizations" table. 3. Enter "Change recipe data records" as the "Name" of the authorization. 4. Repeat steps 2 and 3 to create additional authorizations: "Change system parameters", "Change process parameters". Result Example: Configuring a button with access protection Task In the following example you use a system function to create a button for a screen change. You protect the "To Recipe view" button against unauthorized operation. To do so, you configure the "Change recipe data records" authorization at the "To Recipe view" button. WinCC Basic V13.0 System Manual, 02/2014 3491 Visualize processes 10.5 Configuring user administration Requirements A "Change recipe data records" authorization has been created. A "Recipes" screen has been created. A "Start" screen has been created and opened. A button has been created and marked in the "Start" screen. Procedure 1. Click "Properties > Properties > General" in the Inspector window. 2. Enter "To Recipe view" as the text. 3. Click "Properties > Events > Click" in the Inspector window. 4. Click the "Add function" entry in the first line of the "Function list" table. 5. Select the "ActivateScreen" system function in the "Screens" group. 6. Click the button in the "Screen name" field. A dialog box for selecting the screen opens. 7. Select the "Recipes" screen and use the button to close the dialog box. 8. Click "Properties > Properties > Security" in the Inspector window. 9. Select "Change recipe data records" as the "Authorization." Result Access to the "To Recipe view" button is protected. If, for example, the user "Smith" clicks the button in Runtime, the function "Recipe view" screen is called up. Prerequisite is that the user 3492 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.5 Configuring user administration "Smith" has logged on correctly and has the required authorization. The "Recipes" screen contains a recipe view and other screen objects. If the logged-on user does not have the required authorization or if no user is logged on, the "Logon dialog box" is displayed. Example: Creating user groups and assigning authorizations: Task In the following example you create the user groups and assign authorizations to them. Procedure 1. Open the "User groups" work area. 2. Double-click "Add" in the "Groups" table. 3. Enter "Programmer" as the "Name". 4. Repeat steps 2 and 3 to create the "Commissioner" and "Operator" user groups. 5. Click "Administrator" in the "Groups" table. 6. Activate the "Change system parameters" authorization in the "Authorizations" table. Interim result WinCC Basic V13.0 System Manual, 02/2014 3493 Visualize processes 10.5 Configuring user administration Procedure 1. Click "Operator" in the "Groups" table. 2. Activate the "Change recipe data records" authorization in the "Authorizations" table. 3. Click "Commissioner" in the "Groups" table. 4. Activate the authorizations "Change recipe data records", "Change system parameters" and "Change process parameters" in the "Authorizations" table. 5. Click "Programmer" in the "Groups" table. 6. Activate the "Change recipe data records" authorization in the "Authorizations" table. Result Example: Creating users and assigning them to a user group Task In the following example you create the users and assign user groups to them. The users are sorted alphabetically immediately after the name has been entered. Procedure 1. Open the "Users" work area. 2. Double-click "Add" in the "Users" table. 3494 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.5 Configuring user administration 3. Enter "Miller" as the user name. 4. Click the button in the "Password" column. The dialog box for entering the password is displayed. 5. Enter "miller" as the password. 6. To confirm the password enter it a second time in the lower field. 7. Close the dialog box by using the icon. 8. Activate the "Programmer" user group in the "Groups" table. Interim result Procedure 1. Double-click "Add" in the "Users" table. 2. Enter "Smith" as the user name. 3. Click the button in the "Password" column. The dialog box for entering the password is displayed. 4. Enter "smith" as the password. 5. To confirm the password enter it a second time in the lower field. 6. Close the dialog box by using the icon. 7. Activate the "Commissioner" user group in the "Groups" table. 8. Repeat steps 2 to 6 for the user "Foreman." 9. Activate the "Operators" user group in the "Groups" table. WinCC Basic V13.0 System Manual, 02/2014 3495 Visualize processes 10.6 Working with system functions Result 10.6 Working with system functions 10.6.1 Basics 10.6.1.1 System functions Introduction System functions are functions supplied by WinCC. They are predefined and cannot be changed. You can use system functions to implement many tasks in Runtime even without having any programming knowledge, for example: 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. changing the PLC or setting a bit in the PLC. Alarms, e.g after a different user logs on. 3496 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.6 Working with system functions Usage You use system functions in a function list. When configuring a function list, you select the system functions from a selection list that is sorted by categories: Each system function in WinCC is logically linked with an object and an event. As soon as the event occurs, the system function is triggered. Language dependency The names of the system functions are dependent on the set project language. The functionality can then be recognized immediately by the project planner. Availability You only configure system functions within a function list which are supported by the selected HMI device. If you use a project for several HMI devices, the system functions that are not supported by an HMI device are marked in color. Events The object and the selected function determine which events can be defined as triggers for executing a system function. For example, the "Change value", "Low limit violated" and "Upper limit exceeded" events are associated with the "Tag" object. The "Loaded" and "Cleared" events are associated with the "Screen" object. WinCC Basic V13.0 System Manual, 02/2014 3497 Visualize processes 10.6 Working with system functions 10.6.1.2 Use of system functions Introduction A function list is processed when a configured event occurs in runtime. The operator can trigger an event, for example, by pressing a function key on the HMI device. The system could also trigger an event if a process value falls below a specified limit, for example. Applications You can configure system functions on all the objects that are able to react to an event. You can use system functions directly in function lists and thereby control the sequence. Function list The system functions will be processed one line at a time in a function list. To avoid wait times, system functions in WinCC Runtime with a longer running time are executed simultaneously. For instance, a subsequent system function can already be performed even though the previous system function has not yet been completed. An example for the configuration of a function list can be found under "Changing the operating mode on the HMI device with the current display". 10.6.2 Working with function lists 10.6.2.1 Basic of the functions list Introduction When the configured event occurs, several system functions can be performed with the function list. 3498 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.6 Working with system functions Principle The function list is configured for an event of an object, e.g. a screen object or a tag. The events which are available depend on the selected object and the HMI device. Events occur only when the project is in Runtime. Events include: Value changes of a tag Pressing of a button Activation of Runtime You can configure exactly one function list for each event. Note The choice of configurable system functions in a function list depends on the HMI device chosen. 10.6.2.2 Properties of a function list Status information During configuration the project data is tested in the background. With the following causes the function list is not executed in Runtime and the incorrect entries are marked red: At least one system function is not completely supplied with parameters. At least one system function is contained which is not supported by the selected HMI device, for example, by changing the device type. WinCC Basic V13.0 System Manual, 02/2014 3499 Visualize processes 10.6 Working with system functions Executing system functions System functions in a function list are executed in runtime sequentially from top to bottom. To avoid wait times, system functions with a longer running time (such as file operations) are processed simultaneously. For instance, a subsequent system function can already be performed even though the previous system function has not yet been completed. Use a script with loops, conditional statements and abort conditions to program non-sequential and conditional procedures. Note Availability for specific devices User-defined functions are not available on Basic Panels. 10.6.2.3 Configuring a function list Introduction You can configure a function list by selecting system functions from a drop-down list. The system functions are arranged in the drop-down list according to categories. Requirement Object has at least one configurable event. Procedure Proceed as follows to configure a function list: 1. Open the editor in WinCC in which the object is located. 2. Select the object. 3. Click "Properties > Events" in the Inspector window. Select the event for which you want to configure the function list. 4. Select the "<No Function>" entry in the drop-down list of the Inspector window. 5. Select the desired system function. 3500 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.6 Working with system functions 6. You can also enter the name of the system function. The system function is entered in the function list. 7. If the system function has parameters, specify the values for the parameters. 8. If you want to add other system functions or functions to the function list, then repeat steps four to seven. Result The function list is configured. In addition, to the configured event, the status of the function list is displayed in the Inspector window. When the configured event occurs in Runtime, the function list is completed from top to bottom. WinCC Basic V13.0 System Manual, 02/2014 3501 Visualize processes 10.6 Working with system functions 10.6.2.4 Editing a function list Introduction A function list can be edited as follows: Changing the order of execution for system functions Removing a system function For additional information, refer to "Configuring a function list". Requirement The function list is configured. Changing the order of a system function 1. Select the desired system function in the function list. 2. Then click the appropriate direction arrow in the inspector window until the system function or customized function is in the desired position. Changing the order of several system functions 1. Hold down the <Shift> key. 2. Click the relevant system functions, working in succession. 3. Move the selection to the desired position by drag&drop. Removing a system function 1. Select the desired system function in the function list. 2. Select "Delete" from the shortcut menu. 3502 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.6 Working with system functions 10.6.2.5 Executing a function list in Runtime Principle A function list is executed from top to bottom in Runtime. A distinction is made between synchronous and asynchronous execution, so that no waiting periods ensue during execution. The distinction is made by the system by evaluating the different runtimes of the system functions. User-defined functions are always executed synchronously independent of the runtime. If a system function returns an error status, the execution of the function list is cancelled. Synchronous execution During synchronous execution, the system functions in a function list are executed one after the other. The previous system function must be finished before the next system function can be executed. Asynchronous execution System functions that perform file operations such as saving and reading have a longer runtime than system functions that, for example, set a tag value. Therefore, system functions with longer runtimes are executed asynchronously. For example, while a system function is writing a recipe data record to a storage medium, the next system function is already being executed. Due to the parallel execution of system functions, waiting periods at the HMI device are avoided. 10.6.3 Example 10.6.3.1 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: WinCC Basic V13.0 System Manual, 02/2014 3503 Visualize processes 10.6 Working with system functions Name PLC connection Type OperatingMode No Bool Name Contains Values ShowOperatingMode Bit (0/1) 1: Operating mode: "Online" Text list: 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. 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". 3504 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.6 Working with system functions 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. 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". WinCC Basic V13.0 System Manual, 02/2014 3505 Visualize processes 10.6 Working with system functions Result When you change the operating mode with the buttons, the currently set operating mode on the HMI device is always shown. 10.6.4 Reference 10.6.4.1 Function list Device-based dependency of system functions Availability of system functions The following table shows the availability of system functions and user-defined functions on the HMI devices. Technical data subject to change. Overview KP300 Basic PN KTP400 Basic PN KTP 600 Basic DP KTP 600 Basic PN KTP KTP TP 1500 1000 1000 Basic Basic DP Basic PN PN User-defined functions No No No No No No No Logoff (Page 3509) Yes Yes Yes Yes Yes Yes Yes AdjustContrast (Page 3509) Yes Yes No Yes Yes Yes Yes ActivateScreen (Page 3510) Yes Yes Yes Yes Yes Yes Yes ActivateScreenByNumber (Page 3511) Yes Yes Yes Yes Yes Yes Yes ActivateCleanScreen (Page 3512) No Yes Yes Yes Yes Yes Yes ActivatePreviousScreen (Page 3513) Yes Yes Yes Yes Yes Yes Yes UpdateTag (Page 3514) Yes Yes Yes Yes Yes Yes Yes Logon (Page 3514) Yes Yes Yes Yes Yes Yes Yes EditAlarm (Page 3515) Yes Yes Yes Yes Yes Yes No ScreenObjectCursorDown (Page 3516) Yes Yes Yes Yes Yes Yes Yes ScreenObjectCursorUp (Page 3516) 1) Yes Yes Yes Yes Yes Yes Yes ScreenObjectPageDown (Page 3517) Yes Yes Yes Yes Yes Yes Yes ScreenObjectPageUp (Page 3517) Yes Yes Yes Yes Yes Yes Yes IncreaseFocusedValue (Page 3518) Yes Yes Yes Yes Yes Yes No IncreaseTag (Page 3519) Yes Yes Yes Yes Yes Yes Yes GoToHome (Page 3519) Yes Yes Yes Yes Yes Yes No GoToEnd (Page 3520) Yes Yes Yes Yes Yes Yes No 3506 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.6 Working with system functions InvertBit (Page 3521) KP300 Basic PN KTP400 Basic PN KTP 600 Basic DP KTP 600 Basic PN KTP KTP TP 1500 1000 1000 Basic Basic DP Basic PN PN Yes Yes Yes Yes Yes Yes Yes InvertBitInTag (Page 3522) Yes Yes Yes Yes Yes Yes Yes InvertLinearScaling (Page 3523) Yes Yes Yes Yes Yes Yes Yes CalibrateTouchScreen (Page 3524) Yes Yes Yes Yes Yes Yes Yes TrendViewScrollForward (Page 3525) Yes Yes Yes Yes Yes Yes Yes TrendViewScrollBack (Page 3526) Yes Yes Yes Yes Yes Yes Yes TrendViewExtend (Page 3526) Yes Yes Yes Yes Yes Yes Yes TrendViewCompress (Page 3527) Yes Yes Yes Yes Yes Yes Yes TrendViewRulerRight (Page 3528) Yes Yes Yes Yes Yes Yes Yes TrendViewRulerLeft (Page 3527) Yes Yes Yes Yes Yes Yes Yes TrendViewSetRulerMode (Page 3528) Yes Yes Yes Yes Yes Yes Yes TrendViewStartStop (Page 3529) Yes Yes Yes Yes Yes Yes Yes TrendViewBackToBeginning (Page 3529) Yes Yes Yes Yes Yes Yes Yes GetUserName (Page 3530) Yes Yes Yes Yes Yes Yes Yes GetGroupNumber (Page 3531) Yes Yes Yes Yes Yes Yes Yes GetPassword (Page 3531) Yes Yes Yes Yes Yes Yes Yes LinearScaling (Page 3533) Yes Yes Yes Yes Yes Yes Yes ClearAlarmBuffer (Page 3534) Yes Yes Yes Yes Yes Yes Yes ClearAlarmBufferProTool (Page 3535) Yes Yes Yes Yes Yes Yes Yes AlarmViewEditAlarm (Page 3536) Yes Yes Yes Yes Yes Yes Yes AlarmViewAcknowledgeAlarm (Page 3537) Yes Yes Yes Yes Yes Yes Yes AlarmViewShowOperatorNotes (Page 3537) Yes Yes Yes Yes Yes Yes Yes AcknowledgeAlarm (Page 3538) Yes Yes Yes Yes Yes Yes Yes RecipeViewNewDataRecord (Page 3539) Yes Yes Yes Yes Yes Yes Yes RecipeViewGetDataRecordFromPLC Yes (Page 3539) Yes Yes Yes Yes Yes Yes RecipeViewClearDataRecord (Page 3539) Yes Yes Yes Yes Yes Yes Yes RecipeViewMenu (Page 3540) Yes Yes Yes Yes Yes Yes Yes RecipeViewOpen (Page 3540) Yes Yes Yes Yes Yes Yes Yes RecipeViewSetDataRecordToPLC (Page 3541) Yes Yes Yes Yes Yes Yes Yes RecipeViewSaveDataRecord (Page 3542) Yes Yes Yes Yes Yes Yes Yes RecipeViewSaveAsDataRecord (Page 3542) Yes Yes Yes Yes Yes Yes Yes WinCC Basic V13.0 System Manual, 02/2014 3507 Visualize processes 10.6 Working with system functions KP300 Basic PN KTP400 Basic PN KTP 600 Basic DP KTP 600 Basic PN KTP KTP TP 1500 1000 1000 Basic Basic DP Basic PN PN RecipeViewRenameDataRecord (Page 3542) Yes Yes Yes Yes Yes Yes Yes RecipeViewShowOperatorNotes (Page 3543) Yes Yes Yes Yes Yes Yes Yes RecipeViewBack (Page 3543) Yes Yes Yes Yes Yes Yes Yes ResetBit (Page 3544) Yes Yes Yes Yes Yes Yes Yes ResetBitInTag (Page 3545) Yes Yes Yes Yes Yes Yes Yes PressButton (Page 3546) Yes Yes Yes Yes Yes Yes No ReleaseButton (Page 3547) Yes Yes Yes Yes Yes Yes No ShiftAndMask (Page 3548) Yes Yes Yes Yes Yes Yes Yes PageDown (Page 3550) Yes Yes Yes Yes Yes Yes No PageUp (Page 3549) Yes Yes Yes Yes Yes Yes No SetDeviceMode (Page 3550) Yes Yes Yes Yes Yes Yes Yes SetBit (Page 3551) Yes Yes Yes Yes Yes Yes Yes SetBitInTag (Page 3552) Yes Yes Yes Yes Yes Yes Yes SetBitWhileKeyPressed (Page 3554) Yes Yes Yes Yes Yes Yes Yes SetBacklightColor (Page 3555) Yes No No No No No No SetLanguage (Page 3557) Yes Yes Yes Yes Yes Yes Yes SetTag (Page 3558) Yes Yes Yes Yes Yes Yes Yes SetConnectionMode (Page 3559) Yes Yes Yes Yes Yes Yes Yes SimulateSystemKey (Page 3561) Yes Yes Yes Yes Yes Yes No SimulateTag (Page 3562) Yes Yes Yes Yes Yes Yes Yes StopRuntime (Page 3563) Yes Yes Yes Yes Yes Yes Yes TraceUserChange (Page 3564) Yes Yes Yes Yes Yes Yes Yes DecreaseFocusedValue (Page 3564) Yes Yes Yes Yes Yes Yes No DecreaseTag (Page 3565) Yes Yes Yes Yes Yes Yes Yes ChangeConnection (Page 3565) Yes Yes Yes Yes Yes Yes Yes ShowLogonDialog (Page 3567) Yes Yes Yes Yes Yes Yes Yes ShowOperatorNotes (Page 3568) Yes Yes Yes Yes Yes Yes Yes ShowAlarmWindow (Page 3569) Yes Yes Yes Yes Yes Yes Yes 1) 3508 For KTP600 Basic mono PN only. WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.6 Working with system functions System functions Logoff Description Logs off the current user on the HMI device. Use in the function list Logoff Use in user-defined functions Logoff Can be used if the configured device supports user-defined functions. For additional information, refer to "Device dependency". Parameter -- See also Device-based dependency of system functions (Page 3506) Logon (Page 3514) AdjustContrast Description Changes the contrast of the display one level on the HMI device. Use in the function list AdjustContrast (Adjust) Use in user-defined functions - WinCC Basic V13.0 System Manual, 02/2014 3509 Visualize processes 10.6 Working with system functions Parameters Adjust Specifies how the contrast is changed: 0 (hmiDecrease) = Decrease: Decreases the contrast one level. 1 (hmiIncrease) = Increase: Increases the contrast one level. Application example Objective One button each for increasing and decreasing the screen contrast is desired. Notes on configuring Configure two buttons and configure the "AdjustContrast" system function on the "Press" event. The parameters "Increase" and "Decrease" are allocated. Procedure on HMI device When one of the two buttons is pressed in runtime, the contrast is increased or decreased one level. See also Device-based dependency of system functions (Page 3506) Logoff (Page 3509) ActivateScreen Description Performs a screen change to the given screen. Use the "ActivateScreenByNumber" system function to change from the root screen to the permanent window or vice versa. Use in the function list ActivateScreen (Screen name, Object number) Use in user-defined functions ActivateScreen (Screen_name, Object_number) Can be used if the configured device supports user-defined functions. For additional information, refer to "Device dependency". 3510 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.6 Working with system functions 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. Example The ActivateScreen function is used in the following program code to activate the "Screen_2" screen when you click a button. { // User defined code // i.e. when pressing a button ActivateScreen ("Screen_2", 0); ... } See also Device-based dependency of system functions (Page 3506) ActivateScreenByNumber (Page 3511) ActivateScreenByNumber Description Performs a screen change to a screen depending on a tag value. WinCC Basic V13.0 System Manual, 02/2014 3511 Visualize processes 10.6 Working with system functions The screen is identified by its screen number. Use in the function list ActivateScreenByNumber (Screen number, Object number) Use in user-defined functions ActivateScreenByNumber (Screen_number, Object_number) Can be used if the configured device supports user-defined functions. For additional information, refer to "Device dependency". Parameter Screen number Tag which contains the screen number of the destination screen. When a change from the root screen to the permanent window is desired, "0" or "-1" is specified: 0 = Change from root screen to permanent window -1 = Change from permanent window to root screen Object number The number of the screen object which receives the focus in the given screen after the screen change. The number of the operator control element is to be determined using the tabulator sequence during configuration. When "0" is specified: If the focus is in the permanent window when the system function is called up, the permanent window maintains the focus. If the focus is in the root screen when the system function is called up, the first operator control element in the given screen receives the focus. See also Device-based dependency of system functions (Page 3506) ActivateScreen (Page 3510) ActivateCleanScreen Description Activates the clean screen on the HMI device. The display of the HMI device is disabled for the given time period. When the display of the HMI device is deactivated, it can be cleaned without triggering touch functions by mistake. 3512 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.6 Working with system functions Use in the function list ActivateCleanScreen (Time period) Use in user-defined functions -- Parameters Time period Time period for which the display is disabled. The time remaining is displayed as a progress bar. Value range in seconds from 10 through 300. Note The system function ActivateCleanScreen cannot be simulated. See also Logoff (Page 3509) ActivatePreviousScreen Description Performs a screen change to the screen which was activated before the current screen. The screen change is not performed if no screen was activated beforehand. The last 10 screens that were called up are saved. A system alarm is output when you change to a screen which is no longer saved. Note If you want to use the system function, the screen to which you change has to be used in the navigation structure. Use in the function list ActivatePreviousScreen WinCC Basic V13.0 System Manual, 02/2014 3513 Visualize processes 10.6 Working with system functions Use in user-defined functions ActivatePreviousScreen Can be used if the configured device supports user-defined functions. For additional information, refer to "Device dependency". Parameter -- See also Device-based dependency of system functions (Page 3506) UpdateTag Description Reads the current value of the tag with the specified Update ID from the PLC. Use in the function list UpdateTag (Update ID) Use in user-defined functions - Parameters Update ID Update ID assigned to the tag that will be updated. See also Logoff (Page 3509) Logon Description Logs on the current user on the HMI device. 3514 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.6 Working with system functions Use in the function list Logon (Password, User name) Use in user-defined functions Logon (Password, User_name) Can be used if the configured device supports user-defined functions. For additional information, refer to "Device dependency". Parameter Password The tag from which the password for the user logging on is read. If the user is logged on, the password in the tag is deleted. User name The tag from which the user name for the user logging on is read. See also Device-based dependency of system functions (Page 3506) Logoff (Page 3509) EditAlarm Description Triggers the "Edit" event for all selected alarms. If the alarms to be edited have not yet been acknowledged, the acknowledgment takes place automatically when this system function is called up. This system function can only be used for function keys. Use in the function list EditAlarm Use in user-defined functions EditAlarm Can be used if the configured device supports user-defined functions. For additional information, refer to "Device dependency". WinCC Basic V13.0 System Manual, 02/2014 3515 Visualize processes 10.6 Working with system functions Parameter -- See also Device-based dependency of system functions (Page 3506) ScreenObjectCursorUp Description Results in a line-by-line, upward cursor movement in the specified screen object. The system function can be used for the following screen objects: User view Alarm view Recipe view Use in the function list ScreenObjectCursorUp (Screen object) Use in user-defined functions - Parameters Screen object Name of the screen object in which the key function is triggered. ScreenObjectCursorDown Description Results in a line-by-line, downward cursor movement in the specified screen object. The system function can be used for the following screen objects: User view Alarm view Recipe view 3516 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.6 Working with system functions Use in the function list ScreenObjectCursorDown (Screen object) Use in user-defined functions - Parameters Screen object Name of the screen object in which the key function is triggered. ScreenObjectPageUp Description Results in a page-by-page, upward cursor movement in the specified screen object. The system function can be used for the following screen objects: User view Alarm view Recipe view Use in the function list ScreenObjectPageUp (Screen object) Use in user-defined functions - Parameters Screen object Name of the screen object in which the key function is triggered. ScreenObjectPageDown Description Results in a page-by-page, downward cursor movement in the specified screen object. The system function can be used for the following screen objects: WinCC Basic V13.0 System Manual, 02/2014 3517 Visualize processes 10.6 Working with system functions User view Alarm view Recipe view Use in the function list ScreenObjectPageDown (Screen object) Use in user-defined functions - Parameters Screen object Name of the screen object in which the key function is triggered. IncreaseFocusedValue Description Adds the given value to the value of the tag which is connected to the input field (drop-down list, graphic selection list, slider bar) which has the current focus. This system function can only be used for function keys. Use in the function list IncreaseFocusedValue (Value) Use in user-defined functions - Parameters Value The value which is added to the tag value. See also Device-based dependency of system functions (Page 3506) 3518 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.6 Working with system functions IncreaseTag Description Adds the given value to the value of the tags. X=X+a Note The system function uses the same tag as input and output values. When this system function is used to convert a value, help tags must be used. You can use the "SetTag" system function to assign the tag value to the auxiliary tags. If you configure the system function on the events of an alarm and the tag is not being used in the current screen, it is not ensured that the actual value of the tags is being used in the PLC. You can improve the situation by setting the "Cyclic continuous" acquisition mode. Use in the function list IncreaseTag (Tag, Value) Use in user-defined functions IncreaseTag (Tag, Value) Can be used if the configured device supports user-defined functions. For additional information, refer to "Device dependency". Parameter Tag The tag to which the given value is added. Value The value that is added. See also Device-based dependency of system functions (Page 3506) SetTag (Page 3558) GoToHome Description Executes the key function <Home> on the HMI device. WinCC Basic V13.0 System Manual, 02/2014 3519 Visualize processes 10.6 Working with system functions This system function is used when the HMI device does not have this functionality by default. The system function can only be used for the following function keys. Use in the function list GoToHome Use in user-defined functions GoToHome Can be used if the configured device supports user-defined functions. For additional information, refer to "Device dependency". Parameter -- See also Device-based dependency of system functions (Page 3506) GoToEnd Description Executes the key function <End> on the HMI device. This system function is used when the HMI device does not have this functionality by default. The system function can only be used for the following function keys. Use in the function list GoToEnd Use in user-defined functions GoToEnd Can be used if the configured device supports user-defined functions. For additional information, refer to "Device dependency". Parameter -- 3520 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.6 Working with system functions See also Device-based dependency of system functions (Page 3506) InvertBit Description Inverts the value of the given tag of the "Bool" type: If the tag has the value of 1 (TRUE), it will be set to 0 (FALSE). If the tag has the value of 0 (FALSE), it will be set to 1 (TRUE). Use in the function list InvertBit (Tag) Use in user-defined functions InvertBit (Tag) Can be used if the configured device supports user-defined functions. For additional information, refer to "Device dependency". Parameters Tag The tag whose bit is set. Example The following program code inverts the value of the boolean tag b_value and outputs the result along with the original b_saved value. { BOOL b_value = 0; BOOL b_saved = b_value; //Invert variable invertBit(b_value); //print current and saved value printf ("Current value: %d\r\n, Saved value: %d\r\n",b_value, b_saved); ... } WinCC Basic V13.0 System Manual, 02/2014 3521 Visualize processes 10.6 Working with system functions See also Device-based dependency of system functions (Page 3506) InvertBitInTag (Page 3522) 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. For additional information, refer to "Device dependency". 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. 3522 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.6 Working with system functions Example The following program code inverts a bit at the specified bitposition in the bvalue tag and outputs the result along with the original bsaved value. { BYTE bvalue; BYTE bsaved = bvalue; BYTE bitposition = 2; //Invert bit in bitposition InvertBitInTag (bvalue, bitposition); //print current and saved value printf ("Current value: %d\r\n, Saved value: %d\r\n",bvalue, bsaved); ... } See also Device-based dependency of system functions (Page 3506) InvertBit (Page 3521) InvertLinearScaling Description Assigns a value to the tag X, which is calculated from the value of the given tag Y using the linear function X = (Y - b) / a. The tags X and Y must not be identical. This system function is the inverse of the "LinearScaling" system function. Note The tags X and Y must not be identical. If a tag is to be converted into itself, a auxiliary tag must be used. The "SetTag" system function can be used to assign the value of the tags to be converted to the auxiliary tags. Use in the function list InvertLinearScaling (X, Y, b, a) Use in user-defined functions InverseLinearScaling (X, Y, b, a) WinCC Basic V13.0 System Manual, 02/2014 3523 Visualize processes 10.6 Working with system functions Can be used if the configured device supports user-defined functions. For additional information, refer to "Device dependency". Parameters X The tag which is assigned the value calculated from the linear equation. Y The tag that contains the value used for calculation. b The value which is subtracted. a The value through which is divided. Example The following program code assigns a value to the varX tag by means of the InverseLinearScaling function. { BYTE BYTE BYTE BYTE varX; Yvalue = 10; bvalue = 3; avalue = 4; //Inverse linear scaling InverseLinearScaling (varX, Yvalue, bvalue, avalue); printf ("varX = %d\r\n, varX); ... } The saved return value can be processed in the following code. See also Device-based dependency of system functions (Page 3506) LinearScaling (Page 3533) CalibrateTouchScreen Description Calls a program for calibrating the touch screen. 3524 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.6 Working with system functions During the calibration process, there is a prompt to touch five positions on the screen display. Touch the screen display within 30 seconds, to confirm the calibration process. If the calibration is not completed within this time span, the calibration settings are discarded. The user prompt is in English. Use this system function the first time you start the HMI device. Use in the function list CalibrateTouchScreen Use in user-defined functions CalibrateTouchScreen Can be used if the configured device supports user-defined functions. For additional information, refer to "Device dependency". Parameter -Note The CalibrateTouchScreen system function cannot be simulated. See also Device-based dependency of system functions (Page 3506) TrendViewScrollForward Description Scrolls forward one display width in the Trend view. Use in the function list TrendViewScrollForward (Screen object) Use in user-defined functions - WinCC Basic V13.0 System Manual, 02/2014 3525 Visualize processes 10.6 Working with system functions Parameters Screen object Name of the trend view in which is scrolled forward. TrendViewScrollBack Description Scrolls back one display width to the left in the trend view. Use in the function list TrendViewScrollBack (Screen object) Use in user-defined functions - Parameters Screen object Name of the trend view in which is scrolled back. TrendViewExtend Description Reduces the time period which is displayed in the trend view. Use in the function list TrendViewExtend (Screen object) Use in user-defined functions - Parameters Screen object Name of the trend view in which the displayed time period is reduced. 3526 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.6 Working with system functions TrendViewCompress Description Increases the time period which is displayed in the trend view. Use in the function list TrendViewCompress (Screen object) Use in user-defined functions - Parameters Screen object Name of the trend view in which the displayed time period is increased. TrendViewRulerLeft Description Moves the read-line backwards (to the left) in the trend view. Note In order to be able to move the read-line, the read-line must have been switched on. This is done using the "TrendViewSetRulerMode" system function. Use in the function list TrendViewRulerLeft (Screen object) Use in user-defined functions - Parameters Screen object Name of the trend view in which the read-line is moved backwards. WinCC Basic V13.0 System Manual, 02/2014 3527 Visualize processes 10.6 Working with system functions See also TrendViewSetRulerMode (Page 3528) TrendViewRulerRight Description Moves the read-line forwards (to the right) in the trend view. Note In order to be able to move the read-line, the read-line must have been switched on. This is done using the "TrendViewSetRulerMode" system function. Use in the function list TrendViewRulerRight (Screen object) Use in user-defined functions - Parameters Screen object Name of the trend view in which the read-line is moved forward. See also TrendViewSetRulerMode (Page 3528) TrendViewSetRulerMode Description Hides or shows the read-line in the trend view. The read-line displays the Y value belonging to the X value. Note To ensure that the ruler is displayed, you have to activate the setting "Show ruler" in the trend view properties. 3528 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.6 Working with system functions Use in the function list TrendViewSetRulerMode (Screen object) Use in user-defined functions - Parameters Screen object Name of the trend view in which the read-line is hidden or shown. See also TrendViewRulerLeft (Page 3527) TrendViewRulerRight (Page 3528) TrendViewStartStop Description Stops the trend recording or continues the trend recording in the trend view. Use in the function list TrendViewStartStop (Screen object) Use in user-defined functions - Parameters Screen object Name of the trend view in which the recording of the trend is started or stopped. TrendViewBackToBeginning Description Scrolls back to the beginning of the display range in the trend view. WinCC Basic V13.0 System Manual, 02/2014 3529 Visualize processes 10.6 Working with system functions Use in the function list TrendViewBackToBeginning (Screen object) Use in user-defined functions - Parameters Screen object Name of the trend view in which you scroll to the beginning of the display range. GetUserName Description Writes the user name of the user currently logged on to the HMI device in the given tag. If the given tag has a control connection, the user name is also available in the PLC connection. This system function makes it possible, for example, to implement a user-dependent release of certain functionalities. Use in the function list GetUserName (Tag) Use in user-defined functions GetUserName (Tag) Can be used if the configured device supports user-defined functions. For additional information, refer to "Device dependency". Parameter Tag The tag to which the user name is written. See also Device-based dependency of system functions (Page 3506) 3530 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.6 Working with system functions GetGroupNumber Description Reads the number of the group to which the user logged on to the HMI device belongs, and writes it to the given tag. Use in the function list GetGroupNumber (Tag) Use in user-defined functions GetGroupNumber (Tag) Can be used if the configured device supports user-defined functions. For additional information, refer to "Device dependency". Parameter Tag The tag to which the number of the group is written. See also Device-based dependency of system functions (Page 3506) GetPassword Description Writes the password of the user currently logged on to the HMI device in the given tag. Note Make sure that the value of the given tag is not displayed in another place in the project. Note The passwords of SIMATIC Logon users cannot be read. Use in the function list GetPassword (Tag) WinCC Basic V13.0 System Manual, 02/2014 3531 Visualize processes 10.6 Working with system functions Use in user-defined functions GetPassword (Tag) Can be used if the configured device supports user-defined functions. For additional information, refer to "Device dependency". Parameter Tag The tag to which the password is written. See also Device-based dependency of system functions (Page 3506) ReadPLCMode Description Evaluates the current state of the connected PLC. The system function "ReadPLCMode" can only be configured for the following PLCs: SIMATIC S7-1200 SIMATIC S7-1500 Use in the function list ReadPLCMode (connection, mode) Use in user-defined functions GetPLCMode (Connection, Mode) Parameters Connection Connection of PLC and HMI device. Mode Evaluates the mode of the connected PLC. 8: RUN = The PLC program is being executed. 4: STOP = The PLC program has been interrupted. Select a suitable user variable for the evaluation. 3532 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.6 Working with system functions LinearScaling Description Assigns a value to the tag Y, which is calculated from the value of the given tag X using the linear function Y= (a *X) + b. The inverse of this function is the "InvertLinearScaling" system function. Note The tags X and Y must not be identical. If a tag is to be converted into itself, a auxiliary tag must be used. The "SetTag" system function can be used to assign the value of the tags to be converted to the auxiliary tags. Use in the function list LinearScaling (Y, a, X, b) Use in user-defined functions LinearScaling (Y, a, X, b) Can be used if the configured device supports user-defined functions. For additional information, refer to "Device dependency". Parameters Y The tag which is assigned the value calculated from the linear equation. a The value with which is multiplied. X The tag that contains the value used for calculation. b The value that is added. Example The following program code uses the LinearScaling function to assign a value to the Yvar tag. { WinCC Basic V13.0 System Manual, 02/2014 3533 Visualize processes 10.6 Working with system functions BYTE BYTE BYTE BYTE Yvar; Xvalue = 10; bvalue = 3; avalue = 4; // linear scaling LinearScaling ( Yvar, avalue, Xvalue, bvalue); printf ("Yvar = %d\r\n, Yvar); ... } The saved return value can be processed in the following code. See also Device-based dependency of system functions (Page 3506) InvertLinearScaling (Page 3523) ClearAlarmBuffer Description Deletes alarms from the alarm buffer on the HMI device. Note Alarms which have not yet been acknowledged are also deleted. Use in the function list ClearAlarmBuffer (Alarm class number) Use in user-defined functions ClearAlarmBuffer (Alarm_class_number) Can be used if the configured device supports user-defined functions. For additional information, refer to "Device dependency". Parameter Alarm class number Determines which alarms are to be deleted from the alarm buffer: 0 (hmiAll) = All alarms/events 1 (hmiAlarms) = Alarms of alarm class "Errors" 3534 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.6 Working with system functions 2 (hmiEvents) = Alarms of alarm class "Warnings" 3 (hmiSystem) = Alarms of alarm class "System" 4 (hmiS7Diagnosis) = Alarms of alarm class "Diagnosis Events" Note Device dependency Alarms of alarm class "Diagnosis Events" are not available on Basic Panels. See also Device-based dependency of system functions (Page 3506) ClearAlarmBufferProTool Description The system function exists to ensure compatibility. It has the same functionality as the "ClearAlarmBuffer" system function, but uses the old ProTool numbering. Use in the function list ClearAlarmBufferProTool (Alarm class number) Use in user-defined functions ClearAlarmBufferProtoolLegacy (Alarm_class_number) Can be used if the configured device supports user-defined functions. For additional information, refer to "Device dependency". Parameter Alarm class number Alarm class number whose messages are to be deleted: -1 (hmiAllProtoolLegacy) = All alarms/events 0 (hmiAlarmsProtoolLegacy) = Alarms of alarm class "Errors" 1 (hmiEventsProtoolLegacy) = Alarms of alarm class "Warnings" 2 (hmiSystemProtoolLegacy) = Alarms of alarm class "System" WinCC Basic V13.0 System Manual, 02/2014 3535 Visualize processes 10.6 Working with system functions 3 (hmiS7DiagnosisProtoolLegacy) = Alarms of alarm class "Diagnosis Events" Note Device dependency Alarms of alarm class "Diagnosis Events" are not available on Basic Panels. See also Device-based dependency of system functions (Page 3506) ClearAlarmBuffer (Page 3534) AlarmViewEditAlarm Description Triggers the event "Edit" for all alarms selected in the given alarm view. This system function is used when the integrated button of the ActiveX control should not be used. A system function can in turn be configured on the "Edit" event. For example, it is possible to change to the process screen in which the alarm appeared. Note If the alarms to be edited have not yet been acknowledged, the acknowledgment takes place automatically when this system function is called up. Use in the function list AlarmViewEditAlarm (Screen object) Use in user-defined functions - 3536 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.6 Working with system functions Parameters Screen object Name of the alarm view in which the event is triggered. Note The HMI devices listed below do not support this system function for the "screen" object: OP 73, OP 77A, TP 177A. AlarmViewAcknowledgeAlarm Description Acknowledges the alarms selected in the given alarm view. This system function is used when the integrated button of the ActiveX control should not be used. Use in the function list AlarmViewAcknowledgeAlarm (Screen object) Use in user-defined functions - Parameters Screen object Name of the alarm view in which the event is triggered. Note The HMI devices listed below do not support this system function for the "screen" object: OP 73, OP 77A, TP 177A. AlarmViewShowOperatorNotes Description Displays the configured tooltip of the alarm selected in the given alarm view. WinCC Basic V13.0 System Manual, 02/2014 3537 Visualize processes 10.6 Working with system functions Use in the function list AlarmViewShowOperatorNotes (Screen object) Use in user-defined functions - Parameters Screen object Name of the alarm view in which the event is triggered. Note The HMI devices listed below do not support this system function for the "screen" object: OP 73, OP 77A, TP 177A. AcknowledgeAlarm Description Acknowledges all selected alarms. This system function is used when the HMI device does not have an ACK key or when the integrated key of the alarm view should not be used. This system function can only be used for function keys. Use in the function list AcknowledgeAlarm Use in user-defined functions AcknowledgeAlarm Can be used if the configured device supports user-defined functions. For additional information, refer to "Device dependency". Parameter -- See also Device-based dependency of system functions (Page 3506) 3538 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.6 Working with system functions RecipeViewNewDataRecord Description Creates a new data record in the given recipe view. Use in the function list RecipeViewNewDataRecord (Screen object) Use in user-defined functions - Parameters Screen object Name of the recipe view in which the new recipe data record is created. RecipeViewGetDataRecordFromPLC Description Transfers the data record that is currently loaded in the PLC to the HMI device and displays it in the recipe view. Use in the function list RecipeViewGetDataRecordFromPLC (Screen object) Use in user-defined functions - Parameters Screen object Name of the recipe view in which the recipe data record from the PLC is displayed. RecipeViewClearDataRecord Description Deletes the data record which is currently displayed in the recipe view. WinCC Basic V13.0 System Manual, 02/2014 3539 Visualize processes 10.6 Working with system functions Use in the function list RecipeViewClearDataRecord (Screen object) Use in user-defined functions - Parameters Screen object Name of the recipe view in which the displayed recipe data record is deleted. RecipeViewMenu Description Opens the menu of the specified simple recipe view. Only use this system function at a simple recipe view. Use in the function list RecipeViewMenu (Screen object) Use in user-defined functions - Parameters Screen object Name of the recipe view in which the menu is to be opened. RecipeViewOpen Description Displays the data record values in the given recipe view or changes to the next selection field. The system function has no effect if the selection field for the recipe data record values is displayed on the HMI device. Operation sequence of the selection lists in runtime: 3540 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.6 Working with system functions Recipe name Data record name RecipeDataRecordValues This system function is used when a simple recipe view has been configured. In the simple recipe view, only one selection list is displayed at a time on the HMI device. Use the "RecipeViewBack" system function to display the previous selection list. Use in the function list RecipeViewOpen (Screen object) Use in user-defined functions - Parameters Screen object Name of the recipe view in which the command is triggered. See also RecipeViewBack (Page 3543) RecipeViewSetDataRecordToPLC Description Transfers the recipe data record which is currently displayed in the recipe view to the PLC. Use in the function list RecipeViewSetDataRecordToPLC (Screen object) Use in user-defined functions - Parameters Screen object Name of the recipe view from which the recipe data record is transferred to the connected PLC. WinCC Basic V13.0 System Manual, 02/2014 3541 Visualize processes 10.6 Working with system functions RecipeViewSaveDataRecord Description Saves the recipe data record which is currently displayed in the recipe view. Use in the function list RecipeViewSaveDataRecord (Screen object) Use in user-defined functions - Parameters Screen object Name of the recipe view in which the recipe data record is saved. RecipeViewSaveAsDataRecord Description Saves the data record currently being displayed in the recipe view under a new name. Use in the function list RecipeViewSaveAsDataRecord (Screen object) Use in user-defined functions - Parameters Screen object Saves the data record currently being displayed in the recipe view under a new name and/or new number. RecipeViewRenameDataRecord Description Renames the selected data record in the given recipe view. 3542 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.6 Working with system functions Only use this system function at a simple recipe view. Use in the function list RecipeViewRenameDataRecord (Screen object) Use in user-defined functions - Parameters Screen object Name of the recipe view in which the recipe data record is renamed. RecipeViewShowOperatorNotes Description Displays the configured tooltip of the specified recipe view. Use in the function list RecipeViewShowOperatorNotes (Screen object) Use in user-defined functions - Parameters Screen object Name of the recipe view whose configured tooltip is displayed. RecipeViewBack Description Returns to the previous selection list in the given recipe view. The system function has no effect if the selection field for the recipe is displayed on the HMI device. Operation sequence of the selection lists in runtime: WinCC Basic V13.0 System Manual, 02/2014 3543 Visualize processes 10.6 Working with system functions Recipe name Data record name RecipeDataRecordValues This system function is used when a simple recipe view has been configured. In the simple recipe view, only one selection list is displayed at a time on the HMI device. Use the "RecipeViewOpen" system function to display the recipe data record values or the next selection field. Use in the function list RecipeViewBack (Screen object) Use in user-defined functions - Parameters Screen object Name of the recipe view in which the command is triggered. 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. For additional information, refer to "Device dependency". Parameters Tag The BOOL type tag which is set to 0 (FALSE). 3544 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.6 Working with system functions Example The following program code resets the value of the boolean tag b_value to 0 by means of the ResetBit function and outputs the result along with the original b_saved value. { BOOL b_value = 1; BOOL b_saved = b_value; //Reset bit ResetBit (b_value); //print current and saved value printf ("Current value: %d\r\n, Saved value: %d\r\n",b_value, b_saved); ... } See also Device-based dependency of system functions (Page 3506) ResetBitInTag (Page 3545) ResetBitInTag Description Sets a bit in the specified tag to 0 (FALSE). After changing the given bit, the system function transfers the entire tag back to the PLC. It is not checked whether other bits in the tags have changed in the meantime. Operator and PLC have read-only access to the indicated tag until it is transferred back to the PLC. Note If the PLC supports BOOL tags, do not use this system function. Use the "ResetBit" system function instead. Use in the function list ResetBitInTag (Tag, Bit) Use in user-defined functions ResetBitInTag (Tag, Bit) Can be used if the configured device supports user-defined functions. For additional information, refer to "Device dependency". WinCC Basic V13.0 System Manual, 02/2014 3545 Visualize processes 10.6 Working with system functions 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. Example The following program code sets a bit at the specified bitposition in the bvalue tag to 0 and outputs the result along with the original bsaved value. { BYTE bvalue; BYTE bsaved = bvalue; BYTE bitposition = 2; //Reset bit in bitposition ResetBitInTag (bvalue, bitposition); //print current and saved value printf ("Current value: %d\r\n, Saved value: %d\r\n",bvalue, bsaved); ... } See also Device-based dependency of system functions (Page 3506) ResetBit (Page 3544) PressButton Description The system function can only be configured on the function keys of an HMI device and triggers the "Press key" event at the specified screen object. 3546 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.6 Working with system functions Use this system function when you want to operate a button in a screen with a function key of the HMI device, for example. Note The "PressButton" and "ReleaseButton" system functions must always be configured together. If you configure the "PressButton" system function on the "Press key" event for a function key, the "ReleaseButton" system function is configured on the "Release" event for the same function key. Use in the function list PressButton (Screen object) Use in user-defined functions - Parameters Screen object Name of the screen object on which the event is triggered. ReleaseButton Description The system function can only be configured on the function keys of an HMI device and triggers the "Release button" event at the specified screen object. Use this system function when you want to operate a button in a screen with a function key of the HMI device, for example. Note The "PressButton" and "ReleaseButton" system functions must always be configured together. If you configure the "PressButton" system function on the "Press key" event for a function key, then the "ReleaseButton" system function is configured on the "Release key" event for the same function key. Use in the function list ReleaseButton (Screen object) WinCC Basic V13.0 System Manual, 02/2014 3547 Visualize processes 10.6 Working with system functions Use in user-defined functions - Parameters Screen object Name of the screen object on which the event is triggered. ShiftAndMask Description This system function converts the input bit pattern of the source tags into an output bit pattern of the target tags. This involves bit shifting and masking. Note If the source and target tag have a different number of bits, using the system function in the target tag can result in a violation of the value range. Use in the function list ShiftAndMask (Source tag, Target tag, Bits to shift, Bits to mask) Use in user-defined functions ShiftAndMask (Source_tag, Target_tag, Bits_to_shift, Bits_to_mask) Can be used if the configured device supports user-defined functions. For additional information, refer to "Device dependency". Parameter Source tag The tag includes the input bit pattern. Integer-type tags, e.g. "Byte", "Char", "Int", "UInt", "Long" and "ULong" are permitted. Example: The actual value 72 is set at the 16-bit integer source tag: 0000000001001000. Target tag The output bit pattern is saved in the tag. Integer type tags, e.g. "Byte", "Char", "Int", "UInt", "Long" and "ULong" are permitted. Example: The shifted input bit pattern is multiplied by the bit mask, with bit-by-bit logical AND operation: 0000000000001001. The resultant decimal value "8" is saved to the target tag. Please note the following: 3548 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.6 Working with system functions The source and target tags have the same number of bits. The number of bits to shift is less than the number of bits in the source tag and target tag. Bits to mask does not have more bits than the source tag and the target tag. Bits to shift Number of bits by which the input bit pattern is shifted right. A negative value shifts the input bit pattern to the left. Example: "Bits to shift" has the value "+3". The input bit pattern is shifted right by three bits when the system function is called: 0000000000001001. Bits to the left are padded with "0". Three bits are truncated on the right. The new decimal value is "9". Note The left bit is "1" in a source tag of the data type with negative signed integer. This sign bit is padded with "0" when the bits are shifted right. The sign changes to "+". Bits to mask An integer serves as bit mask. The bit pattern is used to multiply the shifted input bit pattern. Example: Integer "2478" with the bit pattern "0000100110101110". You can enter the bit mask in three different ways: Hexadecimal: First enter the prefix "0h" or "0H", followed by an optional space for better readability. Then group the bit pattern in blocks of four (0000)(1001)(1010)(1110) and set each block in hexadecimal code: (0)(9)(A)(E). Only the characters 0-9, A-F, a-f are allowed: "0h 09AE". Binary: First enter the prefix "0b" or "0B", followed by an optional space for better readability. Then group the binary bit pattern into blocks of four 0000 1001 1010 1110 with spaces in between as a check. Only the characters "0" or "1" are allowed: "0b 0000 1001 1010 1110". Decimal: Enter the value "2478" directly, without a prefix. See also Device-based dependency of system functions (Page 3506) PageUp Description Executes the key function <PageUp> on the HMI device. This system function can only be used for function keys and tasks with a time trigger. Use in the function list PageUp WinCC Basic V13.0 System Manual, 02/2014 3549 Visualize processes 10.6 Working with system functions Use in user-defined functions PageUp Can be used if the configured device supports user-defined functions. For additional information, refer to "Device dependency". Parameter - See also Device-based dependency of system functions (Page 3506) PageDown Description Executes the key function <Pagedown> on the HMI device. This system function can only be used for function keys. Use in the function list PageDown Use in user-defined functions PageDown Can be used if the configured device supports user-defined functions. For additional information, refer to "Device dependency". Parameter - See also Device-based dependency of system functions (Page 3506) SetDeviceMode Description Toggles the operating mode on the HMI device. The following types of operation are possible: "Online", "Offline" and "Load". 3550 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.6 Working with system functions Use in the function list SetDeviceMode (Operating mode) Use in user-defined functions SetDeviceMode (Operating_mode) Can be used if the configured device supports user-defined functions. For additional information, refer to "Device dependency". Parameter Operating mode Determines the operating mode of the HMI device: 0 (hmiOnline) = Online: The connection to the PLC is established. The configured connection status is always set in this process. The states that were last used in Runtime are not considered. 1 (hmiOffline) = Offline: The connection to the PLC is disconnected. 2 (hmiTransfer) = load: A project can be transferred from the configuration computer to the HMI device. Note If you use a PC as an HMI device, the runtime software will be exited when you change operating mode after "Load". See also Device-based dependency of system functions (Page 3506) SetConnectionMode (Page 3559) 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) WinCC Basic V13.0 System Manual, 02/2014 3551 Visualize processes 10.6 Working with system functions Can be used if the configured device supports user-defined functions. For additional information, refer to "Device dependency". Parameters Tag The BOOL type tag which is set to 1 (TRUE). Example The following program code sets the value of the boolean tag b_value to 1 by means of the SetBit function and outputs the result along with the original b_saved value. { BOOL b_value = 0; BOOL b_saved = b_value; //Set bit SetBit (b_value); //print current and saved value printf ("Current value: %d\r\n, Saved value: %d\r\n",b_value, b_saved); ... } See also Device-based dependency of system functions (Page 3506) 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. 3552 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.6 Working with system functions 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. For additional information, refer to "Device dependency". Parameters Tag The tag in which a bit is set to 1 (TRUE). Bit The number of the bit that is set to 1 (TRUE). When this system function is used in a user-defined function, the bits in the specified tag will be counted from right to left independent of the PLC used. The counting begins with 0. Note The guaranteed update of the tags used with actual process values is absolutely conditional in terms of reliable functionality. You should therefore configure the tag in an I/O field or assign the system function to a screen object, such as a button. If you have configured a short event such as the activation of an alarm for the system function you can only access the actual process values by setting the tag for continuous reading. Example The following program code sets a bit to 1 at the specified bitposition in the bvalue tag and outputs the result along with the original bsaved value. { BYTE bvalue; BYTE bsaved = bvalue; BYTE bitposition = 2; //Reset bit in bitposition SetBitInTag (bvalue, bitposition); //print current and saved value printf ("Current value: %d\r\n, Saved value: %d\r\n",bvalue, bsaved); ... } WinCC Basic V13.0 System Manual, 02/2014 3553 Visualize processes 10.6 Working with system functions See also Device-based dependency of system functions (Page 3506) SetBit (Page 3551) SetBitWhileKeyPressed Description Sets the bit of the given tag to 1 (TRUE) as long as the user keeps the configured key pressed. After changing the given bit, the system function transfers the entire tag back to the PLC. It is not checked whether other bits in the tags have changed in the meantime. Operator and PLC have read-only access to the indicated tag until it is transferred back to the PLC. You should only access tags of the BOOL type with this system function to avoid problems with overlapping access to the same tag. Note All functions on the event "Release" are performed immediately by means of a screen change configured for a key, even if the key is kept pressed. If the "SetBitWhileKeyPressed" system function is configured for a function key, the bit will be reset immediately following a screen change. This action is necessary since the key assignments change after the screen change. If the PLC supports BOOL tags, do not use this system function. Use the "SetBit" system function instead. Use in the function list SetBitWhileKeyPressed (Tag, Bit) Use in user-defined functions - Parameters Tag The tag in which a bit is temporarily set to 1 (TRUE). Use only tags of the type BOOL, as far as allowed by the PLC. 3554 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.6 Working with system functions Bit The number of the bit that is temporarily set to 1 (TRUE). Note The guaranteed update of the tags used with actual process values is absolutely conditional in terms of reliable functionality. You should therefore configure the tag in an IO field, or assign the function to a screen element such as a button. If you configured a short event such as the activation of an alarm for the function you can only access the actual process values by setting the tag for continuous reading. See also SetBit (Page 3551) Device-based dependency of system functions (Page 3506) SetBacklightColor Description Defines the background lighting of the button. Note The configuration that was set at Switch off is reestablished when restarting the HMI device. Use in the function list SetBacklightColor (Value) Use in user-defined functions - Parameters Value Defines the background lighting of the button: 0 (hmiWhite) = White: No color 1 (hmiGreen) = Green: Green color 2 (hmiYellow) = Yellow: Yellow color 3 (hmiRed) = Red: Red color WinCC Basic V13.0 System Manual, 02/2014 3555 Visualize processes 10.6 Working with system functions SetPLCDateTime Description Changes the data and the time of the linked PLC The system function "SetPLCDateTime" can only be configured for the following PLCs: SIMATIC S7 1200 SIMATIC S7 1500 Use in the function list SetPLCDateTime (connection, time) Use in user-defined functions SetPLCDateTime (Connection, Time) Parameters Connection Connection of PLC and HMI device. Time Transfers the date and the time of the HMI device to the PLC. The PLC applies the date and the time of the HMI device. SetPLCMode Description Switches the operating mode of the PLC to one of the following states: RUN STOP The system function "SetPLCMode" can only be configured for the following PLCs: SIMATIC S7 1200 SIMATIC S7 1500 Use in the function list SetPLCMode (connection, mode) 3556 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.6 Working with system functions Use in user-defined functions SetPLCMode (Connection, Mode) Parameters Connection Connection of PLC and HMI device. Mode Specifies the operating mode of the PLC: RUN = the PLC is switched to the RUN state. The PLC program is executed. STOP = the PLC is switched to the STOP state. The PLC program is interrupted. SetLanguage Description Toggles the language on the HMI device. All configured text and system events are displayed on the HMI device in the newly set language. Use in the function list SetLanguage (Language) Use in user-defined functions SetLanguage (Language) Can be used if the configured device supports user-defined functions. For additional information, refer to "Device dependency". Parameter Language Determines which language is set on the HMI device. The following specifications are possible: -1 (hmiToggle) = Toggle: Changes to the next language. The sequence is determined during configuration in the "Project languages" editor. Number you have defined under "Languages and fonts" in the "Runtime Settings" editor. Changes to the language with the given number. WinCC Basic V13.0 System Manual, 02/2014 3557 Visualize processes 10.6 Working with system functions Language you have defined under "Languages and fonts" in the "Runtime Settings" editor. Language abbreviation in accordance with the VBScript5 reference: This changes to the language corresponding to the specified language code, e.g. "de-DE" for German (Germany) or "en-US" for English (United States). An overview of the language abbreviations is available in the basic information of VBScript under the topic "Area diagram-ID (LCID) Diagram". See also Device-based dependency of system functions (Page 3506) 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. For additional information, refer to "Device dependency". 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. 3558 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.6 Working with system functions Example The following program code uses the SetTag function to set the value of the gs_tag_bit tag to TRUE and saves the return value to the ok tag. { BOOL ok; BOOL bvalue; //Set the tag to true ok = SetTag("gs_tag_bit", TRUE); //error handling if(ok) { // succeeded printf ( "Function has run through.\r\n" ); bvalue = GetTagBit("gs_tag_bit"); printf ("Value of gs_tag_bit: %d\r\n", bvalue); } else { // failed printf ( "Error - function failed." ); } ... } The saved return value can be processed in the following code. See also Device-based dependency of system functions (Page 3506) IncreaseTag (Page 3519) SetConnectionMode Description Connects or disconnects the given connection. Note A connection to the PLC cannot be established until the operating mode ONLINE has been set on the HMI device. Use the "SetDeviceMode" system function for this purpose. Use in the function list SetConnectionMode (Mode, Connection) WinCC Basic V13.0 System Manual, 02/2014 3559 Visualize processes 10.6 Working with system functions Use in user-defined functions SetConnectionMode (Mode, Connection) Can be used if the configured device supports user-defined functions. For additional information, refer to "Device dependency". Parameter Mode Determines whether a connection to the PLC is established or disconnected: 0 (hmiOnline) = Online: Connection is established. 1 (hmiOffline) = Offline: Connection is disconnected. Connection The PLC to which the HMI device is connected. You specify the name of the PLC in the connection editor. Multiple use of the system function in a user-defined function If you use the "SetConnectionMode" system function for different connections, it may be possible that not all system functions are executed correctly. Proceed as follows to prevent this situation: 1. Create a "BOOL" type tag with the start value "0". 2. Configure the "SetConnectionMode" system function on the "Value change" event of the HMI tags. If you want to disconnect three connections, for example, you must configure the system function three times. 3. In the user-defined function, apply the "InvertBit" system function to the HMI tag. Application example Two typical application examples for this system function are as follows: Test As long as no PLC is connected to the HMI device, no error messages will be output during the test on the HMI device. If the HMI device is connected to a PLC, the connection to the PLC can be established by pressing a key. Commissioning Several PLCs are to be configured for a system. At first, all PLCs except one are configured "Offline". After commissioning of the first PLC, the connection to each of the other PLCs is established by pressing a key. In this way, the other PLCs are started up one after another. See also Device-based dependency of system functions (Page 3506) SetDeviceMode (Page 3550) 3560 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.6 Working with system functions SimulateSystemKey Description Simulates the behavior of a System Key. Use this system function if a system key, such as the "ACK" key, "Input" key or the number pad is not available on the HMI device. Use in the function list SimulateSystemKey (System key) Use in user-defined functions - Parameters System key System Key, the behavior for which is to be simulated. System key "+/-" With the SimulateSystemKey system function, the system key "+/-" is only supported for the following HMI devices: KP300 Basic KP400 Basic KTP400 Basic mono PN KTP400 Basic color PN KTP400 Basic color PN Portrait KTP600 Basic mono PN KTP600 Basic color PN KTP600 Basic color DP KTP1000 Basic PN KTP1000 Basic DP Use the system keys "+" and "-" separately for all other HMI devices. WinCC Basic V13.0 System Manual, 02/2014 3561 Visualize processes 10.6 Working with system functions SimulateTag Description Simulates the behavior of tags and dynamic objects such as text lists, without having the HMI device connected to a PLC. You can, for example, configure the system function to the "Loaded" event of a screen. This system function is used, for example, to demonstrate the functionality of a project. Only tags of the data type Integer can be used for simulation. Tags of the data types Integer and Double Integer, however, can be used with OP 73, OP 77A, TP 177A. Note If you use the system function "SimulateTag" with a short cycle time on a Basic Panel, the HMI device may be overloaded. Use in the function list SimulateTag (Tag, Cycle, Maximum value, Minimum value, Value) Use in user-defined functions - Parameter Tag The tag whose value is changed. Cycle The factor by which the basic cycle of 200 milliseconds is multiplied. The cycle defines when the tag value is changed by the specified value. Possible cycles between 1 and 32767. Maximum value The maximum value that the tag can assume during simulation. The maximum value must be greater than the minimum value but less than / equal to 32767. Minimum value The minimum value that the tag can assume during simulation. The minimum value must be lower than the maximum value but greater than / equal to -32768. Value The value by which the tag value is changed during each cycle. Possible values between -32768 and 32767. 3562 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.6 Working with system functions A positive value increases the tag value. When the maximum value is reached, the tag value is set to the minimum value after the next update cycle. A negative value reduces the tag value. When the minimum value is reached, the tag value is set to the maximum value after the next update cycle. 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. For additional information, refer to "Device dependency". 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) Example The following program code shuts down Runtime and the operating system. { //Stop runtime and shutdown StopRuntime (hmiStopRuntimeAndOperationSystem); } The saved return value can be processed in the following code. See also Device-based dependency of system functions (Page 3506) WinCC Basic V13.0 System Manual, 02/2014 3563 Visualize processes 10.6 Working with system functions TraceUserChange Description Outputs a system event that shows which user is currently logged in on the HMI device. This system function can only be used in the Scheduler. Use in the function list TraceUserChange Use in user-defined functions - Parameters -- DecreaseFocusedValue Description Subtracts the specified value from the value of the tag which is connected to the screen object and currently has the focus. This system function can only be used for function keys. Use in the function list DecreaseFocusedValue (Value) Use in user-defined functions - Parameters Value The value which is subtracted from the tag value. 3564 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.6 Working with system functions 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. The auxiliary tags are assigned to the tag value with the "SetTag" system function. If you configure the system function on the events of an alarm and the tag is not being used in the current screen, it is not ensured that the actual value of the tags is being used in the PLC. You can improve the situation by setting the "Cyclic continuous" acquisition mode. Use in the function list DecreaseTag (Tag, Value) Use in user-defined functions DecreaseTag (Tag, Value) Can be used if the configured device supports user-defined functions. For additional information, refer to "Device dependency". Parameter Tag The tag from which the given value is subtracted. Value The value which is subtracted. See also Device-based dependency of system functions (Page 3506) ChangeConnection Description Disconnects the connection to the currently used PLC in use and establishes a connection to a PLC with another address. The newly connected PLC must belong to the same device class WinCC Basic V13.0 System Manual, 02/2014 3565 Visualize processes 10.6 Working with system functions (S7-1200, S7-300, ...etc). With S7-1200, the use of the function is also only permitted for absolute addressing. Note When changing to another address, ensure that the address is not already being used by another HMI device. The follows address types are supported: IP address MPI address The follows PLC types are supported: SIMATIC S7 300/400 SIMATIC S7-NC SIMOTION Use in the function list ChangeConnection (Connection, Address, Slot, Rack) Use in user-defined functions ChangeConnection (Connection, Address, Slot, Rack) Can be used if the configured device supports user-defined functions. For additional information, refer to "Device dependency". Parameter Connection Name of the connection that is disconnected. The name is set during configuration, for example, in the "Connections" editor. Address MPI/PROFIBUS or IP address of the PLC to which the connection will be established. Note Set the address by means of a tag. The objects list displays the tags of all data types. Select only tags of the following data types: Ethernet connection: "String" data type MPI connection: "Int" data type 3566 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.6 Working with system functions Slot Slot of the PLC to which the connection will be established. Rack Rack of the PLC to which the connection will be established. Application example You want to operate one HMI device on several machines. Configure the necessary PLCs in the project, to which you want to change by pressing a key. When changing the PLC, the connection to the PLC in use is disconnected. Then the connection to the new PLC with other address parameters is reestablished. To access the values of the new PLC, configure the same tags for the PLC used. The PLC which you have indicated when creating the project will be used as default. 1. Enter the name and address of the PLC in the "Connections" editor. 2. Configure a button in the process screen. 3. Configure the "ChangeConnection" system function on the "Press" event. 4. Enter the name of the connection and address of the PLC as parameters. See also Device-based dependency of system functions (Page 3506) ShowLogonDialog Description Opens a dialog on the HMI device with which the user can log on to the HMI device. Use in the function list ShowLogonDialog Use in user-defined functions - Parameters -- WinCC Basic V13.0 System Manual, 02/2014 3567 Visualize processes 10.6 Working with system functions ShowOperatorNotes Application Displays the tooltip configured for the selected object. If the system function is configured on a function key, the tooltip for the screen object that currently has the focus is displayed. If a tooltip is configured for the screen itself, you can switch to this text by pressing <Enter> or by double-clicking on the help window. If the system function is configured on a button, only the tooltip for the current screen is displayed. If a tooltip is configured on the button itself, initially only the tooltip for the button is displayed. You can press <Enter> or double-click on the help window to switch to the tooltip for the current screen. Note No other screen object can be used while the help window is open. To use the screen object, close the help window. Closing the help window You can close the help window in the following ways: Using the keys: By pressing the <HELP> key again By pressing the <ESC> key Using the touch screen: By pressing the button Use in the function list ShowOperatorNotes (Layout) Use in user-defined functions ShowOperatorNotes (Display_mode) Can be used if the configured device supports user-defined functions. For additional information, refer to "Device dependency". Parameter Display mode Determines whether the configured tooltip is hidden or shown: 0 (hmiOff) = Off: Configured tooltip is hidden 1 (hmiOn) = On: Configured tooltip is shown 3568 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.6 Working with system functions -1 (hmiToggle) = Toggle: Toggles between the two modes See also Device-based dependency of system functions (Page 3506) ShowAlarmWindow Description Hides or shows the alarm window on the HMI device. Use in the function list ShowAlarmWindow (Object name, Layout) Use in user-defined functions ShowAlarmWindow (Object_name, Display_mode) Can be used if the configured device supports user-defined functions. For additional information, refer to "Device dependency". Parameter Object name Name of the alarm view which is hidden or shown. Layout Determines whether the alarm window is hidden or shown: 0 (hmiOff) = Off: Alarm view is hidden 1 (hmiOn) = On: Alarm view is shown -1 (hmiToggle) = Toggle: Toggles between the two modes See also Device-based dependency of system functions (Page 3506) WinCC Basic V13.0 System Manual, 02/2014 3569 Visualize processes 10.6 Working with system functions 10.6.4.2 Events Overview Editors Introduction The following table shows which events occur in which editor. Technical data subject to change. Icon Editor Screens HMI alarms HMI tags Scheduler 1 Cleared (Page 3575) X -- -- -- 2 Activate (Page 3575) -- -- -- -- 3 Change (Page 3576) -- -- -- -- 4 Loaded (Page 3576) X -- -- -- 5 Execute (Page 3576) -- -- -- X 6 Selection changed (Page 3577) -- -- -- -- 7 In the event of high limit violation (Page 3577) -- -- X -- 8 In the event of low limit violation (Page 3577) -- -- X -- 9 When dialog is opened (Page 3577) -- -- -- X 10 When dialog is closed (Page 3578) -- -- -- X 11 User change (Page 3578) -- -- -- X 12 Screen change (Page 3578) -- -- -- X 13 Deactivate (Page 3578) -- -- -- X 14 Double-click (Page 3579) -- -- -- -- 15 Press (Page 3579) -- -- -- -- 16 On Finish Input (Page 3580) -- -- -- -- 17 Press ESC twice (Page 3580) -- -- -- -- 18 Outgoing (Page 3580) -- X -- -- 19 Incoming (Page 3581) -- X -- -- 20 Click (Page 3581) -- -- -- -- 21 Click when flashing (Page 3581) -- -- -- -- 22 Loop-in alarm (Page 3582) -- X -- -- 23 Release (Page 3582) -- -- -- -- 24 Alarm buffer overflow (Page 3582) -- -- -- X 3570 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.6 Working with system functions 25 Acknowledge (Page 3583) -- X -- -- 26 Reach margin (Page 3583) -- -- -- -- 27 Runtime Stop (Page 3583) -- -- -- X 28 Press key (Page 3584) -- -- -- -- 29 Release key (Page 3584) -- -- -- -- 30 Overflow (Page 3584) -- -- -- -- 31 Switch OFF (Page 3585) -- -- -- -- 32 Switch ON (Page 3585) -- -- -- -- 33 Low free storage space (Page 3585) -- -- -- -- 34 Free space critically low (Page 3585) -- -- -- -- 35 Value change (Page 3585) -- -- X -- 36 Time expired (Page 3586) -- -- -- -- Basic objects Introduction The following table shows which events occur on which objects. Technical data subject to change. Icon Object Line Ellipse Circle Rectangle Text field Graphic view 1 Cleared (Page 3575) -- -- -- -- -- -- 2 Activate (Page 3575) -- -- -- -- -- -- 3 Change (Page 3576) -- -- -- -- -- -- 4 Loaded (Page 3576) -- -- -- -- -- -- 5 Execute (Page 3576) -- -- -- -- -- -- 6 Selection changed (Page 3577) -- -- -- -- -- -- 7 In the event of high limit violation (Page 3577) -- -- -- -- -- -- WinCC Basic V13.0 System Manual, 02/2014 3571 Visualize processes 10.6 Working with system functions 8 In the event of low limit violation (Page 3577) -- -- -- -- -- -- 9 When dialog is opened (Page 3577) -- -- -- -- -- -- 10 When dialog is closed (Page 3578) -- -- -- -- -- -- 11 User change (Page 3578) -- -- -- -- -- -- 12 Screen change (Page 3578) -- -- -- -- -- -- 13 Deactivate (Page 3578) -- -- -- -- -- -- 14 Double-click (Page 3579) -- -- -- -- -- -- 15 Press (Page 3579) -- -- -- -- -- -- 16 On Finish Input (Page 3580) -- -- -- -- -- -- 17 Press ESC twice (Page 3580) -- -- -- -- -- -- 18 Outgoing (Page 3580) -- -- -- -- -- -- 19 Incoming (Page 3581) -- -- -- -- -- -- 20 Click (Page 3581) -- -- -- -- -- -- 21 Click when flashing (Page 3581) -- -- -- -- -- -- 22 Loop-in alarm (Page 3582) -- -- -- -- -- -- 23 Release (Page 3582) -- -- -- -- -- -- 24 Alarm buffer overflow (Page 3582) -- -- -- -- -- -- 25 Acknowledge (Page 3583) -- -- -- -- -- -- 26 Reach margin (Page 3583) -- -- -- -- -- -- 27 Runtime Stop (Page 3583) -- -- -- -- -- -- 28 Press key (Page 3584) -- -- -- -- -- -- 29 Release key (Page 3584) -- -- -- -- -- -- 30 Overflow (Page 3584) -- -- -- -- -- -- 31 Switch OFF (Page 3585) -- -- -- -- -- -- 32 Switch ON (Page 3585) -- -- -- -- -- -- 33 Low free storage space (Page 3585) -- -- -- -- -- -- 34 Free space critically low (Page 3585) -- -- -- -- -- -- 35 Value change (Page 3585) -- -- -- -- -- -- 36 Time expired (Page 3586) -- -- -- -- -- -- Elements Introduction The following table shows which events occur on which objects. Technical data subject to change. Icon Object IO field Button Symbolic IO field Graphic IO field 3572 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.6 Working with system functions Icon Object Date/time field Bar Switch 1 Cleared (Page 3575) -- -- -- -- -- -- -- 2 Activate (Page 3575) X X X X -- -- X 3 Change (Page 3576) -- X X -- -- -- X 4 Loaded (Page 3576) -- -- -- -- -- -- -- 5 Execute (Page 3576) -- -- -- -- -- -- -- 6 Selection changed (Page 3577) -- -- -- -- -- -- -- 7 In the event of high limit violation (Page 3577) -- -- -- -- -- -- -- 8 In the event of low limit violation (Page 3577) -- -- -- -- -- -- -- 9 When dialog is opened (Page 3577) -- -- -- -- -- -- -- 10 When dialog is closed (Page 3578) -- -- -- -- -- -- -- 11 User change (Page 3578) -- -- -- -- -- -- -- 12 Screen change (Page 3578) -- -- -- -- -- -- -- 13 Deactivate (Page 3578) X X X X -- -- X 14 Double-click (Page 3579) -- -- -- -- -- -- -- 15 Press (Page 3579) -- X -- -- -- -- -- 16 On Finish Input (Page 3580) -- -- -- -- -- -- -- 17 Press ESC twice (Page 3580) -- -- -- -- -- -- -- 18 Outgoing (Page 3580) -- -- -- -- -- -- -- 19 Incoming (Page 3581) -- -- -- -- -- -- -- 20 Click (Page 3581) -- X -- -- -- -- -- 21 Click when flashing (Page 3581) -- -- -- -- -- -- -- 22 Loop-in alarm (Page 3582) -- -- -- -- -- -- -- 23 Release (Page 3582) -- X -- -- -- -- -- 24 Alarm buffer overflow (Page 3582) -- -- -- -- -- -- -- 25 Acknowledge (Page 3583) -- -- -- -- -- -- -- 26 Reach margin (Page 3583) -- -- -- -- -- -- -- 27 Runtime Stop (Page 3583) -- -- -- -- -- -- -- 28 Press key (Page 3584) -- -- -- -- -- -- -- 29 Release key (Page 3584) -- -- -- -- -- -- -- 30 Overflow (Page 3584) -- -- -- -- -- -- -- 31 Switch OFF (Page 3585) -- -- -- -- -- -- X 32 Switch ON (Page 3585) -- -- -- -- -- -- X 33 Low free storage space (Page 3585) -- -- -- -- -- -- -- 34 Free space critically low (Page 3585) -- -- -- -- -- -- -- 35 Value change (Page 3585) -- -- -- -- -- -- -- 36 Time expired (Page 3586) -- -- -- -- -- -- -- WinCC Basic V13.0 System Manual, 02/2014 3573 Visualize processes 10.6 Working with system functions 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 Recipe view Auxiliary indicator 1 Cleared (Page 3575) -- -- -- -- -- -- 2 Activate (Page 3575) X -- X X -- -- 3 Change (Page 3576) -- -- -- -- -- -- 4 Loaded (Page 3576) -- -- -- -- -- -- 5 Execute (Page 3576) -- -- -- -- -- -- 6 Selection changed (Page 3577) -- -- -- -- -- -- 7 In the event of high limit violation (Page 3577) -- -- -- -- -- -- 8 In the event of low limit violation (Page 3577) -- -- -- -- -- -- 9 When dialog is opened (Page 3577) -- -- -- -- -- -- 10 When dialog is closed (Page 3578) -- -- -- -- -- -- 11 User change (Page 3578) -- -- -- -- -- -- 12 Screen change (Page 3578) -- -- -- -- -- -- 13 Deactivate (Page 3578) X -- X X -- -- 14 Double-click (Page 3579) -- -- -- -- -- -- 15 Press (Page 3579) -- -- -- -- -- -- 16 On Finish Input (Page 3580) -- -- -- -- -- -- 17 Press ESC twice (Page 3580) -- -- -- -- -- -- 18 Outgoing (Page 3580) -- -- -- -- -- -- 19 Incoming (Page 3581) 20 Click (Page 3581) -- X -- -- -- -- 21 Click when flashing (Page 3581) -- X -- -- -- -- 22 Loop-in alarm (Page 3582) -- -- -- -- -- -- 23 Release (Page 3582) -- -- -- -- -- -- 24 Alarm buffer overflow (Page 3582) -- -- -- -- -- -- 25 Acknowledge (Page 3583) -- -- -- -- -- -- 26 Reach margin (Page 3583) -- -- -- -- -- -- 3574 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.6 Working with system functions 27 Runtime Stop (Page 3583) -- -- -- -- -- -- 28 Press key (Page 3584) -- -- -- -- -- -- 29 Release key (Page 3584) -- -- -- -- -- -- 30 Overflow (Page 3584) -- -- -- -- -- -- 31 Switch OFF (Page 3585) -- -- -- -- -- -- 32 Switch ON (Page 3585) -- -- -- -- -- -- 33 Low free storage space (Page 3585) -- -- -- -- -- -- 34 Free space critically low (Page 3585) -- -- -- -- -- -- 35 Value change (Page 3585) -- -- -- -- -- -- 36 Time expired (Page 3586) -- -- -- -- -- -- 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 Note that the availability of the event depends on 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 "Enable" event is only used to detect whether an object was selected. The event does not trigger a password prompt. WinCC Basic V13.0 System Manual, 02/2014 3575 Visualize processes 10.6 Working with system functions For this reason, do not use the "Enable" event if you want to configure access protection on the function call of the object. Change 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 Note that the availability of the event depends on the HMI device and object type. 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. 3576 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.6 Working with system functions 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. In the event of high limit violation Description Occurs when the high limit of a tag is exceeded. Note Note that the availability of the event depends on the HMI device and object type. In the event of low limit violation Description Occurs when the low limit of a tag is undershot. Note Note that the availability of the event depends on 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. WinCC Basic V13.0 System Manual, 02/2014 3577 Visualize processes 10.6 Working with system functions 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. 3578 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.6 Working with system functions 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. WinCC Basic V13.0 System Manual, 02/2014 3579 Visualize processes 10.6 Working with system functions 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 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 Note that the availability of the event depends on 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. 3580 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.6 Working with system functions 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. 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. Click when flashing Description Occurs when the user clicks a flashing alarm indicator with the mouse or touches it with a finger. Note Note that the availability of the event depends on the HMI device and object type. WinCC Basic V13.0 System Manual, 02/2014 3581 Visualize processes 10.6 Working with system functions Loop-in alarm Description Occurs as soon as the user selects an alarm in the alarm view and then clicks on the "LoopIn-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. 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. 3582 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.6 Working with system functions 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 Note that the availability of the event depends on the HMI device and object type. 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. WinCC Basic V13.0 System Manual, 02/2014 3583 Visualize processes 10.6 Working with system functions Press key Description Occurs when the user presses a function key. Note Please note that the availability of the event is dependent upon the HMI device and object type. Release key Description Occurs when the user releases a function key. Note Note that the availability of the event depends on 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. 3584 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.6 Working with system functions Switch OFF Description Occurs when the user moves the display and operating object "Switch" to the OFF position. Note Note that the availability of the event depends on 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 Note that the availability of the event depends on 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 a tag or the value of an array element changes. WinCC Basic V13.0 System Manual, 02/2014 3585 Visualize processes 10.7 Planning tasks The value change of a tag is triggered by the PLC or by the user, e.g. when a new value is entered. No event is output if a system function changes the value. Note Please note that the availability of the event depends on 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. 10.7 Planning tasks 10.7.1 Field of application of the Scheduler Definition You can use the Scheduler to configure tasks to run independent of the screen in the background. You create tasks by linking system functions or scripts to a trigger. The linked functions will be called when the triggering event occurs. Example of an application The Scheduler is used to execute event-controlled tasks automatically. For example, you use a task to automate the following: Regular swap out of log data Printout of an alarm report when an alarm buffer overflow occurs Printout of a report at shift end Monitoring a tag Monitoring of a user change 3586 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.7 Planning tasks Note The availability of the listed examples is determined by the HMI device. See also Working with tasks and triggers (Page 3588) Example: Update user following change of user (Page 3593) Work area of the "Scheduler" editor (Page 3589) WinCC Basic V13.0 System Manual, 02/2014 3587 Visualize processes 10.7 Planning tasks 10.7.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. See also Field of application of the Scheduler (Page 3586) 3588 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.7 Planning tasks 10.7.3 Basics 10.7.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. WinCC Basic V13.0 System Manual, 02/2014 3589 Visualize processes 10.7 Planning tasks Inspector window The "Properties" tab of the Inspector window is split into two parts. The "Job" area lists the name of the job and the job type. The "Starting time" area shows the trigger. The area is different depending on the trigger selected. In the "Events" tab use the function list with system functions that will be executed in the task. Note You can obtain more detailed information about the elements of the user interface using the tooltips. To do so, move the mouse pointer to the relevant object or press <F1> if the object has already been selected. See also Field of application of the Scheduler (Page 3586) Planning tasks with event triggers (Page 3591) Triggers (Page 3590) Function list (Page 3590) 10.7.3.2 Function list Function list A trigger starts the function list. The function list is executed line by 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. See also Work area of the "Scheduler" editor (Page 3589) 10.7.3.3 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. 3590 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.7 Planning tasks Event trigger When a task is linked to a system event, the task will be triggered by the event. System events include, for example, Runtime stop, screen change, user change, etc. Each system event can only be configured once for each HMI device. Deactivating job If you do not need a certain job temporarily, deactivate the job in the Engineering System. You also use the trigger "Deactivated" to make a previously configured system event available once again. Example: Task "A" is planned with the system event "Shutdown". This system event is then no longer available for another task "B". Select "Disabled" as the trigger for task "A" to make the "Runtime stop" system event available again. Note The available triggers depend on the HMI device. See also Work area of the "Scheduler" editor (Page 3589) 10.7.3.4 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". WinCC Basic V13.0 System Manual, 02/2014 3591 Visualize processes 10.7 Planning tasks 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. See also Work area of the "Scheduler" editor (Page 3589) 3592 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.7 Planning tasks 10.7.4 Examples 10.7.4.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 > Properties > General": - Select "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". WinCC Basic V13.0 System Manual, 02/2014 3593 Visualize processes 10.7 Planning tasks 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. See also Field of application of the Scheduler (Page 3586) 3594 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs 10.8 Communicating with PLCs 10.8.1 Basics of communication 10.8.1.1 Communication between devices Communication Data exchange between devices is known as communication. The devices can be interconnected directly or via a network. The interconnected devices in communication are referred to as communication partners. +0,GHYLFH +0,GHYLFH 3/& Data transferred between the communication partners may serve different purposes: Display processes Operate processes Output alarms Administer process parameters and machine parameters Communication partners Communication between the following devices is described in more detail in this section: PLC The PLC controls a process by means of a user program. HMI device You use the HMI device to operate and monitor the process. WinCC Basic V13.0 System Manual, 02/2014 3595 Visualize processes 10.8 Communicating with PLCs Basic information for all communication The basis for all types of communication is a network configuration. In a network configuration, you specify the connection that exists between the configured devices. With the network configuration, you also ensure the necessary prerequisites for communication, in other words: Every device in a network is assigned a unique address. The devices carry out communication with consistent transmission characteristics. Automation system The following characteristics describe an automation system: The PLC and HMI device are interconnected The network between the PLC and HMI device is configured Communication between HMI devices The HTTP protocol is available for communication between HMI devices. For more detailed information, refer to the documentation on the SIMATIC HMI HTTP protocol. Communication via a uniform and vendor-neutral interface With OPC (Openess Productivity Collaboration), WinCC has a uniform and manufacturerneutral software interface. This interface enables standardized data exchange between industrial, office, and manufacturing applications. For more detailed information, refer to the documentation for OPC. 10.8.1.2 Devices and networks in the automation system Introduction To set up an automation system, you must configure, parameterize, and interconnect the individual devices. You insert PLCs and HMI devices into the project in the same way. Likewise, you configure the two devices in the same way. Automation system setup: 1. Insert PLC into the project. 2. Insert HMI device into the project. 3. Network the devices together. 4. Interconnect the devices. 3596 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs Inserting devices If you have created a project, you can add a device in the portal view or project view. WinCC Basic V13.0 System Manual, 02/2014 3597 Visualize processes 10.8 Communicating with PLCs Portal view Project view 3598 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs WinCC Basic V13.0 System Manual, 02/2014 3599 Visualize processes 10.8 Communicating with PLCs Networking devices You can network the interfaces of the communication-capable devices conveniently in the "Devices & Networks" editor. In the networking step, you configure the physical device connections. The tabular network overview supplements the graphical network view with the following additional functions: You obtain detailed information on the structure and parameter settings of the devices. Using the "Subnet" column, you can connect communication-capable components to subnets that have been created. 3600 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs Connecting devices After you network the devices together, you configure the connection. You configure the "HMI connection" connection type for communication with the HMI device. 10.8.1.3 Data exchange using tags Communication using tags Process values are forwarded in runtime using tags. Process values are data which is stored in the memory of one of the connected automation systems. They represent the status of a plant in the form of temperatures, fill levels or switching states, for example. Define external tags for processing the process values in WinCC. WinCC works with two types of tag: External tags Internal tags Working with tags See the chapter "Working with tags (Page 3337)" for further information about configuring tags. WinCC Basic V13.0 System Manual, 02/2014 3601 Visualize processes 10.8 Communicating with PLCs 10.8.1.4 Data exchange using area pointers Communication using area pointers Area pointers are parameter fields. WinCC receives information from these parameter fields in Runtime during the course of the project. This information contains data on the location and size of data areas in the PLC. During communication, the PLC and the HMI device alternately access these data areas for read and write operations. Based on the evaluation of data stored in the data areas, the PLC and HMI device initiate mutually defined actions. The area pointers are managed centrally in the "Connections" editor. Area pointers are used to exchange data from specific user data areas. You use the following area pointers in WinCC: Data record Date/time Coordination Job mailbox Date/time PLC Project ID Screen number The availability of the various area pointers is determined by the HMI device used. 10.8.1.5 Communication drivers Communication drivers A communication driver is a software component that establishes a connection between a PLC and an HMI device. The communication driver thus enables the assignment of process values to HMI tags. The interface as well as the profile and transmission speed can be chosen, depending on the HMI device used and the connected communication partner. 3602 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs 10.8.2 Editors for communication 10.8.2.1 "Devices & networks" editor Function of the hardware and network editor The "Devices & networks" editor is the development environment for networking, configuring and assigning parameters to devices and modules. Configuration The "Devices & networks" editor consists of the following components: 1 2 3 WinCC Basic V13.0 System Manual, 02/2014 Device view, network view, topology view Hardware catalog Inspector window 3603 Visualize processes 10.8 Communicating with PLCs The "Devices & networks" editor provides you with three different 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 or topology view. 10.8.2.2 Network view Introduction The network view is a working area of the hardware and network editor. You undertake the following tasks in network view: Configuring and assign device parameters Networking devices with one another 3604 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs Structure The following diagram shows the components of the network view: 1 Changeover switch: network view/device view/topology view 2 Toolbar of network view 3 Graphic area of network view 4 Overview navigation 5 Table area of network view You can use your mouse to change the spacing between the graphic and table areas of the network view. To do this, click on the upper edge of the table view and expand or contract this by moving the mouse with the mouse button held down. You can use the two small arrow keys to minimize, maximize or select the latest table structure of the table view with just one click. WinCC Basic V13.0 System Manual, 02/2014 3605 Visualize processes 10.8 Communicating with PLCs Toolbar The toolbar provides the following functions: Icon Meaning Mode to network devices. Mode to create connections. You can select the connection type using the adjacent drop-down list. Mode to create relations. Show interface addresses. Adjust the zoom setting. You can select the zoom setting or enter it directly in the adjacent drop-down list. You can also zoom in or zoom out the view in steps using the zoom symbol or draw a frame around an area to be zoomed in. Show page breaks Enables the page break preview. Dashed lines will be displayed at the positions where the pages will break when printed. Remember layout Saves the current table view. The layout, width and visibility of columns in the table view is stored. Graphic area The graphic area of the network view displays any network-related devices, networks, connections and relations. In this area, you add devices from the hardware catalog, connect them with each other via their interfaces and configure the communication settings. Overview navigation Click in the overview navigation to obtain an overview of the created objects in the graphic area. By holding down the mouse button, you can quickly navigate to the desired objects and display them in the graphic area. Table area The table area of the network view includes various tables for the devices, connections and communication settings present: Network overview Connections I/O communication You can use the shortcut menu of the title bar of the table to adjust the tabular display. 3606 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs 10.8.2.3 Network data Introduction The "Network view" editor also gives you a tabular view of the "Network data" in addition to the graphic network view. You have the following selections in the "Network data" editor: Network overview Connections VPN I/O communication You open the "Network data" below the graphic network overview. Basic functions The network data are displayed in tabular form and support 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. WinCC Basic V13.0 System Manual, 02/2014 3607 Visualize processes 10.8 Communicating with PLCs Network overview 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. The Connections You will find additional network data under "Connections". 3608 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs 10.8.2.4 Diagnostics of online connections Diagnostics of online connections You can read out the diagnostics data of existing connections in the TIA Portal. The "Diagnostics" function shows the connection data in tabular form in the Inspector window. Requirements Devices must be in "Online" mode. Device information The diagnostics data of all devices in "Online" mode is displayed in the "Diagnostics > Device information" Inspector window. The following data is displayed: Online status Operating mode Device / module Alarm Details Help WinCC Basic V13.0 System Manual, 02/2014 3609 Visualize processes 10.8 Communicating with PLCs Connection information Use the "Connection information" function to display the diagnostics data of the connection selected in the "Devices&Networks" editor. A graphic displays the communication partners of the connection and by which communication driver they are connected with each other. The following data is displayed: End point Interface Subnet Address TSAP Number of HMI resources 10.8.2.5 Device view Introduction The device view is a working area of the hardware and network editor. You undertake the following tasks in the device view: Configuring and assign device parameters Configuring and assign module parameters 3610 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs Structure The following diagram shows the components of the device view: 1 Changeover switch: network view/device view/topology view 2 Toolbar of device view 3 Graphic area of the device view 4 Overview navigation 5 Table area of device view You can use your mouse to change the spacing between the graphic and table areas of the device view. To do this, click on the upper edge of the table view and expand or contract this by moving the mouse with the mouse button held down. You can use the two small arrow keys to minimize, maximize or select the latest table structure of the table view with just one click. WinCC Basic V13.0 System Manual, 02/2014 3611 Visualize processes 10.8 Communicating with PLCs Toolbar The toolbar provides the following functions: Icon Meaning Switches to the network view. Note: The device view can switch between the existing devices using the drop-down list. Show the area of unplugged modules. Show module labels. Adjust the zoom setting. Select the zoom setting or enter it directly in the adjacent drop-down list. You can use the Zoom button to zoom in or out incrementally or to drag a frame around an area to be enlarged. You can read the address descriptions of the I/O channels of signal modules at a zoom level setting of 200% or higher. Show page breaks Enables the page break preview. Dashed lines will be displayed at the positions where the pages will break when printed. Remember layout Saves the current table view. The layout, width and visibility of columns in the table view is stored. Graphic area The graphic area of the device view displays hardware components and if necessary the associated modules that are assigned to each other via one or more racks. In the case of devices with racks, you have the option of installing additional hardware objects from the hardware catalog into the slots on the racks. Overview navigation Click in the overview navigation to obtain an overview of the created objects in the graphic area. By holding down the mouse button, you can quickly navigate to the desired objects and display them in the graphic area. Table area The table area of the device view gives you an overview of the modules used and the most important technical and organizational data. You can use the shortcut menu of the title bar of the table to adjust the tabular display. 10.8.2.6 Topology view Introduction The topology view is a working area of the hardware and network editor. 3612 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs You undertake the following tasks in topology view: Displaying the Ethernet topology Configuring the Ethernet topology Identify and minimize differences between the desired and actual topology Structure The following figure provides an overview of the topology view. 1 Changeover switch: device view / network view / topology view 2 Topology view toolbar 3 Graphic area of the topology view 4 Overview navigation 5 Table area of the topology view You can use your mouse to change the spacing between the graphic and table areas of the topology view. WinCC Basic V13.0 System Manual, 02/2014 3613 Visualize processes 10.8 Communicating with PLCs To do this, click on the upper edge of the table view and expand or contract this by moving the mouse with the mouse button held down. You can use the two small arrow keys to minimize, maximize or select the latest table structure of the table view with just one click. Toolbar The toolbar provides the following functions: Icon Meaning Adjust the zoom setting. You can select the zoom setting via the adjacent drop-down list or enter it directly. You can also zoom in or zoom out the view in steps using the zoom symbol or draw a frame around an area to be zoomed in. Show page breaks Enables the page break preview. Dashed lines will be displayed at the positions where the pages will break when printed. Remember layout Saves the current table view. The layout, width and visibility of columns in the table view is stored. Graphic area The graphic area of the topology view displays Ethernet modules with their appropriate ports and port connections. Here you can add additional hardware objects with Ethernet interfaces. Overview navigation Click in the overview navigation to obtain an overview of the created objects in the graphic area. By holding down the mouse button, you can quickly navigate to the desired objects and display them in the graphic area. Table area This displays the Ethernet or PROFINET modules with their appropriate ports and port connections in a table. This table corresponds to the network overview table in the network view. You can use the shortcut menu of the title bar of the table to adjust the tabular display. 10.8.2.7 Inspector window The properties and parameters shown for the object selected can be edited in the inspector window. 3614 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs Structure The inspector window consists of the following components: 1 Switch between various information and work areas 2 Navigation between various pieces of information and parameters 3 Display showing the selected information and parameters Function The information and parameters in the inspector window are split into different types of information: Properties Info Diagnostics To display the corresponding information and parameters, click in the area you want. The "Properties" area is the most important one for configuring an automation system. This area is displayed by default. The left pane of the inspector window is used for area navigation. Information and parameters are arranged there in groups. If you click on the arrow symbol to the left of the group name, you can expand the group if sub-groups are available. If you select a group or sub-group, the corresponding information and parameters are displayed in the right pane of the inspector window and can be edited there too. WinCC Basic V13.0 System Manual, 02/2014 3615 Visualize processes 10.8 Communicating with PLCs 10.8.2.8 Hardware catalog The "Hardware catalog" task card gives you easy access to a wide range of hardware components. 3616 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs Structure The "Hardware catalog" task card consists of the following panes: 1 2 3 1 "Catalog" pane, search and filter function 2 "Catalog" pane, component selection 3 "Information" pane WinCC Basic V13.0 System Manual, 02/2014 3617 Visualize processes 10.8 Communicating with PLCs Search and filter function The search and filter functions of the "Catalog" pane make it easy to search for particular hardware components. You can limit the display of the hardware components to certain criteria using the filter function. For example, you can limit the display to objects that you can also place within the current context or which contain certain functions. Objects that can be used in the current context include, for example, interconnectable objects in the network view or only modules compatible with the device in the device view. Component selection The component selection in the "Catalog" pane contains the installed hardware components in a tree structure. You can move the devices or modules you want from the catalog to the graphic work area of the device or network view. Installed hardware components without a license are grayed out. You cannot use non-licensed hardware components. Hardware components belonging to various components groups thematically are partially implemented as linked objects. When you click on such linked hardware components, a catalog tree opens in which you can find the appropriate hardware components. Information The "Information" pane contains detailed information on the object selected from the catalog: Schematic representation Name Order number Version number Description 10.8.2.9 Information on hardware components In the hardware catalog, you can display information on selected hardware components in the "Information" pane. You can also display further information on the selected hardware components using the shortcut menu. Access to further information If you select a hardware object in the hardware catalog and open the shortcut menu, you not only have the "Copy" function available but also three options for accessing information on Service & Support: Information regarding product support FAQs Manuals 3618 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs The required information is displayed in the work area of the hardware and network editor. Note You can only access Service & Support when you are connected to the Internet and the function is enabled. By default, the function is disabled. To enable the function, refer to the instructions in the section "Enabling product support". Information regarding product support Here, you have access to general information on hardware and software components. The order number of the selected hardware object is entered automatically in the search mask. You can, however, also search for other hardware and software components. FAQs Here, you have access to "Frequently Asked Questions" (FAQs). You can view various entries on hardware and software questions. Using a detailed search mask, you can filter the required topics. Manuals Here, you have access to the manuals of the various hardware components. This is particularly useful if the configuration, addressing or parameter assignment you are planning requires more detailed knowledge of the hardware you are using. 10.8.3 Networks and connections 10.8.3.1 SIMATIC communication networks Communication networks Overview Communication networks are a central component of modern automation solutions. Industrial networks have to fulfill special requirements, for example: Coupling of automation systems as well as simple sensors, actuators, and computers. The information has to be correct and has to be transferred at the right moment. Robust against electromagnetic disturbances, mechanical stresses and soiling Flexible adaptation to the production requirements Industrial networks belong to the LANs (Local Area Networks) and allow communication within a limited area. WinCC Basic V13.0 System Manual, 02/2014 3619 Visualize processes 10.8 Communicating with PLCs Industrial networks fulfill the following communication functions: Process and field communication of the automation systems including sensors and actuators Data communication between automation systems IT communication for integrating the modern information technology Overview of the networks This section examines the following networks: Industrial Ethernet The industrial network standard for all levels PROFINET The open Industrial Ethernet standard for automation PROFIBUS The international standard for the field area and market leader at the field busses MPI The integrated interface of the SIMATIC products PPI The integrated interface specially for the S7-200 PROFINET Industrial Ehernet PROFIBUS 3620 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs PROFINET and Ethernet Industrial Ethernet Industrial Ethernet, which is based on IEEE 802.3, enables you to connect your automation system to your office networks. Industrial Ethernet provides IT services that you can use to access production data from the office environment. Ethernet network An Ethernet network allows you to interconnect all devices that are connected to the network via an integrated Ethernet interface or a communication module. This enables connection of multiple HMI devices to one SIMATIC S7 PLC and multiple SIMATIC S7 PLCs to one HMI device. The maximum number of communication partners that you can connect to an HMI device is dependent on the HMI device used. Additional information is available in the documentation for the respective HMI device. PROFINET PROFINET is an open standard for industrial automation defined by IEEE 61158 and based on Industrial Ethernet. PROFINET makes use of IT standards all the way to the field level and enables plant-wide engineering. With PROFINET, you can realize high-performance automation solutions for applications with stringent real-time requirements. PROFIBUS PROFIBUS DP PROFIBUS DP (distributed I/O) is used to connect the following devices: PLCs, PCs, HMI devices Distributed I/O devices, e.g., SIMATIC ET 200 Valves Drives PROFIBUS DP's fast response times make it ideally suited for the manufacturing industry. Its basic functionality includes cyclic exchange of process data between the master and PROFIBUS DP slaves, as well as diagnostics. PROFIBUS network You can connect an HMI device within the PROFIBUS network to any SIMATIC S7 module that has an integrated PROFIBUS or PROFIBUS DP interface. You can thereby connect multiple HMI devices to one SIMATIC S7 PLC and multiple SIMATIC S7 PLCs to one HMI device. WinCC Basic V13.0 System Manual, 02/2014 3621 Visualize processes 10.8 Communicating with PLCs The maximum number of communication partners that you can connect to an HMI device is dependent on the HMI device used. Additional information is available in the documentation for the respective HMI device. You configure the SIMATIC S7-200 PLC as a passive device in the network. You connect the SIMATIC S7-200 using the DP connector or a PROFIBUS communication module. MPI MPI MPI (Multi-Point Interface) is the integrated interface for SIMATIC products: PLCs HMI devices Programming device/PC Small subnets with the following characteristics are set up with MPI: Short distances Few devices Small data quantities MPI network You connect the HMI device to the MPI interface of the SIMATIC S7 PLC. This enables connection of multiple HMI devices to one SIMATIC S7 PLC and multiple SIMATIC S7 PLCs to one HMI device. The maximum number of communication partners that you can connect to an HMI device is dependent on the HMI device used. Additional information is available in the documentation for the respective HMI device. Network architectures MPI is based on the PROFIBUS standard (IEC 61158 and EN 50170) and supports the following bus topologies: Line Star Tree An MPI subnet contains a maximum of 127 devices and consists of multiple segments. Each segment contains a maximum of 32 devices and is limited by terminating resistors. Repeaters are used to connect segments. The maximum cable length without a repeater is 50 m. 3622 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs PPI Introduction PPI (point-to-point interface) is an integrated interface that was developed specially for the SIMATIC S7-200. A PPI network typically connects S7-200 PLCs. However, other SIMATIC PLCs (e.g., S7-300 and S7-400) or HMI devices can communicate with a SIMATIC S7-200 in the PPI network. PPI network A PPI connection is a point-to-point connection. The HMI device is the master. The SIMATIC S7-200 is the slave. You can connect a maximum of one SIMATIC S7-200 to an HMI device. You use the serial connector of the CPU to connect the HMI device. You can connect multiple HMI devices to one SIMATIC S7-200. From the perspective of the SIMATIC S7-200, only one connection at a time is possible. Note The PPI network can contain a maximum of four masters in addition to the HMI device. For performance reasons, do not configure more than four devices at a time as a master in the PPI network. Network architectures PPI is based on the PROFIBUS standard (IEC 61158 and EN 50170) and supports the following bus topologies: Line Star Multi-master networks with a maximum of 32 masters are set up with PPI: An unlimited number of masters can communicate with each slave. A slave can be assigned to multiple masters. The RS 485 repeater can be used to extend the PPI network. Modems can also be connected to the PPI network. WinCC Basic V13.0 System Manual, 02/2014 3623 Visualize processes 10.8 Communicating with PLCs 10.8.3.2 Configuring networks and connections Networking devices Introduction The "Devices & Networks" editor is provided for configuring connections. You can network devices in the editor. You can also configure and assign parameters to devices and interfaces. You then configure the required connections between the networked devices. In the "Devices & Networks" editor you configure HMI connections with the PLCs: SIMATIC S7 1500 SIMATIC S7 1200 SIMATIC S7 300 SIMATIC S7 400 You configure the HMI connections to other PLCs in the "Connections" editor of the respective HMI device. Networking devices The network view of the "Devices & Networks" editor includes a graphical area and a tabular area. You can use the graphical area to network the devices in the project with drag-and-drop. The tabular area provides an overview of the devices and their components. You can network the following PLCs together with HMI devices in the "Devices & Networks" area. SIMATIC S7 1500 SIMATIC S7 1200 SIMATIC S7 300 SIMATIC S7 400 All other PLCs are available in the TIA-Portal and are configured "not integrated". You configure "not integrated" connections in the "Connections" editor of the HMI device. 3624 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs With the networking step, you configure the physical connection of the communication partners. The networking of devices is depicted by lines that are colored according to the interface. Configuring an integrated connection in the "Devices & Networks" editor Introduction You configure an HMI connection between the HMI device and a SIMATIC S7 PLC in the "Devices & Networks" editor. This HMI connection is the direct connection between the communication partners that you have created in a project. Integrated connections Connections of devices within a project are referred to as integrated connections. In the case of integrated connections, you can directly configure addresses of PLC tags. Note An HMI connection can be configured in the "Devices & Networks" editor for the following PLCs only: SIMATIC S7 1500 SIMATIC S7 1200 SIMATIC S7 300 SIMATIC S7 400 You configure the HMI connections to all other PLCs in the "Connections" editor of the HMI device. WinCC Basic V13.0 System Manual, 02/2014 3625 Visualize processes 10.8 Communicating with PLCs Configuring an HMI connection in the "Devices & Networks" editor 1. Insert an HMI device and a SIMATIC S7 PLC in your project. 2. Switch to "Connections" mode. 3. Select the "HMI connection" connection type. 3626 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs 4. Use a drag-and-drop operation to interconnect the two PROFINET interfaces. 5. Change the IP address and subnet mask address parameters according to the requirements of your project. Special considerations of the "Devices & Networks" editor Introduction If you are configuring or have already configured networks or HMI connections, the "Devices & Networks" editor supports you with the following functions: Highlighting of communication partners Highlighting of HMI connections Automatic creation of subnets Highlighting of communication partners All communication partners for which an HMI connection is possible are highlighted in turquoise if you have selected the "HMI connection" type. Starting from the interface of a device create an HMI connection to the device of another device using a drag-and-drop operation. During the drag-and-drop operation all potential communication partners are highlighted in turquoise. Use the ESC key to stop connecting interfaces using a drag-and-drop operation. WinCC Basic V13.0 System Manual, 02/2014 3627 Visualize processes 10.8 Communicating with PLCs When the mouse pointer is moved over the interface of a device, the following icons indicate whether a connection is possible: A connection is possible. A connection is not possible. 3628 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs Highlighting of HMI connections A turquoise highlighting of the connection indicates that a HMI connection was created. If several HMI connections are created, you can select one of the already created HMI connections in a dialog. Then you can configure the parameters of the selected HMI connection and the communication partners in the inspector window. Subnets Subnetworks are automatically created and used under the following conditions: If both communication partners are not already interconnected in different networks If a free interface is available to both communication partners. If a subnetwork already exists then that subnetwork is automatically used for the HMI connection. Configuring a non-integrated connection in the "Connections" editor Introduction You use the "Connections" editor of the HMI device to configure a connection between an HMI device and a PLC that cannot be configured in the "Devices & Networks" editor. These connections are referred to as non-integrated connections. WinCC Basic V13.0 System Manual, 02/2014 3629 Visualize processes 10.8 Communicating with PLCs Requirements A project is open. An HMI device has been created. Configuring a connection in the "Connections" editor 1. Open the "Connections" editor of the HMI device. 2. Create a new connection. 3630 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs 3. Select the communication driver. 4. Set the connection parameters. Integrated connections in the "Connections" editor If you have already configured the integrated connections of the HMI device in the "Devices & Networks" editor, they are also displayed in the "Connections" editor. Meaning of the icons used: WinCC Basic V13.0 System Manual, 02/2014 3631 Visualize processes 10.8 Communicating with PLCs Integrated connection Non-integrated connection 10.8.4 Data exchange 10.8.4.1 Data exchange using tags Basics of tags Introduction Process values are forwarded in runtime using tags. Process values are data which is stored in the memory of one of the connected automation systems. They represent the status of a plant in the form of temperatures, fill levels or switching states, for example. Define external tags for processing the process values in WinCC. WinCC works with two types of tag: External tags Internal tags The external tags form the link between WinCC and the automation systems. The values of external tags correspond to the process values from the memory of an automation system. The value of an external tag is determined by reading the process value from the memory of the automation system. It is also possible to rewrite a process value in the memory of the automation system. ([WHUQDOWDJ 3URFHVVYDOXH :LQ&& $XWRPDWLRQV\VWHP Internal tags do not have a process link and only convey values within the WinCC. The tag values are only available as long as runtime is running. Tags in WinCC For external tags, the properties of the tag are used to define the connection that the WinCC uses to communicate with the automation system and form of data exchange. Tags that are not supplied with values by the process - the internal tags - are not connected to the automation system. In the tag's "Connection" property, this is identified by the "Internal tag" entry. 3632 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs You can create tags in different tag tables for greater clarity. You then directly access the individual tag tables in the "HMI tags" node in the project tree. The tags from all tag tables can be displayed with the help of the table "Show all tags". With structures you bundle a number of different tags that form one logical unit. Structures are project-associated data and are available for all HMI devices of the project. You use the "Types" editor in the project library to create and edit a structure. Overview of HMI tag tables Introduction HMI tag tables contain the definitions of the HMI tags that apply across all devices. A tag table is created automatically for each HMI device created in the project. In the project tree there is an "HMI tags" folder for each HMI device. The following tables can be contained in this folder: Default tag table User-defined tag tables Table of all tags In the project tree you can create additional tag tables in the HMI tags folder and use these to sort and group tags and constants. You can move tags to a different tag table using a dragand-drop operation or with the help of the "Tag table" field. Activate the "Tags table" field using the shortcut menu of the column headings. Default tag table There is one default tag table for each HMI device of the project. It cannot be deleted or moved. The default tag table contains HMI tags and, depending on the HMI device, also system tags. You can declare all HMI tags in the standard tags table or, as necessary, additional userdefined tables of tags. User-defined tag tables You can create multiple user-defined tag tables for each HMI device in order to group tags according to your requirements. You can rename, gather into groups, or delete user-defined tag tables. To group tag tables, create additional subfolders in the HMI tags folder. All tags The "All tags" table shows an overview of all HMI tags and system tags of the HMI device in question. This table cannot be deleted, renamed or moved. This table also contains the "Tags table" column, which indicates the tag table of where a tag is included. Using the "Tags table" field, the assignment of a tag to a tags table can be changed. With devices for Runtime Professional, the table "All tags" contain an additional tab "System tags". The system tags are created by the system and used for internal management of the project. The names of the system tags begin with the "@" character. System tags cannot be deleted or renamed. You can evaluate the value of a system tag, but cannot modify it. WinCC Basic V13.0 System Manual, 02/2014 3633 Visualize processes 10.8 Communicating with PLCs Additional tables The following tables are also available in an HMI tag table: Discrete alarms Analog alarms Logging tags With the help of these tables you configure alarms and logging tags for the currently selected HMI tag. Discrete alarms table In the "Discrete alarms" table, you configure discrete alarms to the HMI tag selected in the HMI tag table. When you configure a discrete alarm, multiple selection in the HMI tag table is not possible. You configure the discrete alarms for each HMI tag separately. Analog alarms table In the "Analog alarms" table, you configure analog alarms to the HMI tag selected in the HMI tag table. When you configure an analog alarm, multiple selection in the HMI tag table is not possible. You configure the analog alarms for each HMI tag separately. Logging tags table In the "Logging tags" table, you configure logging tags to the HMI tag selected in the HMI tag table. When you configure a logging tag, multiple selection in the HMI tag table is not possible. You configure the logging tags for each HMI tag separately. The "Logging tags" table is only available if the HMI device used supports logging. If WinCC Runtime Professional is used, you can also assign several log tags to a tag. With the other HMI devices, you can only assign one log tag to a tag. External tags Introduction External tags allow communication (data exchange) between the components of an automation system, for example, between an HMI device and a PLC. Principle An external tag is the image of a defined memory location in the PLC. You have read and write access to this storage location from both the HMI device and from the PLC. Since external tags are the image of a storage location in the PLC, the applicable data types depend on the PLC which is connected to the HMI device. If you write a PLC control program in STEP 7, the PLC tags created in the control program will be added to the PLC tag table. If you want to connect an external tag to a PLC tag, access the PLC tags directly via the PLC tag table and connect them to the external tag. 3634 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs Data types All the data types which are available at the connected PLC are available at an external tag in WinCC. Information about data types which are available for connection to other PLCs can be found in the documentation about the respective communication drivers. See "Auto-Hotspot" for additional information. Note As well as external tags, area pointers are also available for communication between the HMI device and PLC. You can set up and enable the area indicators in the "Connections" editor. Synchronization with PLC tags A variety of options for synchronizing external tags with the PLC tags are available in the Runtime settings under "Settings for tags". When you perform synchronization, you have the option of automatically applying the tag names of the PLC to external tags and reconnecting the existing tags. The generated tag name is derived from the position of the data value in the hierarchical structure of the data block. Update of tag values For external tags, the current tag values are transmitted in runtime via the communication connection between WinCC and the connected automation systems and then saved in the runtime memory. Next, the tag value will be updated to the set cycle time. For use in the runtime project, WinCC accesses tag values in the runtime memory that were read from the PLC at the previous cycle time. As a result, the value in the PLC can already change whilst the value from the runtime memory is being processed. Note PLC array elements in conjunction with S7-1200 or S7-1500 The index of the PLC array elements can begin with any number. In WinCC, indexing always starts with 0. A PLC tag "Array [1..3] of Int", for example, is mapped to "Array [0..2] of Int" in WinCC. When you access an array in a script, pay attention to the correct indexing. WinCC Basic V13.0 System Manual, 02/2014 3635 Visualize processes 10.8 Communicating with PLCs Addressing external tags Introduction The options for addressing external tags depend on the type of connection between WinCC and the PLC in question. A distinction must be made between the following connection types: Integrated connection Connections of devices which are within a project and were created with the "Devices & Networks" editor are referred to as integrated connections. Non-integrated connection Connections of devices which were created with the "Connections" editor are referred to as non-integrated connections. It is not necessary that all of the devices be within a single project. The connection type can also be recognized by its icon. Integrated connection Non-integrated connection You can find additional information in the section "Basics of communication (Page 3595)". Addressing with integrated connections An integrated connection offers the advantage that you can address a tag both symbolically and absolutely. For symbolic addressing, you select the PLC tag via its name and connect it to the HMI tag. The valid data type for the HMI tag is automatically selected by the system. You have to distinguish between the following cases when you address elements in data blocks: Symbolic addressing of data blocks with optimized access and standard access: During the symbolic addressing of a data block with optimized access and standard access, the address of an element in the data block is dynamically assigned and is automatically adopted in the HMI tag in the event of a change. You do not need to compile the connected data block or the WinCC project for this step. For data blocks with optimized access, only symbolic addressing is available. For symbolic addressing of elements in a data block, you only need to recompile and reload the WinCC project in case of the following changes: If the name or the data type of the linked data block element or global PLC tag has changed. If the name or the data type of the higher level structure node of a linked element in the data block element or global PLC tag has changed. If the name of the connected data block has changed. Symbolic addressing is currently available with the following PLCs: SIMATIC S7 1200 SIMATIC S7 1500 Symbolic addressing is also available if you have an integrated link. 3636 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs Note Symbolic addressing is not possible if you are using the "Date/Time" area pointer. You can also use absolute addressing with an integrated connection. You have to use absolute addressing for PLC tags from a SIMATIC S7 300/400 PLC. If you have connected an HMI tag with a PLC tag and the address of the PLC tag changes, you only have to recompile the control program to update the new address in WinCC. Then you recompile the WinCC project and load it onto the HMI device. In WinCC, symbolic addressing is the default method. To change the default setting, select the menu command "Options > Settings". Select "Visualization > Tags" in the "Settings" dialog. If required, disable the "Symbolic access" option. The availability of an integrated connection depends on the PLC used. The following table shows the availability: PLC Integrated connection Comments S7 300/400 Yes The linking of tags is not checked in Runtime. If the tag address changes in the PLC and the HMI device is not compiled again and loaded, the change is not registered in runtime. S7 1200 Yes A validity check of the tag connection is performed in runtime during symbolic addressing. If an address is changed in the PLC, the change is registered and an error message is issued. In the case of absolute addressing, the following behavior applies to the S7 300/400. S7 1500 Yes A validity check of the tag connection is performed in runtime during symbolic addressing. If an address is changed in the PLC, the change is registered and an error message is issued. In the case of absolute addressing, the following behavior applies to the S7 300/400. Create an integrated connection in the "Devices & Networks" editor. If the PLC is contained in the project and integrated connections are supported, you can then also have the connection created automatically. To do this, when configuring the HMI tag, simply select an existing PLC tag to which you want to connect the HMI tag. The integrated connection is then automatically created by the system. Addressing with non-integrated connections In the case of a project with a non-integrated connection, you always configure a tag connection with absolute addressing. Select the valid data type yourself. If the address of a PLC tag changes in a project with a non-integrated connection during the course of the project, you also have to make the change in WinCC. The tag connection cannot be checked for validity in Runtime, an error message is not issued. A non-integrated connection is available for all supported PLCs. WinCC Basic V13.0 System Manual, 02/2014 3637 Visualize processes 10.8 Communicating with PLCs Symbolic addressing is not available in a non-integrated connection. With a non-integrated connection, the control program does not need to be part of the WinCC project. You can perform the configuration of the PLC and the WinCC project independently of each other. For configuration in WinCC, only the addresses used in the PLC and their function have to be known. See also Basics of communication (Page 3595) Internal Tags Introduction Internal tags do not have any connection to the PLC. Internal tags transport values within the HMI device. The tag values are only available as long as runtime is running. Principle Internal tags are stored in the memory of the HMI device. Therefore, only this HMI device has read and write access to the internal tags. You can create internal tags to perform local calculations, for example. You can use the HMI data types for internal tags. Availability depends on the HMI device being used. The following HMI data types are available: 3638 HMI data type Data format Array One-dimensional array Bool Binary tag DateTime Date/time format DInt Signed 32-bit value Int Signed 16-bit value LReal Floating-point number 64-bit IEEE 754 Real Floating-point number 32-bit IEEE 754 SInt Signed 8-bit value UDnt Unsigned 32-bit value UInt Unsigned 16-bit value USInt Unsigned 8-bit value WString Text tag, 16-bit character set WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs 10.8.4.2 Data exchange using area pointers Basic information on area pointers Introduction You use an area pointer to access a data area in the PLC. During communication, the PLC and the HMI device alternately access these data areas for read and write operations. The PLC and the HMI device trigger defined interactions based on the evaluation of stored data. For example, area pointers are required for the following data: Recipes Job mailboxes Sign-of-life monitoring Area pointer The following area pointers are supported: Area pointer Area pointers can be configured for connections. Data record Date/time Coordination Job mailbox Global area pointers of the HMI device Global area pointers can be configured to only one connection for each project. Screen number Date/time PLC Project ID Area pointers for connections Introduction Using the "Area pointer" tab of the "Connections" editor, you can configure the usage of the available area pointers. To configure the area pointers, open the "Connections" editor and open the "Area pointer" tab. WinCC Basic V13.0 System Manual, 02/2014 3639 Visualize processes 10.8 Communicating with PLCs Structure The "Area pointer" tab contains two tables of area pointers. The top part of the table contains the area pointers you can create and enable separately for each available connection. The "Global area pointers of HMI device" table contains the area pointers which are created only once in the project and can be used for only one connection. 3640 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs Use of area pointers "Area pointer" tab Before you use an area pointer, you enable it under "Connections > Area pointer". You then assign the area pointer parameters. You assign the following parameters in the "Area pointer" tab: Active Enables the area pointer. Pointer name Name of the area pointer specified by WinCC. PLC tag Here you select the PLC tag or the tag array that you have configured as the data area for the area pointer. Access mode Here you can select from the following access modes: - Symbolic access - Absolute access Address If you selected "Symbolic access", no address is entered in this field. If you selected "Absolute access", enter the address of a tag in the "Address" field. Length WinCC specifies the length of the area pointer. Acquisition cycle You specify the acquisition cycle in this field for area pointers that are read by the HMI device. Note that a very short acquisition time may have a negative impact on HMI device performance. Comment Enter a comment, for example, to describe the purpose of the area pointer. WinCC Basic V13.0 System Manual, 02/2014 3641 Visualize processes 10.8 Communicating with PLCs Accessing data areas Accessing data areas The following table shows how HMI devices and PLCs access individual data areas for read (R) or write (W) operations. Data area Required for Screen number Evaluation by the PLC in order to determine the active screen. Data record Transfer of data records with synchronization Date/time Transfer of the date and time from the HMI device to the PLC Date/time PLC Coordination HMI device PLC W R R/W R/W W R Transfer of the date and time from the PLC to the HMI device R W Requesting the HMI device status in the PLC program W R Project ID Runtime checks for consistency between the WinCC project ID and the project in the PLC R W Job mailbox Triggering of HMI device functions by the PLC program R/W R/W Configuring area pointers Configuration of area pointers Introduction You use an area pointer to access a data area in the PLC. The data area is stored in the PLC. Prior to configuring area pointers Before you use the area pointer, you must enable and parameterize it under "Connections > Area Pointer". Global data block To access the data area in the PLC, you have to create a global data block in the PLC program. The following example shows the use of a data block. Length of area pointers For area pointers with a length >= 1, you set up the data area as a tag array in a global data block or instance data block. You also have the option to use a PLC tag for area pointers with a length = 1. The configuration of the tags in a data block is dependent on the length of the area pointer you want to use. The unit for the length of an area pointer is a 16-bit word. 3642 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs If, for example, you want to use an area pointer with a length of "5", you must create an array with 5 array elements of the data type UINT in the data block. Alternative procedure Alternatively, you can also use the absolute access mode to access area pointers. Absolute access mode only works on standard PLC data blocks. Parameterizing a global data block Introduction To access the data area in the PLC, a global data block for the area pointer must be parameterized in the PLC program. Requirements A PLC is created in the project. A connection is configured between the PLC and the HMI device. The PLC program contains a global data block. Procedure 1. Open "PLC > Program blocks" in the project tree. 2. Double-click the global data block you created previously. The data block opens. 3. Enter a tag name in the "Name" column. 4. Select "Array[lo .. hi] of type" as the data type in the "Data type" column. 5. Replace the "lo" entry by the low value for the dimension of the array. 6. Replace the "hi" entry by the high value for the dimension of the array. Example: If you configure an area pointer with the length "4", enter the value "0" for "lo" and the value "3" for "hi" inside the brackets. WinCC Basic V13.0 System Manual, 02/2014 3643 Visualize processes 10.8 Communicating with PLCs 7. Replace the "type" designation with the "word" data type. The full data type for an array of 4 tags appears as follows: "Array[0 .. 3] of word". The tag array is created after the entry is confirmed. 8. Click "Compile". The project is compiled. Configuring an area pointer for a connection Introduction After you have parameterized the global data block, you now create the area pointer for the connection. Requirements The global data block has been parameterized in the PLC program. Procedure 1. Open "HMI >Connections" in the project tree. 2. Click the "Area pointer" tab. 3. Enable the required area pointer. You enable a global area pointer by selecting the connection in the "Connection" field. 4. Click the navigation button in the "PLC tag" field. The object list opens. 3644 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs 5. Navigate to the data block in the object list, and select the tag in the right window. You do not need an array tag to configure an area pointer with the length of "1". 6. Select the "Word" data type when creating the tag in the data block. If required, set additional parameters, such as the acquisition cycle, during configuration. Result The area pointer is enabled and connected to the PLC tag in the global data block. 10.8.5 Device dependency 10.8.5.1 Basic Panel Communication drivers SIMATIC communication drivers Device dependency of the Basic Panels Various communication drivers are configured for Basic Panels depending on the communication. The following tables show the communication drivers released for integrated and nonintegrated communication. There are different versions of the HMI devices within the integrated communication. WinCC Basic V13.0 System Manual, 02/2014 3645 Visualize processes 10.8 Communicating with PLCs Communication drivers for integrated communication (V11.0) HMI devices SIMATIC SIMATIC SIMATIC S7-1200 (V1) S7-1200 (V2) S7-1200 (V2.2) SIMATIC SIMATIC SIMATIC S7-1200 (V3) S7-1200 (V4) S7-1500 SIMATIC S7-300/400 KP300 Basic Yes Yes Yes Yes Yes No Yes KP400 Basic Yes Yes Yes Yes Yes No Yes KTP400 Basic PN Yes Yes Yes Yes Yes No Yes KTP600 Basic DP Yes Yes Yes Yes Yes No Yes KTP600 Basic PN Yes Yes Yes Yes Yes No Yes KTP1000 Basic DP Yes Yes Yes Yes Yes No Yes KTP1000 Basic PN Yes Yes Yes Yes Yes No Yes TP1500 Basic PN Yes Yes Yes Yes Yes No Yes Communication drivers for integrated communication (V12.0) HMI devices SIMATIC SIMATIC SIMATIC S7-1200 (V1) S7-1200 (V2) S7-1200 (V2.2) SIMATIC SIMATIC SIMATIC S7-1200 (V3) S7-1200 (V4) S7-1500 SIMATIC S7-300/400 KP300 Basic No Yes Yes Yes Yes Yes Yes KP400 Basic No Yes Yes Yes Yes Yes Yes KTP400 Basic PN No Yes Yes Yes Yes Yes Yes KTP600 Basic DP No Yes Yes Yes Yes Yes Yes KTP600 Basic PN No Yes Yes Yes Yes Yes Yes KTP1000 Basic DP No Yes Yes Yes Yes Yes Yes KTP1000 Basic PN No Yes Yes Yes Yes Yes Yes TP1500 Basic PN No Yes Yes Yes Yes Yes Yes 3646 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs Communication drivers for integrated communication (V13.0) HMI devices SIMATIC SIMATIC SIMATIC S7-1200 (V1) S7-1200 (V2) S7-1200 (V2.2) SIMATIC SIMATIC SIMATIC S7-1200 (V3) S7-1200 (V4) S7-1500 SIMATIC S7-300/400 KTP400 Basic No Yes Yes Yes Yes Yes Yes KTP700 Basic No Yes Yes Yes Yes Yes Yes KTP900 Basic No Yes Yes Yes Yes Yes Yes KTP1200 Basic No Yes Yes Yes Yes Yes Yes Communication drivers for non-integrated communication HMI devices SIMATIC S7-1200 SIMATIC S7-1500 SIMATIC S7-300/400 SIMATIC S7-200 SIMATIC LOGO! SIMATIC HTTP protocol KP300 Basic Yes Yes Yes Yes Yes No KP400 Basic Yes Yes Yes Yes Yes No KTP400 Basic PN Yes Yes Yes Yes Yes No KTP600 Basic DP Yes Yes Yes Yes Yes No KTP600 Basic PN Yes Yes Yes Yes Yes No KTP700 Basic PN Yes Yes Yes Yes Yes No KTP900 Basic PN Yes Yes Yes Yes Yes No KTP1000 Basic DP Yes Yes Yes Yes Yes No KTP1000 Basic PN Yes Yes Yes Yes Yes No TP1500 Basic PN Yes Yes Yes Yes Yes No Other communication drivers Device dependency of the Basic Panels The following table shows which communication drivers you can configure with the various Basic Panels. WinCC Basic V13.0 System Manual, 02/2014 3647 Visualize processes 10.8 Communicating with PLCs Communication drivers HMI devices OPC AllenAllenBradley Bradley EtherNet/IP DF1 Mitsubishi MC TCP/IP Mitsubishi FX Modicon Modbus TCP/IP Modicon Modbus RTU Omron Host Link KP300 Basic No Yes No Yes No Yes No No KP400 Basic No Yes No Yes No Yes No No KTP400 Basic PN No Yes No Yes No Yes No No KTP600 Basic DP No No Yes2) No Yes No Yes1) Yes KTP600 Basic PN No Yes No Yes No Yes No No KTP700 Basic PN No Yes No Yes No Yes No No KTP900 Basic PN No Yes No Yes No Yes No No KTP1000 Basic DP No No Yes2) No Yes No Yes1) Yes KTP1000 Basic PN No Yes No Yes No Yes No No TP1500 Basic PN No Yes No Yes No Yes No No 1) 2) 3648 only with RS 422-RS232 converter Order number: 6AV6 671-8XE00-0AX0 Direct communication with PLC 5 or KF2 module, otherwise only approved with RS422-RS232 converter (option). Order number: 6AV6 671-8XE00-0AX0 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs Interfaces of the Basic Panels Device dependency of the Basic Panels The following table shows which HMI device interfaces are available for the communication driver protocols. Table 10-11 Basic Panels KP300 Basic KTP600 Basic DP KP400 Basic KTP1000 Basic DP KTP400 Basic PN KTP600 Basic PN KTP700 Basic PN KTP900 Basic PN KTP1000 Basic PN TP1500 Basic PN SIMATIC S7 - PPI 1) -- MPI/DP (X2) SIMATIC S7 - MPI -- MPI/DP (X2) SIMATIC S7 - PROFIBUS -- MPI/DP (X2) SIMATIC S7 - PROFINET PROFINET (X1) -- SIMATIC HMI HTTP protocol -- -- OPC -- -- Allen-Bradley EtherNet/IP PROFINET (X1) -- Allen-Bradley DF1 -- MPI/DP (X2) 2) Mitsubishi TCP/IP PROFINET (X1) -- Mitsubishi FX -- MPI/DP (X2) (RS422) Modicon Modbus TCP PROFINET (X1) -- Modicon Modbus RTU -- MPI/DP (X2) 3) Omron Host Link -- MPI/DP (X2) (RS422) 1) 2) 3) WinCC Basic V13.0 System Manual, 02/2014 For SIMATIC S7-200 only Direct communication with PLC5 or KF2 module, otherwise only approved with RS422RS232 converter (option). Order number: 6AV6 671-8XE00-0AX0 only approved with RS 422-RS232 converter Order number: 6AV6 671-8XE00-0AX0 3649 Visualize processes 10.8 Communicating with PLCs Area pointers for Basic Panels Introduction Area pointers are parameter fields from which the HMI device obtains information about the location and size of data areas in the PLC. During communication, the PLC and the HMI device alternately access these data areas for read and write operations. Based on the evaluation of data stored in the data areas, the PLC and HMI device initiate mutually defined actions. WinCC uses the following area pointers: Job mailbox Project ID Screen number Data record Date/time Date/time PLC Coordination Availability of the area pointers The following table shows the availability of the area pointers on the HMI devices. Note that the area pointers can be used only for available communication drivers. Area pointer KP300 Basic KTP400 Basic PN KTP600 Basic PN KTP600 KTP700 KTP900 Basic DP Basic PN Basic PN KTP1000 Basic PN KTP1000 Basic DP TP1500 Basic PN Screen number Yes Yes Yes Yes Yes Yes Yes Yes Yes Data record Yes Yes Yes Yes Yes Yes Yes Yes Yes Date/time Yes Yes Yes Yes Yes Yes Yes Yes Yes Date/time PLC Yes Yes Yes Yes Yes Yes Yes Yes Yes Coordination Yes Yes Yes Yes Yes Yes Yes Yes Yes Project ID Yes Yes Yes Yes Yes Yes Yes Yes Yes Job mailbox Yes Yes Yes Yes Yes Yes Yes Yes Yes 3650 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs 10.8.6 Communicating with SIMATIC S7 1500 10.8.6.1 Communication with SIMATIC S7 1500 Introduction This section describes the communication between an HMI device and the SIMATIC S7 1500 PLC. You can configure the following communication channels for the SIMATIC S7 1500 PLC: PROFINET PROFIBUS HMI connection for communication Configure connections between the HMI device and a SIMATIC S7 1500 in the "Devices & Networks" Editor. WinCC Basic V13.0 System Manual, 02/2014 3651 Visualize processes 10.8 Communicating with PLCs 10.8.6.2 Communication via PROFINET Configuring an HMI connection Communication via PROFINET HMI connections via PROFINET If you have inserted an HMI device and a SIMATIC S7 1500 into the project, interconnect the two PROFINET interfaces in the "Devices & Networks" editor. You can also connect multiple HMI devices to a single SIMATIC S7 1500 and multiple SIMATIC S7 1500 to a single HMI device. The maximum number of communication partners that you can connect to an HMI device is dependent on the HMI device used. Additional information is available in the documentation for the respective HMI device. HMI connection in the "Devices & Networks" editor You configure the HMI connection between the PLC and the HMI device via PROFINET in the "Devices & Networks" editor. Connection in the "Connections" editor Alternatively, you configure the connection between the PLC and HMI device via PROFINET in the "Connections" editor of the HMI device. 3652 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs Configuring an HMI connection via PROFINET Introduction You configure an HMI connection between HMI devices and a SIMATIC S7 1500 via PROFINET or Ethernet in the "Devices & Networks" editor. CAUTION Communication via Ethernet In Ethernet-based communication, the end user is responsible for the security of his data network. Targeted attacks can overload the device and interfere with proper functioning. Requirements The following communication partners are created in the "Devices & Networks" editor: HMI device with PROFINET or Ethernet interface SIMATIC S7 1500 with PROFINET interface Procedure 1. Double-click the "Devices & Networks" item in the project tree. The available communication partners in the project are displayed graphically in the network view. 2. Click the "Connections" button and select "HMI connection" for the connection type. The devices available for connection are highlighted in color. WinCC Basic V13.0 System Manual, 02/2014 3653 Visualize processes 10.8 Communicating with PLCs 3. Click the PROFINET interface of the PLC and use a drag-and-drop operation to draw a connection to the PROFINET or Ethernet interface of the HMI device. 4. Click the connecting line. 5. Click "Highlight HMI connection" and select the HMI connection. The connection is displayed graphically in the Inspector window. 6. Click the communication partners in the "Network view" and change the PROFINET parameters in the Inspector window according to the requirements of your project. See the chapter "Auto-Hotspot" for additional details. Note The created HMI connection is also shown in the tabular area of the editor on the "Connections" tab. You check the connection parameters in the table. You can change the local name for the connection only in the table. Result You have created a connection between an HMI device and a SIMATIC S7 1500. The IP address and subnet mask connection parameters are configured. 3654 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs PROFINET parameters PROFINET parameters for the HMI connection PROFINET parameters for the HMI connection An overview of the configured HMI connection parameters can be found in the properties for the HMI connection. Only limited changes are possible in this Inspector window. Displaying and changing the HMI connection parameters 1. Click the HMI connection in the "Devices & Networks" editor. 2. Change the parameters of the HMI connection in the Inspector window under "Properties > General > General". "Connection" Shows the name of the HMI connection. WinCC Basic V13.0 System Manual, 02/2014 3655 Visualize processes 10.8 Communicating with PLCs "Connection path" The communication partners of the selected HMI connection and the associated PROFINET parameters are displayed in the "Connection path" area. Some of the areas displayed cannot be edited in this dialog. "End point" Displays the device name. This area cannot be edited. "Interface" Displays the selected interface of the device. You can choose between several interfaces, depending on the device. "Interface type" Displays the selected interface type. This area cannot be edited. "Subnet" Displays the selected subnet. This area cannot be edited. "Address" Displays the selected IP address of the device. This area cannot be edited. "Find connection path" button Enables the subsequent specification of connections. PROFINET parameters for the HMI device PROFINET parameters for the HMI device An overview of the configured HMI device parameters can be found in the properties for the HMI device. 3656 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs Displaying and changing PROFINET parameters of the HMI device 1. Click the HMI device in the "Devices & Networks" editor. 2. Change the parameters of the HMI device in the Inspector window under "Properties > General". "Interface networked with" In the "Interface networked with" area, select the subnet of the HMI connection via which the HMI device is connected to the network. You use the "Add new subnet" button to create a new subnet. WinCC Basic V13.0 System Manual, 02/2014 3657 Visualize processes 10.8 Communicating with PLCs "IP protocol" "Set IP address in the project" When you transfer the WinCC project to the HMI device, this IP address is set up directly in the HMI device. Note The device is automatically restarted in the case of HMI devices with the Windows CE 3.0 operating system. HMI devices with Windows CE 3.0: OP 77B TP 177B color PN/DP TP 177B mono DP OP 177B color PN/DP OP 177B mono DP Mobile Panel 177 PN Mobile Panel 177 DP TP 277 6" OP 277 6" "Subnet mask" You assign data of the subnet mask in the "Subnet mask" area. "Use IP router" If you are using an IP router, select "Use IP router" and enter the router address in the "Router address" field. "Set IP address using a different method" If the function "Set IP address using a different method" is activated, the IP address is not taken from the project. You have to enter the IP address directly in the Control Panel of the HMI device. PROFINET parameters for the PLC PROFINET parameters for the PLC An overview of the configured parameters can be found in the properties for the PLC. 3658 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs Displaying and changing PROFINET parameters of the PLC 1. Click the PLC in the "Devices & Networks" editor. 2. Change the parameters of the PLC in the Inspector window under "Properties > General > General". "Interface networked with" In the "Subnet" area, select the subnet of the HMI connection via which the PLC is connected to the network. You use the "Add new subnet" button to create a new subnet. "IP protocol" "Interface type" Depending on the HMI device type, you have various interfaces to choose from. "IP address" You assign the IP address of the HMI device in the "IP address" area. "Subnet mask" You assign data of the subnet mask in the "Subnet mask" area. If you are using an IP router, select "Use IP router" and enter the router address in the field. WinCC Basic V13.0 System Manual, 02/2014 3659 Visualize processes 10.8 Communicating with PLCs Protection of communication Security levels If you want to protect the PLC and HMI device communication, you can assign protection levels for the communication. For a SIMATIC S7-1500 CPU, you can enter multiple passwords and thereby set up different access rights for various user groups. The passwords are entered in a table, so that exactly one protection level is assigned to each password. The effect of the password is given in the "Protection" column. For the SIMATIC S7-1200 controller, several aspects need to be considered when setting protection levels. For additional information on this, see: S7-1200 protection levels Example You select the "Complete protection" protection level for a standard CPU (i.e., not an F-CPU) when configuring it. Afterwards, you enter a separate password for every protection level above it in the table. For users who do not know any of the passwords, the CPU is completely protected. Not even HMI access is possible. For users who know one of the assigned passwords, the effect depends on the table row in which the password occurs: The password in row 1 (no protection) allows access as if the CPU were completely unprotected. Users who know this password have unrestricted access to the CPU. The password in row 2 (write protection) allows access as if the CPU were write-protected. Despite knowing the password, users who know this password only have read access to the CPU. The password in row 3 (read and write protection) allows access as if the CPU were readprotected and write-protected, so that only HMI access is possible for users who know this password. Access password for the HMI connection Introduction You secure access to a PLC by assigning a password. You assign the password when you configure the password. A password is mandatory as of protection level "Complete protection". Communication to the PLC is denied if an incorrect password or no password is entered. 3660 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs Entering access password You enter the password for the PLC in the "Connections" editor. Setting port options Setting the port options Changing connection settings for the PROFINET IO port You can change the network settings for the PROFINET IO port as required. By default, the settings are made automatically. In normal situations, this guarantees problem-free communication. WinCC Basic V13.0 System Manual, 02/2014 3661 Visualize processes 10.8 Communicating with PLCs Possible settings for transmission rate / duplex Depending on the selected device, you can make the following settings for "Transmission rate / duplex": Automatic setting Recommended default setting of the port. The transmission settings are automatically "negotiated" with the peer port. The "Enable autonegotiation" option is also enabled as a default, in other words, you can use cross cables or patch cables for the connection. TP/ITP at x Mbps full duplex (half duplex) Setting of the transmission rate and the full duplex/half duplex mode. The effectiveness depends on the "Enable autonegotiation" setting: - Autonegotiation enabled You can use both cross cable and patch cable. - Autonegotiation disabled Make sure that you use the correct cable (patch cable or cross cable)! The port is also monitored with this setting. Deactivated Depending on the module type, the drop down list box can contain the "- Disabled -" option. This option, for example, allows you to prevent access to an unused port for security reasons. With this setting, diagnostic events are not generated. "Monitor" option This option enables or disables port diagnostics. Examples of port diagnostics: The link status is monitored, in other words, the diagnostics are generated during link-down and the system reserve is monitored in the case of fiber optic ports. Option "Enable autonegotiation " The autonegotiation setting can only be changed if a concrete medium (for example, TP 100 Mbps full duplex) is selected. Whether or not a concrete medium can be set depends on the properties of the module. If autonegotiation is disabled, this causes the port to be permanently specified, as for example, is necessary for a prioritized startup of the IO device. You must make sure the partner port has the same settings because with this option the operating parameters of the connected network are not detected and the data transmission rate and transmission mode can accordingly not be optimally set. Note When a local port is connected, STEP 7 makes the setting for the partner port if the partner port supports the setting. If the partner port does not accept the setting, an error message is generated. 3662 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs Wiring rules for disabled autonegotiation Requirements You have made the following settings for the port in question, for example, to accelerate the startup time of the IO device: Fixed transmission rate Autonegotiation incl. autocrossing disabled The time for negotiating the transmission rate during startup has been saved. If you have disabled autonegotiation, you must observe the wiring rules. Wiring rules for disabled autonegotiation PROFINET devices have the following two types of ports: Type of port PROFINET devices Note Switch port with crossed pin assignment For IO devices: Port 2 Crossed pin assignment means that the pin assignment for the ports for sending and receiving between the respective PROFINET devices is exchanged internally. End device port with uncrossed pin assignment For S7 CPUs with 2 ports: Ports 1 and 2 For IO devices: Port 1 - For S7 CPUs with one port: Port 1 Validity of the wiring rules The cabling rules described in the following paragraph apply exclusively for the situation in which you have specified a fixed port setting. WinCC Basic V13.0 System Manual, 02/2014 3663 Visualize processes 10.8 Communicating with PLCs Rules for cabling You can connect several IO devices in line using a single cable type (patch cable). To do this, you connect port 2 of the IO device (distributed I/O) with port 1 of the next IO device. The following graphic gives an example with two IO devices. 6ZLWFKRU 352),1(7GHYLFH 3 ,2GHYLFH 3 3 3DWFKFDEOHV ,2GHYLFH 3 3 3 3DWFKFDEOHV 6ZLWFKSRUW (QGGHYLFHSRUW Boundaries at the port Requirements To use boundaries, the respective device must have more than one port. If the PROFINET does not support boundary settings, they are not shown. Enable boundaries "Boundaries" are limits for transmission of certain Ethernet frames. The following boundaries can be set at a port: "End of discovery of accessible devices" No forwarding of DCP frames to identify accessible devices. Devices downstream from this port cannot be reached by the project tree under "Accessible devices". Devices downstream from this port cannot be reached by the CPU. "End of topology discovery" LLDP frames (Link Layer Discovery Protocol) are not forwarded for topology detection. "End of sync domain" No forwarding of sync frames transmitted to synchronize nodes within a sync domain. If you operate, for example, a PROFINET device with more than two ports in a ring, you should prevent the sync frame from being fed into the ring by setting a sync boundary (at the ports not inside the ring). Additional example: If you want to use several sync domains, configure a sync domain boundary for the port connected to a PROFINET device from the other sync domain. 3664 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs Restrictions The following restrictions must be observed: The individual check boxes can only be used if the port supports the function in question. If a partner port has been determined for the port, the following check boxes cannot be used: - "End of discovery of accessible devices" - "End of topology discovery" If autonegotiation is disabled, none of the check boxes can be used. 10.8.6.3 Communication via PROFIBUS Configuring an HMI connection Configuring an HMI connection via PROFIBUS Introduction You configure an HMI connection over PROFIBUS between HMI devices and a SIMATIC S7 1500 in the "Devices & Networks" editor. Requirements The following communication partners are created in the "Devices & Networks" editor: HMI device with MPI/DP interface SIMATIC S7 1500 with PROFIBUS interface WinCC Basic V13.0 System Manual, 02/2014 3665 Visualize processes 10.8 Communicating with PLCs Procedure 1. Double-click the "Devices & Networks" item in the project tree. The available communication partners in the project are displayed graphically in the network view. 2. Click the "Connections" button. The devices available for connection are highlighted in color. 3. Click the HMI device interface. 4. Select the "PROFIBUS" interface type in the Inspector window under "Properties > General > HMI MPIDP > Parameters". 5. Click the interface of the PLC and use a drag-and-drop operation to draw a connection to the HMI device. 6. Click the connecting line. 3666 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs 7. Click "Highlight HMI connection" and select the HMI connection. The connection is displayed graphically in the Inspector window. 8. Click the communication partners in the "Network view" and change the PROFINET parameters in the Inspector window according to the requirements of your project. See the chapter "Auto-Hotspot" for additional details. Note The created HMI connection is also shown in the tabular area of the editor on the "Connections" tab. You check the connection parameters in the table. You can change the local name for the connection only in the table. Result You have created an HMI connection over PROFIBUS between an HMI device and a SIMATIC S7 1500. Communication via PROFIBUS HMI connections via PROFIBUS If you have inserted an HMI device and a SIMATIC S7 1500 into the project, interconnect the two PROFIBUS interfaces in the "Devices & Networks" editor. WinCC Basic V13.0 System Manual, 02/2014 3667 Visualize processes 10.8 Communicating with PLCs HMI connection in the "Devices & Networks" editor You configure the HMI connection between the PLC and the HMI device via PROFIBUS in the "Devices & Networks" editor. Connection in the "Connections" editor Alternatively, you configure the connection between the PLC and HMI device in the "Connections" editor of the HMI device. PROFIBUS parameters PROFIBUS parameters for the HMI connection PROFIBUS parameters for the HMI connection An overview of the configured HMI connection parameters can be found in the properties for the HMI connection. Only limited changes are possible in this Inspector window. 3668 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs Displaying and changing the HMI connection parameters 1. Click the HMI connection in the "Devices & Networks" editor. 2. Change the parameters of the HMI connection in the Inspector window under "Properties > General > General". "Connection" Displays whether the devices are networked together. - displayed if the devices are networked together. - displayed if the devices are not networked together. "Connection path" The communication partners of the selected HMI connection and the associated PROFIBUS parameters are displayed in the "Connection path" area. Some of the areas displayed cannot be edited in this dialog. "End point" Displays the device name. This area cannot be edited. "Interface" Displays the selected interface of the device. You can choose between several interfaces, depending on the device. WinCC Basic V13.0 System Manual, 02/2014 3669 Visualize processes 10.8 Communicating with PLCs "Interface type" Displays the selected interface type. This area cannot be edited. "Subnet" Displays the selected subnet. This area cannot be edited. "Address" Displays the PROFIBUS address of the device. This area cannot be edited. "Find connection path" button Enables the subsequent specification of connections. PROFIBUS parameters for the HMI device PROFIBUS parameters for the HMI device An overview of the configured HMI device parameters can be found in the properties for the HMI device. Displaying and changing PROFINET parameters of the HMI device 1. Click the HMI device in the "Devices & Networks" editor. 2. Change the parameters of the HMI device in the Inspector window under "Properties > General > General". "Interface networked with" In the "Interface networked with" area, select the subnet of the HMI connection via which the HMI device is connected to the network. You use the "Add new subnet" button to create a new subnet. 3670 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs "Parameters" "Interface type" You assign the interface type in the "Interface type" area. Depending on the HMI device type, you have various interfaces to choose from. "Address" You assign the PROFIBUS address of the HMI device in the "Address" area. The PROFIBUS address must be unique throughout the PROFIBUS network. "Highest address" The "Highest address" area displays the highest address of the PROFIBUS network. "Transmission speed" The "Transmission speed" is determined by the slowest device connected to the network. The setting is identical throughout the network. PROFIBUS parameters for the PLC PROFIBUS parameters for the PLC An overview of the configured parameters can be found in the properties for the PLC. Displaying and changing PROFIBUS parameters of the PLC 1. Click the PLC in the "Devices & Networks" editor. 2. Change the parameters of the PLC in the Inspector window under "Properties > General > General". "Interface networked with" In the "Subnet" area, select the subnet of the HMI connection via which the PLC is connected to the network. You use the "Add new subnet" button to create a new subnet. WinCC Basic V13.0 System Manual, 02/2014 3671 Visualize processes 10.8 Communicating with PLCs "Parameters" "Interface type" Depending on the HMI device type, you have various interfaces to choose from. "Address" You assign the PROFIBUS address of the HMI device in the "Address" area. The PROFIBUS address must be unique throughout the PROFIBUS network. "Highest address" The "Highest address" area displays the highest address of the PROFIBUS network. "Transmission speed" The "Transmission speed" is determined by the slowest device connected to the network. The setting is identical throughout the network. Protection of communication Access password for the HMI connection Introduction You secure access to a PLC by assigning a password. You assign the password when you configure the password. A password is mandatory as of protection level "Complete protection". Communication cannot be established with the PLC if you enter no password or an incorrect password. 3672 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs Assigning password You enter the password for the PLC in the "Connections" editor. Security levels If you want to protect the PLC and HMI device communication, you can assign protection levels for the communication. For a SIMATIC S7-1500 CPU, you can enter multiple passwords and thereby set up different access rights for various user groups. The passwords are entered in a table, so that exactly one protection level is assigned to each password. The effect of the password is given in the "Protection" column. For the SIMATIC S7-1200 controller, several aspects need to be considered when setting protection levels. For additional information on this, see: Auto-Hotspot Example You select the "Complete protection" protection level for a standard CPU (i.e., not an F-CPU) when configuring it. Afterwards, you enter a separate password for every protection level above it in the table. For users who do not know any of the passwords, the CPU is completely protected. Not even HMI access is possible. For users who know one of the assigned passwords, the effect depends on the table row in which the password occurs: WinCC Basic V13.0 System Manual, 02/2014 3673 Visualize processes 10.8 Communicating with PLCs The password in row 1 (no protection) allows access as if the CPU were completely unprotected. Users who know this password have unrestricted access to the CPU. The password in row 2 (write protection) allows access as if the CPU were write-protected. Despite knowing the password, users who know this password only have read access to the CPU. The password in row 3 (read and write protection) allows access as if the CPU were readprotected and write-protected, so that only HMI access is possible for users who know this password. 10.8.6.4 Data exchange Area pointers General information on area pointers Introduction You use an area pointer to access a data area in the PLC. During communication, the PLC and the HMI device alternately access these data areas for read and write operations. The PLC and the HMI device trigger defined interactions based on the evaluation of stored data. Configuration of area pointers Before you use an area pointer, you enable it under "Connections > Area pointer". You then assign the area pointer parameters. You can find more detailed information on configuring area pointers in: Data exchange using area pointers (Page 3639) Restrictions You can only configure the following data types for communication with SIMATIC S7 1500 for data exchange using area pointers: UInt and array of UInt Word and array of Word Int and array of Int "Array[0..15] of Bool" for area pointer "Coordination" Date_And_Time DTL and LDT 3674 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs "Screen number" area pointer Function The HMI device saves information about the screen called on the HMI device to the "Screen number" area pointer. This allows the transfer of the current screen contents from the HMI device to the PLC. The PLC can trigger specific reactions such as the call of a different screen. Use Configure and enable the area pointer in "Communication > Connections" before you put it into use. You can create only one instance of the "Screen number" area pointer and only on one PLC. The screen number is always transferred to the PLC when a new screen is activated or when the focus within a screen changes from one screen object to another. Structure The area pointer is a data area in the memory of the PLC with a fixed length of 5 words. 15 14 13 12 11 10 9 8 7 6 1st word Current screen type 2nd word Current screen number 3rd word Reserved 4th word Current field number 5th word Reserved 5 4 3 2 1 0 Current screen type "1" for root screen or "4" for permanent window Current screen number 1 to 32767 Current field number 1 to 32767 "Date/time" area pointer Function This area pointer is used to transfer the date and time from the HMI device to the PLC. The PLC writes control job "41" or "40" to the job mailbox. WinCC Basic V13.0 System Manual, 02/2014 3675 Visualize processes 10.8 Communicating with PLCs When it evaluates the control job, the HMI device writes its current date and the time in the data area configured in the "Date/time" area pointer. All definitions are coded in BCD format. Note You cannot use the "Date/Time PLC" area pointer if you have configured the "Date/Time" area pointer. The "Date/Time" area pointer when used in a project which contains multiple connections must be enabled for each configured connection. The date/time data area has the following structure: Data word Most significant byte 7 Least significant byte 0 7 0 n+0 Reserved Hour (0 to 23) n+1 Minute (0 to 59) Second (0 to 59) n+2 Reserved Reserved n+3 Reserved Weekday (1 to 7, 1=Sunday) n+4 Day (1 to 31) Month (1 to 12) n+5 Year (80 to 99/0 to 29) Reserved Time Date Note When making entries in the "Year" data area, you should note that values 80 to 99 result in years 1980 through 1999, while the values 0 to 29 result in the years 2000 through 2029. Using data types The data types "Date_And_Time, DTL" and "LDT" can only be used with the "Date/time" and "Date/time PLC" area pointers. The data format of the "Date/time" area pointer depends on job mailbox 40/41. If there are no control tags linked to the area pointer, or a control tag is linked with the data type "Array[0..5] of UInt/Word/Int", the following applies: The configuration of the "Date/time" area pointer is only used for job mailbox 41. If job mailbox 40 is used, the data format "DATE_AND_TIME (BCD-encoded)" is used (shown in the next section). If the "Date/time" and "Date/time PLC" area pointers are linked to a control tag with the data type "DATE_AND_TIME", "DTL" or "LDT", the associated data format is used in the corresponding area pointer. 3676 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs "Date/time PLC" area pointer Function This area pointer is used to transfer the date and time from the PLC to the HMI device. Use this area pointer if the PLC is the time master. The PLC loads the data area of the area pointer. All definitions are coded in BCD format. The HMI device reads the data cyclically within the configured acquisition cycle and synchronizes itself. Note Set an acquisition cycle of sufficient length for the Date/time area pointer in order to avoid any negative impact on HMI device performance. Recommended: Acquisition cycle of 1 minute, if the process allows this. "Date/Time PLC" is a global area pointer and may be configured only once per project. Note You cannot use the "Date/Time" area pointer if you have configured the "Date/Time PLC" area pointer. The date/time data area has the following structure: DATE_AND_TIME format (in BCD code) Data word Most significant byte 7 n+0 1) WinCC Basic V13.0 System Manual, 02/2014 ...... Year (80 to 99/0 to 29) Least significant byte 0 7 ...... 0 Month (1 to 12) n+1 Day (1 to 31) Hour (0 to 23) n+2 Minute (0 to 59) Second (0 to 59) n+3 Reserved Reserved n+4 1) Reserved Reserved n+5 1) Reserved Reserved Weekday (1 to 7, 1=Sunday) The two data words must exist in the data area to ensure that the data format matches WinCC flexible and to avoid reading false information. 3677 Visualize processes 10.8 Communicating with PLCs Note When making entries in the "Year" data area, you should note that values 80 to 99 result in years 1980 through 1999, while the values 0 to 29 result in the years 2000 through 2029. Using data types The data types "Date_And_Time, DTL" and "LDT" can only be used with the "Date/time" and "Date/time PLC" area pointers. The data format of the "Date/time" area pointer depends on job mailbox 40/41. If there are no control tags linked to the area pointer, or a control tag is linked with the data type "Array[0..5] of UInt/Word/Int", the following applies: The configuration of the "Date/time" area pointer is only used for job mailbox 41. If job mailbox 40 is used, the data format "DATE_AND_TIME (BCD-encoded)" is used (shown in the next section). If the "Date/time" and "Date/time PLC" area pointers are linked to a control tag with the data type "DATE_AND_TIME", "DTL" or "LDT", the associated data format is used in the corresponding area pointer. "Coordination" area pointer Function The "Coordination" area pointer is used to implement the following functions: Detecting the startup of the HMI device in the control program Detecting the current operating mode of the HMI device in the control program Detecting whether the HMI device is ready to communicate in the control program By default, the "Coordination" area pointer has the length of one word and cannot be changed. Usage Note The HMI device always writes the entire coordination area when updating the area pointer. The control program can for this reason not make changes to the coordination area. 3678 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs Assignment of the bits in the "Coordination" area pointer ORZRUGHUE\WH KLJKRUGHUE\WH VWZRUG VWZRUGQRWDVVLJQHG UHVHUYHG [ DVVLJQHG ; ; ; 6WDUWXSELW 2SHUDWLRQPRGH /LIHELW Startup bit The startup bit is set briefly to "0" by the HMI device during startup. It sets the bit permanently to "1" when startup is completed. Operating mode The operating mode bit is set to 1 as soon as the user switches the HMI device offline. The status of the operating mode bit is "0" during normal operation of the HMI device. You can determine the current operating mode of the HMI device by reading this bit in the control program. Life bit The HMI device inverts the life bit at intervals of approximately one second. You can check whether or not there is still a connection to the HMI device by querying this bit in the control program. "Project ID" area pointer Function When Runtime starts, a check can be carried out as to whether the HMI device is connected to the correct PLC. This check is important when operating with several HMI devices. For this, the HMI device compares a value stored on the PLC with the value specified in configuration. This ensures compatibility of the configuration data with the PLC program. If there is no concordance, a system event is given on the HMI device and Runtime is stopped. Use Note HMI connections cannot be switched "online". The HMI connection in which the "Project ID" area pointer is used must be switched "online". WinCC Basic V13.0 System Manual, 02/2014 3679 Visualize processes 10.8 Communicating with PLCs To use this area pointer, set up the following during the configuration: Define the version of the configuration. Values between 1 and 255 are possible. You enter the version in the editor "Runtime settings > General" in the "Identification" area. Data address of the value for the version that is stored in the PLC: You enter the data address in the editor "Communication > Connections" under "Address". Connection failure A connection failure to a device on which the "project ID" area pointer is configured results in all the other connections of the device being switched to "offline". This behavior has the following requirements: You have configured several connections in a project. You are using the "project ID" area pointer in at least one connection. Causes which may set connections "offline": The PLC is not available. The connection has been switched offline in the engineering system. "Job mailbox" area pointer Function The PLC can use the job mailbox to transfer jobs to the HMI device to trigger corresponding actions on the HMI device. These functions include, for example: Display screen Set date and time Data structure The first word of the job mailbox contains the job number. Depending on the job mailbox, up to three parameters can be transferred. Word Most significant byte Least significant byte n+0 0 Job number n+1 Parameter 1 n+2 Parameter 2 n+3 Parameter 3 The HMI device evaluates the job mailbox if the first word of this job is not equal to zero. This means that the parameters must be entered in the job mailbox first, followed by the job number. When the HMI device accepts the job mailbox, the first word is set to 0 again. The execution of the job mailbox is generally not completed at this point in time. 3680 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs Job mailboxes All job mailboxes and their parameters are listed below. The "No." column contains the job number of the job mailbox. Job mailboxes can only be triggered by the PLC when the HMI device is online. No . Function 14 Set time (BCD-coded) Parameter 1 Left byte: Right byte: hours (0-23) Parameter 2 Left byte: minutes (0-59) Right byte: seconds (0-59) Parameter 3 15 23 Setting the date (BCD coded) 3) 4) Parameter 1 Left byte: Right byte: weekday (1-7: Sunday-Saturday) Parameter 2 Left byte: day (1-31) Right byte: month (1-12) Parameter 3 Left byte: year User logon Logs the user on with the name "PLC user" at the HMI device with the group number transferred in Parameter 1. The logon is possible only when the transferred group number exists in the project. 24 Parameter 1 Group number 1 to 255 Parameter 2, 3 - User logoff Logs off the current user. (The function corresponds to the "logoff" system function) Parameter 1, 2, 3 40 - Transfer date/time to PLC (in the S7 format DATE_AND_TIME) An interval of at least 5 seconds must be maintained between two successive jobs to prevent overload of the HMI device. Parameter 1, 2, 3 41 - Transfer date/time to PLC (In OP/MP format) An interval of at least 5 seconds must be maintained between successive jobs to prevent overload of the HMI device. Parameter 1, 2, 3 46 - Update tag Causes the HMI device to read the current value of the tags from the PLC whose update ID matches the value transferred in Parameter 1. (Function corresponds to the "UpdateTag" system function.) Parameter 1 49 1 - 100 Delete alarm buffer Deletes all analog alarms and discrete alarms of the "Warnings" class from the alarm buffer. WinCC Basic V13.0 System Manual, 02/2014 3681 Visualize processes 10.8 Communicating with PLCs No . Function 14 Set time (BCD-coded) Parameter 1, 2, 3 50 - Delete alarm buffer Deletes all analog alarms and discrete alarms of the "Errors" class from the alarm buffer. Parameter 1, 2, 3 51 69 - Screen selection 2) Parameter 1 Screen number Parameter 2 - Parameter 3 Field number Reading data record from PLC 1) Parameter 1 Recipe number (1-999) Parameter 2 Data record number (1-65535) Parameter 3 0: Do not overwrite existing data record 1: Overwrite existing data record 70 Writing data record to PLC 1) Parameter 1 Recipe number (1-999) Parameter 2 Data record number (1-65535) Parameter 3 - 1) Only for devices supporting recipes. 2) OP 73, OP 77A and TP 177A HMI devices also execute the "Screen selection" job mailbox if the on-screen keyboard is active. 3) The weekday is ignored on HMI device KTP 600 BASIC PN. 4) The weekday is ignored when you configure the "Date/Time PLC" area pointer. "Data record" area pointer "Data record" area pointer Function When data records are transferred between the HMI device and PLC, both partners access common communications areas on the PLC. Data transfer types There are two ways of transferring data records between the HMI device and PLC: Transfer without synchronization Transfer with synchronization via the data mailbox 3682 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs Data records are always transferred directly, which means that the tag values are read straight from an address or written straight to an address configured for this tag without being redirected via an interim memory. Initiating the transfer of data records There are three ways of triggering the transfer: Operator input in the recipe view Job mailboxes The transfer of data records can also be triggered by the PLC. Triggering by configured functions If the transfer of data records is triggered by a configured function or by a job mailbox, the recipe view on the HMI device remains operable. The data records are transferred in the background. Simultaneous processing of several transfer requests is, however, not possible. In this case, the HMI device rejects the other transfer requests with a system alarm. Transfer without synchronization If you select asynchronous transfer of data records between the HMI device and PLC, there is no coordination over the common data areas. It is therefore unnecessary to set up a data area during configuration. Asynchronous data record transfer can be a useful alternative, for example when: The system is capable of excluding the risk of uncontrolled overwriting of data by the communication peer. The PLC does not require information about the recipe number and data record number. The transfer of data records is triggered by the operator of the HMI device. Reading values When a read job is triggered, the values are read from the PLC addresses and transferred to the HMI device. Triggering by the operator in the recipe view: The values are downloaded to the HMI device. You can then, for example, process, edit, or save these values in the HMI device. Triggering by a function or job mailbox: The values are saved immediately to the data volume. WinCC Basic V13.0 System Manual, 02/2014 3683 Visualize processes 10.8 Communicating with PLCs Writing values When a write job is triggered, the values are written to the PLC addresses. Triggering by the operator in the recipe view: The current values are written to the PLC. Triggering by a function or job mailbox: The current values are written to the PLC from the data medium. Transfer with synchronization If you select synchronous transfer, both communication partners set status bits in the common data area. You can use this mechanism to prevent uncontrolled overwriting of data in either direction in your control program. Application Synchronous data record transfer can be a useful solution, for example, when: The PLC is the "active partner" in the transfer of data records. The PLC evaluates the information about the recipe number and data record number. The transfer of data records is triggered by means of a Job mailbox. Requirements In order to synchronize transfer of data records between the HMI device and the PLC, the following requirements must be met during configuration: An area pointer has been set up: "Communication > Connections" editor in "Area pointer". The PLC with which the HMI device synchronizes transfer of data records is specified in the recipe: "Recipes" editor in the inspector window the option "Coordinated transfer of data records" under "General > Synchronization > Settings" Structure of the data area The data area has a fixed length of 5 words. Structure of the data area: 15 3684 0 1. Word Current recipe number (1 - 999) 2. Word Current data record number (0 - 65535) 3. Word Reserved 4. Word Status (0, 2, 4, 12) 5. Word Reserved WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs Status The status word (word 4) can adopt the following values: Value Meaning Decimal Binary 0 0000 0000 Transfer permitted, data mailbox free 2 0000 0010 Transferring 4 0000 0100 Transfer completed without error 12 0000 1100 Transfer completed with error Sequence of a transfer triggered by a job mailbox The transfer of data records between the HMI device and the PLC can be initiated by either one of these stations. The two job mailboxs No. 69 and No. 70 are available for this type of transfer. No. 69: Read data record from PLC ("PLC DAT") Job mailbox no. 69 transfers data records from the PLC to the HMI device. The job mailbox is structured as follows: Left byte (LB) Word 1 Right byte (RB) 0 69 Word 2 Recipe number (1-999) Word 3 Data record number (1 to 65535) Word 4 Do not overwrite existing data record: 0 Overwrite existing data record: 1 No. 70: Write data record to PLC ("DAT PLC") Job mailbox No. 70 transfers data records from the HMI device to the PLC. The job mailbox is structured as follows: Left byte (LB) Word 1 WinCC Basic V13.0 System Manual, 02/2014 Right byte (RB) 0 70 Word 2 Recipe number (1-999) Word 3 Data record number (1-65,535) Word 4 -- 3685 Visualize processes 10.8 Communicating with PLCs Sequence when reading from the PLC with job mailbox "PLC DAT" (no. 69) Step Action 1 Check: Status word = 0? Yes No 2 The HMI device enters the recipe and data record number specified in the job and the status "Transferring" in the data record. Abort without return message. 3 The HMI device reads the values from the PLC and saves these to the data record defined in the job mailbox. 4 If "Overwrite" was selected in the job, an existing data record is overwritten without any prompt for confirmation. The HMI device sets the status "Transfer completed." If "Do not overwrite" was selected in the job, and the data record already exists, the HMI device aborts the job and enters 0000 1100 in the status word of the data mailbox. 5 The control program must reset the status word to zero in order to enable further transfers. Sequence of writing to the PLC with job mailbox "DAT PLC" (no. 70) Step Action 1 Check: Status word = 0? Yes No 2 The HMI device enters the recipe and data record number specified in the job and the status "Transferring" in the data mailbox. Abort without return message. 3 The HMI device fetches the values of the data record specified in the function from the data medium and writes the values to the PLC. 4 The HMI device sets the status "Transfer completed." 5 The control program can now evaluate the transferred data. The control program must reset the status word to zero in order to enable further transfers. Sequence of the transfer when triggered by a configured function Reading from the PLC using a configured function 3686 Step Action 1 Check: Status word = 0? Yes No 2 The HMI device enters the recipe and data record number specified in the function and the status "Transferring" in the data mailbox. Abort with system event. 3 The HMI device reads the values from the PLC and stores them in the data record specified in the function. WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs Step 4 Action If "Yes" was selected for the "Overwrite" function, an existing data record is overwritten without any prompt for confirmation. The HMI device sets the status "Transfer completed." If "No" was selected for the "Overwrite" function and the data record already exists, the HMI device aborts the job and enters 0000 1100 in the status word of the data mailbox. 5 The control program must reset the status word to zero in order to enable further transfers. Writing to the PLC by means of configured function Step Action 1 Check: Status word = 0? Yes No 2 The HMI device enters the recipe and data record number specified in the function and the status "Transferring" in the data mailbox. Abort with system event. 3 The HMI device fetches the values of the data record specified in the function from the data medium and transfers the values to the PLC. 4 The HMI device sets the status "Transfer completed." 5 The control program can now evaluate the transferred data. The control program must reset the status word to zero in order to enable further transfers. Possible causes of error when transferring data records Possible causes of error The section below shows possible error causes which lead to the cancellation of data record transfer: Tag address not set up on the PLC Overwriting data records not possible WinCC Basic V13.0 System Manual, 02/2014 3687 Visualize processes 10.8 Communicating with PLCs Recipe number does not exist Data record number does not exist Note The status word may only be set by the HMI device. The PLC may only reset the status word to zero. Note The PLC may only evaluate the recipe and data record numbers when data inconsistency is detected if one of the conditions outlined below has been met: The data mailbox status is set to "Transfer completed". The data mailbox status is set to "Transfer completed with error". Reaction to an aborted transfer due to errors If the transfer of data records is aborted due to errors, the HMI device reacts as follows: Triggering by the operator in the recipe view Information in the status bar of the recipe view and output of system alarms Triggered by function Output of system alarms Triggering by job mailbox No return message on the HMI device You can nonetheless evaluate the status of the transfer by querying the status word in the data record. Trends General information on trends Trends A trend is the graphical representation of one or more values from the PLC. The value is read out time-triggered for Basic Panels. For additional information see: Auto-Hotspot Time-triggered trends The HMI device reads in the trend values cyclically at an interval specified in the configuration. Time-triggered trends are suitable for continuous curves, such as the operating temperature of a motor. 3688 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs Trend request and trend transfer Trend request area The HMI device sets corresponding bits in the trend request area when you open a screen which contains one or more trends on the HMI device. After closing the screen, the HMI device resets the relevant bits in the trend request area. The trend request area can be used for evaluation purposes in the PLC to determine which trend is currently being displayed on the HMI device. Trends can also be triggered without evaluation of the trend request area. Trend transfer area 1 This area is used to trigger trends. You must set the bit assigned to the trend in the trend transfer area and set the trend group bit in your control program. The trend group bit is the last bit in the trend transfer area. The HMI device detects the trigger. The HMI device reads either a value or the entire buffer from the PLC. It then resets the trend bit and the trend group bit. The following picture shows the structure of a trend transfer area. ORZRUGHUE\WH KLJKRUGHUE\WH %LWQXPEHU VWZRUG QWKZRUG 7UHQGJURXSELW The trend transfer area must not be modified by the PLC program until the trend group bit has been reset. Trend transfer area 2 Trend transfer area 2 is required for trends configured with a switch buffer. The trend transfer areas 1 and 2 have a similar structure. Switch buffer The switch buffer is a second buffer for the same trend that can be set up during configuration. The PLC writes to Buffer 2 while the HMI device reads values from Buffer 1, and writes to Buffer 1 when the HMI device is reading Buffer 2. This prevents the PLC from overwriting trend values while the trend is being read by the HMI device. WinCC Basic V13.0 System Manual, 02/2014 3689 Visualize processes 10.8 Communicating with PLCs Permitted data types for trends For SIMATIC S7 You assign one bit to each trend during configuration. Tags and array tags of the "Word" or "Int" data type are permitted. Alarms General information on trends Trends A trend is the graphical representation of one or more values from the PLC. The value is read out either time- or bit-triggered, depending on the configuration. For additional information see: Auto-Hotspot Note The value is read out time-triggered for Basic Panels. Time-triggered trends The HMI device reads in the trend values cyclically at an interval specified in the configuration. Time-triggered trends are suitable for continuous curves, such as the operating temperature of a motor. Bit-triggered trends Through a trigger bit set in the trend request tag, the HMI device either reads in a trend value or an entire trend buffer. This setting is defined in the configuration. Bit-triggered trends are normally used to represent fast changing values. One example might be the injection pressure in the production of plastic parts. To trigger bit-triggered trends, appropriate external tags must be created in the "HMI tags" editor and connected to trend areas during configuration. The HMI device and PLC then communicate with each other via these trend areas. The following areas are available for trends: Trend request area Trend transfer area 1 Trend transfer area 2 (required only with switch buffers) 3690 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs Acknowledgment of alarms Procedure Create suitable tags on the PLC to acknowledge an error alarm. You assign these tags to an alarm in the "Bit messages" editor. You make the assignment in "Properties > Acknowledgment". Distinction in terms of acknowledgment: Acknowledgment by the PLC Acknowledgment on the HMI device Acknowledgment by the PLC In "PLC acknowledgment tag", configure the tag or array tag and the bit number that the HMI device uses to identify a PLC acknowledgment. A bit set in the tag triggers acknowledgment of the assigned error alarm bit at the HMI device. This tag bit returns a function similar to acknowledgment on the HMI device which is triggered by pressing the "ACK" button, for example. The acknowledgment bit must be located in the same tag as the bit for the error alarm. Reset the acknowledgment bit before setting the bit in the alarm area again. The figure below shows the pulse diagram. (UURUDODUP $FNQRZOHGJPHQW 3/&+0,GHYLFH $UULYDORIWKH $FNQRZOHGJP 5HVHWRI HUURUDODUP YLD3/& DFNQRZOHGJPELW 1HZ HUURUDODUP Acknowledgment on the HMI device In the "HMI acknowledgment tag" area, configure the tag or array tag as well as the bit number that the HMI device writes to the PLC after acknowledgment. Make sure when you use an array tag that it is not longer than 6 words. To always create a signal change when setting an assigned acknowledgment bit of a discrete alarm that must be acknowledged, the HMI device will reset the acknowledgment bit assigned to the alarm as soon as it detects an alarm subject to acknowledgment and write the acknowledgment tag in the PLC. There will be a certain delay between detecting the message and writing the acknowledgment tag in the PLC because the HMI device has to process the operations. If a discrete alarm subject to acknowledgment is acknowledged by the HMI device, then the corresponding bit in the assigned acknowledgment tag will be set. The entire acknowledgment WinCC Basic V13.0 System Manual, 02/2014 3691 Visualize processes 10.8 Communicating with PLCs tag is then written to the PLC by the HMI device. This allows the PLC to recognize that a certain alarm message has been acknowledged at the HMI device. Note All alarm bits acknowledged since the last Runtime start will remain in the acknowledgment tag until a new incoming of the respective discrete alarms is detected. This area should only be read by the PLC because the entire section of the HMI device will be overwritten once the next acknowledgment tag is written. The figure below shows the pulse diagram. (UURUDODUP $FNQRZOHGJPHQW +0,GHYLFH3/& $UULYDORIWKH HUURUDODUP 10.8.6.5 5HVHWRI DFNQRZOHGJPELW $FNQRZOHGJP YLD+0,GHYLFH 1HZ HUURUDODUP Performance features of communication S7-1500 device dependency Device dependency If you use devices from an earlier version of the TIA Portal with TIA Portal V13, it may not be possible to configure connections to certain HMI devices. Basic Panels V11.0 HMI devices SIMATIC S7 -1500 KP300 Basic No KP400 Basic No KTP400 Basic PN No KTP600 Basic DP No KTP600 Basic PN No KTP1000 Basic DP No KTP1000 Basic PN No TP1500 Basic PN No 3692 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs Basic Panels V12.0 HMI devices SIMATIC S7 -1500 KP300 Basic Yes KP400 Basic Yes KTP400 Basic PN Yes KTP600 Basic DP Yes KTP600 Basic PN Yes KTP1000 Basic DP Yes KTP1000 Basic PN Yes TP1500 Basic PN Yes Basic Panels V13.0 HMI devices SIMATIC S7 -1500 KTP400 Basic Yes KTP700 Basic Yes KTP900 Basic Yes KTP1200 Basic Yes Valid data types for SIMATIC S7 1500 Valid data types for connections with SIMATIC S7 1500 The table lists the data types that can be used when configuring tags and area pointers. Data type Length BOOL 1 bit BYTE 1 byte WORD 2 bytes DWORD 4 bytes CHAR 1 byte INT 2 bytes DINT 4 bytes REAL 4 bytes TIME 4 bytes DATE 2 bytes TIME_OF_DAY 4 bytes S5TIME 2 bytes COUNTER 2 bytes TIMER 2 bytes WinCC Basic V13.0 System Manual, 02/2014 3693 Visualize processes 10.8 Communicating with PLCs 10.8.6.6 Data type Length DATE_AND_TIME 8 bytes STRING (2+n) bytes, n = 0 to 254 DTL 12 bytes LDT 8 bytes LINT 8 bytes LREAL 8 bytes LTIME 8 bytes LTIME_OF_DAY 8 bytes SINT 1 byte UDINT 4 bytes UINT 2 bytes ULINT 8 bytes USINT 1 byte Configuring connections in the "Connections" editor Connection parameters Parameters to be set To set the connection parameters, such as addresses and profiles, click the connection that you have created in the "Connections" editor. The communication partners are displayed schematically in the Inspector window under "Parameters". The "HMI device", "Network", and "PLC" areas are available for assigning parameters according to the interface used. 3694 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs WinCC Basic V13.0 System Manual, 02/2014 3695 Visualize processes 10.8 Communicating with PLCs Ethernet parameters Parameters for the HMI device You set the parameters for the HMI device in the network under "HMI device".. The changes are not transferred automatically to the HMI device. You must change the settings in the Control Panel of the HMI device. "Interface" If you are directly connected to the HMI device during configuration, you can set up the IP address of the HMI device in WinCC. Note The IP address in the Control Panel will be overwritten upon subsequent loading if you have already set up the IP address in the HMI device control panel. The IP address already set up in the Control Panel will be retained upon subsequent loading if you activate "Set IP address using a different method". The IP address is transferred to the HMI device during project transfer. To set up the IP address of the HMI device: - Click the HMI device. - Open the "Device configuration" editor. - Click the Ethernet interface. - Assign the IP address in the inspector window under: "General > PROFINET interface > Ethernet addresses" "Address" You assign the IP address of the HMI device in the "Address" area. When you transfer the WinCC project to the HMI device, this IP address is set up directly in the HMI device. "Access point" Specifies the access point for the PG/PC interface that can be used to reach the communication partner. 3696 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs Parameters for the PLC Under "PLC", you address the S7 module with which the HMI device will exchange data. Assign a name for the connection for each communication partner. "Address" Under "Address", set the IP address of the S7 module to which the HMI device is connected. "Access password" Enter a password in the "Access password" field. This password must match the one you saved to the PLC. Note You only need a password if you have set "Complete protection" at the PLC. No connection is set up to the PLC if the "Complete protection" security level is stored on the PLC and you do not enter a password. PROFIBUS parameters Parameters for the HMI device You assign the parameters for the HMI device in the network once under "HMI device". The change applies to each communication partner. "Type" Specifies the physical connection used. "Interface" For "Interface", you select the HMI device interface via which the HMI device is connected to the PROFIBUS network. "Baud rate" For "Baud rate", you set the transmission speed of the data in the network. The baud rate is determined by the slowest HMI device connected to the network. The setting must be identical throughout the network. Note If you set a baud rate of 1.5 Mbaud for OP 73 or OP 77A, the highest station address must be less than or equal to 63. "Address" You set the PROFIBUS address of the HMI device under "Address". The PROFIBUS address must be unique in the PROFIBUS network. WinCC Basic V13.0 System Manual, 02/2014 3697 Visualize processes 10.8 Communicating with PLCs "Only master on bus" Disables an additional safety feature against bus faults when the HMI device is connected to the network. A passive station (slave) can only send data if it is requested to do so by an active station (master). In S7-200, you must set an HMI device as the master. "Access point" The access point defines a logical device name through which the communication partner can be reached. Parameters for the network Under "Network", you set the parameters for the PROFIBUS network to which the HMI device is linked. "Profile" For "Profile", you select the network profile that is used in the network. In "Profile", set "DP", "Universal", or "Standard". The setting must be identical throughout the network. "Highest address" For "Highest station address", set the highest station address. The highest station address must be greater than or equal to the highest actual PROFIBUS address. The setting must be identical throughout the network. Note If you set a baud rate of 1.5 Mbaud in the OP 73 or the OP 77A, the highest station address must be less than or equal 63. "Number of masters" For "Number of masters", set the number of masters in the PROFIBUS network. This information is necessary to correctly calculate the bus parameters. 3698 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs Parameters for the PLC Under "PLC", you address the S7 module with which the HMI device will exchange data. Assign a name for the connection for each communication partner. "Address" For "Address", set the PROFIBUS address of the S7 module (CPU, FM, or CP) to which the HMI device is connected. "Access password" Enter a password in the "Access password" field. This password must match the one you saved to the PLC. Note You only need a password if you have set "Complete protection" at the PLC. No connection is set up to the PLC if the "Complete protection" security level is stored on the PLC and you do not enter a password. 10.8.7 Communicating with SIMATIC S7 1200 10.8.7.1 Communication with SIMATIC S7 1200 Introduction This section describes the communication between an HMI device and the SIMATIC S7 1200 PLC. You can configure the following communication channels for the SIMATIC S7 1200 PLC: PROFINET PROFIBUS HMI connection for communication You configure connections between the HMI device and a SIMATIC S7 1200 in the "Devices & Networks" editor. If you have configured a HMI device with a serial port, you must configure a PROFIBUS-capable communication module to the SIMATIC S7 1200. WinCC Basic V13.0 System Manual, 02/2014 3699 Visualize processes 10.8 Communicating with PLCs 10.8.7.2 Communication via PROFINET Communication via PROFINET HMI connections via PROFINET If you have inserted an HMI device and a SIMATIC S7 1200 into the project, you interconnect the two PROFINET interfaces in the "Devices & Networks" editor. You can also connect multiple HMI devices to one SIMATIC S7 1200 and multiple SIMATIC S7 1200s to one HMI device. The maximum number of communication partners that you can connect to an HMI device is dependent on the HMI device used. Additional information is available in the documentation for the respective HMI device. HMI connection in the "Devices & Networks" editor You configure the HMI connection between the PLC and the HMI device via PROFINET in the "Devices & Networks" editor. Connection in the "Connections" editor Alternatively, you configure the connection between the PLC and HMI device via PROFINET in the "Connections" editor of the HMI device. 3700 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs Configuring an HMI connection via PROFINET Introduction You configure an HMI connection between HMI devices and a SIMATIC S7 1200 via PROFINET or Ethernet in the "Devices & Networks" editor. CAUTION Communication via Ethernet In Ethernet-based communication, the end user is responsible for the security of his data network. Targeted attacks can overload the device and interfere with proper functioning. Requirements The following communication partners are created in the "Devices & Networks" editor: SIMATIC S7 1200 HMI device with PROFINET or Ethernet interface Procedure 1. Double-click the "Devices & Networks" item in the project tree. The available communication partners in the project are displayed graphically in the network view. 2. Click the "Connections" button and select "HMI connection" for the connection type. The devices available for connection are highlighted in color. 3. Click the PROFINET interface of the PLC and use a drag-and-drop operation to draw a connection to the PROFINET or Ethernet interface of the HMI device. WinCC Basic V13.0 System Manual, 02/2014 3701 Visualize processes 10.8 Communicating with PLCs 4. Click the connecting line. 5. Click "Highlight HMI connection" and select the HMI connection. The connection is displayed graphically in the Inspector window. 6. Click the communication partners in the "Network view" and change the PROFINET parameters in the Inspector window according to the requirements of your project. See the chapter "PROFINET parameters (Page 3702)" for additional details. Note The created HMI connection is also shown in the tabular area of the editor on the "Connections" tab. You check the connection parameters in the table. You can change the local name for the connection only in the table. Result You have created a connection between an HMI device and a SIMATIC S7 1200. The IP address and subnet mask connection parameters are configured. PROFINET parameters PROFINET parameters for the HMI connection PROFINET parameters for the HMI connection An overview of the configured HMI connection parameters can be found in the properties for the HMI connection. Only limited changes are possible in this Inspector window. 3702 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs Displaying and editing HMI connection parameters 1. Click the HMI connection in the "Devices & Networks" editor. 2. Change the parameters of the HMI connection in the Inspector window under "Properties > General > General". Connection The "Connection" area displays the HMI connection created for communication between the devices. You can edit the name of the HMI connection in this area. "Connection path" The communication partners of the selected HMI connection and the associated PROFINET parameters are displayed in the "Connection path" area. Some of the areas displayed cannot be edited in this dialog. "End point" Displays the device name. This area cannot be edited. "Interface" Displays the selected interface of the device. You can choose between several interfaces, depending on the device. "Interface type" Displays the selected interface type. This area cannot be edited. WinCC Basic V13.0 System Manual, 02/2014 3703 Visualize processes 10.8 Communicating with PLCs "Subnet" Displays the selected subnet. This area cannot be edited. "Address" Displays the selected IP address of the device. This area cannot be edited. "Find connection path" button Enables the subsequent specification of connections. PROFINET parameters for the HMI device PROFINET parameters for the HMI device An overview of the configured HMI device parameters can be found in the properties for the HMI device. Displaying and changing PROFINET parameters of the HMI device 1. Click the HMI device in the "Devices & Networks" editor. 2. Change the parameters of the HMI device in the Inspector window under "Properties > General > General". 3704 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs "Interface networked with" In the "Interface networked with" area, select the subnet of the HMI connection via which the HMI device is connected to the network. You use the "Add new subnet" button to create a new subnet. "IP protocol" "Set IP address in the project" When you transfer the WinCC project to the HMI device, this IP address is set up directly in the HMI device. Note The device is automatically restarted in the case of HMI devices with the Windows CE 3.0 operating system. HMI devices with Windows CE 3.0: OP 77B TP 177B color PN/DP TP 177B mono DP OP 177B color PN/DP OP 177B mono DP Mobile Panel 177 PN Mobile Panel 177 DP TP 277 6" OP 277 6" "Subnet mask" You assign data of the subnet mask in the "Subnet mask" area. "Use IP router" If you are using an IP router, select "Use IP router" and enter the router address in the "Router address" field. "Set IP address using a different method" If the function "Set IP address using a different method" is activated, the IP address is not taken from the project. You have to enter the IP address directly in the Control Panel of the HMI device. PROFINET parameters for the PLC PROFINET parameters for the PLC An overview of the configured parameters can be found in the properties for the PLC. WinCC Basic V13.0 System Manual, 02/2014 3705 Visualize processes 10.8 Communicating with PLCs Displaying and changing PROFINET parameters of the PLC 1. Click the PLC in the "Devices & Networks" editor. 2. Change the parameters of the PLC in the Inspector window under "Properties > General > General". "Interface networked with" In the "Subnet" area, select the subnet of the HMI connection via which the PLC is connected to the network. You use the "Add new subnet" button to create a new subnet. "IP protocol" "Interface type" Depending on the HMI device type, you have various interfaces to choose from. "IP address" You assign the IP address of the HMI device in the "IP address" area. "Subnet mask" You assign data of the subnet mask in the "Subnet mask" area. If you are using an IP router, select "Use IP router" and enter the router address in the field. 3706 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs Configuring Industrial Ethernet Rules for the network configuration The Ethernet interfaces of the devices have a default IP address that you can change. IP address The IP parameters are visible if the communication-capable devices support the TCP/IP protocol. The IP address consists of 4 decimal figures in the range of 0 to 255. The decimal figures are separated from one another by a dot. Example: 140.80.0.2 The IP address consists of the following: The address of the (sub) net The address of the node (generally also called host or network node) Subnet mask The subnet mask splits these two addresses. It determines which part of the IP address addresses the network and which part of the IP address addresses the node. The set bits of the subnet mask determine the network part of the IP address. Example: Subnet mask: 255.255.0.0 = 11111111.11111111.00000000.00000000 In the example given for the above IP address, the subnet mask shown here has the following meaning: The first 2 bytes of the IP address identify the subnet - i.e. 140.80. The last two bytes address the node, thus 0.2. It is generally true that: The network address results from AND linking the IP address and subnet mask. The node address results from AND NOT linking the IP address and subnet mask. Relation between IP address and default subnet mask An agreement exists relating to the assignment of IP address ranges and so-called "Default subnet masks". The first decimal number (from the left) in the IP address determines the structure of the default subnet mask. It determines the number of "1" values (binary) as follows: WinCC Basic V13.0 System Manual, 02/2014 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 3707 Visualize processes 10.8 Communicating with PLCs Note Range of values for the first decimal point A value of between 224 and 255 is also possible for the first decimal number of the IP address (address class D etc). This is, however, not recommended because there is no address check for these values. Masking other subnets You can use the subnet mask to add further structures and form "private" subnets for a subnet that is assigned one of the address classes A, B or C. This is done by setting other lower points of the subnet mask to "1". For each bit set to "1", the number of "private" networks doubles and the number of nodes they contain is halved. Externally, the network functions like an individual network as it did previously. Example: You have a subnet of address class B (e.g. IP address 129.80.xxx.xxx) and change the default subnet mask as follows: Masks Decimal Binary Default subnet mask 255.255.0.0 11111111.11111111.00000000. 00000000 Subnet mask 255.255.128.0 11111111.11111111.10000000. 00000000 Result: All nodes with addresses between 129.80.001.xxx and 129.80.127.xxx are on one subnet, all nodes with addresses between 129.80.128.xxx and 129.80.255.xxx are on another subnet. Router The job of the routers is to connect the subnets. If an IP datagram is to be sent to another network, it first has to be conveyed to a router. To make this possible, in this case you have to enter the address of the router for each node in the subnet. The IP address of a node in the subnet and the address of the router may only differ at the points at which there is a "0" in the subnet mask. Protection of communication Security levels If you want to protect the PLC and HMI device communication, you can assign protection levels for the communication. For a SIMATIC S7-1500 CPU, you can enter multiple passwords and thereby set up different access rights for various user groups. 3708 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs The passwords are entered in a table, so that exactly one protection level is assigned to each password. The effect of the password is given in the "Protection" column. For the SIMATIC S7-1200 controller, several aspects need to be considered when setting protection levels. For additional information on this, see: S7-1200 protection levels Example You select the "Complete protection" protection level for a standard CPU (i.e., not an F-CPU) when configuring it. Afterwards, you enter a separate password for every protection level above it in the table. For users who do not know any of the passwords, the CPU is completely protected. Not even HMI access is possible. For users who know one of the assigned passwords, the effect depends on the table row in which the password occurs: The password in row 1 (no protection) allows access as if the CPU were completely unprotected. Users who know this password have unrestricted access to the CPU. The password in row 2 (write protection) allows access as if the CPU were write-protected. Despite knowing the password, users who know this password only have read access to the CPU. The password in row 3 (read and write protection) allows access as if the CPU were readprotected and write-protected, so that only HMI access is possible for users who know this password. Access password for the HMI connection Introduction You secure access to a PLC by assigning a password. You assign the password when you configure the password. A password is mandatory as of protection level "Complete protection". Communication to the PLC is denied if an incorrect password or no password is entered. WinCC Basic V13.0 System Manual, 02/2014 3709 Visualize processes 10.8 Communicating with PLCs Entering access password You enter the password for the PLC in the "Connections" editor. Setting port options Setting the port options Changing connection settings for the PROFINET IO port You can change the network settings for the PROFINET IO port as required. By default, the settings are made automatically. In normal situations, this guarantees problem-free communication. 3710 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs Possible settings for transmission rate / duplex Depending on the selected device, you can make the following settings for "Transmission rate / duplex": Automatic setting Recommended default setting of the port. The transmission settings are automatically "negotiated" with the peer port. The "Enable autonegotiation" option is also enabled as a default, in other words, you can use cross cables or patch cables for the connection. TP/ITP at x Mbps full duplex (half duplex) Setting of the transmission rate and the full duplex/half duplex mode. The effectiveness depends on the "Enable autonegotiation" setting: - Autonegotiation enabled You can use both cross cable and patch cable. - Autonegotiation disabled Make sure that you use the correct cable (patch cable or cross cable)! The port is also monitored with this setting. Deactivated Depending on the module type, the drop down list box can contain the "- Disabled -" option. This option, for example, allows you to prevent access to an unused port for security reasons. With this setting, diagnostic events are not generated. "Monitor" option This option enables or disables port diagnostics. Examples of port diagnostics: The link status is monitored, in other words, the diagnostics are generated during link-down and the system reserve is monitored in the case of fiber optic ports. Option "Enable autonegotiation " The autonegotiation setting can only be changed if a concrete medium (for example, TP 100 Mbps full duplex) is selected. Whether or not a concrete medium can be set depends on the properties of the module. If autonegotiation is disabled, this causes the port to be permanently specified, as for example, is necessary for a prioritized startup of the IO device. You must make sure the partner port has the same settings because with this option the operating parameters of the connected network are not detected and the data transmission rate and transmission mode can accordingly not be optimally set. Note When a local port is connected, STEP 7 makes the setting for the partner port if the partner port supports the setting. If the partner port does not accept the setting, an error message is generated. WinCC Basic V13.0 System Manual, 02/2014 3711 Visualize processes 10.8 Communicating with PLCs Wiring rules for disabled autonegotiation Requirements You have made the following settings for the port in question, for example, to accelerate the startup time of the IO device: Fixed transmission rate Autonegotiation incl. autocrossing disabled The time for negotiating the transmission rate during startup has been saved. If you have disabled autonegotiation, you must observe the wiring rules. Wiring rules for disabled autonegotiation PROFINET devices have the following two types of ports: Type of port PROFINET devices Note Switch port with crossed pin assignment For IO devices: Port 2 Crossed pin assignment means that the pin assignment for the ports for sending and receiving between the respective PROFINET devices is exchanged internally. End device port with uncrossed pin assignment For S7 CPUs with 2 ports: Ports 1 and 2 For IO devices: Port 1 - For S7 CPUs with one port: Port 1 Validity of the wiring rules The cabling rules described in the following paragraph apply exclusively for the situation in which you have specified a fixed port setting. 3712 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs Rules for cabling You can connect several IO devices in line using a single cable type (patch cable). To do this, you connect port 2 of the IO device (distributed I/O) with port 1 of the next IO device. The following graphic gives an example with two IO devices. 6ZLWFKRU 352),1(7GHYLFH 3 ,2GHYLFH 3 3 3DWFKFDEOHV ,2GHYLFH 3 3 3 3DWFKFDEOHV 6ZLWFKSRUW (QGGHYLFHSRUW Boundaries at the port Requirements To use boundaries, the respective device must have more than one port. If the PROFINET does not support boundary settings, they are not shown. Enable boundaries "Boundaries" are limits for transmission of certain Ethernet frames. The following boundaries can be set at a port: "End of discovery of accessible devices" No forwarding of DCP frames to identify accessible devices. Devices downstream from this port cannot be reached by the project tree under "Accessible devices". Devices downstream from this port cannot be reached by the CPU. "End of topology discovery" LLDP frames (Link Layer Discovery Protocol) are not forwarded for topology detection. "End of sync domain" No forwarding of sync frames transmitted to synchronize nodes within a sync domain. If you operate, for example, a PROFINET device with more than two ports in a ring, you should prevent the sync frame from being fed into the ring by setting a sync boundary (at the ports not inside the ring). Additional example: If you want to use several sync domains, configure a sync domain boundary for the port connected to a PROFINET device from the other sync domain. WinCC Basic V13.0 System Manual, 02/2014 3713 Visualize processes 10.8 Communicating with PLCs Restrictions The following restrictions must be observed: The individual check boxes can only be used if the port supports the function in question. If a partner port has been determined for the port, the following check boxes cannot be used: - "End of discovery of accessible devices" - "End of topology discovery" If autonegotiation is disabled, none of the check boxes can be used. 10.8.7.3 Communication via PROFIBUS Communication via PROFIBUS HMI connections via PROFIBUS If you want to connect a SIMATIC S7 1200 to a HMI device via PROFIBUS, you must configure a PROFIBUS-capable communication module to a slot of the controller first. HMI connection in the "Devices & Networks" editor You configure the HMI connection between the PLC and the HMI device via PROFIBUS in the "Devices & Networks" editor. Connection in the "Connections" editor Alternatively, you configure the connection between the PLC and HMI device in the "Connections" editor of the HMI device. 3714 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs Configuring an HMI connection via PROFIBUS Introduction You configure an HMI connection between HMI devices and a SIMATIC S7-1200 via PROFIBUS in the "Devices & Networks" editor. Requirements The following communication partners are created in the "Devices & Networks" editor: HMI device with MPI/DP interface SIMATIC S7-1200 Procedure 1. Double-click the "Devices & Networks" item in the project tree. The available communication partners in the project are displayed graphically in the network view. 2. Click the "Connections" button. The devices available for connection are highlighted in color. 3. Use a drag-and-drop operation to move a PROFIBUS-capable communication module from the hardware catalog to the PLC. 4. Click the HMI device interface. 5. Select the "PROFIBUS" interface type in the Inspector window under "Properties > General > PROFIBUS address/ MPI address > Parameters". WinCC Basic V13.0 System Manual, 02/2014 3715 Visualize processes 10.8 Communicating with PLCs 6. Click the interface of the communication module and use a drag-and-drop operation to draw a connection to the HMI device. 7. Click the name of the connection. The connection is displayed graphically in the Inspector window. 8. Click "Highlight HMI connection" and select the HMI connection. 9. Click the communication partners in the "Network view" and change the PROFIBUS parameters in the Inspector window according to the requirements of your project. See the section "PROFIBUS parameters (Page 3716)" for additional details. Note The created HMI connection is also shown in the tabular area of the editor on the "Connections" tab. You check the connection parameters in the table. You can change the local name for the connection only in the table. Result You have created an HMI connection between an HMI device and a SIMATIC S7-1200 via PROFIBUS. PROFIBUS parameters PROFIBUS parameters for the HMI connection PROFIBUS parameters for the HMI connection An overview of the configured HMI connection parameters can be found in the properties for the HMI connection. Only limited changes are possible in this Inspector window. 3716 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs Displaying and editing HMI connection parameters 1. Click the HMI connection in the "Devices & Networks" editor. 2. Change the parameters of the HMI connection in the Inspector window under "Properties > General > General". "Connection" The "Connection" area displays the HMI connection created for communication between the devices. You can edit the name of the HMI connection in this area. "Connection path" The communication partners of the selected HMI connection and the associated PROFIBUS parameters are displayed in the "Connection path" area. Some of the areas displayed cannot be edited in this dialog. "End point" Displays the device name. This area cannot be edited. "Interface" Displays the selected interface of the device. You can choose between several interfaces, depending on the device. "Interface type" Displays the selected interface type. This area cannot be edited. WinCC Basic V13.0 System Manual, 02/2014 3717 Visualize processes 10.8 Communicating with PLCs "Subnet" Displays the selected subnet. This area cannot be edited. "Address" Displays the PROFIBUS address of the device. This area cannot be edited. "Find connection path" button Enables the subsequent specification of connections. PROFIBUS parameters for the HMI device PROFIBUS parameters for the HMI device An overview of the configured HMI device parameters can be found in the properties for the HMI device. Displaying and changing PROFIBUS parameters of the HMI device 1. Click the HMI device in the "Devices & Networks" editor. 2. Change the parameters of the HMI device in the Inspector window under "Properties > General > General". 3718 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs "Interface networked with" In the "Interface networked with" area, select the subnet of the HMI connection via which the HMI device is connected to the network. You use the "Add new subnet" button to create a new subnet. "Parameters" "Interface type" Depending on the HMI device type, you have various interfaces to choose from. "Address" You assign the PROFIBUS address of the HMI device in the "Address" area. The PROFIBUS address must be unique throughout the PROFIBUS network. "Highest address" The "Highest address" area displays the highest address of the PROFIBUS network. "Transmission speed" The "Transmission speed" is determined by the slowest device connected to the network. The setting is identical throughout the network. PROFIBUS parameters for the PLC PROFIBUS parameters for the PLC An overview of the configured parameters can be found in the properties for the PLC. WinCC Basic V13.0 System Manual, 02/2014 3719 Visualize processes 10.8 Communicating with PLCs Displaying and changing PROFIBUS parameters of the PLC 1. Click the PLC in the "Devices & Networks" editor. 2. Change the parameters of the PLC in the Inspector window under "Properties > General > General". "Interface networked with" In the "Subnet" area, select the subnet of the HMI connection via which the PLC is connected to the network. You use the "Add new subnet" button to create a new subnet. "Parameters" "Interface type" Depending on the HMI device type, you have various interfaces to choose from. "Address" You assign the PROFIBUS address of the HMI device in the "Address" area. The PROFIBUS address must be unique throughout the PROFIBUS network. "Highest address" The "Highest address" area displays the highest address of the PROFIBUS network. "Transmission speed" The "Transmission speed" is determined by the slowest device connected to the network. The setting is identical throughout the network. 3720 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs Bus profiles with PROFIBUS Introduction Depending on the device types connected and protocols used on the PROFIBUS, different profiles are available. The profiles differ in terms of the setting options and calculation of bus parameters. The profiles are explained below. Devices with different profiles on the same PROFIBUS subnet The PROFIBUS subnet only functions without problem if the bus parameters of all devices have the same values. Profiles and transmission rates Profiles Supported transmission speeds in Kbits/s DP 9,6 19,2 45,45 93,75 187,5 500 1500 3000 6000 12000 Standard 9,6 19,2 45,45 93,75 187,5 500 1500 3000 6000 12000 Universal 9,6 19,2 93,75 187,5 500 1500 Meaning of profiles Profile Meaning DP Select the "DP" bus profile when the only devices connected to the PROFIBUS subnet are those which satisfy the requirements of standard EN 50170 Volume 2/3, Part 8-2 PROFIBUS. The bus parameter setting is optimized on these devices. This includes devices with DP master and DP slave interfaces of the SIMATIC S7 and distributed I/Os of other manufacturers. Standard Compared to the "DP" profile, the "Standard" profile also offers scope for devices of another project or devices which have not been configured here to be taken into account when calculating the bus parameters. The bus parameters are then calculated following a simple, non-optimized algorithm. Universal Select the "Universal" bus profile when individual devices on the PROFIBUS subnet use the PROFIBUS-FMS service. This includes the following devices for example: CP 343-5 PROFIBUS-FMS devices of other manufacturers As with the "Standard" profile, this profile allows you to take other devices into account when calculating the bus parameters. WinCC Basic V13.0 System Manual, 02/2014 3721 Visualize processes 10.8 Communicating with PLCs Protection of communication Security levels If you want to protect the PLC and HMI device communication, you can assign protection levels for the communication. For a SIMATIC S7-1500 CPU, you can enter multiple passwords and thereby set up different access rights for various user groups. The passwords are entered in a table, so that exactly one protection level is assigned to each password. The effect of the password is given in the "Protection" column. For the SIMATIC S7-1200 controller, several aspects need to be considered when setting protection levels. For additional information on this, see: Auto-Hotspot Example You select the "Complete protection" protection level for a standard CPU (i.e., not an F-CPU) when configuring it. Afterwards, you enter a separate password for every protection level above it in the table. For users who do not know any of the passwords, the CPU is completely protected. Not even HMI access is possible. For users who know one of the assigned passwords, the effect depends on the table row in which the password occurs: The password in row 1 (no protection) allows access as if the CPU were completely unprotected. Users who know this password have unrestricted access to the CPU. The password in row 2 (write protection) allows access as if the CPU were write-protected. Despite knowing the password, users who know this password only have read access to the CPU. The password in row 3 (read and write protection) allows access as if the CPU were readprotected and write-protected, so that only HMI access is possible for users who know this password. Access password for the HMI connection Introduction You secure access to a PLC by assigning a password. You assign the password when you configure the password. A password is mandatory as of protection level "Complete protection". Communication cannot be established with the PLC if you enter no password or an incorrect password. 3722 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs Assigning password You enter the password for the PLC in the "Connections" editor. 10.8.7.4 Data exchange Data exchange using area pointers General information on area pointers Introduction You use an area pointer to access a data area in the PLC. During communication, the PLC and the HMI device alternately access these data areas for read and write operations. The PLC and the HMI device trigger defined interactions based on the evaluation of stored data. Configuration of area pointers Before you use an area pointer, you enable it under "Connections > Area pointer". You then assign the area pointer parameters. You can find more detailed information on configuring area pointers in: Configuration of area pointers WinCC Basic V13.0 System Manual, 02/2014 3723 Visualize processes 10.8 Communicating with PLCs Area pointer "Date/time" Function This area pointer is used to transfer the date and time from the HMI device to the PLC. The PLC writes control job "41" to the job mailbox. When it evaluates the control job, the HMI device writes its current date and the time in the data area configured in the "Date/time" area pointer. Note You cannot use the "Date/Time PLC" area pointer if you have configured the "Date/Time" area pointer. The "Date/Time" area pointer when used in a project which contains multiple connections must be enabled for each configured connection. The date/time data area has the following structure: Data word Most significant byte 7 Least significant byte 0 7 0 n+0 Reserved Hour (0 to 23) n+1 Minute (0 to 59) Second (0 to 59) n+2 Reserved Reserved n+3 Reserved Weekday (1 to 7, 1=Sunday) n+4 Day (1 to 31) Month (1 to 12) n+5 Year (80 to 99/0 to 29) Reserved Time Date Note When making entries in the "Year" data area, you should note that values 80 to 99 result in years 1980 through 1999, while the values 0 to 29 result in the years 2000 through 2029. Permitted data types You can use the following data types when you configure the "Date/Time" area pointer. Word UInt DTL Use of the "DTL" data type Use of data type "DTL" with communication driver S7-1200. A tag of the "DTL" data type has a length of 12 bytes and saves information on date and time in a predefined structure. 3724 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs The "DTL" data type has the following structure: Byte Component Data type Value range 0 Year UINT 1970 to 2554 2 Month USINT 0 to 12 3 Day USINT 1 to 31 4 Day of week USINT 1(Sunday) to 7(Saturday) 5 Hour USINT 0 to 23 6 Minute USINT 0 to 59 7 Second USINT 0 to 59 8 Nanoseconds UDINT 0 to 999 999 999 1 The weekday is not considered in the value entry. 9 10 11 The "DTL" data type supports time information down to the nanosecond range. Because panels only support time information down to the millisecond, you may encounter the following restriction when using the area pointers: For the transmission of time information from a panel to the controller, the smallest unit of time is 1 millisecond. The value range from microseconds to nanoseconds of the "DTL" data type is filled with zeros. "Date/time PLC" area pointer Function This area pointer is used to transfer the date and time from the PLC to the HMI device. Use this area pointer if the PLC is the time master. The PLC loads the data area of the area pointer. The HMI device reads the data cyclically within the configured acquisition cycle and synchronizes itself. Note Set an acquisition cycle of sufficient length for the date/time area pointer PLC to avoid any negative impact on HMI device performance. Recommended: Acquisition cycle of 1 minute, if the process allows this. WinCC Basic V13.0 System Manual, 02/2014 3725 Visualize processes 10.8 Communicating with PLCs "Date/Time PLC" is a global area pointer and may be configured only once per project. Note You cannot use the "Date/Time" area pointer if you have configured the "Date/Time PLC" area pointer. The date/time data area has the following structure: DATE_AND_TIME format (in BCD code) Data word Most significant byte 7 n+0 1) ...... Year (80 to 99/0 to 29) Least significant byte 0 7 ...... 0 Month (1 to 12) n+1 Day (1 to 31) Hour (0 to 23) n+2 Minute (0 to 59) Second (0 to 59) n+3 Reserved Reserved Weekday (1 to 7, 1=Sunday) n+4 1) Reserved Reserved n+5 1) Reserved Reserved The two data words must exist in the data area to ensure that the data format matches WinCC flexible and to avoid reading false information. Note When making entries in the "Year" data area, you should note that values 80 to 99 result in years 1980 through 1999, while the values 0 to 29 result in the years 2000 through 2029. Permitted data types You can use the following data types when you configure the "Date/Time PLC" area pointer: DTL Use of the "DTL" data type Use of data type "DTL" with communication driver S7-1200. A tag of the "DTL" data type has a length of 12 bytes and saves information on date and time in a predefined structure. The "DTL" data type has the following structure: 3726 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs Byte Component Data type Value range 0 Year UINT 1970 to 2554 2 Month USINT 0 to 12 3 Day USINT 1 to 31 4 Day of week USINT 1(Sunday) to 7(Saturday) 1 The weekday is not considered in the value entry. 5 Hour USINT 0 to 23 6 Minute USINT 0 to 59 7 Second USINT 0 to 59 8 Nanoseconds UDINT 0 to 999 999 999 9 10 11 The HMI devices do not support the use of nanoseconds. Values in the nanosecond range will be ignored during processing in Runtime. The "DTL" data type supports time information down to the nanosecond range. Because panels only support time information down to the millisecond, you may encounter the following restriction when using the area pointers: For the transmission of time information from a controller to a panel, the range from microseconds to nanoseconds is ignored. The time information is processed on the panel down to milliseconds. Area pointer "Coordination" Function The "Coordination" area pointer is used to implement the following functions: Detecting the startup of the HMI device in the control program Detecting the current operating mode of the HMI device in the control program Detecting whether the HMI device is ready to communicate in the control program By default, the "Coordination" area pointer has the length of one word and cannot be changed. Usage Note The HMI device always writes the entire coordination area when updating the area pointer. The control program can for this reason not make changes to the coordination area. WinCC Basic V13.0 System Manual, 02/2014 3727 Visualize processes 10.8 Communicating with PLCs Assignment of the bits in the "Coordination" area pointer /HVVVLJQLILFDQWE\WH 0RUHVLJQLILFDQWE\WH VWZRUG ; ; ; UHVHUYHG [ DVVLJQHG 6WDUWXSELW 2SHUDWLQJPRGH /LIHELW Startup bit The startup bit is set briefly to "0" by the HMI device during startup. It sets the bit permanently to "1" when startup is completed. Operating mode The operating mode bit is set to 1 as soon as the user switches the HMI device offline. The status of the operating mode bit is "0" during normal operation of the HMI device. You can determine the current operating mode of the HMI device by reading this bit in the control program. Life bit The HMI device inverts the life bit at intervals of approximately one second. You can check whether or not there is still a connection to the HMI device by querying this bit in the control program. Processing in the PLC For a simpler evaluation in the PLC program, use a Bool array for this area pointer when using the SIMATIC S7 1200 communication driver. You will have to map the complete 16-bit word of the area pointer. Configure a tag of the data type "Array [0 .. 15] of bool" for this purpose. Permitted data types You can use the following data types when you configure the "Coordination" area pointer. Word UInt Bool 3728 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs Area pointer "Screen number" Function The HMI devices store information about the screen called up on the HMI device in the "Screen number" area pointer. This allows the transfer of the current screen contents from the HMI device to the PLC. Certain reactions can be triggered in the PLC, such as the call of a different screen. Use Before the "Screen number" area pointer can be used, it must be set up and activated by selecting "Communication Area pointer". You can create only one instance of the "Screen number" area pointer and only on one PLC. The screen number is always transferred to the PLC when a new screen is activated or when the focus within a screen changes from one screen object to another. Structure The area pointer is a data area in the memory of the PLC with a fixed length of 5 words. 15 14 13 12 11 10 9 8 7 6 1. Word Current screen type 2. Word Current screen number 3. Word Reserved 4th word Current field number 5. Word Reserved 5 4 3 2 1 0 Current screen type "1" for root screen or "4" for permanent window Current screen number 1 to 32767 Current field number 1 to 32767 Note Device dependency Permanent windows are not available on Basic Panels. WinCC Basic V13.0 System Manual, 02/2014 3729 Visualize processes 10.8 Communicating with PLCs Permitted data types You can use the following data types when you configure the "Screen number" area pointer. Word UInt Area pointer "Project ID" Function When Runtime starts, a check can be carried out as to whether the HMI device is connected to the correct PLC. This check is important when operating with several HMI devices. For this, the HMI device compares a value stored on the PLC with the value specified in configuration. This ensures compatibility of the configuration data with the PLC program. A missing compatibility results in a corresponding alarm and Runtime will not be started. Use Note HMI connections cannot be switched "online". The HMI connection in which the "Project ID" area pointer is used must be switched "online". To use this area pointer, set up the following during the configuration: Define the version of the configuration. Values between 1 and 255 are possible. You enter the version in the editor "Runtime settings > General" in the "Identification" area. This is where you select the PLC tag or the tag array that you have configured as the data area for the area pointer. Connection failure A connection failure to a device on which the "project ID" area pointer is configured results in all the other connections of the device being switched to "offline". This behavior has the following requirements: You have configured several connections in a project. You are using the "project ID" area pointer in at least one connection. Causes which may set connections "offline": The PLC is not available. The connection has been switched offline in the engineering system. 3730 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs Permitted data types You can use the following data types when you configure the "Project ID" area pointer. Word UInt Area pointer "Job mailbox" Function The PLC can use the job mailbox to transfer jobs to the HMI device to trigger corresponding actions on the HMI device. These functions include, for example: Display screen Set date and time Data structure The first word of the job mailbox contains the job number. Depending on the job mailbox, up to three parameters can be transferred. Word Most significant byte Least significant byte n+0 0 Job number n+1 Parameter 1 n+2 Parameter 2 n+3 Parameter 3 The HMI device evaluates the job mailbox if the first word of this job is not equal to zero. This means that the parameters must be entered in the job mailbox first, followed by the job number. When the HMI device accepts the job mailbox, the first word is set to 0 again. The execution of the job mailbox is generally not completed at this point in time. Job mailboxes All job mailboxes and their parameters are listed below. The "No." column contains the job number of the job mailbox. Job mailboxes can only be triggered by the PLC when the HMI device is online. No . Function 14 Set time (BCD-coded) WinCC Basic V13.0 System Manual, 02/2014 Parameter 1 Left byte: Right byte: hours (0-23) Parameter 2 Left byte: minutes (0-59) Right byte: seconds (0-59) Parameter 3 - 3731 Visualize processes 10.8 Communicating with PLCs No . Function 14 Set time (BCD-coded) 15 23 Set date (BCD-coded) Parameter 1 Left byte: Right byte: weekday (1-7: Sunday-Saturday) Parameter 2 Left byte: day (1-31) Right byte: month (1-12) Parameter 3 Left byte: year User logon Logs the user on with the name "PLC user" at the HMI device with the group number transferred in Parameter 1. The logon is possible only when the transferred group number exists in the project. 24 Parameter 1 Group number 1 to 255 Parameter 2, 3 - User logoff Logs off the current user. (The function corresponds to the "logoff" system function) Parameter 1, 2, 3 40 - Transfer date/time to PLC An interval of at least 5 seconds must be maintained between two successive jobs to prevent overload of the HMI device. Parameter 1, 2, 3 41 - Transfer date/time to PLC An interval of at least 5 seconds must be maintained between two successive jobs to prevent overload of the HMI device. Parameter 1, 2, 3 46 - Update tag Causes the HMI device to read the current value of the tags from the PLC whose update ID matches the value transferred in Parameter 1. (Function corresponds to the "UpdateTag" system function.) Parameter 1 49 1 - 100 Clear event buffer Deletes all analog alarms and discrete alarms of the "Warnings" class from the alarm buffer. Parameter 1, 2, 3 50 - Clear error alarm buffer Deletes all analog alarms and discrete alarms of the "Errors" class from the alarm buffer. Parameter 1, 2, 3 51 69 3732 - Display selection Parameter 1 Screen number Parameter 2 - Parameter 3 Field number Reading data record from PLC 1) Parameter 1 Recipe number (1-999) Parameter 2 Data record number (1-65535) WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs No . Function 14 Set time (BCD-coded) Parameter 3 0: Do not overwrite existing data record 1: Overwrite existing data record 70 Writing data record to PLC 1) Parameter 1 Recipe number (1-999) Parameter 2 Data record number (1-65535) Parameter 3 - 1) Only devices supporting recipes 2) OP 73, OP 77A and TP 177A HMI devices also execute the "Screen selection" job mailbox if the on-screen keyboard is active. 3) The weekday is ignored on HMI device KTP 600 BASIC PN. Permitted data types You can use the following data types when you configure the "Screen number" area pointer: Word UInt "Data record" area pointer "Data mailbox" area pointer Function When data records are transferred between the HMI device and PLC, both partners access common communications areas on the PLC. Data transfer types There are two ways of transferring data records between the HMI device and PLC: Transfer without synchronization Transfer with synchronization over the data mailbox Data records are always transferred directly. That is, the tag values are read from an address or written to an address configured for this tag directly, without redirecting the values by means of interim memory. WinCC Basic V13.0 System Manual, 02/2014 3733 Visualize processes 10.8 Communicating with PLCs Initiating the transfer of data records There are three ways of triggering the transfer: Operator input in the recipe view Job mailboxes The transfer of data records can also be triggered by the PLC. Triggering by configured functions If the transfer of data records is triggered by a job mailbox, the data in the recipe view will be updated as well. Avoid operating the recipe view while job mailboxes for transfer of data records are being triggered. If you have already started editing a data record and a job mailbox is triggered for transfer of data records, then this job mailbox will be rejected. Permitted data types You can use the following data types when you configure the "Data record" area pointer. Word UInt Transfer without synchronization If you select asynchronous transfer of data records between the HMI device and PLC, there is no coordination over the common data areas. It is therefore unnecessary to set up a data area during configuration. Asynchronous data record transfer can be a useful alternative, for example, when: The system is capable of excluding the risk of uncontrolled overwriting of data by the communication peer. The PLC does not require information about the recipe number and data record number. The transfer of data records is triggered by the operator of the HMI device. Reading values When a read job is triggered, the values are read from the PLC addresses and transferred to the HMI device. Triggering by the operator in the recipe view: The values are downloaded to the HMI device. You can then process, edit, or save these values, for example. Triggering by a function or job mailbox: The values are saved immediately to the data volume. 3734 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs Writing values When a write job is triggered, the values are written to the PLC addresses. Triggering by the operator in the recipe view: The current values are written to the PLC. Triggering by a function or job mailbox: The current values are written to the PLC from the data medium. Sequence of a transfer started by the operator in the recipe display Reading from the PLC started by the operator in the recipe view Step Action 1 Check: Status word = 0? Yes No 2 The HMI device enters the recipe number to be read and the status "Transferring" in the data mailbox and sets the data record number to 0. Abort with system alarm. 3 The HMI device reads the values from the PLC and displays them in the recipe view. If the recipes have synchronized tags, the values from the PLC are also written to the tags. 4 The HMI device sets the status "Transfer completed." 5 The control program must reset the status word to zero in order to enable further transfers. Writing to the PLC started by the operator in the recipe view Step Action Check: Status word = 0? 1 Yes The HMI device enters the recipe and data record number to be written and the status "Transferring" in the data mailbox. 2 No Abort with system alarm. The HMI device writes the current values to the PLC. If the recipes have synchronized tags, the changed values are synchronized between the recipe view and tags and then written to the PLC. WinCC Basic V13.0 System Manual, 02/2014 3 The HMI device sets the status "Transfer completed." 4 If required, the control program can now evaluate the transferred data. 5 The control program must reset the status word to zero in order to enable further transfers. 3735 Visualize processes 10.8 Communicating with PLCs Note The status word may only be set by the HMI device. The PLC may only reset the status word to zero. Note The PLC may only evaluate the recipe and data record numbers when data inconsistency is detected if one of the conditions outlined below has been met: The data mailbox status is set to "Transfer completed". The data mailbox status is set to "Transfer completed with error". Sequence of the transfer triggered by a job mailbox The transfer of data records between the HMI device and the PLC can be initiated by either one of these stations. The two job mailboxes No. 69 and No. 70 are available for this type of transfer. No. 69: Read data record from PLC ("PLC DAT") Job mailbox no. 69 transfers data mailboxes from the PLC to the HMI device. The job mailbox is structured as follows: Most significant byte Least significant byte 0 69 Word 1 Word 2 Recipe number (1-999) Word 3 Data record number (1-65,535) Word 4 Do not overwrite existing data record: 0 Overwrite existing data record: 1 No. 70: Write data record to PLC ("DAT PLC") Job mailbox no. 70 transfers data mailboxes from the HMI device to the PLC. The job mailbox is structured as follows: Word 1 3736 Most significant byte Least significant byte 0 70 Word 2 Recipe number (1-999) Word 3 Data record number (1-65,535) Word 4 -- WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs Sequence when reading from the PLC with job mailbox "PLC DAT" (no. 69) Step Action 1 Check: Status word = 0? Yes No 2 The HMI device enters the recipe and data record number specified in the job and the status "Transferring" in the data mailbox. Abort without return message. 3 The HMI device reads the values and stores the values in the data record specified in the job mailbox. 4 If "Overwrite" was selected in the job, an existing data record is overwritten without any prompt for confirmation. The HMI device sets the status "Transfer completed". If "Do not overwrite" was selected in the job, and the data record already exists, the HMI device aborts the job and enters 0000 1100 in the status word of the data mailbox. 5 The control program must reset the status word to zero in order to enable further transfers. Sequence writing to the PLC with job mailbox "DAT PLC" (no. 70) Step Action 1 Check: Status word = 0? Yes No 2 The HMI device enters the recipe and data record number specified in the job and the status "Transferring" in the data mailbox. Abort without return message. 3 The HMI device fetches the values of the data record specified in the job from the data medium and writes the values to the PLC. 4 The HMI device sets the status "Transfer completed." 5 The PLC program can now evaluate the transferred data. To allow further transfers, the PLC program must set the status word to 0 again. Sequence of the transfer when triggered by a configured function Reading from the PLC using a configured function WinCC Basic V13.0 System Manual, 02/2014 Step Action 1 Check: Status word = 0? Yes No 2 The HMI device enters the recipe and data record number specified in the function and the status "Transferring" in the data mailbox. Abort with system alarm. 3 The HMI device reads the values from the PLC and stores them in the data record specified in the function. 3737 Visualize processes 10.8 Communicating with PLCs Step 4 Action If "Yes" was selected for the "Overwrite" function, an existing data record is overwritten without any prompt for confirmation. The HMI device sets the status "Transfer completed." If "No" was selected for the "Overwrite" function and the data record already exists, the HMI device aborts the job and enters 0000 1100 in the status word of the data mailbox. 5 The control program must reset the status word to zero in order to enable further transfers. Writing to the PLC by means of configured function Step Action 1 Check: Status word = 0? Yes No 2 The HMI device enters the recipe and data record number specified in the function and the status "Transferring" in the data mailbox. Abort with system alarm. 3 The HMI device fetches the values of the data record specified in the function from the data medium and transfers the values to the PLC. 4 The HMI device sets the status "Transfer completed." 5 The control program can now evaluate the transferred data. The control program must reset the status word to zero in order to enable further transfers. Possible causes of error when transferring data records Possible causes of error The section below shows possible error causes which lead to the cancellation of data record transfer: Tag address not set up on the PLC Overwriting data records not possible 3738 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs Recipe number does not exist Data record number does not exist Note The status word may only be set by the HMI device. The PLC may only reset the status word to zero. Note The PLC may only evaluate the recipe and data record numbers when data inconsistency is detected if one of the conditions outlined below has been met: The data mailbox status is set to "Transfer completed". The data mailbox status is set to "Transfer completed with error". Reaction to an aborted transfer due to errors If the transfer of data records is aborted due to errors, the HMI device reacts as follows: Triggering by the operator in the recipe view Information in the status bar of the recipe view and output of system alarms Triggered by function Output of system alarms Triggering by job mailbox No return message on the HMI device You can nonetheless evaluate the status of the transfer by querying the status word in the data mailbox. Note Availability for specific devices Notes in the status bar of the recipe view are not available in Basic Panels. Trends Trends A trend is the graphical representation of one or more values from the PLC. The value is read out time-triggered for Basic Panels. For additional information see: Configuring trend displays for values from the PLC (Page 3369) Time-triggered trends The HMI device reads in the trend values cyclically at an interval specified in the configuration. WinCC Basic V13.0 System Manual, 02/2014 3739 Visualize processes 10.8 Communicating with PLCs Time-triggered trends are suitable for continuous curves, such as the operating temperature of a motor. Alarms Configuring alarms Configure alarms Several steps are needed to configure alarms, such as operational messages, error alarms, and acknowledgement. Step 1: Create tags Step 2: Configure alarms Step 3: Configure acknowledgment You can find additional information in the section: Working with alarms (Page 3379) Distinctive features when configuring alarms If you are configuring connections of HMI devices to PLCs of other manufacturers, note the following distinctive features when configuring: Data types of the tags Addressing of tags How the bit positions are counted Data types For connections with a SIMATIC communication driver, the following data types are supported: PLC SIMATIC S7 PLCs 3740 Permitted data types Discrete alarms Analog alarms WORD, INT BYTE, CHAR, WORD, INT, DWORD, DINT, REAL, TIMER WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs How the bit positions are counted For connections with a SIMATIC communication driver, the following counting method applies: How the bit positions are counted Byte 0 Byte 1 Most significant byte Least significant byte In SIMATIC S7 PLCs 7 0 7 0 In WinCC you configure: 15 8 7 0 Acknowledgment of alarms Procedure Create suitable tags on the PLC to acknowledge an error alarm. You assign these tags to an alarm in the "Bit messages" editor. You make the assignment in "Properties > Acknowledgment". Distinction in terms of acknowledgment: Acknowledgment by the PLC Acknowledgment on the HMI device Acknowledgment by the PLC In "PLC acknowledgment tag", configure the tag or array tag and the bit number that the HMI device uses to identify a PLC acknowledgment. A bit set in the tag triggers acknowledgment of the assigned error alarm bit at the HMI device. This tag bit returns a function similar to acknowledgment on the HMI device which is triggered by pressing the "ACK" button, for example. The acknowledgment bit must be located in the same tag as the bit for the error alarm. Reset the acknowledgment bit before setting the bit in the alarm area again. The figure below shows the pulse diagram. (UURUDODUP $FNQRZOHGJPHQW 3/&+0,GHYLFH $UULYDORIWKH $FNQRZOHGJP 5HVHWRI HUURUDODUP YLD3/& DFNQRZOHGJPELW WinCC Basic V13.0 System Manual, 02/2014 1HZ HUURUDODUP 3741 Visualize processes 10.8 Communicating with PLCs Acknowledgment on the HMI device In the "HMI acknowledgment tag" area, configure the tag or array tag as well as the bit number that the HMI device writes to the PLC after acknowledgment. Make sure when you use an array tag that it is not longer than 6 words. To always create a signal change when setting an assigned acknowledgment bit of a discrete alarm that must be acknowledged, the HMI device will reset the acknowledgment bit assigned to the alarm as soon as it detects an alarm subject to acknowledgment and write the acknowledgment tag in the PLC. There will be a certain delay between detecting the message and writing the acknowledgment tag in the PLC because the HMI device has to process the operations. If a discrete alarm subject to acknowledgment is acknowledged by the HMI device, then the corresponding bit in the assigned acknowledgment tag will be set. The entire acknowledgment tag is then written to the PLC by the HMI device. This allows the PLC to recognize that a certain alarm message has been acknowledged at the HMI device. Note All alarm bits acknowledged since the last Runtime start will remain in the acknowledgment tag until a new incoming of the respective discrete alarms is detected. This area should only be read by the PLC because the entire section of the HMI device will be overwritten once the next acknowledgment tag is written. The figure below shows the pulse diagram. (UURUDODUP $FNQRZOHGJPHQW +0,GHYLFH3/& $UULYDORIWKH HUURUDODUP 10.8.7.5 5HVHWRI DFNQRZOHGJPELW $FNQRZOHGJP YLD+0,GHYLFH 1HZ HUURUDODUP Performance features of communication S7-1200 device dependency Communication with the SIMATIC S7-1200 controller If you use devices from an earlier version of the TIA Portal with TIA Portal V12 SP1, it may not be possible to configure integrated connections to certain HMI devices. 3742 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs Basic Panels V11.0 HMI devices SIMATIC S7-1200 (V1) SIMATIC S7-1200 (V2) SIMATIC S7-1200 (V2.2) SIMATIC S7-1200 (V3) SIMATIC S7-1200 (V4) KP300 Basic Yes Yes Yes Yes Yes KP400 Basic Yes Yes Yes Yes Yes KTP400 Basic PN Yes Yes Yes Yes Yes KTP600 Basic DP Yes Yes Yes Yes Yes KTP600 Basic PN Yes Yes Yes Yes Yes KTP1000 Basic DP Yes Yes Yes Yes Yes KTP1000 Basic PN Yes Yes Yes Yes Yes TP1500 Basic PN Yes Yes Yes Yes Yes Basic Panels V12.0 HMI devices SIMATIC S7-1200 (V1) SIMATIC S7-1200 (V2) SIMATIC S7-1200 (V2.2) SIMATIC S7-1200 (V3) SIMATIC S7-1200 (V4) KP300 Basic No Yes Yes Yes Yes KP400 Basic No Yes Yes Yes Yes KTP400 Basic PN No Yes Yes Yes Yes KTP600 Basic DP No Yes Yes Yes Yes KTP600 Basic PN No Yes Yes Yes Yes KTP1000 Basic DP No Yes Yes Yes Yes KTP1000 Basic PN No Yes Yes Yes Yes TP1500 Basic PN Yes Yes Yes Yes No Basic Panels V13.0 HMI devices SIMATIC S7-1200 (V1) SIMATIC S7-1200 (V2) SIMATIC S7-1200 (V2.2) SIMATIC S7-1200 (V3) SIMATIC S7-1200 (V4) KTP700 Basic PN No Yes Yes Yes Yes KTP900 Basic PN No Yes Yes Yes Yes WinCC Basic V13.0 System Manual, 02/2014 3743 Visualize processes 10.8 Communicating with PLCs Valid data types for SIMATIC S7-1200 Valid data types for connections with SIMATIC S7-1200 The table lists the data types that can be used when configuring tags and area pointers. 10.8.7.6 Data type Length BOOL 1 bit SINT 1 byte INT 2 bytes DINT 4 bytes USINT 1 byte UINT 2 bytes UDINT 4 bytes REAL 4 bytes LREAL 8 bytes TIME 4 bytes DATE 2 bytes DTL 12 bytes TIME_OF_DAY, TOD 4 bytes STRING (2+n) bytes, n = 0 to 254 CHAR 1 byte Array of CHAR -- BYTE 1 byte WORD 2 bytes DWORD 4 bytes Creating connections in the "Connections" editor Creating a PROFINET connection Requirements A project is open. An HMI device with a PROFINET interface has been created. 3744 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs Procedure 1. Open the "Connections" editor of the HMI device. 2. Double-click "<Add>". 3. In the "Communication drivers" column, select the "SIMATIC S7 1200" driver. 4. Click the name of the connection. WinCC Basic V13.0 System Manual, 02/2014 3745 Visualize processes 10.8 Communicating with PLCs 5. Select a PROFINET interface of the HMI device in the Inspector window under "Parameters > Interface". 6. Set the IP addresses of the communication partners in the Inspector window: - HMI device: "Parameters > HMI device > Address" - PLC: "Parameters > PLC > Address" Creating a PROFIBUS DP connection Requirements A project is open. An HMI device with a PROFIBUS interface has been created. 3746 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs Procedure 1. Open the "Connections" editor of the HMI device. 2. Double-click "<Add>". 3. In the "Communication drivers" column, select the "SIMATIC S7 1200" driver. 4. Click the name of the connection. 5. Select the "MPI/DP" interface in the Inspector window under "Parameters". WinCC Basic V13.0 System Manual, 02/2014 3747 Visualize processes 10.8 Communicating with PLCs 6. Select the "DP" profile in the Inspector window under "Parameters > Network". 7. Set the addresses of the communication partners in the Inspector window: - HMI device: "Parameters > HMI device > Address" - PLC: "Parameters > PLC > Address" Parameters for the connection Parameters for the connection (SIMATIC S7 1200) Parameters to be set To assign the connection parameters, such as addresses and profiles, click the connection that you have created in the "Connections" editor. The communication partners are displayed schematically in the Inspector window under "Parameters". The "HMI device", "Network", and "PLC" areas are available for assigning parameters according to the interface used. 3748 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs WinCC Basic V13.0 System Manual, 02/2014 3749 Visualize processes 10.8 Communicating with PLCs Ethernet parameters Parameters for the HMI device You set the parameters for the HMI device in the network under "HMI device".. The changes are not transferred automatically to the HMI device. You must change the settings in the Control Panel of the HMI device. "Interface" If you are directly connected to the HMI device during configuration, you can set up the IP address of the HMI device in WinCC. Note The IP address in the Control Panel will be overwritten upon subsequent loading if you have already set up the IP address in the HMI device control panel. The IP address already set up in the Control Panel will be retained upon subsequent loading if you activate "Set IP address using a different method". The IP address is transferred to the HMI device during project transfer. To set up the IP address of the HMI device: - Click the HMI device. - Open the "Device configuration" editor. - Click the Ethernet interface. - Assign the IP address in the inspector window under: "General > PROFINET interface > Ethernet addresses" "Address" You assign the IP address of the HMI device in the "Address" area. When you transfer the WinCC project to the HMI device, this IP address is set up directly in the HMI device. "Access point" Specifies the access point for the PG/PC interface that can be used to reach the communication partner. 3750 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs Parameters for the PLC Under "PLC", you address the S7 module with which the HMI device will exchange data. Assign a name for the connection for each communication partner. "Address" Under "Address", set the IP address of the S7 module to which the HMI device is connected. "Access password" Enter a password in the "Access password" field. This password must match the one you saved to the PLC. Note You only need a password if you have set "Complete protection" at the PLC. No connection is set up to the PLC if the "Complete protection" security level is stored on the PLC and you do not enter a password. PROFIBUS parameters Parameters for the HMI device You assign the parameters for the HMI device in the network once under "HMI device". The change applies to each communication partner. "Type" Specifies the physical connection used. "Interface" For "Interface", you select the HMI device interface via which the HMI device is connected to the PROFIBUS network. "Baud rate" For "Baud rate", you set the transmission speed of the data in the network. The baud rate is determined by the slowest HMI device connected to the network. The setting must be identical throughout the network. Note If you set a baud rate of 1.5 Mbaud for OP 73 or OP 77A, the highest station address must be less than or equal to 63. "Address" You set the PROFIBUS address of the HMI device under "Address". The PROFIBUS address must be unique in the PROFIBUS network. WinCC Basic V13.0 System Manual, 02/2014 3751 Visualize processes 10.8 Communicating with PLCs "Only master on bus" Disables an additional safety feature against bus faults when the HMI device is connected to the network. A passive station (slave) can only send data if it is requested to do so by an active station (master). In S7-200, you must set an HMI device as the master. "Access point" The access point defines a logical device name through which the communication partner can be reached. Parameters for the network Under "Network", you set the parameters for the PROFIBUS network to which the HMI device is linked. "Profile" For "Profile", you select the network profile that is used in the network. In "Profile", set "DP", "Universal", or "Standard". The setting must be identical throughout the network. "Highest address" For "Highest station address", set the highest station address. The highest station address must be greater than or equal to the highest actual PROFIBUS address. The setting must be identical throughout the network. Note If you set a baud rate of 1.5 Mbaud in the OP 73 or the OP 77A, the highest station address must be less than or equal 63. "Number of masters" For "Number of masters", set the number of masters in the PROFIBUS network. This information is necessary to correctly calculate the bus parameters. 3752 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs Parameters for the PLC Under "PLC", you address the S7 module with which the HMI device will exchange data. Assign a name for the connection for each communication partner. "Address" For "Address", set the PROFIBUS address of the S7 module (CPU, FM, or CP) to which the HMI device is connected. "Access password" Enter a password in the "Access password" field. This password must match the one you saved to the PLC. Note You only need a password if you have set "Complete protection" at the PLC. No connection is set up to the PLC if the "Complete protection" security level is stored on the PLC and you do not enter a password. 10.8.8 Communicating with SIMATIC S7 300/400 10.8.8.1 Communication with SIMATIC S7 300/400 Introduction This section describes the communication between an HMI device and the SIMATIC S7 300 and S7 400 PLCs. These two PLCs will be referred to jointly as SIMATIC S7 300/400. You can configure the following communication channels for the SIMATIC S7 300/400 PLC: PROFINET PROFIBUS MPI HMI connection for communication You configure connections between the HMI device and a SIMATIC S7 300/400 in the "Devices & Networks" editor. WinCC Basic V13.0 System Manual, 02/2014 3753 Visualize processes 10.8 Communicating with PLCs 10.8.8.2 Communication via PROFINET Communication via PROFINET HMI connections via PROFINET If you have inserted an HMI device and a SIMATIC S7 300/400 into the project, you interconnect the two PROFINET interfaces in the "Devices & Networks" editor. You can also connect multiple HMI devices to one SIMATIC S7 300/400 and multiple SIMATIC S7 300/400s to one HMI device. The maximum number of communication partners that you can connect to an HMI device is dependent on the HMI device used. Additional information is available in the documentation for the respective HMI device. HMI connection in the "Devices & Networks" editor You configure the HMI connection between the PLC and the HMI device via PROFINET in the "Devices & Networks" editor. Connection in the "Connections" editor Alternatively, you configure the connection between the PLC and HMI device via PROFINET in the "Connections" editor of the HMI device. 3754 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs Configuring an HMI connection via PROFINET Introduction You configure an HMI connection between HMI devices and a SIMATIC S7 300/400 via PROFINET or Ethernet in the "Devices & Networks" editor. CAUTION Communication via Ethernet In Ethernet-based communication, the end user is responsible for the security of his data network. Targeted attacks can overload the device and interfere with proper functioning. Requirements The following communication partners are created in the "Devices & Networks" editor: HMI device with PROFINET or Ethernet interface SIMATIC S7 300/400 with PROFINET interface. Procedure 1. Double-click the "Devices & Networks" item in the project tree. The available communication partners in the project are displayed graphically in the network view. 2. Click the "Connections" button and select "HMI connection" for the connection type. The devices available for connection are highlighted in color. WinCC Basic V13.0 System Manual, 02/2014 3755 Visualize processes 10.8 Communicating with PLCs 3. Click the PROFINET interface of the PLC and use a drag-and-drop operation to draw a connection to the PROFINET or Ethernet interface of the HMI device. 4. Click the connecting line. 5. Click "Highlight HMI connection" and select the HMI connection. The connection is displayed graphically in the Inspector window. 6. Click the communication partners in the "Network view" and change the PROFINET parameters in the Inspector window according to the requirements of your project. See the chapter "PROFINET parameters (Page 3757)" for additional details. Note The created HMI connection is also shown in the tabular area of the editor on the "Connections" tab. You check the connection parameters in the table. You can change the local name for the connection only in the table. Result You have created a connection between an HMI device and a SIMATIC S7 300/400. The IP address and subnet mask connection parameters are configured. 3756 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs PROFINET parameters PROFINET parameters for the HMI connection PROFINET parameters for the HMI connection An overview of the configured HMI connection parameters can be found in the properties for the HMI connection. Only limited changes are possible in this Inspector window. Displaying and changing the HMI connection parameters 1. Click the HMI connection in the "Devices & Networks" editor. 2. Change the parameters of the HMI connection in the Inspector window under "Properties > General > General". WinCC Basic V13.0 System Manual, 02/2014 3757 Visualize processes 10.8 Communicating with PLCs "Connection" Displays whether the devices are networked together. - displayed if the devices are networked together. - displayed if the devices are not networked together. "Connection path" The communication partners of the selected HMI connection and the associated PROFINET parameters are displayed in the "Connection path" area. Some of the areas displayed cannot be edited in this dialog. "End point" Displays the device name. This area cannot be edited. "Interface" Displays the selected interface of the device. You can choose between several interfaces, depending on the device. "Interface type" Displays the selected interface type. This area cannot be edited. "Subnet" Displays the selected subnet. This area cannot be edited. "Address" Displays the selected IP address of the device. This area cannot be edited. "Find connection path" button Enables the subsequent specification of connections. PROFINET parameters for the HMI device PROFINET parameters for the HMI device An overview of the configured HMI device parameters can be found in the properties for the HMI device. 3758 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs Displaying and changing PROFINET parameters of the HMI device 1. Click the HMI device in the "Devices & Networks" editor. 2. Change the parameters of the HMI device in the Inspector window under "Properties > General". "Interface networked with" In the "Interface networked with" area, select the subnet of the HMI connection via which the HMI device is connected to the network. You use the "Add new subnet" button to create a new subnet. WinCC Basic V13.0 System Manual, 02/2014 3759 Visualize processes 10.8 Communicating with PLCs "IP protocol" "Set IP address in the project" When you transfer the WinCC project to the HMI device, this IP address is set up directly in the HMI device. Note The device is automatically restarted in the case of HMI devices with the Windows CE 3.0 operating system. HMI devices with Windows CE 3.0: OP 77B TP 177B color PN/DP TP 177B mono DP OP 177B color PN/DP OP 177B mono DP Mobile Panel 177 PN Mobile Panel 177 DP TP 277 6" OP 277 6" "Subnet mask" You assign data of the subnet mask in the "Subnet mask" area. "Use IP router" If you are using an IP router, select "Use IP router" and enter the router address in the "Router address" field. "Set IP address using a different method" If the function "Set IP address using a different method" is activated, the IP address is not taken from the project. You have to enter the IP address directly in the Control Panel of the HMI device. PROFINET parameters for the PLC PROFINET parameters for the PLC An overview of the configured parameters can be found in the properties for the PLC. 3760 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs Displaying and changing PROFINET parameters of the PLC 1. Click the PLC in the "Devices & Networks" editor. 2. Change the parameters of the PLC in the Inspector window under "Properties > General > General". "Interface networked with" In the "Subnet" area, select the subnet of the HMI connection via which the PLC is connected to the network. You use the "Add new subnet" button to create a new subnet. "IP protocol" "Interface type" Depending on the HMI device type, you have various interfaces to choose from. "IP address" You assign the IP address of the HMI device in the "IP address" area. "Subnet mask" You assign data of the subnet mask in the "Subnet mask" area. If you are using an IP router, select "Use IP router" and enter the router address in the field. WinCC Basic V13.0 System Manual, 02/2014 3761 Visualize processes 10.8 Communicating with PLCs Configuring Industrial Ethernet Rules for the network configuration The Ethernet interfaces of the devices have a default IP address that you can change. IP address The IP parameters are visible if the communication-capable devices support the TCP/IP protocol. The IP address consists of 4 decimal figures in the range of 0 to 255. The decimal figures are separated from one another by a dot. Example: 140.80.0.2 The IP address consists of the following: The address of the (sub) net The address of the node (generally also called host or network node) Subnet mask The subnet mask splits these two addresses. It determines which part of the IP address addresses the network and which part of the IP address addresses the node. The set bits of the subnet mask determine the network part of the IP address. Example: Subnet mask: 255.255.0.0 = 11111111.11111111.00000000.00000000 In the example given for the above IP address, the subnet mask shown here has the following meaning: The first 2 bytes of the IP address identify the subnet - i.e. 140.80. The last two bytes address the node, thus 0.2. It is generally true that: The network address results from AND linking the IP address and subnet mask. The node address results from AND NOT linking the IP address and subnet mask. Relation between IP address and default subnet mask An agreement exists relating to the assignment of IP address ranges and so-called "Default subnet masks". The first decimal number (from the left) in the IP address determines the structure of the default subnet mask. It determines the number of "1" values (binary) as follows: 3762 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 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs Note Range of values for the first decimal point A value of between 224 and 255 is also possible for the first decimal number of the IP address (address class D etc). This is, however, not recommended because there is no address check for these values. Masking other subnets You can use the subnet mask to add further structures and form "private" subnets for a subnet that is assigned one of the address classes A, B or C. This is done by setting other lower points of the subnet mask to "1". For each bit set to "1", the number of "private" networks doubles and the number of nodes they contain is halved. Externally, the network functions like an individual network as it did previously. Example: You have a subnet of address class B (e.g. IP address 129.80.xxx.xxx) and change the default subnet mask as follows: Masks Decimal Binary Default subnet mask 255.255.0.0 11111111.11111111.00000000. 00000000 Subnet mask 255.255.128.0 11111111.11111111.10000000. 00000000 Result: All nodes with addresses between 129.80.001.xxx and 129.80.127.xxx are on one subnet, all nodes with addresses between 129.80.128.xxx and 129.80.255.xxx are on another subnet. Router The job of the routers is to connect the subnets. If an IP datagram is to be sent to another network, it first has to be conveyed to a router. To make this possible, in this case you have to enter the address of the router for each node in the subnet. The IP address of a node in the subnet and the address of the router may only differ at the points at which there is a "0" in the subnet mask. WinCC Basic V13.0 System Manual, 02/2014 3763 Visualize processes 10.8 Communicating with PLCs Setting port options Setting the port options Changing connection settings for the PROFINET IO port You can change the network settings for the PROFINET IO port as required. By default, the settings are made automatically. In normal situations, this guarantees problem-free communication. Possible settings for transmission rate / duplex Depending on the selected device, you can make the following settings for "Transmission rate / duplex": Automatic setting Recommended default setting of the port. The transmission settings are automatically "negotiated" with the peer port. The "Enable autonegotiation" option is also enabled as a default, in other words, you can use cross cables or patch cables for the connection. TP/ITP at x Mbps full duplex (half duplex) Setting of the transmission rate and the full duplex/half duplex mode. The effectiveness depends on the "Enable autonegotiation" setting: - Autonegotiation enabled You can use both cross cable and patch cable. - Autonegotiation disabled Make sure that you use the correct cable (patch cable or cross cable)! The port is also monitored with this setting. Deactivated Depending on the module type, the drop down list box can contain the "- Disabled -" option. This option, for example, allows you to prevent access to an unused port for security reasons. With this setting, diagnostic events are not generated. "Monitor" option This option enables or disables port diagnostics. Examples of port diagnostics: The link status is monitored, in other words, the diagnostics are generated during link-down and the system reserve is monitored in the case of fiber optic ports. Option "Enable autonegotiation " The autonegotiation setting can only be changed if a concrete medium (for example, TP 100 Mbps full duplex) is selected. Whether or not a concrete medium can be set depends on the properties of the module. If autonegotiation is disabled, this causes the port to be permanently specified, as for example, is necessary for a prioritized startup of the IO device. 3764 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs You must make sure the partner port has the same settings because with this option the operating parameters of the connected network are not detected and the data transmission rate and transmission mode can accordingly not be optimally set. Note When a local port is connected, STEP 7 makes the setting for the partner port if the partner port supports the setting. If the partner port does not accept the setting, an error message is generated. Wiring rules for disabled autonegotiation Requirements You have made the following settings for the port in question, for example, to accelerate the startup time of the IO device: Fixed transmission rate Autonegotiation incl. autocrossing disabled The time for negotiating the transmission rate during startup has been saved. If you have disabled autonegotiation, you must observe the wiring rules. Wiring rules for disabled autonegotiation PROFINET devices have the following two types of ports: Type of port PROFINET devices Note Switch port with crossed pin assignment For IO devices: Port 2 Crossed pin assignment means that the pin assignment for the ports for sending and receiving between the respective PROFINET devices is exchanged internally. End device port with uncrossed pin assignment For S7 CPUs with 2 ports: Ports 1 and 2 For IO devices: Port 1 - For S7 CPUs with one port: Port 1 Validity of the wiring rules The cabling rules described in the following paragraph apply exclusively for the situation in which you have specified a fixed port setting. WinCC Basic V13.0 System Manual, 02/2014 3765 Visualize processes 10.8 Communicating with PLCs Rules for cabling You can connect several IO devices in line using a single cable type (patch cable). To do this, you connect port 2 of the IO device (distributed I/O) with port 1 of the next IO device. The following graphic gives an example with two IO devices. 6ZLWFKRU 352),1(7GHYLFH 3 ,2GHYLFH 3 3 3DWFKFDEOHV ,2GHYLFH 3 3 3 3DWFKFDEOHV 6ZLWFKSRUW (QGGHYLFHSRUW Boundaries at the port Requirements To use boundaries, the respective device must have more than one port. If the PROFINET does not support boundary settings, they are not shown. Enable boundaries "Boundaries" are limits for transmission of certain Ethernet frames. The following boundaries can be set at a port: "End of discovery of accessible devices" No forwarding of DCP frames to identify accessible devices. Devices downstream from this port cannot be reached by the project tree under "Accessible devices". Devices downstream from this port cannot be reached by the CPU. "End of topology discovery" LLDP frames (Link Layer Discovery Protocol) are not forwarded for topology detection. "End of sync domain" No forwarding of sync frames transmitted to synchronize nodes within a sync domain. If you operate, for example, a PROFINET device with more than two ports in a ring, you should prevent the sync frame from being fed into the ring by setting a sync boundary (at the ports not inside the ring). Additional example: If you want to use several sync domains, configure a sync domain boundary for the port connected to a PROFINET device from the other sync domain. 3766 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs Restrictions The following restrictions must be observed: The individual check boxes can only be used if the port supports the function in question. If a partner port has been determined for the port, the following check boxes cannot be used: - "End of discovery of accessible devices" - "End of topology discovery" If autonegotiation is disabled, none of the check boxes can be used. 10.8.8.3 Communication via PROFIBUS Communication via PROFIBUS HMI connections via PROFIBUS If you have inserted an HMI device and a SIMATIC S7 300/400 into the project, you interconnect the two PROFIBUS interfaces in the "Devices & Networks" editor. HMI connection in the "Devices & Networks" editor You configure the HMI connection between the PLC and the HMI device via PROFIBUS in the "Devices & Networks" editor. WinCC Basic V13.0 System Manual, 02/2014 3767 Visualize processes 10.8 Communicating with PLCs Connection in the "Connections" editor Alternatively, you configure the connection between the PLC and HMI device in the "Connections" editor of the HMI device. Configuring an HMI connection via PROFIBUS Introduction You configure an HMI connection between HMI devices and a SIMATIC S7 300/400 via PROFIBUS in the "Devices & Networks" editor. Requirements The following communication partners are created in the "Devices & Networks" editor: HMI device with MPI/DP interface SIMATIC S7 300/400 with PROFIBUS interface Procedure 1. Double-click the "Devices & Networks" item in the project tree. The available communication partners in the project are displayed graphically in the network view. 2. Click the "Connections" button. The devices available for connection are highlighted in color. 3. Click the HMI device interface. 4. Select the "PROFIBUS" interface type in the Inspector window under "Properties > General > HMI MPIDP > Parameters". 3768 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs 5. Click the interface of the PLC and use a drag-and-drop operation to draw a connection to the HMI device. 6. Click the connecting line. 7. Click "Highlight HMI connection" and select the HMI connection. The connection is displayed graphically in the Inspector window. 8. Click the communication partners in the "Network view" and change the PROFINET parameters in the Inspector window according to the requirements of your project. See the chapter "PROFIBUS parameters (Page 3770)" for additional details. Note The created HMI connection is also shown in the tabular area of the editor on the "Connections" tab. You check the connection parameters in the table. You can change the local name for the connection only in the table. Result You have created an HMI connection between an HMI device and a SIMATIC S7 300/400 via PROFIBUS. WinCC Basic V13.0 System Manual, 02/2014 3769 Visualize processes 10.8 Communicating with PLCs PROFIBUS parameters PROFIBUS parameters for the HMI connection PROFIBUS parameters for the HMI connection An overview of the configured HMI connection parameters can be found in the properties for the HMI connection. Only limited changes are possible in this Inspector window. Displaying and changing the HMI connection parameters 1. Click the HMI connection in the "Devices & Networks" editor. 2. Change the parameters of the HMI connection in the Inspector window under "Properties > General > General". "Connection" Displays whether the devices are networked together. - displayed if the devices are networked together. - displayed if the devices are not networked together. 3770 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs "Connection path" The communication partners of the selected HMI connection and the associated PROFIBUS parameters are displayed in the "Connection path" area. Some of the areas displayed cannot be edited in this dialog. "End point" Displays the device name. This area is not editable. "Interface" Displays the selected interface of the device. You can choose between several interfaces, depending on the device. "Interface type" Displays the selected interface type. This area is not editable. "Subnet" Displays the selected subnet. This area is not editable. "Address" Displays the PROFIBUS address of the device. This area is not editable. "Find connection path" button Enables the subsequent specification of connections. PROFIBUS parameters for the HMI device PROFIBUS parameters for the HMI device An overview of the configured HMI device parameters can be found in the properties for the HMI device. WinCC Basic V13.0 System Manual, 02/2014 3771 Visualize processes 10.8 Communicating with PLCs Displaying and changing PROFINET parameters of the HMI device 1. Click the HMI device in the "Devices & Networks" editor. 2. Change the parameters of the HMI device in the Inspector window under "Properties > General > General". "Interface networked with" In the "Interface networked with" area, select the subnet of the HMI connection via which the HMI device is connected to the network. You use the "Add new subnet" button to create a new subnet. "Parameters" "Interface type" You assign the interface type in the "Interface type" area. Depending on the HMI device type, you have various interfaces to choose from. "Address" You assign the PROFIBUS address of the HMI device in the "Address" area. The PROFIBUS address must be unique throughout the PROFIBUS network. 3772 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs "Highest address" The "Highest address" area displays the highest address of the PROFIBUS network. "Transmission speed" The "Transmission speed" is determined by the slowest device connected to the network. The setting is identical throughout the network. PROFIBUS parameters for the PLC PROFIBUS parameters for the PLC An overview of the configured parameters can be found in the properties for the PLC. Displaying and changing PROFIBUS parameters of the PLC 1. Click the PLC in the "Devices & Networks" editor. 2. Change the parameters of the PLC in the Inspector window under "Properties > General > General". "Interface networked with" In the "Subnet" area, select the subnet of the HMI connection via which the PLC is connected to the network. You use the "Add new subnet" button to create a new subnet. WinCC Basic V13.0 System Manual, 02/2014 3773 Visualize processes 10.8 Communicating with PLCs "Parameters" "Interface type" Depending on the HMI device type, you have various interfaces to choose from. "Address" You assign the PROFIBUS address of the HMI device in the "Address" area. The PROFIBUS address must be unique throughout the PROFIBUS network. "Highest address" The "Highest address" area displays the highest address of the PROFIBUS network. "Transmission speed" The "Transmission speed" is determined by the slowest device connected to the network. The setting is identical throughout the network. Bus profiles with PROFIBUS Introduction Depending on the device types connected and protocols used on the PROFIBUS, different profiles are available. The profiles differ in terms of the setting options and calculation of bus parameters. The profiles are explained below. Devices with different profiles on the same PROFIBUS subnet The PROFIBUS subnet only functions without problem if the bus parameters of all devices have the same values. Profiles and transmission rates 3774 Profiles Supported transmission speeds in Kbits/s DP 9,6 19,2 45,45 93,75 187,5 500 1500 3000 6000 12000 Standard 9,6 19,2 45,45 93,75 187,5 500 1500 3000 6000 12000 Universal 9,6 19,2 93,75 187,5 500 1500 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs Meaning of profiles Profile Meaning DP Select the "DP" bus profile when the only devices connected to the PROFIBUS subnet are those which satisfy the requirements of standard EN 50170 Volume 2/3, Part 8-2 PROFIBUS. The bus parameter setting is optimized on these devices. This includes devices with DP master and DP slave interfaces of the SIMATIC S7 and distributed I/Os of other manufacturers. Standard Compared to the "DP" profile, the "Standard" profile also offers scope for devices of another project or devices which have not been configured here to be taken into account when calculating the bus parameters. The bus parameters are then calculated following a simple, non-optimized algorithm. Universal Select the "Universal" bus profile when individual devices on the PROFIBUS subnet use the PROFIBUS-FMS service. This includes the following devices for example: CP 343-5 PROFIBUS-FMS devices of other manufacturers As with the "Standard" profile, this profile allows you to take other devices into account when calculating the bus parameters. 10.8.8.4 Communication via MPI Communication via MPI HMI connections via MPI If you have inserted an HMI device and a SIMATIC S7 300/400 into the project, you interconnect the two MPI interfaces in the "Devices & Networks" editor. WinCC Basic V13.0 System Manual, 02/2014 3775 Visualize processes 10.8 Communicating with PLCs HMI connection in the "Devices & Networks" editor You configure the HMI connection between the PLC and the HMI device via PROFIBUS in the "Devices & Networks" editor. Connection in the "Connections" editor Alternatively, you configure the connection between the PLC and HMI device in the "Connections" editor of the HMI device. Configuring an HMI connection via MPI Introduction You configure an HMI connection between HMI devices and a SIMATIC S7 300/400 via MPI in the "Devices & Networks" editor. Requirements The following communication partners are created in the "Devices & Networks" editor: HMI device with MPI/DP interface SIMATIC S7 300/400 with MPI/DP interface 3776 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs Procedure 1. Double-click the "Devices & Networks" item in the project tree. The available communication partners in the project are displayed graphically in the network view. 2. Click the "Connections" button. The devices available for connection are highlighted in color. 3. Click the interface of the PLC and use a drag-and-drop operation to draw a connection to the HMI device. 4. Click the connecting line. The connection is displayed graphically in the Inspector window. WinCC Basic V13.0 System Manual, 02/2014 3777 Visualize processes 10.8 Communicating with PLCs 5. Click "Highlight HMI connection" and select the HMI connection. 6. Click the communication partners in the "Network view" and change the MPI parameters in the Inspector window according to the requirements of your project. See the chapter "MPI parameters (Page 3778)" for additional details. Note The created HMI connection is also shown in the tabular area of the editor on the "Connections" tab. Use the table to monitor the connection parameters and change the connection partner. You can change the local name for the connection only in the table. Result You have created an HMI connection between an HMI device and a SIMATIC S7 300/400 via MPI. MPI parameters MPI parameters for the HMI connection MPI parameters for the HMI connection An overview of the configured HMI connection parameters can be found in the properties for the HMI connection. Only limited changes are possible in this Inspector window. 3778 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs Displaying and changing the HMI connection parameters 1. Click the HMI connection in the "Devices & Networks" editor. 2. Change the parameters of the HMI connection in the Inspector window under "Properties > General > General". "Connection" Displays whether the devices are networked together. - displayed if the devices are networked together. - displayed if the devices are not networked together. "Connection path" The communication partners of the selected HMI connection and the associated MPI parameters are displayed in the "Connection path" area. Some of the areas displayed cannot be edited in this dialog. "End point" Displays the name of the device. This area is not editable. "Interface" Displays the selected interface of the device. You can choose between several interfaces, depending on the device. WinCC Basic V13.0 System Manual, 02/2014 3779 Visualize processes 10.8 Communicating with PLCs "Interface type" Displays the selected interface type. This area is not editable. "Subnet" Displays the selected subnet. This area is not editable. "Address" Displays the MPI address of the device. This area is not editable. "Find connection path" button Enables the subsequent specification of connections. MPI parameters for the HMI device MPI parameters for the HMI device An overview of the configured HMI device parameters can be found in the properties for the HMI device. Displaying and changing MPI parameters of the HMI device 1. Click the HMI device in the "Devices & Networks" editor. 2. Change the parameters of the HMI device in the Inspector window under "Properties > General > General". "Interface networked with" In the "Interface networked with" area, select the subnet of the HMI connection via which the HMI device is connected to the network. You use the "Add new subnet" button to create a new subnet. 3780 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs "Parameters" "Interface type" You assign the interface type in the "Interface type" area. Depending on the HMI device type, you have various interfaces to choose from. "Address" You assign the MPI address of the HMI device in the "Address" area. The MPI address must be unique throughout the MPI network. "Highest address" The "Highest address" area displays the highest address of the MPI network. "Transmission speed" The "Transmission speed" is determined by the slowest device connected to the network. The setting is identical throughout the network. MPI parameters for the PLC MPI parameters for the PLC An overview of the configured parameters can be found in the properties for the PLC. Displaying and changing PROFIBUS parameters of the PLC 1. Click the PLC in the "Devices & Networks" editor. 2. Change the parameters of the PLC in the Inspector window under "Properties > General > General". WinCC Basic V13.0 System Manual, 02/2014 3781 Visualize processes 10.8 Communicating with PLCs "Interface networked with" In the "Subnet" area, select the subnet of the HMI connection via which the HMI device is connected to the network. You use the "Add new subnet" button to create a new subnet. "Parameters" "Interface type" Depending on the HMI device type, you have various interfaces to choose from. "Address" You assign the MPI address of the HMI device in the "Address" area. The MPI address must be unique throughout the MPI network. "Highest address" The "Highest address" area displays the highest address of the MPI network. "Transmission speed" The "Transmission speed" is determined by the slowest device connected to the network. The setting is identical throughout the network. Addressing of the PLC via MPI Introduction Each communication partner must be assigned an MPI network address. Each S7 module which supports communication functions and is operated the SIMATIC S7-300/400 PLC is assigned a unique MPI address. Only one CPU may be used per rack. Note HMI devices cannot be operated with incorrect addressing Always avoid redundant addressing on the MPI bus. MPI address of the communication partner of a SIMATIC S7-300 When assigning addresses, you have to distinguish between communication partners with and without separate MPI address. If the communications partner has its own MPI address, you only need to define the MPI address. If the communication partners do not have a separate MPI address, specify the MPI address of the communications partner used for the connection. In addition, define the slot and rack of a communication partner without its own MPI address. 3782 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs MPI address of the communication partner of a SIMATIC S7-400 Only S7 modules with an MPI connector are assigned an MPI address. Modules without an MPI connector are addressed indirectly: MPI address of the module to which the HMI is connected. The slot and the rack of the module with which the HMI device communicates. 10.8.8.5 Data exchange Data exchange using area pointers General information on area pointers Introduction You use an area pointer to access a data area in the PLC. During communication, the PLC and the HMI device alternately access these data areas for read and write operations. The PLC and the HMI device trigger defined interactions based on the evaluation of stored data. Configuration of area pointers Before you use an area pointer, you enable it under "Connections > Area pointer". You then assign the area pointer parameters. You can find more detailed information on configuring area pointers in: Configuring area pointers (Page 3642) "Screen number" area pointer Function The HMI device saves information about the screen called on the HMI device to the "Screen number" area pointer. This allows the transfer of the current screen contents from the HMI device to the PLC. The PLC can trigger specific reactions such as the call of a different screen. Use Configure and enable the area pointer in "Communication > Connections" before you put it into use. You can create only one instance of the "Screen number" area pointer and only on one PLC. The screen number is always transferred to the PLC when a new screen is activated or when the focus within a screen changes from one screen object to another. WinCC Basic V13.0 System Manual, 02/2014 3783 Visualize processes 10.8 Communicating with PLCs Structure The area pointer is a data area in the memory of the PLC with a fixed length of 5 words. 15 14 13 12 11 10 9 8 7 6 1st word Current screen type 2nd word Current screen number 3rd word Reserved 4th word Current field number 5th word Reserved 5 4 3 2 1 0 Current screen type "1" for root screen or "4" for permanent window Current screen number 1 to 32767 Current field number 1 to 32767 "Date/time" area pointer Function This area pointer is used to transfer the date and time from the HMI device to the PLC. The PLC writes control job "41" or "40" to the job mailbox. When it evaluates the control job, the HMI device writes its current date and the time in the data area configured in the "Date/time" area pointer. All definitions are coded in BCD format. The "Date/Time" area pointer when used in a project which contains multiple connections must be enabled for each configured connection. Note You cannot use the "Date/Time PLC" area pointer if you have configured the "Date/Time" area pointer. Note Symbolic addressing is not possible if you are using the "Date/Time" area pointer. The "Date/Time" area pointer when used in a project which contains multiple connections must be enabled for each configured connection. The date/time data area has the following structure: 3784 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs Data word Most significant byte 7 Least significant byte 0 7 0 n+0 Reserved Hour (0 to 23) n+1 Minute (0 to 59) Second (0 to 59) n+2 Reserved Reserved n+3 Reserved Weekday (1 to 7, 1=Sunday) n+4 Day (1 to 31) Month (1 to 12) n+5 Year (80 to 99/0 to 29) Reserved Time Date Note When making entries in the "Year" data area, you should note that values 80 to 99 result in years 1980 through 1999, while the values 0 to 29 result in the years 2000 through 2029. "Date/time PLC" area pointer Function This area pointer is used to transfer the date and time from the PLC to the HMI device. Use this area pointer if the PLC is the time master. The PLC loads the data area of the area pointer. All definitions are coded in BCD format. The HMI device reads the data cyclically within the configured acquisition cycle and synchronizes itself. Note Set an acquisition cycle of sufficient length for the Date/time area pointer in order to avoid any negative impact on HMI device performance. Recommended: Acquisition cycle of 1 minute, if the process allows this. You cannot use the "Date/Time" area pointer if you have configured the "Date/Time PLC" area pointer. "Date/Time PLC" is a global area pointer and may be configured only once per project. Note You cannot use the "Date/Time" area pointer if you have configured the "Date/Time PLC" area pointer. The date/time data area has the following structure: WinCC Basic V13.0 System Manual, 02/2014 3785 Visualize processes 10.8 Communicating with PLCs DATE_AND_TIME format (in BCD code) Data word Most significant byte 7 1) ...... Least significant byte 0 7 ...... 0 n+0 Year (80 to 99/0 to 29) Month (1 to 12) n+1 Day (1 to 31) Hour (0 to 23) n+2 Minute (0 to 59) n+3 Reserved n+4 1) Reserved Reserved n+5 Reserved Reserved 1) Second (0 to 59) Reserved Weekday (1 to 7, 1=Sunday) The two data words must exist in the data area to ensure that the data format matches WinCC flexible and to avoid reading false information. Note When making entries in the "Year" data area, you should note that values 80 to 99 result in years 1980 through 1999, while the values 0 to 29 result in the years 2000 through 2029. "Coordination" area pointer Function The "Coordination" area pointer is used to implement the following functions: Detecting the startup of the HMI device in the control program Detecting the current operating mode of the HMI device in the control program Detecting whether the HMI device is ready to communicate in the control program By default, the "Coordination" area pointer has the length of one word and cannot be changed. Application Note The HMI device always writes the entire coordination area when updating the area pointer. The control program can for this reason not make changes to the coordination area. 3786 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs Assignment of bits in the "Coordination" area pointer ORZRUGHUE\WH KLJKRUGHUE\WH VWZRUG ; ; ; VWZRUGQRWDVVLJQHG UHVHUYHG [ DVVLJQHG 6WDUWXSELW 2SHUDWLRQPRGH /LIHELW Startup bit The startup bit is set briefly to "0" by the HMI device during startup. It sets the bit permanently to "1" when startup is completed. Operating mode The operating mode bit is set to 1 as soon as the user switches the HMI device offline. The status of the operating mode bit is "0" during normal operation of the HMI device. You can determine the current operating mode of the HMI device by reading this bit in the control program. Life bit The HMI device inverts the life bit at intervals of approximately one second. You can check whether or not there is still a connection to the HMI device by querying this bit in the control program. "Project ID" area pointer Function When Runtime starts, a check can be carried out as to whether the HMI device is connected to the correct PLC. This check is important when operating with several HMI devices. For this, the HMI device compares a value stored on the PLC with the value specified in configuration. This ensures compatibility of the configuration data with the PLC program. If there is no concordance, a system event is given on the HMI device and Runtime is stopped. Use Note HMI connections cannot be switched "online". The HMI connection in which the "Project ID" area pointer is used must be switched "online". To use this area pointer, set up the following during the configuration: WinCC Basic V13.0 System Manual, 02/2014 3787 Visualize processes 10.8 Communicating with PLCs Define the version of the configuration. Values between 1 and 255 are possible. You enter the version in the editor "Runtime settings > General" in the "Identification" area. Data address of the value for the version that is stored in the PLC: You enter the data address in the editor "Communication > Connections" under "Address". Connection failure A connection failure to a device on which the "Project ID" area pointer is configured results in all the other connections of the device being switched to "offline". This behavior has the following requirements: You have configured several connections in a project. You are using the "Project ID" area pointer in at least one connection. Causes which may set connections "offline": The PLC is not available. The connection has been switched offline in the Engineering System. "Job mailbox" area pointer Function The PLC can use the job mailbox to transfer jobs to the HMI device to trigger corresponding actions on the HMI device. These functions include, for example: Display screen Set date and time Data structure The first word of the job mailbox contains the job number. Depending on the job mailbox, up to three parameters can be transferred. Word Most significant byte Least significant byte n+0 0 Job number n+1 Parameter 1 n+2 Parameter 2 n+3 Parameter 3 The HMI device evaluates the job mailbox if the first word of this job is not equal to zero. This means that the parameters must be entered in the job mailbox first, followed by the job number. When the HMI device accepts the job mailbox, the first word is set to 0 again. The execution of the job mailbox is generally not completed at this point in time. 3788 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs Job mailboxes All job mailboxes and their parameters are listed below. The "No." column contains the job number of the job mailbox. Job mailboxes can only be triggered by the PLC when the HMI device is online. No . Function 14 Set time (BCD-coded) Parameter 1 Left byte: Right byte: hours (0-23) Parameter 2 Left byte: minutes (0-59) Right byte: seconds (0-59) Parameter 3 15 23 Setting the date (BCD coded) 3) 4) Parameter 1 Left byte: Right byte: weekday (1-7: Sunday-Saturday) Parameter 2 Left byte: day (1-31) Right byte: month (1-12) Parameter 3 Left byte: year User logon Logs the user on with the name "PLC user" at the HMI device with the group number transferred in Parameter 1. The logon is possible only when the transferred group number exists in the project. 24 Parameter 1 Group number 1 to 255 Parameter 2, 3 - User logoff Logs off the current user. (The function corresponds to the "logoff" system function) Parameter 1, 2, 3 40 - Transfer date/time to PLC (in the S7 format DATE_AND_TIME) An interval of at least 5 seconds must be maintained between two successive jobs to prevent overload of the HMI device. Parameter 1, 2, 3 41 - Transfer date/time to PLC (In OP/MP format) An interval of at least 5 seconds must be maintained between successive jobs to prevent overload of the HMI device. Parameter 1, 2, 3 46 - Update tag Causes the HMI device to read the current value of the tags from the PLC whose update ID matches the value transferred in Parameter 1. (Function corresponds to the "UpdateTag" system function.) Parameter 1 49 1 - 100 Delete alarm buffer Deletes all analog alarms and discrete alarms of the "Warnings" class from the alarm buffer. WinCC Basic V13.0 System Manual, 02/2014 3789 Visualize processes 10.8 Communicating with PLCs No . Function 14 Set time (BCD-coded) Parameter 1, 2, 3 50 - Delete alarm buffer Deletes all analog alarms and discrete alarms of the "Errors" class from the alarm buffer. Parameter 1, 2, 3 51 69 - Screen selection 2) Parameter 1 Screen number Parameter 2 - Parameter 3 Field number Reading data record from PLC 1) Parameter 1 Recipe number (1-999) Parameter 2 Data record number (1-65535) Parameter 3 0: Do not overwrite existing data record 1: Overwrite existing data record 70 Writing data record to PLC 1) Parameter 1 Recipe number (1-999) Parameter 2 Data record number (1-65535) Parameter 3 - 1) Only for devices supporting recipes. 2) OP 73, OP 77A and TP 177A HMI devices also execute the "Screen selection" job mailbox if the on-screen keyboard is active. 3) The weekday is ignored on HMI device KTP 600 BASIC PN. 4) The weekday is ignored when you configure the "Date/Time PLC" area pointer. "Data record" area pointer "Data record" area pointer Function When data records are transferred between the HMI device and PLC, both partners access common communications areas on the PLC. Data transfer types There are two ways of transferring data records between the HMI device and PLC: Transfer without synchronization Transfer with synchronization via the data mailbox 3790 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs Data records are always transferred directly, which means that the tag values are read straight from an address or written straight to an address configured for this tag without being redirected via an interim memory. Initiating the transfer of data records There are three ways of triggering the transfer: Operator input in the recipe view Job mailboxes The transfer of data records can also be triggered by the PLC. Triggering by configured functions If the transfer of data records is triggered by a configured function or by a job mailbox, the recipe view on the HMI device remains operable. The data records are transferred in the background. Simultaneous processing of several transfer requests is, however, not possible. In this case, the HMI device rejects the other transfer requests with a system alarm. Transfer without synchronization If you select asynchronous transfer of data records between the HMI device and PLC, there is no coordination over the common data areas. It is therefore unnecessary to set up a data area during configuration. Asynchronous data record transfer can be a useful alternative, for example when: The system is capable of excluding the risk of uncontrolled overwriting of data by the communication peer. The PLC does not require information about the recipe number and data record number. The transfer of data records is triggered by the operator of the HMI device. Reading values When a read job is triggered, the values are read from the PLC addresses and transferred to the HMI device. Triggering by the operator in the recipe view: The values are downloaded to the HMI device. You can then, for example, process, edit, or save these values in the HMI device. Triggering by a function or job mailbox: The values are saved immediately to the data volume. WinCC Basic V13.0 System Manual, 02/2014 3791 Visualize processes 10.8 Communicating with PLCs Writing values When a write job is triggered, the values are written to the PLC addresses. Triggering by the operator in the recipe view: The current values are written to the PLC. Triggering by a function or job mailbox: The current values are written to the PLC from the data medium. Transfer with synchronization If you select synchronous transfer, both communication partners set status bits in the common data area. You can use this mechanism to prevent uncontrolled overwriting of data in either direction in your control program. Application Synchronous data record transfer can be a useful solution, for example, when: The PLC is the "active partner" in the transfer of data records. The PLC evaluates the information about the recipe number and data record number. The transfer of data records is triggered by means of a Job mailbox. Requirements In order to synchronize transfer of data records between the HMI device and the PLC, the following requirements must be met during configuration: An area pointer has been set up: "Communication > Connections" editor in "Area pointer". The PLC with which the HMI device synchronizes transfer of data records is specified in the recipe: "Recipes" editor in the inspector window the option "Coordinated transfer of data records" under "General > Synchronization > Settings" Structure of the data area The data area has a fixed length of 5 words. Structure of the data area: 15 3792 0 1. Word Current recipe number (1 - 999) 2. Word Current data record number (0 - 65535) 3. Word Reserved 4. Word Status (0, 2, 4, 12) 5. Word Reserved WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs Status The status word (word 4) can adopt the following values: Value Meaning Decimal Binary 0 0000 0000 Transfer permitted, data mailbox free 2 0000 0010 Transferring 4 0000 0100 Transfer completed without error 12 0000 1100 Transfer completed with error Sequence of a transfer started by the operator in the recipe view Reading from the PLC started by the operator in the recipe view Step Action 1 Check: Status word = 0? Yes No 2 The HMI device enters the recipe number to be read and the status "Transferring" in the data record and sets the data record number to 0. Abort with system event. 3 The HMI device reads the values from the PLC and displays them in the recipe view. If the recipes have synchronized tags, the values from the PLC are also written to the tags. 4 The HMI device sets the status "Transfer completed." 5 The control program must reset the status word to zero in order to enable further transfers. Writing to the PLC started by the operator in the recipe view Step Action Check: Status word = 0? 1 Yes The HMI device enters the recipe and data record number to be written and the status "Transferring" in the data record. 2 No Abort with system event. The HMI device writes the current values to the PLC. If the recipes have synchronized tags, the changed values are synchronized between the recipe view and tags and then written to the PLC. WinCC Basic V13.0 System Manual, 02/2014 3 The HMI device sets the status "Transfer completed." 4 If required, the control program can now evaluate the transferred data. 5 The control program must reset the status word to zero in order to enable further transfers. 3793 Visualize processes 10.8 Communicating with PLCs Note The status word may only be set by the HMI device. The PLC may only reset the status word to zero. Note The PLC may only evaluate the recipe and data record numbers when data inconsistency is detected if one of the conditions outlined below has been met: The data mailbox status is set to "Transfer completed". The data mailbox status is set to "Transfer completed with error". Sequence of the transfer triggered by a job mailbox The transfer of data records between the HMI device and the PLC can be initiated by either one of these stations. The two job mailboxs No. 69 and No. 70 are available for this type of transfer. No. 69: Read data record from PLC ("PLC DAT") Job mailbox no. 69 transfers data records from the PLC to the HMI device. The job mailbox is structured as follows: Left byte (LB) Right byte (RB) 0 69 Word 1 Word 2 Recipe number (1-999) Word 3 Data record number (1 to 65535) Word 4 Do not overwrite existing data record: 0 Overwrite existing data record: 1 No. 70: Write data record to PLC ("DAT PLC") Job mailbox No. 70 transfers data records from the HMI device to the PLC. The job mailbox is structured as follows: Left byte (LB) Word 1 3794 Right byte (RB) 0 70 Word 2 Recipe number (1-999) Word 3 Data record number (1-65,535) Word 4 -- WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs Sequence when reading from the PLC with job mailbox "PLC DAT" (no. 69) Step Action 1 Check: Status word = 0? Yes No 2 The HMI device enters the recipe and data record number specified in the job and the status "Transferring" in the data record. Abort without return message. 3 The HMI device reads the values from the PLC and saves these to the data record defined in the job mailbox. 4 If "Overwrite" was selected in the job, an existing data record is overwritten without any prompt for confirmation. The HMI device sets the status "Transfer completed." If "Do not overwrite" was selected in the job, and the data record already exists, the HMI device aborts the job and enters 0000 1100 in the status word of the data mailbox. 5 The control program must reset the status word to zero in order to enable further transfers. Sequence of writing to the PLC with job mailbox "DAT PLC" (no. 70) Step Action 1 Check: Status word = 0? Yes No 2 The HMI device enters the recipe and data record number specified in the job and the status "Transferring" in the data mailbox. Abort without return message. 3 The HMI device fetches the values of the data record specified in the function from the data medium and writes the values to the PLC. 4 The HMI device sets the status "Transfer completed." 5 The control program can now evaluate the transferred data. The control program must reset the status word to zero in order to enable further transfers. Sequence of the transfer when triggered by a configured function Reading from the PLC using a configured function WinCC Basic V13.0 System Manual, 02/2014 Step Action 1 Check: Status word = 0? Yes No 2 The HMI device enters the recipe and data record number specified in the function and the status "Transferring" in the data mailbox. Abort with system event. 3 The HMI device reads the values from the PLC and stores them in the data record specified in the function. 3795 Visualize processes 10.8 Communicating with PLCs Step 4 Action If "Yes" was selected for the "Overwrite" function, an existing data record is overwritten without any prompt for confirmation. The HMI device sets the status "Transfer completed." If "No" was selected for the "Overwrite" function and the data record already exists, the HMI device aborts the job and enters 0000 1100 in the status word of the data mailbox. 5 The control program must reset the status word to zero in order to enable further transfers. Writing to the PLC by means of configured function Step Action 1 Check: Status word = 0? Yes No 2 The HMI device enters the recipe and data record number specified in the function and the status "Transferring" in the data mailbox. Abort with system event. 3 The HMI device fetches the values of the data record specified in the function from the data medium and transfers the values to the PLC. 4 The HMI device sets the status "Transfer completed." 5 The control program can now evaluate the transferred data. The control program must reset the status word to zero in order to enable further transfers. Possible causes of error when transferring data records Possible causes of error The section below shows possible error causes which lead to the cancellation of data record transfer: Tag address not set up on the PLC Overwriting data records not possible 3796 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs Recipe number does not exist Data record number does not exist Note The status word may only be set by the HMI device. The PLC may only reset the status word to zero. Note The PLC may only evaluate the recipe and data record numbers when data inconsistency is detected if one of the conditions outlined below has been met: The data mailbox status is set to "Transfer completed". The data mailbox status is set to "Transfer completed with error". Reaction to an aborted transfer due to errors If the transfer of data records is aborted due to errors, the HMI device reacts as follows: Triggering by the operator in the recipe view Information in the status bar of the recipe view and output of system alarms Triggered by function Output of system alarms Triggering by job mailbox No return message on the HMI device You can nonetheless evaluate the status of the transfer by querying the status word in the data record. Trends Trends A trend is the graphical representation of one or more values from the PLC. The value is read out time-triggered for Basic Panels. For additional information see: Configuring trend displays for values from the PLC (Page 3369) Time-triggered trends The HMI device reads in the trend values cyclically at an interval specified in the configuration. Time-triggered trends are suitable for continuous curves, such as the operating temperature of a motor. WinCC Basic V13.0 System Manual, 02/2014 3797 Visualize processes 10.8 Communicating with PLCs Alarms Configuring alarms Configure alarms Several steps are needed to configure alarms, such as operational messages, error alarms, and acknowledgement. Step 1: Create tags Step 2: Configure alarms Step 3: Configure acknowledgment You can find additional information in the section: Working with alarms (Page 3379) Distinctive features when configuring alarms If you are configuring connections of HMI devices to PLCs of other manufacturers, note the following distinctive features when configuring: Data types of the tags Addressing of tags How the bit positions are counted Data types For connections with a SIMATIC communication driver, the following data types are supported: PLC Permitted data types Discrete alarms Analog alarms WORD, INT BYTE, CHAR, WORD, INT, DWORD, DINT, REAL, COUNTER, TIME SIMATIC S7 300/400 How the bit positions are counted For connections with a SIMATIC communication driver, the following counting method applies: How the bit positions are counted 3798 Byte 0 Byte 1 Most significant byte Least significant byte In SIMATIC S7 PLCs 7 0 7 0 In WinCC you configure: 15 8 7 0 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs Acknowledgment of alarms Procedure Create suitable tags on the PLC to acknowledge an error alarm. You assign these tags to an alarm in the "Bit messages" editor. You make the assignment in "Properties > Acknowledgment". Distinction in terms of acknowledgment: Acknowledgment by the PLC Acknowledgment on the HMI device Acknowledgment by the PLC In "PLC acknowledgment tag", configure the tag or array tag and the bit number that the HMI device uses to identify a PLC acknowledgment. A bit set in the tag triggers acknowledgment of the assigned error alarm bit at the HMI device. This tag bit returns a function similar to acknowledgment on the HMI device which is triggered by pressing the "ACK" button, for example. The acknowledgment bit must be located in the same tag as the bit for the error alarm. Reset the acknowledgment bit before setting the bit in the alarm area again. The figure below shows the pulse diagram. (UURUDODUP $FNQRZOHGJPHQW 3/&+0,GHYLFH $UULYDORIWKH $FNQRZOHGJP 5HVHWRI HUURUDODUP YLD3/& DFNQRZOHGJPELW 1HZ HUURUDODUP Acknowledgment on the HMI device In the "HMI acknowledgment tag" area, configure the tag or array tag as well as the bit number that the HMI device writes to the PLC after acknowledgment. Make sure when you use an array tag that it is not longer than 6 words. To always create a signal change when setting an assigned acknowledgment bit of a discrete alarm that must be acknowledged, the HMI device will reset the acknowledgment bit assigned to the alarm as soon as it detects an alarm subject to acknowledgment and write the acknowledgment tag in the PLC. There will be a certain delay between detecting the message and writing the acknowledgment tag in the PLC because the HMI device has to process the operations. If a discrete alarm subject to acknowledgment is acknowledged by the HMI device, then the corresponding bit in the assigned acknowledgment tag will be set. The entire acknowledgment WinCC Basic V13.0 System Manual, 02/2014 3799 Visualize processes 10.8 Communicating with PLCs tag is then written to the PLC by the HMI device. This allows the PLC to recognize that a certain alarm message has been acknowledged at the HMI device. Note All alarm bits acknowledged since the last Runtime start will remain in the acknowledgment tag until a new incoming of the respective discrete alarms is detected. This area should only be read by the PLC because the entire section of the HMI device will be overwritten once the next acknowledgment tag is written. The figure below shows the pulse diagram. (UURUDODUP $FNQRZOHGJPHQW +0,GHYLFH3/& $UULYDORIWKH HUURUDODUP 10.8.8.6 5HVHWRI DFNQRZOHGJPELW $FNQRZOHGJP YLD+0,GHYLFH 1HZ HUURUDODUP Performance features of communication Permitted data types for SIMATIC S7 300/400 Permitted data types for connections with SIMATIC S7 300/400 The table lists the data types that can be used when configuring tags and area pointers. 3800 Data type Length BOOL 1-bit BYTE 1 byte WORD 2 bytes DWORD 4 bytes CHAR 1 byte INT 2 byte DINT 4 bytes REAL 4 bytes TIME 4 bytes DATE 2 bytes TIME_OF_DAY, TOD 4 bytes S5TIME 2 bytes WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs 10.8.8.7 Data type Length COUNTER 2 bytes TIMER 2 bytes DATE_AND_TIME 8 bytes STRING (2+n) bytes, n = 0 to 254 Creating connections in the "Connections" editor Creating a PROFINET connection Requirements A project is open. An HMI device with a PROFINET interface has been created. Procedure 1. Open the "Connections" editor of the HMI device. 2. Double-click "<Add>". WinCC Basic V13.0 System Manual, 02/2014 3801 Visualize processes 10.8 Communicating with PLCs 3. Select the driver in the "Communication driver" column. 4. Click the name of the connection. 5. Select a PROFINET interface of the HMI device in the Inspector window under "Parameters > Interface". 6. Set the IP addresses of the communication partners in the Inspector window: - HMI device: "Parameters > HMI device > Address" - PLC: "Parameters > PLC > Address" Creating a PROFIBUS connection Requirements A project is open. An HMI device with a PROFIBUS interface has been created. 3802 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs Procedure 1. Open the "Connections" editor of the HMI device. 2. Double-click "<Add>". 3. Select the driver in the "Communication driver" column. 4. Click the name of the connection. 5. Select the "MPI/DP" interface in the Inspector window under "Parameters > Interface". WinCC Basic V13.0 System Manual, 02/2014 3803 Visualize processes 10.8 Communicating with PLCs 6. Select the "DP" profile in the Inspector window under "Parameters > Network". 7. Set the addresses of the communication partners in the inspector window: - HMI device: "Parameters > HMI device > Address" - PLC: "Parameters > PLC > Address" Creating an MPI connection Requirements A project is open. An HMI device with an MPI interface has been created. 3804 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs Procedure 1. Open the "Connections" editor of the HMI device. 2. Double-click "<Add>". 3. Select the driver in the "Communication driver" column. 4. Click the name of the connection. 5. Select the "MPI/DP" interface in the Inspector window under "Parameters > Interface". WinCC Basic V13.0 System Manual, 02/2014 3805 Visualize processes 10.8 Communicating with PLCs 6. Select the "MPI" profile in the Inspector window under "Parameters > Network". 7. Set the addresses of the communication partners in the inspector window: - HMI device: "Parameters > HMI device > Address" - PLC: "Parameters > PLC > Address" Parameters for the connection Parameters for the connection (SIMATIC S7 300/400) Parameters to be set To set the connection parameters, such as addresses and profiles, click the connection that you have created in the "Connections" editor. The communication partners are displayed schematically in the Inspector window under "Parameters". The "HMI device", "Network", and "PLC" areas are available for assigning parameters according to the interface used. 3806 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs WinCC Basic V13.0 System Manual, 02/2014 3807 Visualize processes 10.8 Communicating with PLCs Ethernet parameters Parameters for the HMI device You set the parameters for the HMI device in the network under "HMI device".. The changes are not transferred automatically to the HMI device. You must change the settings in the Control Panel of the HMI device. "Interface" If you are directly connected to the HMI device during configuration, you can set up the IP address of the HMI device in WinCC. Note The IP address in the Control Panel will be overwritten upon subsequent loading if you have already set up the IP address in the HMI device control panel. The IP address already set up in the Control Panel will be retained upon subsequent loading if you activate "Set IP address using a different method". The IP address is transferred to the HMI device during project transfer. To set up the IP address of the HMI device: - Click the HMI device. - Open the "Device configuration" editor. - Click the Ethernet interface. - Assign the IP address in the inspector window under: "General > PROFINET interface > Ethernet addresses" "Address" You assign the IP address of the HMI device in the "Address" area. When you transfer the WinCC project to the HMI device, this IP address is set up directly in the HMI device. "Access point" The access point defines a logical device name through which the communication partner can be reached. Parameters for the PLC Under "PLC", you address the S7 module with which the HMI device will exchange data. Assign a name for the connection for each communication partner. "Address" Under "Address", set the IP address of the S7 module to which the HMI device is connected. "Expansion slot" Defines the number of the expansion slot of the CPU to be addressed. 3808 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs "Rack" Defines the rack number of the CPU to be addressed. "Cyclic operation" Note The setting "Cyclic operation" cannot be configured for the SIMATIC S7 1200 PLC. When cyclic operation is enabled, the PLC optimizes the data exchange between the HMI device and the PLC. This increases system performance. Disable cyclic mode if you are operating several HMI devices in parallel. PROFIBUS parameters Parameters for the HMI device You assign the parameters for the HMI device in the network once under "HMI device". The change applies to each communication partner. "Type" Specifies the physical connection used. "Interface" For "Interface", you select the HMI device interface via which the HMI device is connected to the PROFIBUS network. "Baud rate" For "Baud rate", you set the transmission speed of the data in the network. The baud rate is determined by the slowest HMI device connected to the network. The setting must be identical throughout the network. Note If you set a baud rate of 1.5 Mbaud for OP 73 or OP 77A, the highest station address must be less than or equal to 63. "Address" You set the PROFIBUS address of the HMI device under "Address". The PROFIBUS address must be unique in the PROFIBUS network. "Sole master on bus" Disables an additional safety feature against bus faults when the HMI device is connected to the network. A passive station (slave) can only send data if it is requested to do so by an active station (master). In S7 200, you must set an HMI device as the master. "Access point" The access point defines a logical device name through which the communication partner can be reached. WinCC Basic V13.0 System Manual, 02/2014 3809 Visualize processes 10.8 Communicating with PLCs Parameters for the network Under "Network", you set the parameters for the PROFIBUS network to which the HMI device is linked. "Profile" For "Profile", you select the network profile that is used in the network. In "Profile", set "DP", "Universal", or "Standard". The setting must be identical throughout the network. "Highest address" For "Highest station address", set the highest station address. The highest station address must be greater than or equal to the highest actual PROFIBUS address. The setting must be identical throughout the network. Note If you set a baud rate of 1.5 Mbaud in the OP 73 or the OP 77A, the highest station address must be less than or equal 63. "Number of masters" For "Number of masters", set the number of masters in the PROFIBUS network. This information is necessary to correctly calculate the bus parameters. Parameters for the PLC Under "PLC", you address the S7 module with which the HMI device will exchange data. Assign a name for the connection for each communication partner. "Address" For "Address", set the PROFIBUS address of the S7 module (CPU, FM, or CP) to which the HMI device is connected. "Cyclic operation" Note The setting "Cyclic operation" cannot be configured for the SIMATIC S7 1200 PLC. When cyclic operation is enabled, the PLC optimizes the data exchange between the HMI device and the PLC. This increases system performance. Disable cyclic mode if you are operating several HMI devices in parallel. This setting is not required for SIMATIC S7-200 PLCs. 3810 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs MPI parameters Parameters for the HMI device You assign the parameters for the HMI device in the network once under "HMI device". The change applies to each communication partner. "Type" Specifies the physical connection used. "Interface" For "Interface", you select the HMI device interface via which the HMI device is connected to the MPI network. "Baud rate" For "Baud rate", you set the transmission speed of the data in the network. The baud rate is determined by the slowest HMI device connected to the network. The setting must be identical throughout the network. Note If you set a baud rate of 1.5 Mbaud for OP 73 or OP 77A, the highest station address must be less than or equal to 63. "Address" For "Address", you set the MPI address of the HMI device. The MPI address must be unique throughout the MPI network. "Sole master on bus" Disables an additional safety feature against bus faults when the HMI device is connected to the network. A passive station (slave) can only send data if it is requested to do so by an active station (master). If you have connected only slaves to the HMI device, you must therefore disable the "Sole master on bus" safety feature. In S7 200, you must set an HMI device as the master. Parameters for the network Under "Network", you set the parameters for the MPI network to which the HMI device is linked. "Profile" For "Profile", you select the network profile that is used in the network. In "Profile", set "MPI". The setting must be identical throughout the network. "Highest address" For "Highest station address", set the highest station address. The highest station address must be greater than or equal to the highest actual MPI address. The setting must be identical throughout the network. "Number of masters" This setting is not required for MPI. WinCC Basic V13.0 System Manual, 02/2014 3811 Visualize processes 10.8 Communicating with PLCs Parameters for the PLC Under "PLC", you address the S7 module with which the HMI device will exchange data. Assign a name for the connection for each communication partner. "Address" For "Address", set the MPI address of the S7 module (CPU, FM, or CP) to which the HMI device is connected. "Cyclic mode" When cyclic mode is enabled, the PLC optimizes the data exchange between the HMI device and the PLC. This improves system performance. Disable cyclic mode if you are operating several HMI devices in parallel. This setting is not required for SIMATIC S7-200. Cyclic operation Handling the "Cyclic operation" selection If "Cyclic operation" is enabled, the HMI device sends a message frame to the CPU at the beginning of communication indicating that certain tags are required on a recurring basis. The CPU then always transmits the data at the same cyclic interval. This saves the HMI device from having to output new requests for the data. If cyclic operation is disabled, the HMI device sends a request whenever information is required. Additional properties: Cyclic operation reduces data transmission load at the HMI device. The PLC resources are used to relieve load on the HMI device. The PLC only supports a certain number of cyclic services. The HMI device handles the operation if the PLC cannot provide any further resources for cyclic services. The HMI device generates the cycle if the PLC does not support the cyclic mode. Screen tags are not integrated in cyclic operation. Cyclic mode is only set up at the restart of Runtime. The HMI device transfers several jobs to the PLC if cyclic mode is enabled, depending on the PLC. The HMI device only transfers one job to the PLC if cyclic mode is disabled. 3812 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs 10.8.9 Communicating with SIMATIC S7 200 10.8.9.1 Communication with SIMATIC S7 200 Introduction This section describes the communication between an HMI device and the SIMATIC S7 200 PLC. You can configure the following communication channels for the SIMATIC S7 200 PLC: PROFINET and Ethernet PROFIBUS MPI PPI HMI connection for communication You configure connections between the HMI device and a SIMATIC S7 200 in the "Connections" editor of the HMI device. 10.8.9.2 Creating a connection to SIMATIC S7 200 Introduction You configure a connection to the SIMATIC S7 200 PLC in the "Connections" editor of the HMI device. The interfaces are named differently depending on the HMI device. Requirements A project is open. An HMI device has been created. Procedure 1. Double-click the HMI device under "Devices" in the project tree. 2. Double-click the "Connections" item. WinCC Basic V13.0 System Manual, 02/2014 3813 Visualize processes 10.8 Communicating with PLCs 3. Double-click "<Add>" in the "Connections" editor. 3814 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs 4. In the "Communication drivers" column, select the "SIMATIC S7 200" driver. 5. Select all necessary connection parameters for the interface in the Inspector window under "Parameters". See the chapter "Parameters for the connection (Page 3815)" for additional details. 10.8.9.3 Parameters for the connection Cyclic operation Handling the "Cyclic operation" selection If "Cyclic operation" is enabled, the HMI device sends a message frame to the CPU at the beginning of communication indicating that certain tags are required on a recurring basis. The CPU then always transmits the data at the same cyclic interval. This saves the HMI device from having to output new requests for the data. If cyclic operation is disabled, the HMI device sends a request whenever information is required. Additional properties: Cyclic operation reduces data transmission load at the HMI device. The PLC resources are used to relieve load on the HMI device. The PLC only supports a certain number of cyclic services. The HMI device handles the operation if the PLC cannot provide any further resources for cyclic services. WinCC Basic V13.0 System Manual, 02/2014 3815 Visualize processes 10.8 Communicating with PLCs The HMI device generates the cycle if the PLC does not support the cyclic mode. Screen tags are not integrated in cyclic operation. Cyclic mode is only set up at the restart of Runtime. The HMI device transfers several jobs to the PLC if cyclic mode is enabled, depending on the PLC. The HMI device only transfers one job to the PLC if cyclic mode is disabled. Parameters for the connection (SIMATIC S7 200) Parameters to be set To set the connection parameters, such as addresses and profiles, click the connection that you have created in the "Connections" editor. The communication partners are displayed schematically in the Inspector window under "Parameters". The "HMI device" and "PLC" areas are available for assigning parameters according to the interface used. 3816 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs Ethernet parameters Parameters for the HMI device You set the parameters for the HMI device in the network under "HMI device".. The changes are not transferred automatically to the HMI device. You must change the settings in the Control Panel of the HMI device. "Interface" If you are directly connected to the HMI device during configuration, you can set up the IP address of the HMI device in WinCC. Note The IP address in the Control Panel will be overwritten upon subsequent loading if you have already set up the IP address in the HMI device control panel. The IP address already set up in the Control Panel will be retained upon subsequent loading if you activate "Set IP address using a different method". The IP address is transferred to the HMI device during project transfer. To set up the IP address of the HMI device: - Click the HMI device. - Open the "Device configuration" editor. - Click the Ethernet interface. - Assign the IP address in the inspector window under: "General > PROFINET interface > Ethernet addresses" "Address" You assign the IP address of the HMI device in the "Address" area. When you transfer the WinCC project to the HMI device, this IP address is set up directly in the HMI device. "Access point" The access point defines a logical device name through which the communication partner can be reached. Parameters for the PLC Under "PLC", you address the S7 module with which the HMI device will exchange data. Assign a name for the connection for each communication partner. "Address" Under "Address", set the IP address of the S7 module to which the HMI device is connected. "Expansion slot" Defines the number of the expansion slot of the CPU to be addressed. WinCC Basic V13.0 System Manual, 02/2014 3817 Visualize processes 10.8 Communicating with PLCs "Rack" Defines the rack number of the CPU to be addressed. "Cyclic operation" Note The setting "Cyclic operation" cannot be configured for the SIMATIC S7 1200 PLC. When cyclic operation is enabled, the PLC optimizes the data exchange between the HMI device and the PLC. This increases system performance. Disable cyclic mode if you are operating several HMI devices in parallel. PROFIBUS parameters Parameters for the HMI device You assign the parameters for the HMI device in the network once under "HMI device". The change applies to each communication partner. "Type" Specifies the physical connection used. "Interface" For "Interface", you select the HMI device interface via which the HMI device is connected to the PROFIBUS network. "Baud rate" For "Baud rate", you set the transmission speed of the data in the network. The baud rate is determined by the slowest HMI device connected to the network. The setting must be identical throughout the network. Note If you set a baud rate of 1.5 Mbaud for OP 73 or OP 77A, the highest station address must be less than or equal to 63. "Address" You set the PROFIBUS address of the HMI device under "Address". The PROFIBUS address must be unique in the PROFIBUS network. "Sole master on bus" Disables an additional safety feature against bus faults when the HMI device is connected to the network. A passive station (slave) can only send data if it is requested to do so by an active station (master). In S7 200, you must set an HMI device as the master. "Access point" The access point defines a logical device name through which the communication partner can be reached. 3818 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs Parameters for the network Under "Network", you set the parameters for the PROFIBUS network to which the HMI device is linked. "Profile" For "Profile", you select the network profile that is used in the network. In "Profile", set "DP", "Universal", or "Standard". The setting must be identical throughout the network. "Highest address" For "Highest station address", set the highest station address. The highest station address must be greater than or equal to the highest actual PROFIBUS address. The setting must be identical throughout the network. Note If you set a baud rate of 1.5 Mbaud in the OP 73 or the OP 77A, the highest station address must be less than or equal 63. "Number of masters" For "Number of masters", set the number of masters in the PROFIBUS network. This information is necessary to correctly calculate the bus parameters. Parameters for the PLC Under "PLC", you address the S7 module with which the HMI device will exchange data. Assign a name for the connection for each communication partner. "Address" For "Address", set the PROFIBUS address of the S7 module (CPU, FM, or CP) to which the HMI device is connected. "Cyclic operation" Note The setting "Cyclic operation" cannot be configured for the SIMATIC S7 1200 PLC. When cyclic operation is enabled, the PLC optimizes the data exchange between the HMI device and the PLC. This increases system performance. Disable cyclic mode if you are operating several HMI devices in parallel. This setting is not required for SIMATIC S7-200 PLCs. WinCC Basic V13.0 System Manual, 02/2014 3819 Visualize processes 10.8 Communicating with PLCs MPI parameters Parameters for the HMI device You assign the parameters for the HMI device in the network once under "HMI device". The change applies to each communication partner. "Type" Specifies the physical connection used. "Interface" For "Interface", you select the HMI device interface via which the HMI device is connected to the MPI network. "Baud rate" For "Baud rate", you set the transmission speed of the data in the network. The baud rate is determined by the slowest HMI device connected to the network. The setting must be identical throughout the network. Note If you set a baud rate of 1.5 Mbaud for OP 73 or OP 77A, the highest station address must be less than or equal to 63. "Address" For "Address", you set the MPI address of the HMI device. The MPI address must be unique throughout the MPI network. "Sole master on bus" Disables an additional safety feature against bus faults when the HMI device is connected to the network. A passive station (slave) can only send data if it is requested to do so by an active station (master). If you have connected only slaves to the HMI device, you must therefore disable the "Sole master on bus" safety feature. In S7 200, you must set an HMI device as the master. Parameters for the network Under "Network", you set the parameters for the MPI network to which the HMI device is linked. "Profile" For "Profile", you select the network profile that is used in the network. In "Profile", set "MPI". The setting must be identical throughout the network. "Highest address" For "Highest station address", set the highest station address. The highest station address must be greater than or equal to the highest actual MPI address. The setting must be identical throughout the network. "Number of masters" This setting is not required for MPI. 3820 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs Parameters for the PLC Under "PLC", you address the S7 module with which the HMI device will exchange data. Assign a name for the connection for each communication partner. "Address" For "Address", set the MPI address of the S7 module (CPU, FM, or CP) to which the HMI device is connected. "Cyclic mode" When cyclic mode is enabled, the PLC optimizes the data exchange between the HMI device and the PLC. This improves system performance. Disable cyclic mode if you are operating several HMI devices in parallel. This setting is not required for SIMATIC S7-200. PPI parameters Parameters for the HMI device You assign the parameters for the HMI device in the network once under "HMI device". The change applies to each communication partner. "Type" Specifies the physical connection used. "Interface" For "Interface", you select the HMI device interface via which the HMI device is connected to the PP network. "Baud rate" For "Baud rate", you set the transmission speed of the data in the network. The baud rate is determined by the slowest HMI device connected to the network. The setting must be identical throughout the network. Note If you set a baud rate of 1.5 Mbaud for OP 73 or OP 77A, the highest station address must be less than or equal to 63. "Address" For "Address", you set the PPI address of the HMI device. The PPI address must be unique throughout the PPI network. "Access point" For "Access point", you set the access point via which the communication partner is reached. "Sole master on bus" Disables an additional safety feature against bus faults when the HMI device is connected to the network. A passive station (slave) can only send data if it is requested to do so by an active station (master). If you have connected only slaves to the HMI device, you must therefore disable the "Sole master on bus" safety feature. In S7 200, you must set an HMI device as the master. WinCC Basic V13.0 System Manual, 02/2014 3821 Visualize processes 10.8 Communicating with PLCs Parameters for the network Under "Network", you set the parameters for the network to which the HMI device is linked. "Profile" For "Profile", you select the network profile that is used in the network. In "Profile", set "PPI". The setting must be identical throughout the network. "Highest address" For "Highest station address", set the highest station address. The highest station address must be greater than or equal to the highest actual MPI address. The setting must be identical throughout the network. "Number of masters" Set the number of the master on the network to "1". Parameters for the PLC Under "PLC", you address the S7 module with which the HMI device will exchange data. Assign a name for the connection for each communication partner. "Address" For "Address", set the PPI address of the S7 module to which the HMI device is connected. "Cyclic operation" This parameter is not required for communication via PPI. 10.8.9.4 Data exchange Data exchange using area pointers General information on area pointers Introduction You use an area pointer to access a data area in the PLC. During communication, the PLC and the HMI device alternately access these data areas for read and write operations. The PLC and the HMI device trigger defined interactions based on the evaluation of stored data. Configuration of area pointers Before you use an area pointer, you enable it under "Connections > Area pointer". You then assign the area pointer parameters. You can find more detailed information on configuring area pointers in: Configuring area pointers (Page 3642) 3822 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs "Screen number" area pointer Function The HMI device saves information about the screen called on the HMI device to the "Screen number" area pointer. This allows the transfer of the current screen contents from the HMI device to the PLC. The PLC can trigger specific reactions such as the call of a different screen. Application Configure and enable the area pointer in "Communication > Connections" before you put it into use. You can create only one instance of the "Screen number" area pointer and only on one PLC. The screen number is always transferred to the PLC when a new screen is activated or when the focus within a screen changes from one screen object to another. Structure The area pointer is a data area in the memory of the PLC with a fixed length of 5 words. 15 14 13 12 11 10 9 8 7 6 1st word Current screen type 2nd word Current screen number 3rd word Reserved 4th word Current field number 5th word Reserved 5 4 3 2 1 0 Current screen type "1" for root screen or "4" for permanent window Current screen number 1 to 32767 Current field number 1 to 32767 "Date/time" area pointer Function This area pointer is used to transfer the date and time from the HMI device to the PLC. The PLC writes control job "41" to the job mailbox. WinCC Basic V13.0 System Manual, 02/2014 3823 Visualize processes 10.8 Communicating with PLCs When it evaluates the control job, the HMI device writes its current date and the time in the data area configured in the "Date/time" area pointer. All definitions are coded in BCD format. The "Date/Time" area pointer when used in a project which contains multiple connections must be enabled for each configured connection. Note You cannot use the "Date/Time PLC" area pointer if you have configured the "Date/Time" area pointer. Note Symbolic addressing is not possible if you are using the "Date/Time" area pointer. The "Date/Time" area pointer when used in a project which contains multiple connections must be enabled for each configured connection. The date/time data area has the following structure: Data word Most significant byte 7 Least significant byte 0 7 0 n+0 Reserved Hour (0 to 23) n+1 Minute (0 to 59) Second (0 to 59) n+2 Reserved Reserved n+3 Reserved Weekday (1 to 7, 1=Sunday) n+4 Day (1 to 31) Month (1 to 12) n+5 Year (80 to 99/0 to 29) Reserved Time Date Note When making entries in the "Year" data area, you should note that values 80 to 99 result in years 1980 through 1999, while the values 0 to 29 result in the years 2000 through 2029. "Date/time PLC" area pointer Function This area pointer is used to transfer the date and time from the PLC to the HMI device. Use this area pointer if the PLC is the time master. The PLC loads the data area of the area pointer. All definitions are coded in BCD format. 3824 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs The HMI device reads the data cyclically within the configured acquisition cycle and synchronizes itself. Note Set an acquisition cycle of sufficient length for the Date/time area pointer in order to avoid any negative impact on HMI device performance. Recommended: Acquisition cycle of 1 minute, if the process allows this. "Date/Time PLC" is a global area pointer and may be configured only once per project. Note You cannot use the "Date/Time" area pointer if you have configured the "Date/Time PLC" area pointer. The date/time data area has the following structure: DATE_AND_TIME format (in BCD code) Data word Most significant byte 7 1) ...... Least significant byte 0 7 ...... 0 n+0 Year (80 to 99/0 to 29) Month (1 to 12) n+1 Day (1 to 31) Hour (0 to 23) n+2 Minute (0 to 59) n+3 Reserved n+4 1) Reserved Reserved n+5 Reserved Reserved 1) Second (0 to 59) Reserved Weekday (1 to 7, 1=Sunday) The two data words must exist in the data area to ensure that the data format matches WinCC flexible and to avoid reading false information. Note When making entries in the "Year" data area, you should note that values 80 to 99 result in years 1980 through 1999, while the values 0 to 29 result in the years 2000 through 2029. WinCC Basic V13.0 System Manual, 02/2014 3825 Visualize processes 10.8 Communicating with PLCs "Coordination" area pointer Function The "Coordination" area pointer is used to implement the following functions: Detecting the startup of the HMI device in the control program Detecting the current operating mode of the HMI device in the control program Detecting whether the HMI device is ready to communicate in the control program By default, the "Coordination" area pointer has the length of one word and cannot be changed. Usage Note The HMI device always writes the entire coordination area when updating the area pointer. The control program can for this reason not make changes to the coordination area. Assignment of the bits in the "Coordination" area pointer ORZRUGHUE\WH KLJKRUGHUE\WH VWZRUG VWZRUGQRWDVVLJQHG UHVHUYHG [ DVVLJQHG ; ; ; 6WDUWXSELW 2SHUDWLRQPRGH /LIHELW Startup bit The startup bit is set briefly to "0" by the HMI device during startup. It sets the bit permanently to "1" when startup is completed. Operating mode The operating mode bit is set to 1 as soon as the user switches the HMI device offline. The status of the operating mode bit is "0" during normal operation of the HMI device. You can determine the current operating mode of the HMI device by reading this bit in the control program. Life bit The HMI device inverts the life bit at intervals of approximately one second. You can check whether or not there is still a connection to the HMI device by querying this bit in the control program. 3826 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs "Project ID" area pointer Function When Runtime starts, a check can be carried out as to whether the HMI device is connected to the correct PLC. This check is important when operating with several HMI devices. For this, the HMI device compares a value stored on the PLC with the value specified in configuration. This ensures compatibility of the configuration data with the PLC program. If there is no concordance, a system event is given on the HMI device and Runtime is stopped. Use Note HMI connections cannot be switched "online". The HMI connection in which the "Project ID" area pointer is used must be switched "online". To use this area pointer, set up the following during the configuration: Define the version of the configuration. Values between 1 and 255 are possible. You enter the version in the editor "Runtime settings > General" in the "Identification" area. Data address of the value for the version that is stored in the PLC: You enter the data address in the editor "Communication > Connections" under "Address". Connection failure A connection failure to a device on which the "Project ID" area pointer is configured results in all the other connections of the device being switched to "offline". This behavior has the following requirements: You have configured several connections in a project. You are using the "Project ID" area pointer in at least one connection. Causes which may set connections "offline": The PLC is not available. The connection has been switched offline in the Engineering System. WinCC Basic V13.0 System Manual, 02/2014 3827 Visualize processes 10.8 Communicating with PLCs "Job mailbox" area pointer Function The PLC can use the job mailbox to transfer jobs to the HMI device to trigger corresponding actions on the HMI device. These functions include, for example: Display screen Set date and time Data structure The first word of the job mailbox contains the job number. Depending on the job mailbox, up to three parameters can be transferred. Word Most significant byte Least significant byte n+0 0 Job number n+1 Parameter 1 n+2 Parameter 2 n+3 Parameter 3 The HMI device evaluates the job mailbox if the first word of this job is not equal to zero. This means that the parameters must be entered in the job mailbox first, followed by the job number. When the HMI device accepts the job mailbox, the first word is set to 0 again. The execution of the job mailbox is generally not completed at this point in time. Job mailboxes All job mailboxes and their parameters are listed below. The "No." column contains the job number of the job mailbox. Job mailboxes can only be triggered by the PLC when the HMI device is online. No . Function 14 Set time (BCD-coded) Parameter 1 Left byte: Right byte: hours (0-23) Parameter 2 Left byte: minutes (0-59) Right byte: seconds (0-59) Parameter 3 15 3828 Setting the date (BCD coded) 3) Parameter 1 Left byte: Right byte: Weekday (1-7: Sunday-Saturday) Parameter 2 Left byte: day (1-31) Right byte: month (1-12) Parameter 3 Left byte: year WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs No . Function 14 Set time (BCD-coded) 23 User logon Logs the user on with the name "PLC user" at the HMI device with the group number transferred in Parameter 1. The logon is possible only when the transferred group number exists in the project. 24 Parameter 1 Group number 1 to 255 Parameter 2, 3 - User logoff Logs off the current user. (The function corresponds to the "logoff" system function) Parameter 1, 2, 3 40 - Transfer date/time to PLC (In the S7 format DATE_AND_TIME) An interval of at least 5 seconds must be maintained between two successive jobs to prevent overload of the HMI device. Parameter 1, 2, 3 41 - Transfer date/time to PLC (In OP/MP format) An interval of at least 5 seconds must be maintained between successive jobs to prevent overload of the HMI device. Parameter 1, 2, 3 46 - Update tag Causes the HMI device to read the current value of the tags from the PLC whose update ID matches the value transferred in Parameter 1. (Function corresponds to the "UpdateTag" system function.) Parameter 1 49 1 - 100 Delete alarm buffer Deletes all analog alarms and discrete alarms of the "Warnings" class from the alarm buffer. Parameter 1, 2, 3 50 - Delete alarm buffer Deletes all analog alarms and discrete alarms of the "Errors" class from the alarm buffer. Parameter 1, 2, 3 51 69 - Screen selection 2) Parameter 1 Screen number Parameter 2 - Parameter 3 Field number Reading data record from PLC 1) Parameter 1 Recipe number (1-999) Parameter 2 Data record number (1-65535) Parameter 3 0: Do not overwrite existing data record 1: Overwrite existing data record 70 Writing data record to PLC Parameter 1 WinCC Basic V13.0 System Manual, 02/2014 1) Recipe number (1-999) 3829 Visualize processes 10.8 Communicating with PLCs No . Function 14 Set time (BCD-coded) Parameter 2 Data record number (1-65535) Parameter 3 - 1) Only devices supporting recipes 2) OP 73, OP 77A and TP 177A HMI devices also execute the "Screen selection" job mailbox if the on-screen keyboard is active. 3) The weekday is ignored on HMI device KTP 600 BASIC PN. "Data record" area pointer "Data record" area pointer Function When data records are transferred between the HMI device and PLC, both partners access common communications areas on the PLC. Data transfer types There are two ways of transferring data records between the HMI device and PLC: Transfer without synchronization Transfer with synchronization over the data record Data records are always transferred directly. That is, the tag values are read from an address or written to an address configured for this tag directly, without redirecting the values by means of interim memory. Initiating the transfer of data records There are three ways of triggering the transfer: Operator input in the recipe view Job mailboxes The transfer of data records can also be triggered by the PLC. Triggering by configured functions If the transfer of data records is triggered by a configured function or by a job mailbox, the recipe view on the HMI device remains operable. The data records are transferred in the background. Simultaneous processing of several transfer requests is, however, not possible. In this case, the HMI device rejects the other transfer requests with a system event. 3830 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs Sequence of a transfer started by the operator in the recipe view Reading from the PLC started by the operator in the recipe view Step Action 1 Check: Status word = 0? Yes No 2 The HMI device enters the recipe number to be read and the status "Transferring" in the data record and sets the data record number to 0. Abort with system event. 3 The HMI device reads the values from the PLC and displays them in the recipe view. If the recipes have synchronized tags, the values from the PLC are also written to the tags. 4 The HMI device sets the status "Transfer completed." 5 The control program must reset the status word to zero in order to enable further transfers. Writing to the PLC started by the operator in the recipe view Step Action Check: Status word = 0? 1 Yes The HMI device enters the recipe and data record number to be written and the status "Transferring" in the data mailbox. 2 No Abort with system event. The HMI device writes the current values to the PLC. If the recipes have synchronized tags, the changed values are synchronized in the recipe view and tags and then written to the PLC. 3 The HMI device sets the status "Transfer completed." 4 If required, the control program can now evaluate the transferred data. 5 The control program must reset the status word to zero in order to enable further transfers. Note The status word may only be set by the HMI device. The PLC may only reset the status word to zero. Note The PLC may only evaluate the recipe and data record numbers when data inconsistency is detected if one of the conditions outlined below has been met: The data mailbox status is set to "Transfer completed". The data mailbox status is set to "Transfer completed with error". WinCC Basic V13.0 System Manual, 02/2014 3831 Visualize processes 10.8 Communicating with PLCs Sequence of the transfer triggered by a job mailbox The transfer of data records between the HMI device and the PLC can be initiated by the HMI device or by the PLC. The two job mailboxes No. 69 and No. 70 are available for this type of transfer. No. 69: Read data record from PLC ("PLC DAT") Job mailbox no. 69 transfers data records from the PLC to the HMI device. The job mailbox is structured as follows: Left byte (LB) Right byte (RB) 0 69 Word 1 Word 2 Recipe number (1-999) Word 3 Data record number (1-65,535) Word 4 Do not overwrite existing data record: 0 Overwrite existing data record: 1 No. 70: Write data record to PLC ("DAT PLC") Job mailbox No. 70 transfers data records from the HMI device to the PLC. The job mailbox is structured as follows: Word 1 Left byte (LB) Right byte (RB) 0 70 Word 2 Recipe number (1-999) Word 3 Data record number (1-65,535) Word 4 -- Sequence when reading from the PLC with job mailbox "PLC DAT" (no. 69) Step Action 1 Check: Status word = 0? Yes No 2 The HMI device enters the recipe and data record number specified in the job and the status "Transferring" in the data mailbox. Abort without return message. 3 The HMI device reads the values from the PLC and saves these to the data record defined in the job mailbox. 4 If "Overwrite" was selected in the job, an existing data record is overwritten without any prompt for confirmation. The HMI device sets the status "Transfer completed." If "Do not overwrite" was selected in the job, and the data record already exists, the HMI device aborts the job and enters 0000 1100 in the status word of the data mailbox. 5 3832 The control program must reset the status word to zero in order to enable further transfers. WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs Sequence of writing to the PLC using job mailbox "DAT PLC" (no. 70) Step Action 1 Check: Status word = 0? Yes No 2 The HMI device enters the recipe and data record number specified in the job and the status "Transferring" in the data mailbox. Abort without return message. 3 The HMI device fetches the values of the data record specified in the job from the data medium and writes the values to the PLC. 4 The HMI device sets the status "Transfer completed." 5 The control program can now evaluate the transferred data. The control program must reset the status word to zero in order to enable further transfers. Sequence of the transfer when triggered by a configured function Reading from the PLC using a configured function Step Action 1 Check: Status word = 0? Yes No 2 The HMI device enters the recipe and data record number specified in the function and the status "Transferring" in the data mailbox. Abort with system event. 3 The HMI device reads the values from the PLC and stores them in the data record specified in the function. 4 If "Yes" was selected for the "Overwrite" function, an existing data record is overwritten without any prompt for confirmation. The HMI device sets the status "Transfer completed." If "No" was selected for the "Overwrite" function and the data record already exists, the HMI device aborts the job and enters 0000 1100 in the status word of the data mailbox. 5 The control program must reset the status word to zero in order to enable further transfers. Writing to the PLC by means of configured function Step Action 1 Check: Status word = 0? 2 WinCC Basic V13.0 System Manual, 02/2014 Yes No The HMI device enters the recipe and data record number specified in the function and the status "Transferring" in the data mailbox. Abort with system event. 3833 Visualize processes 10.8 Communicating with PLCs Step Action 3 The HMI device fetches the values of the data record specified in the function from the data medium and transfers the values to the PLC. 4 The HMI device sets the status "Transfer completed." 5 The control program can now evaluate the transferred data. The control program must reset the status word to zero in order to enable further transfers. Possible causes of error when transferring data records Possible causes of faults The section below shows possible causes of errors which lead to a data record transfer being terminated with errors: Tag address not set up on the PLC Overwriting data records not possible Recipe number does not exist Data record number does not exist Note The status word may only be set by the HMI device. The PLC may only reset the status word to zero. Note The PLC may only evaluate the recipe and data record numbers when data inconsistency is detected if one of the conditions outlined below has been met: The data mailbox status is set to "Transfer completed". The data mailbox status is set to "Transfer completed with error". Reaction to an aborted transfer due to errors If the transfer of data records is aborted due to errors, the HMI device reacts as follows: Triggering by the operator in the recipe view Information in the status bar of the recipe view and output of system events Triggered by function Output of system events Triggering by job mailbox No return message on the HMI device You can nonetheless evaluate the status of the transfer by querying the status word in the data mailbox. 3834 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs Transfer without synchronization If you select asynchronous transfer of data records between the HMI device and PLC, there is no coordination over the common data areas. It is therefore unnecessary to set up a data area during configuration. Asynchronous data record transfer can be a useful alternative, for example, when: The system is capable of excluding the risk of uncontrolled overwriting of data by the communication peer. The PLC does not require information about the recipe number and data record number. The transfer of data records is triggered by the operator of the HMI device. Reading values When a read job is triggered, the values are read from the PLC addresses and transferred to the HMI device. Triggering by the operator in the recipe view: The values are downloaded to the HMI device. You can then process, edit, or save these values, for example. Triggering by a function or job mailbox: The values are saved immediately to the data volume. Writing values When a write job is triggered, the values are written to the PLC addresses. Triggering by the operator in the recipe view: The current values are written to the PLC. Triggering by a function or job mailbox: The current values are written to the PLC from the data medium. Transfer with synchronization If you select synchronous transfer, both communication partners set status bits in the common data area. You can use this mechanism to prevent uncontrolled overwriting of data in either direction in your control program. Application Synchronous data record transfer can be a useful solution, for example, when: The PLC is the "active partner" in the transfer of data records. The PLC evaluates the information about the recipe number and data record number. The transfer of data records is triggered by means of a Job mailbox. WinCC Basic V13.0 System Manual, 02/2014 3835 Visualize processes 10.8 Communicating with PLCs Requirements In order to synchronize transfer of data records between the HMI device and the PLC, the following requirements must be met during configuration: An area pointer has been set up: "Communication > Connections" editor in "Area pointer". The PLC with which the HMI device synchronizes transfer of data records is specified in the recipe: "Recipes" editor in the Inspector window the "Coordinated transfer of data records" option under "General > Synchronization > Settings". Structure of the data area The data area has a fixed length of 5 words. Structure of the data area: 15 0 1. Word Current recipe number (1 - 999) 2. Word Current data record number (0 - 65535) 3. Word Reserved 4. Word Status (0, 2, 4, 12) 5. Word Reserved Status The status word (word 4) can adopt the following values: Value Meaning Decimal Binary 0 0000 0000 Transfer permitted, data record free 2 0000 0010 Transferring 4 0000 0100 Transfer completed without error 12 0000 1100 Transfer completed with error Trends Trends A trend is the graphical representation of one or more values from the PLC. The value is read out time-triggered for Basic Panels. For additional information see: Configuring trend displays for values from the PLC (Page 3369) Time-triggered trends The HMI device reads in the trend values cyclically at an interval specified in the configuration. 3836 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs Time-triggered trends are suitable for continuous curves, such as the operating temperature of a motor. Alarms Configuring alarms Configure alarms Several steps are needed to configure alarms, such as operational messages, error alarms, and acknowledgement. Step 1: Create tags Step 2: Configure alarms Step 3: Configure acknowledgment You can find additional information in the section: Working with alarms (Page 3379) Distinctive features when configuring alarms If you are configuring connections of HMI devices to PLCs of other manufacturers, note the following distinctive features when configuring: Data types of the tags Addressing of tags How the bit positions are counted Data types For connections with a SIMATIC communication driver, the following data types are supported: PLC SIMATIC S7 PLCs WinCC Basic V13.0 System Manual, 02/2014 Permitted data types Discrete alarms Analog alarms WORD, INT BYTE, CHAR, WORD, INT, DWORD, DINT, REAL, TIMER 3837 Visualize processes 10.8 Communicating with PLCs How the bit positions are counted For connections with a SIMATIC communication driver, the following counting method applies: How the bit positions are counted Byte 0 Byte 1 Most significant byte Least significant byte In SIMATIC S7 PLCs 7 0 7 0 In WinCC you configure: 15 8 7 0 Acknowledgment of alarms Procedure Create suitable tags on the PLC to acknowledge an error alarm. You assign these tags to an alarm in the "Bit messages" editor. You make the assignment in "Properties > Acknowledgment". Distinction in terms of acknowledgment: Acknowledgment by the PLC Acknowledgment on the HMI device Acknowledgment by the PLC In "PLC acknowledgment tag", configure the tag or array tag and the bit number that the HMI device uses to identify a PLC acknowledgment. A bit set in the tag triggers acknowledgment of the assigned error alarm bit at the HMI device. This tag bit returns a function similar to acknowledgment on the HMI device which is triggered by pressing the "ACK" button, for example. The acknowledgment bit must be located in the same tag as the bit for the error alarm. Reset the acknowledgment bit before setting the bit in the alarm area again. The figure below shows the pulse diagram. (UURUDODUP $FNQRZOHGJPHQW 3/&+0,GHYLFH $UULYDORIWKH $FNQRZOHGJP 5HVHWRI HUURUDODUP YLD3/& DFNQRZOHGJPELW 3838 1HZ HUURUDODUP WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs Acknowledgment on the HMI device In the "HMI acknowledgment tag" area, configure the tag or array tag as well as the bit number that the HMI device writes to the PLC after acknowledgment. Make sure when you use an array tag that it is not longer than 6 words. To always create a signal change when setting an assigned acknowledgment bit of a discrete alarm that must be acknowledged, the HMI device will reset the acknowledgment bit assigned to the alarm as soon as it detects an alarm subject to acknowledgment and write the acknowledgment tag in the PLC. There will be a certain delay between detecting the message and writing the acknowledgment tag in the PLC because the HMI device has to process the operations. If a discrete alarm subject to acknowledgment is acknowledged by the HMI device, then the corresponding bit in the assigned acknowledgment tag will be set. The entire acknowledgment tag is then written to the PLC by the HMI device. This allows the PLC to recognize that a certain alarm message has been acknowledged at the HMI device. Note All alarm bits acknowledged since the last Runtime start will remain in the acknowledgment tag until a new incoming of the respective discrete alarms is detected. This area should only be read by the PLC because the entire section of the HMI device will be overwritten once the next acknowledgment tag is written. The figure below shows the pulse diagram. (UURUDODUP $FNQRZOHGJPHQW +0,GHYLFH3/& $UULYDORIWKH HUURUDODUP WinCC Basic V13.0 System Manual, 02/2014 5HVHWRI DFNQRZOHGJPELW $FNQRZOHGJP YLD+0,GHYLFH 1HZ HUURUDODUP 3839 Visualize processes 10.8 Communicating with PLCs 10.8.9.5 Performance features of communication Permitted data types for SIMATIC S7 200 Permitted data types for connections with SIMATIC S7 200 The table lists the data types that can be used when configuring tags and area pointers. Data type Length Bool 1 bit Byte 1 byte Char 1 byte Word 2 bytes Int 2 bytes DWord 4 bytes DInt 4 bytes Real 4 bytes StringChar -- Timer 2 bytes Array -- Note Disconnection with a PPI network If you are using arrays in the configuration, an array size of approximately 1000 bytes may cause an interruption of the connection. Use smaller arrays in your configuration. 10.8.10 Communicating with SIMATIC LOGO! 10.8.10.1 Communication with SIMATIC LOGO! Introduction This section describes the communication between an HMI device and the SIMATIC SIMATIC LOGO! controller. You can configure the following communication channels for the SIMATIC LOGO! controller: PROFINET Ethernet 3840 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs HMI connection for communication You configure connections between the HMI device and SIMATIC LOGO! in the "Connections" editor of the HMI device. Data exchange Data exchange with the SIMATIC LOGO! control system is possible by means of tags. Data cannot be exchanged using area pointers. 10.8.10.2 Creating a connection to SIMATIC LOGO! Introduction You configure a connection to the SIMATIC LOGO! controller in the "Connections" editor of the HMI device. The interfaces are named differently depending on the HMI device. Requirements A project is open. An HMI device has been created. Procedure 1. Double-click the HMI device under "Devices" in the project tree. 2. Double-click the "Connections" item. WinCC Basic V13.0 System Manual, 02/2014 3841 Visualize processes 10.8 Communicating with PLCs 3. Double-click "<Add>" in the "Connections" editor. 3842 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs 4. In the "Communication drivers" column, select the "SIMATIC LOGO!" driver. 5. Select all necessary connection parameters for the interface in the Inspector window under "Parameters". See the chapter "Auto-Hotspot" for additional details. 10.8.10.3 Connection parameters Connection parameters Parameters to be set To set the connection parameters, such as addresses and profiles, click the connection that you have created in the "Connections" editor. The communication partners are displayed schematically in the Inspector window under "Parameters". The "HMI device" and "PLC" areas are available for assigning parameters according to the interface used. WinCC Basic V13.0 System Manual, 02/2014 3843 Visualize processes 10.8 Communicating with PLCs 3844 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs Ethernet parameters Parameters for the HMI device You set the parameters for the HMI device in the network under "HMI device".. The changes are not transferred automatically to the HMI device. You must change the settings in the Control Panel of the HMI device. "Interface" If you are directly connected to the HMI device during configuration, you can set up the IP address of the HMI device in WinCC. Note The IP address in the Control Panel will be overwritten upon subsequent loading if you have already set up the IP address in the HMI device control panel. The IP address already set up in the Control Panel will be retained upon subsequent loading if you activate "Set IP address using a different method". The IP address is transferred to the HMI device during project transfer. To set up the IP address of the HMI device: - Click the HMI device. - Open the "Device configuration" editor. - Click the Ethernet interface. - Assign the IP address in the inspector window under: "General > PROFINET interface > Ethernet addresses" "Address" You assign the IP address of the HMI device in the "Address" area. When you transfer the WinCC project to the HMI device, this IP address is set up directly in the HMI device. "Access point" The access point defines a logical device name through which the communication partner can be reached. Parameters for the PLC Under "PLC", you address the S7 module with which the HMI device will exchange data. Assign a name for the connection for each communication partner. "Address" Under "Address", set the IP address of the S7 module to which the HMI device is connected. "Expansion slot" Defines the number of the expansion slot of the CPU to be addressed. WinCC Basic V13.0 System Manual, 02/2014 3845 Visualize processes 10.8 Communicating with PLCs "Rack" Defines the rack number of the CPU to be addressed. "Cyclic operation" Note The setting "Cyclic operation" cannot be configured for the SIMATIC S7 1200 PLC. When cyclic operation is enabled, the PLC optimizes the data exchange between the HMI device and the PLC. This increases system performance. Disable cyclic mode if you are operating several HMI devices in parallel. Cyclic operation Handling the "Cyclic operation" selection If "Cyclic operation" is enabled, the HMI device sends a message frame to the CPU at the beginning of communication indicating that certain tags are required on a recurring basis. The CPU then always transmits the data at the same cyclic interval. This saves the HMI device from having to output new requests for the data. If cyclic operation is disabled, the HMI device sends a request whenever information is required. Additional properties: Cyclic operation reduces data transmission load at the HMI device. The PLC resources are used to relieve load on the HMI device. The PLC only supports a certain number of cyclic services. The HMI device handles the operation if the PLC cannot provide any further resources for cyclic services. The HMI device generates the cycle if the PLC does not support the cyclic mode. Screen tags are not integrated in cyclic operation. Cyclic mode is only set up at the restart of Runtime. The HMI device transfers several jobs to the PLC if cyclic mode is enabled, depending on the PLC. The HMI device only transfers one job to the PLC if cyclic mode is disabled. 3846 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs 10.8.10.4 Data exchange Trends General information on trends Trends A trend is the graphical representation of one or more values from the PLC. The value is read out either time- or bit-triggered, depending on the configuration. For additional information see: Auto-Hotspot Note The value is read out time-triggered for Basic Panels. Time-triggered trends The HMI device reads in the trend values cyclically at an interval specified in the configuration. Time-triggered trends are suitable for continuous curves, such as the operating temperature of a motor. Bit-triggered trends Through a trigger bit set in the trend request tag, the HMI device either reads in a trend value or an entire trend buffer. This setting is defined in the configuration. Bit-triggered trends are normally used to represent fast changing values. One example might be the injection pressure in the production of plastic parts. To trigger bit-triggered trends, appropriate external tags must be created in the "HMI tags" editor and connected to trend areas during configuration. The HMI device and PLC then communicate with each other via these trend areas. The following areas are available for trends: Trend request area Trend transfer area 1 Trend transfer area 2 (required only with switch buffers) WinCC Basic V13.0 System Manual, 02/2014 3847 Visualize processes 10.8 Communicating with PLCs Trend request and trend transfer Trend request area The HMI device sets corresponding bits in the trend request area when you open a screen which contains one or more trends on the HMI device. After closing the screen, the HMI device resets the relevant bits in the trend request area. The trend request area can be used for evaluation purposes in the PLC to determine which trend is currently being displayed on the HMI device. Trends can also be triggered without evaluation of the trend request area. Trend transfer area 1 This area is used to trigger trends. You must set the bit assigned to the trend in the trend transfer area and set the trend group bit in your control program. The trend group bit is the last bit in the trend transfer area. The HMI device detects the trigger. The HMI device reads either a value or the entire buffer from the PLC. It then resets the trend bit and the trend group bit. The following picture shows the structure of a trend transfer area. ORZRUGHUE\WH KLJKRUGHUE\WH %LWQXPEHU VWZRUG QWKZRUG 7UHQGJURXSELW The trend transfer area must not be modified by the PLC program until the trend group bit has been reset. Trend transfer area 2 Trend transfer area 2 is required for trends configured with a switch buffer. The trend transfer areas 1 and 2 have a similar structure. Switch buffer The switch buffer is a second buffer for the same trend that can be set up during configuration. The PLC writes to Buffer 2 while the HMI device reads values from Buffer 1, and writes to Buffer 1 when the HMI device is reading Buffer 2. This prevents the PLC from overwriting trend values while the trend is being read by the HMI device. 3848 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs Permitted data types for trends For SIMATIC S7 You assign one bit to each trend during configuration. Tags and array tags of the "Word" or "Int" data type are permitted. Alarms Configuring alarms Configure alarms Several steps are needed to configure alarms, such as operational messages, error alarms, and acknowledgement. Step 1: Create tags Step 2: Configure alarms Step 3: Configure acknowledgment You can find additional information in the section: Auto-Hotspot Distinctive features when configuring alarms If you are configuring connections of HMI devices to PLCs of other manufacturers, note the following distinctive features when configuring: Data types of the tags Addressing of tags How the bit positions are counted Data types For connections with a SIMATIC communication driver, the following data types are supported: PLC SIMATIC S7 PLCs WinCC Basic V13.0 System Manual, 02/2014 Permitted data types Discrete alarms Analog alarms WORD, INT BYTE, CHAR, WORD, INT, DWORD, DINT, REAL, TIMER 3849 Visualize processes 10.8 Communicating with PLCs How the bit positions are counted For connections with a SIMATIC communication driver, the following counting method applies: How the bit positions are counted Byte 0 Byte 1 Most significant byte Least significant byte In SIMATIC S7 PLCs 7 0 7 0 In WinCC you configure: 15 8 7 0 Acknowledgment of alarms Procedure Create suitable tags on the PLC to acknowledge an error alarm. You assign these tags to an alarm in the "Bit messages" editor. You make the assignment in "Properties > Acknowledgment". Distinction in terms of acknowledgment: Acknowledgment by the PLC Acknowledgment on the HMI device Acknowledgment by the PLC In "PLC acknowledgment tag", configure the tag or array tag and the bit number that the HMI device uses to identify a PLC acknowledgment. A bit set in the tag triggers acknowledgment of the assigned error alarm bit at the HMI device. This tag bit returns a function similar to acknowledgment on the HMI device which is triggered by pressing the "ACK" button, for example. The acknowledgment bit must be located in the same tag as the bit for the error alarm. Reset the acknowledgment bit before setting the bit in the alarm area again. The figure below shows the pulse diagram. (UURUDODUP $FNQRZOHGJPHQW 3/&+0,GHYLFH $UULYDORIWKH $FNQRZOHGJP 5HVHWRI HUURUDODUP YLD3/& DFNQRZOHGJPELW 3850 1HZ HUURUDODUP WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs Acknowledgment on the HMI device In the "HMI acknowledgment tag" area, configure the tag or array tag as well as the bit number that the HMI device writes to the PLC after acknowledgment. Make sure when you use an array tag that it is not longer than 6 words. To always create a signal change when setting an assigned acknowledgment bit of a discrete alarm that must be acknowledged, the HMI device will reset the acknowledgment bit assigned to the alarm as soon as it detects an alarm subject to acknowledgment and write the acknowledgment tag in the PLC. There will be a certain delay between detecting the message and writing the acknowledgment tag in the PLC because the HMI device has to process the operations. If a discrete alarm subject to acknowledgment is acknowledged by the HMI device, then the corresponding bit in the assigned acknowledgment tag will be set. The entire acknowledgment tag is then written to the PLC by the HMI device. This allows the PLC to recognize that a certain alarm message has been acknowledged at the HMI device. Note All alarm bits acknowledged since the last Runtime start will remain in the acknowledgment tag until a new incoming of the respective discrete alarms is detected. This area should only be read by the PLC because the entire section of the HMI device will be overwritten once the next acknowledgment tag is written. The figure below shows the pulse diagram. (UURUDODUP $FNQRZOHGJPHQW +0,GHYLFH3/& $UULYDORIWKH HUURUDODUP 5HVHWRI DFNQRZOHGJPELW $FNQRZOHGJP YLD+0,GHYLFH 1HZ HUURUDODUP 10.8.10.5 Performance features of communication Valid data types for SIMATIC LOGO! Valid data types for connections with SIMATIC LOGO! Data type Length Bool 1 bit Byte 1 byte WinCC Basic V13.0 System Manual, 02/2014 3851 Visualize processes 10.8 Communicating with PLCs 10.8.11 Data type Length Int 2 bytes DInt 4 bytes Word 2 bytes DWord 4 bytes Array -- Communication with other PLCs 10.8.11.1 Communication with other PLCs Introduction Communication with other PLCs is communication with PLCs that are not in the SIMATIC family. These PLCs have proprietary protocols for data exchange. The protocols are configured as communication drivers in WinCC. Communication drivers The following communication drivers are supported in WinCC and are already installed: Allen-Bradley - Allen-Bradley EtherNet/IP - Allen-Bradley DF1 Mitsubishi - Mitsubishi MC TCP/IP - Mitsubishi FX Modicon Modbus - Modicon Modbus TCP/IP - Modicon Modbus RTU Omron - Omron Host Link 3852 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs Communication drivers in WinCC RT Professional The following communication drivers are supported for RT Professional: Allen-Bradley - Allen-Bradley EtherNet/IP Mitsubishi - Mitsubishi MC TCP/IP Modicon Modbus - Modicon Modbus TCP Connections between HMI devices and other PLCs You configure the connections between HMI devices and other PLCs in the "Connections" editor of the HMI device. These connections are non-integrated connections. 10.8.11.2 Distinctive features when configuring Distinctive features for data exchange Distinctive features apply when configuring connections to other PLCs, compared to configuring integrated connections. Note the following distinctive features when configuring: Addressing of tags Permitted data types Distinctive features when configuring area pointers Distinctive features when configuring alarms Distinctive features when configuring trends For more detailed information on distinctive features when configuring, refer to Section "Data exchange" of the respective communication driver. 10.8.11.3 Communication drivers Allen-Bradley Allen-Bradley communication drivers Introduction This section describes the communication between an HMI device and PLCs that use AllenBradley communication drivers. WinCC Basic V13.0 System Manual, 02/2014 3853 Visualize processes 10.8 Communicating with PLCs The following communication drivers are supported: Allen-Bradley EtherNet/IP Allen-Bradley DF1 Data exchange Data is exchanged by means of tags or area pointers. Tags The PLC and the HMI device use process values for data exchange. You create tags in the configuration that point to addresses in the PLC. The HMI device reads the value from the defined address, and then displays it. The operator may also enter values on the HMI device, which are then written to the address in the PLC. Area pointers Area pointers are used to exchange specific data and are only set up when these data are used. Allen-Bradley EtherNet/IP Configuring a connection via Allen-Bradley EtherNet/IP Introduction You configure a connection to a PLC with an Allen-Bradley EtherNet/IP communication driver in the "Connections" editor of the HMI device. The Ethernet interfaces are named differently depending on the HMI device. Example: PROFINET interface corresponds to the Ethernet interface Requirements A project is open. An HMI device has been created. Procedure 1. Double-click the HMI device under "Devices" in the project tree. 2. Double-click the "Connections" item. 3854 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs 3. Double-click "<Add>" in the "Connections" editor. WinCC Basic V13.0 System Manual, 02/2014 3855 Visualize processes 10.8 Communicating with PLCs 4. In the "Communication drivers" column, select the "Allen-Bradley EtherNet/IP" driver. 5. Select all necessary connection parameters for the interface in the Inspector window under "Parameters". Parameters for the connection (Allen-Bradley EtherNet/IP) Parameters to be set To assign the connection parameters, such as addresses and profiles, click the connection that you have created in the "Connections" editor. The communication partners are displayed schematically in the Inspector window under "Parameters". The "PLC" area is available for assigning parameters according to the interface used. 3856 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs Parameters for the HMI device You can select only one interface for the HMI device in the Inspector window under "Parameters". Depending on the HMI device, there are several interfaces available. If you are directly connected to the HMI device during configuration, you can set up the IP address of the HMI device in WinCC. The IP address is transferred to the HMI device upon subsequent loading. Note The IP address in the control panel will be overwritten upon subsequent loading if you have already set up the IP address in the HMI device control panel. The IP address already set up in the control panel will be retained upon subsequent loading if you activate "Set IP address using a different method". To set up the IP address of the HMI device: 1. Click on the HMI device. 2. Open the "Device configuration" editor. WinCC Basic V13.0 System Manual, 02/2014 3857 Visualize processes 10.8 Communicating with PLCs 3. Click the Ethernet interface. 4. Assign the IP address in the inspector window under: "General > PROFINET interface > Ethernet addresses" Parameters for the PLC CPU type For "CPU type", set the CPU type of the PLC used. IP address Set the IP address or host name of the Ethernet/IP module of the PLC. Only the IP address can be used on a Basic Panel. Communication path Set the CIP path from the Ethernet module to the PLC. This establishes a logical connection between the Ethernet module and PLC, even if both devices are located in different CIP networks. For additional information see: Examples: Communication path Connecting HMI device to PLC Connections via Allen-Bradley EtherNet/IP Connection The HMI device can be connected to the Allen-Bradley PLC using the following components: Existing Ethernet network that also contains the PLCs Cross-over Ethernet cable connected directly to the Ethernet interface of the CPU or the communication module The connection of the HMI device to an Allen-Bradley PLC is limited primarily to the physical connection of the HMI device. Special blocks for the connection are not required in the PLC. Communication types Approved communication types with Allen-Bradley EtherNet/IP The following communication types are system-tested and approved: Point-to-point connection to the approved PLCs Multipoint connection from a HMI device (Allen-Bradley Ethernet/IP-Client) with up to 4 PLCs with the respectively approved PLCs. CPU types can be mixed. 3858 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs Connection Connection with the following PLCs is approved with Allen-Bradley EtherNet/IP: CPU type: "ControlLogix, Compact Logix" - ControlLogix 556x(1756-L6x) with Ethernet module 1756-ENBT - Guard Logix-System ControlLogix 556xS(1756-L6xS) with Ethernet module 1756-ENBT - CompactLogix - 533xE(1769-L3xE) with Ethernet interface onboard - 532xE(1769-L2xE) with Ethernet interface onboard - 534x (1768-L4x) with Ethernet module 1768-ENBT CPU type: "SLC, MicroLogix" - MicroLogix 1100 (with Ethernet interface onboard) - MicroLogix 1400 (with Ethernet interface onboard) - SLC 5/05 (with Ethernet interface onboard) Performance features of communication Permitted data types for Allen-Bradley EtherNet/IP Permitted data types The table lists the data types that can be used when configuring tags and area pointers. CPU type: ControlLogix, CompactLogix Data type Length Bool 1 bit DInt 4 bytes Int 2 bytes Real 4 bytes SInt 1 byte String 1 to 80 characters UDInt 4 bytes UInt 2 bytes USInt 1 byte Permitted data types arrays WinCC Basic V13.0 System Manual, 02/2014 3859 Visualize processes 10.8 Communicating with PLCs Address Permitted data types Array SInt, USInt, Int, UInt, DInt, UDInt, Real Individual bits from the basic data types of the PLC SInt, USInt, Int, UInt, DInt, UDInt Bool* * Any changed value of certain defined bits is written back to the PLC. There is no check to determine whether any other bits have changed. The PLC (or other PLCs) may only read access the value. CPU type: SLC, MicroLogix Data type Operand type Length ASCII A 0 to 80 characters Bool N, R, C, T, B, S, I, O 1 bit DInt N 4 bytes Int N, R, C, T, S 2 bytes Real N, F 4 bytes String ST 1 to 82 characters UDInt N 4 bytes UInt N, R, C, T, B, I, O 2 bytes Permitted data types arrays Address Permitted data types Array Int, UInt, DInt, UDInt, Real Distinctive features for connections with Allen-Bradley Ethernet/IP With the communication driver Allen Bradley Ethernet/IP and the CPU type SLC, MicroLogix, you can only use array tags for discrete alarms and trends. Note I/O modules with 8 or 16 ports occupy one data word on the PLC. I/O modules with 24 or 32 ports occupy two data words. The HMI device does not output an error message if using non-existent bits. You should always make sure that I/O modules with 8 or 24 ports only occupy the bits that are actually assigned to a port. 3860 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs Supported CPU types for Allen-Bradley EtherNet/IP CPU types The following CPU types are supported for configuring the Allen-Bradley EtherNet/IP communication driver. CompactLogix - 1769-L2xE with Ethernet interface onboard - 1769-L3xE with Ethernet interface onboard - 1768-L4x with Ethernet module 1768-ENBT ControlLogix - 1756-L6x with Ethernet module 1756-ENBT GuardLogix - 1756-L61S with Ethernet module 1756-ENBT - 1756-L62S with Ethernet module 1756-ENBT - 1756-L63S with Ethernet module 1756-ENBT MicroLogix - MicroLogix 1100 / 1400 SLC50x - SLC5/05 Addressing in the C.Logix CPU type Addressing Addressing A tag is uniquely referenced in WinCC by means of an address in the PLC. The address must correspond with the tag name in the PLC. The tag address is defined by a string with a length of up to 128 characters. Using characters for addressing Valid characters for tag addressing: Letters (a to z, A to Z) Numbers (0 to 9) Underscore ( _ ) The tag address consists of tag name and other character strings used to specify the tag in the PLC. WinCC Basic V13.0 System Manual, 02/2014 3861 Visualize processes 10.8 Communicating with PLCs Tag name properties: The tag name may begin but not end with an underscore character. Strings with successive underscore and space characters are invalid. The address may not exceed a length of 128 characters. Note The characters reserved for tag addressing may not be used in program/tag names or at any other address instance. The reserved characters are listed below: Reserved character Function . Element delimiter : Definition of a program tag , Delimiter for addressing multi-dimensional arrays / Reserved for bit addressing. [] Addressing of array elements or arrays PLC and program tags The Allen-Bradley EtherNet/IP communication driver supports addressing of PLC tags (global project tags) and/or program tags (global program tags). A program tag is declared based on the program name in the PLC and actual tag name which are delimited by colon. PLC tags are simply addressed by their name. Note Addressing errors Addressing errors occur when the tag name and data type are inconsistent. Note that the tag name defined in the address field in WinCC must match the tag name in the PLC. Make sure that the data types of tags in WinCC match the data types in the PLC. Note Module-specific tags, e.g. for data on input and output modules, cannot be addressed directly. Instead, use an alias tag in the PLC. Example: Local:3:O. Data cannot be addressed in WinCC. If the alias "MyOut" is defined for Local:3:O in the PLC, you can address with WinCC via MyOut.Data. 3862 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs Addressing syntax Notation of addresses The tables below define the notation for the individual addressing options for Allen-Bradley EtherNet/IP. Table 10-12 Access to arrays, basic data types and structure elements Data types Type Address Basic data types PLC tag Tag name Program tag Programname:tagname PLC tag Array tag Program tag Program name: array tag PLC tag Tagname/bitnumber Program tag Programname:tagname/bitnumber PLC tag Structure tag. Structure element Program tag Program name: structure tag. structure element Arrays Bits Structure elements Note Bit addressing with the data types Bool, Real and String is not permitted and will cause an addressing fault. Description of the syntax Syntax description: (Programname:)tagname([x(,y)(,z)]){.tagname([x(,y)(,z)])}(/ bitnumber) The "( )" defines an optional, single instance of an expression. The "{ }" defines an optional expression with multiple single instances. The address string length may not exceed 128 characters. Addressing types Arrays An array is a data structure that includes a number of data of the same type. WinCC only supports one-dimensional arrays. In the address column of the tag editor, enter the array name possibly by specifying a start element. The length is defined in the Array Elements input box of the tag editor. If array limits in the PLC are exceeded (due to faulty indexing), addressing errors result. These arrays must be declared in the PLC as controller or program tags. WinCC Basic V13.0 System Manual, 02/2014 3863 Visualize processes 10.8 Communicating with PLCs Two- or three-dimensional arrays in the PLC can only be addressed in WinCC if these can be mapped area-wise onto one-dimensional arrays . Note During all read accesses and all write accesses, all array elements of a tag are always read or written, respectively. The contents of an array tag which is interconnected with a PLC are always transferred whenever there is a change. The HMI device and the PLC cannot concurrently write data to the same array tag for this reason. Instead of writing data only to a single element, the program writes the entire array to the PLC. Array elements Elements of one-dimensional, two-dimensional and three-dimensional arrays in the PLC are indexed by setting an index and the corresponding notation in the tag editor. Array addressing starts at element "0", with arrays of all basic types being valid for element addressing. Read/ write operations are only carried out at the addressed element, and not for the entire array. Bits and bit tags Bit access is allowed to all basic data types with the exception of Bool, Real and String. Bit addressing is also allowed at array/structure elements. The Bool data type is set in WinCC when bits and bit tags in the basic data types are addressed. Single-digit bit numbers are addressed with "/x" or "/0x" (x = bit number). Bit numbers are defined by up to two digits. Note With the "Bool" data type in the data types SInt, Int and DInt, after changing the specified bit the complete tag is then written in the PLC again. In the meantime, no check is made as to whether other bits in the tag have since changed. Therefore, the PLC may have only read access to the specified tag. Structures User-defined data types are created by means of structures. These structures group tags of different data types. Structures may consist of basic types, arrays and of other structures. In WinCC, only structure elements are addressed and not entire structures. Structure elements Structure elements are addressed by means of the name of the structure and of the required structure element. This addressing is separated by point. In addition to basic data types, the 3864 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs structure elements may represent arrays or other structures. Only one-dimensional arrays may be used as a structure element. Note The nesting depth of structures is only limited by the maximum length of 128 characters for the address. Address multiplexing Address multiplexing Address multiplexing is possible with the CompactLogix, ControlLogix CPU type. Address multiplexing requires two tags: "Tag_1" of data type "String"; contains a logical address such as "HMI:Robot5.Block5" as value. The value may change to a second valid address, for example, "HMI:Robot4.Block3". "Tag_2" is a tag in which the "Allen-Bradley EtherNet/IP" communication driver is set up as a connection. Enter a valid name of an HMI_tag in square brackets as the address. - e.g.: "[Tag_1]" - The tag must be of the String data type. - The square brackets indicate address multiplexing. - The address is derived from the actual value in "Tag_1". Note You can only multiplex entire Allen-Bradley EtherNet/IP addresses. Multiplexing of address elements is not possible. "HMI:Robot[Tag_1].Block5" is an invalid address. You can optionally click the arrow right icon in the "Address" column. Replace the "Constant" with the "Multiplex" entry by clicking the arrow on the left edge of the next address dialog box. Now the tag selection list only returns tags of data type "String". You can also configure a function triggered by a "change of value" event for multiplexed tags. Examples for addressing Example of a table for addressing The table below defines the basic variants for addressing PLC tags. Other addressing variants are possible by means of combination. WinCC Basic V13.0 System Manual, 02/2014 3865 Visualize processes 10.8 Communicating with PLCs Type Type Address General PLC tag Tag name Program tag Program:tagname Array Access to an element of a 2- Arraytag[Dim1,Dim2] dimensional array Element of structure array (1- Arraytag[Dim1].structureelement dimensional) Structure Bit in element basic type array (2-dimensional) Arraytag[Dim1,Dim2]/Bit Array in structure Structuretag.arraytag Bit in the element of an array in the substructure Structuretag.structure2.arraytag [element]/ bit Note Program tags are addressed by leading the address with the program name derived from the PLC with colon delimiter. Example: Programname:arraytag[Dim1,Dim2] Access to array elements Type Address PLC tag Arraytag[Dim1] Arraytag[Dim1,Dim2] Arraytag[Dim1,Dim2,Dim3] Program tag Programname:arraytag[Dim1] Programname:arraytag[Dim1,Dim2] Programname:arraytag[Dim1,Dim2,Dim3] Examples: Communication path Example 1: Connection with a PLC in the same Allen-Bradley rack. 1,0 3866 Number Meaning 1 Stands for a backplane connection. 0 Stands for a CPU slot number. WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs Example 2: Connection with a PLC in remote Allen-Bradley racks. Two Allen-Bradley racks are networked on Ethernet. 1,2,2,190.130.3.101,1,5 Number Meaning 1 Backplane connection 2 Stands for the CPU slot number of the second Ethernet module. 2 Stands for an Ethernet connection. 190.130.3.101 IP address of a remote AB rack on the network - in particular the third Ethernet module 1 Backplane connection 5 Slot number of the CPU Commissioning components Transferring a project to the HMI device 1. Switch the HMI device to "transfer mode". 2. Set all necessary transfer parameters. - Interface - Transfer parameters - Target storage location 3. Start the project transfer. The project is compiled automatically. All compilation and transfer steps are logged to a message window. Note If running the CompactLogix PLC with firmware earlier than version 18, you will possibly have to restart the HMI device following the transfer of the PLC program. You could also terminate the connection before transferring the PLC program and set up the connection again after having completed the transfer of the PLC program. Interconnecting the PLC with the HMI device 1. Interconnect the PLC with the HMI device using a suitable cable. 2. The message "Connection to PLC .... is established" is output to the HMI device. WinCC Basic V13.0 System Manual, 02/2014 3867 Visualize processes 10.8 Communicating with PLCs Optimizing the configuration Acquisition cycle and update time The acquisition cycles for the "Area pointers" and of the tags defined in the configuration software are decisive in terms of the update times which can actually be achieved. The update time is equivalent to the acquisition cycle + transmission time + processing time. Items to observe when optimizing the update times in configuration data: Optimize the maximum and minimum size of the data areas. Acquisition cycles which are too short lead to unnecessary load on overall performance. Set the acquisition cycle according to the rate of change of the process values. The rate of temperature changes at a furnace, for example, is significantly slower compared to the speed rate of an electrical drive. A time of approx. 1 second is a benchmark for the acquisition cycle. Avoid any gaps when entering the alarm or screen tags in a data area. Changes in the PLC can only be detected reliably if these are available at least within the actual acquisition cycle. Screens The refresh rate of screens is determined by the type and volume of data to be visualized. Only configure short acquisition cycles for objects which actually require shorter refresh cycles. This procedure reduces update times. Trends The HMI device always updates all bit-triggered trends whose group bit is set in the "Trend transfer area". It resets the bits in the next cycle. The group bit in the PLC program can only be set again after the HMI device has reset all bits. Job mailboxes A high rate and volume of job mailboxes transferred may lead to overload in communication between the HMI device and the PLC. The HMI device confirms acceptance of the job mailbox by entering the value zero in the first data word of the job mailbox. The HMI device now processes the job for which it requires a certain time slice. It may take the HMI device some time to process a new job mailbox which is transferred in immediate succession to the job mailbox. The next job mailbox is only accepted if sufficient computing resources are available. 3868 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs Allen-Bradley DF1 Configuring a connection via Allen-Bradley DF1 Introduction You configure a connection to a PLC with an Allen-Bradley DF1 communication driver in the "Connections" editor of the HMI device. The interfaces are named differently depending on the HMI device. Requirements A project is open. An HMI device has been created. Procedure 1. Double-click the HMI device under "Devices" in the project tree. 2. Double-click the "Connections" item. 3. Double-click "<Add>" in the "Connections" editor. WinCC Basic V13.0 System Manual, 02/2014 3869 Visualize processes 10.8 Communicating with PLCs 4. In the "Communication drivers" column, select the "Allen-Bradley DF1" driver. 5. Select all necessary connection parameters for the interface in the Inspector window under "Parameters". Parameters for the connection (Allen-Bradley DF1) Parameters to be set To set the connection parameters, such as addresses and profiles, click the connection that you have created in the "Connections" editor. The communication partners are displayed schematically in the Inspector window under "Parameters". The "HMI device", "Network", and "PLC" areas are available for assigning parameters according to the interface used. 3870 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs Parameters for the HMI device Interface Under "Interface", you select the interface of the HMI device to which the PLC is connected. For additional information, refer to the device manual for the HMI device. Type Specifies the physical connection used. Note If you are using the IF1B interface, you must also reconnect the RS-485 receive data and the RTS signal to the rear of the HMI devices via 4 DIP switches. Baud rate For "Baud rate", select the transmission speed between the HMI device and PLC. Data bits For "Data bits", you can choose between "7 bits" and "8 bits". Parity For "Parity", you can choose from "None", "Even", and "Odd". Stop bits For "Stop bits", you can choose between 1 and 2 bits. WinCC Basic V13.0 System Manual, 02/2014 3871 Visualize processes 10.8 Communicating with PLCs Parameters for the network Checksum For "Checksum", choose the method for determining the error code: "BCC" or "CRC". Parameters for the PLC Destination address For "Destination address", choose the PLC address. If there is a point-to-point DF1 connection, you set the address "0". CPU type For "CPU type", set the CPU type of the PLC used. Note Assign the DF1 FULL-DUPLEX driver in the CPU as follows: "NO HANDSHAKING" for "Control Line" and "AUTO-DETECT" for "Embedded Responses". Connecting HMI device to PLC Connections via Allen-Bradley DF1 Connection The connection is established when you have matched the parameters of the PLC and the HMI device. Special blocks for the connection are not required in the PLC. Note Rockwell offers a variety of communication adapters for integrating "DF1 devices" for the DH485, DH, and DH+ networks. Of these connections, the direct connection and the connection via KF2 and KF3 module are approved. None of the other connections have been system-tested by SIEMENS AG and are therefore not approved. 3872 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs Communication partners for Allen-Bradley DF1 Connectable PLCs The communication drivers listed below support Allen-Bradley PLCs: : DF1 (point-to-point) DF1 (point-to-point) RS-232 RS-422 DF1 (multipoint) over KF2 module to DH+ LAN RS-232/RS-422 SLC500 - - - X SLC501 - - - X SLC502 - - - X SLC503 X - - X SLC504 X - X X SLC505 X - - X MicroLogix X - - X PLC-5 X X X - PLC 1) DF1 (multipoint) over KF3 module to DH485 LAN RS-232 1) Processors released for PLC-5: PLC-5/11, PLC-5/20, PLC-5/30, PLC-5/40, PLC-5/60, and PLC-5/80. Communication types PLCs with Allen-Bradley DF1 communication driver The communication between the HMI device and the following Allen Bradley PLCs is described in this section: SLC500 SLC501 SLC502 SLC503 SLC504 SLC505 PLC5 MicroLogix In these PLCs the connection is made by the PLC-internal protocols Allen Bradley DF1, Allen Bradley DH485 and Allen Bradley DH+. The Allen-Bradley DF1 communication driver is used here, the protocol of which is converted into one of the other two PLC-internal protocols in multipoint communication with the communication modules KF2 (Allen Bradley DH+) and KF3(Allen Bradley DH485). WinCC Basic V13.0 System Manual, 02/2014 3873 Visualize processes 10.8 Communicating with PLCs Enabled types of communication with Allen-Bradley DF1 The following communication types are system-tested and enabled: HMI (Allen Bradley DF1) Point-to-point connection HMI (Allen Bradley DF1) Via KF2 module to Allen Bradley DH+ (communication with up to 4 PLCs) HMI (Allen Bradley DF1) Via KF3 module to Allen Bradley DH485 (communication with up to 4 PLCs) Connectable PLCs The Allen Bradley DF1 communication driver is available for the following Allen-Bradley PLCs: PLC SLC500 DF1 (point-to-point) DF1 (point-to-point) RS 422 DF1 (multipoint) via KF2 module to DH+ LAN RS 232/RS 422 DF1 (multipoint) via KF3 module to DH485 LAN RS 232 2) RS 232 - - - X SLC501 - - - X SLC502 - - - X - - X X SLC503 X 2) SLC504 X 2) - X SLC505 X 2) - - X MicroLogix X 2) - - X X X X - PLC-5 1) 1) 2) 3874 Only the following processors are approved for PLC-5: PLC-5/11, PLC-5/20, PLC-5/30, PLC-5/40, PLC-5/60 und PLC-5/80. For HMI devices which only have an RS 422/485 interface and the communication partner is an RS 232 interface, the RS 422/232 converter is tested and approved. Order number: 6AV6 671-8XE00-0AX0 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs DF1 protocol with multi-point connection Point-to-point connection with DF1 protocol Only point-to-point connections can be established with the DF1 protocol. +0, ') 5656{ 3LQ6XE' &KDQQHO 3LQ6XE' 3/& 3/&[ +0, ') +0, 56 3LQ6XE' ') &KDQQHO 3LQ6XE' 3/& 56 3LQ6XE' &KDQQHOu 3LQ0LQL',1 3/& 6/&6/&t 6/& 0LFUR/RJL[ 1) Only RS 232 is possible for Panel PC and PC. 2) A point-to-point connection to the SLC500, SLC501, and SLC502 PLCs via DF1 is not possible. 3) For MicroLogix ML1500 LRP, Channel 1 (9-pin Sub D) is also possible. Connecting cable HMI panel interface used For connection to PLC5x For connection to SLC5/03, SLC5/04, SLC5/05 For connection to MicroLogix RS 232 9-pin Allen-Bradley cable 1784-CP10 Allen-Bradley cable 1747-CP3 Allen-Bradley cable 1761-CBL-PM02 RS 422 9-pin Connecting cable 9-pin Sub D RS 422 -- -- Refer to the relevant device manual to determine which HMI device interface is to be used. The cable pin assignments can be found in Section "Connecting cables for Allen-Bradley". WinCC Basic V13.0 System Manual, 02/2014 3875 Visualize processes 10.8 Communicating with PLCs DF1 protocol with multi-point connection via KF2 module DF1 protocol with multi-point connection via KF2 module to DH+ LAN The use of a KF2 protocol interface module enables a connection to be made to PLCs in the DH+ LAN (Data Highway Plus Local Area Network). +0, 5656 3LQ6XE' 3/&[ 3/&[ H[FHSW3/& 6/& 3/& 3/& 3/& &KDQQHO$ 3LQ3KRHQL[ &KDQQHO% 3LQ0LQL'LQ ') 56 &KDQQHO 3LQ0LQL'LQ RU 3LQ3KRHQL[ 3LQ6XE' .) '+ 'DWD+LJKZD\3OXV Connecting cable HMI panel interface used For connection to KF2 interface module RS 232 9-pin Allen-Bradley cable 1784-CP10 and 25-pin socket/socket adapter RS 422 9-pin 9-pin Sub D RS 422 connecting cable and 25-pin female/female adapter Refer to the Allen-Bradley documentation for the cable connection from the PLCs to the DH+ data bus. Refer to the relevant device manual to determine which HMI device interface is to be used. The cable pin assignments can be found in Section "Connecting cables for Allen-Bradley". 3876 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs DF1 protocol with multi-point connection via KF3 module DF1 protocol with multi-point connection via KF3 module to DH485 LAN 6/&6/& 6/&6/& +0, 0LFUR/RJL[ 3/& 3/& 3/& 56 3LQ6XE' ') 56 6/&6/& 6/& &KDQQHO 3LQ5- '+ 56 3LQ6XE' '+ 56 3LQ$036'/ .) &KDQQHO{ 3LQ0LQL',1 &KDQQHO 3LQ6XE' $,& '+ 56 3LQ6XE' $,& 3LQ6XE' $,& '+ 56 1) For MicroLogix ML1500 LRP, Channel 1 (9-pin Sub D) is also possible. Connecting cable HMI panel interface used For connection to KF3 interface module RS 232 9-pin Allen-Bradley cable 1784-CP10 and 25-pin socket/socket adapter Refer to the relevant device manual to determine which HMI device interface is to be used. The cable pin assignments can be found in Section "Connecting cables for Allen-Bradley". Connecting cables for Allen-Bradley DF1 Connecting cable 9-pin Sub D RS 422 for Allen-Bradley Connecting cable 9-pin Sub D RS 422 For interconnecting the HMI device (RS 422, 9-pin sub D) - PLC5x, KF2, KF3 You require an additional 25-pin, female / female adapter (gender changer) for interconnections with KF2 and KF3. WinCC Basic V13.0 System Manual, 02/2014 3877 Visualize processes 10.8 Communicating with PLCs +0,GHYLFH FRQQHFWRU SLQ'6XEFRQQHFWRU VFUHZORFNLQJ FDEOHRXWOHWWRWKHUHDU $OOHQ%UDGOH\ FRQQHFWRU SLQ'6XEFRQQHFWRU VFUHZORFNLQJ FDEOHRXWOHWWRWKHUHDU HQFORVXUH 7[' 5[' 7[' 5[' 5[' 7[' 5[' 7[' *1' *1' Shield with large-area contact to housing at both ends, interconnected shield contacts Cable: 3 x 2 x 0.14 mm2, shielded, max. length 60 m Connecting cable 1784-CP10, RS 232, for Allen-Bradley Allen-Bradley cable 1784-CP10 For interconnecting the HMI device (RS 232, 9-pin sub D) - PLC5x, KF2, KF3 You require an additional 25-pin, female / female adapter (gender changer) for interconnections with KF2 and KF3. 3878 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs +0,GHYLFH FRQQHFWRU SLQ'6XEIHPDOHFRQQHFWRU VFUHZORFNLQJ FDEOHRXWOHWWRWKHUHDU $OOHQ%UDGOH\ FRQQHFWRU SLQ'6XEFRQQHFWRU VFUHZORFNLQJ FDEOHRXWOHWWRWKHUHDU HQFORVXUH '&' '75 '65 '65 '75 5[' 7[' 7[' 5[' *1' *1' &76 576 576 &76 Screen connected with housing over large area on both sides max. length 15 m Connecting cable 1747-CP3, RS-232, for Allen-Bradley Allen-Bradley cable 1747-CP3 For interconnecting the HMI device (RS 232, 9-pin sub D) - SLC503, SLC504, SLC505 (Channel 0), AIC+ WinCC Basic V13.0 System Manual, 02/2014 3879 Visualize processes 10.8 Communicating with PLCs +0,GHYLFH FRQQHFWRU SLQ'6XEIHPDOHFRQQHFWRU VFUHZORFNLQJ FDEOHRXWOHWWRWKHUHDU $OOHQ%UDGOH\ FRQQHFWRU SLQ'6XEIHPDOHFRQQHFWRU VFUHZORFNLQJ FDEOHRXWOHWWRWKHUHDU HQFORVXUH '75 '&' '65 '65 '&' '75 5[' 7[' 7[' 5[' *1' *1' &76 576 576 &76 Screen connected with housing over large area on both sides max. length 3 m Connecting cable 1761-CBL-PM02, RS-232, for Allen-Bradley Allen-Bradley cable 1761-CBL-PM02 For interconnecting the HMI device (RS 232, 9-pin sub D) - Micro Logix, AIC+ 3880 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs +0,GHYLFH $OOHQ%UDGOH\ FRQQHFWRU SLQ'6XEIHPDOHFRQQHFWRU VFUHZORFNLQJ FDEOHRXWOHWWRWKHUHDU FRQQHFWRU SLQPLQL',1FRQQHFWRU FDEOHRXWOHWWRWKHUHDU HQFORVXUH '&' '&' 5[' 7[' 7[' 5[' *1' *1' &76 576 576 &76 Screen connected with housing over large area on both sides max. length 15 m Performance features of communication Permitted data types for Allen-Bradley DF1 Permitted data types for Allen-Bradley DF1 The table lists the user data types that can be used when configuring tags and area pointers. Data type Operand type Length ASCII A 1 to 80 characters Bool N, R, C, T, B, S, I, O 1 bit Int N, R, C, T, S 2 bytes DInt N, D UInt N, R, C, T, B, I, O, D UDInt N, D 2) 4 bytes Real N, F 1) 4 bytes WinCC Basic V13.0 System Manual, 02/2014 1) 4 bytes 2) 2) 2 bytes 3881 Visualize processes 10.8 Communicating with PLCs 1) 2) Selectable depending on the selected CPU type. Only for PLC5 CPU type Abbreviations In WinCC, formats of the data types are abbreviated as follows: UNSIGNED INT = UInt UNSIGNED LONG = UDInt SIGNED INT = Int SIGNED LONG = DInt Distinctive features for connections with Allen-Bradley DF1 With Allen Bradley DF1, array tags may only be used for discrete alarms and trends. Note I/O modules with 8 or 16 ports occupy one data word on the PLC. I/O modules with 24 or 32 ports occupy two data words. The HMI device does not output an error message if using non-existent bits. You should always make sure that I/O modules with 8 or 24 ports only occupy the bits that are actually assigned to a port. 3882 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs Supported CPU types for Allen-Bradley DF1 CPU types The following CPU types are supported for configuring the Allen-Bradley DF1 communication driver. SLC - SLC500 - SLC501 - SLC502 - SLC503 - SLC504 - SLC505 MicroLogix - MicroLogix 1x00 - MicroLogix 1100 / 1400 PLC 5 - PLC-5/11 - PLC-5/20 - PLC-5/40 - PLC-5/60 - PLC-5/80 Addressing Addressing The addressing is entered in the following order in the Allen-Bradley DF1 communication driver: Operand type File number Element number WinCC Basic V13.0 System Manual, 02/2014 3883 Visualize processes 10.8 Communicating with PLCs Child element Bit number The address then appears in the following format without spaces: File type file number : Element number . Child element e.g. T8:2.ACC Operand type You have the following options under operand type: I O S B T C R N A D only for PLC5 CPU type File number Select the number between two limits under file number: Low limit High limit 3884 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs The limit values depend on the selected file type. Child element You can select a child element when you have selected one of the following data types: R C T Address areas for Allen Bradley DF1 MicroLogix Address areas Data types Bool Int UInt DInt UDInt Real N N7:0/0 N255:255/15 N7:0 N255:255 N7:0 N255:255 N7:0 N255:254 N7:0 N255:254 N7:0 N255:254 F -- -- -- -- F8:0 F255:255 -- R R6:0.EN R255:255.ER R255:255.DN R255:255.FD R255:255.IN R255:255.EU R255:255.EM R255:255.UL R6:0.LEN R255:255.POS R6:0.LEN R255:255.POS -- -- -- C C5:0.CU C255:255.CD C255:255.DN C255:255.OV C255:255.UN C5:0.PRE C255:255.ACC C5:0.PRE C255:255.ACC -- -- -- T T4:0.DN T255:255.TT T255:255.EN T4:0.PRE T255:255.ACC T4:0.PRE T255:255.ACC -- -- -- B B3:0/0 B255:255/15 -- B3:0 B255:255 -- -- -- S S2:0/0 S2:65/15 S2:0 S2:65 -- -- -- -- I I0:0/0 I38:255/15 -- I0:0 I38:255 -- -- -- O O0:0/0 O38:255/15 -- O0:0/0 O38:255 -- -- -- WinCC Basic V13.0 System Manual, 02/2014 3885 Visualize processes 10.8 Communicating with PLCs SLC500 Address areas Data types Bool Int UInt DInt UDInt Real N N7:0/0 N255:255/15 N7:0 N255:255 N7:0 N255:255 N7:0 N255:254 N7:0 N255:254 N7:0 N255:254 R R6:0.EN R255:255.ER R255:255.DN R255:255.FD R255:255.IN R255:255.EU R255:255.EM R255:255.UL R6:0.LEN R255:255.POS R6:0.LEN R255:255.POS -- -- -- C C5:0.CU C255:255.CD C255:255.DN C255:255.OV C255:255.UN C5:0.PRE C255:255.ACC C5:0.PRE C255:255.ACC -- -- -- T T4:0.DN T255:255.TT T255:255.EN T4:0.PRE T255:255.ACC T4:0.PRE T255:255.ACC -- -- -- B B3:0/0 B255:255/15 -- B3:0 B255:255 -- -- -- S S2:0/0 S2:15/15 S2:0 S2:15 -- -- -- -- I I0:0/0 I38:255/15 -- I0:0 I38:255 -- -- -- O O0:0/0 O38:255/15 -- O0:0 O38:255 -- -- -- SLC501/502 Address areas Data types Bool Int UInt DInt UDInt Real N N7:0/0 N255:255/15 N7:0 N255:255 N7:0 N255:255 N7:0 N255:254 N7:0 N255:254 N7:0 N255:254 R R6:0.EN R255:255.ER R255:255.DN R255:255.FD R255:255.IN R255:255.EU R255:255.EM R255:255.UL R6:0.LEN R255:255.POS R6:0.LEN R255:255.POS -- -- -- 3886 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs Address areas Data types Bool Int UInt DInt UDInt Real C C5:0.CU C255:255.CD C255:255.DN C255:255.OV C255:255.UN C5:0.PRE C255:255.ACC C5:0.PRE C255:255.ACC -- -- -- T T4:0.DN T255:255.TT T255:255.EN T4:0.PRE T255:255.ACC T4:0.PRE T255:255.ACC -- -- -- B B3:0/0 B255:255/15 -- B3:0 B255:255 -- -- -- S S2:0/0 S2:32/15 S2:0 S2:32 -- -- -- -- I I0:0/0 I38:255/15 -- I0:0 I38:255 -- -- -- O O0:0/0 O38:255/15 -- O0:0 O38:255 -- -- -- PLC5 Address areas Data types Bool Int UInt DInt UDInt Real ASCII N N3:0/0 N999:999/15 N3:0 N999:999 N3:0 N999:999 N3:0 N999:999 N3:0 N999:998 N3:0 N999:998 -- F -- -- -- -- -- F3:0 F999:999 -- A -- -- -- -- -- -- A3:0 A999:999 R R3:0.EN R3:0.LEN R3:0.LEN -R999:999.ER R999:999.PO R999:999.PO S S R999:999.DN R999:999.FD R999:999.IN R999:999.EU R999:999.EM R999:999.UL -- -- -- WinCC Basic V13.0 System Manual, 02/2014 3887 Visualize processes 10.8 Communicating with PLCs Address areas Data types Bool Int UInt DInt UDInt Real ASCII C C3:0.CU C3:0.PRE C3:0.PRE -C999:999.CD C999:999.AC C999:999.AC C C C999:999.DN C999:999.OV C999:999.UN -- -- -- T T3:0.DN T999:999.TT T999:999.EN T3:0.PRE T999:999.AC C T3:0.PRE T999:999.AC C -- -- -- -- B B3:0/0 B999:999/15 -- B3:0 B999:999 -- -- -- -- S S2:0/0 S2:127/15 S2:0 S2:127 -- -- -- -- -- I I1:0/0 I1:277/17 -- I1:0 I1:277 -- -- -- -- O O0:0/0 O0:277/17 -- O0:0 O0:277 -- -- -- -- D D3:0/0 D999:999/15 D3:0 D999:999 D3:0 D999:999 -- D3:0 D999:998 -- -- Commissioning components Transferring a project to the HMI device 1. Switch the HMI device to "transfer mode". 2. Set all necessary transfer parameters. - Interface - Transfer parameters - Target storage location 3. Start the project transfer. The project is compiled automatically. All compilation and transfer steps are logged to a message window. Interconnecting the PLC with the HMI device 1. Interconnect the PLC with the HMI device using a suitable cable. 2. The message "Connection to PLC .... is established" is output to the HMI device. 3888 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs Optimizing the configuration Acquisition cycle and update time The acquisition cycles for the "Area pointers" and of the tags defined in the configuration software are decisive in terms of the update times which can actually be achieved. The update time is equivalent to the acquisition cycle + transmission time + processing time. Items to observe when optimizing the update times in configuration data: Optimize the maximum and minimum size of the data areas. Acquisition cycles which are too short lead to unnecessary load on overall performance. Set the acquisition cycle according to the rate of change of the process values. The rate of temperature changes at a furnace, for example, is significantly slower compared to the speed rate of an electrical drive. A time of approx. 1 second is a benchmark for the acquisition cycle. Avoid any gaps when entering the alarm or screen tags in a data area. Changes in the PLC can only be detected reliably if these are available at least within the actual acquisition cycle. Screens The refresh rate of screens is determined by the type and volume of data to be visualized. Only configure short acquisition cycles for objects which actually require shorter refresh cycles. This procedure reduces update times. Trends The HMI device always updates all bit-triggered trends whose group bit is set in the "Trend transfer area". It resets the bits in the next cycle. The group bit in the PLC program can only be set again after the HMI device has reset all bits. Job mailboxes A high rate and volume of job mailboxes transferred may lead to overload in communication between the HMI device and the PLC. The HMI device confirms acceptance of the job mailbox by entering the value zero in the first data word of the job mailbox. The HMI device now processes the job for which it requires a certain time slice. It may take the HMI device some time to process a new job mailbox which is transferred in immediate succession to the job mailbox. The next job mailbox is only accepted if sufficient computing resources are available. WinCC Basic V13.0 System Manual, 02/2014 3889 Visualize processes 10.8 Communicating with PLCs Data exchange Area pointers for Allen-Bradley Area pointers for connections using an Allen-Bradley communication driver You use an area pointer to access a data area in the PLC. For more detailed information on area pointers and their configuration, refer to Section "Data exchange using area pointers". Distinctive features for connections via Allen-Bradley EtherNet/IP You can configure the following area pointers Area pointer Allen-Bradley EtherNet/IP Allen-Bradley DF1 Screen number Yes Yes Date/time Yes Yes Date/time PLC Yes Yes Coordination Yes Yes Project ID Yes Yes Job mailbox Yes Yes Data record Yes Yes Restrictions Allen-Bradley Ethernet/IP The following restrictions apply for configuring area pointers. CPU type Data types File types ControlLogix,CompactLogix Int, UInt -- SLC, MicroLogix Int, UInt N, B Restrictions Allen-Bradley DF1 The following restrictions apply for configuring area pointers. 3890 CPU type Data types File types MicroLogix -- N, O, I, B SLC50x -- N, O, I, B PLC5 -- N, O, I, B WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs See also Data exchange using area pointers (Page 3967) Trends Trends A trend is the graphical representation of one or more values from the PLC. The value is read out time-triggered for Basic Panels. For additional information see: Configuring trend displays for values from the PLC (Page 3369) Time-triggered trends The HMI device reads in the trend values cyclically at an interval specified in the configuration. Time-triggered trends are suitable for continuous curves, such as the operating temperature of a motor. Alarms Configuring alarms Configuring alarms for non-integrated connections Several steps are necessary to configure alarms such as warnings, error messages and acknowledgement. Step 1: Create tags Step 2: Configure alarms Step 3: Configure acknowledgment You can find additional information in the section: Working with alarms (Page 3379) Distinctive features when configuring alarms If you are configuring connections of HMI devices to PLCs of other manufacturers, note the following distinctive features when configuring: Data types of the tags Addressing of tags How the bit positions are counted WinCC Basic V13.0 System Manual, 02/2014 3891 Visualize processes 10.8 Communicating with PLCs Restrictions Only tags whose "File type" is "N", "O", "I", "S" and "B" are allowed for use as a "trigger tag" for discrete alarms. These tags are only valid for the data types "Int" and "UInt". Data types For connections with an Allen-Bradley communication driver, the following data types are supported: Communication drivers PLC Permitted data types Discrete alarms Analog alarms Allen-Bradley DF1 SLC500, SLC501, SLC502, SLC503, SLC504, SLC505, PLC5, MicroLogix Int, UInt Int, UInt, Long, ULong, Real Allen-Bradley EtherNet/IP ControlLogix, CompactLogix, SLC, Micrologix Int, UInt SInt, USInt, Int, UInt, DInt, UDInt, Real How the bit positions are counted For connections with an Allen-Bradley communication driver, the following counting method applies: How the bit positions are counted Left byte Right byte In Allen-Bradley PLCs 15 8 7 0 In WinCC you configure: 15 8 7 0 See also Alarm system in WinCC (Page 3370) Acknowledgment of alarms Procedure Create suitable tags on the PLC to acknowledge an error alarm. You assign these tags to an alarm in the "Bit messages" editor. You make the assignment in "Properties > Acknowledgment". Distinction in terms of acknowledgment: Acknowledgment by the PLC Acknowledgment on the HMI device 3892 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs Acknowledgment by the PLC In "PLC acknowledgment tag", configure the tag or array tag and the bit number that the HMI device uses to identify a PLC acknowledgment. A bit set in the tag triggers acknowledgment of the assigned error alarm bit at the HMI device. This tag bit returns a function similar to acknowledgment on the HMI device which is triggered by pressing the "ACK" button, for example. The acknowledgment bit must be located in the same tag as the bit for the error alarm. Reset the acknowledgment bit before setting the bit in the alarm area again. The figure below shows the pulse diagram. (UURUDODUP $FNQRZOHGJPHQW 3/&+0,GHYLFH $UULYDORIWKH $FNQRZOHGJP 5HVHWRI HUURUDODUP YLD3/& DFNQRZOHGJPELW 1HZ HUURUDODUP Acknowledgment on the HMI device In the "HMI acknowledgment tag" area, configure the tag or array tag as well as the bit number that the HMI device writes to the PLC after acknowledgment. Make sure when you use an array tag that it is not longer than 6 words. To always create a signal change when setting an assigned acknowledgment bit of a discrete alarm that must be acknowledged, the HMI device will reset the acknowledgment bit assigned to the alarm as soon as it detects an alarm subject to acknowledgment and write the acknowledgment tag in the PLC. There will be a certain delay between detecting the message and writing the acknowledgment tag in the PLC because the HMI device has to process the operations. If a discrete alarm subject to acknowledgment is acknowledged by the HMI device, then the corresponding bit in the assigned acknowledgment tag will be set. The entire acknowledgment tag is then written to the PLC by the HMI device. This allows the PLC to recognize that a certain alarm message has been acknowledged at the HMI device. Note All alarm bits acknowledged since the last Runtime start will remain in the acknowledgment tag until a new incoming of the respective discrete alarms is detected. This area should only be read by the PLC because the entire section of the HMI device will be overwritten once the next acknowledgment tag is written. The figure below shows the pulse diagram. WinCC Basic V13.0 System Manual, 02/2014 3893 Visualize processes 10.8 Communicating with PLCs (UURUDODUP $FNQRZOHGJPHQW +0,GHYLFH3/& $UULYDORIWKH HUURUDODUP 5HVHWRI DFNQRZOHGJPELW $FNQRZOHGJP YLD+0,GHYLFH 1HZ HUURUDODUP Mitsubishi Mitsubishi communication drivers Introduction This section describes the communication between an HMI device and PLCs that use Mitsubishi communication drivers. The following communication drivers are supported: Mitsubishi MC TCP/IP Mitsubishi FX Data exchange Data is exchanged by means of tags or area pointers. Tags The PLC and the HMI device use process values for data exchange. You create tags in the configuration that point to addresses in the PLC. The HMI device reads the value from the defined address, and then displays it. The operator may also enter values on the HMI device, which are then written to the address in the PLC. Area pointers Area pointers are used to exchange specific data and are only set up when these data are used. Mitsubishi MC TCP/IP Configuring a connection via Mitsubishi MC TCP/IP Introduction You configure a connection to a PLC with a Mitsubishi MC TCPI/IP communication driver in the "Connections" editor of the HMI device. 3894 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs The Ethernet interfaces are named differently depending on the HMI device. Example: PROFINET interface corresponds to the Ethernet interface Requirements A project is open. An HMI device has been created. Procedure 1. Double-click the HMI device under "Devices" in the project tree. 2. Double-click the "Connections" item. 3. Double-click "<Add>" in the "Connections" editor. WinCC Basic V13.0 System Manual, 02/2014 3895 Visualize processes 10.8 Communicating with PLCs 4. In the "Communication drivers" column, select the "Mitsubishi MC TCPI/IP" driver. 5. Select all necessary connection parameters for the interface in the Inspector window under "Parameters". Parameters for the connection (Mitsubishi MC TCP/IP) Parameters to be set To set the connection parameters, such as addresses and profiles, click the connection that you have created in the "Connections" editor. The communication partners are displayed schematically in the Inspector window under "Parameters". The "HMI device" and "PLC" areas are available for assigning parameters according to the interface used. 3896 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs Parameters for the HMI device You can select only one interface for the HMI device in the Inspector window under "Parameters". Depending on the HMI device, there are several interfaces available. If you are directly connected to the HMI device during configuration, you can set up the IP address of the HMI device in WinCC. The IP address is transferred to the HMI device during project transfer. Note The IP address in the control panel will be overwritten upon subsequent loading if you have already set up the IP address in the HMI device control panel. The IP address already set up in the control panel will be retained upon subsequent loading if you activate "Set IP address using a different method". To set up the IP address of the HMI device: 1. Click on the HMI device. 2. Open the "Device configuration" editor. WinCC Basic V13.0 System Manual, 02/2014 3897 Visualize processes 10.8 Communicating with PLCs 3. Click the Ethernet interface. 4. Assign the IP address in the inspector window under: "General > PROFINET interface > Ethernet addresses" Parameters for the PLC CPU type For "CPU type", you set the type of PLC to which the HMI device is connected. The following settings are possible: -FX3 -Q If you select the FX3 CPU type, the Mitsubishi MC protocol "1E" is used and "3E" for the "Q" CPU type. The "Binary code" protocol variant is always used. Note If the CPU type is changed for a configured connection, tags with the following properties must be revised: * Operands that do not exist for the new CPU type, such as "W", "B", "F". * Inputs and outputs with different addressing (hexadecimal/octal) * Addresses greater than the valid address area of the new CPU type IP address Set the IP address or host name of the Ethernet/IP module of the PLC. Only the IP address can be used on a Basic Panel. Port Set the port number of the module of the PLC. Connecting HMI device to PLC Connections via Mitsubishi MC TCP/IP Connection The HMI device can be connected to the Mitsubishi PLC using the following components: Existing Ethernet network that also contains the PLCs Cross-over Ethernet cable connected directly to the Ethernet interface of the CPU or the communication module The connection of the HMI device to a Mitsubishi PLC is limited primarily to the physical connection of the HMI device. Special blocks for the connection are not required in the PLC. Connect the HMI device to one or several Q-series and/or FX3 PLCs. Connect the HMI device via the following interfaces: 3898 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs Communication interface OnBoard Approved communication module suitable for the PLC Note Timeout response with TCP/IP (Ethernet) Due to the use of the TCP/IP protocol, the breakdown of a connection is detected at the earliest after approximately one minute. Communication failure cannot be reliably detected if no tags are requested, for example, no output tags in the current screen. Configure area pointer coordination for each PLC. This setting ensures that a communication failure is recognized after approximately two minutes, even in the aforementioned scenario. Communication types Approved communication types Only applies for Mitsubishi FX(PG protocol): The point-to-point connection from a HMI device to an approved Mitsubishi FX-CPU via Mitsubishi FX is system-tested and approved by Siemens AG. Only applies for Mitsubishi MC TCP/IP: The following communication types are system-tested and approved: - Point-to-point connection to the approved PLCs - Multipoint connection from a HMI device with up to 4 PLCs with the respectively approved PLCs. CPU types (FX3 and Q) can be mixed. Note The HMI device is a client and the PLC must operate as a server. WinCC Basic V13.0 System Manual, 02/2014 3899 Visualize processes 10.8 Communicating with PLCs Connectable PLCs Connections can be implemented for the following Mitsubishi PLCs: Mitsubishi FX Mitsubishi MC TCP/IP (PG protocol) PLC MELSEC FX1n, FX2n Yes No MELSEC FX3U, FX3UC, FX3G with communication module FX3U-ENET No Yes MELSEC System Q No Yes Q-series with the communication module QJ71E71-100 QnUDEH CPU with Ethernet interface onboard Parameterization of the communications modules FX3 PLCs Procedure 1. Start the FX-Configurator. 2. Select the module. 3. Assign the following settings in the "Operational settings" dialog: - Communication data code: Binary code - Initial timing: Always wait for OPEN - IP address: IP address - Send frame setting: Ethernet(V2.0) - TCP Existence confirmation setting: Use the Ping 3900 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs 4. Assign the following settings in the "Open Settings" dialog: - Protocol: TCP - Open system: Unpassive - Fixed buffer: Receive - Fixed buffer communication procedure: Procedure exist(MC) - Pairing open Disable - Existence confirmation No confirm - Host station Port No. (DEC) Port number Note The port number chosen in the communication module must match the port number in WinCC. A connection with a port number must be assigned for each connected HMI device. You must specify port numbers in decimal values. 5. Confirm the default settings of the other dialog boxes. The network no. and station no. parameters are not relevant for the connection and can be chosen as required. Q PLCs Procedure 1. Click "Edit network parameters". 2. Select the network type: - Ethernet The network number and the group / station number are not evaluated and can be freely assigned WinCC Basic V13.0 System Manual, 02/2014 3901 Visualize processes 10.8 Communicating with PLCs 3. Assign the following settings in the "Operational settings" dialog: - Communication data code: Binary code - Initial timing: Always wait for OPEN - IP address: IP address - Send frame setting: Ethernet(V2.0) - Enable write operations during RUN 4. Assign the following settings in the "Open settings" dialog: - Protocol: TCP - Open system: Unpassive - Pairing open Disable - Existence confirmation No confirm - Host station Port No. (HEX) Port-Nummer Note The port number chosen in the communication module must match the port number in WinCC. A connection with a port number must be assigned for each connected HMI device. You must specify port numbers in hexadecimal values. 3902 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs Internal Ethernet port of the Q0xUDEH CPU Procedure 1. Assign the following settings in the "Internal Ethernet Port" dialog: - IP address: IP address - Communication data code: Binary code - Enable online changes 2. Assign the following settings in the "Open settings" dialog: - Protocol: TCP - Open system: MC-Protocol - Host station Port No. (HEX) Port number Note The port number chosen in the communication module must match the port number in WinCC. A connection with a port number must be assigned for each connected HMI device. Performance features of communication Permitted data types for Mitsubishi MC TCPI/IP Permitted data types The table lists the data types that can be used when configuring tags and area pointers. Data type Operand type Length 4-bit block M, X, Y, B, F 1 byte 8-bit block M, X, Y B, F 1 byte 12-bit block M, X, Y B, F 2 bytes 16-bit block M, X, Y B, F 2 bytes 20-bit block M, X, Y B, F 4 bytes 24-bit block M, X, Y B, F 4 bytes 28-bit block M, X, Y B, F 4 bytes 32-bit block M, X, Y B, F 4 bytes Bool M, D, X, Y B, F 1-bit WinCC Basic V13.0 System Manual, 02/2014 3903 Visualize processes 10.8 Communicating with PLCs Data type Operand type Length DInt D, W 4 bytes DWord D, C, W 4 bytes Int D, W 2 bytes Real 1) D, W 4 bytes String 1) D 1 to 80 characters Word D, T, C, W 2 bytes 1) 2) The "String" and "Real" data types are not available for all CPUs. Operand types B, F and W are only available for CPU type "Q". Note Note the following for write accesses: Tags can only be written if "Enable online changes" or "Enable write operations during RUN" was selected when parameterizing the Mitsubishi communication modules. For data type "Bool" in operand type "D", the entire word is written back to the PLC following a change to the specified bit. There is no check to determine whether any other bits in the word have changed. As a result, the PLC only has read access to the specified word. Note Array elements in I/O fields cannot be used in communication with a Mitsubishi PLC. Supported CPU types for Mitsubishi MC TCP/IP CPU types The following CPU types are supported for configuring the Mitsubishi MC TCP/IP communication driver. FX3 series - FX 3G / FX 3G with communication modul FX3U-ENET - FX 3U / FX 3U with communication modul FX3U-ENET - FX 3UC / FX 3UC with communication modul FX3U-ENET Q series - Q-Series with QJ71E71-100 communication module iQ series / QnUD - QnUDEHCPU with built in ethernet module 3904 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs Addresses for Mitsubishi MC TCP/IP Address areas for connections via Mitsubishi MC TCP/IP The address area boundaries differ for the different series; refer to the Mitsubishi Computerlink manuals for this information. Examples of address area boundaries dependent on the CPU and communication format: Name Operand type Max. address FX3 Max. address Q-Series Output/Input Y/X Octal X/Y 0 - 777 HEX X/Y 0 - 7FF Bit memory M M0 - M3071 and M8000 - M8255 M/L/S 0 - 8191 Data register D D0 - 7999 D8000 - D8255 D0 - 8191 D9000 - D9255 becomes SD1000 SD1255 Counter C C0 - 255 C0 - 1023 Timer T T0 - 255 T0 - 2047 Link register W -- Hex: W0 - FFF Link flag B -- Hex: B0 - FFF Error flag F -- F0 - 2047 Address areas for Mitsubishi MC TCP/IP FX0 Addres s areas Bool Data types Word DWord Real String 4-bit block 8-bit block 12-bit block 16-bit block 20-bit block 24-bit block 28-bit block 32-bit block M M0 -M9999 -- -- -- M0 M999 6 M0 M999 2 M0 M998 8 M0 M998 4 M0 M0 M0 M0 M9980 M9976 M9972 M996 8 D D0.0 - D0 D999.1 D999 5 D0 D998 D0 D998 D0 D998 -- -- -- -- -- -- -- -- T T0 T255 -- -- -- -- -- -- -- -- -- -- -- C-16-Bit 0 C-16Bit 199 -- -- -- -- -- -- -- -- -- -- C-16Bit -- WinCC Basic V13.0 System Manual, 02/2014 3905 Visualize processes 10.8 Communicating with PLCs Addres s areas Bool Data types Word DWord Real String 4-bit block 8-bit block 12-bit block 16-bit block 20-bit block 24-bit block 28-bit block 32-bit block C-32Bit -- -- C-32-Bit 200 C-32Bit 255 -- -- -- -- -- -- -- -- -- X X0 X255 -- -- -- -- X0 X252 X0 X248 X0 X244 X0 X240 X0 X236 X0 X232 X0 X228 X0 X224 Y Y0 X255 -- -- -- -- Y0 Y252 Y0 Y248 Y0 Y244 Y0 Y240 Y0 Y236 Y0 Y232 Y0 Y228 Y0 Y224 Commissioning components Transferring a project to the HMI device 1. Switch the HMI device to "transfer mode". 2. Set all necessary transfer parameters. - Interface - Transfer parameters - Target storage location 3. Start the project transfer. The project is compiled automatically. All compilation and transfer steps are logged to a message window. Interconnecting the PLC with the HMI device 1. Interconnect the PLC with the HMI device using a suitable cable. 2. The message "Connection to PLC .... is established" is output to the HMI device. Optimizing the configuration Acquisition cycle and update time The acquisition cycles for the "Area pointers" and of the tags defined in the configuration software are decisive in terms of the update times which can actually be achieved. The update time is equivalent to the acquisition cycle + transmission time + processing time. Items to observe when optimizing the update times in configuration data: 3906 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs Optimize the maximum and minimum size of the data areas. Acquisition cycles which are too short lead to unnecessary load on overall performance. Set the acquisition cycle according to the rate of change of the process values. The rate of temperature changes at a furnace, for example, is significantly slower compared to the speed rate of an electrical drive. A time of approx. 1 second is a benchmark for the acquisition cycle. Avoid any gaps when entering the alarm or screen tags in a data area. Changes in the PLC can only be detected reliably if these are available at least within the actual acquisition cycle. Screens The refresh rate of screens is determined by the type and volume of data to be visualized. Only configure short acquisition cycles for objects which actually require shorter refresh cycles. This procedure reduces update times. Trends The HMI device always updates all bit-triggered trends whose group bit is set in the "Trend transfer area". It resets the bits in the next cycle. The group bit in the PLC program can only be set again after the HMI device has reset all bits. Job mailboxes A high rate and volume of job mailboxes transferred may lead to overload in communication between the HMI device and the PLC. The HMI device confirms acceptance of the job mailbox by entering the value zero in the first data word of the job mailbox. The HMI device now processes the job for which it requires a certain time slice. It may take the HMI device some time to process a new job mailbox which is transferred in immediate succession to the job mailbox. The next job mailbox is only accepted if sufficient computing resources are available. Mitsubishi FX Configuring a connection via Mitsubishi FX Introduction You configure a connection to a PLC with a Mitsubishi FX communication driver in the "Connections" editor of the HMI device. The Mitsubishi FX protocol is also referred to as the Mitsubishi PG protocol. The interfaces are named differently depending on the HMI device. WinCC Basic V13.0 System Manual, 02/2014 3907 Visualize processes 10.8 Communicating with PLCs Requirements A project is open. An HMI device has been created. Procedure 1. Double-click the HMI device under "Devices" in the project tree. 2. Double-click the "Connections" item. 3. Double-click "<Add>" in the "Connections" editor. 3908 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs 4. In the "Communication drivers" column, select the "Mitsubishi FX" driver. 5. Select all necessary connection parameters for the interface in the Inspector window under "Parameters". Parameters for the connection (Mitsubishi FX) Parameters to be set To assign the connection parameters, such as addresses and profiles, click the connection that you have created in the "Connections" editor. The communication partners are displayed schematically in the Inspector window under "Parameters". The "HMI device", "Network", and "PLC" areas are available for assigning parameters according to the interface used. WinCC Basic V13.0 System Manual, 02/2014 3909 Visualize processes 10.8 Communicating with PLCs Parameters for the HMI device You can select an interface for the HMI device in the Inspector window under "Parameters". Depending on the HMI device, there are several interfaces available. "Type" Specifies the physical connection used. Note If you use the IF1B interface, you must switch over the RS422 receive data and the RTS signal additionally by 4 DIL-switches on the back of the HMI device. Parameters for the PLC Baud rate: For "Baud rate", select the transmission speed between the HMI device and PLC. Select the baud rate "9600". Data bits: Under "Data bits", select "7 bits". Parity: Under "Parity", select "Even". Stop bits: Under "Stop bits", select "1 bit". 3910 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs Connecting HMI device to PLC Communication types Approved communication types Only applies for Mitsubishi FX(PG protocol): The point-to-point connection from a HMI device to an approved Mitsubishi FX-CPU via Mitsubishi FX (PG protocol := protocol for access to the program and memory elements of the FX series PC CPU version V1.21 and after) is system-tested and approved by Siemens AG. Only applies for Mitsubishi MC TCP/IP: The following communication types are system-tested and approved: - Point-to-point connection to the approved PLCs - Multipoint connection from a HMI device with up to 4 PLCs with the respectively approved PLCs. CPU types (FX3 and Q) can be mixed. Note The HMI device is a client and the PLC must operate as a server. Connectable PLCs Connections can be implemented for the following Mitsubishi PLCs: Mitsubishi FX Mitsubishi MC TCP/IP (PG protocol) PLC MELSEC FX1n, FX2n Yes No MELSEC FX3U, FX3UC, FX3G with communication module FX3U-ENET No Yes MELSEC System Q No Yes Q-series with the communication module QJ71E71-100 QnUDEH CPU with Ethernet interface onboard WinCC Basic V13.0 System Manual, 02/2014 3911 Visualize processes 10.8 Communicating with PLCs Connections via Mitsubishi FX Connection Connect the HMI device to the programming interface of the CPU (RS 422) (see documentation of the PLC). The connection between the HMI device and the Mitsubishi PLC is basically restricted to setting the interface parameters. Special blocks for the connection are not required in the PLC. Connecting cable The following connecting cables are available to connect the HMI device to the PLC. Interface to HMI device or adapter FX1n, Fx2n, Mini DIN, 8-pin Mitsubishi Electric PLC via FX protocol RS 232, 9-pin Mitsubishi SC-09 1) RS 422, 9-pin Connecting cable RS422-2P +0,GHYLFH 0LWVXELVKL Since the Mitsubishi PLCs communicate via RS 422 as a standard, theFRQQHFWRU Mitsubishi programming FRQQHFWRU cable SC-09 with integrated RS 422/RS 232 adaptor is necessary forSLQPLQL',1FRQQHFWRU connecting a HMI device via RS SLQ'6XEFRQQHFWRU 232. VFUHZORFNLQJ VFUHZORFNLQJ 1) FDEOHRXWOHWWRWKHUHDU FDEOHRXWOHWWRWKHUHDU HQFORVXUH Note Applies only to RS 232: 7[' Cable length is restricted to 0.32 m. 5[' 5[' Refer to the relevant device manual to determine which HMI device interface is to be used. *1' *1' The cable pin assignments can be found in Section "Connecting cables for Mitsubishi FX". 7[' Connecting cables for Mitsubishi 5[' FX 5[' Connecting cable RS 422 2P, for Mitsubishi 7[' 7[' Connecting cable RS422-2P Shield with large-area contact to housing at both ends Cable: 3 x 2 x 0.14 mm2, shielded, max. length 500 m 3912 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs Performance features of communication Permitted data types for Mitsubishi FX Permitted data types The table lists the data types that can be used when configuring tags and area pointers. Data type Operand type Length 4-bit block M, X, Y 1 byte 8-bit block M, X, Y 1 byte 12-bit block M, X, Y 2 bytes 16-bit block M, X, Y 2 bytes 20-bit block M, X, Y 4 bytes 24-bit block M, X, Y 4 bytes 28-bit block M, X, Y 4 bytes 32-bit block M, X, Y 4 bytes Bool D, M, X, Y 1-bit DWord D, C-32 bit 4 bytes Real D 4 bytes String D 1 to 50 characters Word D, T, C-16 bit 2 bytes Note Note the following for write accesses: For data type "Bool" in operand type "D", the entire word is written back to the PLC following a change to the specified bit. There is no check to determine whether any other bits in the word have changed. As a result, the PLC only has read access to the specified word. Note Array elements in I/O fields cannot be used in communication with a Mitsubishi PLC. WinCC Basic V13.0 System Manual, 02/2014 3913 Visualize processes 10.8 Communicating with PLCs Supported CPU types for Mitsubishi FX CPU types The following CPU types are supported for configuring the Mitsubishi FX communication driver. FX1 series - FX1n FX2 series - FX2n Address areas for Mitsubishi FX FX3 Addre ss Bool areas Int Word DInt DWor Real d String 4-bit 8-bit 121620-bit block block bit bit block block block 24-bit block 28-bit block 32-bit block M M0 M999 9 -- -- -- -- -- -- M0 M99 96 M0 M99 92 M0 M99 88 M0 M99 84 M0 M998 0 M0 M997 6 M0 M997 2 M0 M996 8 D D0.0 D999 9.15 D0 D999 9 D0 D999 9 D0 D999 9 D0 D999 9 D0 D999 9 D0 D999 9 -- -- -- -- -- -- -- -- T -- -- T0 T999 -- -- -- -- -- -- -- -- -- -- -- -- C -- C0 C999 C0 C999 C0 C998 C0 C998 -- -- -- -- -- -- -- -- -- -- X X0 X777 -- -- -- -- -- -- X0 - X0 - X0 - X0 - X0 X774 X770 X764 X760 X754 X0 X750 X0 X744 X0 X740 Y Y0 Y777 -- -- -- -- -- -- Y0 - Y0 - Y0 - Y0 - Y0 Y774 Y770 Y764 Y760 Y754 Y0 Y750 Y0 Y744 Y0 Y740 3914 Data types WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs Q Addre ss Bool areas Int Word DInt DWor Real d String 4-bit 8-bit 121620-bit block block bit bit block block block 24-bit block 28-bit block 32-bit block M M0 M999 9 -- -- -- -- -- -- M0 M99 96 M0 M998 0 M0 M997 6 M0 M997 2 M0 M996 8 F F0 F999 9 -- -- -- -- -- -- F0 - F0 - F0 - F0 - F0 F999 F999 F998 F998 F998 6 2 8 4 0 F0 F997 6 F0 F997 2 F0 F996 8 B B0 BFFF F -- -- -- -- -- -- B0 BFF FC B0 BFF F8 B0 BFF F4 B0 BFF F0 B0 B0 B0 B0 BFFE BFFE BFFE BFFE C 8 4 0 D D0.0 D655 34.15 D0 D655 34 D0 D655 34 D0 D655 33 D0 D655 33 D0 D655 33 D0 D655 34 -- -- -- -- -- -- -- -- T -- -- T0 T204 7 -- -- -- -- -- -- -- -- -- -- -- -- C0 C204 7 C0 C204 7 C0 C204 6 C0 C204 6 -- -- -- -- -- -- -- -- -- -- -- -- -- C Data types M0 M99 92 M0 M99 88 M0 M99 84 W -- W0 WFF FF W0 WFF FF W0 WFF FE W0 WFF FE W0 WFF FE -- -- -- -- -- -- X X0 XFFF F -- -- -- -- -- -- X0 XFF FC X0 XFF F8 X0 XFF F4 X0 XFF F0 X0 X0 X0 X0 XFFE XFFE XFFE XFFE C 8 4 0 Y Y0 YFFF F -- -- -- -- -- -- Y0 YFF FC Y0 YFF F8 Y0 YFF F4 Y0 YFF F0 Y0 Y0 Y0 Y0 YFFE YFFE YFFE YFFE C 8 4 0 FX0 Addres s areas Bool Data types Word M M0 M9999 D D0.0 - D0 D999.1 D999 5 WinCC Basic V13.0 System Manual, 02/2014 DWord Real D0 D998 D0 D998 String 4-bit block 8-bit block 12-bit block 16-bit block 20-bit block 24-bit block 28-bit block 32-bit block M0 M999 6 M0 M999 2 M0 M998 8 M0 M998 4 M0 M0 M0 M0 M9980 M9976 M9972 M9968 D0 D998 3915 Visualize processes 10.8 Communicating with PLCs Addres s areas Bool Data types Word DWord Real T T0 T255 C-16Bit C-16Bit 0 C-16Bit 199 C-32Bit String 4-bit block 8-bit block 12-bit block 16-bit block 20-bit block 24-bit block 28-bit block 32-bit block C-32Bit 200 C-32Bit 255 X X0 X255 X0 X252 X0 X248 X0 X244 X0 X240 X0 X236 X0 X232 X0 X228 X0 X224 Y Y0 X255 Y0 Y252 Y0 Y248 Y0 Y244 Y0 Y240 Y0 Y236 Y0 Y232 Y0 Y228 Y0 Y224 Commissioning components Transferring a project to the HMI device 1. Switch the HMI device to "transfer mode". 2. Set all necessary transfer parameters. - Interface - Transfer parameters - Target storage location 3. Start the project transfer. The project is compiled automatically. All compilation and transfer steps are logged to a message window. Interconnecting the PLC with the HMI device 1. Interconnect the PLC with the HMI device using a suitable cable. 2. The message "Connection to PLC .... is established" is output to the HMI device. Optimizing the configuration Acquisition cycle and update time The acquisition cycles for the "Area pointers" and of the tags defined in the configuration software are decisive in terms of the update times which can actually be achieved. The update time is equivalent to the acquisition cycle + transmission time + processing time. 3916 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs Items to observe when optimizing the update times in configuration data: Optimize the maximum and minimum size of the data areas. Acquisition cycles which are too short lead to unnecessary load on overall performance. Set the acquisition cycle according to the rate of change of the process values. The rate of temperature changes at a furnace, for example, is significantly slower compared to the speed rate of an electrical drive. A time of approx. 1 second is a benchmark for the acquisition cycle. Avoid any gaps when entering the alarm or screen tags in a data area. Changes in the PLC can only be detected reliably if these are available at least within the actual acquisition cycle. Screens The refresh rate of screens is determined by the type and volume of data to be visualized. Only configure short acquisition cycles for objects which actually require shorter refresh cycles. This procedure reduces update times. Trends The HMI device always updates all bit-triggered trends whose group bit is set in the "Trend transfer area". It resets the bits in the next cycle. The group bit in the PLC program can only be set again after the HMI device has reset all bits. Job mailboxes A high rate and volume of job mailboxes transferred may lead to overload in communication between the HMI device and the PLC. The HMI device confirms acceptance of the job mailbox by entering the value zero in the first data word of the job mailbox. The HMI device now processes the job for which it requires a certain time slice. It may take the HMI device some time to process a new job mailbox which is transferred in immediate succession to the job mailbox. The next job mailbox is only accepted if sufficient computing resources are available. Data exchange Area pointers for Mitsubishi Area pointers for connections via Mitsubishi communication drivers You use an area pointer to access a data area in the PLC. For more detailed information on area pointers and their configuration, refer to Section "Data exchange using area pointers". WinCC Basic V13.0 System Manual, 02/2014 3917 Visualize processes 10.8 Communicating with PLCs Special considerations for connections via Mitsubishi communication drivers You can configure the following area pointers Area pointers Mitsubishi MC TCP/IP Mitsubishi FX Screen number Yes Yes Date/time Yes Yes Date/time PLC Yes Yes Coordination Yes Yes Project ID Yes Yes Job mailbox Yes Yes Data record Yes Yes Restrictions Mitsubishi MC TCP/IP The following restrictions apply for configuring area pointers. CPU type Data types Operand type FX3 Int, Word D Q Int, Word D Mitsubishi FX restrictions You cannot use the D operand type for configuring area pointers. See also Data exchange using area pointers (Page 3967) Trends Trends A trend is the graphical representation of one or more values from the PLC. The value is read out time-triggered for Basic Panels. For additional information see: Configuring trend displays for values from the PLC (Page 3369) Time-triggered trends The HMI device reads in the trend values cyclically at an interval specified in the configuration. Time-triggered trends are suitable for continuous curves, such as the operating temperature of a motor. 3918 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs Alarms Configuring alarms Configuring alarms for non-integrated connections Several steps are necessary to configure alarms such as warnings, error messages and acknowledgement. Step 1: Create tags Step 2: Configure alarms Step 3: Configure acknowledgment You can find additional information in the section: Working with alarms (Page 3379) Distinctive features when configuring alarms If you are configuring connections of HMI devices to PLCs of other manufacturers, note the following distinctive features when configuring: Data types of the tags Addressing of tags How the bit positions are counted Data types For connections with a Mitsubishi communication driver, the following data types are supported: PLC Permitted data types Discrete alarms FX1n, FX2n, FX3 series, QSeries, iQ-Series 1) WinCC Basic V13.0 System Manual, 02/2014 Word, Int 1) Analog alarms 4-bit block, 8-bit block, 12-bit block, 16-bit block, 20-bit block, 24-bit block, 28-bit block, 32-bit block, Word, DWord, Int 1), DInt 1), Real, Not for Mitsubishi FX communication driver 3919 Visualize processes 10.8 Communicating with PLCs How the bit positions are counted For connections with a Mitsubishi communication driver, the following counting method applies: How the bit positions are counted Left byte Right byte In Mitsubishi PLCs 15 8 7 0 In WinCC you configure: 15 8 7 0 Restrictions on alarms Mitsubishi MC TCP/IP Only tags of operand type "D" and data types "Word" and "Int" are permitted as trigger tags for discrete alarms. You can use array tags (operand type: "D"; data types: "ARRAY [x..y] of Word" or "ARRAY [x..y] of Int") for discrete alarms. Mitsubishi FX Only tags of operand type "D" and data type "Word" are permitted as trigger tags for discrete alarms. You can use array tags (operand type "D"; data type "ARRAY [x..y] of Word") for discrete alarms." Acknowledgment of alarms Procedure Create suitable tags on the PLC to acknowledge an error alarm. You assign these tags to an alarm in the "Bit messages" editor. You make the assignment in "Properties > Acknowledgment". Distinction in terms of acknowledgment: Acknowledgment by the PLC Acknowledgment on the HMI device Acknowledgment by the PLC In "PLC acknowledgment tag", configure the tag or array tag and the bit number that the HMI device uses to identify a PLC acknowledgment. A bit set in the tag triggers acknowledgment of the assigned error alarm bit at the HMI device. This tag bit returns a function similar to acknowledgment on the HMI device which is triggered by pressing the "ACK" button, for example. The acknowledgment bit must be located in the same tag as the bit for the error alarm. Reset the acknowledgment bit before setting the bit in the alarm area again. The figure below shows the pulse diagram. 3920 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs (UURUDODUP $FNQRZOHGJPHQW 3/&+0,GHYLFH $UULYDORIWKH $FNQRZOHGJP 5HVHWRI HUURUDODUP YLD3/& DFNQRZOHGJPELW 1HZ HUURUDODUP Acknowledgment on the HMI device In the "HMI acknowledgment tag" area, configure the tag or array tag as well as the bit number that the HMI device writes to the PLC after acknowledgment. Make sure when you use an array tag that it is not longer than 6 words. To always create a signal change when setting an assigned acknowledgment bit of a discrete alarm that must be acknowledged, the HMI device will reset the acknowledgment bit assigned to the alarm as soon as it detects an alarm subject to acknowledgment and write the acknowledgment tag in the PLC. There will be a certain delay between detecting the message and writing the acknowledgment tag in the PLC because the HMI device has to process the operations. If a discrete alarm subject to acknowledgment is acknowledged by the HMI device, then the corresponding bit in the assigned acknowledgment tag will be set. The entire acknowledgment tag is then written to the PLC by the HMI device. This allows the PLC to recognize that a certain alarm message has been acknowledged at the HMI device. Note All alarm bits acknowledged since the last Runtime start will remain in the acknowledgment tag until a new incoming of the respective discrete alarms is detected. This area should only be read by the PLC because the entire section of the HMI device will be overwritten once the next acknowledgment tag is written. The figure below shows the pulse diagram. (UURUDODUP $FNQRZOHGJPHQW +0,GHYLFH3/& $UULYDORIWKH HUURUDODUP WinCC Basic V13.0 System Manual, 02/2014 5HVHWRI DFNQRZOHGJPELW $FNQRZOHGJP YLD+0,GHYLFH 1HZ HUURUDODUP 3921 Visualize processes 10.8 Communicating with PLCs Modicon Modbus Modicon Modbus communication drivers Introduction This section describes the communication between an HMI device and PLCs that use Modicon Modbus communication drivers. The following communication drivers are supported: Modicon Modbus TCP/IP Modicon Modbus RTU Data exchange Data is exchanged by means of tags or area pointers. Tags The PLC and the HMI device use process values for data exchange. You create tags in the configuration that point to addresses in the PLC. The HMI device reads the value from the defined address, and then displays it. The operator may also enter values on the HMI device, which are then written to the address in the PLC. Area pointers Area pointers are used to exchange specific data and are only set up when these data are used. Modicon Modbus TCP/IP Configuring a connection via Modicon Modbus TCP/IP Introduction You configure a connection to one of the PLCs with Modicon Modbus TCP/IP communication driver in the "Connections" editor of the HMI device. The Ethernet interfaces are named differently depending on the HMI device. Example: PROFINET interface corresponds to the Ethernet interface Requirements A project is open. An HMI device has been created. 3922 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs Procedure 1. Double-click the HMI device under "Devices" in the project tree. 2. Double-click the "Connections" item. 3. Double-click "<Add>" in the "Connections" editor. WinCC Basic V13.0 System Manual, 02/2014 3923 Visualize processes 10.8 Communicating with PLCs 4. Select the "Modicon Modbus TCP" driver in the "Communication driver" column. 5. Select all necessary connection parameters for the interface in the Inspector window under "Parameters". Parameters for the connection (Modicon Modbus TCP/IP) Parameters to be set To set the connection parameters, such as addresses and profiles, click the connection that you have created in the "Connections" editor. The communication partners are displayed schematically in the Inspector window under "Parameters". The "HMI device" and "PLC" areas are available for assigning parameters according to the interface used. 3924 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs Parameters for the HMI device You can select only one interface for the HMI device in the Inspector window under "Parameters". Depending on the HMI device, there are several interfaces available. If you are directly connected to the HMI device during configuration, you can set up the IP address of the HMI device in WinCC. The IP address is transferred to the HMI device during project transfer. Note The IP address in the control panel will be overwritten upon subsequent loading if you have already set up the IP address in the HMI device control panel. The IP address already set up in the control panel will be retained upon subsequent loading if you activate "Set IP address using a different method". To set up the IP address of the HMI device: 1. Click the HMI device. 2. Open the "Device configuration" editor. WinCC Basic V13.0 System Manual, 02/2014 3925 Visualize processes 10.8 Communicating with PLCs 3. Click the Ethernet interface. 4. Assign the IP address in the inspector window under: "General > PROFINET interface > Ethernet addresses" Parameters for the PLC "CPU type" For "CPU type", you set the Modicon PLC to which the HMI device is connected. "Port" For "Port", you set the port that is used for the TCP/IP connection. The port used by the Modicon PLCs is 502. "Server" You set the IP address or host name of the PLC under "Server". Only the IP address can be used on a Basic Panel. "Distributed slave address" For "Distributed slave address", set the slave address of the remote PLC, but only if a bridge is used. If a bridge is not used, the default value "255" (or "0") must be retained. "Change word order" The "Change word order " parameter only affects the word order of the 32-bit values display. The setting pertains to the data types Double, Double+/-, and Float. The byte order cannot be changed. - "Change word order" not activated The most significant byte is sent first. For double words, the least significant word is sent before the most significant word. This setting has been system-tested for all approved PLCs. - "Change word order" activated The most significant byte is sent first. For double words, the most significant word is sent before the least significant word. Note This setting must be used for the SIEMENS SENTRON PAC3200 and PAC4200 multifunction meters and can be used for PLCs of other manufacturers. "Use single write" If you deselect this function, only function codes 15H and 16H are used for writing into the PLC. If this function remains selected, the function codes 05H, 06H, 15H, and 16H are used. 3926 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs Connecting HMI device to PLC Connections via Modicon Modbus TCP/IP Connection The HMI device can be connected to the Modicon Modbus PLC using the following components: Existing Ethernet network that also contains the PLCs Cross-over Ethernet cable connected directly to the Ethernet interface of the CPU or the communication module The connection of the HMI device to a Modicon Modbus PLC is limited primarily to the physical connection of the HMI device. Special blocks for the connection are not required in the PLC. Note Timeout response with TCP/IP (Ethernet) Due to the use of the TCP/IP protocol, the breakdown of a connection is detected at the earliest after approximately one minute. Communication failure cannot be reliably detected if no tags are requested, for example, no output tags in the current screen. Configure area pointer coordination for each PLC. This setting ensures that a communication failure is recognized after approximately two minutes, even in the aforementioned scenario. WinCC Basic V13.0 System Manual, 02/2014 3927 Visualize processes 10.8 Communicating with PLCs Communication types Approved communication types The following communication types are system-tested and approved: Point-to-point coupling: Multiple point coupling of a HMI device (Modbus TCP/IP Client) with up to 4 PLCs, each with different couplings. CPU types can be mixed. The following couplings are possible: - Coupling the Ethernet CPU interface of the TSX Unity Quantum. - Coupling via the communication modules for Ethernet 140 NOE 771 01 for the TSX Quantum and TSX Unity Quantum series - Coupling via the Ethernet interface of the 171 CCC 980 30 CPU adapter of the Momentum series - Coupling the Ethernet CPU interface of the TSX Unity Premium. - Coupling via the Ethernet TCP/IP connect module TSX ETY 110 for the TSX Premium and TSX Unity Premium series - Coupling via the Ethernet TCP/IP connect module TSX ETY 410 for the Micro series - Coupling via the Ethernet TCP/IP Modbus Plus Bridge 174 CEV 200 40 to the Modbus Plus interface of the Compact, the TSX Quantum and the TSX Unity Quantum series Via the TCP/IP Modbus Plus Bridge, 174 CEV 200 40, the PLCs can be accessed at their Remote Slave Address via the Ethernet interface of this bridge. Note Integration of the HMI device in a Modbus network via a bridge is not possible. The HMI device is the Modbus master. Restrictions The coupling of the HMI device to PLCs of other manufacturers who offer a Modbus TCP/IP interface is not system-tested and thus, not enabled. However, if another PLC is to be used, observe the following instructions: Use the following CPU types, because these operate without address offset and in the usual bit count manner. - Unity, PL7: Premium, Micro, Quantum, M340 The following function codes are used for the respective data areas: 3928 Reading function codes Address range 01 ReadCoilStatus 0x / %M DIGITAL_OUT 02 ReadInputStatus 1x / %I DIGITAL_IN 03 ReadHoldingRegisters 4x / %MW USERDATA WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs Reading function codes Address range 04 ReadInputRegisters 3x / %IW ANALOG_IN 20 (14Hex) ReadGeneralReference 6x / - EXTENDEDMEMORY (not for all CPUs) Writing function codes Address range 06 PresetSingleRegister 4x / %MW USERDATA Single 16 (10Hex) PresetMultipleRegisters 4x / %MW USERDATA Multiple 05 1) ForceSingleCoil 0x / %M DIGITAL_OUT with BIT 15 (0FHex) ForceMultipleCoils 0x / %M DIGITAL_OUT with 16 BIT GROUP 21 (15Hex) WriteGeneralReference 6x / - EXTENDEDMEMORY (not for all CPUs) 1) Select use with "Use single write". 1) Connectable PLCs Connections can be implemented for the following Modicon Modbus PLCs: Modicon Modbus PLC Modicon Modbus RTU 2) Supported protocol Modicon Modbus TCP/IP TSX Compact x x 1) TSX Quantum x x Momentum x x Premium - x Micro - x M340 20x0 (without 2010) - x 1) 2) WinCC Basic V13.0 System Manual, 02/2014 Only via Ethernet TCP/IP Modbus Plus Bridge Communication via RS 232 is tested and enabled for the PLC. In the HMIs that only have a RS 422/485 interface, the RS 422/232 converter with the order number 6AV6 671-8XE00-0AX0 was tested and enabled. 3929 Visualize processes 10.8 Communicating with PLCs Performance features of communication Permissible data types for Modicon Modbus TCP/IP Permitted data types The table lists the data types that can be used when configuring tags and area pointers. Note If you change the Modicon Modbus RTU communication driver to Modicon Modbus TCP/IP, the string in the "String" data type may be different. Permitted data types for CPU type "Unity, PLC: Premium, Micro, Quantum M340" Data type Operand type Length +/- Double %MW 4 bytes +/- Int %MW, %IW 2 bytes 16-bit group %MW, %I 2 bytes ASCII %MW 0 to 80 characters Bit %MW, %IW, %M, %I 1-bit Double %MW 4 bytes Float %MW 4 bytes Int %MW, %IW 2 bytes Note The ranges "%I" and "%IW" are not supported for the following CPU types: Premium Micro M340 Permitted data types for CPU type "Concept, ProWORX: Compact, Quantum, Momentum" 3930 Data type Operand type Length +/- Double 4x, 6x 4 bytes +/- Int 3x, 4x, 6x 2 bytes 16-bit group 0x, 1x 2 bytes ASCII 4x, 6x 0 to 80 characters Bit 0x, 1x, 3x, 4x, 6x 1-bit WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs Data type Operand type Length Double 4x, 6x 4 bytes Float 4x, 6x 4 bytes Int 3x, 4x, 6x 2 bytes Bit counting method The usual bit counting method "16 LSB - 1 MSB" in the following CPU types is only used in the "HMI tags" editor with the selected "Bit" data type: Concept, ProWORX: Compact, Quantum, Momentum The following bit location assignment applies: Left byte Counting with tags 1 2 3 4 5 Right byte 6 7 8 9 10 11 12 13 14 15 16 Format for "Signed" The placeholder "+/-" stands for the data types "Signed Int" and "Signed Double". Supported CPU types for Modicon Modbus TCP/IP CPU types The following CPU types are supported for configuring the Modicon Modbus TCP/IP communication driver. Compact Momentum Quantum - Concept Quantum - Unity Quantum Micro Premium Modicon M340 - 20x0 (except 2010) WinCC Basic V13.0 System Manual, 02/2014 3931 Visualize processes 10.8 Communicating with PLCs Address areas for Modicon Modbus TCP/IP UnityPl7 Address areas Data types Bool 16 Bit Group Int +/- Int DInt +/- DInt Float ASCII %1 %I0 %I65535 %I65535 %I0 %I65520 -- -- -- -- -- -- %M %M0 %M65535 %M65535 %M0 %M65520 -- -- -- -- -- -- %IW %IW0.0 - -- %IW0 %IW65535 %IW0 -%IW65535 -- -- -- -- %MW0 - %MW0 - %MW0 - %MW0 - %MW0 - %MW0 - %MW6553 5 %MW6553 5 %MW6553 4 %MW6553 4 %MW6553 4 %MW6553 5 %IW65535. 15 %MW %MW0.0 %MW6553 5.15 ConceptProWORX Address areas Data types Bool 16 Bit Group Int +/- Int DInt +/- DInt Float ASCII 0x 0x1 0x65535 0x1 0x65520 -- -- -- -- -- -- 1x 1x100001 1x165535 1x100001 1x165520 -- -- -- -- -- -- 3x 3x300001.1 -3x365535.1 6 3x300001 3x365535 3x300001 3x365535 -- -- -- -- 4x 4x400001.1 -4x465535.1 6 4x400001 4x465535 4x400001 4x465535 4x400001 4x465534 4x400001 4x465534 4x400001 4x465534 4x400001 4x465535 6x 6x60000.1: -16x69999.16 :10 6x60000:1 - 6x60000:1 - 6x60000:1 - 6x60000:1 - 6x60000:1 - 6x60000:1 6x69999:10 6x69999:10 6x69998:10 6x69998:10 6x69998:10 6x69999:10 3932 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs Commissioning components Transferring a project to the HMI device 1. Switch the HMI device to "transfer mode". 2. Set all necessary transfer parameters. - Interface - Transfer parameters - Target storage location 3. Start the project transfer. The project is compiled automatically. All compilation and transfer steps are logged to a message window. Interconnecting the PLC with the HMI device 1. Interconnect the PLC with the HMI device using a suitable cable. 2. The message "Connection to PLC .... is established" is output to the HMI device. Optimizing the configuration Acquisition cycle and update time The acquisition cycles for the "Area pointers" and of the tags defined in the configuration software are decisive in terms of the update times which can actually be achieved. The update time is equivalent to the acquisition cycle + transmission time + processing time. Items to observe when optimizing the update times in configuration data: Optimize the maximum and minimum size of the data areas. Acquisition cycles which are too short lead to unnecessary load on overall performance. Set the acquisition cycle according to the rate of change of the process values. The rate of temperature changes at a furnace, for example, is significantly slower compared to the speed rate of an electrical drive. A time of approx. 1 second is a benchmark for the acquisition cycle. Avoid any gaps when entering the alarm or screen tags in a data area. Changes in the PLC can only be detected reliably if these are available at least within the actual acquisition cycle. Screens The refresh rate of screens is determined by the type and volume of data to be visualized. Only configure short acquisition cycles for objects which actually require shorter refresh cycles. This procedure reduces update times. WinCC Basic V13.0 System Manual, 02/2014 3933 Visualize processes 10.8 Communicating with PLCs Trends The HMI device always updates all bit-triggered trends whose group bit is set in the "Trend transfer area". It resets the bits in the next cycle. The group bit in the PLC program can only be set again after the HMI device has reset all bits. Job mailboxes A high rate and volume of job mailboxes transferred may lead to overload in communication between the HMI device and the PLC. The HMI device confirms acceptance of the job mailbox by entering the value zero in the first data word of the job mailbox. The HMI device now processes the job for which it requires a certain time slice. It may take the HMI device some time to process a new job mailbox which is transferred in immediate succession to the job mailbox. The next job mailbox is only accepted if sufficient computing resources are available. Modicon Modbus RTU Configuring a connection via Modicon Modbus RTU Introduction You configure a connection to a PLC with a Modicon Modbus RTU communication driver in the "Connections" editor of the HMI device. The interfaces are named differently depending on the HMI device. Requirements A project is open. An HMI device has been created. Procedure 1. Double-click the HMI device under "Devices" in the project tree. 2. Double-click the "Connections" item. 3934 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs 3. Double-click "<Add>" in the "Connections" editor. WinCC Basic V13.0 System Manual, 02/2014 3935 Visualize processes 10.8 Communicating with PLCs 4. In the "Communication drivers" column, select the "Modicon Modbus RTU" driver. 5. Select all necessary connection parameters for the interface in the Inspector window under "Parameters". Parameters for the connection (Modicon Modbus RTU) Parameters to be set To set the connection parameters, such as addresses and profiles, click the connection that you have created in the "Connections" editor. The communication partners are displayed schematically in the Inspector window under "Parameters". The "HMI device" and "PLC" areas are available for assigning parameters according to the interface used. 3936 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs Parameters for the HMI device You can select an interface for the HMI device in the Inspector window under "Parameters". Depending on the HMI device, there are several interfaces available. Type Only RS 232 is system-tested. No warranty is given for RS 485. Note RS 422 is only approved in combination with the RS 422-RS 232 converter. Order number: 6AV6 671-8XE00-0AX0 Note If you use the IF1B interface, you must switch over the RS422 receive data additionally by 4 DIL-switches on the back of the HMI device. Baud rate For "Baud rate", select the transmission speed between the HMI device and Modicon PLC. A baud rate of 19200 or 9600 can be selected for the communication. A baud rate of 4800 can be selected for certain HMI devices. WinCC Basic V13.0 System Manual, 02/2014 3937 Visualize processes 10.8 Communicating with PLCs Data bits For "Data bits", only the value "8" can be selected. Parity For "Parity", you can choose from "None", "Even", and "Odd". Stop bits For "Stop bits", you can choose between 1 and 2 bits. Parameters for the PLC CPU type For "CPU type", you set the Modicon PLC to which the HMI device is connected. You can select the following CPUs: - Concept, ProWORX: Compact, Quantum Slave address Under "Slave address" you set which slave address the CPU has. Connecting HMI device to PLC Connections via Modicon Modbus RTU Connection Connect the HMI device to the Modicon Modbus RTU interface of the Modicon Modbus RTU slave. The connection of the HMI device to Modicon is limited primarily to the physical connection of the HMI device. Special blocks for the connection are not required in the PLC. Connection cable The following connecting cables are available to connect the HMI device to Modicon Modbus. Modicon PLC Interface to the HMI device directly via Modbus interface (RS232) 9-pin Sub D male connector Via MB Bridge (RS 232) directly via Modbus interface (RS232) 8-pin RJ45 connector RS 232, 9-pin PP1 PP1 PP2 The cable pin assignments can be found in Section "Connecting cables for Modicon Modbus RTU". 3938 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs Communication types Approved communication types The following communication types are system-tested and approved: Ppoint-to-point connection only via the RS-232 interface. Multipoint connection from a HMI device (Modbus-Master) with up to 4 PLCs: The HMI device must be connected with a Modbus Plus Bridge or a Compact, Momentum CPU or TSX Quantum CPU which is configured as a Modbus Plus Bridge. You connect the other PLCs via the Modbus Plus connection on the first PLC. The PLCs can be reached under their address via the bridge functionality of the first PLC. Note It is not possible to integrate the HMI device into a Modbus network because the HMI device is Modbus-Master. Integration of the HMI device into a Modbus Plus network via the "bridge mode" of the Compact, Momentum or Quantum (logical point-to-point communication of the HMI device with a Compact, Momentum or Quantum). Restrictions The connection of the HMI device to PLCs of other manufacturers which offer a Modicon Modbus interface is not system-tested and therefore not approved. If you use another PLC nevertheless, observe the following information: These drivers only work for tags with the bit counting method typical for Modicon PLCs from left (bit1 = most significant bit) to right (bit16 = least significant bit in data type INT). The address offset displayed in the configuring is subtracted at protocol level in the message frame. E.g. in Holding Register 4x the offset "40001". The configured address "40006" therefore becomes address "5" in the message frame. The address (e.g. "5") transferred in the message frame is transformed to the PLC-specific address range in the different Non-Modicon PLCs. A reply message frame without "ExceptionCode" is expected within 500 ms. The following function codes are used for the respective data areas: WinCC Basic V13.0 System Manual, 02/2014 Reading function codes Address range 01 ReadCoilStatus 0x DIGITAL_OUT 02 ReadInputStatus 1x DIGITAL_IN 03 ReadHoldingRegisters 4x USERDATA 04 ReadInputRegisters 3x ANALOG_IN 20 (14Hex) ReadGeneralReference 6x EXTENDEDMEMORY (not for all CPUs) 3939 Visualize processes 10.8 Communicating with PLCs Writing function codes Address range 06 PresetSingleRegister 4x USERDATA Single 16 (10Hex) PresetMultipleRegisters 4x USERDATA Multiple 05 ForceSingleCoil 0x DIGITAL_OUT with data type Bit 15 (0FHex) ForceMultipleCoils 0x DIGITAL_OUT with data type 16 bit group 21 (15Hex) WriteGeneralReference 6x EXTENDEDMEMORY (not for all CPUs) Connectable PLCs Connections can be implemented for the following Modicon Modbus PLCs: Modicon Modbus PLC Modicon Modbus RTU Modicon Modbus TCP/IP TSX Compact x x 1) TSX Quantum x x Momentum x x Premium - x Micro - x M340 20x0 (without 2010) - x 1) 2) 3940 Supported protocol 2) Only via Ethernet TCP/IP-Modbus Plus Bridge Communication via RS 232 is tested and enabled for the PLC. In the HMI devices which only have an RS 422/485 interface, the RS 422/232 converter with the order number 6AV6 671-8XE00-0AX0 was tested and approved. WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs Connecting cables for Modicon Modbus RTU Connecting cable PP1, RS-232, for Modicon Point-to-point cable 1: PLC > PC ... +0,GHYLFH 0RGLFRQ0RGEXV SLQ'6XEIHPDOHFRQQHFWRU SLQ'6XEFRQQHFWRU FRQQHFWRU FRQQHFWRU HQFORVXUH VKLHOG *1' *1' 5[' 7[' 7[' 5[' '75 '65 576 &76 Cables: 3 x 0.14 mm2, shielded, max. length 15 m WinCC Basic V13.0 System Manual, 02/2014 3941 Visualize processes 10.8 Communicating with PLCs Connecting cable PP2, RS-232, for Modicon Point-to-point cable 2: PLC (TSX Compact) > PC... +0,GHYLFH &RQQHFWRU SLQ6XE'FRQQHFWRUSOXJ 0RGLFRQ0RGEXV &RQQHFWRU 3LQ5-6WHFNHU +RXVLQJ 6KLHOGLQJ *1' *1' 5[' 7[' 7[' 5[' 576 &76 3LQLVXSZKHQORRNLQJDWWKHFRQWUROOHU Cables: 3 x 0.14 mm2, shielded, max. length 15 m 3942 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs Performance features of communication Permitted data types for Modicon Modbus RTU Permitted data types The table lists the data types that can be used when configuring tags and area pointers. Data type Operand type Length +/- Double 4x, 6x 4 bytes +/- Int 3x, 4x, 6x 2 bytes 16-bit group 0x, 1x 2 bytes ASCII 4x, 6x 0 to 80 characters Bit 1) 0x, 1x, 3x, 4x, 6x 1-bit Double 4x, 6x 4 bytes Float 4x, 6x 4 bytes Int 3x, 4x, 6x 2 bytes 1) Note the following for write accesses: For data type "Bit" with the operand types "4x" and "6x", the entire word is written back to the PLC following a change to the specified bit. There is no check to determine whether any other bits in the word have changed. As a result, the PLC only has read access to the specified word. The usual bit counting method (16 LSB - 1 MSB) in the following CPU types is only used in the "HMI tags" editor with the selected "Bit" data type: Concept ProWORX: Compact, Quantum The following bit location assignment applies: Left byte Counting with tags 1 2 3 4 5 Right byte 6 7 8 9 10 11 12 13 14 15 16 Format for "Signed" The placeholder "+/-" stands for the data types "Signed Int" and "Signed Double". WinCC Basic V13.0 System Manual, 02/2014 3943 Visualize processes 10.8 Communicating with PLCs Supported CPU types for Modicon Modbus RTU CPU types The following CPU types are supported in the configuration of the Modicon Modbus RTU communication driver. Compact Momentum Quantum Address areas for Modicon Modbus RTU UnityPl7 Address areas Data types Bool 16 Bit Group Int +/- Int DInt +/- DInt Float ASCII %1 %I0 %I65535 %I65535 %I0 %I65520 -- -- -- -- -- -- %M %M0 %M65535 %M65535 %M0 %M65520 -- -- -- -- -- -- %IW %IW0.0 - -- %IW0 %IW65535 %IW0 -%IW65535 -- -- -- -- %MW0 - %MW0 - %MW0 - %MW0 - %MW0 - %MW0 - %MW6553 5 %MW6553 5 %MW6553 4 %MW6553 4 %MW6553 4 %MW6553 5 %IW65535. 15 %MW %MW0.0 %MW6553 5.15 ConceptProWORX Address areas Data types Bool 16 Bit Group Int +/- Int DInt +/- DInt Float ASCII 0x 0x1 0x65535 0x1 0x65520 -- -- -- -- -- -- 1x 1x100001 1x165535 1x100001 1x165520 -- -- -- -- -- -- 3x 3x300001.1 -3x365535.1 6 3x300001 3x365535 3x300001 3x365535 -- -- -- -- 3944 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs Address areas Data types Bool 16 Bit Group Int +/- Int DInt +/- DInt Float ASCII 4x400001 4x465535 4x400001 4x465534 4x400001 4x465534 4x400001 4x465534 4x400001 4x465535 4x 4x400001.1 -4x465535.1 6 4x400001 4x465535 6x 6x60000.1: -16x69999.16 :10 6x60000:1 - 6x60000:1 - 6x60000:1 - 6x60000:1 - 6x60000:1 - 6x60000:1 6x69999:10 6x69999:10 6x69998:10 6x69998:10 6x69998:10 6x69999:10 Commissioning components Transferring a project to the HMI device 1. Switch the HMI device to "transfer mode". 2. Set all necessary transfer parameters. - Interface - Transfer parameters - Target storage location 3. Start the project transfer. The project is compiled automatically. All compilation and transfer steps are logged to a message window. Interconnecting the PLC with the HMI device 1. Interconnect the PLC with the HMI device using a suitable cable. 2. The message "Connection to PLC .... is established" is output to the HMI device. Optimizing the configuration Acquisition cycle and update time The acquisition cycles for the "Area pointers" and of the tags defined in the configuration software are decisive in terms of the update times which can actually be achieved. The update time is equivalent to the acquisition cycle + transmission time + processing time. Items to observe when optimizing the update times in configuration data: WinCC Basic V13.0 System Manual, 02/2014 3945 Visualize processes 10.8 Communicating with PLCs Optimize the maximum and minimum size of the data areas. Acquisition cycles which are too short lead to unnecessary load on overall performance. Set the acquisition cycle according to the rate of change of the process values. The rate of temperature changes at a furnace, for example, is significantly slower compared to the speed rate of an electrical drive. A time of approx. 1 second is a benchmark for the acquisition cycle. Avoid any gaps when entering the alarm or screen tags in a data area. Changes in the PLC can only be detected reliably if these are available at least within the actual acquisition cycle. Screens The refresh rate of screens is determined by the type and volume of data to be visualized. Only configure short acquisition cycles for objects which actually require shorter refresh cycles. This procedure reduces update times. Trends The HMI device always updates all bit-triggered trends whose group bit is set in the "Trend transfer area". It resets the bits in the next cycle. The group bit in the PLC program can only be set again after the HMI device has reset all bits. Job mailboxes A high rate and volume of job mailboxes transferred may lead to overload in communication between the HMI device and the PLC. The HMI device confirms acceptance of the job mailbox by entering the value zero in the first data word of the job mailbox. The HMI device now processes the job for which it requires a certain time slice. It may take the HMI device some time to process a new job mailbox which is transferred in immediate succession to the job mailbox. The next job mailbox is only accepted if sufficient computing resources are available. Data exchange Area pointers for Modicon Modbus Area pointers for connections via Modicon Modbus communication drivers You use an area pointer to access a data area in the PLC. For more detailed information on area pointers and their configuration, refer to Section "Data exchange using area pointers (Page 3967)". 3946 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs Special considerations for connections via Modicon communication drivers You can configure the following area pointers Area pointers Modicon Modbus TCP/IP Modicon Modbus RTU Screen number Yes Yes Date/time Yes Yes Date/time PLC Yes Yes Coordination Yes Yes Project ID Yes Yes Job mailbox Yes Yes Data record Yes Yes Restrictions Modicon Modbus TCP/IP The following restrictions apply for configuring area pointers. CPU type Data types File types Concept, ProWORX: Compact, Quantum, Momentum +/- Int, Int 4x, 6x Unity, PL7: Premium, Micro, Quantum, M340 +/- Int, Int %MW Modicon Modbus RTU restrictions The following restrictions apply for configuring area pointers. CPU type Data types File types Concept, ProWORX: Compact, Quantum, Momentum +/- Int, Int 4x, 6x Trends Trends A trend is the graphical representation of one or more values from the PLC. The value is read out time-triggered for Basic Panels. For additional information see: Configuring trend displays for values from the PLC (Page 3369) Time-triggered trends The HMI device reads in the trend values cyclically at an interval specified in the configuration. WinCC Basic V13.0 System Manual, 02/2014 3947 Visualize processes 10.8 Communicating with PLCs Time-triggered trends are suitable for continuous curves, such as the operating temperature of a motor. Alarms Configuring alarms Configuring alarms for non-integrated connections Several steps are necessary to configure alarms such as warnings, error messages and acknowledgement. Step 1: Create tags Step 2: Configure alarms Step 3: Configure acknowledgment You can find additional information in the section: Working with alarms (Page 3379) Distinctive features when configuring alarms If you are configuring connections of HMI devices to PLCs of other manufacturers, note the following distinctive features when configuring: Data types of the tags Addressing of tags How the bit positions are counted Data types For connections with a Modicon Modbus communication driver, the following data types are supported: PLC All Modicon series Permitted data types Discrete alarms Analog alarms Int, +/-Int 16 Bit Group, Int, +/-Int, Double, +/-Double, Float Arrays and array tags cannot be used for discrete alarms. 3948 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs How the bit positions are counted For connections with a Modicon Modbus communication driver, the following counting method applies: How the bit positions are counted In WinCC you configure: Left byte 15 1 4 1 3 1 2 1 1 Right byte 1 0 9 8 7 6 5 4 3 2 1 0 Acknowledgment of alarms Procedure Create suitable tags on the PLC to acknowledge an error alarm. You assign these tags to an alarm in the "Bit messages" editor. You make the assignment in "Properties > Acknowledgment". Distinction in terms of acknowledgment: Acknowledgment by the PLC Acknowledgment on the HMI device Acknowledgment by the PLC In "PLC acknowledgment tag", configure the tag or array tag and the bit number that the HMI device uses to identify a PLC acknowledgment. A bit set in the tag triggers acknowledgment of the assigned error alarm bit at the HMI device. This tag bit returns a function similar to acknowledgment on the HMI device which is triggered by pressing the "ACK" button, for example. The acknowledgment bit must be located in the same tag as the bit for the error alarm. Reset the acknowledgment bit before setting the bit in the alarm area again. The figure below shows the pulse diagram. (UURUDODUP $FNQRZOHGJPHQW 3/&+0,GHYLFH $UULYDORIWKH $FNQRZOHGJP 5HVHWRI HUURUDODUP YLD3/& DFNQRZOHGJPELW WinCC Basic V13.0 System Manual, 02/2014 1HZ HUURUDODUP 3949 Visualize processes 10.8 Communicating with PLCs Acknowledgment on the HMI device In the "HMI acknowledgment tag" area, configure the tag or array tag as well as the bit number that the HMI device writes to the PLC after acknowledgment. Make sure when you use an array tag that it is not longer than 6 words. To always create a signal change when setting an assigned acknowledgment bit of a discrete alarm that must be acknowledged, the HMI device will reset the acknowledgment bit assigned to the alarm as soon as it detects an alarm subject to acknowledgment and write the acknowledgment tag in the PLC. There will be a certain delay between detecting the message and writing the acknowledgment tag in the PLC because the HMI device has to process the operations. If a discrete alarm subject to acknowledgment is acknowledged by the HMI device, then the corresponding bit in the assigned acknowledgment tag will be set. The entire acknowledgment tag is then written to the PLC by the HMI device. This allows the PLC to recognize that a certain alarm message has been acknowledged at the HMI device. Note All alarm bits acknowledged since the last Runtime start will remain in the acknowledgment tag until a new incoming of the respective discrete alarms is detected. This area should only be read by the PLC because the entire section of the HMI device will be overwritten once the next acknowledgment tag is written. The figure below shows the pulse diagram. (UURUDODUP $FNQRZOHGJPHQW +0,GHYLFH3/& $UULYDORIWKH HUURUDODUP 5HVHWRI DFNQRZOHGJPELW $FNQRZOHGJP YLD+0,GHYLFH 1HZ HUURUDODUP Omron Omron communication drivers Introduction This section describes the communication between an HMI device and PLCs that use Omron communication drivers. The following communication drivers are supported: 3950 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs Omron Host Link Data exchange Data is exchanged by means of tags or area pointers. Tags The PLC and the HMI device use process values for data exchange. You create tags in the configuration that point to addresses in the PLC. The HMI device reads the value from the defined address, and then displays it. The operator may also enter values on the HMI device, which are then written to the address in the PLC. Area pointers Area pointers are used to exchange specific data and are only set up when these data are used. Omron Host Link Configuring a connection via Omron Host Link Introduction You configure a connection to a PLC with an Omron Host Link communication driver in the "Connections" editor of the HMI device. Note Connection with Omron Host Link A connection will not automatically be established when runtime is started if you have configured a connection via Omron. A tag which is in the valid PLC memory area must be configured in the runtime start screen. The connection will otherwise only be established once a corresponding screen has been selected. This tag will be accessed when runtime is started and a connection will then be established. The interfaces are named differently depending on the HMI device. Requirements A project is open. An HMI device has been created. Procedure 1. Double-click the HMI device under "Devices" in the project tree. 2. Double-click the "Connections" item. WinCC Basic V13.0 System Manual, 02/2014 3951 Visualize processes 10.8 Communicating with PLCs 3. Double-click "<Add>" in the "Connections" editor. 3952 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs 4. Select the "Omron Host Link" driver in the "Communication driver" column. 5. Select all necessary connection parameters for the interface in the inspector window under "Parameters". Parameters for the connection (Omron Hostlink) Parameters to be set To set the connection parameters, such as addresses and profiles, click the connection that you have created in the "Connections" editor. The communication partners are displayed schematically in the Inspector window under "Parameters". The "HMI device" and "PLC" areas are available for assigning parameters according to the interface used. WinCC Basic V13.0 System Manual, 02/2014 3953 Visualize processes 10.8 Communicating with PLCs Parameters for the HMI device You can select an interface for the HMI device in the Inspector window under "Parameters". Depending on the HMI device, there are several interfaces available. Type Specifies the physical connection used. Baud rate For "Baud rate", you set the transmission speed of the HMI device to OMRON. A baud rate of 19200 or 9600 can be selected for the communication. Data bits For "Data bits", you can choose between "7 bits" and "8 bits". Parity For "Parity", you can choose from "None", "Even", and "Odd". Stop bits For "Stop bits", you can choose between 1 and 2 bits. 3954 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs Parameters for the PLC Station address For "Station address", set the station number of the connected PLC. Connecting HMI device to PLC Connections via Omron Host Link Connection The connection of the HMI device to an OMRON PLC is limited primarily to the physical connection of the HMI device. Special blocks for the connection are not required in the PLC. Connection cable The following connecting cables are available to connect the HMI device to an Omron PLC. Interface to the HMI device Omron PLC RS232, 9-pin RS232 I/O port RS422, 9-pin RS422, terminals/ pins PP1 Programming cable (standard cable of Omron) -- -- RS232 via converter -- -- -- Multi-point cable 1 RS422, 9-pin -- -- PP2 Multi-point cable 2 RS232, 9-pin Refer to the relevant device manual to determine which HMI device interface is to be used. Communication types Approved communication types The connection from a HMI device to an OMRON-CPU with the Omron Host Link protocol via RS232 and via RS 422 is system-tested and approved by Siemens AG. This concerns the following CPU types: CP1x (CP1L, CP1H, CP1E) CJ1x (CJ1M, CJ1H, CJ1G) CJ2H WinCC Basic V13.0 System Manual, 02/2014 3955 Visualize processes 10.8 Communicating with PLCs CS1x (CS1G, CS1H, CS1D) CPM2C Note Only the following CPU types have been tested and released for Basic Panels, TP 177A and OP 77A: CP1x (CP1L, CP1H, CP1E) CJ1x (CJ1M, CJ1H, CJ1G) Multipoint connection A multipoint connection to the up to 4 approved OMRON PLCs in a RS422-four-wire connection can be implemented with communication modules on the PLCs and is system-tested and approved by Siemens AG. Note The HMI device can only be operated as a master. Exactly one master is possible in the RS422-four-wire-Multidrop connection. 3956 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs Connecting cable Connecting cable MP1, RS-232, over converter, for Omron Multipoint cable 1: MP/TP/PC > PLC +0,GHYLFH SLQ'VXEIHPDOH FRQQHFWRU 7[' 5[' *1' 2PURQ SLQ 'VXEPDOH FRQQHFWRU 9'&P$ ,QUXVKFXUUHQWPD[$ &RQYHUWHU 17$/ 56b56 5[' 7[' 6* 9 5 2Q 6'% 6'$ 5'% 5'$ SLQ'VXEPDOHFRQQHFWRU RU SLQVFUHZFRQQHFWLRQ 5 2II 5'% 5'$ 6'% 6'$ 5 2II 5'% 5'$ 6'% 6'$ 5 2II 5'% 5'$ 6'% 6'$ 5 2Q 5'% 5'$ 6'% 6'$ &,) 1) Inrush current max. 0.8 A shielded, max. length 500 m WinCC Basic V13.0 System Manual, 02/2014 3957 Visualize processes 10.8 Communicating with PLCs Connecting cable MP2, RS-422, for Omron Multipoint cable 2: RS422, MP/TP/PC > SPS_ +0,GHYLFH SLQ'VXEPDOHFRQQHFWRU 7[' 7[' 5[' 5[' 2PURQ SLQ'VXEPDOHFRQQHFWRU RU SLQVFUHZFRQQHFWLRQ 5 2Q 5'% 5'$ 6'% 6'$ 5 2II 5'% 5'$ 6'% 6'$ 5 2II 5'% 5'$ 6'% 6'$ 5 2Q 5'% 5'$ 6'% 6'$ &,) shielded, max. length 500 m Connecting cable PP1, RS-232, for Omron Point-to-point cable PP1, PC/TP/OP - PLC 3958 WinCC Basic V13.0 System Manual, 02/2014 '65 576 &76 7[' *1' 7[' 5[' 5[' HQFORVXUH &6 '5 5[' 7[' 7[' Visualize processes 6* 5[' 10.8 Communicating with PLCs 5 shielded, max. length 15 m Connecting cable PP2, RS-422, for Omron Point-to-point cable PP2, RS-422 ,QVHUWUHVLVWRURKPV!P: HJGHVLJQ shielded, max. length 500 m Performance features of communication Permissible data types for Omron Host Link Permitted data types The table lists the data types that can be used when configuring tags and area pointers. Data type Operand type Length Bool I/O, HR, AR, LR, DM, T/ C bit, CPU status 1-bit Byte CPU type 1 byte DInt HR, AR, LR, DM 4 bytes Int I/O, HR, AR, LR, DM, T/ C Val 2 bytes Real HR, DM 4 bytes String HR, AR, LR, DM 0 to 80 characters UDInt HR, AR, LR, DM 4 bytes UInt I/O, HR, AR, LR, DM, T/ C Val 2 bytes Note Read and write operations of all data areas in the OMRON PLC can only be reliably carried out in "STOP" or "MONITOR" mode. "I/O" refers either to the IR/SR area or the CIO area depending on the PLC series. The operand types "LR", "HR" and "AR" are not available in all PLC series. WinCC Basic V13.0 System Manual, 02/2014 3959 Visualize processes 10.8 Communicating with PLCs Note Note the following for write accesses: For the "Bool" data type with the operand types "I/O", "HR", "AR", "LR" and "DM", the entire word is written back into the PLC when the specified bit is changed. There is no check to determine whether any other bits in the word have changed. As a result, the PLC only has read access to the specified word. Operand type old PLC Operand type CS and CJ PLC CPU Status CPU Status I/O CIO HR H Range 0-511 AR A LR n/a 1) DM D T/C T/C CPU type CPU type 1) You do not get an error message when you read or write the LR area in the following PLCs CS CJ CP Supported CPU types for Omron Host Link CPU types The following CPU types are supported in the configuration of the Omron Host Link communication driver. CP1 - CP1L - CP1H - CP1E CJ1 - CJ1M - CJ1H - CJ1G 3960 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs CJ2 - CJ2H CS1 - CS1G - CS1H - CS1D CPM - CPM2C Addressing in Omron Host Link Addressing of PLCs in Omron Host Link In PLCs of the series CS, CP and CJ, the timers 0-4095 are addressed with T/C 0-2047. The counters 0-4095 must be addressed with an offset of 2048 (T/C 2048-4095 correspond to the counters 0-2047). Counters and timers with addresses > 2047 cannot be addressed via Host Link. Counters and timers with addresses > 2047 cannot be addressed via Host Link. Example: If you want to address counter C20, you must address T/C 20+2048 = T/C 2068. Address areas for Omron Host Link Omron Address areas Data types Bool Byte UInt Int UDInt DInt Real String I/O I/O 0.0 -I/O 9999.15 I/O 0 I/O 9999 I/O 0 I/O 9999 -- -- -- -- HR HR 0.0 HR 9999.15 HR 0 HR 9999 HR 0 HR 9999 HR 0 HR 9998 HR 0 - HR 9998 HR 0 HR 9999 HR 0 HR 9999 AR AR 0.0 AR 9999.15 AR 0 AR 9999 AR 0 AR 9999 AR 0 AR 9998 AR 0 AR 9998 AR 0 AR 9999 LR LR 0.0 LR 9999.15 LR 0 LR 9999 LR 0 LR 9999 LR 0 LR 9998 LR 0 LR 9998 LR 0 LR 9999 DM DM 0.0 DM 9999.15 DM 0 DM 9999 DM 0 DM 9999 DM 0 DM 9998 DM 0 DM 9998 T/C Bit T/C Bit 0 T/C Bit 4095 WinCC Basic V13.0 System Manual, 02/2014 DM 0 DM 9999 DM 0 DM 9999 3961 Visualize processes 10.8 Communicating with PLCs Address areas Data types Bool Byte T/C Val UInt Int T/C Val 0 T/C Val 4095 T/C Val 0 T/C Val 4095 UDInt DInt Real String CPU Status RUN, MONITOR CPU type CPU type Commissioning components Transferring a project to the HMI device 1. Switch the HMI device to "transfer mode". 2. Set all necessary transfer parameters. - Interface - Transfer parameters - Target storage location 3. Start the project transfer. The project is compiled automatically. All compilation and transfer steps are logged to a message window. Interconnecting the PLC with the HMI device 1. Interconnect the PLC with the HMI device using a suitable cable. 2. The message "Connection to PLC .... is established" is output to the HMI device. Optimizing the configuration Acquisition cycle and update time The acquisition cycles for the "Area pointers" and of the tags defined in the configuration software are decisive in terms of the update times which can actually be achieved. The update time is equivalent to the acquisition cycle + transmission time + processing time. Items to observe when optimizing the update times in configuration data: Optimize the maximum and minimum size of the data areas. Acquisition cycles which are too short lead to unnecessary load on overall performance. Set the acquisition cycle according to the rate of change of the process values. The rate of temperature changes at a furnace, for example, is significantly slower compared to the speed rate of an electrical drive. A time of approx. 1 second is a benchmark for the acquisition cycle. 3962 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs Avoid any gaps when entering the alarm or screen tags in a data area. Changes in the PLC can only be detected reliably if these are available at least within the actual acquisition cycle. Screens The refresh rate of screens is determined by the type and volume of data to be visualized. Only configure short acquisition cycles for objects which actually require shorter refresh cycles. This procedure reduces update times. Trends The HMI device always updates all bit-triggered trends whose group bit is set in the "Trend transfer area". It resets the bits in the next cycle. The group bit in the PLC program can only be set again after the HMI device has reset all bits. Job mailboxes A high rate and volume of job mailboxes transferred may lead to overload in communication between the HMI device and the PLC. The HMI device confirms acceptance of the job mailbox by entering the value zero in the first data word of the job mailbox. The HMI device now processes the job for which it requires a certain time slice. It may take the HMI device some time to process a new job mailbox which is transferred in immediate succession to the job mailbox. The next job mailbox is only accepted if sufficient computing resources are available. Data exchange Area pointers for Omron Area pointers in connections via Omron communication drivers You use an area pointer to access a data area in the PLC. For more detailed information on area pointers and their configuration, refer to Section: "Data exchange using area pointers". Special features of connections via Omron Host Link Area pointers can only be created in the following "File types": "DM", "I/O", "HR", "AR", and "LR". See also Data exchange using area pointers (Page 3967) WinCC Basic V13.0 System Manual, 02/2014 3963 Visualize processes 10.8 Communicating with PLCs Trends Trends A trend is the graphical representation of one or more values from the PLC. The value is read out time-triggered for Basic Panels. For additional information see: Configuring trend displays for values from the PLC (Page 3369) Time-triggered trends The HMI device reads in the trend values cyclically at an interval specified in the configuration. Time-triggered trends are suitable for continuous curves, such as the operating temperature of a motor. Alarms Configuring alarms Configuring alarms for non-integrated connections Several steps are necessary to configure alarms such as warnings, error messages and acknowledgement. Step 1: Create tags Step 2: Configure alarms Step 3: Configure acknowledgment You can find additional information in the section: Working with alarms (Page 3379) Distinctive features when configuring alarms If you are configuring connections of HMI devices to PLCs of other manufacturers, note the following distinctive features when configuring: Data types of the tags Addressing of tags How the bit positions are counted 3964 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs Data types For connections with an Omron communication driver, the following data types are supported: PLC Permitted data types Discrete alarms Analog alarms Uint, int UInt, Int, UDInt, DInt CP1, CJ1, CJ2, CS1, CPM How the bit positions are counted For connections with an Omron communication driver, the following counting method applies: How the bit positions are counted Left byte Right byte In Omron PLCs 15 8 7 0 In WinCC you configure: 15 8 7 0 Only tags for the "DM", "I/O", "HR", "AR", and "LR" file types are allowed for use as a trigger tag for discrete alarms. Configuring discrete alarms Use arrays for discrete alarms and append each individual alarm to one bit of the array tags themselves and not to the individual subelements. Only tags for the "DM", "I/O", "HR", "AR", LR" areas and the "Int" and "UInt" file types are permitted for discrete alarms and arrays. Acknowledgment of alarms Procedure Create suitable tags on the PLC to acknowledge an error alarm. You assign these tags to an alarm in the "Bit messages" editor. You make the assignment in "Properties > Acknowledgment". Distinction in terms of acknowledgment: Acknowledgment by the PLC Acknowledgment on the HMI device Acknowledgment by the PLC In "PLC acknowledgment tag", configure the tag or array tag and the bit number that the HMI device uses to identify a PLC acknowledgment. WinCC Basic V13.0 System Manual, 02/2014 3965 Visualize processes 10.8 Communicating with PLCs A bit set in the tag triggers acknowledgment of the assigned error alarm bit at the HMI device. This tag bit returns a function similar to acknowledgment on the HMI device which is triggered by pressing the "ACK" button, for example. The acknowledgment bit must be located in the same tag as the bit for the error alarm. Reset the acknowledgment bit before setting the bit in the alarm area again. The figure below shows the pulse diagram. (UURUDODUP $FNQRZOHGJPHQW 3/&+0,GHYLFH $UULYDORIWKH $FNQRZOHGJP 5HVHWRI HUURUDODUP YLD3/& DFNQRZOHGJPELW 1HZ HUURUDODUP Acknowledgment on the HMI device In the "HMI acknowledgment tag" area, configure the tag or array tag as well as the bit number that the HMI device writes to the PLC after acknowledgment. Make sure when you use an array tag that it is not longer than 6 words. To always create a signal change when setting an assigned acknowledgment bit of a discrete alarm that must be acknowledged, the HMI device will reset the acknowledgment bit assigned to the alarm as soon as it detects an alarm subject to acknowledgment and write the acknowledgment tag in the PLC. There will be a certain delay between detecting the message and writing the acknowledgment tag in the PLC because the HMI device has to process the operations. If a discrete alarm subject to acknowledgment is acknowledged by the HMI device, then the corresponding bit in the assigned acknowledgment tag will be set. The entire acknowledgment tag is then written to the PLC by the HMI device. This allows the PLC to recognize that a certain alarm message has been acknowledged at the HMI device. Note All alarm bits acknowledged since the last Runtime start will remain in the acknowledgment tag until a new incoming of the respective discrete alarms is detected. This area should only be read by the PLC because the entire section of the HMI device will be overwritten once the next acknowledgment tag is written. The figure below shows the pulse diagram. 3966 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs (UURUDODUP $FNQRZOHGJPHQW +0,GHYLFH3/& $UULYDORIWKH HUURUDODUP 5HVHWRI DFNQRZOHGJPELW $FNQRZOHGJP YLD+0,GHYLFH 1HZ HUURUDODUP Communication Service Packages 10.8.11.4 Data exchange using area pointers General information on area pointers Introduction You use an area pointer to access a data area in the PLC. During communication, the PLC and the HMI device alternately access these data areas for read and write operations. The PLC and the HMI device trigger defined interactions based on the evaluation of stored data. Configuration of area pointers Before you use the area pointer, you enable it in "Connections Area pointers". You then assign the area pointer parameters. WinCC Basic V13.0 System Manual, 02/2014 3967 Visualize processes 10.8 Communicating with PLCs Active Enables the area pointer. Pointer name Name of the area pointer specified by WinCC. PLC tag Here you select the PLC tag or the tag array that you have configured as the data area for the area pointer. Address No address is entered into this field because of the symbolic access. Length WinCC specifies the length of the area pointer. Acquisition cycle You specify the acquisition cycle in this field for area pointers that are read by the HMI device. Note that a very short acquisition time may have a negative impact on HMI device performance. Comment Enter a comment, for example, to describe the purpose of the area pointer. Accessing data areas Accessing data areas The following table shows how HMI devices and PLCs access individual data areas for read (R) or write (W) operations. Data area Required for HMI device PLC Screen number Evaluation by the PLC in order to determine the active screen. W R Data record Transfer of data records with synchronization Date/time Transfer of the date and time from the HMI device to the PLC R/W R/W W R Date/time PLC Transfer of the date and time from the PLC to the HMI device R W Coordination Requesting the HMI device status in the PLC program W R Project ID Runtime checks for consistency between the WinCC project ID and the project in the PLC R W Job mailbox Triggering of HMI device functions by the PLC program R/W R/W "Screen number" area pointer Function The HMI device saves information about the screen called on the HMI device to the "Screen number" area pointer. 3968 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs This allows the transfer of the current screen contents from the HMI device to the PLC. The PLC can trigger specific reactions such as the call of a different screen. Use Configure and enable the area pointer in "Communication > Connections" before you put it into use. You can create only one instance of the "Screen number" area pointer and only on one PLC. The screen number is always transferred to the PLC when a new screen is activated or when the focus within a screen changes from one screen object to another. Structure The area pointer is a data area in the memory of the PLC with a fixed length of 5 words. 15 14 13 12 11 10 9 8 7 6 1. word Current screen type 2. word Current screen number 3. word Reserved 4th word Current field number 5. word Reserved 5 4 3 2 1 0 Current screen type "1" for root screen or "4" for permanent window Current screen number 1 to 32767 Current field number 1 to 32767 "Date/time" area pointer Function This area pointer is used to transfer the date and time from the HMI device to the PLC. The PLC writes control job "41" to the job mailbox. When it evaluates the control job, the HMI device writes its current date and the time in the data area configured in the "Date/time" area pointer. All definitions are coded in BCD format. WinCC Basic V13.0 System Manual, 02/2014 3969 Visualize processes 10.8 Communicating with PLCs The "Date/Time" area pointer when used in a project which contains multiple connections must be enabled for each configured connection. Note You cannot use the "Date/Time PLC" area pointer if you have configured the "Date/Time" area pointer. The date/time data area has the following structure: Data word Left byte 15 Right byte 8 7 0 n+0 Reserved Hour (0 to 23) n+1 Minute (0 to 59) Second (0 to 59) n+2 Reserved Reserved n+3 Reserved Weekday (1 to 7, 1=Sunday) n+4 Day (1 to 31) Month (1 to 12) n+5 Year (80 to 99/0 to 29) Reserved Time Date Note When making entries in the "Year" data area, you should note that values 80 to 99 result in years 1980 through 1999, while the values 0 to 29 result in the years 2000 through 2029. "Date/time PLC" area pointer Function This area pointer is used to transfer the date and time from the PLC to the HMI device. Use this area pointer if the PLC is the time master. The PLC loads the data area of the area pointer. All definitions are coded in BCD format. The HMI device reads the data cyclically within the configured acquisition cycle and synchronizes itself. Note Set an acquisition cycle of sufficient length for the Date/time area pointer in order to avoid any negative impact on HMI device performance. Recommended: Acquisition cycle of 1 minute if your process can handle it. 3970 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs "Date/Time PLC" is a global area pointer and may be configured only once per project. Note You cannot use the "Date/Time" area pointer if you have configured the "Date/Time PLC" area pointer. The "Date/time PLC" data area has the following structure: Data word Left byte 15 n+0 1) ...... Right byte 8 7 ...... Year (80 to 99/0 to 29) 0 Month (1 to 12) n+1 Day (1 to 31) Hour (0 to 23) n+2 Minute (0 to 59) Second (0 to 59) n+3 Reserved n+4 1) Reserved Reserved n+5 1) Reserved Reserved Reserved Weekday (1 to 7, 1=Sunday) The two data words must exist in the data area to ensure that the data format matches WinCC and to avoid reading false information. Note When making entries in the "Year" data area, you should note that values 80 to 99 result in years 1980 through 1999, while the values 0 to 29 result in the years 2000 through 2029. "Coordination" area pointer Function The "Coordination" area pointer is used to implement the following functionality: Detecting the startup of the HMI device in the control program detection in the control program of the current HMI device operating mode detection in the control program of the HMI devices ready to communicate state The "Coordination" area pointer has a length of one word. WinCC Basic V13.0 System Manual, 02/2014 3971 Visualize processes 10.8 Communicating with PLCs Use Note The HMI device always writes the entire coordination area when updating the area pointer. The control program may not make changes to the coordination area for this reason. Assignment of bits in the "Coordination" area pointer ORZRUGHUE\WH KLJKRUGHUE\WH VWZRUG VWZRUGQRWDVVLJQHG UHVHUYHG [ DVVLJQHG ; ; ; 6WDUWXSELW 2SHUDWLRQPRGH /LIHELW Startup bit The startup bit is set briefly to "0" by the HMI device during startup. It sets the bit permanently to "1" when startup is completed. Operating mode The operating mode bit is set to 1 as soon as the user switches the HMI device offline. The state of the operating mode bit is "0" during normal operation of the HMI device. You can determine the current operating mode of the HMI device by reading this bit. Life bit The HMI device inverts the life bit at intervals of approximately one second. You can check whether or not the connection to the HMI device is still up by querying this bit in the control program. "Project ID" area pointer Function You can check whether the HMI device is connected to the correct PLC at the start of runtime. This check is important when operating with several HMI devices. The HMI device compares a value stored on the PLC with the value specified in configuration. This ensures compatibility of configuration data with the control program. If discrepancy is detected, a system event is displayed on the HMI device and runtime is stopped. 3972 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs Use To use this area pointer, set up the following during the configuration: Define the version of configuration. Possible values between 1 and 255. You enter the version in the editor "Runtime settings > General" in the "Identification" area. Data address of the value for the version that is stored in the PLC: You enter the data address in the editor "Communication > Connections". Connection failure A connection failure to a device on which the "project ID" area pointer is configured results in all the other connections in the project being switched to "offline". This behavior has the following prerequisites: You have configured several connections in a project. You are using the "project ID" area pointer in at least one connection. Causes which may set connections "offline": The PLC is not available. The connection has been switched offline in the engineering system. "PLC job" area pointer Function The PLC can use the job mailbox to transfer jobs to the HMI device to trigger corresponding actions on the HMI device. These functions include, for example: Display screen Set date and time Data structure The first word of the job mailbox contains the job number. Depending on the job mailbox, up to three parameters can be transferred. Word Left byte Right byte n+0 0 Job number n+1 Parameter 1 n+2 Parameter 2 n+3 Parameter 3 The HMI device evaluates the job mailbox if the first word of this job is not equal to zero. This means that the parameters must be entered in the job mailbox first, followed by the job number. WinCC Basic V13.0 System Manual, 02/2014 3973 Visualize processes 10.8 Communicating with PLCs When the HMI device accepts the job mailbox, the first word is set to 0 again. The execution of the job mailbox is generally not completed at this point in time. Job mailboxes All job mailboxes and their parameters are listed below. The "No." column contains the job number of the job mailbox. Job mailboxes can only be triggered by the PLC when the HMI device is online. Note Please note that not all HMI devices support job mailboxes. No . Function 14 Setting the time (BCD coded) 15 23 Parameter 1 Left byte: Right byte: hours (0-23) Parameter 2 Left byte: minutes (0-59) Right byte: seconds (0-59) Parameter 3 - Setting the date (BCD coded) Parameter 1 Left byte: Right byte: weekday (1-7: Sunday-Saturday) Parameter 2 Left byte: day (1-31) Right byte: month (1-12) Parameter 3 Left byte: year User logon Logs the user on with the name "PLC user" at the HMI device with the group number transferred in Parameter 1. The logon is possible only when the transferred group number exists in the project. 24 Parameter 1 Group number 1 to 255 Parameter 2, 3 - User logoff Logs off the current user. (The function corresponds to the "logoff" system function) Parameter 1, 2, 3 40 - Transfer date/time to PLC (in the S7 format DATE_AND_TIME) An interval of at least 5 seconds must be maintained between two successive jobs to prevent overload of the HMI device. Parameter 1, 2, 3 41 - Transfer date/time to PLC (In OP/MP format) An interval of at least 5 seconds must be maintained between successive jobs in order to prevent overload of the HMI device. 3974 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs No . Function 14 Setting the time (BCD coded) Parameter 1, 2, 3 46 - Update tags Causes the HMI device to read the current value of the tags*from the PLC whose update ID matches the value transferred in parameter 1. (Function corresponds to the "UpdateTag" system function.) Parameter 1 49 1 - 100 Delete alarm buffer Deletes all analog alarms and discrete alarms of the "Warnings" class from the alarm buffer. Parameter 1, 2, 3 50 - Delete alarm buffer Deletes all analog alarms and discrete alarms of the "Errors" class from the alarm buffer. Parameter 1, 2, 3 51 69 - Screen selection 1) Parameter 1 Screen number Parameter 2 - Parameter 3 Field number Read data record from PLC Parameter 1 Recipe number (1-999) Parameter 2 Data record number (1-65535) Parameter 3 0: Do not overwrite existing data record 1: Overwrite existing data record 70 1) Write data record to PLC Parameter 1 Recipe number (1-999) Parameter 2 Data record number (1-65535) Parameter 3 - OP 73, OP 77A and TP 177A HMI devices also execute the "Screen selection" job mailbox if the on-screen keyboard is active. "Data record" area pointer "Data mailbox" area pointer Function When data records are transferred between the HMI device and PLC, both partners access common communications areas on the PLC. WinCC Basic V13.0 System Manual, 02/2014 3975 Visualize processes 10.8 Communicating with PLCs Data transfer types There are two ways of transferring data records between the HMI device and PLC: Transfer without synchronization Transfer with synchronization over the data record Data records are always transferred directly. That is, the tag values are read from an address or written to an address configured for this tag directly, without redirecting the values by means of interim memory. Initiating the transfer of data records There are three ways of triggering the transfer: Operator input in the recipe view Job mailboxes The transfer of data records can also be triggered by the PLC. Triggering by configured functions If the transfer of data records is triggered by a configured function or by a job mailbox, the recipe view on the HMI device remains operable. The data records are transferred in the background. Simultaneous processing of several transfer requests is, however, not possible. In this case, the HMI device rejects the other transfer requests with a system event. Transfer without synchronization If you select asynchronous transfer of data records between the HMI device and PLC, there is no coordination over the common data areas. It is therefore unnecessary to set up a data area during configuration. Asynchronous data record transfer can be a useful alternative, for example, when: The system is capable of excluding the risk of uncontrolled overwriting of data by the communication peer. The PLC does not require information about the recipe number and data record number. The transfer of data records is triggered by the operator of the HMI device. Reading values When a read job is triggered, the values are read from the PLC addresses and transferred to the HMI device. Triggering by the operator in the recipe view: The values are downloaded to the HMI device. You can then process, edit, or save these values, for example. Triggering by a function or job mailbox: The values are saved immediately to the data volume. 3976 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs Writing values When a write job is triggered, the values are written to the PLC addresses. Triggering by the operator in the recipe view: The current values are written to the PLC. Triggering by a function or job mailbox: The current values are written to the PLC from the data medium. Transfer with synchronization If you select synchronous transfer, both communication partners set status bits in the common data area. You can use this mechanism to prevent uncontrolled overwriting of data in either direction in your control program. Application Synchronous data record transfer can be a useful solution, for example, when: The PLC is the "active partner" in the transfer of data records. The PLC evaluates the information about the recipe number and data record number. The transfer of data records is triggered by means of a Job mailbox. Requirements In order to synchronize transfer of data records between the HMI device and the PLC, the following requirements must be met during configuration: An area pointer has been set up: "Communication > Connections" editor in "Area pointer". The PLC with which the HMI device synchronizes transfer of data records is specified in the recipe: "Recipes" editor in the inspector window the option "Coordinated transfer of data records" under "General > Synchronization > Settings" Structure of the data area The data area has a fixed length of 5 words. Structure of the data area: 15 WinCC Basic V13.0 System Manual, 02/2014 0 1. Word Current recipe number (1 - 999) 2. Word Current data record number (0 - 65535) 3. Word Reserved 4. Word Status (0, 2, 4, 12) 5. Word Reserved 3977 Visualize processes 10.8 Communicating with PLCs Status The status word (word 4) can adopt the following values: Value Meaning Decimal Binary 0 0000 0000 Transfer permitted, data record free 2 0000 0010 Transferring. 4 0000 0100 Transfer completed without error 12 0000 1100 Transfer completed with error Sequence of a transfer started by the operator in the recipe display Reading from the PLC started by the operator in the recipe view Step Action 1 Check: Status word = 0? Yes No 2 The HMI device enters the recipe number to be read and the status "Transferring" in the data record and sets the data record number to 0. Abort with system event. 3 The HMI device reads the values from the PLC and displays them in the recipe view. If the recipes have synchronized tags, the values from the PLC are also written to the tags. 4 The HMI device sets the status "Transfer completed." 5 The control program must reset the status word to zero in order to enable further transfers. Writing to the PLC started by the operator in the recipe view Step Action Check: Status word = 0? 1 Yes The HMI device enters the recipe and data record number to be written and the status "Transferring" in the data record. 2 No Abort with system event. The HMI device writes the current values to the PLC. If the recipes have synchronized tags, the changed values are synchronized between the recipe view and tags and then written to the PLC. 3978 3 The HMI device sets the status "Transfer completed." 4 If required, the control program can now evaluate the transferred data. 5 The control program must reset the status word to zero in order to enable further transfers. WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs Note The status word may only be set by the HMI device. The PLC may only reset the status word to zero. Note The PLC may only evaluate the recipe and data record numbers when data inconsistency is detected if one of the conditions outlined below has been met: The data mailbox status is set to "Transfer completed". The data mailbox status is set to "Transfer completed with error". Sequence of the transfer triggered by a PLC job The transfer of data records between the HMI device and the PLC can be initiated by either one of these stations. The two job mailboxes No. 69 and No. 70 are available for this type of transfer. No. 69: Read data record from PLC ("PLC DAT") Job mailbox no. 69 transfers data records from the PLC to the HMI device. The job mailbox is structured as follows: Left byte (LB) Right byte (RB) 0 69 Word 1 Word 2 Recipe number (1-999) Word 3 Data record number (1 to 65535) Word 4 Do not overwrite existing data record: 0 Overwrite existing data record: 1 No. 70: Write data record to PLC ("DAT PLC") Job mailbox No. 70 transfers data records from the HMI device to the PLC. The job mailbox is structured as follows: Left byte (LB) Word 1 WinCC Basic V13.0 System Manual, 02/2014 Right byte (RB) 0 70 Word 2 Recipe number (1-999) Word 3 Data record number (1 to 65535) Word 4 -- 3979 Visualize processes 10.8 Communicating with PLCs Sequence when reading from the PLC with job mailbox "PLC DAT" (no. 69) Step Action 1 Check: Status word = 0? Yes No 2 The HMI device enters the recipe and data record number specified in the job and the status "Transferring" in the data record. Abort without return message. 3 The HMI device reads the values from the PLC and saves these to the data record defined in the job mailbox. 4 If "Overwrite" was selected in the job, an existing data record is overwritten without any prompt for confirmation. The HMI device sets the status "Transfer completed." If "Do not overwrite" was selected in the job, and the data record already exists, the HMI device aborts the job and enters 0000 1100 in the status word of the data record. 5 The control program must reset the status word to zero in order to enable further transfers. Sequence of writing to the PLC with job mailbox "DAT PLC" (no. 70) Step Action 1 Check: Status word = 0? Yes No 2 The HMI device enters the recipe and data record number specified in the job and the status "Transferring" in the data record. Abort without return message. 3 The HMI device fetches the values of the data record specified in the function from the data medium and writes the values to the PLC. 4 The HMI device sets the status "Transfer completed." 5 The control program can now evaluate the transferred data. The control program must reset the status word to zero in order to enable further transfers. Sequence of the transfer when triggered by a configured function Reading from the PLC using a configured function 3980 Step Action 1 Check: Status word = 0? Yes No 2 The HMI device enters the recipe and data record number specified in the function and the status "Transferring" in the data record. Abort with system event. 3 The HMI device reads the values from the PLC and stores them in the data record specified in the function. WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.8 Communicating with PLCs Step 4 Action If "Yes" was selected for the "Overwrite" function, an existing data record is overwritten without any prompt for confirmation. The HMI device sets the status "Transfer completed." If "No" was selected for the "Overwrite" function and the data record already exists, the HMI device aborts the job and enters 0000 1100 in the status word of the data record. 5 The control program must reset the status word to zero in order to enable further transfers. Writing to the PLC by means of configured function Step Action 1 Check: Status word = 0? Yes No 2 The HMI device enters the recipe and data record number specified in the function and the status "Transferring" in the data record. Abort with system event. 3 The HMI device fetches the values of the data record specified in the function from the data medium and transfers the values to the PLC. 4 The HMI device sets the status "Transfer completed." 5 The control program can now evaluate the transferred data. The control program must reset the status word to zero in order to enable further transfers. Possible causes of error when transferring data records Possible causes of error The section below shows possible error causes which lead to the cancellation of data record transfer: Tag address not set up on the PLC Overwriting data records not possible WinCC Basic V13.0 System Manual, 02/2014 3981 Visualize processes 10.9 Using global functions Recipe number does not exist Data record number does not exist Note The status word may only be set by the HMI device. The PLC may only reset the status word to zero. Note The PLC may only evaluate the recipe and data record numbers when data inconsistency is detected if one of the conditions outlined below has been met: The data mailbox status is set to "Transfer completed". The data mailbox status is set to "Transfer completed with error". Reaction to an aborted transfer due to errors If the transfer of data records is aborted due to errors, the HMI device reacts as follows: Triggering by the operator in the recipe view Information in the status bar of the recipe view and output of system alarms Triggered by function Output of system alarms Triggering by job mailbox No return message on the HMI device You can nonetheless evaluate the status of the transfer by querying the status word in the data record. 10.9 Using global functions 10.9.1 HMI device wizard basics Introduction The HMI device wizard will automatically start when you create a new HMI device in your project. 3982 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.9 Using global functions 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. 10.9.2 Working with libraries 10.9.2.1 Basics on libraries Introduction Store all objects you need frequently in the libraries. An object that is stored in the library only has to be configured once. It can then be used repeatedly as often as required. Library objects extend the number of available screen objects and increase the effectiveness during configuration through the multiple usage of ready-to-use objects. WinCC Basic V13.0 System Manual, 02/2014 3983 Visualize processes 10.9 Using global functions Your WinCC software package is supplied with comprehensive libraries that contain, for example, "Motor" or "Valve" objects. You may, however, define your own library objects. You manage libraries in the "Libraries" task card or library view. The following libraries are available: Project library Global libraries Note There is a symbol library in the "Tools" task card in the "Graphics" palette. Project library There is one library for each project. Objects of the project library are stored alongside with the project data and are available only for the project in which the library was created. If the project is moved to another PC, any project library created in it is also moved. To use the library object of the project library in other objects, move or copy the object into a global library. Global libraries A global library is saved independently of the project data in its own file with the extension *.aI12. 3984 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.9 Using global functions A project can access several global libraries. A global library may be used concurrently in several projects. When a library object is changed by a project, this library will be changed in all projects in which these libraries are open. Library objects A library can contain all WinCC objects. Examples: Complete HMI device Screens Display and control objects including tags and functions Graphics Tags Alarms Text and graphics lists Faceplates User data types See also Copy templates and types (Page 3987) 10.9.2.2 Overview of the library view Function of the library view The library view combines the functionality of the "Libraries" task card and the overview window. In the library view, the elements of a library are displayed in various views. In the details view, for example, you see additional properties of the individual elements. You can also edit and version the types in the library view. WinCC Basic V13.0 System Manual, 02/2014 3985 Visualize processes 10.9 Using global functions Layout of the library view The following figure shows the components of the library view: 1 Library tree 2 Library overview 3 "Library view" button 4 "Open or close library overview" button Library tree The library tree is similar to the "Libraries" task card, apart from a few minor differences. In contrast to the task card, there is no "Elements" palette, because the elements are displayed in the library overview. In addition, you can close the library view in the library tree, or open and close the library overview. 3986 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.9 Using global functions Library overview The library overview corresponds to the overview window and displays the elements of the currently selected object in the library tree. You can display the elements in three different views. You can also perform the following actions in the library overview, for example: Copying elements Moving elements Versioning types Editing faceplates and HMI user data types Editing type instances 10.9.2.3 Copy templates and types Introduction Both the "Project library" and the "Global library" contain the two folders "Master copies" and "Types". You can create or use the library objects either as a master copy or a type. Master copies Use master copies to create independent copies of the library object. Types Create instances of objects of the "Types" folder and use these in your project. The instances are bound to their respective type. Administration of the library objects You can copy and move library objects to another library. You can only copy master copies to the "Master copies" folder or any sub-folder of "Master copies". You can also only insert types in the "Types" folder or any sub-folder of "Types". See also Basics on libraries (Page 3983) State of type versions (Page 4001) WinCC Basic V13.0 System Manual, 02/2014 3987 Visualize processes 10.9 Using global functions 10.9.2.4 Libraries in WinCC Introduction The WinCC software package includes extensive libraries. Sorted by topic into folders, they contain preassembled graphic objects which you can use in screens for operation and monitoring of your plant. Global library "Buttons and Switches" The libraries "Buttons and Switches" offer a wide selection of buttons and switches. The folders divide switches and buttons into categories. The "DiagnosticsButtons" folder contains the object "System diagnostics indicator", for example. You use the "System diagnostics indicator" object for system diagnostics in your plant. Note You can only use the objects in the "DiagnosticsButtons" folder on Comfort Panels. You cannot use objects which have "Switch" in the object name or in the associated folder name in Runtime Professional. 3988 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.9 Using global functions Global library "Monitoring and Control objects" The "Monitoring and Control objects" library offers more complex display and operating objects in several designs and corresponding control lights, buttons and switches. In addition, graphics views for the designs are stored in the "Design_Backgrounds" folder; they can be used as object backgrounds for the custom extension of the scope of the library. Note You cannot use objects which have "Switch" in the object name in Runtime Professional. The same applies for the object "D5_Display_3" with the date/time field it contains. 10.9.2.5 Managing libraries Overview of the library management Function of the library management Master copies and types with dependencies to other library elements are subject to some functional restrictions. They can, for example, not be deleted as long as dependencies still WinCC Basic V13.0 System Manual, 02/2014 3989 Visualize processes 10.9 Using global functions exist. This prevents other library elements from becoming useless. The library management is used to identify the dependencies and to create an overview of the work progress. The library management offers the following functions: Display of the correlations of types and master copies If a type is referenced in other types or master copies, the correlations are displayed in the library management. You will also be able to see which library elements reference a type or a master copy. Display of points of use of types in the project Display all types that include a version with the "In testing" or "In progress" status Layout of the library management The following figure shows the components of the library management: 3990 Toolbar of the library management "Types" area "Uses" area WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.9 Using global functions Toolbar of the library management You can perform the following tasks in the toolbar of the library management: Update view If the project was changed, you can update the view of the library management. Clean up library You can clean up the project library and global libraries. By cleaning up a library, you delete all types and type versions that are not linked to an instance in the project. Harmonize project By harmonizing a project, you adapt the names and the path structures of type uses in the project to the corresponding names and path structures of the types within a library. "Types" area The "Types" area displays the contents of the folder that you have selected in the library view. You can open or close all types by using the buttons in the toolbar of the "Types" area. You can also use the "Filter" drop-down list to filter the view and display all types with the "In testing" or "In progress" status only. For each type, the types that it references are displayed. "Uses" area The "Uses" area gives you an overview of the points of use of the selected types and master copies. The "Uses" area is divided into two tabs: "Uses in the project" tab The "Uses in the project" tab is used to show the instances of type versions and their respective point of use in the project. When you select an instance, you can show the cross references of the instance in the project in the Inspector window. "Uses in the library" tab The "Uses in the library" tab is used to show all points within the library at which a type or a master copy is used. Opening library management Procedure To open the library management, follow these steps: 1. Open the library view. 2. Select a type or any folder that contains types. 3. Select the "Library management" command from the shortcut menu. Result The library management opens and the types are displayed with their versions. WinCC Basic V13.0 System Manual, 02/2014 3991 Visualize processes 10.9 Using global functions Filtering types in the library management Introduction A filter function in the library management enables you to limit the displayed types. The following filters are available: Display all types that include a version with "in progress" status Display all types that have no instances in the project Display all types that have more than one version Display all released types Requirement At least one type has been created. Filtering for all types with "in progress" status 1. Select the "Types" folder in the project library. 2. Select the "Library Management" command in the shortcut menu of the "Types" folder. The library management opens. 3. Select "Pending changes" from the "Filter" drop-down list. The "Types" area only displays types that have the "in progress" status. Filtering for all types that have no instances in the project 1. Select the "Types" folder in the project library. 2. Select the "Library Management" command in the shortcut menu of the "Types" folder. The library management opens. 3. Select "No instances in project" from the "Filter" drop-down list. "Not used in project" or "No instances in the project"? The "Types" area only displays types that have the "in progress" status. Filtering for types with multiple versions 1. Select the "Types" folder in the project library. 2. Select the "Library Management" command in the shortcut menu of the "Types" folder. The library management opens. 3. Select "Multiple versions" from the "Filter" drop-down list. 4. The "Types" area only displays types that have more than one version. 3992 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.9 Using global functions Filtering for all released types 1. Select the "Types" folder in the project library. 2. Select the "Library Management" command in the shortcut menu of the "Types" folder. The library management opens. 3. Select "Released types" from the "Filter" drop-down list. The "Types" area only displays types that have released versions. See also Opening library management (Page 3991) Creating a global library Introduction In the libraries you store the configured objects that you want to use several times in your configuration. To use objects in several projects, create a global library. Requirement A project is open. The "Libraries" task card is displayed or the "Library view" is open. Procedure 1. Click the icon under "Global library". The "Create new global library" dialog opens. 2. Enter a name. 3. Select the path where the new library is to be stored. 4. Click "Create". WinCC Basic V13.0 System Manual, 02/2014 3993 Visualize processes 10.9 Using global functions Result The new library is shown in the "Global libraries" palette. The global library contains the "Types", "Master copies" and "Common data" folders. Under the "Common data" you can find reports for the global library. A folder with the name of the global library is created in the file system at the storage location of the global library. This actual library file is given the file name extension ".al12". Saving a global library Introduction A global library is stored in a separate file on your hard disk drive. The file contains the objects of the global library including the referenced objects. E.g. the reference of a tag which was configured on an I/O field is also saved in the library. WinCC prompts you to save the global libraries when you close WinCC or your project without saving. You also can store the global library during configuration, without storing the entire project. Requirement You have opened a project which contains at least one library. The "Libraries" task card is displayed or the library view is open. A library has been changed. Procedure 1. Select the global library that you want to save. 2. Click the icon in the "Global library" palette. You can alternatively select the "Save Library" command in the shortcut menu. If you want to store the global library in a different folder, select "Save as" in the shortcut menu. Select the path in which you want to store the new library and enter a file name. Result The global libraries are saved under their current file name or a file name you have specified. Opening a global library Introduction In WinCC, the global libraries are stored in separate files. You can use a global library in every project. 3994 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.9 Using global functions Requirement You have saved a global library. A project is open. The "Libraries" task card is displayed or the library view is open. Procedure 1. Click the icon in the "Global library" palette. The "Open global library" dialog box is displayed. 2. Select the path in which the library is stored. 3. Click "Open". Note To have the access to a global library from multiple projects, open the global library readonly. As soon as a global library is not opened read-only, access from other projects is blocked. Result WinCC displays the opened global library in the "Global library" palette. Displaying logs of global libraries Logs listing all changes made to the global library are created when global libraries are updated. The logs are stored together with the global library and are always available once you have opened the global library. Procedure To open the logs of a global library, follow these steps: 1. Open the global library in the "Libraries" task card or in the library view. 2. Open "Common data > Logs" in the lower-level folder. 3. Double-click the required log. The log opens in the work area. Updating a project with the contents of a library Introduction After you have edited several types in the project library, update all instances in the project to the most recent version of the types from the project library. WinCC Basic V13.0 System Manual, 02/2014 3995 Visualize processes 10.9 Using global functions Requirement The "Libraries" task card or the library view is open. Procedure 1. Select the project library. 2. Select "Update > Project" from the shortcut menu. A dialog opens. 3. Select either the entire project or individual devices for the update. 4. Select the "Delete all unused versions of affected types" check box to delete all older versions of the updated types from the project library. 5. Click "OK" to confirm. Result All instances of the types are updated in the project to the most recent version of the selected types in the project library. You can find a log of the update process in the project tree under "Common data". Updating a library with the contents of another library The following options are available for updating libraries: Updating a global library with types from another global library Updating the project library with types from a global library Each of the following elements can be selected as source for the update: An entire library Individual folders within a library Individual types Requirement To update a global library, open the library with write rights. Requirement The "Libraries" task card or the library view is open. Procedure To update a library with the contents of a different library, follow these steps: 1. Select the entire library or a folder within the library or individual types. 2. Right-click the source and select the "Update > Library" command from the shortcut menu. The "Update library" dialog box opens. 3996 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.9 Using global functions 3. Select the type of library you want to update: - Select "Update the project library" to update the project library with types from a global library. - Select "Update a global library" if you want to update a global library. 4. Optional: Select the global library you want to update from the drop-down list. 5. Select the "Delete all unused versions of affected types" check box to delete all older versions of the updated types from the project library. 6. Click "OK" to confirm. Result Types not yet available in the target library are supplemented there with all their versions. More recent versions are added to the types that already exist in the target library. If a more recent version of a type already exists in the target library, the latest version is nevertheless copied and automatically assigned a newer version number. A log listing all performed changes to the target library is created for the update process. If you have updated the project library, you can find the log in the project tree under "Common data > Logs". If you have updated a global library, you can find the log in the "Common data > Logs" folder in the level below the global library. 10.9.2.6 Managing objects in a library Displaying library objects Introduction The libraries are displayed as file folders in the corresponding palette. The elements contained in the library are displayed in the file folder and in the "Elements" palette. Requirement At least one library object has been created in a library. The "Libraries" task card is opened. WinCC Basic V13.0 System Manual, 02/2014 3997 Visualize processes 10.9 Using global functions Procedure 1. Select the library in the corresponding palette whose library objects you want to display. 2. Click . The contained library objects are displayed in the "Elements" palette. 3. Click one of the following icons: 3998 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.9 Using global functions Icon Description Element view in detailed mode Element view in list mode Element view in overview mode with icons When several objects are assigned to the library with a multiple selection, only one of the objects is shown in the "Elements" palette. The individual components of this element are displayed in the "Parts" palette. Show parts of the library objects 1. Select the library in the corresponding palette from which you want to view the components of an element. 2. Click . 3. The contained library objects are displayed in the "Elements" palette. 4. Select the element. The "Parts" palette shows the objects of which the element consists. Result The library objects are displayed in accordance with the configuration. The components of the faceplates are displayed. WinCC Basic V13.0 System Manual, 02/2014 3999 Visualize processes 10.9 Using global functions Storing an object in a library Introduction You can store all of WinCC objects, such as screens, tags, graphic objects or alarms in your libraries. You can use drag-and-drop to move the corresponding object from the work area, project window or detail view to the library. In a library you have divided into categories, you can directly add objects to a specific category. Requirement The "Screens" editor is open. A screen object has been created in the work area of the screen. The created libraries are displayed. Procedure 1. Select the object in the work area of the "Screens" editor. 2. Drag-and-drop the object from the work area to the desired library. The mouse pointer is transformed into a crosshair with an appended object icon. Result The object is saved to the library for further use in multiple instances of your configuration. Inserting a library object Introduction The system always assigns the inserted library object a name which consists of the name of the object type and of a consecutive number. 4000 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.9 Using global functions If the inserted object already exists, you have the option of replacing the object or of saving it under a new name. You cannot insert library objects that are not supported by the HMI device. Note If you insert a screen with interconnected template from the library, the template will also be inserted. Any existing matching template is not used. Requirement The "Libraries" task card is opened. The editor in which you want to insert the library object is open. Procedure 1. Select a library object from 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 inserted. Result If the object was contained in the "Copy templates" folder, you have inserted an independent copy of the library object in the editor. If the object was contained in the "Types" folder, you have inserted an instance of the library object in the editor. 10.9.2.7 Using types and their versions State of type versions Introduction Depending on the point of use, the version of a type has different statuses. Released version The "released version" status is available for all types, regardless of the point of use. If you want to edit a released version, you must first create a new test version or an "in progress" version. Released type versions of scripts and screens can be opened and viewed at their instance. WinCC Basic V13.0 System Manual, 02/2014 4001 Visualize processes 10.9 Using global functions "In progress" version The "in progress" status is possible for the following types: Faceplates User data Styles When you create a new type or a new version of a released type, the type is assigned the status "in progress". Types with the "in progress" status can be edited in the library view without the need for a reference to an instance in the project. Upon release, the compatibility of the type is tested by a consistency check. "In testing" version Only versions of scripts and HMI screens have the "in testing" status. When you create a new version of a type, the type is assigned the status "in testing". A version with "in testing" status is linked to an instance in the project. You can set only one version to "in testing" for each type at a given time. A version in testing may only be linked to a single instance in the project. Therefore, it is not possible to copy an instance to the clipboard, to duplicate it or to create an additional type from the instance as long as it has "in testing" status. See also Generating a script as a type (Page 4002) Generating a screen as a type (Page 4003) Create a new version of a type (Page 4004) Copy templates and types (Page 3987) Generating a script as a type Requirement A project is open. An HMI device has been created and opened. The project tree is open. The "Libraries" task card is opened. Procedure 1. Open the "Scripts" editor in the project tree. 2. Create a new script. 4002 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.9 Using global functions 3. Select the script in the project tree. 4. Drag-and-drop the script into a library in the "Libraries" task card. A dialog opens. 5. Enter a name. 6. Enter a comment. Result You have created a type version of a script in the library. The created type is stored as a released version in the library. An instance of the type is used in the project. To change the script create a new version of the script. See also State of type versions (Page 4001) Generating a screen as a type Requirement A project is open. An HMI device has been created and opened. The project tree is open. The "Libraries" task card is opened. Procedure 1. Open the "Screens" editor in the project tree. 2. Create a new screen. 3. Select the screen in the project tree. 4. Drag-and-drop the screen into a library in the "Libraries" task card. A dialog opens. 5. Enter a name. 6. Enter a comment. Result You have created a type of a screen in the library. The created type is stored as a released version in the library. An instance of the type is used in the project. To change the screen create a new version of the screen. WinCC Basic V13.0 System Manual, 02/2014 4003 Visualize processes 10.9 Using global functions See also State of type versions (Page 4001) Generating a style as a type Introduction To define a new style, add a new type in the project library. Adding a new style 1. Open the "Libraries" task card. 2. Select the "Add new type" command under "Types" in the shortcut menu of the project library. A dialog opens. 3. Select "HMI style". Result The new style is created and displayed under its selected name in the project library. The HMI style type is assigned the status "in progress" and the version 0.0.1. Create a new version of a type Principle If you create a new version of a type, the point of use of the type determines the status of the newly created version. Requirement The "Libraries" task card is opened. A type has been created and released. Procedure 1. Select the released type. 2. Select "Edit type" in the shortcut menu. Result for types of faceplates, user data, and styles A new version of the type is created. The version has the status "in progress". The library view opens. 4004 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.9 Using global functions Result for types of scripts and screens A dialog opens. After you have selected the settings in the dialog, the version is set to the status "in testing". The instance used in the project is set to the status "in testing". The library view opens. See also State of type versions (Page 4001) 10.9.3 Using controller data from other projects 10.9.3.1 Basics of Inter Project Engineering (IPE) What is IPE? You can use the IPE (Inter Project Engineering) function to read in controller data from other TIA Portal projects and use it for configuring. IPE enables you to transfer and merge the HMI configuration and PLC programming communication into various TIA Portal projects. 7,$3RUWDOSURMHFW ,3(ILOH ,QLWLDOL]DWLRQ RU 3URMHFWILOH 3/&GHYLFHSUR[\ You can exchange controller data using IPE in two ways: Initializing device proxy via an IPE file (Page 4006) Initializing a device proxy via a project file (Page 4012) WinCC Basic V13.0 System Manual, 02/2014 4005 Visualize processes 10.9 Using global functions 10.9.3.2 Controller data Introduction In the source project of the PLC, you can select which controller data is to be stored as deviceproxy data. To this end, you create a device proxy data from a configured PLC. Which device proxy data can be exchanged? The following device proxy data can be exchanged via IPE: Program blocks Technology objects PLC tags PLC alarms The following information is exchanged automatically: Interfaces of the PLC Configured communication processors and communication modules at the PLC 10.9.3.3 Initializing a device proxy via an IPE file Initializing device proxy via an IPE file How does initialization of a device proxy via an IPE file work? You can exchange controller data between two or more projects using IPE files. Due to their small data volume, you can send IPE files by e-mail, for example. You can create multiple IPE files with different device proxy data for each PLC. A device proxy can only be filled with one device proxy data record in the target project. 4006 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.9 Using global functions 6RXUFHSURMHFW 7DUJHWSURMHFW 3/&B$ ([SRUW 'HYLFHSUR[\GDWD 3/&B$ 'HYLFHSUR[\GDWD 3/&B$ ,QLWLDOL]DWLRQ ,3(ILOH 3/&GHYLFHSUR[\ An IPE file is exported from the source project. The IPE file contains device proxy data of the PLC "PLC_A". A device proxy is created in the target project. In the target project, the device proxy is then initialized with the device proxy data from the IPE file. Following initialization, all device proxy data from the IPE file is contained in the device proxy. If changes are made in the source project, the device proxy of PLC_A in the target project can be updated via the new IPE file. Initializing a device proxy via an IPE file Introduction You initialize device proxy data using a dialog on the device proxy in the TIA Portal. The IPE file contains the device proxy data from the source project. Requirement IPE file is available. WinCC Basic V13.0 System Manual, 02/2014 4007 Visualize processes 10.9 Using global functions Procedure 1. Double-click "Add new device" in the project tree. 2. Select the device proxy under "Controller". A new device is created in the "Devices & Networks" editor. 3. Select the device proxy in the project tree. 4008 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.9 Using global functions 4. Click "Initialize device proxy" in the shortcut menu. 5. Select the IPE file and click "Open". The "Initialize device proxy" dialog opens. Note You cannot select the device proxy data before initialization in the target project. All device proxy data included in the IPE file is transferred. Initialize a project file if you want to select specific device proxy data before initialization: Initializing a device proxy via a project file (Page 4012) 6. Click "OK". Initialization of the device proxy is started. Result Following initialization, all device proxy data from the IPE file is contained in the device proxy. You can now configure an HMI connection with the device proxy and connect PLC tags from the device proxy with HMI tags, for example. WinCC Basic V13.0 System Manual, 02/2014 4009 Visualize processes 10.9 Using global functions Updating a device proxy via an IPE file Introduction If changes were made to the device proxy data in the device proxy source project, the device proxy data can be updated in the target project. Requirement New IPE file contains the device proxy data from the source project. A device proxy has already been initialized using an IPE file in the target project. Procedure 1. Select the device proxy in the project tree. 2. Click "Update device proxy" in the shortcut menu. 4010 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.9 Using global functions 3. Select the IPE file. 4. Select whether you wish to update the PROFINET or PROFIBUS addresses. 5. Click "OK". WinCC Basic V13.0 System Manual, 02/2014 4011 Visualize processes 10.9 Using global functions 10.9.3.4 Initializing a device proxy via a project file Initializing a device proxy via a project file How does an initialization via project file work? You can transfer controller data using a project file in your TIA Portal project: 6RXUFHSURMHFW 3/&B$ 'HYLFHSUR[\GDWD 3/&B% 'HYLFHSUR[\GDWD 7DUJHWSURMHFW ,QLWLDOL]DWLRQRIGHYLFH SUR[\GDWD 3/&GHYLFHSUR[\ There are two PLCs in the source project. Device proxy data objects of the two PLCs are created in the source project. The source project is saved. A device proxy is created in the target project. The source project (*.ap13) is first selected using the command for the initialization of device proxy in the device shortcut menu. The "PLC_A" and "PLC_B" controllers are available for selection and their device proxy data have already been created. After selection of device proxy data of "PLC_A", the data is stored in the PLC_Proxy of the target project. Changes from the source project can be transferred by an update via the project file. Initializing a device proxy via a project file Introduction You initialize the device proxy using a project file. Requirement Project file (*.ap13) exists. 4012 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.9 Using global functions Procedure 1. Double-click "Add new device" in the project tree. 2. Select the device proxy under "Controller". A new device is created in the "Devices & Networks" editor. 3. Select the device proxy in the project tree. WinCC Basic V13.0 System Manual, 02/2014 4013 Visualize processes 10.9 Using global functions 4. Click "Initialize device proxy" in the shortcut menu. 5. Select the following entry in the "Open device proxy data source" dialog: "TIA Portal projects (*.ap13)" 6. Select a project file and click "Open". The "Initialize device proxy" dialog opens. 7. Select a device proxy data object already created from an available PLC to initialize the device proxy. 8. Click "OK". Result Following initialization, the controller data from the project file in the selected device proxy data object is stored in the device proxy. You can now configure an HMI connection with the device proxy and connect PLC tags from the device proxy with HMI tags, for example. Initialization via Classic projects You can find more information on importing controller data from projects prior to TIA Portal V11 in an FAQ. Entry ID: 73502293 (http://support.automation.siemens.com/WW/view/de/73502293) 4014 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.9 Using global functions Updating a device proxy via a project file Introduction If changes have been made to the controller data in the source project of the device proxy, you can update the device proxy in your TIA Portal project. Requirement Project file has been generated from the source project of the device proxy. A device proxy that has already been initialized is available in the target project. Procedure 1. Select the device proxy in the project tree. 2. Click "Update device proxy" in the shortcut menu. WinCC Basic V13.0 System Manual, 02/2014 4015 Visualize processes 10.9 Using global functions 3. Select the project file. The "Update device proxy" dialog opens. 4. Select a device. Note If you have created several device proxy data objects in the source project, you need to select one device proxy data object. Note Already initialized device proxies cannot be overwritten with controller data from a different PLC. 5. Select whether you wish to update the PROFINET or PROFIBUS addresses. 6. Click "OK". 4016 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.9 Using global functions 10.9.4 Importing and exporting project data 10.9.4.1 Importing and exporting project data Introduction WinCC gives you the option of exchanging project data between the projects or copying them to external applications. Exporting and importing between projects You can export the following project data from a project and import them into another project. 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. 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. WinCC Basic V13.0 System Manual, 02/2014 4017 Visualize processes 10.9 Using global functions 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. Copying in Excel format In all spreadsheet editors you can copy the content in Excel format into the buffer of your PC. Subsequently you insert the project data in Excel format directly into any application outside the TIA Portal. To this purpose you use the corresponding command in the shortcut menu of the work area: If you select the command in the shortcut menu of the line header, the complete line is copied into the buffer. If you select the command in the shortcut menu of a cell, only the cell content is copied into the buffer. If you select several lines and select the command, all marked data are always copied into the buffer. This data exchange is only possible as an export. See also Exporting alarms (Page 4022) Exporting tags (Page 4029) Exporting text lists (Page 4034) 10.9.4.2 Importing and exporting recipes Exporting recipes Introduction WinCC features an export function for exporting data records from recipes. Requirements The WinCC project for the export is open. Recipes have been created in a project. The "Recipes" editor is open. 4018 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.9 Using global functions Exporting recipes 1. In the "Recipes" editor, select the recipe with the data records you want to export. 2. Click . The "Export" dialog box opens. The selected recipe is shown under "Recipe selection". 3. Under "Content selection", specify if all or only selected data records are to be exported. 4. Under "File selection", specify the file in which the recipe data is to be stored. 5. Specify the list separator and decimal separator under "Data separation". 6. Click "Export." The export will start. Result The exported data has been written to a CSV file. The CSV file will be stored in the specified directory. See also Exporting alarms (Page 4022) Importing and exporting project data (Page 4017) Exporting tags (Page 4029) Exporting text lists (Page 4034) WinCC Basic V13.0 System Manual, 02/2014 4019 Visualize processes 10.9 Using global functions Importing recipes Introduction Recipes are identified by their name. The recipe name must therefore be unique. Open the import file in a simple text editor to check that it has the correct data structure. Specify whether or not existing data records should be overwritten by records with the same name during the import. Requirements A CSV file containing at least one recipe has been created. The WinCC project for the import is open. The "Recipes" editor is open with at least one recipe. Importing a recipe 1. In the "Recipes" editor, select the recipe with the data records you want to import. 2. Click . The "Import" dialog box opens. The selected recipe is shown under "Recipe selection". 3. Select the file you want to import under "File selection". 4. Under "Strategy", specify if existing data records should be overwritten by records of the same name. 4020 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.9 Using global functions 5. Under "Data separation", select the list separator and the decimal separator to use in the CSV file. 6. Click "Import". The import will start. Result The data records are created in the selected recipe. Depending on the setting for "Strategy", existing data records are overwritten by records with the same name from the CSV file. Existing data records with the same name will also be imported from the CSV file if you deactivate the "Overwrite existing data records" option. Format of recipe data Introduction This section describes the required format of the file for the import of recipes. The file containing the data of the recipes must be available in "*.csv" format. : Structure of recipe data The structure of the import file is fixed. The following example shows the structure of a recipe containing two recipe elements, each with two data records: List separator=<List separator>Decimal symbol=<Decimal separator><List separator><Line break> <Name of the recipe><List separator><List separator><Line break> LANGID_<ID of the language><List separator> <Display name, recipe element 1><List separator> <Display name, recipe element 2><Line break> <Number recipe><List separator> <Recipe data record number 1><List separator> <Recipe data record number 2><Line break> <Tag recipe element 1><List separator> <Recipe data record 1 value 1><List separator> <Recipe data record 2 value 1><Line break> <Tag recipe element 2><List separator> <Recipe data record 1 value 2><List separator> <Recipe data record 2 value 2><Line break> ID of the language Use the "Windows language ID" in decimal notation, e.g. "1033" for English. Additional information is available in the documentation for the Windows operating system. See also Exporting recipes (Page 4018) WinCC Basic V13.0 System Manual, 02/2014 4021 Visualize processes 10.9 Using global functions 10.9.4.3 Importing and exporting alarms Exporting alarms Introduction WinCC has an export function for alarms. Requirements The WinCC project for the export is open. Alarms have been created in the project. The "HMI alarms" editor is open. Exporting alarms 1. Click the button in "Discrete alarms" or "Analog alarms". The "Export" dialog box opens. 2. Click the "..." button and specify in which file the data are saved. 3. Specify whether you want to export "Disrete alarms" or "Analog alarms". 4. Click "Export". The export will start. Result The exported data has been written to an xlsx file. The xlsx file will be stored in the specified folder. See also Importing alarms (Page 4023) Format of the analog alarm data (Page 4024) Format of the discrete alarm data (Page 4027) Exporting recipes (Page 4018) 4022 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.9 Using global functions Exporting tags (Page 4029) Importing and exporting project data (Page 4017) Importing alarms Introduction Alarms are identified by their alarm number. The alarm numbers must be unique in the analog and discrete alarm types. Alarms with redundant alarm numbers will be overwritten. An alarm without an existing alarm number is created. Any empty list entries for existing alarms contained in an xlsx file will be ignored for the purposes of the import. The entries of the existing alarms remain active and will not be replaced by empty ones. Requirements An xlsx file with alarms has been created. The structure of the xlsx file meets the requirements. The WinCC project for the import is open. The "HMI alarms" editor is open. Importing alarms 1. Click the button in "Discrete alarms" or "Analog alarms". The "Import" dialog box opens. 2. Click the "..." button and select the file that you want to import. 3. Click on the "Import" button. The import will start. A progress bar indicates the progress of the import operation. 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. WinCC Basic V13.0 System Manual, 02/2014 4023 Visualize processes 10.9 Using global functions If an object with the same name already exists, the existing object is used. If no object of the same name yet exists, create an object with the relevant name or create a new link. Note The syntax of the import file is checked during xlsx file import. The meaning of the properties or dependencies between the properties is not checked. It is possible to assign a trigger tag of an incorrect type, such as string, to an alarm. An error will be reported during compilation. See also Exporting alarms (Page 4022) 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: 4024 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.9 Using global functions Example of the worksheet "Analog alarms" Table 10-13 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. WinCC Basic V13.0 System Manual, 02/2014 4025 Visualize processes 10.9 Using global functions List entry Meaning Delay time unit Specifies the time unit for the delay. Report Enables reporting of the specific alarm on a printer. True or "1" = Reporting enabled. False or "0" = Reporting disabled. Reporting must also be globally enabled in the project. Info text [de-DE], Info text The tooltip is an optional property of an alarm. Tooltips can contain additional information about the alarm. A tooltip will be displayed in a separate window on the HMI device when the operator presses the <HELP> key. The field designation contains a language ID. Example of the worksheet "Limits" Table 10-14 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. 4026 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.9 Using global functions List entry Meaning Deadband mode Hysteresis mode Specifies whether and in which cases hysteresis will be used. For "Outgoing" For "Incoming" For "Incoming" and "Outgoing" Deadband in percent 0 = The value specified for "Hysteresis" is considered to be absolute. 1 = The value specified for "Hysteresis" is referred to as a percentage of the limit value. Deadband mode Hysteresis Specifies a constant as a value of the hysteresis. Note "No value" in the table Entries in the table which have the value "No value" delete the corresponding values in an existing alarm of the same name. See also Exporting alarms (Page 4022) 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: WinCC Basic V13.0 System Manual, 02/2014 4027 Visualize processes 10.9 Using global functions Example of the worksheet "Discrete alarms" Table 10-15 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. 4028 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.9 Using global functions List entry Meaning PLC acknowledgement tag Specifies the tag containing the bit that acknowledges the alarm of the control program. Only available if the selected alarm class requires alarm acknowledgment. PLC acknowledgment bit Specifies the number of the bit that acknowledges the alarm of the control program. Delay time value Specifies the delay time. The alarm is not triggered until the duration of the limit value violation equals the specified delay time. Delay time unit Specifies the time unit for the delay. Report Enables reporting of the specific alarm on a printer. True or "1" = Reporting enabled. False or "0" = Reporting disabled. Reporting must also be globally enabled in the project. Info text [de-DE], Info text The tooltip is an optional property of an alarm. Tooltips can contain additional information about the alarm. A tooltip will be displayed in a separate window on the HMI device when the operator presses the <HELP> key. The field designation contains a language ID. Note "No value" in the table Entries in the table which have the value "No value" delete the corresponding values in an existing alarm of the same name. See also Exporting alarms (Page 4022) 10.9.4.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. WinCC Basic V13.0 System Manual, 02/2014 4029 Visualize processes 10.9 Using global functions Exporting tags 1. Click on the button in the "HMI Tags" tab. The "Export" dialog box opens. 2. Click the "..." button and specify in which file the data are saved. 3. Click "Export". The export will start. Result The exported data has been written to an xlsx file. The xlsx file will be stored in the specified folder. See also Importing tags (Page 4030) Exporting alarms (Page 4022) Importing and exporting project data (Page 4017) Exporting text lists (Page 4034) Exporting recipes (Page 4018) Format of the tag data (Page 4032) 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. 4030 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.9 Using global functions Importing tags 1. Click "HMI tags" in the project navigation. 2. Double-click "Show all tags". The "HMI tags" editor opens. 3. Click on the button. The "Import" dialog box opens. 4. Click the "..." button and select the file that you want to import. 5. Click on the "Import" button. The import will start. Result The relevant tags have been created in WinCC. Alarms relating to the import operation are displayed in the output window. A log file is saved in the source directory of the import files. The log file has the same name as the respective import file but with the "*.xml" extension. Check when importing the data whether there are any links to objects, for example, dynamic parameters such as tags. If an object with the same name already exists, the existing object is used. If no object of the same name yet exists, create an object with the relevant name or create a new link. Note The syntax of the import file is checked during xlsx file import. The meaning of the properties or dependencies between the properties is not checked. It is possible to assign a tag a trigger tag of the wrong type, for example, string. An error will be reported during compilation. See also Exporting tags (Page 4029) WinCC Basic V13.0 System Manual, 02/2014 4031 Visualize processes 10.9 Using global functions Format of the tag data Introduction This section describes the format required for the file with tag data used for imports. The tag data file must be in "*.xlsx" format. Tag data structure The import file in Microsoft Excel consists of a number of worksheets: HMI Tags (HMI tags) Multiplexing (multiplex tags) Each tag is on a separate line in the import file. The import file with the tag data must have the following format: Example of the worksheet "HMI Tags" Table 10-16 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. 4032 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.9 Using global functions List entry Meaning Data type Specifies the data type of a tag. The data types allowed depend on the communication driver being used. See the "Communication" section of the documentation for additional information on the data types permitted for the various communication drivers. Length Specifies the length of the tag. This entry is only useful for data types with a dynamic length such as strings; it is left empty for all other data types. Address Specifies the tag address in the PLC. The tag address must exactly match the one used in WinCC, for example, "%DB1.DBW0". The tag address is empty for internal tags. Multiplexing Specifies whether multiplexing is used. Index tag Shows the name of the index tag for multiplexing. In Runtime, the system first reads the value of the index tag. It then accesses the tag in the corresponding place in the tag list. StartValue Specifies the start value of a tag. ID tag The update ID updates the value of a tag with the aid of a function or a PLC job. The update ID must be unique within an HMI device. Coding Shows the coding method. DiplayName [de_DE] Shows the display name of an HMI tag. The field designation contains a language ID. The field designation contains a language ID. Display names must be assigned a language ID for import. Texts are imported to the corresponding project language. Acquisition mode Specifies the tag acquisition mode. Acquisition cycle Specifies the tag acquisition cycle. The acquisition cycle must correspond exactly to the one used in WinCC. The value is not language-dependent and should therefore be the same in every language. The default value is "1 s". The acquisition cycle is undefined if the tag acquisition mode is "on demand". User-defined acquisition cycles must be created beforehand as the file will otherwise not be imported. High High Limit type Indicates whether the limit value "High high" is monitored by a constant, a tag or not at all. High High Limit Displays the limit value "High High". High Limit type Indicates whether the limit value "High" is monitored by a constant, a tag or not at all. High Limit Displays the limit value "High". Low Limit type Indicates whether the limit value "Low" is monitored by a constant, a tag or not at all. Low Limit Displays the limit value "Low". Low Low Limit type Indicates whether the limit value "Low Low" is monitored by a constant, a tag or not at all. Low Low Limit Displays the limit value "Low Low". Linear scaling Indicates whether linear scaling is enabled. This entry can only be used for external tags. End value PLC Specifies the end value of the PLC tag. Start value PLC Specifies the start value of the PLC tag. End value HMI Specifies the end value of the HMI tag. Start value HMI Specifies the start value of the HMI tag. WinCC Basic V13.0 System Manual, 02/2014 4033 Visualize processes 10.9 Using global functions Example of the worksheet "Multiplexing" Table 10-17 Meaning of the entries List entry Meaning Name Indicates the configured name of an HMI tag which uses indirect addressing. The HMI tag must be available in the "HMI Tags" worksheet. Index Shows the value which governs which tag is selected. Multiplex Tag Displays the tag from the tag list corresponding to the index value. Note "No value" in the table Entries in the table which have the value "No value" delete the corresponding values in an existing tag of the same name. See also Exporting tags (Page 4029) 10.9.4.5 Importing and exporting text lists Exporting text lists Introduction WinCC has an export function for text lists. 4034 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.9 Using global functions 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. By default, texts are exported in all defined project languages. If you do not want to export specific languages, disable the unnecessary languages in the dialog. 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 Importing text lists (Page 4036) Importing and exporting project data (Page 4017) Exporting tags (Page 4029) Exporting recipes (Page 4018) Format of text list data (Page 4037) WinCC Basic V13.0 System Manual, 02/2014 4035 Visualize processes 10.9 Using global functions 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. 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 4034) 4036 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.9 Using global functions 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: Example of the worksheet "TextList" Table 10-18 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 WinCC Basic V13.0 System Manual, 02/2014 4037 Visualize processes 10.9 Using global functions Example of the worksheet "TextListEntry" Table 10-19 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;> 4038 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.9 Using global functions See also Exporting text lists (Page 4034) 10.9.4.6 Importing and exporting 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. WinCC Basic V13.0 System Manual, 02/2014 4039 Visualize processes 10.9 Using global functions 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. 4040 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.9 Using global functions 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 Importing project texts (Page 4041) 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. See also Exporting project texts (Page 4039) WinCC Basic V13.0 System Manual, 02/2014 4041 Visualize processes 10.9 Using global functions 10.9.5 Using cross-references 10.9.5.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. 10.9.5.2 Displaying the cross-reference list Introduction Details on the use of objects can be found in the cross-reference list. You can show crossreferences for HMI devices, folders and all editors in the project tree. The detail view also lets you select individual objects of the editors. Requirement You have created a project. Several objects have been created. Procedure 1. Select the required entry in the project tree or detail view. 2. Select "Cross-references" in the shortcut menu. The cross-reference list is opened in the work area. 3. Open the "Used by" tab to display where the objects shown in the cross-reference list are used. 4. Open the "Used" tab to view the users of the objects displayed in the cross-reference list. 4042 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.9 Using global functions 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. 10.9.5.3 Structure of the cross-reference list Views of the cross-reference list There are two views of the cross-reference list. The difference between the two views is in the objects displayed in the first column: Used by: Display of the referenced objects. Here, you can see where the object is used. Used: Display of the referencing objects. The users of the object are shown here. The assigned tool tips provide additional information about each object. Structure of the cross-reference list Column Content/meaning Object Name of the object that uses the lower-level objects or that is being used by the lower-level objects. Numbers Number of uses Location of use Each location of use, for example, an object or event Property Function of the referenced objects, for example, tag for data record or process value Connected to PLC tag with which the object is connected. Type Type of object Path Path of object Depending on the installed products, additional columns or different columns are displayed for the cross-references. WinCC Basic V13.0 System Manual, 02/2014 4043 Visualize processes 10.9 Using global functions 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. 10.9.5.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. 4044 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.9 Using global functions 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. 10.9.5.5 Rewiring tags in the screens Introduction You can change the references of tags in the properties of screen objects using the "Change object references" dialog. WinCC Basic V13.0 System Manual, 02/2014 4045 Visualize processes 10.9 Using global functions This function lets you to replace a large number of tags in various screen objects. You search for and replace individual or multiple characters in the tag names. You can open the "Change object references" dialog with the command in the shortcut menu. You can open the dialog for one or more screen objects or a screen. How to replace a tag 1. Select the objects in the screen that contains a tag that you want to change. 2. Select the "Change object references" command in the shortcut menu or in the "Edit" menu. The "Change object references" dialog opens. You can see the selected screen objects and the tags used in the "Object" column. 3. Enter the name or part of the name you want to find in the "Find in reference" input box. 4. Start the search with the "Find next" button. If a reference is found, it is highlighted in the "Reference" column. Another click on the "Find next" button continues the search process until the list has been completely searched. After this, the search process starts again from the top of the list. 5. Enter the name or part of the name you want to replace for the found name in the "Replace with" input box. 6. Click the "Replace" button to replace the selected tag. All references found are replaced by clicking the "Replace all" button. In this way, you can replace a large number of references with another reference. 7. To select a tag from the list of all tags created in the project, click on the "Replace" column. 4046 button in the WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.9 Using global functions 8. To select a tag from the object list or to create a new tag, click on the "Replace" column. button in the 9. Confirm your entry with "OK". The rewiring of the tags is applied in the project. Additional options for searching You can narrow down your search by enabling the following options: Use wildcards Enter * for any number of characters. Example: You want to search for all tags starting with "HMI". Enter "HMI*" in the search key box. Enter ? for an individual character. Find whole words To search only for full names, enable the "Find whole words" option. Replacing arrays and user-defined tags Variables whose names contain special characters . [ ] are shown in quotes. Array type tags and tags of user-defined data types (UDT) contain special characters to separate tags from their elements. However, they are not shown in quotation marks. To replace an array or a UDT with an HMI tag with special characters, enter the name of the HMI tag in quotation marks in the "Replace" input box. If you type the name without quotation marks, a reference to a non-existent array or UDT is created instead of a reference to the desired HMI tag with special characters. Correcting entries If an incorrect entry is made in the "Replace with" input box, the existing references can be replaced by references to non-existent tags. If you detect an incorrect entry before confirming with "OK", you can correct the error. To do this, select the "Replace" column and press the "Remove" button. Any incorrect entries in the "Reference" column are deleted. If you confirm the dialog with "OK", the affected properties of the screen objects are marked in red. Non-existent tags are highlighted in red in the "Change cross references" dialog. If the new tag does not yet exist, you must subsequently create the tag. WinCC Basic V13.0 System Manual, 02/2014 4047 Visualize processes 10.9 Using global functions 10.9.6 Managing languages 10.9.6.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. 4048 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.9 Using global functions See also Language settings in the operating system (Page 4049) Operating system settings for Asian languages (Page 4050) Selecting the user interface language (Page 4051) "Graphics" editor (Page 4062) Languages in Runtime (Page 4066) Example: Configuring a button for language switching (Page 4073) 10.9.6.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 4048) Operating system settings for Asian languages (Page 4050) WinCC Basic V13.0 System Manual, 02/2014 4049 Visualize processes 10.9 Using global functions 10.9.6.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 4048) Language settings in the operating system (Page 4049) 4050 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.9 Using global functions 10.9.6.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 4051) Selecting the reference language and editing language (Page 4052) Languages in WinCC (Page 4048) 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. WinCC Basic V13.0 System Manual, 02/2014 4051 Visualize processes 10.9 Using global functions 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. NOTICE 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 4051) Selecting the reference language and editing language (Page 4052) 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. 4052 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.9 Using global functions 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 4051) Enable project languages (Page 4051) WinCC Basic V13.0 System Manual, 02/2014 4053 Visualize processes 10.9 Using global functions 10.9.6.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 4055) Translating texts directly (Page 4056) Translating texts using reference texts (Page 4058) Exporting project texts (Page 4059) Importing project texts (Page 4061) 4054 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.9 Using global functions 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. See also Working with multiple languages (Page 4054) Translating texts directly (Page 4056) WinCC Basic V13.0 System Manual, 02/2014 4055 Visualize processes 10.9 Using global functions Translating texts using reference texts (Page 4058) Exporting project texts (Page 4059) Importing project texts (Page 4061) 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. 4056 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.9 Using global functions 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 " toolbar. 4. To hide texts that do not have a translation, click on the " button in 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. WinCC Basic V13.0 System Manual, 02/2014 4057 Visualize processes 10.9 Using global functions See also Working with multiple languages (Page 4054) Exporting project texts (Page 4059) Project text basics (Page 4055) Importing project texts (Page 4061) 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 4054) Exporting project texts (Page 4059) Project text basics (Page 4055) Importing project texts (Page 4061) 4058 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.9 Using global functions 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. WinCC Basic V13.0 System Manual, 02/2014 4059 Visualize processes 10.9 Using global functions 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. 4060 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.9 Using global functions 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 4054) Translating texts using reference texts (Page 4058) Translating texts directly (Page 4056) Project text basics (Page 4055) Importing project texts (Page 4061) 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. WinCC Basic V13.0 System Manual, 02/2014 4061 Visualize processes 10.9 Using global functions See also Exporting project texts (Page 4059) Working with multiple languages (Page 4054) Project text basics (Page 4055) Translating texts directly (Page 4056) Translating texts using reference texts (Page 4058) 10.9.6.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 an external image in the graphics library (Page 4064) Storing an image in the graphics library (Page 4063) Languages in WinCC (Page 4048) 4062 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.9 Using global functions Storing an image in the graphics library 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. WinCC Basic V13.0 System Manual, 02/2014 4063 Visualize processes 10.9 Using global functions 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 4062) Storing an external image in the graphics library 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. 4064 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.9 Using global functions 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 4062) WinCC Basic V13.0 System Manual, 02/2014 4065 Visualize processes 10.9 Using global functions 10.9.6.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 4066) Enabling the runtime language (Page 4067) Setting the runtime language order for language switching (Page 4069) Setting the default font for a runtime language (Page 4071) Selecting the log language (Page 4072) Languages in WinCC (Page 4048) 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. 4066 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.9 Using global functions 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 4066) Selecting the log language (Page 4072) Enabling the runtime language (Page 4067) Setting the runtime language order for language switching (Page 4069) Setting the default font for a runtime language (Page 4071) 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. WinCC Basic V13.0 System Manual, 02/2014 4067 Visualize processes 10.9 Using global functions Procedure 1. Double-click on "Runtime settings" in the project tree. 2. Click on "Language & Font". 3. Select the following languages: - English - Italian - 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. 4068 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.9 Using global functions See also Languages in Runtime (Page 4066) Selecting the log language (Page 4072) Setting the runtime language order for language switching (Page 4069) Methods for language switching (Page 4066) 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. English 2. Italian 3. French WinCC Basic V13.0 System Manual, 02/2014 4069 Visualize processes 10.9 Using global functions Procedure 1. Select the runtime language "Italian". 2. Click the button. The runtime language "Italian" is moved 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 4066) Selecting the log language (Page 4072) Enabling the runtime language (Page 4067) Setting the default font for a runtime language (Page 4071) Methods for language switching (Page 4066) 4070 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.9 Using global functions 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 4066) Selecting the log language (Page 4072) Setting the runtime language order for language switching (Page 4069) Methods for language switching (Page 4066) WinCC Basic V13.0 System Manual, 02/2014 4071 Visualize processes 10.9 Using global functions 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 4066) Setting the default font for a runtime language (Page 4071) Setting the runtime language order for language switching (Page 4069) Methods for language switching (Page 4066) Enabling the runtime language (Page 4067) 4072 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.9 Using global functions 10.9.6.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 and the "Switch" setting. 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 4073) Example: Configuring a button for language switching for each runtime language (Page 4074) Languages in WinCC (Page 4048) 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. WinCC Basic V13.0 System Manual, 02/2014 4073 Visualize processes 10.9 Using global functions 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 4073) Example: Configuring a button for language switching for each runtime language (Page 4074) 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. 4074 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.9 Using global functions 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 4073) Example: Configuring a button in multiple languages (Page 4073) WinCC Basic V13.0 System Manual, 02/2014 4075 Visualize processes 10.9 Using global functions 10.9.7 Replacing devices 10.9.7.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. See also Device-specific functions (Page 4077) Screen adjustment options (Page 4080) Key assignment when replacing devices (Page 4078) Engineering system (Page 4181) Basic Panel (Page 4183) 4076 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.9 Using global functions 10.9.7.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. 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 4076) WinCC Basic V13.0 System Manual, 02/2014 4077 Visualize processes 10.9 Using global functions 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. 4078 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.9 Using global functions 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 WinCC Basic V13.0 System Manual, 02/2014 4079 Visualize processes 10.9 Using global functions See also Basics (Page 4076) Screen adjustment options (Page 4080) 10.9.7.3 Adjusting 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. 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. Screen adjustment when replacing devices Adjust the size of the screens to the new device in the menu under "Tools > Settings > Visualization > Resize screen". Select one of the following settings. 4080 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.9 Using global functions None (default setting) The screens are not scaled. The objects in the screen retain their position and size. Use this setting as first test for checking of a possible exchange result because there are no rounding losses during forth and back exchange. This option may result in objects being outside the configurable area if the display of the new device is smaller than the old one. Fit to screen The position and object size are adjusted to the new display size. Resizing takes place along the x-axis and the y-axis. Graphics and font size are adjusted accordingly. Fit to height The aspect ratio is maintained and the screens are adjusted to the height of the new device. Use this option when you are replacing a device with display format 4:3, for example, with a device with widescreen. Fit to 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 4084) Fit objects to contents (Page 4082) WinCC Basic V13.0 System Manual, 02/2014 4081 Visualize processes 10.9 Using global functions Basics (Page 4076) Key assignment when replacing devices (Page 4078) Fit objects to contents Introduction For some objects, you can specify fit to respective content in the Inspector window, for example: Text field: fit to text content I/O field: fit to text content Symbolic I/O field: fit to text content or to text list Graphic view: fit to included graphic Fit to size for text and graphic objects Disable automatic fit to size of the individual objects in the menu under "Options > Settings > Visualization > Resize screen and screen objects > Fit to content". This results in scaling of the objects as specified under "Options > Settings > Visualization > Resize screen and screen objects". Select the objects which are not automatically fitted to size. If "Disable 'fit to size' for text objects" is activated, automatic fit to size is ignored in the text object properties. If you have activated "Fit screen to window height", the text field along with the other objects is scaled in accordance with the height of the new device. If "Disable 'fit to size' for graphic objects" is activated, automatic fit to size is ignored in the graphic object properties. If you have activated "Fit screen to window width", the graphics view along with the other objects is scaled in accordance with the width of the new device. Note The settings have no effect on screen objects whose size cannot be changed, such as alarm indicators or screen objects with a fixed aspect ratio. "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. 4082 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.9 Using global functions - You have activated "Fit screen to window width" and the new device has the same resolution as the current device. Example The figure below shows the effects of automatic sizing using a graphic object with two buttons aligned as an example: Initial situation: Two buttons are aligned on a graphic object. The option "Fit object size to graphic" or "Adjust object size to graphic" is activated in the object properties of the graphic object under "Display > Sizing". Option 1: The original properties of the graphic object are to be maintained after switching the HMI device. Deactivate the option "Disable 'fit to size' for graphical objects" in the settings under "Size adaptation of objects". Effect: The graphic object retains its original size after switching the HMI device. The alignment to the buttons is lost. Option 2: The graphic object is to be placed relative to the new screen resolution after switching the HMI device. Activate the option "Disable 'fit to size' for graphical objects" in the settings under "Size adaptation of objects". The option "Fit graphic to object size" is activated automatically in the object properties of the graphic object. The two buttons are properly aligned on the graphic object even after switching the HMI device. WinCC Basic V13.0 System Manual, 02/2014 4083 Visualize processes 10.9 Using global functions See also Specifying the position of screen objects (Page 4084) Screen adjustment options (Page 4080) Specifying the position of screen objects Introduction There are various ways to adjust the position of screen objects to the new device. Select position Adjust the position of the screen objects to the new device in the menu under "Options > Settings > Visualization > Fit to size screen > Select position". Example The following option aligns the objects with the top left edge. The following object centers the objects in the middle of the screen. See also Fit objects to contents (Page 4082) Screen adjustment options (Page 4080) 4084 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.9 Using global functions 10.9.8 Copying between devices and editors 10.9.8.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. WinCC Basic V13.0 System Manual, 02/2014 4085 Visualize processes 10.9 Using global functions Copying user-defined folders You can create user-defined folders for editors, for example, for HMI tags, screens, etc. You can copy user-defined folders and paste them into another HMI device. The objects contained in a user-defined folder may exceed the limitations applying to the other HMI device, such as the number of supported screens. After they have been pasted, all the objects are displayed. An error is displayed when the project data is compiled. System folders cannot be copied. See also Unsupported objects and functionalities (Page 4086) Unsupported objects and functionalities Introduction When an object is copied, all its properties and settings are transferred to the target HMI device. Unsupported objects Objects that are not supported in the target HMI device cannot be pasted. Note When you copy a screen containing objects which are not supported by the destination HMI device, the objects remain in the background. When you copy the screen again and the new device supports the objects, they are displayed again. Invalid objects The following objects become invalid once they have been pasted into the target HMI device: Referenced objects that do not exist in the target HMI device. Objects with settings that are not supported in the target HMI device. System functions that were configured for objects and that are not supported in the target HMI device. Invalid objects are highlighted by a color coding. Select a supported object or create a new one. If you retain an invalid object, an error will be displayed when the project data is compiled. Colors and fonts Colors and fonts are supported to varying degrees by HMI devices. When unsupported colors and fonts are pasted, they are replaced by supported colors and fonts. When you paste the same object back into the source HMI device, the original settings become active again. 4086 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.9 Using global functions See also Basics (Page 4085) 10.9.8.2 Copying and pasting 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 to height". See also Copying recipes within an HMI device (Page 4087) Copying objects with linked objects (Page 4088) Linked objects copied automatically (Page 4089) 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. WinCC Basic V13.0 System Manual, 02/2014 4087 Visualize processes 10.9 Using global functions You can copy a recipe data record to another recipe, if the other recipe contains the same number of recipe elements. If the data types differ, the value will be copied to the target data record but it is assigned an error flag. "Tags" editor You can drag-and-drop a tag to a recipe element in the "Tag" column. The tag is linked to the recipe element. If a tag is already linked, an error message will be generated. "Screens" editor If you drag-and-drop a recipe to a screen, a new recipe display will be created and linked to the recipe. See also Copying screens (Page 4087) Copying objects with linked objects (Page 4088) Linked objects copied automatically (Page 4089) Copying objects with linked objects Introduction An object is linked to another object in the following situations, for example: You specify a tag for an alarm as a trigger tag. The alarm is the object. The tag is the linked object. You specify a connection for an external tag. The tag is the object. The connection is the linked object. The object is always fully inserted during copying and pasting. Whether or not the linked object is pasted depends on the command used to insert it. Simple pasting The linked object is not copied. The linked object is transferred and handled as follows in the target HMI device: If an object with the same name exists, the existing object with its settings is used. If no object with the same name exists, the name of the object will be displayed. The object becomes invalid. For some objects, linked objects are pasted automatically during simple pasting. 4088 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.9 Using global functions Extended pasting Select the "Extended paste" command in the shortcut menu to paste the linked objects as well. If objects of the same name exist in the target HMI device, you need to decide whether or not to overwrite each of these objects. See also Copying screens (Page 4087) Copying recipes within an HMI device (Page 4087) Linked objects copied automatically Copying linked objects The following table shows the objects for which linked objects are pasted automatically in simple pasting. Object Linked object Screen Template Symbolic I/O field Text list Graphic I/O field Graphics list Graphic view Graphic Tag Alarm Cycle Recipe element Text list Scheduler Triggers See also Copying screens (Page 4087) Copying recipes within an HMI device (Page 4087) 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. WinCC Basic V13.0 System Manual, 02/2014 4089 Visualize processes 10.9 Using global functions Pasting a symbolic I/O field 1. Open a screen. 2. Click on the "Text and graphics lists" editor in the project tree. All existing text and graphics lists will be shown in the details view. 3. Click on a text list, for example, "Textlist1" in the Details view. 4. Drag-and-drop a text list from the Details view to a screen. A symbolic I/O field has been created and connected to the text list "Textlist1". Pasting a graphic I/O field 1. Open a screen. 2. Click on the "Text and graphics lists" editor in the project tree. All existing text and graphics lists will be shown in the details view. 3. Click on a graphics list in the Details view, for example "Graficlist1". 4. Drag-and-drop a graphics list from the Details view to a screen. A graphic I/O field has been created and connected to the graphics list "Graficlist1". 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". 10.9.8.3 Copying between different RT and ES versions Introduction You can copy and paste project data such as screens, objects or tags between projects with different WinCC versions. All configurations that are supported in the target version are retained when you copy data between projects of different WinCC versions. Configurations that are not supported by the target version are marked as invalid with a color code. Copy of control between HMI devices from different device versions WinCC supports all configurations of a previous WinCC version. The following applies when copying within different ES versions: 4090 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.9 Using global functions All the configurations that are also supported in the respective RT version are retained. Default settings are defined for configurations that are only supported in the WinCC version of the target project. Configurations that are not supported by the respective RT version are marked by color as invalid or are not displayed. All properties and settings originally defined in the source HMI device are reactivated when you copy an object back to the source HMI device unchanged. 7,$3RUWDO9[ 3URMHFW9[ 'HYLFH9[ 'HYLFH9[ 'HYLFH9[ 'HYLFH9[ $WWULEXWH $WWULEXWH $WWULEXWH The HMI device must be valid for the current Runtime version. Copying between different ES versions Open a second instance of the TIA Portal to copy between two TIA projects. You can only copy between projects that have the same ES version. The ES version of a project is indicated by the file extension *.ap<version_number>. 7,$3RUWDO 3URMHFWDS[! WinCC Basic V13.0 System Manual, 02/2014 7,$3RUWDO 3URMHFWDS[! 4091 Visualize processes 10.9 Using global functions 7,$3RUWDO 3URMHFWDS[! 7,$3RUWDO 3URMHFWDS\! 10.9.9 Using WinCC version compatibility 10.9.9.1 Basics on version compatibility Introduction Edit existing projects as follows with WinCC: You edit, compile and download existing projects with the range of functions of the previous version of WinCC. You can continue to edit these projects afterwards with the previous version of WinCC. You upgrade existing projects and use the functions of the current WinCC version. Note WinCC functions While editing a project of a previous WinCC version, you can only access the functions and HMI devices of this previous WinCC version. Versions in WinCC In WinCC, you work with different version types: WinCC version The WinCC version installed on the configuration PC, for example, WinCC V12. Project version Projects are created using the WinCC version that is installed on the configuration PC. While you are editing a WinCC project from a previous version in the current WinCC version, the version ID is displayed behind the project name in the project tree. 4092 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.9 Using global functions Runtime version You can configure HMI devices with different runtime versions in WinCC. You specify the runtime version once for an HMI device. The device version must match the Runtime version. Device versions Depending on the used HMI device, the image is a combination of the operating system and / or runtime software. For each HMI device, WinCC provides various images which can be loaded onto the HMI device, if necessary, according to the configuration. The device version corresponds to a specific image. The device version must match the configuration. Compatibility of WinCC versions, Runtime versions and device versions The figure below shows the interaction of versions in the TIA Portal: 7,$3RUWDO9 3URMHFW9 XSGDWH 5XQWLPH9 +0,GHYLFH 9 XSGDWH 7,$3RUWDO9 3URMHFW9 3URMHFW9 5XQWLPH9 5XQWLPH9 +0,GHYLFH 9 +0,GHYLFH 9 XSGDWH 3URMHFW9 5XQWLPH9 XSGDWH +0,GHYLFH 9 Creating projects After you create a new project in WinCC, open and edit it in the WinCC version in which you created it. Saving To save a project of a predecessor WinCC version in this version again, save it in the usual way. If you manually upgrade the project to your WinCC version, please note that you will no longer be able to open the project in the previous WinCC version. To save a project of the previous WinCC version in the current version, upgrade the project to your WinCC version. You can then no longer edit the project with a previous version of WinCC. WinCC Basic V13.0 System Manual, 02/2014 4093 Visualize processes 10.9 Using global functions Compiling, simulating and loading If you are using a project of a previous WinCC version, you can use your current version to generate Runtime data for this previous version. This also allows you to load HMI devices that are no longer compatible with your WinCC version. Copying within projects with different WinCC versions If objects and configurations are also available in the target version, copy these as required via the clipboard or using drag-and-drop. Opening, editing and saving projects of a previous WinCC version You can open and edit projects of previous WinCC versions as required. In doing so, you only utilize the functions of the previous WinCC version. Once you have completed editing, you can once again save and edit the project in the previous WinCC version. Compiling, downloading and simulating projects of a previous WinCC version You can compile, download and simulate projects of previous WinCC versions as required. Your current WinCC version will provide the Runtimes and device versions for the corresponding WinCC version. 10.9.9.2 Editing projects of a previous WinCC version Introduction WinCC provides the option of editing projects of a previous WinCC version. While editing a project of a previous WinCC version, you can only access the functions of this version. In order to use the functions of your current WinCC version for this project, upgrade the project to your WinCC version. Note If you upgrade a project to your WinCC version, please note that you will no longer be able to open and edit the project in the previous WinCC version. Requirement A project of a previous WinCC version has been created. The current WinCC version is installed on the configuration PC. 4094 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.9 Using global functions Procedure Proceed as follows to edit a project of a previous WinCC version: 1. Open the project. 2. Edit the project using the functions of the previous WinCC version. 3. Save the project. 4. Compile the project. 5. Download and simulate the project. 6. You can open the project in the previous WinCC version for further editing, if required. Result The modified project data can be edited further on a different configuration PC with the previous WinCC version for further processing. The Runtime project was generated and downloaded in the corresponding Runtime version. 10.9.9.3 Upgrading projects Introduction If the project version is older than the WinCC version, the version ID is displayed in the project navigation. Your WinCC version also contains the previous version that you can use to edit projects as required. In order to use the functions and options of your WinCC version in a project, upgrade the project to your WinCC version. Then, change your device or runtime version(s) in accordance with the new project version. Note WinCC version compatibility If you upgrade a project to your WinCC version, please note that you will no longer be able to edit it with the previous WinCC version. Requirements The project version is a predecessor of your WinCC version. You have write access to your project drive. The project drive provides sufficient storage capacity for another project of this size. WinCC Basic V13.0 System Manual, 02/2014 4095 Visualize processes 10.9 Using global functions Procedure Proceed as follows to upgrade a project to your WinCC version: 1. Select the project in the project navigation. 2. Select the "Upgrade project" command from the shortcut menu of the project. A dialog opens. 3. Click "Confirm". The project closes and the progress bar is displayed. An alarm is output when the project has been upgraded. Result The project has been saved on the project drive in the previous WinCC version and with the corresponding file extension. The project is displayed on the project drive in the current WinCC version and with the corresponding file extension. The project is displayed without a WinCC version ID in the project navigation. To make use of the functions of the new WinCC version, change your device or runtime version(s) in accordance with the new project version in the next step. 10.9.9.4 Upgrading a global library Introduction In order to process objects of a global library in a project, the global library must be available in the product version of the project. You can upgrade each global library from an older product version to the current product version. You are prompted accordingly when you open the global library. Requirements The version of the global library is a predecessor of your WinCC version. You have write access to your project drive. All types in the library have been released. Note Upgrading a user library If you want to use a user library from an earlier version of WinCC, you must upgrade it. Make sure that all types of the library have been released. The library being upgraded cannot contain a type with the "in progress" status. 4096 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.9 Using global functions Procedure Proceed as follows to upgrade a global library from TIA Portal V12.x or lower: 1. Open the global library. The "Upgrade global library" dialog box opens. 2. Click "OK". A copy of the global library is created and upgraded. The copy of the global library receives the name extension "_V13". The global library opens. Result The global library is stored with the appropriate file extension. See also Basics on version compatibility (Page 4092) Managing libraries (Page 3989) 10.9.9.5 Changing between device versions Selection of the device version When you configure a new HMI device, WinCC automatically selects the latest version of the device. If you want to use a device version other than the one set in WinCC, transfer an image to the HMI device. WinCC provides the images required for the supported HMI devices. Information on the device versions used in WinCC is available in the FAQs on the Internet, entry ID 21742389. NOTICE Changing the device version deletes all data on the HMI device. Data is deleted on the target system if you change the device version. For this reason, you should save existing Runtime data before changing the device version. WinCC Basic V13.0 System Manual, 02/2014 4097 Visualize processes 10.9 Using global functions HMI device configuration The following figure shows the software components of an HMI device: %DVLF3DQHO+0,GHYLFH 5XQWLPHGDWD 5XQWLPHSURMHFW (QJLQHHULQJ6\VWHP 'DWDEDFNXS &RPSLOHG :LQ&&SURMHFW 5XQWLPHVRIWZDUH 'RZQORDG ,PDJH 2SHUDWLQJV\VWHP )LUPZDUH +DUGZDUH 10.9.9.6 Changing the device version Introduction Depending on the required Runtime version, select the suitable device version for your configuration. Note Selection of device versions The selection of available devices versions depends on the version of the project. Requirements A project has been created and opened. The project contains an HMI device. Procedure To change the device version, follow these steps: 1. Double-click on "Devices & Networks" in the project tree. The editor opens. 2. Select the required HMI device from the device view. 3. Select "Change Device/Version" in the device shortcut menu of the HMI device. A dialog opens. 4. Select the required HMI device. 4098 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.9 Using global functions 5. Select the required device version under "Version". 6. Confirm your selection with "OK". Result You have changed the device version in the WinCC project. NOTICE Changing the device version deletes all data on the HMI device. All data is deleted from the HMI device when you change the device version and compile/ download the project. You should therefore backup your Runtime data prior to the download. 10.9.10 Viewing memory card data 10.9.10.1 Basics Introduction WinCC provides you with the possibility of viewing data stored on your memory card. The function supports the use of memory cards of the HMI device and of the CPU. You have the following options: Viewing a backup (Page 4100) Renaming and deleting backups (Page 4101) Auto-Hotspot Auto-Hotspot Auto-Hotspot See also Viewing a backup (Page 4100) Renaming and deleting backups (Page 4101) WinCC Basic V13.0 System Manual, 02/2014 4099 Visualize processes 10.9 Using global functions 10.9.10.2 Working with backups Viewing a backup Introduction The backup of a Basic Panel that is stored on a memory card can also be viewed in the TIA Portal. Requirements WinCC is installed. A memory card with a backup is available. The card reader is connected to the configuration PC. The project view is open. Backup on the memory card in the card reader 1. Insert the memory card into the card reader. 2. Open "SIMATIC Card Reader" in the project navigation. 3. Select the card reader drive. The "Online Card Data" folder is displayed. 4. Open the "Online Card Data" folder 5. Click the backup to open the shortcut menu. 6. Select "Properties". Backup on the memory card of the PLC Proceed as follows if the backup is stored on the memory card of the PLC: 1. Connect the PLC with the configuration PC. 2. Click on the PLC in the project navigation. 3. Select "Connect online" from the shortcut menu. A connection to the PLC is established. Once the PLC is connected, the "Online Card Data" folder is displayed. 4100 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.9 Using global functions 4. Open the "Online Card Data" folder. Note Accessing a password-protected PLC When you attempt to access a PLC that is protected by a password, you will be prompted to enter the password. You need at least read access rights in order to view the data that is stored on the memory card. 5. Click the backup to open the shortcut menu. 6. Select "Properties". Result The backup properties are displayed in a separate dialog. See also Basics (Page 4099) Renaming and deleting backups (Page 4101) Renaming and deleting backups Introduction You may rename and delete backups from a memory card in the project navigation of the TIA Portal. Requirements WinCC is installed. The card reader is connected to the configuration PC. The PLC is connected online with the configuration PC. A memory card with a backup is available. WinCC Basic V13.0 System Manual, 02/2014 4101 Visualize processes 10.10 Compiling and loading The project view is open. The backup is displayed in the project navigation. Note Accessing a password-protected PLC When you attempt to access a PLC that is protected by a password, you will be prompted to enter the password. You need write access rights to rename or delete memory card data. Procedure 1. Click on the backup in the project navigation. 2. Open the shortcut menu. 3. Select "Rename" to rename the file. 4. Enter a new name. 5. Select "Delete" to delete the file. Result The backup file is now renamed or deleted. See also Basics (Page 4099) Viewing a backup (Page 4100) 10.10 Compiling and loading 10.10.1 Compiling and loading projects 10.10.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. 4102 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.10 Compiling and loading Once you have corrected any problems, you download the compiled project to the HMI devices on which the project is to run. 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. Definition of terms 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: (6SURMHFW0L[LQJ %DVLF3DQHO 57SURMHFWV +0,B +0,B %DVLF3DQHO 6FUHHQV +0,WDJV +0,B +0,B 57$GYDQFHG 6FUHHQV +0,WDJV 'RZQORDG )LOHV\VWHP +0,B 5XQWLPH 57$GYDQFHG +0,B &RPSLOH +0,B 573URIHVVLRQDO 6FUHHQV +0,WDJV 'RZQORDG +0,B +0,B )LOHV\VWHP 5XQWLPH 573URIHVVLRQDO +0,B 'RZQORDG )LOHV\VWHP :LQ&& &RQILJXUDWLRQ3& +0,B +0,B )LOHV\VWHP 5XQWLPH +0,GHYLFHV Runtime version The Runtime version depends on the image of the configured HMI device. The Runtime version of the compiled project is displayed under "Info" in the Inspector window. WinCC Basic V13.0 System Manual, 02/2014 4103 Visualize processes 10.10 Compiling and loading 10.10.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: - To only compile changes in the project, select the "Compile > Software (only changes)" 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. 4104 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.10 Compiling and loading 10.10.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. 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 - If the image of the target HMI device does not match the image from the configuration, a prompt is displayed asking whether you want to now change the image. NOTICE Changing the image deletes all data from the HMI device. Data is deleted on the target system if you change the image. For this reason, first back up the following data, if necessary: User administration Recipes - 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 controller tags, you should also compile all modified S7 blocks with the command "Compile > Software" in the shortcut menu before you compile the HMI device. WinCC Basic V13.0 System Manual, 02/2014 4105 Visualize processes 10.10 Compiling and loading Loading with S7 routing Configure the S7 routing settings in the "Devices & Networks" editor in the relevant controller. The settings depend on the device configured. S7 routing supports the following protocols: MPI/PROFIBUS Ethernet Transferring Runtime add-ons Projects can contain Runtime add-ons in the form of controls or CSP (Communication Support Packages). These Runtime add-ons are automatically transferred with the project. 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. If the HMI device supports PROFINET, the name of the HMI device entered in the project navigation is used as the device name for PROFINET communication. The name is written to the HMI device during loading. If a device name for the PROFINET communication has already been entered in the HMI device, it will 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. If the image of the target HMI device does not match the image from the configuration, a prompt is displayed asking whether you want to now change the image. NOTICE Changing the image deletes all data from the HMI device. Data is deleted on the target system if you change the image. For this reason, first back up the following data, if necessary: User administration Recipes 4106 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.10 Compiling and loading Please refer to the documentation for the HMI device used for more detailed information on transfer settings. Note Ending Runtime automatically If automatic transfer is enabled on the HMI device and a transfer is started on the configuration PC, the running project is automatically stopped. The HMI device then switches autonomously to "Transfer" mode. After the commissioning phase, disable the automatic transfer function to prevent the HMI device from switching inadvertently to transfer mode. Transfer mode can cause undesired reactions in the system. To block access to the transfer settings and thus avoid unauthorized changes, assign a password in the Control Panel. 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. 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". WinCC Basic V13.0 System Manual, 02/2014 4107 Visualize processes 10.10 Compiling and loading Result The project is loaded to all selected HMI devices. Any existing project is replaced. The data for user administration and / or recipes is replaced in accordance with the settings in the "Load preview" dialog. During the download, you can keep track of the files that are transferred. 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. Note If the transfer is interrupted, WinCC automatically ensures that no data is lost and that existing data is deleted on the HMI device only after complete transmission. See also Backing up and restoring data of the HMI device (Page 4117) Updating the HMI device operating system (Page 4119) Error messages during loading of projects (Page 4121) Adapting the project for another HMI device (Page 4122) Establishing a connection to the HMI device (Page 4123) 10.10.1.4 Runtime start Starting Runtime on the HMI device Introduction On completion of the project download to the HMI device, you can start the project in Runtime. The project is saved in the HMI device to a file with the following extension: Basic Panels as well as OP 73, OP 77A and TP 177A: "*.srt" The project settings defined in the "Runtime settings" of the HMI device are activated when the project is started in Runtime. 4108 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.10 Compiling and loading The programs that you can use to start projects on the HMI device are available in the Runtime installation folder. Note Ending Runtime automatically If automatic transfer is enabled on the HMI device and a transfer is started on the configuration PC, the running project is automatically stopped. The HMI device then switches autonomously to "Transfer" mode. After the commissioning phase, disable the automatic transfer function to prevent the HMI device from switching inadvertently to transfer mode. Transfer mode can trigger unwanted responses in the plant. To block access to the transfer settings and thus avoid unauthorized changes, assign a password in the Control Panel. Requirement WinCC Runtime is installed on the HMI device. Procedure 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. To select the project file, click "Settings" and enter the path to the project file under "Configuration file". 2. Click "OK" and then "Start". 10.10.2 Simulating projects 10.10.2.1 Simulation basics Introduction You can use the simulator to test the performance of your configuration on the configuration PC. This allows you to quickly locate any logical configuration errors before productive operation. You can start the simulator as follows: In the shortcut menu of the HMI device, or in a screen: "Start simulation" Menu command "Online > Simulation > [Start|With tag simulator|With script debugger]" Under "Visualization > Simulate device" in the portal view. WinCC Basic V13.0 System Manual, 02/2014 4109 Visualize processes 10.10 Compiling and loading Requirements The simulation/runtime component is installed on the configuration PC. Field of application Use the simulator to test various functions of the operator control and monitoring system, such as: Checking limit levels and alarm outputs Consistency of interrupts Configured interrupt simulation Configured warnings Configured error messages Check of status displays Interconnection and screen layout See also Simulating a project (Page 4110) 10.10.2.2 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. 4110 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.10 Compiling and loading 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". 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: WinCC Basic V13.0 System Manual, 02/2014 4111 Visualize processes 10.10 Compiling and loading 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. See also Simulation basics (Page 4109) Working with the tag simulator (Page 4112) 10.10.2.3 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) 4112 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.10 Compiling and loading Column Description 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 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. maxValue 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. WinCC Basic V13.0 System Manual, 02/2014 4113 Visualize processes 10.10 Compiling and loading 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. See also Simulating a project (Page 4110) 10.10.2.4 Simulation restrictions Alarms with dynamic parameters If you use tags or text lists as external tags for alarms, the dynamic parameters of the alarms are not displayed. Only internal tags are enabled for the simulation of alarms in the tag simulator . You can use PLCSim to simulate dynamic parameters. 10.10.3 Servicing the HMI device 10.10.3.1 Overview of HMI device maintenance (Basic Panels) Structure The following figure shows the software components of an HMI device and their relation to the engineering system. 4114 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.10 Compiling and loading %DVLF3DQHO+0,GHYLFH 5XQWLPHGDWD 5XQWLPHSURMHFW (QJLQHHULQJ6\VWHP 'DWDEDFNXS &RPSLOHG :LQ&&SURMHFW 5XQWLPHVRIWZDUH 'RZQORDG ,PDJH 2SHUDWLQJV\VWHP )LUPZDUH +DUGZDUH Runtime data The Runtime data is generated during operation of the plant and stored on the HMI device. This data includes, for example, recipes and data for the user administration. This data is overwritten during loading. If required, save this data before loading a Runtime project. Runtime project The Runtime project contains the compiled configuration data for an HMI device. You download the Runtime project from WinCC to the HMI device. Runtime software and operating system Together, the Runtime software and operating system of an HMI device form the image. Various images are available for the HMI device. All images of an HMI device are available in WinCC. Depending on the configuration, download the appropriate image along with the Runtime project to the HMI device as required. Firmware and hardware The HMI device is delivered with preconfigured firmware and hardware. 10.10.3.2 ProSave Introduction The "ProSave" service tool is installed by default when WinCC is installed. The ProSave functions are accessed in WinCC with the menu "Online > HMI Device maintenance". WinCC Basic V13.0 System Manual, 02/2014 4115 Visualize processes 10.10 Compiling and loading Functional scope ProSave provides all of the functions needed to transfer files to the HMI device. Data backup and restoration of backed-up data Operating system update Communication settings See also Backup of HMI data (Page 4116) Updating the operating system (Page 4118) Overview of HMI device maintenance (Basic Panels) (Page 4114) 10.10.3.3 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, configuration, recipes, user administration, settings Recipes only User administration only Recipes as CSV file A backup file with the extension *.psb is generated when you backup the data of an HMI device. 4116 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.10 Compiling and loading 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 Data backup secures the contents of the flash memory. Note the following when performing a complete data backup and restore operation for HMI devices: In the event of a full restore of all data, all data previously on the device, including the operating system, is deleted irrevocably. If the data restoration was interrupted, execute the command "Reset to factory settings". Restart data restoration. See also Backing up and restoring data of the HMI device (Page 4117) ProSave (Page 4115) Overview of HMI device maintenance (Basic Panels) (Page 4114) 10.10.3.4 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. Requirement The HMI device is connected to the configuration PC The HMI device is selected in the project tree. If a server is used for data backup: The configuration PC has access to the server Backup of the data of the HMI device Proceed as follows to backup the data of the HMI device: 1. Select the "Backup" command from the "Online > HMI Device maintenance" menu. The "Create backup" dialog box opens. 2. Select the type of the PG/PC interface and the target device, and click "Create". The "SIMATIC ProSave" dialog box opens. 3. Select the data to backup for the HMI device under "Data type". 4. Enter the name of the backup file under "Save as". 5. Click "Start Backup". WinCC Basic V13.0 System Manual, 02/2014 4117 Visualize processes 10.10 Compiling and loading 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. The "Restore backup" dialog box opens. 2. Select the type of the PG/PC interface and the target device, and click "Load". The "SIMATIC ProSave" dialog box opens. 3. Enter the name of the backup file under "Save as". Information about the selected backup file is displayed under "File information". 4. 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 4116) Overview of HMI device maintenance (Basic Panels) (Page 4114) 10.10.3.5 Updating the operating system Introduction If the image of an HMI device has a version that does not match the configuration, it is automatically updated, after prompting, during the loading of the project. Loading will then continue. If you decline to update the image, loading is canceled. Updating the image also updates the operating system of the HMI device. Updating the image Connect the HMI device to the configuration PC to update an image. If possible, you should use the interface with the highest bandwidth for this connection, such as Ethernet. Updating the image via a serial connection can take up to an hour. 4118 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.10 Compiling and loading "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 You will require the following to reset to 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 HMI device operating system (Page 4119) ProSave (Page 4115) Overview of HMI device maintenance (Basic Panels) (Page 4114) 10.10.3.6 Updating the HMI device operating system When you update the operating system, the Runtime software on the HMI device is also updated and the device version is changed. NOTICE An operating system update deletes all the data from the HMI device The operating system update deletes all data from the target system. For this reason, you should back up the following data beforehand: User administration Recipes Requirement The HMI device is connected to the configuration PC or the PC with ProSave. The HMI device is selected in the project navigation. Updating the operating system Proceed as follows to update the operating system: WinCC Basic V13.0 System Manual, 02/2014 4119 Visualize processes 10.10 Compiling and loading 1. Select the "Update operating system" command from the "Online > HMI device maintenance" menu. 2. 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 is preset. 3. If required, you can select a different path for the image that you want to transfer to the HMI device. 4. 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. 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 is preset. 3. If required, you can select a different path for the image that you want to transfer to the HMI device. 4. Activate "Reset to factory settings". 5. Click "Update OS". 6. To start "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 updated to the latest version. See also Updating the operating system (Page 4118) Overview of HMI device maintenance (Basic Panels) (Page 4114) 4120 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.10 Compiling and loading 10.10.4 Reference 10.10.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: Incorrect download settings on the HMI device Incorrect HMI device type in the project The HMI device is not connected to the configuration PC. The most common download failures and possible causes and remedies are listed below. The serial download is cancelled Possible remedy: Select a lower baud rate. The download is cancelled due to a compatibility conflict Possible cause Remedy 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. WinCC Basic V13.0 System Manual, 02/2014 Check the device status of the COM connection in the properties window of the Device Manager. 4121 Visualize processes 10.10 Compiling and loading 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). The cause may be the installation of "SIMATIC NET CD 7/2001". Set the access point "S7ONLINE" on the selected device using the "PG/PC Panel" or "Set PC station" application. Check the "baud rate" and "MPI address" network parameters. Download the project from WinCC to the HMI device. Restore the "S7ONLINE" access point to the original device. The configuration is too complex Possible cause Remedy The configuration contains too many different objects or options for the HMI device selected. Remove all objects of a type, e.g. all graphic views. 10.10.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. 4122 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.10 Compiling and loading Use the detail view to copy entries in the project tree for which the "Copy" command is not available in the shortcut menu. Select the "Recipes" entry in the project tree, for example. The recipes are displayed in the detail view. Select the recipes in the detail view and drag them to the "Recipes" entry of the new HMI device. The recipes are copied. You can also select multiple objects in the detail view. Configure the components that cannot be copied, e.g. connections, area pointers, and alarms. Save the project at various points in time. Compile the full project. When the compilation is successfully completed, download the project to the HMI device. Linking references References to linked objects are included in the copying. The references are linked again once the linked objects are copied. Example: You copy a screen in which objects are linked to tags. The tag names are entered at the individual objects after the screen is added to the new HMI device. The tag names are marked in red because the references are open. When you then copy the tags and insert them into the new HMI device, the open references are closed. The red marking for the tag names disappears. For complete references to connected objects in the PLC, you first need to configure a connection to the PLC. Using the information area When you compile the project for the HMI device, errors and warnings are displayed in the "Info" tab of the Inspector window. You can use the shortcut menu command "Go to" to go directly to the location where the error or warning can be corrected. Work through the list of errors and warnings from top to bottom. When the compilation is successfully completed, download the project to the HMI device. 10.10.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. WinCC Basic V13.0 System Manual, 02/2014 4123 Visualize processes 10.11 Operating in Runtime Setting up a connection between the configuration PC and HMI device 1. Check the cable connection between the HMI device and configuration PC. 2. Open the "Devices & Networks" editor in WinCC and start the network view. 3. Select the subnet in the network view and check the settings for the subnet. 4. Select the interface of the HMI device in the network view or device view and check the connection parameters in the Inspector window. 5. Switch on the HMI device and press the "Control Panel" button in the loader. The Control Panel opens. 6. Press "Transfer" twice in the Control Panel. The "Transfer Settings" dialog box opens. 7. Check the settings and then press "Advanced". The [Protocol*] Settings" dialog opens. *: The title of the dialog depends on the protocol used, for example, "PROFIBUS Settings". 8. Check the advanced settings and close the dialog with "OK". Important settings Check the connection settings and in particular the following parameters: Network and station addresses Selected transmission rate Master on the bus; as a general rule, only one master is permitted. If using a configurable adapter for the connection, check the adapter settings, for example, transmission rate, master on the bus. 10.11 Operating in Runtime 10.11.1 Basics 10.11.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. 4124 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.11 Operating in Runtime &RQILJXUDWLRQSKDVH &RQILJXUDWLRQ3& &UHDWHSURMHFW 7HVWWKHSURMHFW 6LPXODWHWKHSURMHFW +0,GHYLFHGHSHQGHQW 6DYHWKHSURMHFW 7UDQVIHUWKHSURMHFW 3URFHVVFRQWUROSKDVH +0,GHYLFH 2SHUDWHWKHSURMHFW &RQQHFWLRQWRWKH3/& 3/& Figure 10-3 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. 10.11.1.2 Tags in Runtime 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. WinCC Basic V13.0 System Manual, 02/2014 4125 Visualize processes 10.11 Operating in Runtime 10.11.1.3 System functions in Runtime Application System functions are used in Runtime for the following purposes: To control the process. To utilize the properties of the HMI device. To configure system setting on the HMI device in online mode. Each system function in WinCC is logically linked with 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. Events The object and the selected function determine the event that can be defined as a trigger for executing a system function. For example, the "Change value", "Low limit violated" and "Upper limit exceeded" events are associated with the "Tag" object. The "Loaded" and "Cleared" events are associated with the "Screen" object. 10.11.2 Commissioning projects 10.11.2.1 Settings in the Runtime software Open the WinCC configuration software and make the following settings for the runtime software: Display on the PLC In WinCC, configure the visual representation of the generated project in runtime. The screen resolution is fixed for Basic Panels. Scroll bars will appear if the screen is larger than the configured screen resolution. To switch off the taskbar, select the Start menu command "Settings > Taskbar". In the "Properties of the Taskbar" dialog, disable the options "Always on top" and "Auto hide". 4126 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.11 Operating in Runtime Dialog fonts The dialog text will be shown in the standard font. Define the default font under "Language & Font" in the "Device Settings" editor. Disabling program switching You lock program switching to prevent operators from calling other applications in Runtime. Click "Window" in the "Device Settings" editor and select the option "Disable program switching". Also hide the Windows taskbar. Note Stop runtime Always configure a softkey or button for calling the "StopRuntime" system function if you lock program switching. Otherwise, you will not be able to close either runtime or Windows. 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. 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. WinCC Basic V13.0 System Manual, 02/2014 4127 Visualize processes 10.11 Operating in Runtime 10.11.2.2 Loading projects 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. 4128 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.11 Operating in Runtime 10.11.2.3 Starting Runtime on the Engineering Station Introduction You can start your project in Runtime at the engineering station while performing the configuration in WinCC. However, this so-called online configuration is subject to certain limitations. The project cannot be compiled in the background while Runtime is active on the Engineering Station. 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. When the project is started in Runtime, the settings you have stored in your project for the HMI device in the "Configuration" editor take effect. Requirement A project is open on the Engineering Station. Procedure Proceed as follows to start Runtime on the Engineering Station: 1. Select the desired HMI device in the project tree. 2. Select the menu command "Online > Start Runtime". 3. If you want to edit project data after Runtime was started on the Engineering Station, select the "Compile > Software" command in the shortcut menu of the HMI device. The updated project is displayed in the Runtime on the Engineering Station. 10.11.2.4 Starting Runtime on the HMI device Introduction On completion of the project download to the HMI device, you can start the project in Runtime. The project is saved in the HMI device to a file with the following extension: Basic Panels as well as OP 73, OP 77A and TP 177A: "*.srt" The project settings defined in the "Runtime settings" of the HMI device are activated when the project is started in Runtime. WinCC Basic V13.0 System Manual, 02/2014 4129 Visualize processes 10.11 Operating in Runtime The programs that you can use to start projects on the HMI device are available in the Runtime installation folder. Note Ending Runtime automatically If automatic transfer is enabled on the HMI device and a transfer is started on the configuration PC, the running project is automatically stopped. The HMI device then switches autonomously to "Transfer" mode. After the commissioning phase, disable the automatic transfer function to prevent the HMI device from switching inadvertently to transfer mode. Transfer mode can trigger unwanted responses in the plant. To block access to the transfer settings and thus avoid unauthorized changes, assign a password in the Control Panel. Requirement WinCC Runtime is installed on the HMI device. Procedure 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. To select the project file, click "Settings" and enter the path to the project file under "Configuration file". 2. Click "OK" and then "Start". 10.11.2.5 Testing a project Introduction You have the following options for testing a WinCC project: 4130 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.11 Operating in Runtime 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 a project". The simulator enables you to test the following: - 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. 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, but you cannot exchange data with the PLC and vice versa. Set the "Offline" mode on the HMI device by assigning the system function "SetDeviceMode" to an operator control. 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 control the plant using the HMI device based on the configuration. Set the "Online" mode on the HMI device by assigning the system function "SetDeviceMode" to an operator control. Procedure Proceed as follows to simulate a project without a PLC connection to the configuration PC: 1. Create 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 the menu command "Online > Simulate Runtime > With tag simulator". When you simulate 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 is opened. The simulation table "*.six" contains all the settings required for the simulation. For additional information, refer to "Working with the tag simulator". 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 the settings for the simulation using the menu command "File > Save." Enter a name to save the file.. The file name is automatically assigned the extension "*.six". 10.11.2.6 Closing a project Introduction You define the steps in closing Runtime in the user program: WinCC Basic V13.0 System Manual, 02/2014 4131 Visualize processes 10.11 Operating in Runtime Procedure Exit Runtime as follows: 1. When Runtime is running, you can close it using the close symbol or the Task Manager. 2. When Runtime is running, press the relevant button to close Runtime. The close of Runtime is especially configured. 10.11.2.7 Backing up and restoring data of the HMI device Introduction Backup the data of an HMI device at regular intervals. Working from the engineering station to which an HMI device is connected, you can backup and restore the data of this HMI device using WinCC. You have the option of conveniently performing a central data backup using ProSave on a computer without WinCC installation. Requirement The HMI device is interconnected with the Engineering Station or the computer is connected with ProSave. The HMI device whose data should be backed up or restored is selected in the project tree. The settings for loading are correctly set in the properties of the HMI device. When using a special storage medium, such as a data server: The HMI device is connected to the storage medium. Procedure Proceed as follows to back up the data: 1. Select the "Backup" command from the "Online > Device maintenance" menu. 2. Select the scope of the backup: "Complete backup," "Recipes," or "User administration." 3. Click "...", select the storage location in the "Select backup file" dialog, and specify a file name. 4. Click "OK." This starts the data backup. The backup can take some time. Procedure for restoring data 1. Select the "Restore" command from the "Online > Device maintenance" menu. 2. Click "...", and select the storage location and file in the "Open" dialog. The "Content" area indicates which HMI device is the origin of the data backup and the scope of the data backup. 3. Click "OK." 4132 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.11 Operating in Runtime This starts the restoration. This process can take some time. 10.11.3 Languages in runtime 10.11.3.1 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 "Language order" is displayed. Setting runtime languages during configuration You can specify the following in the "Language and Font" editor: The project languages available as runtime languages for the HMI device. The order in which the languages are switched. 10.11.3.2 Setting a runtime language Introduction The "Language & Font" editor shows all project languages available in the project. You can select the project languages to be available as runtime languages on the HMI device. In addition, you specify the order in which the languages will be switched. Requirement Multiple languages are enabled in the "Project languages" editor. Procedure 1. Open the "Language & Font" editor under "Device settings". 2. In the "Runtime language" column, select the the languages to be used when runtime first starts. The selected language is assigned the number "0" in the "Language order" column. WinCC Basic V13.0 System Manual, 02/2014 4133 Visualize processes 10.11 Operating in Runtime 3. In the "Runtime language" column, select the language to be activated next when the language is switched. The selected language is assigned the number "1" in the "Language order" column. 4. Select additional languages in the order in which they are to be activated when the language is switched. If the number of languages selected exceeds the number that can be loaded on the HMI device, the table background changes in color. 5. If you want to change the order of a language, select the desired row and then select the shortcut menu command "Move up" or "Move down". Result The enabled runtime languages are transferred with the compiled project to the HMI device. When runtime starts the first time, the project is displayed in the language with the lowest number in the "Language order." If language switching by means of the "SetLanguage" system function has been configured, the specified number sequence determines the order in which the languages are switched. 10.11.3.3 Setting the 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 if you cannot define a specific font. WinCC offers only fonts supported by the HMI device. 4134 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.11 Operating in Runtime 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. Requirement Multiple languages are enabled in the "Project languages" editor. Procedure 1. Open the "Language & Font" editor under "Device settings". 2. Enable the languages to be displayed on the HMI device in the "Runtime language" column. In the "Fixed font 0" column, WinCC shows the fonts used by default in runtime. 3. In the "Configured font 0" column, select another font for each language you want to have available during configuration. These fonts are transferred to the HMI device during a transfer operation. 4. In the "Standard font" column, select the font to be used by default if a font cannot be selected for a text. Result The project texts for the selected language are displayed in the selected font on the HMI device. 10.11.3.4 Configuring 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. 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. Configure the "SetLanguage" system function for each font with the number of the language or the language ID as a parameter. Language switching The operator toggles through all languages using a button. Configure "SetLanguage" system function for the button with the "Toggle" parameter. The language is enabled in the order you have specified in the "Language & Font" editor. 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. WinCC Basic V13.0 System Manual, 02/2014 4135 Visualize processes 10.11 Operating in Runtime 10.11.3.5 Specific features of Asian and Eastern languages in runtime Introduction When configuring for Asian languages some specific features should be observed for operation in runtime. Note You can only use Asian fonts supported by your configuration computer during configuration. Memory requirement for Asian character sets The memory requirement is of course greater when using Asian languages. Therefore, pay attention to any error messages when compiling the project. Inputting Eastern and Asian characters (not ANSI) You cannot enter Eastern and Asian characters in runtime on the Basic Panels. Interpretation of Asian characters When using Sm@rtAcess and Sm@rtService, only the characters known on the HMI device can be used. To be able to use Asian characters, these must be configured in the engineering system. Additionally configured characters require additional memory on the HMI device. Pay attention to the amount of available memory on the HMI device. Font size for Asian character sets Use at least a font size of 10 points to display the text of projects created for Asian languages in runtime. Asian characters will become illegible if smaller font sizes are used. This also applies to the default font used in the "Language & Font" editor. Text field length for Asian languages Make allowances for an appropriate length of the text fields when working on multilingual projects with Asian languages. Field contents may be partially hidden, depending on the font and the font size. 1. Open the "Properties > Appearance" text box in the Inspector window. 2. Under "Fit to size", disable the "Auto-size" option. 3. Verify the proper display in runtime. 4136 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.11 Operating in Runtime 10.11.4 Operating projects 10.11.4.1 Basics Overview of operator control over a project All Basic HMI devices feature a touch screen. Certain Basic HMI devices feature function keys. Use the touch screen and function keys to operate the Control Panel or the project running on your HMI device. DANGER Incorrect operation A project can contain certain operations that require in-depth knowledge about the specific plant on the part of the operator. Ensure that only trained professional personnel operate the plant. Operating the touch screen NOTICE Damage to the touch screen Pointed or sharp objects can damage the plastic surface of the touch screen. Always operate the touch screen with your fingers or with a touch pen only. Triggering unintended actions Touching several operator controls at the same time can trigger unintended actions. Touch only one operator control on the screen at a time. Operator controls are touch-sensitive symbols on the screen of the HMI device. They are basically operated in the same way as mechanical keys. You activate operator controls by touching them with your finger. Note The HMI device returns a visual feedback as soon as it detects that an operator control has been touched. The visual feedback is independent of any communication with the PLC. The visual feedback signal therefore does not indicate whether or not the relevant action is actually executed. Examples of operator controls: WinCC Basic V13.0 System Manual, 02/2014 4137 Visualize processes 10.11 Operating in Runtime Buttons Buttons can assume the following states: "Untouched" "Touched" Invisible buttons The focus of invisible buttons is by default not indicated following selection. 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 operator control. I/O fields A screen keyboard appears as visual feedback after you touched an I/O field, for example, to enter a password. Depending on the HMI device and the configured operator control, the system displays different screen keyboards for entering numerical or alphanumerical values. The screen keyboard is automatically hidden again when input is complete. Operating function keys The function keys can be assigned global or local functions: Function keys with global function assignment A function key with global function assignment always triggers the same action on the HMI device or in the PLC, regardless of the currently displayed screen. The activation of a screen or the closing an alarm window, for example, is such an action. 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 to a function key can vary from screen to screen. The function key could be assigned only a single function within a screen only, that is, either a global or a local function. Local function assignments override global function assignments. General functions of the screen keyboard The following keys are available on the screen keyboard of all Basic HMI devices: Cursor left Cursor right Deleting a character Cancel input Confirm input Displaying infotext. This key only appears when an infotext has been configured for the operator control. 4138 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.11 Operating in Runtime Entering data on the KTP400 Basic Due to the small display, the screen keyboard and the input concept of the KTP400 Basic differs compared to other Basic HMI devices. 7H[W 7H[W 681 ,FRQV 1XPEHUV 681 681 The screen keyboard appears on the HMI device touch screen when you touch an operator control that requires input. The screen keyboard of the KTP400 features four views. You can change the view while making entries using the buttons in the fourth row of the screen keyboard: Button Changes to the view Entering text, characters "A" to "M" Entering text, characters "N" to "Z" Entering numbers, "0" to "9," signed or unsigned and with or without decimal places Entering special characters Entering text, shift to lower case letters WinCC Basic V13.0 System Manual, 02/2014 4139 Visualize processes 10.11 Operating in Runtime Note Job mailbox has no effect PLC job 51 "Select screen" has no effect while the screen keyboard is open. Key assignment The alphanumerical keyboard layout is monolingual. A language change within the project does not have any effect on the layout of the alphanumerical screen keyboard. Entering alphanumerical values 1. Touch the desired operator control on the screen. The alphanumerical screen keyboard opens. 2. Enter the value. Depending on the settings, the HMI device outputs an audible signal. You can change the view of the screen keyboard using the keys <NZ> and <AM>. Use the <Shift> key to enter lower-case letters. 3. Press <Return> key to confirm your entries, or cancel them with <ESC>. Either action closes the screen keyboard. Entering numerical values 1. Touch the desired operator control on the screen. The numerical screen keyboard opens. 2. Enter the value. Depending on the settings, the HMI device outputs an audible signal. You can change the view of the screen keyboard for entering numbers with hexadecimal notation using the <NZ> and <AM> keys. 3. Press <Return> key to confirm your entries, or cancel them with <ESC>. Either action closes the screen keyboard. Checking numerical value limits Tags can be assigned limit values. Any entry of a value outside this limit is rejected. If an alarm view is configured, a system event is triggered and the original value is displayed again. 4140 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.11 Operating in Runtime Decimal places of numerical values The configuration engineer can define the number of decimal places for a numerical text box. The number of decimal places is checked when you enter a value in this type of I/O field. Decimal places that exceed the limit are ignored. Unused decimal places are padded with "0" entries. Entering data on the KTP600, KTP1000, TP1500 Basic Alphanumerical screen keyboard The screen keyboard appears on the HMI device touch screen when you touch an operator control that requires input. 7H[W 1XPEHUV 681 )))) Note Job mailbox has no effect PLC job 51 "Select screen" has no effect while the screen keyboard is open. Key assignment The alphanumerical keyboard layout is monolingual. A language change within the project does not have any effect on the layout of the alphanumerical screen keyboard. WinCC Basic V13.0 System Manual, 02/2014 4141 Visualize processes 10.11 Operating in Runtime Entering alphanumerical values 1. Touch the desired operator control on the screen. The alphanumerical screen keyboard opens. 2. Enter the value. Depending on the settings, the HMI device outputs an audible signal. Use the <Shift> key to enter lower-case letters. 3. Press <Return> key to confirm your entries, or cancel them with <ESC>. Either action closes the screen keyboard. Entering numerical values 1. Touch the desired operator control on the screen. The numerical screen keyboard opens. 2. Enter the value. Depending on the settings, the HMI device outputs an audible signal. 3. Press <Return> key to confirm your entries, or cancel them with <ESC>. Either action closes the screen keyboard. Checking numerical value limits Tags can be assigned limit values. Any entry of a value outside this limit is rejected. If an alarm view is configured, a system event is triggered and the original value is displayed again. Decimal places of numerical values The configuration engineer can define the number of decimal places for a numerical text box. The number of decimal places is checked when you enter a value in this type of I/O field. Decimal places that exceed the limit are ignored. Unused decimal places are padded with "0" entries. 4142 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.11 Operating in Runtime 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 contain, for example, information on the value to be entered. Procedure Proceed as follows to open the tooltip for operator controls: 1. Touch the required operating element. key indicates whether a The screen keyboard opens. The representation of the 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 tooltips 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. WinCC Basic V13.0 System Manual, 02/2014 4143 Visualize processes 10.11 Operating in Runtime 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. 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. 10.11.4.2 Operating objects Bar Application The bar is a dynamic display object. The bar displays a value from the PLC as a rectangular area. The bar allows you to recognize the following at a glance: The distance of the current value from the configured limit values Whether a set point value has been reached The bar can display values such as fill levels or batch counts. 4144 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.11 Operating in Runtime Layout The layout of the bar depends on the configuration: The bar may feature a scale of values The configured limit values can be indicated by lines Color changes can signal when a limit value has been exceeded or has not been reached Date/time field Overview Application A "Date / time box" may have the following runtime functions: Output of the date and time Combined input and output; here the operator can edit the output values so as to reset the date and time. Layout The appearance of the date/time field depends on the language set in the HMI device. The date can be displayed in detail (e.g. Tuesday, 31 December 2003) or in short form (31.12.2003). Operation Depending on the configuration, you can operate the date/time field in the following ways: Standard operation: Change date and time. Runtime behavior When the operator ignores the syntax when entering values, or enters illegal values, the system rejects these. Instead, the original values (plus the time that has elapsed in the meantime) appears in the date/time field and a system alarm is displayed on the HMI device. WinCC Basic V13.0 System Manual, 02/2014 4145 Visualize processes 10.11 Operating in Runtime Touch and key operation Touch operation Proceed as follows to operate the date/time field: 1. Touch the date/time field on the touch screen of the HMI device. The on-screen keyboard is displayed automatically. 2. Enter the required value using the on-screen keyboard. 3. Press <ENTER> to confirm your entry, or cancel it with <ESC>. The on-screen keyboard is cleared automatically after you have confirmed or canceled your entries. Key operation Activate the date/time field, for example, with one or several according to the configured tab sequence. A color frame signals the selected state of the field content. Procedure Proceed as follows to operate the date/time field: 1. Position the cursor using the cursor keys and enter the value. 2. Press . The object changes to the special editing mode. Only one character at any time is marked in the field. - Use the cursor keys / - Use the cursor keys / 3. Confirm your entry with to scroll a character table. to move the cursor to the next or previous input position. , or discard it with . I/O field Overview Application You enter numeric or alphanumeric values in an I/O field. For example, a numeric value could be the number 80 as a temperature reference; an alphanumeric value could be the text "Service" as a user name. 4146 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.11 Operating in Runtime Layout The appearance of the I/O field depends on the configuration: Numeric I/O field For input of numbers in decimal, hexadecimal or binary format. Alphanumeric I/O field For input of character strings. I/O field for date and time For input of calendar dates or time information. The format depends on the set configuration. I/O field for password entry For concealed entry of a password. The entered character string is displayed with placeholders (*). Operation Depending on the configuration, you can operate the I/O field in the following ways: Standard operation: Enter a value in the I/O field. Event: An event is triggered when you operate the I/O field, for example, when you activate it. The processing of a function list can be configured to the event. Runtime behavior Limit value test of numerical values Tags can be assigned limit values. 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 alarm, 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 text box. 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". Hidden input A "*" is displayed for every character during hidden input. The data format of the value entered cannot be recognized. Behavior when switching between input fields When you change to another input field within the same screen, and the screen keyboard appears, the "Exit field" event is not executed for the previous field unless you close the screen keyboard. WinCC Basic V13.0 System Manual, 02/2014 4147 Visualize processes 10.11 Operating in Runtime Touch and key operation Touch operation Proceed as follows to operate the IO field: 1. Touch the IO field on the touch screen of the HMI device. The on-screen keyboard is displayed automatically. 2. Enter the required value using the on-screen keyboard. 3. Press <ENTER> to confirm your entry, or cancel it with <ESC>. The on-screen keyboard is cleared automatically after you have confirmed or canceled your entries. Key operation Activate the IO field,for example, with one or several according to the tab sequence configured. A color frame signals the selection of the field content. Procedure Proceed as follows to operate the IO field: 1. Position the cursor using and a cursor key. 2. This step cancels the field content selection. Enter the desired value. 3. Press . The object will change to special editing mode. Only one character at any time is marked in the field. - Use the cursor keys / to scroll a character table. - Use the cursor keys / to move the cursor to the next or previous input position. 4. Confirm your entry with , or discard it with . Note Enable the input of hexadecimal characters "A" to "F" for numerical values by toggling the . input keys to character mode using the key 4148 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.11 Operating in Runtime Graphic view Application The graphic view displays graphics. Layout The appearance of the graphic depends on the configuration. The graphic view, for example, adapts automatically to the size of the graphic. Note If you use bitmaps with the "Transparent color" setting in WinCC screens, requires highperformance display on the Panel HMI devices. Performance is enhanced by disabling the "Transparent color" setting in the properties of the respective graphic object. This restriction applies in particular when bitmaps are used as background image. Operation The graphic display is for display only and cannot be operated. Graphic I/O field Overview Application A graphic IO field can have the following Runtime functions: Output of graphic list entries Combined input and output Example of its use as output field: WinCC Basic V13.0 System Manual, 02/2014 4149 Visualize processes 10.11 Operating in Runtime To indicate the Runtime status of a valve, the graphic IO field outputs the image of a closed or open valve. Operation Depending on the configuration, you can operate the graphic IO field in the following ways: Standard operation: Select an entry from the graphic list. Event: An event is triggered when you operate the graphic IO field, e.g. when you activate it. The processing of a function list can be configured to the event. Runtime behavior If the graphic IO field displays a cactus image, you have not defined a graphic to be output for a specific value in your project. The contents of the graphic IO field change color to show that it is now activated. The frame in 3D is only shown graphically in an output field. Touch and key operation Touch operation Touch the graphic IO field on the touch screen of the HMI device. Selection mode is now enabled. Select the graphic object using the scroll bar. Touch the selected graphic object to save it or discard the selection by touching a different screen object. 4150 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.11 Operating in Runtime Key operation How to use a graphic IO field on the keyboard device: Step Procedure 1 Select the graphic IO field e.g. The graphic IO field is marked. 2 Enable the selection mode ENTER The selection mode is now enabled. 3 Select an entry 4 Accept selection Moves the cursor by lines. ENTER or Cancel selection ESC The entry selected is now valid. The selection mode is closed. The original value is restored. Trend view Overview Application The trend view is a dynamic display object. The Trend view can display actual process data and process data from a log continuously when it is supported by the HMI device. Layout The layout of the trend view is based on the configuration. A trend view can show multiple curves simultaneously to allow the user, for example, to compare different process sequences. If the displayed process value exceeds or falls below the configured limit values, the violation of the limit can be displayed by a change of color in the curve. A ruler can also simplify the reading of the process values from the trend view. The ruler displays the Y-value that belongs to an X-value. WinCC Basic V13.0 System Manual, 02/2014 4151 Visualize processes 10.11 Operating in Runtime Operation Depending on the configuration you can: The displayed time section extends. The displayed time section reduces. Scroll back by one display width. Scroll forwards by one display width. Stop or continue the trend recording. Operator controls The buttons have the following functions: Operator control Function Scrolls back to the start of trend recording. The start values of the trend recording are displayed there. Zooms the displayed time section Zooms out of the displayed time section Moves the ruler backwards (to the left). Moves the ruler forward (to the right). Scrolls back by one display width (to the left). Scrolls forward by one display width (to the right). Shows or hides the ruler. The ruler displays the X-value associated with a Y-value. Stops or continues trend recording Touch and key operation Procedure Touch the relevant operator controls of the trend view on the touch screen of the HMI device. Procedure Select the trend view with the TAB key using the configured tab sequence. The table below lists the key shortcuts available: 4152 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.11 Operating in Runtime Keys Function CTRL ENTER Scrolls back to the start of trend recording. The start values of the trend recording are displayed there. CTRL + CTRL + CTRL + ALT + Moves the ruler backwards (to the left). CTRL + ALT + Moves the ruler forward (to the right). SHIFT + Scrolls back by one display width (to the left). SHIFT + Scrolls forward by one display width (to the right). Y + Z Enlarges the time section displayed. Reduces the time section displayed. Button Overview Application A button is a virtual key on the screen of the HMI device that can have one or more functions. Layout The layout of the button depends on the button type. Button with text: The text shown on the button gives information regarding the status of the button. Button with graphic: The graphic shown on the button gives information regarding the status of the button. Invisible: The button is not visible during Runtime. Operation Depending on the configuration, you can operate the button in the following ways: Standard operation: Click the button. Event: An event is triggered when you operate the button, e.g. when you click it. The processing of a function list can be configured to the event. Runtime behavior The operation may be followed with a optical feedback. However, note that the optical feedback only indicates a completed operation and not whether the configured functions were actually executed. WinCC Basic V13.0 System Manual, 02/2014 4153 Visualize processes 10.11 Operating in Runtime Touch and key operation Procedure Touch the button on the touch screen of the HMI device. Procedure How to operate a button on the keyboard device: 1. Select the button using a cursor key, e.g. 2. Next, press the ENTER or the key. Switch Overview Application The switch is an operating element and display object with two states: "pressed" and "released." Switches can signal the state of a system component that cannot be seen from the HMI device, e.g. a motor. You can also change the state of that system component at the HMI device. Layout The layout of the switch depends on the switch type. Switches: The switch has a slider. The position of this slider gives information about the status of the switch. Switch with text: The text shown on the switch gives information regarding the status of the switch. Switch with graphic: The graphic shown on the switch gives information regarding the status of the switch. Operation Depending on the configuration, you can operate the switch in the following ways: Standard operation: Click the switch. Event: An event is triggered when you operate the switch, e.g. when you click it. The processing of a function list can be configured to the event. 4154 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.11 Operating in Runtime Runtime behavior A switch has two stable states: When you activate the switch, it changes to the other state. The switch retains this state until the next operation. Touch and key operation Touch operation Touch operation of the switch differs, depending on its type: If a slider is displayed for the switch: Drag the slider to the new position on the touch screen of the HMI device or double-click in the slider range. If only a text or graphic object is displayed for the switch: Touch the switch on the touch screen of the HMI device. Key operation How to operate a switch on the keyboard device: Select the switch using a cursor key, e.g. Next, press the ENTER or the key. Symbolic I/O field Overview Application A symbolic IO field can be assigned the following functions in Runtime: Output of text list entries Combined input and output Example of its use as combination IO field: You control a motor in Runtime by selecting the "Motor OFF" or "Motor ON" text from the text list. The motor is started or stopped in accordance with the selection. The symbolic IO field visualizes the current status of the motor. WinCC Basic V13.0 System Manual, 02/2014 4155 Visualize processes 10.11 Operating in Runtime Operation The following options of operating the symbolic IO field are available, depending on the configuration: Standard operation: Select an entry from the text list. Event: You trigger an event by operating the symbolic IO field, e.g. by enabling it. The processing of a function list can be configured to the event. Runtime behavior The selection list of the symbolic IO field displays an empty text line if a corresponding entry was not defined in project data. The active state is indicated on the HMI device by changing the color of contents of the symbolic IO field. Touch and key operation Touch operation Touch the symbolic IO field on the touch screen of the HMI device. The selection list displays the default entries. If the selection list displays a scroll bar: Touch the scroll bar on the touch screen of the HMI device. Touch the scroll bar and drag to the required position on the touch screen. Select the entry and accept the corresponding tag value by touching the entry on the screen. The selection list closes and the entry is displayed. The focus is still set on the symbolic IO field. Key operation How to operate a symbolic IO field on the keyboard device: Step Procedure 1 Select the symbolic IO field e.g. The symbolic IO field is marked. 2 Open selection list ENTER The drop down list box opens. 3 Select an entry 4 Accept the selection Moves the cursor by lines. ENTER Or Canceling the selection 4156 ESC The entry selected is now valid. The selection list is closed. The original value is restored. The selection list is closed. WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.11 Operating in Runtime 10.11.4.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. 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. WinCC Basic V13.0 System Manual, 02/2014 4157 Visualize processes 10.11 Operating in Runtime 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. Note 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. 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. 4158 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.11 Operating in Runtime 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 logon 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. 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. WinCC Basic V13.0 System Manual, 02/2014 4159 Visualize processes 10.11 Operating in Runtime Procedure for key operation Proceed as follows: 1. Select the "User" input field within the logon dialog by pressing the 2. Enter the user name using the system keys. Switch the numerical keypad to alphabet mode using the 3. Use the key. key to enter letters. 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. 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. 4160 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.11 Operating in Runtime Creating users Requirement The user view is open. You are either authorized for user administration or you are an administrator. A user group has been created. Note 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. Note 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. WinCC Basic V13.0 System Manual, 02/2014 4161 Visualize processes 10.11 Operating in Runtime Changing the user Requirement The user view is open. Your authorization level determines the data you can change: 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. Note 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. 4162 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.11 Operating in Runtime Result User data have been changed. Deleting a user 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. Note 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. 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. WinCC Basic V13.0 System Manual, 02/2014 4163 Visualize processes 10.11 Operating in Runtime 10.11.4.4 Operating alarms Overview Alarms Alarms indicate events and states on the HMI device which have occurred in the plant, 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 Alarm text Event text Location of fault Status Alarm class Alarm number Alarm group Supports diagnostics Alarm classes Alarms are assigned to various alarm classes. The selection depends on the HMI device. "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. 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. "Diagnosis Events" SIMATIC diagnostic alarms show states and events in the SIMATIC S7 controllers. 4164 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.11 Operating in Runtime Note Availability for specific devices Diagnostic alarms are not available for Basic Panels. STEP 7 alarm classes The alarm classes configured in STEP 7 are also available to the HMI device. Note Availability for specific devices STEP 7 alarm classes are not available for Basic Panels. Custom alarm classes The properties of this alarm class must be defined in the configuration. Alarm buffer Alarm events are saved to an internal buffer. The size of this alarm buffer depends on the HMI device type. Alarm report When alarm report is enabled in the project, alarm events are output directly to the connected printer. You can set the reporting function separately for each alarm. The system outputs "Incoming" and "Outgoing" alarm events to the printer. 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 complete 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. Note Availability for specific devices Alarm reports are not available for Basic Panels. 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. Note Availability for specific devices Alarm logs are not available for Basic Panels. WinCC Basic V13.0 System Manual, 02/2014 4165 Visualize processes 10.11 Operating in Runtime Alarm view The alarm view shows selected alarms or alarm events from the alarm buffer or alarm log. Whether alarms 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 acknowledgment 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. Either the current alarm or the oldest alarm is 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 icon that is displayed on the screen when an alarm of the specified alarm class is incoming. The alarm indicator can assume 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 displayed indicates the number of pending alarms. Simple alarm view, alarm window Use The simple alarm view shows selected alarms or alarm events from the alarm buffer or alarm log. The layout and operation of the simple alarm window correspond to that of the simple alarm view. Note The "Single alarm view" object cannot be operated dynamically with a script. In the Engineering System you can dynamically control the visibility of an object, for example, in the "Animations" tab of the Properties window. In Runtime, the "Simple alarm view" does not support animations. If you have configured an animation and wish to perform a consistency check of the project, for example, then an error alarm is issued in the Output window. 4166 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.11 Operating in Runtime 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: Icon Alarm class ! "Errors" (empty) "Warnings" (depends on the configuration) Custom alarm classes $ "System" Operation Depending on the configuration you can: Acknowledge alarms Edit alarms Control elements The buttons have the following functions: Button Function Acknowledge alarm Edit alarm Display infotext for an alarm Shows the full text of the selected alarm in a separate window, the alarm text window. In the alarm text window, you can view alarm text that requires more space than is available in the alarm view. Close the alarm text window with . Scrolls one alarm up Scrolls one page up in the alarm view WinCC Basic V13.0 System Manual, 02/2014 4167 Visualize processes 10.11 Operating in Runtime Button Function Scrolls one page down in the alarm view Scrolls one alarm down Layout of the operator controls The layout of the buttons for operating the simple alarm view depends on the configured size. Therefore check if all the required buttons are available on the HMI device. Detecting pending alarms Introduction You can recognize the presence of alarms which must be acknowledged by the following: For an HMI device with keys: The LED of the key is lit. Depending on the configuration: An alarm indicator is displayed on screen. The configuration determines whether an alarm has to be acknowledged or not. This is also defined by the alarm class which an alarm belongs to. LED in the "ACK" key An LED is integrated in the key on HMI devices with keyboard. The LED is lit if there are alarms requiring acknowledgment which must still be acknowledged. The LED goes out when you acknowledge all alarms requiring acknowledgment. Alarm indicator The alarm indicator is a graphic symbol indicating pending alarms or alarms requiring acknowledgment, depending on the configuration. Figure 10-4 4168 Alarm indicator with three pending alarms WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.11 Operating in Runtime Layout The alarm indicator can assume one of two states: Flashing: The alarm indicator flashes as long as alarms are pending for acknowledgment. The number displayed indicates the number of pending alarms. The project engineer can configure specific functions to be executed by operating the alarm indicator. Static: The alarms are acknowledged but at least one of them is not yet deactivated. Displaying dialogs The displayed alarm indicator view is covered, for example, by the logon dialog, help dialog or alarm text windows. The alarm indicator is visible once you close these dialogs. Display infotext for alarm Procedure for touch operation Proceed as follows to display the info text: 1. Touch the relevant alarm in the alarm view or in the alarm window. The alarm is selected. 2. Touch the button in the simple alarm view or in the advanced alarm view. If configured, the info text assigned to this alarm is displayed. 3. Close the screen for displaying the Info text by means of the button. Procedure for key operation Proceed as follows to display the info text: 1. Select the desired alarm in the alarm view. 2. Press the key . If configured, the info text assigned to this alarm is displayed. 3. Close the info text by pressing the key. Acknowledge alarm Requirement The alarm to be acknowledged is displayed in the alarm window or the alarm view. WinCC Basic V13.0 System Manual, 02/2014 4169 Visualize processes 10.11 Operating in Runtime Procedure for touch operation To acknowledge an alarm, proceed as follows: 1. Touch the relevant alarm in the alarm view or in the alarm window. The alarm is selected. 2. Touch the in the advanced alarm view. button in the simple alarm view or Procedure for key operation The alarm view and the alarm window have a tab sequence with which you can select operator controls and the last selected alarm using the keyboard. To acknowledge an alarm, proceed as follows: 1. Select the desired alarm view or alarm window using the 2. Select the desired alarm. Use the 3. Press the key , , or key. keys accordingly. . Alternative operation Depending on the configuration, you can also acknowledge an alarm with a function key. Result The alarm is acknowledged. If the alarm belongs to an alarm group, all the alarms of the associated group are acknowledged. Editing an alarm Introduction The configuration engineer can assign additional functions to each alarm. These functions are executed when the alarm is processed. Note When you edit an unacknowledged alarm, it is acknowledged automatically. Requirement The alarm to be edited is displayed in the alarm window or the alarm view. 4170 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.11 Operating in Runtime Procedure for touch operation Proceed as follows to edit an alarm: 1. Touch the relevant alarm in the alarm view or in the alarm window. The alarm is selected. 2. Touch the button in the simple alarm view or in the enhanced alarm view. Procedure for key operation Proceed as follows to edit an alarm: 1. Select the desired alarm view or alarm window with 2. Select the desired alarm. Use the HOME , END , 3. Continue to press the key TAB until the button in the extended alarm view. 4. Confirm your entry by pressing the key ENTER or TAB . keys. is selected in the simple alarm view or . Result The system executes the additional functions of the alarm. Additional information on this topic may be available in your plant documentation. 10.11.4.5 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. WinCC Basic V13.0 System Manual, 02/2014 4171 Visualize processes 10.11 Operating in Runtime File cabinet Drawer Drawer Drawer Drawer Recipe collection Recipe Recipe Recipe Recipe Recipes for a fruit juice plant Orange flavored drinks Grape flavored drinks Apple flavored drinks 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. Drawer Suspension Recipe Product variants of apple flavored drinks Recipe data record Apple drink Recipe data record Apple nectar 4172 folder Suspension folder Suspension folder Recipe data record Apple juice WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.11 Operating in Runtime 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. 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. WinCC Basic V13.0 System Manual, 02/2014 4173 Visualize processes 10.11 Operating in Runtime Data flow The following figure shows the data flow in a project with recipes: +0,GHYLFH 5HFLSHPHPRU\ 5HFLSHYLHZ 5HFLSH VFUHHQ 5HFLSHWDJ 5HFLSH 5HFLSH 5HFLSH 5HFLSHQ 3/& 0HPRU\FDUG 4174 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 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.11 Operating in Runtime Simple recipe view Layout The simple recipe view consists of three areas: Recipe list Data record list Element list Figure 10-5 Simple recipe view - example with data record list 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 can use the simple recipe view as follows, depending on the configuration: Create, change, copy or delete recipe data records Read recipe data records from the PLC or transfer to the PLC Operator controls of the simple recipe view 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. Key Touching an entry Function The next lowest display area is opened, i.e. the data record list or the element list. The previous display area opens. The shortcut menu of the display area opens. The table below shows the operation of the shortcut menu: Key Function The menu is closed. The display area opens. Touching the menu command WinCC Basic V13.0 System Manual, 02/2014 Input of the number of the menu command The menu command is executed. 4175 Visualize processes 10.11 Operating in Runtime Shortcut menus of the simple recipe view A shortcut menu can be called for each view area by pressing the button or the key. The shortcut menu lists the commands that are available in the active view area. A number is assigned to each command. You execute the command by entering its number. You can also use the system keys to execute certain commands. The scope depends on the HMI device. Recipe list No. Menu command 0 New Keys Function + A new recipe data record is created for the selected recipe. If a start value is configured, it is displayed in the input field. 1 Displaying infotext Displays the infotext configured for the simple recipe view. 2 Open The record list of the selected recipe opens. Data record list Menu command Keys New Function + 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. 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. Displaying infotext Displays the infotext configured for the simple recipe view. Element list Menu command 4176 Keys Function Save The selected record is renamed. 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. Displaying infotext Displays the infotext configured for the simple recipe view. Rename Renames the selected data record. A dialog box opens where you can enter the name. Previous The data record list opens. WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.11 Operating in Runtime Mouse control or touchscreen control of the simple recipe view 1. Select the desired recipe from the recipe view. 2. Click on the button. The shortcut menu is opened. 3. Select the desired menu command. The menu command is executed. 4. Alternatively, open the desired recipe in the recipe view. The data record list is displayed. 5. Open the desired data record. You could also use the and select a menu command. The menu command is executed. button to open the shortcut menu Using the keyboard with the simple recipe view 1. Press the key as many times as required to select the simple recipe view. 2. Select the desired recipe with the cursor keys. 3. Press the key. The shortcut menu is opened. 4. Press the cursor key as many times as required to select the menu command. 5. Confirm the menu command by pressing the key . 6. Alternatively, press the number of the desired menu command. The menu command is executed. Creating a recipe data record Introduction Create a new recipe data record in the recipe list or in the record list. Then enter the values for the new record in the element list and save the record. Requirement A screen with a simple recipe view is displayed. Procedure Proceed as follows to create a recipe data record: 1. If the recipe list contains several recipes: Select the recipe for which you want to create a new recipe data record. 2. Open the recipe list menu. WinCC Basic V13.0 System Manual, 02/2014 4177 Visualize processes 10.11 Operating in Runtime 3. Select the "0 new" menu command. Creates a new record. The element list of the new record opens. 4. Enter values for the data record elements. The tags of the record can be assigned default values depending on the configuration. 5. Open the menu of the element list and select the "0 Save" menu command. 6. Enter a name for the new record. 7. Confirm your entries. An existing data record is overwritten if you assign its number to a new data record. Result The new recipe data record is saved to the selected recipe. Editing a recipe data record Introduction Edit the values of the recipe data records and save them to a recipe view. Synchronization with the PLC To display the current recipe values from the PLC in the simple recipe view, you first have to read the actual values in the element list from the PLC using menu command "2 From PLC". Values changed in the recipe view are only activated after you transferred the modified data record to the PLC by means of menu command "1 To PLC". Requirement A screen with a recipe view is displayed. Procedure Proceed as follows to copy a recipe data record: 1. If the recipe list contains several recipes: Select the recipe which contains the relevant recipe data record. 2. Open the data record list. 3. Select the recipe data record you want to edit. 4. Open the element list. 5. Edit the element values as required. 6. Save your changes using menu command "0 Save". 4178 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.11 Operating in Runtime Result The edited recipe data record is saved to the selected recipe. Deleting a recipe data record Introduction You can delete all the data records which are not required. Requirement A screen with a simple recipe view is displayed. Procedure for touch operation Proceed as follows to delete a new recipe data record: 1. If the recipe list contains several recipes: Select the recipe which contains the relevant recipe data record. 2. Open the data record list. 3. Select the data record you want to delete. 4. Open the menu. 5. Select the menu command "1 Delete". Procedure for key operation Proceed as follows to delete a new recipe data record: 1. If the recipe list contains several recipes: Select the recipe which contains the relevant recipe data record. 2. Open the data record list. 3. Select the data record you want to delete. 4. Press INS DEL . Result The data record is deleted. Reading a recipe data record from the PLC Introduction The values of recipe elements are exchanged with the PLC via tags. WinCC Basic V13.0 System Manual, 02/2014 4179 Visualize processes 10.11 Operating in Runtime You can edit values which were saved to the recipes in the HMI device directly at plant level within the active project; this may be the case if a valve in the plant opens more than is indicated in the recipe. The values of the tags on the HMI device possibly no longer match the values in the PLC. Read the values from the PLC and output these to the recipe view to synchronize the recipe values. Requirement A screen with a simple recipe view is displayed. Procedure To transfer a recipe data record to the PLC, proceed as follows: 1. If the recipe list contains several recipes: Select the recipe which contains the relevant recipe data record. 2. Select the element list of the recipe data record to which you want to apply the values from the PLC. 3. Open the menu. 4. Select menu command "2 From PLC". The values are read from the PLC. 5. Save the displayed values to the HMI device using menu command "0 Save". Result The values were read from the PLC, are visible on the HMI device and were saved to the selected recipe data record. Note Basic Panels With Basic Panels, the "From PLC" menu command can also be configured for the data record list: In this case, you can also select the "From PLC" menu command in the data record list. Transferring a recipe data record to the PLC Introduction You must transfer the values to the PLC to activate a changed recipe data record for the process. The values displayed in the recipe view are transferred to the PLC. 4180 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.12 Performance features Requirement A screen with a simple recipe view is displayed. Procedure To transfer a recipe data record to the PLC, proceed as follows: 1. If the recipe list contains several recipes: Select the recipe which contains the relevant recipe data record. 2. Select the element list of the recipe data record whose values you want to transfer to the PLC. 3. Open the menu. 4. Select menu command "1 To PLC". Result The values of the recipe data record were transferred to the PLC and are active in the process. Note Basic Panels With Basic Panels, the "To PLC" menu command can also be configured for the data record list: In this case, you can also select the "To PLC" menu command in the data record list. 10.12 Performance features 10.12.1 Engineering system Engineering system The following tables help you assess whether your project still meets the performance specifications of the engineering system. In addition to the specified limits, allowances must also be made for restrictions imposed by main memory resources. WinCC uses up to 2 GB of RAM, depending on the operating system. It is nonetheless useful to install more than 2 GB of main memory on the PC if running many applications with high memory requirements in parallel. WinCC Basic V13.0 System Manual, 02/2014 4181 Visualize processes 10.12 Performance features Project system limits Different system limits apply for the engineering system, depending on whether a 32-bit or 64bit operating system is used. 32-bit operating system 64-bit operating system Number of HMI devices in the project 20 40 Number of HMI tags 1) 80,000 260,000 8,000 20,000 Number of logging tags Number of blocks (faceplates, user data types) 10,000 20,000 Number of screens 3,000 6,000 Number of screen objects per screen 3,200 3,200 Number of screen objects 320,000 640,000 Number of alarms 2) 3) 20,000 60,000 300,000 600,000 10,000 20,000 Number of entries per text list 3,000 3,000 Number of languages 32 32 20 20 300,000 800,000 Number of texts 3) 3) Number of text lists and graphic lists Number of global libraries 3) 3) Number of objects in the project library 1) 2) 3) 3) Including logging tags. With an average of 3 texts and a dynamic parameter Including the objects configured in the "Program PLC" area WinCC system limits for an HMI device 32-bit operating system 64-bit operating system Number of HMI tags 1) 80,000 260,000 Number of logging tags 8,000 20,000 Number of logs 500 1,000 Number of screens 1000 2,000 Number of screen objects per screen 3,200 3,200 Number of screen objects 320,000 640,000 Number of function lists 30,000 60,000 Number of animations and local scripts 50,000 100,000 Number of user-defined functions 1,000 2,000 Number of tasks 500 1,000 Number of alarms 2) 20,000 60,000 Number of recipes 1,000 2,000 Number of recipe elements 10,000 20,000 Number of texts 300,000 600,000 4182 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.12 Performance features 32-bit operating system 64-bit operating system Number of text lists and graphic lists 1,000 2,000 Number of entries per text list 5,000 10,000 Number of users 200 200 Number of reports 300 600 1) 2) Including logging tags. With an average of 3 texts and a dynamic parameter System limits during migration You can migrate projects which are beyond the specified system limits in one or more areas. An alarm will be output if migration creates a project whose limits are beyond the specified system limits. You must then adapt the project after migration to within the specified system limits to ensure safe operation in WinCC. 10.12.2 Basic Panel Basic Panel The following table helps you assess whether your project meets the performance features of the HMI device. The specified maximum values are not additive. It cannot be guaranteed that configurations running on the devices at the full system limits will be functional. In addition to the specified limits, allowances must be made for restrictions imposed by configuration memory resources. Tags KP300 Basic KP400 Basic KTP400 Basic KTP600 Basic KTP1000 Basic TP1500 Basic Number of tags in the project 250 500 250 (mono) 500 (color) 500 500 500 Number of PowerTags -- -- -- -- -- -- Number of elements per array 100 100 100 100 100 100 Number of local tags -- -- -- -- -- -- Number of structures -- -- -- -- -- -- Number of structure elements -- -- -- -- -- -- WinCC Basic V13.0 System Manual, 02/2014 4183 Visualize processes 10.12 Performance features Alarms KP300 Basic KP400 Basic KTP400 Basic KTP600 Basic KTP1000 Basic TP1500 Basic Number of alarm classes 32 32 32 32 32 32 Number of discrete alarms 200 200 200 200 200 200 Number of analog alarms 15 15 15 15 15 15 Length of an alarm in characters 80 80 80 80 80 80 Number of process values per alarm 8 8 8 8 8 8 Size of the alarm buffer 256 256 256 256 256 256 Number of queued alarm events 64 64 64 64 64 64 KP300 Basic KP400 Basic KTP400 Basic KTP600 Basic KTP1000 Basic TP1500 Basic 50 50 50 50 50 50 Number of fields per screen 30 30 30 30 30 30 Number of tags per screen 30 30 30 30 30 30 5 5 5 5 5 5 100 100 100 100 100 100 Screens Number of screens Number of complex objects per screen Number of array elements per screen 1) 2) 1) 2) Complex objects include: Bars, sliders, symbol library, clock, and all objects from the Controls area. Array elements contained in recipes are included in the count. Recipes KP300 Basic KP400 Basic KTP400 Basic KTP600 Basic KTP1000 Basic TP1500 Basic 5 5 5 5 5 5 20 20 20 20 20 20 User data length in bytes per data record -- -- -- -- -- -- Number of data records per recipe 20 20 20 20 20 20 Reserved memory for data records in the internal Flash 40 KB 40 KB 40 KB 40 KB 40 KB 40 KB Number of recipes Number of elements per recipe 1) 4184 1) If arrays are used, each array element counts as one recipe element WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.12 Performance features Logs KP300 Basic KP400 Basic KTP400 Basic KTP600 Basic KTP1000 Basic TP1500 Basic Number of logs -- -- -- -- -- -- Number of entries per log (including all log segments) 1) -- -- -- -- -- -- Number of log segments -- -- -- -- -- -- Cyclic trigger for tag logging -- -- -- -- -- -- Number of tags that can be logged per log -- -- -- -- -- -- 1) The number of entries for the "segmented circular log" logging method is the total number for all sequential logs. The product of the number of sequential logs and the number of data records per sequential log may not exceed the system limit Trends KP300 Basic KP400 Basic KTP400 Basic KTP600 Basic KTP1000 Basic TP1500 Basic 25 25 25 25 25 25 KP300 Basic KP400 Basic KTP400 Basic KTP600 Basic KTP1000 Basic TP1500 Basic Number of graphics lists 100 100 100 100 100 100 Number of text lists 150 150 150 150 150 150 Number of trends Text lists and graphics lists Number of entries per text or graphics list 30 30 30 30 30 30 Number of graphic objects 500 500 500 500 500 500 Number of text elements 500 500 500 500 500 500 KP300 Basic KP400 Basic KTP400 Basic KTP600 Basic KTP1000 Basic TP1500 Basic -- -- -- -- -- -- Scripts Number of scripts WinCC Basic V13.0 System Manual, 02/2014 4185 Visualize processes 10.12 Performance features Communication KP300 Basic KP400 Basic KTP400 Basic KTP600 Basic KTP1000 Basic TP1500 Basic 4 4 4 4 4 4 Number of connections based on "SIMATIC -HMI HTTP" -- -- -- -- -- KP300 Basic KP400 Basic KTP400 Basic KTP600 Basic KTP1000 Basic TP1500 Basic 500 500 500 500 500 500 KP300 Basic KP400 Basic KTP400 Basic KTP600 Basic KTP1000 Basic TP1500 Basic 5 5 5 5 5 5 KP300 Basic KP400 Basic KTP400 Basic KTP600 Basic KTP1000 Basic TP1500 Basic -- -- -- -- -- -- Number of connections Help system Number of characters in a help text Languages Number of runtime languages Scheduler Time-triggered tasks 1) 1) Event-triggered tasks are not relevant for the system limits User administration KP300 Basic KP400 Basic KTP400 Basic KTP600 Basic KTP1000 Basic TP1500 Basic Number of user groups 50 50 50 50 50 50 Number of authorizations 32 32 32 32 32 32 Number of users 50 50 50 50 50 50 4186 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.12 Performance features Project Size of the project file "*.srt" KP300 Basic KP400 Basic KTP400 Basic KTP600 Basic KTP1000 Basic TP1500 Basic 1024 KB 1024 KB 1024 KB 1024 KB 1024 KB 1024 KB See also S7-1200 manual (http://support.automation.siemens.com/WW/view/en/36932465/0/en) 10.12.3 Basic Panel 2nd Generation Basic Panel 2nd Generation The following table helps you assess whether your project meets the performance features of the HMI device. The specified maximum values are not additive. It cannot be guaranteed that configurations running on the devices at the full system limits will be functional. In addition to the specified limits, allowances must be made for restrictions imposed by configuration memory resources. Tags KTP400 Basic KTP700 Basic KTP900 Basic KTP1200 Basic Number of tags in the project 800 800 800 800 Number of PowerTags -- -- -- -- Number of elements per array 100 100 100 100 Number of local tags -- -- -- -- Number of structures -- -- -- -- Number of structure elements -- -- -- -- KTP400 Basic KTP700 Basic KTP900 Basic KTP1200 Basic Number of alarm classes 32 32 32 32 Number of discrete alarms 1000 1000 100 100 Number of analog alarms 25 25 25 25 Length of an alarm in characters 80 80 80 80 Number of process values per alarm 8 8 8 8 Alarms WinCC Basic V13.0 System Manual, 02/2014 4187 Visualize processes 10.12 Performance features KTP400 Basic KTP700 Basic KTP900 Basic KTP1200 Basic Size of the alarm buffer 256 256 256 256 Number of queued alarm events 64 64 64 64 KTP400 Basic KTP700 Basic KTP900 Basic KTP1200 Basic Number of screens 250 250 250 250 Number of fields per screen 100 100 100 100 Number of tags per screen 100 100 100 100 Number of complex objects per screen 1) 150 150 150 150 Number of recipe displays per screen 10 10 10 10 Number of trend displays per screen 8 8 8 8 Number of alarm displays per screen 20 20 20 20 Number of user displays per screen 1 1 1 1 Number of system diagnostic displays per screen 150 150 150 150 Number of array elements per screen 100 100 100 100 Screens 1) 2) 2) Complex objects include: Bars, sliders, symbol library, clock, and all objects from the Controls area. Array elements contained in recipes are included in the count. Recipes KTP400 Basic KTP700 Basic KTP900 Basic KTP1200 Basic Number of recipes 50 50 50 50 Number of elements per recipe1) 100 100 100 100 User data length in KB per data record 32 32 32 32 Number of data records per recipe 100 100 100 100 256 KB 256 KB 256 KB Reserved memory for data records in the internal Flash 256 KB 1) If arrays are used, each array element counts as one recipe element Logs KTP400 Basic KTP700 Basic KTP900 Basic KTP1200 Basic Number of logs 2 2 2 2 Number of entries per log (including all log segments) 10 10 10 10 Number of log segments 10000 10000 10000 10000 1) 4188 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.12 Performance features KTP400 Basic KTP700 Basic KTP900 Basic KTP1200 Basic Cyclic trigger for tag logging 400 400 400 400 Number of tags that can be logged per log 1s 1s 1s 1s 1) The number of entries for the "segmented circular log" logging method is the total number for all sequential logs. The product of the number of sequential logs and the number of data records per sequential log may not exceed the system limit Trends KTP400 Basic KTP700 Basic KTP900 Basic KTP1200 Basic 25 25 25 25 KTP400 Basic KTP700 Basic KTP900 Basic KTP1200 Basic Number of graphics lists 100 100 100 100 Number of text lists 300 300 300 300 Number of entries per text or graphics list 100 100 100 100 Number of graphic objects 1000 1000 1000 1000 Number of text elements 2500 2500 2500 2500 KTP400 Basic KTP700 Basic KTP900 Basic KTP1200 Basic -- -- -- -- Number of trends Text lists and graphics lists Scripts Number of scripts Communication KTP400 Basic KTP700 Basic KTP900 Basic KTP1200 Basic Number of connections 4 4 4 4 Number of connections based on "SIMATIC HMI HTTP" -- -- -- -- KTP400 Basic KTP700 Basic KTP900 Basic KTP1200 Basic 500 500 500 500 Help system Number of characters in a help text WinCC Basic V13.0 System Manual, 02/2014 4189 Visualize processes 10.12 Performance features Languages Number of runtime languages KTP400 Basic KTP700 Basic KTP900 Basic KTP1200 Basic 10 10 10 10 KTP400 Basic KTP700 Basic KTP900 Basic KTP1200 Basic -- -- -- -- Scheduler Time-triggered tasks 1) 1) Event-triggered tasks are not relevant for the system limits User administration KTP400 Basic KTP700 Basic KTP900 Basic KTP1200 Basic Number of user groups 50 50 50 50 Number of authorizations 32 32 32 32 Number of users 50 50 50 50 KTP400 Basic KTP700 Basic KTP900 Basic KTP1200 Basic 10 MB 10 MB 10 MB 10 MB Project Size of the project file "*.srt" 10.12.4 General technical data 10.12.4.1 Permitted characters Introduction The following table shows the restrictions that must be observed when allocating names and passwords. 4190 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.12 Performance features Permitted characters Names / passwords Restriction Names of objects Do not use the special characters ? " / \ * < > % Names and passwords in user view Do not use the special characters ? " / \ & $ % Names of alarm logs In the storage location file - RDB, file - CSV (ASCII) and file -TXT (Unicode) do not use the characters \ / * ? : " < > | For the storage location database, use only the characters a-z A-Z 0-9 _ @ # $ The characters _ @ # $ may not be used as the first character of a name Name of HMI tags HMI tag names may not start with the @ character Names of screens Do not use the special characters ? " / \ * < > Names of AuditTrails Do not use any special characters Names of connections Do not use spaces or special characters Name of VB functions Do not use spaces, special characters or VB keywords Name of Windows user groups and Windows users when using SIMATIC Logon Do not use the special characters / \ 10.12.4.2 Recommended printers Recommended printers The current list of printers recommended for use with the HMI devices is available on the Internet at: Link to the current printer list (http://support.automation.siemens.com/WW/llisapi.dll? aktprim=0&lang=en&referer=%2fWW %2f&func=cslib.csinfo&siteid=csius&caller=view&extranet=standard&viewreg=WW&nodeid0 =10805558&objaction=csopen) Note All HMI devices except for a PC and Panel PC support only one printer at their USB port, even if several ports are available. See also Printer list (http://support.automation.siemens.com/WW/llisapi.dll? aktprim=0&lang=en&referer=%2fWW %2f&func=cslib.csinfo&siteid=csius&caller=view&extranet=standard&viewreg=WW&nodeid0 =10805558&objaction=csopen) WinCC Basic V13.0 System Manual, 02/2014 4191 Visualize processes 10.12 Performance features 10.12.4.3 Memory requirements of recipes for Basic Panels Introduction The following calculation of memory requirements of recipes is valid for Basic Panels, OP 77A, and TP 177A devices. Restrictions The HMI device provides 39 KB of memory space for recipes. This memory space may not be exceeded. The total memory space for recipes is calculated as follows: Total of all recipes + recipe with highest memory requirement. Each recipe may not exceed a maximum memory space of 19 KB. Calculation of memory requirements The memory space requirement of each recipe (in KB) is calculated based on the three addends D1 + D2 + D3. Valid is:: D1 = number of data records x M Rule for M (size of a data record): M = 1 x number of elements of a byte + 2 x number of elements of 2 bytes + 4 x number of elements of 4 bytes + 8 x number of elements of 8 bytes + K Rule for K (size of the string elements): K = number of string elements x (string length + 1) x 2 D2 - data record size D2 = 4 + number of languages x 8 + number of languages x (4 + 4 x number of data records + (length of the data record name + 1) x 2 x number of data records) + 8 + 8 x number of data records Or rewritten: D2 = 12 + 8 x number of data records + number of languages x (12 + number of data records x (4 + (length of the data record name +1) x 2)) D3 - shared memory D3 = 14 + number of elements Note Arrays and single elements can be calculated as described above. 4192 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.13 Migrating to WinCC in the TIA Portal 10.13 Migrating to WinCC in the TIA Portal 10.13.1 Overview of migration to WinCC V12 Overview of the section "Migration to WinCC in the TIA Portal" SIMATIC WinCC offers a number of functional changes in the TIA Portal. Some functions differ from the functions that you know from familiar environments such as WinCC V7 or WinCC flexible. This document provides an overview of the special functions and procedures in SIMATIC WinCC in the TIA Portal. These functions and procedures are fundamentally different from the WinCC V7 and WinCC flexible version, or have a different name. 10.13.2 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: WinCC Basic V13.0 System Manual, 02/2014 4193 Visualize processes 10.13 Migrating to WinCC in the TIA Portal 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 with WinCC in the TIA Portal? In WinCC, 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. 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. 4194 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.13 Migrating to WinCC in the TIA Portal 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 (Page 3988) 10.13.3 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 with WinCC in the TIA Portal? In WinCC, you also configure "Templates" and a "Global screen" along with the "Screens". WinCC Basic V13.0 System Manual, 02/2014 4195 Visualize processes 10.13 Migrating to WinCC in the TIA Portal 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. You can also configure a "System Diagnostics Window" in the global screen of Comfort Panels. Excluding the controls, the screens are displayed in runtime in the following order: 4196 WinCC Basic V13.0 System Manual, 02/2014 Visualize processes 10.13 Migrating to WinCC in the TIA Portal 7HPSODWH 6FUHHQ 0RQLWRU *OREDOVFUHHQ 6\VWHP /D\HU /D\HU For more detailed information, see: Screen basics (Page 3183) WinCC Basic V13.0 System Manual, 02/2014 4197 11 Using technology functions 11.1 PID control 11.1.1 Principles for control 11.1.1.1 Controlled system and actuators Controlled system Room temperature control by means of a heating system is a simple example of a controlled system. A sensor measures the room temperature and transfers the value to a controller. The controller compares the current room temperature with a setpoint and calculates an output value (manipulated variable) for heating control. 6HWSRLQW &RQWUROOHU 2XWSXWYDOXH $FWXDWRU +HDWLQJ 3URFHVVYDOXH 6HQVRU 7HPSHUDWXUH A properly set PID controller reaches this setpoint as quickly as possible and then holds it a constant value. After a change in the output value, the process value often changes only with a time delay. The controller has to compensate for this response. Actuators The actuator is an element of the controlled system and is influenced by the controller. Its function modifies mass and energy flows. The table below provides an overview of actuator applications. Application Actuator Liquid and gaseous mass flow Valve, shutter, gate valve Solid mass flow, e.g., bulk material Articulated baffle, conveyor, vibrator channel Flow of electrical power Switching contact, contactor, relay, thyristor Variable resistor, variable transformer, transistor WinCC Basic V13.0 System Manual, 02/2014 4199 Using technology functions 11.1 PID control Actuators are distinguished as follows: Proportional actuators with constant actuating signal These elements set degrees of opening, angular positions or positions in proportion to the output value. The output value has an analog effect on the process within the control range. Actuators in this group include spring-loaded pneumatic drives, as well as motorized drives with position feedback for which a position control system is formed. An continuous controller, such as PID_Compact, generates the output value. Proportional actuators with pulse-width modulated signal These actuators are used to generate the output of pulses with a length proportional to the output value within the sampling time intervals. The actuator - e.g. a heating resistor or cooling apparatus - is switched on in isochronous mode for durations that differ depending on the output value. The actuating signal can assume unipolar "On" or "Off" states, or represent bipolar states such as "open/close", "forward/backward", "accelerate/brake". The output value is generated by a two-step controller such as PID_Compact with pulsewidth modulation. Actuators with integral action and three-step actuating signal Actuators are frequently operated by motors with an on period that is proportional to the actuator travel of the choke element. This includes elements such as valves, shutters, and gate valves. In spite of their different design, all of these actuators follow the effect of an integral action at the input of the controlled system. A step controller, such as PID_3Step. generates the output value. 11.1.1.2 Controlled systems The properties of a controlled system can hardly be influenced as these are determined by the technical requirements of the process and machinery. Acceptable control results can only be achieved by selecting a suitable controller type for the specific controlled system and adapting the controller to the time response of the controlled system. Therefore, it is is indispensable for the configuration of the proportional, integral and derivative actions of the controller to have precise knowledge of the type and parameters of the controlled system. Controlled system types Controlled systems are classified based on their time response to step changes of the output value. We distinguish between the following controlled systems: Self-regulating controlled systems - Proportional-action controlled systems - PT1 controlled systems - PT2 controlled systems Non-self-regulating controlled systems Controlled systems with and without dead time 4200 WinCC Basic V13.0 System Manual, 02/2014 Using technology functions 11.1 PID control Self-regulating controlled systems Proportional-action controlled systems In proportional-action controlled systems, the process value follows the output value almost immediately. The ratio between the process value and output value is defined by the proportional Gain of the controlled system. Examples: Gate valve in a piping system Voltage dividers Step-down function in hydraulic systems PT1 controlled systems In a PT1 controlled system, the process value initially changes in proportion to the change of the output value. The rate of change of the process value is reduced as a function of the time until the end value is reached, i.e., it is delayed. Examples: Spring damping system Charge of RC elements Water container that is heated with steam. The time constants are often identical for heating and cooling processes, or for charging and discharge characteristics. With different time constants, controlling is clearly more complex. PT2 controlled systems In a PT2 controlled system, the process value does not immediately follow a step change of the output value, i.e., it increases in proportion to the positive rate of rise and then approaches the setpoint at a decreasing rate of rise. The controlled system shows a proportional response characteristic with second order delay element. Examples: Pressure control Flow rate control Temperature control Non-self-regulating controlled systems Non-self-regulating controlled systems have an integral response. The process value approaches an infinite maximum value. Example: Liquid flow into a container Controlled systems with dead time A dead time always represents the runtime or transport time that has to expire before a change to the system input can be measured at the system output. WinCC Basic V13.0 System Manual, 02/2014 4201 Using technology functions 11.1 PID control In controlled systems with dead time, the process value change is delayed by the amount of the dead time. Example: Conveyor 11.1.1.3 Characteristic values of the control section Determining the time response from the step response Time response of the controlled system can be determined based on the time characteristic of process value x following a step change of output value y. Most controlled systems are selfregulating controlled systems. \ W [ 7J ;PD[ [ W 7X W The time response can be determined by approximation using the variables Delay time Tu, Recovery time Tg and Maximum value Xmax. The variables are determined by applying tangents 4202 WinCC Basic V13.0 System Manual, 02/2014 Using technology functions 11.1 PID control to the maximum value and the inflection point of the step response. In many situations, it is not possible to record the response characteristic up to the maximum value because the process value cannot exceed specific values. In this case, the rate of rise vmax is used to identify the controlled system (vmax = x/t). The controllability of the controlled system can be estimated based on the ratio Tu/Tg, or Tu x vmax/Xmax . Rule: Process type Tu / Tg Suitability of the controlled system for controlling I < 0,1 can be controlled well II 0.1 to 0.3 can still be controlled III > 0,3 difficult to control Influence of the dead time on the controllability of a controlled system A controlled system with dead time and recovery reacts as follows to a jump of the output value. \ W [ 7J W 7X 7W 7D Tt Dead time Tu Delay time Tg Recovery time y Output value x Process value The controllability of a self-regulating controlled system with dead time is determined by the ratio of Tt to Tg. Tt must be small compared to Tg. Rule: Tt/Tg 1 WinCC Basic V13.0 System Manual, 02/2014 4203 Using technology functions 11.1 PID control Response rate of controlled systems Controlled systems can be judged on the basis of the following values: Tu < 0.5 min, Tg < 5 min = fast controlled system Tu > 0.5 min, Tg > 5 min = slow controlled system Parameters of certain controlled systems Physical quantity Temperature Controlled system Small electrically heated furnace Large electrically heated annealing furnace Large gas-heated annealing furnace Distillation tower Autoclaves (2.5 m3) High-pressure autoclaves Rate of rise vmax 0.5 to 1 min 5 to 15 min Up to 60 K/min. 1 to 5 min 10 to 20 min Up to 20 K/min. 0.2 to 5 min 3 to 60 min 1 to 30 K/min 1 to 7 min 40 to 60 min 0.1 to 0.5 C/s 0.5 to 0.7 min 10 to 20 min Not specified 12 to 15 min 200 to 300 min Not specified 1 to 4 min 2C/s 0.5 to 3 min 3 to 30 min 5 to 20 K/min 1 to 6 min 5 to 60 min 0.5 to 4 min 3 to 40 min 1 to 5 min 10 to 60 min 1 C/min 0 to 5 s 0.2 to 10 s Not relevant Pipeline with liquid None None Gas pipeline None 0.1 s Not relevant Injection molding machines Extruders Packaging machines Room heating Pressure Recovery time Tg 30 s to 2.5 min Steam superheater Flow rate Delay time Tu Pipeline with gas Drum boiler with gas or oil firing Drum boiler with impact grinding mills 2 to 35 K/min None 150 s Not relevant 1 to 2 min 2 to 5 min Not relevant 0.6 to 1 min Not specified 0.1 to 0.3 cm/s Vessel level Drum boiler Speed Small electric drive None 0.2 to 10 s Not relevant Large electric drive None 5 to 40 s Not relevant Steam turbine None Not specified 50 min-1 Small generators None 1 to 5 s Not relevant Large generators None 5 to 10 s Not relevant Voltage 11.1.1.4 Pulse controller Two-step controllers without feedback Two-step controllers have the state "ON" and "OFF" as the switching function. This corresponds to 100% or 0% output. This behavior generates a sustained oscillation of process value x around setpoint w. The amplitude and duration of the oscillation increase in proportion to the ratio between the delay time Tu and recovery time Tg of the controlled system. These controllers are used mainly 4204 WinCC Basic V13.0 System Manual, 02/2014 Using technology functions 11.1 PID control for simple temperature control systems (such as electrically directly heated furnaces) or as limit-value signaling units. The following diagram shows the characteristic of a two-step controller \ <K Z OFF Yh Control range w Setpoint [ ON The following diagram shows the control function of a two-step controller WinCC Basic V13.0 System Manual, 02/2014 4205 Using technology functions 11.1 PID control [ 7J Z ; 6G 7X W \ W Response characteristic with two-step controller Tu Delay time Tg Recovery time XSd Switching difference Response characteristic without controller Two-step controllers with feedback The behavior of two-step controllers in the case of controlled systems with larger delay times, such as furnaces where the functional space is separated from the heating, can be improved by the use of electronic feedback. The feedback is used to increase the switching frequency of the controller, which reduces the amplitude of the process value. In addition, the control-action results can be improved substantially in dynamic operation. The limit for the switching frequency is set by the output level. It should not exceed 1 to 5 switches per minute at mechanical actuators, such as relays and contactors. In the case of voltage and current outputs with downstream thyristor or Triac controllers high switching frequencies can be selected that exceed the limit frequency of the controlled system by far. 4206 WinCC Basic V13.0 System Manual, 02/2014 Using technology functions 11.1 PID control Since the switching pulses can no longer be determined at the output of the controlled system, results comparable with those of continuous controllers are obtained. The output value is generated by pulse-width modulation of the output value of a continuous controller. Two-step controllers with feedback are used for temperature control in furnaces, at processing machines in the plastics, textile, paper, rubber and foodstuff industries as well as for heating and cooling devices. Three-step controllers Three-step controllers are used for heating / cooling. These controllers have two switching points as their output. The control-action results are optimized through electronic feedback structures. Fields of applications for such controllers are heating, low-temperature, climatic chambers and tool heating units for plastic-processing machines. The following diagram shows the characteristic of a three-step controller \ \ \ \ \ Z [ [ 6K y Output value, e.g. y11 = 100% heating y12 = 0% heating y21 = 0% cooling y22 = 100% cooling x Physical quantity of the process value, e.g., temperature in C w Setpoint xSh Distance between Switching Point 1 and Switching Point 2 WinCC Basic V13.0 System Manual, 02/2014 4207 Using technology functions 11.1 PID control 11.1.1.5 Response to setpoint changes and disturbances Response to setpoint changes The process value should follow a setpoint change as quickly as possible. The response to setpoint changes is improved by minimizing fluctuation of the process value and the time required to reach the new setpoint. [ Z W x Process value w Setpoint Response to disturbances The setpoint is influenced by disturbance variables. The controller has to eliminate the resulting control deviations in the shortest time possible. The response to disturbances is improved by minimizing fluctuation of the process value and the time required to reach the new setpoint. [ Z W x Process value w Setpoint 4208 Influencing a disturbance variable WinCC Basic V13.0 System Manual, 02/2014 Using technology functions 11.1 PID control Disturbance variables are corrected by a controller with integral action. A persistent disturbance variable does not reduce control quality because the control deviation is relatively constant. Dynamic disturbance variables have a more significant impact on control quality because of control deviation fluctuation. The control deviation is eliminated again only by means of the slow acting integral action. A measurable disturbance variable can be included in the controlled system. This inclusion would significantly accelerated the response of the controller. 11.1.1.6 Control Response at Different Feedback Structures Control behavior of controllers A precise adaptation of the controller to the time response of the controlled system is decisive for the controller's precise settling to the setpoint and optimum response to disturbance variables. The feedback circuit can have a proportional action (P), proportional-derivative action (PD), proportional-integral action (PI), or proportional-integral-derivative action (PID). If step functions are to be triggered by control deviations, the step responses of the controllers differ depending on their type. WinCC Basic V13.0 System Manual, 02/2014 4209 Using technology functions 11.1 PID control Step response of a proportional action controller [ W \ W \ W Control deviation Output value of a continuous controller Output value of a pulse controller Equation for proportional action controller Output value and control deviation are directly proportional, meaning: Output value = proportional gain x control deviation y = GAIN x x 4210 WinCC Basic V13.0 System Manual, 02/2014 Using technology functions 11.1 PID control Step response of a PD-action controller [ W \ 70B/$* W \ W Output value of a continuous controller TM_LAG Delay of the Derivative action Control deviation Output value of a pulse controller Equation for PD-action controller The following applies for the step response of the PD-action controller in the time range: W 7' \ *$,1y;:y 70B/$* 70B/$* yH t = time interval since the step of the control deviation The derivative action generates a output value as a function of the rate of change of the process value. A derivative action by itself is not suitable for controlling because the output value only WinCC Basic V13.0 System Manual, 02/2014 4211 Using technology functions 11.1 PID control follows a step of the process value. As long as the process value remains constant, the output value will no longer change. The response to disturbances of the derivative action is improved in combination with a proportional action. Disturbances are not corrected completely. The good dynamic response is advantageous. A well attenuated, non-oscillating response is achieved during approach and setpoint change. A controller with derivative action is not appropriate if a controlled system has pulsing measured quantities, for example, in the case of pressure or flow control systems. 4212 WinCC Basic V13.0 System Manual, 02/2014 Using technology functions 11.1 PID control Step response of a PI-action controller [ W \ W \ W Control deviation Output value of a continuous controller Output value of a pulse controller An integral action in the controller adds the control deviation as a function of the time. This means that the controller corrects the system until the control deviation is eliminated. A sustained control deviation is generated at controllers with proportional action only. This effect can be eliminated by means of an integral action in the controller. In practical experience, a combination of the proportional, integral and derivative actions is ideal, depending on the requirements placed on the control response. The time response of the individual components can be described by the controller parameters proportional gain GAIN, integral action time TI (integral action), and derivative action time TD (derivative action). Equation for PI-action controller WinCC Basic V13.0 System Manual, 02/2014 4213 Using technology functions 11.1 PID control The following applies for the step response of the PI-action controller in the time range: \ *$,1y;:y 7,yW t = time interval since the step of the control deviation 4214 WinCC Basic V13.0 System Manual, 02/2014 Using technology functions 11.1 PID control Step response of a PID controller [ W \ 70B/$* W 7, \ W Control deviation Output value of a continuous controller Output value of a pulse controller TM_LAG Delay of the Derivative action Ti Integral action time Equation for PID controller The following applies for the step response of the PID controller in the time range: WinCC Basic V13.0 System Manual, 02/2014 4215 Using technology functions 11.1 PID control \ *$,1y;:y 7,yW 7' 70B/$* yH W 70B/$* t = time interval since the step of the control deviation Response of a controlled system with different controller structures Most of the controller systems occurring in process engineering can be controlled by means of a controller with PI-action response. In the case of slow controlled system with a large dead time, for example temperature control systems, the control result can be improved by means of a controller with PID action. [ Z W PID controller w Setpoint x Process value No controller PD-action controller Controllers with PI and PID action have the advantage that the process value does not have any deviation from the setpoint value after settling. The process value oscillates over the setpoint during approach. 4216 WinCC Basic V13.0 System Manual, 02/2014 Using technology functions 11.1 PID control 11.1.1.7 Selection of the controller structure for specified controlled systems Selection of the Suitable Controller Structures To achieve optimum control results, select a controller structure that is suitable for the controlled system and that you can adapt to the controlled system within specific limits. The table below provides an overview of suitable combinations of a controller structure and controlled system. Controlled system Controller structure P PD PI PID With dead time only Unsuitable Unsuitable Suitable Unsuitable PT1 with dead time Unsuitable Unsuitable Well suited Well suited PT2 with dead time Unsuitable Suited conditionally Well suited Well suited Higher order Unsuitable Unsuitable Suited conditionally Well suited Not self-regulating Well suited Well suited Well suited Well suited The table below provides an overview of suitable combinations of a controller structure and physical quantity. Physical quantity Controller structure P PD Sustained control deviation WinCC Basic V13.0 System Manual, 02/2014 PI PID No sustained control deviation Temperature For low Well suited performance requirements and proportional action controlled systems with Tu/ Tg < 0,1 The most suitable controller structures for high performance requirements (except for specially adapted special controllers) Pressure Suitable, if the delay time is inconsiderable Unsuitable The most suitable controller structures for high performance requirements (except for specially adapted special controllers) Flow rate Unsuitable, because required GAIN range is usually too large Unsuitable Suitable, but integral action controller alone often better Hardly required 4217 Using technology functions 11.1 PID control 11.1.1.8 PID parameter settings Rule of Thumb for the Parameter Setting Controller structure Setting P GAIN vmax x Tu [ C ] PI GAIN 1.2 x vmax x Tu [ C ] PD GAIN 0.83 x vmax x Tu [ C ] TD 0.25 x vmax x Tu [ min ] TM_LAG 0.5 x TD[ min ] PID GAIN 0.83 x vmax x Tu [ C ] TI 2 x Tu [ min ] TD 0.4 x Tu [ min ] TM_LAG 0.5 x TD[ min ] PD/PID GAIN 0.4 x vmax x Tu [ C ] TI 2 x Tu [ min ] TD 0.4 x Tu [ min ] TM_LAG 0.5 x TD[ min ] Instead of vmax = x / t , you can use Xmax / Tg. In the case of controllers with PID structure the setting of the integral action time and differentialaction time is usually coupled with each other. The ratio TI / TD lies between 4 and 5 and is optimal for most controlled systems. Non-observance of the differential-action time TD is uncritical at PD controllers. In the case of PI and PID controllers, control oscillations occur if the integral action time TI has been select by more than half too small. An integral action time that is too large slows down the settling times of disturbances. One cannot expect that the control loops operate "optimally" after the first parameter settings. Experience shows that adjusting is always necessary, when a system exists that is "difficult to control" with Tu / Tg > 0.3. 11.1.2 Configuring a software controller 11.1.2.1 Overview of software controller For the configuration of a software controller, you need an instruction with the control algorithm and a technology object. The technology object for a software controller corresponds with the instance DB of the instruction. The configuration of the controller is saved in the technology object. In contrast to the instance DBs of other instructions, technology objects are not stored for the program resources, but rather under CPU > Technology objects. 4218 WinCC Basic V13.0 System Manual, 02/2014 Using technology functions 11.1 PID control Technology objects and instructions CPU Library Instruction Technology object Description S7-1200 Compact PID PID_Compact V1.X PID_Compact V1.X Universal PID controller with integrated tuning S7-1200 PID_3Step V1.X PID_3Step V1.X PID controller with integrated tuning for valves S7-1500 PID_Compact V2.X Universal PID controller with integrated tuning S7-1200 V4.x PID_Compact V2.X S7-1500 PID_3Step V2.X PID_3Step V2.X PID controller with integrated tuning for valves S7-1200 V4.x S7-1500/300/4 00 PID basic functions CONT_C CONT_C Continuous controller S7-1500/300/4 00 CONT_S CONT_S Step controller for actuators with integrating behavior S7-1500/300/4 00 PULSEGEN - Pulse generator for actuators with proportional behavior S7-1500/300/4 00 TCONT_CP TCONT_CP Continuous temperature controller with pulse generator S7-1500/300/4 00 TCONT_S TCONT_S Temperature controller for actuators with integrating behavior TUN_EC TUN_EC Optimization of a continuous controller S7-300/400 PID Self Tuner S7-300/400 S7-300/400 S7-300/400 S7-300/400 S7-300/400 S7-300/400 S7-300/400 S7-300/400 TUN_ES TUN_ES Optimization of a step controller Standard PID Control (PID Professional optional package) PID_CP PID_CP Continuous controller with pulse generator PID_ES PID_ES Step controller for actuators with integrating behavior LP_SCHED - Distribute controller calls Modular PID Control (PID Professional optional package) A_DEAD_B - Filter interfering signal from control deviation CRP_IN - Scale analog input signal CRP_OUT - Scale analog output signal DEAD_T - Delay output of input signal S7-300/400 DEADBAND - Suppress small fluctuations to the process value S7-300/400 DIF - Differentiate input signals over time S7-300/400 ERR_MON S7-300/400 INTEG - Integrate input signals over time S7-300/400 LAG1ST - First-order delay element S7-300/400 LAG2ND - Second-order delay element S7-300/400 LIMALARM - Report limit values S7-300/400 LIMITER - Limiting the manipulated variable S7-300/400 LMNGEN_C - Determine manipulated variable for continuous controller S7-300/400 LMNGEN_S - Determine manipulated variable for step controller S7-300/400 NONLIN - Linearize encoder signal WinCC Basic V13.0 System Manual, 02/2014 Monitor control deviation 4219 Using technology functions 11.1 PID control CPU Instruction Technology object Description S7-300/400 NORM - Scale process value physically S7-300/400 OVERRIDE - Switch manipulated variable from 2 PID controllers to 1 actuator S7-300/400 PARA_CTL - Switch parameter sets S7-300/400 PID - PID algorithm S7-300/400 PUSLEGEN_M - Generate pulse for proportional actuators S7-300/400 RMP_SOAK - Specify setpoint according to ramp / soak S7-300/400 ROC_LIM - Limit rate of change S7-300/400 SCALE_M - Scale process value S7-300/400 SP_GEN - Specify setpoint manually S7-300/400 SPLT_RAN - Split manipulated variable range S7-300/400 SWITCH - Switch analog values S7-300/400 LP_SCHED_M - Distribute controller calls 11.1.2.2 Library Steps for the configuration of a software controller All SW-controllers are configured according to the same scheme: 11.1.2.3 Step Description 1 Add technology object (Page 4220) 2 Configure technology object (Page 4221) 3 Call instruction in the user program (Page 4222) 4 Download technology object to device (Page 4223) 5 Commission software controller (Page 4224) 6 Save optimized PID parameters in the project (Page 4225) 7 Comparing values (Page 4226) 8 Display instances of a technology object (Page 4245) Add technology objects Add technology object in the project navigator When a technology object is added, an instance DB is created for the instruction of this technology object. The configuration of the technology object is stored in this instance DB. Requirement A project with a CPU has been created. 4220 WinCC Basic V13.0 System Manual, 02/2014 Using technology functions 11.1 PID control Procedure To add a technology object, proceed as follows: 1. Open the CPU folder in the project tree. 2. Open the "Technology objects" folder. 3. Double-click "Add new object". The "Add new object" dialog box opens. 4. Click on the "PID" button. All available PID-controllers for this CPU are displayed. 5. Select the instruction for the technology object, for example, PID_Compact. 6. Enter an individual name for the technology object in the "Name" input field. 7. Select the "Manual" option if you want to change the suggested data block number of the instance DB. 8. Click "Further information" if you want to add own information to the technology object. 9. Confirm with "OK". Result The new technology object has been created and stored in the project tree in the "Technology objects" folder. The technology object is used if the instruction for this technology object is called in a cyclic interrupt OB. Note You can select the "Add new and open" check box at the bottom of the dialog box. This opens the configuration of the technology object after adding has been completed. 11.1.2.4 Configure technology objects The properties of a technology object on a S7-1200 CPU can be configured in two ways. In the Inspector window of the programming editor In the configuration editor The properties of a technology object on a S7-300/400 CPU can only be configured in the configuration editor. Inspector window of the programming editor In the Inspector window of the programming editor you can only configure the parameters required for operation. The offline values of the parameters are also shown in online mode. You can only change the online values in the commissioning window. To open the Inspector window of the technology object, follow these steps: WinCC Basic V13.0 System Manual, 02/2014 4221 Using technology functions 11.1 PID control 1. Open the "Program blocks" folder in the project tree. 2. Double click the block (cyclic interrupt OB) in which you open the instruction of the SWcontroller. The block is opened in the work area. 3. Click on the instruction of the SW-controller. 4. In the Inspector window, select the "Properties" and "Configuration" tabs consecutively. Configuration window For each technology object, there is a specific configuration window in which you can configure all properties. To open the configuration window of the technology object, follow these steps: 1. Open the "Technology objects" folder in the project tree. 2. Open the technology object in the project tree. 3. Double-click the "Configuration" object. Symbols Icons in the area navigation of the configuration and in the Inspector window show additional details about the completeness of the configuration: The configuration contains default values and is complete. The configuration exclusively contains default values. With these default values the use of the technology object is possible without further changes. The configuration contains values defined by the user and is complete All input fields of the configuration contain valid values and at least one default setting was changed. The configuration is incomplete or faulty At least one input field or a collapsible list contains no or one invalid value. The corresponding field or the drop-down list box has a red background. When clicked the roll-out error message indicates the cause of the error. The properties of a technology object are described in detail in the chapter for the technology object. 11.1.2.5 Call instruction in the user program The instruction of the software controller must be called in a cyclic interrupt OB. The sampling time of the software controller is determined by the interval between the calls in the cyclic interrupt OB. Requirement The cyclic interrupt OB is created and the cycle time of the cyclic interrupt OB is correctly configured. 4222 WinCC Basic V13.0 System Manual, 02/2014 Using technology functions 11.1 PID control Procedure Proceed as follows to call the instruction in the user program: 1. Open the CPU folder in the project tree. 2. Open the "Program blocks" folder. 3. Double-click the cyclic interrupt OB. The block is opened in the work area. 4. Open the "Technology" group in the "Instructions" window and the "PID Control" folder. The folder contains all instructions for software controllers that can be configured on the CPU. 5. Select the instruction and drag it to your cyclic interrupt OB. The "Call options" dialog box opens. 6. Select a technology object or type the name for a new technology object from the "Name" list. Result If the technology object does not exist yet, it is added. The instruction is added in the cyclic interrupt OB. The technology object is assigned to this call of the instruction. 11.1.2.6 Downloading technology objects to device A new or modified configuration of the technology object must be downloaded to the CPU for the online mode. The following characteristics apply when downloading retentive data: Software (changes only) - S7-1200, S7-1500: Retentive data is retained. - S7-300/400: Retentive data is updated immediately. CPU does not change to Stop. Download PLC program to device and reset - S7-1200, S7-1500: Retentive data is updated at the next change from Stop to RUN. The PLC program can only be downloaded completely. - S7-300/400: Retentive data is updated at the next change from Stop to RUN. WinCC Basic V13.0 System Manual, 02/2014 4223 Using technology functions 11.1 PID control Downloading retentive data to an S7-1200 or S7-1500 CPU Note The download and reset of the PLC program during ongoing system operation can result in serious damages or injuries in the case of malfunctions or program errors. Make sure that dangerous states cannot occur before you download and reset the PLC program. Proceed as follows to download the retentive data: 1. Select the entry of the CPU in the project tree. 2. Select the command "Download and reset PLC program" from the "Online" menu. - If you have not established an online connection yet, the "Extended download" dialog opens. In this case, set all required parameters for the connection and click "Download". - If the online connection has been defined, the project data is compiled, if necessary, and the dialog "Load preview" opens. This dialog displays messages and recommends actions necessary for download. 3. Check the messages. As soon as download is possible, the "Download" button becomes active. 4. Click on "Download". The complete PLC program is downloaded and the "Load results" dialog opens. This dialog displays the status and the actions after the download. 5. If the modules are to restart immediately after the download, select the check box "Start all". 6. Close the dialog "Download results" with "Finish". Result The complete PLC program is downloaded to the device. Blocks that only exist online in the device are deleted. By downloading all affected blocks and by deleting any blocks in the device that are not required, you avoid inconsistencies between the blocks in the user program. The messages under "Info > General" in the Inspector window indicate whether the download was successful. 11.1.2.7 Commissioning software controller Procedure To open the "Commissioning" work area of the technology object, follow these steps: 1. Open the "Technology objects" folder in the project tree. 2. Open the technology object in the project tree. 3. Double-click the "Commissioning" object. The commissioning functions are specific for each controller and are described there. 4224 WinCC Basic V13.0 System Manual, 02/2014 Using technology functions 11.1 PID control 11.1.2.8 Save optimized PID parameter in the project The software controller is optimized in the CPU. Through this, the values in the instance-DB on the CPU no longer agree with those in the project. To update the PID parameter in the project with the optimized PID parameters, proceed as follows: Requirement An online connection to the CPU is established and the CPU is in "RUN" mode. The functions of the commissioning window have been enabled by means of the "Start" button. Procedure 1. Open the CPU folder in the project tree. 2. Open the "Technology objects" folder. 3. Open a technology object. 4. Double click on "Commissioning". 5. Click on the icon "Upload PID parameters". 6. Save the project. Result The currently active PID parameters are stored in the project data. When reloading the project data in the CPU, the optimized parameters are used. 11.1.2.9 Comparing values Comparison display and boundary conditions The "Compare values" function provides the following options: Comparison of configured start values of the project with the start values in the CPU and the actual values Direct editing of actual values and the start values of the project Immediate detection and display of input errors with suggested corrections Backup of actual values in the project Transfer of start values of the project to the CPU as actual values WinCC Basic V13.0 System Manual, 02/2014 4225 Using technology functions 11.1 PID control Icons and operator controls The following icons and operator controls are available: Icon Function Start value PLC matches the configured Start value project Start value PLC does not match the configured Start value project The comparison of the Start value PLC with the configured Start value project cannot be performed At least one of the two comparison values has a process-related or syntax error. Transfers actual values to the offline project Transfers updated start values in the project to the CPU (initialize setting values) Opens the "Compare values" dialog Boundary conditions The "Compare values" function is available for S7-1200 and S7-1500 without limitations. The following limitation applies to S7-300 and S7-400: In monitoring mode, an S7-300/S7-400 cannot transfer the start values to the CPU. These values cannot be displayed online with "Compare values". The actual values of the technology object are displayed and can be changed directly. Comparing values The procedure is shown in the following using "PID Parameters" as an example. Requirements A project with a software controller is configured. The project is downloaded to the CPU. The configuration dialog is open in the project navigator. Procedure 1. Open the desired software controller in the project navigation. 2. Double-click the "Configuration" object. 3. Navigate within the configuration window to the "PID Parameters" dialog. 4. Click the icon to activate monitoring mode. The icons and operator controls (Page 4225) of the "Compare values" function are shown behind the parameters. 4226 WinCC Basic V13.0 System Manual, 02/2014 Using technology functions 11.1 PID control 5. Click the desired parameter in the input box and change the parameter values manually by entering them directly. - If the background of the input box is gray, this value is a read-only value and cannot be changed. - To change the values in the "PID Parameters" dialog, enable manual entry by selecting the "Enable manual entry" check box beforehand. 6. Click the icon to open the dialog for the start values. This dialog indicates two values of the parameter: - Start value in CPU: The start value in the CPU is shown in the top part. - Start value in the project: The configured start value in the project is shown in the bottom part. 7. Enter the desired value in the input box for the project. Error detection The input of incorrect values is detected. Corrections are suggested in this case. If you enter a value with incorrect syntax, a rollout containing the corresponding error message opens below the parameter. The incorrect value is not applied. If you enter a value that is incorrect for the process, a dialog opens containing the error message and a suggested correction: Click "No" to accept this suggested correction and correct your input. Click "OK" to apply the incorrect value. NOTICE Malfunctions of the controller Values incorrect for the process can result in controller malfunctions. Backing up actual values Click the project. WinCC Basic V13.0 System Manual, 02/2014 icon to transfer the actual controller values to the start values of your configured 4227 Using technology functions 11.1 PID control Transferring project values to the CPU Click the icon to transfer the configured values of your project to the CPU. CAUTION Prevent personal injury and property damage! Downloading and resetting of the user program while the plant is operating may result in significant property damage and severe personal injuries in the event of malfunctions or program errors. Make sure that dangerous states cannot occur before you download and reset the user program. 11.1.2.10 Parameter view Introduction to the parameter view The Parameter view provides you with a general overview of all relevant parameters of a technology object. You obtain an overview of the parameter settings and can easily change them in offline and online mode. 4228 WinCC Basic V13.0 System Manual, 02/2014 Using technology functions 11.1 PID control "Parameter view" tab Toolbar (Page 4230) Navigation (Page 4231) Parameter table (Page 4231) Function scope The following functions are available for analyzing the parameters of the technology objects and for enabling targeted monitoring and modification. Display functions: Display of parameter values in offline and online mode Display of status information of the parameters Display of value deviations and option for direct correction Display of configuration errors Display of value changes as a result of parameter dependencies Display of all memory values of a parameter: Start value PLC, Start value project, Monitor value Display of the parameter comparison of the memory values of a parameter Operator control functions: Navigation for quickly changing between the parameters and parameter structures. Text filter for faster searches for particular parameters. Sorting function for customizing the order of parameters and parameter groups to requirements. Memory function for backing up structural settings of the Parameter view. Monitoring and modifying of parameter values online. Function for saving a snapshot of parameter values of the CPU in order to capture momentary situations and to respond to them. Function for applying a snapshot of parameter values as start values. Download of modified start values to the CPU. Comparison functions for comparing parameter values with one another. Validity The Parameter view is available for the following technology objects: PID_Compact PID_3Step CONT_C (S7-1500 only) CONT_S (S7-1500 only) WinCC Basic V13.0 System Manual, 02/2014 4229 Using technology functions 11.1 PID control TCONT_CP (S7-1500 only) TCONT_S (S7-1500 only) TO_Axis_PTO (S7-1200 Motion Control) TO_Positioning_Axis (S7-1200 Motion Control) TO_CommandTable_PTO (S7-1200 Motion Control) TO_CommandTable (S7-1200 Motion Control) Structure of the parameter view Toolbar The following functions can be selected in the toolbar of the parameter view. Icon Function Explanation Monitor all Starts the monitoring of visible parameters in the active Parameter view (online mode). Create snapshot of Applies the current monitor values to the "Snapshot" column and monitor values and updates the start values in the project. accept setpoints of this Only in online mode for PID_Compact and PID_3Step. snapshot as start values Initialize setpoints Transfers the start values updated in the project to the CPU. Create snapshot of monitor values Applies the current monitor values to the "Snapshot" column. Modify all selected parameters immediately and once This command is executed once and as quickly as possible without reference to any particular point in the user program. Select navigation structure Toggles between functional navigation and data navigation. Text filter... After entry of a character string: Display of all parameters containing the specified string in one of the currently visible columns. Selection of compare values Selection of parameter values that are to be compared with one another in online mode (Start value project, Start value PLC, Snapshot) Only in online mode for PID_Compact and PID_3Step. Only in online mode. Only in online mode. Only in online mode. Save window settings 4230 Saves your display settings for the Parameter view (e.g., selected navigation structure, activated table columns, etc.) WinCC Basic V13.0 System Manual, 02/2014 Using technology functions 11.1 PID control Navigation Within the "Parameter view" tab, the following alternative navigation structures can be selected. Navigation Explanation Functional navigation In the functional navigation, the structure of the parameters is based on the structure in the configuration dialog ("Functional view" tab), commissioning dialog, and diagnostics dialog. The last group "Other parameters" contains all other parameters of the technology object. Data navigation In the data navigation, the structure of the parameters is based on the structure in the instance DB. The last group "Other parameters" contains the parameters that are not contained in the instance DB. You can use the "Select navigation structure" drop-down list to toggle the navigation structure. Parameter table The table below shows the meaning of the individual columns of the parameter table. You can show or hide the columns as required. Column "Offline" = X: Column is visible in offline mode. Column "Online" = X: Column is visible in online mode (online connection to the CPU). Column Explanation Offline Online Name in functional view Name of the parameter in the functional view. X X Full name in DB Complete path of the parameter in the instance DB. X X X X The display field is empty for parameters that are not configured via the technology object. The display field is empty for parameters that are not contained in the instance DB. Name in DB Name of the parameter in the instance DB. If the parameter is part of a structure or UDT, the prefix ". ./" is added. The display field is empty for parameters that are not contained in the instance DB. Status of configuration Display of the completeness of the configuration using status symbols. Compare result Result of the "Compare values" function. X see Status of configuration (offline) (Page 4239) X This column is shown if there is an online connection and the "Monitor all" button is selected. see Comparing values (Page 4225) WinCC Basic V13.0 System Manual, 02/2014 4231 Using technology functions 11.1 PID control Column Explanation Offline Online Start value project Configured start value in the project. X X X X X X Error indication if entered values have a syntax or process-related error. Default value Value that is pre-assigned to the parameter. The display field is empty for parameters that are not contained in the instance DB. Snapshot Snapshot of the current values in the CPU (monitor values). Error indication if values have a process-related error. Start value PLC Start value in the CPU. X This column is shown if there is an online connection and the "Monitor all" button is selected. Error indication if values have a process-related error. Monitor value Current value in the CPU. X This column is shown if there is an online connection and the "Monitor all" button is selected. Error indication if values have a process-related error. Modify value Value that is to be used to change the monitor valuet. X This column is shown if there is an online connection and the "Monitor all" button is selected. Error indication if entered values have a syntax or process-related error. Selection for transmission Selection of the Modify values that are to be transmitted using the "Modify all selected parameters immediately and once" button. X This column is displayed together with the "Modify value" column. Minimum value Minimum process-related value of the parameter. X X X X If the minimum value is dependent on other parameters, it is defined: Offline: By the Start value project. Online: By the Monitor values. Maximum value Maximum process-related value of the parameter. If the maximum value is dependent on other parameters, it is defined: Offline: By the Start value project. Online: By the Monitor values. Setpoint Designates the parameter as a setpoint. These parameters can be initialized online. X X Data type Data type of the parameter. X X X X Accessible from HMI Indicates whether the HMI can access this parameter during runtime. X X Visible in HMI Indicates whether the parameter is visible in the selection list of the HMI by default. X X Comment Brief description of the parameter. X X The display field is empty for parameters that are not contained in the instance DB. Retain Designates the value as a retentive value. The values of retentive parameters are retained even after the voltage supply is switched off. 4232 WinCC Basic V13.0 System Manual, 02/2014 Using technology functions 11.1 PID control Opening the parameter view Requirement The technology object has been added in the project tree, i.e., the associated instance DB of the instruction has been created. Procedure 1. Open the "Technology objects" folder in the project tree. 2. Open the technology object in the project tree. 3. Double-click the "Configuration" object. 4. Select the "Parameter view" tab in the top right corner. Result The Parameter view opens. Each displayed parameter is represented by one row in the parameter table. The displayable parameter properties (table columns) vary depending on whether you are working with the Parameter view in offline or online mode. In addition, you can selectively display and hide individual table columns. See also Default setting of the parameter view (Page 4233) Default setting of the parameter view Default settings To enable you to work efficiently with the Parameter view, you can customize the parameter display and save your settings. The following customizations are possible and can be saved: Show and hide columns Change column width Change order of the columns Toggle navigation Select parameter group in the navigation Selection of compare values WinCC Basic V13.0 System Manual, 02/2014 4233 Using technology functions 11.1 PID control Show and hide columns To show or hide columns in the parameter table, follow these steps: 1. Position the cursor in the header of the parameter table. 2. Select the "Show/Hide" command in the shortcut menu. The selection of available columns is displayed. 3. To show a column, select the check box for the column. 4. To hide a column, clear the check box for the column. or 1. Position the cursor in the header of the parameter table. 2. Select the "Show all columns" command in the shortcut menu if all columns of the offline or online mode are to be displayed. Some columns can only be displayed in online mode: see Parameter table (Page 4231). Change column width To customize the width of a column so that all texts in the rows can be read, follow these steps: 1. Position the cursor in the header of the parameter table to the right of the column to be customized until the shape of the cursor changes to a cross. 2. Then double-click this location. or 1. Open the shortcut menu on the header of the parameter table. 2. Click - "Optimize column width" or - "Optimize width of all columns". If the column width setting is too narrow, the complete content of individual fields are shown if you hover the cursor briefly over the relevant field. Change order of the columns The columns of the parameter table can be arranged in any way. To change the order of the columns, follow these steps: 4234 WinCC Basic V13.0 System Manual, 02/2014 Using technology functions 11.1 PID control 1. Click on the column header and use a drag-and-drop operation to move it to the desired location. When you release the mouse button, the column is anchored to the new position. Toggle navigation To toggle the display form of the parameters, follow these steps: 1. Select the desired navigation in the "Select navigation structure" drop-down list. - Data navigation - Functional navigation See also Navigation (Page 4231). Select parameter group in the navigation Within the selected navigation, you choose between the "All parameters" display or the display of a subordinate parameter group of your choice. 1. Click the desired parameter group in the navigation. The parameter table only displays the parameters of the parameter group. Selection of compare values (online) To set the compare values for the "Compare values" function, follow these steps: 1. Select the desired compare values in the "Selection of compare values" drop-down list. - Start value project / Start value PLC - Start value project / Snapshot - Start value PLC / Snapshot The "Start value project / Start value PLC" option is set by default. Save default setting of the Parameter view To save the above customizations of the Parameter view, follow these steps: 1. Customize the Parameter view according to your requirements. 2. Click the "Save window settings" button at the top right of the Parameter view. Working with the parameter view Overview The following table provides an overview of the functions of the Parameter view in online and offline mode described in the following. Column "Offline" = X: This function is possible in offline mode. Column "Online" = X: This function is possible in online mode. WinCC Basic V13.0 System Manual, 02/2014 4235 Using technology functions 11.1 PID control Function/action Offline Online Filtering the parameter table (Page 4236) X X Sorting the parameter table (Page 4237) X X Transferring parameter data to other editors (Page 4237) X X Indicating errors (Page 4237) X X Editing start values in the project (Page 4238) X X Status of configuration (offline) (Page 4239) X Monitoring values online in the parameter view (Page 4240) X Create snapshot of monitor values (Page 4240) X Modifying values (Page 4241) X Comparing values (Page 4242) X Applying values from the online program as start values (Page 4243) X Initializing setpoints in the online program (Page 4244) X Filtering the parameter table You can filter the parameters in the parameter table in the following ways: With the text filter With the subgroups of the navigation Both filter methods can be used simultaneously. With the text filter Texts that are visible in the parameter table can be filtered. This means only texts in displayed parameter rows and columns can be filtered. 1. Enter the desired character string for filtering in the "Text filter..." input box. The parameter table displays only the parameters containing the character string. The text filtering is reset. When another parameter group is selected in the navigation. When navigation is changed from data navigation to functional navigation, or vice versa. With the subgroups of the navigation 1. Click the desired parameter group in the navigation, e.g., "Static". The parameter table only shows the static parameters. You can select further subgroups for some groups of the navigation. 2. Click "All parameters" in the navigation if all parameters are to be shown again. 4236 WinCC Basic V13.0 System Manual, 02/2014 Using technology functions 11.1 PID control Sorting the parameter table The values of the parameters are arranged in rows. The parameter table can be sorted by any displayed column. In columns containing numerical values, sorting is based on the magnitude of the numerical value. In text columns, sorting is alphabetical. Sorting by column 1. Position the cursor in the header cell of the desired column. The background of this cell turns blue. 2. Click the column header. Result The entire parameter table is sorted by the selected column. A triangle with tip facing up appears in the column header. Clicking the column header again changes the sorting as follows: Symbol "": Parameter table is sorted in ascending order. Symbol "": Parameter table is sorted in descending order. No symbol: The sorting is removed again. The parameter table assumes the default display. The "../" prefix in the "Name in DB" column is ignored when sorting. Transferring parameter data to other editors After selecting an entire parameter row of the parameter table, you can use the following: Drag-and-drop <Ctrl+C>/<Ctrl+V> Copy/Paste via shortcut menu Transfer parameters to the following editors of the TIA Portal: Program editor Watch table Signal table for trace function The parameter is inserted with its full name: See information in "Full name in DB" column. Indicating errors Error indication Parameter assignment errors that result in compilation errors (e.g., limit violation) are indicated in the Parameter view. WinCC Basic V13.0 System Manual, 02/2014 4237 Using technology functions 11.1 PID control Every time a value is input in the Parameter view, a check is made for process-related and syntax errors and the result is indicated. Bad values are indicated by: Red error symbol in the "Status of configuration" (offline mode) or "Compare result" (online mode, depending on the selected comparison type) columns and/or Table field with red background If you click the bad field, a roll-out error message appears with information of the permissible value range or the required syntax (format) Compilation error From the error message of the compiler, you can directly open the Parameter view (functional navigation) containing the parameter causing the error in situations where the parameter is not displayed in the configuration dialog. Editing start values in the project With the Parameter view, you can edit the start values in the project in offline mode and online mode. You make value changes in the "Start value project" column of the parameter table. In the "Status of configuration" column of the parameter table, the progress of the configuration is indicated by the familiar status symbols from the configuration dialog of the technology object. Boundary conditions If other parameters depend on the parameter whose start value was changed, the start value of the dependent parameters are also adapted. If a parameter of a technology object is not editable, it is also not editable in the parameter view. The ability to edit a parameter can also depend on the values of other parameters. Defining new start values To define start values for parameters in the Parameter view, follow these steps: 1. Open the Parameter view of the technology object. 2. Enter the desired start values in the "Start value project" column. The value must match the data type of the parameter and must not exceed the value range of the parameter. The limits of the value range can be seen in the "Maximum value" and "Minimum value" columns. The "Status of configuration" column indicates the progress of the configuration with colored symbols. See also Status of configuration (offline) (Page 4239) 4238 WinCC Basic V13.0 System Manual, 02/2014 Using technology functions 11.1 PID control Following adaptation of the start values and downloading of the technology object to the CPU, the parameters take the defined value at startup if they are not declared as retentive ("Retain" column). Error indication When a start value is input, a check is made for process-related and syntax errors and the result is indicated. Bad start values are indicated by: Red error symbol in the "Status of configuration" (offline mode) or "Compare result" (online mode, depending on the selected comparison type) columns and/or Red background in the "Start value project" field If you click on the bad field, a roll-out error message appears with information of the permissible value range or the necessary syntax (format) Correcting bad start values 1. Correct bad start values using information from the roll-out error message. Red error symbol, red field background, and roll-out error message are no longer displayed. The project cannot be successfully compiled unless the start values are error-free. Status of configuration (offline) The status of the configuration is indicated by icons: In the "Status of configuration" column in the parameter table In the navigation structure of the functional navigation and data navigation Symbol in "Status of configuration" column Symbol Meaning The start value of the parameter corresponds to the default value and is valid. A start value has not yet been defined by the user. The start value of the parameter contains a value defined by the user. The start value is different than the default value. The start value is error-free and valid. The start value of the parameter is invalid (syntax or process-related error). The input box has a red background. When clicked, the roll-out error message indicates the cause of the error. Only for S7-1200 Motion Control: The start value of the parameter is valid but contains warnings. The input box has a yellow background. WinCC Basic V13.0 System Manual, 02/2014 4239 Using technology functions 11.1 PID control Symbol in the navigation The symbols in the navigation indicate the progress of the configuration in the same way as in the configuration dialog of the technology object. See Configure technology objects (Page 4221) Monitoring values online in the parameter view You can monitor the values currently taken by the parameters of the technology object in the CPU (monitor values) directly in the Parameter view. Requirements There is an online connection. The technology object is downloaded to the CPU. The program execution is active (CPU in "RUN"). The Parameter view of the technology object is open. Procedure 1. Start the monitoring by clicking . As soon as the Parameter view is online, the following columns are additionally displayed: - Compare result - Start value PLC - Monitor value - Modify value - Selection for transmission The "Monitor value" column shows the current parameter values on the CPU. Meaning of the additional columns: see Parameter table (Page 4231) 2. Stop the monitoring by clicking again. Display All columns that are only available online have an orange background: Values in light-orange cells can be changed. Values in cells with a dark orange background cannot be changed. Create snapshot of monitor values You can back up the current values of the technology object on the CPU (monitor values) and display them in the Parameter view. 4240 WinCC Basic V13.0 System Manual, 02/2014 Using technology functions 11.1 PID control Requirements There is an online connection. The technology object is downloaded to the CPU. The program execution is active (CPU in "RUN"). The Parameter view of the technology object is open. The "Monitor all" button is selected. Procedure To show the current parameter values, follow these steps: 1. In the Parameter view, click the "Create snapshot of monitor values" icon . Result The current monitor values are transferred once to the "Snapshot" column of the parameter table. You can analyze the values "frozen" in this way while the monitor values continue to be updated in the "Monitor values" column. Modifying values With the Parameter view, you can modify values of the technology object in the CPU. You can assign values to the parameter once (Modify value) and modify them immediately. The modify request is executed as quickly as possible without reference to any particular point in the user program. DANGER Danger when modifying: Changing the parameter values while the plant is operating may result in severe damage to property and personal injury in the event of malfunctions or program errors. Make sure that dangerous states cannot occur before you use the "Modify" function. Requirements There is an online connection. The technology object is downloaded to the CPU. The program execution is active (CPU in "RUN"). The Parameter view of the technology object is open. WinCC Basic V13.0 System Manual, 02/2014 4241 Using technology functions 11.1 PID control The "Monitor all" button is selected. The parameter can be modified (associated field in the "Modify value" column has a lightorange background). Procedure To modify parameters immediately, follow these steps: 1. Enter the desired modify values in the "Modify values" column of the parameter table. 2. Check whether the check box for modifying is selected in the "Select for transmission" column. The modify values and associated check boxes of dependent parameters are automatically adapted at the same time. 3. Click the "Modify all selected parameters immediately and once" icon . The selected parameters are modified once and immediately with the specified values and can be monitored in the "Modify values" column. The check boxes for modifying in the "Selection for transmission" column are automatically cleared after the modify request is complete. Error indication When a start value is input, a check is made immediately for process-related and syntax errors and the result is indicated. Bad start values are indicated by: Red background in the "Modify value" field and If you click the bad field, a roll-out error message appears with information of the permissible value range or the necessary syntax (format) Bad modify values Modify values with process-related errors can be transmitted. Modify values with syntax errors cannot be transmitted. Comparing values You can use comparison functions to compare the following memory values of a parameter: Start value project Start value PLC Snapshot 4242 WinCC Basic V13.0 System Manual, 02/2014 Using technology functions 11.1 PID control Requirements There is an online connection. The technology object is downloaded to the CPU. The program execution is active (CPU in "RUN"). The Parameter view of the technology object is open. The "Monitor all" button is selected. Procedure To compare the start values on the various target systems, follow these steps: . 1. Click the "Selection of compare values" icon A selection list containing the comparison options opens: - Start value project - Start value PLC (default setting) - Start value project - Snapshot - Start value PLC - Snapshot 2. Select the desired comparison option. The selected comparison option is executed as follows: - A scales symbol appears in the header cells of the two columns selected for comparison. - Symbols are used in the "Compare result" column to indicate the result of the comparison of the selected columns. Symbol in "Compare result" column Symbol Meaning The compare values are equal and error-free. The compare values are not equal and error-free. At least one of the two compare values has a process-related or syntax error. The comparison cannot be performed. At least one of the two compare values is not available (e.g., snapshot). Symbol in the navigation The symbols are shown in the same way in the navigation if the comparison result applies to at least one of the parameters below the displayed navigation structure. Applying values from the online program as start values In order to apply optimized values from the CPU to the project as start values, you create a snapshot of the monitor values. Values of the snapshot marked as a "Setpoint" are then applied to the project as start values. WinCC Basic V13.0 System Manual, 02/2014 4243 Using technology functions 11.1 PID control Requirements The technology object is of type "PID_Compact" or "PID_3Step". There is an online connection. The technology object is downloaded to the CPU. The program execution is active (CPU in "RUN"). The Parameter view of the technology object is open. The "Monitor all" button is selected. Procedure To apply optimized values from the CPU, follow these steps: 1. Click the "Create snapshot of monitor values and accept setpoints of this snapshot as start values" icon . Result The current monitor values are applied to the "Snapshot" column and their setpoints are copied to the "Start value project" column as new start values. Note Applying values of individual parameters You can also apply the values of individual parameters that are not marked as a setpoint from the "Snapshot" column to the "Start values project" column. To do so, copy the values and insert them into the "Start value project" column using the "Copy" and "Paste" commands in the shortcut menu. Initializing setpoints in the online program You can initialize all parameters that are marked as a "Setpoint" in the Parameter view with new values in the CPU in one step. In so doing, the start values are downloaded from the project to the CPU. The CPU remains in "RUN" mode. To avoid data loss on the CPU during a cold restart or warm restart, you must also download the technology object to the CPU. DANGER Danger when changing parameter values Changing the parameter values while the plant is operating may result in severe damage to property and personal injury in the event of malfunctions or program errors. Make sure that dangerous states cannot occur before you reinitialize the setpoints. 4244 WinCC Basic V13.0 System Manual, 02/2014 Using technology functions 11.1 PID control Requirements The technology object is of type "PID_Compact" or "PID_3Step". There is an online connection. The technology object is downloaded to the CPU. The program execution is active (CPU in "RUN"). The Parameter view of the technology object is open. The "Monitor all" button is selected. The parameters marked as a "Setpoint" have a "Start value project" that is free of processrelated and syntax errors Procedure To initialize all setpoints, follow these steps: 1. Enter the desired values in the "Start value project" column. Ensure that the start values are free of process-related and syntax errors. 2. Click the "Initialize setpoints" icon . Result The setpoints in the CPU are initialized with the start values from the project. 11.1.2.11 Display instance DB of a technology object. An instance DB, in which the parameter and static variables are saved, is created for each technology object. Procedure To display the instance DB of a technology object, proceed as follows: 1. Open the CPU folder in the project tree. 2. Open the "Technology objects" folder. 3. Highlight a technology object. 4. Select the command "Open DB editor" in the shortcut menu. 11.1.3 Using PID_Compact 11.1.3.1 Technology object PID_Compact The technology object PID_Compact provides a continuous PID controller with integrated optimization. You can alternatively configure a pulse controller. Both manual and automatic mode are possible. WinCC Basic V13.0 System Manual, 02/2014 4245 Using technology functions 11.1 PID control PID-Compact continuously acquires the measured process value within a control loop and compares it with the required setpoint. From the resulting control deviation, the instruction PID_Compact calculates an output value by which the process value is adapted as quickly and stable as possible to the setpoint. The output value for the PID controller consists of three actions: P action The proportional action of the output value increases in proportion to the control deviation. I action The integral action of the output value increases until the control deviation has been balanced. D action The derivative action increases with the rate of change of control deviation. The process value is corrected to the setpoint as quickly as possible. The derivative action will be reduced again if the rate of change of control deviation drops. The instruction PID_Compact calculates the proportional, integral and derivative parameters for your controlled system during pretuning. Fine tuning can be used to tune the parameters further. You do not need to manually determine the parameters. Additional information Overview of software controller (Page 4218) Add technology objects (Page 4220) Configure technology objects (Page 4221) Configuring PID_Compact V2 (Page 4246) Configuring PID_Compact V1 (Page 4262) 11.1.3.2 PID_Compact V2 Configuring PID_Compact V2 Basic settings Introduction Configure the following properties of the "PID_Compact" technology object under "Basic settings" in the Inspector window or in the configuration window: Physical quantity Control logic Start-up behavior after reset Setpoint (only in the Inspector window) 4246 WinCC Basic V13.0 System Manual, 02/2014 Using technology functions 11.1 PID control Process value (only in the Inspector window) Output value (only in the Inspector window) Setpoint, process value and output value You can only configure the setpoint, process value and output value in the Inspector window of the programming editor. Select the source for each value: Instance DB The value saved in the instance DB is used. Value must be updated in the instance DB by the user program. There should be no value at the instruction. Change via HMI possible. Instruction The value connected to the instruction is used. The value is written to the instance DB each time the instruction is called. No change via HMI possible. Controller type Physical quantity Select the physical quantity and unit of measurement for setpoint, process value, and disturbance variable in the "Controller type" group. Setpoint, process value, and disturbance variable is displayed in this unit of measurement. Control logic An increase of the output value is generally intended to cause an increase in the process value. This is referred to as a normal control logic. PID_Compact does not work with negative proportional gain. Select the check box "Invert control logic" to reduce the process value with a higher output value. Examples Opening the drain valve will reduce the level of a container's contents. Increasing cooling will reduce the temperature. WinCC Basic V13.0 System Manual, 02/2014 4247 Using technology functions 11.1 PID control Startup characteristics 1. To switch to "Inactive" mode after CPU restart, clear the "Activate Mode after CPU restart" check box. To switch to the operating mode saved in the Mode parameter after CPU restart, select the "Activate Mode after CPU restart" check box. 2. In the "Set Mode to" drop-down list, select the mode that is to be enabled after a complete download to the device. After a complete download to the device, PID_Compact starts in the selected operating mode. With each additional restart, PID_Compact starts in the mode that was last saved in Mode. Example You have selected the "Activate Mode after CPU restart" check box and the entry "Pretuning" in the "Set Mode to" list. After a complete download to the device, PID_Compact starts in the "Pretuning" mode. If pretuning is still active, PID_Compact starts in "Pretuning" mode again after restart of the CPU. If pretuning was successfully completed and automatic mode is active, PID_Compact starts in "Automatic mode" after restart of the CPU. Setpoint Procedure Proceed as follows to define a fixed setpoint: 1. Select "Instance DB". 2. Enter a setpoint, e.g. 80 C. 3. Delete any entry in the instruction. Proceed as follows to define a variable setpoint: 1. Select "Instruction". 2. Enter the name of the REAL variable in which the setpoint is saved. Program-controlled assignment of various values to the REAL variable is possible, for example for the time controlled change of the setpoint. Process value PID_Compact will scale the value of the analog input to the physical quantity if you use the analog input value directly. You will need to write a program for processing if you wish first to process the analog input value. The process value is, for example, not directly proportional to the value at the analog input. The processed process value must be in floating point format. 4248 WinCC Basic V13.0 System Manual, 02/2014 Using technology functions 11.1 PID control Procedure Proceed as follows to use the analog input value without processing: 1. Select the entry "Input_PER" in the drop-down list "Input". 2. Select "Instruction" as source. 3. Enter the address of the analog input. Proceed as follows to use the processed process value in floating point format: 1. Select the entry "Input" in the drop-down list "Input". 2. Select "Instruction" as source. 3. Enter the name of the variable in which the processed process value is saved. Output value PID_Compact offers three output values. Your actuator will determine which output value you use. Output_PER The actuator is triggered via an analog output and controlled with a continuous signal, e.g. 0...10V, 4...20mA. Output The output value needs to be processed by the user program, for example because of nonlinear actuator response. Output_PWM The actuator is controlled via a digital output. Pulse width modulation creates minimum ON and minimum OFF times. Procedure Proceed as follows to use the analog output value: 1. Select the entry "Output_PER (analog)" in the drop-down list "Output". 2. Select "Instruction". 3. Enter the address of the analog output. Proceed as follows to process the output value using the user program: 1. Select the entry "Output" in the drop-down list "Output". 2. Select "Instance DB". The calculated output value is saved in the instance data block. 3. For the preparation of the output value, use the output parameter Output. 4. Transfer the processed output value to the actuator via a digital or analog CPU output. Proceed as follows to use the digital output value: 1. Select the entry "Output_PWM" in the drop-down list "Output". 2. Select "Instruction". 3. Enter the address of the digital output. WinCC Basic V13.0 System Manual, 02/2014 4249 Using technology functions 11.1 PID control Process value settings Scaling the process value If you have configured the use of Input_PER in the basic setting, you must convert the value of the analog input to the physical quantity of the process value. The current configuration is displayed in the Input_PER display. Input_PER will be scaled using a low and high value pair if the process value is directly proportional to the value of the analog input. Procedure To scale the process value, follow these steps: 1. Enter the low pair of values in the "Scaled low process value" and "Low" input fields. 2. Enter the high pair of values in the "Scaled high process value" and "High" input boxes. Default settings for the value pairs are stored in the hardware configuration. To use the value pairs from the hardware configuration, follow these steps: 1. Select the PID_Compact instruction in the programming editor. 2. Interconnect Input_PER with an analog input in the basic settings. 3. Click the "Automatic setting" button in the process value settings. The existing values will be overwritten with the values from the hardware configuration. Process value limits You must specify an appropriate absolute high limit and low limit for the process value as limit values for your controlled system. As soon as the process value violates these limits, an error occurs (ErrorBits = 0001h). Tuning is canceled when the process value limits are violated. You can configure how PID_Compact reacts to an error in automatic mode in the output value settings. Advanced settings Monitoring process value Configure a warning high and low limit for the process value in the "Process value monitoring" configuration window. If one of the warning limits is exceeded or undershot during operation, a warning will be displayed at the PID_Compact instruction: At the InputWarning_H output parameter if the warning high limit has been exceeded At the InputWarning_L output parameter if the warning low limit has been undershot The warning limits must be within the process value high and low limits. The process value high and low limits will be used if you do not enter values. 4250 WinCC Basic V13.0 System Manual, 02/2014 Using technology functions 11.1 PID control Example Process value high limit = 98 C; warning high limit = 90 C Warning low limit = 10 C; process value low limit = 0 C PID_Compact will respond as follows: Process value InputWarnin g_H InputWarnin g_L ErrorBi Operating mode ts > 98 C TRUE FALSE 0001h Inactive or Substitute output value with error monitoring 98 C and > 90 C TRUE FALSE 0000h Automatic mode 90 C and 10 C FALSE FALSE 0000h Automatic mode < 10 C and 0 C FALSE TRUE 0000h Automatic mode < 0 C FALSE TRUE 0001h Inactive or Substitute output value with error monitoring In the output value settings, you can specify the reaction of PID_Compact when the process value high limit or low limit is violated. See also Parameters State and Mode V2 (Page 2904) PWM limits The value at the output parameter Output is transformed into a pulse sequence that is output at output parameter Output_PWM by means of a pulse width modulation. Output is calculated in the PID algorithm sampling time, Output_PWM is output in the PID_Compact sampling time. The PID algorithm sampling time is determined during pretuning or fine tuning. If manually setting the PID parameters, you will also need to configure the PID algorithm sampling time. The PID_Compact sampling time is equivalent to the cycle time of the calling OB. The pulse duration is proportional to the value at Output and is always an integer multiple of the PID_Compact sampling time. WinCC Basic V13.0 System Manual, 02/2014 4251 Using technology functions 11.1 PID control 2XWSXW W PV 2XWSXWB3:0 758( )$/6( W PV PID_Compact sampling time PID algorithm sampling time Pulse duration Break time The "Minimum ON time" and the "Minimum OFF time" are rounded to an integer multiple of the PID_Compact sampling time. A pulse or a break is never shorter than the minimum ON or OFF time. The inaccuracies this causes are added up and compensated in the next cycle. Example PID_Compact sampling time = 100 ms PID algorithm sampling time = 1000 ms Minimum ON time = 200 ms Output is a constant 15%. The smallest pulse that PID_Compact can output is 20%. In the first cycle, no pulse is output. In the second cycle, the pulse not output in the first cycle is added to the pulse of the second cycle. 4252 WinCC Basic V13.0 System Manual, 02/2014 Using technology functions 11.1 PID control 2XWSXW 2XWSXWB3:0 W PV 758( )$/6( W PV PID_Compact sampling time PID algorithm sampling time Minimum ON time In order to minimize operation frequency and conserve the actuator, extend the minimum ON and OFF times. If you are using "Output" or "Output_PER", you must configure the value 0.0 for the minimum ON and OFF times. Note The minimum ON and OFF times only affect the output parameter Output_PWM and are not used for any pulse generators integrated in the CPU. Output value Output value limits In the "Output value limits" configuration window, configure the absolute limits of your output value in percent. Absolute output value limits are not violated in neither manual mode nor automatic mode. If an output value outside the limits is specified in manual mode, the effective value is limited in the CPU to the configured limits. The output value limits must match the control logic. The valid output value limit values depend on the Output used. Output -100.0 to 100.0% Output_PER -100.0 to 100.0% Output_PWM 0.0 to 100.0% WinCC Basic V13.0 System Manual, 02/2014 4253 Using technology functions 11.1 PID control Reaction to error NOTICE Your system may be damaged. If you output "Current value while error pending " or "Substitute output value while error pending" in the event of an error, PID_Compact remains in automatic mode. This may cause a violation of the process value limits and damage your system. It is essential to configure how your controlled system reacts in the event of an error to protect your system from damage. PID_Compact is preset so that the controller stays active in most cases in the event of an error. If errors occur frequently in controller mode, this default reaction has a negative effect on the control response. In this case, check the Errorbits parameter and eliminate the cause of the error. PID_Compact generates a programmable output value in response to an error: 4254 WinCC Basic V13.0 System Manual, 02/2014 Using technology functions 11.1 PID control Zero (inactive) PID_Compact outputs 0.0 as output value for all errors and switches to "Inactive" mode. The controller is only reactivated by a falling edge at Reset or a rising edge at ModeActivate. Current value while error is pending If the following errors occur in automatic mode, PID_Compact returns to automatic mode as soon as the errors are no longer pending. If one or more of the following errors occur, PID_Compact stays in automatic mode: - 0001h: The "Input" parameter is outside the process value limits. - 0800h: Sampling time error - 40000h: Invalid value at Disturbance parameter. If one or more of the following errors occur in automatic mode, PID_Compact switches to "Substitute output value with error monitoring" mode and outputs the last valid output value: - 0002h: Invalid value at Input_PER parameter. - 0200h: Invalid value at Input parameter. - 0400h: Calculation of output value failed. - 1000h: Invalid value at Setpoint parameter. If an error occurs in manual mode, PID_Compact continues using the manual value as the output value. If the manual value is invalid, the substitute output value is used. If the manual value and substitute output value are invalid, the output value low limit is used. If the following error occurs during a pretuning or fine tuning, PID_Compact remains in active mode: - 0020h: Pretuning is not permitted during fine tuning. When any other error occurs, PID_Compact cancels the tuning and switches to the mode from which tuning was started. As soon as no errors are pending, PID_Compact returns to automatic mode. Substitute output value while error is pending PID_Compact outputs the substitute output value. If the following error occurs, PID_Compact stays in "Substitute output value with error monitoring" mode and outputs the output value low limit: - 20000h: Invalid value at SubstituteOutput tag. For all other errors, PID_Compact reacts as described for "Current value while error is pending". See also Parameters State and Mode V2 (Page 2904) PID parameters The PID parameters are displayed in the "PID Parameters" configuration window. The PID parameters will be adapted to your controlled system during controller tuning. You do not need to enter the PID parameters manually. WinCC Basic V13.0 System Manual, 02/2014 4255 Using technology functions 11.1 PID control The PID algorithm operates according to the following equation: 1 y = Kp [ (b * w - x) + T * s (w - x) + I Symbol Description y Output value of the PID algorithm TD * s a * TD * s + 1 (c * w - x) Kp Proportional gain s Laplace operator b Proportional action weighting w Setpoint x Process value TI Integral action time a Derivative delay coefficient (derivative delay T1 = a x TD) TD Derivative action time c Derivative action weighting ] The diagram below illustrates the integration of the parameters into the PID algorithm: 6HWSRLQW Z E $QWL:LQGXS /,0,7 , .3 \ F 6FDOHG,QSXW [ '7 All PID parameters are retentive. If you enter the PID parameters manually, you must completely download PID_Compact. Downloading technology objects to device (Page 4223) Proportional gain The value specifies the proportional gain of the controller. PID_Compact does not work with a negative proportional gain. Control logic is inverted under Basic settings > Controller type. 4256 WinCC Basic V13.0 System Manual, 02/2014 Using technology functions 11.1 PID control Integral action time The integral action time determines the time behavior of the integral action. The integral action is deactivated with integral action time = 0.0. Derivative action time The derivative action time determines the time behavior of the derivative action. Derivative action is deactivated with derivative action time = 0.0. Derivative delay coefficient The derivative delay coefficient delays the effect of the derivative action. Derivative delay = derivative action time x derivative delay coefficient 0.0: Derivative action is effective for one cycle only and therefore almost not effective. 0.5: This value has proved useful in practice for controlled systems with one dominant time constant. > 1.0: The greater the coefficient, the longer the effect of the derivative action is delayed. Proportional action weighting The proportional action may weaken with changes to the setpoint. Values from 0.0 to 1.0 are applicable. 1.0: Proportional action for setpoint change is fully effective 0.0: Proportional action for setpoint change is not effective The proportional action is always fully effective when the process value is changed. Derivative action weighting The derivative action may weaken with changes to the setpoint. Values from 0.0 to 1.0 are applicable. 1.0: Derivative action is fully effective upon setpoint change 0.0: Derivative action is not effective upon setpoint change The derivative action is always fully effective when the process value is changed. PID algorithm sampling time The controlled system needs a certain amount of time to respond to changes in the output value. It is therefore not advisable to calculate the output value in every cycle. The sampling time of the PID algorithm represents the time between two calculations of the output value. It is calculated during tuning and rounded to a multiple of the cycle time. All other functions of PID_Compact are executed at every call. If you use Output_PWM, the accuracy of the output signal is determined by the ratio of the PID algorithm sampling time to the cycle time of the OB. The PID algorithm sampling time WinCC Basic V13.0 System Manual, 02/2014 4257 Using technology functions 11.1 PID control corresponds to the time period of the pulse width modulation. The cycle time should be at least 10 times the PID algorithm sampling time. Rule for tuning Select whether PI or PID parameters are to be calculated in the "Controller structure" dropdown list. PID Calculates PID parameters during pretuning and fine tuning. PI Calculates PI parameters during pretuning and fine tuning. User-defined The drop-down list displays "User-defined" if you have configured different controller structures for pretuning and fine tuning via a user program. Commissioning PID_Compact V2 Pretuning The pretuning determines the process response to a jump change of the output value and searches for the point of inflection. The PID parameters are calculated from the maximum rate of rise and dead time of the controlled system. You obtain the best PID parameters when you perform pretuning and fine tuning. The more stable the process value is, the easier it is to calculate the PID parameters and the more precise the result will be. Noise on the process value can be tolerated as long as the rate of rise of the process value is significantly higher compared to the noise. This is most likely the case in operating modes "Inactive" and "manual mode". The PID parameters are backed up before being recalculated. Requirement The "PID_Compact" instruction is called in a cyclic interrupt OB. ManualEnable = FALSE Reset = FALSE PID_Compact is in one of the following modes: "Inactive", "Manual mode", or "Automatic mode". The setpoint and the process value lie within the configured limits (see "Process value monitoring" configuration). The difference between setpoint and process value is greater than 30% of the difference between process value high limit and process value low limit. The distance between the setpoint and the process value is > 50% of the setpoint. 4258 WinCC Basic V13.0 System Manual, 02/2014 Using technology functions 11.1 PID control Procedure To perform pretuning, follow these steps: 1. Double-click the "PID_Compact > Commissioning" entry in the project tree. 2. Select the entry "Pretuning" in the "Tuning mode" drop-down list. 3. Click the "Start" icon. - An online connection will be established. - Value recording is started. - Pretuning is started. - The "Status" field displays the current steps and any errors that may have occurred. The progress bar indicates the progress of the current step. Note Click the "Stop" icon when the progress bar has reached 100% and it can be assumed the controller tuning function is blocked. Check the configuration of the technology object and, if necessary, restart controller tuning. Result If pretuning was performed without an error message, the PID parameters have been tuned. PID_Compact switches to automatic mode and uses the tuned parameters. The tuned PID parameters will be retained during power OFF and a restart of the CPU. If pretuning is not possible, PID_Compact responds with the configured reaction to errors. See also Parameters State and Mode V2 (Page 2904) Fine tuning Fine tuning generates a constant, limited oscillation of the process value. The PID parameters are tuned for the operating point from the amplitude and frequency of this oscillation. All PID parameters are recalculated from the results. PID parameters from fine tuning usually have better master control and disturbance characteristics than PID parameters from pretuning. You obtain the best PID parameters when you perform pretuning and fine tuning. PID_Compact automatically attempts to generate an oscillation greater than the noise of the process value. Fine tuning is only minimally influenced by the stability of the process value. The PID parameters are backed up before being recalculated. Requirement The PID_Compact instruction is called in a cyclic interrupt OB. ManualEnable = FALSE Reset = FALSE WinCC Basic V13.0 System Manual, 02/2014 4259 Using technology functions 11.1 PID control The setpoint and the process value lie within the configured limits. The control loop has stabilized at the operating point. The operating point is reached when the process value corresponds to the setpoint. No disturbances are expected. PID_Compact is in one of the following operating modes: Inactive, automatic mode, or manual mode. Process depends on initial situation Fine tuning can be started from the following operating modes: "Inactive", "automatic mode", or "manual mode". Fine tuning proceeds as follows when started from: Automatic mode Start fine tuning from automatic mode if you wish to improve the existing PID parameters through tuning. PID_Compact controls the system using the existing PID parameters until the control loop has stabilized and the requirements for fine tuning have been met. Only then will fine tuning start. Inactive or manual mode If the requirements for pretuning are met, pretuning is started. The determined PID parameters will be used for control until the control loop has stabilized and the requirements for fine tuning have been met. Only then will fine tuning start. If pretuning is not possible, PID_Compact responds with the configured reaction to errors. An attempt is made to reach the setpoint with the minimum or maximum output value if the process value for pretuning is already too near the setpoint. This can produce increased overshoot. Procedure To perform fine tuning, follow these steps: 1. Select the entry "Fine tuning" in the "Tuning mode" drop-down list. 2. Click the "Start" icon. - An online connection will be established. - Value recording is started. - The process of fine tuning is started. - The "Status" field displays the current steps and any errors that may have occurred. The progress bar indicates the progress of the current step. Note Click the "Stop" icon in the "Tuning mode" group when the progress bar has reached 100% and it is to be assumed that tuning is blocked. Check the configuration of the technology object and, if necessary, restart controller tuning. 4260 WinCC Basic V13.0 System Manual, 02/2014 Using technology functions 11.1 PID control Result If no errors occurred during fine tuning, the PID parameters have been tuned. PID_Compact switches to automatic mode and uses the tuned parameters. The tuned PID parameters will be retained during power OFF and a restart of the CPU. If errors occurred during "fine tuning", PID_Compact responds with the configured response to errors. See also Parameters State and Mode V2 (Page 2904) "Manual" mode The following section describes how you can use the "manual mode" operating mode in the commissioning window of the "PID_Compact" technology object. Manual mode is also possible when an error is pending. Requirement The "PID_Compact" instruction is called in a cyclic interrupt OB. An online connection to the CPU has been established and the CPU is in the "RUN" mode. Procedure Use "Manual mode" in the commissioning window if you want to test the controlled system by specifying a manual value. To define a manual value, follow these steps: 1. Click the "Start" icon. 2. Select the "Manual mode" check box in the "Online status of controller" area. PID_Compact operates in manual mode. The most recent current output value remains in effect. 3. Enter the manual value in the "Output" field as a % value. 4. Click the icon. Result The manual value is written to the CPU and immediately goes into effect. Clear the "Manual mode" check box if the output value is to be specified again by the PID controller. The switchover to automatic mode is bumpless. See also Parameters State and Mode V2 (Page 2904) WinCC Basic V13.0 System Manual, 02/2014 4261 Using technology functions 11.1 PID control 11.1.3.3 PID_Compact V1 Configuring PID_Compact V1 Basic settings Introduction Configure the following properties of the "PID_Compact" technology object under "Basic settings" in the Inspector window or in the configuration window: Physical quantity Control logic Start-up behavior after reset Setpoint (only in the Inspector window) Process value (only in the Inspector window) Output value (only in the Inspector window) Setpoint, process value and output value You can only configure the setpoint, process value and output value in the Inspector window of the programming editor. Select the source for each value: Instance DB The value saved in the instance DB is used. Value must be updated in the instance DB by the user program. There should be no value at the instruction. Change via HMI possible. Instruction The value connected to the instruction is used. The value is written to the instance DB each time the instruction is called. No change via HMI possible. Controller type Physical quantity Select the unit of measurement and physical quantity for the setpoint and process value in the "Controller type" group. The setpoint and process value will be displayed in this unit. Control logic An increase of the output value is generally intended to cause an increase in the process value. This is referred to as a normal control logic. 4262 WinCC Basic V13.0 System Manual, 02/2014 Using technology functions 11.1 PID control PID_Compact does not work with negative proportional gain. Select the check box "Invert control logic" to reduce the process value with a higher output value. Examples Opening the drain valve will reduce the level of a container's contents. Increasing cooling will reduce the temperature. Start-up behavior after reset To change straight to the last active mode after restarting the CPU, select the "Enable last mode after CPU restart" check box. PID_Compact will remain in "Inactive" mode if the check box is cleared. Setpoint Procedure Proceed as follows to define a fixed setpoint: 1. Select "Instance DB". 2. Enter a setpoint, e.g. 80 C. 3. Delete any entry in the instruction. Proceed as follows to define a variable setpoint: 1. Select "Instruction". 2. Enter the name of the REAL variable in which the setpoint is saved. Program-controlled assignment of various values to the REAL variable is possible, for example for the time controlled change of the setpoint. Process value PID_Compact will scale the value of the analog input to the physical quantity if you use the analog input value directly. You will need to write a program for processing if you wish first to process the analog input value. The process value is, for example, not directly proportional to the value at the analog input. The processed process value must be in floating point format. Procedure Proceed as follows to use the analog input value without processing: 1. Select the entry "Input_PER" in the drop-down list "Input". 2. Select "Instruction" as source. 3. Enter the address of the analog input. Proceed as follows to use the processed process value in floating point format: WinCC Basic V13.0 System Manual, 02/2014 4263 Using technology functions 11.1 PID control 1. Select the entry "Input" in the drop-down list "Input". 2. Select "Instruction" as source. 3. Enter the name of the variable in which the processed process value is saved. Output value PID_Compact offers three output values. Your actuator will determine which output value you use. Output_PER The actuator is triggered via an analog output and controlled with a continuous signal, e.g. 0...10V, 4...20mA. Output The output value needs to be processed by the user program, for example because of nonlinear actuator response. Output_PWM The actuator is controlled via a digital output. Pulse width modulation creates minimum ON and minimum OFF times. Procedure Proceed as follows to use the analog output value: 1. Select the entry "Output_PER (analog)" in the drop-down list "Output". 2. Select "Instruction". 3. Enter the address of the analog output. Proceed as follows to process the output value using the user program: 1. Select the entry "Output" in the drop-down list "Output". 2. Select "Instance DB". The calculated output value is saved in the instance data block. 3. For the preparation of the output value, use the output parameter Output. 4. Transfer the processed output value to the actuator via a digital or analog CPU output. Proceed as follows to use the digital output value: 1. Select the entry "Output_PWM" in the drop-down list "Output". 2. Select "Instruction". 3. Enter the address of the digital output. Process value settings Configure the scaling of your process value and specify the process value absolute limits In the "Process value settings" configuration window. 4264 WinCC Basic V13.0 System Manual, 02/2014 Using technology functions 11.1 PID control Scaling the process value If you have configured the use of Input_PER in the basic settings, you will need to convert the value of the analog input into the physical quantity of the process value. The current configuration will be displayed in the Input_PER display. Input_PER will be scaled using a low and high value pair if the process value is directly proportional to the value of the analog input. 1. Enter the low pair of values in the "Scaled low process value" and "Low" input fields. 2. Enter the high pair of values in the "Scaled high process value" and "High" input boxes. Default settings for the value pairs are saved in the hardware configuration. Proceed as follows to use the value pairs from the hardware configuration: 1. Select the instruction PID_Compact in the programming editor. 2. Connect Input_PER with an analog input in the basic settings. 3. Click on the "Automatic setting" button in the process value settings. The existing values will be overwritten with the values from the hardware configuration. Monitoring process value Specify the absolute high and low limit of the process value. As soon as these limits are violated during operation, the controller switches off and the output value is set to 0%. You must enter reasonable limits for your controlled system. Reasonable limits are important during optimization to obtain optimal PID parameters. The default for the "High limit process value" is 120 %. At the I/O input, the process value can be a maximum of 18% higher than the standard range (overrange). An error is no longer reported for a violation of the "High limit process value". Only a wire-break and a short-circuit are recognized and the PID_Compact switches to "Inactive" mode. WARNING If you set very high process value limits (for example -3.4*1038...+3.4*1038), process value monitoring will be disabled. Your system may then be damaged if an error occurs. See also Monitoring process value (Page 4266) PWM limits (Page 4266) Output value limits (Page 4268) PID parameters (Page 4269) WinCC Basic V13.0 System Manual, 02/2014 4265 Using technology functions 11.1 PID control Advanced settings Monitoring process value Configure a warning high and low limit for the process value in the "Process value monitoring" configuration window. If one of the warning limits is exceeded or undershot during operation, a warning will be displayed at the PID_Compact instruction: At the InputWarning_H output parameter if the warning high limit has been exceeded At the InputWarning_L output parameter if the warning low limit has been undershot The warning limits must be within the process value high and low limits. The process value high and low limits will be used if you do not enter values. Example Process value high limit = 98 C; warning high limit = 90 C Warning low limit = 10 C; process value low limit = 0 C PID_Compact will respond as follows: Process value InputWarning_H InputWarning_L Operating mode > 98 C TRUE FALSE Inactive 98 C and > 90 C TRUE FALSE Automatic mode 90 C and 10 C FALSE FALSE Automatic mode < 10 C and 0 C FALSE TRUE Automatic mode < 0 C FALSE TRUE Inactive See also Process value settings (Page 4264) PWM limits (Page 4266) Output value limits (Page 4268) PID parameters (Page 4269) PWM limits The value at the output parameter Output is transformed into a pulse sequence that is output at output parameter Output_PWM by means of a pulse width modulation. Output is calculated in the PID algorithm sampling time, Output_PWM is output in the PID_Compact sampling time. The PID algorithm sampling time is determined during pretuning or fine tuning. If manually setting the PID parameters, you will also need to configure the PID algorithm sampling time. The PID_Compact sampling time is equivalent to the cycle time of the calling OB. The pulse duration is proportional to the value at Output and is always an integer multiple of the PID_Compact sampling time. 4266 WinCC Basic V13.0 System Manual, 02/2014 Using technology functions 11.1 PID control 2XWSXW W PV 2XWSXWB3:0 758( )$/6( W PV PID_Compact sampling time PID algorithm sampling time Pulse duration Break time The "Minimum ON time" and the "Minimum OFF time" are rounded to an integer multiple of the PID_Compact sampling time. A pulse or a break is never shorter than the minimum ON or OFF time. The inaccuracies this causes are added up and compensated in the next cycle. Example PID_Compact sampling time = 100 ms PID algorithm sampling time = 1000 ms Minimum ON time = 200 ms Output is a constant 15%. The smallest pulse that PID_Compact can output is 20%. In the first cycle, no pulse is output. In the second cycle, the pulse not output in the first cycle is added to the pulse of the second cycle. WinCC Basic V13.0 System Manual, 02/2014 4267 Using technology functions 11.1 PID control 2XWSXW 2XWSXWB3:0 W PV 758( )$/6( W PV PID_Compact sampling time PID algorithm sampling time Minimum ON time In order to minimize operation frequency and conserve the actuator, extend the minimum ON and OFF times. If you are using "Output" or "Output_PER", you must configure the value 0.0 for the minimum ON and OFF times. Note The minimum ON and OFF times only affect the output parameter Output_PWM and are not used for any pulse generators integrated in the CPU. See also Process value settings (Page 4264) Monitoring process value (Page 4266) Output value limits (Page 4268) PID parameters (Page 4269) Output value limits In the "Output value limits" configuration window, configure the absolute limits of your output value in percent. Absolute output value limits are not violated in neither manual mode nor in automatic mode. If a output value outside the limits is specified in manual mode, the effective value is limited in the CPU to the configured limits. The valid output value limit values depend on the Output used. 4268 WinCC Basic V13.0 System Manual, 02/2014 Using technology functions 11.1 PID control Output -100.0 to 100.0 Output_PER -100.0 to 100.0 Output_PWM 0.0 to 100.0 PID_Compact sets the output value to 0.0 if an error occurs. 0.0 must therefore always be within the output value limits. You will need to add an offset to Output and Output_PER in the user program if you want an output value low limit of greater than 0.0. See also Process value settings (Page 4264) Monitoring process value (Page 4266) PWM limits (Page 4266) PID parameters (Page 4269) PID parameters The PID parameters are displayed in the "PID Parameters" configuration window. The PID parameters will be adapted to your controlled system during controller tuning. You do not need to enter the PID parameters manually. The PID algorithm operates according to the following equation: 1 y = Kp [ (b * w - x) + T * s (w - x) + I Symbol TD * s a * TD * s + 1 (c * w - x) ] Description y Output value of the PID algorithm Kp Proportional gain s Laplace operator b Proportional action weighting w Setpoint x Process value TI Integral action time a Derivative delay coefficient (derivative delay T1 = a x TD) TD Derivative action time c Derivative action weighting The diagram below illustrates the integration of the parameters into the PID algorithm: WinCC Basic V13.0 System Manual, 02/2014 4269 Using technology functions 11.1 PID control 6HWSRLQW Z E $QWL:LQGXS /,0,7 , .3 \ F 6FDOHG,QSXW [ '7 All PID parameters are retentive. If you enter the PID parameters manually, you must completely download PID_Compact. Auto-Hotspot Proportional gain The value specifies the proportional gain of the controller. PID_Compact does not work with a negative proportional gain. Control logic is inverted under Basic settings > Controller type. Integral action time The integral action time determines the time behavior of the integral action. The integral action is deactivated with integral action time = 0.0. Derivative action time The derivative action time determines the time behavior of the derivative action. Derivative action is deactivated with derivative action time = 0.0. Derivative delay coefficient The derivative delay coefficient delays the effect of the derivative action. Derivative delay = derivative action time x derivative delay coefficient 0.0: Derivative action is effective for one cycle only and therefore almost not effective. 0.5: This value has proved useful in practice for controlled systems with one dominant time constant. > 1.0: The greater the coefficient, the longer the effect of the derivative action is delayed. 4270 WinCC Basic V13.0 System Manual, 02/2014 Using technology functions 11.1 PID control Proportional action weighting The proportional action may weaken with changes to the setpoint. Values from 0.0 to 1.0 are applicable. 1.0: Proportional action for setpoint change is fully effective 0.0: Proportional action for setpoint change is not effective The proportional action is always fully effective when the process value is changed. Derivative action weighting The derivative action may weaken with changes to the setpoint. Values from 0.0 to 1.0 are applicable. 1.0: Derivative action is fully effective upon setpoint change 0.0: Derivative action is not effective upon setpoint change The derivative action is always fully effective when the process value is changed. PID algorithm sampling time The controlled system needs a certain amount of time to respond to changes in the output value. It is therefore not advisable to calculate the output value in every cycle. The sampling time of the PID algorithm represents the time between two calculations of the output value. It is calculated during tuning and rounded to a multiple of the cycle time. All other functions of PID_Compact are executed at every call. If you use Output_PWM, the accuracy of the output signal is determined by the ratio of the PID algorithm sampling time to the cycle time of the OB. The PID algorithm sampling time corresponds to the time period of the pulse width modulation. The cycle time should be at least 10 times the PID algorithm sampling time. Rule for tuning Select whether PI or PID parameters are to be calculated in the "Controller structure" dropdown list. PID Calculates PID parameters during pretuning and fine tuning. PI Calculates PI parameters during pretuning and fine tuning. User-defined The drop-down list displays "User-defined" if you have configured different controller structures for pretuning and fine tuning via a user program. See also Downloading technology objects to device (Page 4223) WinCC Basic V13.0 System Manual, 02/2014 4271 Using technology functions 11.1 PID control Commissioning PID_Compact V1 Commissioning The commissioning window helps you commission the PID controller. You can monitor the values for the setpoint, process value and output value along the time axis in the trend view. The following functions are supported in the commissioning window: Controller pretuning Controller fine tuning Use fine tuning for fine adjustments to the PID parameters. Monitoring the current closed-loop control in the trend view Testing the controlled system by specifying a manual output value All functions require an online connection to the CPU to have been established. Basic handling Select the desired sampling time in the "Sampling time" drop-down list. All values in the commissioning window are updated in the selected update time. Click the "Start" icon in the measuring group if you want to use the commissioning functions. Value recording is started. The current values for the setpoint, process value and output value are entered in the trend view. Operation of the commissioning window is enabled. Click the "Stop" icon if you want to end the commissioning functions. The values recorded in the trend view can continue to be analyzed. Closing the commissioning window will terminate recording in the trend view and delete the recorded values. See also Pretuning (Page 4272) Fine tuning (Page 4274) "Manual" mode (Page 4275) Pretuning The pretuning determines the process response to a jump change of the output value and searches for the point of inflection. The tuned PID parameters are calculated as a function of the maximum slope and dead time of the controlled system. The more stable the process value is, the easier it is to calculate the PID parameters and the more precise the result will be. Noise on the process value can be tolerated as long as the rate of rise of the process value is significantly higher compared to the noise. The PID parameters are backed up before being recalculated. 4272 WinCC Basic V13.0 System Manual, 02/2014 Using technology functions 11.1 PID control Requirement The "PID_Compact" instruction is called in a cyclic interrupt OB. ManualEnable = FALSE PID_Compact is in "inactive" or "manual" mode. The setpoint may not be changed during controller tuning. PID_Compact will otherwise be deactivated. The setpoint and the process value lie within the configured limits (see "Process value monitoring" configuration). The difference between setpoint and process value is greater than 30% of the difference between process value high limit and process value low limit. The distance between the setpoint and the process value is > 50% of the setpoint. Procedure To perform pretuning, follow these steps: 1. Double-click the "PID_Compact > Commissioning" entry in the project tree. 2. Select the entry "Pretuning" in the "Tuning mode" drop-down list. 3. Click the "Start" icon. - An online connection will be established. - Value recording is started. - Pretuning is started. - The "Status" field displays the current steps and any errors that may have occurred. The progress bar indicates the progress of the current step. Note Click the "Stop" icon when the progress bar has reached 100% and it is to be assumed the controller tuning function is blocked. Check the configuration of the technology object and, if necessary, restart controller tuning. Result If pretuning was performed without an error message, the PID parameters have been tuned. PID_Compact switches to automatic mode and uses the tuned parameters. The tuned PID parameters will be retained during power OFF and a restart of the CPU. If pretuning is not possible, PID_Compact will change to "Inactive" mode. See also Parameters State and sRet.i_Mode V1 (Page 2922) Commissioning (Page 4272) WinCC Basic V13.0 System Manual, 02/2014 4273 Using technology functions 11.1 PID control Fine tuning (Page 4274) "Manual" mode (Page 4275) Fine tuning Fine tuning generates a constant, limited oscillation of the process value. The PID parameters are optimized for the operating point from the amplitude and frequency of this oscillation. All PID parameters are recalculated on the basis of the findings. PID parameters from fine tuning usually have better master control and disturbance behavior than PID parameters from pretuning. PID_Compact automatically attempts to generate an oscillation greater than the noise of the process value. Fine tuning is only minimally influenced by the stability of the process value. The PID parameters are backed up before being recalculated. Requirement The PID_Compact instruction is called in a cyclic interrupt OB. ManualEnable = FALSE The setpoint and the process value lie within the configured limits (see "Process value monitoring" configuration). The control loop has stabilized at the operating point. The operating point is reached when the process value corresponds to the setpoint. No disturbances are expected. The setpoint may not be changed during controller tuning. PID_Compact is in inactive mode, automatic mode or manual mode. Process depends on initial situation Fine tuning can be started in "inactive", "automatic" or "manual" mode. Fine tuning proceeds as follows when started in: Automatic mode Start fine tuning in automatic mode if you wish to improve the existing PID parameters using controller tuning. PID_Comact will regulate using the existing PID parameters until the control loop has stabilized and the requirements for fine tuning have been met. Only then will fine tuning start. Inactive or manual mode If the requirements for pretuning are met, pretuning is started. The PID parameters established will be used for adjustment until the control loop has stabilized and the requirements for fine tuning have been met. Only then will fine tuning start. If pretuning is not possible, PID_Compact will change to "Inactive" mode. An attempt is made to reach the setpoint with a minimum or maximum output value if the process value for pretuning is already too near the setpoint. This can produce increased overshoot. 4274 WinCC Basic V13.0 System Manual, 02/2014 Using technology functions 11.1 PID control Procedure Proceed as follows to carry out "fine tuning": 1. Select the entry "Fine tuning" in the "Tuning mode" drop-down list. 2. Click the "Start" icon. - An online connection will be established. - Value recording is started. - The process of fine tuning is started. - The "Status" field displays the current steps and any errors that may have occurred. The progress bar indicates the progress of the current step. Note Click the "Stop" icon in the "Tuning mode" group when the progress bar has reached 100% and it is to be assumed the controller tuning function is blocked. Check the configuration of the technology object and, if necessary, restart controller tuning. Result The PID parameters will have been optimized if fine tuning has been executed without errors. PID_Compact changes to automatic mode and uses the optimized parameters. The optimized PID parameters will be retained during power OFF and a restart of the CPU. If errors occurred during "fine tuning", PID_Compact will change to "inactive" mode. See also Parameters State and sRet.i_Mode V1 (Page 2922) Commissioning (Page 4272) Pretuning (Page 4272) "Manual" mode (Page 4275) "Manual" mode The following section describes how you can use the "Manual" operating mode in the commissioning window of the "PID Compact" technology object. Requirement The "PID_Compact" instruction is called in a cyclic interrupt OB. An online connection to the CPU has been established and the CPU is in the "RUN" mode. The functions of the commissioning window have been enabled via the "Start" icon. WinCC Basic V13.0 System Manual, 02/2014 4275 Using technology functions 11.1 PID control Procedure Use "Manual mode" in the commissioning window if you want to test the process by specifying a manual value. To define a manual value, proceed as follows: 1. Select the check box "Manual mode" in the "Online status of the controller" area. PID_Compact operates in manual mode. The most recent current output value remains in effect. 2. Enter the manual value in the "Output" field as a % value. 3. Click the control icon . Result The manual value is written to the CPU and immediately goes into effect. Note PID_Compact continues to monitor the process value. If the process value limits are exceeded, PID_Compact is deactivated. Clear the "Manual mode" check box if the output value is to be specified again by the PID controller. The change to automatic mode is bumpless. See also Parameters State and sRet.i_Mode V1 (Page 2922) Commissioning (Page 4272) Pretuning (Page 4272) Fine tuning (Page 4274) 11.1.4 Using PID_3Step 11.1.4.1 Technology object PID_3Step The technology object PID_3Step provides a PID controller with tuning for valves or actuators with integral response. You can configure the following controllers: Three-point step controller with position feedback Three-point step controller without position feedback Valve controller with analog output value PID_3Step continuously acquires the measured process value within a control loop and compares it with the setpoint. From the resulting control deviation, PID_3Step calculates an output value through which the process value reaches the setpoint as quickly and steadily as possible. The output value for the PID controller consists of three actions: 4276 WinCC Basic V13.0 System Manual, 02/2014 Using technology functions 11.1 PID control P action The proportional action of the output value increases in proportion to the control deviation. I action The integral action of the output value increases until the control deviation has been balanced. D action The derivative action increases with the rate of change of control deviation. The process value is corrected to the setpoint as quickly as possible. The derivative action will be reduced again if the rate of change of control deviation drops. The instruction PID_3Step calculates the proportional, integral and derivative parameters for your controlled system during pretuning. Fine tuning can be used to tune the parameters further. You do not need to manually determine the parameters. Additional information Overview of software controller (Page 4218) Add technology objects (Page 4220) Configure technology objects (Page 4221) Configuring PID_3Step V2 (Page 4277) Configuring PID_3Step V1 (Page 4294) 11.1.4.2 PID_3Step V2 Configuring PID_3Step V2 Basic settings Introduction Configure the following properties of the "PID_3Step" technology object under "Basic settings" in the Inspector window or in the configuration window: Physical quantity Control logic Start-up behavior after reset Setpoint (only in the Inspector window) Process value (only in the Inspector window) Output value (only in the Inspector window) Position feedback (only in the Inspector window) WinCC Basic V13.0 System Manual, 02/2014 4277 Using technology functions 11.1 PID control Setpoint, process value, output value and position feedback You can only configure the setpoint, process value, output value and position feedback in the Inspector window of the programming editor. Select the source for each value: Instance DB The value saved in the instance DB is used. Value must be updated in the instance DB by the user program. There should be no value at the instruction. Change via HMI possible. Instruction The value connected to the instruction is used. The value is written to the instance DB each time the instruction is called. No change via HMI possible. Controller type Physical quantity Select the physical quantity and unit of measurement for setpoint, process value, and disturbance variable in the "Controller type" group. Setpoint, process value, and disturbance variable is displayed in this unit of measurement. Control logic An increase of the output value is generally intended to cause an increase in the process value. This is referred to as a normal control logic. PID_3Step does not work with negative proportional gain. Select the check box "Invert control logic" to reduce the process value with a higher output value. Examples Opening the drain valve will reduce the level of a container's contents. Increasing cooling will reduce the temperature. Startup characteristics 1. To switch to "Inactive" mode after CPU restart, clear the "Activate Mode after CPU restart" check box. To switch to the operating mode saved in the Mode parameter after CPU restart, select the "Activate Mode after CPU restart" check box. 2. In the "Set Mode to" drop-down list, select the mode that is to be enabled after a complete download to the device. After a complete download to the device, PID_3Step starts in the selected operating mode. With each additional restart, PID_3Step starts in the mode that was last saved in Mode. Example You have selected the "Activate Mode after CPU restart" check box and the entry "Pretuning" in the "Set Mode to" list. After a complete download to the device, PID_3Step starts in the "Pretuning" mode. If pretuning is still active, PID_3Step starts in "Pretuning" mode again after 4278 WinCC Basic V13.0 System Manual, 02/2014 Using technology functions 11.1 PID control restart of the CPU. If pretuning was successfully completed and automatic mode is active, PID_3Step starts in "Automatic mode" after restart of the CPU. Setpoint Procedure Proceed as follows to define a fixed setpoint: 1. Select "Instance DB". 2. Enter a setpoint, e.g. 80 C. 3. Delete any entry in the instruction. Proceed as follows to define a variable setpoint: 1. Select "Instruction". 2. Enter the name of the REAL variable in which the setpoint is saved. Program-controlled assignment of various values to the REAL variable is possible, for example for the time controlled change of the setpoint. Process value PID_3Step will scale the value of the analog input to the physical quantity if you use the analog input value directly. You will need to write a program for processing if you wish first to process the analog input value. The process value is, for example, not directly proportional to the value at the analog input. The processed process value must be in floating point format. Procedure Proceed as follows to use the analog input value without processing: 1. Select the entry "Input_PER" in the drop-down list "Input". 2. Select "Instruction" as source. 3. Enter the address of the analog input. Proceed as follows to use the processed process value in floating point format: 1. Select the entry "Input" in the drop-down list "Input". 2. Select "Instruction" as source. 3. Enter the name of the variable in which the processed process value is saved. Position feedback Position feedback configuration depends upon the actuator used. Actuator without position feedback Actuator with digital endstop signals WinCC Basic V13.0 System Manual, 02/2014 4279 Using technology functions 11.1 PID control Actuator with analog position feedback Actuator with analog position feedback and endstop signals Actuator without position feedback Proceed as follows to configure PID_3Step for an actuator without position feedback: 1. Select the entry "No Feedback" in the drop-down list "Feedback". Actuator with digital endstop signals Proceed as follows to configure PID_3Step for an actuator with endstop signals: 1. Select the entry "No Feedback" in the drop-down list "Feedback". 2. Activate the "Actuator endstop signals" check box. 3. Select "Instruction" as source for Actuator_H and Actuator_L. 4. Enter the addresses of the digital inputs for Actuator_H and Actuator_L. Actuator with analog position feedback Proceed as follows to configure PID_3Step for an actuator with analog position feedback: 1. Select the entry "Feedback" or "Feedback_PER" in the drop-down list "Feedback". - Use the analog input value for Feedback_PER. Configure Feedback_PER scaling in the actuator settings. - Process the analog input value for Feedback using your user program. 2. Select "Instruction" as source. 3. Enter the address of the analog input or the variable of your user program. Actuator with analog position feedback and endstop signals Proceed as follows to configure PID_3Step for an actuator with analog position feedback and endstop signals: 1. Select the entry "Feedback" or "Feedback_PER" in the drop-down list "Feedback". 2. Select "Instruction" as source. 3. Enter the address of the analog input or the variable of your user program. 4. Activate the "Actuator endstop signals" check box. 5. Select "Instruction" as source for Actuator_H and Actuator_L. 6. Enter the addresses of the digital inputs for Actuator_H and Actuator_L. 4280 WinCC Basic V13.0 System Manual, 02/2014 Using technology functions 11.1 PID control Output value PID_3Step offers an analog output value (Output_PER) and digital output values (Output_UP, Output_DN). Your actuator will determine which output value you use. Output_PER The actuator is triggered via an analog output and controlled with a continuous signal, e.g. 0...10V, 4...20mA. Output_UP, Output_DN The actuator is controlled via two digital outputs. Procedure Proceed as follows to use the analog output value: 1. Select the entry "Output (analog)" in the drop-down list "Output". 2. Select "Instruction". 3. Enter the address of the analog output. Proceed as follows to use the digital output value: 1. Select the entry "Output (digital)" in the drop-down list "Output". 2. Select "Instruction" for Output_UP and Output_DN. 3. Enter the addresses of the digital outputs. Proceed as follows to process the output value using the user program: 1. Select the entry corresponding to the actuator in the drop-down list "Output". 2. Select "Instruction". 3. Enter the name of the variable you are using to process the output value. 4. Transfer the processed output value to the actuator by means of an analog or digital CPU output. Process value settings Scaling the process value If you have configured the use of Input_PER in the basic setting, you must convert the value of the analog input to the physical quantity of the process value. The current configuration is displayed in the Input_PER display. Input_PER will be scaled using a low and high value pair if the process value is directly proportional to the value of the analog input. Procedure To scale the process value, follow these steps: 1. Enter the low pair of values in the "Scaled low process value" and "Low" text boxs. 2. Enter the high pair of values in the "Scaled high process value" and "High" input boxes. WinCC Basic V13.0 System Manual, 02/2014 4281 Using technology functions 11.1 PID control Default settings for the value pairs are stored in the hardware configuration. To use the value pairs from the hardware configuration, follow these steps: 1. Select the PID_3Step instruction in the programming editor. 2. Interconnect Input_PER with an analog input in the basic settings. 3. Click the "Automatic setting" button in the process value settings. The existing values will be overwritten with the values from the hardware configuration. Process value limits You must specify an appropriate absolute high limit and low limit for the process value as limit values for your controlled system. As soon as the process value violates these limits, an error occurs (ErrorBits = 0001h). Tuning is canceled when the process value limits are violated. You can specify how PID_3Step responds to errors in automatic mode in the actuator settings. Actuator settings Actuator Actuator-specific times Configure the motor transition time and the minimum ON and OFF times to prevent damage to the actuator. You can find the specifications in the actuator data sheet. The motor transition time is the time in seconds the motor requires to move the actuator from the closed to the opened state. You can measure the motor transition time during commissioning. The motor transition time is retentive. If you enter the motor transition time manually, you must completely download PID_3Step. Downloading technology objects to device (Page 4223) If you are using "Output_UP" or "Output_DN", you can reduce the switching frequency with the minimum on and minimum OFF time. The on or off times calculated are totaled in automatic mode and only become effective when the sum is greater than or equal to the minimum on or OFF time. Manual_UP = TRUE or Manual_DN = TRUE in manual mode operates the actuator for at least the minimum ON or OFF time. Reaction to error PID_3Step is preset so that the controller stays active in most cases in the event of an error. If errors occur frequently in controller mode, this default reaction has a negative effect on the 4282 WinCC Basic V13.0 System Manual, 02/2014 Using technology functions 11.1 PID control control response. In this case, check the Errorbits parameter and eliminate the cause of the error. NOTICE Your system may be damaged. If you output "Current value while error pending" or "Substitute output value while error pending" in the event of an error, PID_3Step remains in automatic mode even if the process value limits are violated. This may damage your system. It is essential to configure how your controlled system reacts in the event of an error to protect your system from damage. PID_3Step generates a programmable output value in response to an error: Current value PID_3Step is switched off and no longer modifies the actuator position. Current value for error while error is pending The controller functions of PID_3Step are switched off and the position of the actuator is no longer changed. If the following errors occur in automatic mode, PID_3Step returns to automatic mode as soon as the errors are no longer pending. - 0002h: Invalid value at Input_PER parameter. - 0200h: Invalid value at Input parameter. - 0400h: Calculation of output value failed. - 1000h: Invalid value at Setpoint parameter. - 2000h: Invalid value at Feedback_PER parameter. - 4000h: Invalid value at Feedback parameter. - 8000h: Error during digital position feedback. - 20000h: Invalid value at SavePosition tag. If one or more of the following errors occur, PID_3Step stays in automatic mode: - 0001h: The Input parameter is outside the process value limits. - 0800h: Sampling time error - 40000h: Invalid value at Disturbance parameter. PID_3Step remains in manual mode if an error occurs in manual mode. If an error occurs during tuning or transition time measurement, PID_3Step switches to the mode in which tuning or transition time measurement was started. Only in the event of the following error is tuning not aborted: - 0020h: Pretuning is not permitted during fine tuning. WinCC Basic V13.0 System Manual, 02/2014 4283 Using technology functions 11.1 PID control Substitute output value PID_3Step moves the actuator to the substitute output value and then switches off. Substitute output value while error is pending PID_3Step moves the actuator to the substitute output value. When the substitute output value is reached, PID_3Step reacts as it does with "Current value for while error is pending". Enter the substitute output value in "%". Only substitute output values 0% and 100% can be approached precisely in the case of actuators without analog position feedback. A substitute output value not equal to 0% or 100% is approached via an internally simulated position feedback. This procedure does not, however, allow the exact approach of substitute output value. All substitute output values can be approached precisely with actuators with analog position feedback. Scaling position feedback Scaling position feedback If you have configured the use of Feedback_PER in the basic settings, you will need to convert the value of the analog input into %. The current configuration will be displayed in the "Feedback" display. Feedback_PER is scaled using a low and high value pair. 1. Enter the low pair of values in the "Low endstop" and "Low" input boxes. 2. Enter the high pair of values in the "High endstop" and "High" input boxes. "Low endstop" must be less than "High endstop"; "Low" must be less than "High". The valid values for "High endstop" and "Low endstop" depend upon: No Feedback, Feedback, Feedback_PER Output (analog), Output (digital) Output Feedback Low endstop High endstop Output (digital) No Feedback Cannot be set (0.0%) Cannot be set (100.0%) Output (digital) Feedback -100.0% or 0.0% 0.0% or +100.0% Output (digital) Feedback_PER -100.0% or 0.0% 0.0% or +100.0% Output (analog) No Feedback Cannot be set (0.0%) Cannot be set (100.0%) Output (analog) Feedback -100.0% or 0.0% 0.0% or +100.0% Output (analog) Feedback_PER -100.0% or 0.0% 0.0% or +100.0% Output value limits Limiting the output value You can exceed or undershoot the output value limits during the transition time measurement and with mode = 10. The output value is limited to these values in all other modes. 4284 WinCC Basic V13.0 System Manual, 02/2014 Using technology functions 11.1 PID control Enter the absolute output value limits in the "Output value high limit" and "Output value low limit" input boxes. The output value limits must be within "Low endstop" and "High endstop". If no Feedback is available and Output (digital) is set, you cannot limit the output value. Output_UP and Output_DN are then reset upon Actuator_H = TRUE or Actuator_L = TRUE. If no endstop signals are available, Output_UP and Output_DN are reset after a travel time of 150% of the motor actuating time. Advanced settings Monitoring process value Configure a warning high and low limit for the process value in the "Process value monitoring" configuration window. If one of the warning limits is exceeded or undershot during operation, a warning will be displayed at the PID_3Step instruction: At the InputWarning_H output parameter if the warning high limit has been exceeded At the InputWarning_L output parameter if the warning low limit has been undershot The warning limits must be within the process value high and low limits. The process value high and low limits will be used if you do not enter values. Example Process value high limit = 98 C; warning high limit = 90 C Warning low limit = 10 C; process value low limit = 0 C PID_3Step will respond as follows: Process value InputWarnin g_H InputWarnin g_L ErrorBi Operating mode ts > 98 C TRUE FALSE 0001h As configured 98 C and > 90 C TRUE FALSE 0000h Automatic mode 90 C and 10 C FALSE FALSE 0000h Automatic mode < 10 C and 0 C FALSE TRUE 0000h Automatic mode < 0 C FALSE TRUE 0001h As configured In the actuator settings, you can configure the response of PID_3Step when the process value high limit or low limit is violated. PID parameters The PID parameters are displayed in the "PID Parameters" configuration window. The PID parameters will be adapted to your controlled system during controller tuning. You do not need to enter the PID parameters manually. The PID algorithm operates according to the following equation: WinCC Basic V13.0 System Manual, 02/2014 4285 Using technology functions 11.1 PID control 1 [ y = K p * s * (b * w - x) + TI * s (w - x) + TD * s a * TD * s + 1 (c * w - x) Symbol Description y Output value of the PID algorithm Kp Proportional gain s Laplace operator b Proportional action weighting w Setpoint x Process value TI Integral action time a Derivative delay coefficient (derivative delay T1 = a x TD) TD Derivative action time c Derivative action weighting ] The diagram below illustrates the integration of the parameters into the PID algorithm: E 6HWSRLQW Z ' . 3 \ 'HDGB% '7 F 7L , 6FDOHG,QSXW [ )DF7W $QWL:LQGXS All PID parameters are retentive. If you enter the PID parameters manually, you must completely download PID_3Step. Downloading technology objects to device (Page 4223) Proportional gain The value specifies the proportional gain of the controller. PID_3Step does not work with a negative proportional gain. Control logic is inverted under Basic settings > Controller type. 4286 WinCC Basic V13.0 System Manual, 02/2014 Using technology functions 11.1 PID control Integral action time The integral action time determines the time behavior of the integral action. The integral action is deactivated with integral action time = 0.0. Derivative action time The derivative action time determines the time behavior of the derivative action. Derivative action is deactivated with derivative action time = 0.0. Derivative delay coefficient The derivative delay coefficient delays the effect of the derivative action. Derivative delay = derivative action time x derivative delay coefficient 0.0: Derivative action is effective for one cycle only and therefore almost not effective. 0.5: This value has proved useful in practice for controlled systems with one dominant time constant. > 1.0: The greater the coefficient, the longer the effect of the derivative action is delayed. Proportional action weighting The proportional action may weaken with changes to the setpoint. Values from 0.0 to 1.0 are applicable. 1.0: Proportional action for setpoint change is fully effective 0.0: Proportional action for setpoint change is not effective The proportional action is always fully effective when the process value is changed. Derivative action weighting The derivative action may weaken with changes to the setpoint. Values from 0.0 to 1.0 are applicable. 1.0: Derivative action is fully effective upon setpoint change 0.0: Derivative action is not effective upon setpoint change The derivative action is always fully effective when the process value is changed. PID algorithm sampling time The controlled system needs a certain amount of time to respond to changes in the output value. It is therefore not advisable to calculate the output value in every cycle. The sampling time of the PID algorithm represents the time between two calculations of the output value. It is calculated during tuning and rounded to a multiple of the PID_3Step sampling time. All other functions of PID_3Step are executed at every call. WinCC Basic V13.0 System Manual, 02/2014 4287 Using technology functions 11.1 PID control Deadband width The deadband suppresses the noise component in the steady controller state. The deadband width specifies the size of the deadband. The deadband is off if the deadband width is 0.0. Commissioning PID_3Step V2 Pretuning The pretuning determines the process response to a pulse of the output value and searches for the point of inflection. The tuned PID parameters are calculated as a function of the maximum slope and dead time of the controlled system. You obtain the best PID parameters when you perform pretuning and fine tuning. The more stable the process value is, the easier it is to calculate the PID parameters and the more precise the result will be. Noise on the process value can be tolerated as long as the rate of rise of the process value is significantly higher compared to the noise. This is most likely the case in operating modes "Inactive" and "manual mode". The PID parameters are backed up before being recalculated. The setpoint is frozen during pretuning. Requirement The PID_3Step instruction is called in a cyclic interrupt OB. ManualEnable = FALSE Reset = FALSE The motor transition time has been configured or measured. PID_3Step is in one of the following modes: "Inactive", "Manual mode", or "Automatic mode". The setpoint and the process value lie within the configured limits (see "Process value settings" configuration). 4288 WinCC Basic V13.0 System Manual, 02/2014 Using technology functions 11.1 PID control Procedure To perform pretuning, follow these steps: 1. Double-click the "PID_3Step > Commissioning" entry in the project tree. 2. Select the entry "Pretuning" in the "Tuning mode" drop-down list in the working area "Tuning". 3. Click the "Start" icon. - An online connection will be established. - Value recording is started. - Pretuning is started. - The "Status" field displays the current steps and any errors that may have occurred. The progress bar indicates the progress of the current step. Note Click the "Stop" icon when the progress bar has reached 100% and it is to be assumed the controller tuning function is blocked. Check the configuration of the technology object and, if necessary, restart controller tuning. Result If pretuning was performed without an error message, the PID parameters have been tuned. PID_3Step switches to automatic mode and uses the tuned parameters. The tuned PID parameters will be retained during power OFF and a restart of the CPU. If pretuning is not possible, PID_3Step responds with the configured reaction to errors. Fine tuning Fine tuning generates a constant, limited oscillation of the process value. The PID parameters are tuned for the operating point from the amplitude and frequency of this oscillation. All PID parameters are recalculated from the results. PID parameters from fine tuning usually have better master control and disturbance characteristics than PID parameters from pretuning. You obtain the best PID parameters when you perform pretuning and fine tuning. PID_3Step automatically attempts to generate an oscillation greater than the noise of the process value. Fine tuning is only minimally influenced by the stability of the process value. The PID parameters are backed up before being recalculated. The setpoint is frozen during fine tuning. Requirement The PID_3Step instruction is called in a cyclic interrupt OB. ManualEnable = FALSE Reset = FALSE The motor transition time has been configured or measured. WinCC Basic V13.0 System Manual, 02/2014 4289 Using technology functions 11.1 PID control The setpoint and the process value lie within the configured limits (see "Process value settings" configuration). The control loop has stabilized at the operating point. The operating point is reached when the process value corresponds to the setpoint. No disturbances are expected. PID_3Step is in inactive mode, automatic mode or manual mode. Process depends on initial situation Fine tuning proceeds as follows when started from: Automatic mode Start fine tuning from automatic mode if you wish to improve the existing PID parameters through tuning. PID_3Step controls the system using the existing PID parameters until the control loop has stabilized and the requirements for fine tuning have been met. Only then will fine tuning start. Inactive or manual mode Pretuning is always started first. The determined PID parameters will be used for control until the control loop has stabilized and the requirements for fine tuning have been met. Only then will fine tuning start. Procedure To perform fine tuning, follow these steps: 1. Select the entry "Fine tuning" in the "Tuning mode" drop-down list. 2. Click the "Start" icon. - An online connection will be established. - Value recording is started. - The process of fine tuning is started. - The "Status" field displays the current steps and any errors that may have occurred. The progress bar indicates the progress of the current step. Note Click the "Stop" icon in the "Tuning mode" group when the progress bar has reached 100% and it is to be assumed the controller tuning function is blocked. Check the configuration of the technology object and, if necessary, restart controller tuning. Result If no errors occurred during fine tuning, the PID parameters have been tuned. PID_3Step switches to automatic mode and uses the tuned parameters. The tuned PID parameters will be retained during power OFF and a restart of the CPU. 4290 WinCC Basic V13.0 System Manual, 02/2014 Using technology functions 11.1 PID control If errors occurred during fine tuning, PID_3Step responds with the configured response to errors. Commissioning with manual PID parameters Requirement The PID_3Step instruction is called in a cyclic interrupt OB. ManualEnable = FALSE Reset = FALSE The motor transition time has been configured or measured. PID_3Step is in "inactive" mode. The setpoint and the process value lie within the configured limits (see "Process value settings" configuration). Procedure Proceed as follows to commission PID_3Step with manual PID parameters: 1. Double-click on "PID_3Step > Configuration" in the project tree. 2. Click on "Advanced settings > PID Parameters" in the configuration window. 3. Select the check box "Enable direct input". 4. Enter the PID parameters. 5. Double-click the "PID_3Step > Commissioning" entry in the project tree. 6. Establish an online connection to the CPU. 7. Load the PID parameters to the CPU. 8. Click the "Start PID_3Step" icon. Result PID_3Step changes to automatic mode and controls using the current PID parameters. See also PID parameters (Page 4285) WinCC Basic V13.0 System Manual, 02/2014 4291 Using technology functions 11.1 PID control Measuring the motor transition time Introduction PID_3Step requires the motor transition time to be as accurate as possible for good controller results. The data in the actuator documentation contains average values for this type of actuator. The value for the specific actuator used may differ. You can measure the motor transition time during commissioning if you are using actuators with position feedback or endstop signals. The output value limits are not taken into consideration during the motor transition time measurement. The actuator can travel to the high or the low endstop. The motor transition time cannot be measured if neither position feedback nor endstop signals are available. Actuators with analog position feedback Proceed as follows to measure motor transition time with position feedback: Requirement Feedback or Feedback_PER has been selected in the basic settings and the signal has been connected. An online connection to the CPU has been established. 1. Select the "Use position feedback" check box. 2. Enter the position to which the actuator is to be moved in the "Target position" input field. The current position feedback (starting position) will be displayed. The difference between "Target position" and "Position feedback" must be at least 50% of the valid output value range. 3. Click the "Start" icon. Result The actuator is moved from the starting position to the target position. Time measurement starts immediately and ends when the actuator reaches the target position. The motor transition time is calculated according to the following equation: Motor transition time = (output value high limit - output value low limit) x Measuring time / AMOUNT (target position - starting position). The progress and status of transition time measurement are displayed. The transition time measured is saved in the instance data block on the CPU and displayed in the "Measured transition time" field. When the transition time measurement is ended and ActivateRecoverMode = TRUE, PID_3Step switches to the operating mode from which the 4292 WinCC Basic V13.0 System Manual, 02/2014 Using technology functions 11.1 PID control transition time measurement was started. If the transition time measurement is ended and ActivateRecoverMode = FALSE, PID_3Step changes to "Inactive" mode. Note Click on the icon "Upload measured transition time" to load the motor transition time measured to the project. Actuators with endstop signals Proceed as follows to measure the transition time of actuators with endstop signals: Requirement The "Endstop signals" check box in the basic settings has been selected and Actuator_H and Actuator_L are connected. An online connection to the CPU has been established. Proceed as follows to measure motor transition time with endstop signals: 1. Select the "Use actuator endstop signals" check box. 2. Select the direction in which the actuator is to be moved. - Open - Close - Open The actuator is moved first to the high endstop, then to the low endstop and then back to the high endstop. - Close - Open - Close The actuator is moved first to the low endstop, then to the high endstop and then back to the low endstop. 3. Click the "Start" icon. Result The actuator is moved in the selected direction. Time measurement will start once the actuator has reached the first endstop and will end when the actuator reaches this endstop for the second time. The motor transition time is equal to the time measured divided by two. The progress and status of transition time measurement are displayed. The transition time measured is saved in the instance data block on the CPU and displayed in the "Measured transition time" field. When the transition time measurement is ended and ActivateRecoverMode = TRUE, PID_3Step switches to the operating mode from which the transition time measurement was started. If the transition time measurement is ended and ActivateRecoverMode = FALSE, PID_3Step changes to "Inactive" mode. Cancelling transition time measurement PID_3Step switches to "Inactive" mode if you cancel transition time measurement by pressing the Stop button. WinCC Basic V13.0 System Manual, 02/2014 4293 Using technology functions 11.1 PID control 11.1.4.3 PID_3Step V1 Configuring PID_3Step V1 Basic settings Introduction Configure the following properties of the "PID_3Step" technology object under "Basic settings" in the Inspector window or in the configuration window: Physical quantity Control logic Start-up behavior after reset Setpoint (only in the Inspector window) Process value (only in the Inspector window) Output value (only in the Inspector window) Position feedback (only in the Inspector window) Setpoint, process value, output value and position feedback You can only configure the setpoint, process value, output value and position feedback in the Inspector window of the programming editor. Select the source for each value: Instance DB The value saved in the instance DB is used. Value must be updated in the instance DB by the user program. There should be no value at the instruction. Change via HMI possible. Instruction The value connected to the instruction is used. The value is written to the instance DB each time the instruction is called. No change via HMI possible. Controller type Physical quantity Select the unit of measurement and physical quantity for the setpoint and process value in the "Controller type" group. The setpoint and process value will be displayed in this unit. Control logic An increase of the output value is generally intended to cause an increase in the process value. This is referred to as a normal control logic. 4294 WinCC Basic V13.0 System Manual, 02/2014 Using technology functions 11.1 PID control PID_3Step does not work with negative proportional gain. Select the check box "Invert control logic" to reduce the process value with a higher output value. Examples Opening the drain valve will reduce the level of a container's contents. Increasing cooling will reduce the temperature. Start-up behavior after reset To change straight to the last active mode after restarting the CPU, select the "Enable last mode after CPU restart" check box. PID_3Step will remain in "Inactive" mode if the check box is cleared. Setpoint Procedure Proceed as follows to define a fixed setpoint: 1. Select "Instance DB". 2. Enter a setpoint, e.g. 80 C. 3. Delete any entry in the instruction. Proceed as follows to define a variable setpoint: 1. Select "Instruction". 2. Enter the name of the REAL variable in which the setpoint is saved. Program-controlled assignment of various values to the REAL variable is possible, for example for the time controlled change of the setpoint. Process value PID_3Step will scale the value of the analog input to the physical quantity if you use the analog input value directly. You will need to write a program for processing if you wish first to process the analog input value. The process value is, for example, not directly proportional to the value at the analog input. The processed process value must be in floating point format. Procedure Proceed as follows to use the analog input value without processing: 1. Select the entry "Input_PER" in the drop-down list "Input". 2. Select "Instruction" as source. 3. Enter the address of the analog input. Proceed as follows to use the processed process value in floating point format: WinCC Basic V13.0 System Manual, 02/2014 4295 Using technology functions 11.1 PID control 1. Select the entry "Input" in the drop-down list "Input". 2. Select "Instruction" as source. 3. Enter the name of the variable in which the processed process value is saved. Position feedback Position feedback configuration depends upon the actuator used. Actuator without position feedback Actuator with digital endstop signals Actuator with analog position feedback Actuator with analog position feedback and endstop signals Actuator without position feedback Proceed as follows to configure PID_3Step for an actuator without position feedback: 1. Select the entry "No Feedback" in the drop-down list "Feedback". Actuator with digital endstop signals Proceed as follows to configure PID_3Step for an actuator with endstop signals: 1. Select the entry "No Feedback" in the drop-down list "Feedback". 2. Activate the "Actuator endstop signals" check box. 3. Select "Instruction" as source for Actuator_H and Actuator_L. 4. Enter the addresses of the digital inputs for Actuator_H and Actuator_L. Actuator with analog position feedback Proceed as follows to configure PID_3Step for an actuator with analog position feedback: 1. Select the entry "Feedback" or "Feedback_PER" in the drop-down list "Feedback". - Use the analog input value for Feedback_PER. Configure Feedback_PER scaling in the actuator settings. - Process the analog input value for Feedback using your user program. 2. Select "Instruction" as source. 3. Enter the address of the analog input or the variable of your user program. Actuator with analog position feedback and endstop signals Proceed as follows to configure PID_3Step for an actuator with analog position feedback and endstop signals: 1. Select the entry "Feedback" or "Feedback_PER" in the drop-down list "Feedback". 2. Select "Instruction" as source. 4296 WinCC Basic V13.0 System Manual, 02/2014 Using technology functions 11.1 PID control 3. Enter the address of the analog input or the variable of your user program. 4. Activate the "Actuator endstop signals" check box. 5. Select "Instruction" as source for Actuator_H and Actuator_L. 6. Enter the addresses of the digital inputs for Actuator_H and Actuator_L. Output value PID_3Step offers an analog output value (Output_PER) and digital output values (Output_UP, Output_DN). Your actuator will determine which output value you use. Output_PER The actuator is triggered via an analog output and controlled with a continuous signal, e.g. 0...10V, 4...20mA. Output_UP, Output_DN The actuator is controlled via two digital outputs. Procedure Proceed as follows to use the analog output value: 1. Select the entry "Output (analog)" in the drop-down list "Output". 2. Select "Instruction". 3. Enter the address of the analog output. Proceed as follows to use the digital output value: 1. Select the entry "Output (digital)" in the drop-down list "Output". 2. Select "Instruction" for Output_UP and Output_DN. 3. Enter the addresses of the digital outputs. Proceed as follows to process the output value using the user program: 1. Select the entry corresponding to the actuator in the drop-down list "Output". 2. Select "Instruction". 3. Enter the name of the variable you are using to process the output value. 4. Transfer the processed output value to the actuator by means of an analog or digital CPU output. Process value settings Configure the scaling of your process value and specify the process value absolute limits In the "Process value settings" configuration window. Scaling the process value If you have configured the use of Input_PER in the basic settings, you will need to convert the value of the analog input into the physical quantity of the process value. The current configuration will be displayed in the Input_PER display. WinCC Basic V13.0 System Manual, 02/2014 4297 Using technology functions 11.1 PID control Input_PER will be scaled using a low and high value pair if the process value is directly proportional to the value of the analog input. 1. Enter the low pair of values in the "Scaled low process value" and "Low" input fields. 2. Enter the high pair of values in the "Scaled high process value" and "High" input boxes. Default settings for the value pairs are saved in the hardware configuration. Proceed as follows to use the value pairs from the hardware configuration: 1. Select the instruction PID_3Step in the programming editor. 2. Connect Input_PER to an analog input in the basic settings. 3. Click on the "Automatic setting" button in the process value settings. The existing values will be overwritten with the values from the hardware configuration. Monitoring process value Specify the absolute high and low limit of the process value. You must enter reasonable limits for your controlled system. Reasonable limits are important during optimization to obtain optimal PID parameters. The default for the "High limit process value" is 120 %. At the I/O input, the process value can be a maximum of 18% higher than the standard range (overrange). This setting ensures that an error is no longer signaled due to a violation of the "Process value high limit". Only a wire-break and a short-circuit are recognized and PID_3Step reacts according to the configured reaction to error. NOTICE Your system may be damaged. If you set very high process value limits (for example -3.4*1038...+3.4*1038), process value monitoring will be disabled. Your system may then be damaged if an error occurs. You need to configure useful process value limits for your controlled system. Actuator settings Actuator-specific times Configure the motor transition time and the minimum ON and OFF times to prevent damage to the actuator. You can find the specifications in the actuator data sheet. The motor transition time is the time in seconds the motor requires to move the actuator from the closed to the opened state. The maximum time that the actuator is moved in one direction is 110% of the motor transition time. You can measure the motor transition time during commissioning. If you are using "Output_UP" or "Output_DN", you can reduce the switching frequency with the minimum on and minimum OFF time. The on or off times calculated are totaled in automatic mode and only become effective when the sum is greater than or equal to the minimum on or OFF time. A rising edge at Manual_UP or Manual_DN in manual mode will operate the actuator for at least the minimum on or OFF time. 4298 WinCC Basic V13.0 System Manual, 02/2014 Using technology functions 11.1 PID control Reaction to error PID_3Step is preset so that the controller stays active in most cases in the event of an error. If errors occur frequently in controller mode, this default reaction has a negative effect on the control response. In this case, check the Errorbits parameter and eliminate the cause of the error. PID_3Step generates a programmable output value in response to an error: Current value PID_3Step is switched off and no longer modifies the actuator position. Current value for error while error is pending The controller functions of PID_3Step are switched off and the position of the actuator is no longer changed. If the following errors occur in automatic mode, PID_3Step returns to automatic mode as soon as the errors are no longer pending. - 0002h: Invalid value at Input_PER parameter. - 0200h: Invalid value at Input parameter. - 0800h: Sampling time error - 1000h: Invalid value at Setpoint parameter. - 2000h: Invalid value at Feedback_PER parameter. - 4000h: Invalid value at Feedback parameter. - 8000h: Error during digital position feedback. If one of these error occurs in manual mode, PID_3Step remains in manual mode. If an error occurs during the tuning or transition time measurement, PID_3Step is switched off. Substitute output value PID_3Step moves the actuator to the substitute output value and then switches off. Substitute output value while error is pending PID_3Step moves the actuator to the substitute output value. When the substitute output value is reached, PID_3Step reacts as it does with "Current value for while error is pending". Enter the substitute output value in "%". Only substitute output values 0% and 100% can be approached precisely in the case of actuators without analog position feedback. The actuator is moved in one direction at 110% of the motor transition time to ensure the high or low endstop is reached. There endstop signals take priority. A substitute output value not equal to 0% or 100% is approached via an internally simulated position feedback. This procedure does not, however, allow the exact approach of substitute output value. All substitute output values can be approached precisely with actuators with analog position feedback. Scaling position feedback If you have configured the use of Feedback_PER in the basic settings, you will need to convert the value of the analog input into %. The current configuration will be displayed in the "Feedback" display. WinCC Basic V13.0 System Manual, 02/2014 4299 Using technology functions 11.1 PID control Feedback_PER is scaled using a low and high value pair. 1. Enter the low pair of values in the "Low endstop" and "Low" input boxes. 2. Enter the high pair of values in the "High endstop" and "High" input boxes. "Low endstop" must be less than "High endstop"; "Low" must be less than "High". The valid values for "High endstop" and "Low endstop" depend upon: No Feedback, Feedback, Feedback_PER Output (analog), Output (digital) Output Feedback Low endstop High endstop Output (digital) No Feedback Cannot be set (0.0%) Cannot be set (100.0%) Output (digital) Feedback -100.0% or 0.0% 0.0% or +100.0% Output (digital) Feedback_PER -100.0% or 0.0% 0.0% or +100.0% Output (analog) No Feedback Cannot be set (0.0%) Cannot be set (100.0%) Output (analog) Feedback -100.0% or 0.0% 0.0% or +100.0% Output (analog) Feedback_PER -100.0% or 0.0% 0.0% or +100.0% Limiting the output value You can only exceed or undershoot the output value limits during the transition time measurement. The output value is limited to these values in all other modes. Enter the absolute output value limits in the "Output value high limit" and "Output value low limit" input boxes. The output value limits must be within "Low endstop" and "High endstop". If no Feedback is available and Output (digital) is set, you cannot limit the output value. The digital outputs are reset with Actuator_H = TRUE or Actuator_L = TRUE, or after a travel time amounting to 110% of the motor transition time. Advanced settings Monitoring process value Configure a warning high and low limit for the process value in the "Process value monitoring" configuration window. If one of the warning limits is exceeded or undershot during operation, a warning will be displayed at the PID_3Step instruction: At the InputWarning_H output parameter if the warning high limit has been exceeded At the InputWarning_L output parameter if the warning low limit has been undershot The warning limits must be within the process value high and low limits. The process value high and low limits will be used if you do not enter values. Example Process value high limit = 98 C; warning high limit = 90 C 4300 WinCC Basic V13.0 System Manual, 02/2014 Using technology functions 11.1 PID control Warning low limit = 10 C; process value low limit = 0 C PID_3Step will respond as follows: Process value InputWarning_H InputWarning_L Operating mode > 98 C TRUE FALSE Inactive 98 C and > 90 C TRUE FALSE Automatic mode 90 C and 10 C FALSE FALSE Automatic mode < 10 C and 0 C FALSE TRUE Automatic mode < 0 C FALSE TRUE Inactive PID parameters The PID parameters are displayed in the "PID Parameters" configuration window. The PID parameters will be adapted to your controlled system during controller tuning. You do not need to enter the PID parameters manually. The PID algorithm operates according to the following equation: [ y = K p * s * (b * w - x) + 1 TI * s (w - x) + Symbol Description y Output value of the PID algorithm TD * s a * TD * s + 1 (c * w - x) Kp Proportional gain s Laplace operator b Proportional action weighting w Setpoint x Process value TI Integral action time a Derivative delay coefficient (derivative delay T1 = a x TD) TD Derivative action time c Derivative action weighting ] The diagram below illustrates the integration of the parameters into the PID algorithm: WinCC Basic V13.0 System Manual, 02/2014 4301 Using technology functions 11.1 PID control E 6HWSRLQW Z '7 F ' . 3 \ 'HDGB% 7L , 6FDOHG,QSXW [ )DF7W $QWL:LQGXS All PID parameters are retentive. If you enter the PID parameters manually, you must completely download PID_3Step. Auto-Hotspot Proportional gain The value specifies the proportional gain of the controller. PID_3Step does not work with a negative proportional gain. Control logic is inverted under Basic settings > Controller type. Integral action time The integral action time determines the time behavior of the integral action. The integral action is deactivated with integral action time = 0.0. Derivative action time The derivative action time determines the time behavior of the derivative action. Derivative action is deactivated with derivative action time = 0.0. Derivative delay coefficient The derivative delay coefficient delays the effect of the derivative action. Derivative delay = derivative action time x derivative delay coefficient 0.0: Derivative action is effective for one cycle only and therefore almost not effective. 0.5: This value has proved useful in practice for controlled systems with one dominant time constant. > 1.0: The greater the coefficient, the longer the effect of the derivative action is delayed. Proportional action weighting The proportional action may weaken with changes to the setpoint. 4302 WinCC Basic V13.0 System Manual, 02/2014 Using technology functions 11.1 PID control Values from 0.0 to 1.0 are applicable. 1.0: Proportional action for setpoint change is fully effective 0.0: Proportional action for setpoint change is not effective The proportional action is always fully effective when the process value is changed. Derivative action weighting The derivative action may weaken with changes to the setpoint. Values from 0.0 to 1.0 are applicable. 1.0: Derivative action is fully effective upon setpoint change 0.0: Derivative action is not effective upon setpoint change The derivative action is always fully effective when the process value is changed. PID algorithm sampling time The controlled system needs a certain amount of time to respond to changes in the output value. It is therefore not advisable to calculate the output value in every cycle. The sampling time of the PID algorithm represents the time between two calculations of the output value. It is calculated during tuning and rounded to a multiple of the PID_3Step sampling time. All other functions of PID_3Step are executed at every call. Deadband width The deadband suppresses the noise component in the steady controller state. The deadband width specifies the size of the deadband. The deadband is off if the deadband width is 0.0. See also Downloading technology objects to device (Page 4223) Commissioning PID_3Step V1 Commissioning You can monitor the setpoint, process value and output value over time in the "Tuning" working area. The following commissioning functions are supported in the curve plotter: Controller pretuning Controller fine tuning Monitoring the current closed-loop control in the trend view All functions require an online connection to the CPU to have been established. WinCC Basic V13.0 System Manual, 02/2014 4303 Using technology functions 11.1 PID control Basic handling Select the desired sampling time in the "Sampling time" drop-down list. All values in the tuning working area are updated in the selected update time. Click the "Start" icon in the measuring group if you want to use the commissioning functions. Value recording is started. The current values for the setpoint, process value and output value are entered in the trend view. Operation of the commissioning window is enabled. Click the "Stop" icon if you want to end the commissioning functions. The values recorded in the trend view can continue to be analyzed. Closing the commissioning window will terminate recording in the trend view and delete the recorded values. Pretuning The pretuning determines the process response to a pulse of the output value and searches for the point of inflection. The tuned PID parameters are calculated as a function of the maximum slope and dead time of the controlled system. The more stable the process value is, the easier it is to calculate the PID parameters and the more precise the result will be. Noise on the process value can be tolerated as long as the rate of rise of the process value is significantly higher compared to the noise. The PID parameters are backed up before being recalculated. The setpoint is frozen during pretuning. Requirement The PID_3Step instruction is called in a cyclic interrupt OB. ManualEnable = FALSE PID_3Step is in "inactive" or "manual" mode. The setpoint and the process value lie within the configured limits (see "Process value settings" configuration). 4304 WinCC Basic V13.0 System Manual, 02/2014 Using technology functions 11.1 PID control Procedure To perform pretuning, follow these steps: 1. Double-click the "PID_3Step > Commissioning" entry in the project tree. 2. Select the entry "Pretuning" in the "Tuning mode" drop-down list in the working area "Tuning". 3. Click the "Start" icon. - An online connection will be established. - Value recording is started. - Pretuning is started. - The "Status" field displays the current steps and any errors that may have occurred. The progress bar indicates the progress of the current step. Note Click the "Stop" icon when the progress bar has reached 100% and it is to be assumed the controller tuning function is blocked. Check the configuration of the technology object and, if necessary, restart controller tuning. Result If pretuning was performed without an error message, the PID parameters have been tuned. PID_3Step switches to automatic mode and uses the tuned parameters. The tuned PID parameters will be retained during power OFF and a restart of the CPU. If pretuning is not possible, PID_3Step changes to "Inactive" mode. Fine tuning Fine tuning generates a constant, limited oscillation of the process value. The PID parameters are optimized for the operating point from the amplitude and frequency of this oscillation. All PID parameters are recalculated on the basis of the findings. PID parameters from fine tuning usually have better master control and disturbance behavior than PID parameters from pretuning. PID_3Step automatically attempts to generate an oscillation greater than the noise of the process value. Fine tuning is only minimally influenced by the stability of the process value. The PID parameters are backed up before being recalculated. The setpoint is frozen during fine tuning. Requirement The PID_3Step instruction is called in a cyclic interrupt OB. ManualEnable = FALSE The motor transition time has been configured or measured. The setpoint and the process value lie within the configured limits (see "Process value settings" configuration). WinCC Basic V13.0 System Manual, 02/2014 4305 Using technology functions 11.1 PID control The control loop has stabilized at the operating point. The operating point is reached when the process value corresponds to the setpoint. No disturbances are expected. PID_3Step is in inactive mode, automatic mode or manual mode. Process depends on initial situation Fine tuning proceeds as follows when started in: Automatic mode Start fine tuning in automatic mode if you wish to improve the existing PID parameters using controller tuning. PID_3Step will regulate using the existing PID parameters until the control loop has stabilized and the requirements for fine tuning have been met. Only then will fine tuning start. Inactive or manual mode Pretuning is always started first. The PID parameters established will be used for adjustment until the control loop has stabilized and the requirements for fine tuning have been met. Only then will fine tuning start. Procedure Proceed as follows to carry out "fine tuning": 1. Select the entry "Fine tuning" in the "Tuning mode" drop-down list. 2. Click the "Start" icon. - An online connection will be established. - Value recording is started. - The process of fine tuning is started. - The "Status" field displays the current steps and any errors that may have occurred. The progress bar indicates the progress of the current step. Note Click the "Stop" icon in the "Tuning mode" group when the progress bar has reached 100% and it is to be assumed the controller tuning function is blocked. Check the configuration of the technology object and, if necessary, restart controller tuning. Result The PID parameters will have been optimized if fine tuning has been executed without errors. PID_3Step changes to automatic mode and uses the optimized parameters. The optimized PID parameters will be retained during power OFF and a restart of the CPU. If errors occurred during fine tuning, PID_3Step will change to "inactive" mode. 4306 WinCC Basic V13.0 System Manual, 02/2014 Using technology functions 11.1 PID control Commissioning with manual PID parameters Procedure Proceed as follows to commission PID_3Step with manual PID parameters: 1. Double-click on "PID_3Step > Configuration" in the project tree. 2. Click on "Advanced settings > PID Parameters" in the configuration window. 3. Select the check box "Enable direct input". 4. Enter the PID parameters. 5. Double-click on "PID_3Step > Commissioning" in the project tree. 6. Establish an online connection to the CPU. 7. Load the PID parameters to the CPU. 8. Click on the "Activate controller" icon. Result PID_3Step changes to automatic mode and controls using the current PID parameters. Measuring the motor transition time Introduction PID_3Step requires the motor transition time to be as accurate as possible for good controller results. The data in the actuator documentation contains average values for this type of actuator. The value for the specific actuator used may differ. You can measure the motor transition time during commissioning if you are using actuators with position feedback or endstop signals. The output value limits are not taken into consideration during the motor transition time measurement. The actuator can travel to the high or the low endstop. The motor transition time cannot be measured if neither position feedback nor endstop signals are available. Actuators with analog position feedback Proceed as follows to measure motor transition time with position feedback: Requirement Feedback or Feedback_PER has been selected in the basic settings and the signal has been connected. An online connection to the CPU has been established. WinCC Basic V13.0 System Manual, 02/2014 4307 Using technology functions 11.1 PID control 1. Select the "Use position feedback" check box. 2. Enter the position to which the actuator is to be moved in the "Target position" input field. The current position feedback (starting position) will be displayed. The difference between "Target position" and "Position feedback" must be at least 50% of the valid output value range. 3. Click the "Start transition time measurement" icon. Result The actuator is moved from the starting position to the target position. Time measurement starts immediately and ends when the actuator reaches the target position. The motor transition time is calculated according to the following equation: Motor transition time = (output value high limit - output value low limit) x Measuring time / AMOUNT (target position - starting position). The progress and status of transition time measurement are displayed. The transition time measured is saved in the instance data block on the CPU and displayed in the "Measured transition time" field. PID_3Step will change to "Inactive" mode once transition time measurement is complete. Note Click on the icon "Upload measured transition time" to load the motor transition time measured to the project. Actuators with endstop signals Proceed as follows to measure the transition time of actuators with endstop signals: Requirement The "Endstop signals" check box in the basic settings has been selected and Actuator_H and Actuator_L are connected. An online connection to the CPU has been established. Proceed as follows to measure motor transition time with endstop signals: 1. Select the "Use actuator endstop signals" check box. 2. Select the direction in which the actuator is to be moved. - Open - Close - Open The actuator is moved first to the high endstop, then to the low endstop and then back to the high endstop. - Close - Open - Close The actuator is moved first to the low endstop, then to the high endstop and then back to the low endstop. 3. Click the 4308 "Start transition time measurement" icon. WinCC Basic V13.0 System Manual, 02/2014 Using technology functions 11.2 Using S7-1200 Motion Control Result The actuator is moved in the selected direction. Time measurement will start once the actuator has reached the first endstop and will end when the actuator reaches this endstop for the second time. The motor transition time is equal to the time measured divided by two. The progress and status of transition time measurement are displayed. The transition time measured is saved in the instance data block on the CPU and displayed in the "Measured transition time" field. PID_3Step will change to "Inactive" mode once transition time measurement is complete. Cancelling transition time measurement PID_3Step will change to "Inactive" mode immediately if you cancel transition time measurement. The actuator will stop being moved. You can reactive PID-3Step in the curve plotter. 11.2 Using S7-1200 Motion Control 11.2.1 Introduction 11.2.1.1 Motion functionality of the CPU S7-1200 The TIA Portal, together with the "Motion Control" functionality of the CPU S71200, supports you in controlling stepper motors and servo motors with pulse interface: You configure the positioning axis and command table technology objects in the TIA Portal. The CPU S7-1200 uses these technology objects to control the pulse generator outputs that control the drives. In the user program you control the axis by means of Motion Control instructions and initiate motion commands of your drive. You can find a multi-media introduction on the Internet (http://www.automation.siemens.com/ mcms/topics/en/simatic/simatic-technology/integrated-functions/simatic-s7-1200/Pages/ Default.aspx). See also Hardware components for motion control (Page 4310) Integration of the positioning axis technology object (Page 4330) Tools of the positioning axis technology object (Page 4333) Use of the command table technology object (Page 4359) Command table technology object tools (Page 4359) WinCC Basic V13.0 System Manual, 02/2014 4309 Using technology functions 11.2 Using S7-1200 Motion Control 11.2.1.2 Hardware components for motion control The representation below shows the basic hardware configuration for a motion control application with the CPU S7-1200. 6,0$7,&6 5816723 (5525 0$,17 , , , , , , , , , , , , , , 6LJQDOERDUG ', &38& '&'&'& ' ;31/$1 3XOVHJHQHUDWRURXWSXWV 352),1(7 3RZHUXQLW IRU VWHSSHUPRWRU 3RZHUXQLW IRU 6HUYRPRWRU CPU S7-1200: CPU S7-1200 combines the functionality of a programmable logic controller with motion control functionality for operation of stepper motors and servo motors with pulse interface. The motion control functionality takes over the control and monitoring of the drives. The DC/DC/DC variants of the CPU S7-1200 have on-board outputs for direct control of drives. The relay variants of the CPU require one of the signal boards described below to control a drive. Signal board You add further inputs and outputs to the CPU with the signal boards. The digital outputs can be used as pulse generator outputs for controlling drives as required. In CPUs with relay outputs, the pulse signal cannot be output on the on-board outputs because the relays do not support the necessary switching frequencies. A signal board with digital outputs must be used to enable you to work with the PTO (Pulse Train Output) on these CPUs. 4310 WinCC Basic V13.0 System Manual, 02/2014 Using technology functions 11.2 Using S7-1200 Motion Control PROFINET Use the PROFINET interface to establish the online connection between the CPU S7-1200 and the programming device. In addition to the online functions of the CPU, additional commissioning and diagnostic functions are available for motion control. Ordering information for CPU Firmware V4 The order information listed below applies to the currently installed product phase (without any installed Hardware Support Packages) of the TIA Portal. Name MLFB (order number) CPU 1211C DC/DC/DC 6ES7211-1AE40-0XB0 CPU 1211C AC/DC/RLY 6ES7211-1BE40-0XB0 CPU 1211C DC/DC/RLY 6ES7211-1HE40-0XB0 CPU 1212C DC/DC/DC 6ES7212-1AE40-0XB0 CPU 1212C AC/DC/RLY 6ES7212-1BE40-0XB0 CPU 1212C DC/DC/RLY 6ES7212-1HE40-0XB0 CPU 1214C DC/DC/DC 6ES7214-1AG40-0XB0 CPU 1214C AC/DC/RLY 6ES7214-1BG40-0XB0 CPU 1214C DC/DC/RLY 6ES7214-1HG40-0XB0 CPU 1214FC DC/DC/DC 6ES7214-1AF40-0XB0 CPU 1214FC DC/DC/RLY 6ES7214-1HF40-0XB0 CPU 1215C DC/DC/DC 6ES7215-1AG40-0XB0 CPU 1215C AC/DC/RLY 6ES7215-1BG40-0XB0 CPU 1215C DC/DC/RLY 6ES7215-1HG40-0XB0 CPU 1215FC DC/DC/DC 6ES7215-1AF40-0XB0 CPU 1215FC DC/DC/RLY 6ES7215-1HF40-0XB0 CPU 1217C DC/DC/DC 6ES7217-1AG40-0XB0 Signal board DI2/DO2 x DC24V 20kHz 6ES7223-0BD30-0XB0 Signal board DI2/DO2 x DC24V 200kHz 6ES7223-3BD30-0XB0 Signal board DO4 x DC24V 200kHz 6ES7222-1BD30-0XB0 Signal board DI2/DO2 x DC5V 200kHz 6ES7223-3AD30-0XB0 Signal board DO4 x DC5V 200kHz 6ES7222-1AD30-0XB0 Use a Hardware Support Package (HSP) to install new hardware components. The hardware component will then be available in the hardware catalog. See also Motion functionality of the CPU S7-1200 (Page 4309) CPU outputs relevant for motion control (technology version V4) (Page 4312) WinCC Basic V13.0 System Manual, 02/2014 4311 Using technology functions 11.2 Using S7-1200 Motion Control 11.2.2 Basics for working with S7-1200 Motion Control 11.2.2.1 CPU outputs relevant for motion control (technology version V4) The number of usable drives depends on the number of PTOs (pulse train outputs) and the number of available pulse generator outputs. The following tables provide information about the relevant dependencies: Maximum number of PTOs 4 PTOs are available for each CPU with technology version V4. This means a maximum of 4 drives can be controlled. Signal type of the PTO Depending on the signal type of the PTO, 1-2 pulse generator outputs are required per PTO (drive): Signal type Number of pulse generator outputs Pulse A and direction B (direction output disabled) *) 1 Pulse A and direction B *) 2 Count up A, count down B 2 A/B phase offset 2 A/B phase offset - quadruple 2 *) The direction output must be on-board or on a signal board. Usable pulse generator outputs and limit frequencies The relay variants of the CPUs can only access the pulse generator outputs of a signal board. Depending on the CPU and signal board, the following pulse signal generator outputs can be used with the following limit frequencies: On-board Q0.0 Q0.1 Q0.2 Q0.3 Q0.4 Q0.5 Q0.6 Q0.7 Q1.0 Q1.1 CPU 1211 (DC/DC/ DC) 100 kHz 100 kHz 100 kHz 100 kHz - - - - - - CPU 1212 (DC/DC/ DC) 100 kHz 100 kHz 100 kHz 100 kHz 30 kHz 30 kHz - - - - CPU 1214(F) (DC/DC/ DC) 100 kHz 100 kHz 100 kHz 100 kHz 30 kHz 30 kHz 30 kHz 30 kHz 30 kHz 30 kHz CPU 1215(F) (DC/DC/ DC) 100 kHz 100 kHz 100 kHz 100 kHz 30 kHz 30 kHz 30 kHz 30 kHz 30 kHz 30 kHz 100 kHz 100 kHz 100 kHz 100 kHz - - - - CPU 1217 (DC/DC/ DC) Signal board 4312 1 MHz 1 MHz 1 MHz 1 MHz Qx.0 Qx.1 Qx.2 Qx.3 100 kHz 100 kHz - - WinCC Basic V13.0 System Manual, 02/2014 Using technology functions 11.2 Using S7-1200 Motion Control On-board Q0.0 Q0.1 Q0.2 Q0.3 Q0.4 Q0.5 Q0.6 Q0.7 Q1.0 Q1.1 Signal board DI2/DO2 x DC24V 20kHz 20 kHz 20 kHz - - - - - - - - Signal board DI2/DO2 x DC24V 200kHz 200 kHz 200 kHz - - - - - - - - Signal board DO4 x DC24V 200kHz 200 kHz 200 kHz 200 kHz 200 kHz - - - - - - Signal board DI2/DO2 x DC5V 200kHz 200 kHz 200 kHz - - - - - - Signal board DO4 x DC5V 200kHz 200 kHz 200 kHz 200 kHz 200 kHz - - - - - - - - The low limit frequency is always 1Hz. The pulse generator outputs can be freely assigned to the PTOs. Note If pulse generator outputs with different limit frequencies are used in accordance with the signal type, the low limit frequency is used in each case. Signal type "Pulse A and direction B" is an exception. With this type of signal, the limit frequency of the pulse generator output is always used. Note Access to pulse generator outputs via the process image The firmware takes control via the corresponding pulse generator and direction outputs if the PTO (Pulse Train Output) is selected and assigned to an axis. With this takeover of the control function, the connection between the process image and I/ O output is also disconnected. Although the user has the option of writing the process image of pulse generator and direction outputs via the user program or watch table, this is not transferred to the I/O output. Accordingly, it is also not possible to monitor the I/O output via the user program or watch table. The information read reflects the value of the process image and does not match the real status of the I/O output. For all other CPU outputs that are not used permanently by the CPU firmware, the status of the I/O output can be controlled or monitored via the process image, as usual. Outputs for drive signals For motion control, you can optionally parameterize a drive interface for "Drive enabled" and "Drive ready". When using the drive interface the digital output for the drive enable and the digital input for "drive ready" can be freely selected. WinCC Basic V13.0 System Manual, 02/2014 4313 Using technology functions 11.2 Using S7-1200 Motion Control Acceleration/deceleration limits The following limits apply to acceleration and deceleration: Acceleration/deceleration Value Minimum acceleration/deceleration 5.0E-3 pulses/s2 Maximum acceleration/deceleration 9.5E+9 pulses/s2 Jerk limits The following limits apply to the jerk: Jerk Value Minimum jerk 4.0E-3 pulses/s3 Maximum jerk 1.0E+10 pulses/s3 See also CPU outputs relevant for motion control (technology version V1...3) (Page 4466) How the pulse interface works (Page 4314) Relationship between the signal type and the direction of travel (Page 4315) Hardware and software limit switches (Page 4319) Jerk limit (Page 4320) Homing (Page 4321) Hardware components for motion control (Page 4310) Integration of the positioning axis technology object (Page 4330) Tools of the positioning axis technology object (Page 4333) 11.2.2.2 How the pulse interface works Depending on the settings of the stepper motor, each pulse affects the movement of the stepper motor by a specific angle. If the stepper motor is set to 1000 pulses per revolution, for example, it moves 0.36 per pulse. The speed of the stepper motor is determined by the number of pulses per time unit. 6ORZ )DVW 4314 WinCC Basic V13.0 System Manual, 02/2014 Using technology functions 11.2 Using S7-1200 Motion Control (The statements made here also apply to servo motors with pulse interface.) See also CPU outputs relevant for motion control (technology version V4) (Page 4312) Relationship between the signal type and the direction of travel (Page 4315) Hardware and software limit switches (Page 4319) Jerk limit (Page 4320) Homing (Page 4321) Integration of the positioning axis technology object (Page 4330) Tools of the positioning axis technology object (Page 4333) 11.2.2.3 Relationship between the signal type and the direction of travel The CPU outputs the velocity and direction of travel via two outputs. The relationships between the configuration and direction of travel differ depending on the selected signal type. You can configure the following signal types in the axis configuration under "Basic parameters > General": "PTO (pulse A and direction B)" "PTO (count up A, count down B)" (as of V4) "PTO (A/B phase offset)" (as of V4) "PTO (A/B phase offset - quadruple)" (as of V4) You configure the direction under "Extended Parameters > Mechanics" in the axis configuration. If you select the "Invert direction" option, the direction logic described below for the respective signal type is inverted. PTO (pulse A and direction B) The pulse output pulses and the direction output level are evaluated for this signal type. The pulses are output via the pulse output of the CPU. The direction output of the CPU specifies the direction of rotation of the drive: 5 V/24 V at direction output positive direction of rotation 0 V at direction output negative direction of rotation The specified voltage depends on the hardware used. The indicated values do not apply to the differential outputs of CPU 1217. WinCC Basic V13.0 System Manual, 02/2014 4315 Using technology functions 11.2 Using S7-1200 Motion Control 3RVLWLYH WUDYHOGLUHFWLRQ 1HJDWLYH WUDYHOGLUHFWLRQ 8 99 3XOVHRXWSXW 9 W 99 'LUHFWLRQRXWSXW 9 W PTO (count up A, count down B) (as of V4) The pulses of an output are evaluated for this signal type. The pulse for the positive direction is output via the "Up pulse output" The pulse for the negative direction is output via the "Down pulse output" The specified voltage depends on the hardware used. The values indicated do not apply to the differential outputs of CPU 1217. 3RVLWLYH WUDYHOGLUHFWLRQ 1HJDWLYH WUDYHOGLUHFWLRQ 8 99 8SSXOVHRXWSXW 9 W 99 'RZQSXOVHRXWSXW 9 W PTO (A/B phase offset) (as of V4) The positive edges of one output in each case are evaluated for this signal type. The pulse is output via the "Phase A" output and phase-shifted via the "Phase B" output. The phase shifting between the outputs defines the direction of rotation: 4316 WinCC Basic V13.0 System Manual, 02/2014 Using technology functions 11.2 Using S7-1200 Motion Control Phase A leads phase B by 90 positive direction of rotation Phase B leads phase A by 90 negative direction of rotation PTO (A/B phase offset - quadruple) (as of V4) The positive and negative edges of both outputs are evaluated for this signal type. A pulse period has four edges with two phases (A and B). The pulse frequency at the output is therefore reduced to a quarter. The pulse is output via the "Phase A" output and phase-shifted via the "Phase B" output. The phase shifting between the outputs defines the direction of rotation: Phase A leads phase B by 90 positive direction of rotation Phase B leads phase A by 90 negative direction of rotation The specified voltage depends on the hardware used. The indicated values do not apply to the differential outputs of CPU 1217. WinCC Basic V13.0 System Manual, 02/2014 4317 Using technology functions 11.2 Using S7-1200 Motion Control SRVLWLYH GLUHFWLRQ QHJDWLYH GLUHFWLRQ 372 $% SKDVHRIIVHW $ 99 3KDVH$ 9 W 99 3KDVH% 9 W 372 $% SKDVHRIIVHW TXDGUXSOH $ 99 3KDVH$ 9 W 99 3KDVH% 9 W Invert direction If you select the "Invert rotation signal" option, the direction logic is inverted: PTO (pulse A and direction B) - 0 V at direction output (low level) positive direction of rotation - 5 V/24 V at direction output (high level) negative direction of rotation The specified voltage depends on the hardware used. The voltages indicated do not apply to the differential outputs of CPU 1217. PTO (count up A, count down B) The outputs "Pulse output down" and "Pulse output up" are swapped. 4318 WinCC Basic V13.0 System Manual, 02/2014 Using technology functions 11.2 Using S7-1200 Motion Control PTO (A/B phase offset) The "Phase A" and "Phase B" outputs are swapped. "PTO (A/B phase offset - quadruple) The "Phase A" and "Phase B" outputs are swapped. See also CPU outputs relevant for motion control (technology version V4) (Page 4312) How the pulse interface works (Page 4314) Hardware and software limit switches (Page 4319) Jerk limit (Page 4320) Homing (Page 4321) Integration of the positioning axis technology object (Page 4330) Tools of the positioning axis technology object (Page 4333) 11.2.2.4 Hardware and software limit switches Use the hardware and software limit switches to limit the "permitted traversing range" and the "working range" of your positioning axis technology object. The relationships are shown in the following diagram: SHUPLWWHGWUDYHOUDQJH ZRUNLQJUDQJH V PHFKDQLFDO VWRS +:OLPLWVZLWFK 6:OLPLWVZLWFK 6:OLPLWVZLWFK +:OLPLWVZLWFK PHFKDQLFDO VWRS Hardware limit switches are limit switches that limit the maximum "permitted traversing range" of the axis. Hardware limit switches are physical switching elements that must be connected to interrupt-capable inputs of the CPU. Software limit switches limit the "working range" of the axis. They should fall inside the hardware limit switches relative to the traversing range. Since the positions of the software limit switches can be flexibly set, the working range of the axis can be adapted on an individual basis, depending on the current traversing profile. In contrast to hardware limit switches, software limit switches are implemented exclusively via the software and do not require their own switching elements. Hardware and software limit switches must be activated prior to use in the configuration or in the user program.. Software limit switches are only active after homing the axis. WinCC Basic V13.0 System Manual, 02/2014 4319 Using technology functions 11.2 Using S7-1200 Motion Control See also CPU outputs relevant for motion control (technology version V4) (Page 4312) How the pulse interface works (Page 4314) Relationship between the signal type and the direction of travel (Page 4315) Jerk limit (Page 4320) Homing (Page 4321) Integration of the positioning axis technology object (Page 4330) Tools of the positioning axis technology object (Page 4333) Position limits (Page 4341) 11.2.2.5 Jerk limit With the jerk limit you can reduce the stresses on your mechanics during an acceleration and deceleration ramp. The acceleration and deceleration value is not changed abruptly when the jerk limiter is active; it is gradually increased and decreased. The figure below shows the velocity and acceleration curve without and with jerk limit. Travel without jerk limit Travel with jerk limit Y Y W W D D W W The jerk limit gives a "smoothed" velocity profile of the axis motion. This ensures, for example, soft starting and braking of a conveyor belt. See also Behavior of the axis when using the jerk limit (Page 4350) CPU outputs relevant for motion control (technology version V4) (Page 4312) 4320 WinCC Basic V13.0 System Manual, 02/2014 Using technology functions 11.2 Using S7-1200 Motion Control How the pulse interface works (Page 4314) Relationship between the signal type and the direction of travel (Page 4315) Hardware and software limit switches (Page 4319) Homing (Page 4321) Integration of the positioning axis technology object (Page 4330) Tools of the positioning axis technology object (Page 4333) 11.2.2.6 Homing Homing means matching the axis coordinates of the technology object to the real, physical location of the drive. For position-controlled axes the entries and displays for the position refer exactly to these axis coordinates. Therefore, agreement between the axis coordinates and the real situation is extremely important. This step is necessary to ensure that the absolute target position of the axis is also achieved exactly with the drive. In the S7-1200 CPU, axis homing is implemented with the motion control instruction, "MC_Home". The following homing modes exist Homing modes Active homing In active homing mode, the motion control instruction "MC_Home" performs the required reference point approach. When the homing switch is detected, the axis is homed according to the configuration. Active traversing motions are aborted. Passive homing During passive homing, the motion control instruction "MC_Home" does not carry out any homing motion. The traversing motion required for this step must be implemented by the user via other motion control instructions. When the homing switch is detected, the axis is homed according to the configuration. Active traversing motions are not aborted upon start of passive homing. Direct homing absolute The axis position is set regardless of the homing switch. Active traversing motions are not aborted. The value of input parameter "Position" of motion control instruction "MC_Home" is set immediately as the reference point of the axis. Direct homing relative The axis position is set regardless of the homing switch. Active traversing motions are not aborted. The following statement applies to the axis position after homing: New axis position = current axis position + value of parameter "Position" of instruction "MC_Home". See also CPU outputs relevant for motion control (technology version V4) (Page 4312) How the pulse interface works (Page 4314) Relationship between the signal type and the direction of travel (Page 4315) WinCC Basic V13.0 System Manual, 02/2014 4321 Using technology functions 11.2 Using S7-1200 Motion Control Hardware and software limit switches (Page 4319) Jerk limit (Page 4320) Integration of the positioning axis technology object (Page 4330) Tools of the positioning axis technology object (Page 4333) Homing (positioning axis technology object as of V2) (Page 4352) 11.2.3 Guidelines on use of motion control The guidelines described here present the basic procedure for using motion control with the CPU S7-1200. Requirements To use the positioning axis technology object, a project with a CPU S7-1200 must be created. Procedure Follow the steps below in the order given to use motion control with the CPU S7-1200. Use the following links for this purpose: 1. Adding a positioning axis technology object (Page 4335) 2. Working with the configuration dialog (Page 4335) 3. Download to CPU (Page 4378) 4. Function test of the axis in the commissioning window (Page 4379) 5. Programming (Page 4400) 6. Diagnostics of the axis control (Page 4418) 11.2.4 Using versions 11.2.4.1 Overview of versions The relationship between the relevant versions for S7-1200 Motion Control can be found in the following table: Technology version You can check the currently selected technology version in the "Instructions" task card in folder "Technology > Motion Control > S7-1200 Motion Control" and in the "Add new object" dialog. Select the technology version in the "Instructions" task card in folder "Technology > Motion Control > S7-1200 Motion Control". 4322 WinCC Basic V13.0 System Manual, 02/2014 Using technology functions 11.2 Using S7-1200 Motion Control If a technology object with an alternative version is added in the "Add new object" dialog, the technology version will also be changed. Note The selection of an alternative technology version will also affect the Motion Control Instructions version (task card). The technology objects and Motion Control instructions will only be converted to the selected version upon compilation or "Load to device". Version of the technology object The version of a technology object can be checked in the inspector window under "Properties > General > Information" in the "Version" box. Motion Control instruction version The Motion Control instruction version can be checked in the inspector window under "Properties > General > Information" in the "Version" box. If the Motion Control instruction version used is not in line with the following compatibility list, the relevant Motion Control instructions will be highlighted in the program editor. Compatibility list Technology V1.0 CPU Technology object Motion Control Instruction V1.0, V2.0, V2.1, V2.2, V3.0 Axis V1.0 MC_Power V1.0 MC_Reset V1.0 MC_Home V1.0 MC_Halt V1.0 MC_MoveAbsolute V1.0 MC_MoveRelative V1.0 MC_MoveVelocity V1.0 MC_MoveJog V1.0 V2.0 Innovations: Jerk limit Command table MC_ChangeDynamic V2.1, V2.2, V3.0 Axis V2.0, Command table V2.0 MC_Power V2.0 MC_Reset V2.0 MC_Home V2.0 MC_Halt V2.0 MC_MoveAbsolute V2.0 MC_MoveRelative V2.0 MC_MoveVelocity V2.0 MC_MoveJog V2.0 MC_CommandTable V2.0 MC_ChangeDynamic V2.0 WinCC Basic V13.0 System Manual, 02/2014 4323 Using technology functions 11.2 Using S7-1200 Motion Control Technology V3.0 Innovation: CPU Technology object Motion Control Instruction V2.2, V3.0, V4.0 Axis V3.0, Command table V3.0 MC_Power V3.0 Load in RUN operating mode MC_Reset V3.0 MC_Home V3.0 MC_Stop V3.0 MC_MoveAbsolute V3.0 MC_MoveRelative V3.0 MC_MoveVelocity V3.0 MC_MoveJog V3.0 MC_CommandTable V3.0 MC_ChangeDynamic V3.0 V4.0 Innovations: V4.0 MC_ReadParam Positioning axis V4.0, command table V4.0 MC_WriteParam Standardization of S71200 and S71500 Motion Control technology data blocks. MC_Power V4.0 MC_Reset V4.0 MC_Home V4.0 MC_Halt V4.0 MC_MoveAbsolute V4.0 MC_MoveRelative V4.0 MC_MoveVelocity V4.0 MC_MoveJog V4.0 MC_CommandTable V4.0 MC_ChangeDynamic V4.0 MC_ReadParam V4.0 MC_WriteParam V4.0 See also Changing a technology version (Page 4324) Compatibility list of tags (Page 4325) Status of limit switch (Page 4328) 11.2.4.2 Changing a technology version Before you can access all the benefits of a new technology version, you may need to set / modify the technology version for existing projects. Note Compatibility of the technology object tags If you are switching from V1...3 and V4, please see the compatibility list (Page 4325) if you are using tags of the technology object in your user program, monitoring tables, etc. 4324 WinCC Basic V13.0 System Manual, 02/2014 Using technology functions 11.2 Using S7-1200 Motion Control Setting/changing a technology version To set or change the technology version, follow these steps: 1. Open the programming editor (e.g., by opening the OB1). 2. In the "Instructions" task card, open the desired technology version in the "Technology > Motion Control > S7-1200 Motion Control" folder. 3. Save and compile the project. Pay attention to any error information that is displayed during compilation. Deal with the causes of the errors indicated. 4. Check the configuration of the technology objects. 5. If necessary, adapt the tag names in the following objects in line with the compatibility list. User program Monitoring tables Force tables HMI configuration Trace configuration See also Overview of versions (Page 4322) Status of limit switch (Page 4328) 11.2.4.3 Compatibility list of tags The technology data blocks for S7-1200 Motion Control and S7-1500 Motion Control have been standardized within the framework of the V4 technology. This has resulted in new tags and tag names for the V4 positioning axis and V4 command table technology objects. Note the following tables if you have used tags of the technology objects in the user program and you want to convert the project from V1...3 to V4 (or vice versa). The tags listed in the "Automatic conversion V1...3 to V4" column are converted automatically when the project is compiled. Tag names in monitoring and force tables or the HMI or trace configuration are not converted. The following tags are new or have been adapted and may have to be corrected in the user program, monitoring tables, etc.: WinCC Basic V13.0 System Manual, 02/2014 4325 Using technology functions 11.2 Using S7-1200 Motion Control Config tags (positioning axis) Tag name V1.0 to V3.0 Tag name V4.0 Automatic conversion V1..3 to V4 <Axis name>.Config.DynamicDefaults.Acceleratio n <Axis name>.DynamicDefaults.Acceleration Yes <Axis name>.Config.DynamicDefaults.Deceleratio n <Axis name>.DynamicDefaults.Deceleration Yes <Axis name>.Config.DynamicDefaults.Emergency Deceleration <Axis name>.DynamicDefaults.EmergencyDeceleration Yes <Axis name>.Config.DynamicDefaults.Jerk <Axis name>.DynamicDefaults.Jerk Yes <Axis name>.Config.DynamicDefaults.JerkActive Not available No <Axis name>.Config.DynamicLimits.MaxVelocity <Axis name>.DynamicLimits.MaxVelocity Yes <Axis name>.Config.DynamicLimits.MinVelocity <Axis name>.DynamicLimits.MinVelocity Yes <Axis name>.Config.General.LengthUnit <Axis name>.Units.LengthUnit Yes <Axis name>.Config.Homing.AutoReversal <Axis name>.Homing.AutoReversal Yes <Axis name>.Config.Homing.Direction <Axis name>.Homing.ApproachDirection Yes <Axis name>.Config.Homing.FastVelocity <Axis name>.Homing.ApproachVelocity Yes <Axis name>.Config.Homing.Offset <Axis name>.Sensor[1].ActiveHoming.HomePositionOffset Yes <Axis name>.Config.Homing.SideActiveHoming <Axis name>.Sensor[1].ActiveHoming.SideInput Yes <Axis name>.Config.Homing.SidePassiveHoming <Axis name>.Sensor[1].PassiveHoming.SideInput Yes <Axis name>.Config.Homing.SlowVelocity <Axis name>.Homing.ReferencingVelocity Yes <Axis name>.Config.Homing.SwitchedLevel <Axis name>.Sensor[1].ActiveHoming.SwitchLevel <Axis name>.Sensor[1].PassiveHoming.SwitchLevel No <Axis name>.Config.Mechanics.InverseDirection <Axis name>.Actor.InverseDirection Yes <Axis name>.Config.Mechanics.LeadScrew <Axis name>.Mechanics.LeadScrew Yes The jerk is activated if the configured jerk is > 0.004 pulse/s3. <Axis <Axis name>.Config.Mechanics.PulsesPerDriveRe name>.Actor.DriveParameter.PulsesPerDriveRevolutio volution n Yes <Axis name>.Config.PositionLimits_HW.Active <Axis name>.PositionLimitsHW.Active Yes <Axis name>.Config.PositionLimits_HW.MaxSwitc hedLevel <Axis name>.PositionLimitsHW.MaxSwitchLevel Yes <Axis <Axis name>.PositionLimitsHW.MinSwitchLevel name>.Config.PositionLimits_HW.MinSwitch edLevel Yes 4326 WinCC Basic V13.0 System Manual, 02/2014 Using technology functions 11.2 Using S7-1200 Motion Control Tag name V1.0 to V3.0 Tag name V4.0 Automatic conversion V1..3 to V4 <Axis name>.Config.PositionLimits_SW.Active <Axis name>.PositionLimitsSW.Active Yes <Axis name>.Config.PositionLimits_SW.MaxPositi on <Axis name>.PositionLimitsSW.MaxPosition Yes <Axis <Axis name>.PositionLimitsSW.MinPosition name>.Config.PositionLimits_SW.MinPositio n Yes Not available <Axis name>.Actor.DirectionMode No Not available <Axis name>.Actor.Type No Not available <Axis name>.Sensor[1].ActiveHoming.Mode No Not available <Axis name>.Sensor[1].PassiveHoming.Mode No ErrorBits tags (positioning axis) Tag name V1.0 to V3.0 Tag name V4.0 <Axis name>.ErrorBits.HwLimitMax <Axis name>.ErrorBits.HWLimit <Axis name>.ErrorBits.HwLimitMin (Note the new status bits and the section Status of the limit switch (Page 4328).) <Axis name>.ErrorBits.SwLimitMaxExceeded <Axis name>.ErrorBits.SWLimit Automatic conversion V1..3 to V4 No No (Note the new status bits and the section Status of the <Axis name>.ErrorBits.SwLimitMaxReached limit switch (Page 4328).) <Axis name>.ErrorBits.SwLimitMinExceeded <Axis name>.ErrorBits.SwLimitMinReached Not available <Axis name>.ErrorBits.DirectionFault No MotionStatus tags (positioning axis) Tag name V1.0 to V3.0 Tag name V4.0 <Axis name>.MotionStatus.Distance <Axis name>.StatusPositioning.Distance Yes <Axis name>.MotionStatus.Position <Axis name>.Position Yes <Axis name>.MotionStatus.TargetPosition <Axis name>.StatusPositioning.TargetPosition Yes <Axis name>.MotionStatus.Velocity <Axis name>.Velocity Yes WinCC Basic V13.0 System Manual, 02/2014 Automatic conversion V1..3 to V4 4327 Using technology functions 11.2 Using S7-1200 Motion Control StatusBits tags (positioning axis) Tag name V1.0 to V3.0 Tag name V4.0 Automatic conversion V1..3 to V4 <Axis name>.StatusBits.Homing <Axis name>.StatusBits.HomingCommand Yes <Axis name>.StatusBits.SpeedCommand <Axis name>.StatusBits.VelocityCommand Yes Not available <Axis name>.StatusBits.HWLimitMaxActive No Not available <Axis name>.StatusBits.HWLimitMinActive No Not available <Axis name>.StatusBits.SWLimitMaxActive No Not available <Axis name>.StatusBits.SWLimitMinActive No Tags (command table) Tag name V1.0 to V3.0 Tag name V4.0 Automatic conversion V1..3 to V4 <Command table>.Config.Command[n].Position <Command table>.Command[n].Position Yes <Command table>.Config.Command[n].Velocity <Command table>.Command[n].Velocity Yes <Command table>.Config.Command[n].Duration <Command table>.Command[n].Duration Yes <Command table>.Config.Command[n].NextStep <Command table>.Command[n].NextStep Yes <Command table>.Config.Command[n].StepCode <Command table>.Command[n].StepCode Yes See also Overview of versions (Page 4322) Changing a technology version (Page 4324) Tags of the positioning axis technology object as of V4 (Page 4446) 11.2.4.4 Status of limit switch The status and error bits for the display of the reached limit switch have been adapted in version V4. In order to replicate the behavior of the error bits of versions V1...3, use the following logical operators: 4328 WinCC Basic V13.0 System Manual, 02/2014 Using technology functions 11.2 Using S7-1200 Motion Control V1...3 V4 <Axis name>.ErrorBits.HwLimitMin <Axis name>.ErrorBits.HWLimit AND <Axis name>.StatusBits.HWLimitMinActive <Axis name>.ErrorBits.HwLimitMax <Axis name>.ErrorBits.HWLimit AND <Axis name>.StatusBits.HWLimitMaxActive <Axis name>.ErrorBits.SwLimitMinReached <Axis name>.ErrorBits.SWLimit AND (<Axis name>.Position = <Axis name>.PositioningLimits_SW.MinPosition) <Axis name>.ErrorBits.SwLimitMinExceeded <Axis name>.ErrorBits.SWLimit AND (<Axis name>.Position < <Axis name>.PositioningLimits_SW.MinPosition) <Axis name>.ErrorBits.SwLimitMaxReached <Axis name>.ErrorBits.SWLimit AND (<Axis name>.Position = <Axis name>.PositioningLimits_SW.MaxPosition) <Axis name>.ErrorBits.SwLimitMaxExceeded <Axis name>.ErrorBits.SWLimit AND (<Axis name>.Position > <Axis name>.PositioningLimits_SW.MaxPosition) See also Overview of versions (Page 4322) Changing a technology version (Page 4324) Compatibility list of tags (Page 4325) WinCC Basic V13.0 System Manual, 02/2014 4329 Using technology functions 11.2 Using S7-1200 Motion Control 11.2.5 Positioning axis technology object 11.2.5.1 Integration of the positioning axis technology object The following representation shows the relationships between the hardware and software components that are implemented when using the positioning axis technology object: &38KDUGZDUH 'ULYH S 6,0$7,&6 5816723 (5525 0$,17 , , , , , , , , , , , , , , 6LJQDOERDUG ', &38& '&'&'& ;31/$1 ' 3XOVHDQG GLUHFWLRQRXWSXWV LVVKRZQLQWKH 7,$SRUWDODV $[LV WHFKQRORJ\REMHFW '%[ &RQWUROOLQJ WKHKDUGZDUH &RQILJXUDWLRQ GDWD 0RGLILDEOH FRQILJXUDWLRQ GDWD &XUUHQW D[LVGDWD &XUUHQW D[LVGDWD 8VHUSURJUDP &38ILUPZDUH 6WDWXVDQGHUURU LQIRUPDWLRQRQ WKHDFWLYHMREV 6WDUWMREV 4330 WinCC Basic V13.0 System Manual, 02/2014 Using technology functions 11.2 Using S7-1200 Motion Control CPU hardware The physical drive is controlled and monitored by the CPU hardware. Drive The drive represents the unit of power unit and motor. Stepper motors or servo motors with a pulse interface may be used. Positioning axis technology object The physical drive including mechanics is mapped in the TIA Portal as a positioning axis technology object. To do this, configure the positioning axis technology object with the following parameters: Selection of the PTOs (Pulse Train Output) to be used and configuration of the drive interface Parameter for mechanics and gear transmission of the drive (or the machine or system) Parameter for position monitoring, for dynamic parameters and for homing The configuration of the positioning axis technology object is saved in the technology object (data block). This data block also forms the interface between the user program and the CPU firmware. The current axis data is saved in the data block of the technology object at the runtime of the user program. User program You start Motion Control instructions jobs in the CPU firmware with the user program. The following jobs for controlling the axis are possible: Enable and disable axis Position axis absolutely Position axis relatively Move axis with velocity set point Run axis commands as motion sequence (technology as of V2) Moving axes in jog mode Stop axis Reference axis; set reference point Change dynamic settings of axis Continuously read motion data of the axis Write tag of axis Acknowledge error You determine the command parameters with the input parameters of the Motion Control instructions and the axis configuration. The output parameters of the instruction give you up to date information about the status and any errors of the command. WinCC Basic V13.0 System Manual, 02/2014 4331 Using technology functions 11.2 Using S7-1200 Motion Control Before starting a command for the axis, you must enable the axis with the Motion Control instruction "MC_Power". You can read out configuration data and current axis data with the tags of the technology object. You can change individual, changeable tags of the technology object (e.g. the current acceleration) from the user program. You can also change the dynamic settings of the axis with the Motion Control instruction "MC_ChangeDynamic" and write additional configuration data with "MC_WriteParam". You can read the current motion status of the axis with the Motion Control instruction "MC_ReadParam". CPU firmware The motion control jobs started in the user program are processed in the CPU firmware. When using the axis control table, Motion Control jobs are triggered by operating the axis control table. The CPU firmware performs the following jobs depending on the configuration: Calculate the exact motion profile for motion jobs and emergency stop situations Control the drive enable and the pulse and direction signal Monitor the drive and the hardware and software limit switches Up to date feedback of status and error information to the Motion Control instructions in the user program Writing of current axis data into the data block of the technology object See also Tags of the positioning axis technology object as of V4 (Page 4446) CPU outputs relevant for motion control (technology version V4) (Page 4312) Relationship between the signal type and the direction of travel (Page 4315) Tools of the positioning axis technology object (Page 4333) Hardware and software limit switches (Page 4319) Homing (Page 4321) 4332 WinCC Basic V13.0 System Manual, 02/2014 Using technology functions 11.2 Using S7-1200 Motion Control 11.2.5.2 Tools of the positioning axis technology object The TIA Portal provides the "Configuration", "Commissioning", and "Diagnostics" tools for the positioning axis technology object. The following representation shows the interaction of the three tools with the technology object and the drive: 'ULYH 3RVLWLRQLQJD[LVWHFKQRORJ\REMHFW '%[ &RQILJXUDWLRQGDWD &RQILJXUDWLRQ &RPPLVVLRQLQJ SDUDPHWHUV &RPPLVVLRQLQJ D[LVFRQWURO SDQHO 6WDWXVDQG HUURULQIRUPDWLRQ 'LDJQRVWLFV Reading and writing of configuration data of the technology object; Drive control via the technology object; Reading axis status for display on the control panel Readout of the current status and error information of the technology object. WinCC Basic V13.0 System Manual, 02/2014 4333 Using technology functions 11.2 Using S7-1200 Motion Control Configuration Use the "Configuration" tool to configure the following properties of the positioning axis technology object: Selection of the PTO to be used and configuration of the drive interface Properties of the mechanics and the transmission ratio of the drive (or machine or system) Properties for position monitoring, dynamics, and homing Save the configuration in the data block of the technology object. Commissioning Use the "Commissioning" tool to test the function of your axis without having to create a user program. When the tool is started, the axis control table will be displayed. The following commands are available on the axis control table: Enabling and disabling the axis Move axis in jog mode Position axis in absolute and relative terms Home axis Acknowledge errors The dynamic values can be adjusted accordingly for the motion commands. The axis control table also shows the current axis status. Diagnostics Use the "Diagnostics" tool to keep track of the current status and error information for the axis and drive. See also CPU outputs relevant for motion control (technology version V4) (Page 4312) Relationship between the signal type and the direction of travel (Page 4315) Integration of the positioning axis technology object (Page 4330) Hardware and software limit switches (Page 4319) Homing (Page 4321) Configuring the positioning axis technology object (Page 4335) Commissioning the axis - Axis control panel (Page 4379) Axis - Diagnostics (Page 4418) 4334 WinCC Basic V13.0 System Manual, 02/2014 Using technology functions 11.2 Using S7-1200 Motion Control 11.2.5.3 Adding a positioning axis technology object Requirements A project with a CPU S7-1200 has been created. Procedure To add a positioning axis technology object in the project tree, follow these steps: 1. Open the "CPU > Technology objects" folder in the project tree. 2. Double-click the "Add new object" command. The "Add new object" dialog opens. 3. Select the "Motion Control" technology. 4. Open the "Motion Contro > S7-1200 Motion Control" folder. 5. Select the desired technology version in the "Version" column. 6. Select the "TO_PositioningAxis" object. 7. Enter the name of the axis in the "Name" input box. 8. To change the automatically assigned data block number, select the "Manual" option. 9. To display additional information about the technology object, click "Additional information". 10.Confirm your entry with "OK". Result The new technology object is created and saved to the "Technology objects" folder in the project tree. See also Guidelines on use of motion control (Page 4322) 11.2.5.4 Configuring the positioning axis technology object Working with the configuration dialog You configure the properties of the technology object in the configuration window. Proceed as follows to open the configuration window of the technology object: 1. Open the group of the required technology object in the project tree. 2. Double-click the "Configuration" object. The configuration is divided into the following categories: WinCC Basic V13.0 System Manual, 02/2014 4335 Using technology functions 11.2 Using S7-1200 Motion Control Basic parameters The basic parameters contain all the parameters which must be configured for a functioning axis. Extended parameters The advanced parameters include parameters to adapt to your drive or your plant. Configuration window icons Icons in the area navigation of the configuration show additional details about the status of the configuration: The configuration contains default values and is complete. The configuration contains only default values. With these default values you can use the technology object without additional changes. The configuration contains values set by the user and is complete. All input boxess of the configuration contain valid values and at least one preset value has changed. The configuration is incomplete or incorrect At least one input box or drop-down list contains an invalid value. The corresponding box or the drop-down list is displayed on a red background. Click the roll-out error message to indicate the cause of error. The configuration is valid but contains warnings For example, only one hardware limit switch is configured. Depending on the plant, the lacking configuration of a hardware limit switch may result in a hazard. The corresponding box or the drop-down list is displayed on a yellow background. See also Guidelines on use of motion control (Page 4322) Basic parameters (Page 4337) Extended parameters (Page 4339) Compare values The "Compare values" function provides the following options: Comparison of configured start values of the project with the start values in the CPU and the actual values Direct editing of actual values and the start values of the project Immediate detection and display of input errors with suggested corrections Backup of actual values in the project Transfer of start values of the project to the CPU as actual values 4336 WinCC Basic V13.0 System Manual, 02/2014 Using technology functions 11.2 Using S7-1200 Motion Control Icons and operator controls The following icons and operator controls are available: Icon Function Start value in CPU matches the configured Start value in the project Start value in CPU does not match the configured Start value in the project The comparison of the Start value in CPU with the configured Start value in the project cannot be performed Backs up the actual values in the project Transfers updated start values in the project to the CPU (initialize setting values) Opens the "Compare values" dialog Basic parameters Configuration - General (positioning axis technology object as of V4) Configure the basic properties of the positioning axis technology object in the "General" configuration window. Axis name Define the name of the axis or the name of the positioning axis technology object in this box. The technology object is listed under this name in the project navigation. Hardware interface The pulses are output to the power unit of the drive by fixed assigned digital outputs. In CPUs with relay outputs, the pulse signal cannot be output on these outputs because the relays do not support the necessary switching frequencies. A signal board with digital outputs must be used to enable you to work with the PTO (Pulse Train Output) on these CPUs. Note The PTO requires the functionality of a fast counter (HSC). An internal HSC is used for this, the count of which cannot be evaluated. Selecting the pulse generator In the drop-down list, select the PTO (Pulse Train Output) which is to provide the pulses for controlling the stepper motors or servo motors with pulse interface. If the pulse generators and high-speed counters are not used elsewhere in the device configuration, the hardware WinCC Basic V13.0 System Manual, 02/2014 4337 Using technology functions 11.2 Using S7-1200 Motion Control interface can be configured automatically. In this case, the PTO selected in the drop-down list is displayed with a white background. "Device configuration" button This button takes you to the settings for the pulse options in the device configuration of the CPU. Signal type Select the desired signal type in the drop-down list. The following signal types are available: PTO (pulse A and direction B) A pulse output and a direction output are used for controlling the stepper motor. PTO (count up A, count down B) One pulse output each for motion in positive direction and negative direction is used for controlling the stepper motor. PTO (A/B phase offset) Both pulse outputs for Phase A and for Phase B run at the same frequency. The period of the pulse outputs is evaluated at the drive end as a step. The phase offset between Phase A and Phase B determines the direction of the motion. PTO (A/B phase offset - quadruple) Both pulse outputs for Phase A and for Phase B run at the same frequency. All positive edges and all negative edges of Phase A and Phase B are evaluated as a step at the drive end. The phase offset between Phase A and Phase B determines the direction of the motion. Pulse output (signal type "PTO (pulse A and direction B)") Select the desired output for the pulse output in this box. You can select the output using a symbolic address or assign an absolute address. Activate direction output (signal type "PTO (pulse A and direction B)") You can deactivate and activate the direction output in "pulse and direction" mode. This option enables you to limit the motion direction. Direction output (signal type "PTO (pulse A and direction B)") Select the desired output for the direction output in this box. You can select the output using a symbolic address or assign an absolute address. Pulse output up (signal type "PTO (count up A, count down B)") Select the desired pulse output for motions in positive direction in this box. You can select the output using a symbolic address or assign an absolute address. 4338 WinCC Basic V13.0 System Manual, 02/2014 Using technology functions 11.2 Using S7-1200 Motion Control Pulse output down (signal type "PTO (count up A, count down B)") Select the desired pulse output for motions in negative direction in this box. You can select the output using a symbolic address or assign an absolute address. Phase A (signal types "PTO (A/B phase offset)" and "PTO (A/B phase offset - quadruple)") Select the desired pulse output for Phase A signals in this box. You can select the output using a symbolic address or assign an absolute address. Phase B (signal types "PTO (A/B phase offset)" and "PTO (A/B phase offset - quadruple)") Select the desired pulse output for Phase B signals in this box. You can select the output using a symbolic address or assign an absolute address. User unit Select the desired unit for the dimension system of the axis in the dropdown list. The selected unit is used for further configuration of the positioning axis technology object and for displaying the current axis data. The values at the input parameters (Position, Distance, Velocity, ...) of the Motion Control instructions also refer to this unit. Note Later changing of the dimension system may not be converted correctly in all the configuration windows of the technology object. In this case check the configuration of all axis parameters. The values of the input parameters of the Motion Control instructions may have to be adapted to the new unit of measurement in the user program. See also CPU outputs relevant for motion control (technology version V4) (Page 4312) Relationship between the signal type and the direction of travel (Page 4315) Configuration - General ("Axis" technology object V1...3) (Page 4470) Extended parameters Configuration - Drive interface Configure the output for drive enable and the input for the "Drive ready" feedback signal of the drive in the "Drive signals" configuration window. Drive enable is controlled by Motion Control instruction "MC_Power" and enables power to the drive. The signal is provided to the drive via the output to be configured. WinCC Basic V13.0 System Manual, 02/2014 4339 Using technology functions 11.2 Using S7-1200 Motion Control The drive signals "Drive ready" to the CPU if it is ready to start executing travel after receipt of drive enable. The "Drive ready" signal is reported back to the CPU via the input to be configured. If the drive does not have any interfaces of this type, you will not have to configure the parameters. In this case, select the value TRUE for the ready input. See also Configuration - Mechanics (Page 4340) Position limits (Page 4341) Dynamics (Page 4345) Homing (positioning axis technology object as of V2) (Page 4352) Configuration - Mechanics Configure the mechanical properties of the drive in the "Mechanics" configuration window. Increments per motor revolution Configure the number of pulses required for one revolution of the motor in this box. Limits (independent of the selected unit of measurement): 0 < Pulse per motor revolution 2147483647 Distance per revolution In this box, configure the load distance per motor revolution covered by the mechanical system of your unit. Limits (independent of the selected unit of measurement): 0.0 < Distance per revolution 1.0e12 Permitted direction of rotation (technology version as of V4) Configure this box to determine whether the mechanics of your system are to move in both directions or only in the positive or negative direction. If you have not activated the direction output of the pulse generator in the "PTO (pulse A and direction B)" mode, the selection is limited to the positive or negative direction. Invert direction You can use the "Invert direction" check box to adapt the control system to the direction logic of the drive. The direction logic is inverted according to the selected mode of the pulse generator: 4340 WinCC Basic V13.0 System Manual, 02/2014 Using technology functions 11.2 Using S7-1200 Motion Control PTO (pulse A and direction B) - 0 V at direction output positive direction of rotation - 5 V/24 V at direction output negative direction of rotation The specified voltage depends on the hardware used. The indicated values do not apply to the differential outputs of CPU 1217. PTO (count up A, count down B) The outputs "Pulse output down" and "Pulse output up" are swapped. PTO (A/B phase offset) The "Phase A" and "Phase B" outputs are swapped. "PTO (A/B phase offset - quadruple) The "Phase A" and "Phase B" outputs are swapped. See also Configuration - Drive interface (Page 4339) Position limits (Page 4341) Dynamics (Page 4345) Homing (positioning axis technology object as of V2) (Page 4352) Relationship between the signal type and the direction of travel (Page 4315) Position limits Requirements for hardware limit switches Use only hardware limit switches that remain permanently switched after being approached. This switching status may only be revoked after a return to the valid travel range. See also Configuration - Position limits (Page 4341) Behavior of axis when position limits is tripped (Page 4343) Changing the position limits configuration in the user program (Page 4344) Configuration - Position limits Configure the hardware and software limit switches of the axis in the "Position limits" configuration window. Enable hardware limit switch Activate the function of the low and upper hardware limit switch with this check box. The hardware limit switches can be used for purposes of direction reversal during a homing procedure. For details, refer to the configuration description for homing. WinCC Basic V13.0 System Manual, 02/2014 4341 Using technology functions 11.2 Using S7-1200 Motion Control Lower / upper HW limit switch input Select the digital input for the low or upper hardware limit switch from the drop-down list. The input must be interrupt-capable. The digital onboard CPU inputs and the digital inputs of a plugged signal board can be selected as inputs for the HW limit switches. Note The digital inputs are set to a filter time of 6.4 ms by default. If these are used as hardware limit switches, undesired decelerations may occur. If this occurs, reduce the filter time for the relevant digital inputs. The filter time can be set under "Input filter" in the device configuration of the digital inputs. Active level In the drop-down list, select the signal level available at the CPU when the hardware limit switch is approached. "Lower level" selected 0 V (FALSE) at CPU input corresponds to hardware limit switch approached "High level" selected 5 V / 24 V (TRUE) at the CPU input = hardware limit switch approached (the actual voltage depends on the hardware used) Enable software limit switch Activate the function of the low and upper software limit switch with this check box. Note The enabled software limit switch only affects a homed axis. High and lower software limit switch Enter the position value of the low and upper software limit switch in these boxes. Limits (independent of the selected unit of measurement): -1.0e12 lower software limit switch 1.0e12 -1.0e12 upper software limit switch 1.0e12 The value of the upper software limit switch must be greater than or equal to the value of the lower software limit switch. See also Requirements for hardware limit switches (Page 4341) Behavior of axis when position limits is tripped (Page 4343) 4342 WinCC Basic V13.0 System Manual, 02/2014 Using technology functions 11.2 Using S7-1200 Motion Control Changing the position limits configuration in the user program (Page 4344) Configuration - Homing - Active (Page 4353) Behavior of axis when position limits is tripped Behavior of axis when hardware limit switches are approached When the hardware limit switches are approached, the axis brakes to a standstill at the configured emergency stop deceleration. The specified emergency stop deceleration must be sufficient to reliably stop the axis before the mechanical stop. The following diagram presents the behavior of the axis after it approaches the hardware limit switches: _Y_ V SHUPLWWHGWUDYHOUDQJH V PHFKDQLFDO VWRS ORZHU +:OLPLWVZLWFK XSSHU +:OLPLWVZLWFK PHFKDQLFDO VWRS The axis brakes to a standstill at the configured emergency stop deceleration. Range in which the HW limit switches signal the status "approached". The "HW limit switch approached" error is displayed in the motion control instruction to be initiated, in "MC_Power", and in the technology object tags. Instructions for eliminating errors can be found in the Appendix under "List of ErrorIDs and ErrorInfos". Behavior of axis when software limit switches are reached If software limit switches are activated, an active motion is stopped at the position of the software limit switch. The axis is braked at the configured deceleration. The following diagram presents the behavior of the axis until it reaches the software limit switches: WinCC Basic V13.0 System Manual, 02/2014 4343 Using technology functions 11.2 Using S7-1200 Motion Control :RUNLQJUDQJH _Y_ V /RZ 6:OLPLWVZLWFK +LJK 6:OLPLWVZLWFK The axis brakes to a standstill at the configured deceleration. The "SW limit switch approached" error is displayed in the initiating Motion Control instruction, at "MC_Power", and in the technology object tags. Instructions for eliminating errors can be found in the Appendix under "List of ErrorIDs and ErrorInfos". You can learn about the circumstances that can lead to exceeding the software limit switches in the sections "Software limit switches in conjunction with a homing operation (Page 4429)" and "Software limit switches in conjunction with dynamic changes (Page 4434)". Use additional hardware limit switches if a mechanical endstop is located after the software limit switches and there is a risk of mechanical damage. See also Requirements for hardware limit switches (Page 4341) Configuration - Position limits (Page 4341) Changing the position limits configuration in the user program (Page 4344) Changing the position limits configuration in the user program You can change the following configuration parameters during runtime of the user program in the CPU: Hardware limit switches You can also activate and deactivate the hardware limit switches during runtime of the user program. Use the following technology object tag for this purpose: <Axis name>.PositionLimitsHW.Active Refer to the description of the technology object tags (Page 4446) in the appendix for information on when changes to the configuration parameter take effect. 4344 WinCC Basic V13.0 System Manual, 02/2014 Using technology functions 11.2 Using S7-1200 Motion Control Software limit switches You can also activate and deactivate the software limit switches and change their position values during runtime of the user program. Use the following technology object tags for this purpose: <Axis name>.PositionLimitsSW.Active for activating and deactivating the software limit switches <Axis name>.PositionLimitsSW.MinPosition for changing the position of the lower software limit switch <Axis name>.PositionLimitsSW.MaxPosition for changing the position of the upper software limit switch Refer to the description of technology object tags in the appendix for information on when changes to the configuration parameters take effect. See also Compatibility list of tags (Page 4325) MC_ChangeDynamic: Change dynamic settings of axis V4 (Page 2848) Requirements for hardware limit switches (Page 4341) Configuration - Position limits (Page 4341) Behavior of axis when position limits is tripped (Page 4343) Dynamics Configuration - General dynamics Configure the maximum velocity, the start/stop velocity, the acceleration and deceleration, and the jerk limit (positioning axis technology object as of V2) of the axis in the "General dynamics" configuration window. Velocity limiting unit Select the unit of measurement with which you want to set the velocity limits in the dropdown list. The unit set here depends on the unit of measurement set under "Configuration - General" and serves only for easier input. Maximum velocity / Start/stop velocity Define the maximum permissible velocity and the start/stop velocity of the axis in these boxes. The start/stop velocity is the minimum permissible velocity of the axis. Limit values: The limits indicated below refer to the "Pulses/s" unit of measurement: WinCC Basic V13.0 System Manual, 02/2014 4345 Using technology functions 11.2 Using S7-1200 Motion Control Positioning axis technology object V4 - 1 start/stop velocity 20000 (signal board 20 kHz) 1 start/stop velocity 200000 (signal board 200 kHz) 1 start/stop velocity 100000 (on-board CPU outputs 100 kHz) 1 start/stop velocity 30000 (on-board CPU outputs 30 kHz) 1 start/stop velocity 1000000 (on-board CPU outputs 1 MHz CPU 1217) - 1 maximum velocity 20000 (signal board 20 kHz) 1 maximum velocity 200000 (signal board 200 kHz) 1 maximum velocity 100000 (on-board CPU outputs 100 kHz) 1 maximum velocity 30000 (on-board CPU outputs 30 kHz) 1 maximum velocity 1000000 (on-board CPU outputs 1 MHz CPU 1217) You can learn about the limits for the technology object positioning axis < V4 in the appendix Outputs of the CPU relevant for Motion Control (technology version V1...3) (Page 4466). The value of the maximum velocity must be greater or equal to the value of the start/stop velocity. The limits for other units of measurement must be converted by the user to conform to the given mechanics. Acceleration / Delay - Ramp-up time / Ramp-down time Set the desired acceleration in the "Ramp-up time" or "Acceleration" boxes. The desired deceleration can be set in the "Deceleration time" or "Deceleration" boxes. The relation between the ramp-up time and acceleration and the deceleration time and deceleration is shown in the following equations: Rampup time = Deceleration time = Maximum velocity - Start/stop velocity Acceleration Maximum velocity - Start/stop velocity Deceleration Motion jobs started in the user program are performed with the selected acceleration / deceleration. The limits for acceleration and deceleration can be found in section Hardware components for motion control (Page 4310). Note Changes to the velocity limits ("start/stop velocity" and "maximum velocity") influence the acceleration and deceleration values of the axis. The ramp-up and deceleration times are retained. 4346 WinCC Basic V13.0 System Manual, 02/2014 Using technology functions 11.2 Using S7-1200 Motion Control Activate the jerk limit (positioning axis technology object as of V2) Activate the jerk limit with this check box. Note If an error occurs, the axis decelerates with the configured emergency stop deceleration. An activated jerk limit is not considered here. Smoothing time / jerk (positioning axis technology object as of V2) You can input the parameters of the jerk limit in the "Smoothing time" box or alternatively in the "Jerk" box. Set the desired jerk for acceleration and deceleration ramp in the "Jerk" box. Set the desired smoothing time for the acceleration ramp in the "Rounding time" box. Note Smoothing time V2...3 The set smoothing time visible in the configuration only applies to the acceleration ramp. If the values for acceleration and deceleration differ, the smoothing time of the deceleration ramp is calculated according to the jerk of the acceleration ramp and used. (See also Behavior of the axis when using the jerk limit (Page 4350) The smoothing time of the deceleration is adapted as follows: Acceleration > deceleration The smoothing time used for the deceleration ramp is shorter than that for the acceleration ramp. Acceleration < deceleration The smoothing time used for the deceleration ramp is greater than that for the acceleration ramp. Acceleration = deceleration The smoothing times of the acceleration and deceleration ramp are equal. The relation between smoothing times and jerk is shown in the following equation: 5RXQGLQJRIIWLPH DFFHOHUDWLRQUDPS 5RXQGLQJRIIWLPH GHFHOHUDWLRQUDPS $FFHOHUDWLRQ -HUN 'HFHOHUDWLRQ -HUN Motion jobs started in the user program are performed with the selected jerk. WinCC Basic V13.0 System Manual, 02/2014 4347 Using technology functions 11.2 Using S7-1200 Motion Control The limits for the jerk can be found in section Hardware components for motion control (Page 4310). See also Behavior of the axis when using the jerk limit (Page 4350) Hardware components for motion control (Page 4310) Configuration - Dynamics emergency stop (Page 4348) Changing the configuration of dynamics in the user program (Page 4351) Configuration - Dynamics emergency stop Configure the emergency stop deceleration of the axis in the "Dynamics emergency stop" configuration window. In the event of an error, and when disabling the axis, the axis is brought to a standstill with this deceleration using the Motion Control instruction "MC_Power" (input parameter StopMode = 0 or 2). Velocity limits The velocity values configured in the "General dynamics" configuration window are once again displayed in this information area. Deceleration Set the deceleration value for emergency stop in the "Emergency stop deceleration" or "Emergency stop ramp-down time" field. The relation between emergency stop deceleration time and emergency stop deceleration is shown in the following equation: Emergency stop ramp-down = Maximum velocity - Start/stop velocity Emergency stop deceleration The specified emergency stop deceleration must be sufficient to bring the axis to a standstill in a timely manner in the event of an emergency (for example, when the hardware limit switch is approached prior to reaching the mechanical endstop). The configured maximum velocity of the axis must be used as a basis for selecting the emergency stop deceleration. Limit values: The limits indicated below refer to the "Pulses/s2" unit of measurement: As of CPU firmware V3 0.005 emergency stop deceleration 9.5E9 CPU Firmware V1...2 0.28 emergency stop deceleration 9.5E9 The limits for other units of measurement must be converted to conform to the given mechanics. 4348 WinCC Basic V13.0 System Manual, 02/2014 Using technology functions 11.2 Using S7-1200 Motion Control See also Configuration - General dynamics (Page 4345) Changing the configuration of dynamics in the user program (Page 4351) WinCC Basic V13.0 System Manual, 02/2014 4349 Using technology functions 11.2 Using S7-1200 Motion Control Behavior of the axis when using the jerk limit Axis acceleration and deceleration is not stopped abruptly when the jerk limit is activated; it is adjusted gently according to the set step or smoothing time. The diagram below details the behavior of the axis with and without activated jerk limit: Without jerk limit With jerk limit Y Y W W D D W W M M W W W WUX WD WUG WG W WUX WD t Time axis v Velocity a Acceleration 4350 W W WUG WG WinCC Basic V13.0 System Manual, 02/2014 Using technology functions 11.2 Using S7-1200 Motion Control j Jerk tru Rampup time ta Time taken for the axis to accelerate trd Deceleration time td Time taken for the axis to decelerate t1 Smoothing time of the acceleration ramp t2 Smoothing time of the deceleration ramp The example shows travel in which the deceleration value is twice the acceleration value . The resulting ramp-down time trd is therefore only half the length of the ramp-up time tru. Acceleration and deceleration change abruptly without a jerk limit. Acceleration and deceleration change gradually with activated jerk limiter. As the jerk applies to entire motion, the rate is the same for the increase and decrease in acceleration and deceleration. The step value j becomes infinitely high as soon as the change is made without jerk limit. The step is limited to the configured value when the jerk limit is activated. The smoothing time t1 given in the configuration applies to the acceleration ramp. The deceleration ramp smoothing time t2 is calculated from the configured jerk value and the configured deceleration. See also Configuration - General dynamics (Page 4345) Changing the configuration of dynamics in the user program You can change the following configuration parameters during runtime of the user program in the CPU: Acceleration and deceleration You can also change the values for acceleration and deceleration during runtime of the user program. Use the following technology object tags for this purpose: <Axis name>.DynamicDefaults.Acceleration for changing acceleration <Axis name>.DynamicDefaults.Deceleration for changing deceleration Refer to the description of the technology object tags (Page 4446) in the appendix for information on when changes to the configuration parameters take effect. WinCC Basic V13.0 System Manual, 02/2014 4351 Using technology functions 11.2 Using S7-1200 Motion Control Emergency stop deceleration You can also change the value for the emergency stop deceleration during runtime of the user program. Use the following technology object tag for this purpose: <Axis name>.DynamicDefaults.EmergencyDeceleration Refer to the description of the technology object tags in the appendix for information on when changes to the configuration parameter take effect. Note After changes to this parameter, it may be necessary to adapt the positions of the hardware limit switches and other safety-relevant settings. Jerk limit You can also activate and deactivate the jerk limit at runtime of the user program and change the value for the jerk. To do this, use the technology object tag <Axis name>.DynamicDefaults.Jerk. If you enter a value > 0.004 pulse/s3 for the jerk, the jerk limit is activated with the specified value. If you enter a value = 0.0 for the jerk, the jerk limit is deactivated. Refer to the description of the technology object tags in the appendix for information on when changes to the configuration parameter take effect. See also Changing configuration of dynamic values in user program ("Axis" technology object V1...3) (Page 4472) Compatibility list of tags (Page 4325) MC_ChangeDynamic: Change dynamic settings of axis V4 (Page 2848) Configuration - General dynamics (Page 4345) Configuration - Dynamics emergency stop (Page 4348) Homing (positioning axis technology object as of V2) Configuration - Homing - Passive Configure the necessary parameters for passive homing in the "Homing - Passive" configuration window. The movement for passive homing must be triggered by the user (e.g. using an axis motion command). Passive homing is started using Motion Control instruction "MC_Home" with input parameter "Mode" = 2. 4352 WinCC Basic V13.0 System Manual, 02/2014 Using technology functions 11.2 Using S7-1200 Motion Control Homing switch input Select the digital input for the homing switch from the drop-down list. The input must be interrupt-capable. The on-board CPU inputs and the inputs of an inserted signal board can be selected as inputs for the homing switch. Note The digital inputs are set to a filter time of 6.4 ms by default. When the digital inputs are used as a homing switch, this can result in undesired decelerations and thus inaccuracies. Depending on the homing velocity and extent of the homing switch, the home position may not be detected. The filter time can be set under "Input filter" in the device configuration of the digital inputs. The specified filter time must be less than the duration of the input signal at the homing switch. Active level In the drop-list, select the level of the homing switch that is to be used for homing. Side of the homing switch This is where you select whether the axis is to be homed on the low or high end of the homing switch. Home position The position configured in the Motion Control instruction "MC_Home" is used as the home position. Note If passive homing is carried out without an axis motion command (axis at a standstill), homing will be executed upon the next rising or falling edge at the homing switch. Configuration - Homing - Active Configure the necessary parameters for active homing in the "Active homing" configuration window. Active homing is started using Motion Control instruction "MC_Home" with input parameter "Mode" = 3. WinCC Basic V13.0 System Manual, 02/2014 4353 Using technology functions 11.2 Using S7-1200 Motion Control Homing switch input Select the digital input for the homing switch from the drop-down list. The input must be interrupt-capable. The on-board CPU inputs and the inputs of an inserted signal board can be selected as inputs for the homing switch. Note The digital inputs are set to a filter time of 6.4 ms by default. When the digital inputs are used as a homing switch, this can result in undesired decelerations and thus inaccuracies. Depending on the homing velocity and extent of the homing switch, the home position may not be detected. The filter time can be set under "Input filter" in the device configuration of the digital inputs. The specified filter time must be less than the duration of the input signal at the homing switch. Active level In the drop-list, select the level of the homing switch that is to be used for homing. Allowing direction reversal at the hardware limit switch Activate the check box to use the hardware limit switch as a reversing cam for the homing procedure. The hardware limit switches must be enabled for the reversal of direction (at least the hardware limit switch in the direction of approach must be configured). If the hardware limit switch is reached during active homing, the axis brakes at the configured deceleration (not with the emergency stop deceleration) and reverses direction. The homing switch is then sensed in reverse direction. If the direction reversal is not active and the axis reaches the hardware limit switch during active homing, the homing procedure is aborted with an error and the axis is braked at the emergency stop deceleration. Note If possible, use one of the following measures to ensure that the machine does not travel to a mechanical endstop in the event of a direction reversal: Keep the approach velocity low. Increase the configured acceleration/deceleration. Increase the distance between the hardware limit switch and the mechanical endstop. Approach/homing direction With the direction selection, you determine the approach direction used during active homing to search for the homing switch, as well as the homing direction. The homing direction specifies the travel direction the axis uses to approach the configured end of the homing switch to carry out the homing operation. 4354 WinCC Basic V13.0 System Manual, 02/2014 Using technology functions 11.2 Using S7-1200 Motion Control Side of the homing switch This is where you select whether the axis is to be homed on the low or high end of the homing switch. Approach velocity In this box, specify the velocity at which the homing switch is to be searched for during the homing procedure. Limits (independent of the selected unit of measurement): Start/stop velocity approach velocity maximum velocity Homing velocity In this box, specify the velocity at which the homing switch is to be approached for homing. Limits (independent of the selected unit of measurement): Start/stop velocity Homing velocity Maximum velocity Home position offset If the desired home position deviates from the position of the homing switch, the home position offset can be specified in this box. If the value does not equal 0, the axis executes the following actions following homing at the homing switch: 1. Move the axis at the homing velocity by the value of the home position offset 2. Upon reaching the "home position offset", the axis is at the home position that was specified in input parameter "Position" of the "MC_Home" Motion Control instruction. Limits (independent of the selected unit of measurement): -1.0e12 home position offset 1.0e12 Home position The position configured in the Motion Control instruction "MC_Home" is used as the home position. Sequence - Passive homing Passive homing is started with Motion Control instruction "MC_Home" (input parameter Mode = 2). Input parameter "Position" specifies the absolute reference point position. The diagram below shows an example of a characteristic curve for passive homing with the following configuration parameters: WinCC Basic V13.0 System Manual, 02/2014 4355 Using technology functions 11.2 Using S7-1200 Motion Control "Reference point switch side" = "High side" Y 7UDYHOLQSRVLWLYH GLUHFWLRQ V 7UDYHOLQQHJDWLYHGLUHFWLRQ 0RYHPHQWEHIRUHWKH UHIHUHQFHSRLQWVZLWFK 5HIHUHQFHSRLQWSRVLWLRQ 0RYHPHQWEDVHGRQ UHIHUHQFHSRLQWVZLWFK Movement towards reference point switch (red section of curve) The Motion Control instruction "MC_Home" does not itself carry out any homing motion when passive homing is started. The travel required for reaching the reference point switch must be implemented by the user via other motion control instructions such as "MC_MoveRelative". The tag <axis name>.StatusBits.HomingDone remains TRUE during passive homing if the axis has already been homed. Axis homing (transition from red to green section of curve) The axis is homed when the configured side of the reference point switch is reached. The current position of the axis is set to the reference point position. This is specified at the "Position" parameter of the "MC_Home" Motion Control instruction. The variable <axis name>.StatusBits.HomingDone will be set to "TRUE" if the axis has not been been homed before. The travel previously started is not cancelled. Movement beyond reference point switch (green section of curve) Following homing at the reference point switch, the axis continues and completes the previously started travel with the corrected axis position. 4356 WinCC Basic V13.0 System Manual, 02/2014 Using technology functions 11.2 Using S7-1200 Motion Control Sequence - Active homing You start active homing with motion control instruction "MC_Home" (input parameter Mode = 3). The "Position" input parameter specifies the absolute home position. Alternatively, you can start active homing on the axis command table for test purposes. The diagram below shows an example of a characteristic curve for an active reference point approach with the following configuration parameters: "Approach/homing direction" = "Positive direction" "Side of the homing switch" = "Top side" Value of "home position offset" > 0 Y $SSURDFKYHORFLW\ +RPLQJYHORFLW\ V 5HIHUHQFHSRLQWSRVLWLRQ 5HIHUHQFHSRLQWRIIVHW Search for homing switch (blue curve section) When active homing starts, the axis accelerates to the configured "approach velocity" and searches at this velocity for the homing switch. The tag <axis name>.StatusBits.HomingDone is set to FALSE. Reference point approach (red curve section) When the homing switch is detected, the axis in this example brakes and reverses, to be homed to the configured side of the homing switch at the configured homing velocity. Homing causes the tag <axis name>.StatusBits.HomingDone to change to TRUE. Travel to home position offset (green curve segment) After homing, the axis moves at the homing velocity along the path to the home position offset. There the axis is at the homing point position that was specified in input parameter "Position" of the "MC_Home" Motion Control instruction. WinCC Basic V13.0 System Manual, 02/2014 4357 Using technology functions 11.2 Using S7-1200 Motion Control See also Configuration - Homing - General (Axis technology object V2...3) (Page 4476) Changing the homing configuration in the user program With positioning axis technology object as of V2, you can change the following configuration parameters during runtime of the user program in the CPU: Passive homing You can change the end of the homing switch for passive homing during the user program runtime. Use the following technology object tag for this purpose: <Axis name>.Sensor[1].PassiveHoming.SideInput for changing the end of the homing switch Refer to the description of the technology object tags (Page 4446) in the appendix for information on when changes to the configuration parameter take effect. Active homing You can change the direction of approach, the end of the homing switch, the approach velocity, the homing velocity, and the home position offset for active homing during the program runtime of the user program. Use the following technology object tags for this purpose: <Axis name>.Homing.AutoReversal for changing the auto reverse at the HW limit switch <Axis name>.Homing.ApproachDirection for changing the approach/homing direction <Axis name>.Sensor[1].ActiveHoming.SideInput for changing the end of the homing switch <Axis name>.Homing.ApproachVelocity for changing the approach velocity <Axis name>.Homing.ReferencingVelocity for changing the homing velocity <Axis name>.Sensor[1].ActiveHoming.HomePositionOffset for changing the home position offset Refer to the description of the technology object tags in the appendix for information on when changes to the configuration parameter take effect. See also Compatibility list of tags (Page 4325) MC_ChangeDynamic: Change dynamic settings of axis V4 (Page 2848) 4358 WinCC Basic V13.0 System Manual, 02/2014 Using technology functions 11.2 Using S7-1200 Motion Control 11.2.6 Technology object command table 11.2.6.1 Use of the command table technology object The Motion Control instruction "Command table" allows you to combine multiple individual axis control commands in one movement sequence. The technology object can be used with technology version as of V2. You configure the movement sequence as a table in a configuration dialog. The motion profile of the movement sequences can be checked on a graph before the project is loaded to the CPU. The command tables created are then linked to an axis and used in the user program with the "MC_CommandTable" Motion Control instruction. You can process part or all of the command table. 11.2.6.2 Command table technology object tools The "Configuration" tool is provided in the TIA Portal for the "Command Table" technology object. The representation below shows the interaction of the tool with the technology object: 7HFKQRORJLFDOREMHFW &RPPDQGWDEOH '%[ &RQILJXUDWLRQGDWD &RQILJXUDWLRQ Writing and reading the configuration of the technology object WinCC Basic V13.0 System Manual, 02/2014 4359 Using technology functions 11.2 Using S7-1200 Motion Control Configuration Configure the following properties of the "Command Table" technology object with the "Configuration" tool: You can create one or more movement sequences by configuring individual jobs. You can configure the graphic display to check your movement sequence using an axis already configured or a configurable default axis. The movement sequence data are saved in the data block of the technology object. 11.2.6.3 Adding the technological object command table Requirements A project with a CPU S7-1200 has been created. The CPU firmware version is V2.1 or higher Procedure Proceed as follows to add a "Command table" technology object in the project tree: 1. Open the "CPU > Technology objects" folder in the project tree. 2. Double-click the "Add new object" command. The "Add new object" dialog opens. 3. Select the "Motion Control" technology. 4. Open the "Motion Contro > S7-1200 Motion Control" folder. 5. Select the desired technology version in the "Version" column. 6. Select the "TO_CommandTable" object. 7. Enter the name of the command table in the "Name" input box. 8. To change the automatically assigned data block number, select the "Manual" option. 9. To display additional information about the technology object, click "Additional information". 10.Confirm your entry with "OK". Result The new technology object is created and saved to the "Technology objects" folder in the project tree. 4360 WinCC Basic V13.0 System Manual, 02/2014 Using technology functions 11.2 Using S7-1200 Motion Control 11.2.6.4 Configuring the command table technology object Working with the configuration dialog You configure the properties of the technology object in the configuration window. Proceed as follows to open the configuration window of the technology object: 1. Open the group of the required technology object in the project tree. 2. Double-click the "Configuration" object. The configuration is divided into the following categories: Basic parameters The basic parameters contain all parameters which must be configured for a functional command table. Extended parameters The extended parameters contain the parameters of the default axis or display the parameter values of the axis selected. Configuration window icons Icons in the area navigation of the configuration show additional details about the status of the configuration: The configuration contains default values and is complete. The configuration contains only default values. With these default values, you can use the technology object without additional changes. The configuration contains values set by the user and is complete. All input fields of the configuration contain valid values and at least one preset value has changed. The configuration is incomplete or incorrect At least one input field or drop-down list contains an invalid value. The corresponding field or the drop-down list is displayed on a red background. Click the roll-out error message to display the cause of the error. The configuration contains mutually incompatible parameter values The configuration contains parameter values that contradict each other either in size or logic. The corresponding field or the drop-down list is displayed on a yellow background. See also Guidelines on use of motion control (Page 4322) Basic parameters (Page 4362) Extended parameters (Page 4375) WinCC Basic V13.0 System Manual, 02/2014 4361 Using technology functions 11.2 Using S7-1200 Motion Control Compare values The "Compare values" function provides the following options: Comparison of configured start values of the project with the start values in the CPU and the actual values Direct editing of actual values and the start values of the project Immediate detection and display of input errors with suggested corrections Backup of actual values in the project Transfer of start values of the project to the CPU as actual values Icons and operator controls The following icons and operator controls are available: Icon Function Start value in CPU matches the configured Start value in the project Start value in CPU does not match the configured Start value in the project The comparison of the Start value in CPU with the configured Start value in the project cannot be performed Backs up the actual values in the project Transfers updated start values in the project to the CPU (initialize setting values) Opens the "Compare values" dialog Basic parameters Configuration - General Configure the name of the technology object in the "General" configuration window. Name Define the name of the command table or the name of the "Command table" technology object in this field. The technology object will be listed under this name in the project tree. See also Configuration - Command table (Page 4363) Shortcut menu commands - Command table (Page 4366) Working with the trend diagram (Page 4367) Shortcut menu commands - Curve chart (Page 4371) 4362 WinCC Basic V13.0 System Manual, 02/2014 Using technology functions 11.2 Using S7-1200 Motion Control Transition from "Complete command" to "Blend motion" (Page 4372) Changing the command table configuration in the user program (Page 4374) Configuration - Command table Create the desired movement sequence in the "Command Table" configuration window and check the result against the graphic view in the trend diagram. Note Small deviations are possible between the time behavior and position in the trend shown and the real movement of the axis. Movements in response to software limit switches being reached are not shown. Activate warnings Activate the display of warnings in the command table with this checkbox. Use axis parameters of From the drop-down list, select which axis parameters are to be used for selecting the graphic view of and checking the movement sequence. Select "Default axis" if you have yet to add an axis to the "Technology object" folder or wish to use value which have not been configured in any of the available axes. You configure the properties of the default axis under "Advanced parameters". The axis parameters of the axis selected at the "Axis" parameter are used to process the command table in the user program. Column: Step Shows the step number of the command. Column: Command type In this column, select the command types which are to be used for processing the command table. Up to 32 commands can be entered. The commands will be processed in sequence. You can choose between the following entries and command types: Empty The entry serves as a placeholder for any commands to be added. The empty entry is ignored when the command table is processed. Halt Stop axis (the command only takes effect after a "Velocity set point" command) Positioning Relative Position axis relatively WinCC Basic V13.0 System Manual, 02/2014 4363 Using technology functions 11.2 Using S7-1200 Motion Control Positioning Absolute Position axis absolutely Velocity set point Move axis at set velocity Wait Waits until the given period is over. Wait does not stop active traversing. Separator Adds a Separator line above the selected line. The Separator line acts as a range limit for the graphic display of the trend view. Use the Separator lines if you wish to process parts of the command table. Column: Position Enter the position or travel path for the selected command in this column: Command "Positioning Relative" The command will move the axis by the the given travel path. Command "Positioning Absolute" The command will move the axis by the the given position. Separator The value given specifies the start position for the graphic display. Limit values (independent of the selected user unit): -1.0e12 position / distance -1.0e-12 1.0e-12 position / distance 1.0e12 Position / travel path = 0.0 Column: Velocity In this column, you enter the velocity for the selected command: Command "Positioning Relative" The command will move the axis at the the given velocity. The given velocity will not be reached if the travel path selected is not large enough. Command "Positioning Absolute" The command will move the axis at the the given velocity. The given velocity will not be reached if the target position is too close to the starting position. Command " Velocity set point" The command will move the axis at the the given velocity. The given velocity will not be reached during the command if too short a runtime is selected. Limit values (independent of the selected user unit): 4364 WinCC Basic V13.0 System Manual, 02/2014 Using technology functions 11.2 Using S7-1200 Motion Control For the commands: "Positioning Relative" and "Positioning Absolute" - 1.0e-12 velocity 1.0e12 For the command: "Velocity set point" - -1.0e12 velocity -1.0e-12 - 1.0e-12 velocity 1.0e12 - Velocity = 0.0 Column: Duration Enter the duration of the selected command in this column: Command " Velocity set point" The command will move the axis for the specified duration. The duration includes both the acceleration phase and the constant travel phase. The next command will be processed once the duration is over. Command "Wait" Waits until the given duration is over. Limit values (independent of the selected user unit): 0.001s duration 64800s Column: Next step Select the mode of transition to the next step from the drop-down list: Complete command The command will be completed. The next command will be processed immediately. Blend motion The motion of the current command will be blended with the motion of the following command. The transition mode "Blend motion" is available with command types "Positioning Relative" and "Positioning Absolute". Motion will be blended with motions of the following command types: - Positioning Relative - Positioning Absolute - Velocity set point No blending occurs with other command types. For the exact behavior of the axis when a command is appended or overlapped, see: Transition from "Complete command" to "Blend motion" (Page 4372) Column: Step code Enter a numerical value / bit pattern in this column which is to be output at the "StepCode" output parameter of the "MC_CommandTable" Motion Control instruction while the command is being processed. Limit values: WinCC Basic V13.0 System Manual, 02/2014 4365 Using technology functions 11.2 Using S7-1200 Motion Control 0 code number 65535 See also Configuration - General (Page 4362) Shortcut menu commands - Command table (Page 4366) Working with the trend diagram (Page 4367) Shortcut menu commands - Curve chart (Page 4371) Transition from "Complete command" to "Blend motion" (Page 4372) Changing the command table configuration in the user program (Page 4374) Shortcut menu commands - Command table The following shortcut menu commands are available in the command table: Insert empty line Adds an empty line above the selected line. This shortcut menu command can only be executed if there are enough empty lines at the end of the command table. Add empty line Adds an empty line below the selected line. This shortcut menu command can only be executed if there are enough empty lines at the end of the command table. Insert separator line Adds a separator line above the selected line. You cannot have two consecutive separator lines. Add separator line Adds a separator line below the selected line. You cannot have two consecutive separator lines, nor can you add a separator line at the end of the command table. Cut Removes the selected lines or content of the selected cell and saves them/it in the clipboard. Selected lines will be deleted and the subsequent lines of the command table shifted up. 4366 WinCC Basic V13.0 System Manual, 02/2014 Using technology functions 11.2 Using S7-1200 Motion Control Copy Copies the selected lines or content of the selected cell and saves them/it in the clipboard. Paste Selected lines: Pastes the lines from the clipboard into the table above the selected line. Selected cell: Pastes the content of the clipboard into the selected line. This shortcut menu command can only be executed if there are enough empty lines at the end of the command table. Replace Replaces the selected lines with the lines in the clipboard. Delete Deletes the selected lines. The lines below in the command table shift up. See also Configuration - General (Page 4362) Configuration - Command table (Page 4363) Working with the trend diagram (Page 4367) Shortcut menu commands - Curve chart (Page 4371) Transition from "Complete command" to "Blend motion" (Page 4372) Changing the command table configuration in the user program (Page 4374) Working with the trend diagram The following tools and information are available in the trend view. WinCC Basic V13.0 System Manual, 02/2014 4367 Using technology functions 11.2 Using S7-1200 Motion Control Trend view and components Trend view Position curve Velocity curve Curve section of a selected command Ruler Ruler position marking Software limit switch position Start/stop velocity Position axis scale range Time axis scale range Velocity axis scale range Scroll bar, position axis Scroll bar time axis Scroll bar, velocity axis Selecting the grid Selecting separator sections If the command table consists of multiple sections separated by separators, you can select these sections in the trend view by selecting a command in the section. 4368 WinCC Basic V13.0 System Manual, 02/2014 Using technology functions 11.2 Using S7-1200 Motion Control Selecting commands Commands can be selected in the trend view and in the command table: Click on a point on the velocity or position curve in the trend view. The corresponding command will be highlighted in the command table. Select a command in the command table. The corresponding section of curve will be highlighted. Selecting the visible range of the trend view Follow the steps below to adjust the section of the trend view to be displayed: Select the scaling in the shortcut menu: Scale to curves: Scales the axes so the position and velocity curves are visible. Scale to curves and limits: Scales the axes so the position and velocity curves, the positions of the activated software limit switches and the minimum and maximum velocity limits are visible. The view selected will be marked in the shortcut menu with a tick. Selecting the section to be shown within the range: WinCC Basic V13.0 System Manual, 02/2014 4369 Using technology functions 11.2 Using S7-1200 Motion Control Range which the curve values and / or limits are within. (see Selecting in the shortcut menu) Selected range to be shown in the trend window. You set the range with the margin cursor at the right-hand and left-hand margin. You set the position within range with the drag cursor. You can also define the position by clicking in range . Selecting the section to be shown with the mouse: Drag a section of the trend view by clicking and dragging with the mouse. The section of curve selected will be enlarged once you release the mouse. Undoing the last change to the section: Select the shortcut command "Undo zoom" to undo the last change to the section. Synchronizing the grid Click on the axis scales to select whether the grid is to be synchronized with the position axis or velocity axis. 4370 WinCC Basic V13.0 System Manual, 02/2014 Using technology functions 11.2 Using S7-1200 Motion Control Reading off curve values from the ruler Activate the ruler using the shortcut menu command "Show ruler". You can move the ruler to any point on the curves using the ruler cursor. See also Configuration - General (Page 4362) Configuration - Command table (Page 4363) Shortcut menu commands - Command table (Page 4366) Shortcut menu commands - Curve chart (Page 4371) Transition from "Complete command" to "Blend motion" (Page 4372) Changing the command table configuration in the user program (Page 4374) Shortcut menu commands - Curve chart The following shortcut menu commands are available in the curve window: Zoom 100% Selects a zoom factor which will show 100% of the curve values and / or limits. Undo zoom Undoes the last zoom change. Scale to curves Scales the axes so the position and velocity curves are visible. Scale to curves and limits Scales the axes so the position and velocity curves, the positions of the activated software limit switches and the minimum and maximum velocity limits are visible. Show velocity limits Shows the lines of the velocity limits. WinCC Basic V13.0 System Manual, 02/2014 4371 Using technology functions 11.2 Using S7-1200 Motion Control Show software limit switches Shows the lines of the software limit switches. Show ruler Fades the ruler in / out Use the ruler when you want to see the individual values of the curves. See also Configuration - General (Page 4362) Configuration - Command table (Page 4363) Shortcut menu commands - Command table (Page 4366) Working with the trend diagram (Page 4367) Transition from "Complete command" to "Blend motion" (Page 4372) Changing the command table configuration in the user program (Page 4374) Transition from "Complete command" to "Blend motion" The charts below show the transition between movements in various different transition modes in the "Next step" column: 4372 WinCC Basic V13.0 System Manual, 02/2014 Using technology functions 11.2 Using S7-1200 Motion Control Motion transition with preceding positioning jobs The following diagrams show a command sequence with two motion tasks. The first command is for positioning (green). The second command is for velocity (red) or positioning (blue): Complete job Blend motion Transition from lower to higher velocity Transition from lower to higher velocity Y Y W W A job with high velocity is appended to a previous positioning job. The positioning job terminates at its target position at velocity "0". The second job starts from standstill. A job with high velocity is overlapped with a previous positioning job. The first positioning job terminates without standstill at its target position. The second job starts with the new velocity. Transition from higher to lower velocity Transition from higher to lower velocity Y Y W A job with low velocity is appended to a previous positioning job. The positioning job terminates at its target position at velocity "0". The second job starts from standstill. W A job with low velocity is overlapped with a previous positioning job. The first positioning job terminates without standstill at its target position. The first job starts with the new velocity. 1. Job "Positioning Relative" or "Positioning Absolute" 2. Job "Velocity set point" 2. Job "Positioning Relative" or "Positioning Absolute" WinCC Basic V13.0 System Manual, 02/2014 4373 Using technology functions 11.2 Using S7-1200 Motion Control Motion transition with preceding velocity jobs The following diagrams show a command sequence with two motion tasks. The first command is for velocity (violet). The second command is for velocity (red) or positioning (blue): Transition from lower to higher velocity Transition from higher to lower velocity Y Y W A job with a high velocity is appended to a previous velocity job. The first velocity job ends after the defined runtime. The second job starts with the new velocity. W A command with lower velocity is blended with a previous velocity command. The second job starts with the new velocity. 1. Job "Velocity set point" 2. Job "Velocity set point" 2. Job "Positioning Relative" or "Positioning Absolute" See also Configuration - General (Page 4362) Configuration - Command table (Page 4363) Shortcut menu commands - Command table (Page 4366) Working with the trend diagram (Page 4367) Shortcut menu commands - Curve chart (Page 4371) Changing the command table configuration in the user program (Page 4374) Changing the command table configuration in the user program You can change the following configuration parameters during runtime of the user program in the CPU: Commands and corresponding values You can also change the parameters of the command table during the runtime of the user program. Use the following technology object tags for this purpose: <Table name>.Command[1..32].Type for changing the command type <Table name>.Command[1..32].Position for changing the position/travel distance 4374 WinCC Basic V13.0 System Manual, 02/2014 Using technology functions 11.2 Using S7-1200 Motion Control <Table name>.Command[1..32].Velocity for changing the velocity <Table name>.Command[1..32].Duration for changing the duration <Table name>.Command[1..32].NextStep for changing the parameter "Next step" <Table name>.Command[1..32].StepCode for changing the step code Refer to the description of the technology object tags (Page 4465) in the appendix for information on when changes to the configuration parameters take effect. See also Compatibility list of tags (Page 4325) Configuration - General (Page 4362) Configuration - Command table (Page 4363) Shortcut menu commands - Command table (Page 4366) Working with the trend diagram (Page 4367) Shortcut menu commands - Curve chart (Page 4371) Transition from "Complete command" to "Blend motion" (Page 4372) Extended parameters Chart parameters Configuration - General Configure the basic properties of the chart view of the "Command table" technology object in the "General" configuration window. Note If the default axis has been selected under "Use axis parameters of", the unit of measurement can be edited. If a configured axis has been selected, the unit of measurement for this axis will be displayed. Use axis parameters of From the drop-down list, select which axis parameters are to be used for selecting the graphic view of and checking the movement sequence. Select "Default axis" if you have yet to add an axis to the "Technology object" folder or wish to use values which have not been configured in any of the available axes. WinCC Basic V13.0 System Manual, 02/2014 4375 Using technology functions 11.2 Using S7-1200 Motion Control The axis parameters of the axis selected at the "Axis" parameter will be used to process the command table in the user program. Unit of measurement Enter the unit of measurement for the default axis in this field. If a preconfigured axis has been selected under "Use axis parameters of", the unit of measurement configured in these parameter will be displayed. Configuration - Dynamics Configure the acceleration and deceleration and the jerk limit for the default axis in the "Dynamics" configuration window. Note If the default axis has been selected under "Use axis parameters of", the following fields can be edited. If a configured axis has been selected, the values of this axis will be displayed. Acceleration / deceleration Set the desired acceleration of the default axis in the "Acceleration" field. The desired deceleration can be set in the "Deceleration" field. Motion jobs configured in the command table will be calculated with the selected acceleration / deceleration. Limit values: 1.0e-12 acceleration 1.0e12 1.0e-12 deceleration 1.0e12 Activate jerk limit Activate the jerk limit with this checkbox. Step Set the desired step for ramping up and ramping down in the "Step" field. Motion jobs configured in the command table will be calculated with the selected step. Limit values: 4376 WinCC Basic V13.0 System Manual, 02/2014 Using technology functions 11.2 Using S7-1200 Motion Control 1.0e-12 jerk 1.0e12 Configuration - Limit values Configure the maximum velocity, the start/stop velocity and the software limit switches of the default axis in the "Limits" configuration window. Note If the default axis has been selected under "Use axis parameters of", the following fields can be edited. If a configured axis has been selected, the values of this axis will be displayed. Maximum velocity / Start/stop velocity Define the maximum permissible velocity and the start/stop velocity of the default axis in these fields. The start/stop velocity is the minimum permissible velocity of the default axis. Limit values: 1.0e-12 start/stop velocity 1.0e12 Start/stop velocity = 0.0 1.0e-12 maximum velocity 1.0e12 Maximum velocity = 0.0 The value of the maximum velocity must be greater or equal to the value of the start/stop velocity. Enable software limit switches Activate the function of the low and high software limit switch with this checkbox. Movements in response to software limit switches being reached are not shown in the trend view. Low / high software limit switch Enter the position value of the low and high software limit switches in these fields. Limits: -1.0e12 low software limit switch -1.0e-12 1.0e-12 low software limit switch 1.0e12 Low software limit switch = 0.0 -1.0e12 high software limit switch -1.0e-12 1.0e-12 high software limit switch 1.0e12 High software limit switch = 0.0 The value of the high software limit switch must be greater than or equal to the value of the low software limit switch. WinCC Basic V13.0 System Manual, 02/2014 4377 Using technology functions 11.2 Using S7-1200 Motion Control 11.2.7 Download to CPU When loading to the CPU S7-1200 always ensure that the project files are consistent after the online and offline loading. It is not possible to load single blocks. When selecting single blocks, all new and modified blocks are always loaded. The following object groups can be loaded to the CPU: Context menu command Description "Download to device" All Download all new and modified blocks and a new or modified hardware configuration Hardware configuration Download a new or modified hardware configuration Software Download all new and modified blocks Software (all blocks) Download all blocks The data of the Motion Control technology objects are saved in the data blocks. The conditions for downloading of "blocks" thus apply when loading a new or modified technology object. CAUTION Possible malfunctions of the axis when loading without hardware configuration The hardware configuration is modified when the following modifications are made to the axis configuration: Modification of the pulse generator (PTO) Modification of the HW limit switch address Modification of the homing switch address If the modified configuration of the axis is loaded with the context menu commands "Software" or "Software (all blocks)" without downloading the hardware configuration, this can lead to malfunctions of the axis. Ensure that the current hardware configuration is downloaded to the CPU under the conditions listed below. Download in CPU S7-1200 RUN operating mode (from firmware version V2.2) For CPU S7-1200 from firmware version V2.2, when loading in CPU RUN operating mode it is checked whether it is possible to load without stopping the CPU. The following conditions apply when loading data blocks in RUN operating mode: Data block modified values Data block modified structure Download to load memory Download to work memory Yes No Yes (as of firmware V4) Yes (as of firmware V4) When downloading with reinitialization For tags in reserve for downloading without reinitialization No (firmware V2.2...3) 4378 No (firmware V2.2...3) WinCC Basic V13.0 System Manual, 02/2014 Using technology functions 11.2 Using S7-1200 Motion Control Download to load memory Download to work memory New data block Yes Yes Data block deleted Yes Yes Also note the following when deleting data blocks and downloading data blocks with reinitialization: The axis must be locked when downloading a positioning axis technology object. When downloading a command table technology object, no MC_CommandTable command with this command table must be active (parameter "Busy" = FALSE). When downloading an MC_Power instance data block, no MC_Power instruction must be active (parameter "Busy" = FALSE). From technology version V3.0, Motion Control technology objects (data blocks) can also be downloaded in CPU RUN operating mode. Technology objects after V3.0 cannot be downloaded in CPU RUN operating mode. Select one of the actions described below to download the modified version of a Motion Control technology object (from version V3.0) to the work memory: Technology object axis and command table Change the CPU operating mode from STOP to RUN. Technology object axis Disable the axis and execute a "Restart" using the Motion Control instruction "MC_Reset". Technology object command table Ensure that the command table is not being used. Download the data block of the command table to the work memory using the extended instruction "READ_DBL". See also Guidelines on use of motion control (Page 4322) MC_Reset: Acknowledge fault V4 (Page 2824) 11.2.8 Commissioning the axis - Axis control panel Use the axis command table to move the axis in manual mode, to optimize the axis settings, and to test your system. The axis control table can only be used if an online connection to the CPU is established. Note Response times of the axis control panel The response time during axis control table operation depends on the communication load of the CPU. Close all other online windows of the TIA Portal to minimize the response time. WinCC Basic V13.0 System Manual, 02/2014 4379 Using technology functions 11.2 Using S7-1200 Motion Control "Manual control" button Click "Manual control" to move the axis in manual control mode. Start by disabling the axis in the user program using Motion Control instruction "MC_Power". In "Manual control" mode, the axis control table takes over control priority for the axis functions. The user program has no influence on the axis functions until manual control is ended. CAUTION Additional axes in automatic mode The Manual control is active for one axis only. If additional axes are in automatic mode, dangerous situations may arise as a result. In this happens, disable all other axes. "Automatic mode" button Click "Automatic mode" to end the "Manual control" mode. The axis control table passes back the control priority and the axis can be controlled by the user program again. The axis must be re-enabled in the user program and homed, if required. Complete all active traversing motions before switching to automatic control; otherwise, the axis will be braked with the emergency stop deceleration. "Enable" button Click "Enable" to enable the axis in "Manual control" mode. When the axis is enabled, the axis control panel functions can be used. If the axis cannot be enabled because certain conditions are not met, note the error message in the "Error message" box. Information on eliminating errors is available in the appendix under "List of ErrorIDs and ErrorInfos". After the error has been corrected, enable the axis again. "Disable" button Click "Disable" if you want to temporarily disable the axis in "Manual control" mode. 4380 WinCC Basic V13.0 System Manual, 02/2014 Using technology functions 11.2 Using S7-1200 Motion Control "Command" area Operation in the "Command" area is only possible if the axis is enabled. You can select one of the following command inputs: Jogging This command is equivalent to Motion Control command "MC_MoveJog" in the user program. Positioning This command is equivalent to the Motion Control commands "MC_MoveAbsolute" and "MC_MoveRelative" in the user program. The axis must be homed for absolute positioning. Homing This command is equivalent to Motion Control command "MC_Home" in the user program. - The "Set reference point" button corresponds to Mode = 0 (direct homing absolute) - The "Active homing" button corresponds to Mode = 3 (active homing) For active homing, the homing switch must be configured in the axis configuration. The values for approach velocity, homing velocity, and reference position offset are taken from the axis configuration unchanged. Depending on the selection, the relevant boxes for entry of setpoints and the buttons for starting the command are displayed. Jerk limitation can be activated and deactivated using the "Activate jerk limit" button. By default, the jerk is applied with 10% of the configured value. This value can be changed as required. "Axis status" area If "Manual control" mode is activated, the current axis status and drive status are shown in the "Axis status" area. The current position and velocity of the axis are displayed at "Process values". Click "Acknowledge" to acknowledge all cleared errors. The "Info message" box displays advanced information about the status of the axis. "Current values" area This area displays the current position and velocity of the axis. WinCC Basic V13.0 System Manual, 02/2014 4381 Using technology functions 11.2 Using S7-1200 Motion Control Error message The "Error message" box shows the current error. In "Manual control" mode, the error entry can be deleted by pressing the "Acknowledge" button once the error is eliminated. Note Initial values for velocity, acceleration / deceleration and jerk For safety reasons, the "Velocity", "Acceleration/deceleration" and "Jerk" parameters are initialized with values equivalent to only 10% of the configured values when the axis command table is activated. The "Jerk" parameter is only used for technology object "Axis" V2.0 and higher. The values in the configuration view displayed when you select "Extended parameters > Dynamics > General" are used for initialization. The "Velocity" parameter on the control panel is derived from the "Maximum velocity" and the "Acceleration/deceleration" parameters from "Acceleration" in the configuration. The "Velocity", "Acceleration/deceleration" and "Jerk" parameters can be changed in the axis command table; this does not affect the values in the configuration. See also Guidelines on use of motion control (Page 4322) 4382 WinCC Basic V13.0 System Manual, 02/2014 Using technology functions 11.2 Using S7-1200 Motion Control 11.2.9 Parameter view 11.2.9.1 Introduction to the parameter view The Parameter view provides you with a general overview of all relevant parameters of a technology object. You obtain an overview of the parameter settings and can easily change them in offline and online mode. "Parameter view" tab Toolbar (Page 4230) Navigation (Page 4231) Parameter table (Page 4231) Function scope The following functions are available for analyzing the parameters of the technology objects and for enabling targeted monitoring and modification. Display functions: WinCC Basic V13.0 System Manual, 02/2014 4383 Using technology functions 11.2 Using S7-1200 Motion Control Display of parameter values in offline and online mode Display of status information of the parameters Display of value deviations and option for direct correction Display of configuration errors Display of value changes as a result of parameter dependencies Display of all memory values of a parameter: Start value PLC, Start value project, Monitor value Display of the parameter comparison of the memory values of a parameter Operator control functions: Navigation for quickly changing between the parameters and parameter structures. Text filter for faster searches for particular parameters. Sorting function for customizing the order of parameters and parameter groups to requirements. Memory function for backing up structural settings of the Parameter view. Monitoring and modifying of parameter values online. Function for saving a snapshot of parameter values of the CPU in order to capture momentary situations and to respond to them. Function for applying a snapshot of parameter values as start values. Download of modified start values to the CPU. Comparison functions for comparing parameter values with one another. Validity The Parameter view is available for the following technology objects: PID_Compact PID_3Step CONT_C (S7-1500 only) CONT_S (S7-1500 only) TCONT_CP (S7-1500 only) TCONT_S (S7-1500 only) TO_Axis_PTO (S7-1200 Motion Control) TO_Positioning_Axis (S7-1200 Motion Control) TO_CommandTable_PTO (S7-1200 Motion Control) TO_CommandTable (S7-1200 Motion Control) 4384 WinCC Basic V13.0 System Manual, 02/2014 Using technology functions 11.2 Using S7-1200 Motion Control 11.2.9.2 Structure of the parameter view Toolbar The following functions can be selected in the toolbar of the parameter view. Icon Function Explanation Monitor all Starts the monitoring of visible parameters in the active Parameter view (online mode). Create snapshot of Applies the current monitor values to the "Snapshot" column and monitor values and updates the start values in the project. accept setpoints of this Only in online mode for PID_Compact and PID_3Step. snapshot as start values Initialize setpoints Transfers the start values updated in the project to the CPU. Create snapshot of monitor values Applies the current monitor values to the "Snapshot" column. Modify all selected parameters immediately and once This command is executed once and as quickly as possible without reference to any particular point in the user program. Select navigation structure Toggles between functional navigation and data navigation. Text filter... After entry of a character string: Display of all parameters containing the specified string in one of the currently visible columns. Selection of compare values Selection of parameter values that are to be compared with one another in online mode (Start value project, Start value PLC, Snapshot) Only in online mode for PID_Compact and PID_3Step. Only in online mode. Only in online mode. Only in online mode. Save window settings WinCC Basic V13.0 System Manual, 02/2014 Saves your display settings for the Parameter view (e.g., selected navigation structure, activated table columns, etc.) 4385 Using technology functions 11.2 Using S7-1200 Motion Control Navigation Within the "Parameter view" tab, the following alternative navigation structures can be selected. Navigation Explanation Functional navigation In the functional navigation, the structure of the parameters is based on the structure in the configuration dialog ("Functional view" tab), commissioning dialog, and diagnostics dialog. The last group "Other parameters" contains all other parameters of the technology object. Data navigation In the data navigation, the structure of the parameters is based on the structure in the instance DB. The last group "Other parameters" contains the parameters that are not contained in the instance DB. You can use the "Select navigation structure" drop-down list to toggle the navigation structure. Parameter table The table below shows the meaning of the individual columns of the parameter table. You can show or hide the columns as required. Column "Offline" = X: Column is visible in offline mode. Column "Online" = X: Column is visible in online mode (online connection to the CPU). Column Explanation Offline Online Name in functional view Name of the parameter in the functional view. X X Full name in DB Complete path of the parameter in the instance DB. X X X X The display field is empty for parameters that are not configured via the technology object. The display field is empty for parameters that are not contained in the instance DB. Name in DB Name of the parameter in the instance DB. If the parameter is part of a structure or UDT, the prefix ". ./" is added. The display field is empty for parameters that are not contained in the instance DB. Status of configuration Display of the completeness of the configuration using status symbols. Compare result Result of the "Compare values" function. X see Status of configuration (offline) (Page 4239) X This column is shown if there is an online connection and the "Monitor all" button is selected. see Comparing values (Page 4225) 4386 WinCC Basic V13.0 System Manual, 02/2014 Using technology functions 11.2 Using S7-1200 Motion Control Column Explanation Offline Online Start value project Configured start value in the project. X X X X X X Error indication if entered values have a syntax or process-related error. Default value Value that is pre-assigned to the parameter. The display field is empty for parameters that are not contained in the instance DB. Snapshot Snapshot of the current values in the CPU (monitor values). Error indication if values have a process-related error. Start value PLC Start value in the CPU. X This column is shown if there is an online connection and the "Monitor all" button is selected. Error indication if values have a process-related error. Monitor value Current value in the CPU. X This column is shown if there is an online connection and the "Monitor all" button is selected. Error indication if values have a process-related error. Modify value Value that is to be used to change the monitor valuet. X This column is shown if there is an online connection and the "Monitor all" button is selected. Error indication if entered values have a syntax or process-related error. Selection for transmission Selection of the Modify values that are to be transmitted using the "Modify all selected parameters immediately and once" button. X This column is displayed together with the "Modify value" column. Minimum value Minimum process-related value of the parameter. X X X X If the minimum value is dependent on other parameters, it is defined: Offline: By the Start value project. Online: By the Monitor values. Maximum value Maximum process-related value of the parameter. If the maximum value is dependent on other parameters, it is defined: Offline: By the Start value project. Online: By the Monitor values. Setpoint Designates the parameter as a setpoint. These parameters can be initialized online. X X Data type Data type of the parameter. X X X X Accessible from HMI Indicates whether the HMI can access this parameter during runtime. X X Visible in HMI Indicates whether the parameter is visible in the selection list of the HMI by default. X X Comment Brief description of the parameter. X X The display field is empty for parameters that are not contained in the instance DB. Retain Designates the value as a retentive value. The values of retentive parameters are retained even after the voltage supply is switched off. WinCC Basic V13.0 System Manual, 02/2014 4387 Using technology functions 11.2 Using S7-1200 Motion Control 11.2.9.3 Opening the parameter view Requirement The technology object has been added in the project tree, i.e., the associated instance DB of the instruction has been created. Procedure 1. Open the "Technology objects" folder in the project tree. 2. Open the technology object in the project tree. 3. Double-click the "Configuration" object. 4. Select the "Parameter view" tab in the top right corner. Result The Parameter view opens. Each displayed parameter is represented by one row in the parameter table. The displayable parameter properties (table columns) vary depending on whether you are working with the Parameter view in offline or online mode. In addition, you can selectively display and hide individual table columns. See also Default setting of the parameter view (Page 4233) 11.2.9.4 Default setting of the parameter view Default settings To enable you to work efficiently with the Parameter view, you can customize the parameter display and save your settings. The following customizations are possible and can be saved: Show and hide columns Change column width Change order of the columns Toggle navigation Select parameter group in the navigation Selection of compare values 4388 WinCC Basic V13.0 System Manual, 02/2014 Using technology functions 11.2 Using S7-1200 Motion Control Show and hide columns To show or hide columns in the parameter table, follow these steps: 1. Position the cursor in the header of the parameter table. 2. Select the "Show/Hide" command in the shortcut menu. The selection of available columns is displayed. 3. To show a column, select the check box for the column. 4. To hide a column, clear the check box for the column. or 1. Position the cursor in the header of the parameter table. 2. Select the "Show all columns" command in the shortcut menu if all columns of the offline or online mode are to be displayed. Some columns can only be displayed in online mode: see Parameter table (Page 4231). Change column width To customize the width of a column so that all texts in the rows can be read, follow these steps: 1. Position the cursor in the header of the parameter table to the right of the column to be customized until the shape of the cursor changes to a cross. 2. Then double-click this location. or 1. Open the shortcut menu on the header of the parameter table. 2. Click - "Optimize column width" or - "Optimize width of all columns". If the column width setting is too narrow, the complete content of individual fields are shown if you hover the cursor briefly over the relevant field. Change order of the columns The columns of the parameter table can be arranged in any way. To change the order of the columns, follow these steps: WinCC Basic V13.0 System Manual, 02/2014 4389 Using technology functions 11.2 Using S7-1200 Motion Control 1. Click on the column header and use a drag-and-drop operation to move it to the desired location. When you release the mouse button, the column is anchored to the new position. Toggle navigation To toggle the display form of the parameters, follow these steps: 1. Select the desired navigation in the "Select navigation structure" drop-down list. - Data navigation - Functional navigation See also Navigation (Page 4231). Select parameter group in the navigation Within the selected navigation, you choose between the "All parameters" display or the display of a subordinate parameter group of your choice. 1. Click the desired parameter group in the navigation. The parameter table only displays the parameters of the parameter group. Selection of compare values (online) To set the compare values for the "Compare values" function, follow these steps: 1. Select the desired compare values in the "Selection of compare values" drop-down list. - Start value project / Start value PLC - Start value project / Snapshot - Start value PLC / Snapshot The "Start value project / Start value PLC" option is set by default. Save default setting of the Parameter view To save the above customizations of the Parameter view, follow these steps: 1. Customize the Parameter view according to your requirements. 2. Click the "Save window settings" button 11.2.9.5 at the top right of the Parameter view. Working with the parameter view Overview The following table provides an overview of the functions of the Parameter view in online and offline mode described in the following. Column "Offline" = X: This function is possible in offline mode. Column "Online" = X: This function is possible in online mode. 4390 WinCC Basic V13.0 System Manual, 02/2014 Using technology functions 11.2 Using S7-1200 Motion Control Function/action Offline Online Filtering the parameter table (Page 4236) X X Sorting the parameter table (Page 4237) X X Transferring parameter data to other editors (Page 4237) X X Indicating errors (Page 4237) X X Editing start values in the project (Page 4238) X X Status of configuration (offline) (Page 4239) X Monitoring values online in the parameter view (Page 4240) X Create snapshot of monitor values (Page 4240) X Modifying values (Page 4241) X Comparing values (Page 4242) X Applying values from the online program as start values (Page 4243) X Initializing setpoints in the online program (Page 4244) X Filtering the parameter table You can filter the parameters in the parameter table in the following ways: With the text filter With the subgroups of the navigation Both filter methods can be used simultaneously. With the text filter Texts that are visible in the parameter table can be filtered. This means only texts in displayed parameter rows and columns can be filtered. 1. Enter the desired character string for filtering in the "Text filter..." input box. The parameter table displays only the parameters containing the character string. The text filtering is reset. When another parameter group is selected in the navigation. When navigation is changed from data navigation to functional navigation, or vice versa. With the subgroups of the navigation 1. Click the desired parameter group in the navigation, e.g., "Static". The parameter table only shows the static parameters. You can select further subgroups for some groups of the navigation. 2. Click "All parameters" in the navigation if all parameters are to be shown again. WinCC Basic V13.0 System Manual, 02/2014 4391 Using technology functions 11.2 Using S7-1200 Motion Control Sorting the parameter table The values of the parameters are arranged in rows. The parameter table can be sorted by any displayed column. In columns containing numerical values, sorting is based on the magnitude of the numerical value. In text columns, sorting is alphabetical. Sorting by column 1. Position the cursor in the header cell of the desired column. The background of this cell turns blue. 2. Click the column header. Result The entire parameter table is sorted by the selected column. A triangle with tip facing up appears in the column header. Clicking the column header again changes the sorting as follows: Symbol "": Parameter table is sorted in ascending order. Symbol "": Parameter table is sorted in descending order. No symbol: The sorting is removed again. The parameter table assumes the default display. The "../" prefix in the "Name in DB" column is ignored when sorting. Transferring parameter data to other editors After selecting an entire parameter row of the parameter table, you can use the following: Drag-and-drop <Ctrl+C>/<Ctrl+V> Copy/Paste via shortcut menu Transfer parameters to the following editors of the TIA Portal: Program editor Watch table Signal table for trace function The parameter is inserted with its full name: See information in "Full name in DB" column. Indicating errors Error indication Parameter assignment errors that result in compilation errors (e.g., limit violation) are indicated in the Parameter view. 4392 WinCC Basic V13.0 System Manual, 02/2014 Using technology functions 11.2 Using S7-1200 Motion Control Every time a value is input in the Parameter view, a check is made for process-related and syntax errors and the result is indicated. Bad values are indicated by: Red error symbol in the "Status of configuration" (offline mode) or "Compare result" (online mode, depending on the selected comparison type) columns and/or Table field with red background If you click the bad field, a roll-out error message appears with information of the permissible value range or the required syntax (format) Compilation error From the error message of the compiler, you can directly open the Parameter view (functional navigation) containing the parameter causing the error in situations where the parameter is not displayed in the configuration dialog. Editing start values in the project With the Parameter view, you can edit the start values in the project in offline mode and online mode. You make value changes in the "Start value project" column of the parameter table. In the "Status of configuration" column of the parameter table, the progress of the configuration is indicated by the familiar status symbols from the configuration dialog of the technology object. Boundary conditions If other parameters depend on the parameter whose start value was changed, the start value of the dependent parameters are also adapted. If a parameter of a technology object is not editable, it is also not editable in the parameter view. The ability to edit a parameter can also depend on the values of other parameters. Defining new start values To define start values for parameters in the Parameter view, follow these steps: 1. Open the Parameter view of the technology object. 2. Enter the desired start values in the "Start value project" column. The value must match the data type of the parameter and must not exceed the value range of the parameter. The limits of the value range can be seen in the "Maximum value" and "Minimum value" columns. The "Status of configuration" column indicates the progress of the configuration with colored symbols. See also Status of configuration (offline) (Page 4239) WinCC Basic V13.0 System Manual, 02/2014 4393 Using technology functions 11.2 Using S7-1200 Motion Control Following adaptation of the start values and downloading of the technology object to the CPU, the parameters take the defined value at startup if they are not declared as retentive ("Retain" column). Error indication When a start value is input, a check is made for process-related and syntax errors and the result is indicated. Bad start values are indicated by: Red error symbol in the "Status of configuration" (offline mode) or "Compare result" (online mode, depending on the selected comparison type) columns and/or Red background in the "Start value project" field If you click on the bad field, a roll-out error message appears with information of the permissible value range or the necessary syntax (format) Correcting bad start values 1. Correct bad start values using information from the roll-out error message. Red error symbol, red field background, and roll-out error message are no longer displayed. The project cannot be successfully compiled unless the start values are error-free. Status of configuration (offline) The status of the configuration is indicated by icons: In the "Status of configuration" column in the parameter table In the navigation structure of the functional navigation and data navigation Symbol in "Status of configuration" column Symbol Meaning The start value of the parameter corresponds to the default value and is valid. A start value has not yet been defined by the user. The start value of the parameter contains a value defined by the user. The start value is different than the default value. The start value is error-free and valid. The start value of the parameter is invalid (syntax or process-related error). The input box has a red background. When clicked, the roll-out error message indicates the cause of the error. Only for S7-1200 Motion Control: The start value of the parameter is valid but contains warnings. The input box has a yellow background. 4394 WinCC Basic V13.0 System Manual, 02/2014 Using technology functions 11.2 Using S7-1200 Motion Control Symbol in the navigation The symbols in the navigation indicate the progress of the configuration in the same way as in the configuration dialog of the technology object. See Configure technology objects (Page 4221) Monitoring values online in the parameter view You can monitor the values currently taken by the parameters of the technology object in the CPU (monitor values) directly in the Parameter view. Requirements There is an online connection. The technology object is downloaded to the CPU. The program execution is active (CPU in "RUN"). The Parameter view of the technology object is open. Procedure 1. Start the monitoring by clicking . As soon as the Parameter view is online, the following columns are additionally displayed: - Compare result - Start value PLC - Monitor value - Modify value - Selection for transmission The "Monitor value" column shows the current parameter values on the CPU. Meaning of the additional columns: see Parameter table (Page 4231) 2. Stop the monitoring by clicking again. Display All columns that are only available online have an orange background: Values in light-orange cells can be changed. Values in cells with a dark orange background cannot be changed. Create snapshot of monitor values You can back up the current values of the technology object on the CPU (monitor values) and display them in the Parameter view. WinCC Basic V13.0 System Manual, 02/2014 4395 Using technology functions 11.2 Using S7-1200 Motion Control Requirements There is an online connection. The technology object is downloaded to the CPU. The program execution is active (CPU in "RUN"). The Parameter view of the technology object is open. The "Monitor all" button is selected. Procedure To show the current parameter values, follow these steps: 1. In the Parameter view, click the "Create snapshot of monitor values" icon . Result The current monitor values are transferred once to the "Snapshot" column of the parameter table. You can analyze the values "frozen" in this way while the monitor values continue to be updated in the "Monitor values" column. Modifying values With the Parameter view, you can modify values of the technology object in the CPU. You can assign values to the parameter once (Modify value) and modify them immediately. The modify request is executed as quickly as possible without reference to any particular point in the user program. DANGER Danger when modifying: Changing the parameter values while the plant is operating may result in severe damage to property and personal injury in the event of malfunctions or program errors. Make sure that dangerous states cannot occur before you use the "Modify" function. Requirements There is an online connection. The technology object is downloaded to the CPU. The program execution is active (CPU in "RUN"). The Parameter view of the technology object is open. 4396 WinCC Basic V13.0 System Manual, 02/2014 Using technology functions 11.2 Using S7-1200 Motion Control The "Monitor all" button is selected. The parameter can be modified (associated field in the "Modify value" column has a lightorange background). Procedure To modify parameters immediately, follow these steps: 1. Enter the desired modify values in the "Modify values" column of the parameter table. 2. Check whether the check box for modifying is selected in the "Select for transmission" column. The modify values and associated check boxes of dependent parameters are automatically adapted at the same time. 3. Click the "Modify all selected parameters immediately and once" icon . The selected parameters are modified once and immediately with the specified values and can be monitored in the "Modify values" column. The check boxes for modifying in the "Selection for transmission" column are automatically cleared after the modify request is complete. Error indication When a start value is input, a check is made immediately for process-related and syntax errors and the result is indicated. Bad start values are indicated by: Red background in the "Modify value" field and If you click the bad field, a roll-out error message appears with information of the permissible value range or the necessary syntax (format) Bad modify values Modify values with process-related errors can be transmitted. Modify values with syntax errors cannot be transmitted. Comparing values You can use comparison functions to compare the following memory values of a parameter: Start value project Start value PLC Snapshot WinCC Basic V13.0 System Manual, 02/2014 4397 Using technology functions 11.2 Using S7-1200 Motion Control Requirements There is an online connection. The technology object is downloaded to the CPU. The program execution is active (CPU in "RUN"). The Parameter view of the technology object is open. The "Monitor all" button is selected. Procedure To compare the start values on the various target systems, follow these steps: . 1. Click the "Selection of compare values" icon A selection list containing the comparison options opens: - Start value project - Start value PLC (default setting) - Start value project - Snapshot - Start value PLC - Snapshot 2. Select the desired comparison option. The selected comparison option is executed as follows: - A scales symbol appears in the header cells of the two columns selected for comparison. - Symbols are used in the "Compare result" column to indicate the result of the comparison of the selected columns. Symbol in "Compare result" column Symbol Meaning The compare values are equal and error-free. The compare values are not equal and error-free. At least one of the two compare values has a process-related or syntax error. The comparison cannot be performed. At least one of the two compare values is not available (e.g., snapshot). Symbol in the navigation The symbols are shown in the same way in the navigation if the comparison result applies to at least one of the parameters below the displayed navigation structure. Applying values from the online program as start values In order to apply optimized values from the CPU to the project as start values, you create a snapshot of the monitor values. Values of the snapshot marked as a "Setpoint" are then applied to the project as start values. 4398 WinCC Basic V13.0 System Manual, 02/2014 Using technology functions 11.2 Using S7-1200 Motion Control Requirements The technology object is of type "PID_Compact" or "PID_3Step". There is an online connection. The technology object is downloaded to the CPU. The program execution is active (CPU in "RUN"). The Parameter view of the technology object is open. The "Monitor all" button is selected. Procedure To apply optimized values from the CPU, follow these steps: 1. Click the "Create snapshot of monitor values and accept setpoints of this snapshot as start values" icon . Result The current monitor values are applied to the "Snapshot" column and their setpoints are copied to the "Start value project" column as new start values. Note Applying values of individual parameters You can also apply the values of individual parameters that are not marked as a setpoint from the "Snapshot" column to the "Start values project" column. To do so, copy the values and insert them into the "Start value project" column using the "Copy" and "Paste" commands in the shortcut menu. Initializing setpoints in the online program You can initialize all parameters that are marked as a "Setpoint" in the Parameter view with new values in the CPU in one step. In so doing, the start values are downloaded from the project to the CPU. The CPU remains in "RUN" mode. To avoid data loss on the CPU during a cold restart or warm restart, you must also download the technology object to the CPU. DANGER Danger when changing parameter values Changing the parameter values while the plant is operating may result in severe damage to property and personal injury in the event of malfunctions or program errors. Make sure that dangerous states cannot occur before you reinitialize the setpoints. WinCC Basic V13.0 System Manual, 02/2014 4399 Using technology functions 11.2 Using S7-1200 Motion Control Requirements The technology object is of type "PID_Compact" or "PID_3Step". There is an online connection. The technology object is downloaded to the CPU. The program execution is active (CPU in "RUN"). The Parameter view of the technology object is open. The "Monitor all" button is selected. The parameters marked as a "Setpoint" have a "Start value project" that is free of processrelated and syntax errors Procedure To initialize all setpoints, follow these steps: 1. Enter the desired values in the "Start value project" column. Ensure that the start values are free of process-related and syntax errors. 2. Click the "Initialize setpoints" icon . Result The setpoints in the CPU are initialized with the start values from the project. 11.2.10 Programming 11.2.10.1 Overview of the Motion Control statements You control the axis with the user program using Motion Control instructions. The instructions start Motion Control commands that execute the desired functions. The status of the Motion Control commands and any errors that occur during their execution can be obtained from the output parameters of the Motion Control instructions. The following Motion Control instructions are available: MC_Power: Enable, disable axis V4 (Page 2820) MC_Reset: Acknowledge fault V4 (Page 2824) MC_Home: Home axes, set reference point V4 (Page 2826) MC_Halt: Halt axes V4 (Page 2829) MC_MoveAbsolute: Absolute positioning of axes V4 (Page 2832) MC_MoveRelative: Relative positioning of axes V4 (Page 2835) MC_MoveVelocity: Move axes at preset rotational speed V4 (Page 2839) MC_MoveJog: Move axes in jog mode V4 (Page 2843) MC_CommandTable: Run axis commands as motion sequence V4 (Page 2846) 4400 WinCC Basic V13.0 System Manual, 02/2014 Using technology functions 11.2 Using S7-1200 Motion Control MC_ChangeDynamic: Change dynamic settings of axis V4 (Page 2848) MC_ReadParam: Continuously read motion data of a positioning axis V4 (Page 2850) MC_WriteParam: Write tag of positioning axis V4 (Page 2852) See also Creating a user program (Page 4401) Programming notes (Page 4404) Behavior of the Motion Control commands after POWER OFF and restart (Page 4406) Monitoring active commands (Page 4406) Error displays of the Motion Control statements (Page 4417) 11.2.10.2 Creating a user program In the section below you learn how to create a user program with the basic configuration for controlling your axis. All available axis functions are controlled using the Motion Control instructions to be inserted. Requirement The technology object has been created and configured without errors. Before creating and testing the user program, it is advisable to test the function of the axis and the corresponding parts of the system with the axis command table. Procedure Proceed as follows to create the user program in accordance with the principles described below: 1. In the project tree, double-click your code block (the code block must be called in the cyclic program). The code block is opened in the programming editor and all available instructions are displayed. 2. Open the "Technology" category and the "Motion Control" and "S7-1200 Motion Control" folders. 3. Use a drag-and-drop operation to move the "MC_Power" instruction to the desired network of the code block. The dialog box for defining the instance DB opens. 4. In the next dialog box, select from the following alternatives: Single instance Click "Single instance" and select whether you want to define the name and number of the instance DB automatically or manually. Multi-instance Click "Multi-instance" and select whether you want to define the name of the multi-instance automatically or manually. WinCC Basic V13.0 System Manual, 02/2014 4401 Using technology functions 11.2 Using S7-1200 Motion Control 5. Click "OK". The Motion Control instruction "MC_Power" is inserted into the network. Parameters marked with "<???>" must be initialized; all other parameters are assigned default values. Parameters displayed in black are required for use of the Motion Control instruction. 4402 WinCC Basic V13.0 System Manual, 02/2014 Using technology functions 11.2 Using S7-1200 Motion Control 6. Select technology object in the project tree and drag-and-drop it on <???>. Following selection of the technology object data block, the following buttons are available: Click the stethoscope icon if you want to open the diagnostics dialog for the technology object. Click the toolbox icon if you want to open the configuration view of the technology object. Click the arrow down icon to view additional parameters of the Motion Control instruction. The grayed-out parameters now visible can be used optionally. 7. Add your choice of Motion Control instructions in accordance with steps 3 to 6. Result You have created the basic configuration for axis control in the user program. WinCC Basic V13.0 System Manual, 02/2014 4403 Using technology functions 11.2 Using S7-1200 Motion Control Initialize the input parameters of Motion Control instructions in other parts of the user program to initiate the desired jobs for the "Axis" technology object. Evaluate the output parameters of the Motion Control instructions and the tags of the data block to track the initiated jobs and the status of the axis. Refer to the detailed description for details on the parameters of Motion Control instructions. See also Overview of the Motion Control statements (Page 4400) Programming notes (Page 4404) Behavior of the Motion Control commands after POWER OFF and restart (Page 4406) Monitoring active commands (Page 4406) Error displays of the Motion Control statements (Page 4417) 11.2.10.3 Programming notes When creating your user program, note the following information: Cyclic call of utilized motion control instructions The current status of command execution is available via the output parameters of the motion control instruction. The status is updated with every call of the motion control instruction. Therefore, make sure that the utilized motion control instructions are called cyclically. Transfer of parameter values of a motion control instruction The parameter values pending for the input parameters are transferred with a positive edge at input parameter "Execute" when the block is called. The motion control command is started with these parameter values. Parameter values that are subsequently changed for the motion control instruction are not transferred until the next start of the motion control command. Exceptions to this are input parameters "StopMode" of motion control instruction "MC_Power" and "Velocity" of motion control instruction "MC_MoveJog". A change in the input parameter is also applied when "Enable" = TRUE, or "JogForward" and "JogBackward". . 4404 WinCC Basic V13.0 System Manual, 02/2014 Using technology functions 11.2 Using S7-1200 Motion Control Programming under consideration of the status information In a stepwise execution of motion control jobs, make sure to wait for the active command to finish before starting a new command. Use the status messages of the motion control instruction and the "StatusBits" tag of the technology object to check for completion of the active command. In the examples below, observe the indicated sequence. Failure to observe the sequence will display an axis or command error. - Axis enable with motion control instruction "MC_Power" You must enable the axis before it can take on motion jobs. Use an AND operation of tag <Axis name>.StatusBits.Enable = TRUE with output parameter Status = TRUE of motion control instruction "MC_Power" to verify that the axis is enabled. - Acknowledge error with motion control instruction "MC_Reset" Prior to starting a motion control command, errors requiring acknowledgement must be acknowledged with "MC_Reset". Eliminate the cause of the error and acknowledge the error with motion control instruction "MC_Reset". Verify that the error has been successfully acknowledged before initiating a new command. For this purpose, use an AND operation of tag <Axis name>.StatusBits.Error = FALSE with output parameter Done = TRUE of motion control instruction "MC_Reset". - Home axis with motion control instruction "MC_Home" Before you can start an MC_MoveAbsolute command, the axis must be homed. Use an AND operation of tag <Axis name>.StatusBits.HomingDone = TRUE with output parameter Done = TRUE of motion control instruction "MC_Home" to verify that the axis has been homed. Override of motion control command processing Motion control jobs for moving an axis can also be executed as overriding jobs. If a new motion control command is started for an axis while another motion control command is active, the active command is overridden by the new command before the existing command is completely executed. The overridden command signals this using CommandAborted = TRUE in the motion control instruction. It is possible to override an active MC_MoveRelative command with a MC_MoveAbsolute command. Avoiding multiple use of the same instance All relevant information of a motion control command is stored in its instance. Do not start a new command using this instance, if you want to track the status of the current command. Use different instances if you want to track the commands separately. If the same instance is used for multiple motion control commands, the status and error information of the individual commands will overwrite each other. Call of motion control instructions in different priority classes (run levels) Motion Control instructions with the same instance may not be called in different priority classes without interlocking. To learn how to call locked motion control instructions, refer to "Tracking commands from higher priority classes (run levels) (Page 4427)". See also Overview of the Motion Control statements (Page 4400) Creating a user program (Page 4401) Behavior of the Motion Control commands after POWER OFF and restart (Page 4406) Monitoring active commands (Page 4406) WinCC Basic V13.0 System Manual, 02/2014 4405 Using technology functions 11.2 Using S7-1200 Motion Control Error displays of the Motion Control statements (Page 4417) Tracking jobs from higher priority classes (execution levels) (Page 4427) 11.2.10.4 Behavior of the Motion Control commands after POWER OFF and restart A POWER OFF or CPU-STOP aborts all active motion control jobs. All CPU outputs, including pulse and direction outputs, are reset. After a subsequent POWER ON or CPU restart (CPU RUN), the technology objects and the motion control jobs will be reinitialized. All actual data of the technology objects as well as all status and error information of the previously active motion control jobs are reset to their initial values. Before the axis can be reused, it must be enabled again using the Motion Control instruction "MC_Power". If homing is required, the axis must be homed again with Motion Control instruction "MC_Home". See also Overview of the Motion Control statements (Page 4400) Creating a user program (Page 4401) Programming notes (Page 4404) Monitoring active commands (Page 4406) Error displays of the Motion Control statements (Page 4417) 11.2.10.5 Monitoring active commands Monitoring active commands There are three typical groups for tracking active Motion Control commands: Motion control instructions with output parameter "Done" Motion control instruction "MC_MoveVelocity" Motion control instruction "MC_MoveJog" Motion control instructions with "Done" output parameter Motion control instructions with the output parameter "Done" are started via input parameter "Execute" and have a defined conclusion (for example, with Motion Control instruction "MC_Home": Homing was successful). The command is complete and the axis is at a standstill. The commands of the following Motion Control instructions have a defined conclusion: MC_Reset MC_Home MC_Halt 4406 WinCC Basic V13.0 System Manual, 02/2014 Using technology functions 11.2 Using S7-1200 Motion Control MC_MoveAbsolute MC_MoveRelative MC_CommandTable (technology object as of V2) MC_ChangeDynamic (technology object as of V2) MC_WriteParam (as of technology object V4) MC_ReadParam (as of technology object V4) The output parameter "Done" indicates the value TRUE, if the command has been successfully completed. The output parameters "Busy", "CommandAborted", and "Error" signal that the command is still being processed, has been aborted or an error is pending. The Motion Control instruction "MC_Reset" cannot be aborted and thus has no "CommandAborted" output parameter. The Motion Control instruction "MC_ChangeDynamic" is completed immediately and therefore has no "Busy" or "CommandAborted" output parameters. During execution of the Motion Control command, the output parameter "Busy" indicates the value TRUE. If the command has been completed, aborted, or stopped by an error, the output parameter "Busy" changes its value to FALSE. This change occurs regardless of the signal at input parameter "Execute". Output parameters "Done", "CommandAborted", and "Error" indicate the value TRUE for at least one cycle. These status messages are latched while input parameter "Execute" is set to TRUE. The behavior of the status bits is presented below for various example situations: WinCC Basic V13.0 System Manual, 02/2014 4407 Using technology functions 11.2 Using S7-1200 Motion Control Complete execution of command If the Motion Control command has been completely executed by the time of its conclusion, this is indicated by the value TRUE in output parameter "Done". The signal status of the input parameter "Execute" influences the display duration at the output parameter "Done": "Execute" changes its value to FALSE during processing of the command ([HFXWH %XV\ 'RQH ([HFXWH %XV\ 'RQH &RPPDQG $ERUWHG (UURU &RPPDQG $ERUWHG (UURU "Execute" changes its value to FALSE after completion of the command The command is started with a positive edge at the input parameter "Execute". Depending on the programming, "Execute" can still be reset to the value FALSE during the command, or the value TRUE can be retained until after completion of the command. While the command is active, the output parameter "Busy" indicates the value TRUE. With conclusion of the command (for example, for Motion Control instruction "MC_Home": Homing was successful), output parameter "Busy" changes to FALSE and "Done" to TRUE. If "Execute" retains the value TRUE until after completion of the command, then "Done" also remains TRUE and changes its value to FALSE together with "Execute". If "Execute" has been set to FALSE before the command is complete, "Done" indicates the value TRUE for only one execution cycle. 4408 WinCC Basic V13.0 System Manual, 02/2014 Using technology functions 11.2 Using S7-1200 Motion Control Abort command If the Motion Control command is aborted during execution, this is indicated by the value TRUE in output parameter "CommandAborted". The signal status of the input parameter "Execute" influences the display duration at the output parameter "CommandAborted": "Execute" changes its value to FALSE before the command is aborted. "Execute" changes its value to FALSE after the command is aborted. Abort ([HFXWH %XV\ 'RQH Abort ([HFXWH %XV\ 'RQH &RPPDQG $ERUWHG (UURU &RPPDQG $ERUWHG (UURU The command is started with a positive edge at the input parameter "Execute". Depending on the programming, "Execute" can still be reset to the value FALSE during the command, or the value TRUE can be retained until after completion of the command. While the command is active, the output parameter "Busy" indicates the value TRUE. During command execution, the command is aborted by another Motion Control command. If the command is aborted, output parameter "Busy" changes to FALSE and "CommandAborted" to TRUE. If "Execute" retains the value TRUE until after the command is aborted, then "CommandAborted" also remains TRUE and changes its value to FALSE together with "Execute". If "Execute" has been set to FALSE before the command is aborted, "CommandAborted" indicates the value TRUE for only one execution cycle. WinCC Basic V13.0 System Manual, 02/2014 4409 Using technology functions 11.2 Using S7-1200 Motion Control Error during command execution If an error occurs during execution of the Motion Control command, this is indicated by the value TRUE in the output parameter "Error". The signal status of the input parameter "Execute" influences the display duration at the output parameter "Error": "Execute" changes its value to FALSE before the error occurs "Execute" changes its value to FALSE after the error occurs Error Error ([HFXWH %XV\ 'RQH ([HFXWH %XV\ 'RQH &RPPDQG $ERUWHG (UURU &RPPDQG $ERUWHG (UURU The command is started with a positive edge at the input parameter "Execute". Depending on the programming, "Execute" can still be reset to the value FALSE during the command, or the value TRUE can be retained until after completion of the command. While the command is active, the output parameter "Busy" indicates the value TRUE. An error occurred during command execution. When the error occurs, the output parameter "Busy" changes to FALSE and "Error" to TRUE. If "Execute" retains the value TRUE until after the error occurs, then "Error" also remains TRUE and only changes its value to FALSE together with "Execute". If "Execute" has been set to FALSE before the error occurs, "Error" indicates the value TRUE for only one execution cycle. Motion control instruction MC_MoveVelocity A "MC_MoveVelocity" command is started with a positive edge at the "Execute" parameter. The command objective is fulfilled when the assigned velocity is reached and the axis travels at constant velocity. When the assigned velocity is reached and maintained, this is indicated in the "InVelocity" parameter with the value TRUE. The motion of the axis can, for example, be stopped with an "MC_Halt" command. The output parameters "Busy", "CommandAborted", and "Error" signal that the command is still being processed, has been aborted or an error is pending. 4410 WinCC Basic V13.0 System Manual, 02/2014 Using technology functions 11.2 Using S7-1200 Motion Control During execution of the Motion Control command, the output parameter "Busy" indicates the value TRUE. If the command has been stopped by another command or by an error, the output parameter "Busy" changes its value to FALSE. This change occurs regardless of the signal at the input parameter "Execute". The output parameters "CommandAborted" and "Error" show the value TRUE for at least one cycle. These status messages are latched while input parameter "Execute" is set to TRUE. The behavior of the status bits is presented below for various example situations: The parameterized velocity is reached If the Motion Control command has been executed by the time the parameterized velocity is reached, this is indicated by the value TRUE in output parameter "InVelocity". The parameter "Execute" has no effect on the indication duration in the "InVelocity" parameter. ([HFXWH %XV\ ,Q9HORFLW\ &RPPDQG $ERUWHG (UURU The job is started with a positive edge at the "Execute" parameter. Depending on the programming, "Execute" can be reset to the FALSE value before or after the parameterized velocity has been reached. While the job is active, the parameter "Busy" shows the value TRUE. When the assigned velocity is reached, the "InVelocity" parameter changes to TRUE. The "Busy" and "InVelocity" parameters retain the TRUE value until the "MC_MoveVelocity" command is overridden by another Motion Control command or stopped by an error. The command is aborted prior to reaching the parameterized velocity If the Motion Control command is aborted before the parameterized velocity is reached, this is indicated by the value TRUE in output parameter "CommandAborted". The signal status of WinCC Basic V13.0 System Manual, 02/2014 4411 Using technology functions 11.2 Using S7-1200 Motion Control input parameter "Execute" influences the display duration at the output parameter "CommandAborted". "Execute" changes its value to FALSE before the command is aborted. "Execute" changes its value to FALSE after the command is aborted. Abort Abort ([HFXWH %XV\ ,Q9HORFLW\ ([HFXWH %XV\ ,Q9HORFLW\ &RPPDQG $ERUWHG (UURU &RPPDQG $ERUWHG (UURU The command is started with a positive edge at the input parameter "Execute". Depending on the programming, "Execute" can still be reset to the value FALSE during the command, or the value TRUE can be retained until after the command is aborted. While the command is active, the output parameter "Busy" indicates the value TRUE. During command execution, the command is aborted by another Motion Control command. If the command is aborted, output parameter "Busy" changes to FALSE and "CommandAborted" to TRUE. If "Execute" retains the value TRUE until after the command is aborted, then "CommandAborted" also remains TRUE and changes its status to FALSE together with "Execute". If "Execute" has been reset to FALSE before the command is aborted, "CommandAborted" indicates the value TRUE for only one execution cycle. Note Under the following conditions, an abort is not indicated in output parameter "CommandAborted": The parameterized velocity has been reached, input parameter "Execute" has the value FALSE, and a new Motion Control command is initiated. 4412 WinCC Basic V13.0 System Manual, 02/2014 Using technology functions 11.2 Using S7-1200 Motion Control An error has occurred prior to reaching the parameterized velocity If an error occurs during execution of the Motion Control command before the parameterized velocity has been reached, this is indicated by the value TRUE in the output parameter "Error". The signal status of the input parameter "Execute" influences the display duration at the output parameter "Error": "Execute" changes its value to FALSE before the error occurs "Execute" changes its value to FALSE after the error occurs Error Error ([HFXWH %XV\ ,Q9HORFLW\ ([HFXWH %XV\ ,Q9HORFLW\ &RPPDQG $ERUWHG (UURU &RPPDQG $ERUWHG (UURU The command is started with a positive edge at the input parameter "Execute". Depending on the programming, "Execute" can still be reset to the value FALSE during the command, or the value TRUE can be retained until after the error has occurred. While the command is active, the output parameter "Busy" indicates the value TRUE. An error occurred during command execution. When the error occurs, the output parameter "Busy" changes to FALSE and "Error" to TRUE. If "Execute" retains the value TRUE until after the error has occurred, then "Error" also remains TRUE and only changes its status to FALSE together with "Execute". If "Execute" has been reset to FALSE before the error occurs, "Error" indicates the value TRUE for only one execution cycle. Note Under the following conditions, an error is not indicated in output parameter "Error": The parameterized velocity has been reached, input parameter "Execute" has the value FALSE, and an axis error occurs (software limit switch is approached, for example). The error of the axis is only indicated in the "MC_Power" Motion Control instruction. WinCC Basic V13.0 System Manual, 02/2014 4413 Using technology functions 11.2 Using S7-1200 Motion Control Motion control instruction MC_MoveJog The commands of Motion Control instruction "MC_MoveJog" implement a jog operation. The motion control commands "MC_MoveJog" do not have a defined end. The command objective is fulfilled when the parameterized velocity is reached for the first time and the axis travels at constant velocity. When the parameterized velocity is reached, this is indicated by the value TRUE in output parameter "InVelocity". The order is complete when input parameter "JogForward" or "JogBackward" has been set to the value FALSE and the axis has come to a standstill. The output parameters "Busy", "CommandAborted", and "Error" signal that the command is still being processed, has been aborted or an error is pending. During processing of the motion control command, the output parameter "Busy" indicates the value TRUE. If the command has been completed, aborted, or stopped by an error, the output parameter "Busy" changes its value to FALSE. The output parameter "InVelocity" indicates the status TRUE, as long as the axis is moving at the parameterized velocity. The output parameters "CommandAborted" and "Error" indicate the status for at least one cycle. These status messages are latched as long as either input parameter "JogForward" or "JogBackward" is set to TRUE. The behavior of the status bits is presented below for various example situations: The parameterized velocity is reached and maintained If the motion control command has been executed by the time the parameterized velocity is reached, this is indicated by the value TRUE in output parameter "InVelocity". Jog mode is controlled by input parameter "JogForward" -RJ)RUZDUG -RJ%DFNZDUG %XV\ ,Q9HORFLW\ -RJ)RUZDUG -RJ%DFNZDUG %XV\ ,Q9HORFLW\ &RPPDQG $ERUWHG &RPPDQG $ERUWHG (UURU (UURU 4414 Jog mode is controlled by input parameter "JogBackward". WinCC Basic V13.0 System Manual, 02/2014 Using technology functions 11.2 Using S7-1200 Motion Control The command is started with a positive edge at the input parameter "JogForward" or "JogBackward". While the command is active, the output parameter "Busy" indicates the value TRUE. When the parameterized velocity is reached, the output parameter "InVelocity" changes to TRUE. When the input parameter "JogForward" or "JogBackward" is reset to the value FALSE, the axis motion ends. The axis starts to decelerate. As a result, the axis no longer moves at constant velocity and the output parameter "InVelocity" changes its status to FALSE. If the axis has come to a standstill, the motion control command is complete and the output parameter "Busy" changes its value to FALSE. The command is aborted during execution If the motion control command is aborted during execution, this is indicated by the value TRUE in output parameter "CommandAborted". The behavior is independent of whether or not the parameterized velocity has been reached. Jog mode is controlled by input parameter "JogForward". Jog mode is controlled by input parameter "JogBackward". Abort Abort -RJ)RUZDUG -RJ%DFNZDUG %XV\ ,Q9HORFLW\ -RJ)RUZDUG -RJ%DFNZDUG %XV\ &RPPDQG $ERUWHG (UURU ,Q9HORFLW\ &RPPDQG $ERUWHG (UURU The command is started with a positive edge at the input parameter "JogForward" or "JogBackward". While the command is active, the output parameter "Busy" indicates the value TRUE. During command execution, the command is aborted by another motion control command. If the command is aborted, output parameter "Busy" changes to FALSE and "CommandAborted" to TRUE. When the input parameter "JogForward" or "JogBackward" is reset to the value FALSE, the output parameter "CommandAborted" changes its value to FALSE. WinCC Basic V13.0 System Manual, 02/2014 4415 Using technology functions 11.2 Using S7-1200 Motion Control Note The command abort is indicated in the output parameter "CommandAborted" for only one execution cycle, if all conditions below are met: The input parameters "JogForward" and "JogBackward" have the value FALSE (but the axis is still decelerating) and a new motion control command is initiated. An error has occurred during command execution If an error occurs during execution of the motion control command, this is indicated by the value TRUE in output parameter "Error". The behavior is independent of whether or not the parameterized velocity has been reached. Jog mode is controlled by input parameter "JogForward". Jog mode is controlled by input parameter "JogBackward". Error -RJ)RUZDUG -RJ%DFNZDUG %XV\ ,Q9HORFLW\ Error -RJ)RUZDUG -RJ%DFNZDUG %XV\ ,Q9HORFLW\ &RPPDQG $ERUWHG (UURU &RPPDQG $ERUWHG (UURU The command is started with a positive edge at the input parameter "JogForward" or "JogBackward". While the command is active, the output parameter "Busy" indicates the value TRUE. 4416 WinCC Basic V13.0 System Manual, 02/2014 Using technology functions 11.2 Using S7-1200 Motion Control An error occurred during command execution. When the error occurs, the output parameter "Busy" changes to FALSE and "Error" to TRUE. When the input parameter "JogForward" or "JogBackward" is reset to the value FALSE, the output parameter "Error" changes its value to FALSE. Note An error occurrence is indicated in the output parameter "Error" for only one execution cycle, if all the conditions below are met: The input parameters "JogForward" and "JogBackward" have the value FALSE (but the axis is still decelerating) and a new error occurs (software limit switch is approached, for example). 11.2.10.6 Error displays of the Motion Control statements The Motion Control instructions indicate any errors in motion control commands and the technology object at the output parameters "Error", "ErrorID" and "ErroInfo" of the Motion Control instructions. Error display at output parameters "Error", "ErrorID" and "ErrorInfo" If the output parameter "Error" indicates the value TRUE, the complete command, or portions thereof, could not be executed. The cause of the error is indicated by the value in output parameter "ErrorID". Detailed information about the cause of the error is returned by the value in output parameter ErrorInfo. We distinguish between the following error classes for error indication: Operating error with axis stop (for example, "HW limit switch was approached") Operating errors with axis stop are errors that occur during runtime of the user program. If the axis is in motion, it is stopped with the configured deceleration or emergency stop deceleration, depending on the error. The errors are indicated in the error-triggering Motion Control instruction and in the Motion Control instruction "MC_Power". Operating error without axis stop (for example, "Axis is not homed") Operating errors without axis stop are errors that occur during runtime of the user program. If the axis is in motion, the motion is continued. The errors are only indicated in the Motion Control instruction which triggers the error. Configuration error in Motion Control instruction (for example "Incorrect value in parameter "Velocity") Parameterization errors occur when incorrect information is specified in the input parameters of Motion Control instructions. If the axis is in motion, the motion is continued. The errors are only indicated in the Motion Control instruction which triggers the error. WinCC Basic V13.0 System Manual, 02/2014 4417 Using technology functions 11.2 Using S7-1200 Motion Control Configuration error on technology object "Axis" (for example, "Value for "Acceleration" is invalid") A configuration error exists if one or more parameters are incorrectly configured in the axis configuration or if editable configuration data have been modified incorrectly during runtime of the program. An axis in motion is stopped with the configured emergency stop deceleration. The error is indicated in the error-triggering Motion Control instruction and in Motion Control instruction "MC_Power". Configuration error on technology object "Command table" (for example "Value for "Velocity" is invalid") There is a configuration error if one or more parameters are incorrectly set in the axis command table or if programmable configuration data have been modified incorrectly during runtime of the program. If the axis is in motion, the motion is continued. The errors are only indicated in the "MC_CommandTable" Motion Control instruction. Internal error When an internal error occurs, the axis is stopped. The errors are indicated in the errortriggering Motion Control instruction and, in some cases, in the Motion Control instruction "MC_Power". A detailed description of the ErrorIDs and ErrorInfos, as well as their remedies, is available in the Appendix (Page 4436). See also Overview of the Motion Control statements (Page 4400) Creating a user program (Page 4401) Programming notes (Page 4404) Behavior of the Motion Control commands after POWER OFF and restart (Page 4406) Monitoring active commands (Page 4406) List of ErrorIDs and ErrorInfos (technology objects as of V4) (Page 4436) 11.2.11 Axis - Diagnostics 11.2.11.1 Status and error bits (technology objects as of V4) You use the "Status and error bits" diagnostic function to monitor the most important status and error messages for the axis in the TIA Portal. The diagnostic function display is available in online mode in "Manual control" mode and in "Automatic control" when the axis is active. The status error messages have the following meaning: 4418 WinCC Basic V13.0 System Manual, 02/2014 Using technology functions 11.2 Using S7-1200 Motion Control Status messages Status message - Axis Enabled Description The axis is enabled and ready to be controlled via Motion Control commands. (Tag of technology object: <Axis name>.StatusBits.Enable) Homed The axis is homed and is capable of executing absolute positioning commands of Motion Control instruction "MC_MoveAbsolute". The axis does not have to be homed for relative positioning. Special situations: During active homing, the status is FALSE. If a homed axis undergoes passive homing, the status is set to TRUE during passive homing. (Tag of technology object: <Axis name>.StatusBits.HomingDone) Axis error An error has occurred in the "Axis" technology object. Additional information about the error is available in automatic control at the ErrorID and ErrorInfo parameters of the Motion Control instructions. In manual mode, the "Error message" box of the axis control panel displays detailed information about the cause of error. (Tag of technology object: <Axis name>.StatusBits.Error) Control panel active The "Manual control" mode was enabled in the axis control panel. The axis control panel has control priority over the "Axis" technology object. The axis cannot be controlled from the user program. (Tag of technology object: <Axis name>.StatusBits.ControlPanelActive) Restart necessary A modified configuration of the axis was downloaded to the load memory in CPU RUN operating mode. To download the modified configuration to the work memory, you need to restart the axis. Use the Motion Control instruction MC_Reset to do this. (Tag of technology object: <Axis name>.StatusBits.RestartRequired) Status message - Drive Description Ready The drive is ready for operation. (Tag of technology object: <Axis name>.StatusBits.DriveReady) Drive error The drive has reported an error due to loss of its "Drive ready" signal. (Tag of technology object: <Axis name>.ErrorBits.DriveFault) Status message - Motion Description Standstill The axis is at a standstill. (Tag of technology object: <Axis name>.StatusBits.StandStill) Acceleration The axis accelerates. (Tag of technology object: <Axis name>.StatusBits.Accelerating) Constant velocity The axis travels at constant velocity. (Tag of technology object: <Axis name>.StatusBits.ConstantVelocity) Deceleration The axis decelerates (slows down). (Tag of technology object: <Axis name>.StatusBits.Decelerating) WinCC Basic V13.0 System Manual, 02/2014 4419 Using technology functions 11.2 Using S7-1200 Motion Control Status message - Motion type Description Positioning The axis executes a positioning command of the Motion Control instruction "MC_MoveAbsolute", "MC_MoveRelative" or the axis control panel. (Tag of technology object: <Axis name>.StatusBits.PositioningCommand) Travel with velocity specification The axis executes a command with velocity specification of the Motion Control instruction "MC_MoveVelocity", "MC_MoveJog" or the axis control panel. (Tag of technology object: <Axis name>.StatusBits.VelocityCommand) Homing The axis executes a homing command of the Motion Control instruction "MC_Home" or the axis control panel. (Tag of technology object: <Axis name>.StatusBits.HomingCommand) Command table active The axis is controlled by Motion Control instruction "MC_CommandTable". (Tag of technology object: <Axis name>.StatusBits.CommandTableActive) Limit switch status messages Limit switch status message Description Lower SW limit switch has been reached A software limit switch was reached or exceeded. Upper SW limit switch has been reached A hardware limit switch was reached or exceeded. Lower HW limit switch was reached The lower hardware limit switch was reached or exceeded. Upper HW limit switch was reached The upper hardware limit switch was reached or exceeded. (Tag of technology object: <Axis name>.StatusBits.SWLimitMinActive) (Tag of technology object: <Axis name>.StatusBits.SWLimitMaxActive) (Tag of technology object: <Axis name>.StatusBits.HWLimitMinActive) (Tag of technology object: <Axis name>.StatusBits.HWLimitMaxActive) Error messages Error message Description SW limit switch has been reached A software limit switch was reached or exceeded. HW limit switch has been reached A hardware limit switch was reached or exceeded. (Tag of technology object: <Axis name>.ErrorBits.SWLimit) (Tag of technology object: <Axis name>.ErrorBits.HWLimit) Impermissible motion direction The motion direction of the command does not match the configured motion direction. (Tag of technology object: <Axis name>.ErrorBits.DirectionFault) PTO already in use A second axis is using the same PTO (Pulse Train Output) and HSC (High Speed Counter) and is enabled with "MC_Power". (Tag of technology object: <Axis name>.ErrorBits.HWUsed) Configuration error The "Axis" technology object was incorrectly configured or editable configuration data were modified incorrectly during runtime of the user program. (Tag of technology object: <Axis name>.ErrorBits.ConfigFault) Internal error An internal error has occurred. (Tag of technology object: <Axis name>.ErrorBits.SystemFault) 4420 WinCC Basic V13.0 System Manual, 02/2014 Using technology functions 11.2 Using S7-1200 Motion Control The output window below shows the first reported and still unacknowledged error. See also StatusBits tags as of V4 (Page 4459) ErrorBits tags as of V4 (Page 4463) Diagnostics - Status and error bits ("Axis" technology object V1...3) (Page 4478) Compatibility list of tags (Page 4325) Motion status (Page 4421) 11.2.11.2 Motion status Use the "Motion status" diagnostic function to monitor the motion status of the axis in the TIA Portal. The diagnostic function display is available in online mode in "Manual control" mode and in "Automatic control" when the axis is active. The displayed status information has the following meaning: Status Description Current position The "Current position" box indicates the current axis position. If the axis is not homed, the value indicates the position value relative to the enable position of the axis. (Tag of technology object: <Axis name>.Position) Current velocity The "Current velocity" box indicates the current axis velocity. (Tag of technology object: <Axis name>.Velocity) Target position The "Target position" box indicates the current target position of an active positioning command or of the axis command table. The value of the "Target position" is only valid during execution of a positioning command. (Tag of technology object: <Axis name>.StatusPositioning.TargetPosition) Remaining traversing distance The "Remaining traversing distance" box indicates the traversing distance currently remaining for an active positioning command or the axis command table. The "Remaining traversing distance" value is only valid during execution of a positioning command. (Tag of technology object: <Axis name>.StatusPositioning.Distance) See also Position tag as of V4 (Page 4446) Velocity tag as of V4 (Page 4446) StatusPositioning tags as of V4 (Page 4458) Compatibility list of tags (Page 4325) Status and error bits (technology objects as of V4) (Page 4418) 11.2.11.3 Dynamics settings Use the "Dynamics settings" diagnostic function to monitor the dynamic limits of the axis in the TIA Portal. The diagnostic function display is available in online mode in "Manual control" mode WinCC Basic V13.0 System Manual, 02/2014 4421 Using technology functions 11.2 Using S7-1200 Motion Control and in "Automatic control" when the axis is active. The displayed status information has the following meaning: Dynamic limit Description Acceleration The "Acceleration" box indicates the currently configured acceleration of the axis. (Tag of technology object: <Axis name>.DynamicDefaults.Acceleration) Deceleration The "Deceleration" box indicates the currently configured deceleration of the axis. (Tag of technology object: <Axis name>.DynamicDefaults.Deceleration) Emergency stop deceleration The "Emergency stop deceleration" box indicates the currently configured emergency stop deceleration of the axis. (Tag of technology object: <Axis name>.DynamicDefaults.EmergencyDeceleration) Jerk The "Velocity" box indicates the current axis step velocity configured. (axis technology object as of V2) (Tag of technology object: <Axis name>.DynamicDefaults.Jerk) See also DynamicDefaults tags as of V4 (Page 4453) Compatibility list of tags (Page 4325) 11.2.12 Appendix 11.2.12.1 Using multiple axes with the same PTO Use the Motion Control functionality of the CPU S7-1200 to run multiple positioning axis technology objects with the same PTO (Pulse Train Output) and thus with the same CPU outputs. This is appropriate, for example, if different axis configurations are to be used for different production sequences via one PTO. As described below, it is possible to switch 4422 WinCC Basic V13.0 System Manual, 02/2014 Using technology functions 11.2 Using S7-1200 Motion Control between these axis configurations as often as necessary. The following diagram presents the basic functional relationships: 7HFKQRORJ\REMHFW 3RVLWLRQLQJD[LVB 0&B3RZHUB,QVWDQFHB 372 3XOVH7UDLQ2XWSXW $[LVFRQILJXUDWLRQ 7HFKQRORJ\REMHFW 3RVLWLRQLQJD[LVB , , , , , , , , 5816723 (5525 0$,17 ', &38& '&'&'& ' 0&B3RZHUB,QVWDQFHB; 7HFKQRORJ\REMHFW 3RVLWLRQLQJD[LVB; , , , , , , 6,0$7,& 6 $[LVFRQILJXUDWLRQ 0&B3RZHUB,QVWDQFHB ;31/$1 $[LVFRQILJXUDWLRQ; In this example, several positioning axis technology objects, each with its own axis configuration, use the same PTO. Each axis must be called in the user program with a separate call of Motion Control instruction "MC_Power" with a separate instance data block. Only one axis at a time may use the PTO. The axis that is currently using the PTO indicates this with tag <Axis name>.StatusBits.Activated = TRUE. Switchover of the positioning axis technology object The program scheme described below shows you how to switch between different technology objects and, thus, between different axis configurations. To use the same PTO with multiple axes without error indications, only the Motion Control instructions of the axis currently being used may be called. The following diagram presents this principle using Motion Control instruction "MC_Power" as an example: WinCC Basic V13.0 System Manual, 02/2014 4423 Using technology functions 11.2 Using S7-1200 Motion Control &DOOLQDFWLYH (1 0&B3RZHUB,QVWDQFHB 7HFKQRORJ\REMHFW 3RVLWLRQLQJD[LVB 372 3XOVH7UDLQ2XWSXW 0&B3RZHUB,QVWDQFHB; ', &38& '&'&'& ' 7HFKQRORJ\REMHFW 3RVLWLRQLQJD[LVB; &DOOLQDFWLYH (1 , , , , , , 6,0$7,& 6 6WDWXV%LWV$FWLYDWHG 758( (UURU%LWV+Z8VHG )$/6( 5816723 (5525 0$,17 (QDEOH 758( (UURU )$/6( 7HFKQRORJ\REMHFW 3RVLWLRQLQJD[LVB (1 0&B3RZHUB,QVWDQFHB , , , , , , , , &DOODFWLYH ;31/$1 The tags of the activated axis ("Positioning axis_2" here) show the following typical indicators in the user program: <Axis name>.StatusBits.Activated = TRUE <Axis name>.ErrorBits.HWUsed = FALSE To switch from one positioning axis technology object to another, follow the steps described below. In the example, a switch is made from "Positioning axis_2" to "Positioning axis_1": 1. End any active traversing motions of activated "Positioning axis_2" 2. Disable "Positioning axis_2" with the associated Motion Control instruction "MC_Power" using input parameter Enable = FALSE 3. To verify that "Positioning axis_2" has been disabled, use an AND operation of output parameter Status = FALSE of Motion Control instruction "MC_Power" and technology object tag <Axis name>.StatusBits.Enable = FALSE. 4. Deactivate the conditional call of the Motion Control instructions for "Positioning axis_2". 5. Activate the conditional call of the Motion Control instruction for "Positioning axis_1". At the first call of the corresponding Motion Control instruction "MC_Power", "Positioning axis_2" is deactivated and "Positioning axis_1" is activated. 6. Enable "Positioning axis_1" with the associated Motion Control instruction "MC_Power" using input parameter Enable = TRUE. 7. To verify that "Positioning axis_1" has been enabled, use an AND operation of output parameter Status = TRUE of Motion Control instruction "MC_Power" and technology object tag <Axis name>.StatusBits.Enable = TRUE. It is also always possible to cyclically call all Motion Control instructions of all axes working with a single PTO. 4424 WinCC Basic V13.0 System Manual, 02/2014 Using technology functions 11.2 Using S7-1200 Motion Control &DOODFWLYH (1 0&B3RZHUB,QVWDQFHB 7HFKQRORJ\REMHFW 3RVLWLRQLQJD[LVB 372 3XOVH7UDLQ2XWSXW 6,0$7,& 6 6WDWXV%LWV$FWLYDWHG 758( (UURU%LWV+Z8VHG )$/6( 5816723 (5525 0$,17 (QDEOH 758( (UURU )$/6( 7HFKQRORJ\REMHFW 3RVLWLRQLQJD[LVB ', &38& '&'&'& ' 0&B3RZHUB,QVWDQFHB; (QDEOH )$/6( (UURU 758( 7HFKQRORJ\REMHFW 3RVLWLRQLQJD[LVB; &DOODFWLYH (1 , , , , , , (1 0&B3RZHUB,QVWDQFHB &DOODFWLYH 6WDWXV%LWV$FWLYDWHG )$/6( (UURU%LWV+Z8VHG 758( , , , , , , , , (QDEOH )$/6( (UURU 758( ;31/$1 6WDWXV%LWV$FWLYDWHG )$/6( (UURU%LWV+Z8VHG 758( When an axis is enabled (here "Positioning axis_2"), this axis becomes active. In contrast to the conditional call, the Motion Control instructions of the deactivated axes (here "Positioning axis_1" and "Positioning axis_x") indicate errors. The tags of these axes indicate the status <Axis name>.StatusBits.Activated = FALSE and <Axis name>.ErrorBits.HWUsed = TRUE. Use the conditional call of the Motion Control instructions if you want to implement the user program without error indicators. See also Tags of the positioning axis technology object as of V4 (Page 4446) Using multiple drives with the same PTO (Page 4426) Tracking jobs from higher priority classes (execution levels) (Page 4427) Special cases for use of software limit switches (Page 4429) List of ErrorIDs and ErrorInfos (technology objects as of V4) (Page 4436) WinCC Basic V13.0 System Manual, 02/2014 4425 Using technology functions 11.2 Using S7-1200 Motion Control 11.2.12.2 Using multiple drives with the same PTO If multiple drives are to be used, they can be run with a common PTO (Pulse Train Output) using changeover. The following diagram represents the basic circuit design: S zpth{pjG z^TXYWW , , , , , , , , , , , , , , 6LJQDOERDUG y|uVz{vw lyyvy thpu{ ', jw|GXYX[j kjVkjVkj ' XawuVshuV 3XOVHDQGGLUHFWLRQRXWSXWV 3RZHUXQLW 3RZHUXQLW The changeover between drives can be controlled, if required, by the user program via a digital output. If different axis configurations are required for the different drives, a changeover between these configurations is required for the PTO. For additional information on this topic, refer to "Using multiple axes with the same PTO (Page 4422)". See also Tags of the positioning axis technology object as of V4 (Page 4446) Using multiple axes with the same PTO (Page 4422) Tracking jobs from higher priority classes (execution levels) (Page 4427) Special cases for use of software limit switches (Page 4429) List of ErrorIDs and ErrorInfos (technology objects as of V4) (Page 4436) 4426 WinCC Basic V13.0 System Manual, 02/2014 Using technology functions 11.2 Using S7-1200 Motion Control 11.2.12.3 Tracking jobs from higher priority classes (execution levels) Depending on the application, it may be necessary to start Motion Control commands (for example, interrupt-controlled) in a higher priority class (execution level). The Motion Control instructions must be called at short intervals for status monitoring. Motion Control commands cannot be sufficiently closely monitored if the higher priority Motion Control commands are called only once or at too great an interval. Tracking in such cases can be carried out in the cycle OB. An instance data block that is not currently being utilized must be available for each start of a higher priority Motion Control command. Refer to the following flow chart to see how you start Motion Control commands in a higher priority class (for example, hardware interrupt OB) and continue tracking in the program cycle OB: WinCC Basic V13.0 System Manual, 02/2014 4427 Using technology functions 11.2 Using S7-1200 Motion Control F\FOH2% SURFHVV2% 6WDUWSURFHVV DODUP2% $GGLWLRQDOJHQHUDO SURJUDPFRGH 1H[WJHQHUDO SURJUDPFRGH 9DULDEOH '%[BXVHG 758(" \HV 2SHQLQJWKH0RWLRQ&RQWURO LQVWUXFWLRQVZLWK'%[ DQG([HFXWH 758( UHDGLQJVWDWXVRIRUGHU 9DULDEOH '%[BXVHG 758(" QR \HV QR 0RWLRQ&RQWURO MREILQLVKHGRUFDQFHOHG" QR 4XHULHGDOO'%V DYDLODEOH" QR \HV 2SHQLQJ0RWLRQ&RQWUROLQVWUXFWLRQ ZLWK'%[DQG([HFXWH )$/6( SUHSDUH'%IRUUHGHSOR\PHQW '%[ QH[W'% DYDLODEOH 5HVHWYDULDEOH '%[BXVHG 4XHULHGDOO'%V DYDLODEOH" \HV 1H[WJHQHUDO SURJUDPFRGH 6HWYDULDEOH '%[BXVHG 2SHQLQJWKH0RWLRQ&RQWURO LQVWUXFWLRQVZLWK'%[ DQG([HFXWH 758( VWDUWLQJRUGHU (UURU LQVXIILFLHQW'%V QR '%[ QH[W'%DYDLODEOH \HV F\FOHFNHFNSRLQW 1H[WJHQHUDO SURJUDPFRGH (QGRISURFHVV DODUP2% Depending on the frequency of the Motion Control commands you want to start, you will have to generate a sufficient number of instance data blocks. Users determine which instance data block is currently used in the DBx_used tags. 4428 WinCC Basic V13.0 System Manual, 02/2014 Using technology functions 11.2 Using S7-1200 Motion Control Start of Motion Control command in the hardware interrupt OB Binary queries of the DBx_used tags (orange) are used to find an instance data block not currently in use. If such an instance data block is found, the utilized instance data block is marked as "used" (green) and the Motion Control command is started with this instance data block (blue). Any other program sections of the hardware interrupt OB are then executed, followed by a return to the program cycle OB. Tracking of started Motion Control commands in the program cycle OB All instance data blocks available in the cycle OB are checked to determine if they are currently in use by means of the DBx_used tag (violet). If an instance data block is in use (Motion Control command is being processed), the Motion Control instruction with this instance data block and input parameter Execute = TRUE is called to read out the status messages (red). If the command is complete or has been aborted, the following actions are taken next (blue green): Call of Motion Control instruction with input parameter Execute = FALSE Resetting the DBx_used tag This completes the command tracking, and the instance data block is now available for use again. See also Tags of the positioning axis technology object as of V4 (Page 4446) Using multiple axes with the same PTO (Page 4422) Using multiple drives with the same PTO (Page 4426) Special cases for use of software limit switches (Page 4429) List of ErrorIDs and ErrorInfos (technology objects as of V4) (Page 4436) 11.2.12.4 Special cases for use of software limit switches Software limit switches in conjunction with a homing operation Due to unfavorably parameterized homing jobs, the braking action of the axis may be influenced at the software limit switch. Take the following examples into consideration when developing your program. WinCC Basic V13.0 System Manual, 02/2014 4429 Using technology functions 11.2 Using S7-1200 Motion Control Example 1: During a travel command, a homing job (for example, Set reference point) offsets the current axis position in the direction of the software limit switch. It is still possible to bring the axis to a standstill before reaching the software limit switch: Y ROGD[LV SRVLWLRQ QHZD[LV SRVLWLRQ VRIWZDUH OLPLWVZLWFK V The green curve shows the motion without the homing job. The axis brakes at the configured deceleration and comes to a standstill at a position before the software limit switch. A new axis position is set as a result of the homing job. The area between the old and new axis position is thus "skipped". Based on the new axis position, the axis would theoretically be stopped with the configured deceleration at a position after the software limit switch (red curve). Because braking with the configured deceleration is no longer sufficient, the axis actually follows the blue curve. Following constant motion, the axis brakes at the configured emergency stop deceleration and comes to a standstill at the position of the software limit switch. Example 2: During a travel command, a homing job (for example, Set reference point) offsets the current axis position in the direction of the software limit switch. In contrast to example 1, it is no longer 4430 WinCC Basic V13.0 System Manual, 02/2014 Using technology functions 11.2 Using S7-1200 Motion Control possible to bring the axis to a standstill before reaching the software limit switch. The axis overruns the position of the software limit switch. Y ROGD[LV SRVLWLRQ QHZD[LV SRVLWLRQ V VRIWZDUH OLPLWVZLWFK The green curve shows the motion without the homing job. The axis brakes at the configured deceleration and comes to a standstill at a position before the software limit switch. A new axis position is set as a result of the homing job. The area between the old and new axis position is thus "skipped". Based on the new axis position, the axis would theoretically be stopped with the configured deceleration at a position well after the software limit switch (red curve). Because braking with the configured deceleration is no longer sufficient, the axis actually follows the blue curve. The axis brakes with the configured emergency stop deceleration. However, the emergency stop deceleration is not sufficient to stop the axis at the position of the software limit switch. The position of the software limit switch is overrun. WinCC Basic V13.0 System Manual, 02/2014 4431 Using technology functions 11.2 Using S7-1200 Motion Control Example 3: During a braking operation, a homing job (for example, Set reference point) offsets the current axis position in the direction of the software limit switch. It is still possible to bring the axis to a standstill before reaching the software limit switch: Y QHZD[LV SRVLWLRQ VRIWZDUH OLPLWVZLWFK V ROGD[LV SRVLWLRQ The green curve shows the motion without the homing job. The axis brakes at the configured deceleration and comes to a standstill at a position before the software limit switch. A new axis position is set as a result of the homing job. The area between the old and new axis position is thus "skipped". Based on the new axis position, the axis would theoretically be stopped with the configured deceleration at a position after the software limit switch (red curve). Because braking with the configured deceleration is no longer sufficient, the axis actually follows the blue curve. Following constant motion, the axis brakes at the configured emergency stop deceleration and comes to a standstill at the position of the software limit switch. Example 4: During a braking operation, a homing job (for example, Set reference point) offsets the current axis position in the direction of the software limit switch. In contrast to example 3, it is no longer possible to bring the axis to a standstill before reaching the software limit switch. The axis overruns the position of the software limit switch. 4432 WinCC Basic V13.0 System Manual, 02/2014 Using technology functions 11.2 Using S7-1200 Motion Control Y ROGD[LV SRVLWLRQ QHZD[LV SRVLWLRQ V VRIWZDUH OLPLWVZLWFK The green curve shows the motion without the homing job. The axis brakes at the configured deceleration and comes to a standstill at a position before the software limit switch. A new axis position is set as a result of the homing job. The area between the old and new axis position is thus "skipped". Based on the new axis position, the axis would theoretically be stopped with the configured deceleration at a position well after the software limit switch (red curve). Because braking with the configured deceleration is no longer sufficient, the axis actually follows the blue curve. The axis brakes with the configured emergency stop deceleration. However, the emergency stop deceleration is not sufficient to stop the axis at the position of the software limit switch. The position of the software limit switch is overrun. See also Software limit switches and software limit switch position changes. (Page 4433) Software limit switches in conjunction with dynamic changes (Page 4434) Behavior of axis when position limits is tripped (Page 4343) Software limit switches and software limit switch position changes. An incorrect change in the position of the software limit switch during the runtime of the user program can abruptly reduce the distance between the current axis position and the position of the software limit switch. WinCC Basic V13.0 System Manual, 02/2014 4433 Using technology functions 11.2 Using S7-1200 Motion Control The axis response is similar to that described in Software limit switches in conjunction with a homing operation (Page 4429). See also Software limit switches in conjunction with a homing operation (Page 4429) Software limit switches in conjunction with dynamic changes (Page 4434) Behavior of axis when position limits is tripped (Page 4343) Software limit switches in conjunction with dynamic changes It is possible to influence the deceleration of the axis in the area of the software limit switches in conjunction with overriding motion commands. This applies when the overriding motion command is started with a lower deceleration (tag <Axis name>.DynamicDefaults.Deceleration). Take the following examples into consideration when developing your program. Example 1: During axis motion, an active motion command is overridden by another motion command with a lower deceleration: Y UHSODFHPHQWPRWLRQ VWDUWHG 4434 VRIWZDUHOLPLW VZLWFK V WinCC Basic V13.0 System Manual, 02/2014 Using technology functions 11.2 Using S7-1200 Motion Control The green curve shows the motion of an active command without this command being overridden. The axis brakes at the configured deceleration and comes to a standstill at a position before the software limit switch. Based on the overriding motion command with lower deceleration, the axis would theoretically be stopped with the configured deceleration at a position after the software limit switch (red curve). Because braking with the configured deceleration of the overriding motion command is no longer sufficient, the axis actually follows the blue curve. Following a constant motion, the axis brakes at the emergency stop deceleration and comes to a standstill at the position of the software limit switch. Example 2: During braking of the axis, an active motion command is overridden by another motion command with a lower deceleration: Y UHSODFHPHQWPRWLRQ VWDUWHG VRIWZDUHOLPLW VZLWFK V The green curve shows the motion of an active command without this command being overridden. The axis brakes at the configured deceleration and comes to a standstill at a position before the software limit switch. Based on the overriding motion command with lower deceleration, the axis would theoretically be stopped at a position well after the software limit switch (red curve). Because braking with the configured deceleration of the overriding motion command is no longer sufficient, the axis actually follows the blue curve. Following a constant motion, the axis brakes at the emergency stop deceleration and comes to a standstill at the position of the software limit switch. WinCC Basic V13.0 System Manual, 02/2014 4435 Using technology functions 11.2 Using S7-1200 Motion Control See also Software limit switches in conjunction with a homing operation (Page 4429) Software limit switches and software limit switch position changes. (Page 4433) Behavior of axis when position limits is tripped (Page 4343) 11.2.12.5 Reducing velocity for a short positioning duration The CPU can reduce the velocity of a positioning command when the planned positioning duration is < 2 ms. The velocity of command execution will then be reduced for the entire duration. The reduced velocity (pulses per s) is calculated as follows: Reduced velocity = Number of pulses to be output * 500Hz Velocity is not reduced if the planned positioning duration is >= 2 ms. 11.2.12.6 Dynamic adjustment of start/stop velocity The configuration of your velocity limits (start/stop velocity and maximum velocity), the dynamic values (acceleration, deceleration and jerk) and the target speed of the traversing command may under certain circumstances result in the start/stop velocity being dynamically adjusted by the CPU. This is for example the case when, due to a low configured start/stop velocity, the time required for the first pulses would be longer than that possible for the entire acceleration. The first pulse is in these cases output at a greater velocity than the configured start/stop velocity. The subsequent pulses are also dynamically adjusted to ensure the acceleration process can be completed in the specified time. Ensure in the event of any pulse loss that the hardware (drive) you use is adjusted to this situation, or change the dynamic settings of your axis to avoid dynamic adjustment of the start/ stop velocity. 11.2.12.7 List of ErrorIDs and ErrorInfos (technology objects as of V4) The following table lists all ErrorIDs and ErrorInfos that can be indicated in Motion Control instructions. In addition to the cause of the error, remedies for eliminating the error are also listed: Operating error with axis stop ErrorID ErrorInfo 16#8000 4436 Remedy Drive error, loss of "Drive ready" 16#0001 16#8001 Description - Acknowledge error with instruction "MC_Reset"; provide drive signal; restart command, if necessary Lower SW limit switch has been tripped WinCC Basic V13.0 System Manual, 02/2014 Using technology functions 11.2 Using S7-1200 Motion Control ErrorID ErrorInfo Description Remedy 16#000E The position of the lower SW limit switch was reached with the currently configured deceleration 16#000F The position of the lower SW limit switch was reached with the emergency stop deceleration Acknowledge the error with instruction "MC_Reset"; use a motion command to move the axis in the positive direction out of the range of the SW limit switch 16#0010 The position of the lower SW limit switch was exceeded with the emergency stop deceleration 16#8002 Upper SW limit switch has been tripped 16#000E The position of the upper SW limit switch was reached with the currently configured deceleration 16#000F The position of the upper SW limit switch was reached with the emergency stop deceleration 16#0010 The position of the upper SW limit switch was exceeded with the emergency stop deceleration 16#8003 Acknowledge the error with instruction "MC_Reset"; use a motion command to move the axis in the negative direction out of the range of the SW limit switch Lower HW limit switch was reached 16#000E The lower HW limit switch was reached. The axis was stopped with the emergency stop deceleration. (During an active homing procedure, the homing switch was not found) 16#8004 Acknowledge the error for an enabled axis with instruction "MC_Reset"; use a motion command to move the axis in the positive direction out of the range of the HW limit switch. Upper HW limit switch was reached 16#000E The upper HW limit switch has been reached. The axis was stopped with the emergency stop deceleration. (During an active homing procedure, the homing switch was not found) 16#8005 Acknowledge the error for an enabled axis with instruction "MC_Reset"; use a motion command to move the axis in the negative direction out of the range of the HW limit switch. PTO/HSC are already being used by another axis 16#0001 - The axis was configured incorrectly: Correct the configuration of the PTO (Pulse Train Output) / HSC (High Speed Counter) and download it to the controller More than one axis is to run with one PTO: Another axis is using the PTO / HSC. If the current axis is to assume the control, the other axis must be disabled with "MC_Power" Enable = FALSE. (see also Using multiple axes with the same PTO (Page 4422)) 16#8006 A communication error in the control panel has occurred 16#0012 16#8007 A timeout has occurred Check the cable connection and press the "Manual control" button again. The axis cannot be enabled. 16#0025 Restarting Wait until the axis restart is complete. 16#0026 Executing loading process in RUN mode Wait until the loading process is complete. 16#8008 WinCC Basic V13.0 System Manual, 02/2014 Impermissible motion direction 4437 Using technology functions 11.2 Using S7-1200 Motion Control ErrorID ErrorInfo Description Remedy 16#002E The selected motion direction is not allowed. 16#002F A reversing motion is not possible with the selected motion direction. Adjust the motion direction and restart the command. Adjust the allowed direction of rotation in the technology object configuration under "Extended parameters > Mechanics" Restart the command. Operating error without axis stop ErrorID ErrorInfo 16#8200 Description Remedy Axis is not enabled 16#0001 16#8201 - Enable the axis; restart the command Axis has already been enabled by another "MC_Power" instance 16#0001 16#8202 - Enable the axis with only one "MC_Power" instance The maximum number of simultaneously active Motion Control commands has been exceeded (maximum of 200 commands for all motion control technology objects) 16#0001 - Reduce the number of simultaneously active commands; restart the command A command is active if parameter "Busy" = TRUE in the Motion Control instruction. 16#8203 Axis is currently operated in "Manual control" (axis control panel) 16#0001 16#8204 Exit "Manual control"; restart the command Axis is not homed 16#0001 16#8205 - Home the axis with instruction "MC_Home"; restart the command The axis is currently controlled by the user program (the error is only displayed in the axis control panel) 16#0013 The axis is enabled in the user program. 16#0001 - 16#8206 Disable axis with instruction "MC_Power" and select "Manual control" again in the axis control panel Technology object not activated yet 16#8207 Enable the axis with instruction "MC_Power" Enable = TRUE or enable the axis in the axis control panel. Command rejected 16#0016 Active homing is running; another homing method cannot be started. Wait for active homing to finish or abort the active homing with a motion command, for example, "MC_Halt". 16#0018 The axis cannot be moved with a command table while it is being actively or passively homed. Wait until direct or passive homing is complete. 16#0019 The axis cannot be actively or passively homed while a command table is being processed. Wait for command table to finish or abort the command table with a motion command, for example, "MC_Halt". 16#8208 Difference between maximum and start/stop velocity is invalid 16#0002 4438 - Number format of value is invalid Correct the value; restart the command WinCC Basic V13.0 System Manual, 02/2014 Using technology functions 11.2 Using S7-1200 Motion Control ErrorID ErrorInfo Description 16#000A Value is less than or equal to 0 16#8209 Remedy Invalid acceleration for technology object "Axis" 16#0002 Number format of value is invalid 16#000A Value is less than or equal to 0 16#0013 The axis is enabled in the user program. Disable the axis with the "MC_Power" instruction; restart again 16#0027 The axis is currently being operated in "Manual control" (axis control panel) Exit "Manual control"; restart again 16#820A Correct the value; restart the command It is not possible to restart the axis 16#820B It is not possible to execute the command table 16#0026 Executing loading process in RUN mode Wait until the loading process is complete. Block parameter error ErrorID ErrorInfo 16#8400 Description Remedy Invalid value at parameter "Position" of the Motion Control instruction 16#0002 Number format of value is invalid 16#0005 The value is outside the number range (greater than 1e12) 16#0006 The value is outside the number range (less than -1e12) 16#8401 Correct the value; restart the command Invalid value at parameter "Distance" of the Motion Control instruction 16#0002 Number format of value is invalid 16#0005 The value is outside the number range (greater than 1e12) 16#0006 The value is outside the number range (less than -1e12) 16#8402 Correct the value; restart the command Invalid value at parameter "Velocity" of the Motion Control instruction 16#0002 Number format of value is invalid 16#0008 Value is greater than the configured maximum velocity 16#0009 Value is less than the configured start/stop velocity 16#0024 Value is less than 0 16#8403 Correct the value; restart the command Invalid value at parameter "Direction" of the Motion Control instruction 16#0011 The selection value is invalid 16#0011 The selection value is invalid Correct the selection value; restart the command 16#0015 Active/passive homing is not configured Correct the configuration and download it to the controller; enable the axis and restart the command 16#8404 Correct the selection value; restart the command Invalid value at parameter "Mode" of the Motion Control instruction WinCC Basic V13.0 System Manual, 02/2014 4439 Using technology functions 11.2 Using S7-1200 Motion Control ErrorID ErrorInfo Description Remedy 16#0017 The direction reversal is activated at the hardware limit switch, despite the fact that the hardware limit switches are disabled Activate the HW limit switch using the tag <Axis name>.PositionLimitsHW.Active = TRUE, restart the command Correct the configuration and download it to the controller; enable the axis and restart the command 16#8405 Invalid value at parameter "StopMode" of the Motion Control instruction 16#0011 16#8406 Correct the selection value; enable the axis again Simultaneous forward and backward jogging is not allowed 16#0001 16#8407 - Take steps to ensure that parameters "JogForward" and "JogBackward" do not have signal status TRUE simultaneously; restart the command. Switching to another axis with instruction "MC_Power" is only permitted after disabling the active axis. 16#0001 16#8408 - Disable the active axis; it is then possible to switch to the other axis and enable it. Invalid value at parameter "Axis" of the Motion Control instruction 16#001A The specified value does not match the required technology object version 16#001B The specified value does not match the required technology object type 16#001C The specified value is not a Motion Control technology data block 16#001A The specified value does not match the required technology object version 16#001B The specified value does not match the required technology object type 16#001C The specified value is not a Motion Control technology data block 16#8409 Correct the value; restart the command Invalid value at parameter "CommandTable" of the Motion Control instruction 16#840A Correct the value; restart the command Invalid value at parameter "StartStep" of the Motion Control instruction 16#000A Value is less than or equal to 0 16#001D The start step is greater than the end step 16#001E Value is greater than 32 16#840B Correct the value; restart the command Invalid value at parameter "EndStep" of the Motion Control instruction 16#000A Value is less than or equal to 0 16#001E Value is greater than 32 16#840C Correct the value; restart the command Invalid value at parameter "RampUpTime" of the Motion Control instruction 16#0002 Number format of value is invalid 16#000A Value is less than or equal to 0 16#840D Correct the value; restart the command Invalid value at parameter "RampDownTime" of the Motion Control instruction 16#0002 Number format of value is invalid 16#000A Value is less than or equal to 0 16#840E 4440 The selection value is invalid Correct the value; restart the command Invalid value at parameter "EmergencyRampTime" of the Motion Control instruction 16#0002 Number format of value is invalid 16#000A Value is less than or equal to 0 Correct the value; restart the command WinCC Basic V13.0 System Manual, 02/2014 Using technology functions 11.2 Using S7-1200 Motion Control ErrorID ErrorInfo 16#840F Description Remedy Invalid value at parameter "JerkTime" of the Motion Control instruction 16#0002 Number format of value is invalid 16#000A Value is less than or equal to 0 16#8410 Correct the value; restart the command Invalid value at parameter "Parameter" of the Motion Control instruction 16#0028 Data types of VARIANT pointer "Parameter" and "Value" do not match. Use a suitable data type; restart command 16#0029 VARIANT pointer "Parameter" does not point to a data block of the technology object. Correct the VARIANT pointer; restart the command 16#002A The value at the VARIANT pointer "Parameter" cannot be read. Correct the VARIANT pointer; restart the command 16#002B The value at the VARIANT pointer "Parameter" cannot be written. Correct the VARIANT pointer or value; restart the command 16#002C The axis is not disabled. Disable the axis; restart the command 16#0002 Number format of value is invalid 16#8411 Invalid value at parameter "Value" of the Motion Control instruction Correct the value; restart the command Configuration error of the axis ErrorID ErrorInfo 16#8600 Description Remedy Parameter assignment of pulse generator (PTO is invalid 16#000B The address is invalid 16#0014 The selected hardware is used by another application 16#8601 Download error-free configuration to the controller; enable the axis again with instruction "MC_Power" Parameter assignment of the high-speed counter (HSC) is invalid 16#000B The address is invalid 16#0014 The selected hardware is used by another application 16#8602 Download error-free configuration to the controller; enable the axis again with instruction "MC_Power" Invalid parameter assignment of "Enable output" 16#000B 16#8603 The address is invalid Download error-free configuration to the controller; enable the axis again with instruction "MC_Power" Invalid parameter assignment of "Ready input" 16#000B 16#8604 The address is invalid Download error-free configuration to the controller; enable the axis again with instruction "MC_Power" Invalid "Pulses per motor revolution" value 16#000A 16#8605 Value is less than or equal to zero Download error-free configuration to the controller; enable the axis again with instruction "MC_Power" Invalid "Distance per revolution" value 16#0002 Number format of value is invalid 16#0005 The value is outside the number range (greater than 1e12) 16#000A Value is less than or equal to zero 16#8606 Download error-free configuration to the controller; enable the axis again with instruction "MC_Power" Invalid "Start/stop velocity" value 16#0002 Number format of value is invalid 16#0003 Value exceeds the upper hardware limit WinCC Basic V13.0 System Manual, 02/2014 Download error-free configuration to the controller; enable the axis again with instruction "MC_Power" 4441 Using technology functions 11.2 Using S7-1200 Motion Control ErrorID ErrorInfo Description 16#0004 Value is less than the lower hardware limit 16#0007 The start/stop velocity is greater than the maximum velocity 16#8607 Invalid "maximum velocity" value 16#0002 Number format of value is invalid 16#0003 Value exceeds the upper hardware limit 16#0004 Value is less than the lower hardware limit 16#8608 Download error-free configuration to the controller; enable the axis again with instruction "MC_Power" Invalid "Acceleration" value 16#0002 Number format of value is invalid 16#0003 Value exceeds the upper hardware limit 16#0004 Value is less than the lower hardware limit 16#8609 Download error-free configuration to the controller; enable the axis again with instruction "MC_Power" Correct the incorrect value online; acknowledge error with instruction "MC_Reset" and restart the command, if necessary Invalid "Deceleration" value 16#0002 Number format of value is invalid 16#0003 Value exceeds the upper hardware limit 16#0004 Value is less than the lower hardware limit 16#860A Download error-free configuration to the controller; enable the axis again with instruction "MC_Power" Correct the incorrect value online; acknowledge error with instruction "MC_Reset" and restart the command, if necessary Invalid "Emergency stop deceleration" value 16#0002 Number format of value is invalid 16#0003 Value exceeds the upper hardware limit 16#0004 Value is less than the lower hardware limit 16#860B Download error-free configuration to the controller; enable the axis again with instruction "MC_Power" Correct the incorrect value online; acknowledge error with instruction "MC_Reset" and restart the command, if necessary Value for position of the lower SW limit switch is invalid 16#0002 Number format of value is invalid 16#0005 The value is outside the number range (greater than 1e12) 16#0006 The value is outside the number range (less than -1e12) 16#0030 The position value of the lower software limit switch is greater than that of the upper software limit switch 16#860C Download error-free configuration to the controller; enable the axis again with instruction "MC_Power" Correct the incorrect value online; acknowledge error with instruction "MC_Reset" and restart the command, if necessary Value for position of the upper SW limit switch is invalid 16#0002 Number format of value is invalid 16#0005 The value is outside the number range (greater than 1e12) 16#0006 The value is outside the number range (less than -1e12) 16#860D 4442 Remedy Download error-free configuration to the controller; enable the axis again with instruction "MC_Power" Correct the incorrect value online; acknowledge error with instruction "MC_Reset" and restart the command, if necessary Invalid address of the lower HW limit switch 16#000B Invalid address 16#000C The address of the falling edge is invalid 16#000D The address of the rising edge is invalid Download error-free configuration to the controller; enable the axis again with instruction "MC_Power" WinCC Basic V13.0 System Manual, 02/2014 Using technology functions 11.2 Using S7-1200 Motion Control ErrorID ErrorInfo 16#860E Description Remedy Invalid address of the upper HW limit switch 16#000B Invalid address 16#000C The address of the falling edge is invalid 16#000D The address of the rising edge is invalid 16#860F Download error-free configuration to the controller; enable the axis again with instruction "MC_Power" Invalid "home position offset" value 16#0002 Number format of value is invalid 16#0005 The value is outside the number range (greater than 1e12) 16#0006 The value is outside the number range (less than -1e12) 16#8610 Download error-free configuration to the controller; enable the axis again with instruction "MC_Power" Correct the incorrect value online; acknowledge error with instruction "MC_Reset" and restart the command, if necessary Invalid "approach velocity" value 16#0002 Number format of value is invalid 16#0008 The velocity is greater than the maximum velocity 16#0009 The velocity is less than the start/stop velocity 16#8611 Download error-free configuration to the controller; enable the axis again with instruction "MC_Power" Correct the incorrect value online; acknowledge error with instruction "MC_Reset" and restart the command, if necessary Invalid "Homing velocity" value 16#0002 Number format of value is invalid 16#0008 The velocity is greater than the maximum velocity 16#0009 The velocity is less than the start/stop velocity 16#000B Invalid address 16#000C The address of the falling edge is invalid 16#8612 Download error-free configuration to the controller; enable the axis again with instruction "MC_Power" Correct the incorrect value online; acknowledge error with instruction "MC_Reset" and restart the command, if necessary Invalid address of the homing switch 16#000D 16#8613 Download error-free configuration to the controller; enable the axis again with instruction "MC_Power" The address of the rising edge is invalid During active homing, direction reversal at the hardware limit switch is activated although the hardware limit switches are not configured 16#0001 - Download error-free configuration to the controller; enable the axis again with instruction "MC_Power" Correct the incorrect value online; acknowledge error with instruction "MC_Reset" and restart the command, if necessary 16#8614 Invalid "Jerk" value 16#0002 Number format of value is invalid 16#001F Value is greater than the maximum jerk 16#0020 Value is less than the minimum jerk 16#8615 Download error-free configuration to the controller; enable the axis again with instruction "MC_Power" Correct the incorrect value online; acknowledge error with instruction "MC_Reset" and restart the command, if necessary Value for "Unit of measurement" is invalid 16#0011 16#8616 WinCC Basic V13.0 System Manual, 02/2014 The selection value is invalid Download error-free configuration to the controller; enable the axis again with instruction "MC_Power" Address of homing switch is invalid (passive homing as of V4) 4443 Using technology functions 11.2 Using S7-1200 Motion Control ErrorID ErrorInfo Description Remedy 16#0011 The selection value is invalid Download error-free configuration to the controller; enable the axis again with instruction "MC_Power" Correct the incorrect value online; acknowledge error with instruction "MC_Reset" and restart the command, if necessary 16#8617 Value of tag <Axis name>.Sensor.Sensor[1].ActiveHoming.Mode is invalid 16#0011 The selection value is invalid (Valid value: 2 = Homing via digital input) Download error-free configuration to the controller; enable the axis again with instruction "MC_Power" Correct the incorrect value online; acknowledge error with instruction "MC_Reset" and restart the command, if necessary 16#8618 Value of tag <Axis name>.Sensor.Sensor[1].PassiveHoming.Mode is invalid 16#0011 The selection value is invalid (Valid value: 2 = Homing via digital input) Download error-free configuration to the controller; enable the axis again with instruction "MC_Power" Correct the incorrect value online; acknowledge error with instruction "MC_Reset" and restart the command, if necessary 16#8619 Value of tag <Axis name>.Actor.Type is invalid 16#0011 The selection value is invalid Download error-free configuration to the controller; enable the axis again with instruction (Valid value: 2 = Connection via pulse interface) "MC_Power" Correct the incorrect value online; acknowledge error with instruction "MC_Reset" and restart the command, if necessary 16#861A Value for "Permitted direction of rotation" is invalid 16#0011 The selection value is invalid 16#002D "Both directions" not allowed when direction output is deactivated Download error-free configuration to the controller; enable the axis again with instruction "MC_Power" Correct the incorrect value online; acknowledge error with instruction "MC_Reset" and restart the command, if necessary Configuration error of the command table ErrorID ErrorInfo 16#8700 Description Remedy Value for "Command type" in the command table is invalid 16#0001 - Download error-free configuration to the controller; enable the axis again with instruction "MC_Power" Correct the incorrect value online and restart the command, if necessary 16#8701 4444 Value for "Position / travel path" in the command table is invalid WinCC Basic V13.0 System Manual, 02/2014 Using technology functions 11.2 Using S7-1200 Motion Control ErrorID ErrorInfo Description Remedy 16#0002 Number format of value is invalid 16#0005 The value is outside the number range (greater than 1e12) Download error-free configuration to the controller; enable the axis again with instruction "MC_Power" 16#0006 The value is outside the number range (less than -1e12) 16#8702 Correct the incorrect value online and restart the command, if necessary Value for "Velocity" in the command table is invalid 16#0002 Number format of value is invalid 16#0008 Value is greater than the configured maximum velocity 16#0009 Value is less than the configured start/stop velocity 16#8703 Download error-free configuration to the controller; enable the axis again with instruction "MC_Power" Correct the incorrect value online and restart the command, if necessary Value for "Duration" in the command table is invalid 16#0002 Number format of value is invalid 16#0021 Value is greater than 64800 s 16#0022 Value is less than 0.001 s 16#8704 Download error-free configuration to the controller; enable the axis again with instruction "MC_Power" Correct the incorrect value online and restart the command, if necessary Value for "Next step" in the command table is invalid 16#0011 The selection value is invalid 16#0023 The command transition is not permitted for this command Download error-free configuration to the controller; enable the axis again with instruction "MC_Power" Correct the incorrect value online and restart the command, if necessary Internal errors ErrorID ErrorInfo Description 16#8FFF Remedy Internal error 16#F0** - POWER OFF and POWER ON the CPU If this does not work, contact Customer Support. Have the following information ready: ErrorID ErrorInfo Diagnostic buffer entries See also Tags of the positioning axis technology object as of V4 (Page 4446) ErrorIDs and ErrorInfos (Page 4481) Error displays of the Motion Control statements (Page 4417) Using multiple axes with the same PTO (Page 4422) Using multiple drives with the same PTO (Page 4426) WinCC Basic V13.0 System Manual, 02/2014 4445 Using technology functions 11.2 Using S7-1200 Motion Control Tracking jobs from higher priority classes (execution levels) (Page 4427) Special cases for use of software limit switches (Page 4429) 11.2.12.8 Tags of the positioning axis technology object as of V4 Position tag as of V4 Legend Data type Data type of tag Start value Start value of tag Access Access to the tag in the user program: RCC The tag can be read in the user program and is updated at each cycle checkpoint. P RP The tag can be read with the Motion Control instruction "MC_ReadParam". The current value of the corresponding tag is determined at the start of the command. Effective Specifies when a change to the tag takes effect. HMI The tag can be used in an HMI system (according to the access to the tag in the user program). <Axis name>.Position Current position of the axis (indicated in the configured unit of measurement) If the axis is not homed, the tag indicates the position value relative to the enable position of the axis. Data type Start value Access Effective HMI Real 0.0 RCCP, RP - X See also Motion status (Page 4421) Tag of the axis technology object V1...3 (Page 4494) Velocity tag as of V4 Legend Data type Data type of tag Start value Start value of tag Access Access to the tag in the user program: RCC The tag can be read in the user program and is updated at each cycle checkpoint. P RP 4446 The tag can be read with the Motion Control instruction "MC_ReadParam". The current value of the corresponding tag is determined at the start of the command. WinCC Basic V13.0 System Manual, 02/2014 Using technology functions 11.2 Using S7-1200 Motion Control Effective Specifies when a change to the tag takes effect. HMI The tag can be used in an HMI system (according to the access to the tag in the user program). <Axis name>.Velocity Current velocity of the axis (indicated in the configured unit of measurement) Data type Start value Access Effective HMI Real 0.0 RCCP, RP - X See also Motion status (Page 4421) Tag of the axis technology object V1...3 (Page 4494) Actor tags as of V4 Legend Data type Data type of tag Start value Start value of tag Access Access to the tag in the user program: Effective R The tag can be read in the user program. WP If the axis is disabled (MC_Power.Status = FALSE), the tag can be written with the Motion Control instruction "MC_WriteParam". - The tag cannot be used in the user program. Specifies when a change to the tag takes effect: 2 HMI When axis is enabled The tag can be used in an HMI system (according to the access to the tag in the user program). <Axis name>.Actor.Type Drive connection The drive is connected via a pulse interface. Data type Start value Access Effective HMI DInt 2 R - X <Axis name>.Actor.InverseDirection Invert direction FALSE = The direction is not inverted. TRUE = The direction is inverted. Data type Start value Access Effective HMI Bool FALSE R - X WP 2 - WinCC Basic V13.0 System Manual, 02/2014 4447 Using technology functions 11.2 Using S7-1200 Motion Control <Axis name>.Actor.DirectionMode Permitted direction of rotation 0 = Both directions 1 = Positive direction 2 = Negative direction Data type Start value Access Effective HMI Int 0 R - X WP 2 - <Axis name>.Actor.Interface.EnableDriveOutput Enable output (internal parameter) Data type Start value Access Effective HMI VREF - - - - <Axis name>.Actor.Interface.DriveReadyInput Ready input (internal parameter) Data type Start value Access Effective HMI VREF - - - - <Axis name>.Actor.Interface.PTO Pulse output (internal parameter) Data type Start value Access Effective HMI DWord 0 - - - <Axis name>.Actor.DriveParameter.PulsesPerDriveRevolution Pulses per motor revolution Data type Start value Access Effective HMI DInt 1000 R - X WP 2 - See also Tag of the axis technology object V1...3 (Page 4494) 4448 WinCC Basic V13.0 System Manual, 02/2014 Using technology functions 11.2 Using S7-1200 Motion Control Sensor[1] tags as of V4 ActiveHoming tags as of V4 Legend Data type Data type of tag Start value Start value of tag The start value can be overwritten by the axis configuration. Access Access to the tag in the user program: RW The tag can be read and written in the user program. The tag can be written with Motion Control instruction "MC_WriteParam". Effective HMI R The tag can be read in the user program. WP If the axis is disabled (MC_Power.Status = FALSE), the tag can be written with the Motion Control instruction "MC_WriteParam". - The tag cannot be used in the user program. Specifies when a change to the tag takes effect: 1 When axis is activated (<Axis name>.StatusBits.Activated tag changes from FALSE TRUE), disabled, or enabled 2 When axis is enabled 8 When an active homing command is started The tag can be used in an HMI system (according to the access to the tag in the user program). <Axis name>.Sensor[1].ActiveHoming.Mode Active homing mode 2 = Homing via digital input Data type Start value Access Effective HMI DInt 2 R - X WP 2 - <Axis name>.Sensor[1].ActiveHoming.SideInput End of the homing switch to which the axis is homed during active homing FALSE = Lower end TRUE = Upper end Data type Start value Access Effective HMI Bool FALSE RW 1, 8 X <Axis name>.Sensor[1].ActiveHoming.DigitalInputAddress Symbolic input address of the homing switch (internal parameter) Data type Start value Access Effective HMI VREF - - - - WinCC Basic V13.0 System Manual, 02/2014 4449 Using technology functions 11.2 Using S7-1200 Motion Control <Axis name>.Sensor[1].ActiveHoming.HomePositionOffset Home position offset (active homing) (indicated in the configured unit of measurement) Data type Start value Access Effective HMI Real 0.0 RW 1, 8 X <Axis name>.Sensor[1].ActiveHoming.SwitchLevel Selection of signal level that is present at the CPU input when the homing switch is reached FALSE = Low level (Low-active) TRUE = High level (High-active) Data type Start value Access Effective HMI Bool TRUE RW 1, 8 X See also Tag of the axis technology object V1...3 (Page 4494) PassiveHoming tags as of V4 Legend Data type Data type of tag Start value Start value of tag The start value can be overwritten by the axis configuration. Access Access to the tag in the user program: RW The tag can be read and written in the user program. The tag can be written with Motion Control instruction "MC_WriteParam". Effective HMI R The tag can be read in the user program. WP If the axis is disabled (MC_Power.Status = FALSE), the tag can be written with the Motion Control instruction "MC_WriteParam". - The tag cannot be used in the user program. Specifies when a change to the tag takes effect: 1 When axis is activated (<Axis name>.StatusBits.Activated tag changes from FALSE -> TRUE), disabled, or enabled 2 When axis is enabled 7 When a passive homing command is started The tag can be used in an HMI system (according to the access to the tag in the user program). <Axis name>.Sensor[1].PassiveHoming.Mode Passive homing mode 2 = Homing via digital input Data type Start value Access Effective HMI DInt 2 R - X WP 2 - 4450 WinCC Basic V13.0 System Manual, 02/2014 Using technology functions 11.2 Using S7-1200 Motion Control <Axis name>.Sensor[1].PassiveHoming.SideInput End of the homing switch to which the axis is homed during passive homing FALSE = Lower end TRUE = Upper end Data type Start value Access Effective HMI Bool FALSE RW 1, 7 X <Axis name>.Sensor[1].PassiveHoming.DigitalInputAddress Symbolic input address of the homing switch (internal parameter) Data type Start value Access Effective HMI VREF - - - - <Axis name>.Sensor[1].PassiveHoming.SwitchLevel Selection of level that is present at the CPU input when the homing switch is reached FALSE = Low level (Low-active) TRUE = High level (High-active) Data type Start value Access Effective HMI Bool TRUE RW 1, 7 X See also Tag of the axis technology object V1...3 (Page 4494) Units tag as of V4 Legend Data type Data type of tag Start value Start value of tag The start value can be overwritten by the axis configuration. Access Effective Access to the tag in the user program: R The tag can be read in the user program. WP If the axis is disabled (MC_Power.Status = FALSE), the tag can be written with the Motion Control instruction "MC_WriteParam". Specifies when a change to the tag takes effect: 2 HMI When axis is enabled The tag can be used in an HMI system (according to the access to the tag in the user program). WinCC Basic V13.0 System Manual, 02/2014 4451 Using technology functions 11.2 Using S7-1200 Motion Control <Axis name>.Units.LengthUnit Configured unit of measurement of the parameter -1 = "Pulse" 1005 = "" (degrees) 1013 = "mm" 1010 =: "m" 1018 = "ft" 1019 = "in" Data type Start value Access Effective HMI Int 1013 R - X WP 2 - See also Tag of the axis technology object V1...3 (Page 4494) Mechanics tag as of V4 Legend Data type Data type of tag Start value Start value of tag The start value can be overwritten by the axis configuration. Access Effective Access to the tag in the user program: R The tag can be read in the user program. WP If the axis is disabled (MC_Power.Status = FALSE), the tag can be written with the Motion Control instruction "MC_WriteParam". Specifies when a change to the tag takes effect: 2 HMI When axis is enabled The tag can be used in an HMI system (according to the access to the tag in the user program). <Axis name>.Mechanics.LeadScrew Distance per revolution (indicated in the configured unit of measurement) Data type Start value Access Effective HMI Real 10.0 R - X WP 2 - See also Tag of the axis technology object V1...3 (Page 4494) 4452 WinCC Basic V13.0 System Manual, 02/2014 Using technology functions 11.2 Using S7-1200 Motion Control DynamicLimits tags as of V4 Legend Data type Data type of tag Start value Start value of tag The start value can be overwritten by the axis configuration. Access Effective Access to the tag in the user program: R The tag can be read in the user program. WP If the axis is disabled (MC_Power.Status = FALSE), the tag can be written with the Motion Control instruction "MC_WriteParam". Specifies when a change to the tag takes effect: 2 HMI When axis is enabled The tag can be used in an HMI system (according to the access to the tag in the user program). <Axis name>.DynamicLimits.MaxVelocity Maximum velocity of the axis (indicated in the configured unit of measurement) Data type Start value Access Effective HMI Real 250.0 R - X WP 2 - <Axis name>.DynamicLimits.MinVelocity Start/stop velocity of the axis (indicated in the configured unit of measurement) Data type Start value Access Effective HMI Real 10.0 R - X WP 2 - See also Tag of the axis technology object V1...3 (Page 4494) DynamicDefaults tags as of V4 Legend Data type Data type of tag Start value Start value of tag The start value can be overwritten by the axis configuration. Access Access to the tag in the user program: RW The tag can be read and written in the user program. The tag can be written with Motion Control instruction "MC_WriteParam". Effective Specifies when a change to the tag takes effect: WinCC Basic V13.0 System Manual, 02/2014 4453 Using technology functions 11.2 Using S7-1200 Motion Control HMI 1 When axis is activated (<Axis name>.StatusBits.Activated tag changes from FALSE -> TRUE), disabled, or enabled 5 The next time an MC_MoveAbsolute, MC_MoveRelative, MC_MoveVelocity, MC_MoveJog, MC_Halt, MC_CommandTable, or active MC_Home command is started (Mode = 3). 6 When a MC_MoveJog command is stopped The tag can be used in an HMI system (according to the access to the tag in the user program). <Axis name>.DynamicDefaults.Acceleration Acceleration of the axis (indicated in the configured unit of measurement) Data type Start value Access Effective HMI Real 48.0 RW 1, 5, 6 X <Axis name>.DynamicDefaults.Deceleration Deceleration of the axis (indicated in the configured unit of measurement) Data type Start value Access Effective HMI Real 48.0 RW 1, 5, 6 X <Axis name>.DynamicDefaults.EmergencyDeceleration Emergency stop deceleration of the axis (indicated in the configured unit of measurement) Data type Start value Access Effective HMI Real 120.0 RW 1, 5, 6 X <Axis name>.DynamicDefaults.Jerk Jerk during acceleration and deceleration ramp of the axis (indicated in the configured unit of measurement) The jerk is activated if the configured jerk is greater than 0.00004 mm/s. Data type Start value Access Effective HMI Real 192.0 RW 1, 5 X See also Tag of the axis technology object V1...3 (Page 4494) PositionLimitsSW tags as of V4 Legend Data type Data type of tag Start value Start value of tag The start value can be overwritten by the axis configuration. 4454 WinCC Basic V13.0 System Manual, 02/2014 Using technology functions 11.2 Using S7-1200 Motion Control Access Access to the tag in the user program: RW The tag can be read and written in the user program. The tag can be written with Motion Control instruction "MC_WriteParam". Effective HMI Specifies when a change to the tag takes effect: 1 When axis is activated (<Axis name>.StatusBits.Activated tag changes from FALSE -> TRUE), disabled, or enabled 5 The next time an MC_MoveAbsolute, MC_MoveRelative, MC_MoveVelocity, MC_MoveJog, MC_Halt, MC_CommandTable, or active MC_Home command is started (Mode = 3). 6 When a MC_MoveJog command is stopped The tag can be used in an HMI system (according to the access to the tag in the user program). <Axis name>.PositionLimitsSW.Active Activation of the software limit switches FALSE = The software limit switches are deactivated. TRUE = The software limit switches are activated. Data type Start value Access Effective HMI Bool FALSE RW 1, 5, 6 X <Axis name>.PositionLimitsSW.MinPosition Position of the lower software limit switch (indicated in the configured unit of measurement) Data type Start value Access Effective HMI Real -10000.0 RW 1, 5, 6 X <Axis name>.PositionLimitsSW.MaxPosition Position of the upper software limit switch (indicated in the configured unit of measurement) Data type Start value Access Effective HMI Real 10000.0 RW 1, 5, 6 X See also Tag of the axis technology object V1...3 (Page 4494) PositionLimitsHW tags as of V4 Legend Data type Data type of tag Start value Start value of tag The start value can be overwritten by the axis configuration. Access Access to tag in the user program: RW The tag can be read and written in the user program. The tag can be written with Motion Control instruction "MC_WriteParam". WinCC Basic V13.0 System Manual, 02/2014 4455 Using technology functions 11.2 Using S7-1200 Motion Control Effective HMI R The tag can be read in the user program. WP If the axis is disabled (MC_Power.Status = FALSE), the tag can be written with Motion Control instruction "MC_WriteParam". - The tag cannot be used in the user program. Specifies when a change to the tag takes effect: 1 When axis is activated (<Axis name>.StatusBits.Activated tag changes from FALSE -> TRUE), disabled, or enabled 2 When axis is enabled 5 The next time an MC_MoveAbsolute, MC_MoveRelative, MC_MoveVelocity, MC_MoveJog, MC_Halt, MC_CommandTable, or active MC_Home command is started (Mode = 3). 6 When a MC_MoveJog command is stopped The tag can be used in an HMI system (according to the access to the tag in the user program). <Axis name>.PositionLimitsHW.Active Activation of the hardware limit switches FALSE = The hardware limit switches are deactivated. TRUE = The hardware limit switches are activated. Data type Start value Access Effective HMI Bool FALSE RW 1, 5, 6 X <Axis name>.PositionLimitsHW.MinSwitchLevel Selection of signal level that is present at the CPU input when the lower hardware limit switch is reached FALSE = Low level (Low-active) TRUE = High level (High-active) Data type Start value Access Effective HMI Bool FALSE R - X WP 2 - <Axis name>.PositionLimitsHW.MinSwitchAddress Symbolic input address of the lower hardware limit switch (internal parameter) Data type Start value Access Effective HMI VREF - - - - <Axis name>.PositionLimitsHW.MaxSwitchLevel Selection of signal level that is present at the CPU input when the upper hardware limit switch is reached FALSE = Low level (Low-active) TRUE = High level (High-active) Data type Start value Access Effective HMI Bool FALSE R - X WP 2 - 4456 WinCC Basic V13.0 System Manual, 02/2014 Using technology functions 11.2 Using S7-1200 Motion Control <Axis name>.PositionLimitsHW.MaxSwitchAddress Input address of the upper hardware limit switch (internal parameter) Data type Start value Access Effective HMI VREF - - - - See also Tag of the axis technology object V1...3 (Page 4494) Homing tags as of V4 Legend Data type Data type of tag Start value Start value of tag The start value can be overwritten by the axis configuration. Access Access to the tag in the user program: RW The tag can be read and written in the user program. The tag can be written with Motion Control instruction "MC_WriteParam". Effective HMI Specifies when a change to the tag takes effect: 1 When axis is activated (<Axis name>.StatusBits.Activated tag changes from FALSE TRUE), disabled, or enabled 8 When an active homing command is started The tag can be used in an HMI system (according to the access to the tag in the user program). <Axis name>.Homing.AutoReversal Activation of auto reverse at the hardware limit switch during active homing FALSE = Auto reversal at the hardware limit switch is deactivated. TRUE = Auto reversal at the hardware limit switch is activated. Data type Start value Access Effective HMI Bool FALSE RW 1, 8 X <Axis name>.Homing.ApproachDirection Approach and homing direction of axis during active homing FALSE = Negative approach direction for finding the homing switch and negative homing direction TRUE = Positive approach direction for finding the homing switch and positive homing direction Data type Start value Access Effective HMI Bool TRUE RW 1, 8 X WinCC Basic V13.0 System Manual, 02/2014 4457 Using technology functions 11.2 Using S7-1200 Motion Control <Axis name>.Homing.ApproachVelocity Approach velocity of the axis during active homing (indicated in the configured unit of measurement) Data type Start value Access Effective HMI Real 200.0 RW 1, 8 X <Axis name>.Homing.ReferencingVelocity Homing velocity of the axis during active homing (indicated in the configured unit of measurement) Data type Start value Access Effective HMI Real 40.0 RW 1, 8 X See also Tag of the axis technology object V1...3 (Page 4494) StatusPositioning tags as of V4 Legend Data type Data type of tag Start value Start value of tag Access Access to the tag in the user program: RCC The tag can be read in the user program and is updated at each cycle checkpoint. P RP The tag can be read with the Motion Control instruction "MC_ReadParam". The current value of the corresponding tag is determined at the start of the command. Effective Specifies when a change to the tag takes effect. HMI The tag can be used in an HMI system. <Axis name>.StatusPositioning.Distance Current distance of axis from target position (indicated in the configured unit of measurement) The value of the tag is only valid during execution of a positioning command with "MC_MoveAbsolute", "MC_MoveRelative", or the axis control panel. Data type Start value Access Effective HMI Real 0.0 RCCP, RP - X 4458 WinCC Basic V13.0 System Manual, 02/2014 Using technology functions 11.2 Using S7-1200 Motion Control <Axis name>.StatusPositioning.TargetPosition Target position of the axis (indicated in the configured unit of measurement) The value of the tag is only valid during execution of a positioning command with "MC_MoveAbsolute", "MC_MoveRelative", or the axis control panel. Data type Start value Access Effective HMI Real 0.0 RCCP, RP - X See also Motion status (Page 4421) Tag of the axis technology object V1...3 (Page 4494) StatusBits tags as of V4 Legend Data type Data type of tag Start value Start value of tag Access Access to the tag in the user program: RCC The tag can be read in the user program and is updated at each cycle checkpoint. P Effective Specifies when a change to the tag takes effect. HMI The tag can be used in an HMI system. <Axis name>.StatusBits.Activated Activation of the axis FALSE = The axis is not activated. TRUE = The axis is activated. It is connected to the assigned PTO (Pulse Train Output). The data of the technology data block will be updated cyclically. Data type Start value Access Effective HMI Bool FALSE RCCP - X <Axis name>.StatusBits.Enable Enable status of the axis FALSE = The axis is not enabled. TRUE = The axis is enabled and ready to accept Motion Control commands. Data type Start value Access Effective HMI Bool FALSE RCCP - X WinCC Basic V13.0 System Manual, 02/2014 4459 Using technology functions 11.2 Using S7-1200 Motion Control <Axis name>.StatusBits.HomingDone Homing status of the axis FALSE = The axis is not homed. TRUE = The axis is homed and is capable of executing absolute positioning commands. The axis does not have to be homed for relative positioning. The status is FALSE during active homing. The status remains TRUE during passive homing if the axis was already homed beforehand. Data type Start value Access Effective HMI Bool FALSE RCCP - X <Axis name>.StatusBits.Done Command execution on the axis FALSE = A Motion Control command is active on the axis. TRUE = A Motion Control command is not active on the axis. Data type Start value Access Effective HMI Bool FALSE RCCP - X <Axis name>.StatusBits.Error Error status on the axis FALSE = No error is active on the axis. TRUE = An error occurred on the axis. Additional information about the error is available in automatic control at the "ErrorID" and "ErrorInfo" parameters of the Motion Control instructions. In manual mode, the "Error message" box of the axis control panel displays detailed information about the cause of error. Data type Start value Access Effective HMI Bool FALSE RCCP - X <Axis name>.StatusBits.StandStill Standstill of the axis FALSE = The axis is in motion. TRUE = The axis is at a standstill. Data type Start value Access Effective HMI Bool FALSE RCCP - X <Axis name>.StatusBits.PositioningCommand Execution of a positioning command FALSE = A positioning command is not active on the axis. TRUE = The axis is executing a positioning command of the "MC_MoveRelative" or MC_MoveAbsolute Motion Control instruction. Data type Start value Access Effective HMI Bool FALSE RCCP - X 4460 WinCC Basic V13.0 System Manual, 02/2014 Using technology functions 11.2 Using S7-1200 Motion Control <Axis name>.StatusBits.VelocityCommand Execution of a command with velocity specification FALSE = A command with velocity specification is not active on the axis. TRUE = The axis is executing a motion command with velocity specification of the "MC_MoveVelocity" or MC_MoveJog Motion Control instruction. Data type Start value Access Effective HMI Bool FALSE RCCP - X <Axis name>.StatusBits.HomingCommand Execution of a homing command FALSE = A homing command is not active on the axis. TRUE = The axis is executing a homing command of the "MC_Home" Motion Control instruction. Data type Start value Access Effective HMI Bool FALSE RCCP - X <Axis name>.StatusBits.CommandTableActive Execution of a command table FALSE = A command table is not active on the axis. TRUE = The axis is controlled by "MC_CommandTable" Motion Control instruction. Data type Start value Access Effective HMI Bool FALSE RCCP - X <Axis name>.StatusBits.ConstantVelocity Constant velocity FALSE = The axis is accelerating, decelerating, or at a standstill. TRUE = The setpoint velocity has been reached. The axis is moving at constant velocity. Data type Start value Access Effective HMI Bool FALSE RCCP - X <Axis name>.StatusBits.Accelerating Acceleration process FALSE = The axis is decelerating, moving at constant velocity, or at a standstill. TRUE = The axis is accelerating. Data type Start value Access Effective HMI Bool FALSE RCCP - X <Axis name>.StatusBits.Decelerating Deceleration process FALSE = The axis is accelerating, moving at constant velocity, or at a standstill. TRUE = The axis is decelerating. Data type Start value Access Effective HMI Bool FALSE RCCP - X WinCC Basic V13.0 System Manual, 02/2014 4461 Using technology functions 11.2 Using S7-1200 Motion Control <Axis name>.StatusBits.ControlPanelActive Activation status of the axis control panel FALSE = "Automatic mode" is activated. The user program has control priority over the axis. TRUE = The "Manual control" mode was enabled in the axis control panel. The axis control panel has control priority over the axis. The axis cannot be controlled from the user program. Data type Start value Access Effective HMI Bool FALSE RCCP - X <Axis name>.StatusBits.DriveReady Operational status of the drive FALSE = The drive is not ready. Setpoints will not be executed. TRUE = The drive is ready. Setpoints can be executed. Data type Start value Access Effective HMI Bool FALSE RCCP - X <Axis name>.StatusBits.RestartRequired Restart of axis required FALSE = A restart of the axis is not required. TRUE = Values were modified in the load memory. To download the values to the work memory while the CPU is in RUN mode, the axis must be restarted. Use the MC_Reset Motion Control instruction to do this. Data type Start value Access Effective HMI Bool FALSE RCCP - X <Axis name>.StatusBits.SWLimitMinActive Status of the lower software limit switch FALSE = The axis is kept within its configured working range. TRUE = The lower software limit switch was reached or exceeded. Data type Start value Access Effective HMI Bool FALSE RCCP - X <Axis name>.StatusBits.SWLimitMaxActive Status of the upper software limit switch FALSE = The axis is kept within its configured working range. TRUE = The upper software limit switch was reached or exceeded. Data type Start value Access Effective HMI Bool FALSE RCCP - X <Axis name>.StatusBits.HWLimitMinActive Status of the lower hardware limit switch FALSE = The axis is kept within its configured permitted traversing range. TRUE = The lower hardware limit switch was reached or exceeded. Data type Start value Access Effective HMI Bool FALSE RCCP - X 4462 WinCC Basic V13.0 System Manual, 02/2014 Using technology functions 11.2 Using S7-1200 Motion Control <Axis name>.StatusBits.HWLimitMaxActive Status of the upper hardware limit switch FALSE = The axis is kept within its configured permitted traversing range. TRUE = The upper hardware limit switch was reached or exceeded. Data type Start value Access Effective HMI Bool FALSE RCCP - X See also Status and error bits (technology objects as of V4) (Page 4418) Tag of the axis technology object V1...3 (Page 4494) ErrorBits tags as of V4 Legend Data type Data type of tag Start value Start value of tag Access Access to the tag in the user program: RCC The tag can be read in the user program and is updated at each cycle checkpoint. P Effective Specifies when a change to the tag takes effect. HMI The tag can be used in an HMI system. <Axis name>.ErrorBits.SystemFault Internal system error Data type Start value Access Effective HMI Bool FALSE RCCP - X <Axis name>.ErrorBits.ConfigFault Incorrect configuration of the axis Data type Start value Access Effective HMI Bool FALSE RCCP - X <Axis name>.ErrorBits.DriveFault Error in the drive. Loss of the "Drive ready" signal. Data type Start value Access Effective HMI Bool FALSE RCCP - X <Axis name>.ErrorBits.SWLimit Software limit switch reached or exceeded Data type Start value Access Effective HMI Bool FALSE RCCP - X WinCC Basic V13.0 System Manual, 02/2014 4463 Using technology functions 11.2 Using S7-1200 Motion Control <Axis name>.ErrorBits.HWLimit Hardware limit switch reached or exceeded Data type Start value Access Effective HMI Bool FALSE RCCP - X <Axis name>.ErrorBits.DirectionFault Impermissible motion direction Data type Start value Access Effective HMI Bool FALSE RCCP - X <Axis name>.ErrorBits.HWUsed Another axis is using the same PTO (Pulse Train Output) and is enabled with "MC_Power". Data type Start value Access Effective HMI Bool FALSE RCCP - X See also Status and error bits (technology objects as of V4) (Page 4418) Tag of the axis technology object V1...3 (Page 4494) ControlPanel tags as of V4 The "ControlPanel" tags do not contain any user-relevant data. These tags cannot be accessed in the user program. See also Tag of the axis technology object V1...3 (Page 4494) Internal tags as of V4 The "Internal" tags do not contain any user-relevant data. These tags cannot be accessed in the user program. See also Tag of the axis technology object V1...3 (Page 4494) Update of the technology object tags The status and error information of the axis indicated in the technology object tags is updated at each cycle control point. Changes to the values of configuration tags do not take effect immediately. For information on the conditions under which a change takes effect, refer to the detailed description of the relevant tag. 4464 WinCC Basic V13.0 System Manual, 02/2014 Using technology functions 11.2 Using S7-1200 Motion Control 11.2.12.9 Tags of the command table technology object as of V4 Command[1...32] tags as of V4 Legend Data type Data type of tag Start value Start value of tag The start value can be overwritten by the configuration of the command table. Access Access to the tag in the user program: RW The tag can be read and written in the user program. R The tag can be read in the user program. - The tag cannot be used in the user program. Effective Specifies when a change to the tag takes effect. HMI The tag can be used in an HMI system. <Command table>.Command[n].Type Command type 0 = "Empty" command 2 = "Hold" command 5 = "Relative positioning" command 6 = "Absolute positioning" command 7 = "Velocity setpoint" command 151 = "Wait" command Data type Start value Access Effective HMI Int 0 RW - X <Command table>.Command[n].Position Target position/traversing distance of the command Data type Start value Access Effective HMI Real 0.0 RW - X <Axis name>.Command[n].Velocity Command velocity Data type Start value Access Effective HMI Real 0.0 RW - X <Command table>.Command[n].Duration Command duration Data type Start value Access Effective HMI Real 0.0 RW - X WinCC Basic V13.0 System Manual, 02/2014 4465 Using technology functions 11.2 Using S7-1200 Motion Control <Command table>.Command[n].NextStep Mode for the transition to the next command 0 = "Complete command" 1 = "Blend movement" Data type Start value Access Effective HMI Int 0 RW - X <Command table>.Command[n].StepCode Command step code Data type Start value Access Effective HMI Word 0 RW - X See also Tags of the command table technology object V1...3 (Page 4509) 11.2.12.1 Versions V1...3 0 CPU outputs relevant for motion control (technology version V1...3) The number of usable drives depends on the CPU, the number of PTOs (pulse train outputs) and the number of available pulse generator outputs. The following tables provide information about the relevant dependencies: Maximum number of PTOs The maximum number of controllable PTOs (drives) depends on the order number of CPU: Order number CPU Number of PTOs xxxxxxx-1xx30-xxxx 2 xxxxxxx-1xx31-xxxx 4 The maximum number of controllable PTOs (drives) applies regardless of the use of a signal board. Usable pulse generator outputs The CPU provides one pulse output and one direction output for controlling a stepper motor drive or a servo motor drive with pulse interface. The pulse output provides the drive with the pulses required for motor motion. The direction output controls the travel direction of the drive. Pulse and direction outputs are permanently assigned to one another and form a pulse generator output. On-board CPU outputs or outputs of a signal board can be used as pulse generator outputs. You select between on-board CPU outputs and outputs of the signal board during device configuration under Pulse generators (PTO/PWM) on the "Properties" tab. 4466 WinCC Basic V13.0 System Manual, 02/2014 Using technology functions 11.2 Using S7-1200 Motion Control The following table shows the number of usable drives per CPU or signal board: CPU Onboard Signal board DI2/DO2 x DC24V 20kHz DI2/DO2 x DC24V 200kHz DO4 x DC24V 200kHz DI2/DO2 x DC5V 200kHz DO4 x DC5V 200kHz CPU 1211C, CPU 1212C, CPU 1214C DC/DC/ DC 2 2 2 2 2 2 (MLFB - order number AC/DC/ RLY - 1 1 2 1 2 DC/DC/ RLY - 1 1 2 1 2 DC/DC/ DC 2 3 3 4 3 4 AC/DC/ RLY - 1 1 2 1 2 DC/DC/ RLY - 1 1 2 1 2 DC/DC/ DC 3 4 4 4 4 4 AC/DC/ RLY - 1 1 2 1 2 DC/DC/ RLY - 1 1 2 1 2 DC/DC/ DC 4 4 4 4 4 4 AC/DC/ RLY - 1 1 2 1 2 DC/DC/ RLY - 1 1 2 1 2 DC/DC/ DC 4 4 4 4 4 4 AC/DC/ RLY - 1 1 2 1 2 DC/DC/ RLY - 1 1 2 1 2 xxxxxxx-1xx30-xxxx) CPU 1211C (MLFB - order number xxxxxxx-1xx31-xxxx) CPU 1212C (MLFB - order number xxxxxxx-1xx31-xxxx) CPU 1214C (MLFB - order number xxxxxxx-1xx31-xxxx) CPU 1215C The following table shows the address assignment of the pulse and direction outputs: CPU S7-1200: Outputs PTO1 *) Pls. Dir. Pls. Dir. Pls. Dir. Pls. Dir. CPU 1211C, CPU CPU 1212C, Signal CPU 1214C, board CPU1215C (DC/DC/DC) Ax.0 Ax.1 Ax.2 Ax.3 Ax.4 Ax.5 Ax.6 Ax.7 Ay.0 Ay.1 Ay.2 Ay.3 Ay.0 Ay.1 Ay.2 Ay.3 - - - - - - - - CPU 1211C, CPU CPU 1212C, CPU 1214C, WinCC Basic V13.0 System Manual, 02/2014 Outputs PTO2 **) Outputs PTO3 *) Outputs PTO4 **) 4467 Using technology functions 11.2 Using S7-1200 Motion Control CPU S7-1200: CPU 1215C (AC/DC/ RLY) Outputs PTO1 *) Signal board CPU 1211C, CPU CPU 1212C, Signal CPU 1214C, board CPU 1215C (DC/DC/ RLY) Outputs PTO2 **) Outputs PTO3 *) Outputs PTO4 **) Pls. Dir. Pls. Dir. Pls. Dir. Pls. Dir. Ay.0 Ay.1 Ay.2 Ay.3 Ay.0 Ay.1 Ay.2 Ay.3 - - - - - - - - Ay.0 Ay.1 Ay.2 Ay.3 Ay.0 Ay.1 Ay.2 Ay.3 x = Initial byte address of on-board CPU outputs (default value = 0) y = Initial byte address of signal board outputs (default value = 4) * If a DC/DC/DC CPU variant is used together with a DI2/DO2 signal board, the signals of the PTO1/3 can be generated via the on-board CPU outputs or via the signal board. ** If a DC/DC/DC CPU variant is used together with a DO4 signal board, the signals for PTO1/3 or PTO2/4 can be generated via the on-board CPU outputs or via the signal board. PTO3 and PTO4 are only available for CPUs with the order numbers xxxxxxx-1xx31-xxxx. Note Access to pulse generator outputs via the process image The firmware takes control via the corresponding pulse generator outputs if the PTO (Pulse Train Output) is selected and assigned to an axis. With this takeover of the control function, the connection between the process image and I/ O output is also disconnected. Although the user has the option of writing the process image of pulse generator outputs via the user program or watch table, this is not transferred to the I/O output. Accordingly, it is also not possible to monitor the I/O output via the user program or watch table. The information read reflects the value of the process image and does not match the real status of the I/O output. For all other CPU outputs that are not used permanently by the CPU firmware, the status of the I/O output can be controlled or monitored via the process image, as usual. 4468 WinCC Basic V13.0 System Manual, 02/2014 Using technology functions 11.2 Using S7-1200 Motion Control Limit frequencies of pulse outputs The following limit frequencies apply to the pulse outputs: Pulse output Limit frequencies for technology object positioning axis V1 Limiting frequencies of the technology object positioning axis V2/V3 with CPU < V3.0 Limiting frequencies of the technology object positioning axis V2/V3 with CPU V3.0 On-board (MLFB - order number xxxxxxx-1xx30-xxxx) 2 Hz f 100 kHz 2 Hz f 100 kHz 1 Hz f 100 kHz On-board (MLFB - order number xxxxxxx-1xx31xxxx) 2 Hz f 100 kHz (PTO 1+2) 2 Hz f 100 kHz 2 Hz f 20 kHz (PTO 3+4) (PTO 1+2) 1 Hz f 100 kHz (PTO 1+2) Signal board DI2/DO2 x DC24V 20kHz 2 Hz f 20 kHz 2 Hz f 20 kHz 1 Hz f 20 kHz Signal board DI2/DO2 x DC24V 200kHz 2 Hz f 100 kHz 2 Hz f 200 kHz 1 Hz f 200 kHz Signal board DO4 x DC24V 200kHz 2 Hz f 100 kHz 2 Hz f 200 kHz 1 Hz f 200 kHz Signal board DI2/DO2 x DC5V 200kHz 2 Hz f 100 kHz 2 Hz f 200 kHz 1 Hz f 200 kHz Signal board DO4 x DC5V 200kHz 2 Hz f 100 kHz 2 Hz f 200 kHz 1 Hz f 200 kHz 2 Hz f 20 kHz (PTO 3+4) 1 Hz f 20 kHz (PTO 3+4) Drive signals For motion control, you can optionally parameterize a drive interface for "Drive enabled" and "Drive ready". When using the drive interface the digital output for the drive enable and the digital input for "drive ready" can be freely selected. Acceleration/deceleration limits The following limits apply to acceleration and deceleration: Acceleration/deceleration Value (CPU < V3.0) Value (CPU V3.0) Minimum acceleration/deceleration 2.8E-1 pulses/s 5.0E-3 pulses/s2 Maximum acceleration/deceleration 9.5E+9 pulses/s 9.5E+9 pulses/s2 Value (CPU < V3.0) Value (CPU V3.0) Minimum jerk 4.0E-2 pulses/s 4.0E-3 pulses/s3 Maximum jerk 1.5E+8 pulses/s 2 2 Jerk limits The following limits apply to the jerk: Jerk WinCC Basic V13.0 System Manual, 02/2014 3 3 1.0E+10 pulses/s3 4469 Using technology functions 11.2 Using S7-1200 Motion Control See also CPU outputs relevant for motion control (technology version V4) (Page 4312) Configuration dialogs Configuration - General ("Axis" technology object V1...3) Configure the basic properties of the "Axis" technology object in the "General" configuration window. Axis name: Define the name of the axis or the name of the "Axis" technology object in this box. The technology object is listed under this name in the project navigation. Hardware interface The pulses are output to the power unit of the drive by fixed assigned digital outputs. In CPUs with relay outputs, the pulse signal cannot be output on these outputs because the relays do not support the necessary switching frequencies. A signal board with digital outputs must be used to enable you to work with the PTO (Pulse Train Output) on these CPUs. Note The PTO requires the functionality of a fast counter (HSC). An HSC is used for this purpose with CPU version <V3.0. The HSC is then no longer available to the user. An internal HSC is used for this with CPU version V3.0. The count can not be evaluated from its input address. The assignment between PTO and HSC is fixed. When the user activates PTO1, it is connected to the HSC1. If the PTO2 is activated, this is connected with the HSC2. In the "Pulse generator selection" drop-down list, select the PTO (Pulse Train Output) which is to provide the pulses for controlling the stepper motors or servo motors with pulse interface. If the pulse generators and high-speed counters are not used elsewhere in the device configuration, the hardware interface can be configured automatically. In this case, the PTO selected in the drop-down list is displayed with a white background. The interfaces used are listed in the output boxes "Output source", "Pulse output", "Direction output" and "Assigned fast counter". Proceed as follows if you wish to change the interfaces or if the PTO could not be automatically configured (entry in the "Pulse generator selection" drop-down list is highlighted in red): 4470 WinCC Basic V13.0 System Manual, 02/2014 Using technology functions 11.2 Using S7-1200 Motion Control 1. Click on the "Device configuration" button. The pulse generator device configuration opens. Enlarge the property window of the device configuration if the configuration of the pulse generator is not visible. 2. Select the "Enable this pulse generator" check box. 3. Select the "Parameter assignment" entry in the area navigation. The "Parameter assignment" opens. 4. In the "Pulse generator as:" dropdown list select the "PTO" entry. 5. In the "Output source:" dropdown list select the "Integrated CPU output" or "Signal board output" entry. The "Signal board output" entry can only be selected for PTO1 or for PTO1 and PTO2 depending on the installed signal board. For more detailed information, see section: CPU outputs relevant for motion control (technology version V4) (Page 4312) 6. Go back to the axis configuration. Unless the corresponding fast counter has already been used elsewhere, the PTO boxes of the "General" axis configuration are not shaded red. If this is not the case, correct the configuration based on the error messages. User unit Select the desired unit for the dimension system of the axis in the dropdown list. The selected unit is used for additional configuration of the "Axis" technology object and for displaying the current axis data. WinCC Basic V13.0 System Manual, 02/2014 4471 Using technology functions 11.2 Using S7-1200 Motion Control The values at the input parameters (Position, Distance, Velocity, ...) of the Motion Control instructions also refer to this unit. Note Later changing of the dimension system may not be converted correctly in all the configuration windows of the technology object. In this case check the configuration of all axis parameters. The values of the input parameters of the Motion Control instructions may have to be adapted to the new unit of measurement in the user program. See also Configuration - General (positioning axis technology object as of V4) (Page 4337) Changing configuration of dynamic values in user program ("Axis" technology object V1...3) You can change the following configuration parameters during runtime of the user program in the CPU: Acceleration and deceleration You can also change the values for acceleration and deceleration during runtime of the user program. Use the following technology object tags for this purpose: <Axis name>.Config.DynamicDefaults.Acceleration for changing acceleration <Axis name>.Config.DynamicDefaults.Deceleration for changing deceleration Refer to the description of the technology object tags (Page 4494) in the appendix for information on when changes to the configuration parameters take effect. Emergency stop deceleration You can also change the value for the emergency stop deceleration during runtime of the user program. Use the following technology object tag for this purpose: <Axis name>.Config.DynamicDefaults.EmergencyDeceleration Refer to the description of the technology object tags in the appendix for information on when changes to the configuration parameter take effect. NOTICE After changes to this parameter, it may be necessary to adapt the positions of the hardware limit switches and other safety-relevant settings. 4472 WinCC Basic V13.0 System Manual, 02/2014 Using technology functions 11.2 Using S7-1200 Motion Control Jerk limit (as of technology object "Axis" V2.0) You can also activate and deactivate the jerk limit at runtime of the user program and change the value for the jerk. Use the following technology object tags for this purpose: <Axis name>.Config.DynamicDefaults.JerkActive for activating and deactivating the jerk limit <Axis name>.Config.DynamicDefaults.Jerk for changing the jerk Refer to the description of the technology object tags in the appendix for information on when changes to the configuration parameter take effect. See also Changing the configuration of dynamics in the user program (Page 4351) Configuration - Homing ("Axis" technology object V1) Configure the parameters for active and passive homing in the "Homing" configuration window. The homing method is set using the "Mode" input parameter of the Motion Control instruction. Here, Mode = 2 means passive homing and Mode = 3 means active homing. Reference point switch input Select the digital input for the reference point switch from the drop-down list. The input must be interrupt-capable. The onboard CPU inputs and the inputs of an inserted signal board can be selected as inputs for the reference point switch. Note The digital inputs are set to a filter time of 6.4 ms by default. When the digital inputs are used as a reference point switch, this can result in undesired decelerations and thus inaccuracies. Depending on the homing velocity and extent of the reference point switch, the reference point may not be detected. The filter time can be set under "Input filter" in the device configuration of the digital inputs. The specified filter time must be less than the duration of the input signal at the reference point switch. Permitting direction reversal after reaching the HW limit switch (active homing only) Activate the check box to use the hardware limit switch as a reversing cam for the homing procedure. The hardware limit switches must be activated for direction reversal. If the CPU firmware V1.0 is used, both hardware limit switches must be configured. If CPU firmware as of V2.0 is used, only the hardware limit switch in the approach direction must be configured. If the hardware limit switch is reached during active homing, the axis brakes at the configured deceleration (not with the emergency stop deceleration) and reverses direction. The reference point switch is then sensed in reverse direction. WinCC Basic V13.0 System Manual, 02/2014 4473 Using technology functions 11.2 Using S7-1200 Motion Control If the direction reversal is not active and the axis reaches the hardware limit switch during active homing, the homing procedure is aborted with an error and the axis is braked at the emergency stop deceleration. Note Use one of the following measures to ensure that the machine does not travel to a mechanical endstop in the event of a direction reversal: Keep the approach velocity low Increase the configured acceleration/deceleration Increase the distance between hardware limit switch and mechanical stop Approach / homing direction (active and passive homing) With the direction selection, you determine the "approach direction" used during active homing to search for the reference point switch, as well as the homing direction. The homing direction specifies the travel direction the axis uses to approach the configured end of the reference point switch to carry out the homing operation. Refer to the table under "Reference point switches" for the effect of the approach direction setting on passive homing. Side of the reference point switch (active and passive homing) Active homing This is where you select whether the axis is homed on the low or high end of the reference point switch. Note Depending on the start position of the axis and the configuration of the homing parameters, the homing procedure sequence can differ from the diagram in the configuration window. Passive homing With passive homing, the traversing motions for purposes of homing must be implemented by the user via motion commands. The end of the reference point switch on which homing occurs depends on the following factors: - "Approach direction" configuration - "Reference point switch" configuration - Current travel direction during passive homing The table below presents details on the effect of factors: Influencing factors: 4474 Configuration Configuration Approach direction Reference point switch Positive "Bottom side" Result: Current travel direction Homing on Reference point switch Positive direction Top side Negative direction Bottom side WinCC Basic V13.0 System Manual, 02/2014 Using technology functions 11.2 Using S7-1200 Motion Control Influencing factors: Configuration Configuration Approach direction Reference point switch Positive "Top side" Negative Negative "Bottom side" "Top side" Result: Current travel direction Homing on Reference point switch Positive direction Bottom side Negative direction Top side Positive direction Bottom side Negative direction Top side Positive direction Top side Negative direction Bottom side Velocity (active homing only) In this box, specify the velocity at which the reference point switch is to be searched for during the homing procedure. Limits (independent of the selected unit of measurement): Start/stop velocity approach velocity maximum velocity Homing velocity (active homing only) In this box, specify the velocity at which the axis approaches the reference point switch for homing. Limits (independent of the selected unit of measurement): Start/stop velocity Homing velocity Maximum velocity Home position offset (active homing only) If the desired home position deviates from the position of the reference point switch, the home position offset can be specified in this box. If the value does not equal 0, the axis executes the following actions following homing at the reference point switch: 1. Move the axis at the homing velocity by the value of the home position offset 2. Upon reaching the "home position offset", the axis is at the home position that was specified in input parameter "Position" of the "MC_Home" Motion Control instruction. Limits (independent of the selected unit of measurement): -1.0e12 home position offset 1.0e12 Home position The position configured in the Motion Control instruction "MC_Home" is used as the home position. WinCC Basic V13.0 System Manual, 02/2014 4475 Using technology functions 11.2 Using S7-1200 Motion Control Configuration - Homing ("Axis" technology object V2...3) Configuration - Homing - General (Axis technology object V2...3) Configure the reference point switch input for active and passive homing in the "Homing General" configuration window. Reference point switch input Select the digital input for the homing switch from the drop-down list. The input must be interrupt-capable. The on-board CPU inputs and the inputs of an inserted signal board can be selected as inputs for the homing switch. Note The digital inputs are set to a filter time of 6.4 ms by default. When the digital inputs are used as a homing switch, this can result in undesired decelerations and thus inaccuracies. Depending on the homing velocity and extent of the homing switch, the home position may not be detected. The filter time can be set under "Input filter" in the device configuration of the digital inputs. The specified filter time must be less than the duration of the input signal at the homing switch. Active level In the drop-list, select the level of the homing switch that is to be used for homing. See also Sequence - Active homing (Page 4357) Configuration - Homing - Passive (Axis technology object V2...3) Configure the necessary parameters for passive homing in the "Homing - Passive" configuration window. The movement for passive homing must be triggered by the user (e.g. using an axis motion command). Passive homing is started using Motion Control instruction "MC_Home" with input parameter "Mode" = 2. Side of the homing switch This is where you select whether the axis is to be homed on the low or high end of the homing switch. 4476 WinCC Basic V13.0 System Manual, 02/2014 Using technology functions 11.2 Using S7-1200 Motion Control Home position The position configured in the Motion Control instruction "MC_Home" is used as the home position. Note If passive homing is carried out without an axis motion command (axis at a standstill), homing will be executed upon the next rising or falling edge at the homing switch. Configuration - Homing - Active (Axis technology object V2...3) Configure the necessary parameters for active homing in the "Active homing" configuration window. Active homing is started using Motion Control instruction "MC_Home" with input parameter "Mode" = 3. Permit auto reverse at the hardware limit switch Activate the check box to use the hardware limit switch as a reversing cam for the homing procedure. The hardware limit switches must be enabled for the reversal of direction (at least the hardware limit switch in the direction of approach must be configured). If the hardware limit switch is reached during active homing, the axis brakes at the configured deceleration (not with the emergency stop deceleration) and reverses direction. The homing switch is then sensed in reverse direction. If the direction reversal is not active and the axis reaches the hardware limit switch during active homing, the homing procedure is aborted with an error and the axis is braked at the emergency stop deceleration. Note If possible, use one of the following measures to ensure that the machine does not travel to a mechanical endstop in the event of a direction reversal: Keep the approach velocity low. Increase the configured acceleration/deceleration. Increase the distance between the hardware limit switch and the mechanical endstop. Approach/homing direction With the direction selection, you determine the approach direction used during active homing to search for the homing switch, as well as the homing direction. The homing direction specifies the travel direction the axis uses to approach the configured end of the homing switch to carry out the homing operation. Side of the homing switch This is where you select whether the axis is to be homed on the low or high end of the homing switch. WinCC Basic V13.0 System Manual, 02/2014 4477 Using technology functions 11.2 Using S7-1200 Motion Control Velocity In this box, specify the velocity at which the homing switch is to be searched for during the homing procedure. Limits (independent of the selected unit of measurement): Start/stop velocity approach velocity maximum velocity Homing velocity In this box, specify the velocity at which the reference point switch is to be approached for homing. Limits (independent of the selected unit of measurement): Start/stop velocity Homing velocity Maximum velocity Home position offset If the desired home position deviates from the position of the homing switch, the home position offset can be specified in this box. If the value does not equal 0, the axis executes the following actions following homing at the homing switch: 1. Move the axis at the homing velocity by the value of the home position offset 2. Upon reaching the "home position offset", the axis is at the home position that was specified in input parameter "Position" of the "MC_Home" Motion Control instruction. Limits (independent of the selected unit of measurement): -1.0e12 home position offset 1.0e12 Home position The position configured in the Motion Control instruction "MC_Home" is used as the home position. Diagnostics - Status and error bits ("Axis" technology object V1...3) You use the "Status and error bits" diagnostic function to monitor the most important status and error messages for the axis in the TIA Portal. The diagnostic function display is available in online mode in "Manual control" mode and in "Automatic control" when the axis is active. The status error messages have the following meaning: 4478 WinCC Basic V13.0 System Manual, 02/2014 Using technology functions 11.2 Using S7-1200 Motion Control Status of the axis Status Description Enabled The axis is enabled and ready to be controlled via Motion Control commands. (Tag of technology object: <Axis name>.StatusBits.Enable) Homed The axis is homed and is capable of executing absolute positioning commands of Motion Control instruction "MC_MoveAbsolute". The axis does not have to be homed for relative positioning. Special situations: During active homing, the status is FALSE. If a homed axis undergoes passive homing, the status is set to TRUE during passive homing. (Tag of technology object: <Axis name>.StatusBits.HomingDone) Axis error An error has occurred in the "Axis" technology object. Additional information about the error is available in automatic control at the ErrorID and ErrorInfo parameters of the Motion Control instructions. In manual mode, the "Error message" box of the axis control panel displays detailed information about the cause of error. (Tag of technology object: <Axis name>.StatusBits.Error) Axis control panel enabled The "Manual control" mode was enabled in the axis control panel. The axis control panel has control priority over the "Axis" technology object. The axis cannot be controlled from the user program. (Tag of technology object: <Axis name>.StatusBits.ControlPanelActive) Restart necessary A modified configuration of the axis was downloaded to the load memory in CPU RUN operating mode. To download the modified configuration to the work memory, you need to restart the axis. Use the Motion Control instruction MC_Reset to do this. Drive status Status Description Drive ready The drive is ready for operation. (Tag of technology object: <Axis name>.StatusBits.DriveReady) Drive error The drive has reported an error due to loss of its "Drive ready" signal. (Tag of technology object: <Axis name>.ErrorBits.DriveFault) Status of the axis motion Status Description Standstill The axis is at a standstill. (Tag of technology object: <Axis name>.StatusBits.StandStill) Acceleration The axis accelerates. (Tag of technology object: <Axis name>.StatusBits.Acceleration) Constant velocity The axis travels at constant velocity. (Tag of technology object: <Axis name>.StatusBits.ConstantVelocity) Deceleration The axis decelerates (slows down). (Tag of technology object: <Axis name>.StatusBits.Deceleration) WinCC Basic V13.0 System Manual, 02/2014 4479 Using technology functions 11.2 Using S7-1200 Motion Control Status of the motion mode Status Description Positioning The axis executes a positioning command of the Motion Control instruction "MC_MoveAbsolute", "MC_MoveRelative" or the axis control panel. (Tag of technology object: <Axis name>.StatusBits.PositioningCommand) Travel with velocity specification The axis executes a command with velocity specification of the Motion Control instruction "MC_MoveVelocity", "MC_MoveJog" or the axis control panel. (Tag of technology object: <Axis name>.StatusBits.SpeedCommand) Homing The axis executes a homing command of the Motion Control instruction "MC_Home" or the axis control panel. (Tag of technology object: <Axis name>.StatusBits.Homing) Command table active The axis is controlled by Motion Control instruction "MC_CommandTable". (as of technology object Axis V2.0) (Tag of technology object: <Axis name>.StatusBits.CommandTableActive) Error messages Error Description Lower SW limit switch was reached The lower software limit switch has been reached. Lower SW limit switch was exceeded The lower software limit switch has been exceeded. Upper SW limit switch was reached The upper software limit switch has been reached. Upper SW limit switch was exceeded The upper software limit switch has been exceeded. Lower HW limit switch was reached The lower hardware limit switch has been reached. Upper HW limit switch was reached The upper hardware limit switch has been reached. PTO and HSC already in use A second axis is using the same PTO (Pulse Train Output) and HSC (High Speed Counter) and is enabled with "MC_Power". (Tag of technology object: <Axis name>.ErrorBits.SwLimitMinReached) (Tag of technology object: <Axis name>.ErrorBits.SwLimitMinExceeded) (Tag of technology object: <Axis name>.ErrorBits.SwLimitMaxReached) (Tag of technology object: <Axis name>.ErrorBits.SwLimitMaxExceeded) (Tag of technology object: <Axis name>.ErrorBits.HwLimitMin) (Tag of technology object: <Axis name>.ErrorBits.HwLimitMax) (Tag of technology object: <Axis name>.ErrorBits.HwUsed) Configuration error The "Axis" technology object was incorrectly configured or editable configuration data were modified incorrectly during runtime of the user program. (Tag of technology object: <Axis name>.ErrorBits.ConfigFault) Internal error An internal error has occurred. (Tag of technology object: <Axis name>.ErrorBits.SystemFault) See also Status and error bits (technology objects as of V4) (Page 4418) 4480 WinCC Basic V13.0 System Manual, 02/2014 Using technology functions 11.2 Using S7-1200 Motion Control ErrorIDs and ErrorInfos List of ErrorIDs and ErrorInfos (technology objects V2...3) The following table lists all ErrorIDs and ErrorInfos that can be indicated in Motion Control instructions. In addition to the cause of the error, remedies for eliminating the error are also listed: Operating error with axis stop ErrorID ErrorInfo 16#8000 Description Remedy Drive error, loss of "Drive ready" 16#0001 16#8001 - Acknowledge error with instruction "MC_Reset"; provide drive signal; restart command, if necessary Lower SW limit switch has been tripped 16#000E The position of the lower SW limit switch was reached with the currently configured deceleration 16#000F The position of the lower SW limit switch was reached with the emergency stop deceleration 16#0010 The position of the lower SW limit switch was exceeded with the emergency stop deceleration 16#8002 Acknowledge the error with instruction "MC_Reset"; use a motion command to move the axis in the positive direction out of the range of the SW limit switch Upper SW limit switch has been tripped 16#000E The position of the upper SW limit switch was reached with the currently configured deceleration 16#000F The position of the upper SW limit switch was reached with the emergency stop deceleration 16#0010 The position of the upper SW limit switch was exceeded with the emergency stop deceleration 16#8003 Acknowledge the error with instruction "MC_Reset"; use a motion command to move the axis in the negative direction out of the range of the SW limit switch Lower HW limit switch was reached 16#000E The lower HW limit switch was reached. The axis was stopped with the emergency stop deceleration. (During an active homing procedure, the reference point switch was not found) 16#8004 Acknowledge the error for an enabled axis with instruction "MC_Reset"; use a motion command to move the axis in the positive direction out of the range of the HW limit switch. Upper HW limit switch was reached 16#000E The upper HW limit switch has been reached. The axis was stopped with the emergency stop deceleration. (During an active homing procedure, the reference point switch was not found) 16#8005 Acknowledge the error for an enabled axis with instruction "MC_Reset"; use a motion command to move the axis in the negative direction out of the range of the HW limit switch. PTO/HSC are already being used by another axis 16#0001 - The axis was configured incorrectly: Correct the configuration of the PTO (Pulse Train Output) / HSC (High Speed Counter) and download it to the controller WinCC Basic V13.0 System Manual, 02/2014 4481 Using technology functions 11.2 Using S7-1200 Motion Control ErrorID ErrorInfo Description Remedy More than one axis is to run with one PTO: Another axis is using the PTO / HSC. If the current axis is to assume the control, the other axis must be disabled with "MC_Power" Enable = FALSE. (see also Using multiple axes with the same PTO (Page 4422)) 16#8006 A communication error in the control panel has occurred 16#0012 16#8007 A timeout has occurred Check the cable connection and press the "Manual control" button again. The axis cannot be enabled. 16#0025 Restarting Wait until the axis restart is complete. 16#0026 Executing loading process in RUN mode Wait until the loading process is complete. Operating error without axis stop ErrorID ErrorInfo 16#8200 Description Remedy Axis is not enabled 16#0001 16#8201 - Enable the axis; restart the command Axis has already been enabled by another "MC_Power" instance 16#0001 16#8202 - Enable the axis with only one "MC_Power" instance The maximum number of simultaneously active Motion Control commands has been exceeded (maximum of 200 commands for all motion control technology objects) 16#0001 - Reduce the number of simultaneously active commands; restart the command A command is active if parameter "Busy" = TRUE in the Motion Control instruction. 16#8203 Axis is currently operated in "Manual control" (axis control panel) 16#0001 16#8204 Exit "Manual control"; restart the command Axis is not homed 16#0001 16#8205 - Home the axis with instruction "MC_Home"; restart the command The axis is currently controlled by the user program (the error is only displayed in the axis control panel) 16#0013 16#8206 The axis is enabled in the user program. Disable axis with instruction "MC_Power" and select "Manual control" again in the axis control panel Technology object not activated yet 16#0001 16#8207 - Enable the axis with instruction "MC_Power" Enable = TRUE or enable the axis in the axis control panel. Command rejected 16#0016 4482 - Active homing is running; another homing method cannot be started. Wait for active homing to finish or abort the active homing with a motion command, for example, "MC_Halt". WinCC Basic V13.0 System Manual, 02/2014 Using technology functions 11.2 Using S7-1200 Motion Control ErrorID ErrorInfo Description Remedy 16#0018 The axis cannot be moved with a command table while it is being actively or passively homed. Wait until direct or passive homing is complete. 16#0019 The axis cannot be actively or passively homed while a command table is being processed. Wait for command table to finish or abort the command table with a motion command, for example, "MC_Halt". 16#8208 Difference between maximum and start/stop velocity is invalid 16#0002 Number format of value is invalid 16#000A Value is less than or equal to 0 16#8209 Correct the value; restart the command Invalid acceleration for technology object "Axis" 16#0002 Number format of value is invalid 16#000A Value is less than or equal to 0 16#820A Correct the value; restart the command It is not possible to restart the axis 16#0013 The axis is enabled in the user program. Disable the axis with the "MC_Power" instruction; restart again 16#0027 The axis is currently being operated in "Manual control" (axis control panel) Exit "Manual control"; restart again 16#820B It is not possible to execute the command table 16#0026 Executing loading process in RUN mode Wait until the loading process is complete. Block parameter error ErrorID ErrorInfo 16#8400 Description Remedy Invalid value at parameter "Position" of the Motion Control instruction 16#0002 Number format of value is invalid 16#0005 The value is outside the number range (greater than 1e12) 16#0006 The value is outside the number range (less than -1e12) 16#8401 Correct the value; restart the command Invalid value at parameter "Distance" of the Motion Control instruction 16#0002 Number format of value is invalid 16#0005 The value is outside the number range (greater than 1e12) 16#0006 The value is outside the number range (less than -1e12) 16#8402 Correct the value; restart the command Invalid value at parameter "Velocity" of the Motion Control instruction 16#0002 Number format of value is invalid 16#0008 Value is greater than the configured maximum velocity 16#0009 Value is less than the configured start/stop velocity 16#0024 Value is less than 0 16#8403 Correct the value; restart the command Invalid value at parameter "Direction" of the Motion Control instruction 16#0011 16#8404 WinCC Basic V13.0 System Manual, 02/2014 The selection value is invalid Correct the selection value; restart the command Invalid value at parameter "Mode" of the Motion Control instruction 4483 Using technology functions 11.2 Using S7-1200 Motion Control ErrorID ErrorInfo Description Remedy 16#0011 The selection value is invalid Correct the selection value; restart the command 16#0015 Active/passive homing is not configured Correct the configuration and download it to the controller; enable the axis and restart the command 16#0017 The direction reversal is activated at the hardware limit switch, despite the fact that the hardware limit switches are disabled Activate the hardware limit switch using the tag <axis>.Config.PositionLimits_HW.Active = TRUE, restart the command Correct the configuration and download it to the controller; enable the axis and restart the command 16#8405 Invalid value at parameter "StopMode" of the Motion Control instruction 16#0011 The selection value is invalid 16#0001 - 16#8406 Simultaneous forward and backward jogging is not allowed 16#8407 Take steps to ensure that parameters "JogForward" and "JogBackward" do not have signal status TRUE simultaneously; restart the command. Switching to another axis with instruction "MC_Power" is only permitted after disabling the active axis. 16#0001 16#8408 - Disable the active axis; it is then possible to switch to the other axis and enable it. Invalid value at parameter "Axis" of the Motion Control instruction 16#001A The specified value does not match the required technology object version 16#001B The specified value does not match the required technology object type 16#001C The specified value is not a Motion Control technology data block 16#001A The specified value does not match the required technology object version 16#001B The specified value does not match the required technology object type 16#001C The specified value is not a Motion Control technology data block 16#8409 Correct the value; restart the command Invalid value at parameter "CommandTable" of the Motion Control instruction 16#840A Correct the value; restart the command Invalid value at parameter "StartStep" of the Motion Control instruction 16#000A Value is less than or equal to 0 16#001D The start step is greater than the end step 16#001E Value is greater than 32 16#840B Correct the value; restart the command Invalid value at parameter "EndStep" of the Motion Control instruction 16#000A Value is less than or equal to 0 16#001E Value is greater than 32 16#840C Correct the value; restart the command Invalid value at parameter "RampUpTime" of the Motion Control instruction 16#0002 Number format of value is invalid 16#000A Value is less than or equal to 0 16#840D 4484 Correct the selection value; enable the axis again Correct the value; restart the command Invalid value at parameter "RampDownTime" of the Motion Control instruction 16#0002 Number format of value is invalid 16#000A Value is less than or equal to 0 Correct the value; restart the command WinCC Basic V13.0 System Manual, 02/2014 Using technology functions 11.2 Using S7-1200 Motion Control ErrorID ErrorInfo 16#840E Description Remedy Invalid value at parameter "EmergencyRampTime" of the Motion Control instruction 16#0002 Number format of value is invalid 16#000A Value is less than or equal to 0 16#840F Correct the value; restart the command Invalid value at parameter "JerkTime" of the Motion Control instruction 16#0002 Number format of value is invalid 16#000A Value is less than or equal to 0 Correct the value; restart the command Configuration error of the axis ErrorID ErrorInfo 16#8600 Description Remedy Parameter assignment of pulse generator (PTO is invalid 16#000B The address is invalid 16#0014 The selected hardware is used by another application 16#8601 Download error-free configuration to the controller; enable the axis again with instruction "MC_Power" Parameter assignment of the high-speed counter (HSC) is invalid 16#000B The address is invalid 16#0014 The selected hardware is used by another application 16#8602 Download error-free configuration to the controller; enable the axis again with instruction "MC_Power" Invalid parameter assignment of "Enable output" 16#000B 16#8603 The address is invalid Download error-free configuration to the controller; enable the axis again with instruction "MC_Power" Invalid parameter assignment of "Ready input" 16#000B 16#8604 The address is invalid Download error-free configuration to the controller; enable the axis again with instruction "MC_Power" Invalid "Pulses per motor revolution" value 16#000A 16#8605 Value is less than or equal to zero Download error-free configuration to the controller; enable the axis again with instruction "MC_Power" Invalid "Distance per revolution" value 16#0002 Number format of value is invalid 16#0005 The value is outside the number range (greater than 1e12) 16#000A Value is less than or equal to zero 16#8606 Download error-free configuration to the controller; enable the axis again with instruction "MC_Power" Invalid "Start/stop velocity" value 16#0002 Number format of value is invalid 16#0003 Value exceeds the upper hardware limit 16#0004 Value is less than the lower hardware limit 16#0007 The start/stop velocity is greater than the maximum velocity 16#8607 Download error-free configuration to the controller; enable the axis again with instruction "MC_Power" Invalid "maximum velocity" value 16#0002 Number format of value is invalid 16#0003 Value exceeds the upper hardware limit WinCC Basic V13.0 System Manual, 02/2014 Download error-free configuration to the controller; enable the axis again with instruction "MC_Power" 4485 Using technology functions 11.2 Using S7-1200 Motion Control ErrorID ErrorInfo Description 16#0004 Value is less than the lower hardware limit 16#8608 Invalid "Acceleration" value 16#0002 Number format of value is invalid 16#0003 Value exceeds the upper hardware limit 16#0004 Value is less than the lower hardware limit 16#8609 Number format of value is invalid 16#0003 Value exceeds the upper hardware limit 16#0004 Value is less than the lower hardware limit Correct the incorrect value online; acknowledge error with instruction "MC_Reset" and restart the command, if necessary Download error-free configuration to the controller; enable the axis again with instruction "MC_Power" Correct the incorrect value online; acknowledge error with instruction "MC_Reset" and restart the command, if necessary Invalid "Emergency stop deceleration" value 16#0002 Number format of value is invalid 16#0003 Value exceeds the upper hardware limit 16#0004 Value is less than the lower hardware limit 16#860B Download error-free configuration to the controller; enable the axis again with instruction "MC_Power" Correct the incorrect value online; acknowledge error with instruction "MC_Reset" and restart the command, if necessary Value for position of the lower SW limit switch is invalid 16#0002 Number format of value is invalid 16#0005 The value is outside the number range (greater than 1e12) 16#0006 The value is outside the number range (less than -1e12) 16#0007 The position value of the lower software limit switch is greater than that of the upper software limit switch 16#860C Download error-free configuration to the controller; enable the axis again with instruction "MC_Power" Correct the incorrect value online; acknowledge error with instruction "MC_Reset" and restart the command, if necessary Value for position of the upper SW limit switch is invalid 16#0002 Number format of value is invalid 16#0005 The value is outside the number range (greater than 1e12) 16#0006 The value is outside the number range (less than -1e12) 16#860D Download error-free configuration to the controller; enable the axis again with instruction "MC_Power" Correct the incorrect value online; acknowledge error with instruction "MC_Reset" and restart the command, if necessary Invalid address of the lower HW limit switch 16#000C The address of the falling edge is invalid 16#000D The address of the rising edge is invalid 16#860E 4486 Download error-free configuration to the controller; enable the axis again with instruction "MC_Power" Invalid "Deceleration" value 16#0002 16#860A 16#860F Remedy Download error-free configuration to the controller; enable the axis again with instruction "MC_Power" Invalid address of the upper HW limit switch 16#000C The address of the falling edge is invalid 16#000D The address of the rising edge is invalid Download error-free configuration to the controller; enable the axis again with instruction "MC_Power" Invalid "home position offset" value WinCC Basic V13.0 System Manual, 02/2014 Using technology functions 11.2 Using S7-1200 Motion Control ErrorID ErrorInfo Description Remedy 16#0002 Number format of value is invalid 16#0005 The value is outside the number range (greater than 1e12) Download error-free configuration to the controller; enable the axis again with instruction "MC_Power" 16#0006 The value is outside the number range (less than -1e12) 16#8610 Correct the incorrect value online; acknowledge error with instruction "MC_Reset" and restart the command, if necessary Invalid "approach velocity" value 16#0002 Number format of value is invalid 16#0008 The velocity is greater than the maximum velocity 16#0009 The velocity is less than the start/stop velocity 16#8611 Download error-free configuration to the controller; enable the axis again with instruction "MC_Power" Correct the incorrect value online; acknowledge error with instruction "MC_Reset" and restart the command, if necessary Invalid "Homing velocity" value 16#0002 Number format of value is invalid 16#0008 The velocity is greater than the maximum velocity 16#0009 The velocity is less than the start/stop velocity 16#8612 Download error-free configuration to the controller; enable the axis again with instruction "MC_Power" Correct the incorrect value online; acknowledge error with instruction "MC_Reset" and restart the command, if necessary Invalid address of the reference point switch 16#000C The address of the falling edge is invalid 16#000D The address of the rising edge is invalid 16#8613 Download error-free configuration to the controller; enable the axis again with instruction "MC_Power" During active homing, direction reversal at the hardware limit switch is activated although the hardware limit switches are not configured 16#0001 - Download error-free configuration to the controller; enable the axis again with instruction "MC_Power" Correct the incorrect value online; acknowledge error with instruction "MC_Reset" and restart the command, if necessary 16#8614 Invalid "Jerk" value 16#0002 Number format of value is invalid 16#001F Value is greater than the maximum jerk 16#0020 Value is less than the minimum jerk 16#8615 Download error-free configuration to the controller; enable the axis again with instruction "MC_Power" Correct the incorrect value online; acknowledge error with instruction "MC_Reset" and restart the command, if necessary Value for "Unit of measurement" is invalid 16#0011 WinCC Basic V13.0 System Manual, 02/2014 The selection value is invalid Download error-free configuration to the controller; enable the axis again with instruction "MC_Power" 4487 Using technology functions 11.2 Using S7-1200 Motion Control Configuration error of the command table ErrorID ErrorInfo 16#8700 Description Remedy Value for "Command type" in the command table is invalid 16#0001 - Download error-free configuration to the controller; enable the axis again with instruction "MC_Power" Correct the incorrect value online and restart the command, if necessary 16#8701 Value for "Position / travel path" in the command table is invalid 16#0002 Number format of value is invalid 16#0005 The value is outside the number range (greater than 1e12) 16#0006 The value is outside the number range (less than -1e12 16#8702 Download error-free configuration to the controller; enable the axis again with instruction "MC_Power" Correct the incorrect value online and restart the command, if necessary Value for "Velocity" in the command table is invalid 16#0002 Number format of value is invalid 16#0008 Value is greater than the configured maximum velocity 16#0009 Value is less than the configured start/stop velocity 16#8703 Download error-free configuration to the controller; enable the axis again with instruction "MC_Power" Correct the incorrect value online and restart the command, if necessary Value for "Duration" in the command table is invalid 16#0002 Number format of value is invalid 16#0021 Value is greater than 64800 s 16#0022 Value is less than 0.001 s 16#8704 Download error-free configuration to the controller; enable the axis again with instruction "MC_Power" Correct the incorrect value online and restart the command, if necessary Value for "Next step" in the command table is invalid 16#0011 The selection value is invalid 16#0023 The command transition is not permitted for this command Download error-free configuration to the controller; enable the axis again with instruction "MC_Power" Correct the incorrect value online and restart the command, if necessary Internal errors ErrorID ErrorInfo 16#8FFF Description Remedy Internal error 16#F0** - POWER OFF and POWER ON the CPU If this does not work, contact Customer Support. Have the following information ready: ErrorID ErrorInfo Diagnostic buffer entries 4488 WinCC Basic V13.0 System Manual, 02/2014 Using technology functions 11.2 Using S7-1200 Motion Control See also List of ErrorIDs and ErrorInfos (technology objects as of V4) (Page 4436) Using multiple axes with the same PTO (Page 4422) List of ErrorIDs and ErrorInfos (technology objects V1) The following table lists all ErrorIDs and ErrorInfos that can be indicated in Motion Control instructions. In addition to the cause of the error, remedies for eliminating the error are also listed: Operating error with axis stop ErrorID ErrorInfo 16#8000 Description Remedy Drive error, loss of "Drive ready" 16#0001 16#8001 - Acknowledge error with instruction "MC_Reset"; provide drive signal; restart command, if necessary Lower SW limit switch has been tripped 16#000E The position of the lower SW limit switch was reached with the currently configured deceleration 16#000F The position of the lower SW limit switch was reached with the emergency stop deceleration 16#0010 The position of the lower SW limit switch was exceeded with the emergency stop deceleration 16#000E The position of the upper SW limit switch was reached with the currently configured deceleration 16#000F The position of the upper SW limit switch was reached with the emergency stop deceleration 16#0010 The position of the upper SW limit switch was exceeded with the emergency stop deceleration 16#8002 Acknowledge the error with instruction "MC_Reset"; use a motion command to move the axis in the positive direction out of the range of the SW limit switch Upper SW limit switch has been tripped 16#8003 Acknowledge the error with instruction "MC_Reset"; use a motion command to move the axis in the negative direction out of the range of the SW limit switch Lower HW limit switch was reached 16#000E The lower HW limit switch was reached. The axis was stopped with the emergency stop deceleration. (During an active homing procedure, the reference point switch was not found) 16#8004 Acknowledge the error for an enabled axis with instruction "MC_Reset"; use a motion command to move the axis in the positive direction out of the range of the HW limit switch. Upper HW limit switch was reached 16#000E The upper HW limit switch has been reached. The axis was stopped with the emergency stop deceleration. (During an active homing procedure, the reference point switch was not found) 16#8005 WinCC Basic V13.0 System Manual, 02/2014 Acknowledge the error for an enabled axis with instruction "MC_Reset"; use a motion command to move the axis in the negative direction out of the range of the HW limit switch. PTO/HSC are already being used by another axis 4489 Using technology functions 11.2 Using S7-1200 Motion Control ErrorID ErrorInfo Description Remedy 16#0001 - The axis was configured incorrectly: Correct the configuration of the PTO (Pulse Train Output) / HSC (High Speed Counter) and download it to the controller More than one axis is to run with one PTO: Another axis is using the PTO / HSC. If the current axis is to assume the control, the other axis must be disabled with "MC_Power" Enable = FALSE. (see also Using multiple axes with the same PTO (Page 4422)) Operating error without axis stop ErrorID ErrorInfo 16#8200 Description Remedy Axis is not enabled 16#0001 16#8201 - Enable the axis; restart the command Axis has already been enabled by another "MC_Power" instance 16#0001 16#8202 - Enable the axis with only one "MC_Power" instruction The maximum number of simultaneously active Motion Control commands was exceeded (maximum of 200 commands for all motion control technology objects) 16#0001 - Reduce the number of simultaneously active commands; restart the command A command is active if parameter "Busy" = TRUE in the Motion Control instruction. 16#8203 Axis is currently operated in "Manual control" (axis control panel) 16#0001 16#8204 Exit "Manual control"; restart the command Axis is not homed 16#0001 16#8205 - Home the axis with instruction "MC_Home"; restart the command The axis is currently controlled by the user program (the error is only displayed in the axis control panel) 16#0001 16#8206 - Disable axis with instruction "MC_Power" and select "Manual control" again in the axis control panel Technology object Axis not yet enabled 16#0001 16#8207 - Enable the axis with instruction "MC_Power" Enable = TRUE or enable the axis in the axis control panel. Command rejected 16#0016 4490 - Active homing is running; another homing method cannot be started. Wait for active homing to finish or abort the active homing with a motion command, for example, "MC_Halt". The other homing type can then be started. WinCC Basic V13.0 System Manual, 02/2014 Using technology functions 11.2 Using S7-1200 Motion Control Block parameter error ErrorID ErrorInfo 16#8400 Description Remedy Invalid value at parameter "Position" of the Motion Control instruction 16#0002 Number format of value is invalid 16#0005 The value is outside the number range (greater than 1e12) 16#0006 The value is outside the number range (less than -1e12) 16#8401 Correct the "position" value; restart the command Invalid value at parameter "Distance" of the Motion Control instruction 16#0002 Number format of value is invalid 16#0005 The value is outside the number range (greater than 1e12) 16#0006 The value is outside the number range (less than -1e12) 16#8402 Correct the "Distance" value; restart the command Invalid value at parameter "Velocity" of the Motion Control instruction 16#0002 Number format of value is invalid 16#0008 Velocity is greater than the maximum velocity 16#0009 Velocity is less than the start/stop velocity 16#8403 Correct the "Velocity" value; restart the command Invalid value at parameter "Direction" of the Motion Control instruction 16#0011 16#8404 Invalid selection value Correct the selection value; restart the command Invalid value at parameter "Mode" of the Motion Control instruction 16#0011 Invalid selection value Correct the selection value; restart the command 16#0015 Active/passive homing is not configured Correct the configuration and download it to the controller; enable the axis and restart the command 16#0017 Axis reversal is activated at the HW limit switch, despite the fact that the hardware limit switches are disabled Activate the hardware limit switch using the tag <axis>.Config.PositionLimits_HW.Active = TRUE, restart the command Correct the configuration and download it to the controller; enable the axis and restart the command 16#8405 Invalid value at parameter "StopMode" of the Motion Control instruction 16#0011 Invalid selection value 16#0001 - 16#8406 Correct the selection value; enable the axis again Simultaneous forward and backward jogging is not allowed 16#8407 Take steps to ensure that parameters "JogForward" and "JogBackward" do not have signal status TRUE simultaneously; restart the command. Switching the axis with Motion Control instruction "MC_Power" is only permitted after disabling the axis. 16#0001 WinCC Basic V13.0 System Manual, 02/2014 - Disable the active axis; it is then possible to switch to the other axis and enable it. 4491 Using technology functions 11.2 Using S7-1200 Motion Control Configuration error ErrorID ErrorInfo 16#8600 16#000B Address is invalid 16#000B Address is invalid 16#000D Address is invalid Correct the configuration of the PTO (Pulse Train Output) and download it to the controller Parameter assignment of the high-speed counter (HSC) is invalid 16#8602 Correct the configuration of the HSC (High Speed Counter) and download it to the controller Invalid parameter assignment of "Enable output" 16#8603 Correct the configuration and download it to the controller Invalid parameter assignment of "Ready input" 16#000D 16#8604 Address is invalid Correct the configuration and download it to the controller Invalid "Pulses per motor revolution" value 16#000A 16#8605 Value is less than or equal to zero Correct the configuration and download it to the controller Invalid "Distance per revolution" value 16#0002 Number format of value is invalid 16#000A Value is less than or equal to zero 16#8606 Correct the configuration and download it to the controller Invalid "Start/stop velocity" value 16#0002 Number format of value is invalid 16#0003 Value exceeds the hardware limit 16#0004 Value is less than the hardware limit 16#0007 The start/stop velocity is greater than the maximum velocity 16#8607 Correct the configuration and download it to the controller Invalid "Maximum velocity" value 16#0002 Number format of value is invalid 16#0003 Value exceeds the hardware limit 16#0004 Value is less than the hardware limit 16#8608 Correct the configuration and download it to the controller Invalid "Acceleration" value 16#0002 Number format of value is invalid 16#0003 Value exceeds the hardware limit 16#0004 Value is less than the hardware limit 16#8609 4492 Remedy Parameter assignment of pulse generator (PTO is invalid 16#8601 16#860A Description Download error-free configuration to the controller; enable the axis again with instruction "MC_Power" Correct the incorrect value online; acknowledge error with instruction "MC_Reset" and restart the command, if necessary Invalid "Deceleration" value 16#0002 Number format of value is invalid 16#0003 Value exceeds the hardware limit 16#0004 Value is less than the hardware limit Download error-free configuration to the controller; enable the axis again with instruction "MC_Power" Correct the incorrect value online; acknowledge error with instruction "MC_Reset" and restart the command, if necessary Invalid "Emergency stop deceleration" value WinCC Basic V13.0 System Manual, 02/2014 Using technology functions 11.2 Using S7-1200 Motion Control ErrorID ErrorInfo Description Remedy 16#0002 Number format of value is invalid 16#0003 Value exceeds the hardware limit 16#0004 Value is less than the hardware limit Download error-free configuration to the controller; enable the axis again with instruction "MC_Power" 16#860B Correct the incorrect value online; acknowledge error with instruction "MC_Reset" and restart the command, if necessary Value for position of the lower SW limit switch is invalid 16#0002 Number format of value is invalid 16#0005 The value is outside the number range (greater than 1e12) 16#0006 The value is outside the number range (less than -1e12) 16#0007 The position value of the lower SW limit switch is greater than that of the upper SW limit switch 16#860C Download error-free configuration to the controller; enable the axis again with instruction "MC_Power" Correct the incorrect value online; acknowledge error with instruction "MC_Reset" and restart the command, if necessary Value for position of the upper SW limit switch is invalid 16#0002 Number format of value is invalid 16#0005 The value is outside the number range (greater than 1e12) 16#0006 The value is outside the number range (less than -1e12) 16#860D Download error-free configuration to the controller; enable the axis again with instruction "MC_Power" Correct the incorrect value online; acknowledge error with instruction "MC_Reset" and restart the command, if necessary Invalid address of the lower HW limit switch 16#000C Address of falling edge is invalid 16#000D Address of rising edge is invalid 16#860E Correct the configuration and download it to the controller Invalid address of the upper HW limit switch 16#000C Address of falling edge is invalid 16#000D Address of rising edge is invalid 16#860F Correct the configuration and download it to the controller Invalid "home position offset" value 16#0002 Number format of value is invalid 16#0005 The value is outside the number range (greater than 1e12) 16#0006 The value is outside the number range (less than -1e12) 16#8610 Correct the configuration and download it to the controller Invalid "approach velocity" value 16#0002 Number format of value is invalid 16#0008 Velocity is greater than the maximum velocity 16#0009 Velocity is less than the start/stop velocity 16#8611 Correct the configuration and download it to the controller Invalid "Homing velocity" value 16#0002 Number format of value is invalid 16#0008 Velocity is greater than the maximum velocity 16#0009 Velocity is less than the start/stop velocity 16#8612 Correct the configuration and download it to the controller Invalid address of the reference point switch 16#000C Address of falling edge is invalid 16#000D Address of rising edge is invalid WinCC Basic V13.0 System Manual, 02/2014 Correct the configuration and download it to the controller 4493 Using technology functions 11.2 Using S7-1200 Motion Control ErrorID ErrorInfo Description 16#8613 Remedy During active homing, direction reversal at the hardware limit switch is activated although the hardware limit switches are not configured 16#0001 - Correct the configuration and download it to the controller Description Remedy Internal errors ErrorID ErrorInfo 16#8FFF Internal error 16#F0** - POWER OFF and POWER ON the CPU If this does not work, contact Customer Support. Have the following information ready: ErrorID ErrorInfo Diagnostic buffer entries See also List of ErrorIDs and ErrorInfos (technology objects as of V4) (Page 4436) Using multiple axes with the same PTO (Page 4422) Tag of the axis technology object V1...3 Config tags V1...3 Config.General tags V1...3 Legend Data type Data type of tag Start value Start value of tag The start value can be overwritten by the axis configuration. Access Access to tag in the user program: RW The tag can be read and written in the user program. R The tag can be read in the user program. - The tag cannot be used in the user program. Effective Specifies when a change to the tag takes effect. HMI The tag can be used in an HMI system. 4494 WinCC Basic V13.0 System Manual, 02/2014 Using technology functions 11.2 Using S7-1200 Motion Control <Axis name>.Config.General.PTO Tag cannot be evaluated in the user program. Data type Start value Access Effective HMI DWORD DW#16#00000000 - - - <Axis name>.Config.General.HSC Tag cannot be evaluated in the user program. Data type Start value Access Effective HMI DWORD DW#16#00000000 - - - <Axis name>.Config.General.LengthUnit ("Axis" technology object as of V2.0) The unit of measurement for the parameter selected in the configuration: 1013 = "mm" 1010 =: "m" 1019 = "in" 1018 = "ft" 1005 = "" (degrees) -1 = "Pulse" Data type Start value Access Effective HMI Int 1013 R - X See also Tags of the positioning axis technology object as of V4 (Page 4446) Config.DriveInterface tags V1...3 Legend Data type Data type of tag Start value Start value of tag The start value can be overwritten by the axis configuration. Access Access to tag in the user program: RW The tag can be read and written in the user program. R The tag can be read in the user program. - The tag cannot be used in the user program. Effective Specifies when a change to the tag takes effect. HMI The tag can be used in an HMI system. <Axis name>.Config.DriveInterface.EnableOutput Tags cannot be evaluated in the user program. Data type Start value Access Effective HMI - - - - - WinCC Basic V13.0 System Manual, 02/2014 4495 Using technology functions 11.2 Using S7-1200 Motion Control <Axis name>.Config.DriveInterface.ReadyInput Tags cannot be evaluated in the user program. Data type Start value Access Effective HMI - - - - - See also Tags of the positioning axis technology object as of V4 (Page 4446) Config.Mechanics tags V1...3 Legend Data type Data type of tag Start value Start value of tag The start value can be overwritten by the axis configuration. Access Access to tag in the user program: RW The tag can be read and written in the user program. R The tag can be read in the user program. - The tag cannot be used in the user program. Effective Specifies when a change to the tag takes effect. HMI The tag can be used in an HMI system. <Axis name>.Config.Mechanics.PulsesPerDriveRevolution Increments per motor revolution Data type Start value Access Effective HMI DInt L#1000 R - X <Axis name>.Config.Mechanics.LeadScrew Distance per revolution (specified in the configured unit of measurement) Data type Start value Access Effective HMI Real 1.0E+001 R - X <Axis name>.Config.Mechanics.InverseDirection Invert direction Data type Start value Access Effective HMI Bool FALSE R - X See also Tags of the positioning axis technology object as of V4 (Page 4446) 4496 WinCC Basic V13.0 System Manual, 02/2014 Using technology functions 11.2 Using S7-1200 Motion Control Config.DynamicLimits tags V1...3 Legend Data type Data type of tag Start value Start value of tag The start value can be overwritten by the axis configuration. Access Access to tag in the user program: RW The tag can be read and written in the user program. R The tag can be read in the user program. - The tag cannot be used in the user program. Effective Specifies when a change to the tag takes effect. HMI The tag can be used in an HMI system. <Axis name>.Config.DynamicLimits.MinVelocity Start/stop velocity of axis (specified in the configured unit of measurement) Data type Start value Access Effective HMI Real 1.0E+001 R - X <Axis name>.Config.DynamicLimits.MaxVelocity Maximum velocity of axis (specified in the configured unit of measurement) Data type Start value Access Effective HMI Real 2.5E+002 R - X See also Tags of the positioning axis technology object as of V4 (Page 4446) Config.DynamicDefaults tags V1...3 Legend Data type Data type of tag Start value Start value of tag The start value can be overwritten by the axis configuration. Access Effective Access to tag in the user program: RW The tag can be read and written in the user program. R The tag can be read in the user program. - The tag cannot be used in the user program. Specifies when a change to the tag takes effect. 1 When axis is activated (<Axis name>.StatusBits.Activated tag changes from FALSE -> TRUE), disabled, or enabled 2 When axis is enabled WinCC Basic V13.0 System Manual, 02/2014 4497 Using technology functions 11.2 Using S7-1200 Motion Control HMI 5 The next time an MC_MoveAbsolute, MC_MoveRelative, MC_MoveVelocity, MC_MoveJog, MC_Halt, MC_CommandTable or active MC_Home command is started (Mode = 3). 6 When a MC_MoveJog command is stopped The tag can be used in an HMI system. <Axis name>.Config.DynamicDefaults.Acceleration Acceleration of axis (specified in the configured dimension unit) Data type Start value Access Effective HMI Real 4.8E+001 RW 5 CPU Firmware V1.0 X 1, 5, 6 CPU firmware as of V2.0 <Axis name>.Config.DynamicDefaults.Deceleration Deceleration of axis (specified in the configured dimension unit) Data type Start value Access Effective HMI Real 4.8E+001 RW 5, 6 CPU Firmware V1.0 X 1, 5, 6 CPU firmware as of V2.0 <Axis name>.Config.DynamicDefaults.EmergencyDeceleration Emergency stop deceleration of axis (specified in the configured dimension unit) Data type Start value Access Effective HMI Real 1.2E+002 RW 2, 5, 6 CPU Firmware V1.0 X 1, 5, 6 CPU firmware as of V2.0 <Axis name>.Config.DynamicDefaults.JerkActive ("Axis" technology object as of V2.0) TRUE = the jerk limit is activated Data type Start value Access Effective HMI Bool FALSE RW 1, 5 X <Axis name>.Config.DynamicDefaults.Jerk ("Axis" technology object as of V2.0) Jerk during axis acceleration and deceleration ramp (specified in the configured unit of measurement) Data type Start value Access Effective HMI Real 1.92E+002 RW 1, 5 X See also Tags of the positioning axis technology object as of V4 (Page 4446) 4498 WinCC Basic V13.0 System Manual, 02/2014 Using technology functions 11.2 Using S7-1200 Motion Control Config.PositionLimits_SW tags V1...3 Legend Data type Data type of tag Start value Start value of tag The start value can be overwritten by the axis configuration. Access Effective HMI Access to tag in the user program: RW The tag can be read and written in the user program. R The tag can be read in the user program. - The tag cannot be used in the user program. Specifies when a change to the tag takes effect. 1 When axis is activated (<Axis name>.StatusBits.Activated tag changes from FALSE -> TRUE), disabled, or enabled 4 Upon the next start of a Motion Control command after a standstill of the axis. The axis standstill can be checked with tag <Axis name>. StatusBits.Standstill. 5 The next time an MC_MoveAbsolute, MC_MoveRelative, MC_MoveVelocity, MC_MoveJog, MC_Halt, MC_CommandTable or active MC_Home command is started (Mode = 3). The tag can be used in an HMI system. <Axis name>.Config.PositionLimits_SW.Active TRUE = The software limit switches are activated Data type Start value Access Effective HMI Bool FALSE RW 4 CPU Firmware V1.0 X 1, 5, 6 CPU firmware as of V2.0 <Axis name>.Config.PositionLimits_SW.MinPosition Position of lower software limit switch (specified in the configured unit of measurement) Data type Start value Access Effective HMI Real -1.0E+004 RW 4 CPU Firmware V1.0 X 1, 5, 6 CPU firmware as of V2.0 <Axis name>.Config.PositionLimits_SW.MaxPosition Position of upper software limit switch (specified in the configured unit of measurement) Data type Start value Access Effective HMI Real 1.0E+004 RW 4 CPU Firmware V1.0 X 1, 5, 6 CPU firmware as of V2.0 WinCC Basic V13.0 System Manual, 02/2014 4499 Using technology functions 11.2 Using S7-1200 Motion Control See also Tags of the positioning axis technology object as of V4 (Page 4446) Config.PositionLimits_HW tags V1...3 Legend Data type Data type of tag Start value Start value of tag The start value can be overwritten by the axis configuration. Access Effective HMI Access to tag in the user program: RW The tag can be read and written in the user program. R The tag can be read in the user program. - The tag cannot be used in the user program. Specifies when a change to the tag takes effect. 1 When axis is activated (<Axis name>.StatusBits.Activated tag changes from FALSE -> TRUE), disabled, or enabled 3 After axis enable (the axis must have previously been at a standstill). The axis standstill can be checked with tag <Axis name>. StatusBits.Standstill. 4 Upon the next start of a Motion Control command after a standstill of the axis. The axis standstill can be checked with tag <Axis name>. StatusBits.Standstill. 5 The next time an MC_MoveAbsolute, MC_MoveRelative, MC_MoveVelocity, MC_MoveJog, MC_Halt, MC_CommandTable or active MC_Home command is started (Mode = 3). The tag can be used in an HMI system. <Axis name>.Config.PositionLimits_HW.Active TRUE = The hardware limit switches are active. Data type Start value Access Effective HMI Bool FALSE RW 3, 4 CPU Firmware V1.0 X 1, 5, 6 CPU firmware as of V2.0 <Axis name>.Config.PositionLimits_HW.MinSwitchedLevel TRUE = 24 V at CPU input corresponds to lower hardware limit switch approached FALSE = 0 V at CPU input corresponds to lower hardware limit switch approached Data type Start value Access Effective HMI Bool FALSE R - X <Axis name>.Config.PositionLimits_HW.MinFallingEvent Tag cannot be evaluated in the user program. Data type Start value Access Effective HMI DWord DW#16#00000000 - - - 4500 WinCC Basic V13.0 System Manual, 02/2014 Using technology functions 11.2 Using S7-1200 Motion Control <Axis name>.Config.PositionLimits_HW.MinRisingEvent Tag cannot be evaluated in the user program. Data type Start value Access Effective HMI DWord DW#16#00000000 - - - <Axis name>.Config.PositionLimits_HW.MaxSwitchedLevel TRUE = 24 V at CPU input corresponds to upper hardware limit switch approached FALSE = 0 V at CPU input corresponds to upper hardware limit switch approached Data type Start value Access Effective HMI Bool FALSE R - X <Axis name>.Config.PositionLimits_HW.MaxFallingEvent Tag cannot be evaluated in the user program. Data type Start value Access Effective HMI DWord DW#16#00000000 - - - <Axis name>.Config.PositionLimits_HW.MaxRisingEvent Tag cannot be evaluated in the user program. Data type Start value Access Effective HMI DWord DW#16#00000000 - - - See also Tags of the positioning axis technology object as of V4 (Page 4446) Config.Homing tags V1...3 Legend Data type Data type of tag Start value Start value of tag The start value can be overwritten by the axis configuration. Access Effective HMI Access to tag in the user program: RW The tag can be read and written in the user program. R The tag can be read in the user program. - The tag cannot be used in the user program. Specifies when a change to the tag takes effect. 1 When axis is activated (<Axis name>.StatusBits.Activated tag changes from FALSE -> TRUE), disabled, or enabled 7 When a passive homing command is started 8 When an active homing command is started The tag can be used in an HMI system. WinCC Basic V13.0 System Manual, 02/2014 4501 Using technology functions 11.2 Using S7-1200 Motion Control <Axis name>.Config.Homing.AutoReversal TRUE = Direction reversal at hardware limit switch enabled (active homing) FALSE = Direction reversal at hardware limit switch disabled (active homing) Data type Start value Access Effective HMI Bool TRUE R - Technology object "Axis" V1.0 X RW 1, 8 Technology object "Axis" V2.0 <Axis name>.Config.Homing.Direction TRUE = Positive approach direction to search for reference point switch and positive homing direction (active homing) FALSE = Negative approach direction to search for reference point switch and positive homing direction (active homing) Data type Start value Access Effective HMI Bool TRUE R - Technology object "Axis" V1.0 X RW 1, 8 Technology object "Axis" V2.0 <Axis name>.Config.Homing.SideActiveHoming ("Axis" technology object as of V2.0) TRUE = Homing on high end of the reference point switch (active homing) TRUE = Homing on lower end of the reference point switch (active homing) Data type Start value Access Effective HMI Bool TRUE RW 1, 8 X <Axis name>.Config.Homing.SidePassiveHoming ("Axis" technology object as of V2.0) TRUE = Homing on high end of the reference point switch (passive homing) TRUE = Homing on lower end of the reference point switch (passive homing) Data type Start value Access Effective HMI Bool TRUE RW 1, 7 X <Axis name>.Config.Homing.RisingEdge (as of technology object "Axis" V1.0) TRUE = Homing with negative signal edge of the reference point switch (active homing) FALSE = Homing with positive signal edge of the reference point switch (active homing) For information on the effect of the tag on passive homing, refer to the description in "Configuration - Homing". Data type Start value Access Effective HMI Bool FALSE R - X <Axis name>.Config.Homing.Offset Home position offset /specified in the configured unit of measurement (active homing) Data type 4502 Start value Access Effective HMI WinCC Basic V13.0 System Manual, 02/2014 Using technology functions 11.2 Using S7-1200 Motion Control <Axis name>.Config.Homing.Offset Real 0.0 R RW - Technology object "Axis" V1.0 1, 8 Technology object "Axis" V2.0 X <Axis name>.Config.Homing.FastVelocity Approach velocity / specified in the configured unit of measurement (active homing) Data type Start value Access Effective HMI Real 2.0E+002 R - Technology object "Axis" V1.0 X RW 1, 8 Technology object "Axis" V2.0 <Axis name>.Config.Homing.SlowVelocity Homing velocity / specified in the configured unit of measurement (active homing) Data type Start value Access Effective HMI Real 4.0E+001 R - Technology object "Axis" V1.0 X RW 1, 8 Technology object "Axis" V2.0 <Axis name>.Config.Homing.FallingEvent Tag cannot be evaluated in the user program. Data type Start value Access Effective HMI DWord DW#16#00000000 - - - HMI <Axis name>.Config.Homing.RisingEvent Tag cannot be evaluated in the user program. Data type Start value Access Effective DWord DW#16#00000000 - - See also Tags of the positioning axis technology object as of V4 (Page 4446) MotionStatus tags V1...3 Legend Data type Data type of tag Start value Start value of tag Access Access to tag in the user program: RW WinCC Basic V13.0 System Manual, 02/2014 The tag can be read and written in the user program. 4503 Using technology functions 11.2 Using S7-1200 Motion Control R The tag can be read in the user program. - The tag cannot be used in the user program. Effective Specifies when a change to the tag takes effect. HMI The tag can be used in an HMI system. <Axis name>.MotionStatus.Position Current position of the axis (specified in the configured unit of measurement) If the axis is not homed, the tag indicates the position value relative to the enable position of the axis. Data type Start value Access Effective HMI Real 0.0 R - X <Axis name>.MotionStatus.Velocity Current velocity of the axis (specified in the configured unit of measurement) Data type Start value Access Effective HMI Real 0.0 R - X <Axis name>.MotionStatus.Distance Current distance to the target position of the axis (specified in the configured unit of measurement) The value of the tag is only valid during execution of a positioning command with "MC_MoveAbsolute" or "MC_MoveRelative" or of the axis command table. Data type Start value Access Effective HMI Real 0.0 R - X <Axis name>.MotionStatus.TargetPosition Target position of axis (specified in the configured unit of measurement) The value of the tag is only valid during execution of a positioning command with "MC_MoveAbsolute" or "MC_MoveRelative" or of the axis command table. Data type Start value Access Effective HMI Real 0.0 R - X See also Motion status (Page 4421) Tags of the positioning axis technology object as of V4 (Page 4446) StatusBits tags V1...3 Legend Data type Data type of tag Start value Start value of tag Access Access to tag in the user program: 4504 RW The tag can be read and written in the user program. R The tag can be read in the user program. WinCC Basic V13.0 System Manual, 02/2014 Using technology functions 11.2 Using S7-1200 Motion Control - The tag cannot be used in the user program. Effective Specifies when a change to the tag takes effect. HMI The tag can be used in an HMI system. <Axis name>.StatusBits.Activated TRUE = The axis is activated. It is connected to the assigned PTO (Pulse Train Output). The data of the technology data block will be updated cyclically. Data type Start value Access Effective HMI Bool FALSE R - X <Axis name>.StatusBits.Enable TRUE = The axis is enabled and ready to take on Motion Control commands. Data type Start value Access Effective HMI Bool FALSE R - X <Axis name>.StatusBits.HomingDone TRUE = The axis is homed and is capable of executing absolute positioning commands. The axis does not have to be homed for relative positioning. The status is FALSE during active homing. The status remains TRUE during passive homing if the axis has already been homed. Data type Start value Access Effective HMI Bool FALSE R - X <Axis name>.StatusBits.Done TRUE = No Motion Control command is active on the axis. Data type Start value Access Effective HMI Bool FALSE R - X <Axis name>.StatusBits.Error TRUE = An error occurred in the axis technology object. Detailed information about the error is available in automatic mode in the "ErrorID" and "ErrorInfo" parameters of the Motion Control instructions. In manual mode, the "Error message" box of the axis control panel displays detailed information about the cause of error. Data type Start value Access Effective HMI Bool FALSE R - X <Axis name>.StatusBits.StandStill TRUE = The axis is at a standstill. Data type Start value Access Effective HMI Bool FALSE R - X WinCC Basic V13.0 System Manual, 02/2014 4505 Using technology functions 11.2 Using S7-1200 Motion Control <Axis name>.StatusBits.PositioningCommand TRUE = The axis is executing a positioning command. Data type Start value Access Effective HMI Bool FALSE R - X <Axis name>.StatusBits.SpeedCommand TRUE = The axis is executing a travel command at predefined velocity. Data type Start value Access Effective HMI Bool FALSE R - X <Axis name>.StatusBits.Homing TRUE = The axis is executing a homing command of the "MC_Home" Motion Control instruction or axis command table. Data type Start value Access Effective HMI Bool FALSE R - X <Axis name>.StatusBits.CommandTableActive TRUE = The axis is controlled by Motion Control instruction "MC_CommandTable". Data type Start value Access Effective HMI Bool FALSE R - X <Axis name>.StatusBits.ConstantVelocity TRUE = The axis travels at constant velocity. Data type Start value Access Effective HMI Bool FALSE R - X <Axis name>.StatusBits.Acceleration TRUE = The axis accelerates. Data type Start value Access Effective HMI Bool FALSE R - X <Axis name>.StatusBits.Deceleration TRUE = The axis decelerates (slows down). Data type Start value Access Effective HMI Bool FALSE R - X <Axis name>.StatusBits.ControlPanelActive TRUE = The "Manual control" mode has been enabled in the axis command table. The axis command table has control priority over the "Axis" technology object. The axis cannot be controlled from the user program. Data type Start value Access Effective HMI Bool FALSE R - X 4506 WinCC Basic V13.0 System Manual, 02/2014 Using technology functions 11.2 Using S7-1200 Motion Control <Axis name>.StatusBits.DriveReady TRUE = The drive is ready. Data type Start value Access Effective HMI Bool FALSE R - X <Axis name>.StatusBits.RestartRequired TRUE = Values were modified in the load memory. To download the values in the CPU RUN operating mode to the work memory, you need to restart the axis. Use the Motion Control instruction MC_Reset to do this. Data type Start value Access Effective HMI Bool FALSE R - X See also Status and error bits (technology objects as of V4) (Page 4418) Tags of the positioning axis technology object as of V4 (Page 4446) ErrorBits tags V1...3 Legend Data type Data type of tag Start value Start value of tag Access Access to tag in the user program: RW The tag can be read and written in the user program. R The tag can be read in the user program. - The tag cannot be used in the user program. Effective Specifies when a change to the tag takes effect. HMI The tag can be used in an HMI system. <Axis name>.ErrorBits.SystemFault TRUE = Internal system error. Data type Start value Access Effective HMI Bool FALSE R - X <Axis name>.ErrorBits.ConfigFault TRUE = Incorrect configuration of axis. Data type Start value Access Effective HMI Bool FALSE R - X WinCC Basic V13.0 System Manual, 02/2014 4507 Using technology functions 11.2 Using S7-1200 Motion Control <Axis name>.ErrorBits.DriveFault TRUE = The drive has reported an error due to loss of its "Drive ready" signal. Data type Start value Access Effective HMI Bool FALSE R - X <Axis name>.ErrorBits.SwLimitMinReached TRUE = The lower software limit switch has been reached. Data type Start value Access Effective HMI Bool FALSE R - X <Axis name>.ErrorBits.SwLimitMinExceeded TRUE = The lower software limit switch has been exceeded. Data type Start value Access Effective HMI Bool FALSE R - X <Axis name>.ErrorBits.SwLimitMaxReached TRUE = The upper software limit switch has been reached. Data type Start value Access Effective HMI Bool FALSE R - X <Axis name>.ErrorBits.SwLimitMaxExceeded TRUE = The upper software limit switch has been exceeded. Data type Start value Access Effective HMI Bool FALSE R - X <Axis name>.ErrorBits.HwLimitMin TRUE = The lower hardware limit switch has been approached. Data type Start value Access Effective HMI Bool FALSE R - X <Axis name>.ErrorBits.HwLimitMax TRUE = The upper hardware limit switch has been approached. Data type Start value Access Effective HMI Bool FALSE R - X <Axis name>.ErrorBits.HwUsed TRUE = A second axis is using the same PTO (Pulse Train Output) and is enabled with "MC_Power". Data type Start value Access Effective HMI Bool FALSE R - X 4508 WinCC Basic V13.0 System Manual, 02/2014 Using technology functions 11.2 Using S7-1200 Motion Control See also Status and error bits (technology objects as of V4) (Page 4418) Tags of the positioning axis technology object as of V4 (Page 4446) Internal tags V1...3 The "Internal" tags contain no user-relevant data; these tags cannot be accessed in the user program. See also Tags of the positioning axis technology object as of V4 (Page 4446) ControlPanel tags V1...3 The "ControlPanel" tags contain no user-relevant data; these tags cannot be accessed in the user program. See also Tags of the positioning axis technology object as of V4 (Page 4446) Update of the technology object tags The status and error information of the axis indicated in the technology object tags is updated at each cycle control point. The change in values of editable configuration tags does not take effect immediately. For information on the conditions under which a change takes effect, refer to the detailed description of the relevant tag. Tags of the command table technology object V1...3 Config.Command.Command[1 ... 32] tags V1...3 Legend Data type Data type of the tag Start value Start value of tag The start value can be overwritten by the configuration of the command table. Access Access to the tag in the user program: RW The tag can be read and written in the user program. R The tag can be read in the user program. - The tag cannot be used in the user program. WinCC Basic V13.0 System Manual, 02/2014 4509 Using technology functions 11.2 Using S7-1200 Motion Control Effective Specifies when a change in the tag takes effect. HMI The tag can be used in an HMI system. <Command table>.Config.Command.Command[x].Type Command type 0 = "Empty" command 2 = "Hold" command 5 = "Relative positioning" command 6 = "Absolute positioning" command 7 = "Velocity setpoint" command 151 = "Wait" command Data type Start value Access Effective HMI Int 0 RW - X Access Effective HMI RW - X <Command table>. Config.Command.Command[x].Position Command target position / travel path Data type Start value Real <Command table>. Config.Command.Command[x].Velocity Command velocity Data type Start value Access Effective HMI Real 0.0 RW - X <Command table>. Config.Command.Command[x].Duration Command duration Data type Start value Access Effective HMI Real 0.0 RW - X <Command table>. Config.Command.Command[x].BufferMode Value for command "Next step" 0 = "Complete command" 1 = "Blend movement" Data type Start value Access Effective HMI Int 0 RW - X <Command table>. Config.Command.Command[x].StepCode Command step code Data type Start value Access Effective HMI Word 0 RW - X 4510 WinCC Basic V13.0 System Manual, 02/2014 Using technology functions 11.2 Using S7-1200 Motion Control See also Tags of the command table technology object as of V4 (Page 4465) WinCC Basic V13.0 System Manual, 02/2014 4511 Using Team Engineering 12.1 Shared commissioning of projects 12.1.1 Basics for shared commissioning 12 Introduction As part of Team Engineering , you have the option to perform shared commissioning of projects. Several editors can access one CPU at the same time with up to five engineering systems (ES) in this process. A special advantage is that parts of a master project can be edited independently and offline at the same time during the commissioning phase. The changes of the other editors are displayed in the dialog "Software synchronization" during loading and synchronized automatically, if possible. Certain online functions can also be executed at the same time from several engineering systems on the shared CPU, for example: Monitoring blocks on the CPU Controlling blocks on the CPU Trace functions The following online functions cannot be executed at the same time: Forcing: Only one ES can force on the CPU. Loading: Only one ES can load to the CPU. You can also find additional information on the topic of Team Engineering at Service and support in Siemens Industry online support (http://support.automation.siemens.com/WW/view/ en/82142829). Creating a master project A "master project" structured according to the specified rules (Page 4519), which already contains the complete configured hardware configuration with all required tags and blocks, is used as the basis for the shared commissioning. This project is loaded in the jointly used CPU WinCC Basic V13.0 System Manual, 02/2014 4513 Using Team Engineering 12.1 Shared commissioning of projects and then distributed as "master project" by means of project copies to up to five participating engineering systems. (QJLQHHULQJSKDVH &RPPLVVLRQLQJSKDVH 3URMHFWFRS\ &UHDWHSURMHFWVWUXFWXUH &RQILJXUHKDUGZDUH&UHDWH SURJUDP &KDQJHV WR)%V)&V'%V LQSURJUDPSDUW &38 3URMHFWFRS\ &KDQJHV WR)%V)&V'%V LQSURJUDPSDUW 0DVWHUSURMHFW ([HFXWLQJFHQWUDO FKDQJHVWKDWDIIHFW VKDUHGSURMHFWSDUWV 6KDUHG&38 3URMHFWFRS\ &KDQJHV WR)%V)&V'%V LQSURJUDPSDUW Working with project copies Each engineering system only processes the parts it was assigned within the specific project copy. This is especially important to avoid conflicts during loading and unintentional overwriting of blocks that were already modified by other engineering systems. Each ES loads its parts to the shared CPU after editing. The TIA Portal helps you during download to the CPU. The changes made since the last download are displayed in the dialog "Software synchronization before loading to a device" (hereafter referred to as "synchronization dialog"), by means of an online-offline comparison. You are provided recommendations during download to the CPU about how you can synchronize the offline data you have edited with the existing online data. If there are "competing changes", you may have to synchronize them manually. Competing changes are: when different editors edit the same block in different project copies at the same time. when PLC tags (I, Q, M, T, C) are added, changed or deleted in the project copies. when blocks that have relations to the hardware configuration are edited in the project copies. when F blocks are edited in the project copies. Each editor loads their changes only after all conflicts have been removed. 4514 WinCC Basic V13.0 System Manual, 02/2014 Using Team Engineering 12.1 Shared commissioning of projects The procedure for editing and loading of project copies can be repeated as often as necessary by the individual engineering systems until the shared commissioning is complete. Integrating project copies into the master project once again The individual project copies must once again be integrated into the master project at the end of commissioning at the same time. This way you also back up the data that only exist in the offline projects and have not been downloaded to the CPU. These include, for example, the project languages and text lists created in the project copies. To do this, open the master project and one project copy as reference object. You determine the differences between the two projects by performing an offline/offline comparison using the comparison editor. Copy the edited objects from the respective project copy to the master project. Repeat this step for all project copies. When the shared commissioning is completed, you have an executable master project with all created project data. The integration of the project data into the master project is required even if you determine during the commissioning phase that the shared central elements need to be expanded or corrected, for example, the PLC tag table needs to be expanded, or a new hardware component needs to be added. Notes on compatibility The following compatibility rules apply to shared commissioning: If an engineering system with TIA Portal V13 or later is online on the CPU and performs a download, a second ES cannot establish an online connection regardless of the version. If an engineering system with TIA Portal < V13 is online on the CPU, a second ES cannot establish an online connection regardless of the version. See also Requirements for shared commissioning (Page 4515) Procedure for shared commissioning (Page 4516) 12.1.2 Requirements for shared commissioning Software and hardware requirements For shared commissioning of projects, the minimum software and hardware requirements for the installation of TIA Portal V13 or later must be met. The following requirements also apply: Software: WinCC Basic V13.0 System Manual, 02/2014 4515 Using Team Engineering 12.1 Shared commissioning of projects You have installed TIA Portal V13 or later and the "SIMATIC STEP 7 Professional" software package on the involved engineering systems. The same software version must be installed on all engineering systems. The master project must be one created with V13 or later. Hardware: You have access to a fully configured CPU S7-1500 as of firmware version V1.5. The involved engineering systems (max. 5) can establish an online connection to this CPU. Requirements for shared, parallel working on the project The following requirements are in effect for shared commissioning of projects: You have created a project with complete hardware configuration and fully programmed user program that can be commissioned. The project was downloaded to the CPU and defined as "master project". Multiple engineering systems have access to this CPU and can establish an online connection to this CPU. You are familiar with the defined rules and procedures for working together on one CPU. Note on compatibity mode The functions for shared commissioning are not available in compatibility mode. See also Basics for shared commissioning (Page 4513) Procedure for shared commissioning (Page 4516) Rules for shared commissioning (Page 4519) 12.1.3 Procedure for shared commissioning Introduction If you are performing shared commissioning a project as part of team engineering, it is very important that all editors of the project observe a defined procedure. Only when the specified procedure is observed are changes and corrections in the project automatically synchronized and applied, and changes of individual editors not unintentionally overwritten during loading or even lost in case of competing changes. 4516 WinCC Basic V13.0 System Manual, 02/2014 Using Team Engineering 12.1 Shared commissioning of projects Procedure for creating the master project The master project is created in the following steps: 1. Create a master project that includes the entire project structure. 2. Fully configure the hardware for the master project. 3. Define a language as project language, which must also be used exclusively by all participating engineering systems. 4. Create all tags and blocks that are required in the master project. 5. Create your own folders and groups for the blocks to be edited by the individual engineering systems. 6. Create a fully programmed and executable user program. 7. Download the master project to the shared CPU. 8. Save the master project following every download. For this, also observe the Rules for shared commissioning (Page 4519). Procedure for shared commissioning Shared commissioning takes place with the following steps: 1. Download the master project to the shared CPU. 2. Create copies of the master project and distribute them to the editors involved in the project on the associated engineering systems. 3. Inform all editors who is to edit the specific parts of the project copies and who may download to the CPU. 4. Have the project copies edited in the individual engineering systems. 5. After editing, the individual engineering systems download the changes one after the other to the CPU. 6. All changes are automatically detected during loading by means of an online-offline comparison. The displayed synchronization dialog offer you recommendations for synchronizing the modified data when possible. You may first have to download blocks that were edited by other editors to your ES before you can download your changes to the CPU. This may be needed to update the corrections of the other editors that have already been downloaded to the CPU in your project copy. The following synchronization options are available: - Download block: There are edited blocks on the CPU that must be updated in your project copy. - Download block: There are new blocks on the CPU that must be downloaded to your project copy. - Blocks with competing changes: System-supported synchronization is not possible in this case; the conflict must be resolved manually. 7. Manually resolve any conflicts that may occur due to competing changes or changes to central objects. 8. Download your project copy to the CPU when all conflicts have been removed. WinCC Basic V13.0 System Manual, 02/2014 4517 Using Team Engineering 12.1 Shared commissioning of projects 9. Save your project copy following every download. 10.Repeat editing of project copies and download to the CPU as often as necessary until shared commissioning is complete. 11.Integrate the completely edited project copies into the master project once again in order to also back up the project data that only exist offline. You should also observe the Rules for shared commissioning (Page 4519). Procedure for manual synchronization of competing changes Manual synchronization of competing changes is performed in the following steps: 1. Start the comparison editor to manually resolve a conflict displayed in the synchronization dialog during download to the CPU. Select the shared CPU in the project tree and select the "Compare > Offline/Online" command in the shortcut menu. You can define certain actions depending on the status of the objects. Note, however, that you can only perform actions in one direction during synchronizing. 2. First, select the action "Upload from device" for all blocks that were changed by other editors on the CPU and which you want to apply. 3. If necessary, perform a detailed comparison of the blocks to identify differences between your offline blocks and the online blocks loaded on the CPU. 4. Manually correct the competing changes to the blocks. 5. Then download the affected blocks to the CPU using the "Continue without synchronization" command. 6. Save your project or project copy following every download. For this, also observe the Rules for shared commissioning (Page 4519). Note To prevent online changes occurring again while an engineering system is being manually synchronized, no downloading to the shared CPU should be performed by another participating engineering system during the manual synchronizing. Procedure for integrating project copies into the master project You integrate project copies into the master project with the following steps: 1. Open the master project and the project copy to be integrated as a reference object. 2. Copy the program parts you have edited from the respective project copy to the master project and confirm overwriting the existing objects. You can also use the comparison editor to apply your program parts to the master project. 3. Save the master project and download it to the shared CPU with the "Continue without synchronization" command. 4. Save the master project following every download. 4518 WinCC Basic V13.0 System Manual, 02/2014 Using Team Engineering 12.1 Shared commissioning of projects For this, also observe the Rules for shared commissioning (Page 4519). Procedure for modifying central objects within the master project Modification of central objects that have an effect on all program parts is performed with the following steps: 1. Stop further processing of the project copies. 2. Integrate all existing project copies one after the other into the master project as described above. 3. Download the master project to the shared CPU with the "Continue without synchronization" command. 4. Make the required modification on the shared objects such as in the hardware configuration, for example, or in the PLC tag table. The procedure is the same for modification of other central objects such as technology objects, F blocks, OBs, etc. 5. Download the master project into the CPU once again when modification is complete. 6. Save the master project following every download. 7. Distribute the updated project copies to the respective engineering systems for further processing. For this, also observe the Rules for shared commissioning (Page 4519). See also Basics for shared commissioning (Page 4513) Requirements for shared commissioning (Page 4515) Rules for shared commissioning (Page 4519) 12.1.4 Rules for shared commissioning Introduction If you are performing shared commissioning a project as part of team engineering, it is very important that all editors of the project observe predefined rules for successful cooperation. WinCC Basic V13.0 System Manual, 02/2014 4519 Using Team Engineering 12.1 Shared commissioning of projects Rules for the master project The following rules are to be observed: Create a master project that is suitable for shared editing. Divide the user program into program parts that are independent of each other. Use "Groups" to visually separate the program parts from each other. Use a main OB and a central FC for each program part which calls the functions of the part program. If possible, create a separate PLC tag table for each part. In the master project, specify a project language which cannot be changed in the project copies. If you want to exchange data between the program parts, use the FC and FB interface parameters (IN, OUT, INOUT) or global data blocks. Use global data blocks to save the data for the individual program parts, no bit memories. Do not assign different names for blocks with identical addresses. Do not assign identical names for blocks with different addresses. Example of the program structure in the master project Here is an example of a team-capable, structured master project that is suitable for parallel editing during shared commissioning. The program parts edited by the individual Engineering Systems are: Program part 1: "Conveyer" Program part 2: "Drill" Program part 3: "FurtherProgramPart" Each program part contains a "main FB", which calls the specific lower-lever functions for this program part. Example: in the "Conveyer" program part, the "ConveyerMainFB" calls the "ConveyerStartup" function. 4520 WinCC Basic V13.0 System Manual, 02/2014 Using Team Engineering 12.1 Shared commissioning of projects In team engineering, this subdivision within the project structure allows the parallel editing of individual program parts and the automatic synchronization of changes during the shared commissioning phase. Rules for shared working on one CPU Observe the following rules for shared working: Editor only edits the blocks they have been assigned in the project copy in the assigned groups. Only FBs, DBs, FCs and UDTs may be changed in the project copies, i.e. the following program elements should not be edited in the project copies: - Hardware configurations - PLC tag table - Organization blocks - Technological objects - Text lists and project language - F blocks Global data blocks should be used in programming instead of bit memories. WinCC Basic V13.0 System Manual, 02/2014 4521 Using Team Engineering 12.1 Shared commissioning of projects IEC timers and counters should be used during programming instead of SIMATIC timers and counters. The project language specified in the master project may not be changed in the project copies. Rules for editing shared, central objects Observe the following rules for shared central objects: Changes to shared central objects always have to be made by means of the master project. These objects include: - Hardware configurations - PLC tag table - Organization blocks - Technological objects - Text lists and project language - F blocks Before the shared central objects can be modified in the master project, the various working versions within the project copies must first be integrated into the master project once again. The modification can then be made within the master project, and the master project can then be downloaded to the shared CPU. Once modification is complete, new project copies can be created and distributed to the engineering systems for further processing. Rules for downloading to the CPU Observe the following rules for downloading: Editors may only download the project copies one after the other; only one engineering system can download at any given time. No other engineering system may be connected online with the CPU during download. Perform the synchronization that is offered automatically in the synchronization dialog. This ensures that changes from other editors are not unintentionally overwritten. Correct the name conflicts that are shown in the synchronization dialog, which you rename in your offline block before downloading to the CPU. A name conflict is indicated if you want to download to the CPU a block that already exists with identical name on the CPU. 4522 WinCC Basic V13.0 System Manual, 02/2014 Using Team Engineering 12.1 Shared commissioning of projects So-called "competing changes" must be corrected manually. Competing changes come about when two editors work on the same block on two engineering systems at the same time. The first editor can still download his or her changes to the CPU without any problems. However, if the second editor wants to download the same block with the changes the editor has made, the synchronization dialog displays a conflict that cannot be removed automatically. The previous changes made to this block would be undone by overwriting during download. The editors have to decide in this case which change is to be applied and which one is to be discarded. Alternatively, you can manually merge the changes with the help of the detailed comparison of the blocks in the comparison editor. Such changes should always be avoided by implementing a good project structure and corresponding agreements between the editors. Changes to central objects are displayed in the synchronization dialog but cannot be synchronized automatically. Changes to central objects always have to be made by means of the master project. Save your project or project copy following every download. Note Creating and subsequent deleting of objects in the project copies Please note that a software synchronization is also required before downloading when you create a new object in a project copy and then delete this again immediately afterwards. The creation of an object causes a change in the internal data management which cannot be undone by the subsequent deleting of the object. As a result it is necessary to perform a synchronization before the next loading if the newly created object was deleted immediately thereafter and no change in the existing object is visible within the project copy. Rules for online functions The following rules are to be observed when using online functions: Monitoring and controlling: Up to five Engineering Systems can be monitored and controlled simultaneously on the CPU blocks. A specific code block can only be monitored and controlled by one Engineering System at a time. However, additional Engineering Systems can simultaneously monitor and control other code blocks. Force Forcing can only be implemented on the CPU from one Engineering System at a time. The Engineering Systems that starts the forcing has taken over the forcing job exclusively. Although the other Engineering Systems receive the information that a forcing job is running, they cannot access this job and cannot also see any results. As soon as the Engineering System to which the force job belongs ends the online connection, the force job can be applied by another ES that establishes an online connection to the CPU and changes the existing force job. WinCC Basic V13.0 System Manual, 02/2014 4523 Using Team Engineering 12.2 Exchanging data with Inter Project Engineering (IPE) Trace functions: Up to four Engineering Systems can perform trace functions simultaneously. The Engineering Systems that starts the tracing has taken over the trace job exclusively. Although the other Engineering Systems can see this job in the trace editor, they cannot access it. As soon as the Engineering System to which the trace job belongs closes the trace editor, the trace job can be taken over by another ES that re-opens the trace editor. See also Basics for shared commissioning (Page 4513) Requirements for shared commissioning (Page 4515) Procedure for shared commissioning (Page 4516) 12.2 Exchanging data with Inter Project Engineering (IPE) 12.2.1 Basics of Inter Project Engineering (IPE) Introduction to Inter Project Engineering (IPE) The functionality of Inter Project Engineering, hereinafter referred to as IPE, is used to exchange the controller data in a source project between different projects with the help of a device proxy. You can then transfer this data to other projects, for visualization in HMI, for example, and use it there for further configuration. Inter Project Engineering gives you a simple way of providing controller data from a PLC programming across multiple projects for an HMI configuration. Using the object "Device Proxy Data", you exchange controller data across multiple projects consistently and easily without redundant configuration overheads. This makes it possible for HMI project engineers to work on a project without the hardware configuration having to be present in their project. This means they can work on the PLC project and on the HMI project at the same time. You can exchange the following controller data between projects via the device proxy: Program blocks Technological objects PLC tags PLC alarms The following data is automatically included in the exchange: 4524 WinCC Basic V13.0 System Manual, 02/2014 Using Team Engineering 12.2 Exchanging data with Inter Project Engineering (IPE) Controller interfaces Configured communication processors and communication modules This automatic data exchange ensures that the interfaces and the configured communication processors and modules are transferred along with the data you selected. This data is required to allow you to continue working consistently and without problems in your target project. Cross-project data exchange The following options are available for cross-project data exchange with Inter Project Engineering: Exchanging controller data via IPE file Exchanging controller data via project file Exchanging controller data via IPE file The figure below shows cross-project data exchange via an IPE file. 6RXUFHSURMHFW 7DUJHWSURMHFW 3/&B$ ([SRUW 'HYLFHSUR[\GDWD 3/&B$ 'HYLFHSUR[\GDWD 3/&B$ ,QLWLDOL]DWLRQ ,3(ILOH 3/&GHYLFHSUR[\ The PLC controller data from the source project is transferred to the PLC in the target project via the object "Device Proxy Data". Controller data that is exchanged via an IPE file must originate from TIA Portal Projects V13 or higher. Exchanging controller data via a project file The figure below shows cross-project data exchange via a project file. WinCC Basic V13.0 System Manual, 02/2014 4525 Using Team Engineering 12.2 Exchanging data with Inter Project Engineering (IPE) 6RXUFHSURMHFW 3/&B$ 'HYLFHSUR[\GDWD 7DUJHWSURMHFW ,QLWLDOL]DWLRQ 3URMHFWILOH 3/&B% 'HYLFHSUR[\GDWD 3/&GHYLFHSUR[\ The PLC controller data from the source project is transferred to the PLC in the target project via a project file. You can easily transfer and continue to use controller data from older TIA Portal projects as well as STEP 7 Classic projects that are not integrated in TIA Portal in your current TIA Portal projects. See also Requirements for Inter Project Engineering (IPE) (Page 4526) Procedure for working with Inter Project Engineering (IPE) (Page 4527) 12.2.2 Requirements for Inter Project Engineering (IPE) Software and hardware requirements To use the functionality of Inter Project Engineering, the minimum software and hardware requirements for the installation of TIA Portal V13 or higher must be met. The following requirements also apply: You have installed TIA Portal V13 or higher and the "SIMATIC STEP 7 Professional" software package. You are using a CPU of the S7-1200/1500 or S7-300/400 series. The same software version must be installed on all involved controllers. 4526 WinCC Basic V13.0 System Manual, 02/2014 Using Team Engineering 12.2 Exchanging data with Inter Project Engineering (IPE) Requirements for IPE The requirements for accepting controller data from projects are as follows: You have created a project with hardware configuration and PLC data that can be transferred to another project. You have made sure that the project is consistent before you transfer the controller data by means of the device proxy data. You are familiar with the defined procedures for Inter Project Engineering. Notes on compatibility mode The functions for Inter Project Engineering are not available in compatibility mode. See also Basics of Inter Project Engineering (IPE) (Page 4524) Procedure for working with Inter Project Engineering (IPE) (Page 4527) 12.2.3 Procedure for working with Inter Project Engineering (IPE) Exchanging controller data across projects You can use the functionality of Inter Project Engineering to exchange existing controller data between different projects with the help of a device proxy and to continue using this data in another project. The device proxy provides you with a consistent and convenient way of exchanging data between projects without redundant configuration overheads. Procedure for exchanging controller data via an IPE file To exchange data via an IPE file, follow these steps: 1. Using TIA Portal V13 or higher, create a project with all required controller data and an executable user program. 2. Configure the hardware required for the project. 3. Compile the project to ensure consistency in your project. 4. In your project, create the object "Device Proxy Data" below the required CPU by clicking the corresponding command "Add device proxy data" in the "Device Proxy Data" folder. Result: The "Device Proxy Data" object has been created. 5. Select the required device proxy data in the project tree and double-click the object to open it in the editor. WinCC Basic V13.0 System Manual, 02/2014 4527 Using Team Engineering 12.2 Exchanging data with Inter Project Engineering (IPE) 6. Enter the required data for the device proxy data in the editor under "General" or apply the default setting. You can change the name and enter a comment for export of the controller data. In the "Define content" area of the editor select which of the existing controller data you wish to export as IPE file and click "Export device proxy data". 7. In the subsequent dialog, enter the name and storage location for the IPE file to be created and click "Save". You will be notified as soon as the export has been completed successfully. Result: The selected controller data are exported as IPE file. 8. In your target project, create a device proxy to be able to import the controller data contained in the IPE file. To do so, click the command "Add new device" and select the required device proxy in the dialog that opens. 9. Click the newly created device proxy and select the "Initialize device proxy" command from the shortcut menu. 10.Select the previously created IPE file to be used for the initialization, and confirm the selection in the following dialog with "OK". This starts the initialization. Result: The controller data from the source project contained in the IPE file is transferred to the device proxy in the target project. After the successful exchange of controller data, you can continue with the configuration in your target project and, for example, connect PLC tags with HMI tags. The controller data can be updated as often as required when it is changed in the source project. Procedure for exchanging controller data via a project file When exchanging controller data via a project file, device proxy data can either be predefined in the source project or it can be defined and selected from the target project. Follow these steps to exchange data via a project file: 1. Using TIA Portal V13 or higher, create a project with all required controller data and an executable user program. 2. Configure the hardware required for the project. 3. Compile the project to ensure consistency in your project. 4. Open the TIA Portal project from which you want to import the controller data into the target project. 5. In your project, create the object "Device Proxy Data" below the required CPU by clicking the corresponding command "Add device proxy data" in the "Device Proxy Data" folder. Result: The "Device Proxy Data" object has been created. 6. Enter the required data for the device proxy data in the editor under "General" or apply the default setting. You can change the name and enter a comment for the device proxy data. 7. In the "Define content" area of the editor select which of the existing controller data you want to provide by means of the device proxy data. 8. Click "Save" to save the changes in the project. Result: You have successfully saved the selected controller data in your device proxy data. 4528 WinCC Basic V13.0 System Manual, 02/2014 Using Team Engineering 12.2 Exchanging data with Inter Project Engineering (IPE) 9. In your target project, create a device proxy to import the controller data contained in the project file. To do so, click the command "Add new device" and select the required device proxy in the dialog that opens. 10.Click the newly created device proxy and select the "Initialize device proxy" command from the shortcut menu. 11.Select the previously created project file with the prepared device proxy data to be used for the initialization, and confirm the selection in the following dialog with "OK". This starts the initialization. Result: The controller data from the source project contained in the project file is transferred to the device proxy in the target project. After the successful exchange of controller data, you can continue with the configuration in your target project and, for example, connect PLC tags with HMI tags. The controller data can be updated as often as required when it is changed in the source project. Procedure for updating already transferred controller data System requirements for the update: The following requirements must be met for updating already transferred controller data with the help of the already created "Device Proxy Data" object: You are using the same project for the update as for the previous transfer of the controller data. You are using the already created "Device Proxy Data" for transfer of the controller data. You have not made any changes to the hardware configuration or the communication interfaces in the meantime. You can add new hardware components. Updating procedure: 1. Open the TIA Portal project from which you want to update the controller data in the target project. 2. Double-click the existing "Device Proxy Data" object and select under content which controller data you want to make available for the update. 3. Save the project or export the IPE file once again. 4. Open the required target project in the TIA Portal. 5. Click the existing device proxy in the target project and select the "Update device proxy" command from the shortcut menu. 6. Select the source which is to be used for the update, and confirm the selection. 7. In the following dialog, select under "Device" the CPU that was previously used as source, from which the controller data is to be re-imported. 8. Under "Defined device proxy data", select the required object and exit the dialog with "OK". 9. The update is then started and the selected device proxy data is transferred from the source project to the device proxy in the target project. WinCC Basic V13.0 System Manual, 02/2014 4529 Using Team Engineering 12.2 Exchanging data with Inter Project Engineering (IPE) After the successful update of the controller data, you can continue with the configuration in your target object and, for example, connect PLC tags with HMI tags. The controller data can be updated as often as required when it is changed in the source project. See also Basics of Inter Project Engineering (IPE) (Page 4524) Requirements for Inter Project Engineering (IPE) (Page 4526) Creating device proxy data (Page 1713) Opening device proxy data (Page 1714) Exchange of controller data via IPE file (Page 1714) 4530 WinCC Basic V13.0 System Manual, 02/2014 Using online and diagnostics functions 13.1 13 Displaying accessible devices Accessible devices Accessible devices are all devices connected to an interface of the programming device / PC and that are turned on. Devices that allow only restricted configuration using the currently installed products or that cannot be configured at all can also be displayed. Displaying accessible devices on an interface of the programming device / PC in the project tree To display accessible devices on a single interface of the programming device / PC, follow these steps: 1. Open the "Online access" folder in the project tree. 2. Click on the arrow to the left of the interface to show all the objects arranged below the interface. 3. Double-click on the "Update accessible devices" command below the interface. All devices that are accessible over this interface are displayed in the project tree. When there is a large number of connected devices, the update process may take some time. You can see the progress of the update in the status bar. If you have found the desired device before the update is completed, you can cancel the update of accessible devices. To do this, click on the cross to the right of the progress bar. Displaying accessible devices in a list To display the accessible devices on all available interfaces in an overview list, follow these steps: 1. Select the "Accessible devices" command in the "Online" menu. The "Accessible devices" dialog is displayed. 2. Select the type of interface from the "Type of the PG/PC interface" drop-down list. The "PG/ PC interface" drop-down list then shows only the interfaces of the programming device / PC that match the selected interface type. 3. Select the required interface of the programming device / PC from the "PG/PC interface" drop-down list, for example an Industrial Ethernet adapter. If no devices are available on an interface, an unbroken connecting line is displayed between the programming device / PC and the device. If devices are accessible, an unbroken connecting line is shown and the devices accessible on the selected interface of the programming device / PC are displayed in a list. WinCC Basic V13.0 System Manual, 02/2014 4531 Using online and diagnostics functions 13.2 Changing the device configuration online 4. If you have connected a new device in the meantime, click the "Refresh" button to refresh the list of accessible devices. 5. To go to a device in the project tree, select the device from the list of accessible devices and click the "Show" button. The interface to which the selected device is connected is shown as selected in the project tree. Displaying additional information about the accessible devices in the project tree To display additional information on the accessible devices in the project tree, follow these steps: 1. Click on the arrow to the left of one of the accessible devices in the project tree. All data available online, for example blocks and system data, is displayed for known devices. Objects that you cannot edit directly at this point are grayed out. If additional editing options are available for a device, for example, downloading using the shortcut menu, the device is shown in black text. See also Changing the device configuration online (Page 4532) 13.2 Changing the device configuration online You can assign parameters to some devices, preferably in small hardware setups, directly online. You do not need to create a project or have offline data to do this. In this way, you can quickly and easily change the device configuration. You do not need to compile the hardware configuration or perform a download. Depending on the device, either all changes become active immediately or they are written to the device only after confirmation. Requirement The device must support online parameter assignment. You can learn whether or not your specific devices support this function in the device manual. The device must be connected to the PG/PC and available in the list of accessible devices. Procedure To change the device configuration online, follow these steps: 1. Show the accessible devices on the interface via which the device is connected. To learn how to show the accessible devices, see the previous chapter "Showing accessible devices (Page 4531)". 2. Expand the device to display the lower-level elements. 3. Double-click the "Parametrize device" item. A configuration page for the device opens in the work area. 4532 WinCC Basic V13.0 System Manual, 02/2014 Using online and diagnostics functions 13.3 Connecting devices online 4. Make all required settings. With some devices, the new settings take effect immediately. 5. Optionally, depending on the device: Click on the "Upload to device" button. The settings are transferred to the device. 13.3 Connecting devices online 13.3.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 scope 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. WinCC Basic V13.0 System Manual, 02/2014 4533 Using online and diagnostics functions 13.3 Connecting devices online Note that suddenly terminating an online connection can lead to loss of data or a connected device may interrupt program execution. Performing an LED flash test In many online dialogs you can perform an LED flash test, if the device connected online supports this feature. If you select the "Flash LED" check box, an LED flashes on the currently selected device. 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 4535) 4534 WinCC Basic V13.0 System Manual, 02/2014 Using online and diagnostics functions 13.3 Connecting devices online 13.3.2 View in online mode Online displays After the online connection has been established successfully, the user interface changes. If a device is unavailable, this is indicated by a symbol. The following figure shows a device connected online and the corresponding user interface: The title bar of the active window gets an orange background as soon as at least one of WinCC Basic V13.0 System Manual, 02/2014 the devices currently displayed in the editor has been successfully connected online. If one or more devices are unavailable, a symbol for a broken connection appears in the title bar of the editor. 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. 4535 Using online and diagnostics functions 13.3 Connecting devices online 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 4533) Basics of project data comparison (Page 273) 13.3.3 Establishing and canceling an online connection Requirement At least one PG/PC interface is installed and is physically connected to a device, for example with an Ethernet cable. As an alternative, it is also possible to establish a virtual connection using PLCSIM. Go online To establish an online connection, follow these steps: 1. In the project tree, select one or mote devices to which you want an online connection to be established. 2. Select the "Go online" command in the "Online" menu. If the device was already connected to a specific PG/PC interface, the online connection is automatically established to the previous PG/PC interface. In this case, you can ignore the following steps. If there was no previous connection, the "Go online" dialog opens. 3. Select the type of interface from the "Type of the PG/PC interface" drop-down list. The "PG/ PC interface" drop-down list then shows only the interfaces of the programming device / PC that match the selected interface type. 4. Select the required interface of the programming device / PC from the "PG/PC interface" drop-down list, for example an Industrial Ethernet adapter. 4536 WinCC Basic V13.0 System Manual, 02/2014 Using online and diagnostics functions 13.3 Connecting devices online 5. In the "Connection to subnet" drop-down list, select the interface via which the device is connected to the programming device or PC. In this case, a direct connection is established to the device, without a network node, for example, an interposed switch. Alternatively, select the appropriate subnet for the connection to the programming device or PC if the device can be accessed via a network node. If you do not know how the device is connected to the programming device or PC, choose the "Try all interfaces" entry. If you selected an MPI or PROFIBUS subnet, the bus parameters configured in the programming device/PC interface are applied at this point. 6. If the device is accessible via a gateway, select the gateway that connects the two subnets involved in the "1st gateway" drop-down list. If no devices are available on the interface, a broken connecting line is displayed between the programming device / PC and the device. If devices are accessible, an unbroken connecting line is shown and the devices accessible on the selected interface of the programming device/PC are displayed in the "Compatible devices in target subnet" list. 7. Optional: Click the "Update" button to update the "Compatible devices in target subnet" list. 8. Optional: Select the "Flash LED" check box to the left of the graphic to run an LED flash test. With this function, you can check that you have selected the correct device. The LED flash test is not supported by all devices. 9. Select your device in the "Compatible devices in target subnet" table, and confirm your selection with "Go online". The online connection to the selected target device is established. Result After the online connection has been established, the title bars of the editors change to orange. An orange activity bar is also shown in the title bar of an editor and in the status bar. In the project tree, status symbols show the difference between online and offline objects. The connection path is stored for future connection attempts. It is no longer necessary to open the "Go online" dialog unless you want to select a new connection path. Note If no accessible device is displayed, select a different network access for the PG/PC interface or check the settings of the interface. Canceling an online connection To disconnect the existing online connection, follow these steps: 1. Select the device you want to disconnect from in the project tree. 2. Select the "Go offline" command in the "Online" menu. See also Connecting online with several devices (Page 4538) View in online mode (Page 4535) WinCC Basic V13.0 System Manual, 02/2014 4537 Using online and diagnostics functions 13.3 Connecting devices online Assigning a temporary IP address (Page 4550) Influence of user rights (Page 228) 13.3.4 Connecting online with several devices You can establish an online connection to several devices at the same time without needing to select individual devices previously in the network view. Requirement No device must be selected At least one PG/PC interface is installed and is physically connected to a device, for example with an Ethernet cable. As an alternative, it is also possible to establish a virtual online connection using PLCSIM or a remote connection. Procedure To establish an online connection to several devices at the same time, follow these steps: 1. Select the project in the project tree. 2. Select the "Go online" command in the "Online" menu. The "Select device for opening the online connection" dialog opens with a table of all available devices. 3. Select the devices to which you want to establish an online connection in the "Go online" column. 4. Click the "Go online" button. Result Without any further prompt for confirmation, a connection is established to all selected devices if a connection was already established to the selected devices at least once. If there was no previous online connection, the "Go online" dialog opens. In this case, first configure the online connection as described in the section "Go online and Go offline (Page 4536)". See also Establishing and canceling an online connection (Page 4536) Assigning a temporary IP address (Page 4550) 13.3.5 Disconnecting online connections of multiple devices You can disconnect the online connections to multiple devices at one time without needing to select individual devices beforehand in the network view. 4538 WinCC Basic V13.0 System Manual, 02/2014 Using online and diagnostics functions 13.4 Backing up the software and hardware configuration of a device Requirement No device is selected. There is currently an online connection to at least one device. Procedure To terminate the online connections to multiple devices at one time, follow these steps: 1. Select the "Go offline" command in the "Online" menu. The "Select devices" dialog opens with a table of all available devices. 2. Select the device for which you want to terminate the online connection in the "Go offline" column. 3. Click the "Go offline" button. Result The online connection to the all the selected devices is terminated. 13.4 Backing up the software and hardware configuration of a device 13.4.1 Creating a backup of a device Backing up the software and hardware configuration of an S7-300/400 CPU If you have already downloaded a configuration to an S7-300/400 CPU, it is advisable to make a backup. You may have modified the configuration and want to test the new configuration. Before you download the new configuration to the CPU, you can create a backup of the current device state and then restore the current configuration at a later date. The backup is performed with the current values of the CPU. In the case of S7-400 CPUs with fail-safe function, the initial values are backed up. You can create as many backups as you want and store a variety of configurations for a CPU. The backups are named with the name of the CPU and the time and date of the backup. You can find the backup in the project tree under the CPU in the "Online backups" folder. The following figure shows an S7-319 CPU for which two backups were created: WinCC Basic V13.0 System Manual, 02/2014 4539 Using online and diagnostics functions 13.4 Backing up the software and hardware configuration of a device See also Restoring the software and hardware configuration of a device (Page 4541) Backing up a device configuration (Page 4540) General information on loading (Page 265) 13.4.2 Backing up a device configuration You can back up the configuration of a S7-300/400 CPU in the TIA Portal. So you can download and test a new configuration to a device without any risk. If needed, you can restore the initial configuration of the CPU. Requirement The CPU must already be created in the project. It must be an S7-300/400 CPU. The CPU must be online. If there is no online connection, an online connection is established during the backup. 4540 WinCC Basic V13.0 System Manual, 02/2014 Using online and diagnostics functions 13.4 Backing up the software and hardware configuration of a device Procedure To create a backup of the current configuration of a CPU, follow these steps: 1. Select the CPU in the project tree. 2. Select the "Backup from online device" command in the "Online" menu. Result: A backup of the entire hardware configuration and software is created. The backup is stored in the project tree in the "Name of the CPU > Online backups" folder. The backup is assigned the name of the CPU with the time and date of the backup. You can rename the backup, but you cannot make any changes to the contents of the backup. See also Establishing and canceling an online connection (Page 4536) Restoring the software and hardware configuration of a device (Page 4541) Creating a backup of a device (Page 4539) 13.4.3 Restoring the software and hardware configuration of a device If you have backed up the configuration of a device at an earlier point in time, you can transfer the backup back to the device. The saved configuration is then restored on the device. Requirement You must have previously configure the device and stored a backup of the device in the project. Procedure To restore older software and hardware state on a device, follow these steps: 1. Open up the folder of the device in the project tree to display the lower-level objects. 2. Open the "Online backups" folder. 3. Select the backup you want to restore. 4. In the "Online" menu, select the "Download to device" command. - 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 terminating an online connection (Page 4536) WinCC Basic V13.0 System Manual, 02/2014 4541 Using online and diagnostics functions 13.5 Configuring the PG/PC interface 5. Check the messages in the "Load preview" dialog, and select the actions in the "Action" column, if necessary. Note 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. 6. As soon as loading becomes possible, the "Load" button is enabled. 7. Click the "Load" button. The backup is transferred to the device and device is restored. 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. 8. Click the "Finish" button. See also Creating a backup of a device (Page 4539) 13.5 Configuring the PG/PC interface 13.5.1 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: 4542 WinCC Basic V13.0 System Manual, 02/2014 Using online and diagnostics functions 13.5 Configuring the PG/PC interface "Online access" folder in the project tree All interfaces installed in the programming device/PC are displayed in the "Online access" folder. Show/hide interfaces Use the function "Show/hide interfaces" to show or hide individual interfaces. Status display for the interfaces The current status of an interface is indicated by an icon to the right of the name. You can see the meaning of the icon in the tooltip. Updating the list of accessible devices. This function is available for each hardware interface of the programming device/PC. Software interfaces, such as a remote connection, do not offer this function. Devices connected via the respective interface with the programming device/PC The type of the respective device and its status are displayed by the preceding icon. Displaying or updating accessible devices You have the following options if you want to display all devices accessible online on your programming device/PC: Display of the accessible devices on a single interface of the programming device / PC in the project tree. In the project tree, you can also display additional information about the individual accessible devices. Display of the accessible devices of all interfaces in a list. See also: Displaying accessible devices WinCC Basic V13.0 System Manual, 02/2014 4543 Using online and diagnostics functions 13.5 Configuring the PG/PC interface Overview of icons for accessible devices The accessible devices are identified with an icon according to their type and status. The following is an overview of all icons and their meaning. Icon for unidentified modules This icon is displayed whenever the identification of a module is not yet complete or when the identification of a module was not successful, for example, because the required online data could not be read. Icon for the following device types: PLCs SIMOCODE pro devices IE/PB links CPs of PC systems SCALANCE head modules S7-300 and S7-400 CPs PROFINET IO devices and PROFINET CPs SCALANCE modules and gateways that could not be identified PROFINET IO devices, encoders, switchgear, sensors and identification systems that were replaced by similar devices because these could not be identified Icon for the following device types: HMI devices PROFINET IO devices of the HMI type if these could not be identified and were therefore replaced by a similar device PROFINET IO devices of the drive type that could not be identified and were therefore replaced by a similar device PROFINET IO devices of the type development kit and network components that could not be identified and were therefore replaced by a similar device PROFINET IO devices of the type TeleService adapter that could not be identified and were therefore replaced by a similar device See also Displaying and modifying interface properties (Page 4545) 13.5.2 Basics of assigning parameters for the PG/PC interface Options for connecting to target systems If the devices of the project are connected via different subnets, you assign a suitable network access to each PG/PC interface to be able to establish online connections to the target systems. The following interfaces are automatically supported: MPI PROFIBUS Industrial Ethernet (ISO and TCP/IP) 4544 WinCC Basic V13.0 System Manual, 02/2014 Using online and diagnostics functions 13.5 Configuring the PG/PC interface You can make various settings for the interfaces. The following sections explain the parameter settings you can make. Note Note that changes to interface parameters have a direct influence on the operating system and the programming device / PC. Remember that some parameter settings can only be changed if you have adequate user rights. See also Setting parameters for the Industrial Ethernet interface (Page 4547) Setting parameters for the MPI and PROFIBUS interfaces (Page 4551) 13.5.3 Showing or hiding interfaces To improve clarity, it is possible to hide individual interfaces of the PG/PC in the project tree and to show them again when necessary. Procedure To show or hide individual interfaces, follow the steps below: 1. Open the "Online access" folder in the project tree. 2. Double click on the "Display/hide interfaces" icon. The "Display/hide interfaces" dialog opens. 3. Enable or disable the required interfaces in the "Display in the project tree" column. 4. Click the "Apply" button. The changes are applied. The view of the interfaces in the "Online access" folder is refreshed. 13.5.4 Displaying and modifying interface properties Introduction For each interface, you can display and, in some cases, modify properties, for example the network type, address, and status. WinCC Basic V13.0 System Manual, 02/2014 4545 Using online and diagnostics functions 13.5 Configuring the PG/PC interface Procedure To open the properties, follow these steps: 1. Right-click on the required interface below "Online access" in the project tree. 2. Select the "Properties" command from the shortcut menu. A dialog containing the properties of the interface opens. On the left of the dialog, you will see the area navigation. You can view the current parameter settings in the individual entries in the area navigation and, if necessary, change them. 13.5.5 Adding interfaces You have the option of installing additional interfaces after installation of the TIA Portal. Procedure To install an interface at a later time and add it to the TIA Portal, follow these steps: 1. Install or update the drivers in the operating system once you have installed the interface hardware. 2. Close the TIA Portal if it is still open. 3. Open the Windows control panel. 4. Open the entry "Setting the PG/PC Interface" in the Control Panel. The "Setting the PG/PC Interface" dialog opens. 5. Make any necessary changes to the interface configuration and confirm them with "OK". You have to click "OK", even if you have not made any changes. 6. Restart the TIA Portal. Result The newly installed interface is now displayed in the project tree under the "Online access" folder. 4546 WinCC Basic V13.0 System Manual, 02/2014 Using online and diagnostics functions 13.5 Configuring the PG/PC interface 13.5.6 Setting parameters for the Ethernet interface 13.5.6.1 Setting parameters for the Industrial Ethernet interface Options in the parameter settings for the Industrial Ethernet interface When setting parameters for the Industrial Ethernet interface, you have the following options: Parameters dependent on the operating system The Industrial Ethernet interface has parameters that are set in the operating system and are valid for all connected devices. These parameter settings are only displayed here, they can, however, be changed in the network settings of the operating system. Parameters that can be set in the software Note Note that changes to interface parameters have a direct influence on the operating system and the programming device / PC. Remember that some parameter settings can only be changed if you have adequate user rights. Parameters for the Industrial Ethernet interface The following table contains an overview of the parameters of the Industrial Ethernet interface that are set by the operating system and can be changed by the user. Parameter settings that cannot be changed Parameters that can be set MAC address Fast acknowledge at the IE-PG access and for TCP/IP DHCP server activated/deactivated Timeout at the IE-PG access and for TCP/IP APIPA activated/deactivated LLDP IP address Additional, dynamic IP addresses for the network adapter Subnet mask - DNS addresses - DHCP addresses - See also Basics of assigning parameters for the PG/PC interface (Page 4544) Displaying operating system parameters (Page 4548) Connecting the PG/PC interface to a subnet (Page 4548) Setting parameters for the Ethernet interface (Page 4549) Assigning a temporary IP address (Page 4550) WinCC Basic V13.0 System Manual, 02/2014 4547 Using online and diagnostics functions 13.5 Configuring the PG/PC interface Managing temporary IP addresses (Page 4550) Influence of user rights (Page 228) 13.5.6.2 Displaying operating system parameters The Ethernet interface is part of the operating system. All parameters of the network adapter can therefore be adapted in the network settings of the operating system. You can display the following parameters in the software: Physical address of the network adapter Assignment of the IP address by a DHCP server activated or deactivated Assignment of a private IP address by the operating system activated or deactivated Current static IP address Assigned subnet mask DNS addresses DHCP addresses If you want to modify the parameter settings, please refer to the documentation of the operating system or the network adapter. Displaying current parameters of the Ethernet interface To display the current parameters of the Ethernet interface, follow these steps: 1. Select the Ethernet interface in the project tree in "Online access". 2. Select the "Properties" command in the shortcut menu of the interface. The dialog for configuring the interface opens. 3. Select "Configurations > Industrial Ethernet" in the area navigation. See also Setting parameters for the Ethernet interface (Page 4549) 13.5.6.3 Connecting the PG/PC interface to a subnet If you have created several subnets, you can specify the subnet to which the Ethernet interface is connected. Procedure To select the subnet to which the Ethernet interface is connected, follow these steps: 1. Select the Ethernet interface in the project tree in "Online access". 2. Select the "Properties" command in the shortcut menu of the interface. The dialog for configuring the interface opens. 4548 WinCC Basic V13.0 System Manual, 02/2014 Using online and diagnostics functions 13.5 Configuring the PG/PC interface 3. Go to "General > Assignment" and select the subnet to which you want to connect the Ethernet interface of the programming device / PC in the "Connection to subnet" drop-down list. 4. Close the dialog with "OK". 13.5.6.4 Setting parameters for the Ethernet interface You can adapt some parameter settings relating to the network protocol directly in the software. Requirement You must have adequate user rights. See also: Influence of user rights (Page 228). Procedure To change parameter settings relating to the network protocol, follow these steps: 1. Select the Ethernet interface in the project tree in "Online access". 2. Select the "Properties" command in the shortcut menu of the interface. The dialog for configuring the interface opens. 3. Select "Configurations > IE-PG access" to adapt the protocol settings relevant to network management. - Select the "Fast acknowledge" check box to achieve faster reaction times with smaller network packets. - From the "Timeout" drop-down list, select the maximum time that can elapse before a network node is detected. 4. To activate the LLDP protocol and discover the network topology more accurately, set the "LLDP active" check box in "Configurations > LLDP". 5. Select "Configurations > TCP/IP" to adapt the TCP/IP protocol for network traffic during runtime. - Select the "Fast acknowledge" check box to achieve faster reaction times with smaller network packets. - From the "Timeout" drop-down list, select the maximum time that can elapse before there is a timeout during communication with a network node. See also Influence of user rights (Page 228) Displaying operating system parameters (Page 4548) WinCC Basic V13.0 System Manual, 02/2014 4549 Using online and diagnostics functions 13.5 Configuring the PG/PC interface 13.5.6.5 Assigning a temporary IP address Adding a dynamic IP address If the IP address of a device is located in a different subnet from the IP address of the network adapter, you will first need to assign an additional IP address with the same subnet address as the device. Only then is communication between the device and the programming device / PC possible. The assignment of an additional temporary IP address is also proposed automatically if you want to perform an online action and the current IP address of the programming device/PC is not yet in the correct subnet. A temporarily assigned IP address remains valid until the next time the programming device/ PC is restarted or until you delete it manually. Note You require adequate permissions to be able to assign a temporary IP address. See also: Influence of user rights (Page 228) See also Managing temporary IP addresses (Page 4550) 13.5.6.6 Managing temporary IP addresses If the IP address of a device is located in a different subnet from the current static IP address of the network adapter, the network adapter temporarily assigns a suitable IP address from the subnet of the device. You can display all temporarily assigned addresses and delete them. Note that IP addresses that you manually assigned in the operating system are not displayed in the TIA Portal. Requirement To delete, you require adequate permissions. Procedure To display and delete temporarily assigned addresses, follow these steps: 1. Select the Ethernet interface in the project tree in "Online access". 2. Select the "Properties" command in the shortcut menu of the interface. The dialog for configuring the interface opens. 4550 WinCC Basic V13.0 System Manual, 02/2014 Using online and diagnostics functions 13.5 Configuring the PG/PC interface 3. Select "Configurations > IE-PG access". A table with the assigned IP addresses is displayed. 4. Click the "Delete project-specific IP addresses" button to delete all the IP addresses at one time. See also Influence of user rights (Page 228) 13.5.6.7 Resetting the TCP/IP configuration If you have changed the TCP/IP protocol settings, you can reset them to the defaults. Procedure To restore the TCP/IP configuration to the default settings, follow these steps: 1. Select the Ethernet interface in the project tree in "Online access". 2. Select the "Properties" command in the shortcut menu of the interface. The dialog for configuring the interface opens. 3. Select "Configurations > TCP/IP". 4. Click the "Standard" button to reset all the settings. 13.5.7 Setting parameters for the MPI and PROFIBUS interfaces 13.5.7.1 Setting parameters for the MPI and PROFIBUS interfaces Possible parameter settings for the MPI and PROFIBUS interfaces The following parameter settings can be made for the MPI and PROFIBUS interfaces: Automatic configuration: You can use automatic detection functions to find out whether a device is connected to the PG/PC interface over PROFIBUS or MPI. Selecting a default configuration for PROFIBUS or MPI that can be adapted later. Device- and network-related settings for MPI and PROFIBUS You can set device- and network-related parameters for MPI and PROFIBUS interfaces. Device-related parameters are local settings for the interface. Network-related parameters, on the other hand, must match up on all devices. WinCC Basic V13.0 System Manual, 02/2014 4551 Using online and diagnostics functions 13.5 Configuring the PG/PC interface MPI interface parameters you can modify You can adapt the following default parameters for the MPI interface: Device-related parameters Network-related parameters Is the only master Highest address Own address Transmission rate Timeout PROFIBUS interface parameters you can modify You can adapt the following default parameters for the PROFIBUS interface: Device-related parameters Network-related parameters Is the only master Highest address Own address Transmission rate Timeout Profile Bus parameters Number of masters on bus Number of slaves on bus See also Basics of assigning parameters for the PG/PC interface (Page 4544) 13.5.7.2 Setting MPI or PROFIBUS interface parameters automatically Setting up automatic bus parameter detection If you select an interface with automatic detection of the bus parameters (for example CP 5611 (Auto)), you can connect the programming device or PC to MPI or PROFIBUS without needing to set bus parameters. At a transmission speed lower than 187.5 Kbps, you may, however, have waiting times of up to one minute. Requirement Masters that distribute bus parameters cyclically are connected to the bus. In PROFIBUS networks, the cyclic distribution of the bus parameters must be enabled. 4552 WinCC Basic V13.0 System Manual, 02/2014 Using online and diagnostics functions 13.5 Configuring the PG/PC interface Procedure To enable automatic bus parameter detection, follow these steps: 1. Select the interface in the project tree. 2. Select the "Properties" command in the shortcut menu of the interface. The dialog for configuring the interface opens. 3. Go to "General > Configurations > Active configuration" and select the setting "Automatic protocol detection". 4. Go to "Configurations > Auto configuration > Local settings" and select the address of the PG/PC interface in the "Own address" drop-down list. 5. If you then want to display the current bus settings, click the "Network detection" button. See also Setting parameters for the MPI interface (Page 4553) Setting parameters for the PROFIBUS interface (Page 4555) 13.5.7.3 Setting parameters for the MPI interface Changing the parameter settings of the MPI interface The network-related parameters and bus parameters for the MPI network can be adapted. You should first select a default setting and then adapt this to the specific situation. Setting defaults for the MPI interface To adapt the parameters of the MPI interface, follow these steps: 1. Select the interface in the project tree. 2. Select the "Properties" command in the shortcut menu of the interface. The dialog for configuring the interface opens. WinCC Basic V13.0 System Manual, 02/2014 4553 Using online and diagnostics functions 13.5 Configuring the PG/PC interface 3. Go to "General > Assignment" and select the subnet with which you want to connect the interface in the "Connection to subnet" drop-down list. 4. Under "General > Configuration", select a default for the device and network-related parameters. The defaults are suitable for most configurations. Select one of the following settings: - Automatic protocol detection You can connect the programming device to MPI or PROFIBUS without having to set bus parameters. At a transmission speed lower than 187.5 Kbps, you may, however, have waiting times of up to one minute. Prerequisite for the automatic detection is a connection to the bus master, which distributes the bus parameters cyclically. With PROFIBUS subnets, cyclic distribution of bus parameters may not be deactivated (default PROFIBUS network setting). - MPI The "MPI" transmission protocol is selected. Typical parameters are set that are adequate for most configurations. You can change the parameters to your needs, however. - PROFIBUS The "PROFIBUS" transmission protocol is selected. Typical parameters are set that are adequate for most configurations. You can change the parameters to your needs, however. Changing the default parameter settings To adapt the default settings to your requirements, change the parameter setting where necessary in "Configurations > MPI". You can set the following device-related parameters: Is only master An additional verification function to prevent bus disruptions when connecting the PG/PC to the network is disabled because the programming device or PC is the only master on the bus. - Do not enable this option unless you have only connected slaves to your programming device or PC. - If the "Is only master" check box is enabled, it is not possible to identify the directly connected device in the "Accessible devices" window. Own address This setting relates to the programming device or PC on which you call up the parameter settings of the interface. Set the local device address of your programming device or PC here. - This address must be unique throughout the network. - The programming device or PC is addressed using this address in the MPI network. 4554 WinCC Basic V13.0 System Manual, 02/2014 Using online and diagnostics functions 13.5 Configuring the PG/PC interface Check This enables an additional safety function to prevent bus disruptions when connecting the PG/PC to the network. The driver checks whether the local address is already being used by another station. Active as well as passive stations are taken into consideration in this case. The driver monitors this on the PROFIBUS. The connection of the PG/PC to the network will take longer with the automatic check. To use the check, the driver must support the function. Furthermore, the "Is only master" option must not be selected. Timeout Set a higher timeout value if, for example, you have problems with long response times on the network. You can set the following network-related parameters: Highest address: Select the configured highest device address. Make sure that the same highest device address is set for all devices of a PROFIBUS or MPI network. Transfer rate: Here, you select the transmission speed to be used on the MPI network. See also Setting MPI or PROFIBUS interface parameters automatically (Page 4552) 13.5.7.4 Setting parameters for the PROFIBUS interface Changing the parameter settings of the PROFIBUS interface The network-related parameters and bus parameters for the PROFIBUS network can be adapted more precisely. You should first select a default setting and then adapt this to the specific situation. Setting defaults for the PROFIBUS interface To adapt the parameters of the PROFIBUS interface, follow these steps: 1. Select the interface in the project tree. 2. Select the "Properties" command in the shortcut menu of the interface. The dialog for configuring the interface opens. WinCC Basic V13.0 System Manual, 02/2014 4555 Using online and diagnostics functions 13.5 Configuring the PG/PC interface 3. Go to "General > Assignment" and select the subnet with which you want to connect the interface in the "Connection to subnet" drop-down list. 4. Under "General > Configuration", select a default for the device and network-related parameters. The defaults are suitable for most configurations. Select one of the following settings: - Automatic protocol detection You can connect the programming device to MPI or PROFIBUS without having to set bus parameters. At a transmission speed lower than 187.5 Kbps, you may, however, have waiting times of up to one minute. Prerequisite for the automatic detection is a connection to the bus master, which distributes the bus parameters cyclically. With PROFIBUS subnets, cyclic distribution of bus parameters may not be deactivated (default PROFIBUS network setting). - MPI The "MPI" transmission protocol is selected. Typical parameters are set that are adequate for most configurations. You can change the parameters to your needs, however. - PROFIBUS The "PROFIBUS" transmission protocol is selected. Typical parameters are set that are adequate for most configurations. You can change the parameters to your needs, however. Changing the default parameter settings To adapt the default settings to your requirements, change the parameter setting where necessary in "Configurations > PROFIBUS". You can set the following device-related parameters: Is only master An additional verification function to prevent bus disruptions when connecting the PG/PC to the network is disabled because the programming device or PC is the only master on the bus. - Do not enable this option unless you have only connected slaves to your programming device or PC. - If the "Is only master" check box is enabled, it is not possible to identify the directly connected device in the "Accessible devices" window. Own address This setting relates to the programming device or PC on which you call up the parameter settings of the interface. Set the local device address of your programming device or PC here. - This address must be unique throughout the network. - The programming device or PC is addressed using this address in the PROFIBUS network. 4556 WinCC Basic V13.0 System Manual, 02/2014 Using online and diagnostics functions 13.5 Configuring the PG/PC interface Check This enables an additional safety function to prevent bus disruptions when connecting the PG/PC to the network. The driver checks whether the local address is already being used by another station. Active as well as passive stations are taken into consideration in this case. The driver monitors this on the PROFIBUS. The connection of the PG/PC to the network will take longer with the automatic check. To use the check, the driver must support the function. Furthermore, the "Is only master" option must not be selected. Timeout Set a higher timeout value if, for example, you have problems with long response times on the network. You can set the following network-related parameters: Highest address: Select the configured highest device address. Make sure that the same highest station address is set for all devices of a PROFIBUS network. Transfer rate: Here, you select the transmission speed to be used on the PROFIBUS network. Profile: You have a choice of four alternatives for the PROFIBUS settings. "DP", "Standard" and "Universal (DP/FMS)" are predefined settings that you cannot change. If you select "Userdefined", you can adapt the bus parameters yourself. - If you have selected "User-defined", go to "Configurations > PROFIBUS > Bus parameters" in area navigation. - If you have selected one of the defaults (DP, Standard or Universal (DP/FMS)), you should select the "Include" check box in "Configurations > PROFIBUS > Bus parameters > Additional parameters". You can then set the number of masters and slaves on the bus. This allows a more precise calculation of the bus parameters and potential bus disruptions can be prevented. The option cannot be selected with a user-defined profile. See also Overview of the bus parameters for PROFIBUS (Page 4557) Setting MPI or PROFIBUS interface parameters automatically (Page 4552) 13.5.7.5 Overview of the bus parameters for PROFIBUS Introduction The PROFIBUS subnet will only function problem-free 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. It may be possible for the bus parameters to be adjusted depending on the bus profile. The offline values of the bus parameters are always shown even if you are online and linked to the target system. The displayed parameters are valid for the entire PROFIBUS subnet. WinCC Basic V13.0 System Manual, 02/2014 4557 Using online and diagnostics functions 13.5 Configuring the PG/PC interface Meaning of the individual parameters Tslot: Wait-to-receive time (slot time) The wait-to-receive time (slot time) defines the maximum time the sender will wait to receive a response from the addressed partner. Max. Tsdr: Maximum protocol processing time (max. station delay responder) The maximum protocol processing time defines the time after which the responding device must have processed the protocol. Min. Tsdr: Minimum protocol processing time (min. station delay responder) The minimum protocol processing time specifies the minimum time required by the responding device to process the protocol. Tset: Trigger time (setup time) The trigger time is the time that may lapse between the reception of a data frame frame and the reaction to it. Tqui: Quiet time for modulator The quiet time for modulator specifies the time required to change from sending to receiving. GAP factor: GAP update factor (GAP factor) The GAP factor specifies the number of token rotations before a new device is included in the token ring. Retry limit: Maximum number of repeated call attempts (retry limit) This parameter defines the maximum number of attempts made to reach a device. Trdy: Ready time The ready time is the time for an acknowledgment or response. Tid1: Idle time 1 Idle time 1 specifies the delay time after receiving a response. Tid2: Idle time 2 Idle time 2 specifies the delay time after sending a call without a response. Ttr: Target rotation time The target rotation time is the maximum time made available for a token rotation. During this time, all active devices (masters) receive the token once. The difference between the desired token round-trip time and the actual token round-trip time decides how much time is left for masters to send data frames to the slaves. As the minimum target rotation time (Ttr), select a value = 5000 times the HSA (Highest Station Address). Watchdog: Watchdog The watchdog time specifies the time after which a device must be addressed. As the minimum watchdog time, select a value = 6250 times the HSA. Note If you want to create a user-defined bus profile, please note that the minimum target rotation time (Ttr) should be 5000 times the HSA (highest PROFIBUS address). The minimum watchdog time should also be 6250 times the HSA. 4558 WinCC Basic V13.0 System Manual, 02/2014 Using online and diagnostics functions 13.6 Using the trace and logic analyzer function See also Setting parameters for the PROFIBUS interface (Page 4555) 13.5.7.6 Resetting the MPI or PROFIBUS configuration If you have changed the MPI or PROFIBUS protocol settings, you can reset them to the defaults. Procedure To restore the MPI or PROFIBUS configuration to the default settings, follow these steps: 1. Select the MPI/PROFIBUS interface in the project tree in "Online access". 2. Select the "Properties" command in the shortcut menu of the interface. The dialog for configuring the interface opens. 3. Select "Configurations > MPI" or "Configurations > PROFIBUS", depending on the interface properties you want to reset. 4. Click the "Standard" button to reset all the settings. 13.6 Using the trace and logic analyzer function Preface Purpose of the documentation The diagnostics options available with the trace and logic analyzer function are described in this documentation. Depending on the device used, the recording options can vary. Required basic knowledge In order to understand this documentation, the following knowledge is required: General knowledge in the field of automation Knowledge about the use of Windows-based computers S7-1200/1500 CPUs - Knowledge of working with the SIMATIC industrial automation system - Knowledge of working with TIA Portal >= V12.0 SINAMICS G120 - Knowledge of working with the drive WinCC Basic V13.0 System Manual, 02/2014 4559 Using online and diagnostics functions 13.6 Using the trace and logic analyzer function Validity of the documentation This documentation applies to all products of the S7-1200, S7-1500 and SINAMICS G120 product family. Conventions This documentation contains pictures of the devices described. The pictures may differ slightly from the devices supplied. Please also observe notes marked as follows: Note A note contains important information on the product described in the documentation, on the handling of the product and on the section of the documentation to which particular attention should be paid. Further support The range of technical documentation for the individual SIMATIC products and systems is available on the Internet (http://www.siemens.com/simatic-tech-doku-portal). The online catalog and the online ordering system is available on the Internet (http:// mall.automation.siemens.com). 13.6.1 Security information Siemens provides products and solutions with industrial security functions that support the secure operation of plants, solutions, machines, equipment and/or networks. They are important components in a holistic industrial security concept. With this in mind, Siemens' products and solutions undergo continuous development. Siemens recommends strongly that you regularly check for product updates. For the secure operation of Siemens products and solutions, it is necessary to take suitable preventive action (e.g. cell protection concept) and integrate each component into a holistic, state-of-the-art industrial security concept. Third-party products that may be in use should also be considered. You can find more information about industrial security on the Internet (http:// www.siemens.com/industrialsecurity). To stay informed about product updates as they occur, sign up for a product-specific newsletter. You can find more information on the Internet (http:// support.automation.siemens.com). 4560 WinCC Basic V13.0 System Manual, 02/2014 Using online and diagnostics functions 13.6 Using the trace and logic analyzer function 13.6.1 Description 13.6.1.1 Supported hardware The following devices (Page 4586) support the trace and logic analyzer function: SIMATIC S7-1200 CPUs (as of firmware version V4.0) SIMATIC S7-1500 CPUs SINAMICS G120 13.6.1.2 Recording of measured values with the trace function Introduction The trace and logic analyzer function can be called in the device folder in the project navigator under the name "Traces" (Page 4564). You record device tags and evaluate the recordings with the trace and logic analyzer function. Tags are, for example, drive parameters or system and user tags of a CPU. The maximum recording duration is limited by the memory size. How much memory is available for the recording depends on the hardware used. The recordings are saved on the device and, when required, can be read out with the engineering system (ES) and saved permanently. The trace and logic analyzer function is therefore suitable for monitoring highly dynamic processes. The recorded values are overwritten when "Installed traces" is activated again. Active recordings from the axis control panel or from the PID are displayed at "Installed traces". These recordings can be added to the measurements in the curve diagram of the axis control panel or the PID via a shortcut menu command. Depending on the device (Page 4586) used, the recording options can vary. A quick start (Page 4574) for working with the trace and logic analyzer function can be found in the Operation section. The following figure shows the method of operation of the "Traces": WinCC Basic V13.0 System Manual, 02/2014 4561 Using online and diagnostics functions 13.6 Using the trace and logic analyzer function 7UDFHFRQILJXUDWLRQ /RDGWUDFH FRQILJXUDWLRQWRWKH GHYLFH :DLWIRUWULJJHU FRQGLWLRQDQG UHFRUGGDWD 7UDQVIHUPHDVXUH PHQWWRWKH3* 'LVSOD\PDQDJH DQGVDYHPHDVXUH PHQW Trace configuration on the programming device (PG) in the TIA Portal You can specify the signals to be recorded, the duration of the recording and the trigger condition in the trace configuration. The trace configuration depends on the device and is described at the respective device (Page 4586). Transferring the trace configuration from the PG to the device You can transfer the complete trace configuration (Page 4581) to the device when an online connection is established. Waiting for the recording If the installed trace configuration is activated (Page 4581), then the recording is performed independently of the PG. The recording is started as soon as the trigger condition is satisfied. Transferring the measurement from the device to the PG The saving of the measurement in the project (Page 4583) stores the measurement in the opened project of the TIA Portal. The measurement can be saved at any time after completing the recording, irrespective of the time of the measurement. Evaluating, managing and saving the measurement Numerous options are available for the evaluation of the measurement in the curve diagram and in the signal table (Page 4582). Various display types are possible, for example, a bit representation for binary signals. Measurements can also be exported and imported as a file. With the saving of the project (Page 4583) in the TIA Portal, the measurements transferred to the project are also saved. 13.6.1.3 Trace configuration, recording and measurement This section explains the meaning of the terms: trace configuration, recording and measurement. 4562 WinCC Basic V13.0 System Manual, 02/2014 Using online and diagnostics functions 13.6 Using the trace and logic analyzer function Trace configuration You can make the following settings in the trace configuration : Signals to be recorded Recording conditions - Sampling - Trigger Recording A recording is performed in the device. There is only one recording for each installed trace configuration. When a new recording is started, the old recording is overwritten. An installed recording is not retentive (it is lost when the device is switched off/on) and can be saved permanently in the project as a measurement. Installed traces An installed trace consists of a trace configuration and optionally a recording. The maximum number of installed traces depends on the device. The status of an installed trace can be viewed online. Measurement A measurement always consists of a trace configuration with an associated recording. If an installed trace contains a recording, it can be saved in the project as a measurement. The recording of a measurement can be viewed offline. 13.6.1.4 Data storage The trace handling and the curve diagram also enable the transfer of the trace configuration and the viewing of the recording. The following figure is a schematic diagram of the data storage: WinCC Basic V13.0 System Manual, 02/2014 4563 Using online and diagnostics functions 13.6 Using the trace and logic analyzer function &XUYHGLDJUDP 7UDFHFRQILJXUDWLRQ ,QVWDOOHGWUDFHV 0HDVXUHPHQW ,PSRUW ([SRUW 'HYLFHUHWHQWLYH ,PSRUW ([SRUW 3URMHFW 'HYLFHQRQUHWHQWLYH 3URMHFW Note Saving the trace configuration and measurement You save the trace configuration and measurement with the project in the TIA Portal. If you close the project without saving, the trace configurations and the measurements transferred to the project are discarded. The trace editor can be closed and reopened without loss of data until the project is closed. 13.6.2 Software user interface Display areas The user interface of the trace and logic analyzer function consists of several areas. The example in the figure below shows the division of the user interface in the TIA Portal: 4564 WinCC Basic V13.0 System Manual, 02/2014 Using online and diagnostics functions 13.6 Using the trace and logic analyzer function D E 1 Project navigator Working area 2 Title bar of the working area Shows the device to which the current display belongs. 3a Toolbar of the trace handling (Page 4570) Selection of recordings for display in the curve diagram and buttons for activation/ deactivation of installed traces. 4 Toolbar of the curve diagram (Page 4566) Tools for editing the measurement and for adapting the display in the curve diagram. 5 Curve diagram (Page 4566) Display of the recorded values. 6 Signal table (Page 4568) Signals of the shown measurement. WinCC Basic V13.0 System Manual, 02/2014 4565 Using online and diagnostics functions 13.6 Using the trace and logic analyzer function 3b Trace handling (Page 4570) Creation of new trace configurations and the handling of the measurements. Device-specific area (see Devices (Page 4586)) 7 Properties area in the Inspector window Configuration dialog boxes for the recording duration, trigger condition and signal selection. 13.6.2.1 Project navigator If a device supports the trace and logic analyzer function, in the project navigator below the device. Double-clicking 13.6.2.2 "Traces" is offered for selection "Traces" opens the trace editor. Working area User interface - curve diagram The curve diagram displays the selected signals of a recording. Bits are shown in the lower diagram as a bit track. You can adjust the display of the signals in the signal table (Page 4568) and with the aid of the toolbar of the curve diagram. Setting options and displays in the curve diagram The following figure shows an example of the display in the TIA Portal: The scale in the diagram applies to the selected (highlighted in gray) signal in the legend. The legend can be moved laterally with the mouse. 4566 WinCC Basic V13.0 System Manual, 02/2014 Using online and diagnostics functions 13.6 Using the trace and logic analyzer function Shortcut menu commands The following table shows the shortcut menu commands in the curve diagram: Shortcut menu command Description "Save diagram as image" Exports the current display as a bitmap. "Copy image to clipboard" Copies the current display to the clipboard. "Center measurement cursors" Positions the activated measurement cursors at a central point in the current display. "Add to measurements" Adds the shown recording to the "Measurements" table. (only axis control panel and PID) Toolbar of the curve diagram Tools are available for adapting the display via buttons. The following table shows the functions of the buttons: Icon Function Description Undo zoom Undoes the zoom function executed last. If several zoom functions have been executed, they can be undone step-by-step. Redo zoom Redoes the last undone zoom function. If several zoom functions have been undone, they can be redone stepby-step. Standard view Uses the current view as standard for this recording. If the trace recording is shown again later, the standard view is restored. Move view Moves the display with the mouse button pressed. Zoom selection Selection of an arbitrary range with the mouse button pressed. The display is scaled to the range selection. Vertical zoom selection Selection of a vertical range with the mouse button pressed. The display is scaled to the range selection. Horizontal zoom selection Selection of a horizontal range with the mouse button pressed. The display is scaled to the range selection. Display all Scales the display of the available data so that the entire time range and all values are displayed. Note The dynamic progress indicator of a running trace is stopped when a zoom function is activated. This button activates the progress indicator again. WinCC Basic V13.0 System Manual, 02/2014 Zoom in Enlargement of the display. The ranges of the time axis and value axis are reduced every time the button is clicked. The curves are displayed larger. Zoom out Reduction of the display. The ranges of the time axis and value axis are increased every time the button is clicked. The curves are displayed smaller. Scale automatically Scaling of the display so that all values are displayed for the currently displayed time range. 4567 Using online and diagnostics functions 13.6 Using the trace and logic analyzer function Icon Function Description Arrange in tracks Arranges signals one beneath the other without overlaps. Unit changeover of the time axis Changeover of the unit between time and cycles. Display samples The samples are displayed as small circles on the curves. Display vertical measurement cursors Display of the vertical measurement cursors. The vertical position of the two measurement cursors can be moved with the mouse. The associated measured values and the difference of the measurement cursors corresponding to the position are shown in the signal table. Display horizontal measurement cursors Display of the horizontal measurement cursors. Display chart legend The horizontal position of the two measurement cursors can be moved with the mouse. Display or hiding of the chart legend in the curve diagram. Align the chart legend to the left Display of the chart legend on the left side of the curve diagram. Align the chart legend to the right Display of the chart legend on the right side of the curve diagram. Change background color Changeover between various background colors. User interface - signal table The signal table lists the signals of the selected measurement and provides setting options for some properties. If recording data of "Installed traces" is displayed and the settings are changed in the signal table, these settings are retained until there is a change to the offline mode. If the "Installed trace" is added to the measurements, the current settings of the signal table are saved in the measurement. The signals can be sorted using drag-and-drop. The bits of a signal can be resorted within a signal. Setting options and displays in the signal table The following figure shows an example of the display in the TIA Portal: The following table shows the settings and displays of the recorded signals: 4568 WinCC Basic V13.0 System Manual, 02/2014 Using online and diagnostics functions 13.6 Using the trace and logic analyzer function Column Description Static display of the signal icon Selection for the display in the curve diagram The point indicates that at least one bit has been selected for display as bit track for the signal in the bit selection. "Name" Display of the signal name A click on the name of a displayed signal updates the scale in the curve diagram. Open bit selection Individual bits can also be selected for the following data types for display as a bit track in the lower curve diagram. Byte, Word, DWord, LWord SInt, USInt, Int, UInt, DInt, UDInt, LInt, ULInt Example of an opened bit selection for the DWORD data type: Select or deselect the relevant bit for display by clicking the icon. "Data type" Display of the data type "Address" Display of the address (not for symbolic tags) "Color" Display and setting option for the color of the signal "Min. Y-scale" Display or input of the minimum value for the scaling of the signal "Max. Y-scale" Display or input of the maximum value for the scaling of the signal "Signal group" Display or input of the signal group name for one signal group The Y-scales are scaled identically for all signals of one signal group. Enter an identical signal group name for those signals that are to be scaled identically. Signals can be removed from the signal group by deleting the signal group name. The signal groups can be saved via the function "Use current view as standard" (button ). "Y(t1)" Display of the value at the position of the first measurement cursor "Y(t2)" Display of the value at the position of the second measurement cursor "Y" Display of the value difference between the first and the second measurement cursor "Unit" Display of the unit (e.g. for technology objects) "Comment" Display and input option for a comment about the signal Shortcut menu commands The following table shows the shortcut menu commands of the signal table: WinCC Basic V13.0 System Manual, 02/2014 Shortcut menu command Description "Cut" Cannot be selected. "Copy" Copies the contents of the selected lines to the clipboard. 4569 Using online and diagnostics functions 13.6 Using the trace and logic analyzer function Shortcut menu command Description "Paste" Cannot be selected. "Show/hide signal" Shows/hides the signal in the curve diagram. "Bring to foreground" Displays the selected signal in the foreground. The other signals are hidden. User interface - trace management The trace handling enables the configuration and handling of trace configurations. Setting options and displays in the trace handling The following figure shows an example of the display in the TIA Portal: Trace configuration Recording (recorded values) Toolbar of the trace handling A recording can be selected for display via a drop-down list and buttons, and activated or deactivated. The example in the figure below shows the toolbar of the trace handling The following table describes the functions of the buttons: Icon Description Static icon display of the drop-down list selection in the curve diagram Selection of an "Installed trace" or a "Measurement" for display in the curve diagram Activation of the recording The button is available for "Installed traces". Deactivation of the recording The button is available for "Installed traces". 4570 WinCC Basic V13.0 System Manual, 02/2014 Using online and diagnostics functions 13.6 Using the trace and logic analyzer function "Trace configurations" table The table contains all the trace configurations of the project that can be transferred to the device. Each trace configuration contains the tags to be recorded and the required recording settings. The data is displayed in offline and online mode. The following table shows the settings and displays: Column Icon - Description Display of the icon for the trace configuration Incorrect trace configurations are shown with a red border and cannot be transferred to the device. Check the configuration in the Inspector window. Double-clicking the icon brings the Inspector window with the properties to the foreground. "Trace configuration" - Name of the trace configuration. The name can be changed after double-clicking the field. "Comment" - Input field for a comment. Shortcut menu commands The following table shows the shortcut menu commands of the "Trace configurations" table when a line is selected: Shortcut menu command Description "Cut" Cannot be selected. "Copy" Copies the contents of the selected lines to the clipboard. "Paste" Pastes the contents of the clipboard. "Delete" Deletes the selected lines from the table or deletes the name of the selected cell. "Rename" Switches the selected cell to the editing mode. "Transfer trace configuration to device" Transfers the trace configuration selected in the "Trace configurations" table to the device. The button is active when all the required settings in the devicespecific configuration have been configured correctly in the Inspector window and there is an online connection. "Export trace configuration" Exports a trace configuration as a file with the "*.ttcfgx" file extension. For compatibility reasons, the "*.ttcfg" file extension will be supported in V12, but does not contain any information about the device family. "Import trace configuration" Imports a trace configuration from a file. "Properties" Brings the Inspector window with the device-specific properties to the foreground. "Installed traces" table The table contains the trace configurations already transferred to the device and their current status. The data is displayed in the online mode. The following table shows the settings and displays: WinCC Basic V13.0 System Manual, 02/2014 4571 Using online and diagnostics functions 13.6 Using the trace and logic analyzer function Column Icon - Description Static display of the online icon Double-clicking the icon brings the Inspector window with the devicespecific properties to the foreground. Selection for the display in the curve diagram A click on the icon shows/hides the recording in the curve diagram. "Installed traces" - "Active" Name of the trace configuration. Activation of the recording and feedback of the status. The checkbox is reset at the end of the recording. If the recording of an installed trace is repeated, then the settings relevant for the display (curve diagram and signal table) are also retained for the new recording. "Status" - Status display of the trace configuration The following states are possible: "Installing" "Waiting for trigger" "Recording" "Recording completed" "Aborted" "Fault" "Comment" - Display of the trace configuration comment Shortcut menu commands The following table shows the shortcut menu commands of the "Installed traces" table when a line is selected: Shortcut menu command Description "Cut" Cannot be selected. "Copy" Copies the contents of the selected lines to the clipboard. "Paste" Cannot be selected. "Delete" Deletes the selected lines from the table. "Rename" Cannot be selected. "Add to trace configurations" Transfers the installed trace configuration to the "Trace configurations" table. "Add to measurements" Adds the selected "Installed trace" to the "Measurements" table. Note The "Installed trace" data can be saved as a measurement after being displayed once in the curve diagram. The recording data is loaded from the device for the display. 4572 "Activate" Activates the recording and shows the status in the table "Show/hide in curve diagram" Shows/hides the recording in the curve diagram. "Properties" Brings the Inspector window with the device-specific properties to the foreground. WinCC Basic V13.0 System Manual, 02/2014 Using online and diagnostics functions 13.6 Using the trace and logic analyzer function "Measurements" table The table contains the trace configurations with recordings. The data is displayed in offline and online mode. Measurements can also be exported and imported, see Exporting and importing measurements (Page 4583). The following table shows the settings and displays: Column Icon - Description Static display of the icon for a measurement Double-clicking the icon brings the Inspector window with the devicespecific properties to the foreground. Selection for the display in the curve diagram A click on the icon shows/hides the recording in the curve diagram. "Measurements" - "Trigger time" - Name of the measurement The name can be changed after double-clicking the field. The meaning of the time stamp depends on the device Examples: SIMATIC S7-1200/1500 CPUs The absolute time of the controller is entered at the start of the recording. SINAMICS G120 The transfer time is entered with the transfer of the trace configuration to the device. "Comment" - Input field for a comment. Shortcut menu commands The following table shows the shortcut menu commands of the "Measurements" table when a line is selected: Shortcut menu command Description "Cut" Cannot be selected. "Copy" Copies the contents of the selected lines to the clipboard. "Paste" Pastes the contents of the clipboard. "Delete" Deletes the selected lines from the table or deletes the name of the selected cell. "Rename" Switches the selected cell to the editing mode. "Add to trace configurations" Transfers the trace configuration of the measurement to the "Trace configurations" table. "Show/hide in curve diagram" Shows/hides the recording in the curve diagram. "Export measurement" Exports a measurement as a file with the "*.ttrecx" or "*.csv" file extension. For compatibility reasons, the "*.ttrec" file extension will be supported in V12, but does not contain any information about the device family. WinCC Basic V13.0 System Manual, 02/2014 4573 Using online and diagnostics functions 13.6 Using the trace and logic analyzer function Shortcut menu command Description "Import measurement" Imports a measurement from a file with the "*.ttrecx" file extension. For compatibility reasons, the "*.ttrec" file extension will be supported in V12, but does not contain any information about the device family. "Properties" Brings the Inspector window with the device-specific properties to the foreground. Buttons The following table shows the functions available via buttons: Icon Description Button to transfer a selected trace configuration to the device The selected trace configuration in the "Trace configurations" table is transferred to the device. The button is active when all the required settings in the configuration have been correctly configured in the Inspector window and there is an online connection. Button to transfer a selected trace configuration from the device The trace configuration selected in the "Installed traces" table is transferred from the device to the "Trace configurations" table. Button to transfer a selected measurement from the device to the project The selection in the "Installed traces" table is added to the "Measurements" table. Note for S7 CPUs In order to be able to save the "Installed trace" data as a measurement, it must first have been displayed once in the curve diagram. The recording data is loaded from the device when displayed. 13.6.2.3 Device-specific area The device-specific area enables the trace configuration. The signals to be recorded and the trigger condition are specified here. These and other configuration options are described in the device-specific part (Page 4586) for the individual devices. 13.6.3 Operation 13.6.3.1 Quick start This description shows the steps for a recording of the S7-1500 CPU as an example. The displayed settings can differ depending on the device. Requirement A device is configured that supports the trace and logic analyzer function. 4574 WinCC Basic V13.0 System Manual, 02/2014 Using online and diagnostics functions 13.6 Using the trace and logic analyzer function Calling the trace editor The following figure shows the project navigator with "Traces" below the device: Procedure: 1. Open the trace editor by double-clicking the "Traces" entry. Creating a trace configuration The following figure shows the "Trace configurations" table: Procedure: WinCC Basic V13.0 System Manual, 02/2014 4575 Using online and diagnostics functions 13.6 Using the trace and logic analyzer function 1. Enter the name of the trace configuration in the "Trace configurations" table. Selecting signals The following figure shows the configuration of the signals: Procedure: 1. Select the signals to be recorded in the "Signals" area of the Inspector window. Or: 1. Drag a signal to the table using drag-and-drop. Configuring the recording cycle The following figure shows the configuration of the sampling: Procedure: 4576 WinCC Basic V13.0 System Manual, 02/2014 Using online and diagnostics functions 13.6 Using the trace and logic analyzer function 1. Configure the sampling. Configuring the trigger The following figure shows the configuration of the trigger: Procedure: 1. Configure the trigger mode and the condition for the selected trigger. Transferring the trace configuration to the device The following figure shows the trace handling in online mode: Procedure: 1. Check whether the configuration is correct based on the icon in the "Trace configurations" table. The icon indicates a correct trace configuration. The icon indicates a faulty trace configuration. Only correct trace configurations can be transferred to the device. 2. Establish an online connection to the device. 3. Select the trace configuration in the "Trace configurations" table and transfer it to the device with the button. WinCC Basic V13.0 System Manual, 02/2014 4577 Using online and diagnostics functions 13.6 Using the trace and logic analyzer function Activating a recording The following figure shows the trace handling with an installed trace configuration: Procedure: 1. Click the checkbox in the "Active" column in the "Installed traces" table. Displaying the recording The following figure shows the curve diagram with the recording of the "Installed trace": Procedure: 4578 WinCC Basic V13.0 System Manual, 02/2014 Using online and diagnostics functions 13.6 Using the trace and logic analyzer function 1. Wait until the "Recording" or "Recording completed" status is displayed in the "Installed traces" table. 2. Click the icon in the "Installed traces" table to display the recording in the curve diagram. 3. Click the icon of a signal in the signal table. The individual bits of the signal are offered for display as a bit track. 4. In the signal table, select or deselect the individual signals and bits for display with the icon. Saving the measurement in the project The following figure shows the measurement saved in the project: Procedure: 1. Select the measurement in the "Installed traces" table and transfer it to the project with the button. 13.6.3.2 Using the trace function - overview Requirement A device is configured in the TIA Portal that supports the trace and logic analyzer function and to which an online connection has been established. Procedure The following table shows a procedural overview with typical steps when working with the trace and logic analyzer function. WinCC Basic V13.0 System Manual, 02/2014 Step Description 1 Calling the trace editor (Page 4580) 2 Configuring the trace (Page 4580) 3 Transferring the trace configuration to the device (Page 4581) 4 Activating/deactivating an installed trace (Page 4581) 5 Monitoring the recording (Page 4582) 6 Saving measurements in the project (Page 4583) 7 Displaying the recording (Page 4582) 4579 Using online and diagnostics functions 13.6 Using the trace and logic analyzer function 13.6.3.3 Calling the trace editor A trace editor can be opened for each device in the project navigator. The following instructions describe how you call the trace editor in the work area of the TIA Portal. Requirement A device is configured that supports the trace and logic analyzer function. Procedure To call the trace editor, proceed as follows: 1. In the project navigator, double-click the device. The device folder opens. 2. Double-click "Traces". 13.6.3.4 Trace handling Configuring the trace Requirement The trace editor is open. Creating and deleting the trace configuration To create a new trace configuration, proceed as follows: 1. Click the "<Add>" entry in the "Trace configurations" table in the Trace handling (Page 4570). 2. Enter the name for the trace configuration. The new trace configuration is created. To delete a trace configuration, proceed as follows: 1. Right-click a trace configuration in the "Trace configurations" table and select the shortcut menu command "Delete". The trace configuration is deleted. Configuring the trace In the configuration, you specify the recording and trigger conditions and select the signals to be recorded. 4580 WinCC Basic V13.0 System Manual, 02/2014 Using online and diagnostics functions 13.6 Using the trace and logic analyzer function See Section "Configuration" below the respective device (Page 4586). Note Saving the trace configuration You save the trace configuration with the project in the TIA Portal. If you close the project without saving, the configuration is discarded. The trace editor can be closed and reopened without loss of data until the project is closed. Transferring the trace configuration to the device Requirement A valid trace configuration is located in the "Trace configurations" table. The maximum number of "Installed traces" has not been reached yet. There is an online connection to the device. Procedure To transfer a trace configuration to the device, proceed as follows: 1. Select a trace configuration 2. Click the in the "Trace configurations" table. button to transfer the trace configuration to the device. Result The trace configuration is transferred to the device and displayed in the "Installed traces" table. Activating/deactivating an installed trace Requirement A trace configuration is installed and there is an online connection to the device. WinCC Basic V13.0 System Manual, 02/2014 4581 Using online and diagnostics functions 13.6 Using the trace and logic analyzer function Activating an installed trace To activate the recording for an installed trace, proceed as follows: 1. Activate the checkbox of the "Active" column in the "Installed traces" table. The installed trace is activated and starts the recording according to the configured trigger condition. The trigger condition is device-specific and described in Section "Configuration" below the respective device (Page 4586). Note When a recording is restarted, the previously recorded values are lost. To save the recorded values, save the measurement in the project (Page 4583) before you activate the recording again. Deactivating an installed trace To deactivate an activated installed trace, proceed as follows: 1. Deactivate the checkbox of the "Active" column in the "Installed traces" table. The installed trace is deactivated. Displaying the recording Requirement A trace configuration with recording is in the device and there is an online connection to the device or there is an entry in the "Measurements" table. Procedure To display the recording, proceed as follows: 1. Select an entry in the "Installed traces" table. 2. Click in the column for the selected entry. Or: 1. Select an entry in the "Measurements" table. 2. Click in the column for the selected entry. Result The recording is displayed in the curve diagram and the signal table. 4582 WinCC Basic V13.0 System Manual, 02/2014 Using online and diagnostics functions 13.6 Using the trace and logic analyzer function Saving measurements in the project Requirement A trace configuration with recording is installed and there is an online connection to the device. The "Installed trace" data must have been displayed at least once in the curve diagram. The recording data is loaded from the device for the display. Procedure To save a recording in the project, proceed as follows: 1. Click an entry in the "Installed traces" table in the trace handling. 2. Click the button to transfer the selected entry. The selected entry in the "Installed traces" table is added to the "Measurements" table. 3. Save the project in the TIA Portal. Exporting and importing measurements Requirement There is at least one measurement in the "Measurements" table. Exporting measurements To export a measurement, proceed as follows: 1. Right-click an entry in the "Measurements" table and select the shortcut menu command "Export measurement". 2. Select a folder, a file name and a data type to save the measurement. 3. Click the "Save" button. Importing measurements To import a measurement, proceed as follows: 1. Right-click in the "Measurements" table and select the shortcut menu command "Import measurement". 2. Select the file of the "*.ttrecx" file type with the measurement to be imported. 3. Click the "Open" button. The imported measurement is displayed with the file name in the "Measurements" table. WinCC Basic V13.0 System Manual, 02/2014 4583 Using online and diagnostics functions 13.6 Using the trace and logic analyzer function Transferring the trace configuration from the device to the project Requirement A trace configuration is installed and there is an online connection to the device. Procedure To transfer a trace configuration to the project, proceed as follows: 1. Select an entry in the "Installed traces" table. 2. Click the button to transfer the trace configuration from the device. Result The configuration of the "installed trace" is transferred to the "Trace configurations" table. Deleting installed traces Requirement A trace is installed and there is an online connection to the device. Deleting an installed trace To delete an installed trace, proceed as follows: 1. Select one or more lines to be deleted in the "Installed traces" table. 2. Press <Del> to delete the "Installed traces". 13.6.3.5 Signal table Use of the signal table The signal table shows the signals of an installed trace or a measurement. You can show or hide individual signals for the display in the table and adapt the properties for the display. Individual bits can be selected for some data types and displayed as a bit track. The following operating instructions describe the operation of the signal table. Requirement An entry is selected in the column in the "Installed traces" or "Measurements" table. For the display of individual bits as a bit track: At least one recorded signal supports the display as a bit track. 4584 WinCC Basic V13.0 System Manual, 02/2014 Using online and diagnostics functions 13.6 Using the trace and logic analyzer function Selecting individual signals in the signal table and changing the format To adapt the display to suit your requirements, proceed as follows: 1. Click the icon of the respective signal in the column to select or deselect it for the display. 2. Click in the "Color" column for the respective signal to change the default color of the signal. 3. Click the "Bring to foreground" entry in the shortcut menu of a signal to display it in the foreground. Selecting individual bits in the signal table for display as a bit track To display individual bits as a bit track in the lower curve diagram, proceed as follows: 1. Click the icon of a signal in the signal table. 2. Click the icon in the opened bit selection of the signal to select or deselect individual bits for the display. 13.6.3.6 Curve diagram Use of the curve diagram The curve diagram shows the signals of a recording selected in the signal table. Select the recording in the "Installed traces" or "Measurements" table of the trace handling. The display area can be zoomed as required. Measurement cursors can be used to select individual values for display in the signal table. The following operating instructions describe the use of the measurement cursors. Requirement A recording has been selected for display. Evaluation of a certain instant of a recording To display the values for a specific sample, proceed as follows: 1. Display the vertical measurement cursors via the button. 2. Move a measurement cursor with the mouse to the required position in the recording. The values of the signals are displayed in the signal table. The time or sample for the measurement cursors is displayed in the lower area of the curve diagram. Evaluation of the difference between two samples To display the difference, proceed as follows: 1. Display the vertical measurement cursors via the button. 2. Move both measurement cursors with the mouse to the required samples in the recording. The values of the signals and the difference are displayed in the signal table. The time or sample for the measurement cursors is displayed in the lower area of the curve diagram. WinCC Basic V13.0 System Manual, 02/2014 4585 Using online and diagnostics functions 13.6 Using the trace and logic analyzer function Using horizontal measurement cursors To check whether a certain value has been reached, proceed as follows: 1. Display the horizontal measurement cursors via the button. 2. Move a measurement cursor with the mouse to the required value of the recording. The values of the measurement cursor for the selected signal are displayed in the lower area of the curve diagram. Printing a recording The curve diagram supports the saving of the display as a bitmap and the copying of the display to the clipboard. Also use these functions (Page 4566) for printing. 13.6.4 Devices 13.6.4.1 S7-1200/1500 CPUs Recordable variables Device-dependent recording of tags The following list shows the operand areas from which tags can be recorded: Process image input Process image output Bit memory Data blocks Data types Elementary data types can be recorded. The availability of the individual data types depends on the device used: The following table lists the elementary data types: Data types Note Binary numbers BOOL - Bit strings 4586 BYTE - WORD - DWORD - LWORD Symbolic name required WinCC Basic V13.0 System Manual, 02/2014 Using online and diagnostics functions 13.6 Using the trace and logic analyzer function Data types Note Integers SINT - USINT - INT - UINT - DINT - UDINT - LINT Symbolic name required ULINT Symbolic name required Floating-point numbers REAL - LREAL Symbolic name required Lifetime of the installed trace configuration and recorded values Installed trace configurations are retained after POWER OFF. The recording is activated again after the restart of the CPU. Recorded values are lost during the restart. Note Downloading a configuration to the device in the "STOP" operating state Note that after downloading a configuration in the "STOP" operating state, you must check the installed traces and, if required, reactivate them or transfer them again. Note If signals or trigger tags that affect the address are changed, the trace configuration must also be transferred to the device again. This is the case for example, when a data block is shortened or extended or the data type is changed. Recording levels The following list shows the execution levels that can be selected for the recording cycle: Program cycle - OB 1 Time-of-day interrupt - OB 1x Time-delay interrupt - OB 2x Watchdog interrupt - OB 3x Synchronized processing cycles - OB 6x, not OB 60 WinCC Basic V13.0 System Manual, 02/2014 4587 Using online and diagnostics functions 13.6 Using the trace and logic analyzer function Servo task - OB 91 (S7-1500) IPO - OB 92 (S7-1500) Note The measured values are recorded at the end of the OB after the processing of the user program. Quantity structure The following table shows the maximum quantity structure that can be recorded with the trace and logic analyzer function: Device Maximum number of "Installed traces" Maximum number of signals per trace configuration 2 16 At least 4 16 S7-1200 (as of firmware version V4.0) S7-1500 (depending on the CPU type) Example of S7-1516 Maximum of 3854 samples for 16 long tags Maximum of 21844 samples for 16 binary tags Maximum of 58250 samples for 1 binary tag Refer to respective manual for more detailed information. CPU load through trace recording A trace recording increases the runtime of the respective recording level that can result in an execution level overflow with high utilization of the CPU. Remedy Change the trace configuration 1) Configure fewer tags and signals. 2) Then increase the number of tags and signals up to the maximum number of signals step-by-step without an execution level overflow. Select a slower recording level 4588 WinCC Basic V13.0 System Manual, 02/2014 Using online and diagnostics functions 13.6 Using the trace and logic analyzer function Software user interface of the device-specific area Structure of the user interface Display areas in the Properties window of the Inspector The settings options differ depending on the configured device. The following figure shows an example of the display in the TIA Portal: The area navigation provides the following entries for selection: General Configuration - Signals (Page 4590) - Recording conditions (Page 4591) Display of the properties of a trace configuration The trace configuration is selected in the trace handling: Selection in the "Trace configurations" table The properties are displayed in the Inspector window and can be changed. Selection in the the "Installed traces" table or "Measurements" table The properties are displayed write-protected in the Inspector window. User interface - General The "General" area shows the name of the trace configuration and input fields for the author and a comment. WinCC Basic V13.0 System Manual, 02/2014 4589 Using online and diagnostics functions 13.6 Using the trace and logic analyzer function Input options and displays in General The following figure shows an example of the display in the TIA Portal: The following table shows the input fields and displays: Column Icon Description "Name" - Name of the trace configuration "Author" - Author of the trace configuration "Comment" - Input field for a comment User interface - Signals The "Signals" area shows a table in which the signals to be recorded are configured for the selected trace configuration. Signals can also be inserted in the table using drag-and-drop. The signals can be sorted using drag-and-drop. Setting options and displays in "Signals" The following figure shows an example of the display in the TIA Portal: The following table shows the settings and displays: 4590 WinCC Basic V13.0 System Manual, 02/2014 Using online and diagnostics functions 13.6 Using the trace and logic analyzer function Column Icon Description Display of the signal icon for a selected signal. "Name" - Input field for the name or address of the signal. Examples: M0.0 DB1.DBW3 "Data_block_1".pressure - Button to open the signal selection table. The button is displayed when the table line is selected. Clicking the icon opens a table which offers possible signals for selection. The selected signal is displayed in the input field. "Data type" - Text field with display of the data type for the signal. "Address" - Input field for the address of the signal. With purely symbolic signals the field remains empty. "Color" - Text field for display and selection of the color. Click the selected field to display the signal color. Click the signal color to open the color selection dialog. "Comment" Input field for a comment on the signal. Shortcut menu commands The following table shows the shortcut menu commands of the table: Shortcut menu command Description "Cut" Cannot be selected. "Copy" Copies the contents of the selected lines to the clipboard. "Paste" Pastes the contents of the clipboard to the selected line. The existing contents are overwritten. "Delete" Deletes the selected lines from the table or deletes the name of the selected cell. "Rename" Switches the selected cell to the editing mode. Recording conditions Supported data types The following table shows the supported data types for the trigger tag: WinCC Basic V13.0 System Manual, 02/2014 Memory requirement and format of the number Data type 1 byte BOOL 8-bit integers SINT, USINT, BYTE 16-bit integers INT, UINT, WORD 32-bit integers DINT, UDINT, DWORD 64-bit integers LINT, ULINT, LWORD (device-dependent) 4591 Using online and diagnostics functions 13.6 Using the trace and logic analyzer function Memory requirement and format of the number Data type 32-bit floating-point numbers REAL 64-bit floating-point numbers LREAL User interface - Recording conditions The "Recording conditions" area shows the trigger condition for the selected trace configuration and in which cycle, how fast and how long the recording is made. The configuration is only possible if the trace configuration has been selected in the "Trace configurations" table of the trace handling. Setting options and displays in "Recording conditions" The following figure shows an example of the display in the TIA Portal: Setting/display Description "Recording time" Drop-down list Selection of the recording time. See Recording levels (Page 4587) Text field Detailed information on the selected recording time. "Record every" Input field 4592 Input of the reduction in relation to the cycles. WinCC Basic V13.0 System Manual, 02/2014 Using online and diagnostics functions 13.6 Using the trace and logic analyzer function Setting/display Drop-down list Description Selection of the reduction factor. The following settings are possible: "Cycle" Text field Display of the sampling time, taking into account the configured reduction. "Recording duration" Input field Input of the recording duration in relation to the samples. If the "Recording duration = max. recording duration" checkbox is activated, entries are overwritten by the value displayed in "Max. recording duration". Drop-down list Select the time unit for the recording duration. The following settings are possible: "Samples" Text field Displays the calculated recording duration. "Max. recording duration" Text field Displays the calculated maximum recording duration. The "Max. recording duration" depends on how many signals are recorded and the data type of these signals. "Use max. recording duration" "Trigger mode" Drop-down list Set the recording duration to the maximum value. When the checkbox is activated, the recording duration is set to the maximum possible recording duration. The set reduction in the "Record every" input field is taken into account. The recording duration is also adapted when additional signals are added. Selection of the trigger mode. The following settings are possible: "Record immediately" The recording is made immediately after the device is activated. "Trigger on tag" The recording is made as soon as the installed trace is activated and the configured trigger condition is fulfilled. Text field "Trigger tag" Input field Display of the trigger type. The "Trigger tag" specifies a signal that is used to trigger the recording. Enter a signal. Examples: M0.0 DB1.DBW3 "DataBlock_1".Temperature Opens the signal selection table. Clicking the icon opens a table which offers possible signals for selection as trigger tag. The selected signal is displayed in the input field. Text field "Event" Display of the trigger tag address. The events that can be used on this trigger tag are offered for selection according to the data type of the trigger tag. The event can only be configured when a valid signal has been entered as trigger tag. WinCC Basic V13.0 System Manual, 02/2014 4593 Using online and diagnostics functions 13.6 Using the trace and logic analyzer function Setting/display Drop-down list Description Event selection for which the trigger tag is checked. The entries in the drop-down list are described in Section Trigger event (Page 4594). Text field "Value" Display of the comparison type. Configuration of the selected event. The configuration options differ depending on the format of the trigger tag and the selected event. See Trigger event (Page 4594). "Pre-trigger" "Pre-trigger" defines the time during which the signals are already recorded before the actual trigger condition is fulfilled. If the trigger event occurs immediately or shortly after the activation of the recording, this may result in a shorter recording duration. Example of "recording duration" = 20 samples and "pre-trigger" = 5 samples: Trigger event occurs 50 samples after activation of the recording Actual recording duration = 20 samples Trigger event occurs 2 samples after activation of the recording Actual recording duration = 17 samples Input field Input of the duration in relation to the selection in the drop-down list. Drop-down list Select the time unit The following settings are possible: "Samples" Text field Displays the calculated "pre-trigger" period Trigger event Depending on the selection in the drop-down list box, the further settings differ for the "event". The individual events are described below. "=TRUE" Supported data types: Bit (Page 4591) The recording starts when the state of the trigger is TRUE. "=FALSE" Supported data types: Bit (Page 4591) The recording starts when the state of the trigger is FALSE. "Rising edge" Supported data types: Bit (Page 4591) The recording is started when the trigger state changes from FALSE to TRUE. After activation of the installed trace, at least two cycles are required to identify the edge. 4594 WinCC Basic V13.0 System Manual, 02/2014 Using online and diagnostics functions 13.6 Using the trace and logic analyzer function "Rising signal" Supported data types: Integers and floating-point numbers (Page 4591) The recording is started when the rising value of the trigger reaches or exceeds the value configured for this event. After activation of the installed trace, at least two cycles are required to identify the edge. "Falling edge" Supported data types: Bit (Page 4591) The recording is started when the trigger state changes from TRUE to FALSE. After activation of the installed trace, at least two cycles are required to identify the edge. "Falling signal" Supported data types: Integers and floating-point numbers (Page 4591) The recording is started when the falling value of the trigger reaches or falls below the value configured for this event. After activation of the installed trace, at least two cycles are required to identify the edge. "In the range" Supported data types: Integers and floating-point numbers (Page 4591) The recording starts as soon as the value of the trigger is in the value range configured for this event. "Outside of the range" Supported data types: Integers and floating-point numbers (Page 4591) The recording starts as soon as the value of the trigger is outside the value range configured for this event. "= value" Supported data types: Integers (Page 4591) The recording starts when the value of the trigger is equal to the value configured for this event. "<> value" Supported data types: Integers (Page 4591) The recording starts when the value of the trigger is not equal to the value configured for this event. "= bit pattern" Supported data types: Integers (Page 4591) WinCC Basic V13.0 System Manual, 02/2014 4595 Using online and diagnostics functions 13.6 Using the trace and logic analyzer function The recording starts when the value of the trigger matches the bit pattern configured for this event. The following figure shows the setting options for a "bit pattern": It is possible to switch between the icons by clicking the respective button. The following table shows the icons: Icon Description Bit is not evaluated Bit is checked for FALSE Bit is checked for TRUE "<> bit pattern" Supported data types: Integers (Page 4591) The recording starts when the value of the trigger does not match the bit pattern configured for this event. See also Configuring the trigger conditions (Page 4598) Configuration Trace configuration - overview The configuration of the recording conditions and the signals to be recorded is device-specific. 4596 WinCC Basic V13.0 System Manual, 02/2014 Using online and diagnostics functions 13.6 Using the trace and logic analyzer function Requirement A trace configuration has been created and selected in the "Trace configurations" table of the trace handling. Procedure The following table shows the procedure for configuring. Step Description 1 Documentation of the configuration (optional) Enter a comment and an author for the configuration. 2 Selecting signals (Page 4597) Select the signals to be recorded in the "Signals" area. 3 Configuring the recording cycle and duration Select a recording time, a cycle and the duration in the "Recording conditions" area. 4 Configuring the trigger conditions (Page 4598) In the "Recording conditions" area, select whether the recording is to be performed immediately or depending on a trigger condition. Selecting signals Requirement A trace configuration has been created and selected in the "Trace configurations" table of the trace handling. The "Signals" area is open in the Inspector window. Procedure To configure the signals to be recorded, proceed as follows: 1. Click in the first empty line of the table. 2. Click in the first empty line of the "Name" column. 3. Select a signal. The following options are available: - In the "Name" column, click the button and select a tag. - Enter the symbolic tag name in the cell in the "Name" column. - Enter the address directly in the "Address" column. - Drag a signal to the table using drag-and-drop. 4. Click in the "Display color" column and select a color for the display of the signal. 5. Click in the "Comment" column and enter a comment for the signal. 6. Repeat the procedure from step 1 until all the signals to be recorded have been entered in the table. WinCC Basic V13.0 System Manual, 02/2014 4597 Using online and diagnostics functions 13.6 Using the trace and logic analyzer function Configuring the recording cycle and duration Requirement A trace configuration has been created and selected in the "Trace configurations" table of the trace handling. The "Recording conditions" area is open in the Inspector window. Procedure To configure the cycle and the duration of a recording, proceed as follows: 1. Click the button for the recording time. 2. Select an OB for the recording time (Page 4587). 3. Select a unit for the reduction factor in the drop-down list box for "Record every". 4. Enter the factor for the reduction in the input field for "Record every". 5. Select a unit in the drop-down list box for "Recording duration". 6. Specify the recording duration. The following options are available: - Enter a value for the duration in the input field for "Recording duration". - Activate the "Use max. recording duration" checkbox. Configuring the trigger conditions Requirement A trace configuration has been created and selected in the "Trace configurations" table of the trace handling. The "Recording conditions" area is open in the Inspector window. 4598 WinCC Basic V13.0 System Manual, 02/2014 Using online and diagnostics functions 13.7 Establishing a remote connection with TeleService "Record immediately" trigger condition To start the recording immediately, proceed as follows: 1. Select the "Record immediately" entry in the drop-down list for "Trigger mode". The input fields for the trigger tag are hidden. "Trigger on tag" trigger condition To start the recording depending on a condition, proceed as follows: 1. Select the "Trigger on tag" entry in the drop-down list for "Trigger mode". 2. Select a trigger tag. The following options are available: - Click the button for the trigger tag and select a tag. - Enter the address or the symbolic name of the tag directly in the input field for the trigger tag. A drop-down list with events and input fields is displayed. The display depends on the data type of the tag. 3. Configure the event. 4. Select a unit for the pre-trigger in the drop-down list for "Pre-trigger". 5. In order to record a period before the trigger event, enter a value greater than 0 in the input field for the pre-trigger. Note The trigger condition is checked in every cycle irrespective of the setting in "Record every". To reliably identify the trigger, the trigger signal must be present for at least one full cycle. 13.7 Establishing a remote connection with TeleService 13.7.1 Basics of working with TeleService 13.7.1.1 Introduction to TeleService Introduction TeleService gives your controller telecommunication capability. You can manage, control and monitor distributed plants centrally by means of remote connections. WinCC Basic V13.0 System Manual, 02/2014 4599 Using online and diagnostics functions 13.7 Establishing a remote connection with TeleService Scope of functions TeleService allows you to use the range of TIA portal functions via a telephone network or an Internet connection by establishing a remote connection to a remote plant. The online connection allows you to edit a remote plant as usual with the TIA Portal. Advantages Using TeleService offers the following advantages: You can easily access even remote sections of plants and include them in a complete system. You can offer rapid help and support in the event of faults in a remote system without having to go there yourself. You can employ your resources effectively. It significantly reduces costs. It can significantly reduce plant downtimes. It improves the efficiency of your plant. See also TeleService functionality (Page 4600) 13.7.1.2 TeleService functionality TeleService fields of application TeleService offers the following the fields of application: Access to remote systems (remote maintenance): You can manage, control, and monitor remote systems centrally by means of remote connections. This is possible with an S7-300/400 CPU, an S7-1200 CPU and an S7-1500 CPU and a TS Adapter MPI or a TS Adapter IE. Establishing connections from and to remote systems (PG-AS remote link): You can use PRODAVE MPI V5.0 and newer to establish a remote connection to a remote system, and the communications instruction "PG_DIAL" to establish a remote connection from a remote system. This is possible with an S7-300/400 CPU and a TS Adapter MPI. Data exchange between systems (AS-AS remote link): The communications instruction "AS_DIAL" allows two automation systems to exchange process data over the telephone network. This is possible with an S7-300/400 CPU and a TS Adapter MPI. 4600 WinCC Basic V13.0 System Manual, 02/2014 Using online and diagnostics functions 13.7 Establishing a remote connection with TeleService Sending an text message from a system: An automation system can send a message (SMS) via a GSM wireless modem using the communications instruction "SMS_SEND" ". This is possible with an S7-300/400 CPU and a TS Adapter MPI. Sending an email from a system An automation system can also send an email with the following communications instructions and a TS Adapter IE . - S7-300/400 CPUs (CPU S7-31x-2PN/DP or CPU 41x-3PN/D) use the instruction "AS_MAIL" - S7-1200 CPUs use the instruction "TM_MAIL" - S7-1500 CPUs use the instruction "TMAIL_C" 13.7.1.3 Telephone book at TeleService Introduction By double clicking the "phone book" folder in the project tree you open the phone book editor displaying the TeleService phone book. Each version of the TIA Portal has its own "global phone book". If a global phone book from an earlier version of the TIA Portal is found in a more recent version of the TIA Portal, you will be asked once if you want to import this phone book. This gives you the advantage of being able to import the system data from the previous version into the more recent version of the TIA Portal. Global phone book properties The global phone book is used in TeleService to manage specific system data that are required to establish a remote connection. When you open the phone book for the first time, you will see an empty phone book with all available columns; in all other cases, the last phone book edited is displayed. You can enter any number of systems in a phone book. Systems contain the data required for establishing a remote connection, for example, the name and location of the device and the phone number to be dialed, along with all country-specific details. With VPN connections, you can enter an IP address or a DNS name instead of the phone number. The TS adapters used for establishing the connection are distinguished by color, depending on whether a TS Adapter MPI or a TS Adapter IE is used for establishing the connection. See also Working with the phone book (Page 4602) WinCC Basic V13.0 System Manual, 02/2014 4601 Using online and diagnostics functions 13.7 Establishing a remote connection with TeleService 13.7.2 Working with the phone book 13.7.2.1 Basics on working with the phone book Working with the phone book You have the following options when working with a phone book: Open phone book Save phone book Import phone book data Export phone book data Printing the phone book Use phone book data to establish a remote connection You can implement these functions simply and easily by using the buttons in the phone book toolbar. Note Access to phone books The phonebook is user specific in TeleService. However, it is not possible to access the global phone book with more than one instance of the TIA portal at the same time. See also Open phone book (Page 4604) Saving phone book (Page 4605) Exporting phone book data (Page 4607) Printing the phone book (Page 4608) Structure of the phone book (Page 4602) 13.7.2.2 Structure of the phone book Introduction A global phone book in TeleService is used to manage the data you require for establishing a remote connection. Once you have created the connection data and saved it in the phone book, you can access it each time you want to establish a remote connection. 4602 WinCC Basic V13.0 System Manual, 02/2014 Using online and diagnostics functions 13.7 Establishing a remote connection with TeleService Structure of the phone book The integrated global phone book in TeleService contains the following columns: Column name Meaning System name Enter a name for your system. Adapter type Select the TS Adapter type used in the drop-down list: TS Adapter MPI or TS Adapter IE. Connection type Select the required connection type: Dial-up connection or VPN connection. Area code Enter the required area code. This column is only active with dial-up connections. This column cannot be edited for VPN connections. Phone number/remote address Enter the required connection data for establishing the remote connection. For dial-up connections, this can be a phone number, and for VPN connections a DNS name or an IP address. Fingerprint Enter the corresponding fingerprint for establishing a VPN connection to the TS Adapter IE Advanced. Country Enter the country code. This column is only active with dial-up connections. This column cannot be edited for VPN connections. User name Enter the user name you have logged on under. Password Enter the password for this user name. Group Enter the group if you have carried out grouping. Company Enter the company to be contacted. Department Enter the relevant department. Street Enter the street. Town/City Enter the town or city to which the remote connection is to be established. Comment Enter a comment if required. Showing or hiding columns You can show or hide the individual columns. To do so, select the required column header and open the shortcut menu with the right mouse button. 13.7.2.3 Symbols in the phone book Meaning of the TeleService icons The following table shows the meaning of the TeleService icons: Symbol Meaning Open the global phone book Imports a phone book Exports a phone book WinCC Basic V13.0 System Manual, 02/2014 4603 Using online and diagnostics functions 13.7 Establishing a remote connection with TeleService Symbol Meaning Establishes a remote connection Terminates the active remote connection Establishes a remote connection or terminates it Displays the connection to a TS Adapter IE in the phone book Displays the connection to a TS Adapter MPI in the phone book Adds a new row to the phone book Inserts a new row in the phone book 13.7.2.4 Manage phone book Open phone book Opening phone books To open the phone book, follow these steps: 1. In the project tree, double-click on the "Phone book" folder under "Online access" > "TeleService". 2. The phone book opens so that you can enter or edit the required system data. Inserting rows in the phone book Inserting rows in the phone book To insert a new row in the phone book, follow these steps: 1. Select the row in front of which you want to insert a new row. 2. Click the "Insert row" button in the toolbar. Result A new row is inserted in the phone book above the selected row. 4604 WinCC Basic V13.0 System Manual, 02/2014 Using online and diagnostics functions 13.7 Establishing a remote connection with TeleService Showing and hiding columns in the phone book Showing and hiding columns To show or hide columns in the phone book, follow these steps: 1. Click a column header. 2. In the shortcut menu, select the "Show/hide columns" command. The selection of available columns is displayed. 3. To show a column, select the column's check box. 4. To hide a column, clear the column's check box. Result The respective columns are shown or hidden when displaying the phone book. Saving phone book Saving phone books When you exit the phone book editor or leave the TIA portal, you are asked whether you want to save the global phone book. Click "Yes" to save the phone book. Importing phone book data Introduction It is possible to import the phone book data from an external file or from an older version of the TIA Portal. Requirement You have already created an import-capable phone book file. You have already created a phone book with an older version of the TIA Portal. Importing phone book data from a phone book file To import phone book data from a phone book file, follow these steps: 1. Open the "TeleService" folder under "Online access" in the project tree. 2. Double-click on the "Phone book" folder. 3. Click the "Import" button in the toolbar. WinCC Basic V13.0 System Manual, 02/2014 4605 Using online and diagnostics functions 13.7 Establishing a remote connection with TeleService 4. Confirm the prompt asking if you want to save the current state of the phone book with "Yes", if applicable, and specify the location for storing the phone book in the dialog that follows. 5. If you do not want to save the current state of the phone book, answer the prompt with "No". In the subsequent dialog, select the phone book file to which the current phone book should be stored. 6. Close the dialog box with "OK". Result The imported phone book data is displayed in the global phone book. Note Defining dialing rules Dialing rules must be defined before the "area code" and "country" columns in the imported phone book can be edited for dial-up connections. To define dialing rules, follow the link in the history. Importing phone book data from an older version of the TIA Portal To import phone book data from an older version of the TIA Portal, follow these steps: 1. Open the "TeleService" folder under "Online access" in the project tree. 2. Double-click on the "Phone book" folder. 3. Click the "Import" button in the toolbar. 4. Confirm the prompt asking if you want to save the current state of the phone book with "Yes", if applicable, and specify the location for storing the phone book in the dialog that follows. 5. If you do not want to save the current state of the phone book, answer the prompt with "No". 6. Enter the following path in the dialog that follows: "%appdata%\siemens\automation \TeleService\GlobalTeleServicePhoneBook.tel". 7. Close the dialog box with "OK". Result The phone book data imported from the older version of the TIA Portal is displayed in the global phone book. 4606 WinCC Basic V13.0 System Manual, 02/2014 Using online and diagnostics functions 13.7 Establishing a remote connection with TeleService Note Defining dialing rules Dialing rules must be defined before the "area code" and "country" columns in the imported phone book can be edited for dial-up connections. To define dialing rules, follow the link in the history. See also Defining dialing rules (Page 4608) Exporting phone book data Introduction It is possible to export phone book data to an external file. Requirement You have already created a phone book under TeleService with the corresponding system data. Procedure Proceed as follows to export the phone book data: 1. Open the "TeleService" folder in project tree. 2. Double-click on the "Phone book" folder. 3. Click the "Export" button in the toolbar. 4. In the next dialog box, select where the current phone book is to be exported. 5. Close the dialog box with "OK". Result The exported phone book data are saved in the specified export file. WinCC Basic V13.0 System Manual, 02/2014 4607 Using online and diagnostics functions 13.7 Establishing a remote connection with TeleService Printing the phone book Printing phone books You can print out all or some of the data in a phone book. Proceed as follows: 1. Open the phone book. 2. Select the Phone book > Print menu command or click on the appropriate button in the toolbar. The "Print" dialog will open. 3. Specify whether you wish to print the complete phone book or just part of it and set all other options. 4. Start the print job with "OK". Result The phone book data is printed on the default printer. If the printout is more than one page long, an identifier is printed after the page number at the bottom right corner of the page to indicate that there is another page. The last page does not have this symbol, indicating that no more pages are to follow. Defining dialing rules Procedure To define location-specific dialing rules, follow these steps: 1. Open the folder "Online access" in the TIA portal and select the "TeleService" folder. 2. Use the shortcut menu to access the "TeleService" properties. 3. In the dialog that follows, open the "Advanced settings" tab and activate the "Use dialing rules" option. 4. Click the "Adapt" button. 5. In the dialog that follows, enter the required location information for connection establishment. - For new locations, enter the country or region and the corresponding area code. - If required, set the correct destination code and pre-dial line for local/long-distance calls. - Select your chosen dialing mode for the location. 6. Exit the dialog by clicking "OK". 7. In the next dialog, select the location from which you wish to dial, and click "OK". 4608 WinCC Basic V13.0 System Manual, 02/2014 Using online and diagnostics functions 13.7 Establishing a remote connection with TeleService 8. In the TeleService dialog that follows, check that the correct location appears under "Location". 9. Confirm your entries by clicking "OK". Note Modem operation on a local loop or extension You do not need to specify a pre-dial line if you operate your modem on a local loop (main telephone line). The fields for the pre-dial lines for local calls and long-distance calls must be empty. If you operate your modem on an extension, you should enter the pre-dial lines which need to be called to access a local loop. Example of the use of dialing rules The following example illustrates the use of location-specific dialing rules for the city of Karlsruhe in Germany. In the TeleService phone book, you enter the phone number "1234567", without the area code and without the country code. Result: The phone number "1234567" is always dialed, irrespective of the location of the caller. In addition to the phone number "1234567", you enter the location-specific dial parameters for the Karlsruhe area code "0721" and the country code "+49" for Germany in the TeleService phone book. Result: "1234567" is dialed from Karlsruhe. "07211234567" is dialed from other towns in Germany. "00497211234567" is dialed from other countries. Note Display in the phone book The "area code" and "country" columns in the TeleService phone book can only be edited once you have defined the dialing rules as detailed above. WinCC Basic V13.0 System Manual, 02/2014 4609 Using online and diagnostics functions 13.7 Establishing a remote connection with TeleService 13.7.3 Remote connections as dial-up connections 13.7.3.1 Basics for establishing a dial-up connection Using a TS Adapter for dial-up connections A TS Adapter is needed for establishing a remote dial-up connection using TeleService. The TS Adapter is used to prepare an automation system for use with TeleService by connecting it to a telephone network via a modem. The TS Adapter has an integrated parameter memory in which a parameter set for TeleService operation is stored. With the function "export adapter parameter", different parameter sets can be saved in external files, and reloaded in the TS Adapter via the function "import adapter parameter". Establishing a remote dial-up connection You can choose between a number of different TS Adapters, each of which offers a different functionality and different connection options. The figure below shows two possible configurations for establishing a dial-up connection to a system with the TS Adapter IE. 76$GDSWHUb,( 2SHUDWLRQZLWKH[WPRGHP 0RGHP 0RGHP (WKHUQHW 3URJUDPPLQJGHYLFH3& $XWRPDWLRQV\VWHP 76$GDSWHUb,( 2SHUDWLRQZLWKLQWPRGHP 0RGHP 3URJUDPPLQJGHYLFH3& 4610 (WKHUQHW $XWRPDWLRQV\VWHP WinCC Basic V13.0 System Manual, 02/2014 Using online and diagnostics functions 13.7 Establishing a remote connection with TeleService Overview of possible TS Adapter: The TS Adapter comes in the following versions: TS Adapter II (also designated "TS Adapter MPI") TS Adapter IE Standard (also designated "TS Adapter IE") TS Adapter IE Basic (also designated "TS Adapter IE") Designation "TS Adapter" In the following pages, the designation "TS Adapter" stands for all versions. The relevant product designation is listed beside information which only applies to a specific version, for example, "TS Adapter II" or "TS Adapter IE Standard". Note For more detailed information on your TS Adapter, please refer to the documentation supplied with the TS Adapter. See also Short description of the TS adapter MPI (Page 4619) Short description of the TS adapter IE (Page 4626) Exporting adapter parameters (Page 4625) Importing adapter parameters (Page 4626) 13.7.3.2 Telephone networks and modems Supported telephone networks and modems Telephone networks which can be used TeleService can be used with digital networks (ISDN), analog networks and wireless networks (with GSM technology). This version supports a remote connection to a TS Adapter. Modem support TeleService has been implemented to be independent of the modem. This means that all standard modems which can be installed in the Windows Control Panel and are visible as modems can also be used by TeleService. The choice of modem type is determined primarily by the existing hardware of the programming device/PC and the telephone network to be used. WinCC Basic V13.0 System Manual, 02/2014 4611 Using online and diagnostics functions 13.7 Establishing a remote connection with TeleService The following modem types/media are supported: Modems (external modems at the COM interface, internal modems and PCMCIA cards) External ISDN adapter at the COM interface or USB interface Internal ISDN adapter with virtual COM interface (for example AVM CAPI port) External ISDN modems (ISDN adapter with integrated analog modem functionality) at the COM interface or USB interface Radio network modems with GSM technology, PCMCIA adapter card or data cable and mobile phone Gateways Gateways between the various telephone networks are in principle possible. Remote connections from an ISDN adapter to an analog modem and vice versa only function with special ISDN telephone adapters. Performance in telephone networks The data throughput of a remote connection depends on the modem and telephone network used and the quality of the telephone line. Installing the local modem Introduction If you have already installed a modem for data transfer in your operating system, this modem can also be used for TeleService. If a modem has not yet been installed for your operating system, one must be installed before you can establish a remote connection with TeleService. Procedure Proceed as follows: 1. Make sure your programming device/PC and the modem are switched off. 2. Physically connect the external modem to a COM or USB interface on your programming device/PC. You can also install an internal modem or a PCMCIA card in accordance with the manufacturer's specifications. 3. Now switch on the modem and then the programming device or the PC. 4612 WinCC Basic V13.0 System Manual, 02/2014 Using online and diagnostics functions 13.7 Establishing a remote connection with TeleService Result Plug-and-play modems are recognized and installed automatically by the operating system. Dialogs will take you through the installation procedure. Note Modems without plug-and-play If your modem is not recognized automatically when switched on, you will have to install it yourself using the Control Panel. Please refer to the information in the documentation supplied with your modem. Connecting and configuring the remote modem Introduction A modem must also be connected to the remote system before you can work with TeleService. This modem is designated the "remote modem". Configuring the remote modem The modem receives all parameters required for operation from the TS Adapter connected. These include data for initializing the modem and settings for serial transmission between the TS Adapter and the modem. The data required for the remote modem is specified during the configuration of the TS Adapter. The modem may be internal or external depending on the TS Adapter used. How to connect a TS Adapter with an internal modem 1. Switch off the TS Adapter. 2. Connect the TS Adapter to the automation system. 3. Connect the TS Adapter to the telephone line. 4. Switch on the TS Adapter. How to connect a TS Adapter with an external modem 1. Switch off the modem. 2. Connect the TS Adapter to the automation system. 3. Connect the TS Adapter to the modem using a modem cable. 4. Connect the modem to the telephone line. 5. Switch on the modem. 6. Switch on the TS Adapter. WinCC Basic V13.0 System Manual, 02/2014 4613 Using online and diagnostics functions 13.7 Establishing a remote connection with TeleService Note Please note the following information on configuring the remote modem: The default parameters for the modem and the serial port set in the TS Adapter should in most cases ensure successful operation; changes in the parameter assignment will only be needed in rare cases. You need only change the parameter assignment of the TS Adapter if a modem connection is not established or if factory settings are to be adapted or optimized. TS Adapter parameter assignment can be changed via either a direct or a remote connection. 13.7.3.3 Access protection for dial-up connections Access protection information Introduction When you assign the parameters for your TS adapter, you can restrict access to the parameters of the TS adapter and access to remote systems. Scope of access protection Access protection only exists for remote connections; TS adapter parameter assignment can be accessed at any time in direct connection mode. Access protection also exists in direct connection for the TS adapter IE. Access protection information The TS Adapter MPI is not delivered with access protection activated. There is a default password for the TS adapter IE. The first user who assigns the parameters for this adapter can therefore activate access protection by defining the password for a user and/or a callback number. This is a multi-level access protection with several users, each with or without administrator rights. For the TS adapter MPI there is only one adminstrator and no more than two users. For a modem connection, only an administrator can define the two users and change and, if necessary, delete their settings. Those logged in as users can only change their own passwords and their own callback numbers. However, with the TS adapter MP you can access the process of assigning parameters of the TS adapter in direct connection, without restriction. 4614 WinCC Basic V13.0 System Manual, 02/2014 Using online and diagnostics functions 13.7 Establishing a remote connection with TeleService Advantages Access protection offers the following advantages: Unauthorized access by persons outside the system is almost impossible. The plant operator bears most of the telephone costs. TeleService callback options Callback variants The costs of a telephone connection are normally borne by the caller who establishes the dialup connection. TeleService can, however, be used so that after a short initial connection the modem connection is established again in the opposite direction, in other words initiated by the TS Adapter (callback). In this case, the plant operator bears the costs of the callback. There are two callback variants in TeleService: 1. Callback to a number specified during connection establishment. 2. Callback to a number stored on the TS Adapter. Levels of protection Introduction You can set up one of two possible levels of access protection for TeleService access to the TS Adapter. Different options are available with each protection level. Access protection options Access protection level 1: The TS Adapter is protected by the user name and password. You can access the TS Adapter via any telephone line and specify any callback number during connection establishment. Access protection level 2: The TS Adapter is protected by the user name, password, and the callback number. You can only access the TS Adapter from one telephone connection per user. The table below sets out the above conditions for the various protection levels: WinCC Basic V13.0 System Manual, 02/2014 Level of access protection Administrator/User password Callback number 1 enter do not enter 2 enter enter 4615 Using online and diagnostics functions 13.7 Establishing a remote connection with TeleService Logging on to TS Adapter When you log on to the TS Adapter and after you have set up access protection, enter your user name, the corresponding password and, if desired, a callback number: Level of access protection Administrator/User password Callback number 1 enter do not enter or enter any callback number 2 enter do not enter If you have entered a callback number during connection establishment (access protection level 1) or stored a callback number in the TS Adapter (access protection level 2), the modem connection will be terminated and the TS Adapter will call back the given number. Setting up access protection and callback number for the TS adapter Introduction During the parameter assignment for the TS adapter MPI in TeleService, you can set up access protection and a callback number for the parameter assignment of the adapter and connection to the remote system. The following describes the parameter assignment for a TS adapter MPI. The parameter assignment of a TS adapter IE is carried out in analog. The specific method is described in the web help of this adapter. Requirement A TS Adapter MPI is connected to your computer and is displayed in the project tree under "Accessible nodes". Procedure To set up access protection for the TS adapter, proceed as follows: 1. Click on the command "Assign TS Adapter MPI parameters" in the project tree. 2. Open the "Access security" tab. 3. Enter a password for your user name and/or number that you want the modem to call back following logon. - If you are an administrator, you can change all the settings for administrators and users, and delete or create users. - If you are logged on as a user, you can only change your own settings (password and callback number). 4. Confirm all entries before exiting the dialog with "OK". 5. Click the "Yes" button to confirm the following query. 4616 WinCC Basic V13.0 System Manual, 02/2014 Using online and diagnostics functions 13.7 Establishing a remote connection with TeleService Result The parameter assignment for the access protection and the callback number is saved in the non-volatile memory of the TS adapter MPI. Note Important points to note when setting up access protection: The settings in the "Modem" tab must correspond to the conditions at the plant if callback functionality is to be guaranteed. Entering an incorrect callback number in the role of "ADMIN" user will mean you are no longer able to access the TS Adapter MPI over a remote connection! Test the callback number before you enter it as the "ADMIN" user by calling the given callback number during connection establishment (access protection level 1). Complete a callback in TeleService Callback options Two different callback variants can be set up in TeleService. The following callback options are available: Callback to a number specified during connection establishment. Callback to a number stored on the TS Adapter Callback to a number specified during connection establishment 1. In the project tree of the TIA portal, open the "Online access" folder. 2. Click on the "TeleService" folder it contains. 3. Double-click the "Set up/close remote connection" entry. The "Set up remote connection to the remote system" dialog opens. 4. In the "Adapter type" drop-down list, select the adapter type used. 5. Select the "dial-up connection" under "Connection type" if it is not already selected. 6. Select the modem you are using under "Local Settings". 7. Enter the phone number to be dialed in the appropriate box or open the phone book by clicking on the button behind it and take the desired phone number from the phone book. 8. Enter your user name and associated password of the TS adapter. 9. If you want a "Connection setup with callback", select the appropriate option button. WinCC Basic V13.0 System Manual, 02/2014 4617 Using online and diagnostics functions 13.7 Establishing a remote connection with TeleService 10.Click the "Connect" button to establish the required remote connection. This button only becomes active when you have entered all the parameters needed to establish a remote connection. Any remote connection is displayed under "Status". 11.Enter the desired callback number in the dialog that follows. Result The remote connection to the desired system is made with callback. The connected system is shown with the corresponding icon in the project tree. Note This procedure is useful if the costs of the modem connection are to be borne by the plant operator and if the actual callback number is not fixed, i.e. callback is not always to the same receiver. It is particularly useful for mobile users. Callback to a number stored on the TS Adapter 1. Assign the parameters for the desired callback number in the TS adapter. 2. Establish a connection to the TS adapter as described above, and observe the following features: - Enter the user name and password for which the callback number parameters are assigned in the TS adapter. - The check box "Establish a connection with callback" does not have to be selected, since the callback number is already known by the TS adapter. Result Callback to a number stored on the TS adapter has been established. If a remote connection is established, the callback occurs from the remote system. Note This procedure offers the highest level of access protection. However, it does pose a risk: if the callback number stored on the TS Adapter is not correct, it will no longer be possible to access the TS Adapter over a modem connection. The device can in such a case only be put back into operation by changing the parameter settings on site. 4618 WinCC Basic V13.0 System Manual, 02/2014 Using online and diagnostics functions 13.7 Establishing a remote connection with TeleService 13.7.3.4 TS adapter MPI Short description of the TS adapter MPI TS Adapter MPI: The designation "TS Adapter MPI" is a collective term for allTS Adapter with an MPI/DP interface. The TS Adapter MPI comes in the following versions: As TS Adapter I (parameters cannot be assigned via the TIA Portal) as TS Adapter II The table below provides a short description of the functionalities. For detailed information on your TS Adapter, please refer to the documentation supplied with your TS Adapter. TS Adapter II: Direct connection Connection via the Universal Serial Bus (USB). The firmware can be replaced. The modem is integrated or can also be connected as external modem. The TS Adapter II switches automatically between the modems. As long as no external modem is connected, the adapter will use the internal modem. There are two variants With internal analog modem. An external modem can also be connected to the RS232 port. With internal ISDN adapter. An external modem can also be connected to the RS232 port. Use of the designation "TS Adapter" For TeleService the designation "TS Adapter" is the generalization for all versions. The relevant product designation is listed beside information which only applies to a specific version of a TS Adapter, for example, "TS Adapter II", "TS Adapter IE Standard" or "TS Adapter IE Basic". How the TS adapter MPI works How the TS Adapter MPI Works In line with the configuration, the TS Adapter MPI connects the serial port or USB port of your programming device/personal computer (direct connection) or the serial port of a modem (modem connection) to the MPI/PROFIBUS network of your automation system. The TS Adapter MPI has a non-volatile memory. Parameters for the following functions are stored in this memory: The MPI/PROFIBUS network (network parameters) The mode of the modem used WinCC Basic V13.0 System Manual, 02/2014 4619 Using online and diagnostics functions 13.7 Establishing a remote connection with TeleService The serial port to the modem Access protection Default parameter assignment The TS Adapter comes with default parameter assignment. The parameters can be set and saved to the non-volatile memory of the TS adapter in a parameter assignment session. When "Direct connection" is configured, the TS Adapter will only use the network parameters for access to the MPI/PROFIBUS network. In the "Modem connection" configuration, all the parameters stored on the TS Adapter will be activated. Note For more detailed information on the configuration of your TS Adapter, please refer to the documentation supplied with it. Operating a TS adapter MPI in direct connection mode Direct connection with TS Adapter MPI The direct connection is used to assign the parameters of the TS Adapter MPI. The same configuration also allows you to go online in the TIA Portal and thereby check the configured MPI/PROFIBUS parameters for bus compatibility. This means that (as with a PC adapter) SIMATIC S7/C7 systems can be accessed via the MPI/DP interface without an MPI/ PROFIBUS module occupying a slot for a programming device/PC. Access protection for the TS Adapter is not active in direct connection configuration. This means that the parameter assignment of the TS Adapter can be changed without any problems, for example by importing adapter parameters. Note Display of the TS Adapter MPI in the TIA Portal As soon as you have connected a TS Adapter MPI with the PG/PC using the USB port, the "TS Adapter" folder is displayed in the project tree of the TIA Portal. When you open the folder, you can assign the parameters of the connected TS Adapter MPI via the following dialog. Establishing the direct connection for TS Adapter MPI Direct connection mode means there is a direct connection via the TS Adapter MPI between the programming device/personal computer on which TeleService is installed and the automation system. No modem is required. 4620 WinCC Basic V13.0 System Manual, 02/2014 Using online and diagnostics functions 13.7 Establishing a remote connection with TeleService The figure below shows the configuration of the TS Adapter MPI with a direct connection. 76$GDSWHU,, 86% 03,'3 86%FDEOH 3URJUDPPLQJGHYLFH3& $XWRPDWLRQV\VWHP Operating a TS adapter MPI in modem connection mode Introduction to the modem connection with TS Adapter MPI This configuration allows you to dial into a remote system. To do this, you establish a remote connection to a remote system using TeleService on a telephone network. Over the established modem connection, you can then work with the selected plant as usual with the TIA Portal. Establishing a modem connection with TS Adapter MPI This connection between the programming device or PC on which TeleService is installed and the automation system in which the TS Adapter MPI is inserted in the MPI/DP interface is made through a modem route. The configuration therefore includes the programming device or PC via the telephone network and the TS Adapter MPI on the MPI/DP interface of the automation system. The figure below shows the structure of the modem connection. WinCC Basic V13.0 System Manual, 02/2014 4621 Using online and diagnostics functions 13.7 Establishing a remote connection with TeleService 0RGHP 76$GDSWHU, 0RGHP 03,'3 $XWRPDWLRQV\VWHP 3URJUDPPLQJ GHYLFH3& 76$GDSWHU,, 2SHUDWLRQZLWKH[WPRGHP 0RGHP 03,'3 0RGHP $XWRPDWLRQV\VWHP 3URJUDPPLQJGHYLFH3& 76$GDSWHU,, 2SHUDWLRQZLWKLQWPRGHP 0RGHP 3URJUDPPLQJ GHYLFH3& 03,'3 $XWRPDWLRQV\VWHP Note Parallel operation between direct and modem connection The TS Adapter II has two connections for communication with PG/PC, both of which can be connected at the same time. At the same time, connect the USB interface with the PG/PC and the modem interface with the telephone network. In this configuration you can either use the direct or the modem connection. A parallel operation is not possible! TS adapter MPI configuration options Useful information on configuring the TS Adapter MPI The TS Adapter MPI can be configured in both direct connection mode and via an existing remote connection. The following parameter assignment options are available: Reconfiguration (Page 4623) Restoring default parameter assignment (Page 4624) Importing adapter parameters (Page 4626) Exporting adapter parameters (Page 4625) Setting up access protection (Page 4616) 4622 WinCC Basic V13.0 System Manual, 02/2014 Using online and diagnostics functions 13.7 Establishing a remote connection with TeleService Parameter assignment Configure your TS Adapter in accordance with the documentation supplied with the TS Adapter. It will detail the exact procedure for parameter assignment. Note Please note the following when configuring the TS Adapter MPI If you change the current parameter settings when there is an established remote connection, there is a risk it will not subsequently be possible to establish a modem connection with the modified parameters. The TS Adapter MPI can in this case only be configured in direct connection mode. This means that either parameter assignment must be carried out with a programming device/personal computer at the plant location or the TS Adapter MPI must be brought to the location of the local programming device/personal computer in order to be configured. Positive acknowledgement During parameter assignment, the data is written to the non-volatile memory of the TS Adapter MPI. The parameter assignment process is not acknowledged positively until all precautions have been taken to ensure that parameter changes have been carried out correctly and will thus survive a power failure. Changes become effective for the TS Adapter MPI as follows: The serial parameters, the modem parameters and the parameters for access protection are activated once the remote connection has been terminated. The modified network parameters are activated immediately. Configuring TS adapter MPI Introduction The TS Adapter MPI can be configured in both direct connection mode and via an existing remote connection in modem connection mode. The following describes the method for assigning parameters. Requirement A TS Adapter MPI is connected to your computer and the folder "TS Adapter" is displayed in the project tree under "Online access". WinCC Basic V13.0 System Manual, 02/2014 4623 Using online and diagnostics functions 13.7 Establishing a remote connection with TeleService Procedure To assign the parameters for the TS Adapter MPI im Direktanschluss please proceed as follows: 1. Double-click the "Online access" folder in the project tree. 2. Open the required folder: - The "TS Adapter" folder for a direct connection. - For an existing remote connection, the "TeleService" folder followed by the folder with the required system name. 3. Select the command "Assign TS Adapter MPI parameters". The "Assign TS Adapter MPI parameters" dialog opens. 4. Set the required parameters in the individual tabs of the dialog. 5. Confirm your entries with "OK". Result The configured parameters are saved in the non-volatile memory of the TS Adapter MPI. Parameter assignment is then complete. Restoring default parameter assignment for TS adapter MPI Introduction You can restore the default, factory state parameters of the TS Adapter MPI. Requirement A TS Adapter MPI is connected to your computer and is displayed in the project tree under "Online access" in the "TeleService" folder. Procedure Proceed as follows to restore default parameters for the TS Adapter MPI: 1. Open the "TeleService" folder in project tree. 2. Double-click the "TS Adapter MPI" folder. 3. Select the command "Assign TS Adapter MPI parameters". The "Assign TS Adapter MPI parameters" dialog opens. 4. Click the "Reset" button under "General". 5. Confirm your entries with "OK". 4624 WinCC Basic V13.0 System Manual, 02/2014 Using online and diagnostics functions 13.7 Establishing a remote connection with TeleService Result The TS Adapter MPI default parameters set on delivery are restored. See also TS adapter MPI configuration options (Page 4622) Exporting adapter parameters Introduction You can export the configuration of a TS Adapter MPI to an external file. The configuration saved in this file can be imported in turn into any number of TS Adapter MPI. This can for example be useful if you want to assign identical parameters to multipleTS Adapter MPI or if you want save, document or distribute the parameter set. Requirement A TS Adapter MPI is connected to your computer and is displayed in the project tree under "Online access" in the "TeleService" folder. Procedure To export the adapter parameters of a TS Adapter MPI: 1. Open the "TeleService" folder in project tree. 2. Double-click the "TS Adapter MPI" folder. 3. Select the command "Assign TS Adapter MPI parameters". The "Assign TS Adapter MPI parameters" dialog opens. 4. Click the "Export" button. 5. A window will open in which you can select the file to which you wish to export the configuration of the TS Adapter MPI. 6. Confirm with "Save". Result The parameters of the TS Adapter MPI are saved in the specified file (*.tap). The export of the adapter parameters is now complete. WinCC Basic V13.0 System Manual, 02/2014 4625 Using online and diagnostics functions 13.7 Establishing a remote connection with TeleService Importing adapter parameters Introduction You can import the configuration of a TS Adapter MPI from a previously created export file (*.tap). The configuration saved in this file can be imported into any number of TS Adapter. This can for example be useful if you want to assign identical parameters to multiple TS Adapter MPI. You can import parameters locally in direct connection mode or via an existing remote connection in modem connection mode. Requirement A TS Adapter MPI is connected to your computer and is displayed in the project tree under "Online access" in the "TeleService" folder. Procedure To import the adapter parameters of a TS Adapter MPI: 1. Open the "TeleService" folder in project tree. 2. Double-click the "TS Adapter MPI" folder. 3. Select the command "Assign TS Adapter MPI parameters". The "Assign TS Adapter MPI parameters" dialog opens. 4. Click the "Import" button. 5. A dialog will open in which you can select the file to which you wish to import the configuration of the TS Adapter MPI. 6. Confirm the next dialog with "Yes". Result The parameters selected are saved in the non-volatile memory of the TS Adapter MPI. Adapter parameter import is then complete. 13.7.3.5 TS adapter IE Short description of the TS adapter IE TS Adapter IE The designation "TS Adapter IE" is a collective term for allTS Adapter with an Ethernet port. The TS Adapter IE comes in the following versions: 4626 WinCC Basic V13.0 System Manual, 02/2014 Using online and diagnostics functions 13.7 Establishing a remote connection with TeleService as TS Adapter IE Standard as TS Adapter IE Basic The tables below provide a short description of the functionalities. For detailed information on your TS Adapter, please refer to the documentation supplied with it. TS Adapter IE Standard: Direct connection by means of Industrial Ethernet (IE). Firmware update possible. Modem integrated or external. The TS Adapter IE cannot automatically switch between modems like the TS Adapter II. Parameters are assigned via a Web interface. There are 2 variants: With internal analog modem. An external modem can also be connected to the RS232 port. With internal ISDN adapter. An external modem can also be connected to the RS232 port. TS Adapter IE Basic: Direct connection by means of Industrial Ethernet (IE). Firmware update possible. Plug-in modules. Parameters are assigned via a Web interface. There are 4 variants: TS Adapter IE Basic MODEM: Basic device TS Adapter IE Basic with TS Module MODEM for operation on the analog telephone network. TS Adapter IE Basic ISDN: Basic device TS Adapter IE Basic with TS Module ISDN for operation on ISDN telephone systems. TS Adapter IE Basic GSM: Basic device TS Adapter IE Basic with TS Module GSM for operation on the GSM radio network. TS Adapter IE Basic RS232: Basic device TS Adapter IE Basic with TS Module RS232 for connecting an external modem. Use of the designation "TS Adapter" "TS Adapter" is used in the TeleService online help as a general designation for all versions. The relevant product designation is listed beside information which only applies to a specific version of a TS Adapter, e.g. "TS Adapter I", "TS Adapter II", "TS Adapter IE Standard" or "TS Adapter IE Basic". How the TS adapter IE works How the TS Adapter IE works The TS Adapter IE connects the telephone network or the serial port of a modem with the Industrial Ethernet of your automation system. The TS Adapter IE has a non-volatile memory. Parameters for the following functions are stored in this memory: WinCC Basic V13.0 System Manual, 02/2014 4627 Using online and diagnostics functions 13.7 Establishing a remote connection with TeleService The mode of the modem used The serial port to the modem Access protection Default parameter assignment The TS Adapter IE comes with default parameter assignment. The parameters can be set and saved to the non-volatile memory of the TS adapter in a parameter assignment session. Note For more detailed information on the configuration of your TS Adapter, please refer to the documentation supplied with it. Connection Types Connection types of the TS Adapter IE Basic The following diagrams show the connection types possible with the TS Adapter IE Basic. Direct connection In the direct connection to the PG/PC, you can set the TS Adapter IE Basic through Ethernet. Note The operation of the TS Adapter IE Basic without a TS module is not permitted. 760RGXO 76$GDSWHU,(%DVLF 3*3& (WKHUQHW Figure 13-1 4628 Direct connection WinCC Basic V13.0 System Manual, 02/2014 Using online and diagnostics functions 13.7 Establishing a remote connection with TeleService Connection to the telephone network In order to have a direct connection to the telephone network, you must connect the TS Adapter IE Basic together with one of the following TS modules: TS Module Modem TS Module ISDN 760RGXOH0RGHP 760RGXOH,6'1 76$GDSWHU,(%DVLF $XWRPDWLRQV\VWHP 0RGHP :$1 (WKHUQHW 3*3& Figure 13-2 Direct connection to the telephone network More information about the TS modules can be found in the TS Adapter modular manual. Connection to the GSM network In order to connect to the GSM network, you must operate the TS Adapter IE Basic together with this TS module: TS Module GSM 760RGXOH*60 76$GDSWHU,(%DVLF $XWRPDWLRQV\VWHP 0RGHP (WKHUQHW 3*3& Figure 13-3 Connection to the GSM network More information about the TS modules can be found in the TS Adapter modular manual. WinCC Basic V13.0 System Manual, 02/2014 4629 Using online and diagnostics functions 13.7 Establishing a remote connection with TeleService Connection to the telephone network through an external modem For the connection to an external modem, you must operate the TS Adapter IE Basic together with this module: TS Module RS232 760RGXOH56 76$GDSWHU,(%DVLF $XWRPDWLRQV\VWHP 0RGHP :$1 0RGHP (WKHUQHW 3*3& Figure 13-4 Connection to an external modem More information about the TS modules can be found in the TS Adapter modular manual. TS Adapter IE parameter assignment options Useful information for configuring the TS Adapter IE The TS Adapter IE is configured via a Web interface. Web help associated with the parameter assignment interface is made available for the configuring the TS Adapter IE. The following parameter assignment options are available: Reconfiguration Restoring default parameter assignment Importing adapter parameters Exporting adapter parameters Note Parameter assignment Configure your TS Adapter in accordance with the documentation supplied with the TS Adapter. It will detail the exact procedure for parameter assignments. 4630 WinCC Basic V13.0 System Manual, 02/2014 Using online and diagnostics functions 13.7 Establishing a remote connection with TeleService Parameter assignment for TS Adapter IE Introduction The TS Adapter IE can be configured in both direct connection mode and via an existing remote connection in modem connection mode. Both parameter assignment options are described below. Specific details for assigning parameters of the TS Adapter IE can be obtained from the TS Adapter IE documentation. Parameter assignment of the TS Adapter IE in direct connection Requirement There is a LAN connection to your TS Adapter IE . The TS Adapter IE Basic is connected to the power supply. Procedure To assign the parameters for the TS Adapter IE , proceed as follows: 1. In the project tree of the TIA portal, open the "Online access" folder. 2. Double-click on the Ethernet port of your computer. 3. Double-click on the "Display accessible nodes" command. The TS Adapter IE is then displayed. 4. Double-click on the <TS Adapter IE> folder and then on "Online and diagnostic", and assign the desired IP address to the TS Adapter IE in the following dialogs. Please note that the IP address of the PG/PC interface card is located in the same subnet as the IP address that you issue for the TS Adapter IE. 5. Update the view in the project tree for the "Accessible nodes", so that the TS Adapter IE is displayed with the newly allocated IP address. 6. Open the folder <TS Adapter IE> in the device list. 7. Double-click the command "Assign TS Adapter IE parameters". The allocated web interface opens for assigning the TS Adapters IE parameters. 8. Complete the "logon" for the web interface. 9. Set the required parameters in the individual tabs of the dialog. 10.Confirm your entries with "Save settings". Result The configured parameters are saved in the non-volatile memory of the TS Adapter IE. Parameter assignment is then complete. WinCC Basic V13.0 System Manual, 02/2014 4631 Using online and diagnostics functions 13.7 Establishing a remote connection with TeleService Parameter assignment of the TS Adapter IE using a remote connection Requirement There is an established remote connection to a TS Adapter IE . Procedure 1. In the project tree of the TIA portal, open the "Online access" folder. 2. Open the "TeleService" folder followed by the required system folder. 3. Double-click the command "Assign TS Adapter IE parameters". The associated web interface for assignment of the TS Adapter IE parameters opens. The "logon" for the web interface takes place automatically with the login data of the remote connection. 4. Set the required parameters in the individual tabs of the dialog. 5. Confirm your entries with "Save settings". Result The configured parameters are saved in the non-volatile memory of the TS Adapter IE. Parameter assignment is then complete. 13.7.3.6 Establishing a dial-up connection to a remote system Establishing a dial-up connection Introduction to establishing a remote dial-up connection A dial-up connection is established when you use TeleService to dial into a remote system via a telephone network. The programming device/personal computer is connected to the telephone network with TeleService via a modem. At the other end, the automation system is connected to the telephone line via a configured TS Adapter and a modem. Requirements A local modem is installed and configured. The TS Adapter is located in the remote system. A remote modem is installed and parameters have been assigned. 4632 WinCC Basic V13.0 System Manual, 02/2014 Using online and diagnostics functions 13.7 Establishing a remote connection with TeleService Proceed as follows: 1. In the project tree of the TIA portal, open the "Online access" folder. 2. Click on the "TeleService" folder it contains. 3. Double-click the "Set up/close remote connection" entry. The "Set up remote connection to the remote system" dialog opens. 4. In the "Adapter type" drop-down list, select the adapter type used. 5. Under "Connection type", select "Dial-up connection". 6. Select the modem you are using under "Local settings". 7. Enter the phone number to be dialed in the appropriate box or open the phone book by clicking on the button behind it and take the desired phone number from the phone book. 8. Enter your user name and the corresponding password. 9. If you want a "Connection setup with callback", select the appropriate option button. 10.Click the "Connect" button to establish the required remote connection. This button only becomes active when you have entered all the parameters needed to establish a remote connection. Any remote connection is displayed under "Status". Result The dial-up connection to the desired system is established. The dialog closes as soon as the dial-up connection is established. The following message appears in the TIA Portal status bar: "Remote connection is established". You can now use the remote connection with TIA Portal and communicate with the automation system. Connection cannot be established If the connection cannot be established, try to find the cause using the "Notes on troubleshooting". Terminating the connection Once you have finished editing the remote system, exit the remote connection in the project tree by double-clicking on the entry "Establish/disconnect remote connection". By exiting the TIA Portal you are also terminating the remote connection. WinCC Basic V13.0 System Manual, 02/2014 4633 Using online and diagnostics functions 13.7 Establishing a remote connection with TeleService Terminating a dial-up connection Terminating an active dial-up connection Note Terminating the dial-up connection You should go offline in the TIA Portal before you terminate the remote connection. Proceed as follows: 1. Double-click the "Set up/close remote connection" entry in the TIA portal. 2. Confirm the prompt in the dialog that follows with "Yes". Result The connection is terminated. 13.7.4 Remote VPN connections 13.7.4.1 Basics for establishing a VPN connection Using a TS Adapter IE Advanced for VPN connections A TS Adapter IE Advanced is required to establish a VPN connection using TeleService. VPN definition VPN stands for "Virtual Private Network". This is a private network of computers based on a public network infrastructure. VPN is used to create a connection that is as secure as possible between devices in a private network at different locations and the gateway of another network. A VPN device has direct access to the gateway in the other network over an encrypted connection. 4634 WinCC Basic V13.0 System Manual, 02/2014 Using online and diagnostics functions 13.7 Establishing a remote connection with TeleService VPN connections When a VPN connection is established with TeleService, a CA certificate and a unique fingerprint generated from it are used for the unique identification of the TS Adapter IE Advanced. The VPN connection allows a communication that is secure from tapping and manipulation between the remote PC and the TS Adapter. If you want to establish a VPN connection to multiple remote networks, you will require a separate TS Adapter IE Advanced as an interface for each network. The networks connected by the TS Adapter can used identical IP addresses internally. Only the external IP addresses (WAN) of the TS Adapters need to be different. Only one VPN connection to a TS Adapter is possible at any one time. Note Authentication Please not that the CA certificate exclusively authenticates the TS Adapter IE Advanced. As in the case of dial-up connections, users are authenticated via the login (user name and password). Therefore, use only a secure password for the login. See also Establishing VPN connections (Page 4640) Terminating VPN connections (Page 4642) 13.7.4.2 Basics of CA certificates Introduction To establish a secure VPN connection with TeleService, you need to generate a CA certificate with a unique fingerprint when you configure the TS Adapter IE Advanced. You can install this CA certificate as follows on each PC which is to access the TS Adapter IE Advanced: Using the automatic download in the TeleService connection dialog, by entering the fingerprint for the CA certificate Manually by using the Microsoft(R) Management Console. Definition of CA certificate A CA certificate is a digital certificate issued by a "certificate authority" or "certification authority", hereinafter referred to as "CA". In the case of the TS Adapter IE Advanced, selfsigned certificates are used; the certification authority in this case is the TS Adapter IE Advanced itself. WinCC Basic V13.0 System Manual, 02/2014 4635 Using online and diagnostics functions 13.7 Establishing a remote connection with TeleService Certificates for "SSTP" (Secure Socket Tunneling Protocol) and "HTTPS" (Hypertext Transfer Protocol Secure) are derived from the CA certificate. CA certificates contain a "key" and additional information used for authentication and for encrypting and decrypting confidential data. Additional information includes the validity period, references to certificate revocation lists, etc. which are included in the certificate by the CA. Using CA certificates with TeleService A CA certificate with a unique fingerprint is generated by the TS Adapter to uniquely identify the TS Adapter IE Advanced as connection partner for the remote PC. This CA certificate must be saved in the Windows certificate store of your programming device/ PC before you can establish a VPN connection. When you access the Web server using a direct connection, a security warning will appear if no CA certificate exists. In such cases, however, you can choose to ignore the warning and allow the connection. Note Handling CA certificates Specialist knowledge of the operating system is required for handling CA certificates. CA certificates should only be managed by trained personnel! You require administrator rights to manage CA certificates. Definition of fingerprint The fingerprint is a 20-byte hexadecimal expression. It provides a unique value for a CA certificate and is used to identify a specific CA certificate. A fingerprint is calculated dynamically using the SHA-1 algorithm and is not physically contained in the CA certificate. Use of fingerprints with TeleService The CA certificate is used to uniquely identify the TS Adapter IE Advanced as connection partner. A unique 20-byte fingerprint of this certificate is generated each time a CA certificate is generated by the TS Adapter IE Advanced. It is calculated automatically by the TS Adapter IE Advanced when the certificate is generated. Each certificate has a specific, unique fingerprint. This fingerprint must be transferred securely to your computer, for example by phone or in an encrypted e-mail. You need to enter this fingerprint in the connection dialog when establishing a VPN connection with TeleService, unless the CA certificate is already saved on your PC in the Windows certificate store. You will find the fingerprint for your TS Adapter IE Advanced in the Web interface for the TS Adapter IE Advanced. To open the Web interface, double-click the command "Assign TS Adapter IE Advanced parameters" in the device list in the TIA portal. Carry out the Web login to view the fingerprint in the "Security > Certificates" tab. 4636 WinCC Basic V13.0 System Manual, 02/2014 Using online and diagnostics functions 13.7 Establishing a remote connection with TeleService CA certificate download during connection establishment When the connection is established, TeleService checks whether a suitable CA certificate is installed in the Windows certificate store of your programming device/PC. If an appropriate certificate is found, the VPN connection is established as an SSTP connection (Secure Socket Tunneling Protocol). If no appropriate CA certificate is found, the CA certificate is first loaded by the corresponding TS Adapter IE Advanced. The TS Adapter IE Advanced is called by the remote address entered in the connection dialog. If this download of the CA certificate is successful, the fingerprint of the downloaded CA certificate is calculated and compared with the fingerprint entered in the connection dialog. If the two fingerprints match, a dialog opens and you are prompted to save the CA certificate in the Windows certificate store of your programming device/PC. You require administrator rights to save the CA certificate. The VPN connection is then established. See also Installing CA certificates for VPN connections (Page 4637) Deleting CA certificates for VPN connections (Page 4640) 13.7.4.3 Installing CA certificates for VPN connections Installing CA certificates To establish a secure VPN connection between your programming device/PC and a remote system with TeleService, you require a valid CA certificate generated by the TS Adapter IE Advanced. This must be saved in the Windows certificate store of your programming device/ PC. A CA certificate can be installed manually or using an automatic download. CA certificates are managed with the Microsoft(R) Management Console. Note Handling CA certificates Specialist knowledge of the operating system is required for handling CA certificates. CA certificates should only be managed by trained personnel! You require administrator rights to manage CA certificates! Requirement A CA certificate has yet to be installed in the Windows certificate store on your computer. WinCC Basic V13.0 System Manual, 02/2014 4637 Using online and diagnostics functions 13.7 Establishing a remote connection with TeleService Installing CA certificates using the automatic download Proceed as follows: 1. Log on to the system as administrator. 2. Transfer the fingerprint for the CA certificate from the TS Adapter IE Advanced to your computer using a "secure route", for example by phone or in an encrypted e-mail. You will find the fingerprint for your TS Adapter IE Advanced in the Web interface for the TS Adapter IE Advanced. To open the Web interface, double-click the command "Assign TS Adapter IE parameters" in the device list in the TIA portal. Perform the Web login to view the fingerprint in the "Security > Certificates" tab. 3. In the project tree of the TIA portal, open the "Online access" folder. 4. Click on the "TeleService" folder it contains. 5. Double-click the "Set up/close remote connection" entry. The "Set up remote connection to the remote system" dialog opens. 6. Select the "TS Adapter IE Advanced" as Adapter type from the drop-down list. 7. Under "Connection type", select "VPN". 8. In the relevant input box, enter the IP address / DNS name for the TS Adapter IE Advanced to be contacted. Alternatively, you can apply any existing data from the phone book by clicking the corresponding button. 9. Enter your user name and the corresponding password. 10.Copy the fingerprint displayed in the Web interface for the TS Adapter IE Advanced to the "Fingerprint" column. 11.Click the "Connect" button to establish the required remote connection. This button only becomes active when you have entered all the parameters needed to establish a remote connection. 12.No valid CA certificate is found, because no CA certificate has been installed on your PC yet. A "normal" connection (not a VPN connection) is therefore established and the certificate required is downloaded from the TS Adapter IE Advanced to the working memory of your computer. The fingerprint is then calculated (SHA-1 algorithm) and compared with the fingerprint entered in the connection dialog. If the two fingerprints match, a dialog opens and you are prompted to save the CA certificate in the Windows certificate store of your programming device/PC. 13.Confirm that you want to save the CA certificate. Result The VPN connection to the required TS Adapter IE Advanced is established. The dialog closes once the connection is established. 4638 WinCC Basic V13.0 System Manual, 02/2014 Using online and diagnostics functions 13.7 Establishing a remote connection with TeleService Manual installation of CA certificates Proceed as follows: 1. Log on to the system as administrator. 2. Open the Windows Certificate Manager on your programming device/PC with the Microsoft(R) Management Console. Click "Start", enter "mmc" in the search field and press ENTER. The console will open. 3. Open the "File" menu and click "Add/remove snap-in...". The "Add/remove snap-in..." dialog will open. 4. Double-click "Certificates" in the "Snap-in" list and select "Computer account" in the dialog that opens. 5. Select "Local computer" in the next dialog and click "Finish" and "OK". The console root opens and the "Certificates (local computer)" folder appears. 6. Open the displayed "Certificates (local computer)" folder and click "Trusted certification authorities". 7. Click the "Certificates " folder and use the shortcut menu to access the command "All tasks" > "Import...". 8. Note the information that appears in the "Certificate - Import wizard" dialog and click "Next". 9. In the dialog that follows, click "Browse ..." and select the required CA certificate. 10.Then click "Next" twice and subsequently "Finish" to install the CA certificate. Result The selected CA certificate is installed at the specified location in the Windows certificate memory. Note Additional information ... ... on installing CA certificates can be found using the "F1" button in the online help of your operating system. WinCC Basic V13.0 System Manual, 02/2014 4639 Using online and diagnostics functions 13.7 Establishing a remote connection with TeleService 13.7.4.4 Deleting CA certificates for VPN connections Deleting CA certificates Proceed as follows: 1. Log on to the system as administrator. 2. Open the Windows Certificate Manager on your programming device/PC with the Microsoft(R) Management Console. Click "Start", enter "mmc" in the search field and press the ENTER KEY. The console will open. 3. Open the "File" menu and click "Add/remove snap-in...". The snap-in selection dialog will open. 4. Double-click "Certificates" in the "Snap-in" list and select "Computer account" in the dialog that opens. 5. Select "Local computer" in the next dialog and click "Finish" and "OK". The console root opens and the "Certificates (local computer)" folder appears. 6. Open the displayed "Certificates (local computer)" folder and click "Trusted certification authorities". 7. Open the "Certificates" folder, select the required CA certificate and click "Delete" in the shortcut menu. 8. Confirm the next prompt with "Yes". Result The selected CA certificate is deleted from the list of available certificates. 13.7.4.5 Establishing a VPN connection to a remote system Establishing VPN connections Introduction to establishing VPN connections A VPN connection is established when you use TeleService to connect to a remove system over the Internet. To do this, your programming device/PC with installed TIA Portal is connected to the Internet at one end. At the other end, the automation system is connected to the Internet via the WAN (Wide Area Network) interface of the configured TS Adapter IE Advanced. Requirement Your programming device/PC is connected to the Internet. There is a TS Adapter IE Advanced in the remote system. 4640 WinCC Basic V13.0 System Manual, 02/2014 Using online and diagnostics functions 13.7 Establishing a remote connection with TeleService The TS Adapter IE Advanced has been configured and is connected to the Internet. The CA certificate required for identifying the TS Adapter has been generated and installed in the Windows certificate store of your programming device/PC. Proceed as follows: 1. In the project tree of the TIA portal, open the "Online access" folder. 2. Click on the "TeleService" folder it contains. 3. Double-click the "Set up/close remote connection" entry. The "Set up remote connection to the remote system" dialog opens. 4. Select the "TS Adapter IE Advanced" as "Adapter type" from the drop-down list. 5. Enter "VPN" as "connection type". 6. Enter the IP address / DNS name for the TS Adapter IE Advanced to be contacted in the relevant field. Alternatively, you can apply any existing data from the phone book by clicking the corresponding button. 7. Enter your user name and the corresponding password. 8. Click the "Establish" button to establish the required VPN connection. This button only becomes active once you have entered all the parameters needed for establishing the remote connection. Result The VPN connection to the required system is established. "Status" indicates the progress in establishing the connection. The dialog closes once the VPN connection is established. The following message appears in the TIA Portal status bar: "Remote connection is established". You can now use the remote connection with TIA Portal and communicate with the automation system. Connection cannot be established If the connection cannot be established, try to find the cause using the "Notes on troubleshooting". Note Rules for IP addresses Only use IP addresses which have not yet been assigned in the system network. If the IP address configured for the TS Adapter IE Advanced has already been assigned in the system network, the TS Adapter IE Advanced can only be addressed by its MAC address. WinCC Basic V13.0 System Manual, 02/2014 4641 Using online and diagnostics functions 13.7 Establishing a remote connection with TeleService See also Installing CA certificates for VPN connections (Page 4637) Terminating VPN connections Terminating an active VPN connection Note Terminating the VPN connection You should go offline in the TIA portal before you terminate the VPN connection. Proceed as follows: 1. Double-click the "Set up/close remote connection" entry in the TIA portal. 2. Confirm the prompt in the dialog that follows with "Yes". Result The VPN connection is terminated. 13.7.4.6 TS Adapter IE Advanced Short description of the TS Adapter IE Advanced TS Adapter IE Advanced The TS Adapter IE Advanced has the following properties: Direct connection over Industrial Ethernet (IE), 2 ports WAN (Wide Area Network) interface for VPN connections Firmware update supported Plug-in modules Parameters are assigned via a Web interface. 4642 WinCC Basic V13.0 System Manual, 02/2014 Using online and diagnostics functions 13.7 Establishing a remote connection with TeleService Note Further information on the TS Adapter IE Advanced For detailed information on your TS Adapter, please refer to the documentation supplied with your TS Adapter. Connection types TS Adapter IE Advanced connection types The following diagrams show the types of connection possible with the TS Adapter IE Advanced. Direct connection In the direct connection to the programming device/PC, you can set the TS Adapter IE Advanced parameters over the Ethernet. 760RGXOH 76$GDSWHU,($GYDQFHG 3*3& (WKHUQHW Figure 13-5 WinCC Basic V13.0 System Manual, 02/2014 TS Adapter IE Advanced - direct connection 4643 Using online and diagnostics functions 13.7 Establishing a remote connection with TeleService Connection to the Internet (DSL modem/router) In order to connect to the Internet, you must operate the DSL modem/router at the WAN connection of the TS Adapter IE Advanced. 760RGXOH 76$GDSWHU,($GYDQFHG :$1 '6/ 0RGHP5RXWHU (WKHUQHW Figure 13-6 TS Adapter IE Advanced - connection to the Internet Connection to the company network (Intranet) In order to connect to the Intranet, you must operate system network (Ethernet) at one of the two LAN connections of the TS Adapter IE Advanced. 760RGXOH 76$GDSWHU,($GYDQFHG (QJLQHHULQJ6WDWLRQ 2SHUDWRU6WDWLRQ 6HUYHU (WKHUQHW $XWRPDWLVLHUXQJVV\VWHPH Figure 13-7 TS Adapter IE Advanced - connection to company network (Intranet) Additional information For more detailed information on the TS modules, please refer to the documentation supplied with your TS Adapter IE Advanced. TS Adapter IE Advanced parameter assignment options Basics on configuring the TS Adapter IE The TS Adapter IE Advanced is configured via a Web interface. Web help in the Web interface is available for assigning TS Adapter IE Advanced parameters. Parameter assignment options include: 4644 WinCC Basic V13.0 System Manual, 02/2014 Using online and diagnostics functions 13.7 Establishing a remote connection with TeleService Reconfiguration Restoring default parameter assignment Importing adapter parameters Exporting adapter parameters Note Parameter assignment Configure your TS Adapter IE Advanced in accordance with the documentation supplied. This details the exact procedure for parameter assignment. Parameter assignment for TS Adapter IE Advanced Introduction The TS Adapter IE Advanced can be configured in both direct connection mode and via an existing remote connection. Both parameter assignment options are described below. Specific details on assigning parameters for the TS Adapter IE Advanced are available in the TS Adapter IE Advanced documentation. Assigning parameters for the TS Adapter IE Advanced in direct connection Requirement There is a LAN connection to your TS Adapter IE Advanced. Procedure To assign the parameters for the TS Adapter IE Advanced, proceed as follows: 1. In the project tree of the TIA portal, open the "Online access" folder. 2. Double-click on the Ethernet port of your computer. 3. Double-click on the "Display accessible nodes" command. The TS Adapter IE Advanced is then displayed. 4. Double-click on the "TS Adapter IE Advanced" folder and then on "Online and diagnostics", and assign the desired IP address to the TS Adapter in the dialogs that follow. Please note that the IP address of the programming device/PC interface card must be located in the same subnet as the IP address that you assign for the TS Adapter IE Advanced. 5. Update the view in the project tree for the "Accessible nodes", so that the TS Adapter IE Advanced is displayed with the newly assigned IP address. WinCC Basic V13.0 System Manual, 02/2014 4645 Using online and diagnostics functions 13.7 Establishing a remote connection with TeleService 6. Open the folder "TS Adapter IE Advanced" in the device list. 7. Double-click the command "Assign TS Adapter IE parameters". The corresponding Web interface opens for assigning TS Adapter IE Advanced parameters. 8. Complete the "logon" for the web interface. 9. Set the required parameters in the individual tabs of the dialog. 10.Confirm your entries with "Save settings". Result The configured parameters are saved in the non-volatile memory of the TS Adapter IE Advanced. Parameter assignment is then complete. Assigning parameters for the TS Adapter IE Advanced using a remote connection Requirement There is an established remote connection to a TS Adapter IE Advanced.. Procedure 1. In the project tree of the TIA Portal, open the "Online access" folder. 2. Open the "TeleService" folder followed by the required plant folder. 3. Double-click the command "Assign TS Adapter IE parameters". The associated web interface for assignment of the TS Adapter IE parameters opens. The "logon" for the web interface takes place automatically with the login data of the remote connection. 4. Set the required parameters in the individual tabs of the dialog. 5. Confirm your entries with "Save settings". Result The configured parameters are saved in the non-volatile memory of the TS Adapter IE Advanced. Parameter assignment is then complete. 4646 WinCC Basic V13.0 System Manual, 02/2014 Using online and diagnostics functions 13.7 Establishing a remote connection with TeleService 13.7.5 CPU controlled TeleService remote connections 13.7.5.1 Overview of CPU controlled remote connections Introduction TeleService offers a range of options for establishing remote connections; these differ according to the CPU used. The initiative for establishing a connection starts from the CPU. The communications instructions given below are used for the individual connection options. Connection establishment with S7-300/400 CPUs The following communications instructions are available: Communications instruction "PG_DIAL": Establish remote connection to programming device/PC Communications instruction "SMS_SEND": Send text message (SMS) Communications instruction "AS_DIAL": Establish remote connection to AS Communications instruction "AS_MAIL": Transfer email Connection establishment with S7-1200 CPUs The following communications instruction is available: Communications instruction "TM_MAIL": Transfer email Connection establishment with S7-1500 CPUs The following communications instruction is available: Communications instruction "TMAIL_C": Transfer email Note Description of individual communications instructions More detailed information on the available communications instructions can be found in the information system of the TIA Portal in the directory "References > Communication > TeleService". See also TS Adapter IE parameter assignment options (Page 4630) WinCC Basic V13.0 System Manual, 02/2014 4647 Using online and diagnostics functions 13.7 Establishing a remote connection with TeleService 13.7.5.2 Establishing a connection from and to remote systens (PG-AS-remote coupling) Remote plant access to a programming device/personal computer Introduction You can establish a remote connection to and communicate with a remote system using the application TeleService and a TS Adapter MPI. The initiative for establishing the remote connection comes from the programming device/personal computer. However, events which require rapid intervention often occur at a remote system. In such cases, the automation system can initiate a remote connection to a programming device/ personal computer if an asynchronous event occurs. The graphic below shows the components which are required for establishing a connection from a plant to a programming device/personal computer. $XWRPDWLRQV\VWHP 6& &38 3URJUDPPLQJGHYLFH3& 8VHUSURJUDP 8VHUSURJUDP 352'$9($3,9 3*B',$/LQVWUXFWLRQ 5HPRWHFRQQHFWLRQ 6EDVLFFRPPXQLFDWLRQ 76b$GDSWHU 7HOH6HUYLFH 5HPRWHOLQN 0RGHP 7HOHSKRQHQHWZRUN 0RGHP 03,QHWZRUN Figure 13-8 How the "PG_DIAL" communications instruction works Requirements for establishing a connection Introduction Certain hardware and software requirements must be fulfilled if a remote system is to establish a remote connection to a programming device/personal computer. These requirements are detailed below. Hardware requirements: The only hardware required for establishing a remote connection from a remote system to a programming device/personal computer is that needed for accessing the remote system from the programming device/personal computer. 4648 WinCC Basic V13.0 System Manual, 02/2014 Using online and diagnostics functions 13.7 Establishing a remote connection with TeleService Your user program calls the communication instruction "PG_DIAL" to establish the connection. This can only be executed on an S7-300 or S7-400 CPU on which S7 basic communication is implemented. A TS Adapter I , version 5.0 or later, or a TS Adapter II must be used. Software requirements at the plant end: Communication instruction "PG_DIAL" is included in the TeleService scope of delivery and is installed when the TIA portal is installed. You will find the communication instructions installed in the "Communication > TeleService" folder of the block editor task card. If a remote system is to establish a remote connection to a programming device/personal computer, the plant user program must call the "PG_DIAL" function block. Software requirements for the programming device/personal computer You require a software product in the programming device/personal computer which, with TeleService, waits for a call from a remote system, recognizes this call and informs your user program. 13.7.5.3 Data exchange between remote systems (AS-AS-remote coupling) AS-AS remote link basics Introduction The AS-AS remote link allows two automation systems to exchange process data via the telephone network. Requirement Communication instruction "AS_DIAL" is available if you use a CPU from the S7-300/400 family. Definition: Local and remote automation system The automation system from which the initiative to establish the remote connection originates is described as local. The automation system to which the remote connection is to be established is described as remote. Data exchange over the AS-AS remote link Data exchange is carried out using specific communication instructions for non-configured S7 connections. Use the communication instruction "AS_DIAL" to establish a remote connection to the automation system. WinCC Basic V13.0 System Manual, 02/2014 4649 Using online and diagnostics functions 13.7 Establishing a remote connection with TeleService More detailed information on establishing the connection can be found in the information system in the directory "References > Communication > TeleService". The following graphic shows the components required for establishing a connection from a local to a remote automation system. /RFDO DXWRPDWLRQV\VWHP 6& /RFDO&38 5HPRWH DXWRPDWLRQV\VWHP 6& 5HPRWH&38 8VHUSURJUDP 8VHUSURJUDP $6B',$/LQVWUXFWLRQ ;B5&9 5HPRWHFRQQHFWLRQ ;B6(1';B387 ;B*(7 /RFDO 76$GDSWHU /RFDO03,3' QHWZRUN Figure 13-9 /RFDO PRGHP 5HPRWH PRGHP 5HPRWH 76$GDSWHU 7HOHSKRQH QHWZRUN 5HPRWH03,3' QHWZRUN Data exchange over the AS-AS remote link Hardware and software requirements for AS-AS remote link Introduction Certain hardware and software requirements must be fulfilled before a local automation system can establish a remote connection to a remote automation system. These requirements are detailed below. Hardware requirements The only hardware you need for transferring process data from a local to a remote automation system is that also needed for accessing the respective automation system from the programming device/personal computer. To establish and terminate the remote connection, the TIA Portal user program of the local CPU calls a communication instruction. This communication instruction can be executed on an S7-300/400 CPU or a C7 CPU. The communication instruction requires S7 basic communication to be implemented on the CPU. The remote CPU must also support S7 basic communication. A TS Adapter I, version V5.1 or later, or a TS Adapter II must be used. 4650 WinCC Basic V13.0 System Manual, 02/2014 Using online and diagnostics functions 13.7 Establishing a remote connection with TeleService Software requirements The "AS_DIAL" communication instruction is included in the product package of TeleService, and is integrated into the library of the TIA Portal during the installation in the communication instructions folder of the Task Card under TeleService. In order to establish and terminate a remote connection to a remote automation system from a local automation system, call the communication instruction "AS_DIAL" in the TIA Portal user program of the local CPU. $6$6UHPRWHOLQN $XWRPDWLRQV\VWHP 6& $XWRPDWLRQV\VWHP 6& 8VHUSURJUDP 8VHUSURJUDP $6B',$/LQVWUXFWLRQ $6B',$/LQVWUXFWLRQ 6)&V 6)&V 03, 03, 76$GDSWHU 76$GDSWHU 0RGHP 7HOHSKRQH QHWZRUN 0RGHP Figure 13-10 Hardware and software requirements for AS-AS remote link 13.7.5.4 Send SMS from a system Requirements for sending an SMS Introduction Certain hardware and software requirements must be fulfilled before a system can send an SMS. These requirements are detailed below. Hardware requirements To send an SMS from a system, you will require a GSM wireless modem and a TS Adapter MPI. A TS Adapter I, version V5.2 or later, or a TS Adapter II must be used. WinCC Basic V13.0 System Manual, 02/2014 4651 Using online and diagnostics functions 13.7 Establishing a remote connection with TeleService Software requirements at the system end The "SMS_SEND" communications instruction is included in the scope of delivery of TeleService, and is integrated into the library of the TIA Portal during the installation in the communications instructions folder of the Task Card under TeleService. If a system is to send an SMS, the user program of the system must call the communications instruction "SMS_SEND". $XWRPDWLRQV\VWHP 6& &38 )D[ (PDLO 8VHUSURJUDP 606B6(1'LQVWUXFWLRQ 6EDVLFFRPPXQLFDWLRQ 76$GDSWHU :LUHOHVVPRGHP &HOO 03,QHWZRUN 7HOHSKRQHZLUHOHVV QHWZRUNDQG QHWZRUNSURYLGHU Figure 13-11 How the "SMS_SEND" communications instruction works Note You may be able to send an SMS not only to a cell phone but also to an email address or a fax device by using additional services offered by the cell phone service provider. 13.7.5.5 Send an email from a system Requirements for sending e-mails Introduction The following hardware and software requirements must be fulfilled if a system is to send an email: 4652 WinCC Basic V13.0 System Manual, 02/2014 Using online and diagnostics functions 13.7 Establishing a remote connection with TeleService Hardware requirements You need a TS Adapter IE to send an email from a system and one of the CPUs listed below: a CPU 31x2 PN/DP as of firmware version V2.5 a CPU 41x-3 PN/DP a CPU of the S7-1200 series a CPU of the S7-1500 series Software requirements at the system end Different communications instructions are included in the scope of delivery of TeleService depending on the CPU that are integrated into the library of the TIA Portal during the installation in the communications instructions folder of the Task Card under TeleService. If a system is to send an email, the user program of the system must call the corresponding communications instruction for the CPU. The following communications instructions are available for sending an email: S7-300/400 CPUs: use the communications instruction "AS_MAIL": Transfer email S7-1200 CPU V 2.0 and V 3.0: use the communications instruction "TM_MAIL": Transfer email S7-1200 CPU >V3.0: use the communications instruction "TMAIL_C": Transfer email S7-1500 CPUs: use the communications instruction "TMAIL_C": Transfer email The respective communications instruction transfers an email from a CPU to a mail server by means of the Simple Mail Transfer Protocol (SMTP) with the "LOGIN" authentication method. The data is transferred unencrypted with this SMTP process. The figure below shows an example with the communications instruction "AS_MAIL": WinCC Basic V13.0 System Manual, 02/2014 4653 Using online and diagnostics functions 13.7 Establishing a remote connection with TeleService (PDLO 8QLILHG0HVVDJLQJ ,63 $XWRPDWLRQV\VWHP 66&38 ,3 :$1,QWHUQHW ,63 8VHUSURJUDP $6B0$,/LQVWUXFWLRQ 2SHQFRPPXQLFDWLRQYLD,QGXVWULDO (WKHUQHW 76$GDSWHU ,QGXVWULDO(WKHUQHW ,3 ,QGXVWULDO(WKHUQHWORFDOQHWZRUN The "Use gateway/router" property must also be set for the Ethernet interface in the configuration of the CPU on which the communications instruction "AS_MAIL" runs. (available in the device configuration under Ethernet addresses and there under IP protocol)The IP address of the Ethernet interface of the TS Adapter IE is to be specified as "Address". Note You can find further information in the task card in the "Communications instructions" folder under TeleService. 4654 WinCC Basic V13.0 System Manual, 02/2014 Using online and diagnostics functions 13.7 Establishing a remote connection with TeleService 13.7.6 Notes on troubleshooting 13.7.6.1 General information on troubleshooting for modem problems Introduction The information below should help you establish and eliminate the causes of any modem problems. 1. Enable "Record log file" for data traffic between PG/PC and modem. The entries in this file can provide valuable information for determining the cause of errors. 2. Switch on the loudspeaker on your local modem. Select a volume loud enough to be clearly heard. You can then hear whether: - there is a dial tone at the connection - the modem called is busy - the modem called accepts the call. Common modem problems Modem connection problems are among the most common modem problems: Modem connection is not established Modem connection is interrupted The topics below contain tables detailing possible causes and providing information on eliminating the error in question. See also Dial-up connection to the TS Adapter is not established (Page 4656) Dial-up connection from the TS Adapter is not established (Page 4657) Modem connection is interrupted (Page 4658) Modem alarms (Page 4659) Recording a log file for the modem (Page 4655) 13.7.6.2 Recording a log file for the modem Introduction It is advisable to record a log file as this makes it easier to find the causes of faults in a modem. WinCC Basic V13.0 System Manual, 02/2014 4655 Using online and diagnostics functions 13.7 Establishing a remote connection with TeleService Procedure: Proceed as follows: 1. Activate the properties dialog of the modem used via the "Phone and modem options" option in the Control Panel. 2. Check the settings of the "Log" option in the "Diagnostics" tab and if necessary change the log file settings so that the file is recorded. Result: Activity between the programming device/personal computer and the modem are entered in the log file. If there are problems establishing the connection, you can evaluate the data recorded in the log file to determine the cause of the error. 13.7.6.3 Dial-up connection to the TS Adapter is not established Dial-up connection to TS Adapter is not established The table below sets out possible causes and how to eliminate them if no remote connection to the TS Adapter can be established. Possible cause Check/Remedy Cabling faulty Are all the connecting cables connected correctly? Are the connectors loose? Dial parameters for main telephone line and extension incorrectly set Do the properties and dial parameters of your modem match the phone connection to main phone line or extension? Do not specify a dial-out code in the "Dial parameters" dialog if you operate your modem on a local loop (main telephone line). The fields for the dial-out code for local calls and long-distance calls must be empty. Dialing mode incorrectly set Is the correct dialing mode (tone/pulse) set in the dialog for the dial parameters of your modem? Use a connected telephone to check the connection on which you want to operate the modem. You should hear crackling noises on the telephone during pulse dialing and tones of varying pitches during tone dialing. Set the corresponding dialing mode in the modem dial parameters. 4656 WinCC Basic V13.0 System Manual, 02/2014 Using online and diagnostics functions 13.7 Establishing a remote connection with TeleService Possible cause Check/Remedy Dial disable active The dial disable function is a country-specific modem property which, depending on the modem, becomes effective after one or more unsuccessful attempts to establish a connection. If your modem still does not respond after several attempts to dial, the dial disable function may be active. Characters are still sent to the modem after the dial command but the modem does not start the dialing process. The driver receives a general error message. Refer to the modem documentation for information on how the dial disable function is implemented for your modem. Create a log file (Page 4655) (modemlog.txt) in which the activities between the programming device/personal computer and modem are recorded. Then check whether the file contains an entry caused by dial disable (e.g. DELAYED). Phone connection defective or busy Connect a phone and check whether a dial tone can be heard on this connection. Any analog phone connected on the same connection must be hung up. You cannot establish an additional modem connection on this connection if there is an existing phone connection. Serial parameters set incorrectly Are the correct values entered in the "Settings" tab for modem properties (8 data bits, no parity, 1 stop bit)? Is the correct COM interface set in the "General" tab for the modem properties? Initialization string of the TS Adapter is not suitable for the modem. Familiarize yourself with the modem initialization string requirements and set the string accordingly. Procedure for configuring the TS Adapter IE (Page 4627) Settings for error correction between the modem at the TS Adapter and the modem at the PC/programming device are not compatible. Adapt the modem settings. Useful information on configuring the TS Adapter MPI (Page 4622) Restoring the default parameter assignment of a TS Adapter MPI (Page 4624) Procedure for configuring the TS Adapter IE (Page 4623) 13.7.6.4 Dial-up connection from the TS Adapter is not established No callback from TS Adapter The table below sets out possible causes and how to eliminate them if there is no callback from the TS Adapter. Possible cause Check/Remedy Errors in the location or call settings in the TS Adapter Check the TS Adapter parameter assignment: Are the dialing mode and dial-out code set correctly for your phone connection? Does the modem at the TS Adapter support the characters configured for the dialout code? Is "Wait for dial tone before dialing" deactivated for an extension? Initialization of modem insufficient Check the string for modem initialization: Callback number is incorrect Check the configuration of the callback number you assigned. The modem may require a further initialization in order to establish a remote connection. Properties of the modem initialization string for the TS Adapter MPI WinCC Basic V13.0 System Manual, 02/2014 4657 Using online and diagnostics functions 13.7 Establishing a remote connection with TeleService No call from TS Adapter MPI The table below sets out possible causes and and how to remedy them if there is no call from the TS Adapter MPI. Possible cause Check/Remedy Phone number is incorrect Is the required number being transferred to the communication instruction "PG_DIAL" ? TS Adapter MPI parameter assignment incorrect Check the TS Adapter MPI parameter assignment: Are the dialing mode and dial-out code set correctly for your phone connection? Does the modem at the TS Adapter MPI support the characters configured for the dial-out code? Is "Wait for dial tone before dialing" deactivated for an extension? 13.7.6.5 Modem connection is interrupted Modem connection is interrupted The table below sets out possible causes and and how to remedy them if the modem connection is interrupted. Possible cause: Check / Remedy: Metering pulses in the line Metering pulses will be generated if you have applied to the phone company for a metering clock. This may mean that the modem no longer recognizes the carrier signal and switches off. Set a longer waiting or switch-off time at the modem. Have the metering pulse deactivated by the phone company. Shielding Are the connection cables used shielded sufficiently? Make sure that the modem cables do not run next to power cables and that they are as far as possible from power supply units and monitors. Protocol timeout Set fixed monitoring times. Automatic connection termination Deactivate the option that terminates an existing connection automatically after a specified time without data transfer ("Terminate after idle of ..."). Data flow control deactivated Click on the "Extended" button in the "Settings" tab of the modem properties and activate the following options in the dialog displayed (if available and not yet set): Initialization string of the TS Adapter is not suitable for the modem - Data flow control - Hardware (RTS/CTS) - Data compression - Error control Set the modem initialization string in accordance with the following requirements. See also: TS Adapter IE parameter assignment options (Page 4630) See also TS adapter MPI configuration options (Page 4622) 4658 WinCC Basic V13.0 System Manual, 02/2014 Using online and diagnostics functions 13.7 Establishing a remote connection with TeleService 13.7.6.6 Checklist for troubleshooting the modem Introduction The following list should help you establish the potential cause of any problems with the modem. The help topics below set out how and in which dialogs you define the relevant settings. Modem connection cannot be established: Check the cabling and the connections. Check whether the correct dialing mode (tone/pulse) is set. If your modem does not react after several attempts to dial, a dial disable function may be active. Familiarize yourself with dial disable on your modem. Are you operating your modem on a main telephone line or on an extension line? Configure the properties and dialing parameters of the modem accordingly. Enable the log file option in the advanced properties. The next attempt to establish a connection will then be recorded in a file in the Windows directory. Ensure that the ISDN TAs used work with the same B and D channel protocol. The modem connection is terminated: Metering pulses can have a negative affect on a connection. Have the pulses deactivated by your telephone company. Set fixed monitoring times. Deactivate the option that terminates an existing connection automatically after a specified time without data transfer (idle). Make sure that you have activated RTS/CTS for data flow control. 13.7.6.7 Modem alarms Information in the log file The modem alarms are entered in a log file if you have activated the recording function. The log file contains the following information: Alarm: Possible cause: Remedy: NO DIALTONE A phone call may currently be being carried out on this line. Repeat the process once the phone call is over. NO CARRIER The device dialed is not ready, is not a modem or cannot establish a connection in the set operating mode. Check the numbers and the settings. WinCC Basic V13.0 System Manual, 02/2014 4659 Using online and diagnostics functions 13.7 Establishing a remote connection with TeleService Alarm: Possible cause: Remedy: BUSY The device dialed is busy. Try again later. DELAYED: ... Dial disable Refer to the modem documentation for information on how the dial disable function is implemented for your modem and if necessary remove it. 13.7.6.8 Possible error messages with VPN connections VPN connection to TS Adapter IE Advanced is not established The table below sets out possible errors and how to eliminate them if no VPN connection to the TS Adapter IE Advanced can be established. Possible errors Check/Remedy The error message "The webpage Note: This problem occurs when the Windows certificate store contains a CA cannot be displayed" appears when certificate with the same name as the CA certificate which has just been generated. the Web interface is accessed. If a CA certificate for this TS Adapter is already installed in the Windows certificate store and you have generated a new CA certificate on the TS Adapter, you need to remove the old CA certificate from the Windows certificate store and install the newly generated CA certificate. See also: Installing CA certificates for VPN connections (Page 4637) See also: Deleting CA certificates for VPN connections (Page 4640) Error message: "Unexpected error in application". Check whether other users have been saved in the TS Adapter IE Advanced user database. The user "Administrator" cannot establish a remote connection. Error message: "No corresponding CA certificate was found in the Windows certificate store". Use the automatic certificate download. Enter the fingerprint in the corresponding field in the connection dialog. See also: Establishing VPN connections (Page 4640) Or Export the CA certificate from the Web interface of the TS Adapter IE Advanced and install it manually in the Windows certificate store. See also: Installing CA certificates for VPN connections (Page 4637) Error message: "The remote address specified does not correspond to the remote address of the TS Adapter". You must use the remote address which you specified in the TS Adapter IE Advanced to establish the connection. You cannot use the IP address if you have entered the DNS name (and vice versa). Error message: "The signature of If you have generated a new CA certificate on the TS Adapter IE Advanced, you the certificate could not be verified". need to delete the old CA certificate from the Windows certificate store and install the new one. See also: Deleting CA certificates for VPN connections (Page 4640) See also: Installing CA certificates for VPN connections (Page 4637) Error message: "Protocol error" 4660 Check to make sure that the IP address of the service PC is set in the configuration of the TS Adapter IE Advanced (Parameter > Plant Network) WinCC Basic V13.0 System Manual, 02/2014 Using online and diagnostics functions 13.7 Establishing a remote connection with TeleService Possible errors Check/Remedy Error message: "Connection setup error." Check to make sure that the LAN IP-address of the TS Adapter IE Advanced and the IP address of your network cards are in the same subnet. If this is the case, deactivate this network card before you establish the remote connection. An e-mail cannot be sent. Check whether there is a network/Internet connection at the WAN port. Check whether the mail server is accessible. Check whether the outgoing connections in the TS Adapter IE Advanced are valid. Check whether the SMTP port in the firewall is open for outgoing connections. WinCC Basic V13.0 System Manual, 02/2014 4661 Hardware documentation 14.1 14 General information on the hardware documentation Additional information on the available hardware The TIA Portal can be used to configure a wide variety of hardware, depending on the installed products. You can find the available hardware in the hardware catalog. You can find all the current manuals, operating instructions and FAQs as well as updates for your devices in the Siemens Industry Online Support (https://support.automation.siemens.com/). To help you locate the appropriate documents for your hardware in the Siemens Industry Online Support, the following sections list all modules and module families that are available in the current scope of the installation of the TIA Portal. You will find a link for each module that takes you directly to the relevant manuals and operating instructions in the Siemens Industry Online Support. 14.2 PLC 14.2.1 SIMATIC S7-1200 14.2.1.1 CPU CPU 1211C (6ES7 211-1xxx-0XB0) Information on the CPUs is available here: CPU 1211C AC/DC/Rly (6ES7 211-1BD30-0XB0 (http://support.automation.siemens.com/ WW/llisapi.dll? func=cslib.csinfo&lang=en&objid=6ES72111BD300XB0&objaction=csviewmlfbbeitraege& subtype=133300&caller=view)) CPU 1211C AC/DC/Rly (6ES7 211-1BE31-0XB0 (http://support.automation.siemens.com/ WW/llisapi.dll? func=cslib.csinfo&lang=en&objid=6ES72111BE310XB0&objaction=csviewmlfbbeitraege& subtype=133300&caller=view)) CPU 1211C AC/DC/Rly (6ES7 211-1BE40-0XB0 (http://support.automation.siemens.com/ WW/llisapi.dll? func=cslib.csinfo&lang=en&objid=6ES72111BE400XB0&objaction=csviewmlfbbeitraege& subtype=133300&caller=view)) WinCC Basic V13.0 System Manual, 02/2014 4663 Hardware documentation 14.2 PLC CPU 1211C DC/DC/DC (6ES7 211-1AD30-0XB0 (http://support.automation.siemens.com/ WW/llisapi.dll? func=cslib.csinfo&lang=en&objid=6ES72111AD300XB0&objaction=csviewmlfbbeitraege& subtype=133300&caller=view)) CPU 1211C DC/DC/DC (6ES7 211-1AE31-0XB0 (http://support.automation.siemens.com/ WW/llisapi.dll? func=cslib.csinfo&lang=en&objid=6ES72111AE310XB0&objaction=csviewmlfbbeitraege& subtype=133300&caller=view)) CPU 1211C DC/DC/DC (6ES7 211-1AE40-0XB0 (http://support.automation.siemens.com/ WW/llisapi.dll? func=cslib.csinfo&lang=en&objid=6ES72111AE400XB0&objaction=csviewmlfbbeitraege& subtype=133300&caller=view)) CPU 1211C DC/DC/Rly (6ES7 211-1HD30-0XB0 (http://support.automation.siemens.com/ WW/llisapi.dll? func=cslib.csinfo&lang=en&objid=6ES72111HD300XB0&objaction=csviewmlfbbeitraege& subtype=133300&caller=view)) CPU 1211C DC/DC/Rly (6ES7 211-1HE31-0XB0 (http://support.automation.siemens.com/ WW/llisapi.dll? func=cslib.csinfo&lang=en&objid=6ES72111HE310XB0&objaction=csviewmlfbbeitraege& subtype=133300&caller=view)) CPU 1211C DC/DC/Rly (6ES7 211-1HE40-0XB0 (http://support.automation.siemens.com/ WW/llisapi.dll? func=cslib.csinfo&lang=en&objid=6ES72111HE400XB0&objaction=csviewmlfbbeitraege& subtype=133300&caller=view)) CPU 1212C (6ES7 212-1xxx-0XB0) Information on the CPUs is available here: CPU 1212C AC/DC/Rly (6ES7 212-1BD30-0XB0 (http://support.automation.siemens.com/ WW/llisapi.dll? func=cslib.csinfo&lang=en&objid=6ES72121BD300XB0&objaction=csviewmlfbbeitraege& subtype=133300&caller=view)) CPU 1212C AC/DC/Rly (6ES7 212-1BE31-0XB0 (http://support.automation.siemens.com/ WW/llisapi.dll? func=cslib.csinfo&lang=en&objid=6ES72121BE310XB0&objaction=csviewmlfbbeitraege& subtype=133300&caller=view)) CPU 1212C AC/DC/Rly (6ES7 212-1BE40-0XB0 (http://support.automation.siemens.com/ WW/llisapi.dll? func=cslib.csinfo&lang=en&objid=6ES72121BE400XB0&objaction=csviewmlfbbeitraege& subtype=133300&caller=view)) 4664 WinCC Basic V13.0 System Manual, 02/2014 Hardware documentation 14.2 PLC CPU 1212C DC/DC/DC (6ES7 212-1AD30-0XB0 (http://support.automation.siemens.com/ WW/llisapi.dll? func=cslib.csinfo&lang=en&objid=6ES72121AD300XB0&objaction=csviewmlfbbeitraege& subtype=133300&caller=view)) CPU 1212C DC/DC/DC (6ES7 212-1AE31-0XB0 (http://support.automation.siemens.com/ WW/llisapi.dll? func=cslib.csinfo&lang=en&objid=6ES72121AE310XB0&objaction=csviewmlfbbeitraege& subtype=133300&caller=view)) CPU 1212C DC/DC/DC (6ES7 212-1AE40-0XB0 (http://support.automation.siemens.com/ WW/llisapi.dll? func=cslib.csinfo&lang=en&objid=6ES72121AE400XB0&objaction=csviewmlfbbeitraege& subtype=133300&caller=view)) CPU 1212C DC/DC/Rly (6ES7 212-1HD30-0XB0 (http://support.automation.siemens.com/ WW/llisapi.dll? func=cslib.csinfo&lang=en&objid=6ES72121HD300XB0&objaction=csviewmlfbbeitraege& subtype=133300&caller=view)) CPU 1212C DC/DC/Rly (6ES7 212-1HE31-0XB0 (http://support.automation.siemens.com/ WW/llisapi.dll? func=cslib.csinfo&lang=en&objid=6ES72121HE310XB0&objaction=csviewmlfbbeitraege& subtype=133300&caller=view)) CPU 1212C DC/DC/Rly (6ES7 212-1HE40-0XB0 (http://support.automation.siemens.com/ WW/llisapi.dll? func=cslib.csinfo&lang=en&objid=6ES72121HE400XB0&objaction=csviewmlfbbeitraege& subtype=133300&caller=view)) CPU 1214C (6ES7 214-1xxx-0XB0) Information on the CPUs is available here: CPU 1214C AC/DC/Rly (6ES7 214-1BE30-0XB0 (http://support.automation.siemens.com/ WW/llisapi.dll? func=cslib.csinfo&lang=en&objid=6ES72141BE300XB0&objaction=csviewmlfbbeitraege& subtype=133300&caller=view)) CPU 1214C AC/DC/Rly (6ES7 214-1BG31-0XB0 (http://support.automation.siemens.com/ WW/llisapi.dll? func=cslib.csinfo&lang=en&objid=6ES72141BG310XB0&objaction=csviewmlfbbeitraege& subtype=133300&caller=view)) CPU 1214C AC/DC/Rly (6ES7 214-1BG40-0XB0 (http://support.automation.siemens.com/ WW/llisapi.dll? func=cslib.csinfo&lang=en&objid=6ES72141BG400XB0&objaction=csviewmlfbbeitraege& subtype=133300&caller=view)) WinCC Basic V13.0 System Manual, 02/2014 4665 Hardware documentation 14.2 PLC CPU 1214C DC/DC/DC (6ES7 214-1AE30-0XB0 (http://support.automation.siemens.com/ WW/llisapi.dll? func=cslib.csinfo&lang=en&objid=6ES72141AE300XB0&objaction=csviewmlfbbeitraege& subtype=133300&caller=view)) CPU 1214C DC/DC/DC (6ES7 214-1AG31-0XB0 (http://support.automation.siemens.com/ WW/llisapi.dll? func=cslib.csinfo&lang=en&objid=6ES72141AG310XB0&objaction=csviewmlfbbeitraege& subtype=133300&caller=view)) CPU 1214C DC/DC/DC (6ES7 214-1AG40-0XB0 (http://support.automation.siemens.com/ WW/llisapi.dll? func=cslib.csinfo&lang=en&objid=6ES72141AG400XB0&objaction=csviewmlfbbeitraege& subtype=133300&caller=view)) CPU 1214C DC/DC/Rly (6ES7 214-1HE30-0XB0 (http://support.automation.siemens.com/ WW/llisapi.dll? func=cslib.csinfo&lang=en&objid=6ES72141HE300XB0&objaction=csviewmlfbbeitraege& subtype=133300&caller=view)) CPU 1214C DC/DC/Rly (6ES7 214-1HG31-0XB0 (http://support.automation.siemens.com/ WW/llisapi.dll? func=cslib.csinfo&lang=en&objid=6ES72141HG310XB0&objaction=csviewmlfbbeitraege &subtype=133300&caller=view)) CPU 1214C DC/DC/Rly (6ES7 214-1HG40-0XB0 (http://support.automation.siemens.com/ WW/llisapi.dll? func=cslib.csinfo&lang=en&objid=6ES72141HG400XB0&objaction=csviewmlfbbeitraege &subtype=133300&caller=view)) CPU 1215C (6ES7 215-1xxx-0XB0) Information on the CPUs is available here: CPU 1215C DC/DC/DC (6ES7 215-1BG31-0XB0 (http://support.automation.siemens.com/ WW/llisapi.dll? func=cslib.csinfo&lang=en&objid=6ES72151BG310XB0&objaction=csviewmlfbbeitraege& subtype=133300&caller=view)) CPU 1215C DC/DC/DC (6ES7 215-1BG40-0XB0 (http://support.automation.siemens.com/ WW/llisapi.dll? func=cslib.csinfo&lang=en&objid=6ES72151BG400XB0&objaction=csviewmlfbbeitraege& subtype=133300&caller=view)) CPU 1215C AC/DC/Rly (6ES7 215-1AG31-0XB0 (http://support.automation.siemens.com/ WW/llisapi.dll? func=cslib.csinfo&lang=en&objid=6ES72151AG310XB0&objaction=csviewmlfbbeitraege& subtype=133300&caller=view)) 4666 WinCC Basic V13.0 System Manual, 02/2014 Hardware documentation 14.2 PLC CPU 1215C AC/DC/Rly (6ES7 215-1AG40-0XB0 (http://support.automation.siemens.com/ WW/llisapi.dll? func=cslib.csinfo&lang=en&objid=6ES72151AG400XB0&objaction=csviewmlfbbeitraege& subtype=133300&caller=view)) CPU 1215C DC/DC/Rly (6ES7 215-1HG31-0XB0 (http://support.automation.siemens.com/ WW/llisapi.dll? func=cslib.csinfo&lang=en&objid=6ES72151HG310XB0&objaction=csviewmlfbbeitraege &subtype=133300&caller=view)) CPU 1215C DC/DC/Rly (6ES7 215-1HG40-0XB0 (http://support.automation.siemens.com/ WW/llisapi.dll? func=cslib.csinfo&lang=en&objid=6ES72151HG400XB0&objaction=csviewmlfbbeitraege &subtype=133300&caller=view)) CPU 1217C (6ES7 217-1xxx-0XB0) Information on the 1217C DC/DC/DC CPU is available here (http:// support.automation.siemens.com/WW/llisapi.dll? func=cslib.csinfo&lang=en&objid=6ES72171AG400XB0&objaction=csviewmlfbbeitraege&su btype=133300&caller=view). 14.2.1.2 Signal boards Signal boards (6ES7 2xx-xxx30-0XB0) Information on signal boards for S7-1200 is available here: DI 4x24VDC (6ES7 221-3BD30-0XB0 (http://support.automation.siemens.com/WW/ llisapi.dll? func=cslib.csinfo&lang=en&objid=6ES72233BD300XB0&objaction=csviewmlfbbeitraege& subtype=133300&caller=viewB)) DI 4x5VDC (6ES7 221-3AD30-0XB0 (http://support.automation.siemens.com/WW/ llisapi.dll? func=cslib.csinfo&lang=en&objid=6ES72213AD300XB0&objaction=csviewmlfbbeitraege& subtype=133300&caller=view)) DQ 4x24VDC (6ES7 222-1BD30-0XB0 (http://support.automation.siemens.com/WW/ llisapi.dll? func=cslib.csinfo&lang=en&objid=6ES72221BD300XB0&objaction=csviewmlfbbeitraege& subtype=133300&caller=viewB)) DQ 4x5VDC (6ES7 222-1AD30-0XB0 (http://support.automation.siemens.com/WW/ llisapi.dll? func=cslib.csinfo&lang=en&objid=6ES72221AD300XB0&objaction=csviewmlfbbeitraege& subtype=133300&caller=viewB)) WinCC Basic V13.0 System Manual, 02/2014 4667 Hardware documentation 14.2 PLC DI 2/DQ 2x24VDC (6ES7 223-0BD30-0XB0 (http://support.automation.siemens.com/WW/ llisapi.dll? func=cslib.csinfo&lang=en&objid=6ES72230BD300XB0&objaction=csviewmlfbbeitraege& subtype=133300&caller=viewB)) DI 2/DQ 2x24VDC (6ES7 223-3BD30-0XB0 (http://support.automation.siemens.com/WW/ llisapi.dll? func=cslib.csinfo&lang=en&objid=6ES72213BD300XB0&objaction=csviewmlfbbeitraege& subtype=133300&caller=view)) DI 2/DQ 2x5VDC (6ES7 223-3AD30-0XB0 (http://support.automation.siemens.com/WW/ llisapi.dll? func=cslib.csinfo&lang=en&objid=6ES72233AD300XB0&objaction=csviewmlfbbeitraege& subtype=133300&caller=viewB)) AI 1x12BIT (6ES7 231-4HA30-0XB0 (http://support.automation.siemens.com/WW/ llisapi.dll? func=cslib.csinfo&lang=en&objid=6ES72314HA300XB0&objaction=csviewmlfbbeitraege& subtype=133300&caller=viewB)) AI 1xRTD (6ES7 231-5PA30-0XB0 (http://support.automation.siemens.com/WW/llisapi.dll? func=cslib.csinfo&lang=en&objid=6ES72315PA300XB0&objaction=csviewmlfbbeitraege& subtype=133300&caller=viewB)) AI 1xTC (6ES7 231-5QA30-0XB0 (http://support.automation.siemens.com/WW/llisapi.dll? func=cslib.csinfo&lang=en&objid=6ES72315QA300XB0&objaction=csviewmlfbbeitraege& subtype=133300&caller=viewB)) AQ 1x12BIT (6ES7 232-4HA30-0XB0 (http://support.automation.siemens.com/WW/ llisapi.dll? func=cslib.csinfo&lang=en&objid=6ES72324HA300XB0&objaction=csviewmlfbbeitraege& subtype=133300&caller=viewB)) 14.2.1.3 Communication boards Point-to-point CB 1241 (6ES7 241-1CH30-1XB0) Information on the CB 1241 communication board is available here (http:// support.automation.siemens.com/WW/llisapi.dll? func=cslib.csinfo&lang=en&objid=6ES72411CH301XB0&objaction=csviewmlfbbeitraege&su btype=133300&caller=view). 4668 WinCC Basic V13.0 System Manual, 02/2014 Hardware documentation 14.2 PLC 14.2.1.4 Battery boards BB 1297 (6ES7 297-0AX30-0XA0) Information on the BB 1297 communication board is available here (http:// support.automation.siemens.com/WW/llisapi.dll?aktprim=100&lang=en&referer=%2fWW %2f&func=cslib.cssearch&nodeid0=41886045&viewreg=WW&siteid=csius&extranet=standar d&groupid=4000002&objaction=cssearch&content=adsearch%2Fadsearch%2Easpx). 14.2.1.5 Digital input modules Digital input modules (6ES7 221-1Bx3x-0XB0) Information on the digital input modules is available here: DI8 x 24VDC (6ES7 221-1BF30-0XB0 (http://support.automation.siemens.com/WW/ llisapi.dll? func=cslib.csinfo&lang=en&objid=6ES72211BF300XB0&objaction=csviewmlfbbeitraege& subtype=133300&caller=view)) DI8 x 24VDC (6ES7 221-1BF32-0XB0 (http://support.automation.siemens.com/WW/ llisapi.dll? func=cslib.csinfo&lang=en&objid=6ES72211BF320XB0&objaction=csviewmlfbbeitraege& subtype=133300&caller=view)) DI16 x 24VDC (6ES7 221-1BH30-0XB0 (http://support.automation.siemens.com/WW/ llisapi.dll? func=cslib.csinfo&lang=en&objid=6ES72211BH300XB0&objaction=csviewmlfbbeitraege& subtype=133300&caller=view)) DI16 x 24VDC (6ES7 221-1BH32-0XB0 (http://support.automation.siemens.com/WW/ llisapi.dll? func=cslib.csinfo&lang=en&objid=6ES72211BH320XB0&objaction=csviewmlfbbeitraege& subtype=133300&caller=view)) WinCC Basic V13.0 System Manual, 02/2014 4669 Hardware documentation 14.2 PLC 14.2.1.6 Digital output modules Digital output modules (6ES7 222-1xx3x-0XB0) Information on the digital output modules is available here: DQ 8x24VDC (6ES7 222-1BF30-0XB0 (http://support.automation.siemens.com/WW/ llisapi.dll? func=cslib.csinfo&lang=en&objid=6ES72221BF300XB0&objaction=csviewmlfbbeitraege& subtype=133300&caller=view)) DQ 8x24VDC (6ES7 222-1BF32-0XB0 (http://support.automation.siemens.com/WW/ llisapi.dll? func=cslib.csinfo&lang=en&objid=6ES72221BF320XB0&objaction=csviewmlfbbeitraege& subtype=133300&caller=view)) DQ 16x24VDC (6ES7 222-1BH30-0XB0 (http://support.automation.siemens.com/WW/ llisapi.dll? func=cslib.csinfo&lang=en&objid=6ES72221BH300XB0&objaction=csviewmlfbbeitraege& subtype=133300&caller=view)) DQ 16x24VDC (6ES7 222-1BH32-0XB0 (http://support.automation.siemens.com/WW/ llisapi.dll? func=cslib.csinfo&lang=en&objid=6ES72221BH320XB0&objaction=csviewmlfbbeitraege& subtype=133300&caller=view)) DQ 16xRelay (6ES7 222-1HH30-0XB0 (http://support.automation.siemens.com/WW/ llisapi.dll? func=cslib.csinfo&lang=en&objid=6ES72221HH300XB0&objaction=csviewmlfbbeitraege& subtype=133300&caller=view)) DQ 16xRelay (6ES7 222-1HH32-0XB0 (http://support.automation.siemens.com/WW/ llisapi.dll? func=cslib.csinfo&lang=en&objid=6ES72221HH320XB0&objaction=csviewmlfbbeitraege& subtype=133300&caller=view)) DQ 8xRelay (6ES7 222-1HF30-0XB0 (http://support.automation.siemens.com/WW/ llisapi.dll? func=cslib.csinfo&lang=en&objid=6ES72221HF300XB0&objaction=csviewmlfbbeitraege& subtype=133300&caller=view)) DQ 8xRelay (6ES7 222-1HF32-0XB0 (http://support.automation.siemens.com/WW/ llisapi.dll? func=cslib.csinfo&lang=en&objid=6ES72221HF320XB0&objaction=csviewmlfbbeitraege& subtype=133300&caller=view)) 4670 WinCC Basic V13.0 System Manual, 02/2014 Hardware documentation 14.2 PLC DQ 8xNO/NC Relay (6ES7 222-1XF30-0XB0 (http://support.automation.siemens.com/ WW/llisapi.dll? func=cslib.csinfo&lang=en&objid=6ES72221XF300XB0&objaction=csviewmlfbbeitraege& subtype=133300&caller=view)) DQ 8xNO/NC Relay (6ES7 222-1XF32-0XB0 (http://support.automation.siemens.com/ WW/llisapi.dll? func=cslib.csinfo&lang=en&objid=6ES72221XF320XB0&objaction=csviewmlfbbeitraege& subtype=133300&caller=view)) 14.2.1.7 Digital input and digital output modules Digital input and output modules (6ES7 223-1xx3x-0XB0) Information on the digital input and output modules is available here: DI 8/DQ 8x24VDC (6ES7 223-1BH30-0XB0 (http://support.automation.siemens.com/WW/ llisapi.dll? func=cslib.csinfo&lang=en&objid=6ES72231BH300XB0&objaction=csviewmlfbbeitraege& subtype=133300&caller=view)) DI 8/DQ 8x24VDC (6ES7 223-1BH32-0XB0 (http://support.automation.siemens.com/WW/ llisapi.dll? func=cslib.csinfo&lang=en&objid=6ES72231BH320XB0&objaction=csviewmlfbbeitraege& subtype=133300&caller=view)) DI 16/DQ 16x24VDC (6ES7 223-1BL30-0XB0 (http://support.automation.siemens.com/ WW/llisapi.dll? func=cslib.csinfo&lang=en&objid=6ES72231BL300XB0&objaction=csviewmlfbbeitraege& subtype=133300&caller=view)) DI 16/DQ 16x24VDC (6ES7 223-1BL32-0XB0 (http://support.automation.siemens.com/ WW/llisapi.dll? func=cslib.csinfo&lang=en&objid=6ES72231BL320XB0&objaction=csviewmlfbbeitraege& subtype=133300&caller=view)) DI 8x24VDC/DQ 8xRelay (6ES7 223-1PH30-0XB0 (http:// support.automation.siemens.com/WW/llisapi.dll? func=cslib.csinfo&lang=en&objid=6ES72231PH300XB0&objaction=csviewmlfbbeitraege& subtype=133300&caller=view)) DI 8x24VDC/DQ 8xRelay (6ES7 223-1PH32-0XB0 (http:// support.automation.siemens.com/WW/llisapi.dll? func=cslib.csinfo&lang=en&objid=6ES72231PH320XB0&objaction=csviewmlfbbeitraege& subtype=133300&caller=view)) DI 16x24VDC/DQ 16xRelay (6ES7 223-1PL30-0XB0 (http:// support.automation.siemens.com/WW/llisapi.dll? func=cslib.csinfo&lang=en&objid=6ES72231PL300XB0&objaction=csviewmlfbbeitraege& subtype=133300&caller=view)) WinCC Basic V13.0 System Manual, 02/2014 4671 Hardware documentation 14.2 PLC DI 16x24VDC/DQ 16xRelay (6ES7 223-1PL32-0XB0 (http:// support.automation.siemens.com/WW/llisapi.dll? func=cslib.csinfo&lang=en&objid=6ES72231PL320XB0&objaction=csviewmlfbbeitraege& subtype=133300&caller=view)) DI/DO 8x120VAC/DQ 8xRelay (6ES7 223-1QH30-0XB0 (http:// support.automation.siemens.com/WW/llisapi.dll? func=cslib.csinfo&lang=en&objid=6ES72231QH300XB0&objaction=csviewmlfbbeitraege &subtype=133300&caller=view)) DI/DO 8x120VAC/DQ 8xRelay (6ES7 223-1QH32-0XB0 (http:// support.automation.siemens.com/WW/llisapi.dll? func=cslib.csinfo&lang=en&objid=6ES72231QH320XB0&objaction=csviewmlfbbeitraege &subtype=133300&caller=view)) 14.2.1.8 Analog input modules Analog input modules (6ES7 231-xxx3x-0XB0) Information on the analog input modules is available here: AI 4x13BIT (6ES7 231-4HD30-0XB0 (http://support.automation.siemens.com/WW/ llisapi.dll? func=cslib.csinfo&lang=en&objid=6ES72314HD300XB0&objaction=csviewmlfbbeitraege& subtype=133300&caller=view)) AI 4x13BIT (6ES7 231-4HD32-0XB0 (http://support.automation.siemens.com/WW/ llisapi.dll? func=cslib.csinfo&lang=en&objid=6ES72314HD320XB0&objaction=csviewmlfbbeitraege& subtype=133300&caller=view)) AI 4x16BIT (6ES7 231-5ND30-0XB0 (http://support.automation.siemens.com/WW/ llisapi.dll? func=cslib.csinfo&lang=en&objid=6ES72315ND300XB0&objaction=csviewmlfbbeitraege& subtype=133300&caller=view)) AI 4x16BIT (6ES7 231-5ND32-0XB0 (http://support.automation.siemens.com/WW/ llisapi.dll? func=cslib.csinfo&lang=en&objid=6ES72315ND320XB0&objaction=csviewmlfbbeitraege& subtype=133300&caller=view)) AI 8x13BIT (6ES7 231-4HF30-0XB0 (http://support.automation.siemens.com/WW/ llisapi.dll? func=cslib.csinfo&lang=en&objid=6ES72314HF300XB0&objaction=csviewmlfbbeitraege& subtype=133300&caller=view)) AI 8x13BIT (6ES7 231-4HF32-0XB0 (http://support.automation.siemens.com/WW/ llisapi.dll? func=cslib.csinfo&lang=en&objid=6ES72314HF320XB0&objaction=csviewmlfbbeitraege& subtype=133300&caller=view)) 4672 WinCC Basic V13.0 System Manual, 02/2014 Hardware documentation 14.2 PLC AI 4xRTD (6ES7 231-5PD30-0XB0 (http://support.automation.siemens.com/WW/ llisapi.dll? func=cslib.csinfo&lang=en&objid=6ES72315PD300XB0&objaction=csviewmlfbbeitraege& subtype=133300&caller=view)) AI 4xRTD (6ES7 231-5PD32-0XB0 (http://support.automation.siemens.com/WW/ llisapi.dll? func=cslib.csinfo&lang=en&objid=6ES72315PD320XB0&objaction=csviewmlfbbeitraege& subtype=133300&caller=view)) AI 8xRTD (6ES7 231-5PF30-0XB0 (http://support.automation.siemens.com/WW/llisapi.dll? func=cslib.csinfo&lang=en&objid=6ES723145PF300XB0&objaction=csviewmlfbbeitraege &subtype=133300&caller=view)) AI 8xRTD (6ES7 231-5PF32-0XB0 (http://support.automation.siemens.com/WW/llisapi.dll? func=cslib.csinfo&lang=en&objid=6ES72315PF320XB0&objaction=csviewmlfbbeitraege& subtype=133300&caller=view)) AI 4xTC (6ES7 231-5QD30-0XB0 (http://support.automation.siemens.com/WW/llisapi.dll? func=cslib.csinfo&lang=en&objid=6ES72315QD300XB0&objaction=csviewmlfbbeitraege &subtype=133300&caller=view)) AI 4xTC (6ES7 231-5QD32-0XB0 (http://support.automation.siemens.com/WW/llisapi.dll? func=cslib.csinfo&lang=en&objid=6ES72315QD320XB0&objaction=csviewmlfbbeitraege &subtype=133300&caller=view)) AI 8xTC (6ES7 231-5QF30-0XB0 (http://support.automation.siemens.com/WW/llisapi.dll? func=cslib.csinfo&lang=en&objid=6ES72315QF300XB0&objaction=csviewmlfbbeitraege& subtype=133300&caller=view)) AI 8xTC (6ES7 231-5QF32-0XB0 (http://support.automation.siemens.com/WW/llisapi.dll? func=cslib.csinfo&lang=en&objid=6ES72315QF320XB0&objaction=csviewmlfbbeitraege& subtype=133300&caller=view)) WinCC Basic V13.0 System Manual, 02/2014 4673 Hardware documentation 14.2 PLC 14.2.1.9 Analog output modules Analog output modules (6ES7 234-4Hx3x-0XB0) Information on the analog output modules is available here: AQ 2x14BIT (6ES7 232-4HB30-0XB0 (http://support.automation.siemens.com/WW/ llisapi.dll? func=cslib.csinfo&lang=en&objid=6ES72344HB300XB0&objaction=csviewmlfbbeitraege& subtype=133300&caller=view)) AQ 2x14BIT (6ES7 232-4HB32-0XB0 (http://support.automation.siemens.com/WW/ llisapi.dll? func=cslib.csinfo&lang=en&objid=6ES72344HB320XB0&objaction=csviewmlfbbeitraege& subtype=133300&caller=view)) AQ 4x14BIT (6ES7 232-4HD30-0XB0 (http://support.automation.siemens.com/WW/ llisapi.dll? func=cslib.csinfo&lang=en&objid=6ES72344HD300XB0&objaction=csviewmlfbbeitraege& subtype=133300&caller=view)) AQ 4x14BIT (6ES7 232-4HD32-0XB0 (http://support.automation.siemens.com/WW/ llisapi.dll? func=cslib.csinfo&lang=en&objid=6ES72344HD320XB0&objaction=csviewmlfbbeitraege& subtype=133300&caller=view)) 14.2.1.10 Analog input and analog output modules Analog input and output module (6ES7 234-4HE3x-0XB0) Information on the analog input and output modules is available here: AI 4x13BIT/AQ 2x14BIT (6ES7 234-4HE30-0XB0 (http://support.automation.siemens.com/ WW/llisapi.dll? func=cslib.csinfo&lang=en&objid=6ES72324HB300XB0&objaction=csviewmlfbbeitraege& subtype=133300&caller=view)) AI 4x13BIT/AQ 2x14BIT (6ES7 234-4HE32-0XB0 (http://support.automation.siemens.com/ WW/llisapi.dll? func=cslib.csinfo&lang=en&objid=6ES72324HB320XB0&objaction=csviewmlfbbeitraege& subtype=133300&caller=view)) 4674 WinCC Basic V13.0 System Manual, 02/2014 Hardware documentation 14.2 PLC 14.2.1.11 Communications modules Industrial Remote Communication CP 1242-7 (6GK7 242-7KX30-0XE00) Information on the CP 1242-7 Telecontrol communication module is available here (http:// support.automation.siemens.com/WW/llisapi.dll? func=cslib.csinfo&lang=en&objid=6GK72427KX300XE0&objaction=csviewmlfbbeitraege&su btype=133300&caller=view). CP 1243-1 (6GK7 243-1JX30-0XE0) Information on the CP 1243-1 Ethernet communication module is available here (http:// support.automation.siemens.com/WW/llisapi.dll? func=cslib.csinfo&lang=en&objid=6GK72431JX300XE0&objaction=csviewmlfbbeitraege&sub type=133300&caller=view). PROFIBUS CM 1242-5 (6GK7 242-5DX3x-0XE0) Information on the CM 1242-5 PROFIBUS communication module is available here (http:// support.automation.siemens.com/WW/llisapi.dll? func=cslib.csinfo&lang=en&objid=6GK72425DX300XE0&objaction=csviewmlfbbeitraege&su btype=133300&caller=view). CM 1243-5 (6GK7 243-5DX3x-0XE0) Information on the CM 1243-5 PROFIBUS communication module is available here (http:// support.automation.siemens.com/WW/llisapi.dll? func=cslib.csinfo&lang=en&objid=6GK72435DX300XE0&objaction=csviewmlfbbeitraege&su btype=133300&caller=view). Point-to-point CM 1241 RS232 (6ES7 241-1AH30-0XB0) Information on the CM 1241 (RS232) communication module for point-to-point connections is available here (http://support.automation.siemens.com/WW/llisapi.dll? WinCC Basic V13.0 System Manual, 02/2014 4675 Hardware documentation 14.2 PLC func=cslib.csinfo&lang=en&objid=6ES72411AH300XB0&objaction=csviewmlfbbeitraege&su btype=133300&caller=view). CM 1241 RS232 (6ES7 241-1AH32-0XB0) Information on the CM 1241 (RS232) communication module for point-to-point connections is available here (https://support.automation.siemens.com/WW/llisapi.dll? func=cslib.csinfo&lang=en&objid=6ES72411AH320XB0&objaction=csviewmlfbbeitraege&su btype=133300&caller=view). CM 1241 RS485 (6ES7 241-1CH30-0XB0) Information on the CM 1241 (RS485) communication module for point-to-point connections is available here (http://support.automation.siemens.com/WW/llisapi.dll? func=cslib.csinfo&lang=en&objid=6ES72411CH300XB0&objaction=csviewmlfbbeitraege&su btype=133300&caller=view). CM 1241 RS422/485 (6ES7 241-1CH31-0XB0) Information on the CM 1241 (RS422/485) communication module for point-to-point connections is available here (http://support.automation.siemens.com/WW/llisapi.dll? func=cslib.csinfo&lang=en&objid=6ES72411CH310XB0&objaction=csviewmlfbbeitraege&su btype=133300&caller=view). CM 1241 RS422/485 (6ES7 241-1CH32-0XB0) Information on the CM 1241 (RS422/485) communication module for point-to-point connections is available here (https://support.automation.siemens.com/WW/llisapi.dll? func=cslib.csinfo&lang=en&objid=6ES72411CH320XB0&objaction=csviewmlfbbeitraege&su btype=133300&caller=view). Identification systems RF120C (6GT2 002-0LA00) Information on the communication module for Ident technology RFC120C is available here (http://support.automation.siemens.com/WW/llisapi.dll? func=cslib.csinfo&lang=en&objid=6GT20020LA00&objaction=csviewmlfbbeitraege&subtype =133300&caller=view). 4676 WinCC Basic V13.0 System Manual, 02/2014 Hardware documentation 14.2 PLC AS-Interface AS-Interface CM 1243-2 (3RK7 243-2AA30-0XB0) Information on the CM 1243-2 AS-i communication module is available here (http:// support.automation.siemens.com/WW/llisapi.dll? func=cslib.csinfo&lang=en&objid=3RK72432AA300XB0&objaction=csviewmlfbbeitraege&su btype=133300&caller=view). 14.2.1.12 Technology modules SIWAREX WP231 (7MH4 960-2AA01) Information on the SIWAREX WP231 weighing module is available here (https:// support.automation.siemens.com/WW/llisapi.dll? func=cslib.csinfo&lang=en&objid=7MH4960-2AA01&objaction=csviewmlfbbeitraege&subtyp e=133300&caller=view). SIWAREX WP241 (7MH4 960-4AA01) Information on the SIWAREX WP241 weighing module is available here (https:// support.automation.siemens.com/WW/llisapi.dll? func=cslib.csinfo&lang=en&objid=7MH4960-4AA01&objaction=csviewmlfbbeitraege&subtyp e=133300&caller=view). 4SI IO-Link (6ES7 278-4BD32-0XB0) Information on the 4SI IO-Link IO-Link Master technology module is available here (https:// support.automation.siemens.com/WW/llisapi.dll? func=cslib.csinfo&lang=en&objid=6ES72784BD320XB0&objaction=csviewmlfbbeitraege&su btype=133300&caller=view). WinCC Basic V13.0 System Manual, 02/2014 4677 Hardware documentation 14.3 Distributed I/O 14.3 Distributed I/O 14.3.1 ET 200MP 14.3.1.1 Interface modules PROFINET IM 155-5 PN ST (6ES7 155-5AA00-0AB0) Information on the distributed I/O module IM 155-5 PN ST is available here (http:// support.automation.siemens.com/WW/llisapi.dll? func=cslib.csinfo&lang=en&objid=6ES71555AA000AB0&objaction=csviewmlfbbeitraege&su btype=133300&caller=view). IM 155-5 PN HF (6ES7 155-5AA00-0AC0) Information on the IM 155-5 PN HF distributed I/O module is available here (http:// support.automation.siemens.com/WW/llisapi.dll? func=cslib.csinfo&lang=en&objid=6ES71555AA000AC0&objaction=csviewmlfbbeitraege&su btype=133300&caller=view). 14.3.1.2 Digital input modules DI 16x24VDC BA (6ES7 521-1BH10-0AA0) Information on the DI 16x24VDC BA digital input module is available here (https:// support.automation.siemens.com/WW/llisapi.dll? func=cslib.csinfo&lang=en&objid=6ES75211BH100AA0&objaction=csviewmlfbbeitraege&su btype=133300&caller=view). DI 16x24VDC HF (6ES7 521-1BH00-0AB0) Information on the digital input module DI 16x24VDC HF is available here (https:// support.automation.siemens.com/WW/llisapi.dll? func=cslib.csinfo&lang=en&objid=6ES75211BH000AB0&objaction=csviewmlfbbeitraege&su btype=133300&caller=view). 4678 WinCC Basic V13.0 System Manual, 02/2014 Hardware documentation 14.3 Distributed I/O DI 16x24VDC SRC BA (6xxx 521-1BH50-xAA0) Information on the DI 16x24VDC HF digital input module (including SIPLUS variant) is available here (https://support.automation.siemens.com/WW/llisapi.dll? func=cslib.csinfo&lang=en&objid=6ES75211BH500AA0&objaction=csviewmlfbbeitraege&su btype=133300&caller=view). DI 16x230VAC BA (6xxx 521-1FH00-xAA0) Information on the DI 16x24VDC HF digital input module (including SIPLUS variant) is available here (https://support.automation.siemens.com/WW/llisapi.dll? func=cslib.csinfo&lang=en&objid=6ES75211FH000AA0&objaction=csviewmlfbbeitraege&su btype=133300&caller=view). DI 32x24VDC HF (6ES7 521-1BL00-0AB0) Information on the digital input module DI 16x24VDC HF is available here (https:// support.automation.siemens.com/WW/llisapi.dll? func=cslib.csinfo&lang=en&objid=6ES75211BL000AB0&objaction=csviewmlfbbeitraege&sub type=133300&caller=view). DI 32x24VDC BA (6ES7 521-1BL10-0AA0) Information on the DI 16x24VDC BA digital input module is available here (https:// support.automation.siemens.com/WW/llisapi.dll? func=cslib.csinfo&lang=en&objid=6ES75211BL100AA0&objaction=csviewmlfbbeitraege&sub type=133300&caller=view). 14.3.1.3 Digital output modules DQ 8x24VDC/2A HF (6xxx 522-1BF00-xAB0) Information on the DQ 8x24VDC/2A HF digital output module (including SIPLUS variant) is available here (https://support.automation.siemens.com/WW/llisapi.dll? func=cslib.csinfo&lang=en&objid=6ES75221BF000AB0&objaction=csviewmlfbbeitraege&sub type=133300&caller=view). WinCC Basic V13.0 System Manual, 02/2014 4679 Hardware documentation 14.3 Distributed I/O DQ 8x230VAC/2A ST (6xxx 522-5FF00-xAB0) Information on the DQ 8x230VAC/2A ST digital output module (including SIPLUS variant) is available here (https://support.automation.siemens.com/WW/llisapi.dll? func=cslib.csinfo&lang=en&objid=6ES75225FF000AB0&objaction=csviewmlfbbeitraege&sub type=133300&caller=view). DQ 8x230VAC/5A ST (6xxx 522-5HF00-xAB0) Information on the 8x230VAC/5A ST digital output module (including SIPLUS variant) is available here (https://support.automation.siemens.com/WW/llisapi.dll? func=cslib.csinfo&lang=en&objid=6ES75225HF000AB0&objaction=csviewmlfbbeitraege&su btype=133300&caller=view). DQ 16x24VDC/0.5A BA (6ES7 522-1BH10-0AA0) Information on the DQ 16x24VDC/0.5A BA digital output module is available here (http:// support.automation.siemens.com/WW/llisapi.dll? func=cslib.csinfo&lang=en&objid=6ES75221BH100AA0&objaction=csviewmlfbbeitraege&su btype=133300&caller=view). DQ 16x24VDC/0.5A ST (6ES7 522-1BH00-0AB0) Information on the digital output module DQ 16x24VDC/0.5A ST is available here (https:// support.automation.siemens.com/WW/llisapi.dll? func=cslib.csinfo&lang=en&objid=6ES75221BH000AB0&objaction=csviewmlfbbeitraege&su btype=133300&caller=view). DQ 32x24VDC/0.5A BA (6ES7 522-1BL10-0AA0) Information on the DQ 32x 24VDC/0.5A BA digital output module is available here (http:// support.automation.siemens.com/WW/llisapi.dll? func=cslib.csinfo&lang=en&objid=6ES75221BL100AA0&objaction=csviewmlfbbeitraege&sub type=133300&caller=view). DQ 32x24VDC/0.5A ST (6ES7 522-1BL00-0AB0) Information on the digital output module DQ 32x 24VDC/0.5A is available here (https:// support.automation.siemens.com/WW/llisapi.dll? 4680 WinCC Basic V13.0 System Manual, 02/2014 Hardware documentation 14.3 Distributed I/O func=cslib.csinfo&lang=en&objid=6ES75221BL000AB0&objaction=csviewmlfbbeitraege&sub type=133300&caller=view). 14.3.1.4 Digital input and digital output modules DI16/DO 16x24VDC (6ES7 523-1BL00-0AA0) Information on the DI 16/DO 16x24VDC digital input and output module is available here (https://support.automation.siemens.com/WW/llisapi.dll? func=cslib.csinfo&lang=en&objid=6ES75231BL000AA0&objaction=csviewmlfbbeitraege&sub type=133300&caller=view). 14.3.1.5 Analog input modules AI 4xU/I/RTD/TC ST (6ES7 531-7QD00-0AB0) Information on the AI 4xU/I/RTD/TC ST analog input module is available here (https:// support.automation.siemens.com/WW/llisapi.dll? func=cslib.csinfo&lang=en&objid=6ES75317QD00AB0&objaction=csviewmlfbbeitraege&subt ype=133300&caller=view). AI 8xU/I/RTD/TC ST (6ES7 531-7KF00-0AB0) Information on the analog input module AI 8xU/I/RTD/TC ST is available here (https:// support.automation.siemens.com/WW/llisapi.dll? func=cslib.csinfo&lang=en&objid=6ES75317KF000AB0&objaction=csviewmlfbbeitraege&sub type=133300&caller=view). AI 8xU/I HS (6xxx 531-7NF10-xAB0) Information on the AI 8xU/I HS analog input module (including SIPLUS variant) is available here (https://support.automation.siemens.com/WW/llisapi.dll? func=cslib.csinfo&lang=en&objid=6ES75317NF100AB0&objaction=csviewmlfbbeitraege&su btype=133300&caller=view). WinCC Basic V13.0 System Manual, 02/2014 4681 Hardware documentation 14.3 Distributed I/O 14.3.1.6 Analog output modules AQ 2xU/I ST (6ES7 532-5NB00-0AB0) Information on the AQ 2xU/I ST analog output module is available here (https:// support.automation.siemens.com/WW/llisapi.dll? func=cslib.csinfo&lang=en&objid=6ES75325NB000AB0&objaction=csviewmlfbbeitraege&su btype=133300&caller=view). AQ 4xU/I ST (6ES7 532-5HD00-0AB0) Information on the analog output module AQ 4xU/I ST is available here (https:// support.automation.siemens.com/WW/llisapi.dll? func=cslib.csinfo&lang=en&objid=6ES75325HD000AB0&objaction=csviewmlfbbeitraege&su btype=133300&caller=view). AQ 8xU/I HS (6xxx 532-5HF00-xAB0) Information on the AQ 8xU/I HS analog output module (including SIPLUS variant) is available here (https://support.automation.siemens.com/WW/llisapi.dll? func=cslib.csinfo&lang=en&objid=6ES75325HF000AB0&objaction=csviewmlfbbeitraege&su btype=133300&caller=view). 14.3.1.7 Analog input and analog output modules AI/AQ 4xU/I/RTD/TC / 2xU/I ST (6ES7 534-7QE00-0AB0) Information on the AI/AQ 4xU/I/RTD/TC / 2xU/I ST analog input and output module is available here (https://support.automation.siemens.com/WW/llisapi.dll? func=cslib.csinfo&lang=en&objid=6ES75347QE000AB0&objaction=csviewmlfbbeitraege&su btype=133300&caller=view). 4682 WinCC Basic V13.0 System Manual, 02/2014 Hardware documentation 14.3 Distributed I/O 14.3.1.8 Communications modules PROFINET/Ethernet CM 1542-1 (6GK7 542-1AX00-0XE) Information on the CM 1542-1 PROFINET/Ethernet communication module is available here (https://support.automation.siemens.com/WW/llisapi.dll? func=cslib.csinfo&lang=en&objid=6GK75421AX000XE0&objaction=csviewmlfbbeitraege&su btype=133300&caller=view). CP 1543-1 (6GK7 543-1AX00-0XE0) Information on the CP 1543-1 PROFINET/Ethernet communications processor is available here (https://support.automation.siemens.com/WW/llisapi.dll? func=cslib.csinfo&lang=en&objid=6GK75431AX000XE0&objaction=csviewmlfbbeitraege&su btype=133300&caller=view). PROFIBUS CM 1542-5 (6GK7 542-5DX00-0XE0) Information on the CM 1542-5 PROFIBUS communication module is available here (https:// support.automation.siemens.com/WW/llisapi.dll? func=cslib.csinfo&lang=en&objid=6GK75425DX000XE0&objaction=csviewmlfbbeitraege&su btype=133300&caller=view). Point-to-point RS232 CM PtP RS232 BA (6xxx 540-1AD00-xAA0) Information on the CM PtP RS232 BA point-to-point communication module (including SIPLUS variant) is available here (https://support.automation.siemens.com/WW/llisapi.dll? func=cslib.csinfo&lang=en&objid=6ES75401AD000AA0&objaction=csviewmlfbbeitraege&su btype=133300&caller=view). WinCC Basic V13.0 System Manual, 02/2014 4683 Hardware documentation 14.3 Distributed I/O CM PtP RS232 HF (6ES7 541-1AD00-0AB0) Information on the CM PtP RS232 HF point-to-point communication module is available here (https://support.automation.siemens.com/WW/llisapi.dll? func=cslib.csinfo&lang=en&objid=6ES75411AD000AB0&objaction=csviewmlfbbeitraege&su btype=133300&caller=view). RS422/485 CM PtP RS422/485 BA (6xxx 540-1AB00-xAA0) Information on the CM PtP RS422/485 BA point-to-point communication module (including SIPLUS variant) is available here (https://support.automation.siemens.com/WW/llisapi.dll? func=cslib.csinfo&lang=en&objid=6ES75401AB000AA0&objaction=csviewmlfbbeitraege&su btype=133300&caller=view). CM PtP RS422/485 HF (6xxx 541-1AB00-xAB0) Information on the CM PtP RS422/485 HF point-to-point communication module (including SIPLUS variant) is available here (https://support.automation.siemens.com/WW/llisapi.dll? func=cslib.csinfo&lang=en&objid=6ES75411AB000AB0&objaction=csviewmlfbbeitraege&su btype=133300&caller=view). 14.3.1.9 Power supply module PS 25W 24VDC (6ES7 505-0KA00-0AB0) Information on the PS 25W 24VDC power supply module is available here (https:// support.automation.siemens.com/WW/llisapi.dll? func=cslib.csinfo&lang=en&objid=6ES75050KA000AB0&objaction=csviewmlfbbeitraege&su btype=133300&caller=view). PS 60W 24/48/60VDC (6xxx 505-0RA00-xAB0) Information on the PS 60W 24/48/60VDC power supply module (including SIPLUS variant) is available here (https://support.automation.siemens.com/WW/llisapi.dll? func=cslib.csinfo&lang=en&objid=6ES75050RA000AB0&objaction=csviewmlfbbeitraege&su btype=133300&caller=view). 4684 WinCC Basic V13.0 System Manual, 02/2014 Hardware documentation 14.3 Distributed I/O PS 60W 120/230VAC/DC (6xxx 507-0RA00-xAB0) Information on the power supply module PS 60W 120/230VAC/DC (including SIPLUS variant) is available here (https://support.automation.siemens.com/WW/llisapi.dll? func=cslib.csinfo&lang=en&objid=6ES75070RA000AB0&objaction=csviewmlfbbeitraege&su btype=133300&caller=view). 14.3.1.10 Technology modules TM Count 2x24V (6ES7 550-1AA00-0AB0) Information on the counter module TM Count 2x24V is available here (https:// support.automation.siemens.com/WW/llisapi.dll? func=cslib.csinfo&lang=en&objid=6ES75501AA000AB0&objaction=csviewmlfbbeitraege&su btype=133300&caller=view). TM PosInput 2 (6ES7 551-1AB00-0AB0) Information on the positioning module TM PosInput 2 is available here (https:// support.automation.siemens.com/WW/llisapi.dll? func=cslib.csinfo&lang=en&objid=6ES75511AB000AB0&objaction=csviewmlfbbeitraege&su btype=133300&caller=view). CM AS-i Master (3RK7 137-6SA00-0BC1) Information on the CM AS-i Master module is available here (https:// support.automation.siemens.com/WW/llisapi.dll? func=cslib.csinfo&lang=en&objid=3RK71376SA000BC1&objaction=csviewmlfbbeitraege&su btype=133300&caller=view). F-CM AS-i (3RK7 136-6SC00-0BC1) Information on the F-CM AS-i module is available here (https:// support.automation.siemens.com/WW/llisapi.dll? func=cslib.csinfo&lang=en&objid=3RK71366SC000BC1&objaction=csviewmlfbbeitraege&su btype=133300&caller=view). WinCC Basic V13.0 System Manual, 02/2014 4685 Hardware documentation 14.3 Distributed I/O 14.3.2 ET 200SP 14.3.2.1 CPU CPU 1510SP-1 (6ES7 510-1DJ00-0AB0) Information on the 1510SP-1 CPU is available here (https://support.automation.siemens.com/ WW/llisapi.dll? func=cslib.csinfo&lang=en&objid=6ES75101DJ000AB0&objaction=csviewmlfbbeitraege&sub type=133300&caller=view). CPU 1512SP-1 (6ES7 512-1DK00-0AB0) Information on the 1512SP-1 CPU is available here (https://support.automation.siemens.com/ WW/llisapi.dll? func=cslib.csinfo&lang=en&objid=6ES75121DK000AB0&objaction=csviewmlfbbeitraege&su btype=133300&caller=view). 14.3.2.2 Interface modules PROFINET IM 155-6 PN ST (6ES7 155-6AU00-0BN0) You can find information on the interface module IM 155-6 PN ST here (https:// support.automation.siemens.com/WW/llisapi.dll? func=cslib.csinfo&lang=en&objid=6ES71556AU000BN0&objaction=csviewmlfbbeitraege&su btype=133300&caller=view). IM 155-6 PN HF (6ES7 1556AU000CN0) You can find information on the interface module IM 155-6 PN HF here (https:// support.automation.siemens.com/WW/llisapi.dll? func=cslib.csinfo&lang=en&objid=6ES71556AU000CN0&objaction=csviewmlfbbeitraege&su btype=133300&caller=view). 4686 WinCC Basic V13.0 System Manual, 02/2014 Hardware documentation 14.3 Distributed I/O PROFIBUS IM 155-6 DP HF (6ES7 155-6BU00-0CN0) Information on the IM 155-6 DP HF interface module is available here (https:// support.automation.siemens.com/WW/llisapi.dll? func=cslib.csinfo&lang=en&objid=6ES71556BU000CN0&objaction=csviewmlfbbeitraege&su btype=133300&caller=view). Other fieldbuses IM 155-6 Receive (6ES7 155-6DU00-0BN0) Information on the IM 155-6 Receive interface module is available here (https:// support.automation.siemens.com/WW/llisapi.dll? func=cslib.csinfo&lang=en&objid=6ES71556DU000BN0&objaction=csviewmlfbbeitraege&su btype=133300&caller=view). 14.3.2.3 Digital input modules DI 4x120..230VAC ST (6ES7 131-6FD00-0BB1) Information on the DI 4x120..230VAC ST digital input module is available here (https:// support.automation.siemens.com/WW/llisapi.dll? func=cslib.csinfo&lang=en&objid=6ES71316FD000BB1&objaction=csviewmlfbbeitraege&su btype=133300&caller=view). DI 8x24VDC ST (6ES7 131-6BF00-0BA0) Information on the digital input module DI 8x24VDC ST is available here (https:// support.automation.siemens.com/WW/llisapi.dll? func=cslib.csinfo&lang=en&objid=6ES71316BF000BA0&objaction=csviewmlfbbeitraege&sub type=133300&caller=view). DI 8x24VDC HF (6ES7 131-6BF00-0CA0) Information on the digital input module DI 8x24VDC HF is available here (https:// support.automation.siemens.com/WW/llisapi.dll? func=cslib.csinfo&lang=en&objid=6ES71316BF000CA0&objaction=csviewmlfbbeitraege&su btype=133300&caller=view). WinCC Basic V13.0 System Manual, 02/2014 4687 Hardware documentation 14.3 Distributed I/O DI 8xNAMUR HF (6ES7 131-6TF00-0CA0) Information on the DI 8xNAMUR HF digital input module is available here (https:// support.automation.siemens.com/WW/llisapi.dll? func=cslib.csinfo&lang=en&objid=6ES71316TF000CA0&objaction=csviewmlfbbeitraege&sub type=133300&caller=view). DI 8x24VDC SRC BA (6ES7 131-6BF60-0AA0) Information on the DI 8x24VDC SRC BA digital input module is available here (https:// support.automation.siemens.com/WW/llisapi.dll? func=cslib.csinfo&lang=en&objid=6ES71316BF6000A0&objaction=csviewmlfbbeitraege&sub type=133300&caller=view). DI 16x24VDC ST (6ES7 131-6BH00-0BA0) Information on the digital input module DI 16x24VDC ST is available here (https:// support.automation.siemens.com/WW/llisapi.dll? func=cslib.csinfo&lang=en&objid=6ES71316BH000BA0&objaction=csviewmlfbbeitraege&su btype=133300&caller=view). 14.3.2.4 Digital output modules DQ 4x24VDC/2A ST (6ES7 132-6BD20-0BA0) Information on the digital output module DQ 4x24VDC/2A ST is available here (https:// support.automation.siemens.com/WW/llisapi.dll? func=cslib.csinfo&lang=en&objid=6ES71326BD200BA0&objaction=csviewmlfbbeitraege&su btype=133300&caller=view). DQ 4x24..230VAC/2A ST (6ES7 132-6FD00-0BB1) Information on the DQ 4x24..230VAC/2A ST digital output module is available here (https:// support.automation.siemens.com/WW/llisapi.dll? func=cslib.csinfo&lang=en&objid=6ES71326FD000BB1&objaction=csviewmlfbbeitraege&su btype=133300&caller=view). DQ 4x24VDC/2A HF (6ES7 132-6BD20-0CA0) Information on the DQ 4x24VDC/2A HF digital output module is available here (https:// support.automation.siemens.com/WW/llisapi.dll? 4688 WinCC Basic V13.0 System Manual, 02/2014 Hardware documentation 14.3 Distributed I/O func=cslib.csinfo&lang=en&objid=6ES71326BD200CA0&objaction=csviewmlfbbeitraege&su btype=133300&caller=view). RQ 4x120..230VUC/5A NO ST (6ES7 132-6HD00-0BB0) Information on the RQ 4x120..230VUC/5A NO ST relay output module is available here (https:// support.automation.siemens.com/WW/llisapi.dll? func=cslib.csinfo&lang=en&objid=6ES71326HD000BB0&objaction=csviewmlfbbeitraege&su btype=133300&caller=view). RQ 4x24VUC/2A CO ST (6ES7 132-6GD50-0BA0) Information on the RQ 4x24VUC/2A CO ST relay output module is available here. DQ 8x24VDC/0.5A ST (6ES7 132-6BF00-0BA0) Information on the digital output module DQ 8x24VDC/0.5A ST is available here (https:// support.automation.siemens.com/WW/llisapi.dll? func=cslib.csinfo&lang=en&objid=6ES71326BF000BA0&objaction=csviewmlfbbeitraege&sub type=133300&caller=view). DQ 8x24VDC/0.5A SNK BA (6ES7 132-6BF60-0AA0) Information on the DQ 8x24VDC/0.5A SNK BA digital output module is available here (https:// support.automation.siemens.com/WW/llisapi.dll? func=cslib.csinfo&lang=en&objid=6ES71326BF600AA0&objaction=csviewmlfbbeitraege&sub type=133300&caller=view). DQ 8x24VDC/0.5A HF (6ES7 132-6BF00-0CA0) Information on the digital output module DQ 8x24VDC/0.5A HF is available here (https:// support.automation.siemens.com/WW/llisapi.dll? func=cslib.csinfo&lang=en&objid=6ES71326BF000CA0&objaction=csviewmlfbbeitraege&su btype=133300&caller=view). DQ 16x24VDC/0.5A ST (6ES7 132-6BH00-0BA0) Information on the digital output module DQ 16x24VDC/0.5A ST is available here (https:// support.automation.siemens.com/WW/llisapi.dll? func=cslib.csinfo&lang=en&objid=6ES71326BH000BA0&objaction=csviewmlfbbeitraege&su btype=133300&caller=view). WinCC Basic V13.0 System Manual, 02/2014 4689 Hardware documentation 14.3 Distributed I/O 14.3.2.5 Analog input modules AI 2xU/I 2-/4-wire HF (6ES7 134-6HB00-0CA1) Information on the AI 2xU/I 2-/4-wire HF analog input module is available here (https:// support.automation.siemens.com/WW/llisapi.dll? func=cslib.csinfo&lang=en&objid=6ES71346HB000CA1&objaction=csviewmlfbbeitraege&su btype=133300&caller=view). AI 2xU/I 2-/4-wire HS (6ES7 134-6HB00-0DA1) Information on the AI 2xU/I 2-/4-wire HS analog input module is available here (https:// support.automation.siemens.com/WW/llisapi.dll? func=cslib.csinfo&lang=en&objid=6ES71346HB000DA1&objaction=csviewmlfbbeitraege&su btype=133300&caller=view). AI 4xI 2-/4-wire ST (6ES7 134-6GD00-0BA1) Information on the analog input module AI 4xI 2-/4-wire ST is available here (https:// support.automation.siemens.com/WW/llisapi.dll? func=cslib.csinfo&lang=en&objid=6ES71346GD000BA1&objaction=csviewmlfbbeitraege&su btype=133300&caller=view). AI 4xU/I 2-wire ST (6ES7 134-6HD00-0BA1) Information on the analog input module AI 4xU/I 2-wire ST is available here (https:// support.automation.siemens.com/WW/llisapi.dll? func=cslib.csinfo&lang=en&objid=6ES71346HD000BA1&objaction=csviewmlfbbeitraege&su btype=133300&caller=view). AI 4xRTD/TC 2-/3-/4-wire HF (6ES7 134-6JD00-0CA1) Information on the analog input module AI 4xRTD/TC 2-/3-/4-wire HF is available here (https:// support.automation.siemens.com/WW/llisapi.dll? func=cslib.csinfo&lang=en&objid=6ES71346JD000CA1&objaction=csviewmlfbbeitraege&sub type=133300&caller=view). 4690 WinCC Basic V13.0 System Manual, 02/2014 Hardware documentation 14.3 Distributed I/O AI 8xRTD/TC 2-wire HF (6ES7 134-6JF00-0CA1) Information on the AI 8xRTD/TC 2-wire HF analog input module is available here (https:// support.automation.siemens.com/WW/llisapi.dll? func=cslib.csinfo&lang=en&objid=6ES71346JF000CA1&objaction=csviewmlfbbeitraege&sub type=133300&caller=view). AI EnergyMeter ST (6ES7 134-6PA00-0BD0) Information on the AI EnergyMeter ST relay output module is available here (https:// support.automation.siemens.com/WW/llisapi.dll? func=cslib.csinfo&lang=en&objid=6ES71346PA000BD0&objaction=csviewmlfbbeitraege&su btype=133300&caller=view). 14.3.2.6 Analog output modules AQ 2xU/I HF (6ES7 135-6HB00-0CA1) Information on the AQ 2xU/I HF analog output module is available here (https:// support.automation.siemens.com/WW/llisapi.dll? func=cslib.csinfo&lang=en&objid=6ES71356HB000CA1&objaction=csviewmlfbbeitraege&su btype=133300&caller=view). AQ 2xU/I HS (6ES7 135-6HB00-0DA1) Information on the analog output module AQ 2xU/I HS is available here (https:// support.automation.siemens.com/WW/llisapi.dll? func=cslib.csinfo&lang=en&objid=6ES71356HB000DA1&objaction=csviewmlfbbeitraege&su btype=133300&caller=view). AQ 4xU/I ST (6ES7 135-6HD00-0BA1) Information on the analog output module AQ 4xU/I ST is available here (https:// support.automation.siemens.com/WW/llisapi.dll? func=cslib.csinfo&lang=en&objid=6ES71356HD000BA1&objaction=csviewmlfbbeitraege&su btype=133300&caller=view). WinCC Basic V13.0 System Manual, 02/2014 4691 Hardware documentation 14.3 Distributed I/O 14.3.2.7 Communication modules CM PtP (6ES7 137-6AA00-0BA0) Information on the CM PtP communication module is available here (https:// support.automation.siemens.com/WW/llisapi.dll? func=cslib.csinfo&lang=en&objid=6ES71376AA000BA0&objaction=csviewmlfbbeitraege&su btype=133300&caller=view). 14.3.2.8 Power modules PM 120..230VAC/10A ST (6ES7 133-6AA00-0BC0) Information on the PM 120..230VAC/10A ST power module is available here (https:// support.automation.siemens.com/WW/llisapi.dll? func=cslib.csinfo&lang=en&objid=6ES71336AA000BC0&objaction=csviewmlfbbeitraege&su btype=133300&caller=view). 14.3.2.9 Special modules Server module (6ES7 193-6PA00-0AA0) Information on the server module is available here (https://support.automation.siemens.com/ WW/llisapi.dll? func=cslib.csinfo&lang=en&objid=6ES71936PA000AA0&objaction=csviewmlfbbeitraege&su btype=133300&caller=view). BusAdapter BA 2xSCRJ (6ES7 193-6AP00-0AA0) Information on the BA 2xSCRJ BusAdapter is available here. See also Link to the device manual (https://support.automation.siemens.com/WW/llisapi.dll? func=cslib.csinfo&lang=en&objid=6ES71936AP000AA0&objaction=csviewmlfbbeitraege&su btype=133300&caller=view) BusAdapter BA 2xRJ45 (6ES7 193-6AR00-0AA0) Information on the BusAdapter BA 2xRJ45 is available here (https:// support.automation.siemens.com/WW/llisapi.dll? 4692 WinCC Basic V13.0 System Manual, 02/2014 Hardware documentation 14.3 Distributed I/O func=cslib.csinfo&lang=en&objid=6ES71936AR000AA0&objaction=csviewmlfbbeitraege&su btype=133300&caller=view). BusAdapter FC (6ES7 193-6AF00-0AA0) Information on the BusAdapter FC is available here (https://support.automation.siemens.com/ WW/llisapi.dll? func=cslib.csinfo&lang=en&objid=6ES71936AF000AA0&objaction=csviewmlfbbeitraege&sub type=133300&caller=view). BusAdapter Send (6ES7 193-6AS00-0AA0) Information on the BusAdapter Send is available here (https:// support.automation.siemens.com/WW/llisapi.dll? func=cslib.csinfo&lang=en&objid=6ES71936AS000AA0&objaction=csviewmlfbbeitraege&su btype=133300&caller=view). BusAdapter Receive (6ES7 193-6AE00-0AA0) Information on the BusAdapter Receive is available here (https:// support.automation.siemens.com/WW/llisapi.dll? func=cslib.csinfo&lang=en&objid=6ES71936AE000AA0&objaction=csviewmlfbbeitraege&su btype=133300&caller=view). 14.3.2.10 Technology modules TM Count 1x24V (6ES7 138-6AA00-0BA0) Information on the relay output module TMCount 1x24V is available here (https:// support.automation.siemens.com/WW/llisapi.dll? func=cslib.csinfo&lang=en&objid=6ES71386AA000BA0&objaction=csviewmlfbbeitraege&su btype=133300&caller=view). TM PosInput 1 (6ES7 138-6BA00-0BA0) Information on the positioning module TM PosInput 1 is available here (https:// support.automation.siemens.com/WW/llisapi.dll? func=cslib.csinfo&lang=en&objid=6ES71386BA000BA0&objaction=csviewmlfbbeitraege&su btype=133300&caller=view). WinCC Basic V13.0 System Manual, 02/2014 4693 Hardware documentation 14.3 Distributed I/O IO-Link Master Module (6ES7 137-6BD00-0BA0) Information on the relay output module IO-Link Master Module is available here (https:// support.automation.siemens.com/WW/llisapi.dll? func=cslib.csinfo&lang=en&objid=6ES71376BD000BA0&objaction=csviewmlfbbeitraege&su btype=133300&caller=view). 4694 WinCC Basic V13.0 System Manual, 02/2014 Index -, 1481 add external graphic , 4064 add graphic to graphics library, 4063 6ES7 1556AU000CN0, 4686 Absolute value, 1857, 2137 Connection configuration General, 474 External source file Editing, 1564 Opening, 1564 Module Inserting, 418 Quality code, 1074 SetBacklightColor, 3555 SIMATIC PC station Load, 65 STARTUP Warm restart, 952 Zoom in/out, (See Zoom) " "WWW" instruction, 691 # #, 1382 & &, 1485, 1486 ( (), 1486 * *, 1481 WinCC Basic V13.0 System Manual, 02/2014 **, 1481 *.bmp, 3232 *.cer, 610 *.dat, 610 *.emf, 3232 *.gif, 3232 *.ico, 3232 *.jpeg, 3232 *.jpg, 3232 *.p12, 538, 610 *.tif, 3232 *.wmf, 3232 . .Net service packs, 30 .Net versions, 30 / /, 1481 : :=, 1486, 1487 :P, 962 + +, 1481 < <, 1484 <=, 1484 <>, 1484, 1486 = =, 1484 ==, 1486 > >, 1484 >=, 1484 4695 Index 3 32-bit down counter, 1039 3DES, 588 3RK7 136-6SC00-0BC1, 4686 3RK7 137-6SA00-0BC1, 4685 3RK7 243-2AA30-0XB0, 4677 6 6AG1 505-0RA00-0AB0, 4685 6AG1 507-0RA00-0AB0, 4685 6AG1 521-1BH50-7AA0, 4679 6AG1 521-1FH00-7AA0, 4679 6AG1 522-1BF00-7AB0, 4680 6AG1 522-5FF00-7AB0, 4680 6AG1 522-5HF00-2AB0, 4680 6AG1 531-7NF10-7AB0, 4682 6AG1 532-5HF00-7AB0, 4682 6AG1 540-1AB00-7AA0, 4684 6AG1 540-1AD00-7AA0, 4684 6AG1 541-1AB00-7AB0, 4684 6ES7 131-6BF00-0BA0, 4687 6ES7 131-6BF00-0CA0, 4687 6ES7 131-6BF60-0AA0, 4688 6ES7 131-6BH00-0BA0, 4688 6ES7 131-6FD00-0BB1, 4687 6ES7 131-6TF00-0CA0, 4688 6ES7 132-6BD20-0BA0, 4688 6ES7 132-6BD20-0CA0, 4689 6ES7 132-6BF00-0BA0, 4689 6ES7 132-6BF00-0CA0, 4689 6ES7 132-6BF60-0AA0, 4689 6ES7 132-6BH00-0BA0, 4690 6ES7 132-6FD00-0BB1, 4688 6ES7 132-6GD50-0BA0, 4689 6ES7 132-6HD00-0BB0, 4689 6ES7 133-6AA00-0BC0, 4692 6ES7 134-6GD00-0BA1, 4690 6ES7 134-6HB00-0CA1, 4690 6ES7 134-6HB00-0DA1, 4690 6ES7 134-6HD00-0BA1, 4690 6ES7 134-6JD00-0CA1, 4690 6ES7 134-6JF00-0CA1, 4691 6ES7 134-6PA00-0BD0, 4691 6ES7 135-6HB00-0CA1, 4691 6ES7 135-6HB00-0DA1, 4691 6ES7 135-6HD00-0BA1, 4691 6ES7 137-6AA00-0BA0, 4692 6ES7 137-6BD00-0BA0, 4694 4696 6ES7 138-6AA00-0BA0, 4693 6ES7 138-6BA00-0BA0, 4694 6ES7 155-5AA00-0AB0, 4678 6ES7 155-5AA00-0AC0, 4678 6ES7 155-6AU00-0BN0, 4686 6ES7 155-6BU00-0CN0, 4687 6ES7 155-6DU00-0BN0, 4687 6ES7 193-6AE00-0AA0, 4693 6ES7 193-6AF00-0AA0, 4693 6ES7 193-6AP00-0AA0, 4692 6ES7 193-6AR00-0AA0, 4693 6ES7 193-6AS00-0AA0, 4693 6ES7 193-6PA00-0AA0, 4692 6ES7 211-1AD30-0XB0, 4664 6ES7 211-1AE31-0XB0, 4664 6ES7 211-1AE40-0XB0, 4664 6ES7 211-1BD30-0XB0, 4664 6ES7 211-1BE31-0XB0, 4664 6ES7 211-1BE40-0XB0, 4664 6ES7 211-1HD30-0XB0, 4664 6ES7 211-1HE31-0XB0, 4664 6ES7 211-1HE40-0XB0, 4664 6ES7 212-1AD30-0XB0, 4665 6ES7 212-1AE31-0XB0, 4665 6ES7 212-1AE40-0XB0, 4665 6ES7 212-1BD30-0XB0, 4665 6ES7 212-1BE31-0XB0, 4665 6ES7 212-1BE40-0XB0, 4665 6ES7 212-1HD30-0XB0, 4665 6ES7 212-1HE31-0XB0, 4665 6ES7 212-1HE40-0XB0, 4665 6ES7 214-1AE30-0XB0, 4666 6ES7 214-1AG31-0XB0, 4666 6ES7 214-1AG40-0XB0, 4666 6ES7 214-1BE30-0XB0, 4666 6ES7 214-1BG31-0XB0, 4666 6ES7 214-1BG40-0XB0, 4666 6ES7 214-1HE30-0XB0, 4666 6ES7 214-1HG31-0XB0, 4666 6ES7 214-1HG40-0XB0, 4666 6ES7 215-1AG31-0XB0, 4667 6ES7 215-1AG40-0XB0, 4667 6ES7 215-1BG31-0XB0, 4667 6ES7 215-1BG40-0XB0, 4667 6ES7 215-1HG31-0XB0, 4667 6ES7 215-1HG40-0XB0, 4667 6ES7 217-1AG40-0XB0, 4667 6ES7 221-1BF30-0XB0, 4670 6ES7 221-1BF32-0XB0, 4670 6ES7 221-1BH30-0XB0, 4670 6ES7 221-1BH32-0XB0, 4670 6ES7 221-3AD30-0XB0, 4668 WinCC Basic V13.0 System Manual, 02/2014 Index 6ES7 221-3BD30-0XB0, 4668 6ES7 222-1AD30-0XB0, 4668 6ES7 222-1BD30-0XB0, 4668 6ES7 222-1BF30-0XB0, 4671 6ES7 222-1BF32-0XB0, 4671 6ES7 222-1BH30-0XB0, 4671 6ES7 222-1BH32-0XB0, 4671 6ES7 222-1HF30-0XB0, 4671 6ES7 222-1HF32-0XB0, 4671 6ES7 222-1HH30-0XB0, 4671 6ES7 222-1HH32-0XB0, 4671 6ES7 222-1XF30-0XB0, 4671 6ES7 222-1XF32-0XB0, 4671 6ES7 223-0BD30-0XB0, 4668 6ES7 223-1BH30-0XB0, 4672 6ES7 223-1BH32-0XB0, 4672 6ES7 223-1BL30-0XB0, 4672 6ES7 223-1BL32-0XB0, 4672 6ES7 223-1PH30-0XB0, 4672 6ES7 223-1PH32-0XB0, 4672 6ES7 223-1PL30-0XB0, 4672 6ES7 223-1PL32-0XB0, 4672 6ES7 223-1QH30-0XB0, 4672 6ES7 223-1QH32-0XB0, 4672 6ES7 223-3AD30-0XB0, 4668 6ES7 223-3BD30-0XB0, 4668 6ES7 231-4HA30-0XB0, 4668 6ES7 231-4HD30-0XB0, 4674 6ES7 231-4HD32-0XB0, 4674 6ES7 231-4HF30-0XB0, 4674 6ES7 231-4HF32-0XB0, 4674 6ES7 231-5ND30-0XB0, 4674 6ES7 231-5ND32-0XB0, 4674 6ES7 231-5PA30-0XB0, 4668 6ES7 231-5PD30-0XB0, 4674 6ES7 231-5PD32-0XB0, 4674 6ES7 231-5PF30-0XB0, 4674 6ES7 231-5PF32-0XB0, 4674 6ES7 231-5QA30-0XB0, 4668 6ES7 231-5QD30-0XB0, 4674 6ES7 231-5QD32-0XB0, 4674 6ES7 231-5QF30-0XB0, 4674 6ES7 231-5QF32-0XB0, 4674 6ES7 232-4HA30-0XB0, 4668 6ES7 232-4HB30-0XB0, 4674 6ES7 232-4HB32-0XB0, 4674 6ES7 232-4HD30-0XB0, 4674 6ES7 232-4HD32-0XB0, 4674 6ES7 234-4HE30-0XB0, 4675 6ES7 234-4HE32-0XB0, 4675 6ES7 241-1AH30-0XB0, 4676 6ES7 241-1AH32-0XB0, 4676 WinCC Basic V13.0 System Manual, 02/2014 6ES7 241-1CH30-0XB0, 4676 6ES7 241-1CH30-1XB0, 4668, 4669 6ES7 241-1CH31-0XB0, 4676 6ES7 241-1CH32-0XB0, 4676 6ES7 278-4BD32-0XB0, 4678 6ES7 505-0KA00-0AB0, 4684 6ES7 505-0RA00-0AB0, 4684 6ES7 507-0RA00-0AB0, 4685 6ES7 510-1DJ00-0AB0, 4686 6ES7 512-1DK00-0AB0, 4686 6ES7 521-1BH00-0AB0, 4679 6ES7 521-1BH10-0AA0, 4678 6ES7 521-1BL10-0AA0, 4679 6ES7 522-1BF00-0AB0, 4679 6ES7 522-1BH00-0AB0, 4680 6ES7 522-1BH10-0AA0, 4680 6ES7 522-1BL00-0AB0, 4681 6ES7 522-1BL10-0AA0, 4680 6ES7 522-5FF00-0AB0, 4680 6ES7 522-5HF00-0AB0, 4680 6ES7 523-1BL00-0AA0, 4681 6ES7 531-7KF00-0AB0, 4681 6ES7 531-7NF10-0AB0, 4681 6ES7 531-7QD00-0AB0, 4681 6ES7 532-5HD00-0AB0, 4682 6ES7 532-5HF00-0AB0, 4682 6ES7 532-5NB00-0AB0, 4682 6ES7 534-7QE00-0AB0, 4682 6ES7 540-1AB00-0AA0, 4684 6ES7 540-1AD00-0AA0, 4683 6ES7 541-1AB00-0AB0, 4684 6ES7 541-1AD00-0AB0, 4684 6ES7 550-1AA00-0AB0, 4685 6GK7 242-5DX30-0XE0, 4675 6GK7 242-5DX31-0XE0, 4675 6GK7 242-7KX30-0XE0, 4675 6GK7 243-1JX30-0XE0, 4675 6GK7 243-5DX30-0XE0, 4675 6GK7 243-5DX31-0XE0, 4675 6GK7 542-1AX00-0XE0, 4683 6GK7 542-5DX00-0XE0, 4683 6GK7 543-1AX00-0XE0, 4683 6GT2 002-0LA00, 4677 7 7MH4 960-2AA01, 4677 7MH4 960-4AA01, 4677 4697 Index A AB, 1309 Ability to read back connection parameters, 496 ABS, 1857, 2137, 2348 Absolute Addressing of a tag, 3334, 3636 Absolute value, 2348 Access control, 832 Automatic learning, 832 Access protection, 3487 Access protection level 1, 4615 Access protection level 2, 4615 Advantages, 4615 Configuring, 3491 Factory state, 4614 User administration, 3486 Validity, 4614 Access to operands, 1185, 1186, 1187, 1189, 1190, 1192, 1193 Accessible devices, 926, 3664, 3713, 3766 ACK, 4168 Acknowledge, 3374, 3583 Alarm, 4170 Error alarm, 4170 AcknowledgeAlarm, 3538 Acknowledgment, 3376 Configuring, 3399, 3400, 3401 Acknowledgment concept Alarm with simple acknowledgment, 3378 Alarm without acknowledgment, 3378 Acknowledgment model, 3378 ACL, 832 ACOS, 1874, 2154, 2363 Acquisition cycle Area pointer, 3641 Tag, 3350, 3357, 3367 Acquisition mode Tag, 3350 ACT_TINT, 2703 Actions Basics of redoing actions, 312 Basics of undoing, 312 Redoing, 316 Undoing, 315 activate, 3575 Activate Project language, 4052 ActivateCleanScreen, 3512 ActivatePreviousScreen, 3513 ActivateScreen, 3510 4698 ActivateScreenByNumber, 3511 Active Area pointer, 3641 Active bus module (ET 200M), 1072 Active nodes, 592 AD, 1309 Adapting a project For a different HMI device, 4122 Add, 1848, 2126 Objects to the group, 3238 ADD, 1848, 2126 Add empty line, 4366 Add separator line, 4366 Adding Adding timers with T_ADD, 2507 Additional field devices (PROFIBUS and PROFINET), 900, 929 Address Area pointer, 3641 Mitsubishi, 3905 Omron Host Link, 3961 address conversion Instructions for, 2805 Address multiplexing with absolute addresses, 3358 with symbolic addresses, 3358 Address overview, 425 Address packing, 892 Address range, 562 Changing, 666 Address register, 1201, 1202 Addresses Assigning, 668 Determining a module with GEO_LOG, 2813 Interrupt with packed, 898 Pack, 892 Read station address with GetStationInfo, 2748 Unpack, 893 Addressing, 962 Addressing tags indirectly, 3354, 3355 Allen-Bradley, 3865, 3883 Allen-Bradley Ethernet IP, 3861 Changing, 666 Ethernet/IP, 3865, 3883 General, 665 MPI, 3782 Multiplexing, 3354 Addressing operands, 1185, 1186, 1187, 1189, 1190, 1192, 1193, 1196, 1197, 1198, 1200, 1201, 1202 AdjustContrast, 3509 Admin, 4163 Administrator, 540 WinCC Basic V13.0 System Manual, 02/2014 Index Advanced Encryption Standard (AES), 588 Advanced mode Global firewall rules, 548 AES, 588 AES-128, 583 Aggressive mode, 588 Aging time, 836 Alarm Acknowledge, 4170 Components, 3379 Configuring, 3385, 3391 Displaying, 3312 Editing, 4170 Exporting, 4022 Importing, 4023 in Runtime, 4164 In Runtime, 3402 Inspector window, 53 System function, 3407 Alarm buffer in Runtime, 4165 In Runtime, 3403 Alarm buffer overflow, 3582 Alarm class, 3379 in Runtime, 4164 In Runtime, 3402 Layout, 3404, 4167 Alarm classes, 3375 Custom, 3375 Name change through migration, 123 Predefined, 3375 Use, 3375 Alarm display, 944 "Active alarms" view, 946 Acknowledging an alarm, 947 Archive view, 944 Clear archive, 946 Export archive, 946 Ignoring alarms, 948 Layout of the alarms in the "Active alarms" view, 946 Layout of the alarms in the archive view, 945 Receiving alarms, 945 Using the keyboard, 948 Alarm event Acknowledge, 3374 Incoming, 3374 Outgoing, 3374 Alarm group, 3378, 3380 Configuring, 3383 Creating, 3383 Migration, 122 WinCC Basic V13.0 System Manual, 02/2014 Alarm indicator, 53, 3317, 3394, 3405, 4168 Alarm classes, 3317 Configuring, 3397 Events, 3317 in Runtime, 4166 In Runtime, 3403 Layout, 3317, 3405 Operation, 3405 Alarm log in Runtime, 4165 Alarm message Acknowledgment by the PLC, 3691, 3741, 3799, 3838, 3850, 3893, 3920, 3949, 3966 Acknowledgment on the HMI device, 3691, 3742, 3799, 3839, 3851, 3893, 3921, 3950, 3966 Configure acknowledgment, 3691, 3741, 3799, 3838, 3850, 3892, 3920, 3949, 3965 Alarm number, 3379 Alarm status, 3380 Acknowledged, 3374 Incoming, 3374 Outgoing, 3374 Alarm system, 3371 Alarm text, 3380 Formatting, 3389 Output fields, 59 Removing format settings, 3389 Special characters, 59 Alarm types, 3372 Alarm view, 53, 3312, 3314, 3394, 3405, 4168 Alarm text window, 3405, 4168 Column, 3313 Configuring, 3395 Configuring the layout, 3396 Control element, 3313 Layout, 3312, 3404, 4167 Operation, 3405, 4168 Alarm window, 53, 3394 Configuring, 3397 in Runtime, 4166 In Runtime, 3403 Alarm with simple acknowledgment, 3378 Alarm without acknowledgment, 3378 Alarms Configuring, 3740, 3798, 3837, 3849 Data types, 3740, 3798, 3837, 3849 Modicon Modbus, 3948 Non-integrated connection, 3948 Output of a tag value, 3388 Restriction, 3920 AlarmViewAcknowledgeAlarm, 3537 AlarmViewEditAlarm, 3536 4699 Index AlarmViewShowOperatorNotes, 3537 Align Object flush, 3212 Allen-Bradley, 3852, 3873, 3874 Allen-Bradley DF1 communication driver, 3873, 3874 Analog alarm, 3892 Basic Panel, 3647 Communication drivers, 3853 Data type, 3892 DF1, 3853 EtherNet/IP, 3853 Mitsubishi, 3919 Allen-Bradley Area pointer, 3890 Allen-Bradley DF1 Configuring a connection, 3869 Connection, 3869, 3872 Connection parameters, 3870 CPU type, 3883 KF2 module, 3873, 3874 KF3 module, 3873, 3874 Migrating data types, 136 Valid data type, 3881 Allen-Bradley Ethernet IP Address multiplexing, 3865 Addressing, 3861 Addressing type, 3863 Migrating data types, 136 Allen-Bradley EtherNet/IP Configuring a connection, 3854 Connection, 3854, 3858 Connection parameters, 3856 Data type, 3859 Analog alarm, 3372 Allen-Bradley, 3892 Configuring, 3385, 3392 Limit value exceeded, 3348 Mitsubishi, 3919 Omron, 3964 Analog alarm types, 3372 Analog alarms Configuring, 3381 Analog module Resetting to factory settings, 1128 Analog value, 1937, 1939, 2219, 2222, 2427, 2429 Analog value processing, 1937, 1939, 2219, 2222, 2427, 2429 AND, 1485, 1486, 1971, 2015, 2016, 2255 Animation Configuring, 3268 Diagonal movement, 3271 4700 Direct movement, 3272 Green arrow in Overview, 3268 Horizontal movement, 3270 Multiple selection, 3275 Object group, 3274 Overview, 3268 Vertical movement, 3271 Antivirus programs, 73, 82 ANY, 1242 Appearance Dynamization of an object, 3269 Applet, 542 Application, 930 Button, 4153 Date/time field, 4145 Graphic IO field, 4149 Graphic view, 4149 IO field, 4146 Recipe view, 3319 Switch, 4154 Symbolic IO field, 4155 Trend view, 4151 User view, 3299 Arccosine, 1874, 2154, 2363 Archiving projects, 258, 259 Arcsine, 1872, 2153, 2362 Arctangent, 2364 Arctangent value, 1875, 2156 Area of unplugged modules, 412 Area pointer, 3639, 3674, 3723, 3783, 3822, 3967 Acquisition cycle, 3641 Active, 3641 Address, 3641 Allen-Bradley, 3890 Basic Panel, 3650 Comment, 3641 Connection, 3639, 3644 Connections editor, 3640 Coordination, 3971 Data record, 3438, 3682, 3733, 3790, 3830, 3975 Date/time, 3724, 3725 Job mailbox, 3680, 3731, 3788, 3828, 3973 Length, 3641 PLC tag, 3641 Pointer name, 3641 Project ID, 3679, 3730, 3787, 3827, 3972 Screen number, 3675, 3729, 3783, 3823, 3968 Tab, 3641 Trends, 3690, 3847 Area pointers Configuring, 3642 Coordination, 3678, 3727, 3786, 3826 WinCC Basic V13.0 System Manual, 02/2014 Index Creating, 3642 Date/time, 3675, 3784, 3823, 3969 Date/time PLC, 3677, 3785, 3824, 3970 Length, 3643 Mitsubishi, 3917 Modicon Modbus, 3946 Omron, 3963 ARP, 642 Diagnostics, 642 Table, 642 Arrange Object in the screen, 3204 Arrangement of byte sequence, 2188, 2382 Array, 57, 166, 1235, 1236, 3364, 3366 Creating, 3366 Indirect addressing, 3354, 3364 see ARRAY, 1383, 1531 ARRAY, 1198 Addressing, 1190 Declaration in global data blocks, 1531 Declaration in PLC data types, 1554 Declaration in the block interface, 1383 Example, 1238 Format, 1235, 1236 ARRAY component, 41 Array data block, 1908, 1910, 1912, 1916, 2190, 2192, 2194, 2198, 2384, 2386, 2387, 2390 ARRAY data block, 1148, 1151, 1187, 1190, 1334, 1524, 1527, 1547 Array element Location of use of HMI tag, 57 Name, 57 Array elements, 3364 ARRAY limits, 1489 Array tag, 3364 Char, 57 AS interface, 902 ASCII code table, 498 ASCII TSAP, 498 Asian, 29 Asian characters Input on the HMI device, 4136 Interpretation, 4136 Memory requirements, 4136 Asian languages Configuration, 4136 Font size, 4136 Text field length, 4136 Asian operating system, 4050 ASIN, 1872, 2153, 2362 Assembling manuals, 239 WinCC Basic V13.0 System Manual, 02/2014 Assign Object of a layer, 3292 Assigning a function to a function key, 3283 a graphic to a function key, 3286 Function key, 3278, 3280, 3282 Assigning an IP address Basics, 1120 from the project context, 1121 Using "Accessible devices", 1120 Assigning global data blocks , 42 Assigning symbol, 668 Assigning tag, 668 Assignment, 1487, 1745, 2022 Negate, 1746, 2023 Assignment list Enabling the display of retentive bit memories, 1626 Assignment list Meaning of symbols, 1620 Defining filter, 1623 Delete filter, 1623 Displaying, 1621 Example for displaying bit memory, 1619 Example for displaying inputs and outputs, 1619 Filter options, 1623 Filtering, 1624 Introduction, 1618 Setting view options, 1622 Structure, 1619 Asynchronous Transferring data, 3683, 3734, 3791, 3835, 3976 Asynchronous error event Delaying with DIS_AIRT, 2721 Disabling with DIS_IRT, 2718 Enabling with EN_AIRT, 2722 Enabling with EN_IRT, 2720 AT , 1193 ATAN, 1875, 2156, 2364 ATH, 2539 ATTACH, 968, 2692 ATTR_DB, 2802 Audit log, 606, 608 Authentication, 774, 867 Authentication methods, 586, 587 Authorization, 4157 Assignment, 3471, 3493 Changing the name, 3476 Configuring, 3485 Creating, 3470, 3491 Deleting, 3476 Managing, 3475 4701 Index Autocompletion Function, 1371 Insert tag, 1371, 1372 Inserting an instruction, 1372 Automatic commissioning, 926 Automation system, 3596, 3620 Local, 4649 Remote, 4649 Setting up, 3596 Autonegotiation, 925 Disabled, 3663, 3712, 3765 Availability Object for Basic Panels, 3297 Availability for specific devices Screen, 3185 AW, 1309 AWP command, 679, 680 AWP_In_Variable, 683 AWP_Out_Variable, 681 AX, 1309 Axis and command table technology object List of ErrorIDs and ErrorInfo, 4436 B Background color Dynamization, 3269 Backing up, 4158 HMI device data, 4132 Backup Data of the HMI device, 4116 Deleting, 4101 Rename, 4101 Backup from online device, 4541 Bar, 3298, 4144 Color transition, 3298 Display limit lines, 3298 Bar segment Defining, 3299 Basic mode, 1656 Basic Panel Area pointer, 3650 Communication drivers, 3647 Display and operating object, 3297 ETHERNET, 3649 IF1B, 3649 Interface, 3649 Mitsubishi, 3647 Modicon Modbus, 3647 Omron, 3647 OPC, 3647 Runtime start, 4108, 4129 4702 Basics Migration, 112 BCDCPL, 2013, 2298, 2504 Behavior Button, 4153 Date/time field, 4145 Graphic IO field, 4150 IO field, 4147 Simple recipe view, 3456, 4176 Switch, 4155 Symbolic IO field, 4156 Benefits of using TeleService, 4600 Bit (0, 1) Graphics list, 3261 Text list, 3253 Bit field Reset, 2026 Resetting, 1749 Set, 2025 Setting, 1748 Bit logic operations AND, 2015, 2016 EXCLUSIVE OR, 2019 Insert input, 2020 OR, 2017, 2018 Bit mask, 2004, 2289, 2495 Bit memories Enabling the display of retentive bit memories, 1626 Bit number (0 - 31) Graphics list , 3263 Text list, 3254 Bit string, 1209, 1210, 1211 64-bit, 1211 Bits Count, 2014, 2505 Counting, 2299 BITSUM, 2014, 2299, 2505 Bit-triggered trends, 3690, 3847 BLKMOV, 1923, 2205, 2413 Block Block, 2205 Changing passwords for know-how protected blocks, 1616 Closing, 1350 Comparing, 1570 Comparing code blocks, 1567 Comparing data blocks, 1568 Comparison, 1565 Compiling, 1594 Compiling in the program editor, 1597 Compiling in the project tree, 1596 WinCC Basic V13.0 System Manual, 02/2014 Index Consistency check, 1594, 1631, 1637 Consistency check in the call structure, 1632 Copying, 1337, 1340 Deleting offline, 1352 Deleting online, 1352 Displaying properties, 1348 Download to device, 1599, 1603 Downloading to a memory card, 1608 Downloading to device in RUN operating mode, 1602 Editing properties, 1348 Entering a comment, 1342 Entering a title, 1341 exporting to an external source file, 1562 Fill, 1902, 1927, 2184, 2210, 2379, 2418 Fill uninterruptible, 1904, 2186, 2380 Find and open, 1349 Inserting, 1337 Know-how protection, 1610 Leave, 2452 Move, 2175, 2372, 2413 Move uninterruptible, 1900, 1925, 2181, 2207, 2377, 2415 Moving, 1894, 1923 Opening, 1349 Opening know-how protected blocks, 1614 Optimized access, 1151, 1153 Pasting, 1341 Printing know-how protected blocks, 1615 Properties, 1343 Removing copy protection, 1612 Renaming, 1351 Saving, 1350 Setting up copy protection, 1612 Time stamp, 1346 Types, 1145 Upload from device, 1599 Uploading blocks from a memory card, 1609 Uploading blocks from device, 1607 Using a library, 1335 BLOCK, 1247 Block access Data block, 1536 Block call Basics, 1156 Calling as single instance or multiple instance, 1158 Correcting the call type, 1420, 1461 Inserting, 1417, 1459, 1505, 1506, 1508, 1509, 1510, 1511 Multi-instance, 1159 Nesting depth, 1157 WinCC Basic V13.0 System Manual, 02/2014 Single instance, 1159 Updating, 1419, 1460, 1512 Block comment Hiding, 1363 Showing, 1363 Block comparison Basics, 1565 Changing the block, 1589 Comparing code blocks, 1567 Comparing data blocks, 1568 Detailed comparison, 1571, 1572, 1576, 1579, 1582 Execute action, 287 Navigation, 1588 Synchronize scrolling, 1589 Updating comparison results, 284, 1590 Block consistency Checking, 1632 Checking in the dependency structure, 1637 Block folder, 1331 Block interface Declaring ARRAY, 1383 Declaring PLC data type, 1385 Declaring STRUCT, 1384 Declaring tags, 1381, 1382, 1386 Hiding, 1363 Importing and exporting tags, 1397 Multi-instance, 1387 Purpose of tag declaration, 1375 Retentivity, 1391 Showing, 1363 Structure, 1375 Tag properties, 1390, 1392 Updating, 1387 Valid data types, 1378, 1380 Block parameters, 1161, 1163, 1165, 1167, 1169, 1170, 1171, 1172 Basics, 1013 Block interface, 1375 Block property Displaying, 1348 Editing, 1348 Function, 1343 Overview, 1343 Bookmarks Deleting, 1496 Function, 1494 Navigating, 1495 Setting, 1495 BOOL, 1208, 1256, 1273 BOOL_TO_, 1273 4703 Index Borders Placeholder for document information, 303 Specifying the print area, 302 Boundaries, 926, 3664, 3713, 3766 Boundary reached, 3583 Branch, 2440, 2442 Closing, 1436 Definition, 1434, 1476 Deleting, 1437, 1477 Inserting, 1436, 1477 Rules, 1435 Rules , 1476 BRCV, 3089 Broadcast, 562, 570, 838 BSEND, 3086 Button, 3321, 4153 Application, 4153 Behavior, 4153 Configuring, 3491 Configuring access protection, 3487 Define hotkey, 3323 Graphic, 3322 Layout, 4153 Mode, 3322 Operation, 4153 Text, 3322 Buttons and Switches Library, 3988 BY, 2444 BYTE, 1209, 1257, 1274 BYTE_TO_, 1274 Bytes Swap, 2382 Swap, 1906, 2188 C CA certificate, 534, 537, 538, 4635 CA group certificate, 538 Cabling rules (PROFINET), 925, 3663, 3712, 3765 CALC, 1845, 2123 Calculate, 1420, 1462, 1845, 2123 CALCULATE, 1420, 1462 CalibrateTouchScreen, 3524 Calibrating, 1126 Overview, 1125 Call hierarchy, 1157 Call structure, 1626 Meaning of symbols, 1628 Displaying, 1630 Introduction, 1626 Setting view options, 1631 4704 Structure, 1629 Callback to a number specified during connection establishment, 4617 Calling FAQs for a module, 401 Calling manuals for a module, 401 CAN_DINT, 2708 CAN_TINT, 2702 Canceling a calibration, 1128 Canceling printing, 308 Cascaded counting function, 1039 CASE, 2442 Catalog, (see Hardware catalog) CD, 1820, 2100 CEIL, 1933, 2215, 2423 Certificate, 535, 587 Exporting, 534 Importing, 534 Renewing, 537 Replace, 538 Replacing, 538 self-signed, 537 signed by certificate authority, 537 Certificate authority, 534, 535 Certificate manager, 535 Change, 3576 Change word order Modicon MODBUS TCP/IP, 3926 ChangeConnection, 3566 Changeover contact, 1075 Changeover contact sensor type, 1074 Changing Displayed name of user group, 3476 Logoff time in runtime, 3483 Name of the user, 3482 Object size, 3209 Password, 3474 User group in runtime, 3483 Users, 4162 Changing a port interconnection Graphic view, 519 Changing and displaying operating mode (example), 3503 Changing the configuration online, 4532 Changing the device configuration online, 4532 Changing the name Authorization, 3476 User group, 3475 Users, 3474 Char Array tag, 57 CHAR, 1230, 1271, 1297 CHAR_TO_, 1297 WinCC Basic V13.0 System Manual, 02/2014 Index Character, 1230, 1231 Character string, 1231, 1233 Combining character strings with CONCAT, 2544 Comparing string tags with S_COMP, 2522 Converting from a hexadecimal number with HTA, 2541 Converting number to character string with VAL_STRG, 2526 Converting numeric character string with STRG_VAL, 2524 Converting to a hexadecimal number with ATH, 2539 Converting with S_CONV, 2523 Copying characters to character string with Chars_TO_Strg, 2531 Deleting characters with DELETE, 2546 Determine maximum length with MAX_LEN, 2532 Determining length with LEN, 2543 Finding a character with FIND, 2549 Inserting characters with INSERT, 2547 Reading out left character with LEFT, 2544 Reading out middle character with MID, 2545 Reading out right character with RIGHT, 2545 Replacing character with REPLACE, 2548 Characters, 29 Chars_TO_Strg, 2531 Checking Device version, 4098 Checking the connection, 3157 Checklist for troubleshooting the modem, 4659 Circle, 3308 Radius, 3308 CJ1, 3960 CJ2, 3960 Class of Service, 802 ClearAlarmBuffer, 3534 ClearAlarmBufferProTool, 3535 ClearAlarmBufferProtoolLegacy, 3535 cleared, 3575 Click, 3581 Click when flashing, 3581 Clock memory, 971, 993 Closing Runtime, 4131 CMP <, 1831, 2110 CMP <=, 1827, 2107 CMP <>, 1823, 2103 CMP ==, 1821, 2101 CMP >, 1829, 2109 CMP >=, 1825, 2105 Coil, 1745 Negate, 1746 WinCC Basic V13.0 System Manual, 02/2014 Color Diagnostics of Ethernet cables, 1093 Diagnostics of ports, 1093 Color transition Bar, 3298 Column Alarm view, 3313 Comfort Panel S7-1200, 64 Command table technology object Tools, 4359 Add new object, 4360 Basic parameters, 4361 Command table configuration, 4363 Command.Command[1...32] tags, 4465 Configuration window icons, 4361 Configuring activate warnings, 4363 Configuring duration, 4365 Configuring position / travel path, 4364 Configuring the command type, 4363 Configuring the next step, 4365 Configuring the step code, 4365 Configuring use axis parameters of, 4363 Configuring velocity, 4364 Extended parameters, 4361 General configuration, 4362 Usage, 4359 Comment Area pointer, 3641 Comments Inserting in SCL program, 1514 Commissioning HMI device, 4125 Communication, 998, 3595 Basics, 3596 Definition, 3595 S7 1200, 3699 S7 1500, 3651 S7 200, 3813 S7 300, 3753 S7 400, 3753 SIMATIC LOGO!, 3840 Third-party drivers, 3852 using area pointers, 3602 Communication drivers, 3602 Allen-Bradley, 3853 Basic Panel, 3647 Mitsubishi, 3894 Modicon Modbus, 3922 Omron, 3950 Communication load, 971 Communication network, 3620 4705 Index PROFINET, 3621 Communication partners HMI device, 3595 Networking, 3624 PLC, 3595 SIMATIC S7, 3699, 3753, 3810, 3819, 3822 Communication types Allen-Bradley, 3858 Connectable PLCs, 3929, 3940 Enabled, 3899, 3911, 3928, 3939, 3955 Ethernet/IP, 3858 Restriction, 3928, 3939 Communication via PUT/GET instructions Basic information on PUT/GET instructions, 501 Creating and assigning parameters to a connection, 506 Deleting an interconnection, 507 Overview of connection configuration, 502 Requirements, 501 Starting connection parameter assignment, 505 Communications Cycle load, 976 Communications instruction "AS_DIAL", 4649, 4650 "AS_MAIL", 4652 "PG_DIAL", 4648, 4649 "SMS_SEND", 4651 Communications load, 976 Communications module (CM), 3011 Communications modules, 984 Properties, 984 Communications port Configuring, 985 Communications protocol Defining, 988 Overview, 987 Compact, 3931, 3944 CompactLogix, 3861 Comparator operations Time tags, 2506 Compare Bit mask, 2004, 2289, 2495 Character strings with S_COMP, 2522 Equal, 1821, 2101 Greater or equal, 1825, 2105 Greater than, 1829, 2109 Less or equal, 1827, 2107 Less than, 1831, 2110 Not equal, 1823, 2103 Compare editor Changing the view, 288 Filtering the view, 283 4706 Overview, 276 Showing and hiding columns, 282 Specifying actions, 286 Compare offline/online Automatic device assignment, 523 Compare scan matrix, 2006, 2291, 2497 Comparing, 43 Comparing library objects, 326 Compatibility, 36 Backward compatibility of projects, 243 Global libraries from older product versions, 339 Projects from older program versions, 243 Projects with add-on software, 244 S7-1200 CPU firmware versions, 1021 WinCC version, 4093 Compile Block, 1596 Compiling Address parameters, 64 Blocks, 1594 Consistency check, 1594 Correcting compilation errors, 1598 Migrated project, 116 Project, 4104 Components Alarm, 3379 Commissioning, 3867, 3888, 3906, 3916, 3933, 3945, 3962 CONCAT, 2544 Configuration DP slave, 888 DP slave, simple, 879 Hardware, 404 Loading to device, 934 Loading to PG/PC, 935 Tag, 3343 Configuration control, 1053, 1065 Configuration mode, 758 Configuration phase, 4124 Configuration rights, 542 Configure a PROFIBUS subnet Matching parameters to one another, 439 Setting bus parameters, 439 Configure acknowledgment Alarm message, 3691, 3741, 3799, 3838, 3850, 3892, 3920, 3949, 3965 Configure alarms Allen-Bradley, 3891 Data types, 3919 Non-integrated connection, 3919 Special considerations, 3919 WinCC Basic V13.0 System Manual, 02/2014 Index Configured Loop-in-alarm, 3389 Configuring, 3385, 3393 Access protection, 3491 Alarm acknowledgment, 3399, 3400, 3401 Alarm group, 3383 Alarm view, 3395 Alarms, 3740, 3837, 3849 Analog alarm, 3385, 3392 Analog alarms, 3381 Authorization, 3485 Connections, 3801, 3802, 3804, 3813, 3841 Controller alarms, 3381 Discrete alarm, 3383, 3391 Discrete alarms, 3381 Event-driven tasks, 3387 HART variable, 1073 I-slave, 889 Layout of the alarm view, 3396 Multiple tags, 3343 Recipe view, 3452 Rectangle, 3246 System events, 3381 Trend view for values from the PLC, 3369 Configuring a connection Allen-Bradley DF1, 3869 Allen-Bradley EtherNet/IP, 3854 Mitsubishi FX, 3907 Mitsubishi MC TCP/IP, 3895 Modicon Modbus RTU, 3934 Modicon Modbus TCP, 3922 Omron Host Link, 3951 Configuring a PROFIBUS subnet Meaning of the bus parameters, 440 Configuring internal subnets manually, 637 Configuring IP network nodes manually, 636 Configuring MAC network nodes manually, 637 Configuring the network with Ethernet, 444, 3707, 3762 Creating private subnets, 446, 3708, 3763 Linking networks, 446, 3708, 3763 Relationship between IP address and subnet mask, 445, 3707, 3762 Setting the IP address, 445, 3707, 3762 Setting the subnet mask, 445, 3707, 3762 Configuring the remote modem, 4613 Connecting PLC, 3858, 3898, 3912, 3927, 3955 Connecting a TS Adapter with an external modem, 4613 Connecting a TS Adapter with an internal modem, 4613 WinCC Basic V13.0 System Manual, 02/2014 Connecting cable 6XV1440 - 2P for Mitsubishi PG protocol, 3912 Allen-Bradley cable 1784-CP10, 3878 Mitsubishi FX, 3912 Connecting cable 9-pole Sub D, RS 422, 3877 Connecting cables Point-to-point cable 1, Point-to-point cable 2, 3942 Connection, 451, 464, 3601 Address details, 1141 Allen-Bradley DF1, 3869, 3872 Allen-Bradley EtherNet/IP, 3854 Area pointer, 3639, 3644 Configuring, 3625, 3629, 3854, 3869, 3895, 3907, 3922, 3934, 3951 Configuring a connection when there is no or no clear network assignment, 456 Creating, 483, 3625, 3629 Deleting, 486 Highlighting, 3627 Integrated, 3625 integrated connection, 3334, 3636 Mitsubishi MC TCP/IP, 3895 Modicon, 3938 Modicon Modbus RTU, 3934 Modicon Modbus TCP, 3922 offline, 3680, 3730, 3788, 3827 Omron communication drivers, 3963 Omron Host Link, 3951 Parameters, 3856, 3870, 3896, 3909, 3924, 3936, 3953 Password, 3660, 3672, 3709, 3722 S7 200, 3813, 3841 Table, 3624 Connection cable Allen-Bradley cable 1747-CP3, 3879 Allen-Bradley cable 1761-CBL-PM02, 3880 Modicon, 3938 Multipoint cable 1:MP/TP/PC, 3957 Multipoint cable 2:RS422, MP/TP/PC, 3958 Omron Host Link, 3955 Point-to-point cable PP2 for Omron, 3958, 3959 Connection configuration Connection parameters, 479 Overview, 476 Starting, 482 Connection description Changing parameter values, 495 Data block , 489, 492, 493 Structure, 489, 492, 493 Connection details, 1141 4707 Index Connection diagnostics Detailed, 1139 Overview, 1137 Connection information, 1139 Diagnostics, 3609 Connection mechanisms, 998 Connection modes, 704 Connection parameter assignment of PUT/GET instructions, 505 Connection parameters Allen-Bradley DF1, 3870 Allen-Bradley EtherNet/IP, 3856 Mitsubishi FX, 3909 Mitsubishi MC TCP/IP, 3896 Modicon Modbus RTU, 3936 Modicon Modbus TCP, 3924 Omron Host Link, 3953 Connection parameters of PUT/GET instructions, 504 Connection resource, 451, 464 Connection resources Online, 1140 Connection rules, 652, 661 Connection status Displaying using icons, 1138 Connections Allen-Bradley DF1, 3873, 3874 Configuring, 3801, 3802, 3804, 3813, 3841 Editor, 3801, 3802, 3804 Consistency Slot rules, 406 Consistency check, 633, 1631, 1632, 1637 Introduction, 1631, 1637 local, 533 project-wide, 534 Constant Data types, 1182 Definition, 1180 Global constant, 1181, 1182, 1183, 1319, 1320, 1323 Local constant, 1181, 1182, 1183, 1375, 1381, 1390 Non-typed constant, 1180 Symbolic constant, 1181 Typed constant, 1180 Context filter, 407 CONTINUE, 2449 Control element Alarm view, 3313 simple alarm view, 4167 Simple alarm view, 3404 Trend view, 3310 4708 Controller alarms Configuring, 3381 Controller data, 4006 Initializing, 4005, 4007 ControlLogix, 3861 Control-timer alarm, 1997, 2000, 2282, 2285, 2488, 2491 Conversion, 1253 Explicit, 1273, 1274, 1280, 1282, 1283, 1285, 1287, 1289, 1290, 1292, 1293, 1294, 1295, 1296, 1297, 1298 Explicit , 1275, 1277 Implicit, 1256, 1257, 1258, 1259, 1260, 1261, 1262, 1263, 1264, 1265, 1266, 1267, 1268, 1269, 1270, 1271, 1272 Conversion operations Converting timers with T_CONV, 2507 Convert, 1930, 2212, 2421 CONVERT, 1930, 2212, 2421 Converted name (PROFINET), 912 Converting A character string to a hexadecimal number with ATH, 2539 Character string in array with Ctrl_TO_Chars, 2529 Character strings with S_CONV, 2523 Converting number to numeric character string with VAL_STRG, 2526 Converting numeric character string to number with STRG_VAL, 2524 Converting timers with T_CONV, 2507 Copying characters to numerical character string with Chars_TO_Strg, 2531 Hexadecimal number to character string with HTA, 2541 Converting an unspecified CPU, 146 Cookie, 684 Coordinated transfer, 3438 With PLC, 3438 Coordination, 3602 Copy Screen, 3190 Tag, 3342 Template, 3196 Copy protection, 1612 Copying Adjusting screen size, 4087 Alarm indicator, 53 Alarm view, 53 Alarm window, 53 Color, 4086 Excel format, 4018 WinCC Basic V13.0 System Manual, 02/2014 Index Font, 4086 Function key, 4087 Hardware component, 421 HMI device, 48 Invalid object, 4086 Linked objects, 4088, 4089 Principle, 4085 Screen, 4087 User-defined folders, 4086 CoS, 802 Queue, 802 COS, 1870, 2150, 2360 CoS (Class of Service), 719 Cosine, 1870, 2150, 2360 Count Down, 1806, 1816, 1820, 2085, 2095, 2100, 2333, 2340 Up, 1803, 1814, 1819, 2082, 2093, 2330, 2338 Up and down, 1808, 1812, 2088, 2335, 2342 Up and Down, 2091 Count (8 DI NAMUR), 1037 COUNTER, 1247, 1812, 2342 Counter input, 980 Counter mode, 980 Counter operations Control high-speed counters, 2882 High-speed counters, 2882 Counter, high-speed, 979 Counting Up, 2098 CountOfElements, 1921, 2203, 2412 Cover page Placeholder for document information, 303 CP 1242-7, 39, 701 CP 1613, 31 CP 1623, 31 CP 343-2, 38 CP1, 3960 C-PLUG Formatting, 792 CPM, 3960 CPU Displaying the current LED status, 1103 Fill level of all types of memory, 1104, 1105 Inserting a signal board, 670 Properties, 970 Reading date and time-of-day with RD_SYS_T, 2512 Reading out a diagnostics buffer, 1107 Selecting from the hardware catalog, 413 Setting time-of-day with WR_SYS_T, 2511 Switching operating mode, 1113 WinCC Basic V13.0 System Manual, 02/2014 CPU control panel Display area, 1104 CPU data block Definition, 1150 Deleting, 1353 CPU firmware, 1021 CPU load through trace, 4588 CPU memory area Displaying, 1641 CPU properties, 971 CPU type Allen-Bradley DF1, 3883 Allen-Bradley EtherNet/IP, 3861 FX3 series, 3904 Mitsubishi FX, 3914 Mitsubishi MC TCP/IP, 3904 Modicon Modbus RTU, 3944 Modicon Modbus TCP, 3931 Omron Host Link, 3960 Create Connection, 3701 Global library, 3993 Group, 3236 Template, 3195 Users, 3472 Users in runtime, 3480 CREATE_DB, 2796 Creating, 3445 Alarm group, 3383 Array, 3366 Connection, 3625, 3629, 3653, 3755 External tag, 3337 Infotext, 3385, 3387 Internal tag, 3339 Recipe, 3445 Recipe data record, 4177 Recipe data record on the HMI device, 3458, 3459 Screen, 3189 User group, 3470, 3493 Users, 3494, 4159, 4161 Creating a new type Style, 4004 Creating a print preview, 304 Creating a route, 630 Creating a type Screen, 4003 Script, 4002 Creating a watch table, 1659 Creating custom documentation, 239 Creating labels, 309 4709 Index Crossing Definition, 1437 Deleting, 1439 Inserting, 1438 rearranging, 1438 Cross-reference Inspector window, 53 Cross-reference list, (See cross-references), (See cross-references) Displaying, 1645, 4042 Overview, 1645, 4042 Settings, 1643, 4043 Sorting columns, 1643, 4043 Structure, 1643, 4043 Views, 1643, 4043 Cross-references Displaying, 1645, 4042, 4045 Introduction, 1642, 4042 Linking, 4045 Replace, 4045 Uses, 1642, 4042 CS1, 3960 CSV file, 4018, 4020, 4029 CTD, 1806, 2085, 2333 CTRL_HSC, 2882 CTRL_PWM, 2764 CTU, 1803, 2082, 2330 CTUD, 1808, 2088, 2335 CU, 1819, 2098 Cu10 sensor, 1061 Custom alarm classes, 3375 Cycle load, 976 Cycle monitoring time, 2458 Cycle time, 971, 975 display configured, 1097 display measured, 1102 Cyclic Continuous, 3351 In operation, 3351 Cyclic interrupt, 1006 Cyclic interrupt OB Assigning parameters, 1015 Description, 1006 Querying parameters with QRY_CINT, 2696 Setting parameters with SET_CINT, 2694 Cyclic operation, 3812, 3815, 3846 Cyclic program execution Options for interrupting, 999 Programming, 999 4710 D D_ACT_DP, 2591 Data areas Area pointer, 3642, 3968 Reading, 3642, 3968 Writing, 3642, 3968 Data backup, 90 HMI device, 4116, 4132 Data bit (DBX), 958 Data block Adjusting data values during commissioning, 1535, 1547, 1548, 1549 ARRAY data block, 1148, 1151, 1187, 1190, 1334, 1524, 1527, 1547 Based on a PLC data type , 1533 CPU data block, 1150 Creating, 1334, 1527 Creating with CREATE_DB, 2796 Declaration table, 1525 Declaring ARRAY, 1531 Declaring STRUCT, 1532 Default value, 1533 Deleting with DELETE_DB, 2803 Displaying values, 1546 Global data block, 1148, 1524 Importing and exporting tags, 1545 Instance data block, 1149, 1524 Loading block changes without reinitialization, 1529 Monitoring data values online, 1545 Optimized access, 1151, 1153 Programming, 1524, 1530 Reading attributes with ATTR_DB, 2802 Reading from load memory with READ_DBL, 2798 Retentive behavior, 1536, 1537 Start value, 1533, 1534 Tag properties, 1538, 1540, 1541 Updating, 1528 Using setting values, 1535, 1547, 1548, 1549 Writing to load memory with WRIT_DBL, 2800 Data byte (DBB), 958 Data consistency, 3074 Data double word (DBD), 958 Data Encryption Standard (DES), 589 Data exchange, 3595 DP slave, 879 I-slave - DP master, 880 Tags, 3601 Trends, 3690, 3847 WinCC Basic V13.0 System Manual, 02/2014 Index using area pointers, 3602 Data exchange over the AS-AS remote link Communication instruction "AS_DIAL", 4649 Data flow, 4174 Data flow control, 986 Data log, 675 Closing with DataLogClose, 2789 Creating with DataLogCreate, 2775 Creating with DataLogNewFile, 2792 Creating with DataLogTypedNewFile, 2794 Deleting with DataLogDelete, 2791 Empty with DataLogClear, 2785 Opening with DataLogOpen, 2782 Opening with DataLogTypedOpen, 2783 Writing with DataLogWrite, 2787 Data mailbox For recipes, 3438 Data record, 3602 Asynchronously reading data record of a module with RD_DPARA, 2686 Making available on I-device with PRVREC, 2608 Reading, 3459 Reading from configured system data with RD_DPARM, 2688 Reading of a module with RD_DPAR, 2684 Reading with RD_REC, 2596 Reading with RDREC, 2558 Receiving on I-device with RCVREC, 2605 Transfer, 3460 Transferring with WRREC, 2560 Writing and reading data records, 2682 Writing predefined parameters with WR_DPARM, 2690 Writing with WR_REC, 2600 Data record list, 3441 Data type Convert explicit, 2212, 2421 Explicit conversion, 1930 Allen-Bradley, 3892 Allen-Bradley EtherNet/IP, 3859 ANY, 1242 ARRAY, 1235, 1236 BOOL, 1208, 1256, 1273 BYTE, 1209, 1257, 1274 CHAR, 1230, 1271, 1297 Conversion, 1253, 1259, 1268, 1269, 1270 DATE, 1226, 1270, 1294 DINT, 1216, 1264, 1287 Discrete alarm, 3892, 3919, 3964 DT, 1228 DTL, 1229, 1269, 1296 DWORD, 1211, 1259, 1277 WinCC Basic V13.0 System Manual, 02/2014 Explicit conversion, 1273, 1274, 1275, 1277, 1280, 1282, 1283, 1285, 1287, 1289, 1290, 1292, 1293, 1294, 1295, 1296, 1297, 1298 Implicit conversion, 1256, 1257, 1258, 1260, 1261, 1262, 1263, 1264, 1265, 1266, 1267, 1269, 1271, 1272 INT, 1214, 1262, 1283 Internal tag, 3336, 3638 LDT, 1229 LINT, 1217 LREAL, 1221, 1267, 1292 LTIME, 1225 LTIME_OF_DAY, 1227 LWORD, 1211 Mitsubishi, 3919 Mitsubishi FX, 3913 Mitsubishi MC TCP/IP, 3903 Modicon Modbus RTU, 3943 Modicon Modbus TCP, 3930 Omron, 3964 Omron Host Link, 3959 PLC data type, 1248, 1551 POINTER, 1240 REAL, 1220, 1266, 1290 S5TIME, 1223 SCL instruction, 1499, 1500, 1501 SINT, 1212, 1260, 1280 STRING, 1231, 1272, 1298 STRUCT, 1239 TIME, 1225, 1268, 1293 TIME_OF_DAY, 1227 TOD, 1269, 1295 UDINT, 1216, 1265, 1289 UINT, 1215, 1263, 1285 ULINT, 1219 USINT, 1213, 1261, 1282 Valid, 3859, 3903, 3913, 3930, 3943, 3959 Validity, 1204 VARIANT, 1245 WCHAR, 1231 WORD, 1210, 1258, 1275 WSTRING, 1233 Data type conversion, 41 Data types, 158 Migration, 135 S7 1500, 3693 S7 200, 3840 S7 300/400, 3800 S7-1200 V1, 3744 Trends, 3690, 3849 Valid, 3693, 3744, 3800, 3840 Data word (DBW), 958 4711 Index DataLogClear, 2785 DataLogClose, 2789 DataLogCreate, 2775 DataLogDelete, 2791 DataLogNewFile, 2792 DataLogOpen, 2782 DataLogTypedNewFile, 2794 DataLogTypedOpen, 2783 DataLogWrite, 2787 Date, 1226, 1228, 1229 DATE, 1226, 1270, 1294 Date/time, 3602 Area pointer, 3724 Date/time field, 3300 Application, 4145 Behavior, 4145 Display system time, 3301 Format, 3301 Layout, 4145 Operation, 4145 Using tags, 3301 Date/time PLC, 3602 DATE_AND_LTIME, 1229 DATE_AND_TIME, 1228 DATE_TO_, 1294 DB, 1334, 1527 DB variable Definition, 1179 DB_ANY_TO_VARIANT, 2433 DCAT, 1997, 2282, 2488 DCP (Primary Setup Tool), 555 DCP server, 758 Deactivate, 3578 Dead peer detection (DPD), 595 Deadband Setting, 3387 DEC, 1856, 2136 Decimal places, 32, 1876, 2157, 2365, 4141, 4142 DECO, 1977, 2261, 2469 Decode, 1977, 2261, 2469 DecreaseFocusedValue, 3564 DecreaseTag, 3565 Decrement, 1856, 2136 Default font, 4071, 4134 Default style Defining, 3200 Defective devices, 1086 Defective license, 79, 91 Define Reference object, 3211 Define hotkey, 3323 4712 Defining For the assignment list, 1623 Delay time Setting, 3387 Delete Template, 3196 DELETE, 2546 DELETE_DB, 2803 Deleting Authorization, 3476 Filter in the assignment list, 1623 Hardware component, 420 Object, 3206 Recipe data record, 4179 Screen, 3190 Tag, 3342 User group, 3476 Users, 3475, 4163 Deleting a connection, 150 Deleting CA certificates, 4640 Demultiplex, 1984, 2268, 2475 DEMUX, 1984, 2268, 2475 Dependencies of rights, 544 Dependency structure, 1633 Introduction, 1633 Meaning of symbols, 1635 Setting view options, 1636 Structure, 1634 Dependency structure Displaying, 1635 DES, 583, 589 Deserialization, 2366 Deserialize, 1884, 2165, 2366 Designation TS Adapter, 4611, 4619, 4627 Designing a background, 3217 Designing a border, 3217 Destruction of license keys, 78 DETACH, 2693 Detailed comparison Performing, 284 Starting, 1571 Visualization of the comparison result for GRAPH, 1582 Visualization of the comparison result for LAD/ FBD, 1572 Visualization of the comparison result for SCL, 1579 Visualization of the comparison result for STL, 1576 Details view, 209 Determine diagnostics status, 1106 WinCC Basic V13.0 System Manual, 02/2014 Index Determining time of day, 1114 Device Adding to a hardware configuration , 415 Copying, 48, 421 Defective devices, 1086 Deleting, 420 Inserting, 3597 Moving, 422 Renaming, 522 Device address, 665 Device dependency S7-1200 V1, 3742 S7-1200 V2, 3742 S7-1200 V3, 3742 S7-1200 V4, 3742 SIMATIC S7-1500 V1.0, 3692 Device information, 294, 1086 Diagnostics, 3609 Device name, 906, 912 Device name, automatic commissioning (PROFINET), 908 Device number, 907 Device overview Address range, 665 Device proxy Initializing, 4012 Updating, 4010, 4015 Device replacement, 423 Device Tool, 932, 933 Device version, 4106 Checking, 4098 Switching, 4097 Updating, 4118 Device view Area of unplugged modules, 412 Edit parameters, 424 Edit properties, 424 Hardware and network editor, 390, 3611 Inserting a signal board, 669 Inserting module, 417 Racks, 408 Device wizard, 3982 Devices Connecting, 3601 Networking, 3600, 3624 Devices & Networks, 3600, 3624 Devices and networks, 3600, 3624 Connections, 3625 HMI connections, 3625 DeviceStates, 2751 DHCP Client, 771 WinCC Basic V13.0 System Manual, 02/2014 Server configuration, 631 DHCP server, 632 Diagnose repeater, 1134 Diagnostic data Reading out with GET_DIAG, 2759 Diagnostic error interrupt, 1009 Diagnostic interrupt OB, 1009 Diagnostics, 598, 1048 Connection, 3609 Connection information, 3609 Device, 3609 Device information, 3609 DP slave, reading diagnostic data with DPNRM_DG, 2616 Diagnostics buffer Basics, 961, 1129 Organization, 1129 Diagnostics status Determining and displaying online, 1087 Diagnostics user, 540 Diagonal movement Animation, 3271 Dialing rules in phone books, 4608 dial-up connection Establishing, 4632 Terminating, 4634 Diffie-Hellman key agreement, 588 DINT, 1216, 1264 DINT , 1287 DINT_TO_, 1287 Direct access to the I/O, 962 Direct key configuring, 3288 Direction output and travel direction relation, 4315 DIS_AIRT, 2721 DIS_IRT, 2718 Disabling Project language, 4052 Discrete alarm, 3372, 3373 Allen-Bradley, 3892 Configuring, 3383, 3391 Mitsubishi, 3919 Omron, 3964 Discrete alarm types, 3372 Discrete alarms Configuring, 3381 display Tooltip, 4143 Display HMI backup, 4100 4713 Index Display object Availability for Basic Panels, 3297 Display PDF files, 75 Display system time, 3301 Display Welcome Tour, 75 Displaying Call structure, 1630 Assignment list , 1621 CPU memory area, 1641 Cross-reference, 4045 Cross-references, 1645, 4042 Dependency structure , 1635 Load memory, 1642 Maximum load memory available, 1642 Program information, 1617 Displaying a force table, 1687 Displaying alarms, 944 Displaying memory types of a CPU, 1104, 1105 Displaying or hiding tag information, 1433, 1474, 1502 Displaying support for a module, 401 Displaying the online status, 4537 Displaying values As a trend, 3368 Distribute Objects evenly, 3213 Distributed I/O, 877, 1046 DIV, 1852, 2131 Divide, 1852, 2131 DMSK_FLT, 2716 DNS client, 762 DO, 2444, 2446 Documentation editor Layout, 299 Documentation settings Using frames and cover pages, 297 Double word, 1211 double-click, 3579 Download, (See Loading to device) Error messages, 4121 Project, 4107, 4125 Downloading Downloading blocks to a memory card, 1608 Downloading blocks to device, 1604, 1605 Downloading data to the PLC Error message, 64 DP, 3721, 3774 DP interface, 882 DP master, 664, 1032 Add DP master system, 885 Devices and modules, 882 Disconnection from DP master system, 885 4714 Display on DP slave, 884 DP interface, 882 DP master system Add DP slave, 887 Creating, 878, 881, 882 Determining topology with DP_TOPOL, 2619 Disconnect DP slave, 887 Disconnection from subnet, 885 Edit properties, 886 Highlight, 884 Node disconnection, 885 DP slave, 664 Activating and deactivating with D_ACT_DP, 2591 Add to DP master system, 887 Assign DP master system, 887 configuring, 888 Configuring, 879 Data exchange, 879 Disconnect from DP master system, 887 DP master display, 884 Hardware catalog, 878 Intelligent, (See I-slave) Networking, 881 Reading diagnostic data with DPNRM_DG, 2616 Synchronizing groups with DP_SYC_FR, 2610 Types, 886 With preprocessing, (See I-slave) DP standard slave, 900 DP standard slaves Reading a portion of the inputs with GETIO_PART, 2563 Reading all inputs with GETIO, 2562 Reading consistent data with DPRD_DAT, 2601 Writing a part of the outputs with SETIO_PART, 2564 Writing all outputs with SETIO, 2563 Writing consistent data with DPWR_DAT, 2603 DP/DP coupler, 878 DP_TOPOL, 2619 DPNRM_DG, 2616 DPRD_DAT, 2601 DPSYC_FR, 2610 DPV1 Configuring an ET 200S, 898 DPWR_DAT, 2603 DRUM, 1994, 2279, 2485 DSCP, 802 DST Daylight saving time, 776 DT, 1228 DTL, 1229, 1269, 1296 WinCC Basic V13.0 System Manual, 02/2014 Index DTL_TO_, 1296 Duration, 1223 DWORD, 1211, 1259, 1277 DWORD_TO_, 1277 Dynamic reference temperature, 1068 Dynamization Color of an object, 3269 Flashing, 3269 Object, 3264 Dynamize Appearance of an object, 3269 Direct movement, 3272 Green arrow in Overview, 3268 Movement of an object, 3270 E Eastern characters Input on the HMI device, 4136 EB, 1309 EC31-RTX, 38 ED, 1309 Edge Negative, 1754, 1756, 1759, 2031, 2033, 2036, 2301 Positive, 1753, 1755, 1757, 2030, 2032, 2035, 2300 Edit Object within a group, 3240 Edit networking Disconnecting from a network, 436 EditAlarm, 3515 Editing Alarm, 4170 Folder link, 3232 Function list, 3502 Recipe data record, 4178 Editing a version of a type in testing, 363 Editing language, 250, 4048 Selecting, 4052 Editing networking Copying a subnet, 436 Copying subnets and devices, 437 Editor Connection, 3629 Connections, 3801, 3802, 3804 Devices and networks, 3627 Graphics, 4062 Element list, 3441 Ellipse Horizontal radius, 3304 Vertical radius, 3304 WinCC Basic V13.0 System Manual, 02/2014 Ellipse , 3303 ELSE, 2440, 2442 ELSIF, 2440 E-mail Transferring e-mail with TM_MAIL, 3174 Transferring e-mail with TMAIL_C, 3114 Empty box Inserting a LAD element, 1412 Inserting an FBD element, 1454 EN/ENO mechanism Basics, 1299 FBD example, 1302 LAD example, 1302 SCL example, 1303 STL example, 1304 EN_AIRT, 2722 EN_IRT, 2720 Enable autonegation, 924, 3662, 3711, 3764 Enable output ENO, 163 Enabling the firewall SCALANCE S, 622, 624 Enabling tunneled communication CP x43-1 Adv., 645 SCALANCE S, 622, 624 ENCO, 1978, 2262, 2470 Encode, 1978, 2262, 2470 Encryption, 528 Encryption software, 82, 86 End of detection of accessible devices, 926 End of discovery of accessible devices, 3664, 3713, 3766 End of sync domain, 926, 3664, 3713, 3766 End of topology discovery, 926, 3664, 3713, 3766 END_CASE, 2442 END_FOR, 2444 END_IF, 2440 END_REPEAT, 2448 END_WHILE, 2446 Endian, 2402, 2404, 2406, 2407 ENDIS_PW, 1955, 2238, 2453 Engineering system Performance features, 4181 ENO, 163 Enumeration types, 686 Enumerations Web server, 688 EQ_ElemType, 1839, 2118 EQ_Type, 1837, 2116 Equal, 1842, 2120 EQUAL ARRAY, 1844, 2122, 2347 Error alarm Acknowledge, 4170 4715 Index Error analysis with RET_VAL, 1738 Error handling, 1523 Basics, 1519 GetError, 1961, 2244, 2459 GetErrorID, 1964, 2248, 2462 Local error handling, 1521 Error information, 1521, 1738, 1961, 1964, 2244, 2248, 2459, 2462 Error message Downloading data to the PLC, 64 Error messages Download, 4121 Error status, 737 ESP protocol, 589 Establishing a connection from a remote system ("PG_DIAL"), 4648 Establishing a remote connection, 4632 Procedure, 4633 ET 200eco, 1030 ET 200eco PN, 1030, 1046 ET 200iSP, 1030 ET 200iSP distributed I/O station Definition, 1032 ET 200L, 1030 ET 200M, 1030, 1072 Definition, 1071 ET 200MP, 1063 ET 200pro, 1030 ET 200R, 1030 ET 200S, 1030 DPV1 mode, 898 Option handling, 894, 897 Positioning module, 38 Reference junctions, 890 Slot rules, 890 ET 200S COMPACT, 1030 ET 200SP, 1052 Application area, 1052 ET 200M distributed IO device, 1071 Ethernet, 444, 446 Parameters, 3696, 3750, 3808, 3817, 3845 ETHERNET Basic Panel, 3649 Ethernet interface Displaying parameters, 4548 Ethernet module Removal/insertion, 35 Ethernet non IP frames, 547 Ethernet Statistics Frame length, 746 Frame type, 747 Interface statistics, 745 4716 Packet Errors, 747, 748 Event Acknowledge, 3583 activate, 3575 Alarm buffer overflow, 3582 Assigning organization block (OB) with ATTACH, 2692 Boundary reached, 3583 Canceling assignment to organization block (OB) with DETACH, 2693 Change, 3576 cleared, 3575 Click, 3581 Click when flashing, 3581 Deactivate, 3578 double-click, 3579 Execute, 3576 For function lists, 3356 Free space critically low, 3585 Incoming, 3581 Input finished, 3580 Inspector window, 53 Loop-In-Alarm, 3582 Low free storage space, 3585 Outgoing, 3580 Overflow, 3584 Press, 3579 Press ESC twice, 3580 Press key, 3584 release, 3582 Release key, 3584 Runtime Stop, 3583 Screen change, 3578 Selection changed, 3577 Switch OFF, 3585 Switch ON, 3585 Tags, 3356 Time expired, 3586 User change, 3578 Value change, 3585 When dialog is closed, 3578 When dialog is opened, 3577 When high limit is exceeded, 3577 When low limit is undershot, 3577 Event name, 1016 Event trigger, 3591, 3594 Event-driven tasks Configuring:event-driven tasks, 3385 Events Configuration, 767 Log table, 736 Severity filter, 769 WinCC Basic V13.0 System Manual, 02/2014 Index EW, 1309 EX, 1309 Example Application for alarm classes, 3375 Changing and displaying operating mode, 3503 Controlling a conveyor belt, 1716, 1731 Controlling room temperature, 1722, 1729 Detecting the direction of a conveyor belt, 1718, 1725, 1733 Detecting the fill level of a storage area, 1719, 1726, 1734 For displaying bit memory in the assignment list, 1619 For displaying inputs and outputs in the assignment list, 1619 For entering force values in the force table, 1690 Modify values in the watch table, 1663 System alarm, 3372 Example: Discrete alarm, 3373 Examples Controlling a conveyor belt, 1724 Exchangeable medium, 926 Exchanging, 4006 EXCLUSIVE OR, 2018, 2019 Bit logic operations, 2018 Execute, 3576 Exit User program, 1960, 2244, 2458 EXIT, 2450 EXP, 1868, 2148, 2358 Expanded mode, 1656 Expanding and collapsing sections of code, 1494 Exponential value, 1868, 2148 Exponentiate, 1878, 2158 Export Alarm, 4022 Excel format, 4018 Project texts, 4039, 4059 Recipe, 4018 Tag, 4029 Text list, 4034 Export of labels, 309 Exporting an NTP server, 579 Expression Basics, 1480 Logical expression, 1485 Relational expressions, 1484 Expression Arithmetic expression, 1481 EXPT, 1878, 2158 Extended download to device, 64 WinCC Basic V13.0 System Manual, 02/2014 Extended status information, 1489 External, 41 External graphic Edit folder, 3231 Link folder, 3232 Removing the folder link, 3231 Rename folder, 3231 External image file add to graphics library, 4064 Managing, 3204 Storing in the image browser, 3233 External source file Basics, 1560 Exporting blocks, 1562 inserting, 1563 Linking file types to an editor, 1564 Rules for programming, 1561 External sources, 41 External tags Data exchange, 3601 F F_TRIG, 1761, 2038, 2301 Facility, 568 Factory settings Resetting to, 1117, 1118 Resetting to , 4119 FALSE, 2300, 2301 FAQs, 3619 Fault monitoring Connection status change, 788 Power supply, 787 Redundancy, 788 Favorites Adding, 1415, 1457, 1503 Hiding, 1363 Removing, 1417, 1458, 1504 Showing, 1363 Using, 1416, 1457, 1503 FB, 1147 FBD, 1441, 1724, 1725, 1726 Detailed comparison, 1572 FBD element Copying, 1466 Cutting, 1467 Deleting, 1472 Inserting, 1453, 1454 Inserting an operand , 1473 pasting from the clipboard, 1467 Replacing, 1468 Rules for inserting, 1451 4717 Index Selecting, 1465 FBD network Branch, 1476 Deleting a branch, 1477 Inserting a block call, 1417, 1459 Inserting a branch, 1477 Program status display, 1653 Rules for branches, 1476 FC, 1146 FETCH/WRITE, 998 Field device, 900, 929 FieldRead, 1891, 2171 FieldWrite, 1892, 2173 File Browser, 675 Fill Block, 1902, 1927, 2184, 2210, 2379, 2418 Block uninterruptible, 1904, 2186, 2380 FILL, 1927, 2210, 2418 FILL_BLK, 1902, 2184, 2379 Filter Defining for the assignment list, 1623 Delete, 1623 Hardware catalog, 407 In the assignment list, 1623 Selecting, 1624 Filters Assignment list , 1624 FIND, 2549 Find and replace, 316 Additional options for searching, 317 Replacing search keys, 318 Start search, 318 Using the search function, 317 Firewall Creating service groups, 553, 555 Defining ICMP services, 552 Firewall rules, 547 Managing service groups, 553, 556 Firmware, 1021 Updating, 4118 Firmware card, 955 Firmware update, 1115 Firmware update memory card, 956 Firmware version V4, 29 Fixed reference temperature, 1068 Flash test, 1133 Flashing, 3269 Flip Object, 3204 Flip-flop Reset/set, 1751, 2029 Set/reset, 1750, 2027 4718 Floating-point number, 1220, 1221 Check invalidity, 1836, 2115 Check validity, 1835, 2114 Floating-point numbers, 1222 Invalid , 1222 FLOOR, 1934, 2217, 2424 Flutter monitoring, 1075 Folder link Editing, 3232 Removing, 3232 Renaming, 3232 Font settings Migrate, 120 Font size Asian languages , 4136 FOR, 2444 Force Force all, 1704 Stop forcing, 1706, 1707 Force job On SD card, 31 Force table Meaning of the icons, 1686 "Monitor once and now" command for tags, 1698 Basic mode, 1685 Display, 1687 Expanded mode, 1685 Functionality, 1682 Layout, 1684 Meaning of the columns, 1684 Monitoring and modifying modes, 1670 Opening, 1687 Overview of the display formats, 1691 Overview of the test options, 1682 Permitted operands, 1689 Permitted operands for force values, 1690 Saving, 1688 Switching between basic mode and expanded mode, 1685 Syntax check, 1688 Test options, 1682 Force value Permitted operands, 1690 Forcing tags Safety precautions, 1684, 1700 Foreground color Dynamization, 3269 Form exponential value, 2358 Format, 3301 Formatting Alarm text, 3389 FRAC, 1876, 2157, 2365 WinCC Basic V13.0 System Manual, 02/2014 Index Fragment, 688, 694 Free space critically low, 3585 Free-form comments Deleting, 1424, 1465 Editing, 1422, 1464 Inserting, 1422, 1463 Introduction, 1421, 1463 Frequency meter, 1043, 1046 FTP, 542, 544, 998 FTPS certificates, 534 Function Assigning to a function key, 3283 Function (FC) Creating, 1333 Definition, 1146 exporting to an external source file, 1562 Function block (FB) Creating, 1333 Definition, 1147 exporting to an external source file, 1562 Instance data block, 1147 Function Block Diagram, 1441 Function key, 3278 Assigning a function, 3283 Assigning a graphic, 3286 Global assignment, 3280 Global screen, 3194 Local assignment, 3194, 3282 protect with password, 3285 Use global assignment, 3194 used for screen navigation, 3290 Function list, 3356, 3498, 3590 Asynchronous execution, 3503 Execution, 3500 Execution in Runtime, 3503 Synchronous execution, 3503 System function, 3500 User-defined functions, 3500 Function lists Editing, 3502 Functional scope ProSave, 4116 Functionality of the force table, 1682 Functions Updating tag value, 3333, 3635 FX1 series, 3914 FX2 series, 3914 FX3 PLC, 3900 FX3 series, 3904 WinCC Basic V13.0 System Manual, 02/2014 G GADR_LGC, 2817 Gateway, 444 GEN_DIAG, 2757 General information on troubleshooting, 4655 General rules, 1162 Generating diagnostics information, 2757 Generation of packed addresses, 893 GEO_LOG, 2813 GEO2LOG, 2806 Geographic coordinates, 760 GET, 3078 Get_AlarmState, 2725 GET_DIAG, 43, 2759 Get_IM_Data, 2741 GET_NAME, 29, 2745 GetBlockName, 2551 GetError, 1522, 1523, 1961, 2244, 2459 GetError , 1521 GetErrorID, 1521, 1522, 1523, 1964, 2248, 2462 GetGroupNumber, 3531 GetInstanceName, 2550 GETIO, 2562 GETIO_PART, 2563 GetPassword, 3531 GetPLCMode, 3532 GetStationInfo, 2748 GetSymbolName, 2550 GetUserName, 3530 Gigabit address, 537 Global assignment Of a function key, 3278, 3280 Global data block, 1148 Configuring, 3643 Creating, 3643 Retentive behavior, 1537 Global firewall rules, 548 Assigning, 550 Global libraries, 326 Archiving, 347 Backward compatibility with older product versions, 340 Compatibility mode V12 SP1, 339 Retrieving, 348 Global library, 3984 Adding types, 370 Archiving, 347 Cleaning up, 380 Closing, 345 Create, 3993 4719 Index Creating, 338 Creating folders, 351 Deleting, 346 Displaying logs, 344, 3995 Migrating, 127 Open, 3994 Opening, 340 Save, 3994 Saving, 344 Showing properties, 343 Updating the project, 372 Upgrade, 4097 Using filter view, 353 Using the element view, 329 Using types, 371 Global packet filter rules, 550 Global screen, 3193 Function key, 3194 Template, 3195 Global softkey, 3280 Global tag, (See PLC tag) GMRP, 836 Go online, 1131 connecting several devices, 4538, 4539 Multiple TIA Portal instances, 35 Going offline, 1133 GOTO, 2451 GoToEnd, 3520 GoToHome, 3519 GPRS, 703 GRAPH Detailed comparison, 1582 Graphic add to graphics library, 4063 Alignment, 3221 Assigning to a function key, 3286 Button, 3322 Distance, 3222 Graphic view, 3305 Inserting, 3204 managing, 3231 Size adjustment, 3221 Stretching, 3305, 3307 Using from the graphic browser, 3231 With transparent background, 3231 Graphic browser, 3231 Graphic browser , 4064 Graphic I/O field, 3306 Output graphics list, 3264 Graphic IO field, 4149 Application, 4149 Behavior, 4150 4720 Operation, 4150 Graphic view, 3304, 4149 Application, 4149 Layout, 4149 Operation, 4149 transparent color, 3305 Graphics, 3233 Editor, 4062 Graphics list Application, 3255 Bit (0, 1), 3261 Bit number (0 - 31), 3263 Creating, 3256 Graphic I/O field, 3264 Outputting configuration data, 3264 Range (0 - 31), 3257 Range (... - ...), 3260 group Cancel, 3237 Edit, 3236 Ungroup, 3237 Group Adding objects, 3238 Cancel, 3237 Creating, 3236 Editing, 3236 Removing an object, 3239 Ungroup, 3237 Group name, 551, 554 Group properties, 587 GSD files Configuring devices (PROFIBUS), 900 GSD revisions (PROFIBUS), 899 Installation, 900 GSD files (PROFINET), 927 Changing revision, 929 Installation, 929 GSDML, (See GSD files (PROFINET)) GSM network, 703 H Handshaking, 987 Hardware, 43 Comparing, 29 Configuring and assigning parameters, 404 Detection, 38 Edit parameters, 424 Edit properties, 424 Hardware and network editor Device view, 390, 3611 Network view, 387, 3605 WinCC Basic V13.0 System Manual, 02/2014 Index Topology view, 392, 3613 Hardware and software limit switches Function, 4319 Hardware catalog Adding device, 415 Browsing, 407 DP slave, 878 DP/DP coupler, 878 I slave, 878 Selecting the hardware component, 413 Task card, 399, 3617 Hardware configuration Adding device, 415 Adding module, 417 Hardware configuration for Motion Control S7-1200, 4310 Hardware data types, 1251 Hardware detection, 417 Hardware diagnostics, 1085 Hardware documentation, 4663 Hardware editor Components, 386, 3603 Function, 385, 3603 Hardware catalog, 399, 3617 Inspector window, 3615 Inspector window , 397 Hardware identifier, 665, 1054, 1065 Determining with LOG2MOD, 2809 Hardware interrupt, 1007 How it works, 968 Hardware interrupt OB Description, 1007 Parameter assignment, 1016 Hardware requirements, 81 Communications instruction "AS_MAIL", 4653 Communications instruction "PG_DIAL", 4648 Communications instruction "SMS_SEND", 4651 Hardware requirements for AS-AS remote link Communication instruction "AS_DIAL", 4650 Hardware support package Installing, 96 Hardware version, 734 Hardware-controlled data flow control, 986 Harmonizing Object size, 3209 HART, 1034 HART variables Configuring, 1073 Quality code, 1074 Structure, 1073 Help Browsing, 234 WinCC Basic V13.0 System Manual, 02/2014 Call topic from favorites, 235 Delete topic from favorites, 236 Find keywords, 234 Full-text search, 234 Identification of help topics, 231 Open tooltip cascades automatically, 237 Opening, 233 Printing help topics, 236 Save topics in favorites, 235 Use index, 234 Help indicator, 3307 Hidden input, 3303 Hidden parameters, 1433, 1474 Highlighting Connection, 3627 High-speed counter Configuring, 982 General, 979 How it works, 979 HMI backup Deleting, 4101 Display, 4100 Rename, 4101 HMI connection, 147, 464, 998, 3601 Creating, 3653, 3701, 3755 MPI, 3776 MPI parameters, 3778 Password, 3660, 3672, 3709, 3722 PROFIBUS, 3665, 3768 PROFIBUS parameters, 3668, 3716, 3770 PROFINET, 3652, 3653, 3700, 3701, 3754, 3755 PROFINET parameters, 3655, 3702, 3757 S7 1200, 3701 S7 1500, 3653 S7 300/400, 3755 HMI connections Devices & Networks, 3625 HMI device, 89 Changing the device type, 4122 Commissioning, 4125 Configuration, 4098 Data backup, 4114, 4116, 4117, 4132 Image, 4114 Load, 4114 MPI parameters, 3780 Performance features, 4183, 4187 PROFIBUS parameters, 3670, 3718, 3771 PROFINET parameters, 3656, 3704, 3758 Recommissioning, 4125 Reloading the operating system, 4119 Reset to factory settings, 4120 Restoring data, 4116, 4118, 4132 4721 Index Software, 4114 System limits, 4183, 4187 HMI device configuration, 4098 HMI device licensing Non-PC-based, 89 HMI device on a PLC Commissioning, 3867, 3888, 3906, 3916, 3933, 3945, 3962 HMI device replacement, 48 HMI device type Changing, 4122 HMI device version, 4097, 4098, (Device version), (Device version) HMI device wizard, 3982 HMI style, 4004 Homing Homing modes, 4321 Horizontal radius, 3304 How the frequency meter works, 1044 HSC, 979 HSP, (See support package) HTA, 2541 HTTP, 551 Load/save, 763 HTTPS, 623, 674 HTTPS server only, 757 HW ID See Hardware identifier, 665 I I address, 665 I slave Hardware catalog, 878 I&M data: read out with Get_IM_Data, 2741 I/O Direct access to, 962 I/O access error, 960 I/O address, 665, 962 I/O field, 3301 Data format, 3302 Decimal format, 55 Format, 55 Hidden input, 3303 Mode, 3302 I/O input, 958 I/O output, 958 I/Os, 1186 IB, 1309 ICMP, 557 Icon For comparison, 1091 4722 For comparison status, 1139 for connection status, 1138 For hardware diagnostics, 1090 for operating state, 1092 For software diagnostics, 1091 For value comparison, 4336, 4362 Overlay icon, 1092 Icons in TeleService, 4603 Icons in the force table, 1686 Icons in the watch table, 1658 ID, 1309 I-device, 915 IE/AS-i link PN IO, 902 IEC check, 1253 Setting, 1256 IEC counters, 161 IEC timer, 1225 IEC timers, 161 IEEE 802.3, 547 IEEE tag, 1033 IF, 2440 IF1B Basic Panel, 3649 IGMP, 836 IGMP querier, 836 IKE settings, 587 Image, 4097, 4105, 4106, 4118 HMI device, 4114 Image file Storing in the image browser, 3233 Storing in the image browser , 4064 IMC, 2004, 2289, 2495 Import Alarm, 4023 Analog alarm structure, 4024 Project texts, 4041, 4061 Recipe, 4020 Structure of discrete alarms, 4027 Structure of recipe data, 4021 Tag, 4031 Text list, 4036 Importing a recipe Structure for the import, 4021 Importing analog alarms Structure for the import, 4024 Importing discrete alarms Structure for the import, 4027 Importing NTP servers, 579 in the screen Arrange object, 3213 IN_RANGE, 1833, 2112 WinCC Basic V13.0 System Manual, 02/2014 Index INC, 1855, 2135 Incoming, 3374, 3581 IncreaseFocusedValue, 3518 IncreaseTag, 3519 Increment, 1855, 2135 Indenting and outdenting Lines, 1492 Index tag, 3354, 3355 Indirect addressing, 159, 1196, 1197, 1198, 1200, 1201 Indirect addressing , 3354 Industrial Ethernet, 3620 Information ARP table, 735 Ethernet Statistics, 746 Event log, 736 Frame type, 747 Packet Errors, 747, 748 Spanning Tree, 738 Versions, 733 Information system Components of the information system, 230 Roll-out, 232 Tooltip, 232 Infotext, 3380 Creating, 3385, 3387 INIT_RD, 1967, 2251, 2465 Initialization IPE file, 4006 Project file, 4012 Initialization (user-defined web pages), 677 Initialize all retain data, 1967, 2251, 2465 Initializing Controller data, 4005 IPE file, 4007 Project file, 4012 Input Inserting, 1428, 2020 remove, 1429, 1470 Input (I), 958 Input byte (IB), 958 Input finished, 3580 Input word (IW), 958 INSERT, 2547 Insert empty line, 4366 Insert input, 1469 Insert separator line, 4366 Inserting Graphic, 3204 Library object, 4001 Object, 3203, 3204 Rectangle, 3245 WinCC Basic V13.0 System Manual, 02/2014 Inserting a comment section, 2453 Inspector window Cross-reference, 53 Event, 53 Hardware and network editor, 3615 Layout, 203 Reducing automatically, 198 Inspector window Diagnostics tab, 1086 Hardware and network editor, 397 Install update, 96 Installation Displaying software, 97 Licenses, 74 Log, 92 Modifying products, 98 ProSave, 64 Repairing products, 100 run automatically, 73 Smartdrive, 49 Starting, 93 Support package, 96 System requirements, 75 Target directory, 73 Updates, 96 Updating products, 98 Installing CA certificate, 4637 Installing license keys, 78 Installing support packages, 96 Installing the local modem, 4612 Instance data block Creating, 1149 Definition, 1149 Modifying the data types of IEC timers and IEC counters, 1501 Retentive behavior, 1536 Instruction Copying, 1516 Cutting, 1516 Deleting, 1516 Inserting, 1516 Rules, 1497 Specify data type, 1413, 1414, 1454, 1456 Versions, 1365 Instruction profile Activating and deactivating, 1369 Basics, 1366 Creating, 1367 Deleting, 1370 Editing, 1368 Opening, 1368 Instructions for configuring a remote modem, 4614 4723 Index INT, 1214, 1262, 1283 INT_TO_, 1283 Integer, 1935, 2218, 2426 16-bit, 1214, 1215 32-bit, 1216 64-bit, 1217, 1219 8-bit, 1212, 1213 Integrated Connection, 3625, 3629 Integrated connection, 3334, 3636 Integrated project Converting an unspecified CPU, 146 Creating an integrated HMI connection, 147 Deleting an unspecified connection, 150 Linking HMI tags, 149 Migrating, 131, 142 Post-editing, 145 Intelligent DP slave, (See I-slave) Inter Project Engineering Creating "Device Proxy Data" in the source project, 1713 Exchange of controller data via "IPE file", 1714 Exchanging controller data across projects, 1711, 4527 Opening "Device Proxy Data", 1714 Procedure for exchanging controller data via a project file, 1712, 4528 Procedure for exchanging controller data via an IPE file, 1711, 4527 Procedure for updating already transferred controller data, 1712, 4529 Requirements, 1710, 4527 Software and hardware requirements, 1710, 4526 Inter Project Engineering (IPE) Basics, 1708, 4524 Exchanging controller data via IPE file, 1709, 4525 Exchanging controller data via project file, 1709, 4525 Interconnecting, 446 Interconnecting ports Graphic view, 519, 521 Table view, 520, 522 Interface, (See block interface) Adding, 4546 Basic Panel, 3649 Displaying, 1098 Renaming, 522 Interface properties, 1098 Interfaces, 29 Interference frequency suppression, 1067 4724 Internal Ethernet port, 3903 Internal Ethernet port Open settings, 3903 Internal network nodes Configuring, 593 Diagnostics, 605 Internal reference junction, 1068 Internal tags Data exchange, 3601 Internet Key Exchange (IKE), 588 Inter-Project_Engineering IPE, 4005 Interrupt event Delaying with DIS_AIRT, 2721 Disabling with DIS_IRT, 2718 Enabling with EN_AIRT, 2722 Enabling with EN_IRT, 2720 Interrupts Activating time-of-day interrupt with ACT_TINT, 2703 Canceling time-delay interrupt with CAN_DINT, 2708 Canceling time-of-day interrupt with CAN_TINT, 2702 Querying time-delay interrupt with QRY_DINT, 2708 Querying time-of-day interrupt with QRY_TINT, 2704 Receiving from I/O module with RALRM, 2566 Setting time-of-day interrupt with SET_TINT, 2697 Setting time-of-day interrupt with SET_TINTL, 2700 Starting time-delay interrupt with SRT_DINT, 2707 With packed addresses, 898 Intrusion Detection System (IDS), 82, 86 INV, 1976, 2260 Invalid license With a time zone change, 79, 91 InverseLinearScaling, 3523 Invert, 1744, 1976, 2021, 2260 InvertBit, 3521 InvertBitInTag, 3522 InvertLinearScaling, 3523 IO device Networking, 918 Update time, 921 Watchdog time, 922 IO field, 4146 Application, 4146 WinCC Basic V13.0 System Manual, 02/2014 Index Behavior, 4147 Changing between input fields, 4147 IO field, 4148 Layout, 4147 Operation, 4147 Touch operation, 4148 IO system, 918 Creating, 918 IO2MOD, 2810 IO-Link, 932 IP access control list, 543 IP address, 31, 444, 446, 906 IP address parameters, 907, 915 IP configuration Change parameters from the user program, 3162 IP packet filter rules, 557 IP parameters, 1098 IP protocol, 3705 IP rule sets, 548 IP services, 551 IP subnet, 446 IPE, 4005 File, 4006, 4007 IPE data Updating, 4010, 4015 IPE file, 4006 Initialization, 4006 Initializing, 4007 IPsec settings, 587 IPv4 addresses, 562 IPv6 E-mail, 1084 FETCH/WRITE, 1084 FTP client, 1084 FTP server, 1084 Notation, 1084 SNMP, 1084 Use with the CP 1543-1, 1084 IPv6 addresses, 562 IQ sense, 1076 iQ series, 3904 IS_ARRAY, 1844, 2122, 2347 IS_NULL, 1842, 2120 ISAKMP, 597 I-slave, 880, 888 Configuring, 889 Data access, 889 Data exchange, 880 ISO protocol, 635 Isochronous mode, 934, 939 ISO-on-TCP Characteristics, 488 WinCC Basic V13.0 System Manual, 02/2014 TSAP, 497 IW, 1309 IX, 1309 J Jerk limit Function, 4320 JMP, 1946, 2229 JMP_LIST, 1949, 2232 JMPN, 1947, 2230 Job mailbox, 3602 Transferring data, 3685, 3736, 3794, 3832, 3979 Jump, 1946, 1947, 1948, 1949, 1950, 1953, 2229, 2230, 2231, 2232, 2234, 2237 Jump distributor, 1950, 2234 Jump label, 1948, 2231, 2451 Jump list, 1949, 2232 K Key operation Date/time field, 4146 IO field, 4148 Keyboard operation, 402 Basic functions of the TIA Portal, 218 Customizing editors, 223 Editing objects, 224 Editing texts, 225 Navigation in the TIA Portal, 221 Online functions, 227 Project editing, 220 Selecting objects, 224 Tables, 226 Window, 220 KEY-PLUG, 790, 792 Formatting, 792 Keyword highlighting, 1489 Keywords, 1173 Know-how protection Changing a password, 1616 Introduction, 1610 Opening blocks, 1614 Printing block, 1615 remove, 1616 Setting up, 1613 L LABEL, 1948, 2231 LACP, 828 4725 Index LAD, 1398, 1718 Detailed comparison, 1572 LAD element Copying, 1425 Cutting, 1426 Deleting, 1431 Inserting, 1411, 1412 Inserting an operand, 1431 pasting from the clipboard, 1426 Replacing, 1427 Rules for inserting, 1409 Selecting, 1424 LAD network Branch, 1434 Closing a branch, 1436 Crossing, 1437 Deleting a branch, 1437 Deleting a crossing, 1439 Insert crossing, 1438 Inserting a block call, 1417, 1459 Inserting a branch, 1436 Program status display, 1652 Prohibited interconnections, 1411 Rearranging a crossing, 1438 Rules for simultaneous branches, 1435 Ladder Logic, 1398 Language Activate project language, 4052 Asian languages, 4050 Asian operating system, 4050 Disabling the project language, 4052 Editing language, 4052 Language support, 4050 Language-dependent format, 4049 Language-specific graphic, 4062 Log, 4072 multilingual project , 4054 Reference language, 4052 Regional format of the date, time, currency, and numbers, 4049 Language abbreviation, 698 Language behavior On-screen keyboard, 66 Language switching, 698, 4066, 4135 Log, 4072 Runtime language, 4069 Languages Migrating, 125 Layer Assigning objects to a layer, 3292 Layer 2, 547 Layer 3, 547, 792 4726 Layout Alarm indicator, 3317, 3405 Alarm view, 3312, 3315, 3404, 4167 Bar, 3298 Button, 3322, 4153 Circle, 3308 Date/time field, 3300, 4145 Ellipse, 3304 Graphic I/O field, 3306 Graphic view, 3305, 4149 I/O field, 3302 IO field, 4147 Line, 3311 Rectangle, 3318 Simple recipe view, 3455, 4175 Simple user view, 4158 Switch, 3321, 4154 Symbolic I/O field, 3323 Text field, 3326 Trend view, 3309, 4151 User view, 3300 Layout of the force table, 1684 LDT, 1229 Lead and lag algorithm, 2008, 2293, 2499 LEAD_LAG, 2008, 2293, 2499 Learning functionality, 593 Learning mode, 634 LED, 2740 LED ACK, 4168 LED status Reading out with LED, 2740 LEFT, 2544 LEN, 2543 Length Area pointer, 3641 Area pointers, 3643 LGC_GADR, 2818 Library, 3984 Adding a master copy, 352 Adding and using a block, 1335 Basics, 325 Buttons and Switches, 3988 Cleaning up, 380 Comparing library elements, 381 Copying a library object, 3987 Copying types to the clipboard, 375 Creating folders, 351 Cutting library elements, 375 Cutting master copies, 375 Cutting types, 375 Deleting instances, 376 Deleting types and versions, 376 WinCC Basic V13.0 System Manual, 02/2014 Index Displaying the properties of a type, 359 Harmonizing names and path structure, 379 Master copies, 325 Master copy, 3987 Moving library elements, 376 Open, 3994 Opening a released type version, 358 Pasting master copies from the clipboard, 376 Pasting types from the clipboard, 375 PLC data types generated by the system, 42 Released type version, 357 Save, 3994 Storing an object, 4000 Style, 4004 Task card, 327 Type, 3987 Type version in progress, 356 Type version in test, 356 Types, 325 Using filter view, 353 Using master copies, 351, 354 Using the element view, 329 Using types, 354 Versioning of types, 355 Library management Displaying cross references of an instance, 337 Displaying instances of type versions, 337 Displaying relations between library objects, 338 Filtering, 3992 Filtering by non-released types, 336 Opening, 335, 3991 Overview, 333, 3989 Library object, 3984, 3985 Inserting, 4001 Library view Exit, 333 Opening, 333 Overview, 330, 3985 License Defective, 79, 91 Defective license, 79, 92 Starting without a valid license, 88 Starting without valid license, 77 License key, 78, 90 Handling license keys, 78 Working with license keys, 90 License Manager Panel Plugin, 89 Licenses, 74 Life of certificates, 586 LIMIT, 1862, 2142, 2353 Limit and enable password legitimation, 1955, 2238, 2453 WinCC Basic V13.0 System Manual, 02/2014 Limit range Tag, 3347 Limit value, 1058, 1862, 2142, 2353, 3380 Tag, 3348 Limit value check, 4140, 4142 Limit value exceeded Analog alarm, 3348 Line, 3311 Design, 3217 Line end, 3217, 3311 Line start, 3311 Line break, 1049 Line end Line, 3311 Line start Line, 3311 Linear programming, 1144 LinearScaling, 3533 Link folder External graphic, 3232 Linked objects Copying, 4088, 4089 Linking, 4045 Linking HMI tags, 149 LINT, 1217 LLDP, 543, 544, 926 LLDP (Link Layer Discovery Protocol), 926, 3664, 3713, 3766 LN, 1866, 2147, 2357 Load Extended download to device, 64 HMI device, 4114 SIMATIC PC station, 65 Load memory, 957, 1638 Displaying, 1642 Load window layout Loading additional window layouts, 215 Loading via quick access, 215 Loading Blocks to the device, 1602 Configurations with PROFIBUS, 939 Configurations with PROFINET, 939 Configurations with web server, 938 Device configurations, 936 Distributed I/O, 937 Downloading project data to the device, 267 Downloading to a memory card, 269 from a device, 36, 42, 270 General information, 265 Going online, 943 GSDML, 940 HMI devices, 943 4727 Index I-device, 940 IE/PB-Link, 942 in RUN operating mode, 1602 Isochronous applications, 934, 939 Module comments, 37 Placeholder, 940 Shared Devices, 942 Subnets, 938 to PG/PC, 935 to the device, 36, 934 Uploading blocks from a memory card, 1609 Loading projects with connected HMI device, 4105 Loading with S7 routing, 4106 Local assignment Of a function key, 3278, 3282 Local data bit (L), 958 Local data byte (LB), 958 Local data double word (LD), 958 Local data word (LW), 958 Local error handling, 1521 Error information, 1521 Instructions, 1521 Priorities, 1522 Local logging, 599 Local tag, 1375 Local time, 971 Calculating with SET_TIMEZONE, 2516 Reading out with RD_LOC_T, 2513 Writing with WR_LOC_T, 2513 Log Language switching, 4072 Runtime language, 4072 Log file Modem alarms , 4659 Log language, 4072 Log table Event log, 736 LOG_GEO, 2814 LOG2GEO, 2808 LOG2MOD, 2809 Logarithm, 1866, 2147, 2357 Logging, 598 CP x43-1 Adv., 645 SCALANCE S, 622, 624 Logic analyzer function, 4561 Logic operation AND, 1971, 2255 EXCLUSIVE OR, 1974, 2258 OR, 1973, 2257 Logic path Deleting, 1479 4728 Inserting, 1479 Use, 1478 Logical address Determining a module with GADR_LGC, 2817 Determining a module with RD_LGADR, 2816 Determining associated slot with LGC_GADR, 2818 Determining associated slot with LOG_GEO, 2814 Logoff, 3509 Users, 4160 Logoff time, 4157 Changing, 3475 Changing in runtime, 3483 Logon, 3514 Logon failed, 3485 Reporting, 3488 User, 3484 Logon dialog Configuring access protection, 3487 Logon for web server, 672 Logon web server, 672 Long word, 1211 Loop, 2440, 2444, 2446, 2448, 2449, 2450 Loop-in-alarm Configured, 3389 Loop-In-Alarm, 3582 Low free storage space, 3585 LREAL, 1221, 1267, 1292 LREAL_TO_, 1292 LTIME, 1225 LTOD, 1227 LWORD, 1211 M MAC packet filter rules, 560 MAC rule sets, 548 MAC services, 554 Main, 999 Main mode, 588 managing Graphic, 3231 Managing User group, 3475 Users, 3474 Users in runtime, 3482 Manual fragment, 694 Manuals, 3619 Master copy Library, 3987 WinCC Basic V13.0 System Manual, 02/2014 Index Math functions CALCULATE, 1420, 1462 MAX, 1860, 2140, 2351 MAX_LEN, 2532 Maximum, 1860, 2140, 2351 Maximum cycle time, 954, 975, 976, 1960, 2243 Maximum length Tag, 66 Maximum load memory available Displaying, 1642 MB, 1309 MB_CLIENT, 3038, 3055 MB_COMM_LOAD, 3021 MB_MASTER, 3025 MB_SERVER, 3045, 3066 MB_SLAVE, 3032 MC_ChangeDynamic Instruction, 2848 Parameter, 2848 Parameter, 2851 MC_CommandTable Instruction, 2846 Parameter, 2847 MC_Halt Function chart, 2831 Instruction, 2829 Parameter, 2863 Parameters, 2830 MC_Home Instruction, 2826 Parameter, 2827 MC_MoveAbsolute Parameter, 2833 Function chart, 2834 Instruction, 2832 MC_MoveJog Function chart, 2845 Instruction, 2843 Parameter, 2844 MC_MoveRelative Function chart, 2838 Instruction, 2835 Parameter, 2836 MC_MoveVelocity Function chart, 2842 Instruction, 2839 MC_Power Function chart, 2823 Instruction, 2820 Parameters, 2820 MCAT, 2000, 2285, 2491 MD, 1309 WinCC Basic V13.0 System Manual, 02/2014 MD5, 583, 589 MDM, 239 Meaning of the columns in the force table, 1684 Measure program runtime, 1969, 2253, 2467 Measuring window (GATE), 1046 Memory area Load memory, 957 Retentive memory areas, 959 Work memory, 957 Memory bit (M), 958 Memory byte (MB), 958 Memory card, 31, 955, (See Memory Card) Accessing, 324 Adding a card reader, 323 Formatting, 1119 Introduction, 322 Removal/insertion, 35 Showing properties, 324 Memory cards, 32 Memory double word (MD), 958 Memory requirements Recipe, 4192 Memory reserve, 42 Memory reset, 955 Making, 1114 Memory word (MW), 958 Menu command Simple recipe view, 3456, 4176 Message Sending, 990 Specifying the end, 991 Specifying the start, 990 MIB, 543 Micro, 3931 MicroLogix, 3861, 3883 MID, 2545 Migrated project Compiling, 116 Migrating projects Procedure, 110 Requirements, 109 Migration, 31 Adaptations beforehand, 117 Alarm groups, 122 Allen-Bradley DF1 data types, 136 Allen-Bradley Ethernet IP data types, 136 Basics, 112 Data types Modicon Modbus, 137 Data types Modicon Modbus TCP/IP, 138 Data types Omron Hostlink/Multilink, 138 Data types SIMATIC S7 200, 139 Data types SIMATIC S7 300/400, 139 4729 Index Displaying a log file, 111 Displaying history, 111 Font settings, 120 Global library, 127 Including the hardware configuration, 106 Integrated project, 142 Introduction, 112 Introduction to migration, 105 Migrating an integrated project, 131, 142 Migrating projects, 115, 133 Mitsubishi FX data types, 137 of external tags, 135 of languages, 125 of project text, 125 Project library, 127 Recipe data, 128 Runtime data, 128 Supported HMI devices, 117 Supported products, 105 Tags, 121 Text, 125 The migration process, 105 User administration, 128 WinCC V7.0 SP3, 51 Migration tool, 114 Creating a migration file, 109 Distribution and sources, 103 Including the hardware configuration, 107 Removing, 104 System requirements, 103 Using the migration tool, 106 MIN, 1858, 2138, 2349 Minimum, 1858, 2138, 2349 Minimum cycle time, 954, 975 Mirroring, 809, 811 Missing supply voltage, 1058, 1066 Mitsubishi, 3852 Address, 3905 Analog alarm, 3919 Basic Panel, 3647 Communication drivers, 3894 Connection interruption, 61 FX, 3894 TCP/IP, 3894 Mitsubishi FX Configuring a connection, 3907 Connection, 3907, 3912 Connection parameters, 3909 CPU type, 3914 Data type, 3913 Migrating data types, 137 Mitsubishi MC TCP/IP, 3899, 3911 4730 Mitsubishi MC TCP/IP Configuring a connection, 3895 Connection, 3895, 3898 Connection parameters, 3896 CPU type, 3904 Data type, 3903 Mixed mode, 590 MOD, 1481, 1853, 2132 Modbus communication as a slave with MB_SLAVE, 3032 as Modbus master with MB_MASTER, 3025 Configuring a port with MB_COMM_LOAD, 3021 Mode, 3322 Graphic I/O field, 3306 I/O field, 3302 Modem Local, 4612 Problem, 4655 Remote, 4613 Modem alarms Log file, 4659 Modem connection cannot be established, 4659 Modem connection is closed, 4659 Modem connection is interrupted, 4658 Causes and solutions, 4658 Modems without plug-and-play, 4613 Modicon Approved communication with Modbus RTU, 3939 Connection, 3938 Connection cable, 3938 Restrictions with Modbus RTU, 3939 Modicon M340, 3931 Modicon Modbus, 3852 Basic Panel, 3647 Communication drivers, 3922 Migrating data types, 137 RTU, 3922 TCP, 3922 Modicon Modbus connection Data types, 3948 Modicon Modbus RTU, 3944 Configuring a connection, 3934 Connection, 3934 Connection parameters, 3936 Data type, 3943 Modicon Modbus TCP, 3931 Configuring a connection, 3922 Connection, 3922, 3927 Connection parameters, 3924 Data type, 3930 WinCC Basic V13.0 System Manual, 02/2014 Index Modicon MODBUS TCP/IP Change word order, 3926 Modicon Modbus TCP/IP Migrating data types, 138 Modify High-speed counters, 2882 Modify value Permitted operands, 1663 Modifying mode, 1670 Module Addressing, 665 Asynchronously reading data record with RD_DPARA, 2686 Communication Status, 604 Configuring and assigning, 35 Copying, 421 Deleting, 420 Determine diagnostics status, 1106 Determining logical address of the slot with LOG_GEO, 2814 Determining logical address with GADR_LGC, 2817 Determining logical addresses with RD_LGADR, 2816 Determining slot of a logical address with LGC_GADR, 2818 Determining start address with GEO_LOG, 2813 Inserting, 35, 419 Moving, 422 Reading data record with RD_DPAR, 2684 Removing, 35 Replacing, 423 Select, 410 Time of day on a module, 1114 Module addressing, 962 Module arrangement, 407 Module comments, 37 Module replacement, 146 Module rights, 542 Module titles, 409 Module version Updating, 426 ModuleStates, 2755 Momentum, 3931, 3944 Monitor, 924, 3662, 3711, 3764 Monitoring "Monitor all" command, 1672, 1697 "Monitor now" command, 1698 "Monitor once and now" command, 1673 Monitoring and modifying modes, 1670 Monitoring mode, 1670 Monitoring window, 1075 WinCC Basic V13.0 System Manual, 02/2014 Mono-master system, 879 Motion Control CPU S7-1200 Guidelines, 4322 Move Block, 1894, 1923, 2175, 2205, 2372, 2413 Block uninterruptible, 1900, 1925, 2181, 2207, 2377, 2415 Character string in array with Ctrl_TO_Chars, 2529 Screen, 3190 Value, 1879, 2160 MOVE, 164, 1879, 2160 Move block, 1896, 2177, 2374 Move view Keyboard operation, 403 Overview navigation, 388, 391, 393 MOVE_BLK, 1894, 2175, 2372 MOVE_BLK_VARIANT, 1896, 2177, 2374 MoveVelocity Parameter, 2840 Moving Hardware components, 422 Moving the view Overview navigation, 3606, 3612, 3614 MPI, 3620 Addressing, 3782 Connection, 3804 HMI connection, 3776 Network, 3622 Network architecture, 3622 Parameters, 3778, 3780, 3781 S7 200, 3811, 3820 S7 300/400, 3775, 3776 MPI address S7 300, 3782 S7 400, 3783 MPI communication S7 300/400, 3775 MPI parameters S7 300/400, 3778, 3780, 3781 MRP domain, 1101 MRP domain properties, 1101 MSK_FLT, 2715 MSTP, 823 MUL, 1850, 2129 Multicast, 570, 834 Multi-instance Declaring, 1387 Definition, 1159 Multi-key operation, 69 Multiple instance, 1189 Correcting the call type, 1420, 1461 4731 Index Multiple selection, 410, 3210 Multiple Spanning Tree, 823 Multiplex, 1981, 2265, 2473 Multiplex/synchronous mode, 1080 Multiplexing, 3354 Address multiplexing, 3358 Address multiplexing Allen-Bradley Ethernet IP, 3865 with absolute addresses, 3358 with symbolic addresses, 3358 Multiply, 1850, 2129 Multi-point connection Allen-Bradley DF1, 3876, 3877 MUX, 1981, 2265, 2473 MW, 1309 MX, 1309 My Documentation Manager, 239 N N, 1754, 1756, 2031, 2033 N_TRIG, 1759, 2036 Name Array element, 57 Names of alarm classes Change through migration, 123 NAT/NAPT Routing, 569 NE_ElemType, 1841, 2119 NE_Type, 1838, 2117 NEG, 1854, 2133 Negate, 1854, 2133 Negotiation, 784 Nesting depth, 1157 Network, 40, 3595 Closing, 1405, 1447 Copying, 1404, 1446 Deleting, 1404, 1447 Entering a comment, 1407, 1450 Ethernet, 3621 Insert title, 1406, 1449 Inserting, 1402, 1404, 1445, 1446 MPI, 3622 Navigating blocks, 1408, 1451 Opening, 1405, 1447 PPI, 3623 PROFIBUS, 3621 PROFINET, 3621 Selecting, 1403, 1445 Using, 1402, 1444 Network access Opening the properties, 4545 4732 Network adapter, 644 Network architecture PPI, 3623 Network comments Hiding, 1363 Showing, 1363 Network drive, 31 Network editor Components, 386, 3603 Function, 385, 3603 Hardware catalog, 399, 3617 Inspector window, 3615 Inspector window , 397 Network ID, 630 Network overview Basic functions, 433 Basic functions for editing the network overview table, 433 Network Syslog, 599 Network view, 3624 Adding device, 415 Hardware and network editor, 387, 3605 Networking Communication partners, 3624 Devices, 3624 Networking devices Basics of configuring networks, 429 Editing interface parameters, 435 Editing network parameters, 435 Networking several interfaces at the same time, 431 Networking with an existing subnet, 432 Networking without an existing subnet, 430 Networks within a project, 429 Requirements, 434 Types of communication, 429 Networking in the device view Networking options, 433 Procedure, 434 New data types, 158 Nodes with an unknown IP address, 591 Non-integrated Connection, 3629 Non-licensed mode Engineering System, 88 ES, 77 HMI devices, 89 NORM_X, 1939, 2222, 2429 Normalize, 1939, 2222, 2429 Normally closed contact, 1743 Normally open contact, 1742 NOT, 1485, 1486, 1744 WinCC Basic V13.0 System Manual, 02/2014 Index Not equal, 1843, 2121 NOT_NULL, 1843, 2121 NOT_OK, 1836, 2115 NTP, 834 NTP (secure), 579 NTP server, 579 NULL, 1240 O O, 4533 OB Events and OBs, 963 Overview, 963 OB 1, 999 OB 80, 1008 OB 82, 1009 OB for manufacturer-specific interrupt, 1004 OB for profile-specific interrupt, 1004 OB 83, 1011 object Group, 3236 Paste, 3228 Rotate, 3215 Object Arrange, 3204, 3213 Assigning to a layer, 3292 Availability for Basic Panels, 3297 Creating a new OLE object, 3204 Creating an OLE object from a file, 3204 Deleting, 3206 Design, 3217 Designing the background color, 3219 Designing the fill pattern, 3220 Dynamization, 3264 Dynamization of the appearance, 3269 Dynamize direct movement, 3272 editing within a group, 3240 Evenly distributing, 3213 Flip, 3204 Flush alignment, 3212 Grouping, 3236 Inserting, 3203, 3204 Inserting of the same type, 3204 Inserting several times, 3228 Multiplying, 3228 outside the area, 3214 Repositioning and resizing multiple objects, 3204, 3230 Repositioning objects, 3207 Resize, 3209 Rotate, 3204, 3215 WinCC Basic V13.0 System Manual, 02/2014 Select multiple objects, 3210 Selecting multiple objects, 3204 Storing in a library, 4000 Tab sequence, 3204 Transparency, 3220 Object group Animation, 3274 Editing an object within a group, 3240 Removing an object, 3239 Object list Tag, 3338 Object names Uniqueness, 113 Object size Harmonizing, 3209 Obtaining user rights Logging on to the operating system with administrator privileges, 229 With Windows user account control, 229 OF, 2442 Off delay, 1767, 1775, 1793, 1802, 2044, 2070, 2080, 2308, 2328 Offline, 528 OK, 1835, 2114 OLE object create from a file, 3204 Recreate, 3204 Save in Graphics, 3233 Storing in the image browser , 4064 Omron, 3852 Analog alarm, 3964 Basic Panel, 3647 Communication drivers, 3950 Host Link, 3950 Omron Host Link, 3960 Address, 3961 Configuring a connection, 3951 Connection, 3951, 3955 Connection cable, 3955 Connection parameters, 3953 Data type, 3959 Omron Hostlink/Multilink Migrating data types, 138 On delay, 1765, 1773, 1788, 1799, 2042, 2065, 2076, 2305, 2323 Retentive, 1791, 1800, 2068, 2078, 2325 On demand, 3351 Ones complement, 1976, 2260 Online, 29, 528 Hardware detection, 417 Online access, 4542 Online and Diagnostics view, 1085 4733 Index Online connection, 4533 Multiple TIA Portal instances, 35 Online diagnostics, 600 Online displays Orange color, 1094 Online mode, 4533 Canceling an online connection, 4537 Display of the online mode, 4535 Displaying accessible devices on an interface, 4531 Displaying all accessible devices as a list, 4531 Go online, 4536 Standby or hibernation of the programming device / PC, 4533 Online operation, 30, 35 Online Tools, 1085, 1095 OP 73 Baud rate on PROFIBUS, 3697, 3751 OP 77A Baud rate on PROFIBUS, 3697, 3751 OP 73 Baud rate on PROFIBUS, 3809, 3811, 3818, 3820, 3821 OP 77A Baud rate on PROFIBUS, 3809, 3811, 3818, 3820, 3821 OP73 Loading a project, 65 OP77A Loading a project, 65 OPC Basic Panel, 3647 Open Global library, 3994 Open a project, 244 Compatibility mode V12 SP1, 243 Open log file Packet filter events, 606, 608 Security events, 606, 608 System events, 605, 608 Open User Communication Changing parameter values, 495 Ability to read back, 496 Changing IP configuration parameters with T_CONFIG, 3162 Connection configuration, 474, 476 Connection description, 489, 492, 493 Connection establishment, 474 Connection parameters, 479 Creating a connection, 483 Deleting an interconnection, 486 4734 Establishing a communication connection with TCON, 3124, 3127 Establishing a connection and reading data with TRCV_C, 3102, 3107 Establishing a connection and sending data with TSEND_C, 3091, 3095 General, 473 Instructions, 474 Port numbers, 494 Protocols used, 487 Receiving data via UDP with TURCV, 3153 Receiving data with TRCV, 3140, 3144 Sending data via UDP with TUSEND, 3150 Sending data with TSEND, 3134, 3137 Starting connection parameter assignment, 482 TCON_IP_RFC, 493 TCON_IP_v4, 492 TCON_Param, 489 Terminating a communications connection with TDISCON, 3132 TSAP, 497 Opening a force table, 1687 Opening a watch table, 1660 Opening phone books, 4604 Opening Siemens Industry Online Support, 401 Operand, 1173, 1179, 1180, 1181, 1182, 1183, 1185, 1186, 1187, 1189, 1190, 1192, 1193 Inserting, 1431, 1473 Operand area, 958 Operating behavior Enabling system memory, 992 Using clock memory, 993 Using time-of-day functions, 978 Operating mode, 644 Introduction, 949 RUN, 954 STARTUP, 951 STOP, 954 Transitions, 950 Operating object Availability for Basic Panels, 3297 Operating recipes Creating a recipe data record, 3458 Creating recipe data records, 3458, 3459 Read recipe data record, 3459 Transfer data record, 3460 Operating system Asian language setting, 4050 Setting to Western, 4050 Updating, 4119 Operating system , 1143 WinCC Basic V13.0 System Manual, 02/2014 Index Operation Alarm indicator, 3405 Button, 4153 Date/time field, 4145 Graphic IO field, 4150 Graphic view, 4149 IO field, 4147 simple alarm view, 4167 Simple alarm view, 3404 Simple recipe view, 3455, 4175 Simple user view, 4159 Switch, 4154 Symbolic IO field, 4156 Trend view, 4152 Operation in runtime Multi-key operation, 69 Operator control Alarm view, 3315 Trend view, 4152 Operator input in the recipe view Transferring data, 3735, 3793, 3831, 3978 Optimized access, 1151, 1153 Optimized block access, 157 Optimizing the configuration Allen-Bradley DF1, 3868, 3889, 3906, 3916, 3933, 3945, 3962 Option handling, 894, 897, (See Configuration control (ET 200SP)), (See Configuration control (ET 200MP)) OR, 1486, 1973, 2017, 2018, 2257 Order number, 399, 734 Organization block (OB) Assigning event with ATTACH, 2692 Canceling event assignment with DETACH, 2693 Creating, 1332 Cyclic interrupt OB, querying parameters with QRY_CINT, 2696 Cyclic interrupt OB, setting parameters with SET_CINT, 2694 exporting to an external source file, 1562 Function, 1146 Reading start information with RD_SINFO, 2729 Start information, 1146 OSPF Area range, 857 Areas, 725, 856 Configuration, 854 Interfaces, 858 Link State Advertisement, 725 OSPFv2 Interfaces, 751 OSPFv2 LSDB (information), 755 OSPFv2 neighbors, 752 OSPFv2 virtual neighbors, 754 WinCC Basic V13.0 System Manual, 02/2014 Router, 725 Router status, 725 Virtual Links, 860 Other PLCs Addressing, 3853 Data types, 3853 Special features, 3853 OUT_RANGE, 1834, 2113 Outgoing, 3374, 3580 Output Inserting, 1428, 1469 remove, 1429, 1470 Output (O), 958 Output byte (QB), 958 Output double word (QD), 958 Output fields Multiplex tag, 59 Output word (QW), 958 Overflow, 1050, 1058, 3584 Overlay icon, 1092 Overlaying Tag, 1193 Overlaying tags, 1386 Overview using the display formats in the force table, 1691 via the display formats in the watch table, 1665 Overview navigation, 388, 391, 393, 3606, 3612, 3614 Overview of the cross-reference list, 1645 Overview of TS Adapters that can be used, 4611 Overview window, 48, 210 Comparing objects, 212 Display all blocks, 213 Showing and hiding columns, 213 Sorting details view, 213 P P, 1753, 1755, 2030, 2032 P_TRIG, 1757, 2035 Packet filter log, 606, 608 PageDown, 3550 PageUp, 3549 Pane mode, 207 Panning, (See move view) Parameter For CPU, 971 Hidden parameters, 1433, 1474 Predefined - writing with WR_DPARM, 2690 SIMATIC LOGO!, 3843 Parameter assignment, 1162 4735 Index Parameter assignment parameters Hardware, 404 Parameter transfer, 1161, 1163, 1165, 1167, 1169, 1170, 1171, 1172 Parameter types, 1247 Parameters Connection, 3856, 3870, 3896, 3909, 3924, 3936, 3953 MPI, 3778, 3780, 3781 PROFIBUS, 3668, 3670, 3671, 3716, 3718, 3719, 3770, 3771, 3773 S7 1200, 3748 S7 1500, 3694 S7 200, 3806, 3811, 3816, 3820, 3821 Part number, (see Order number) Password, 4157 Backing up, 4158 Changing, 3474 For CPU access protection, 971 for function key, 3285 Hierarchy level, 3468 HMI connection, 3660, 3672, 3709, 3722 Password aging, 3469 Password complexity, 3469 Restoring, 4158 Password legitimation, 1955, 2238, 2453 Password list, 4157 Password protection, 672, 971, 994, 995 Protection concept, 288 Revoking access rights, 289 Pasting Adjusting screen size, 4087 Color, 4086 Font, 4086 Function key, 4087 Invalid object, 4086 Principle, 4085 PC CP, 527 PE_CMD, 2635 PE_DS3_Write_ET200S, 2641 PE_End_RSP, 2672 PE_Error_RSP, 2669 PE_Get_Mode_RSP, 2674 PE_I_DEV, 2665 PE_List_Modes_RSP, 2673 PE_Measurement_List_RSP, 2679 PE_Measurement_Value_RSP, 2681 PE_PEM_Status_RSP, 2676 PE_Start_End, 2631 PE_Start_RSP, 2670 PE_WOL, 2642 PEEK, 2393 4736 Read memory address, 2393 PEEK_BOOL, 2395 Read memory bit, 2395 Perfect Forward Secrecy, 589 Performance, 156 Performance features Engineering system, 4181 HMI device, 4183, 4187 Permanent connection, 704 Permanent station, 704 Permit access with PUT/GET communication from remote partners, 998 Permit overwriting of device name, 926 Permitted data types Trends, 3690, 3849 Permitted operands for the force table, 1689 Permitted operands for the watch table, 1662 PG/PC interface Go online, 4537 Modifiable MPI interface parameters, 4552 Modifiable PROFIBUS interface parameters, 4552 PID_3Step In/out parameters, 2944 Input parameters, 2940, 2971 Instruction, 2931, 2963 Output parameters, 2942, 2972 Static tags, 2973 PID_Compact Input parameters, 2893, 2915 In/out parameters, 2895 Instruction, 2912 Output parameters, 2894, 2916 Static tags, 2896, 2917 Pin assignment 6XV1440 - 2P for Mitsubishi PG protocol, 3912 Allen-Bradley, 3877 Allen-Bradley cable 1747-CP3, 3879 Allen-Bradley cable 1761-CBL-PM02, 3880 Allen-Bradley cable 1784-CP10, 3878 Multipoint cable 1:MP/TP/PC, 3957 Multipoint cable 2:RS422, MP/TP/PC, 3958 Point-to-point cable 1, Point-to-point cable 2, 3942 Point-to-point cable PP1 for Omron, 3958 Point-to-point cable PP2 for Omron, 3959 Ping, 794 Placeholder device, 940 PLC Connecting, 3858, 3898, 3912, 3927, 3955 MPI parameters, 3781 PROFIBUS parameters, 3671, 3719, 3773 WinCC Basic V13.0 System Manual, 02/2014 Index PROFINET parameters, 3658, 3705, 3760 Reading recipe data record, 4179 Tag, 3354 Transferring recipe data record, 4180 PLC data, 4006 PLC data type Addressing, 1191 Comparing, 1593 Creating, 1552 Declaration in data blocks, 1533 Declaration in the block interface, 1385 Declaration table for PLC data types, 1551 Declaring, 1555 Declaring ARRAY, 1554 Declaring STRUCT, 1555 Definition, 1248, 1551 Deleting, 1553 Offline/offline comparison, 1569 PLC data types generated by the system in libraries, 42 Programming the structure, 1553 Tag properties, 1556, 1557 PLC data types, 40, 158 PLC tag Importing and exporting, 1327, 1328, 1329 Automatically filling in cells, 1327 Comparing, 1591 Comparing a PLC tag table, 1569 Comparison, 1565 Copying, 1325 Declaring, 1313, 1314, 1316, 1318 Definition, 1179 Monitor, 1324 Offline/offline comparison, 1569 Permissible addresses and data types, 1311 PLC tag table, 1305, 1306, 1311, 1312, 1313 Properties, 1321, 1322 Reconnecting, 3346 Retentive behavior, 1315 Rules, 1311 Sorting rows, 1326 Updating comparison results, 284 PLC tags, 680, 681, 683 PLC5, 3883 PLUG, 792 C-PLUG, (C-PLUG) KEY-PLUG, (KEY-PLUG) PN/PN couplers Grouping, 931 Linking Ethernet subnets, 931 Pointer ANY, 1242 WinCC Basic V13.0 System Manual, 02/2014 POINTER, 1240 VARIANT, 1245 POINTER, 1240 Pointer name Area pointer, 3641 point-to-point, 723 Point-to-point communication (PtP), 984 Freeport protocol, 984 Point-to-point connection Allen-Bradley DF1, 3875 Configuring communication parameters with PORT_CFG, 2992 Configuring receive parameters with RCV_CFG, 2996 Configuring serial transmission parameters with SEND_CFG, 2995 Deleting receive buffer with RCV_RST, 3006 Enable receiving with RCV_PTP, 3005 Initiating data transfer with SEND_PTP, 3003 Querying the signal state with SGN_GET, 3007 Setting output signals with SGN_SET, 3008 POKE, 2397 Write memory address, 2397 POKE_BLK, 2400 Write memory area, 2400 POKE_BOOL, 2399 Write memory bit, 2399 Port, 446 102 (S7 protocol - TCP), 551 123 (NTP), 571, 578 161 (SNMP), 571 20/21 (FTP), 551 443 (HTTPS), 571 4500 (IPsec), 571 500 (IPsec), 571 500 (ISAKMP - UDP), 597 514 (Syslog), 571 80 (HTTP), 551 8448 (security diagnostics), 657 Configuration, 785 Interconnecting, 920 Port configuration, 784, 787 Renaming, 522 Port configuration, 787 Port diagnostics SFP diagnostics, 797 Port numbers, 494 Port options, 925, 3663, 3712, 3765 Enable autonegation, 924, 3662, 3711, 3764 Monitor, 924, 3662, 3711, 3764 Transmission medium/duplex, 923 Transmission rate / duplex, 3662, 3711, 3764 4737 Index PORT_CFG, 2992 Portal view, 187 Position Editing multiple objects, 3230 Of objects, 3207 Positioning axis technology object Configuring approach/homing direction, 4354 Configuring distance per motor revolution, 4340 Configuring end of reference point switch, 4353 Configuring maximum velocity / start/stop velocity, 4345 Configuring passive homing, 4352 Configuring the homing speed, 4355 Drive enable configuration, 4339 Drive ready configuration, 4340 PTO and HSC configuration, 4337 User unit configuration, 4339 Active homing, 4357 ActiveHoming tags, 4449 Actor tags, 4447 Add new object, 4335 Axis name configuration, 4337 Basic parameters, 4336 Changing the configuration parameters for dynamics in the user program, 4351 Changing the configuration parameters for homing in the user program, 4358 Commissioning overview, 4334 Configuration overview, 4334 Configuration window icons, 4336 Configuring acceleration, 4346 Configuring active homing, 4353 Configuring deceleration, 4346 Configuring end of reference point switch, 4355 Configuring home position offset, 4355 Configuring invert direction signal, 4340 Configuring jerk limiter, 4347 Configuring permit auto reverse at the hardware limit switch, 4354 Configuring pulses per motor revolution, 4340 Configuring ramp-down time, 4346 Configuring ramp-up time, 4346 Configuring reference point position, 4353, 4355 Configuring reference point switch input, 4353, 4354 Configuring smoothing time, 4347 Configuring the velocity limiting unit configuration, 4345 Diagnostics overview, 4334 Drive signal configuration, 4339 DynamicDefaults tags, 4454 DynamicLimits tags, 4453 4738 Emergency stop deceleration configuration, 4348 ErrorBits tags, 4463 Extended parameters, 4336 General dynamics configuration, 4345 Hardware and software components, 4330 Hardware interface configuration, 4337 Homing tags, 4457 Mechanics configuration, 4340 Mechanics tag, 4452 Passive homing, 4355 PassiveHoming tags, 4450 Position tag, 4446 PositionLimitsHW tags, 4456 PositionLimitsSW tags, 4455 Response when jerk limiter is activated, 4350 StatusBits tags, 4459 StatusPositioning tags, 4458 Tools, 4333 Units tag, 4452 Updating the tags, 4464 Velocity tag, 4447 Possible cause of error Transferring data, 3687, 3738, 3796, 3834, 3981 Power budget, 1064 PPI, 3620 Network, 3623 Network architecture, 3623 S7 200, 3821 Predefined alarm classes, 3375, 3376 Predefined firewall rules CP 1543-1, 657 CP 1628, 648 CP x43-1 Adv., 646 SCALANCE S, 622, 624 Predefined styles, 3227 Premium, 3931 Prerequisites for establishing a VPN connection, 4640 Preshared keys, 587 Press, 3579 Press ESC twice, 3580 Press key, 3584 PressButton, 3546 Print scope, 291 Printable contents, 291 Printing Changing the settings, 292 Creating a cover page, 297 Creating frames, 296 Documentation settings, 290 Elements in the library, 295 Elements in the project tree, 295 WinCC Basic V13.0 System Manual, 02/2014 Index Non-printable contents, 291 Non-printable objects, 292 Print contents, 294 Printing device view, 394 Printing network view, 394 Process a cover page, 298 Process borders, 298 Specify layout, 293 Specify print layout, 293 Specifying the print area, 302 Structure of printout, 290 Use borders, 295 Use borders and cover pages, 290 Use cover page, 293 Printing a project, 307 Printing labels, 311 Determining the correction value for the print shift, 312 Printing of alarms Configuring:printing of alarms, 3393 Priorities Local error handling, 1522 Process control phase, 4124 Process data area Module addressing, 962 Module start address, 962 Process image, 962 Basics, 960 I/O access error, 960 Reading inputs with GETIO, 2562 Reading the process image area with GETIO_PART, 2563 Synchronizing the inputs with SYNC_PI, 2555 Synchronizing the outputs with SYNC_PO, 2556 Transferring the process image area with SETIO_PART, 2564 Updating, 960 Updating inputs with UPDAT_PI, 2551 Updating the outputs with UPDAT_PO, 2553 Writing outputs with SETIO, 2563 Product support, 3619 PROFIBUS, 441, 3620, 3721, 3774 Connection with PROFINET, 902 ET 200S in DPV1 mode, 898 HMI connection, 3665, 3715, 3768 Network, 3621 OP 73, 3697, 3751 OP 77A, 3697, 3751 OP 73, 3809, 3811, 3818, 3820, 3821 OP 77A, 3809, 3811, 3818, 3820, 3821 Parameters, 3668, 3670, 3671, 3697, 3716, 3718, 3719, 3751, 3770, 3771, 3773, 3809, 3818 WinCC Basic V13.0 System Manual, 02/2014 S7 1200, 3714 S7 1500, 3667 S7 300/400, 3665, 3767, 3768 S7-1200, 3715 Standard, 3721, 3774 Universal, 3721, 3774 PROFIBUS cable configuration Optical ring, 443 PROFIBUS communication S7 1200, 3714 S7 1500, 3667 S7 300/400, 3767 PROFIBUS DP, 881, 3621 Connection, 3802 PROFIBUS parameters S7 1200, 3716, 3718, 3719 S7 1500, 3668, 3670, 3671 S7 300/400, 3770, 3771, 3773 PROFIBUS profile, 441, 3721, 3774 Different profiles on the same subnet, 441, 3721, 3774 Effect on the transmission rate, 441, 3721, 3774 Meaning of profiles, 442, 3721, 3775 PROFIenergy Control PROFIenergy commands in the I-Device, 2665 Description, 2629 Generate answer to command at end of pause, 2672 Generate answer to command at start of pause, 2670 Generate list of supported measured values as answer, 2679 Generate negative answer to command, 2669 Generate PEM status as answer, 2676 Generate queried energy data as answer, 2674 Generate queried energy savings modes as answer, 2673 Generate queried measured values as answer, 2681 Generate supported PROFIenergy commands as answer, 2678 PE_CMD, 2635 PE_DS3_Write_ET200S, 2641 PE_End_RSP, 2672 PE_Error_RSP, 2669 PE_Get_Mode_RSP, 2674 PE_I_DEV, 2665 PE_Identify_RSP, 2678 PE_List_Modes_RSP, 2673 PE_Measurement_List_RSP, 2679 PE_Measurement_Value_RSP, 2681 4739 Index PE_PEM_Status_RSP, 2676 PE_Start_End, 2631 PE_Start_RSP, 2670 Reading out status information, 2635 Set power module switching behavior, 2641 Start and exit energy-saving mode, 2631, 2635 Wake on LAN, 2642 Profile, (See bus profile) Profiles, 1004 PROFINET, 446, 635, 3620 Connection, 3801 Connection with PROFIBUS, 902 Device replacement without exchangeable medium, 926 HMI connection, 3652, 3653, 3700, 3701, 3754, 3755 S7 1200, 3700 S7 1500, 3652 S7 300/400, 3754 PROFINET address, 537 PROFINET device name, 912 PROFINET interface, 915, 971, 1098 PROFINET IO, 901, 906, 907, 917, 918 Port options, 923, 3662, 3711, 3764 PROFINET IO device Assigning a name, 1122 Name assignment in the dialog, 1124 Name assignment in the online and diagnostics view, 1123 PROFINET IO devices Reading a portion of the inputs with GETIO_PART, 2563 Reading consistent data with DPRD_DAT, 2601 Writing a part of the outputs with SETIO_PART, 2564 Writing all outputs with SETIO, 2563 Writing consistent data with DPWR_DAT, 2603 PROFINET IO system, 918 PROFINET parameters HMI connection, 3655, 3702, 3757 HMI device, 3656, 3704, 3758 PLC, 3658, 3705, 3760 S7 1200, 3702, 3705 S7 1500, 3655, 3656, 3658 S7 300/400, 3757, 3758, 3760 PROFINET RT class, 902 Program alarm generating with Program_Alarm, 2722 Program card, 955 Program control operations, 1960, 2244, 2458 Program cycle OB Description, 999 4740 Program editor "Instructions" task card, 1356 Block interface, 1356 Enlarging the programming window, 1362 Favorites, 1356 Function, 1354 General settings, 183, 185, 186, 1373 Programming window, 1356 Structure, 1355 Testing task card, 1356 Toolbar, 1356 Using the keyboard, 1358 Program execution Cyclic, 999 Program information Displaying, 1617 In the assignment list, 1618 In the call structure, 1626 In the dependency structure, 1633 in the tab , 1638 Views, 1617 Program resources, 1331 Program status Editing blocks, 1651 FBD, 1653 Function, 1648 LAD, 1652 Modify tag, 1651 SCL, 1654 Switching off, 1649 Switching on, 1649 Program_Alarm, 2722 Programming Linear, 1144 Structured, 1144 Programming language Changeover, 1519 FBD, 1441 LAD, 1398 Rules for changing, 1518 Programming recommendations, 159 Programming window Customizing, 1491 SCL, 1490 Project Basics, 241 Carrying out an online/offline comparison, 274 Carrying out offline/offline comparisons, 274 Closing, 249 Comparing data, 36, 273 compile (overview), 4102 Compiling , 4104 WinCC Basic V13.0 System Manual, 02/2014 Index Compiling project data, 264 Creating, 242 Deleting, 249 Detailed comparison, 284 Download, 4107, 4125 download (overview), 4102 Harmonizing, 379 Migrate, 133 Migrating, 115 multilingual, 4054 Multiple connections, 3680, 3730, 3788, 3827 Saving, 248 Showing properties, 248 Simulation with a tag simulator, 4111 Upgrade, 4096 Project archives, 258 Project data Compiling, 264 Downloading to a memory card, 269 Export alarm, 4022 Export text list, 4034 Exporting a recipe, 4018 Exporting tag, 4029 Importing alarms, 4023 Information on compiling, 263 Information on loading, 265 IO-Link master module, 36 Loading, 267 Uploading from a device, 270 Project file Initialization, 4012 Initializing, 4012 Project ID, 3602 Project language, 250, 4048 Activate, 4052 Disabling, 4052 Project languages Changing the editing language, 253 Specifying project languages, 252 System texts, 4055 Use, 250 User texts, 4055 Project library, 49, 326, 3984 Adding types, 359 Assigning a common version to types, 373 Cleaning up, 380 Creating folders, 351 Discarding all versions, 365 Discarding the type version, 365 Migrating, 127 Performing a consistency check for a type version, 364 WinCC Basic V13.0 System Manual, 02/2014 Release all versions, 367 Release the type versions, 366 Updating the project, 368 Using filter view, 353 Using the element view, 329 Using types, 360 Project text Exporting, 4039, 4059 Project texts Application example, 257 Changing the text of selected objects, 254 Displaying reference text, 254, 4058 Exporting all texts, 256 Exporting individual texts, 255 Importing, 256, 4041, 4061 Migrating, 125 Translating individual texts, 4056 Translating project texts, 253 Translation into project languages, 250, 4055 Project tree Adding device, 415 Function, 192 Hiding, 1362 Reducing automatically, 198 Showing, 1362 Project version Upgrade, 4096 Project view, 189 Properties (CPU), 971 Properties of the VPN group, 587 ProSave, 4115 Installation, 64 Protect Function key with password, 3285 Protection concept, 995, 998 Introduction, 288 Revoking access rights, 289 Protection level, 994, 995 Revoking access rights, 289 Protocol, 551 Proxy ARP, 642 PRVREC, 2608 PT, 2058 PTC resistor, 1061 PTO, 42 Pull/plug interrupt (ET 200M), 1072 Pull/plug interrupt OB, 1011 Pulse, 1762, 1771, 1782, 1796, 2039, 2059, 2073, 2303, 2317 Extended, 1785, 1797, 2062, 2074, 2320 Pulse extension, 1057 4741 Index Pulse generator Enabling/disabling with CTRL_PWM, 2764 Pulse interface Principle, 4315 Pulse stretching, 1075 PUT, 3081 PUT / GET, 998 PWM, 42 Q Q PLC, 3901 Q address, 665 Q series, 3904 Q0xUDEH CPU PLC, 3903 QB, 1309 QD, 1309 QRY_CINT, 2696 QRY_DINT, 2708 QRY_TINT, 2704 Quantum, 3931 QW, 1309 QX, 1309 R R, 441, 1747, 2023 R_TRIG, 1760, 2037, 2300 Rack error OB, 1012 Rack or station failure, 1012 Racks, 408 Inserting a module, 418 Radius, 3308 RADIUS, 866 RALRM, 2566 Range Value outside range, 1834, 2113 Value within range, 1833, 2112 Range (... - ...) Graphics list, 3260 RCV_CFG, 2996 RCV_PTP, 3005 RCV_RST, 3006 RCVREC, 2605 RD_ADDR , 2811 RD_DPAR, 2684 RD_DPARA, 2686 RD_DPARM, 2688 RD_LGADR, 2816 4742 RD_LOC_T, 2513 RD_REC, 2596 RD_SINFO, 2729 RD_SYS_T, 2512 RDREC, 2558 RE_TRIGR, 1960, 2243, 2458 Read continuously Tag, 3351 Read field, 1891, 2171 Read memory address, 2393 Read memory bit, 2395 Read system time with TIME_TCK, 2519 READ_BIG, 2406 READ_DBL, 43, 2798 READ_ERR, 2717 READ_LITTLE, 2402 ReadFromArrayDB, 1908, 2190, 2384 ReadFromArrayDBL, 1912, 2194, 2387 Reading A data record with RD_REC, 2596 Asynchronously- data record of a module with RD_DPARA, 2686 Data record of a module with RD_DPAR, 2684 from a data block in load memory with READ_DBL, 2798 Local time with RD_LOC_T, 2513 Reading data From DP standard slaves/PROFINET IO devices with DPRD_DAT, 2601 From remote CPU with GET, 3078 Reading out LED status with LED, 2740 Recipe data record, 4179 Reading out a diagnostics buffer, 1107 Reading tags, 681 Read-only, 994 ReadPLCMode, 3532 REAL, 1220, 1266, 1290 REAL_TO_, 1290 Receiving data on I-device with RCVREC, 2605 Recipe, 675, 3433, 3434, 3435, 4021, 4171 Application example: Machine parameter assignment, 3434 Application example:Batch production, 3434 Basics, 3433, 3434 Control, 4173 Creating new, 3445 Data flow, 4174 Data record, 3435, 4172 Entry, 3435 Exporting, 4018 WinCC Basic V13.0 System Manual, 02/2014 Index Exporting to CSV file, 2766 Importing, 4020 Importing into data block, 2768 Memory requirements, 4192 Use, 3434 Use of text lists, 3440 Recipe data Migration, 128 Recipe data record Create on the HMI device, 3458, 3459 Creating, 4177 Creating new, 3445 Creating on the HMI device, 3458 Deleting, 4179 Editing, 4178 Reading from PLC, 4179 Synchronize with PLC, 4178 Transferring the project, 70 Transferring to PLC, 4180 Use of text lists, 3440 Recipe element Creating new, 3445 Recipe list, 3441 Recipe view, 3441 Application, 3319 Behavior with screen change, 3442 Configuring, 3452 Layout, 3319 Operation using the function key, 3442 Recipe data record, 3436, 3443 Simple, 3441 Toolbar, 3319 Updating, 3442 RecipeExport, 2766 RecipeImport, 2768 RecipeViewBack, 3543 RecipeViewClearDataRecord, 3539 RecipeViewGetDataRecordFromPLC, 3539 RecipeViewMenu, 3540 RecipeViewNewDataRecord, 3539 RecipeViewOpen, 3540 RecipeViewRenameDataRecord, 3542 RecipeViewSaveAsDataRecord, 3542 RecipeViewSaveDataRecord, 3542 RecipeViewSetDataRecordToPLC, 3541 RecipeViewShowOperatorNotes, 3543 Recommissioning HMI device, 4125 Reconnecting Tag, 3346 Reconnecting a PLC tag, 3346 Recording a log file for the modem, 4655 WinCC Basic V13.0 System Manual, 02/2014 Rectangle Configuring, 3246 Inserting, 3245 Inserting and configuring, 3244 Radius corners X, 3318 Radius corners Y, 3318 Redoing actions Basics of redoing actions, 312 Redoing actions, 316 Reference channel, 1058 Reference channel error, 1066 Reference channel of the module, 1068 Reference junction, 891, 1035, 1050, 1058, 1068 Reference language, 250, 4048 Selecting, 4052 Reference object Defining, 3211 Reference project Basics, 261 Closing, 261 Comparing, 262 Opening, 261 Reference temperature, 1058, 1068 References, 159 release, 3582 Release key, 3584 ReleaseButton, 3547 Remainder of division, 1853, 2132 Remote access user, 540 Remote connection as CPU-controlled remote connection, 4647 as dial-up connection, 4610 As VPN connection, 4634 Remote connection cannot be established, 4633 Remote connection from the TS Adapter is not established, 4657 Remote connection to the TS Adapter is not established, 4656 Remote desktop, 30 Remote system access to a programming device/ personal computer, 4648 Remove Formatting in the alarm text, 3389 Object from the group, 3239 Removing Folder link, 3232 Rename Screen, 3190 Tag, 3342 Template, 3196 Renewing the CA group certificate, 592 REPEAT, 2448 4743 Index Replace Cross-references, 4045 REPLACE, 2548 Replace modules during operation, 1072 Replacing Module, 423 Replacing devices, 423 Limitations on connections, 4076 Principle, 4076 Requirements for establishing a remote connection, 4632 Requirements for sending an SMS, 4651 Requirements for sending emails, 4652 Reset, 763 Bit field, 1749, 2026 IEC timer, 1779, 2314 Operand, 1747, 1751, 2023, 2029 To factory settings, 1117, 1118 to factory settings , 4119 Reset timer, 2056 RESET_BF, 1749, 2026 ResetBit, 3544 ResetBitInTag, 3545 Resetting to factory settings, 4119 Resetting the connection, 3156 Resetting the MPI/PROFIBUS settings, 4559 Resetting the TCP/IP settings, 4551 Resetting the user interface layout, 217 Resources, 1638 Code work memory, 1638 Data work memory, 1638 Introduction, 1638 Load memory, 1638 Retentive memory, 1638 Retentive memory data, 1638 Work memory, 1638 Resources tab Structure, 1640 Restart, 763 Restore Data of the HMI device, 4118 Restore process License key, 90 Restore window layout, 215 Restoring, 4158 Data of the HMI device, 4116 HMI device data, 4132 Restoring a backup, 4541 Restoring a device, 4541 Restoring data HMI device, 4116, 4118, 4132 4744 Restriction Modicon Modbus RTU, 3947 Modicon Modbus TCP/IP, 3947 Restrictions due to user rights, 228, 229 Recognizing, 229 RET, 1953, 2237 Retain, 1153 Retentive behavior Bit memory, timers, counters, 1315 Retentive bit memories Enabling the display, 1626 Retentive memory, 1638 Retentivity, 959, 1151 Bit memory, timers, counters, 1315 Block interface, 1391 Data block, 1536 Data block , 1537 PLC tag, 1315 Retentivity of IP address parameters, 915 Retrieving projects, 260 RETURN, 2452 RIGHT, 2545 Ring Redundancy, 816 RIP RIPv2 statistics, 757 RIPv2 Configuration, 863 Interfaces, 863 RLO Invert, 1744, 2021 RMON History, 841 Statistics, 840 ROL, 1992, 2277, 2483 Role name, 541 Roles, 540 System-defined, 540 User-defined, 541 Root certification authorities, 536 Root, square, 2356 ROR, 1990, 2275, 2481 Rotate Left, 1992, 2277, 2483 Object, 3204 Right, 1990, 2275, 2481 Round, 1931, 1933, 1934, 1935, 2214, 2215, 2217, 2218, 2422, 2423, 2424 ROUND, 1931, 2214, 2422 Router, 444 Router IP address, 630 Routing, 724 Routing table, 750 WinCC Basic V13.0 System Manual, 02/2014 Index Static routes, 724 VRRP, 724 Routing mode, 568 RS, 1751, 2029 RS-232/PIP multi-master cable, 988 RT, 1779, 2056, 2314 RT class, 902 RT_INFO, 2737 RTM, 1251, 2520 Rules for configuring MPI networks Rules for assigning the MPI address, 437 Rules for network configuration for PROFIBUS networks Assigning device addresses, 437, 438 RUN, 954 Rung Deleting, 1441 Inserting, 1441 Use, 1439 Runtime Execution of the function list, 3503 Mouse wheel, 68 Simulating, 4109 Start screen, 3191 RUNTIME, 1969, 2253, 2467 Measure program runtime, 1969, 2253, 2467 Runtime data Migration, 128 Runtime language, 4048, 4066, 4133 Font, 4071, 4134 Log, 4072 Order for language switching, 4069 Selecting, 4067, 4133 Runtime meters Handling with RTM, 2520 Runtime settings User administration, 3192, 3467, 3483, 3484 Runtime start Basic Panel, 4108, 4129 Runtime Stop, 3583 Runtime version, 4103 S S, 1748, 2024 S_AVERZ, 1793 S_CD, 1816, 2095 S_COMP, 2522 S_CONV, 2523 S_CU, 1814, 2093, 2338 S_CUD, 2091 S_EVERZ, 1788 WinCC Basic V13.0 System Manual, 02/2014 S_MOVE, 2521 S_ODT, 1788, 2065, 2323 S_ODTS, 1791, 2068, 2325 S_OFFDT, 1793, 2070, 2328 S_PEXT, 1785, 2062, 2320 S_PULSE, 1782, 2059, 2317 S_SEVERZ, 1791 S5TIME, 1223 S7 1200 Communication, 3699 Connection parameters, 3748 HMI connection, 3701 Parameters, 3748 PROFIBUS, 3714 PROFIBUS parameters, 3716, 3718, 3719 PROFINET, 3700 S7 1500 Communication, 3651 Connection parameters, 3694 Data types, 3693 HMI connection, 3653 Parameters, 3694 PROFIBUS, 3665, 3667 PROFIBUS parameters, 3668, 3670, 3671 PROFINET, 3652 PROFINET parameters, 3655, 3656, 3658 S7 200 Communication, 3813 Connection, 3813, 3841 Connection parameters, 3816 Data types, 3840 MPI, 3811, 3820 Parameters, 3811, 3816, 3820, 3821 PPI, 3821 S7 300 Communication, 3753 MPI address, 3782 S7 300/400 Connection parameters, 3806 Data types, 3800 HMI connection, 3755 MPI, 3775, 3776 MPI parameters, 3778, 3780, 3781 Parameters, 3806 PROFIBUS, 3767, 3768 PROFIBUS parameters, 3770, 3771, 3773 PROFINET, 3754 PROFINET parameters, 3757, 3758, 3760 S7 400 Communication, 3753 MPI address, 3783 4745 Index S7 communication Parameter, 3075 Receive data from a remote partner instruction with BRCV, 3089 Receive data from a remote partner instruction with URCV, 3085 Send and receive parameters, 3077 Send data to a remote partner instruction with BSEND, 3086 Send data to a remote partner instruction with USEND, 3083 User data size, 3077 S7 connection, 451 TSAP, 462 S7 CPU Work memory, 957 Load memory, 957 Operand area, 958 S7 routing Loading, 4106 S7-1200, 37 PROFIBUS, 3715 S7-1200 modules, 37 S7-1200 V2 Data types, 3744 S7-CP, 527 S7-PCT, 933 SA lifetime, 589 Safety guidelines, 237 Safety instruction Changing the recipe data record in the background, 3442 Switching tooltip, 4143 Safety precautions when forcing tags, 1684, 1700 Save Data of the HMI device, 4117 Global library, 3994 Save table layout, 214 Save user interface Save layout in editors, 214 Save window layout, 214 Save window layout, 214 Saving a force table, 1688 Saving a watch table, 1661 Saving phone books, 4605 Saving the user interface, 214 SC, 1818, 2097 SCALANCE S, 526 Scale, 1937, 1941, 2219, 2224, 2427, 2435 SCALE, 1941, 2224, 2435 SCALE_X, 1937, 2219, 2427 4746 Scaling Applying linear scaling to a tag, 3351, 3353 Scan operand for negative signal edge, 1754, 2031 Scan operand for positive signal edge, 1753, 2030 Scan RLO for negative signal edge, 1759, 2036 Scan RLO for positive signal edge, 1757, 2035 Scheduler, 3586 Deactivated task, 3591 Event trigger, 3591, 3594 Function list, 3590 Triggers, 3590 Work area, 3589 SCL, 41, 1480, 1731, 1733 Detailed comparison, 1579 Insert comment, 2453 Programming window, 1490 SCL instruction Changing the data type, 1500, 1501 Data type basics, 1499 Inserting, 1498, 1499 Rules, 1497 Selecting, 1515 SCL program Inserting a block call, 1505, 1506, 1508, 1509, 1510, 1511 Inserting an instruction, 1498, 1499 Inserting comments, 1514 Program status display, 1654 Selecting an instruction, 1515 Showing and hiding the parameter list, 1513 Screen Availability for specific devices, 3185 Copy, 3190 Copying, 4087 Creating, 3189 Creating a type, 4003 Deleting, 3190 Font, 3185 Inserting, 3190 Library, 4003 Move, 3190 Rename, 3190 Use template, 3198 Working steps in creating, 3189 Zooming, 3188 Screen change, 3578 Screen keyboard Alphanumerical, 4140, 4142 Key assignment, 4140, 4141 KTP400 Basic, 4139 KTP600, KTP1000, TP1500 Basic, 4141 Language behavior, 66 WinCC Basic V13.0 System Manual, 02/2014 Index Numerical, 4140, 4142 Screen number, 3602 Screen object Dynamic movement, 3270 Screen template, 3280 ScreenObjectCursorDown, 3516 ScreenObjectCursorUp, 3516 ScreenObjectPageDown, 3517 ScreenObjectPageUp, 3517 Script Creating a type, 4002 Library, 4002 Updating tag value, 3333, 3635 SD, 1797, 1799, 2076 SD card Open force job, 31 SE, 1797, 2074 Search Hardware catalog, 407 Security, 40 Security Configuration Tool Configuration views, 528 Security events, 606, 608 Security module, 527 Security program, 82, 86 Security settings, 772 Security system, 4157 SEG, 2011, 2296, 2502 Segment diagnostics Graphic display, 1136 Icons, 1135 Text display, 1136 SEL, 1979, 2264, 2471 Select, 1979, 2264, 2471 Multiple objects, 3210 Selecting Multiple objects, 3204 Selection changed, 3577 Send clock cycle, 921 SEND_CFG, 2995 SEND_PTP, 3003 Sequencer, 1994, 2279, 2485 Serial number, 734 Serialization, 2168, 2369 Serialize, 1887, 2168, 2369 Service & Support, 3619 Service data Saving, 1112 Service groups, 553, 555 Servo motor, 4310 Set Bit field, 1748, 2025 WinCC Basic V13.0 System Manual, 02/2014 Counter start value, 1818, 2097 Operand, 1748, 1750, 2024, 2027 Set limit value, 1862, 2142, 2353 Set operand on negative signal edge, 1756, 2033 Set operand on positive signal edge, 1755, 2032 Set tag on negative signal edge, 1761, 2038, 2301 Set tag on positive signal edge, 1760, 2037, 2300 SET_BF, 1748, 2025 SET_CINT, 2694 SET_TIMEZONE, 2516 SET_TINT, 2697 SET_TINTL, 2700 SetBacklightColor, 3555 SetBit, 3551 SetBitInTag, 3552 SetBitWhileKeyPressed, 3554 SetConnectionMode, 3559 SetDeviceMode, 3550 SETIO, 2563 SETIO_PART, 2564 SetLanguage, 3557 SetPLCMode, 3556 SetTag, 3558 Setting Deadband, 3387 Delay time, 3387 Language, 4144 Languages in the operating system, 4049 Style, 3227 View options for the assignment list, 1622 View options for the dependency structure, 1636 Setting AS-i network configuration parameters, 450 Setting ENO automatically, 1489 Setting language, 4144 Setting parameters for the Ethernet interface, 4549 Adding a dynamic IP address, 4550 Connecting to a subnet, 4548 Deleting dynamic IP addresses, 4550 Modifiable parameters, 4547 Options in the parameter settings, 4547 Setting the communication load, 444 Setting the font, size and color , 1491 Setting the mnemonics, 1364 Setting the tab spacing , 1491 Settings Changing, 186, 1374, 1401, 1444, 1490 FBD, 1401, 1443 General, 183, 185, 186, 1373 LAD, 1401, 1443 SCL, 1489 Settings for the PG/PC interface, 4544 Automatic bus parameter detection, 4552 4747 Index Setting parameters for the MPI interface, 4553 Setting parameters for the PROFIBUS interface, 4555 Seven-segment display, 2011, 2296, 2502 Severity, 568 SF, 1802, 2080 SFP diagnostics, 797 SGN_GET, 3007 SGN_SET, 3008 SHA algorithm, 773 SHA1, 583, 589 Shared device Associated IO controllers, 1100 Shift Left, 1988, 2273, 2479 Right, 1986, 2271, 2477 SHL, 1988, 2273, 2479 Short-circuit to ground, 1056 Short-circuit to L+, 1057 Show Limit lines on the bar, 3298 Show line numbers, 1492 Show/hide interfaces, 4545 ShowAlarmWindow, 3569 Showing and hiding absolute operands, 1492 Showing and hiding columns, 282, 1327, 1397, 1545, 1559 ShowLogonDialog, 3567 ShowOperatorNotes, 3568 SHR, 1986, 2271, 2477 SiClock, 555 Sign, 1857, 2137 Signal board, 669 Inserting, 670 SIMATIC LOGO! Communication, 3840 Connection parameters, 3843 Parameter, 3843 SIMATIC memory card Formatting, 1119 SIMATIC S7 Communication partners, 3699, 3753, 3810, 3819, 3822 SIMATIC S7 Embedded Controller, 38 SIMATIC S7 200 Migrating data types, 139 SIMATIC S7 300/400 Migrating data types, 139 simple alarm view, 4166 Control element, 4167 Operation, 4167 Use, 4166 4748 Simple alarm view Application, 3403 Control element, 3404 Operation, 3404 simple alarm window Application, 3403 Use, 4166 Simple recipe view, 3441 Behavior, 3456, 4176 Layout, 3455, 4175 Menu command, 3456, 4175, 4176 Operation, 3455, 4175 Simple user view, 4158 Layout, 4158 Operation, 4159 Use, 4158 Simulate hardware, 382 Simulate modules, 382 Simulate software, 382 SimulateSystemKey, 3561 SimulateTag, 3562 Simulating Project with tag simulator, 4111 Simulating devices, 382 Simulation, 69 PLC connection, 70 Runtime, 4109 SIN, 1869, 2149, 2359 Sine, 1869, 2149, 2359 Single instance Correcting the call type, 1420, 1461 Definition, 1159 Example, 1159 SINT, 1212, 1260, 1280 SINT_TO_, 1280 Size Editing multiple objects, 3230 SLC, 3883 Slice access, 1192 Slicing, 159 Slot Determining logical address with LGC_GADR, 2818 Determining logical address with LOG_GEO, 2814 Racks, 409 Select, 410 Slot rules, 406 ET 200S, 890 Smartdrive Installation, 49 SMC, 2006, 2291, 2497 WinCC Basic V13.0 System Manual, 02/2014 Index Smoothing, 1049, 1067 SMTP Client, 769 SNC_RTCB, 2518 SNMP, 543, 720, 758, 772 Groups, 772 SNMP trap, 772 SNMPv1, 720 SNMPv2c, 720 SNMPv3, 720 Users, 773 SNMPv1, 583 SNMPv3, 583 Softkey, 3278, 3282 global, 3280 SOFTNET Security Client Configuring in the project, 610 Creating a configuration file, 610 Database, 610 Using, 609 SOFTNET Security Client, 526 Software HMI device, 4114 Software controller Configuring, 4219 Software requirements at the plant end Communications instruction "PG_DIAL", 4649 Software requirements at the system end Communications instruction "AS_MAIL", 4653 Communications instruction "SMS_SEND", 4652 Software requirements for AS-AS remote link Communication instruction "AS_DIAL", 4651 Software requirements for the programming device/ personal computer Communications instruction "PG_DIAL", 4649 Software version, 734 Software-controlled data flow control, 987 SP, 1796, 2073 Spanning Tree Information, 738 Rapid Spanning Tree, 723 Special characters Alarm text, 59 Special considerations Omron Host Link, 3963 Special tag (web server), 684 Speedy Splitter, 387, 390, 392, 402 SQR, 2355 SQR , 1864, 2144 SQRT, 1865, 2146, 2356 Square, 1864, 2144, 2355 Square root, 1865, 2146, 2356 SR, 1750, 2027 WinCC Basic V13.0 System Manual, 02/2014 SRT_DINT, 2707 SS, 1800, 2078 SSH server, 757 SSL certificate, 537 Stamping, 3228 Standard PROFIBUS, 3721, 3774 Standard device, 927 Standard router, 630 Standard slave, 900 Standard user, 540 Standby module Substitute value, 895 Start address, 665, 962 Start information, 1146 Start off-delay timer, 2052 Start on-delay timer, 2050 Start pulse timer, 2048 Start screen, 3191 Start the online and diagnostics view, 1094 Start the simulation, 383 Start value, 41 Tag, 3349, 3350 Starting removal, 101 Starting the migration tool, 108 Starting the topology view, 512 Startup, 999 Organization blocks, 999 STARTUP Function, 951 STARTUP activities, 952 Startup OB Description, 999 Start-up parameters, 953 Startup routine, 999 Startup type, 971 Stateful packet inspection, 547 Station Copying, 421 Deleting, 420 Moving, 422 Read information with GetStationInfo, 2748 Renaming, 522 Station name, (See device name) Status, 1003 Module defective, 1107 Status interrupt, 1003 Status interrupt OB, 1003 Status of the online connection, 1131 Stepper motor, 4310 STL Detailed comparison, 1576 4749 Index STL source Generating blocks, 1564 STOP, 954 Stop forcing, 1706, 1707 StopRuntime, 3563 Storing External graphic, 3233 STP, 1960, 2244, 2458 Strg_TO_Chars, 2529 STRG_VAL, 2524 String Comparing tags with S_COMP, 2522 STRING, 1200, 1231, 1272, 1298 Addressing, 1191 STRING_TO_, 1298 STRUCT Addressing, 1191 Declaration in global data blocks, 1532 Declaration in the block interface, 1384 Declaring in a PLC data type, 1555 Structure, 1239 Structure, 1052, 1064 Call structure, 1629 of the cross-reference list, 1643, 4043 Of the dependency structure, 1634 Resources tab, 1640 STRUCT, 1239 Structured programming, 1144 Style Changing, 3200 Creating a new type, 4004 Deleting, 3199 Edit, 3200 Setting, 3227 SUB, 1849, 2128 Subnet, 446 Subnet mask, 444, 907 Substitute value Standby module, 895 Subtract, 1849, 2128 Subtracting Subtracting timers with T_SUB, 2508 Supply voltage, 1058 SWAP, 1906, 2188, 2382 Swap bytes, 1906 Switch, 3320, 4154 Application, 4154 Behavior, 4155 Layout, 4154 Operation, 4154 Type, 3321 SWITCH, 1950, 2234 4750 Switch buffer, 3689, 3848 Switch OFF, 3585 Switch ON, 3585 Switching between basic mode and expanded mode in the force table, 1685 Switching between basic mode and expanded mode in the watch table, 1657 Switching operating mode, 1113 Switchover time, 989 Switchport, 925, 3663, 3712, 3765 Symbol Alarm classes, 3395 For value comparison, 4225 Symbolic addressing, 160 of a tag, 3335, 3637 Symbolic I/O field, 3323 Mode, 3324 Text list, 3254, 3324 Symbolic IO field, 4155 Application, 4155 Behavior, 4156 Operation, 4156 Symbolic programming Displaying absolute addresses, 1365 Symbolism, 157 Symbols In the assignment list, 1620 In the call structure, 1628 In the dependency structure, 1635 Sync domain, 926, 1100, 3664, 3713, 3766 Sync domain properties, 1100 SYNC_PI, 2555 SYNC_PO, 2556 Synchronization From DP slaves with DP_SYC_FR, 2610 Slave clocks with SNC_RTCB, 2518 Synchronization (user-defined web pages), 677 Synchronize, 3333, 3635 Synchronizing a PLC tag, 3346 Synchronizing user-defined web pages, 3172 Synchronous Transferring data, 3684, 3792, 3835, 3977 Synchronous errors Masking with MSK_FLT, 2715 Querying the error register with READ_ERR, 2717 Unmasking with DMSK_FLT, 2716 Syntax Addressing, 3863 Syntax errors Basics, 1517 Finding errors, 1517 WinCC Basic V13.0 System Manual, 02/2014 Index Syntax for AWP commands, 680 Syslog Client, 784 Syslog server, 599 System General information, 759 System configuration, 757 System alarm, 3372 Meaning, 3408, 3409, 3413, 3418 System block System blocks folder, 1331 System diagnostics, 3429 Detail view, 3430 Device view, 3430 Diagnostic buffer view, 3430 System diagnostics view, 3429 System diagnostics view Configuring, 3432 Detail view, 3325 Device view, 3325 Diagnostic buffer view, 3325 System event, 3372 Meaning, 3408, 3409, 3412, 3413, 3415, 3416, 3417, 3418, 3419, 3420, 3422, 3424, 3425 Parameters, 3408 System events, 605, 608 Configuring, 3381 System function Application, 3498 Function list, 3500 In the function list, 3498 Usage, 3497 Use, 3498 System functions, 3496 AcknowledgeAlarm, 3538 ActivateCleanScreen, 3512 ActivatePreviousScreen, 3513 ActivateScreen, 3510 ActivateScreenByNumber, 3511 AdjustContrast, 3509 AlarmViewAcknowledgeAlarm, 3537 AlarmViewEditAlarm, 3536 AlarmViewShowOperatorNotes, 3537 Available, 3506 CalibrateTouchScreen, 3524 ChangeConnection, 3566 ClearAlarmBuffer , 3534 ClearAlarmBufferProTool , 3535 DecreaseFocusedValue, 3564 DecreaseTag, 3565 EditAlarm, 3515 GetGroupNumber, 3531 GetPassword, 3531 WinCC Basic V13.0 System Manual, 02/2014 GetUserName, 3530 GoToEnd, 3520 GoToHome, 3519 IncreaseFocusedValue, 3518 IncreaseTag, 3519 InvertBit, 3521 InvertBitInTag, 3522 InvertLinearScaling, 3523 LinearScaling, 3533 Logoff, 3509 Logon, 3514 PageDown, 3550 PageUp, 3549 PressButton, 3546 RecipeViewBack, 3543 RecipeViewClearDataRecord, 3539 RecipeViewGetDataRecordFromPLC, 3539 RecipeViewMenu, 3540 RecipeViewNewDataRecord, 3539 RecipeViewOpen, 3540 RecipeViewRenameDataRecord, 3542 RecipeViewSaveAsDataRecord, 3542 RecipeViewSaveDataRecord, 3542 RecipeViewSetDataRecordToPLC, 3541 RecipeViewShowOperatorNotes, 3543 ReleaseButton, 3547 ResetBit, 3544 ResetBitInTag, 3545 ScreenObjectCursorDown, 3516 ScreenObjectCursorUp, 3516 ScreenObjectPageDown, 3517 ScreenObjectPageUp, 3517 SetBit, 3551 SetBitInTag, 3552 SetBitWhileKeyPressed, 3554 SetConnectionMode, 3559 SetDeviceMode, 3550 SetLanguage, 3557 SetTag, 3558 ShowAlarmWindow, 3569 ShowLogonDialog, 3567 ShowOperatorNotes, 3568 SimulateSystemKey, 3561 SimulateTag, 3562 StopRuntime, 3563 TraceUserChange, 3564 TrendViewBackToBeginning, 3529 TrendViewCompress, 3527 TrendViewExtend, 3526 TrendViewRulerLeft, 3528 TrendViewRulerRight, 3527 TrendViewScrollBack, 3526 4751 Index TrendViewScrollForward, 3525 TrendViewSetRulerMode, 3528 TrendViewStartStop, 3529 UpdateTag, 3514 System limits HMI device, 4183, 4187 System log, 605, 608 System memory, 971, 992 Diagnostics buffer, 961, 1129 Operand areas, 958 process image input/output, 960 System power supply, 1064 System requirement for WinCC Basic, 83 System requirements STEP 7 Basic, 80 System texts, 251 System Time NTP Client, 779 PTP Client, 781 SNTP Client, 778 System-defined role Administrator, 540 diagnostics, 540 Remote access, 540 standard, 540 System-defined text lists Editing, 321 Modifying texts, 322 System-relevant information Module information, 1095 Vendor information, 1095 T T_ADD, 2507 T_COMBINE, 2510 T_COMP, 2506 T_CONFIG, 43, 3162 T_CONV, 2507 T_DIAG, 3157 T_DIFF, 2509 T_RESET, 3156 T_SUB, 2508 Table Connection, 3624 Table:Designing a border, 3223 Tag absolute addressing, 3334, 3636 Acquisition cycle, 3350, 3357, 3367 Acquisition mode, 3350 Addressing, 3337 Changing the PLC, 3354 Comment, 3339 4752 Configuration, 3343 Configuring several tags, 3343 Connection to PLC, 3337 Copy, 3342 Creating external tags, 3337 Creating internal tags, 3339 Data type, 3339 Deleting, 3342 Displaying or hiding tag information, 1433, 1474, 1502 Displaying values, 3368 Event, 3356 Exporting, 4029 External tag, 3332, 3634 Importing, 4031 in Runtime, 3350 Index tag, 3354, 3355 Indirect addressing, 3354, 3355 Internal tag, 3336, 3638 Length, 3339 Limit range, 3347 Limit value, 3348 Linear scaling, 3351, 3353 Maximum length, 66 Multiplexing, 3354 Name, 3339 Negative, 1761, 2038 Object list, 3338 Output in alarm, 3388 Overlaying, 1193 Overview, 1179 PLC tag, 1305 PLC tags and DB tags, 1179 Positive, 1760, 2037 Read continuously, 3351 Reconnecting, 3346 Rename, 3342 Start value, 3349, 3350 symbolic addressing, 3335, 3637 Update, 3351, 3357 Tag data Structure for the import, 4032, 4037 Tag declaration Automatically filling in cells, 1327, 1397, 1544, 1559 Based on a PLC data type, 1533 Block interface, 1375 Declaring ARRAY, 1383 Declaring PLC data type, 1385 Declaring STRUCT, 1384 Declaring tags, 1381, 1382, 1386 Deleting a tag, 1326, 1396, 1543, 1558 WinCC Basic V13.0 System Manual, 02/2014 Index Importing and exporting tags, 1397, 1545 Inserting a table row, 1324, 1395, 1542, 1558 Inserting table rows at the end, 1396, 1543, 1558 Multi-instance, 1387 Overlaying tags, 1386 Purpose of tag declaration, 1375 Reserved key words, 1173 Retentivity, 1391 Showing and hiding columns , 1327, 1397, 1545, 1559 Sorting rows, 1326 Tag properties, 1390, 1392, 1538, 1540, 1541 Updating the block interface, 1387 Valid data types, 1378, 1380 Tag import Tag data structure, 4032, 4037 Tag list Indirect addressing, 3354, 3355 Tag simulator, 4112 Tag table Default, 3331, 3633 for HMI devices, 3331, 3633 user-defined, 3331, 3633 Tag value Output, 3368 Tags Basics, 3330, 3632 Data exchange, 3601 Migrating, 121 Migration, 135 Monitor all, 1672, 1697 Monitor now, 1698 Monitor once and now, 1673 Tan, 2361 TAN, 1871, 2152 Tangent, 1871, 2152, 2361 Task, 3588 Deactivate, 3591 Task card, 3186 Changing the pane mode, 207 Function, 205 Hardware catalog, 399, 3617 Reducing automatically, 198 Task Card Online Tools, 1095 Tools, 3200 TCI (Tool Calling Interface), 932 TCON, 3124, 3127 TCON_IP_RFC, 493 TCON_IP_v4, 492 TCON_Param, 489 TCP, 551 WinCC Basic V13.0 System Manual, 02/2014 Characteristics, 488 Port numbers, 494 TDISCON, 3132 Team Engineering Creating a master project, 4513 Example of the program structure in the master project, 4520 Integrating project copies into the master project once again, 4515 Introduction to shared commissioning, 4513 Notes on compatibility, 4515 Procedure for creating the master project, 4517 Procedure for integrating project copies into the master project, 4518 Procedure for manual synchronization of competing changes, 4518 Procedure for modifying central objects within the master project, 4519 Procedure for shared commissioning, 4517 Requirements for shared, parallel working on the project, 4516 Rules for downloading to the CPU, 4522 Rules for editing shared central objects, 4522 Rules for online functions, 4523 Rules for shared working on one CPU, 4521 Rules for the master project, 4520 Software and hardware requirements, 4515 Working with project copies, 4514 Technology object command table: Shortcut menu commands, 4366 Technology objects PID_3Step, 4276 PID_Compact, 4245 Telecontrol server, 703 TELECONTROL SERVER BASIC, 703 TeleService Meaning of the icons, 4603 Phone book properties, 4601 Access to phone books, 4602 AS_DIAL, 4649 Callback variants, 4615 Communications instruction:"AS_DIAL", 4600 Communications instruction:"AS_MAIL", 4601 Communications instruction:"PG_DIAL", 4600 Communications instruction:"SMS_SEND", 4601 Communications instruction:"TM_MAIL", 4601 Communications instruction:"TMAIL_C", 4601 Connection establishment options:S7-1200 CPUs, 4647 Connection establishment options:S7-1500 CPUs, 4647 4753 Index Connection establishment options:S7-300/400 CPUs, 4647 Defining dialing rules, 4608 Establish connection to AS, 4649 Export phone book, 4607 Functionality, 4600 Gateways, 4612 Import phone book, 4605 Inserting rows in the phone book, 4604 Modem support, 4611 Modem types / media, 4612 Open phone book, 4604 Performance in telephone networks, 4612 Phone book, 4601 Printing the phone book, 4608 Save phone book, 4605 Showing or hiding columns in the phone book, 4605 Structure of the phone book, 4603 Transferring e-mail with TM_MAIL, 3174 Working with the phone book, 4602 TeleService callback options, 4617 TeleService phone book, 4601 TeleService via GPRS, 707 Establish connection, 708 Temperature coefficient, 1048, 1067 Temperature compensation, 1035 template Template, 3196 Template, 3278 Copy, 3196 Creating, 3195 Deleting, 3196 Global screen, 3195 Inserting, 3196 Move, 3196 Rename, 3196 Use in screen, 3198 temporary, 704 Temporary connection, 704 Temporary station, 704 Tens complement, 2013, 2298, 2504 Terminal modules and electronic modules, 1032 Terminating the remote connection, 4633 Test options in the force table, 1682 Text Button, 3322 Text field, 3326 Text field, 3326 Size, 3327 Text field length Asian languages , 4136 4754 Text list Application, 3248 Bit (0, 1), 3253 Bit number (0 - 31), 3254 Creating, 3249 Exporting, 4034 Importing, 4036 Symbolic I/O field, 3254, 3324 Value/Range, 3251 Text lists Introduction, 319 System-defined, 319 Use in recipe data records, 3440 User-defined, 319 Texts Migrating, 125 TFTP Load/save, 765 THEN, 2440 Third-party drivers Communication, 3852 Special features, 3853 THIS, 1187 TIA Portal Exiting, 183 Starting, 183 Time, 758, 971, 1223, 1225 TIME, 1225, 1268, 1293 Time accumulator, 1769, 2046, 2054, 2311 Time delay, 1968, 2252, 2466 Time delay interrupt, 1005 Time duration, 1780, 2058, 2315 Time error interrupt, 1008 Time error OB, 1008 Time expired, 3586 Time of day Precision Time Protocol, 781 Setting the time of day in the Online and Diagnostics view, 1114 SNTP (Simple Network Time Protocol), 778 System Time, 775 Time-of-day synchronization, 778 Time stamp, 3380 Time stamping, 1036 Time synchronization, 579, 971 TIME_TCK, 2519 TIME_TO_, 1293 Time-delay interrupt Canceling with CAN_DINT, 2708 Instructions, 2705 Querying with QRY_DINT, 2708 Starting with SRT_DINT, 2707 WinCC Basic V13.0 System Manual, 02/2014 Index Time-delay interrupt OB, 1005 Time-of-day, 1227, 1228, 1229 Calculating local time with SET_TIMEZONE, 2516 Reading the system time of the CPU with TIME_TCK, 2519 Reading time-of-day and date of CPU with RD_SYS_T, 2512 Setting for CPU with WR_SYS_T, 2511 Time-of-day function Basics, 978 Clock parameters, 979 Reading the time-of-day, 978 Setting the time-of-day, 978 Time-of-day format, 978 Time-of-day interrupt Activating with ACT_TINT, 2703 Cancel, 1001 Canceling with CAN_TINT, 2702 Function, 1001 Querying with QRY_TINT, 2704 Rules, 1001 Set and activate, 1001 Setting with SET_TINT, 2697, 2700 Status query, 1001 Time-of-day interrupt OB Parameter assignment, 1014 Timer, 1225, 1782, 2059 Recording, 1777 TIMER, 1247 Timers Adding with the instruction T_ADD, 2507 Combine date and time with T_COMBINE, 2510 Comparing time tags with T_COMP, 2506 Converting with T_CONV, 2507 Determining difference with T_DIFF, 2509 Subtracting with T_SUB, 2508 Time-triggered trends, 3690, 3847 TM_MAIL, 3174 TMAIL_C, 3114 TO, 2444 TO_PositioningAxis, 4335 TOD, 1227, 1269, 1295 TOD_TO_, 1295 TOF, 1767, 1775, 2044, 2052, 2308 Toggle Between runtime languages, 4135 Between Runtime languages, 4066 TON, 1765, 1773, 2042, 2050, 2305 TONR, 1769, 1777, 2046, 2054, 2311 Tool Calling Interface (TCI), 932 WinCC Basic V13.0 System Manual, 02/2014 Toolbar Order, 3204, 3213 Tools, 3200 Tooltip display, 4143 Topology discovery, 926, 3664, 3713, 3766 Topology editor, 446 Topology view Adding device, 415 Adopt devices identified online, 526 Adopt port interconnections identified online, 525 Configured topology, 512, 513 Diagnostics status in the graphic view, 515 Diagnostics status in the table view, 515 Differences compared with the network view, 511 Functions, 510 Hardware and network editor, 392, 3613 Interconnecting ports, 518 Offline/online comparison, 516 Touch operation IO field, 4148 TP, 1762, 1771, 2039, 2048, 2303 TP177A Loading a project, 65 Trace, 4561 Bit track, 4566 CPU load, 4588 Curve diagram, 4566, 4585 Data storage, 4563 Installed traces, 4571 Lifetime of the values, 4587 Measurement, 4563, 4573, 4583 Measurement cursor, 4585 Pre-trigger, 4594 Printing, 4586 Project navigator, 4566 Quantity structure, 4588 Quick start, 4574 Recordable tags, 4586 Recording, 4563, 4582 Recording conditions, 4591, 4592, 4594 Recording cycle, 4576, 4598 Recording duration, 4598 Recording levels, 4587 Reduction, 4592 Sampling, 4576 Saving the trace configuration, 4581 Signal table, 4568, 4585 Signals, 4590, 4597 Supported devices, 4561 Trace configuration, 4563, 4571, 4580, 4581, 4584, 4597 4755 Index Trace editor, 4580 Trace handling, 4570 Trigger, 4599 Trigger mode, 4593 Trigger tag, 4591, 4593 Trigger time, 4573 User interface, 4564, 4589 Trace function, 4561 Trace S7-1200/1500, 4586 TraceUserChange, 3564 Transfer card, 955 Transfer card; see Transfer card, 955 Transferring Recipe data record, 4180 Transferring data Area pointer, 3639, 3674, 3723, 3783, 3822, 3967 Area pointer screen number, 3675, 3729, 3783, 3823, 3968 Coordination area pointer, 3678, 3727, 3786, 3826, 3971 Data record are pointer, 3975 Data record area pointer, 3682, 3733, 3790, 3830 Date/time area pointer, 3675, 3724, 3725, 3784, 3823, 3969 Date/time PLC area pointer, 3677, 3785, 3824, 3970 Job mailbox, 3685, 3736, 3794, 3832, 3979 Job mailbox area pointer, 3680, 3731, 3788, 3828, 3973 Operator input in the recipe view, 3735, 3793, 3831, 3978 Possible cause of error, 3687, 3738, 3796, 3834, 3981 Project ID area pointer, 3679, 3730, 3787, 3827, 3972 Triggering by means of a configured function, 3686, 3737, 3795, 3833, 3980 With synchronization, 3684, 3792, 3835, 3977 Without synchronization, 3683, 3734, 3791, 3835, 3976 Transferring the project HMI device, 70 Recipe data record, 70 Translate Editor, 4054 Translating texts, 250 Transmission medium/duplex, 923 Transmission rate / duplex, 3662, 3711, 3764 Transparency In graphic, 3231 transparent color, 3305 4756 Display on panels, 3305 Display on the panel HMI, 4149 TRCV, 3140, 3144 TRCV_C, 43, 3102, 3107 Trend request Trend transfer, 3689, 3848 Trend request area, 3689, 3848 Trend transfer area, 3689, 3848 Trend transfer area 1 Trend transfer area 2, 3689, 3848 Trend view, 3309, 4151 Application, 4151 Button, 3310 Configuring for values from the PLC, 3369 Layout, 4151 Operation, 4152 Operator control, 4152 TrendViewBackToBeginning, 3529 TrendViewCompress, 3527 TrendViewExtend, 3526 TrendViewRulerLeft, 3528 TrendViewRulerRight, 3527 TrendViewScrollBack, 3526 TrendViewScrollForward, 3525 TrendViewSetRulerMode, 3528 TrendViewStartStop, 3529 Trigger tag, 3380 Triggering by means of a configured function Transferring data, 3686, 3737, 3795, 3833, 3980 Triggers, 3590 Event trigger, 3591, 3594 TRUE, 2300, 2301 TRUNC, 1935, 2218, 2426 TS adapter, 69 TS Adapter IE Advanced Brief description, 4642 Connection types, 4643 Parameter assignment, 4645 Parameter assignment options, 4644 TS Adapter MPI Brief description, 4619 Default parameter assignment, 4620 Direct connection, 4620 Establishing a modem connection, 4621 Establishing the direct connection, 4620 Exporting adapter parameters, 4625 Importing adapter parameters, 4626 Modem connection, 4621 parameter Assignment, 4623 Parameter assignment , 4623 Parameter assignment options, 4622 Principle of operation, 4619 WinCC Basic V13.0 System Manual, 02/2014 Index Restoring the default parameter assignments, 4624 Setting up access protection, 4616 TS Adapter IE Brief description, 4626 Default parameter assignment, 4628 Parameter assignment, 4631, 4645 Principle of operation, 4627 TS Adapter IE Basic Connection to the GSM network, 4629 Connection to the telephone network, 4629 Connection to the telephone network through an external modem, 4630 Connection types, 4628 TSAP ASCII code table, 498 Structure, 462, 497 TSAP assignment Examples, 499 TSEND, 3134, 3137 TSEND_C, 3091, 3095 TURCV, 3153 TUSEND, 3150 Twos complement, 1854, 2133 Type Library, 3987 TypeOf, 2344 TypeOfElements, 2345 Types of DP slave, 886 U UART data transmission, 983 UBLKMOV, 1925, 2207, 2415 UDINT, 1216, 1265, 1289 UDINT_TO_, 1289 UDP, 551, 557, 578 Characteristics, 489 Port numbers, 494 UDT, 40, 158, 168 UFILL_BLK, 1904, 2186, 2380 UINT, 1215, 1263, 1285 UINT_TO_, 1285 ULINT, 1219 UMOVE_BLK, 1900, 2181, 2377 Underflow, 1050, 1058 Undoing actions Basics of undoing, 312 Undoing last action, 315 Undoing multiple actions, 315 Uninstalling license keys, 78 WinCC Basic V13.0 System Manual, 02/2014 Uniqueness of object names, 113 Universal PROFIBUS, 3721, 3774 Universal Serial Interface Protocol, (See USS protocol) Universal symbolism, 157 Unknown peers, 591 Unlock User, 3483 Unplugged module, 412 Unscale, 1943, 2227, 2438 UNSCALE, 1943, 2227, 2438 Unspecified CPU, 416 UNTIL, 2448 UPDAT_PI, 2551 UPDAT_PO, 2553 Update, 1004 Tag, 3351, 3357 Update cycle, 3367 Update interrupt, 1004 Update interrupt OB, 1004 Update time, 921 UpdateTag, 3514 Updating Device proxy, 4010, 4015 IPE data, 4010, 4015 Operating system, 4119 Updating a library, 377, 3996 Updating the device version, 4118 Updating the firmware , 4118 Updating the operating system, 4118 Updating types to the latest version, 377, 3996 Upgrade Global library, 4097 Project, 4096 Project version, 4096 Upgrading a global library, 342 Upload, 935 URCV, 3085 USB card readers, 32 Use, 3434 Of recipes, 3434 Screen navigation function keys, 3290 simple alarm view, 4166 simple alarm window, 4166 Simple user view, 4158 System function, 3498 Use global assignment Function key, 3194 Useful information on configuring the TS Adapter MPI, 4622 4757 Index USEND, 3083 User Assigning roles, 542 Changing, 3482 Creating roles, 540 Deleting in runtime, 3483 Logon, 3484 Setting up, 539 Unlock, 3483 User administration, 3463 Migration, 128 Object with access protection, 3486 Runtime settings, 3192, 3467, 3483, 3484 Setting up, 3489 User change, 3578, 3593 User data Area, 962 Backing up, 4158 Restoring, 4158 User group, 4157 Administer authorizations, 3475 Assigning, 3494 Assigning users, 3473 Change displayed name, 3476 Changing in runtime, 3483 Changing the name, 3475 Creating, 3493 Deleting, 3476 Managing, 3475 Unauthorized, 3485 User interface "Reference projects" palette, 207 Details view, 209 Inspector window, 203 Maximizing the work area, 197 Minimizing the work area, 197 Overview window, 210 Portal view, 187 Project tree, 192 Project view, 189 Task card, 205 Views, 187 Work area, 195 User interface language, 4048 Selecting, 4051 User name, 540 User program Finding errors, 1517 Function, 1143 Testing, 1647 User texts, 251 User view, 3477 4758 Application, 3299 Complex user view , 3479 Configuring, 3480 Layout, 3300 Number of lines, 3300 Simple user view, 3477 User-defined, 29 User-defined functions In function lists, 3500 User-defined roles, 541 User-defined text lists Creating, 320 Editing, 321 Editing value ranges and texts, 321 User-defined web pages, 676, 679, 688, 690, 691 Users, 4157 Admin, 4163 Assigning a user group, 3473 Changing the name, 3474 Changing, touch operation, 4162 Create, 3472 Creating, 3494, 4159 Creating in runtime, 3480 Creating, touch operation, 4159, 4161 Deleting, 3475, 4163 Logging logons, 3488 Logoff, 4160 Managing, 3474, 3482 Updating after change of user, 3593 Using a TS Adapter for TeleService, 4610, 4634 Using frames and cover pages from the library, 297 Using tags, 3301 Using the keyboard Editing texts, 1358 FBD, 1358 GRAPH, 1358 LAD, 1358 Program editor, 1358 SCL, 1358 STL, 1358 Using the on-screen keyboard, 228 Using UDTs, 168 USINT, 1213, 1261, 1282 USINT_TO_, 1282 USS communication Controlling a transmission to a drive with USS_PORT, 3014 Data exchange with drives via USS_DRIVE, 3015 Modifying parameters in the drive with USS_WPM, 3019 Reading parameters from the drive with USS_RPM, 3017 WinCC Basic V13.0 System Manual, 02/2014 Index USS protocol Instructions, 3009 USS status codes, 3020 USS_DRIVE, 3015 USS_PORT, 3014 USS_RPM, 3017 USS_WPM, 3019 V VAL_STRG, 2526 Valid Data type, 3859, 3903, 3913, 3930, 3943, 3959 Data types, 3693, 3744, 3800, 3840 Valid data type Allen-Bradley DF1, 3881 Value, 1857, 2137 Value assignment, 1487 Value change, 3585 Value/Range Text list, 3251 Values Comparing, 4225, 4336, 4362 Variable index, 166 VARIANT, 174, 1245, 1837, 1838, 1839, 1841, 1919, 1920, 1921, 2116, 2117, 2118, 2119, 2201, 2202, 2203, 2344, 2345, 2409, 2410, 2412, 2431, 2433 VARIANT_TO_DB_ANY, 2431 VariantGet, 1919, 2201, 2409 VariantPut, 1920, 2202, 2410 Vendor ID, 734 Version overview, 1021 Versioning of types Released version, 357 Version in progress, 356 Version in test, 356 Versions in WinCC, 4092 Vertical movement Animation, 3271 Vertical radius, 3304 View options For the assignment list, 1622 Setting the call structure, 1631 Setting the dependency structure, 1636 Views of the cross-reference list, 1643, 4043 Virtual Machine (VM) Supported virtualization platforms, 81, 85 Virus scanners, 86 VLAN, 717 Day, 807 Port VID, 807 Priority, 807 WinCC Basic V13.0 System Manual, 02/2014 VLAN ID, 720 VLAN tag, 719 VLAN operation, 587 VLAN tagging, 587 VMware - PC CPs, 39 VOID, 1247 VPN connection Deleting CA certificates, 4640 Establishing, 4640 Installing CA certificate, 4637 Terminating, 4642 VPN connection is not established Check and remedy, 4660 VPN group, 585 VRRP Address overview, 853 Backup router, 724 Configuration, 852 Master router, 724 Router, 851 Virtual router, 724 VRRP router, 724 VRRP Statistics, 740 W WAIT, 1968, 2252, 2466 Wake on LAN, 2642 Wake-up call, 704 Wake-up SMS, 704 WAN IP address Specifying, 596 Warm restart, 952 Watch table Meaning of the icons, 1658 Basic mode, 1656 Copying, 1660 Creating, 1659 Example of filling out a watch table, 1661 Expanded mode, 1656 Layout, 1656 Loading data blocks during an active control job, 44 Meaning of the columns, 1656 Monitoring and modifying modes, 1670 Multiple access to the same CPU, 44 Opening, 1660 Overview of the display formats, 1665 Overview of the test options, 1655 Permitted operands, 1662 Permitted operands for modify values, 1663 Possible applications, 1655 4759 Index Saving, 1661 Switching between basic mode and expanded mode, 1657 Syntax check, 1661 Testing wiring, 1655 Watchdog time, 922 WCHAR, 1231 Web application, 676 Web Control DB, 692 Web data blocks, 690 Web pages in browser, 697 Web server, 663, 670, 672, 676, 679, 690 Enable, 673 Enumerations, 688 Fragment, 688 HTTPS, 674 When dialog is closed, 3578 When dialog is opened, 3577 When high limit is exceeded, 3577 When low limit is undershot, 3577 WHILE, 2446 WinCC flexible project Migrate, 133 Migrating, 115 WinCC V7.0 SP3, 51 WinCC version Compatibility, 4093 WinCC flexible Runtime Closing, 4131 Window layouts Changing order, 216 Deleting window layouts, 216 Wire break, 1049, 1066 Wireless LAN/PB link, 902 Wiring tests, 1655 Wizard Device wizard, 3982 WORD, 1210, 1258, 1275 WORD_TO_, 1275 Work area Embedding floating elements, 200 Floating elements, 200 Function, 195 Maximizing, 197 Maximizing elements, 202 Minimizing, 197 Minimizing elements, 202 Saving a layout of editors and tables, 216 Splitting, 199 Switching between elements, 202 Using grouped elements, 200 Work memory, 957, 1638 4760 Working step to create screens, 3189 WR_DPARM, 2690 WR_LOC_T, 2513 WR_REC, 2600 WR_SYS_T, 2511 WRIT_DBL, 43, 2800 Write field, 1892, 2173 Write memory address, 2397 Write memory area, 2400 Write memory bit, 2399 WRITE_BIG, 2407 WRITE_LITTLE, 2404 WriteToArrayDB, 1910, 2192, 2386 WriteToArrayDBL, 1916, 2198, 2390 Writing A data record with WR_REC, 2600 Writing data in remote CPU with PUT, 3081 To DP standard slaves/PROFINET IO devices with DPWR_DAT, 2603 Writing tags, 683 WRREC, 2560 WSTRING, 1200, 1233 Addressing, 1191 WWW (instruction), 691 WWW Synchronizing user-defined web pages, 3172 X xlsx file, 4023, 4030, 4034, 4036 XOR, 1485, 1486, 1974, 2018, 2019, 2258 Z Zoom Adjusting the zoom setting, 388, 390, 393, 3606, 3612, 3614 Keyboard operation, 403 Zooming Screen, 3188 WinCC Basic V13.0 System Manual, 02/2014